LADO_Sustainment_Bridge_PWS.pdf

PERFORMANCE- BASED WORK

STATEMENT

FOR

Launch and Early Orbit, Anomaly Resolution and Disposal Operations (LADO) Sustainment

FOR THE

309 SMXG SOFTWAREMAINTENANCEGROUP

Hill AFB, UT

1 June 2017

TABLE OF CONTENTS

SECTION TITLE PAGE

1. DESCRIPTION OF SERVICES

2. SCOPE

3. TECHNICAL REQUIREMENTS

4. SERVICES SUMMARY

5. PLACE / PERIOD OF PERFORMANCE & CDRLs

6. CONTRACT ADMINISTRATION

APPENDIX A: ACROYNMS

APPENDIX B: GOVERNMENT FURNISHED PROPERTY

APPENDIX C: SAFETY

1. DESCRIPTION OF SERVICES

This Performance-Based Work Statement (PWS) outlines the tasks and duties required of the contractor to support the OO-ALC 517th SMXS. The intent of this PWS is to obtain engineering services for activities needed in support of Launch and early orbit, Anomaly

Resolution, and Disposal Operations (LADO) sustainment.

1.1 Background.

GPS is a space-based radio navigation, time distribution and Nuclear Detonation (NUDET)

Detection System (NDS). Its mission is to provide precise, continuous, all weather, three dimensional (3-D) position, velocity, timing and NUDET information to properly equipped air, land, sea and space-based users. GPS serves both military and civilian users.

GPS consists of three segments: Space Segment (SS) which nominally consists of 31 operational satellites in 6 orbital planes with up to 6 satellites appropriately spaced in each plane; User Segment which consists of the NUDET Detection users and Navigation users;

and the Control Segment (CS) which consists of the LADO (Launch and early orbit, Anomaly resolution and Disposal Operations) system and the OCS (for operational orbit support).

LADO consists of three major functions: 1) Telemetry, Tracking and Commanding (TT&C),

2) Mission Planning, and 3) LADO Simulation. The TT&C provides the commanding of the satellite(s), sending and receiving telemetry as well as tracking data. Mission Planning is responsible for the planning and execution of satellite maneuvers during launch and early orbit (LEO), anomaly resolution and disposal activities. The LADO Simulator provides a simulation of telemetry, commanding and selected subsystems functionality for the different block type satellites forming the GPS constellation. It also provides simulation of specified maneuvers and anomalies, as well as ground facilities utilized for the LADO mission.

1.2 Compliance Documentation

The following documents are part of this PWS to the extent identified herein; applicability to the most recent versions unless otherwise specified. In the event a conflict is found between document revisions, the contractor shall seek Government direction. The contractor shall comply with the most current version of the Space and Missile Systems Center Standard Software Development for Space

Systems (SMC-S-012) in the performance of the tasks and duties outlined in this PWS.

Document Title Effective Date

2 SOPS Instruction 10-5 Current Version

AFI 63-131; Modification Program Management 6 Nov 2009

DCID 6/3 Manual 11 December 2003

DoD 5220-22M National Industrial Security

Program Operations Manual

28 Feb 2006

DoDI 8500.01 Cybersecurity 14 March 2014

DoDI 8510.01; Risk Management Framework

(RMF) for DoD Information Technology (IT)

12 March 2014

DoDI 8530.01 Cybersecurity Activities Support to DoD Information Network Operations

7 March 2016

DoD 8570.01-M Information Assurance

Workforce Improvement Program

10 November 2015

GPS Security Classification Guide December 2015

MIL STD 882E; Department of Defense

Standard Practice, System Safety

11 May 2012; Tasks 101, 102, 105, 204, 205, 206, 301, and 303

SMC/GPL OI 63-131 Modification Management and Technical Baseline Control of GPS OCS

28 June 2016

2 SOPS OI Training updates, schedule requests Current Version

2 SOPS MCB Format Presentation products Current Version

Braxton Configuration Management Plan Current Version

SMC Standard SMC-S-001; Systems Engineering

12 July 2010

SMC Standard SMC-S-002; Configuration Management

13 June 2008

SMC Standard SMC-S-003; Quality Systems 13 June 2008

SMC Standard SMC-S-012; Software Development for Space Systems

13 June 2008

SMC Standard SMC-S-019; Program and Subcontractor Management

11 August 2008

SMC Standard SMC-S-021; Technical Reviews & Audits for Systems, Equipment and Computer Software

15 September 2009

2. SCOPE

The Contractor shall support all LADO products that contribute to LADO systems that are both currently in place, and any mission unique systems built into LADO. The software list includes, but is not limited to the following products:

2.1 The contractor shall provide software upgrades, changes, and modifications to the

TT&C, Core Applications, Simulation software and applicable hardware devices.

2.2 LADO Hardware and Software Licenses

2.2.1 The contractor shall supply user licenses for all applicable LADO software, as referenced in PARA 2.

2.2.2 The contractor shall maintain Freeflyer (or equivalent) and Veritas Backup Exec Server licenses and their service agreements, as required. If the above licenses are permitted by the

Government to be replaced with another Government approved software, the contractor shall provide and maintain the replacement licenses and respective maintenance support, as required.

2.2.3 The contractor shall provide software changes and modifications to the TT&C, Core

