Difference between revisions of "System Deployment and Use"
(→Topics) |
|||
Line 10: | Line 10: | ||
Planning for system deployment and use should begin early in the SE process to ensure successful transition into operational use. | Planning for system deployment and use should begin early in the SE process to ensure successful transition into operational use. | ||
+ | |||
+ | ===Topics=== | ||
+ | The topics contained within this knowledge area include: | ||
+ | *[[System Deployment]] | ||
+ | *[[Operation of the System]] | ||
+ | *[[System Maintenance]] | ||
+ | *[[Logistics]] | ||
==System Deployment and Use Fundamentals== | ==System Deployment and Use Fundamentals== |
Revision as of 19:16, 26 July 2011
Introduction
System deployment and use are critical systems engineering (SE) activities that ensure that the developed system is operationally acceptable and that the responsibility for the effective, efficient, and safe operations of the system is transferred to the owner. System deployment includes transition of the capability to the ultimate end-user, as well as transition of support and maintenance responsibilities to the post-deployment support organization or organizations. It may include a period of reliability demonstration tests and the phasing out of legacy systems that the developed system replaces. System use includes a continual assessment of the operational effectiveness of the deployed system or service, identification of mission threat and operational risk, and performance of the actions required to maintain operational effectiveness or evolve the capability to meet changing needs. Evolution of the operational system may occur with smaller maintenance actions or, if the changes cross an agreed-to threshold (complexity, risk, cost, etc.), may require a formal development project with deliberate planning and SE activities resulting in an enhanced system. As the operational phase is generally the longest in the system life cycle, activities that may occur during operation are allocated between two knowledge areas (KAs): System Deployment and Use and System Life Cycle Management. The System Life Management KA specifically deals with SE activities required for system evolution and end of system life: these include service life extension, capability updates/upgrades and modernization during system operation, and system disposal and retirement. In contrast, the System Deployment and Use KA specifically deals with activities required to ensure that system operation can continue as expected. This includes the following topics:
- Deployment/Transition
- System Use
- System Maintenance
Planning for system deployment and use should begin early in the SE process to ensure successful transition into operational use.
Topics
The topics contained within this knowledge area include:
System Deployment and Use Fundamentals
System deployment and use includes the processes used to plan for and manage the transition of new or evolved systems and capabilities into operational use and the transition of support responsibilities to the eventual maintenance or support organization. The use stage normally represents the longest period of a system life cycle and, hence, generally accounts for the largest portion of the life cycle cost. These activities need to be properly managed in order to evaluate the actual system performance, effectiveness and cost in its intended environment and within its specified utilization over its life cycle. Included in use are the aspects of continuation of personnel training and certification. As part of deployment/transition activities, special conditions that may apply during the eventual decommissioning or disposal of the system, or for a legacy system it may replace, are identified and accommodated in life cycle plans and system architectures and designs (see System Development KA). SE leadership ensures the developed system meets specified requirements, that it be used in the intended environment, and that when the system is transitioned into operation, it achieves the users’ defined mission capabilities and can be maintained throughout the intended life cycle. SE ensures that plans and clear transition criteria into operations are developed and are agreed to by relevant stakeholders and that planning is completed for system maintenance and support after the system is deployed. These plans should generally include reasonable accommodation for planned and potential evolution of the system and its eventual removal from operational use. (For additional information on evolution and retirement, please see the System Life Cycle Maintenance KA.)
Practical Considerations
Glossary
References
Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Citations
List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Primary References
All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.
Additional References
All additional references should be listed in alphabetical order.