JSSMO PWS FOLLOW ON - 06 Feb 2025.pdf

Joint Service System Management Office (JSSMO) Global Positioning System (GPS) User Equipment (UE) System Support

Performance Work Statement 23 January 2026 – 22 January 2031

1. INTRODUCTION/BACKGROUND

The Air Force Life Cycle Management Center (AFLCMC) Joint Service System Management Office (JSSMO) manages systems to provide precise position, navigation, and timing information to a variety of Department of Defense (DoD) weapon systems. These systems include but are not limited to the Software Defined User Equipment (SDUE), Miniaturized Airborne GPS Receiver (MAGR) 2000, Embedded GPS/Inertial Navigation System (EGI), Defense Advanced GPS Receiver (DAGR), GPS Antenna System 1 (GAS-1), Advanced Digital Antenna Production System (ADAP), GPS Antennas, Antenna Electronics (AE), Resilient Embedded GPS/INS (R-EGI), Air Force Vanguard Transition programs, and alternative navigation capabilities. Some systems are in initial development and many of these systems are undergoing significant modernization efforts to respond to new threats, improve supportability, improve long-term resiliency, and adopt open architecture standards, and digital engineering best practices. Modernization efforts are underway for both the MAGR-2K and the EGI receiver systems in support of aircraft modernization efforts. Additionally, R-EGI and SDUE are in rapid development using innovative acquisition approaches.

2. SCOPE

This work scope provides Contractor Support Services and Studies and Analysis (S&A) to the Multi-Global Navigation Satellite Service (GNSS) User Equipment (EU) Systems, and Assured Position, Navigation, and Timing (PNT) and related programs.

This requirement will provide support services including, but not limited to, rapid response modernization acquisition and sustainment planning; program startup planning; manpower analysis; sustainment and production support; Foreign Military Sales future planning; Test & Evaluation (T&E) support; PNT systems, platform and weapons integration; planning and standards development; implementation of open architecture tenants; alternative or complementary navigation application development and integration; development of senior leader advocacy briefings; assured PNT engineering support; cybersecurity; information Assurance; aircraft, weapons and Multi-GNSS receivers and user equipment acquisition integration and planning in support of PNT.

The scope of services for this contract is to provide the services outline in the descriptions below.

3. SPECIFIC TASKS

3.1 Strategic Planning & Program Execution –

3.1.1 Senior Program Management Support

Upon award, the Contractor shall designate one (1) individual to serve as the overall Contractor Program Manager (PM) for the entire task order. The PM shall be responsible for serving as the coordinating single point of contact between the Contractor and Government and hold a Top-Secret clearance. This individual shall be responsible for overall management direction and general support and coordination to the COR (Contract Officer’s Representative) and Government staff, as needed. The PM shall be fully authorized to manage the activities of Contractor and third-party Contractors needed to meet the contract requirements, providing a corporate escalation path for issues that may arise. They will provide both a monthly and an annual report summarizing program accomplishments and overall deliverables. This individual must be available for the duration of the contract and provide the Monthly Status Report (MSR) as detailed below. In addition to the overall PM, the contractor shall provide a site manager to manage the activities under the individual programs. All Program Managers shall have PM level 3 Project Management Professional (PMP) or Acquisition Professional Development Program (APDP) PM level 3 certification and in-depth knowledge of Multi-GNSS programs and the Performance Work Statement (PWS) tasks.

3.1.1.1. Project Management: Manage several concurrent pre-award, modernization, production, and sustainment projects with multiple milestone events and S&A tasks.

Delegate tasks to an on-site task lead, as long as the project complexity can be adequately managed without interfering with routine duties. Manage complex assigned projects; ensure the highest quality standards are met for all deliverables. Identify and mitigate risks. Manage resources (people, costs, risks) to ensure effective and efficient use of all on-site or off-site contractor resources.

3.1.2. Production and Sustainment Support. Provide sustainment logistical, program management, acquisition planning and sustainment engineering support ensuring fleet readiness.

3.1.2.1. Acquisition Support: Develop market research plans and support market research analysis. Develop and staff Early Strategy & Issues Session (ESIS) and Acquisition Strategy Plan (ASP) strategies for new production and sustainment delivery order contracts. Conduct risk analysis and document the results. Assist the Government in developing overall program risk reduction plans. Develop program/project cost estimates. Develop and manage program/project integrated master schedules (IMS) that are resource loaded. Develop technical contract requirements documents for new

Original Equipment Manufacturer (OEM) contractual documents, PWS, Contract Data Requirements List (CDRL), Quality Assurance Surveillance Plan (QASP), etc.). Assist in evaluating OEM provided Engineering Change Proposals (ECPs) and other technical submittals to the government to ensure technical requirements are met by documenting all findings in comprehensive Comment Resolution Matrix’s (CRMs) and ensure proper adjudication of comments with appropriate Government offices.

Participate in OEM program reviews, Technical Interchange Meetings (TIMs), requirements reviews, and other ad hoc meetings as may be required to ensure all contractual documents reflect a sound and comprehensive production & sustainment strategy.