Applications, Ace Premier Simulation and Software and applicable hardware devices as it relates directly to the KS-252 integration.

2.3 Cryptographic Upgrades

2.3.1 The contractor shall ensure LADO software supports the cryptographic upgrades within the system. This includes integration of the cryptographic equipment into the LADO system.

2.3.2 The contractor shall provide software changes and modifications to the TT&C, Core

Applications, Ace Premier Simulation software and applicable hardware devices as it relates directly to cryptographic integration (including firmware updates).

3. TECHNICAL REQUIREMENTS

3.1 Software Engineering Tasks

3.1.1 The contractor shall write software that requires knowledge in the core product programming language(s) to correct errors, add new launch, anomaly resolution and orbital operations capabilities, and upgrade interfaces to improve performance. The core programming language is C++. Documentation of changes must be made according to the established processes as specified SMC-S-012 and may include the Software User’s Manual

(SUM). (CDRL A001)

3.1.2 The contractor shall complete software builds within agreed upon completion date(s) established during release planning, and integrated into the Global Positioning System (GPS)

Enterprise/Master Schedule. All errors identified shall be documented within the

Government approved database and corrected within the assigned software build phase.

(Service Summary)

3.1.3 The contractor shall prepare all Space and Missile Center Sustainment Programing

Office prioritized (up to 50) Software Change Requests (SCRs) annually, to include a detailed engineering analysis, engineering design, risk assessment, and test methodology. The

Contractor shall maintain, in the government approved database, SCRs throughout the release cycle. The contractor shall design, code and test software modifications.

3.1.4 The contractor shall provide training to the system end users (operators) on new software releases that significantly affect the form or utility of the TT&C, Core Application, and Simulation software at least seven days prior to the Modification Control Board (MCB).

The Contractor shall provide training to the system end users (operators) on general topics in

Telemetry, Tracking, and Commanding (TT&C) and Simulator operations by in classroom briefings or over-the-shoulder activities. (Service Summary)

3.1.5 The contractor shall provide subject matter expert support for TT&C, Core

Application, and Simulation software in support of standalone exercises, and spacecraft readiness rehearsals, and launch and early orbit activities.

The contractor shall install or assist in its installation of licenses on the test bed and operational computers. The contractor shall install licenses within 12 hours at Peterson and

Schriever AFB, and install licenses within 7 business days at Vandenberg AFB.

3.1.6 The contractor shall provide 24/7 on-site support for surge periods or on-call support up to 3 times per year.

3.1.7 The contractor shall ensure the LADO system is supported by the most current operating system mandated by DoD policy.

3.1.7.1 The contractor shall update the TT&C, Core Application, Simulation software as well as the LRU/FEPs hardware as a result of an the Windows 10 operating system upgrade.

3.1.7.2 The contractor shall ensure the LADO system database operates and integrates with all the Windows 10 operating system and software upgrades.

3.1.8 The contractor shall participate in the Decision Review Board (DRB).

3.2 Hardware Tasks

3.2.1 The contractor shall supply LADO hardware/software components and assist in the installation and maintenance of these at the test laboratory at Peterson AFB, Schriever AFB, and at the Alternate Master Control Station (AMCS). The hardware includes:

SIU Black (Simulator Interface Unit- Command)

SIU Red (Simulator Interface Unit-Telemetry)

CCT (Command, Control and Tracking)

CTK (Command, Telemetry and KG Controller)

3.2.2 The contractor

shall maintain LRU/FEPs, to include replacement of defective LRU and FEP. The contractor shall repair or replace the defective units on the operational systems (during real-world or Mission Operations Transfer) within 12 hours at Schriever

AFB and Vandenberg AFB. The contractor shall repair or replace the defective units on the non-operational systems within 5 business days at Peterson AFB, Schriever AFB and

Vandenberg AFB.

3.2.3 The contractor shall provide meeting documentation and participate in the Critical Design

Review (CDR) Board and the Preliminary Design Review (PDR) Board. (CDRL A002)

3.3 Systems Engineering Tasks

3.3.1 The contractor will receive requests to change or modify the way the system operates through Problem Reports (PRs) in the government approved database.

3.3.1.1 The contractor shall analyze system requirements and decompose into the correct subsystem functionality.

3.3.1.2 After the Problem Report Board (PRB) identifies a PR and the Government determines it is necessary to be fixed, the contractor shall prepare an engineering analysis of the reported problem by the date established by the Requirements Screening Panel (RSP).

This analysis includes: the affected requirements, a cost estimate justification, qualification requirements, test plan, and cost attributes. The PRB uses these engineering analysis to determine whether to include this PR in a future software release. If the PR is to be included in a future release, it then becomes a Software Change Request (SCR).

3.3.2 The contractor shall identify candidate PRs/SCRs for inclusion into a software release, and provide an engineering assessment to the 517th.

3.3.3 The contractor shall prepare a design and enter it in the government approved database describing the specific approach for resolving the SCRs associated with a release, and conduct design reviews either through a meeting or email. The 517th GPS Project Director will review the design. This is executed in conformance with SMC-S-012, Software

Development for Space Systems. This task supports the software builds specified in paragraph 3.1.2.

3.3.4 The contractor shall participate in special studies (up to 4 times per year) and provide recommendations to the 517th to improve system performance, reliability, usability, and maintainability. (Service Summary). (CDRL A003)

