SlideShare une entreprise Scribd logo
1  sur  9
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 1 of 9
OPERATIONS AND MAINTENANCE TRANSITION PLAN TEMPLATE
The Operations and Maintenance Transition Plan template is designed to facilitate migration of an application system
from a development environment to a production / maintenance environment. Although not required by IEEE
Standards, the Transition Plan format was developed as a “lessons-learned” item from multiple production application
systems.
Information displayed in blocked text under each section is suggested items for inclusion in the Transition Plan.
Information displayed in italics is informational. Delete the italics text items and add your project-specific input. These
items are food for thought on the section they address.
REVISION HISTORY
Revision # Revision Date Description of Change Author
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 2 of 9
Table of Contents
Operations and Maintenance Transition Plan Template .......................... 1
Revision History....................................................................................... 1
Overview......................................................................................................... 3
Scope.............................................................................................................. 3
Product...................................................................................................... 3
Documentation......................................................................................... 3
Relationships to Other Agencies / Projects.......................................... 4
Strategies....................................................................................................... 4
Identify Strategies.................................................................................... 4
Select Strategy ........................................................................................ 4
Transition Schedules, Tasks and Activities................................................ 4
Installation ................................................................................................ 5
Operations and Support ......................................................................... 5
Conversion............................................................................................... 5
Maintenance............................................................................................. 5
Resource Requirements............................................................................... 5
Software Resources................................................................................ 5
Hardware Resources .............................................................................. 6
Facilities.................................................................................................... 6
Personnel ................................................................................................. 6
Acceptance Criteria (including Service Level Agreement (SLA))............ 7
Management Controls .................................................................................. 7
Reporting Procedures................................................................................... 7
Appendix A – Sample Work Breakdown Structure (WBS) ...................... 7
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 3 of 9
OVERVIEW
The purpose of transition planning is to layout the tasks and activities that need to take place to efficiently move a
product (i.e., specify product name, or in-house developed software or COTS software, middleware or component
software/hardware) from the development or pilot environment to the production, operations and maintenance
environment. The transition planning steps apply whether the product is being transitioned within an agency (i.e.
from agency development staff to agency network or operations staff) or to an outside agency (i.e., Information
Technology Systems).
The transition plan shall include an introduction or scope statement addressing background information on the
project. Show the relationship of the project to other projects and / or organizations or agencies, address
maintenance resources required, identify the transition team’s organization and responsibilities, as well as the tools,
techniques, and methodologies that are needed to perform an efficient and effective transition.
The transition plan shall include deployment schedules, resource estimates, identification of special resources and
staffing. The transition plan shall also define management controls and reporting procedures, as well as the risks
and contingencies. Special attention must be given to minimizing operational risks. An impact statement
should be produced outlining the potential impact of the transition to the existing infrastructure, operations and
support staff and to the user community.
SCOPE
(A Scope Statement for the transition shall be a part of the Transition Plan information. Include a full identification of
the product to which this document applies:
- Product overview,
- Overview of the supporting documentation, and
- Description of the relationship of the product to other related projects and agencies.)
PRODUCT
(Include a brief statement of the purpose of the product to which this document applies. It shall describe the general
nature of the product; summarize the history of development, operation, and maintenance; identify the project
sponsor, acquirer, user, developer, vendor, and maintenance organizations; identify current and planned operating
sites; and list other relevant documents.)
Table purpose Row 1 Row 2
Column 1 Text Text
Column 2 Text Text
Column 3 Text Text
Column 4 Text Text
Column 5 Text Text
DOCUMENTATION
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 4 of 9
(Include a listing of all the documentation related to the product that is to be transitioned to the operations area
includes any security or privacy protection consideration associated with its use. Include as a part this any licensing
information for the product.)
Table purpose Row 1 Row 2
Column 1 Text Text
Column 2 Text Text
Column 3 Text Text
Column 4 Text Text
Column 5 Text Text
RELATIONSHIPS TO OTHER AGENCIES / PROJECTS
(Include a diagram, flow chart or description of the relationship(s) of the product being transitioned to any other
projects and agencies.)
STRATEGIES
IDENTIFY STRATEGIES
(Identify the transition strategies and tools to be used as part of the Transition Plan. Identify all the options for
moving the product from its present state into production/operations. These options could include:
- Incremental implementation or phased approach,
- Parallel execution,
- One-time conversion and switchover or
- Any combinations of the above.
Each option shall also identify the advantages and disadvantages, risks, estimated time frames, and estimated
resources.)
SELECT STRATEGY
(Evaluate each of the transition options, comparing them to the transition requirements, and selecting the one that is
most appropriate for the project. Once a transition strategy has been selected, then the justification is documented
and approved.)
TRANSITION SCHEDULES, TASKS AND ACTIVITIES
(Develop detail schedules for the selected transition strategy. The time schedule shall include equipment installation,
training, conversion, deployment, and or retirement of the existing system (if applicable) as well as any transition
activities required to turn over the product from developers or vendors to operational staff. Include schedules and
milestones for conducting the transition activities.
Include in this section an installation schedule for equipment (new or existing), software, databases, etc. Include
provisions for training personnel with the operational software and target computer(s), as well as any maintenance
software and / or host system(s).
Describe the developer’s plans for transitioning the deliverable product to the maintenance organization. This should
address the following:
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 5 of 9
 Planning/coordination of meetings,
 Preparation of items to be delivered to the maintenance organization,
 Packaging, shipment, installation, and checkout of the product maintenance environment,
 Packaging, shipment, installation, and checkout of the operational software, and
 Training of maintenance / operational personnel.)
