OPIR PWS v.4_15_Jan_2025.pdf

i

PERFORMANCE-BASED WORK STATEMENT (PWS)

NEXT-GENERATION OVERHEAD PERSISTENT INFRARED (NEXT-GEN OPIR)

SOFTWARE DEPOT ACTIVATION GAP ANALYSIS

U.S. AIR FORCE

AIR FORCE SUSTAINMENT CENTER/SOFTWARE DIRECTORATE (AFSC/SW)

January 15, 2025 ii

TABLE OF CONTENTS

1 DESCRIPTION OF SERVICES

1.1 Scope

1.2 Background

2 period of performance

2.1 Period of Performance

2.2 Table 2-1

2.3 Phase-In Period

2.4 Execution Period

2.5 Phase Out Period

3 General deliverable requirements

3.1 Labor Category and Base Operating Support Report

3.2 Facilities Management Report

3.3 Information Technology (IT) and Networking Report

3.4 Lab Environment Report

3.5 Software Development Life Cycle (SDLC) Report

3.6 Training Report

3.7 Operations and Process Report

3.8 Technical Data Report

4 ADDITIONAL REQUIREMENTS

4.1 Personnel Roster

4.2 Monthly Status Report (MSR)

4.3 Project Planning Chart

5 SERVICE SUMMARY

6 CDRL SUMMARY

6.1 Deliverable Requirements

6.2 Additional Deliverable Requirements

6.3 Deliverables

7 COntract REQUIREMENTS

7.1 Government Surveillance/Inspection

7.2 Quality Management System (QMS)

7.3 Quality Assurance

7.4 Government Provided Property, Support, And Information

iii

7.5 Travel

7.6 Program Management

7.7 Security Requirements

7.8 Safety Requirements

8 CONFLICTS OF INTEREST

9 GENERAL INFORMATION

9.1 Government Representatives

9.2 Environmental

9.3 Invoicing/Payment

9.4 Hours of Operation

Appendix A – REFERENCES

1 DESCRIPTION OF SERVICES

1.1 Scope

The Next Generation Overhead Persistent Infrared (Next-Gen OPIR) program is intended to first augment, then replace, the Space Based Infrared System (SBIRS) program-of-record and will utilize two sets of satellites that provide worldwide initial warning of ballistic missile attacks on the United States using Infrared detection. Next-Gen OPIR GEO (NGG) satellites will have a

Geosynchronous Earth Orbit with coverage around the equator. Lockheed Martin is the prime contractor for the NGG Space vehicles with Raytheon as a subcontractor for the satellites’ payload. Next-Gen OPIR Polar (NGP) will consist of satellites providing infrared coverage of the northern polar region. Northrop Grumman is prime for these satellites with Ball Aerospace providing their payloads.

Gap analyses will be performed to determine the differential between where the SWEG organizations are and where they need to be to perform this workload. This PWS describes the performance objectives and standards expected of the contractor to provide information necessary for SWEG to produce the gap analysis documents.

1.2 Background

Air Force Materiel Command (AFMC) identified Next-Generation Overhead Persistent Infrared

(Next-Gen OPIR) Polar and GEO Space Vehicle software (SW) workloads for Depot Source-Of-

Repair (DSOR). DSORs #20-078F and #22-022F assigned the 309th Software Engineering

Group (309 SWEG) at Hill AFB, Utah responsibility for both efforts. 402 SWEG at Robins

AFB, GA will partner with 309 SWEG (collectively referred to as “SWEG”) and the OEM contractors to determine the requirements to standup organic Software (SW) sustainment under both organizations.

2 PERIOD OF PERFORMANCE

2.1 Period of Performance

The entire contract duration will be divided into a phase-in period, an execution period, and a phase-out period. Commencing from the date of contract award, the period of performance will initiate, with the first phase being the phase-in period. The total contract period of performance shall consist of a 30-calendar day phase-in period, a 120-calendar day execution period, and a 60-calendar day phase-out period. Entry and exit criteria for each period is shown in the table below.

2.2 Table 2-1

Phase-in Period (30

Calendar Days)

Execution Period (120

Calendar Days)

Phase-out Period (60

Calendar Days)

Entry

Criteria

• Project Kickoff meeting scheduled.

• Establishment of communication channels and coordination protocols between the contractor and SWEG.

• Acknowledgment of the

PWS tasks and schedule by both parties.

• Establish format of deliverables (see PWS

Section 6.3).

• Completion of the phase-in period.

• Site visits at Contractor facility.

• Availability of all required personnel, equipment, and resources for the Execution

Period

• Completion of the Execution

Period.

• Scheduled additional site visits unless waived by

SWEG.

• Availability of all required personnel and resources for phase-out activities.

• Initiation of the knowledge transfer process to the contracting organization or relevant stakeholders.

• Begin Government review and acceptance of deliverables in Section 3 of the PWS.

Exit

Criteria

• Completion of Project

Kickoff Meeting

• Delivery of Master

Schedule/Project Plan

(see Section 6 of the

PWS). Delivery of Key

