Service Transition. Service Transition encompasses the planning and execution of all system changes for GCSS-MC/LCM Increment 1. System changes are divided into two categories, CRs and ECPs. Proposed system changes require a responsive, agile, yet disciplined approach to the GCSS-MC system and are categorized by components of the system and are aligned with the Program’s organization: • Infrastructure including hardware, operating system, and databases • Functional business processes • Cybersecurity System Security • Data Quality/Interfaces GCSS-MC/LCM Increment 1 currently has a documented backlog of approximately 600 CRs awaiting disposition. The CRs cover a broad area including functional, system security, interface management, infrastructure, training, audit, and WAN optimization. The CRs vary in level of priority (based on IEEE 12207 classification) and impact to the user community with the majority of changes classified as priority 2. The backlog is managed by the GCSS-MC CCB. GCSS-MC releases updates to the production system as fixes become available. In FY 2017, there were 288 CRs addressed. Of the 288 CRs, 175 CRs were children, meaning a parent CR resolution closed the child CR. Of the 113 CRs applied to production, 57 were for System Security & Infrastructure and 56 were configuration or code fixes. In addition, GCSS-MC released an average 5 CRs per quarter to address cybersecurity issues in FY 2017. The schedule also accounts for implementation of quarterly Oracle CPUs to maintain system security compliance. The SRs elevated from Incident and Problem Management from the Tier 1, 2, and 3 Service Desks are associated with a respective CR. CRs generated as a result of testing another change are associated to each other. Issues can be identified by a sub-type which identifies the GCSS-MC change authority (Change Assessment Board [CAB], CCB) and the associated configuration items impacted by the change. System changes come from a variety of sources, including, changes to the hardware or software design, code fixes, configuration fixes, and data scripts changes. System changes are also necessary to comply with and/or respond to IA/Cybersecurity requirements, integrating new capabilities (from external development, and design changes to make functions more responsive to customer needs). The Contractor shall provide responsive, disciplined support to sustain, change, and enhance the GCSS-MC/LCM Increment 1 system following the Configuration Management Process detailed in Figure 6.
Appears in 2 contracts