3.1.2.2. Sustainment Engineering: Provide engineering and technical support to Failure Analysis, Deficiency Reports, Diminishing Manufacturing Sources and Material Shortages, and Product Improvements. Evaluate failures and accomplish trend analysis for field failures, review and evaluate deficiencies reported and resolve as required.

Monitor and identify solutions/replacements for part obsolescence. Identify improvements as required for service life extension, technology refresh, and product modernization. Monitor fielded items to ensure Operational Safety, Suitability and Effectiveness of systems are maintained.

3.1.3. Acquisition Planning & Support: The contractor shall provide acquisition planning and program support for the modernization and development programs.

3.1.3.1. Acquisition Planning: Develop acquisition milestone documents to support Acquisition Category (ACAT) I, II, & III Milestone entry at the appropriate decision points.

Develop market research plans and support market research analysis. Develop and staff ESIS and ASP strategies. Conduct risk analysis and document the results. Assist the Government in developing overall program risk reduction plans. Develop program/project cost estimates. Develop and manage program/project integrated master schedules with resource loading. Develop technical contract requirements documents for new OEM contractual documents (PWS, CDRL, QASP, System Requirement Document (SRD), etc.). Assist in evaluating OEM provided ECPs and other technical submittals to the government to ensure technical requirements are met by documenting all findings in comprehensive CRMs and ensure proper adjudication of comments with appropriate Government offices. Participate in OEM program reviews, TIMs, requirements reviews, and other ad hoc meetings as may be required to ensure all contractual documents reflect a sound and comprehensive development program strategy. Manage technical requirements traceability and conduct requirements prioritization analysis.

3.1.3.2. Program Execution Support: Program Execution Support: The contractor shall provide technical and management expertise to support Multi-GNSS UE Pre & Post Design Review efforts, including:

3.1.3.2.1. Evaluating the Modular Open Systems Architecture (MOSA), Multi- Platform Common Core Military Code (M-Code), Common Modular EGI Operational Flight Program (OFP) Baseline Development, and Mission Upgrade Trade Studies against OEM PWS requirements, Technology Maturation and Risk Reduction (TMRR) objectives, and program strategies.

3.1.3.2.2. Assisting the government in meeting programs' acquisition planning efforts, reviewing trade study results and recommendations for robustness in meeting overall modernization efforts, and assessing OEM's experimental results using pre-production M-code receivers to make risk reduction plans.

3.1.3.2.3. Monitoring and evaluating OEM results from the Engineering Study Assets (ESA) with pre-production M-Code receivers, including Legacy Codes (C/A and Y- Code) and M-Code, to ensure no degradation in performance with Legacy Code capability due to receiver modernization.

3.1.3.2.4. Managing and controlling receiver hardware/software configurations to limit configuration proliferation.

3.1.3.2.5. Assisting the government in developing draft contractual documents for OEM follow-on development efforts, including statement of work, CDRLs, Initial Capability Documents (ICDs), and SRD creation, and in the technical evaluation of proposals from EGI OEMs in response to government Requests for Proposal (RFP).

3.1.3.3. Technical Support:

3.1.3.3.1. Test & Evaluation: Develop, optimize, execute and evaluate the testing of system performance, interoperability, reliability, and cybersecurity. Provide expertise in development of test plans and strategies, as well as actively support Integrated Test Team (ITT). Use building block approach to ensure adequate testing from subassembly level to system level is planned coordinated. Ensure combined testing is maximized for system level verification in Developmental Testing and Operational Testing at the Platform level. Review contractor test plans and procedures for compliance with overall program requirements, verification methods and the test plans and strategies. Leverage experience from Navigation Warfare (NAVWAR) Multi-GNSS legacy testing to incorporate lesson learned into test approach. Provide oversight of contractor test execution according to test plans and procedures.

3.1.3.3.2. Platform, Weapons, Multi-GNSS Integration: Support integration of Multi-GNSS and Navigation subsystems into DoD multiservice platforms on predominantly fixed wing and rotor aircrafts. Ensure design, requirements and technical data items support air worthiness certification, security approvals (Authority to Operate) and Military Standard (MIL STD) 1553 messages. Review and verify Interface Control Documents (ICDs) between subsystems and platforms.

Support Platform System Integration Lab (SIL) testing to ensure compliance with ICDs.

3.1.3.3.3. Open Architecture: Recommend potential frameworks for open architecture to ensure faster integration into DoD platforms. Identify key interfaces and data flows and alternative navigation capabilities allowing faster updates to PNT subsystem components in response to evolving threats and technology improvements. Provide expertise in hardware and software partitioning to minimize recertification efforts and regression testing on updated subsystems. Provide recommendations and develop plans pertaining to implementation/compliance with Modular Open Systems Approach (MOSA) and appropriate open standards for development to include Sensor Open Systems (SOSA), Future Airborne Capability Environment (FACE), Open Mission Systems (OMS), VMEbus International Trade Association (VITA), and ASPN.

3.1.3.3.4. Position, Navigation & Timing: Support development of Multi-GNSS and Navigation Subsystems. Accomplish technical review of contractor’s requirements and designs to ensure platform performance is maintained or improved for PNT.

Provide support in navigation, GPS security certification, NAVWAR compliance, Military Standard Order (MSO) certification, airworthiness, multi-GNSS, platform integration, navigation assurance, integrity monitoring, and data/signal coupling.