Personnel Roster (see

Section and 6 of the

PWS)

• Scheduled site visits to

Contractor’s facility.

• Achievement of predetermined project milestones within the scheduled timelines.

• Submission of comprehensive progress reports and documentation of completed tasks and deliverables as detailed in

Section 4.2 of the PWS.

• Completion of contractor site visits.

• Reviewed site visit conclusions between

Contractor and SWEG.

• Approval of the phase-out plan tasking by both parties.

• Comprehensive resolution of all identified technical inquiries as outlined in the

Section 4.2.1 of the PWS.

• Final delivery of all reports as detailed in Section 3 of the

PWS.

• Successful transfer of knowledge, including project insights, documentation, and best practices, to the contracting organization.

• Government approval of

Final Documents and all issues resolved (See Section

2.4.2).

• Formal acceptance and approval of the phase-out activities by both parties.

2.3 Phase-In Period

The phase-in period shall not exceed 30 calendar days from date of contract award. The following tasks shall be accomplished during the phase-in period:

2.3.1 Kickoff Meeting

The Contractor shall attend a Project Kick-off Meeting to be held within the Phase-in period.

The Government team will schedule and coordinate virtual Project Kick-off Meeting no later than (NLT) five (5) calendar days after contract award. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will also provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and

Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel and key SWEG representatives. The Government team will provide an agenda that includes, but not be limited to, the following:

• Introduction of personnel

• Overview of project tasks

• Schedule to include the Project Planning Chart (shows major tasks, milestones, and deliverables, planned and actual start and completion dates for each deliverable) (CDRL

A010).

• Communication Plan/lines of communication overview (between both Contractor and

Government)

• Formatting of deliverables.

• Reporting Requirements, e.g. Monthly Status Report (MSR) (CDRL-A011).

• POCs, to include their roles and responsibilities for the contract.

• Overview of Phase-In period to include process, timeframes, and status.

• Additional issues of concern (Leave/back-up support)

2.3.2 Identify Key Personnel

The Contractor shall identify key personnel for the contract, including participants of the site surveys. A list of these key personnel shall be included on a Key Personnel Roster (reference paragraph 4.1). An update of this roster shall be included in each Monthly Status Report

(reference paragraph 4.2).

2.3.3 Schedule Site Visit to Contractor Facility

The Contractor shall schedule a site visit for the Government to the Contractor’s facility within the phase-in period. The Contractor shall be responsible for collaborating with SWEG to select suitable dates, arrange necessary security and visitation materials, and establish an itinerary for the visit.

2.3.4 Provide Project Planning Chart

The Contractor shall provide a Project Planning Chart of the outline of deliverables and progress for each (reference paragraph 4.3). An update of this Project Planning Chart shall be included in each Monthly Status Report (reference paragraph 4.3).

2.4 Execution Period

The Execution Period begins after the conclusion of the Phase-in Period and shall be completed no later than 120 calendar days from contract award date. The following tasks shall be accomplished during the Execution Period:

The requested deliverables shall be provided electronically and shall be delivered on a weekly cadence as documents are produced with final delivery no later than 120 Calendar days from the start of the Execution Period.

2.4.1 Conduct Site Visit to Contractor Facility

A visit to the Contractor’s facility shall occur within the 7 calendar days from the beginning of the Execution Period. The Government team will consist of approximately 6 individuals from

SWEG. The site visit should not exceed 3 calendar days. If SWEG determines it is necessary, there will be a follow-on visit of an additional three business days for resolution of any identified discrepancies.

The purpose of the site visit is to discuss the Gap Analysis Contract CDRL deliveries on site with the OEM and confirm the information produced for each. This includes, but not limited to, verification of OEM networks, software development environment/processes, and lab facilities to confirm data from each section of the contract requirements

The Contractor shall identify all security and visitation requirements for required site visits to the

Contractor’s facility/facilities. The Contractor’s security team(s) shall assist SWEG personnel to verify and/or obtain all security clearances and visitation requirements prior to arrival. All visits shall be coordinated in advance between the SWEG and the Contractor at least 7 calendar days prior to arrival.

2.4.2 Technical Inquiries

The Contractor shall provide responses to technical inquiries made by the Government and provide a resolution or path forward in an event log to be included with the MSR (see Section 6 of the PWS).

2.4.3 Weekly Status Meetings

The SWEG and the Contractor shall hold weekly SWEG-led contract status meetings. Sub-teams shall be formed as necessary with representatives of the Contractor and SWEG to focus on areas of deliverables and report the status and issues at the weekly meetings.

2.4.4 Provide Final Deliverables

The Contractor shall provide all final deliverables as detailed in Section 3 of the PWS 120 calendar days from the start of the Execution period.

2.5 Phase Out Period

The phase out period shall be for 60 calendar days after the end of the Execution Period during which the Contractor shall provide reach back for engineering support, follow-on questions, and one additional follow-on site visit, if requested.

2.5.1 Additional Site Visits

The Contractor shall support a follow-on site visit if requested by SWEG.

