08_Atch_01_GSOW_A0001_20090519.doc

ATTACHMENT 1: GOVERNMENT STATEMENT OF WORK

ATTACHMENT 1: GOVERNMENT STATEMENT OF WORK

GPS Advanced Control Segment (OCX)

Attachment 1:

Government Statement of Work (GSOW) for

FA8807-09-R-0003

29 April 2009

TABLE OF CONTENTS

INTRODUCTION

1. Scope

2. Applicable Documents

3. Next Generation Control Segment (OCX) Requirements

3.1 OCX System Engineering/Program Management

3.1.1 OCX Systems Engineering

3.1.1.1 Requirement Development and Verification

3.1.1.2 Risk Management

3.1.1.3 Configuration Management

3.1.1.4 Critical and Technical Performance Measures

3.1.2 OCX Program Management

3.1.2.1 Business Operations

3.1.2.2 Subcontract Management

3.1.2.3 Contracts and Pricing

3.1.2.4 Data Management

3.1.2.4.1 Library

3.1.2.4.2 Information Services

3.1.3 Software Engineering 13

3.1.3.1 Software Development and Software Maintenance Planning 14

3.1.3.2 Software Process and Monitoring

3.1.3.3 Segment-wide Software Design and Software Interfaces

3.1.3.4 Segment-wide Software Integration and Verification

3.2 Integration, Assembly, Test and Checkout

3.3 RESERVED

3.4 OCX System Test & Evaluation

3.5 OCX Training

3.6 OCX Data

3.7 OCX Peculiar Support Equipment

3.8 OCX Common Support Equipment 23

3.9 OCX Transition, Operations and Maintenance Support 23

3.9.1 Site Activation

3.9.2 Interim Contractor Support for Block 1.0

3.9.2.1 Transition Support

3.9.2.2 Level I Hardware Maintenance

3.9.2.3 Level I Software Maintenance

3.9.2.4 Level II Hardware Maintenance

3.9.2.5 Level II Software Maintenance

3.9.2.6 Problem Resolution Support

3.9.2.7 Tech Order Support

3.10 RESERVED

3.11 OCX Initial Spares and Repair Parts

3.12 Ground Terminal Subsystems

3.12.1 Monitor Station (MS)

3.12.2 Legacy Ground Antenna (GA)

3.12.3 RESERVED (for AGA)

3.13 Command and Control Subsystem

3.13.1 TT&C Software

3.13.2 OCX MCS, AMCS

3.14 Mission Management Subsystem

3.15 Data Archive/Storage Subsystem

3.16 Mission Data Processing Subsystem

3.17 Mission Data Analysis and Dissemination Subsystem 34

3.18 OCX Mission Infrastructure Subsystems

3.18.1 GPS System Simulator (GSYS)

3.18.2 Test Assets

3.18.3 Development Labs

3.18.4 Transition Support Facility/Sustainment Support Facility

3.18.5 OCX Communication Infrastructure

3.18.6 Enterprise Infrastructure

3.18.7 Crew Training Simulator

3.19 RESERVED

3.20 RESERVED

3.21 RESERVED

3.22 RESERVED

3.23 RESERVED

3.24 Sustainment

3.24.1 Option for Software Maintenance Level I

3.24.2 Option for Software Maintenance Level II

3.24.3 Option for Hardware Maintenance Level I

3.24.4 Option for Hardware Maintenance Level II

3.24.5 Option for Technical Order Support

4. Inter-segment Overarching SEIT/PM

4.1 System Integration Demonstration Management

4.2 GPS system of system requirements verification

4.3 System of Systems Test Support

4.4 System Integration Technical Interface Meetings

4.5 SEIT Processes

4.6 DoDAF Architecture

4.7 Modeling and Simulation Support Management

4.8 System Technical Performance Measures Support Management 51

4.9 System Capability Thread Support Management

4.10 Specialty Engineering Management

4.10.1 Integrated Logistics Support

4.10.2 Quality Assurance (QA)

4.10.3 Reliability, Maintainability, and Availability

4.10.4 Survivability

4.10.5 Environmental, Safety and Occupational Health (ESOH)

4.10.6 System Safety

4.10.7 Human Factors

4.10.8 Electromagnetic Compatibility and Radio Frequency Management 58

4.10.9 Positioning, Signal Integrity, and Continuity Assurance (PSICA) 59

4.10.10 Information Assurance Certification Accreditation and Approvals 59

4.10.11 Continuity of Operations, Disaster Recovery, and Incident Response 60

4.10.12 Program Protection, Technology Control and Foreign Disclosure 61

4.10.13 Information Assurance Requirements and Processes

4.10.14 Information Assurance Contractor Training and Certification 62

4.10.15 International Compatibility and Interoperability 62

5. Special Studies

6. Capability Insertion Program

7. System Modifications Annex 1 CSOW Instructions

OCX Phase B Government Statement of Work INTRODUCTION: OCX - GPS Advanced Control Segment (GPS Ground System) The GPS system is acquired by the Global Positioning Systems Wing (GPSW), Space and Missile Systems Center (SMC), Los Angeles AFB, El Segundo, California.

GPS is a satellite-based radio navigation system that provides accurate position, velocity, and time (PNT) for military and civil users worldwide. To achieve overall system capability requires three key but distinct segments: Command & Control, Space Vehicles, and User Equipment. System level requirements are allocated to these three segments which are synchronized to enable satisfaction of system performance standards and required operational capability.