3.4 Test Engineering Tasks

3.4.1 The contractor shall receive testing tasks according to paragraph 5.8 in SMC-S-

012. The contractor shall perform unit integration and testing to ensure that it works together as intended. The activity of unit integration and testing may require the use of all verification methods (i.e., Inspection (I), Analysis (A), Demonstration (D), and Test (T)).

3.4.1.1 The contractor shall perform unit testing on TT&C, Core Application, and

Simulation software in accordance with SMC-S- 012, Software Development for Space

Systems. This task supports the software builds specified in paragraph 3.1.2.

3.4.1.2 The contractor shall perform integration/regression testing on software changes for each new release, and provide a report. The Contractor shall maintain the software baseline configuration with on-call support for off-hour system deliveries and installations. The contractor shall provide support during normal work hours (8 hours a day/5 days a week 0700-

1530, Mon-Fri). Additionally, the contractor shall provide on-call support for off-hour system deliveries and installations. (Service Summary)

3.4.1.3 The contractor shall conduct pre-delivery integration testing to verify compatibility of software changes with existing software baseline in, accordance with SMC-S-012, Software

Development for Space Systems. This task supports the software builds specified in paragraph 3.1.2. (Service Summary)

3.4.1.4 The contractor shall analyze the test data collected during testing to determine if the specifications and requirements were met in accordance with SMC-S-012, Software

Development for Space Systems. This task supports the software builds specified in paragraph 3.1.2. The contractor shall document all system non-conformances using the project defect tracking process in a government approved database at least one week prior to the PRB meeting.

3.4.1.5 The contractor shall provide the 517th with installation instructions for each delivery on or before the Modification Control Board (MCB) approval to install the software for operational use. (CDRL A004)

3.4.1.6 The contractor shall provide installation and test support to Level 1 at the completion of Level 2 testing. Level 1 performs operational testing on each new release.

3.5 Documentation

3.5.1 The contractor shall incorporate Government initiated AFTO 22/252s annually, republish and distribute accurate and complete technical orders for GPS LADO system.

The contractor shall also maintain tracking spreadsheet in contractor format with all received and approved AFTO 22s and 252s with planned publication dates.

3.5.1.1 The contractor shall provide the government pre-publication reviews of the GPS

LADO Maintenance Technical Order (T.O.) and drawing package at 75% and 90%. The contractor shall follow the GPS/DoD/Mil-Std processes listed in the compliance section of this PWS for interim publication and final publication of TOs (CDRL A005).

3.5.1.2 The contractor shall provide the government a review of the final maintenance

Technical Order and drawing package for 100% completion. (CDRL A005).

3.5.1.3 The contractor shall submit T.O.s in SGML/pdf as prescribed in MIL-STD-

38784, MIL-STD-38807, and T.O.00-5 series unless there are previously incorporated deviations.

3.5.1.4 The contractor shall print and deliver GPS LADO Application T.O.s per requirements in Enhanced Technical Information Management System (ETIMS)/Joint

Computer Aided Acquisition Logistics System (JCALS).

3.5.1.5 The contractor shall upload softcopy of all applicable T.O.s to the Government approved data repository and/or ETIMS.

3.5.1.6 The contractor shall submit all change history on AFTO 22s and any deviations from those forms shall be delivered with T.O. for review. Attaching redlines to the AFTO forms is acceptable.

3.5.1.7 The contractor shall maintain a tracking spreadsheet in contractor format with all received and approved AFTO 22s and 252s with planned publication dates.

3.5.1.8 The contractor shall ensure change history, to include the AFTO 22/252 and any deviations from those forms, will be delivered with TOs for Government review(s).

3.5.2 The contractor shall perform TO numbering requests, revisions, or changes, as requested by the TOMA. The contractor shall perform routine database corrections for

JCALS/ETIMS.

3.5.2.1 The contractor shall ensure 100% accurate data input into JCALS/ETIMS.

3.5.2.2 The contractor shall ensure requests, revisions or changes are addressed within

30 calendar days of notification for database discrepancies and within 7 calendar days of notification for errors.

3.5.2.3 The contractor shall ensure TO number requests are accomplished within 5 calendar days.

3.5.2.4 The contractor shall ensure revisions and changes are accomplished within 2 calendar days of Technical Order Management Agent (TOMA) request.

3.5.3 The contractor shall author/submit AFTO 22/252s to report and correct deficiencies in published TOs or to provide TO updates as a result of hardware or software changes. Each AFTO 22/252 must include all requested changes for that particular maintenance action.

3.5.3.1 The contractor shall ensure AFTO 22/252s are IAW TO 005 series and MIL-STD

38784.

3.5.3.2 The contractor shall ensure Emergency findings are documented and submitted within 24 hours of finding.

3.5.3.3 The contractor shall ensure Routine findings are documented and submitted within 7 calendar days of finding.

3.5.3.4 The contractor shall ensure Urgent findings are documented and submitted within

48 hours of finding.

3.5.4 The contractor shall update and release engineering drawings annually to correct existing errors based on Government, Level 2 or drafter documented changes using

Government approved configuration management process. The engineering drawings may include changes or updates to Vendor Item Control Drawing (VICD), rack elevation, connection diagrams, floor layouts, power and grounding and drawing trees for LADO