INSTALLATION
(Installation consists of the transportation and installation of the product from the development environment to the
target environment(s). It includes any modifications to the product, checkout in the target environment(s), and
customer acceptance. If problems arise, these should be identified and reported. If necessary, temporary “work-
around(s)” should be defined.)
OPERATIONS AND SUPPORT
(Operations and support activity group involves users operation of the product and ongoing support. Support
includes providing technical assistance, consulting with the user, and recording user support requests by
maintaining a Support Request Log. The Operations and Support activities can trigger maintenance activities via
the ongoing project monitoring and controlling activities or problem and change logs.)
CONVERSION
(Conversion addresses any data or database transfers to the product and its underlying components.)
Table purpose Row 1 Row 2
Column 1 Text Text
Column 2 Text Text
Column 3 Text Text
Column 4 Text Text
Column 5 Text Text
MAINTENANCE
(Maintenance activities are concerned with the identification of enhancements and the resolution of product errors,
faults and failures. The requirements for software maintenance initiate “service level changes” or “product
modification requests” by using defined problem and change management reporting procedures.)
RESOURCE REQUIREMENTS
(Include estimates for resources (hardware, software, and facility) as well as any special resources (i.e. service and
maintenance contracts), and staffing for the selected transition strategy.
Assign staff, agency, and vendor responsibility for each task identified. This allows managers and project team
members to plan and coordinate the work of this project with other assignments. If specific individuals cannot be
identified when the transition plan is developed, generic names may be used and replaced with individual names as
soon as the resources are identified.)
SOFTWARE RESOURCES
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 6 of 9
(Describe any software and associated documentation needed to maintain the deliverable product. The description
should include specific names, identification numbers, version numbers, release numbers and configurations as
applicable. References to user/operator manuals or instructions for each item should be included. Identify for each
product item where it is to come from --acquirer-furnished, currently owned by the organization, or to be purchased.
Include information about vendor support, licensing, and usage and ownership rights, whether the item is currently
supported by the vendor, whether it is expected to be supported at the time of delivery, whether licenses will be
assigned to the maintenance organization, and the terms of such licenses. Include any required service and
maintenance contract costs as well as payment responsibility.)
Table purpose Row 1 Row 2
Column 1 Text Text
Column 2 Text Text
Column 3 Text Text
Column 4 Text Text
Column 5 Text Text
HARDWARE RESOURCES
(Describe the hardware and associated documentation needed to maintain the deliverable product. This hardware
may include computers, peripheral equipment, simulators, emulators, diagnostic equipment, and non-computer
equipment. The description shall include specific models, versions, and configurations. References to user/operator
manuals or instructions for each item should be included. Identification each hardware item and document as
acquirer-furnished, an items that will be delivered to the maintenance organization, an item the maintenance
organization currently owns or needs to acquire. (If the item is to be acquired, include information about a current
source of supply, and order information as well as what budget is to pay for it.) Include information about
manufacturer support, licensing, and usage and ownership rights, whether the items are currently supported by the
manufacturer, or will be in the future, and whether licenses will be assigned to the maintenance organization and the
terms of such licenses.)
Table purpose Row 1 Row 2
Column 1 Text Text
Column 2 Text Text
Column 3 Text Text
Column 4 Text Text
Column 5 Text Text
FACILITIES
(Describe any facilities needed to maintain the deliverable product. These facilities may include special buildings,
rooms, mock-ups, building features such as raised flooring or cabling, building features to support security and
privacy protection requirements, building features to support safety requirements, special power requirements, and
so on. Include any diagrams that may be applicable.)
PERSONNEL
(Describe the personnel needed to maintain the deliverable product, include anticipated number of personnel, types
of support personnel (job descriptions), skill levels and expertise requirements, and security clearance.)
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 7 of 9
Table purpose Row 1 Row 2
Column 1 Text Text
Column 2 Text Text
Column 3 Text Text
Column 4 Text Text
Column 5 Text Text
ACCEPTANCE CRITERIA (INCLUDING SERVICE LEVEL AGREEMENT (SLA))
(Establish the exit or acceptance criteria for transiting the product. Criteria that will determine the acceptability of the
deliverable work products shall be specified. Representatives of the transitioning organization and the acquiring
organization shall sign a formal agreement, such as a Service Level Agreement, that outlines the acceptance criteria.
Any technical processes methods, or tools as well as performance benchmarks required for product acceptance,
shall be specified in the agreement. Also include an estimation of the operational budget for the product and how
these expenses will be covered.)
MANAGEMENT CONTROLS
(Define management controls to ensure that each task is successfully executed and completed based on the
approved acceptance criteria.
This shall include procedures for progress control, quality control, change control, version control, and issue
management during the transition process.)
REPORTING PROCEDURES
(Define the reporting procedures for the transition period. Include such things as type of evaluations (review, audit,
or test) as well as anomalies that are identified during the performance of these evaluations shall be reported.)
APPENDIX A – SAMPLE WORK BREAKDOWN STRUCTURE (WBS)
Product Installation
Distribute Product (software)
Package and distribute product
Distribute installation information
Conduct integration test for product
Conduct regression test for product
Conduct user acceptance test for software
Conduct reviews for product
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 8 of 9
Perform configuration control for product
Implement documentation for product
Install Product (software)
Install product (packaged software) and database data
Install any related hardware for the product
Document installation problems
Accept Product (software) in Operations Environment
Compare installed product (software) to acceptance criteria
Conduct reviews for installed product (software)
Perform configuration control for installed product (software)
Operations and Support
Operate the System
Utilize installed software system
Monitor performance
Identify anomalies
Produce operations log
Conduct reviews for operations logs
Perform configuration control for operations logs
Provide Technical Assistance and Consulting
Provide response to technical questions or problems
Log problems
Maintain Support Request Logs
Record support requests
Record anomalies
Conduct reviews for support request logs
OPERATIONS AND MAINTENANCE
TransitionPlan NUMBER: 443-04-nnn
EFFECTIVE DATE: mm-dd-2015
Page 9 of 9
Maintenance
Identify Product (software) Improvements Needs
Identify product improvements
Develop corrective/perfective strategies
Produce product (software) improvement recommendations
Implement Problem Reporting Method
Analyze reported problems
Produce report log
Produce enhancement problem reported information
Produce corrective problem reported information
Perform configuration control for reported information
Reapply Software Life Cycle methodology