This statement of work is associated with the Ground based command and control segment of GPS. The GPS Advanced Control Segment (OCX) will provide new capabilities to continue to ensure GPS remains the world standard for PNT and eliminates shortcomings and vulnerabilities inherent in the current architecture that threaten to severely impact vital military operations, civil commerce, transportation, and public safety.

The overall acquisition strategy is to incrementally develop a ground control segment that can introduce new capabilities through block deliveries to operations. This strategy will reduce overall execution risk, deliver new capability to the field faster, and enable a more predictable and executable cost, schedule, and performance baseline.

1. Scope This GSOW covers design, development, testing, integration, verification, validation, deployment, transition to operations, and sustainment throughout the GPS OCX life cycle. Specifically, OCX shall support the assured integrity and continuity of the GPS control system in compliance with the GPS III Control Segment Specification (SS-CS-800). This GSOW tracks to the OCX Phase B Work Breakdown Structure (WBS) and describes the effort required to complete OCX Blocks 1.0 and 2.0. It covers all tasks to achieve: command and control of the GPS IIA, IIR, IIR-M, IIF, and IIIA SVs, replace the OCS Master Control Station (MCS) with a new OCX MCS, replace the OCS Alternate Master Control Station (AMCS) with a new OCX AMCS, upgrade or replace the Air Force and NGA Monitor Stations associated with changes to communications networks, provide the ability to monitor all current GPS signals as well as L1C, L2C, L5 and M-Code and deliver new/upgraded support facilities. It includes modifications to the existing GPS Ground Antennas (GAs), if needed, to ensure compatibility with new/modified OCX interfaces. It also includes tasks for the evolution of the control segment to deliver a robust infrastructure for new information assurance, integrity, and net centricity requirements to support future NAVWAR and Effects Based Operations (EBO) capabilities. This GSOW also includes a capability insertion program which studies, analyzes, demonstrates, tests, and prototypes key technologies capabilities relevant to OCX Block 3.0 and OCX Block 4.0.

2. Applicable Documents Attachment 2, “Compliance and Reference Document List and Tailoring”, contains the compliance documents applicable to this contract.

3. Next Generation Control Segment (OCX) Requirements

3.1. OCX System Engineering/Program Management

The Contractor shall:

a. Design a system that meets all requirements of SS-CS-800 (effectivities 10-15) and other applicable specifications and ICDs and is operationally effective, suitable, sustainable, cost-effective, meets DoD security certification/accreditation requirements, facilitates interconnections with classified systems, and meets DoD net-readiness standards for interoperability, supportability and functional capability.

b. Apply Systems Engineering and Program Management to transition, ICS, sustainment, and the Capability Insertion Program.

3.1.1 OCX Systems Engineering (CDRL A001) (CDRL A037) (CDRL A054) (CDRL A059) (CDRL A063) (CDRL A060) The contractor shall:

a. Prepare and maintain a Systems Engineering Management Plan (SEMP) and ensure that it is compatible with the Government-supplied SEP. (CDRL A037)

b. Implement the PCO approved SEMP and manage the Ground Segment systems engineering processes in accordance with SMC Standard SMC-S-001 “Systems Engineering”. Analyze OCX system functional, performance, support, and interface requirements. Derive, allocate, link, and control the OCX requirements baseline. Implement a requirements flow-down management system that is electronically accessible by the Government providing bi-directional traceability among specification, design, integration, test and verification for all hardware and software work products performed on this SOW.

c. Incorporate systems engineering and analytical techniques to design a system that meets performance requirements and maximizes affordability for the life-cycle of OCX. Conduct ground system and subsystem trade studies and engineering analyses. Conduct system effectiveness modeling and technical budget modeling to determine the impact of subsystem performance/functional budget variances on OCX system performance. Provide support to definition of OCX development labs and test beds (e.g., the Transition Support Facility (TSF)). Provide support to definition of OCX functional, environmental, and performance test requirements and support integration, assembly & test (IA&T) activities.

d. Produce OCX system functional, timing, and data/control flows, and develop and deliver the portions of the Orbital Operations Handbook (OOH) that apply to OCX. Develop and maintain the OCX functional, software, and hardware diagrams. Document and maintain the OCX system design baseline. Coordinate change assessments at the system and subsystem levels. (CDRL A060)

e. Conduct Technical Review tasks to include the coordination and preparation of technical information for presentation, the compilation and distribution of agendas, the documentation of review minutes, and the coordination of review action item resolution. Technical reviews shall include, but not be limited to, design reviews (e.g., Software Specification Review (SSR), Preliminary Design Review (PDR), Critical Design Review (CDR)), audits (e.g., Standard CMMI Appraisal Method for Process Improvement (SCAMPI)), and milestone approvals (e.g., Milestone-C (MS-C) support), as well as technical interchange meetings (TIMs) (e.g., Transition Working Group (TWG)).

f. Develop in Block 1.0 and maintain in Block 2.0 an overall OCX system architecture with supporting rationale that provides the required functional capabilities and performance in accordance with applicable Control Segment (CS) specifications. Develop an OCX architecture that provides the following attributes: capable of evolving to meet changing GPS mission requirements; capable of scaling performance to meet increasing demands on OCX resources; capable of easily tracking evolution of commercial off the shelf (COTS) and government off the shelf (GOTS) hardware and software products used in the OCX system; feasibility of security C&A, ease of use, ease of maintenance; reduction of staffing requirements for routine constellation operations; and establishing a foundation for net-centric operations. Ensure that the overall OCX architecture is used to flow down to documented architectural descriptions for functional areas (e.g., software, communications, security). Develop models and simulations, and use them to support analyses and trade studies.

