1. Implementation Plans and Teams IACT424/924 Corporate Network Design and Implementation

2. Overview Where does network design fit within the organization Planning the implementation: accommodating uniqueness Key components of implementation plans Test plans Implementation management teams Scale of Implementation

3. Definitions Implement Merriam Webster Carry out, accomplish; Especially : to give practical effect to and ensure of actual fulfilment by concrete measures OED To complete, perform, carry into effect (a contract, agreement, etc.); to fulfil (an engagement or promise).

4. Where Does Network Design Fit Within the Organization? Business PlanningNetwork DesignImplement NetworkOperations Define Objectives and Requirements Create Initial Solution Define Deployment Strategy Review and Approve Develop Architecture Develop Detailed Design Create Build Documentation Review and Verify Design Create Implementation Plan Procure Resources and Facilities Stage and Install Certify and Hand-off To Operations Develop Operations Policies and Capabilities Fault Management Configuration Management Change Management Performance Management

5. Where Does Network Design Fit Within the Organization? Business PlanningNetwork DesignImplement NetworkOperations Define Objectives and Requirements Create Initial Solution Define Deployment Strategy Review and Approve Develop Architecture Develop Detailed Design Create Build Documentation Review and Verify Design Create Implementation Plan Procure Resources and Facilities Stage and Install Certify and Hand-off To Operations Develop Operations Policies and Capabilities Fault Management Configuration Management Change Management Performance Management

6. Planning the Implementation: Accommodating Uniqueness Implementations are not all the same If you conform to to the same implementation routine you risk getting trapped

7. Implementation Plan The implementation plan is the single greatest point of failure of many technology strategies A successful plan should incorporate various components and should be highly detailed, controlled and monitored

8. Key Components of Implementation Plans Definition of needs and deployment of resources The redesign of existing business processes and the technical infrastructure to meet the efficiencies that can be achieved with the new technology Installation and customisation of the software and/or hardware

9. Key Components of Implementation Plans Conducting comprehensive training on the redesigned processes as well as the application or hardware Testing the process and technology in a controlled environment And rolling out the new processes and technology

10. Implementation Plan Documents The most current state of the work to be done is represented by the Implementation Plan The Documents found in prototypical implementation plans include: Deliverables Document Work Statements Sign-Off Sheets Schedule Problem Log Test Plan Implementation Management Teams Problem Reports Change Log Change Request Configuration Management Implementation Resource Requirements

11. Implementation Plan Documents Deliverables document Outlines what decisions have been made and what deliverables have been promised Work statements Written by each person or group involved in the implementation and define in detail what deliverables they are responsible for

12. Implementation Plan Documents Sign-off sheets In effect these are contracts that formalise acceptance of deliverables by the person responsible for accepting them Schedule Shows times and date that each deliverable must be accomplished by

13. Implementation Plan Documents Test plan An English narrative describing concisely what has to be done Testing seeks to find errors of commission and omission made during the design, development and implementation phases What do you test? Everything in the implementation plan Terminology should be defined and clarified between team members

14. Test Plans Type of TestingDefinitionSynonyms Unit TestingEach individual unitModular System TestingEvery NE that utilises a particular system Application Integration TestingAn entire stream of systems User Acceptance TestingAn entire stream of systemsUAP Regression TestingPre-existing functionality not impacted by the implementation Stress TestingDoing ‘bad’ things to the system Volume TestingFull production volumes of dataCapacity Restart TestSystem can be restarted as required rerun

15. Implementation Management Teams Implementation management teams Administer the logistical problems of implementing the system The Implementation Plan should document Teams duties Who is on the team Roles and responsibilities

16. Implementation Management Teams Types of implementation Management Teams Installation Management Team Problem Report Team Problem Management Team Change Management Team

17. Implementation Management Teams Installation Management Team Deals with problems that occur as system or product is being installed Responsibility is “mission critical” Members should not be ‘out-of-town’ during system installation These are the people you call at 2am when the installation has problems Membership Senior Manager responsible for an area of IS Mid-level managers responsible for particular systems

18. Implementation Management Teams Problem Report Team Reviews problem reports as they occur Identifies, prioritises, assigns problem solutions Allows problems to be addressed efficiently Concerned with problems that impact across systems or application groups

19. Implementation Management Teams Problem Management Team This team is called in when problems have not been resolved within a few days Typically there are different problem management teams to address different areas of the implementation Membership of the Problem Management Teams should be documented in the implementation plan

20. Implementation Management Teams Change Management Team Reviews all items necessitating changes to the plan and existing systems One of the most common issues is mismatched expectations Should ensure that there are no “un- documented” changes made and hence helps to ensure stability

21. Tools Problem log Problem reports Change log Change request Configuration management

22. Implementation Resource Requirements Implementation resource requirements Documents all resources required by the implementation Personnel Hardware Software etc

23. Implementation Plan Evaluate results The continuing evaluation of the results that are being achieved with the new processes and technology is paramount to a successful process The results should be monitored closely and adjustments made where needed, on a timely basis

24. Scale of Implementation Will/Do your employees use the Internet frequently? Do you anticipate a large volume of traffic between branches? Do plan to use videoconferencing? Who will use your connection to the Internet? Office Dial in from home Dial in from remote locations