(CDRL A006).

3.5.4.1 The contractor shall ensure configuration management of drawings is In

Accordance With (IAW) MIL-HDBK-61, Configuration Management Guidance.

3.5.4.2 The contractor shall ensure change history, to include drawing change requests and any deviations from that form, will be delivered with the drawings for review.

3.5.4.3 The contractor shall ensure drawings updates are made in time to support TO publication. If no TO change is required, the drawing and change request will be delivered for final review within 90 calendar days of receipt of changes, and released within 30 calendar days of receipt of final Government review comments.

3.5.4.4 The contractor shall ensure GPS engineering drawings will be compliant with the most current version of ASME Y14.100, with the exception of the drawing tree, or deviations agreed upon in advance with the Government.

3.5.4.5 The contractor shall ensure there is no more than two (2) technical errors, and no more than two (2) administrative errors per five pages, per drawing during the final drawing review.

3.5.5 The contractor shall evaluate and deliver Contractor Furnished Equipment

Notices (CFEN) with Commercial Off-the-Shelf (COTS) manual data. TO numbering, or incorporation into existing TO, will be at Government direction.

3.5.5.1 If incorporation into existing TO is required, the contractor shall ensure changes are made in time to support TO pre-publication review.

3.5.5.2 The contractor shall complete CFEN evaluation, TO numbering or incorporation in time to meet equipment installation date.

3.5.5.3 The contractor shall deliver the report to the Government equipment specialist via e-mail or hardcopy.

3.5.5.4 The contractor shall evaluate COTS manual for inadequacies and recommend TO numbering or incorporation into existing TO per TO 00-5-1, TO 00-5-3 and MIL-PRF

32216. If incorporation into existing TO is required, changes shall be compliant with AF

TO standards

3.5.6 The contractor shall update the following documentation in support of releases as required by the 517th:

Software User Manual (SUM)

Release Installation Instructions

TOs/Drawings

Work Cards

Technical Reports

Cybersecurity Artifacts

3.6 Cross Domain Solution

3.6.1 The contractor shall provide software and hardware support for the Government approved cross-domain solution. This includes software update and modification in order to integrate the current LADO TT&C, Core Applications, Ace Premier Simulation software with the cross-domain solution.

3.6.2 The contractor shall follow the same documentation requirements listed in section 3.5

3.6.3 The contractor shall follow the same software engineering tasks listed in 3.1

3.6.4 The contractor shall follow the same systems engineering tasks listed in section 3.3

3.6.5 The contractor shall follow the same test engineering tasks listed in section 3.4

3.6.6 The contractor shall support security assessment, formal factory acceptance testing, and functional demonstrations of the CDS.

3.6.7 The contractor shall update, as needed, the cybersecurity artifacts for the Certification

Test and Evaluation in support of the CDS accreditation effort. This documentation is a mix of product documentation and Certification Test & Evaluation (CT&E ) specific generated documentation which includes, but is not limited to the following:

a. CDS Technology Summary

b. Security Concept of Operations

c. Security Controls Traceability Matrix (SCTM)

d. Functional Specifications

e. User/Administrative/Installation Guides

f. Independent Verification and Validation (IV&V) Test Procedures and Results or

Government Acceptance Testing and results

g. High-Level Design

h. Low-Level Design

i. Configuration Management Plan

j. Filter Specifications-Data Validation Guide

k. System Security Plan

l. Developer-provided test procedures for all security controls identified in the SAGF as applicable to lab-based testing

m. Vendor Self-Assessment (VSA)

3.6.8 The contractor shall provide final documentation and final cybersecurity artifacts required to complete the Risk Management Framework certification for the LADO system.

3.6.9 The contractor shall support test events, technical meetings, and programmatic discussions required to support the CDS CT&E, including the events and activities outlined in the CDS Security Assessment Process Guide.

3.6.10 The contractor shall support onsite setup and training of the CDS for the CT&E independent lab evaluation, the Security Assessment Out brief (SAO) and the meetings/documentation/testing for the operational accreditation of the CDS.

3.6.11 The contractor shall support test events, technical meetings, and programmatic discussions required to support the CDS CT&E, including the events and activities outlined in the CDS Security Assessment Process Guide.

3.6.12 The contractor shall provide support, technical assistance and any additional artifacts for the CDS Security, Test and Evaluation (ST&E).

3.7 Database Administrator (DBA)

3.7.1 The contractor shall provide analysis, diagnostics, and resolution assistance to LADO

GPS Government LADO Level 1 and Level 2 support personnel as required when

Government personnel determine abnormalities indicate a database issue has been encountered.

3.7.2 The contractor shall provide all documentation and installation instructions/procedures

(to include all software scripts or installation software) necessary to deliver and make functional any LADO database upgrades.

3.7.3 The contractor shall ensure all DoD Security Technical Implementation Guides

(STiGs) concerning Oracle Security are adhered to, and each Oracle patch update delivery is installed. That each Oracle patch, or STiG compliance modification is forwarded to the 517th

L1/L2 personnel with full installation documentation and procedures.

3.7.4 The contractor shall develop and deliver procedures, (to include any scripts, batch files, or executables), to preserve legacy operational (L1)/ Test (L2) data upon the implementation of any LADO driven database modification. This data transferal will be limited to only the immediate prior delivered version (CDRL A007).