g. Closely coordinate activities in SE/PM with those with those activities described in 3.1.3 Software Engineering and 3.6 OCX Data.

h. Plan a seamless transition from the AEP/LADO architecture to OCX (Block 1.0) without interruption or degradation of GPS services and without interruption of the capability to command and control the operational GPS satellites. Write detailed procedures for transitioning control of the constellation to OCX, verifying OCX performance, and falling back to AEP/LADO if needed. Establish metrics to detect the need to fall back and write the procedures for the process of falling back to AEP/LADO in a timely manner to prevent disruption of the GPS signal in space.

i. Ensure that OCX is delivered such that it will support a seamless transition to operations (with fall-back planning) from OCX Block 1.0 to Block 2.0 and for each incremental delivery within Blocks 1.0 and 2.0. Ensure that Block 2.0 will be delivered such that it will support a seamless transition to its successor regardless of whether that is an additional OCX Block or a separate acquisition.

3.1.1.1 Requirements Development and Verification (CDRL A006) (CDRL A007) (CDRL A008) (CDRL A011) (CDRL A012) (CDRL A025) (CDRL A037) The contractor shall:

a. Perform Requirements Development and Verification tasks in accordance with SMC Standard SMC-S-001 “Systems Engineering”, TOR-2005(3901)-4243 and appropriate OCX specifications. Use a disciplined systems engineering approach to define requirements, control changes, verify the OCX product, and achieve operational suitability.

b. Perform the functional, performance, support, and interface requirements analyses required to derive, allocate, link, and control the OCX requirements baseline, and provide traceability and verification of all OCX and interface requirements in accordance with SMC Standard SMC-S-001 “Systems Engineering” (see also CJCSI 6212.01). Conduct activities that involve Government operational stakeholders to proactively and accurately derive the requirement and design details associated with maturing concepts of operations. Define, develop, and maintain prime item and critical item specifications in accordance with applicable Military Standards. Perform the flow-down of requirements from A-level to B1-level specifications and B2-level specifications, and develop and maintain a computer-based Requirements Management (Allocation, Traceability and Verification) Database. Develop product fabrication specifications. Provide traceability from lower level specs to the applicable ground segment specifications. Conduct a Software Specification Review (SSR) to demonstrate the adequacy of the requirements prior to preliminary design.

c. Develop and implement an OCX Program Verification plan including processes to allocate system-level requirements and segment, prime item, critical item, subsystem, and element verification activities. Ensure that each requirement is assigned a requirement verification owner who is responsible for preparing a written plan for how the requirement will be verified in the OCX system.

3.1.1.2 Risk Management (CDRL A061)

The contractor shall:

a. Establish, implement, and maintain an active Risk and Opportunities Management Program that is compatible with the GPS Wing Systems Engineering Plan (SEP) and Risk Management process GP OI 63-1108, “Risk Management”. Minimize and control technical, cost, and schedule risk on the OCX program. Maintain a Risk Assessment database that is electronically accessible by the Government.

b. Use a risk management tool to manage the risk database that has the ability to export the OCX risk database in a format compatible with the GPSW risk database tool (expected to be Active Risk Manager.) Maintain all discrete risk mitigation activities in the IMS with unique identifiers (UIDs), and have the ability to retrieve all risk mitigation tasks for a specific identified risk from the IMS.

c. Identify and mitigate ground segment risks caused by events external to the OCX Program. Support mitigation of system-level risks. Support the GPSW enterprise risk management process.

3.1.1.3 Configuration Management

The contractor shall:

a. Establish strong, comprehensive Configuration Management (CM) processes for both software and hardware, and perform CM tasks in accordance with MIL-STD-973. Maintain control over the software/hardware baselines at development labs, subcontractors, and test facilities, as well as the software/hardware baselines at the MCS, AMCS, and TSF/SSF. Ensure that contractor’s CM processes and tools inter-operate with the government’s CM processes and tools. Maintain the functional baseline.

b. Conduct Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) in accordance with MIL-STD-973 to verify the functional and physical baselines of products and demonstrate compliance to the technical requirements of the developmental and product specifications.

c. Maintain the product baseline after PCA, with GPSW IPTs maintaining change veto rights.

d. Co-chair FCA/PCAs with the GPSW down to the level of critical items and approval of Software Requirement Specifications (SRSs) and Software Product Specifications (SPS).

3.1.1.4 Critical and Technical Performance Measures (TPM) (CDRL A053) The contractor shall:

a. Develop, track and perform trend analysis for OCX TPMs in accordance with SMC Standard SMC-S-001 “Systems Engineering”. Select parameters and establish metrics to track critical TPMs. Maintain a metrics database that is electronically accessible by the Government. Present data to the Government when requested.

b. Develop metrics to track and perform trend analysis for OCX contributions to meeting Critical Technical Parameters (CTPs), Key Performance Parameters (KPPs) and Key System Attributes (KSAs) in the GPS III Capabilities Development Document (CDD).

3.1.2 OCX Program Management (CDRL A042)

The contractor shall:

