D662 – Implement Live Client Systems – Hardware & Software
Establish the user’s’ “client” environment as required for the new application in accordance with the Technical Plan.
The purpose of this activity is to acquire, install, configure, and test those “client” hardware and software elements that have not already been implemented during the system build and testing activities.
PATH PLANNING GUIDANCE
This process is optional. It is used where new or modified client systems are required. Also, the required work may have already been conducted as part of Process D130 – install hardware, software, and communications equipment.
Dependent procedures (Finish-Start):
Conduct final operations review (D895)
Conduct final user review (D897)
Decision to go live (D900)
DETAILED DESCRIPTION OF TASKS
The project manager should ensure that client systems are installed in a timely manner in relation to dependent project activities. The full configuration may be required prior to live running where it is used in user testing, training, data loading or volume testing. The vendor will normally provide detail of considerations concerning its implementation.
Work of this nature normally requires the close co-operation of the client organisation’s IT department. In many cases the work will be conducted entirely by them.
Technical Plan (D110)
details of user population and location
installation standards and procedures
hardware and software inventories
vendor contracts and technical documentation
capacity and performance analysis reports
Needs for equipment
Details of requirements for client hardware and software should be finalised. In particular, it will be necessary to agree the needs and proposed allocations with departmental managers, along with the placement of equipment. This will be largely based on the predicted user population and predicted usage.
Consider and agree any options. For example, minimum specification equipment may adequately meet the new system’s needs, but not represent the best value for money for the organisation which might benefit from better specification machines and software which could then be used for other purposes in addition to the new system.
Establish and agree which budgets the costs should be charged to. In some cases the client organisation will expect costs of local equipment to be accepted by the local office or user departments rather than being centrally funded or funded out of the project budget.
Planning and documenting the equipment and its configuration
Placement and allocation of client facilities should be documented. Many client organisations will require the individual identification of machines for asset registers or for inventory control. Styles and standards for the documentation will normally be defined by the client organisation’s existing approach.
Testing and Implementing
Once installed, the communications software and equipment should be tested and any required local training or guidance should be provided.
Testing is not normally required on a formal basis – it is usually sufficient to demonstrate that the systems work.
In some cases it may be necessary to train local staff in the use of the equipment. Where this is a significant effort or has a critical impact on the overall business solution, it should normally have been included in the user training programme (see Process D760).
The main functional use of the system will normally be dealt with in the mainstream user training programme. Some minor procedures may need to be defined and publicised to deal with specific local details, eg:
operation of the equipment,
connecting to the server,
access by new users,
updates to the client software,
adding, changing, removing or moving client equipment,
how to deal with problems.