3.7.5 The contractor shall provide to the Level 1/Level 2 Government support personnel documentation on all delivered Oracle procedures developed by Braxton on the function, purpose, and interdependencies that are intended as normal or maintenance scripts.

3.7.6 The contractor shall provide to the Government a full data dictionary, and data model diagram of the existing LADO database. This diagram will show structure and table relationships as well as a description of the purpose/intent of each table.

3.8 Reserved

3.9 Project Management

3.9.1 The contractor shall provide project management support for TT&C, Core

Application, and Simulation software for the Software Engineering, Systems Engineering, Test Engineering, Documentation and Database Management tasks. The following are tasks included: Staff tasking and performance management, developing and maintaining an operating budget, Developing and maintaining a project schedule, and providing status reporting to customer and upper management. Identifying and managing project risk items.

Status is provided during weekly status meetings and in monthly status reports.

3.9.2 The contractor shall provide task status during the weekly status meetings and included in the monthly status reports. The weekly status meetings and the monthly status reports shall include, but not limited, to:

a) Current task status

b) Planned task completion date

c) Actual task completion date

d) Estimated hours to complete each task in the software release

e) Actual hours to complete each task in the software release

f) Issues and concerns regarding software release

g) Explanation for late tasks

3.10 Reports and Meetings

3.10.1 Weekly Status Meeting

3.10.1.1 The contractor shall provide status to the 517th during weekly team meetings.

Weekly status must include the Contractor’s performance in comparison to the planned delivery schedule for each product delivery in a software release. This comparison shall include, but not limited to, status of actual percent (%) complete, planned percent complete as of the reporting date, and issues/concerns with associated recommendations (any risks that would cause a change in schedule or cost, associated recommendations to mitigate issue). The weekly status reporting will include a task completion list detailing the status of development tasks and test execution activities as well as the high level status of project completion. If schedules are behind, an explanation must be included.

3.10.1.2 The contractor shall also identify and report any official/unofficial problem reports that are written and corrected during the software development cycle. This includes problem reports documented during peer review and test results.

3.10.2 Monthly Status Report

3.10.2.1 The contractor shall provide a Monthly Status Report to 517th GPS Project Director and the Contract Officer Representative (COR) by the 10th day of the following month.

Reports will show the status and progress of the project(s) being worked and significant

Contractor achievements or roadblocks. The report will identify breakdown of government funds usage for the month and remaining project funds. All data deliverables will be referenced in the monthly status reports. (CDRL A008)

3.10.2.2 The contractor’s monthly status report shall include software release development/testing objectives and thresholds (e.g. planned completion and actual completion) in regards to meeting the projected software release delivery date to the 517th.

3.10.3 Meetings

3.10.3.1 The contractor shall participate in meetings when changes to the hardware/software baseline are required or as t he events schedule indicates. These meetings include: (Service Summary)

Weekly Status Meetings

Problem Report Board (PRB)

Requirements Screening Panel (RSP)

Critical Design Review

Preliminary Design Review

Modification Control Board

Engineering Review Board (ERB)

Release Planning

Rehearsal Support

Program Management Review

Technical Interchange Meetings

4. SERVICES SUMMARY

Performance Objective PWS

Paragraph

Performance Threshold

The contractor shall write software and write the

SUM.

3.1.1 72 hours after software delivery

(CDRL A001)

The contractor shall complete software builds within agreed upon completion date

3.1.2 By the dates established in the scheduling

meeting.

The contractor shall prepare all government prioritized up to 50

Software Change Requests

(SCRs) annually

3.1.3 Up to 50 SCRs

The contractor shall provide training to the system end users

(operators) on new software releases.

3.1.4 At least seven days prior to Modification

Control Board meeting.

The contractor shall supply licenses for all applicable LADO hardware and install or assist the installation of hardware at the test laboratory at Peterson AFB, Schriever AFB, and/or Vandenberg

AFB

3.1.5 Install licenses within 12 hours at Peterson

and Schriever AFB, and install hardware within 7 business days at Vandenberg

AFB.

The contractor shall provide 24/7 on-site support for surge periods or on-call support up to 3 times per year

3.1.6 Up to 3 times/yr

The contractor shall participate in the Decision Review Board

3.1.8 100% participation required.

The contractor shall perform hardware problem diagnostics, repair and/or replacement when problems arise with their proprietary equipment at the test laboratory at Peterson AFB, Schriever AFB, and Vandenberg

AFB

3.2.2 The contractor

shall maintain LRU/FEPs, to include replacement of defective LRU and FEP. The contractor shall repair or replace the defective units on the operational systems (during real-world or

Mission Operations Transfer) within 12 hours at Schriever AFB and Vandenberg

AFB. The contractor shall repair or replace the defective units on the non-operational systems within 5 business days at Peterson AFB, Schriever AFB and

Vandenberg AFB.

The contractor shall provide meeting documentation and participate in the Critical

Design Review (CDR) Board and the Preliminary Design

Review (PDR) Board. (CDRL

A002)

3.2.3 Provide CDR and PDR meeting

documentation 48 hours in advance prior to meeting.

Contractor shall prepare an engineering analyses of the reported PR that the PRB has identified

3.3.1.2 By the date established by the