a. Provide program management including business and administrative planning, organizing, directing, coordinating, controlling, and approval actions designed to accomplish the overall program objectives.

b. Maintain the IMS as an essential program management tool and ensure currency and consistency as an essential element of the Earned Value Management System.

d. Establish and maintain joint IPTs to include subcontractors as well as members of the GPSW and other GPS stakeholders. Some stakeholders may be resident at the contractor’s site. Include other Segment (associate) contractors in IPT meetings, as appropriate. Provide the resources associated with implementation of the joint IPT (e.g., administrative support, office space, computer resources, and communications for Government resident and visiting personnel).

e. Conduct design reviews and other scheduled reviews in accordance with MIL-STD-1521B.

f. Support Government formal readiness reviews, as appropriate, as described in SMCI 63-1202, SMCI 63-1203 and SMCI 63-1204.

g. Attend other segment major reviews and system integration TIMs for the purposes of understanding segment synchronization and identification of potential disconnect

3.1.2.1 Business Operations (CDRL A001) (CDRL A013) (CDRL A014) (CDRL A015) (CDRL A038) (CDRL A040) (CDRL A041) (CDRL A042) (CDRL A046) (CDRL A075) (CDRL A077) (CDRL A078) The contractor shall:

a. Conduct weekly Business Management Reviews. The content of the Reviews shall include (but not be limited to) the following topics: Updated Expenditures, Billing Status, Funding Status, Earned Value Management System (EVMS) status, Contractual Actions/Correspondence, Critical Path reviews, Staffing, Government Furnished Property (GFP) Status, Top Ten issues, and Risk Summary.

b. Conduct weekly Schedule Management Reviews. The content of the Reviews shall include (but not be limited to) the following topics: schedule metrics, identification of late tasks, critical path schedules, and program summary schedules.

c. Conduct monthly Program Management Reviews including (but not limited to): Critical Path Schedule, Earned Value Metrics, Key software and KPP/KSA metrics, Risk Summary, IPT status of problems and progress, and program issues.

d. Develop, update, and maintain the Contract Work Breakdown Structure (CWBS), Integrated Master Plan (IMP), and an Integrated Master Schedule (IMS) to execute and track the progress of the program, including subcontractor deliverables.

e. Deliver a monthly IMS update that aligns forecasted dates with the Earned Value EAC for major milestones. The detail PMB planning shall not be less than 12 months. The IMS shall be maintained as the primary tracking tool for Earned Value Management System (EVMS) to assess program status.

f. Support all requirements identified by SMC-H003, SMC-H017 and DFARS § 252.234-7002.

g. Establish and maintain Associate Contractor, Non-Disclosure, and other agreements (-H008: ACA) that may be required in support of contract activities.

h. Maintain budgets by elements cost, track cumulative and monthly resource expenditures, and performance against established budgets. Provide an annual Resource Distribution Table (RDT) which includes prime contractors, subcontractors, and lower-tier subcontractors cost that meet the Cost Summary Data Report (CSDR) threshold.

i. Establish and maintain operations and cost reporting that supports the monthly delivery of the Contract Performance Report (CPR) and Contract Funds Status Report (CFSR). Reconcile the CPR and the CFSR when submitted to the Government. When two or more appropriation sources are used segregate funds data by appropriations in the CFSR accounting reference.

j. Synchronize subcontractor data contained in the CPR, IMS and CFSR submittal for the same accounting month as the prime’s CPR, IMS and CFSR submittals.

k. Coordinate and receive Government concurrence for the rolling wave detail planning strategy for the Performance Measurement Baseline (PMB). Ensure that rolling waves are aligned to logical program milestones such as SSR, PDR, CDR, and the final software drops of OCX Blocks 1.0 and 2.0.

l. Maintain updated Contract Value, Management Reserve, Undistributed Budget and PMB change logs. These logs shall be available for Government review at any time.

m. Support a robust Integrated Baseline Review (IBR) in accordance with section (e) of DFARS 252.234-7002 no later than 180 days after (1) contract award (2) the exercise of significant contracts options, and (3) incorporation of major Performance Measurement Baseline (PMB) modifications.

n. At a minimum, provide to the Government a “most likely” Estimate at Completion (EAC) consistent with the Contractor’s System Description, Policies and Procedures; the program’s cumulative Earned Value indices; the program’s Technical performance and risk profile, and the forecast finish dates contained in the IMS.

o. Provide on a quarterly basis the following with the “most likely” EAC: the anticipated Management Reserve burndown plan by month, a Risk / Opportunity resolution matrix that identifies risk by item, and the worst case impact and probability of occurrence of each risk.

p. Provide life cycle cost data to be used by SMC and the GPSW to support ongoing and future cost estimating. Include actual recurring and non-recurring costs, functional costs such as engineering, quality control, tooling and manufacturing, hardware quantities at the WBS level, and other direct and indirect costs without profit/fee. Include functional cost-hour and progress curve reports. All of these cost elements must be traceable to the DCARC approved CWBS.

q. Support GPSW-sponsored Independent reviews, as required, to provide insight to senior teams evaluating program readiness for key program events (e.g., TRAs, IPAs associated with Milestone approvals, IRTs, IRRTs).

r. Provide initial and final reports on software resources data to include size, effort, schedule, and other descriptive development data. This report constitutes a contract data deliverable that formalizes the reporting of software metric and resource data.

3.1.2.2 Subcontract Management