Contenu connexe

Tendances

It Service Management Implementation Overview
It Service Management Implementation OverviewIt Service Management Implementation Overview
It Service Management Implementation Overview
Alan McSweeney
 
Risk Management
Risk ManagementRisk Management
Risk Management
vivekaathuri
 
IT PMO Charter (Linkedin)
IT PMO Charter (Linkedin)IT PMO Charter (Linkedin)
IT PMO Charter (Linkedin)
jimmcdonaldpmp
 
GEA-NZ v3.1 Business Reference Model and Taxonomy
GEA-NZ v3.1 Business Reference Model and TaxonomyGEA-NZ v3.1 Business Reference Model and Taxonomy
GEA-NZ v3.1 Business Reference Model and Taxonomy
Regine Deleu
 

Tendances (20)

IT Strategy
IT StrategyIT Strategy
IT Strategy
 
Approaches to business architecture
Approaches to business architectureApproaches to business architecture
Approaches to business architecture
 
PRINCE2 - Presentation
PRINCE2 - PresentationPRINCE2 - Presentation
PRINCE2 - Presentation
 
Digital Operating Model & IT4IT
Digital Operating Model & IT4ITDigital Operating Model & IT4IT
Digital Operating Model & IT4IT
 
Example business continuity plan
Example business continuity planExample business continuity plan
Example business continuity plan
 
Define an IT Strategy and Roadmap
Define an IT Strategy and RoadmapDefine an IT Strategy and Roadmap
Define an IT Strategy and Roadmap
 
It Service Management Implementation Overview
It Service Management Implementation OverviewIt Service Management Implementation Overview
It Service Management Implementation Overview
 
EA foundations (Views, Repository, Artifacts and Metamodel)
EA foundations (Views, Repository, Artifacts and Metamodel)EA foundations (Views, Repository, Artifacts and Metamodel)
EA foundations (Views, Repository, Artifacts and Metamodel)
 
ITGC audit of ERPs
ITGC audit of ERPsITGC audit of ERPs
ITGC audit of ERPs
 