Requirements Screening Panel.

The contractor shall prepare and enter design for review in the government approved database describing the specific approach for resolving the SCRs associated with a release, and conduct design reviews either through a meeting or email.

3.3.3 SMC-S-012, Software Development

for Space Systems. This task supports the software builds specified in paragraph 3.1.2

The contractor shall participate in special studies and provide recommendations to the 517th to improve system performance, reliability, usability, and maintainability.

3.3.4 Perform up to four special studies per

year. (CDRL A003)

The contractor shall perform unit testing on TT&C, Core

Applications, and Simulation software.

3.4.1.1 SMC-S-012, Software Development

for Space Systems. This task supports the software builds specified in paragraph 3.1.2.

The Contractor shall maintain the software baseline configuration.

3.4.1.2 Provide support during normal work hours

8 hours a day/5 days a week (0700-1530, Mon-Fri). Additionally provide on-call support for off-hour system deliveries and installations.

The contractor shall conduct pre-delivery integration testing to verify compatibility of software changes with existing software baseline.

3.4.1.3

SMC-S-012, Software Development for Space Systems. This task supports the software builds specified in paragraph 3.1.2.

The contractor shall analyze the test data collected during testing to determine if the specifications and requirements were met.

3.4.1.4

SMC-S-012, Software Development for Space Systems. This task supports the software builds specified in paragraph 3.1.2.

The contractor shall document all system non-conformances using the project defect tracking process in a government approved database.

3.4.1.4 At least one week prior to the Problem Report Board meeting.

The contractor shall provide the 517th with installation instructions for each delivery.

3.4.1.5 On or before MCB approval to install

the software for operational use.

(CDRL A004)

The contractor shall submit 75%, 90% and 100% Documentation packages per agreed upon schedule for each software release.

3.5.1.1/3.5.1.2 Complete and accurate with no more than 15 errors identified by the Government each review (e.g.

75%, 90%, 100%).

ERRORS are as follows; inaccurate data, non-standard formatting, incompatibility with approved viewers, USAF compliant software or 517th processes.

Corrected pages will be provided at no additional cost/fee.

The contractor shall provide a final engineering drawing package.

3.5.4/3.5.4.4 The contractor shall ensure there is no more than two (2) technical errors, and no more than two (2) administrative errors per five pages, per drawing during the final drawing review. (CDRL A006).

Provide a Monthly Status Report to the authorized 517th and/or government representative

3.10.2 By the 10th calendar day of the

following month (CDRL A008)

The contractor shall participate in meetings when changes to the hardware/software baseline are required.

3.10.3.1 Provide technical support for at least 70

meetings per year.

The contractor shall have established a Quality Control

Program (QCP)

6.9.1 60 Days after start of contract. (CDRL

A009)

The contractor shall perform configuration management to include the identification, control, accounting and auditing of the functional and physical characteristics of

LADO systems and the maintenance of the systems documentation.

6.11.2 Compliant or Non-compliant

5. PLACE / PERIOD OF PERFORMANCE & CDRLs

5.1 Period of Performance

5.1.1 The period of performance of this task shall be a 5 month base period with a 7 month option, following contract award.

5.1.2 Primary Performance Locations

Primary Place of Performance

Schriever AFB

Peterson AFB

Vandenberg AFB

Braxton Contractor Facility

5.2 CDRLs

PWS

Paragraph

CDRL

Number

Description Delivery

Dates

Government

Approval

Data Rights

3.1.1 A001 Software

User’s Manual

As Req Approval Unlimited

3.2.3 A002 Meeting

Documentation

(CDR/PDR)

As Req Approval Unlimited

3.3.4 A003 Special Studies

Report

As Req Approval Unlimited

3.4.1.5 A004 Installation

Instructions

As Req Approval Unlimited

3.5.1.1, 3.5.1.2

A005

Approved

Technical

Order

As Req Approval Unlimited

3.5.4 A006 Drawing

Package

As Req Approval Unlimited

3.9.4 A007 Legacy Data As Req Approval Unlimited

3.11.2.1 A008 Monthly Status

Report

Monthly Information

Only

Unlimited

6.9.1 A009 Quality Control

plan

60 Days after start of contract

Approval Unlimited

6. CONTRACT ADMINISTRATION

6.1.1 The contractor shall ensure professional and technically qualified personnel to perform assigned tasking. The Contractor shall provide total task management and supervise contractor personnel. The Contractor’s Technical Lead shall serve as the primary point of contact for all technical aspects of the required work. This person shall also be a prime provider of the required technical services. No personal services shall be performed. The Contractor shall have current working knowledge/experience of the GPS LADO system to include TT&C development and testing procedures.

6.2 Government Furnished Property (GFP) at Peterson Air Force Base

6.2.1 GFP Listed in Appendix B will be provided under this contract. Said

GFP will be transferred to the new contract.

6.2.2 Access to Government owned equipment located at Peterson Air Force Base shall be provided to the contractor. Government furnished items will include access to unclassified Government instructions, criteria, standards, and guidelines relating to facilities and utility engineering.

6.2.3 All government owned equipment must be safeguarded by the contractor.

Government owned equipment shall remain in possession of the Government and is only available for contractor use during normal working hours, as specified in paragraph 5.13.1. The exception to this is for an emergency fix (E-Fix).