The contractor shall:

a. Establish necessary subcontracts and oversee the administration of subcontracts, purchase orders with subcontractors, and interdivisional agreements. Provide guidance to subcontractors for development and administration of subcontract agreements, purchase orders, and interdivisional agreements to ensure proper flow-down of Government requirements. Place priority attention on subcontractor software process planning and management and on test philosophy and planning. Ensure any subcontractor data is available to the Government.

b. Employ close technical, programmatic and administrative management of subcontractors to ensure adherence to all standards and approved practices. Include Government personnel in all major subcontractor reviews.

3.1.2.3 Contracts and Pricing

The contractor shall perform all necessary contract and pricing management activities, including but not limited to: proposal development, negotiation, administration and implementation of the contract and contract changes, responses to “what if” exercises initiated by GPSW, responses to below threshold contract changes in accordance with SMC Standard SMC-S-019 and other special contract provisions.

3.1.2.4 Data Management (CDRL A039)

The Contractor shall:

a. Implement and maintain a seamless Electronic Data Interchange (EDI) Network utilizing web-enabled technology to provide continuously available, secure, encrypted remote access to the Government for all draft or completed items on the Data Accession List (DAL) and the Contract Data Requirements List (CDRL) as well as all other working data, including subcontractor data, developed to support the management and engineering efforts of the program. The Contractor shall establish an EDI Network capable of fully supporting Government access to information within ten business days of contract award. The program office will provide a list of authorized personnel for access to the Contractor's database after contract award. The Contractor's information shall be compatible with typical Government PC-based systems using the MS Office suite of applications (e.g., Word, Excel, and PowerPoint) as well as Adobe Acrobat.

b. The information shall be safeguarded at multiple levels consistent with Attachment 6 “DD Form 254 Contract Security Classification Specification” (e.g., Unclassified, For Official Use Only (FOUO), Confidential, Secret).

c. Official CDRL data items shall still be submitted as directed in Exhibit A, ‘Contract Data Requirements List’. Providing access to a data item through the EDI Network is not sufficient to receive credit for meeting the delivery requirements in Exhibit A.

d. The Contractor shall use the Telelogic Dynamic Object Oriented Requirements System (DOORS) tool to maintain and manage its OCX requirements documentation. At a minimum, the DOORS tool shall be used to maintain and show traceability of the OCX requirements from the SS-CS-800 down to all of the requirements documents that will be generated from the SS-CS-800 as required by the Contract DD Forms 1423 in the CDRL. The Contractor shall also maintain and deliver applicable CDRL items using DOORS, as required by the Contract DD Forms 1423, and allow Government representatives to remotely access the Contractor's OCX DOORS database on a real-time basis. The initial DOORS version to be used by the Contractor for OCX shall be coordinated with the Government at contract award and all future changes to the DOORS version shall be coordinated with the Government. Access to the DOORS database shall be provided within thirty (30) calendar days of contract award.

3.1.2.4.1 Library (CDRL A037)

The contractor shall provide an electronic design decision database that is readily available and directly accessible by the Government. Document and organize data used and generated by the systems engineering effort. Provide an audit trail of results and rationale from identified needs to verified solutions. Provide a chronological track with links to the initial plans and results from each iteration (to include tradeoffs and other assessments) and to changes to the baseline or functional architecture as a result of the decisions.

3.1.2.4.2 Information Services

The contractor shall:

a. Ensure contractor-generated data is compatible with entry into the GPSW integrated data environment (IDE) or directly participate in using the GPSW IDE.

b. Generate data necessary to complete assigned actions for entry into the IDE.

c. Provide an electronic collaborative data environment for use by the GPS Wing and associate contractors.

d. Provide feedback for GPSW consideration on how these processes and its interrelationship with its internal contractor processes can improve program effectiveness and efficiency.

3.1.3 Software Engineering (CDRL A001) (CDRL A006) (CDRL A011) (CDRL A022) (CDRL A025) (CDRL A027) (CDRL A028) The contractor shall:

a. Establish a government-contractor collaborative approach to oversee software development with an emphasis on:

1. Incremental software delivery based on realistic size, effort, cost, reliability, and schedule estimates.

2. Feasibility of overlapping software development schedules.

3. Management of multiple software baselines and multiple security classification levels.

4. Maturity and appropriateness of commercial items, COTS, Government Off-The-Shelf (GOTS), and reuse selection items.

5. Support of government studies and prototyping of high risk areas for software.

6. Software risk management approach that is effective in identifying and mitigating significant software risks. The software risk management approach shall be IAW the OCX Risk Management Plan.

7. Identification of anticipated changes of COTS, GOTS, and reuse items including early identification of potential issues and opportunities. Coordinate decisions about which upgrades need to be applied to the OCX operational baseline with incremental build planning and periodic technology refreshes (as in Sec. 4.10.1m).

8. Identification, assessment, demonstration (when possible), and incorporation of COTS, GOTS, and reuse software that supports developed software and software integration.

9. Development of systems and software management, engineering, development, and work products to support periodic evaluation (as defined in the contract) of the contractor team’s capabilities using the Standard CMMI Appraisal Method for Process Improvement (SCAMPI) (See Sec. 3.1.3.2.d.).