7 Themes of Prince2
7 Themes of Prince27 Themes of Prince2
7 Themes of Prince2
 
Risk Management
Risk ManagementRisk Management
Risk Management
 
How To Use a Structured Project Intake Process to Improve your Project Portfolio
How To Use a Structured Project Intake Process to Improve your Project PortfolioHow To Use a Structured Project Intake Process to Improve your Project Portfolio
How To Use a Structured Project Intake Process to Improve your Project Portfolio
 
Applying PDCA, A3 Thinking & Problem Solving
Applying PDCA, A3 Thinking & Problem SolvingApplying PDCA, A3 Thinking & Problem Solving
Applying PDCA, A3 Thinking & Problem Solving
 
IT Governance – The missing compass in a technology changing world
 IT Governance – The missing compass in a technology changing world IT Governance – The missing compass in a technology changing world
IT Governance – The missing compass in a technology changing world
 
Itil process framework__rowe(40)
Itil process framework__rowe(40)Itil process framework__rowe(40)
Itil process framework__rowe(40)
 
Continuous Delivery of Agile Architecture
Continuous Delivery of Agile ArchitectureContinuous Delivery of Agile Architecture
Continuous Delivery of Agile Architecture
 
Balanced Scorecard IT Strategy and Project Management
Balanced Scorecard IT Strategy and Project ManagementBalanced Scorecard IT Strategy and Project Management
Balanced Scorecard IT Strategy and Project Management
 
IT PMO Charter (Linkedin)
IT PMO Charter (Linkedin)IT PMO Charter (Linkedin)
IT PMO Charter (Linkedin)
 
GEA-NZ v3.1 Business Reference Model and Taxonomy
GEA-NZ v3.1 Business Reference Model and TaxonomyGEA-NZ v3.1 Business Reference Model and Taxonomy
GEA-NZ v3.1 Business Reference Model and Taxonomy
 
Governance Culture & Incentives- Fundamentals of Operational Risk
Governance Culture & Incentives- Fundamentals of Operational RiskGovernance Culture & Incentives- Fundamentals of Operational Risk
Governance Culture & Incentives- Fundamentals of Operational Risk
 

Similaire à Transition to operations template Julie Bozzi Oregon

eCIO PPT Sunsetting strategy v 3 general distribution
eCIO PPT Sunsetting strategy v 3 general distributioneCIO PPT Sunsetting strategy v 3 general distribution
eCIO PPT Sunsetting strategy v 3 general distribution
David Niles
 
Software Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docxSoftware Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docx
rosemariebrayshaw
 
T Jull - Product Development for Point-of-Care Testing Systems
T Jull - Product Development for Point-of-Care Testing SystemsT Jull - Product Development for Point-of-Care Testing Systems
T Jull - Product Development for Point-of-Care Testing Systems
Thomas Jull
 
DMAIC addressed Bearnson S-N tracking for all product.
DMAIC addressed Bearnson S-N tracking for all product.DMAIC addressed Bearnson S-N tracking for all product.
DMAIC addressed Bearnson S-N tracking for all product.
Bill Bearnson
 
TaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docx
TaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docxTaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docx
TaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docx
SANSKAR20
 
MagdaEContosResume
MagdaEContosResumeMagdaEContosResume
MagdaEContosResume
Magda Contos
 
Templateplanodedisponibilidadedosservios 120602150709-phpapp02
Templateplanodedisponibilidadedosservios 120602150709-phpapp02Templateplanodedisponibilidadedosservios 120602150709-phpapp02
Templateplanodedisponibilidadedosservios 120602150709-phpapp02
Ismael Rodrigues
 

Similaire à Transition to operations template Julie Bozzi Oregon (20)

Concept Service Transition_v1 0.docx
Concept Service Transition_v1 0.docxConcept Service Transition_v1 0.docx
Concept Service Transition_v1 0.docx
 
eCIO PPT Sunsetting strategy v 3 general distribution
eCIO PPT Sunsetting strategy v 3 general distributioneCIO PPT Sunsetting strategy v 3 general distribution
eCIO PPT Sunsetting strategy v 3 general distribution
 
0.3 aim phases_and_documentations
0.3 aim phases_and_documentations0.3 aim phases_and_documentations
0.3 aim phases_and_documentations
 
Software Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docxSoftware Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docx
 
Spm unit 3
Spm unit 3Spm unit 3
Spm unit 3
 
An Enterprise Architecture Design Build Approach - Innovate Vancouver.pdf
An Enterprise Architecture Design  Build Approach - Innovate Vancouver.pdfAn Enterprise Architecture Design  Build Approach - Innovate Vancouver.pdf
An Enterprise Architecture Design Build Approach - Innovate Vancouver.pdf
 