3.1.3.3.5. Systems Engineering: Translate requirements into design criteria, evaluate alternative design approaches, and develop system specifications. Apply advanced theories, concepts, principles and processes to the acquisition, development, or sustainment of PNT. Performs analysis and integrates technical requirements, directives, and program plans in support of assigned PNT projects/programs. Create, manage, and update requirements documents. Use requirements prioritization system for trade decision during program execution.

Provide recommendations for use of Model-Based Systems Engineering (MBSE) best practices and manage model development. Develop the Systems Engineering Plan (SEP) and all necessary prerequisite documentation to include required appendices.

Support technical design reviews, configuration audits, risk assessments, and other systems engineering processes as defined by the SEP.

3.1.3.3.6. Manufacturing Engineering: Evaluate contractor’s manufacturing readiness. Prepare and Support Manufacturing Readiness Assessment (MRA) in support of program Production Readiness Review and Production Decision. Leverage experience from successful MRAs conducted on multiple Department of Defense development programs.

3.1.4. Receiver, Platform Integration: The contractor shall support receiver and platform integration efforts with DoD Aircraft customers to identify, track and resolve technical requirements and ensure an end-to-end solution. Support platform integration by maintaining awareness of dependencies between existing programs of record, managing a master schedule for delivering PNT capabilities, and informing stakeholders on Position, Navigation, and Timing Program Office’s (PNT PO) programs of record, PNT capabilities that exist, and offer trade space solutions that meet user’s mission.

3.1.4.1. Integration Working Group(s): Coordinate working group meetings. Plan, schedule, and create minutes and action items, track and close action items and report status monthly.

3.1.4.2. Aircraft Integration Scheduling: Coordinate with DoD Aircraft platforms to identify technical requirements and identify developmental and production receiver needs. Develop and maintain cross platform, receiver, and weapons integration master schedules. Develop, coordinate, and maintain an overall platform, receiver, antenna, and weapons roadmaps.

3.1.5. JSSMO S&A:

3.1.5.1. Trade Studies: Conduct engineering and trade studies as required. Trade studies supported shall include as a minimum: (1) Miniaturized Airborne GPS Receiver 2000 Military Code (MAGR-2K-M) Resiliency; (2) Handheld GPS receiver Acquisition Approaches; (3) Operational Safety, Suitability, and Effectiveness (OSS&E); (4) Military GPS User Equipment (MGUE) Source of Supply; (5) Trusted Foundry Requirements; (6) Open Architecture; (7) Antenna Anti-Jam/Anti-Spoof; (8) Alternative Navigation Capabilities on aircraft platforms; and (9) Antenna Modernization Acquisition Approaches

3.1.5.2. Logistics Support Analysis: Support efforts to resolve logistics shortfalls in existing JSSMO GPS receiver systems. Assist in the development of AF contractual documents and upgrade packages (ECPs) to address logistics shortfalls with the OEM’s fielded capability. Evaluate OEM logistic assessments of obsolete parts, diminishing manufacturing sources, Re Test OK (RTOK) and other supportability items for existing fielded systems. Consider the impact of material, training and supply processes to mitigate current logistics challenges. Assess the robustness of existing system performance requirements to meet warfighter logistics needs. Develop acquisition options to address these issues to provide more logistically supportable systems to the warfighter.

3.1.6. Cybersecurity/Information Assurance (IA):

3.1.6.1. The contractor shall support the Cybersecurity JSSMO mission through the execution tasks associated to the integration of the Cybersecurity Risk Management Framework (RMF) into the system acquisition lifecycle. The JSSMO requires integrating cybersecurity activities into existing processes, system security architecture, and data flows. Support analysis of JSSMO systems to find opportunities for increased capabilities to protect, detect, react, and restore from adversary attacks. Support tasks associated to ensuring the continued alignment of cybersecurity across the technical baselines, system security architecture, data flows, and design. Knowledge of the following DoD policies is required:

• Department of Defense Instruction (DoDI) 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT)

• DoDI 8500.01, Cybersecurity

• DoDI 5000.02, Operation of the Defense Acquisition System

3.1.6.2. The contractor shall assist in relevant tasks and assignments in support of the JSSMO Cybersecurity mission to meet statutory, regulatory, and system requirements, balancing lifecycle cost, schedule, system performance, risk, and system security.

3.2. Various Programs Support

3.2.1. Acquisition Program Management Support

3.2.1.1. Contractors will be responsible for providing administrative support services for program management, in accordance with (IAW) applicable contracting and acquisition regulatory guidance. These efforts will serve to assist the Program Office (PO) with the acquisition process. The contractors cannot represent the Government in the acquisition process, and they cannot obligate the government. Contractors must clearly identify themselves as a Contractor in their emails, documents, meetings and conversations. Only the PCO has the authority to make changes or commitments that affect price, quality, quantity, delivery or other terms and conditions of the contract.

Tasks that are not within the scope of this PWS shall be brought to the attention of the

PCO. The contractors shall assist the PO in the acquisition process and satisfy performance objectives by performing the following tasks:

3.2.1.2. Review incoming Purchase Requests (PR) and Military Interdepartmental Purchase Requests (MIPRs) for adequacy and completeness of documentation and availability of funds.