b. Provide software engineering management and control to ensure all software activities in development of OCX software and integration with other non-developed software used in OCX (e.g., COTS and GOTS applications) are conducted in accordance with the contractor’s government-approved OCX Software Development Plan (SDP). This task includes all software used in: 1) satisfying, verifying, or validating requirements; 2) testing (e.g., test scripts); 3) performing or supporting operations; and 4) performing or supporting sustainment.

c. Plan and control the technical, business, and project management efforts necessary to accomplish overall GPS OCX software objectives in accordance with the established IMS.

d. Provide software engineering management interaction through support for segment level reviews. Conduct software level progress reviews, design reviews, peer reviews, joint technical reviews, test readiness reviews, and production readiness reviews. Participate in meetings and reviews, as necessary, to ensure effective and efficient program execution including Program Management Reviews to report software technical, cost, and schedule performance at Ground Segment Program Management level.

e. Describe how requirements were allocated from the OCX system level to the lowest level of decomposition of the software items at program reviews, including SSRs, IBRs and PMRs.

f. Support change assessments at the control segment, elements and software levels, and follow the software lifecycle processes for making approved software changes.

3.1.3.1 Software Development and Software Maintenance Planning (CDRL A022) (CDRL A030) (CDRL A049) (CDRL A057) The contractor shall:

a. Develop and maintain an integrated SDP for all team members and all software items in the following categories (including the software portion of firmware): ground segment (e.g., mission planning; telemetry, tracking, and commanding; data archive and storage, mission data processing; mission data analysis and dissemination, mission support; infrastructure and services, supporting databases and tools, SV integration support); and other software (e.g., applications, security, safety, training, modeling, simulation, analysis, database support, automatic test equipment, test facility and environment, and maintenance) used in any of the following: a) satisfying, verifying, or validating requirements; b) performing or supporting operations; c) performing or supporting sustainment.

b. Plan the builds and the requirements to be met in each build.

c. Plan the integration, regression testing, and qualification testing of software items for each build

d. Develop and maintain a plan for analyzing and correcting all problems found during all phases of the software life cycle.

e. Develop, maintain, and follow a plan for transitioning the software to operations and sustainment.

f. Employ automated configuration management tools that enforce controls for software development, preventing unauthorized modifications to software including software that has not yet been moved to the production code library. Define and implement a software development process that limits the privilege of application programmers to change production code and data, and periodically review those privileges

g. Integrate the PSICA Plan requirements into the contractually binding SDP.

h. Develop and employ a plan for net-centric service development and deployment that utilizes service versioning compatible with Joint IC/DoD service versioning guidelines or other applicable DoD service versioning guidance.

3.1.3.2 Software Process and Monitoring (CDRL A053)

The contractor shall:

a. Implement a comprehensive software and system metrics process including the use of leading quality indicators and performing cross-metric analyses. Collect, analyze, and report software metrics data, including at a minimum the metrics in the Segment and Software Metrics Report (SSMR). Report progress on net-centric service development using a method that is, at a minimum, compliant with the Data and Service Exposure Tracking Sheets in accordance with CJCSI 6212.01.

b. Evaluate software products and control the software development through proactive analysis and corrective action (e.g., cost, schedule, tasks, progress of peer reviews, product metrics, integration, verification).

c. Maintain consistency among software products (e.g., requirements, use cases, architecture documentation, design artifacts, code, and test cases). Identify interdependencies between software artifacts and maintain them in an automated system to support software design analysis and assessment of impacts due to changes.

d. Support, participate in, and respond to feedback from SCAMPI(SM) process improvement appraisals.

e. Develop and maintain a process improvement plan resulting from findings of process improvement appraisals, product and process audits, and other reviews.

f. Perform process improvements in accordance with the process improvement plan.

g. Collect all data on software failures, discrepancies, and recoveries required by MIL STD 785B/T task 104.

h. Develop, maintain, and adhere to a rigorous process for tracking problem reports (PRs). Ensure that all PRs are proactively communicated to the government in a timely manner in a form that is compatible with the government’s PR tracking system. The PR tracking process and system shall include for each PR: identification of the PR’s source, assessment of the PR’s category of severity, and the current status of the handling of the PR through final operational verification and closure.

3.1.3.3 Segment-wide Software Design and Software Interfaces (CDRL A011) (CDRL A022) (CDRL A023) (CDRL A025) (CDRL A026) (CDRL A027) (CDRL A028) (CDRL A029) (CDRL A030) (CDRL A031) (CDRL A032) (CDRL A033) (CDRL A034) (CDRL A053) (CDRL A055) (CDRL A075) (CDRL A076) The contractor shall:

a. Derive system, segment, and subsystem requirements and allocate requirements to the lowest level of decomposition. Work with associate contractors in other segments to ensure that requirements and their flow-down and allocation are correct. Flow-down the GPS system-level requirements through the segment and subsystem levels, and allocate requirements to the lowest level of decomposition. Provide timely feedback for issues identified during flow-down and allocation of requirements. Maintain design information about software-related interfaces in an automated system to support software design analysis and assessment of impacts due to changes.

