 |
 |
|
Epok®
Federated Acess Manager allows business people responsible for sensitive information to distribute the authority to access information across organizational boundaries thereby enabling new techniques of information-sharing and collaboration. Our applications further manage the risks associated with cross-organizational information-sharing by creating accountability through strong auditing and forensic capabilities. Our unique product set has many touch points in your infrastructure and potentially the infrastructures of partners with whom you are collaborating. Additionally, the nature of sharing sensitive information across new boundaries is filled with security, trust, and policy hurdles. Consequently, deployments need to be well defined and well planned. In addition to engagements specific to each implementation, we offer a Quick Start engagement which is a five to ten day effort designed to quickly provide a customer with a working Epok deployment.
Epok’s Professional Services organization utilizes the following approach for the implementation and deployment of Epok Federated Acess Manager solutions. The processes, templates, checklists, and other guidance included in Epok’s methodology ensure success.  Epok Federated Acess Manager Deployment Process
Data Sharing Analysis and Baseline Architecture The activities of this phase are oriented towards the definition of the specific requirements of the solution and the data sharing landscape of interest. The foundation elements of the solution space are identified and documented. These include fully defining the objectives of the deployment and identifying key elements of the foundation such as the users, user needs, documents and resources to be shared, resource owners, partners involved in the sharing, access policy, and several other areas. The gathering, analysis, and aggregation of this information allow us to create the Epok Federated Acess Manager Solution Definition – a document used in all of the subsequent process phases. Solution Architecture Using the Epok Federated Acess Manager Solution Definition document as a foundation, Epok, with your input, will identify, architect, and document the physical architecture of the Epok Federated Acess Manager deployment. In addition, we will also identify existing infrastructure components to integrate with, specifications for any custom integration work, and security components that will comprise the solution. Implementation Implementation encompasses all of the activities necessary to install, configure, integrate, and test the Epok Federated Acess Manager solution. At the end of this implementation phase, and in conjunction with the completion of Deployment Planning, the solution will be ready for production deployment. Implementation consists of a variety of activities including Installation and configuration of Epok Federated Acess Manager components, establishment of an AuthorityNet using Epok Federated Acess Manager Architect, integration with existing software and network infrastructure, and testing. Deployment Planning Deployment planning spans much of the implementation, runs in parallel to several of the phases above, and must address all aspects of the deployment so that the likelihood of success is maximized. Activities are focused around the development of a procedure for readiness determination, development of a step-by-step plan for the deployment into production operations, and preparedness of the user community. Deployment Deployment refers to the controlled release of the implemented and tested solution into a production environment specifically for the purpose of providing Epok Federated Acess Manager -based capabilities to the intended user audience. Therefore, the details of the deployment are governed by the results of the Deployment Planning phase described above.
Operations Planning Operations planning is necessary to ensure that the necessary roles, responsibilities, tools, and procedures are identified and in place to support the deployed solution. This planning is typically the responsibility of the customer or integrator (i.e., someone who is familiar with the operational requirements, procedures, and environment in which the Epok Federated Acess Manager solution is deployed) with Epok providing a supporting role with respect to operations of the Epok Federated Acess Manager solution. Depending on the deployment scenario, details of this planning can vary widely. Operations planning activities typically include planning and preparedness for customer support, downtime due to outages or maintenance, backup and recovery, monitoring, and reporting. Operations Operations refers to the execution, by the designated individuals, of the tasks and responsibilities identified during the Operations Planning phase described above. |
|
 |