3.2.1.3. Assist in the authoring of Justifications & Approvals (J&As), Statement of Works (SOWs), PWS, market research, Determination & Findings (D&Fs) and other documentation for the PNT-PO.

3.2.1.4. Assist and perform technical evaluations of contract modifications and proposals.

3.2.1.5. Maintain acquisition trackers, Program Office schedules, and financial data and report data as required by the PO via uploads to tracking systems and through briefings.

3.2.1.6. Track, review and report on vendor CDRL deliverables and deliveries.

3.2.2. Key Data Processor Loading & Installation Facility (KLIF) & Integrated Support Facility (ISF) Support The contractor shall provide program management support to assist the Government with sustaining the day-to-day operations in the KLIF and planned future CIC operations

3.2.2.1. The contractor shall assist the Government budgeting and cost accountability to support KLIF/CIC operations for support in programming SAASM/MGUE devices and overall KLIF/CIC performance (local and Mobile). This includes responsibility for processes and management of workload performed. The contractor shall track incoming and outgoing product and assist in program management activities related to programming SAASM (P(Y) Code/MGUE (M-Code) devices as defined by the customer.

3.2.2.2. The contractor shall assist as needed in the management, operation, maintenance, upgrade, roadmap planning, and technology insertion/refresh of the ISF.

3.3 Surge Support: Surge support accomplished under this PWS requirement can include but not limited to tasks outlined below.

3.3.1. Advocacy Briefings & Taskers: Generate execution and advocacy briefings, bullet point papers or white papers to be presented to the Program Executive Officer (PEO), and higher headquarters, as required. Assist, as required, in PNT PO HBC coordination and briefing efforts to senior DoD leadership.

3.3.1.1. Development of Open Architectures & Guidance Assurance: The contractor shall coordinate with Air Force Research Laboratory (AFRL), Aircraft programs, the Air Force (AF) PNT office and potentially with Army, United States Navy (USN) and United States Coast Guard (USCG) offices for participation in developing open architecture and understanding the impacts to Multi-GNSS UE systems. The Contractor shall participate in the development of modular open systems standards and specifications for user equipment and aircraft interfaces to be implemented.

3.3.1.2. Advocacy Briefings: The contractor, as required, shall generate execution and advocacy briefings for presenting to Senior Leadership. The briefs will be focused primarily on program execution and acquisition planning, comprehensive data set representing (with backups) all the information from prior and current contractor efforts and contain a subset of information with recommendations for implementation.

Briefings shall constitute the final out brief and product of this Task Directive Plan (TDP).

The contractor shall be available to assist as required in coordination and briefing efforts to DoD leadership.

3.3.2. Management Surge Capability and Rapid Response: Provide the ability to rapidly (in less than one business day) respond to short term, higher headquarters, taskers or to surge significant resources from multiple skill sets over a short term (1 week to 3 months). This surge or rapid response requires unique SME (Subject Matter Expert) skill sets and on-call availability outside of the core on-site resources.

3.3.2.1. SME Access

Periodically the Government will require access to off-site senior SMEs. Such SMEs are required to have past experience at the level indicated and must be available immediately when required to support emergent Government needs.

3.3.2.1.1. Programmatic Support:

• Acquisition Management (experience as a former ACAT I or II Senior Material Leader (SML) or higher)

• Contracting (PK) (experience as former ACAT I / II Contracting Officer)

• Financial Management (FM) (experience as a former ACAT I/II or higher

Headquarters)

• Logistics Management (LG) (experience as a Product Support Manager)

• Program Scheduler (experience in IMS development and interdependencies)

3.3.2.1.2. Senior Technical Support: These SMEs shall be PNT-recognized experts in the DoD community who can demonstrate their qualifications in the following areas.

• PNT Engineering (minimum of two of the following): 20+ years of experience in respective fields as detailed below w/ a minimum of 5 in the last 10 years;

published works for well-known PNT professional journals or conferences;

submitted PNT patents; PhD in relevant engineering field; chairperson/board member/major technical contributor of industry and/or government standards committee for PNT-related architecture.

o Multi GNSS Receivers o PNT Antennas/Antenna Electronics o Alternative/Complementary Navigation

• Test & Evaluation: 20+ years of Developmental Testing and Operational Testing (DT/OT) experience; APDP T&E practitioner (formally Level III) certified within the last 10 years or graduated from military T&E school.

• Avionics Integration: 20+ years of airborne integration experience and direct involvement with 3+ platforms.

• Cybersecurity: 20+ years of cybersecurity experience focused in technical knowledge of PNT systems, threat evaluation, testing, and countermeasure development.

3.3.2.2. The contractor shall provide the SMEs in their staffing matrix and provide pricing per hour for the SMEs.

3.3.3. S&A Surge: The Government COR will issue S&A tasks as required. S&A tasks will be directed through a Task Directive (TD). Contractor shall provide a TDP in response to each TD. The TDP will identify the approach for accomplishing the work, deliverables, schedule, and labor hours required.

3.3.4. Product Support Business Case Analysis (PS-BCA): Complete Multi-GNSS User Equipment PS-BCA using a structured methodology to generate a document that aids decision making by identifying and comparing alternatives by examining the mission and business impacts (both financial and non-financial), risks, and sensitivities.

3.3.5. Manpower Analysis: Develop manpower estimates for PNT PO HBC to develop and acquire the PNT upgrades consistent with joint service, long-range Assured PNT objectives.

Update and maintain the JSSMO resource assigned Integrated Master Schedule and associated manpower modeling worksheets/models to produce near-real time assessments of projected manpower needs and recommended courses of action. The manpower model shall provide a dynamic workforce management tool to allow rapid support of fact-of-life changes and shall include schedule-based, estimated functional allocations (e.g. PM, EN, PK, FM, LG, etc.) for each supported project.

3.3.5.1. Generate Manpower Estimates for PNT PO HBC: The contractor shall continue developing manpower estimates for PNT PO HBC to provide continued Program Objective Memorandum (POM) inputs for manpower. The contractor shall use and update existing JSSMO manpower estimating tools, methods, and databases based on fact-of-life changes. The basis for the contractor manpower estimates is to draw analogies from other programs and account for differences and similarities (Complexity factors) with these other programs to provide an average estimate against all evaluated programs. Additionally, the contractor shall estimate the functional allocation (e.g. PM, EN, FM, LG, etc.) for each PNT PO HBC manpower excursion.

3.3.5.2. Provide all required documentation and analysis to be incorporated into yearly Electronic Systems Directorate POM inputs, standard manpower tools, or other tools as requested.

3.3.6. Data Rights: Conduct studies and analysis to determine the best approach to acquiring the necessary data rights to support the planned program strategies for long-term sustainment and upgrades. Consideration shall be given to the impact on future resiliency efforts and long-term plan to return the technical baseline to the government.

3.3.7. Capability and Technology Roadmaps: Conduct studies and analysis to recommend long-term program capability roadmaps and technology insertion plans for all product lines.

Consider DoD’s 2015 PNT science and technology Roadmap, Industry Consortium efforts tied to alternative navigation capabilities, Section 2.0 Assured PNT of this PWS, or other relative areas where applicable.

3.3.7.1. Airborne/Handheld/Antenna Roadmap: Develop and maintain roadmaps for inserting planned and potential capabilities into the next generation of Multi-GNSS antennas (to include antenna electronics), airborne and handheld Multi-GNSS receivers.

The roadmap shall be based on current plans for M-Code, Automatic Dependent Surveillance- Broadcast (ADS-B) upgrades, beam forming antennas, with technology insertion on ramps. In addition to acquiring system capability and technology maturation plans from industry, conduct a preliminary cost assessment for both development and production of a new MAGR-2K-M, EGI, and modernized beamforming antenna as a Multi-GNSS system.

3.3.7.2. Future Planning: The contractor shall maintain and/or develop a comprehensive roadmap for the integration of current and future Positioning, Navigation, and Timing (PNT) and Navigation Warfare (NAVWAR) capabilities into next-generation systems, encompassing a range of platforms and technologies, including but not limited to EGI, MAGR 2K, and Multi-GNSS antenna modernization. The roadmap shall be based on currently approved ES (Electronic Systems) Directorate PEO ASP.

Concurrently the contractor shall continue to monitor the plans of Navy, USCG and Army aircraft programs to better inform the roadmap. Additionally, the contractor may visit other locations as necessary to better understand upgrade plans for the GPS satellite and ground systems and customer requirements. The contractor shall also create a resource loaded IMS including all users of the PNT/NAVWAR systems showing planned aircraft OFP cycle upgrades. The purpose of this schedule is to show when key upgrades are to occur and what are the schedule options for upgrades based on aircraft OFP plans. In addition to acquiring system capability and technology maturation plans from industry the contractor shall visit current PNT/NAVWAR contractors to understand their capabilities and plans for existing EGI, MAGR-2K-M, and GPS antenna systems. The contractor shall conduct preliminary cost assessments for PNT/NAVWAR systems.

3.3.8. Milestone Documents: Provide support in preparing necessary acquisition milestone documents for appropriate modernization programs.

3.4 CLIN 0004 EBHS FFP

3.4.1 – Weapons Integration with M-Code Capability

3.5.1.1. Strategic planning: The contractor shall support the government’s efforts to develop and implement a common construct across Multi-GNSS modernization activities. The Contractor shall conduct analysis and integration of Multi-GNSS modernization activities across AFLCMC/HB, and GPS Directorate MGUE planning and development, AFLCMC/EB portfolio Multi-GNSS modernization, and AFLCMC/EZ Assured PNT development.

3.4.1.2. Identify Acquisition Strategies: The contractor shall complete an analytical assessment of various acquisition strategies for PEO Weapons platforms’ Multi-GNSS modernization. Strategies considered shall include looking at each weapon system individually as well as consideration of development and implementation of a common solution across the entire weapon portfolio. In the conduct of the analytical assessment the contractor shall work with the PEO Weapons Program Offices and contractor SMEs to identify unique program requirements, cost constraints for implementing different acquisition strategies (both development and life cycle), schedule, and risk inherent in each approach.

3.4.1.3. Perform Requirements Analysis: The contractor shall, in collaboration with PEO Weapons Program Offices and warfighter requirements SMEs, assess the required performance in the presence of GPS jamming of each munition. Considering launch platform(s), CONOPS, and projected threat scenarios the assessment shall determine the degree of GPS anti-jam capability required.

3.4.1.4. Identify Courses of Action (COAs): The contractor shall develop time-phased COAs addressing technology insertion opportunities, sources of funds, and roles and responsibilities that provide the best chance for success. Using PO projections of PEO Weapons programs modernization funding levels, the contractor shall develop excursions to the COAs to optimize capability insertion given candidate prioritization and available funds. The COAs shall identify potential technology cut-in opportunities within the context of current and projected production lots. Each COA shall identify funding sources and address relevant roles and responsibilities.

3.4.1.5. Perform System of Systems Analysis: The contractor shall provide an analytical assessment of enabling infrastructure to ensure modernized GPS components are supportable when fielded. Analysis includes assessment of cost and schedule implications of modifications to encryption, Mission Planning Systems, and aircraft interfaces required to ensure upgraded munitions’ GPS investment provides tangible operational capability improvements when fielded. Additionally, the contractor shall lay out a strategy for ensuring integration of munitions upgrade activities with those of the enabling systems.

3.4.1.6. Weapons Integration with M-Code Capability: The contractor shall support the government’s efforts to develop and implement a common construct across Multi-GNSS modernization weapons activities as it applies to weapons integration with M-Code capability. The Contractor shall conduct analysis and integration of Multi-GNSS modernization activities across AFLCMC/HBC and the GPS Directorate MGUE planning and development, AFLCMC/EB portfolio GPS modernization, and AFLCMC/EZ Assured PNT development.

3.5 EZA and AF Cyber Resiliency Office for Weapons Systems (CROWS)

3.5.1.1. The contractor shall support these organizations by identifying disconnects in the planning, stand-up, implementation and execution of USAF Assured PNT and related technologies, to include recommendations on establishing future COAs relevant to identifying and implementing an overall resiliency strategy. The contractor shall conduct fact finding and investigate current DoD level directives and provide task options. Specific sub-objectives are identified below:

3.5.1.2. The contractor shall assist in data gathering and fact finding on Department of Defense (DoD), USAF and AFLCMC directives, instructions and organizational goals pertaining to Assured PNT planning, stand-up, implementation and execution.

3.5.1.3. The contractor shall research and conduct data gathering and fact finding on current and evolving threat capabilities that could degrade or deny PNT capabilities.

3.5.1.4. The contractor shall collaborate with the Government to identify initiatives, strategies, investments, roadmaps, systems engineering activities, and COAs to provide Assured PNT capabilities in the future.

3.5.1.5. Roadmaps: The contractor shall review, participate and provide systems engineering support to AFLCMC/EZA and Program Office engineering personnel concerning Assured PNT tasks and actions and concerning the development of integrated roadmaps addressing Assured PNT, to include the interaction and interdependence of CNS/ATM, M- Code, ADS-B Out, advanced tactical data links, and IFF Mk XII Mode 5 capabilities.

3.5.1.6. The contractor shall review, participate in and provide systems engineering support to AFLCMC/EZA and Program Office engineering personnel concerning efforts associated with GPS based navigation databases and data chain processes.

3.5.1.7. The contractor shall generate and develop documentation (point papers, briefings) of the fact-finding assessment results, to include identification of follow-on task recommendations and development of a strategic roadmap.

3.5.1.8. Open System Architecture: The contractor shall assist in generating MOSA standards for use by OEMs in their modernization for M-Code capability.

3.5.1.9. The contractor shall support AFLCMC/EZA by identifying disconnects in the USAF Assured PNT acquisition process, to include recommendations on establishing future COAs relevant to identifying an overall development strategy.

3.5.1.10. The contractor shall participate in and provide systems engineering support for efforts aimed at developing material and non-material solutions to identified gaps in the cyber resiliency of fielded Assured PNT and related systems to include tactical data link systems.

3.6. Configuration and Data Management Support

Contractor shall aid in the application of the fundamentals of configuration management to establish and maintain consistency of a product’s performance, function, and physical attributes with its requirements, design, and operational information throughout its life. The Contractor shall assist in analyzing the impacts of the configuration management change process on lifecycle sustainment. The Contractor shall assist in the development and management of all CDRL requirements. The Contractor shall assist in updating and maintaining electronic database toolkits. The Contractor shall assist with the planning and implementation of Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) and confirm the adequacy of data used to support these audits. The Contractor shall participate in Government review/meetings/working groups as applicable and in Government and industry teams for the resolution of complex configuration management issues. The Contractor shall assist in developing the Configuration Control Board (CCB) charter and assist in the execution of the CCBs. The Contractor shall assist in reviewing/developing/updating applicable program documentation for configuration/data management relevant requirements.

