DD254.pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Performance-Based Work Statement (PWS)

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

U.S AIR FORCE

309 SWEG

8/5/2025

TABLE OF CONTENTS

i

DESCRIPTION OF SERVICES

This Performance-Based Work Statement (PWS) outlines the tasks and duties required of the contractor to support the Air Force Software Directorate (AFSC/SW) 517 Software Engineering Squadron (517 SWES). 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. The period of performance of this contract shall be a 12-month base period with one (1) option year and a final six (6) month option to extend.

Primary Place of Performance

Schriever SFB, Colorado

Peterson SFB, Colorado

Vandenberg SFB, Colorado

Contractor Facility

Table 1: Primary Performance Locations

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 Fair, 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 Operational Control Segment (OCS) for operational orbit support.

LADO consists of three major functions: 1) Telemetry, Tracking and Commanding (TT&C), 2) Mission Planning and Orbital Analysis (MPOA), and 3) LADO Simulation. The TT&C provides the commanding of the satellite(s), sending and receiving telemetry as well as tracking data. The MPOA 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

There are no additional compliance requirements outside of the basic IDIQ PWS for this effort.

SCOPE

The Contractor shall support 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:

TT&C and Scheduling

Core Application Bundle

Front End Devices and Hardware

· AceCP

· AceVS

· AceWLS

· AceTWS

· AceCPB

· AceDBE

· AceMenu

· AceTS

· AceAdmin

· AceRM

· AceFCM

· AceCCT

· AceCTK

· AceSIU-Black

· AceSIU-Red

AceADE

· Orbit Determination

Simulation Software

Front End Devices

· AceSIM

· IIR

· IIF and ground control segment interface to STARSim (IIF flight code)

· AceSIU

· AceTWG

· AceKS252

Table 2: LADO AcePremier Applications and Hardware

LADO Hardware and Software Licenses

The contractor shall supply user licenses for all applicable LADO software, as referenced in Table 2. The contractor shall provide upgrades, changes, and modifications to the TT&C, Core Applications, Simulations software and applicable hardware devices.

The contractor shall maintain Freeflyer (or equivalent), Everfox, 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.

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.

The contractor shall maintain the hardware and software necessary for the operation of the unclassified and classified LADO development environments as referenced in PARA 2.

The contractor shall maintain the communication between the classified and unclassified development environments using Everfox High Speed Guard (HSG) software for non-satellite commands and telemetry

The contractor shall maintain the communication between the classified and unclassified development environments using KS-252 cryptography equipment for satellite commands and telemetry

The contractor shall maintain at least two strings of equipment that can simulate satellite communication. A string of equipment is a complete hardware/software system that can simulate the LADO system to ensure the LADO software can successfully simulate a satellite contact with simulated satellite commands, telemetry, and ground commands. This includes Front-End Processors (CCT, CTK, SIUA, SIUB), workstations, KS-252 cryptography, and HSGs. Additionally, a string includes all necessary support hardware including, but not limited to, domain controller servers and ethernet switches. This excludes data aggregators and data TAPs.

The contractor shall support licenses necessary for an AceADE Orbit Determination standalone capability if the government determines it necessary.

Cryptographic Upgrades

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

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).

BASIC SERVICES

Software Engineering Tasks

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 shall be made according to the established processes as specified SMC-S-012 and may include the Software User’s Manual (SUM).

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. (CDRL A/B/C 015)

The contractor shall deliver to the Government a Software Development Plan in order to provide the Government insight into the processes to be followed for software development as well as cybersecurity/software assurance (CDRL A/B/C A012).

The contractor shall prepare all Mission Delta 31 (MD31)/ 31 Sustainment Squadron (31 STS) Program Office prioritized (up to 5) GitLab Issues (hereafter called Issue(s)) annually only on Emergency or Urgent Issues, to include a detailed engineering analysis, engineering design, risk assessment, and test methodology. The Contractor shall maintain, in the government approved database, Issues throughout the release cycle. The contractor shall design, code and test software modifications. (CDRL A/B/C 016)

The contractor shall provide subject matter expert support for TT&C, Core Application, and Ace Premier 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 SFB, and install licenses within 7 business days at Vandenberg SFB.

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

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