An Approach of Improve Efficiencies through DevOps Adoption
An Approach of Improve Efficiencies through DevOps AdoptionAn Approach of Improve Efficiencies through DevOps Adoption
An Approach of Improve Efficiencies through DevOps Adoption
 
Migration Decoded
Migration DecodedMigration Decoded
Migration Decoded
 
Developing supplemental performance requirements
Developing supplemental performance requirementsDeveloping supplemental performance requirements
Developing supplemental performance requirements
 
T Jull - Product Development for Point-of-Care Testing Systems
T Jull - Product Development for Point-of-Care Testing SystemsT Jull - Product Development for Point-of-Care Testing Systems
T Jull - Product Development for Point-of-Care Testing Systems
 
DMAIC addressed Bearnson S-N tracking for all product.
DMAIC addressed Bearnson S-N tracking for all product.DMAIC addressed Bearnson S-N tracking for all product.
DMAIC addressed Bearnson S-N tracking for all product.
 
2010-36-0387I_Paper
2010-36-0387I_Paper2010-36-0387I_Paper
2010-36-0387I_Paper
 
TaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docx
TaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docxTaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docx
TaskFounded in 1990, Century Pharmaceuticals Ltd is a regional A.docx
 
Maintainability engineering
Maintainability engineeringMaintainability engineering
Maintainability engineering
 
MagdaEContosResume
MagdaEContosResumeMagdaEContosResume
MagdaEContosResume
 
SDLC
SDLCSDLC
SDLC
 
06 template test plan
06 template test plan06 template test plan
06 template test plan
 
Templateplanodedisponibilidadedosservios 120602150709-phpapp02
Templateplanodedisponibilidadedosservios 120602150709-phpapp02Templateplanodedisponibilidadedosservios 120602150709-phpapp02
Templateplanodedisponibilidadedosservios 120602150709-phpapp02
 
IT infra, emerging technology and governance
IT infra, emerging technology and governance IT infra, emerging technology and governance
IT infra, emerging technology and governance
 
softwareMaintenance.pdf
softwareMaintenance.pdfsoftwareMaintenance.pdf
softwareMaintenance.pdf
 

Plus de Julie Bozzi, PfPM, PMP (9)

Julie Bozzi Oregon MAGI Medicaid System Objectives
Julie Bozzi Oregon MAGI Medicaid System ObjectivesJulie Bozzi Oregon MAGI Medicaid System Objectives
Julie Bozzi Oregon MAGI Medicaid System Objectives
 
Julie Bozzi Oregon MAGI Project Overview 112015
Julie Bozzi Oregon MAGI Project Overview 112015Julie Bozzi Oregon MAGI Project Overview 112015
Julie Bozzi Oregon MAGI Project Overview 112015
 
Process documentation template julie bozzi Oregon
Process documentation template  julie bozzi OregonProcess documentation template  julie bozzi Oregon
Process documentation template julie bozzi Oregon
 
Backup policy template julie bozzi oregon
Backup policy template   julie bozzi oregonBackup policy template   julie bozzi oregon
Backup policy template julie bozzi oregon
 
PMO-NOPOLY Julie Bozzi Oregon
PMO-NOPOLY Julie Bozzi OregonPMO-NOPOLY Julie Bozzi Oregon
PMO-NOPOLY Julie Bozzi Oregon
 
Oregon blue book DAS Leadership 2015 - Julie Bozzi Oregon
Oregon blue book DAS Leadership 2015 - Julie Bozzi OregonOregon blue book DAS Leadership 2015 - Julie Bozzi Oregon
Oregon blue book DAS Leadership 2015 - Julie Bozzi Oregon
 
ETS Service Levels 2013-15 Julie Bozzi Oregon
ETS Service Levels 2013-15 Julie Bozzi OregonETS Service Levels 2013-15 Julie Bozzi Oregon
ETS Service Levels 2013-15 Julie Bozzi Oregon
 
ETS Strategic Plan 2012-2016 Julie Bozzi Oregon
ETS Strategic Plan 2012-2016 Julie Bozzi OregonETS Strategic Plan 2012-2016 Julie Bozzi Oregon
ETS Strategic Plan 2012-2016 Julie Bozzi Oregon
 
2011 Strategic Plan and Annual Report - Final _ Julie Bozzi Oregon
2011 Strategic Plan and Annual Report - Final _ Julie Bozzi Oregon2011 Strategic Plan and Annual Report - Final _ Julie Bozzi Oregon
2011 Strategic Plan and Annual Report - Final _ Julie Bozzi Oregon
 

Dernier

Histor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slideHistor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slide
vu2urc
 