b. Perform segment-level design and develop overall segment-wide software architecture. Develop an overall OCX software architecture in coordination with the OCX overall system architecture (Sec. 3.1.1.f). Perform architectural and design assessments and provide supporting rationale to demonstrate the architecture provides the required functional capabilities and performance in accordance with applicable CS and interface requirements specifications. Specifically, develop an OCX software architecture that provides the following attributes: capable of evolving to meet changing GPS mission requirements; capable of scaling performance to meet increasing demands on OCX resources; capable of easily tracking evolution of commercial off the shelf (COTS) and government off the shelf (GOTS) hardware and software products used in the OCX system; feasibility of security C&A, ease of use, ease of maintenance; reduction of staffing requirements for routine constellation operations; and establishing a foundation for net-centricity. Ensure that the overall OCX software architecture is used to flow down to documented architectural descriptions for lower levels and flow up to the OCX overall system architecture. Develop software architectural models and use them to support analyses and trade studies.

c. Evaluate OCX software architecture using the ATAMSM (Architecture Trade-off Analysis Method) prior to PDR. Provide for active Government participation in ATAM events. Track the ATAM outcome as OCX risks

d. Identify, track, and resolve any software and interface issues between software items and subsystems. d. Identify, track, and resolve computer hardware resource utilization margin issues.

e. Implement and maintain the ground segment software, databases, support software, and documentation required to support integration, verification, launch preparation, and operations.

3.1.3.4 Segment-wide Software Integration and Verification (CDRL A012) (CDRL A026) (CDRL A027) (CDRL A028) (CDRL A030) (CDRL A031) (CDRL A032) (CDRL A033) (CDRL A049) (CDRL A050) (CDRL A051) (CDRL A053) The contractor shall:

a. Manage and conduct the integration, regression testing, and verification of each software item in each OCX element.

b. Manage and conduct the integration of ground segment subsystem and element software to verify the segment level software functionality.

c. Conduct a rigorous test program capable of identifying issues between software items and subsystems.

d. Maintain the integrity of the segment-wide software products and their configuration management. (See also Sec. 3.6.b.)

e. Support independent verification and validation (IV&V) of the critical ground segment software, as required. Deliver the ground segment and subsystem source code including the executable code and all the software patches, databases, and the associated documentation including flow diagrams to support the real-time IV&V tests.

f. Produce all software artifacts and perform all software verification processes required by the PSICA Plan.

3.2 Integration, Assembly, Test and Checkout

The contractor shall charge this effort to the individual product elements. This is a no-cost CWBS element.

3.3 RESERVED

3.4 OCX System Test & Evaluation (CDRL A052) (CDRL A067) (CDRL A068) The contractor shall:

a. Develop and implement an OCX Test Program in accordance with AFI 99-103 and other OCX test requirements. Ensure consistency with the GPS Enterprise Test and Evaluation Master Plan (TEMP). Ensure that the test program embraces a methodology that: verifies segment (CS-800) and allocated system-level (SYS-800) requirements; provides Integrated Test data collection opportunities for applicable Service Operational Test Agencies (OTAs); validates applicable mission capabilities as defined by the GPS and Military GPS User Equipment (MGUE) CDDs, CONOPS and Enabling Concepts; supports system certifications such as IA and Interoperability and Supportability; prepares the system for MOT&E activities in accordance with AFMAN 63-119; and supports data collection/analysis and problem resolution during OT&E execution.

b. Assist the Government with the planning and execution of the Enterprise TEMP, OCX Annex (Annex E), and System Test Plans and Procedures to include System Demonstrations and Integrated System Tests. Coordinate applicable System Demonstrations with the GPS IIIA prime contractor to achieve synchronization and unification of OCX with GPS IIIA and user interface test cases.

c. Conduct test readiness reviews subject to Government approval prior to the start of Full Qualification Test and Run for Record in accordance with the GPS E-TEMP.

d. Perform segment integration and checkout prior to factory testing to provide for early problem detection and resolution. Specifically:

1. Plan and implement a robust and disciplined component, element, sub-system, and system level test and evaluation program to verify and validate that the delivered system will meet program requirements and operates within the GPS Enterprise.

2. Ensure availability of test assets and test resources required for testing, such as facilities, test support equipment, test articles, trainers, and simulators, models and test beds are available and capable of supporting OCX development, transition, training, procedure checkout, Tech Order certification/verification, Developmental Test & Evaluation (DT&E), Integrated Test, Operational Test & Evaluation (OT&E), and deficiency resolution.

3. Develop and implement a Deficiency Resolution Process at the segment and system level in accordance with AF T.O. 00-35D-54 and consistent with the GPS Enterprise TEMP.

4. Develop and implement a Common T&E Database in accordance with AFI 99-103 and the GPS Enterprise TEMP.

5. Provide a contractor's Problem Reporting / Deficiency Reporting Database that is electronically compatible with the official AF Deficiency Reporting Database. (Electronically in the sense that files can be transferred from the contactor's data base to the government's database without manual entry. Translators are acceptable interfaces.) Use the USAF Deficiency Reporting Process in accordance with TO 00-35D-54, Section 2.3.1.2.

6. Perform verification and validation (V&V) in accordance with AFI 16-1001 and in accordance with Defense Modeling and Simulation Office's Guide, Introduction to VV&A Standards and Practices for DoD M&S. Assist the Government in the accreditation for simulators used for requirements' verification IAW AFI 16-1001.

7. Allocate cost and schedule resources to facilitate unplanned certification requirements that may arise during verification and transition testing.

8. Allocate cost and schedule resources to provide adequate margin for deficiency resolution activities throughout the test life-cycle.

9. Define Giver-Receiver relationships for all applicable test activities to include system demonstrations, Integrated System Test (IST), element and above verification events, system-level test support, and OT&E activities.