6.3 Disclosure of Information:

6.3.1 Information made available to the contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the CO. The contractor agrees to assume responsibility for protecting the confidentiality of Government records, which are not public information. Each contractor or employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

6.4 Identification of Non-Disclosure Requirements

6.4.1 Completion of non-disclosure statements will be required by on-site contractor personnel to ensure information that is considered sensitive or proprietary is not compromised.

6.5 Conflicts of Interest

6.5.1 The contractor shall include in its staffing plan any actual or potential conflicts of interest that may arise under the performance of its contract. Also, the contractor shall immediately notify the CO, if during the performance of the contract, it becomes aware of any circumstance where its personnel or sub- contractors may have a conflict of interest. In such circumstances, the contractor may propose a conflict of interest mitigation plan offering suitable processes for alleviating situations that may lead to conflict of interest situations or the appearance of conflict of interest. The contractor is also cautioned that there may be instances where actions taken under this contract may preclude them from proposing on other contracts.

6.6 Problem Resolution

6.6.1 The contractor shall bring problems, or potential issues, affecting performance to the attention of the COR and the 517th GPS Project Director as soon as possible. Verbal reports will be followed up with written reports when directed. This notification shall not relieve the contractor of its responsibility to correct problems for which they are responsible. The contractor will work cooperatively with the COR and/or CO to resolve issues as they arise

6.7 Security Requirements

6.7.1 517th GPS Project Director will assist contractor in processing the necessary DoD forms to obtain base or area badges for access to Government facilities.

6.7.2 DD Form 254: Overarching security requirements and Contractor access to classified information shall be as specified in the basic DD Form 254, which will be further identified in the contract DD Form 254, tailored as required. All Contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable

National Agency Check Local Agency Checks and Credit Check (NACLC).

6.7.3 Visitor Group Security Agreement: The Contractor shall sign a Contractor Visitor Group

Security Agreement to protect classified information involved in performance under this contract. The Agreement will outline responsibilities in the following areas: Contractor security supervision; Standard Practice Procedures; access, accountability, storage, and transmission of classified material; marking requirements; security education; personnel security clearances; reports; security checks; security guidance; emergency protection;

protection of Government resources; DD Forms 254; periodic security reviews; and other responsibilities, as required.

6.7.4 The Contractor shall be required to comply with local procedures for handling classified materials in the following facilities where classified information is processed or stored:

Facility Location Work Facility Security

Classification

MCS Building 400, MOD 11 and

17, Schriever AFB CO

LADO Sustainment SECRET

AMCS Vandenberg AFB CA LADO Sustainment SECRET

6.7.5 If required, the contractor may contact the government security manager for a Common

Access Card (CAC). The Government security manager will direct contractor to appropriate location and registration processes.

6.7.6 If needed, the contractor shall also obtain a Building ID and access card from the appropriate government security manager.

6.7.7 When the period of performance is complete and/or Contractor leaves work, on this project, they shall have 5 working days to terminate all their network user account(s) and to return all access cards and base identification badges.

6.7.8 The 517 SMXS or SMC/SL shall provide special base access, computer security training and security training to the contractor employees by the appropriate government agency as needed. This training must be preapproved by the 517 SMXS project director.

Special base access, computer security training and security training will be provided to the contractor employees by the appropriate

6.7.9 Individuals performing work under this contract shall comply with applicable program security requirements as stated below. This contract will support the following levels of security: Unclassified and Secret (S).

6.7.10 All personnel shall have a Secret clearance or higher and be United States citizens.

Contractors shall obtain security clearances prior to performing services under the contract.

The contractor shall comply with the Contract Security Classification Specification (DD Form

254) for this contract which encompass all security requirements. All personnel shall comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and AFI 10-701, Operations Security. In accordance with DoD

5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable National Agency Check plus Written Inquiries

(NACI).

6.7.11 The contractor shall obtaining the appropriate (PSI) for its employees prior to assigning them to work this contract. For the contract PSI cost shall be the responsibility of the contractor. Acquisition planning must consider Anti-Terrorism (AT) measures when the effort to be contracted could affect the security of operating forces (particularly in-transit forces), information systems and communications systems IAW DoD Instructions 2000.16 Anti-

Terrorism Standards.

6.8 OPSEC Requirements

6.8.1 The contractor shall comply with the OPSEC requirements of the Government facilities. Access to the Peterson Network is required for the period of performance.

6.8.2 If a government provided e-mail account is required the contractor will take

Information Assurance Awareness Training prior to receiving access to that account, and annually thereafter.

6.8.3 Contractors are required to report in a timely manner (3 days AFI 33-202) to the appropriate security manager & Functional System Administrator, personnel who no longer need personal computer, network or Automated Information System (AIS) access.

6.9 Quality Control

6.9.1 The contractor shall have established a Quality Control Program to ensure the requirements of this contract are provided as specified. The contractor’s quality management program shall comply with the minimum quality management systems elements specified in the American National Standards Institute (ANSI), American Standards Organization (ASO), and International Standard Organization (ISO) family of standards. The contractor shall provide a Quality Control Plan (QCP) detailing the contractor’s quality system, including management commitment to quality, policy and practices. (CDRL A009)

6.10 Quality Assurance