3.6.1 – Configuration Data Management: The Contractor personnel shall perform configuration management and data management tasks as described in this section of the PWS. The Contractor shall assist in establishing and maintaining consistency of a product’s performance, functional and physical attributes with its requirements, design and operational information throughout its life. The Contractor shall assist in analyzing the impacts of the configuration management change process on lifecycle sustainment. The Contractor shall assist in identifying all pertinent sources of and uses for configuration management data. The Contractor shall assist in confirming the adequacy of data for use in system verification reviews (SVR), FCAs, and PCAs and performing said audits. The Contractor shall aid the United Stated Government (USG) in proposing resolutions to conflicting ECP recommendations. The Contractor shall assist data users and requestors with the assessment of proposed configuration management changes and impact systems sustainment and supportability requirements and provide the Government with findings and recommendations.

3.6.1.1. Configuration Identification: The Contractor shall assist in the review of program specifications for hardware and software; review engineering drawings and conduct in-process reviews; request nomenclature and Computer Program Identification Number (CPIN) assignment for Configuration Items (CIs); ensure marking of CI/Computer Software CIs (CSCIs) and associated documentation is accurate; and ensure appropriate documentation is approved and placed on contract for establishment/update of USG controlled baselines.

3.6.1.2. Configuration Control: The Contractor shall aid in the review ECPs, CCPs, RFDs for format and content requirements. The Contractor shall assist in the resolution of discrepancies and issues between the Government and weapon system Contractor;