The contractor shall provide information for and participate in the Decision Review Board (DRB) by being present and answer questions. Contractor shall participate as requested by Government Program Manager. CDRL (A/B/C 0014)

Hardware Tasks

The contractor shall supply LADO hardware/software components and assist in the installation and maintenance of these at the test laboratory at Peterson SFB, Master Control Station (MCS) at Schriever SFB, and the Alternate Master Control Station (AMCS) at Vandenberg SFB. 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)

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 SFB and Vandenberg SFB. The contractor shall repair or replace the defective units on the non-operational systems within 5 business days at Peterson SFB, Schriever SFB and Vandenberg SFB.

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 A/B/C001)

Systems Engineering Tasks

The contractor will receive requests to change or modify the way the system operates through Issue(s) in the government approved database only on Emergency or Urgent Issues.

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

After the Government identifies an Emergency or Urgent Issue 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 in concurrence with the Government. This analysis includes: the affected requirements, a cost estimate justification, qualification requirements, test plan, and cost attributes. The Release Content Meeting (RCM) uses these engineering analyses to determine whether to include this Issue in a future software release.

The contractor shall identify candidate Emergency or Urgent Issues for inclusion into a software release and provide an engineering assessment to the 517th.

The contractor shall prepare a design and enter it in the government approved database describing the specific approach for resolving the Issues 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.

Test Engineering Tasks

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)).

The contractor shall perform unit testing on TT&C, Core Application, and AcePremier 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.

The Contractor shall maintain the software baseline configuration with emergency on-call support for off-hour system deliveries and installations. The contractor shall provide emergency support during normal work hours (8 hours a day/5 days a week 0700-1530, Mon-Fri). Additionally, the contractor shall provide emergency 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 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 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.

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.

The contractor shall provide test procedures for an Issue fixed as part of a release (CDRL A/B/C 011)

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.

Cybersecurity/Software Assurance

Personnel with privileged access to Government controlled systems shall be qualified and certified personnel IAW DOD 8570.01-M.

The contractor shall ensure the test baseline mirrors the same baseline or greater (Government approved) to the baseline of the LADO operational system in regards to cybersecurity COTS patches and hardware configurations. In the instance, the test baseline is different than the operational system, the contractor shall update their baseline per Government direction and within mutually agreed upon timeline. Note: As required, the Government will provide the contractor a secure baseline for the development baseline.

The contractor shall provide required artifacts for inclusion in the Government assessment and authorization packages for all LADO systems. This includes, but is not limited to, engineering documents, data flows, network drawings, schematics reports and ports, protocols and services.

The contractor shall deliver to the Government a Security Test Plan outlining the security objectives for a set of security tests to be performed on the LADO Software (CDRL A/B/C A010).

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 submit a Software Quality Assurance Analysis (CDRL A/B/C A004) containing how static analysis is used within the contractor’s development lifecycle in writing and in a diagrammatic form for illustrative purposes. Included in this analysis, the contractor shall develop and deliver mission criticality analysis(-es); vulnerability assessment(s); risk evaluation(s); and identification and counter measurement implementation(s) with each release based on the results of the static analysis tool. The contractor shall identify Mission-Critical findings of which would result in either CAT I or CAT

II categorization (See definitions below).

CAT I: Any vulnerability, the exploitation of which will directly and immediately result in loss of Confidentiality, Availability, or Integrity.

CAT II: Any vulnerability, the exploitation of which has a potential to result in loss of Confidentiality, Availability, or Integrity.

CAT III: Any vulnerability, the existence of which degrades measures to protect against loss of Confidentiality, Availability, or Integrity.

For each CAT I and CAT II Mission-Critical finding identified by the contractor in the criticality analysis, the contractor shall identify the associated logic-bearing system components (e.g. hardware, firmware, and software) that implement, protect, or introduce vulnerability, to that function (thereafter referred to collectively as the “critical components”). The contractor shall utilize an industry standard static tool for the respective LADO software language that identifies the top 25 Common Weakness Enumeration/System Administration, Networking, and Security Institute (CWE/SANS) according to the following table:

Table 3. Example Software Static Analysis Tool

