|
Implementation
The chart below depicts the phases of activity and the individual steps involved in each phase.
This way, an outline is created for the typical implementation of the eSD product.
During the analysis phase, we conduct a preliminary study of the 'customer environment' in order to assess current software management methods, as well as to determine and document the work effort needed for conducting a more detailed study. The Planning and implementation of the eSDx product solution follows this study. The Analysis Phase is generally completed within a week and involves some basic interaction with a limited number of customer-staff people.
[Top]
Before proceeding with the Analysis Phase, we ask that the customer read and sign an agreement describing the objectives of the Analysis Phase and our dependencies on the customer-staff. This agreement also provides the cost of the Analysis Phase.
[Top]
The initial interviews involve a small number of key customer management and staff people.
These interviews seek to obtain information about the following items.
- Current software management methods
- Customer organization of computer users and geographic distribution
- Future software management objectives and goals
- High level computer and network topology
- Number of computers and applications
[Top]
The findings of the Analysis Phase are summarized in a brief document that describes our conclusions and recommendations.
An executive presentation is also prepared, highlighting this information.
[Top]
The Analysis Phase documentation is given to the customer.
The executive presentation is used as a means to review and discuss our findings and recommendations.
[Top]
Like the Analysis Phase, the Study Phase uses interviews as a means of gaining additional insight into the customer software/management requirements. In order to obtain the more detailed information that is needed for this phase, a larger number of people are interviewed.
This phase can take up to two weeks depending on the size and complexity of the customer enterprise.
[Top]
As with the Analysis Phase, we ask that the customer read and sign an agreement describing the objectives of the Study Phase and our dependencies on the customer-staff. This agreement also provides the cost of the Study Phase.
[Top]
The detailed interviews involve a larger number of key customer management and staff people. These interviews seek to obtain information about the following items.
- Desired improvements for current software management methods
- Key contacts for customer organization of computer users with locations and phone numbers
- Detailed computer and network topology
- Number of computers by organizational and geographic location
- Organizational and individual application requirements
- Current software licenses and tracking mechanisms
- Packaging and deployment considerations for customer applications to be placed under software management
- Adequacy and availability of equipment that could be used as eSDx Servers
[Top]
The findings of the Study Phase are summarized as part of the Statement of Work (SoW) document. This document provides details about the proposed software management solutions along with a schedule estimate for planning and implementation. An executive presentation is also prepared that highlights this information.
[Top]
The SoW document resulting from the Study Phase is given to the customer.
The executive presentation is used as a means of reviewing and discussing our findings and recommendations.
[Top]
During the Plan Phase, preparations are made for the final rollout of the eSDx software management solution and this culminates in a pilot rollout. This phase can take up to three weeks depending on the size and complexity of the customer enterprise.
[Top]
We ask that the customer read and sign the SoW before commencement of the Planning and Implementation Phases. This is to make sure that everyone has a clear understanding of the objectives of the project, and the roles and responsibilities of all participants.
[Top]
This plan contains all activities that will be needed in order to complete the project, along with dates and who is responsible for each activity. The project plan will be baselined and subsequently used during weekly checkpoint meetings to ensure that all activities are being met in a timely manor.
[Top]
The first wave of training will be provided to customer-staff who are involved in central support operations and in the pilot project. This training will prepare these people to carry out their eSDx software management responsibilities.
[Top]
The customer may elect to have eSDx Management provide the equipment needed for the eSDx servers. After being ordered and received, this equipment is then prepared and tested by loading the necessary software on it. Of course the customer may choose instead to use their own existing equipment for eSDx servers. This equipment will be prepared and tested in the same manner.
[Top]
The database is created on the Master eSDx Server, it is then prepared for use by loading the following kinds of information into it.
- Expected inventory of computers and the users and/or organizations related to them
- Licensed software vendor, title, version, and count information
- Customer policies regarding how and when software and updates are distributed, which users and/or organizations are associated with which computers, who individually or organizationally is entitled to which software, the actions that should take place when unauthorized software is found on a computer, etc.
- Administrative delegation information
[Top]
The customer applications that will come into play during the pilot rollout are packaged. This will also be used as a learning opportunity for customer developers who will be responsible for packaging other customer applications and updates.
[Top]
eSDx software management is implemented using a small, controlled group of computers, users, and applications to verify that everything is in place to support the complete rollout during the Implementation Phase. Additionally, this will be used as a learning opportunity for customer-staff who will be responsible for future implementation activities.
The results of the Pilot Rollout are reviewed with customer management as a means of demonstrating readiness for full implementation.
[Top]
The final phase will see the full rollout of the eSDx software management upon all server and client computers. These are the computers that were selected by the customer to be placed under software management.
This phase can take up to four weeks depending on the size and complexity of the customer enterprise.
[Top]
[Top]
[Top]
[Top]
[Top]
[Top]
[Top]
|