planning and scheduling of CCBs; prepare CCB briefings and documentation; and track implementation of approved changes.

3.6.1.3. Configuration Status Accounting (CSA): The Contractor shall assist with the determination of CSA data base requirements; monitor data input; track the configuration of fielded systems and equipment; and monitor changes and status of configuration baseline documentation.

3.6.2 – Contract Data Management

3.6.2.1. User Assistance: The Contractor shall assist data users and requesters with the selection and tailoring of Data Item Descriptions (DIDs); the preparation of one-time standard DIDs; and filling out Data Management forms such as CDRLs and Contractor Data Requirements Substantiation (AF Form 585). The Contractor shall be knowledgeable in the application of distribution statements, destruction notices, and Federal Acquisition Regulation/Defense Federal Acquisition Regulation Supplement (FAR/DFARS) data rights clauses to assist in performing the following tasks:

• Providing support in the evaluation of change proposals to determine data impacts

• Tracking the delivery and government approval of contract technical data

• Aiding in the acquisition and use of Contractor Integrated Technical Information

Service (CITIS)

3.6.2.2. Data Calls and Reviews: The Contractor shall provide support in organizing and issuing Data Calls. This support shall include, but not be limited to, drafting of Data Call letters for USG review and release, integrating inputs into draft CDRLs, preparing data review documentation, participating in the Data Call, documenting discussion/recommended changes, preparing draft minutes after the completion of the Data Call, and following up on and maintaining status of action items.