The contractor shall provide support to assure software functions as intended and vulnerabilities, either intentionally or unintentionally designed or inserted as part of the software are minimized per agreed upon 517th & MD 31/31 STS processes. Utilizing current government policy and/or operating procedures the contractor may be required to assist in the investigation and application of risk mitigation procedures and to exploit vulnerabilities at the system and sub- system level. Activities include, but are not limited to, improvements in software assurance through the development of tools and techniques; strengthening software partitioning and modularity capabilities; and theoretical and practical application of enhanced vulnerability discovery.

The contractor shall demonstrate they have visibility into its supply chain for critical components, understand how supply chain risk can be introduced through those components, and has implemented or plans to implement countermeasures to mitigate such risks. The contractor shall plan for and implement countermeasures that mitigate the risk of foreign intelligence or foreign influence, technology exploitation, supply chain and battlefield threats and vulnerabilities that result in CAT I and CAT II protection failures of the system

Prior to each release delivery, the contractor shall conduct code signing (or equivalent action such as hashing) to their LADO COTS software development product in order to ensure software code integrity. COTS Software development product includes software and firmware version updates, patches, service packs, device drivers, and basic input output system (BIOS) updates. The contractor shall provide confirmation that code signing or equivalent action was completed for that particular release as a part of the release documentation delivered to the Government.

TEMPEST

The Contractor shall reference AFSSI-7702 and AFMAN 33-214 volumes 1 and 2 to meet or exceed EMSEC/TEMPEST information assurance requirements for the following:

Equipment utilized within the lab must meet or exceed EMSEC/TEMPEST information assurance requirements.

Equipment must be installed following EMSEC/TEMPEST requirements.

Equipment must maintain correct distance if there are classified and unclassified components within the same proximity. This includes walls which do not meet EMSEC/TEMPEST requirements for separation of space.

Contractor personnel must meet information assurance requirements when performing duties and responsibilities.

The Contractor shall implement an EMSEC/TEMPEST program which prevents EMSEC/TEMPEST violations.

The Contractor shall implement countermeasures to prevent EMSEC/TEMPEST violations.

The Contractor shall allow the Government, as part of its inspection and acceptance, to conduct an EMSEC/TEMPEST inspection or any additional tests to ensure that information technology delivered under this contract satisfies the information assurance standards specified.

The Contractor shall allow the Government to conduct periodic EMSEC/TEMPEST inspections throughout the contract.

The Contractor shall meet all EMSEC/TEMPEST requirements for an Authorization to Operate (ATO).

The Contractor shall correct any EMSEC/TEMPEST deficiencies immediately or within 3 business days after providing the Government a memo with justification as to why deficiencies could not be corrected immediately.

Documentation

The contractor shall support the Government (517 SWES) in creating 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.

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

Software User Manual (Redlined version) (CDRL A/B/C 014)

Release Installation Instructions

TOs/Drawings (Redlined version)

Technical Reports (CDRL A/B/C 009)

Cybersecurity Artifacts

Test Procedures (CDRL A/B/C 011)

Software Development Plan (CDRL A/B/C 012)

Database Design Description (CDRL A/B/C 013)

Database Administration

The contractor shall provide all documentation and installation instructions/procedures (to include all software scripts) necessary to deliver and make functional any SQL LADO database changes. (CDRL A/B/C 013)

The contractor shall provide project management support for TT&C, Core Application, and Ace Premier Simulation software for the Software Engineering, Systems Engineering, Test Engineering, Documentation and Database Management tasks. The Contractor shall complete the following tasks: 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, and providing status during weekly status meetings and in monthly status reports.

The contractor shall provide task status during the weekly status meetings only when working on Emergency or Urgent Issues and include them in the monthly status reports. The weekly status meetings and the monthly status reports shall include, but not limited, to:

Current task status

Planned task completion date

Actual task completion date

Estimated hours to complete each task in the software release

Actual hours to complete each task in the software release

Issues and concerns regarding software release

Explanation for late tasks

Reports and Meetings

Weekly Status Meeting only when working on Emergency or Urgent Issues

The contractor shall provide status to the 517th during weekly team meetings. Weekly status shall 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 is 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 shall be included.

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.

Monthly Status Report

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 shall show the status and progress of the project(s) being worked and significant Contractor achievements or roadblocks. The report shall 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 A/B/C 001).

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.