2.5.2 Government Review and Acceptance of Final Deliverables

The Government will review the deliverables and may request an answer to inquiries about the documents within the first 30 days of the Phase-out Period. In the event of such a request, the

Contractor shall confirm receipt of the request within 3 calendar days of the request and shall provide a response with a proposed resolution or path forward within 5 calendar days of receipt request. The response shall be sent to the Government PM and COR by email.

3 GENERAL DELIVERABLE REQUIREMENTS

All document deliverables shall be provided to the 309 and 402 SWEGs as agreed to in the kick-off meeting (Section 2.3 of the PWS). The contractor and SWEG will decide the order and intervals of document delivery during the phase-in period, with final document delivery no later than 120 Calendar days from the start of the Execution period. The order and interval of document delivery will be documented in the Project Planning Chart and delivered in the MSR

(Section 4.2, 4.3 of the PWS). (CDRL A011 – DI-MGMT-80507).

3.1 Labor Category and Base Operating Support Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A001). The Contractor shall provide a report of the expected positions by labor category and level required to support OPIR software sustainment as identified by studies in this GAP analysis. The Contractor shall provide this report no later than

120 calendar days from start of Execution period/150 calendar days after contract award.

(DI-MISC-80508B/T)

3.1.1 Personnel and skillsets required for OFP software sustainment

The Contractor shall provide comprehensive job descriptions for each position, outlining responsibilities, required skills, required security clearance level, and qualifications for Flight

OFP Software Maintenance (SW and Environments). For each role, the Contractor shall state if the role requires full time/part time employee and if remote work is applicable.

3.1.2 Required staffing amount and skillset necessary to support build and integration at the prime integrator’s facility.

The Contractor shall identify typical travel schedules, amount of personnel permanently staffed at the prime integrator’s facilities dedicated in part or full to these projects and the staff primarily assigned to sustainment. The Contractor shall identify personnel responsibilities levied upon the

Contractor in support of test and qualification at the prime integrator.

3.2 Facilities Management Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A002). For facility management deliverables, the facilities are only those where OPIR software work occurs. The Contractor shall provide this report no later than 120 calendar days from start of Execution period/150 calendar days after contract award. See all sub-components of the report (3.2.1-3.2.7)

(DI-MISC-80508B/T)

3.2.1 Facility Requirements

The Contractor shall identify requirements for workspaces and lab spaces that are required to support Next-Gen Geo OPIR software sustainment to include, the classification level of workspaces for each developer and support role. The Contractor shall Identify if a role may require workspaces at multiple classification levels, if a role may require intermittent access to specific classification levels and estimated occurrence of required access. (e.g., daily, weekly, etc.), physical facility requirements that are required to support NGG OPIR software sustainment, and space requirements for each classification level necessary to support the program.

3.2.2 Facility Lessons Learned and Challenges

The Contractor shall detail any challenges faced during the facility setup or operations and any lessons learned from these experiences.

3.2.3 Supplier and Contractor Information

The Contractor shall provide information regarding suppliers, contractors, and service providers involved in supporting the operation and maintenance of the facility. The Contractor shall delineate the requirements for the facility and its equipment, rather than specifying individual service providers. However, it is essential to identify any proprietary supplier or contractor dependencies if applicable.

3.2.4 Utilities and Services

The Contractor shall provide utility requirements such as electricity, water, HVAC (Heating, Ventilation, and Air Conditioning), internet connectivity, and other necessary services.

3.2.5 Facility Equipment and Tools

The Contractor shall provide a comprehensive list of all equipment, machinery, tools, and specialized hardware used in the facility, delineating type, manufacturer, part number, and serial numbers.

3.2.6 Facility and Workspaces

The Contractor shall provide details about the physical layout of the facility, including floor plans, room dimensions, classification level, electrical requirements, cooling, environmental control, and the arrangement of workspaces, labs, or specialized areas. Facility and workspace deliverable shall be for the spaces and facility relevant to OPIR flight software development.

3.3 Information Technology (IT) and Networking Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A003). IT and networking deliverables are only focused on the IT and networking that supports OPIR software. The Contractor shall provide this report no later than 120 calendar days from start of Execution period/150 calendar days after contract award. See all sub-components of the report (3.3.1-3.3.13).

(DI-MISC-80508B/T)

3.3.1 Network Architecture Diagrams

The Contractor shall provide detailed diagrams depicting the layout of the network, including connections, routers, switches, and any network segmentation or special configurations. The

Contractor shall assign each network to the following categories: Contractor- Owned Contractor-

Operated, Government-Owned Contractor- Operated, and Government-Owned Government-

Operated. The Contractor shall identify classification level of the networks required to support

NGG OPIR Flight Software sustainment.

3.3.2 Internet Service Provider (ISP) Information

The Contractor shall provide details about the Internet Service Provider (ISP), internet connection type, bandwidth requirements, service-level agreements (SLAs), and any redundancy measures in place.

3.3.3 Network Configuration and Settings

The Contractor shall provide details on high level network configurations, IP addressing schemes, subnets, virtual local area network (VLAN), and any security protocols or encryption methods used. This deliverable is only for items relevant to OPIR flight software development.