6.10.1 The Contracting Officer Representative is the authorized government representative(s) who will perform assessments of the contractor’s performance. Subsequent to contract award, the identity of the COR(s), with a letter defining duties and authority will be promptly furnished to the contractor.

6.10.2 The COR(s) or alternate(s) will inform the task manager in person when discrepancies occur and will request corrective action. The COR(s) or alternate(s) will make a notation of the discrepancy on the assessment checklist with the date and time the discrepancy was noted and will request the task manager (or authorized representative) to initial the entry on the checklist.

6.10.3 Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contracting Officer, not the COR(s).

6.10.4 The services to be performed by the contractor during the period of this contract are at all times and places subject to review by the CO or designated government representative.

6.10.5 The 517 SMXS will periodically evaluate the contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The Government representative will evaluate the contractor’s performance through inspections and receipt of complaints from base personnel.

6.10.6 The 517 SMXS may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints.

6.11 Configuration Management

6.11.1 The contractor shall allow the Government access to all software/hardware engineering processes and procedures needed to perform the work on this contract.

6.11.2 The contractor shall perform configuration management to include the identification, control, accounting and auditing of the functional and physical characteristics of LADO systems and the maintenance of the systems documentation.

6.11.3 Provide technical support to 517 SMXS personnel during reviews and system safety related meetings at Peterson AFB. Assess current system configuration when reviewing documents, attending reviews, planning meetings or working groups or any other meeting/council and relay significant findings to the Government.

6.12 Hours of Operation

6.12.1 Accomplishment of the results contained in this PWS requires work at Peterson AFB, Schriever AFB and at various contractor and Government facilities in the continental United

States. Normal workdays are Monday through Friday, Government workers typically work 80 hours per two weeks. Flextime workers start not earlier than 0600 and not later than 0900.

Core hours of work are from 0900 to 1500 daily. All employees are expected to be available during core hours. Contractors are not authorized compensation for attendance at base functions unless directly related to project assignments as authorized by the project manager.

6.12.2 Unless otherwise required by the Government, the contractor shall not have access to

Government facilities on the following federal holidays: New Year’s Day, Martin Luther

King’s Birthday, President’s Day, Memorial Day, Independence Day, Labor Day, Columbus

Day, Veterans’ Day, Thanksgiving Day, and Christmas Day.

6.12.2.1 If the holiday falls on Sunday, it is observed on Monday. If the holiday falls on

Saturday, it is observed on Friday.

6.12.3 In addition to these days designated as holidays, the Government observes the following days: Any day designated by federal statute, any day designated by executive order, any day designated by a President of the United States proclamation.

6.13 Travel / Temporary Duty (TDY)

6.13.1 Travel within El Paso County including other contractor’s facilities, Schriever Air

Force Base, and Petersen Air Force base, will be considered the local area.

6.13.2 No Government reimbursement will be given for travel within the local area.

6.13.3 Travel to other government facilities, or other facilities outside the local area, shall be pre-approved by the Contract Officer. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234 and FAR 31.205-46, Travel Costs.

6.14 Safety

6.14.1 The contract must comply with all security, safety and health rules of the installation to ensure protection of personnel and property. See Appendix C.

6.14.2 The Contractor shall provide their OSHA 300 information from their DART submission to the CO/COR by 15 January of each year. The contractor shall also email a copy to OO-

ALC.OMO.VPPCTRTCIRDART@us.af.mil. The Government will use this information as a part of the installation's annual OSHA VPP self-evaluation report.

6.15 Cybersecurity/Software Assurance

6.15.1 The contractor shall provide cybersecurity support to the Government sustainment cybersecurity team for continued Assessment and Authorization of all LADO systems (MCS, AMCS, LADO Lab) IAW Department of Defense current cybersecurity guidance.

6.15.2 In coordination with the Government, the contractor shall design, develop and implement secure applications and configurations through applying applicable DoD STIGs, checklists, vendor security guidance, industry best practices, and applicable vendor product security patches. The contractor shall ensure applications are in compliance with DoDI

8500.01 Cybersecurity (current version) and DODI 8551.1 Ports, Protocols, and Services

Management (PPSM) (current version) and free of all of the Common Weakness

Enumeration/System Administration, Networking, and Security Institute (CWE/SANS). The contractor shall leverage, to the maximum extent possible, automated tools to identify and remediate vulnerabilities or weaknesses in the application design/coding, such as those described in the CWE/SANS TOP 25 Most Dangerous Software Errors http://www.sans.org/top25-software-errors/.

6.15.3 The contractor shall assist the Government cybersecurity personnel with the following activities related to the contractor’s hardware/software:

a. Provide required cybersecurity artifacts for all assigned cybersecurity controls for inclusion in the Government assessment and authorization packages for all LADO systems.

b. Provide support (e.g., system administration, database administration, data analysis) to Government cybersecurity team for successful completion of Security

Test and Evaluations (ST&Es).

c. Perform network vulnerability scans in support of Government validation checks annually.

d. This support requires qualified and certified personnel (IAW DOD Directive

8140.01,) for both IA and computing environments.

6.15.4 This support requires qualified and certified personnel (IAW DOD Directive 8140.01).

6.16 The contractor shall provide support to assure software functions as intended and is free of vulnerabilities, either intentionally or unintentionally designed or inserted as part of the software.