Meetings

The contractor shall participate in meetings when changes to the hardware/software baseline are required or as the events schedule indicates. These meetings include:

· Weekly Status Meetings only when working on Emergency or Urgent Issues

· Release Content Meeting (RCM)

· Critical Design Review

· Preliminary Design Review

· Modification Control Board

· Engineering Review Board (ERB)

· Release Planning

· Rehearsal Support

· Program Management Review

· Technical Interchange Meetings

SERVICE SUMMARY

Service Summary Number

Performance Requirement

Performance Threshold

Method of Surveillance

Frequency

A001

3.7.2.1

Contractor's Progress, Status and Management Report

Due by the 10th calendar day of each month

Random sampling, 100% inspection, periodic sampling

Monthly

3.3.4

Government Furnished Property Inventory Report

Due 120 days ARO, and any required updates to GFP

100% inspection

Random

6.2

Quality Assurance Program Plan

Due 14 days ARO

100% inspection

Annual

Air Force -Technical Manual Contract Requirements (TMCR)

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Manuals, Technical - Time Compliance Technical Orders

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Product Drawing And Associated List

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

COTS Manuals

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Technical Reports-Study/Services

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Security Test Plan

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Test Procedure

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Software Development Plan

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Database Design Description

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Software User Manual

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Computer Software Product End Item

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Software Test Plan

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

Configuration Management Plan

Due 90 days ARO, and as required from the Government requests

Validate with PM upon request

As Requested

Phase-Out Transition Plan

Reference individual Task Order PWS for specific delivery instructions.

Reference individual Task Order

Reference individual Task Order

CDRL SUMMARY

Contract information data shall be delivered electronically in accordance to the corresponding requirement for each Data Item listed in Table 5-1 (below). The contractor shall have no more than one error per quarter for all CDRL submittals. The contractor shall submit CDRLs according to the due date indicated and have no more than one CDRL per quarter submitted after the identified due date. Grammatical errors do not count as an error. Substantive mistakes shall be corrected within two working days and corrective action taken to prevent recurrence of inaccurate late CDRLs.

Table 5-1

CDRL Number

Title

PWS Paragraph

A/B/C/D/E/F/G 001

Contractor's Progress, Status and Management Report

3.7.2.1

A/B/C/D/E/F/G 002

Equipment Inventory Records

6.1

A/B/C/D/E/F/G 003

Quality Control Plan

6.2

A/B/C/D/E/F/G 005

Air Force -Technical Manual Contract Requirements (TMCR)

3.6.2.3

A/B/C/D/E/F/G 006

Manuals, Technical - Time Compliance Technical Orders

3.6.2.3

A/B/C/D/E/F/G 007

Product Drawing And Associated List

3.6.2.3

A/B/C/D/E/F/G 008

Commercial Off-The Shelf Manuals

3.1.1

A/B/C/D/E/F/G 009

Technical Report - Study Services

3.6.2.4

A/B/C/D/E/F/G 010

Security Test Plan

3.3.4

A/B/C/D/E/F/G 011

Test Procedures

3.6.2.6

A/B/C/D/E/F/G 012

Software Development Plan

3.6.2.7

A/B/C/D/E/F/G 013

Database Design Description

3.6.2.8

A/B/C/D/E/F/G 014

Software User Manual

3.6.2.1

A/B/C/D/E/F/G 015

Computer Software Product End Items

3.1.2

A/B/C/D/E/F/G 016

Software Test Plan (STP)

3.1.4

A/B/C/D/E/F/G 017

Configuration Management Plan

6.5.2

A/B/C/D/E/F/G 018

Transition/Phase-Out Plan

6.1.2

ADDITIONAL REQUIREMENTS

Government Furnished Property (GFP)

Government furnished property will be issued to the contractor for repair when repairs are needed. The contractor shall safeguard all GFP placed into the contractor’s care. GFP shall be shipped to the OEM facility and returned to the 517th SWES by the contractor, at the contractor’s expense. (See attached excel spreadsheet). The contractor shall provide an equipment inventory record within 120 calendar days after contract award. (CDRL A/B/C 002)

The contractor shall develop a transition plan for decommissioning the Parsons LADO development lab to include the return of any GFP to the government (CDRL A/B/C 018)

