Draft_PWS_Gap_Analysis_3-Dec-20.docx

DRAFT

DRAFT

PERFORMANCE WORK STATEMENT

FOR

402d SOFTWARE ENGINEERING GROUP

GAP ANALYSIS FOR AN/APG-81 RADAR SYSTEM SOFTWARE SUSTAINMENT

3 December 2020

1.0 DESCRIPTION. The purpose of this requirement is for a Contractor to provide support to identify requirements, tasks, data, deliverables, and infrastructure required for the 402d Software Engineering Group (402 SWEG) at Robins Air Force Base (AFB), Georgia to establish software sustainment capability for the F-35 Joint Strike Fighter (JSF) AN/APG-81 Radar System Technical Refresh (TR) 2 Operational Flight Program (OFP). The Government will establish and lead a gap analysis team with the Contractor, who shall provide the necessary data and support.

1.1 Period of Performance. The total contract period of performance shall consist of a 20-business day phase-in period, a 120-business day execution period, and a 45-business day phase-out period.

Note: The total contract period of performance shall not be extended due to COVID-19 related issues, and site visits shall not be substituted by teleconferencing or through online collaboration unless mandated by Federal, State, or local directives.

1.1.1 Phase-In period. The phase-in period shall begin on contract award date and end 20 business days after award date. The following tasks shall be accomplished during the phase-in period:

1.1.1.1 The Contractor and 402 SWEG shall identify key personnel for the contract, including participants of the site surveys. Key personnel shall review requirements and deliverables of the contract.

1.1.1.2 402 SWEG personnel will acquire the proper security clearances and visitation requirements necessary to assess the AN/APG-81 Radar software sustainment capabilities at the Contractor’s facilities. The Contractor shall identify all security and visitation requirements for the site visit to the Contractor’s facility. The Contractor’s security team shall assist 402 SWEG personnel to verify and/or obtain all security clearances and visitation requirements prior to arrival.

1.1.1.3 The Contractor shall be prepared to participate in a 402 SWEG led kick-off meeting within five (5) business days after period of performance start date. This meeting will be held virtually.

1.1.1.4 The Contractor shall onboard a minimum of two (2) 402 SWEG selected engineers so that they may access Contractor Radar OFP facilities and integrate with the Contractor OFP development teams. The following onboarding procedures shall be accomplished for each employee:

1.1.1.4.1 402 SWEG personnel will work with the Contractor to accomplish any missing security requirements needed to access the systems necessary to train on the AN/APG-81 Radar OFP.

1.1.1.4.2 Personnel orientation and facilities access requirements necessary to integrate with the Contractor AN/APG-81 Radar OFP development teams.

1.1.1.4.3 Appropriate access required for AN/APG-81 networks, code, tools, hardware, labs, tech data, and email. Included are all of the necessary items for the engineers to train on the radar system.

1.1.1.4.4. Work space and resources to train 402 SWEG engineers to work on APG-81 tasks. (e.g. desk, phone, development stations, unclassified terminals, etc.)

1.1.2 Execution Period. All activities/tasks (excluding phase-in and phase-out periods) shall be completed no later than 120 business days from contract award date.

1.1.2.1 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 60 business days from the start of the Execution Period.

1.1.2.2 A site visit to the Contractor’s facilities shall occur 20 business days after all deliverables are received. Duration of the site visit shall not be longer than 10 business days. There will be a follow-on visit of an additional three business days for resolution of any identified discrepancies.

1.1.2.3 A reciprocal visit by the Contractor to the 402 SWEG shall be completed within 14 business days of completion of the 3-day follow-on site visit to the Contractor’s facilities.

1.1.2.4 All visits shall be coordinated in advance between the 402 SWEG and the Contractor at least 5 days prior to arrival.

1.1.3 Phase Out Period. The phase out period shall be for 45 business days following the 120-day execution period during which the Contractor shall provide reach back for engineering support, procurement, and follow on questions.

1.2 Deliverables.

1.2.1 The 402 SWEG, with input from the Contractor, will develop an agenda and checklist for each area within the List of Deliverables that requires review.

1.2.2 All document deliverables shall be provided on a weekly cadence as documents are produced to the 402 SWEG with final delivery no later than 20 business days before the start of the site visit to the Contractor’s facility.

1.2.2.1 NOTE: Deliverables for the following paragraphs shall be accomplished and delivered within 30 business days after the execution period start date: 1.6.3.1, 1.6.3.2, 1.6.3.3, 1.6.4.1, 1.6.4.2, 1.6.5.1, 1.6.5.3 and 1.6.5.4.