3.3.4 Communications requirements

The Contractor shall identify the necessity of secure teleconferencing lines necessary to support

Next-Gen OPIR software sustainment. The Contractor shall specify the virtual teleconferencing requirements and security levels needed.

3.3.5 Networking Storage Requirements

The Contractor shall identify physical storage requirements for networking support equipment and spare networking support equipment, to include data storage requirements to support software development, lab and flight test instrumentation data, support documentation and configuration management functions. The Contractor shall identify the classification level and classification requirements for storing required data types of each storage space. Network

Documentation

The Contractor shall provide network documentation including topologies, data flow, ports protocols and services (PPS), data diodes and all Risk Management Framework (RMF) documentation necessary to maintain network Authority to Operate (ATO). The Contractor shall identify bandwidth requirements for each network and Voice over Internet Protocol (VoIP) requirements for each network.

3.3.6 IT Compliance and Regulations

The Contractor shall provide processes used to ensure compliance with relevant standards, regulations, and cybersecurity protocols applicable to the facility’s IT infrastructure.

3.3.7 IT Policies and Procedures

The Contractor shall provide documented policies and procedures related to IT operations, network management, cybersecurity protocols, and disaster recovery plans.

3.3.8 Backup and Recovery Procedures

The Contractor shall provide a report documenting protocols and methods used for data backup, storage, and recovery in case of system failure or data loss.

3.3.9 IT Support and Maintenance

The Contractor shall provide a report documenting support services, maintenance contracts, and arrangements with IT service providers or vendors for network and system maintenance.

3.3.10 Security Measures

The Contractor shall provide a report documenting the security measures in place, including firewalls, intrusion detection systems, antivirus software, access controls, and any encryption methods used to secure the network.

3.3.11 Software and Operating Systems

The Contractor shall provide information on the software used for network management, security, operating systems, and any specialized applications. The Contractor shall identify necessary software tools for network administration, monitoring, operations, support, and network security. The Contractor shall identify non-commercial software used for networking and IT.

3.3.12 Hardware Inventory

The Contractor shall provide a list of all networking equipment, such as servers, routers, switches, firewalls, access points, and other hardware components used in the facility.

3.4 Lab Environment Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A004). The lab environment is defined as only the labs in which work supporting OPIR software occurs. The Contractor shall provide this report no later than 120 calendar days from start of Execution period/150 calendar days from date of contract award. See all sub-components of the report (3.4.1-3.4.9)

(DI-MISC-80508B/T)

3.4.1 Lab Infrastructure Details

The Contractor shall provide specifics about the lab’s physical infrastructure, including floor plans, room dimensions, layout, and equipment placement. The Contractor shall include relevant wiring diagrams and interface documents. The Contractor shall include connector parts numbers and cable wiring diagrams for lab equipment.

3.4.2 Equipment Inventory

The Contractor shall provide a comprehensive inventory of all hardware, such as servers, workstations, testing equipment, test stations, networking devices, and any specialized machinery or tools used in the lab. The Contractor shall identify part numbers for all commercial-off-the-shelf (COTS), government-off-the-shelf (GOTS), and specialized vendor development equipment to include breakout boxes, data recorders, oscilloscopes, real-time spectrum analyzers, and computer systems including vendor and equipment part numbers. The

Contractor shall identify each tool as commercial, non-commercial, government owned, proprietary, or open source. For equipment, the Contractor shall state dimensions, weight, cooling, electrical requirements. The Contractor shall identify non-commercial tools, models, databases, datasets, firmware, and simulations necessary to support, operate, and test lab spaces.

3.4.3 Tool Configuration

The Contractor shall provide a report detailing how the lab environment is configured for different activates supporting the OPIR effort. The Contractor shall include the setup of testing environments, staging areas, and production-like environments. The Contractor shall provide details about the configurations and settings used for tools, including how they are set up, integrated, and customized for the lab’s specific needs.

3.4.4 Lab Storage

The Contractor shall provide a report detailing lab storage requirements that will be required to support software sustainment. The Contractor shall identify physical storage requirements for spare and support equipment, including the classification level of each storage space.

3.4.5 Supplies and Consumables

The Contractor shall provide a list of supplies and consumables regularly used in the lab, including chemicals, reagents, lab ware, and any specialized materials.

3.4.6 Safety Protocols

The Contractor shall provide a report detailing safety measures and protocols followed in the lab, including emergency procedures, hazardous material handling, and protective gear requirements.

3.4.7 Compliance and Regulations

The Contractor shall provide a report detailing needed compliance with industry and government standards, regulations, and safety protocols relevant to the lab’s operations.

3.4.8 Operating Procedures and Workflows

The contractor shall provide documented procedures, workflows, and best practices followed in the lab for various operations and tasks.

3.4.9 Lab Maintenance

The Contractor shall identify the repair and disposal process for lab assets. The Contractor shall document planned and expected lab equipment obsolescence. The Contractor shall identify upgrade plans, details of established sustainment, and replacement plans. The Contractor shall identify maintenance and support information including stock information for Line Replaceable