Dernier (20)

A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
 
🐬 The future of MySQL is Postgres 🐘
🐬  The future of MySQL is Postgres   🐘🐬  The future of MySQL is Postgres   🐘
🐬 The future of MySQL is Postgres 🐘
 
[2024]Digital Global Overview Report 2024 Meltwater.pdf
[2024]Digital Global Overview Report 2024 Meltwater.pdf[2024]Digital Global Overview Report 2024 Meltwater.pdf
[2024]Digital Global Overview Report 2024 Meltwater.pdf
 
Advantages of Hiring UIUX Design Service Providers for Your Business
Advantages of Hiring UIUX Design Service Providers for Your BusinessAdvantages of Hiring UIUX Design Service Providers for Your Business
Advantages of Hiring UIUX Design Service Providers for Your Business
 
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
Understanding Discord NSFW Servers A Guide for Responsible Users.pdfUnderstanding Discord NSFW Servers A Guide for Responsible Users.pdf
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
 
Powerful Google developer tools for immediate impact! (2023-24 C)
Powerful Google developer tools for immediate impact! (2023-24 C)Powerful Google developer tools for immediate impact! (2023-24 C)
Powerful Google developer tools for immediate impact! (2023-24 C)
 
GenCyber Cyber Security Day Presentation
GenCyber Cyber Security Day PresentationGenCyber Cyber Security Day Presentation
GenCyber Cyber Security Day Presentation
 
Histor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slideHistor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slide
 
What Are The Drone Anti-jamming Systems Technology?
What Are The Drone Anti-jamming Systems Technology?What Are The Drone Anti-jamming Systems Technology?
What Are The Drone Anti-jamming Systems Technology?
 
Boost PC performance: How more available memory can improve productivity
Boost PC performance: How more available memory can improve productivityBoost PC performance: How more available memory can improve productivity
Boost PC performance: How more available memory can improve productivity
 
Developing An App To Navigate The Roads of Brazil
Developing An App To Navigate The Roads of BrazilDeveloping An App To Navigate The Roads of Brazil
Developing An App To Navigate The Roads of Brazil
 
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
 
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
 
Strategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherStrategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a Fresher
 
HTML Injection Attacks: Impact and Mitigation Strategies
HTML Injection Attacks: Impact and Mitigation StrategiesHTML Injection Attacks: Impact and Mitigation Strategies
HTML Injection Attacks: Impact and Mitigation Strategies
 
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, AdobeApidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
 
Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
 
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
 