1.2.3 The Contractor shall appoint a team capable of assessing the areas of deliverables. The appointed experts shall support 402 SWEG efforts to produce a site survey report documenting the team’s findings and identify requirements necessary for the 402 SWEG to establish AN/APG-81 TR2 OFP software sustainment capabilities.

1.2.3.1 The appointed personnel shall be fully available to provide support to the 402 SWEG throughout all site visits and throughout the contract period of performance.

1.2.3.2 The Contractor is required to inform the Government of other necessary items not listed that are needed to activate a sustainment facility, and the reason for necessity.

1.2.4 Weekly Status Meetings. The 402 SWEG and the Contractor shall hold weekly 402 SWEG led status meetings to ensure the objectives of the contract are being met. The weekly status meetings shall be held virtually. Sub teams shall be formed to focus on areas of deliverables and report the status and issues at the weekly meetings. The 402 SWEG and the Contractor shall each appoint one representative that will collaborate to address issues elevated by the sub teams.

1.3 Requirements for Specific Types of Deliverables. Deliverables for which these requirements apply will contain the markings (A thru D) in the “Additional Requirements” column of the “List of Deliverables”.

A. Software Document Requirements. For each software deliverable type identified in the list of deliverables, the documentation provided by the Contractor shall include the following details:

1. Include version numbers, checksums, classification levels, and security requirements.

2. Identify target hardware and operating systems.

3. A detailed description of usage and how the item is used to develop, implement, and test software requirements.

4. Identify software license agreement and owner of each piece of software.

5. If software is commercial, identify the vendor, and purpose.

6. Identify the configuration management process.

7. Identify modern dependencies such as cloud computing and machine learning.

8. Identify current and future planned OS, software, tool upgrades, and changes to be applied to networking environments.

9. Identify any applicable standards.

B. Equipment Document Requirements. For each equipment deliverable type identified in the list of deliverables, the documentation provided by the Contractor shall include the following details:

1. Dimensions, weight, cooling, electrical requirements, and storage classification level.

2. Document planned and expected lab equipment obsolescence and provide details of established sustainment and replacement plans.

3. Identify specialized and customized equipment configurations

4. Identify current and future planned equipment upgrades due to either capability requirements or obsolescence replacements.

5. Identify all commercial items and the supplier

6. A detailed description of usage of how the item is used to develop, implement, and test software requirements.

C. General Document Requirements. For each document deliverable type identified in the list of deliverables, the documentation provided by the Contractor shall include the following details:

1. Version numbers

2. Classification level

3. Document/database type

4. Method of access

5. Description of purpose

6. Document/database owner

7. Configuration management strategy

8. Include details for referenced documents.

9. A detailed description of usage of how the item is used to develop, implement, and test software requirements.

10. The Contractor shall also provide an electronic copy of each identified document, unless it is an openly available standard or military specification.

D. Non-Commercial Software. For non-commercial software, the Contractor shall include the following details:

1. Identify source code

2. Identify executable(s)

3. Identify build procedures

4. Identify Operating System (OS) used

5. Identify any unique host requirements

6. A detailed description of usage of how the item is used to develop, implement, and test software requirements.

7. Identify the data rights asserted and the basis for the assertion.

1.4 Electronic Delivery Method. The Contractor shall format items developed for the Government in Microsoft Office Open XML standards. If the item requires tools or software to open/view not readily available to the Government, the Government will inform the Contractor. The Contractor will reformat using available formats such as Microsoft Office Open XML standards or Adobe PDF.

1.5 Verification Methods. The following verification methods (1, 2, and 3) will be used by the Government to assess deliverables:

1 - Contractor site verification by organic team augmented with Contractor subject matter experts.

2 - Review of received documentation by organic team augmented by Contractor subject matter experts.

3- Technical inquiries and/or interviews with Contractor subject matter experts.

1.6 List of Deliverables. The Contractor shall provide the following information to the 402 SWEG:

PERSONNEL AND BASE SUPPORT

1.6.1 Personnel and Base Operating Support. The Contractor shall provide documentation containing the following information:

(CDRL A001, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.1.1 Personnel and skillsets required for OFP software sustainment.

· Identify the current Full-time Equivalent (FTE) staffing for OFP, test, management, network, configuration, security, and other supporting roles.

· Identify responsibilities for each role.

· Identify the type and number of personnel that regularly work at the prime integrator’s facilities for build and integration support

· Identify the personnel responsibilities levied upon the Contractor in support of test and qualification at the prime integrator.

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

· Identify typical travel schedules

· Identify amount of personnel permanently staffed at the prime integrator’s facilities dedicated in part or full to these projects. Identify the staff primarily assigned to sustainment

· Identify personnel responsibilities levied upon the Contractor in support of test and qualification at the prime integrator.

1.6.1.3 A list identifying software change requests from the most recent block cycle.

· Identify number of FTE staff required.

· Identify number of labor hours.

· Identify rework time of defects and phase of discovery.

FACILITIES

1.6.2 Facilities Management. The Contractor shall provide documentation containing the following information:

(CDRL A002, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.2.1 Detailed requirements for management/engineer workspaces.

1.6.2.2 The classification level of workspaces for each developer and support role.

· Identify if a role may require workspaces at multiple classification levels.

· Identify if a role may require intermittent access to specific classification levels and estimated occurrence of required access. (e.g. daily, weekly, etc.)

1.6.2.3 Physical facility requirements that are required to support AN/APG-81 software sustainment.

· Identify space requirements for each classification level necessary to support the program.

1.6.2.4 Communications requirements necessary to support AN/APG-81 software sustainment.

· Identify the need for secure teleconferencing lines required to support.

· Identify virtual teleconferencing and security levels required to support.

1.6.2.5 Security. Physical security requirements that will be levied upon the 402 SWEG software complex in support of software sustainment.

· Identify security levels required for development, testing, and delivery for each required lab space, communications room, and developer workspace.

· Identify special security measures required for access to F-35 development facilities and labs to be located at Robins AFB.

· Identify current physical security measures in place at the Contractor’s facility that will be required at Robins AFB.

INFORMATION TECHNOLOGY (IT) AND NETWORKING

1.6.3 Network Topology. The Contractor shall provide documentation containing the following information:

(CDRL A003, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.3.1 Detailing network connectivity necessary to support the software sustainment effort of the AN/APG-81 Radar system.

· Identify networks and classification level to support software sustainment.

· Include connections that may be required with other OEMs and the prime integrator.

· Identify unique data transfer methods to the prime integrator necessary to support the software development environment.

· Provide network documentation including topologies, data flow, ports protocols and services (PPS), data diodes.

· Identify bandwidth requirements for each identified network.

· Identify Voice over Internet Protocol (VoIP) requirements for each network.

· Identify the Owner and Operator of each network (i.e. Contractor-Owned Contractor-Operated, Government-Owned Contractor-Operated, and Government-Owned Government-Operated).

1.6.3.2 Detailing enclave networks that 402 SWEG personnel will be required to support within the 402 SWEG facility.

· Identify bandwidth requirements for each identified network.

1.6.3.3 Identify personnel and skillsets necessary to initiate networking between 402 SWEG facilities and the OEM.

· Identify key points of contact (POCs) for each identified network.

· Identify Contractor certification requirements.

1.6.3.4 Equipment. Provide a list of specific equipment necessary to support each network configuration including encryption hardware.

1.6.3.5 Provide a list of digital storage requirements.

· Identify required digital storage amount.

· Identify digital storage classification level.

· Identify backup and archival requirements.

1.6.3.6 Software Tools. Identify network software tools required in support of APG-81 development, test, and delivery functions.

· Identify software tools required for network monitoring.

· Identify network administering software tools.

· Identify software tools required for securing networks.

· Identify software tools required for network support.

· Identify software tools required for network operations.

1.6.3.7 Identify non-commercial software used for networking and IT.

1.6.3.8 Storage. Detailing network storage requirements to support AN/APG-81 software sustainment.

· Identify physical storage requirements for networking support equipment.

· Identify physical storage requirements for spare networking support equipment.

· Identify the classification level of each storage space.

· Identify data storage requirements to support software development.

· Identify data storage requirements to support lab and flight test instrumentation data.

· Identify data storage requirements to support documentation and configuration management functions.

· Identify classification requirements for storing required data types.

LAB ENVIRONMENT

1.6.4 Infrastructure. The Contractor shall provide documentation containing the following information:

(CDRL A004, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.4.1 Detailing laboratory requirements including, but not limited to, floor space, accessibility, electrical requirements, cooling, environmental control, and classification.

1.6.4.2 Equipment. Detailing equipment/Software Integration Lab (SWIL) requirements necessary to support AN/APG-81 software sustainment.

· Identify an equipment configuration providing minimum viable support baseline for organic software sustainment.

· Identify specialized test stations and equipment needed to develop and test software for the AN/APG-81 sustainment configuration.

· Identify a delta equipment configuration with respect to the minimum viable support baseline defining additional equipment that may enable the 402 SWEG more effectively develop, integrate or test the AN/APG-81 software.

· Identify use cases and benefits of additional recommended equipment.

· Identify required support equipment including breakout boxes, data recorders, oscilloscopes, real-time spectrum analyzers, and computer systems including vendor and equipment part numbers.

1.6.4.3 Detailing sustainment and operations details necessary to support the SWIL.

· Identify maintenance and support information including stock information for Line Replaceable Unit (LRU), Shop Replaceable Unit (SRU), and cable assemblies to maintain the facility identified in 1.6.4.2.

· Identify the repair process for SWIL assets identified in 1.6.4.2 and designated “throwaway” items as such.

· Document planned and expected lab equipment obsolescence.

· Identify upgrade plans, details of established sustainment, and replacement plans.

1.6.4.4 Detailing modeling and simulation requirements necessary to support AN/APG-81 SWIL.

· Identify models and specialized software that must be maintained.

· Identify models and specialized software that must be delivered to OEMs and/or the prime integrator.

· Identify simulation capabilities used in the development and test of AN/APG-81 software

· Identify simulations created in-house used to test AN/APG-81 software before SWIL test.

· Identify simulations created in-house by third parties used to test AN/APG-81 software before SWIL test.

· Identify radar performance requirements that are verified using simulation capabilities versus hardware in the loop.

· Identify the fidelity of the simulations used to test Radar and dependent/interoperating subsystems.

· Identify how each model is maintained and the method of validation.

· Identify the software architecture of the simulation environment.

· Identify all CSCIs, firmware modules, and source code.

· Identify target hardware for each CSCI and firmware module.

· Identify the tools, compilers, databases, and models by simulation CSCI.

1.6.4.5 Detailing data collection methods used in the lab and flight test.

· Identify delivery methods from outside sources, such as the prime integrator and the flight test community.

· Identify hardware required for processing and collecting radar data from the lab and flight test

1.6.4.6 Identify non-commercial tools, models, databases, datasets, firmware, and simulations necessary to support, operate, and test the AN/APG-81 SWIL.

· Identify all simulation and emulation CSCIs, firmware modules, and source code.

· Identify target hardware for each simulation and emulation CSCI and firmware module.

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

1.6.4.7 Storage. Detailing lab storage requirements that will be required to support AN/APG-81 software sustainment.

· Identify physical storage requirements for spare and support equipment not identified above; including the classification level of each storage space.

· Identify data storage requirements to support software development, lab and flight test instrumentation data, documentation, and configuration management functions.

· Identify classification requirements for storing required data types.

1.6.4.8 Software Tools. Detailing software tools including, but not limited to, scenario generators and build loaders required to use lab resources for development, test and delivery of AN/APG-81 software.

· Describe how each item is used during the development process.

· Identify the target hardware for each software tool.

· Identify the tools, compilers, databases, and models by simulation CSCI. Identify software tools and process required to record and analyze data. Identify software tools required from OEM and/or prime integrator.

· Identify the delivery method and frequencies of these updates.

1.6.4.9 Identify noncommercial software used for software tools including, but not limited to, scenario generators and build loaders required to use lab resources for development, test and delivery of AN/APG-81 software.

1.6.4.10 Equipment Tools. Provide a list of specialized and custom tools required to support the SWIL equipment.

· Identify tool sourcing if acquired by an external vendor.

· Identify tools and drawings for tools built in-house.

· Identify expected acquisition process and procedures for each tool.

1.6.4.11 Technical Data. Provide lab technical data and documentation pertaining to the development, maintenance, upgrade and expansion of the SWIL.

· Identify deliverable technical data package detailing the equipment and connectivity within the SWIL.

· Include editable CAD files in AutoCAD dwg format.

· Include signal names throughout equipment environment.

· Provide drawing tree organization of drawings.

· Include aircraft wiring diagrams and interface documents relevant to the AN/APG-81 system.

· Include connector parts numbers and cable wiring diagrams for lab equipment.

· Include operations manuals, technical drawings, block diagrams, interface documents, theory of operation.

· Include formal qualification test (FQT) procedures and test reports for the current AN/APG-81 SWIL.

CD or DVD 2,3

SOFTWARE DEVELOPMENT

1.6.5 The Contractor shall provide documentation containing the following information:

(CDRL A005, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.5.1 Software Architecture. An overview of the AN/APG-81 software Architecture.

· Identify all software CSCIs and firmware modules that reside on the AN/APG-81.

· Identify the software units that makeup each CSCI and firmware module.

· Show the static relationships of the software units.

· State the purpose of each software unit.

· Identify all source code modules, databases, and data sets for each CSCI and firmware module.

· Identify all Interface Control Documents for the subsystem.

1.6.5.2 Identify all AN/APG-81 source code, databases, datasets, and firmware.

1.6.5.3 Life Cycle Practices. Provide documentation on software development life cycle.

· Identify software development processes for implementing, building, and testing OFP code.

· Identify software testing strategy (i.e. test-driven development, unit test, integration test, regression test)

· Identify how test code is checked-in and vetted for lab testing.

· Identify process for developer to access Radar test bench.

· Identify code repository, version control, and management processes used to manage developmental, test, and production code.

· Identify classification levels used at each phase of the software development life cycle

1.6.5.4 Provide documentation on external dependencies within the software development life cycle.

· Identify dependencies to the prime integrators and other program stakeholders.

· Identify the delivery processes to and from third parties for tools, models, and software.

· Identify integration events that occur with third parties prior to SWIL testing.

· Identify the release process for delivery of software to the prime integrator and other stakeholders to whom deliveries are provided.

· Identify types of software releases and the details of the technical data package that is required for each release type.

1.6.5.5 Provide documentation on current and future software modernization practices that are and will be used for OFP software sustainment.

· Identify modern software practices (i.e. Agile, DevOps) that have been applied and plan to be applied to the OFP development lifecycle within the next 24 months.

· Identify software development, integration, and delivery automation pipelines that are currently in use and planned to be used within the next 24 months.

· Identify opportunities for remote collaboration between 402 SWEG personnel onsite at Robins AFB and Contractor OFP development, test and support teams.

1.6.5.6 Equipment. Provide list of baseline equipment required to support the software development environment for full OFP development including development, integration, build, and test of software requirements.

· Identify unique and proprietary hardware.

· Identify unique hardware interfaces.

· Identify the configuration of each item including hardware and software components, models, and version information.

1.6.5.7 Software Tools. Detailing tools and services necessary to support the software development environment for full OFP development including development, integration, build, and test of software requirements.

· Identify specific software applications used for source code development and modification.

· Identify specific IDE and versions used for source code compiling and/or building.

· Identify specific test suites and languages used for developing unit and/or integration tests.

· Identify how each tool and service is used during the development, integration, build and test of software requirements.

1.6.5.8 Identify non-commercial software necessary for development, integration, build, and test of software requirements.

1.6.5.9 Detailing simulations, emulations, and utilities necessary for development, integration, build and test of software requirements.

· Identify software license agreements and owner of each tool.

· Identify applicable standards that each item follows.

· Identify how each simulations, emulations, and utilities are used during the development, integration, build and test of software requirements.

1.6.5.10 Identify non-commercial simulation, emulation, and utility products necessary for development, integration, build, and test of software requirements.

1.6.5.11 Detailing automated test capability currently used to perform unit and lab testing in support of APG81 software development and test.

· Identify automated test capability language and interfaces

· Identify future updates to automated test capabilities

· Identify how automated test scripts are configuration managed and tied into testing requirement

1.6.5.12 Detailing scripts, datasets, databases, and firmware necessary for development, integration, build, and test of APG-81 and supporting software.

1.6.5.13 Identify noncommercial software used for scripts, datasets, databases, and firmware.

1.6.5.14 Detailing data collection methods used in the lab and flight test.

· Identify delivery methods from outside sources, such as the prime integrator and the flight test community.

· Identify software tools and processes required to record and analyze data.

· Identify hardware required for processing and collecting radar data from the lab and flight test.

1.6.5.15 Document planned and expected obsolescence of tools and provide details of established sustainment and replacement plans.

1.6.5.16 Technical Data. Detailing technical data required to develop, integrate, build, and test AN/APG-81 OFP software requirements.

· Include programming manuals, coding standards, technical drawings, block diagrams, interface documents, requirements documents, DR/PR documents

TRAINING

1.6.6 The Contractor shall provide documentation containing the following information:

(CDRL A006, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.6.1 Provide a list of System Level training and familiarization necessary to support the software sustainment effort of the AN/APG-81 Radar system. If the training is Contractor developed, provide a copy of the training material with the list of required training.

1.6.6.2 Provide a list of training to support the Software Integration Laboratory and hardware maintenance necessary to support the software sustainment effort of the AN/APG-81 Radar system.

1.6.6.3 Provide a list of training necessary to support software change management, requirements analysis, requirements traceability, deficiency investigation, etc.

1.6.6.4 Provide a list of training necessary to support the AN/APG-81 Radar software development environment and software toolsets.

1.6.6.5 Provide a list of training necessary to support AN/APG81 Radar software integration and testing including, but not limited to, unit testing, independent validation & verification, software integration testing, and development/operational flight-testing.

1.6.6.6 Provide a list of training necessary to support the analysis of test data provided by, but not limited to, the prime integrator, flight-test recordings, test-range data, etc.

1.6.6.7 Provide a list of training necessary for 402 SWEG personnel to support configuration management and project management activities.

1.6.6.8 Provide a list of upcoming JSF and AN/APG-81 specific training and familiarization opportunities that may be beneficial to 402 SWEG personnel within the next 12 months.

OPERATIONS AND PROCESS

1.6.7 The Contractor shall provide documentation containing the following information:

(CDRL A007, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.7.1 Security. Detailing program security requirements that will be levied upon 402 SWEG personnel in support of software sustainment.

· Identify Contractor personnel responsible for administering program security protocol.

· Identify and provide copies of documents and guidelines for each program security requirement.

1.6.7.2 Program Management. Detailing program management responsibilities that will extend to the 402 SWEG in support AN/APG-81 software sustainment.

· Identify meetings where 402 SWEG attendance will be required to support program management.

· Identify regular interactions that should occur between 402 SWEG program management personnel and the OEM, the Joint Program Office, and/or the prime integrator.

· Identify potential entry points for 402 SWEG support within the existing software change management process.

· Document the change process for performing interface changes with and in support of changes to other subsystems.

· Identify opportunities for 402 SWEG personnel to be involved in software design reviews and software test events within the next 24 months.

1.6.7.3 Configuration Management. Detailing configuration management requirements necessary to support AN/APG-81 software sustainment and to allow 402 SWEG personnel collaboration within the OEM’s and the prime integrator’s development environment.

· Identify software and online tools necessary to support software and documentation configuration management.

· Provide a list of documentation and databases that the 402 SWEG will be expected to maintain configuration management over.

· Identify meetings 402 SWEG attendance will be required to support software configuration management and network configuration management.

· Identify methods and tools used for real-time information flow between Contractor, the prime integrator, JPO and other stakeholders

· Include version numbers, hash values, classification levels, security requirements, required OS versions, and a description of usage.

· Identify each piece of software as commercial, Government owned, proprietary, open-source.

· Identify the configuration management process for non-commercial tools.

1.6.7.4 Quality. Detailing quality standards that must be followed for integration of OFP builds in to prime integrator facilities and air and ground testing.

· Identify tasks that would be the responsibility of 402 SWEG for software sustainment.

· Identify and provide copies of existing documentation and guidelines for each standard.

1.6.7.5 Cybersecurity. Detailing the Cybersecurity certification requirements and process for the AN/APG-81 Radar OFP.

· Identify tasks that would be the responsibility of 402 SWEG for software sustainment.

· Identify and provide copies of existing documentation and guidelines for each certification requirement.

1.6.7.6 Airworthiness. Detailing the Airworthiness certification requirements and process for the AN/APG-81 Radar OFP.

· Identify tasks that would be the responsibility of 402 SWEG for software sustainment.

· Identify and provide copies of existing documentation and guidelines for each certification requirement.

1.6.7.7 Detailing external audits and/or external reviews that are required to evaluate integration and flight Airworthiness of the AN/APG-81 Radar OFP.

· Identify tasks that would be the responsibility of 402 SWEG for software sustainment.

· Identify and provide copies of existing documentation and guidelines for each review/audit process.

1.6.7.8 Environmental, Safety and Occupational Health (ESOH). Detailing ESOH requirements and hazards necessary to support an AN/APG-81 radar integration and test facility.

· Identify RF hazard and safety Mitigations used in OEM facility for radar transmission.

· Provide copies of applicable documented standards that are followed by the Contractor.

1.6.7.9 Detailing HAZMAT procedures necessary to perform support operations for an AN/APG-81 radar integration and test facility.

· Identify HAZMAT procedures associated with PAO and other hazardous materials used at OEM facility

· Provide copies of applicable documented standards that are followed by the Contractor.

TECHNICAL DATA

1.6.8 The Contractor shall provide documentation containing the following information:

(CDRL A008, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.8.1 System Technical Data. Provide documentation containing system architecture and configuration data for the AN/APG-81 system.

· Identify system level documentation including flight manuals, interface documents, system illustrated parts breakdowns specifications, system diagrams, wiring diagrams, system requirements specifications, software design descriptions, interface requirements specifications, interface design documents, interface control document, prime item development specifications, and operations and maintenance diagrams.

· Include documentation for functional, operational, and interface requirements and requirements traceability matrix (RTM) of the most recent AN/APG-81 operational flight configuration.

· Include formal qualification test procedures and test reports for the most recent AN/APG81 operational flight configuration.

ON-BOARD TRAINING REQUIREMENTS

1.6.9 The Contractor shall provide documentation containing the following information:

(CDRL A009, DI-MISC-80805/T, Technical Report–Study/Services)

1.6.9.1 System Technical Data. Provide a list of recommended training plan goals for Government Radar engineer trainee at the Contractor facility.

2.0 SERVICES SUMMARY.

2.1 Government Surveillance/Inspection. In accordance with FAR clause 52.246-4, the Government has the right to inspect and test 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.

2.1.1 The Government Contract Surveillance Management Office (CSMO) 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.

2.1.2 The Contractor shall provide effective support with an emphasis on overall success and positive impact to SWEG mission objectives. The Contractor shall perform each PWS paragraph error free without complaint 95% of the time, and shall ensure the remaining 5% is resolved within five (5) workdays.

3.0 GOVERNMENT PROVIDED PROPERTY, SUPPORT, AND INFORMATION.

3.1 Government-Owned and Government-Managed Information. The Government will furnish or make available to the Contractor any Government-owned and Government-managed technical information or guidance as required for the performance of the contract. All Government Furnished Information (GFI) shall remain property of the Government. The Contractor shall comply with applicable FAR and DFARS clauses in the contract and the terms of this PWS regarding the use and dissemination of this information.

3.2 Government Property and Information Protection. The Contractor shall apply appropriate security measures to protect Government property and information from unauthorized or unlawful disclosure or loss, and shall protect from disclosure any proprietary information or intellectual property that has been provided for use under Government purpose rights. The Contractor shall ensure that any proprietary information or intellectual property provided by the Government is used only for Government purposes.

3.3 Publicly Available Information. The Government will not furnish information that is publicly available, whether by unrestricted public access or by purchase in the commercial marketplace.

3.4 Contractor Produced Data/Information. All documents, notes, records, software tools developed, and/or software produced by the Contractor to fulfill the requirements of this PWS shall become the property of the Government. The Government will have unlimited rights to all data/materials and will determine the scope of publication and distribution. The Contractor shall be required to deliver electronic copies of all documents, notes, records and software to the Government upon termination of the contract services or expiration of the contract period.

3.5 Supply Chain Risk Management. The Contractor shall implement risk management procedures to ensure that system, equipment, components, software, maintenance equipment, and supplies do not incorporate counterfeit parts, malicious code, or other elements that would allow adversaries to gain access to data and critical program information and disrupt operations. Contractor risk management procedures shall comply with Air Force Pamphlet (AFPAM) 63-113, Program Protection Planning for Life Cycle Management, SAE Aerospace Standard AS5553, Counterfeit Electronic Parts: Avoidance, Detection, Mitigation, and Disposition, and National Institute of Standards and Technology (NIST) Special Publication 800-53, Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations.

4.0 GENERAL INFORMATION.

4.1 Government Program Manager. The 402 SWEG Government Representatives are the Government’s points of contact for this requirement. The Government Representative’s will provide technical oversight of the Contractor's performance, and report any performance problems to the Contracting Officer. Government Representatives will not supervise the Contractor, and they are not empowered to make any contractual commitments or authorize any contractual changes on the Government’s behalf. The following individual(s) will serve as Government Representatives for this contract:

SWEG Government Representative (Primary) SWEG Government Representative (Alternate)

4.2 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 as a liaison to the Government for contract performance matters. The name and phone number of the Contractor’s PM shall be provided in writing to the Contracting Officer and Government Representatives no later than five (5) business days after contract award date.

4.2.1 The Contractor’s PM shall acknowledge Government technical inquiries within two (2) business days of receipt and shall provide a response within five (5) business days of receipt.

4.3 Contractor Management Responsibilities.

4.3.1 The Contractor shall retain responsibility for any teaming partner or subcontractor and shall be accountable for their performance.

4.3.2 The Contractor shall comply with all established policies, operating instructions, and regulations relating to the performance of assigned duties. These include environmental, health, safety, and security compliance measures.

4.3.3 The Contractor shall not employ persons on this contract if such employee is identified to the Contractor as a potential threat to the health, safety, security, and/or general wellbeing to 402 SWEG operations. All Contractor employees shall conduct themselves in a professional, courteous manner.

4.3.4 The Contractor shall ensure all Contractor employees possess the required training, qualifications, proficiency, and security clearances necessary to satisfy all contract requirements.

4.3.5 The Contractor shall develop and submit all required information and deliverables in accordance with contract requirements and timelines.

4.3.6 The Contractor shall not perform any work outside the scope or requirements of this PWS without the express written approval of the Contracting Officer.

4.3.7 Contractor personnel shall wear visible identification designating them as Contractors at all times while on Robins Air Force Base. Contractor personnel, whether prime or Subcontractor are not authorized sponsorship privileges.

4.4 Clarification Responsibility. The Contractor has the responsibility to clarify direction received from the Government. In the event the Contractor has questions regarding the PWS or information critical to the success of the contract, the Contractor shall seek clarification from the Contracting Officer.

4.5 Personnel Limitations. The Contractor shall not utilize any foreign persons in the processing of work under this contract. Only U.S. persons shall have access to either technical data or defense articles. A U.S. person is defined as a U.S. citizen (whether naturalized or native born) or a permanent resident (green card holder). Foreign persons with work or student visas do not qualify as U.S. persons. A foreign person is any person that either is not a U.S. person or has not been verified to be a U.S. person.

4.6 Non-Personal Services. This is a non-personal services contract as defined in Federal Acquisition Regulations (FAR) clause 37.101. The Contractor shall comply with the terms and conditions of the contract, but Contractor employees are not employees of the Government and shall be free from Government supervision with respect to the manner or method of performance of the services specified. The Contractor shall manage and administer the work required and bear sole responsibility for complying with all technical, schedule, or financial requirements or constraints related to the performance of the contract.

4.7 Place of Performance and Operating Hours. The Contractor shall perform services in building 229 at Robins AFB. Normal operating hours shall be 7:30 am to 5:00 pm (Eastern Time) Monday through Friday. The Contractor shall only be permitted access to Government facilities when Government personnel are present. The following Federal holidays are observed by Government personnel: New Year’s Day, Martin Luther King Day, President’s Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving, and Christmas. If the holiday falls on Saturday, it is observed on Friday. If the holiday falls on a Sunday, it is observed on Monday. Local and/or Robins AFB procedures will be followed during inclement weather.

4.8 Travel. In the event Contractor travel is required in support of these services, it shall be authorized in advance by the Contracting Officer prior to costs being incurred. Travel by Contractor personnel shall be conducted in accordance with the Joint Travel Regulations (JTR), and applicable supplements. The Contractor shall make its own travel and lodging arrangements, and receipts must be presented with the invoice for reimbursement of travel costs.

4.9 Security Requirements.

4.9.1 Government Security Regulations. The Contractor shall ensure personnel, information, system, facility, and international security requirements are met in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and Air Force Instruction (AFI) 31-101, Integrated Defense.

4.9.2 Security Clearance. Security clearance requirements for this contract are SECRET and SECRET/Special Access Program (SAP). The security clearance eligibility for each Contractor employee must be verified by the 402 SWEG Security Office prior to Contractor employees beginning work. Access to and familiarity with Joint Personnel Adjudication System (JPAS) and Defense Information System for Security (DISS) is necessary for processing clearance requests. Refer to the associated DD Form 254, Department of Defense (DoD) Contract Security Classification Specification for security requirements.

4.9.2.1 Contractor personnel shall not be authorized access to classified information or work on classified projects or programs without a valid security clearance. Contractor personnel whose clearances have been suspended or revoked shall be denied access to classified information and defense articles.

4.10 Communications Security (COMSEC). The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified and/or sensitive, but unclassified, information in accordance with DoD 5220.22-M.

4.11 Operations Security (OPSEC). The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with OPSEC requirements including procedures to protect classified and/or sensitive, but unclassified, Government projects and/or programs. The Contractor shall ensure Contractor personnel who perform work at Robins AFB or another Government facility comply with the OPSEC procedures of the facility.

4.12 Security Incident or Violation. The Contractor shall immediately notify the Government Security Office of any potential or actual security incidents or violations including potential or actual unauthorized disclosure or compromise of classified and/or sensitive, but unclassified, information.

4.13 Requirement for Contractor Credentials. All Personnel requesting installation Contractor credentials must present a valid state issued identification card or driver's license and a social security card before they will be issued a credential. If Contractor employees are not a US citizen, they must possess proof showing they are allowed to work in the United States/Georgia. Persons must present a previously issued Contractor identification card if applicable.

4.13.1 The Air Force has mandated visitors, to include all non-DOD cardholders, to consent to a check of their criminal history prior to being allowed access to installations. The check is similar to a driver’s license check and will be conducted at the Visitor Control Center (VCC) off Watson Boulevard, Robins AFB, GA. Unescorted visitors will need their driver’s license or state-issued ID, and a social security card, which will be checked by name, dates of birth and social security number.