Blog Posts Process Analysis

Project Delivery Process D662

Blog: Biz-Performance, David Brown

D662 – Implement Live Client Systems – Hardware & Software

SIIPS Delivery Processes (D).png

DEFINITION

SIIPS D662.pngEstablish the user’s’ “client” environment as required for the new application in accordance with the Technical Plan.

SUMMARY

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.

DEPENDENCIES

Prerequisites (Finish-Start):
  • Review technical environment and plan installation (D110)
Dependent procedures(Finish-Finish):
  • Technical testing and tuning (D810)
Dependent procedures (Finish-Start):
  • Conduct final operations review (D895)
  • Conduct final user review (D897)
  • Decision to go live (D900)

RECEIVABLES

  • Technical Plan (D110)

DELIVERABLES

  • hardware and software orders and licences
  • installed client systems
  • corresponding documentation

TOOLS

  • (none)

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.

Information sources

  • 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
  • operations management

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.

Leave a Comment

Get the BPI Web Feed

Using the HTML code below, you can display this Business Process Incubator page content with the current filter and sorting inside your web site for FREE.

Copy/Paste this code in your website html code:

<iframe src="https://www.businessprocessincubator.com/content/project-delivery-process-d662/?feed=html" frameborder="0" scrolling="auto" width="100%" height="700">

Customizing your BPI Web Feed

You can click on the Get the BPI Web Feed link on any of our page to create the best possible feed for your site. Here are a few tips to customize your BPI Web Feed.

Customizing the Content Filter
On any page, you can add filter criteria using the MORE FILTERS interface:

Customizing the Content Filter

Customizing the Content Sorting
Clicking on the sorting options will also change the way your BPI Web Feed will be ordered on your site:

Get the BPI Web Feed

Some integration examples

BPMN.org

XPDL.org

×