Unit (LRU), Shop Replaceable Unit (SRU), and cable assemblies to maintain the facility. The

Contractor shall document planned and expected equipment obsolescence. The Contractor shall identify upgrade plans, details of established sustainment, specify classification, and replacement plans.

3.5 Software Development Life Cycle (SDLC) Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A005). The SDLC encompasses software development, integration, testing, deployment, documentation, DevOps practices, Agile mythology, and version control of OPIR software. The Contractor shall provide this report no later than 120 calendar days from start of Execution period/150 calendar days from date of contract award. See all sub-components of the report (3.5.1-3.5.20

(DI-MISC-80508B/T)

3.5.1 Software Architecture

The Contractor shall provide an overview of the Software Architecture. The Contractor shall identify all software Computer Software Configuration Item (CSCIs) and firmware modules along with their constituent software units. The Contractor shall show the static relationships of the software units and state the purpose of each software unit.

3.5.2 Current Software Development Workflow

The Contractor shall provide the existing workflow, including the steps involved in the software development process, from ideation to deployment. The Contractor shall identify classification levels used at each phase of the software development lifecycle. The Contractor shall include methodologies and best practices. The Contractor shall identify integration events that occur with third parties prior to testing.

3.5.3 Software Development Life Cycle External Dependencies

The Contractor shall provide documentation on external dependencies within the SDLC. The

Contractor shall identify dependencies to the prime integrators and other program stakeholders.

The Contractor shall identify any risks associated with each dependency.

3.5.4 Software Modernization

The Contactor shall provide documentation on past, present, and future software modernization practices. The Contractor shall detail how feedback from users and stakeholders is collected, and how it is used to drive improvements in the process of the SDLC.

3.5.5 Change Requests

The Contractor shall provide a list identifying past and present software change requests. The

Contractor shall detail the status of the requests, reason for the request, rework time of defects, and phase of discovery.

3.5.6 Version Control and Branching Strategies

The Contractor shall provide information about the version control system used, branching strategies, and how code is managed, merged, and released within the lab environment. The

Contractor shall identify how test code is checked-in and vetted for lab testing.

3.5.7 Source Code

The Contractor shall identify all source code, databases, datasets, and firmware.

3.5.8 Technology Stack

The Contractor shall provide information on the technology stack used for development, including programming languages, frameworks, databases, and any third-party services.

3.5.9 Testing and Quality Assurance Procedures

The Contractor shall provide insights into the testing methodologies, types of testing performed

(i.e. test-driven development, unit test, integration test, regression test), and quality assurance measures used during the SDLC. The Contractor shall provide information on the coding standards, best practices, and guidelines followed by the development team for ensuring code quality and consistency.

3.5.10 Automated Testing

The Contractor shall provide a report detailing automated test capability currently used to support the SDLC. The Contractor shall identify automated test capability, language, interfaces, and future updates. The Contractor shall identify how automated test scripts are configuration managed and traced to testing requirement.

3.5.11 Data Transfer Methods

The Contractor shall identify unique data transfer methods to the prime integrator necessary to support the SDLC.

3.5.12 Software Development Life Cycle Equipment

The Contractor shall provide list of baseline equipment required to support the SDLC environment. Identify unique and proprietary hardware along with their interfaces and configuration. The Contractor shall provide a report of the software development environment setup, including the tools and Integrated Development Environments (IDE)s used by the OEM development team.

3.5.13 Software and Tools

The Contractor shall provide concise information on SDLC tools. Specify essential software tools (e.g., scenario generators, build loaders) for lab resource utilization in development, testing, and software delivery. The Contractor shall provide to indicate commercial or non-commercial status, tool usage, and target hardware. The Contractor shall provide a report detailing necessary simulations, emulations, and utilities for the SDLC. Include software license agreements, ownership, and applicable standards for each tool.

3.5.14 Non-Commercial Software

The Contractor shall identify source code, Operating System(s), executable(s), and build procedures for non-commercial software. The Contractor shall identify unique host requirements, data rights asserted, and the basis for the assertion.

3.5.15 CSCI Information

The Contractor shall identify all simulation and emulation CSCIs, firmware modules, and source code. The Contractor shall provide identify target hardware for each simulation and emulation

CSCI and firmware module. Identify the tools, compilers, databases, and models by simulation and emulation CSCI.

3.5.16 Release Process

The Contractor shall identify the release process for delivery of software to the prime integrator and other stakeholders. The Contractor shall provide identify types of software releases and technical data package details required for each release type.

3.5.17 Build and Deployment Processes

The Contractor shall provide details about the build processes, deployment strategies, and release methodologies, including how new features and updates are tested and rolled out to production.

3.5.18 Software Training and Support Materials

The Contractor shall provide a report detailing any training materials, tutorials, or support documentation available for the software tools used in the SDLC.

3.5.19 SDLC Team Structure and Roles

The Contractor shall provide information about the current team structure, roles, and responsibilities of each team member involved in the SDLC.

3.5.20 Risk Management

The Contractor shall identify any past and current risks identified in the SDLC. Detail consequence, likelihood, and mitigations for each risk.

3.6 Training Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A006). Training deliverables is only for training in support of OPIR software. The Contractor shall provide this report no later than 120 calendar days from start of Execution period/150 calendar days from date of contract award. See sub-components of the report (3.6.1-3.6.4).