3.6.2.3. CDRLs: The Contractor shall provide support in the identification of appropriate DIDs, the preparation of CDRLs for inclusion in RFPs, the maintenance of CDRLs for contracts, and contract modifications. These tasks will be performed using either automated or manual processing systems as specified in the applicable task order;

provide support to receive, login, track, and maintain status of contract data deliverables; assist with maintaining electronic and manual data management files and provide associated historical information.

3.6.2.4. Data Management Files: The Contractor shall aid in updating and maintaining data management files, and associated DID file.

3.6.2.5. Engineering Data Management (EDM): The Contractor shall provide recommendations on the acquisition of engineering drawings; assist in conducting in-process reviews (IPRs) for engineering drawings; aid in evaluating engineering drawings documentation to ensure format, drafting practices and limited rights legends comply with contractual requirements; assist in maintaining EDM files; and assist in performing follow-up actions to resolve drawings deficiencies and closing out action items.

3.6.2.6. Deficiency Reporting (DR): The Contractor shall utilize the Joint Deficiency Reporting System (JDRS) or similar system to assist in the following DR tasks:

• Originating, receiving, processing and tracking closure of DRs

• Monitoring investigations; processing and disposition of exhibits

• Responding to inquiries from field units, Contractors, etc.

• Conducting briefings and generating reports for management on DR status and trends; and scheduling and providing support for Material Improvement Project (MIP) Review Boards.

3.7. Travel

The Contractor shall also perform non-local travel in support of this contract, as required by the Government. The Government may authorize and require Contractor personnel to travel to participate in meetings, reviews, audits and other efforts as necessary to accomplish assigned tasks. This contract will require frequent travel to Robins AFB, GA. Travel must be coordinated and authorized by the CO or the COR, prior to incurring costs. Travel requests shall be submitted at a minimum of 5 days prior to travel. The Contractor shall submit the travel request with all attached estimated through the Government Procuring Contracting Officer. Contractor costs for travel will be reimbursed in accordance with FAR 31.205-46, in arrears. The travel costs shall be reasonable and allowable as defined in FAR 31.201 and in accordance with the limitations of the Joint Travel Regulation (JTR)/Federal Travel Regulation (FTR)/ Department of State Standardized Regulation (DSSR).

The contractor shall invoice monthly on the basis of cost incurred. The contractor must provide documentation in support of all travel expenses. The contractor will not be reimbursed for local travel (within a 50-mile radius of the Government/contractor’s facility) or commuter travel (commute from home to work site).