Transition to operations template Julie Bozzi Oregon

  • 1. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 1 of 9 OPERATIONS AND MAINTENANCE TRANSITION PLAN TEMPLATE The Operations and Maintenance Transition Plan template is designed to facilitate migration of an application system from a development environment to a production / maintenance environment. Although not required by IEEE Standards, the Transition Plan format was developed as a “lessons-learned” item from multiple production application systems. Information displayed in blocked text under each section is suggested items for inclusion in the Transition Plan. Information displayed in italics is informational. Delete the italics text items and add your project-specific input. These items are food for thought on the section they address. REVISION HISTORY Revision # Revision Date Description of Change Author
  • 2. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 2 of 9 Table of Contents Operations and Maintenance Transition Plan Template .......................... 1 Revision History....................................................................................... 1 Overview......................................................................................................... 3 Scope.............................................................................................................. 3 Product...................................................................................................... 3 Documentation......................................................................................... 3 Relationships to Other Agencies / Projects.......................................... 4 Strategies....................................................................................................... 4 Identify Strategies.................................................................................... 4 Select Strategy ........................................................................................ 4 Transition Schedules, Tasks and Activities................................................ 4 Installation ................................................................................................ 5 Operations and Support ......................................................................... 5 Conversion............................................................................................... 5 Maintenance............................................................................................. 5 Resource Requirements............................................................................... 5 Software Resources................................................................................ 5 Hardware Resources .............................................................................. 6 Facilities.................................................................................................... 6 Personnel ................................................................................................. 6 Acceptance Criteria (including Service Level Agreement (SLA))............ 7 Management Controls .................................................................................. 7 Reporting Procedures................................................................................... 7 Appendix A – Sample Work Breakdown Structure (WBS) ...................... 7
  • 3. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 3 of 9 OVERVIEW The purpose of transition planning is to layout the tasks and activities that need to take place to efficiently move a product (i.e., specify product name, or in-house developed software or COTS software, middleware or component software/hardware) from the development or pilot environment to the production, operations and maintenance environment. The transition planning steps apply whether the product is being transitioned within an agency (i.e. from agency development staff to agency network or operations staff) or to an outside agency (i.e., Information Technology Systems). The transition plan shall include an introduction or scope statement addressing background information on the project. Show the relationship of the project to other projects and / or organizations or agencies, address maintenance resources required, identify the transition team’s organization and responsibilities, as well as the tools, techniques, and methodologies that are needed to perform an efficient and effective transition. The transition plan shall include deployment schedules, resource estimates, identification of special resources and staffing. The transition plan shall also define management controls and reporting procedures, as well as the risks and contingencies. Special attention must be given to minimizing operational risks. An impact statement should be produced outlining the potential impact of the transition to the existing infrastructure, operations and support staff and to the user community. SCOPE (A Scope Statement for the transition shall be a part of the Transition Plan information. Include a full identification of the product to which this document applies: - Product overview, - Overview of the supporting documentation, and - Description of the relationship of the product to other related projects and agencies.) PRODUCT (Include a brief statement of the purpose of the product to which this document applies. It shall describe the general nature of the product; summarize the history of development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, vendor, and maintenance organizations; identify current and planned operating sites; and list other relevant documents.) Table purpose Row 1 Row 2 Column 1 Text Text Column 2 Text Text Column 3 Text Text Column 4 Text Text Column 5 Text Text DOCUMENTATION
  • 4. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 4 of 9 (Include a listing of all the documentation related to the product that is to be transitioned to the operations area includes any security or privacy protection consideration associated with its use. Include as a part this any licensing information for the product.) Table purpose Row 1 Row 2 Column 1 Text Text Column 2 Text Text Column 3 Text Text Column 4 Text Text Column 5 Text Text RELATIONSHIPS TO OTHER AGENCIES / PROJECTS (Include a diagram, flow chart or description of the relationship(s) of the product being transitioned to any other projects and agencies.) STRATEGIES IDENTIFY STRATEGIES (Identify the transition strategies and tools to be used as part of the Transition Plan. Identify all the options for moving the product from its present state into production/operations. These options could include: - Incremental implementation or phased approach, - Parallel execution, - One-time conversion and switchover or - Any combinations of the above. Each option shall also identify the advantages and disadvantages, risks, estimated time frames, and estimated resources.) SELECT STRATEGY (Evaluate each of the transition options, comparing them to the transition requirements, and selecting the one that is most appropriate for the project. Once a transition strategy has been selected, then the justification is documented and approved.) TRANSITION SCHEDULES, TASKS AND ACTIVITIES (Develop detail schedules for the selected transition strategy. The time schedule shall include equipment installation, training, conversion, deployment, and or retirement of the existing system (if applicable) as well as any transition activities required to turn over the product from developers or vendors to operational staff. Include schedules and milestones for conducting the transition activities. Include in this section an installation schedule for equipment (new or existing), software, databases, etc. Include provisions for training personnel with the operational software and target computer(s), as well as any maintenance software and / or host system(s). Describe the developer’s plans for transitioning the deliverable product to the maintenance organization. This should address the following:
  • 5. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 5 of 9  Planning/coordination of meetings,  Preparation of items to be delivered to the maintenance organization,  Packaging, shipment, installation, and checkout of the product maintenance environment,  Packaging, shipment, installation, and checkout of the operational software, and  Training of maintenance / operational personnel.) INSTALLATION (Installation consists of the transportation and installation of the product from the development environment to the target environment(s). It includes any modifications to the product, checkout in the target environment(s), and customer acceptance. If problems arise, these should be identified and reported. If necessary, temporary “work- around(s)” should be defined.) OPERATIONS AND SUPPORT (Operations and support activity group involves users operation of the product and ongoing support. Support includes providing technical assistance, consulting with the user, and recording user support requests by maintaining a Support Request Log. The Operations and Support activities can trigger maintenance activities via the ongoing project monitoring and controlling activities or problem and change logs.) CONVERSION (Conversion addresses any data or database transfers to the product and its underlying components.) Table purpose Row 1 Row 2 Column 1 Text Text Column 2 Text Text Column 3 Text Text Column 4 Text Text Column 5 Text Text MAINTENANCE (Maintenance activities are concerned with the identification of enhancements and the resolution of product errors, faults and failures. The requirements for software maintenance initiate “service level changes” or “product modification requests” by using defined problem and change management reporting procedures.) RESOURCE REQUIREMENTS (Include estimates for resources (hardware, software, and facility) as well as any special resources (i.e. service and maintenance contracts), and staffing for the selected transition strategy. Assign staff, agency, and vendor responsibility for each task identified. This allows managers and project team members to plan and coordinate the work of this project with other assignments. If specific individuals cannot be identified when the transition plan is developed, generic names may be used and replaced with individual names as soon as the resources are identified.) SOFTWARE RESOURCES
  • 6. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 6 of 9 (Describe any software and associated documentation needed to maintain the deliverable product. The description should include specific names, identification numbers, version numbers, release numbers and configurations as applicable. References to user/operator manuals or instructions for each item should be included. Identify for each product item where it is to come from --acquirer-furnished, currently owned by the organization, or to be purchased. Include information about vendor support, licensing, and usage and ownership rights, whether the item is currently supported by the vendor, whether it is expected to be supported at the time of delivery, whether licenses will be assigned to the maintenance organization, and the terms of such licenses. Include any required service and maintenance contract costs as well as payment responsibility.) Table purpose Row 1 Row 2 Column 1 Text Text Column 2 Text Text Column 3 Text Text Column 4 Text Text Column 5 Text Text HARDWARE RESOURCES (Describe the hardware and associated documentation needed to maintain the deliverable product. This hardware may include computers, peripheral equipment, simulators, emulators, diagnostic equipment, and non-computer equipment. The description shall include specific models, versions, and configurations. References to user/operator manuals or instructions for each item should be included. Identification each hardware item and document as acquirer-furnished, an items that will be delivered to the maintenance organization, an item the maintenance organization currently owns or needs to acquire. (If the item is to be acquired, include information about a current source of supply, and order information as well as what budget is to pay for it.) Include information about manufacturer support, licensing, and usage and ownership rights, whether the items are currently supported by the manufacturer, or will be in the future, and whether licenses will be assigned to the maintenance organization and the terms of such licenses.) Table purpose Row 1 Row 2 Column 1 Text Text Column 2 Text Text Column 3 Text Text Column 4 Text Text Column 5 Text Text FACILITIES (Describe any facilities needed to maintain the deliverable product. These facilities may include special buildings, rooms, mock-ups, building features such as raised flooring or cabling, building features to support security and privacy protection requirements, building features to support safety requirements, special power requirements, and so on. Include any diagrams that may be applicable.) PERSONNEL (Describe the personnel needed to maintain the deliverable product, include anticipated number of personnel, types of support personnel (job descriptions), skill levels and expertise requirements, and security clearance.)
  • 7. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 7 of 9 Table purpose Row 1 Row 2 Column 1 Text Text Column 2 Text Text Column 3 Text Text Column 4 Text Text Column 5 Text Text ACCEPTANCE CRITERIA (INCLUDING SERVICE LEVEL AGREEMENT (SLA)) (Establish the exit or acceptance criteria for transiting the product. Criteria that will determine the acceptability of the deliverable work products shall be specified. Representatives of the transitioning organization and the acquiring organization shall sign a formal agreement, such as a Service Level Agreement, that outlines the acceptance criteria. Any technical processes methods, or tools as well as performance benchmarks required for product acceptance, shall be specified in the agreement. Also include an estimation of the operational budget for the product and how these expenses will be covered.) MANAGEMENT CONTROLS (Define management controls to ensure that each task is successfully executed and completed based on the approved acceptance criteria. This shall include procedures for progress control, quality control, change control, version control, and issue management during the transition process.) REPORTING PROCEDURES (Define the reporting procedures for the transition period. Include such things as type of evaluations (review, audit, or test) as well as anomalies that are identified during the performance of these evaluations shall be reported.) APPENDIX A – SAMPLE WORK BREAKDOWN STRUCTURE (WBS) Product Installation Distribute Product (software) Package and distribute product Distribute installation information Conduct integration test for product Conduct regression test for product Conduct user acceptance test for software Conduct reviews for product
  • 8. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 8 of 9 Perform configuration control for product Implement documentation for product Install Product (software) Install product (packaged software) and database data Install any related hardware for the product Document installation problems Accept Product (software) in Operations Environment Compare installed product (software) to acceptance criteria Conduct reviews for installed product (software) Perform configuration control for installed product (software) Operations and Support Operate the System Utilize installed software system Monitor performance Identify anomalies Produce operations log Conduct reviews for operations logs Perform configuration control for operations logs Provide Technical Assistance and Consulting Provide response to technical questions or problems Log problems Maintain Support Request Logs Record support requests Record anomalies Conduct reviews for support request logs
  • 9. OPERATIONS AND MAINTENANCE TransitionPlan NUMBER: 443-04-nnn EFFECTIVE DATE: mm-dd-2015 Page 9 of 9 Maintenance Identify Product (software) Improvements Needs Identify product improvements Develop corrective/perfective strategies Produce product (software) improvement recommendations Implement Problem Reporting Method Analyze reported problems Produce report log Produce enhancement problem reported information Produce corrective problem reported information Perform configuration control for reported information Reapply Software Life Cycle methodology