(DI-MISC-80508B/T)

3.6.1 Training Goals and Objectives

The Contractor shall provide specific training goals and objectives, including the desired outcomes, skills, and competencies that the training program aims to develop in the participants.

3.6.2 Training Materials

The Contractor shall provide access to existing Original Equipment Manufacturer (OEM) training materials, including guides, tutorials, and any internal resources used for training purposes to support the OPIR flight software sustainment.

3.6.3 Training and Development Programs

The Contractor shall provide a list of any training programs, skill development initiatives, or ongoing learning opportunities provided to employees, internally or externally, to support flight software sustainment. The Contractor shall identify System Level training and familiarization necessary to support NGG OPIR Flight Software sustainment to include the training necessary to support software change management, requirements analysis, requirements traceability, deficiency investigation, software integration and testing including, but not limited to, unit testing, independent validation & verification, software integration testing, and development/operational flight-testing.

3.7 Operations and Process Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A007). The Contractor shall provide a report of operation and process deliverables are for the operation and process of work supporting OPIR flight software sustainment. The Contractor shall provide this report no later than 120 calendar days from start of Execution period/150 calendar days from date of contract award. See sub-components of the report (3.7.1-3.7.12).

(DI-MISC-80508B/T)

3.7.1 Program Management

The Contractor shall provide a report of program management responsibilities that will extend to the SWEG in support of Next-Gen OPIR software sustainment. The Contractor shall provide a report to include an overall program summary, advice, and any future recommendations for

SWEG.

3.7.2 Data Storage

The Contractor shall identify data storage requirements to support software development, lab and test instrumentation data, and documentation and configuration management functions.

3.7.3 Digital Storage Requirements

The Contractor shall identify required digital storage amount, classification level, storage requirements, and archival requirements.

3.7.4 HAZMAT Procedures

The Contractor shall provide a report detailing HAZMAT procedures necessary to perform support operations for Next-Gen OPIR facilities. The Contractor shall identify HAZMAT procedures associated with PAO and other hazardous materials used at OEM facility.

3.7.5 Environmental Procedures

The Contractor shall provide a report detailing Environmental, Safety and Occupational Health

(ESOH), detailing ESOH requirements and hazards necessary to support Next-Gen OPIR integration and test facility. The Contractor shall identify RF hazard and safety mitigations used in OEM facility for Next-Gen OPIR transmission.

3.7.6 Cybersecurity

The Contractor shall provide a report of the Cybersecurity certification requirements and process for the Next-Gen OPIR.

3.7.7 Configuration Management

The Contractor shall provide a report of configuration management requirements necessary to support software sustainment and to allow SWEG personnel collaboration within the OEM’s and the prime integrator’s development environments. The Contractor shall identify software and online tools necessary to support software and documentation configuration management. The

Contractor shall identify the configuration management process for all tools, to include version numbers, hash values, classification levels, security requirements, required OS versions, and a description of usage; identify each piece of software as commercial, non-commercial, Government owned, proprietary, and open source.

3.7.8 Information Flow

The Contractor shall identify methods and tools used for real-time information flow between

Contractor, the prime integrator, and other stakeholders. The Contractor shall include classification levels, security requirements, and a description of usage.

3.7.9 Project Management Tools

The Contractor shall identify the project management tools and software being used to track tasks, progress, and milestones.

3.7.10 Facility Compliance and Regulations

The Contractor shall provide documentation related to compliance with industry standards, regulations, and safety protocols relevant to the facility.

3.7.11 Operating Procedures and Workflows

The Contractor shall provide documented operating procedures, workflows, and best practices followed in the facility.

3.8 Technical Data Report

The Contractor shall provide documentation containing the following information in a deliverable technical report: (CDRL A008). The technical data deliverables are only for technical data supporting NGG OPIR Flight software. The Contractor shall provide this report no later than 120 calendar days from start of Execution period/150 calendar days from date of contract award. See sub-components of the report (3.8.1-3.8.7).

(DI-MISC-80508B/T)

3.8.1 System Technical Data

The Contractor shall provide documentation containing system architecture and configuration data for the Next-Gen OPIR system.

The Contractor shall identify system-level documentation, interface documents, illustrated parts breakdown specifications, system diagrams, wiring diagrams, system requirements specifications, interface requirements specifications, interface design documents, interface control documents, prime item development specifications, and operations and maintenance diagrams.

The Contractor shall include documentation covering functional, operational, and interface requirements, along with a requirements traceability matrix (RTM). All items shall be only for

OPIR flight software.

The Contractor shall provide documentation containing formal qualification test procedures and test reports for the most recent NGG OPIR Flight OFP at the highest configuration level.