Invoice submissions including travel costs shall include completed travel expense sheets (i.e., travel voucher) for each trip and each employee who traveled. The travel expense report, receipts of $75 or more (with exceptions being lodging and transportation whereby receipts are required regardless of dollar value), and supporting documentation (e.g., approval email for exceeding per diem rates, cost comparisons, etc.) shall be submitted with the invoice. Expense report(s) must include the traveler’s name, dates of travel, destination, purpose of travel, Approval Authority documentation (e.g., copy of the e-mail authorizing travel by Government official), and cost for each trip. All travel costs shall be compiled into the Government provided travel expense sheet or similar document that has been determined to be acceptable by the

Government. The entire submission shall be complete and organized to enable the Government to complete an efficient review. Submissions that are not complete and organized are subject to rejection.

4. QUALITY

Both the Contractor and the Government have responsibilities for providing and ensuring quality services, respectively.

4.1. Quality Control

The contractor shall establish and maintain a complete Quality Control Plan (QCP) to ensure the requirements of this contract are provided as specified in accordance with the applicable Inspection of Services Clause. The contractor shall make appropriate modifications (at no additional costs to the government) and obtain acceptance of the plan by the CO. The Government has the right to require revisions of the QCP (at no cost to the Government) should the incorporated plan fail to deliver the quality of the services provided at any time during the contract performance. The plan shall include, but is not limited to the following:

• A description of the inspection system covering all services listed.

• The specification of inspection frequency.

• The title of the individual(s) who shall perform the inspection and their organizational placement.

• A description of the methods for identifying, correcting, and preventing defects in the quality of service performed before the level becomes unacceptable.

• On-site records of all inspections conducted by the Contractor are required. The format of the inspection record shall include, but is not limited to, the following:

o Date, time, and location of the inspection.

o A signature block for the person who performed the inspection.

o Rating of acceptable or unacceptable.

o Area designated for deficiencies noted and corrective action taken.

o Total number of inspections.

4.2 Quality Assurance

The Government will perform periodic reviews of the contractor’s performance in accordance with the Government’s Quality Assurance Surveillance Plan (QASP). The Government reserves the right to review services to be provided, including those developed or performed at the Contractor's facilities, to determine conformity with performance and technical requirements.

5. SERVICE DELIVERY SUMMARY

5.1. Service Delivery Summary

The following Service Delivery Summary (SDS) will guide overall performance of the contract.

The following criteria will be used to determine if performance requirements are met.

Performance Standards Performance Threshold Incentive/Disincentive

TO Kickoff/Performance Start

• Performance initiated within 15 business days of award unless otherwise indicated.

Kickoff and requirements review completed within 5 business days of task order award unless otherwise agreed.

• Performance Assessment reflected in Contractor Performance Assessment Reporting System

(CPARS)

Monthly Status Report, Meeting and Monthly Invoice

• 100% complete with all required information.

• 100% accurate.

• Submitted no later than

(NLT) 15th calendar day of month following the reporting period.

• Performance Assessment reflected in

CPARS

Trip Report

• Within 10 business days following completion of each trip

• Performance Assessment reflected in

CPARS

Management/Administration

• Post award contract concerns addressed timely and in writing to all necessary parties.

• Performance Assessment reflected in

CPARS

Staff Quality and Continuity

• Ensure qualified staffing and retention is maintained at 90% annually or better throughout the life of the contract. Position shall not be vacant for longer than 3 weeks to

• Performance Assessment reflected in

CPARS

include vacations or illnesses.

Quality Control Plan (QCP)

• Performance Assessment reflected in

CPARS

6. DELIVERABLES

6.1. Contractor Submission

Deliverables are to be transmitted with a cover letter, on the prime contractor’s letterhead, describing the contents, electronically via email to the designated COR, and to any other destination(s) as required per the Government’s request. The contractor shall provide hard copy deliverables as required per the Government’s request. All deliverables shall be produced using recommended software tools/versions as approved by the Government. All reports shall be accomplished utilizing the MS (Microsoft) Office Software Suite to include MS Project as required.

6.2. Government Review

Government personnel will have 10 workdays to review deliverables (to include resubmissions) and provide written acceptance/rejection. Government representatives and/or the applicable CORs will notify the contractor of deliverable acceptance or provide comments in writing. The contractor shall incorporate Government comments or provide rationale for not doing so within 5 days of receipt of comments. Government acceptance of the final deliverable will be based on resolution of Government comments or acceptance of rationale for non-inclusion. Additional changes volunteered by the contractor will be considered a resubmission of the deliverable.

6.3. Deliverable Rights

All information such as software, data, designs, test materials, documents, documentation, notes, records, software tools acquired, and/or software source code and modifications produced by the contractor under this PWS shall become the sole property of the U.S.

Government, which shall have unlimited rights to all materials and 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 request, termination or expiration of the contract. The Government shall retain ownership of all proprietary information and intellectual property generated under this contract.

6.4. Transfer of Ownership

All data and documentation, including all studies, reports, spreadsheets, software, data, designs, presentations, documentation, etc., produced by the contractor or for the Government using this PWS are the property of the Government upon its taking possession of task deliverables or upon termination or expiration of the contract.

6.5. Monthly Status Report

The contractor shall provide an MSR, no later than the 15th calendar day of the month following the monthly reporting period, to be submitted simultaneously with the monthly invoice.