10. Support data collection, analysis, and reporting activities related to early OTA involvement (e.g., Operational Assessments, Status Reports) during the design review, Independent Program Assessment (IPA), Defense Space Acquisition Board (DSAB), and Milestone processes (e.g.,OCX MS-C).

11. Support development of Operational Test Readiness Process (OTRP) that includes but not limited to review of DT&E results; assessment of the system’s progress against CTPs documented in the TEMP; analysis of identified technical risks to verify that those risks have been retired during DT; and a review of the MOT&E entrance criteria specified in the GPS-E TEMP.

e. Assist the government in completing the DISA Joint Interoperability Test Certification (JITC) based upon the approved capabilities specifications.

f. Perform all work under this SOW element consistent with the proposed GPS Enterprise Test Evaluation Master Plan (TEMP) as depicted in the Figure 3.4-1.

g. Maintain the OCX system during developmental testing. This task includes items such as contractor support, technical assistance, spares, repair of repairables, warehousing and distribution of spares and repair parts during the test period.

Figure 3.4-1 Pictorial Overview of GPS Enterprise TEMP

3.5 OCX Training (CDRL A035) (CDRL A054) (CDRL A060)

The contractor shall:

a. Perform all efforts required to develop an OCX training approach that meets or exceeds the requirements of SS-CS-800 and the Space Training Contracts Requirements ((STCR) in Attachment 2), The contractor is responsible for delivering a training approach consistent with an incremental development approach designed to train and maintain proficiency of all operators and organic maintainers (both Level 1 & 2) of the system, taking into consideration the results of the government conducted training system requirements analysis (TSRA). Training will include updates for any system modifications, support to the GPS III associate contractor for development of SV training (i.e., cadre crew training), and support of technology insertion. Training will include an appropriate mix of tools, training simulators, and training media to guarantee training proficiencies are achieved.

b. Perform all efforts required to produce all deliverable training equipment, deliverable services, accessories, aids and facility drawings/lists (to include communication networks and external interfaces such as DMO-S, crypto, and DISA approval) required to meet the OCX training objectives. Items such as computers, peripherals, operations trainers, training course materials, contractor conducted training courses, curriculum, and other materials (required to design, execute, and produce the contractor developed training program) are included.

c. Prepare and deliver training materials and conduct training sessions for: launch, early orbit, anomaly resolution, and disposal satellite operations, routine constellation management, user operations support, Effects Based Operations (EBO), deployment of operations from the MCS to the AMCS, and return of operations to the MCS from the AMCS. Ensure that training plans include off-nominal situations and how to recognize and respond to them appropriately (e.g., SV anomalies, OCX anomalies, Air Force Satellite Control Network (AFSCN) and communications anomalies, operations around the time of system maintenance events, and operations at the AMCS). This task includes plans for transitioning system modifications developed between blocks into subsequent block deliveries.

d. Develop and conduct “cadre training” prior to block acceptance. Cadre training will include the conduct of two “focus days” per year to enable the operator cadre team to review the system design and obtain hands on familiarization with the system. Allow 2-3 days per session.

e. Develop a training approach for each OCX block taking into account OCX development, testing, deployment, and transition schedules. Ensure that the OCX training approach and schedule meets the constraint that all individual and crew training for a given OCX Block shall be in place at least 6 months before the Block is scheduled as Ready to Transition to Operations (RTO). Maintain the training schedule to take into account GPS IIR-M, GPS IIF, and GPS IIIA launch schedules, routine station-keeping and disposal operations for GPS IIA, GPS IIR, GPS IIR-M, GPS IIF, and GPS IIIA SVs, as well as maintenance of ground segment assets such as MSs and GAs. Ensure that the training plan also includes plans to aid in transition from interim contractor support to contractor sustainment support or government depot support as determined by the government.

f. Perform analysis of the training and training support needed to conduct a complete operations training program and provide necessary training integration support to ensure the OCX program is complementary with the GPS III Training program. Develop proficiency standards and training plans for all operations personnel (e.g., satellite operator positions, crew shift leaders, simulator operators, and system administration personnel).

g. Design, develop, build, integrate, test and checkout the Crew Training Simulator (CTS) in accordance with the government approved SDP. Ensure that the CTS allows operators to be trained and certified for GPS operations. Ensure that the CTS provides the functional equivalent from the user’s point of view of the GCC (GPS Control Center) / GNOC (GPS NAVWAR Operations Center) and the alternate control centers (the AGCC/AGNOC.) Provide the capability for the CTS (or Standard Space Trainer (SST), if directed) to manage the training sessions as well as to record and store student performance data and report it.

3.6 OCX Data (CDRL A073)

The contractor shall:

a. Perform all efforts required to make available all OCX deliveries required by individual CDRL DD Form 1423.

b. All commercial and noncommercial computer programs (inclusive of firmware) delivered to the Government under CLINs 0100-0600, 1000-3000 and 6000 shall be identical to that/those computer programs (inclusive of firmware) delivered to the Government in CDRL A033. In addition to OCX developmental software, this also includes all COTS/GOTS, NDI, or proprietary software required to install, check-out, and use the OCX software. Maintain rigorous configuration management controls to ensure that all incremental software data deliveries and software item deliveries remain in synchronization at all times and are documented accordingly.

c. Transfer OCX delivered software to the Government with all files and manuals to ensure that it can be recreated from provided source files (e.g., “make”…