3.8.2 Documentation Practices

The Contractor shall provide a report of the existing documentation practices, including how code, APIs, and system architecture are documented, and how knowledge transfer occurs within the team pertaining to OPIR Flight Software sustainment.

3.8.3 Software Sustainment Documentation

The Contractor shall provide a list of documentation and databases required for software sustainment.

3.8.4 Software Technical Data

The Contractor shall provide a report of the technical data required to develop, integrate, build, and test software. The Contractor shall include programming manuals, coding standards, technical drawings, block diagrams, interface documents, requirements documents, software design descriptions, DR/PR documents. Include formal qualification test procedures and test reports for the most recent Next-Gen OPIR Flight Software.

3.8.5 Data Collection

The Contractor shall provide a report detailing data collection methods used in the lab for Flight

Software. Identify delivery methods from outside sources, such as the prime integrator. The

Contractor shall identify software tools and processes required to record and analyze data.

Identify hardware required for processing and collecting Next-Gen OPIR data.

3.8.6 Tool Documentation and Knowledge Base

The Contractor shall provide documentation, guides, or knowledge base articles related to tools supporting flight software development, integration, build, and test. The Contractor shall include operations manuals, technical drawings, block diagrams, interface documents, and theory of operation. For each tool, the Contractor shall provide all test plans and reports that tool is used in and state the purpose of the tool for the test.

3.8.7 Lab Technical Data

The Contractor shall provide documentation and lab technical data pertaining to the development and maintenance of the lab spaces. The Contractor shall identify software tools and process required to record and analyze data for Flight Software.

4 ADDITIONAL REQUIREMENTS

4.1 Personnel Roster

The Contractor shall provide a key personnel roster of employees assigned under this contract in a deliverable (CDRL A009) due 5 days from contract award. The Contractor shall provide an updated roster within 5 calendar days of any changes to key personnel. The Contractor shall include the employee’s name, role, contact information and security clearance level in the roster.

(CDRL A008 – DI-MGMT-81834)

4.2 Monthly Status Report (MSR)

The Contractor shall submit by email to the Government PM, COR, and CO a Monthly Status

Report (MSR) on the fifth calendar day of each month, except the first month. This report shall include a narrative review of contractor accomplishments, and a summary of tasks and milestone progress completed during the previous calendar month. The MSR shall include a comprehensive copy of the issue/event log of current and past issues (see sub section of MSR), the current Contract Project Planning Chart (reference this paragraph), financial invoice submission status and the current key personnel roster (Section 6.1 of the PWS). (CDRL A010 –

DI-MGMT-80368A)

4.2.1 Technical Inquiries

At any time during the contract period of performance the Government Program Manager may request by email an answer to a technical issue or question. In the event of such a request, the

Contractor shall confirm receipt of the request within 3 calendar days of the request and shall provide a response with a proposed resolution or path forward within 5 calendar days of receipt request. The response shall be sent to the Government PM and COR by email. All responses

(open and closed) shall be tracked in an issue/event log that shall be included as part of the

Monthly Status Report. (See 4.2)

4.3 Project Planning Chart

The Contractor shall provide a Project Planning Chart no later than 30 calendar days from contract award, to include, expected start, review, and completion dates of deliverable reports in

Section 3 of this PWS. This Project Planning Chart shall be updated monthly and shall be delivered with the Monthly Status Report (Section 6.2 of the PWS). (CDRL A011 – DI-MGMT-

80507)

5 SERVICE SUMMARY

PWS

Paragraph

Performance

Objective

Performance Threshold Monitoring

Method

Frequency AQL

2.3.1 Project Kick-Off

Meeting

Contractor shall attend the Project

Kick-off meeting and provide input and understanding of all of the elements of this section specified

Verification of attendance of

Contractor

Personnel

Event Driven 100%

2.3.2 & 4.1 Personnel Roster The Contractor shall provide a key personnel roster of employees assigned under this contract

100% Inspection Event Driven 100%

2.3.4, 4.3 Project Planning Chart The Contractor shall provide a Project

Planning Chart no later than 30 days from contract award, to include, expected start, review, and completion dates of deliverable reports in Section

3 of this PWS

100% Inspection Event Driven 100%

3.1-3.8

Technical

Report

Delivery

The contractor shall deliver all

Technical Reports on the due dates as outlined in the PWS – any changes will be updated and submitted within ten

(10) business days. Contract Data

Requirements List (CDRL)

A001-A008

100%

Inspection

As Required

100% on time delivery

3.1-3.8

Technical Report

Content

Contractor shall deliver all Technical

Reports which address all elements outlined in PWS Section 3.

CDRL A001-A008

100%

Inspection

100% of required content

4.2

Provide

Monthly Status

Report (MSR)

Contractor MSR shall include a narrative review of contractor accomplishments, and a summary of tasks and milestone progress, Contract

Project Planning Chart, financial invoice submission status and current

Key personnel roster changes, technical inquiries completed during the previous calendar month. MSR shall be provided by the 5th day of the following month.

CDRL A010