Quality Control Plan

The contractor shall establish a complete Quality Control Plan (QCP) to ensure the requirements of this contract are provided as specified (CDRL A/B/C 003). 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 report shall be submitted to the 517th SWES Engineer, NLT 30 days post contract award.

Quality Assurance

The 517th SWES Engineer or alternate(s), will perform assessments of the contractor’s performance. Subsequent to contract award, specific name and contact information of the 517th SWES Engineer(s), with a letter defining duties and authority will be furnished to the contractor.

The 517th SWES Engineer or alternate(s) will inform the task manager in person when discrepancies occur and will request corrective action. The 517th SWES Engineer 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.

The government 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.

Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the CO.

CONTRACT ADMINISTRATION

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.

Configuration Management

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

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. The contractor shall 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 (CDRL A/B/C 017).

The contractor shall provide technical support to 517 SWES personnel during reviews and system safety related meetings at Peterson SFB. The contractor shall 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.

Problem Resolution

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 shall work cooperatively with the COR and/or CO to resolve issues as they arise.

Security Requirements

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

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).

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.

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

Schriever SFB, CO

LADO Sustainment

SECRET

AMCS

Vandenberg SFB, CA

LADO Sustainment

SECRET

Contractor Facility

LADO Sustainment

SECRET

The contractor shall contact the government security manager for a Common Access Card (CAC). The Government security manager will direct contractor to appropriate location and registration processes. Comment by OETTINGER, CHELSEY L CIV USAF AFMC AFSC/SWPA: Do we not know if this is a requirement or not? We should know this up front.

The contractor shall also obtain a Building ID and access card from the appropriate government security manager.

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.

The 517 SWES or GPS Program Office will 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 SWES project director. Special base access, computer security training and security training will be provided to the contractor employees by the appropriate

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).

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).

The contractor shall obtain 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.

Cybersecurity/Software Assurance Comment by OETTINGER, CHELSEY L CIV USAF AFMC AFSC/SWPA: This should be up with the task section.

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

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/.

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

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

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. Utilizing current government policy and/or operating procedures the contractor may be required to assist in the investigation and application of risk mitigation procedures and to exploit vulnerabilities at the system and sub-system level. Activities include, but are not limited to, improvements in software assurance through the development of tools and techniques; strengthening software partitioning and modularity capabilities; and theoretical and practical application of enhanced vulnerability discovery. The contractor shall demonstrate that the contractor has visibility into its supply chain for critical components, understands how supply chain risk can be introduced through those components, and has implemented or plans to implement countermeasures to mitigate such risks. The contractor shall plan for and implement countermeasures that mitigate the risk of foreign intelligence or foreign influence, technology exploitation, supply chain and battlefield threats and vulnerabilities that result in Level I (Catastrophic) and Level II (Critical) protection failures of the system per MIL-STD-882 mission criticality definitions

Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The Contractor shall ensure there are no Organizational Conflict of Interest (OCI) considerations associated with management of the work distribution across prime and subcontractors. Cross teaming is permitted provided the teaming arrangement does not create any OCI.

Travel / Temporary Duty (TDY)

Travel within El Paso County including other contractor facilities, Schriever Space Force Base, and Petersen Space Force Base will be considered the local area.

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

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.

Manpower Reporting:

The Contractor shall report ALL Contractor labor hours (including sub-contractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.SAM.gov

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data. User Manuals: Data for Air Force service requirements must be input at the ECMRA link. User manuals for Government personnel and Contractors are available at the ECMRA link at http://www.SAM.gov

Base Access

Contractor shall schedule all visits and coordinate Base entry by contacting their Government Sponsor. The contractor will be escorted at all times.

Contractor personnel performing work under this contract must have an active secret security clearance at time of award, and must maintain this level of security clearance through the entire period of performance.

Display of Identification

When contractor employees are inside a secure work area within an AFB/SFB, they shall wear visible Government-provided identification either as a part of, or attached to, their outer clothing. The identification shall clearly identify the individual as being a contractor employee.

Obtaining Identification

During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel. Upon the termination or completion of the contract, or in the case of an employee who no longer requires access to the work site, the contractor shall be responsible for promptly returning credentials to the Security Forces Pass and Registration Office. Lost badges shall be reported to the Maintenance TPMoup Security Officer within one (1) working day of the badge being lost.

Removal of Contractor Personnel

The contractor understands that any contractor employee may be summarily and immediately removed from or denied access to any Government property, facility, and installation at the sole discretion of competent Government authority if that authority determines such action is necessary to protect or preserve Government property, safety, and security, or to maintain good order and discipline.

Network Access: Comment by OETTINGER, CHELSEY L CIV USAF AFMC AFSC/SWPA: A CAC is required for this, and it’s not clear above or below that a CAC is required.

The Contractor must meet the same security requirements as government employees for access to AF networks or Automated Information Systems (AIS).

For those contractor employees who require government computer access only, a National Agency Check with written Inquiries (NACI) must be accomplished through the government.

Contractor employees shall complete Network User Licensing Computer Based Training (CBT) per AFI 33-115 Volume 2, paragraph 5.4.

Contractor employees requiring a government provided e-mail account shall annually complete the Information Assurance Awareness training. Interim access may be granted by Designated Approving Authorities only after submission of the NACI and favorable finger print determination has been received by the applicable security manager.

Contractors who no longer need network or AIS access shall report within 3 business days to the appropriate security manager and the Functional System Administrator.

The contractor understands that any contractor employee may be summarily and immediately removed from or denied access to any government property, facility, and installation at the sole discretion of competent government authority if that authority determines such action is necessary to protect or preserve government property, safety and security, or to maintain good order and discipline.

Additional Security Requirements

The contractor shall comply with all Security, Force Protection, and Antiterrorism requirements enforced at each installation. The contractor shall comply with local unit in and out processing procedures for all contractor personnel to ensure proper security-related briefings and debriefings are accomplished.

Contractor Identification Badges and Access Cards

The Contractor shall utilize the Defense Biometric Identification System (DBIDS) Badge/Controlled/Restricted Authorization Badge (CAB/RAB) in accordance with Hill AFB Instruction 36-812 and Hill Installation Defense Plan.

DBIDS Cards

Contractor submits a completed Air Force Materiel Command (AFMC) Form 496, Application for AFMC Identification Card, to the Contracting Officer Representative (COR). The COR completes and forwards Form 496 to the Security Manager (SM) for signature and processing. The SM will notify the COR after Form 496 is approved with instructions for obtaining a DBIDS. Contractors shall return completed Form 496 to issuing SM to begin the in-processing. Contractor employees with issues associated with their information on their Form 496 will be disapproved for DBIDS and will not be granted access to the installation.

NOTE: Escort authority will not be authorized, and Force Protection “Bravo” is the minimum established by Security Forces Squadron (SFS). Contractors with a current DBIDS have authority to sponsor (not escort) onto the installation and must follow installation procedures for doing so. Contractors who do not require access to DoD IT systems will be issued a DBIDS only.

Contractor employees approved for DBIDS will require sponsorship onto the installation to Pass and ID (building 430) to be issued a DBIDS. Employees going to SFS without being sponsored are considered to be on the installation illegally.

Common issues with a denied Form 496: derogatory background, such as felony criminal charge/s (current or past), foreign national, missing information on form, failed to receive DBIDS within allotted time frame after approval.

If denied access the employee will return all government issued credentials and will vacate the installation immediately. A separate notification will be provided by the 75 ABW/CC if an appeal is requested for access.

Controlled Area Badge Process

Employees without a current DBIDS, or denied access to the installation, will not be issued a CAB until all issues are resolved.

The contractor shall provide, through the COR, written justification with employee full name, Height, Weight, Eye Color, Hair Color, contract number with expiration date and areas needing access to the issuing SM to initiate a request for a badge.

Controlled area badge (CAB) requests shall be completed by the group SM, who shall complete an AF Form 2586, Unescorted Entry Authorization Certificate, for each employee requiring entry into controlled/restricted areas. The contractor employee shall carry the AF Form 2586 to Security Forces (building 430). The AF Form 2586 will be returned to the issuing SM for accountability.

NOTE: CABs will not be issued for the inconvenience of having to be escorted.

While in the Controlled Areas, contractor employees shall display the CAB…