Monthly and

PM

coordination.

Monthly

95% On time

Delivery

4.2.1 Technical Inquiry Contractor’s PM acknowledges

Government technical inquiries within three (3) calendar days of receipt and provides an answer or resolution or path forward within five (5) calendar days of initial request from SWEG

100% Inspection As Required 100%

6 CDRL SUMMARY

6.1 Deliverable Requirements

The requested deliverables shall be provided electronically. All deliverables are to be in contractor’s format, subject to government approval. If any item requires tools or software to open/view not readily available to the Government, the Contractor shall provide the tools or means necessary for the Government to view the delivered documents.

6.2 Additional Deliverable Requirements

1. Include classification levels, security markings, and version numbers.

2. For all documents; state document owner, method of access, description of purpose, and list of reference documents.

3. Identify any applicable standards and provide digital copies of the standards.

organizations.

2.3.4, 4.3 Project Planning

Chart (PPC) Contractor PCC shall include, expected start, review, and completion dates of deliverable reports in Section 3 of this PWS and delivered not later than thirty (30) days from Contract award. Then subsequently updated in the MSR.

CDRL A011

100% Inspection and PM coordination

As Required 100% on time delivery

7.2 Quality Program Plan

The contractor shall provide a Quality

Program Plan (QPP) delivered within fifteen (15) days of contract award detailing the contractor’s quality system, including management commitment to quality, policy and practices. Updates shall be provided whenever there is a change. CDRL

A012

100% Inspection As Required and compliance

7.6.1

Contractor Program

Manager (PM)

The Contractor shall provide a

Program Manager (PM) who shall be the single point of contact responsible for Contractor personnel, including all administrative duties of Contractor personnel, and act as a liaison to the

Government for contract performance matters. .

100% Inspection

6.3 Deliverables

The Contractor shall provide the following information to SWEG:

Table 6-1

PWS Para. Exhibit Title CDRL REF Delivery

3.1 A001

Labor Category and Base Operating

Support Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

3.2 A002

Facilities Management Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

3.3 A003

Information Technology (IT) and

Networking Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

3.4 A004

Lab Environment Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

3.5 A005

Software Development Life Cycle

(SDLC) Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

3.6 A006

Training Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

3.7 A007

Operations and Process Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

3.8 A008

Technical Data Report

DI-MISC-80508B/T 150 Calendar Days after

Contract Award – 120 Days after start of Execution Period

2.3.2, 4.1 A009

Key Personnel Roster

DI-MGMT-81834 5 calendar days after Contract

Award. (Updates should be included in the MSR

(reference Para. 4.2)

4.2, 4.1, 4.3 A010 Monthly Status Report (MSR)

DI-MGMT-80368A 5th calendar day of each month (except first month)

2.3.4, 4.3 A011

Project Planning Chart

DI-MGMT-80507 First submission shall be 30 days from contract award.

Updates should be included in

MSR (reference para 4.3).

7.2 A012 Quality Management System-

Quality Program Plan

DI-QCIC-81722 First submission shall be 15 days after contract award.

7 CONTRACT REQUIREMENTS

7.1 Government Surveillance/Inspection

In accordance with IAW DoDI 5000.72 and the DFARS PGI 201.602, the Government has the right to inspect all services called for by the contract, to the extent practicable at all times and places during the term of the contract. The Government will perform inspections and tests in a manner that will not unduly delay the work. This will not relieve the Contractor of responsibility for providing adequate quality control measures or from any contract requirement. The

Government will ensure Contractor performance is effectively monitored and documented.

The Air Force Sustainment Center Software Directorate Procurement (AFSC/SWP) office shall periodically evaluate the Contractor’s performance by appointing a Primary and Alternate

Contracting Officer Representative (COR) for the contract. The Government has the option to request a meeting with the Contractor at any time to discuss Contractor performance. The

Contractor shall comply with all Government inspection efforts.

7.2 Quality Management System (QMS)

The Contractor shall ensure the quality of deliverables through a quality control and inspection system. Within 15 days of contract award, the Contractor shall submit a Quality Program Plan

(QPP) addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. 100% compliance with the QMS is required. (CDRL A012, DI-QCIC-81722, Quality Program Plan)

7.3 Quality Assurance

7.3.1 The AFSC/SWP office will perform assessments of the contractor’s performance.

Subsequent to contract award, specific name and contact information of the AFSC/SWP office, with a letter defining duties and authority will be furnished to the contractor.

7.3.2 The AFSC/SWP office will inform the contractor in person when discrepancies occur and will request corrective action. The AFSC/SWP office 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.

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

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

7.4 Government Provided Property, Support, And Information.

Government Provided Property, Support, And Information is not required for this effort.

7.5 Travel

There is no travel required by the Contractor for this contract.

7.6 Program Management

7.6.1 Contractor Program Manager

The Contractor shall provide the necessary resources and infrastructure to manage and administer this contract. The Contractor shall provide a Program Manager (PM) who shall be the single point of contact responsible for Contractor personnel, including all administrative duties of Contractor personnel, and act…