CSCI Follow-on SOW Draft RS ZS 9 30 2026.docx

CUI

Statement of Work for Joint Strike Fighter (JSF) Joint Program Office (JPO) Mission Planning Environment (MPE) Systems Engineering and Analysis 30 September 2026

Scope: The task is to perform concept development, requirements development, and system-engineering services for the F-35 Lightning II MPE IPT in support of F-35 NextGen MPE. This effort will include direct support to the MPE IPT to research how requirements modeling and analysis can provide the basis for a new secure enterprise for technical evaluations, program scheduling, and development. The task includes research into operator workflows and use cases required to develop and sustain MPE operations for the F-35 community. The task includes international exercises researching multi-national collaboration functions designed to formulate future MPE capability and modernization definition. The task also includes concept development, definition, and documentation for full-spectrum training for the MPE and design and implementation planning for an MPE SSA. The contractor will provide research, requirements definition, system-engineering services, and program planning assistance to the F-35 MPE IPT.

The effort includes research and development efforts for the MPE integrated IPT using modeling and analysis to evaluate cross-domain solutions (CDS) activities for technical development requirements. The task includes documentation of ground-based operator workflows and use cases required to sustain and improve Joint and Coalition operations across the F-35 community.

Applicable documents: The documents listed below are presented only as representative sources of the technological interface details that may be required during Contract performance. Likewise, the documentation listed is not all-inclusive but is representative of the type of information that may be necessary to perform the work. The applicable document version is the latest version at time of award. Documents may be added and/or updated to the latest applicable revision as required during the execution of this Contract.

2.1 Department of Defense specifications

2.1.1 DoD National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule.

2.1.2 SECNAV M-5510.36B, Department of the Navy, Information Security Program, 12 Jul 2019.

2.1.3 DoDI 5200.48, Controlled Unclassified Information (CUI), 6 Mar 2020.

2.1.4 DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program, 5 Apr 2019.

2.1.5 DoDI 5230.24, Distribution Statements on DoD Technical Information, 10 Jan 2023

2.1.6 SECNAV M-5510.30C, Department of the Navy, Personnel Security Program, 24 Jan 2020.

2.1.7 OPNAVINST 3440.17A, Navy Installation Emergency Management Program, 1 Aug 2014

2.1.8 DODI 8582.01 - Security of Non-DoD Information Systems Processing Unclassified Non-Public DoD Information, 9 December 2019

2.1.9 NIST SP 800-171r2 – Special Publication: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, February 2020

Requirements

3.1 General Requirements

3.1.1 Compatibility - The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government IT environment through the security classification of (PWS/SOW writer to choose appropriate level). The current operating environment required for this contract includes:

Microsoft Windows 11 Microsoft Project 2016 or greater Microsoft Office Professional Plus 2016 or greater Microsoft Office 365 Adobe Acrobat XI (reader) Internet access

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the IPT. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the IPT during working hours whether at Contractor work site or on travel.

3.1.2 Work Location, Facilities and Telework

3.1.2.1 Work location: Approximately 10percent of work will be performed at Government site and 90 percent of work to be performed at Contractor site. Government site(s) include China Lake, CA, Point Mugu, CA, and Hill AFB, UT). Contractors performing on-site support will be provided (examples include but are not limited to: Access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications) necessary to carry out assigned tasks.

3.1.2.2 Telework/Remote Work: The Contractor may allow employees to telework and/or work remotely with approval from the COR in writing, that a position’s tasking is eligible for telework and/or remote work. The Contractor may utilize alternate worksites/locations to telework and/or work from a remote location to support continued performance of PWS/SOW tasks in accordance with company policy. When using telework and/or remote work, the Contractor remains responsible for contract performance and compliance with any applicable cost accounting standards and contract cost principles / procedures.

3.1.3 Contract Status reporting. The Contractor shall provide the following documentation.

3.1.3.1 Monthly Progress and Financial Status Report: The Contractor shall provide a progress and financial status report. The report shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category and material and travel costs. (CDRL A009).

0. Technical Reports. The contractor shall report and summarize all operational analysis, technology review and assessment findings and investigations in memoranda and the monthly report. It will describe activities performed, actions taken and provide recommendations for Government consideration. These findings will provide data and information that the Government may or may not use in the formulation of concepts. (CDRL A002)

0. Technical Briefings and Meetings. The contractor shall prepare briefings that will consist of executive briefings at the contractor's site, briefings at Navy training centers, briefings to visiting dignitaries, acquisition program offices, and at meetings, conferences, and symposia. Content will be provided to the government for review prior to delivery to any audience outside NAWCWD. (CDRL A00A).

0. System / Software Documentation. While performing any development, implementation, testing or evaluation, all contractor documentation pertinent to the assigned project will be delivered to the government as systems / software developments once completed. Testing and evaluation will be described in test plan and report documents. (CDRL A004) (CDRL A00B)

0. Software Items. All software, including source code, make files, build instructions, associated libraries, and/or utilities developed, will be delivered, when needed, on electronic media suitable for installation, compilation, and use on government-owned computers. Software shall be accompanied by any necessary installation or build module instructions and/or administrator function descriptions. (CDRL A004)

0. Training Materials. The contractor shall provide government user or operator training and associated documentation on developed prototype programs or application features, interfaces, or requirements. (CDRL A006)

3.1.4 Work Schedule to include Installation Work Schedule, holidays, and installation closure.

3.1.4.1 Work schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are 9.5 hours (including a 30-minute lunch break), from 0730 to 1700 each Monday through Thursday and 8.5 hours (including a 30-minute lunch break), from 0730 to 1600 alternating Fridays (except on the legal holidays specified in paragraph 3.1.4.1.2). Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday – alternating Fridays.

3.1.4.1.1 Installation Work Schedule: The Naval Air Warfare Center Weapons Division works a 4/5/9 work schedule. Therefore, alternate Fridays are not a part of the normal workweek for work performed on-site at a Naval Air Warfare Center Weapons Division site. The majority of the Government offices are closed on alternate Fridays.

No deviation in the normal workweek will be permitted without express advance approval by the designated Contracting Officer with coordination of the using departments.

The Contractor may allow its employees to work the installation work schedule provided the requirements of this SOW are met. If the Contractor chooses to allow its employees to work an alternate schedule in support of this contract, any additional costs associated with the implementation of the alternate schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the alternate schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government to the ACOR/COR.

3.1.4.1.2 Holidays: The Government observes the Federal holidays identified on the Office of Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview.

The Contractor is permitted to observe these Federal Holidays in accordance with its corporate policy.

3.1.4.1.3 Installation closure: When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility shall follow their parent company’s policies.

Contractor personnel may not perform work on-site at a Government facility without oversight from Federal personnel. In very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential.

3.1.5 Other Direct Costs:

3.1.5.1 Travel: Travel may include general and administrative expenses but shall not include profit. Temporary travel to other locations in support of program tasking is required. If required, temporary travel locations include Arlington, VA, Fort Worth, TX, China Lake, CA, Washington, DC, and other locations as designated by the Government This list is not all inclusive as locations may change over the life of the contract.

3.1.5.2 Material. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The Contractor shall transfer all materials not depleted to the COR by way of a Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administrative expenses but shall not include profit/fee.

The contractor shall manage material and consumable supplies at levels to meet mission requirements. The contractor must obtain prior approval from the COR for any purchases valued from $0 - $2,500. The contractor must obtain prior approval from the Contracting Officer for any purchases valued over $2,500. The contractor shall submit a consent package providing a description, price, evidence of adequate price competition, or if unavailable, a justification for use of a single source, and a determination that the price is fair and reasonable. The contractor shall submit all consent packages to the COR for either approval of material purchasing for $0 - $2,500 or initial review of material purchasing over $2,500. The COR will forward consent packages for material purchasing over $2,500 to the Contracting Officer for approval. These requirements apply to all contractor purchases.

3.1.6 Subcontractors: Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW shall flow down to subcontractors providing support under this contract.

3.1.7 Management of Contractor Personnel: The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for individual contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services.

3.1.8 Transition Strategy

3.1.8.1

3.1.8.2 Transition Out. The Contractor’s overall transition out strategy shall be built around maintaining the mission of the F-35 MPE IPT with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to the termination or expiration of the contract, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall deliver a Transition Out Plan, to include the minimum elements listed below.

3.1.8.2.1 Work Turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming contractor or Government personnel for the period of transition via weekly status meetings.

3.1.8.2.2 Quality Assurance. The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

3.1.8.2.3 Risk Mitigation Strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

3.1.8.2.4 Data/Information Transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.2 Security

3.2.1All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract's DD-254, Contract Security Classification Specification Form.

Contractor personnel shall require access to classified information in performance of this contract up to and including TOP SECRET, with a safeguarding level of SECRET. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

The contractor will require access to non-substantial Sensitive Compartmented Information (SCI) at the task order level. Access to SCI requires a final U.S. Government Top Secret Personnel Security Clearance based upon a Tier 5 (T5) or Tier 5 Reinvestigation (T5R) and SCI indoctrination. Non-substantial SCI security requirements will be addressed at the task order level.

Access to Special Access Program Information is required in performance of this contract in order to support the NAWCWD Radar Reflectivity Lab, functions of which require the measurement of sensitive elements of the F-35 Platform. The contractor shall comply with all of the special program security requirements outlined within the DD Form 254.

The contractor will require access to COMSEC for the work being performed under this contract. U.S. cryptographic equipment inventory information, as well as the systems and manner in which each particular equipment is sued, is for official use only. Publication or release of any related COMSEC information by any means, by the contractor, without prior written approval of the contracting officer is prohibited. The contractor must be a U.S. citizen, have a final Government security clearance with the appropriate personnel security background investigation for the level of classification involved, have strict need-to-know, have the appropriate COMSEC briefing before access is granted, and granted access only in conformance with procedures established for the particular type of COMSEC information involved. The contractor shall adhere to the DD Form 254 COMSEC security requirements, facility COMSEC material control and operating procedures, and all applicable COMSEC regulations, instructions, and policies. Prior approval from the Government Contracting Activity is required in order for a prime contractor to grant COMSEC access to a subcontractor.

The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information; For Official Use Only; Covered Defense Information). Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

Controlled Unclassified Information including For Official Use Only and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3.

3.2.2 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).

3.2.3 SAAR-N: All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf.

SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.4 Command Access Cards (CAC) / Local Badges: Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to all Department of Defense and NAWCWD instructions. All CACs and identification badges issued to Contractor employees shall be returned to the Contracting Officer’s Representative following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with local security and facility requirements.

In order to maintain access to Navy IT resources, the contractor shall ensure completion of the most current initial and annual DOD Cyber Awareness Challenge training. The contractor shall ensure completion of a Cyber Awareness Training Certificate or the latest version thereof, monitor expiration of requisite background investigations, and initiate re-investigations as required.

If requested, the contractor shall provide to the COR/ACOR or designated SAAR-N Government Sponsor documentation sufficient to prove that it is monitoring/tracking the SAAR-N requirements for its employees who are accessing Navy IT resources. For those contractor personnel not in compliance with the requirements of this clause, access to Navy IT resources will be denied/revoked.

3.2.5 DD-254: The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “For Official Use Only”. Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

3.2.6 Information Security. Direct Support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAV M-5510.36B (series). The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36B

3.2.7 Marking: CUI information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDI 5200.48, Controlled Unclassified Information (CUI). Contractor shall not store or transmit CUI on personal information technology systems or via personal e-mail. Unclassified e-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure (PKI) certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption.

3.2.8 Public Release: Disclosure of information is covered by DFARS 252.204-7000 Disclosure of Information, incorporated in Section I of the contract. Concerning subsection (a)(2), “information otherwise in the public domain” is information officially released into the public domain, e.g. via Distribution Statement A, and does not include information in the public domain that has not been officially released. For disclosure of unclassified information that has not been officially released, the contractor must seek specific approval from the Contracting Officer, with approval from the NAWCWD Public Affairs Office (PAO).

Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release in accordance with the Contract Security Classification Specification, DD Form 254 (Block 12).

3.2.9 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information: All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident occurring.

3.2.10 Operations Security (OPSEC): The contractor shall accomplish the following minimum requirements in support of the NAWCWD OPSEC Program:

3.2.11 Determine Critical Information (CI) in accordance with DoDM 5205.02 (Appendix 1 through Enclosure 3). Critical Information, which individually, or in aggregate, reveal sensitive details about NAWCWD or the contractor’s security or operations, related to support or performance of this SOW.

3.2.12 Adhere to OPSEC Measures and implement countermeasures to protect CI and sensitive activities, especially information or activities that could compromise classified information, operations, or degrade the planning and execution of operations performed or supported by the contractor in support of the mission.

3.2.13 Unclassified information that is sensitive, shall be marked – Controlled Unclassified Information (CUI)

3.2.14 NAWCWD has identified the following baseline Critical Information and Indicators List (CIIL):

1) Details regarding military operations, missions and exercises

2) System and Program Tactics, Techniques and Procedures

3) Emergency response procedures, capabilities, rally points and recall procedures

4) Measures used in Force Protection Conditions (FPCON), and Standard Operating Procedures (SOP)

5) Operational characteristics for new or modified weapon systems

6) Test or evaluation information pertaining to events, scheduling, dates and times

7) Known or probable vulnerabilities to any weapon system or their support systems

8) Intelligence sources or methods of gaining intelligence

9) Information revealing communications security (COMSEC), TEMPEST or Physical Security vulnerabilities

10) Communications systems status, upgrades or proposed changes

11) Network user identifications (IDs), passwords and access codes to restricted/controlled spaces

12) Travel reservations and plans, locations, routes and VIP agendas

13) Personnel privacy: Names, phone numbers, addresses, financials, job titles and passwords

14) Increased/decreased budget costs for future force or mission changes

3.2.15 Industrial Security will maintain, review and have oversight of all classified contracts and associated DD Form 254s. All contract material needing an OPSEC review, e.g. OPSEC Plans, shall only be submitted through the Industrial Security Office, Group D112000.

3.2.16 All CI developed by the contractor and or NAWCWD; in electronic or hard-copy form shall be protected by a minimum of the following countermeasures:

3.2.17 All CI will be evaluated using the DoD OPSEC Process, as described in the National Security Decision Directive 298 (NSDD), and DoDM 5205.02 (Appendix 1 to Enclosure 3).

3.2.18 Per DoDM 5205.02 (Enclosure 6), OPSEC training must be included as part of the contractor’s ongoing security awareness program. OPSEC Fundamentals (OPSE 1301), produced by the Interagency OPSEC Support Staff (IOSS), located on the IOSS website (https://www.iad.gov/ioss/).

3.2.19 If the contractor cannot resolve an issue concerning OPSEC Measures, they will contact the Contracting Officer’s Representative (COR), who shall consult with the appropriate NAWCWD Security Officer, Security Coordinator, or Technical Point of Contact (TPOC).

3.2.20 All above requirements shall be enforced by the Prime Contractor’s Facility Security Officer (FSO), to include their subcontractors.

3.2.21 The contractor shall comply with the OPSEC requirements outlined within the DD Form 254. The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the contract. The contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The OPSEC program shall be in accordance with DoD and DON operations security (OPSEC) requirements, to include:

1) Assignment of responsibility for OPSEC direction and implementation

2) Planning guidance for the use of the OPSEC Process to identify vulnerabilities and apply applicable countermeasures (Contact NAWCWD Industrial Security Office for a current OPSEC Annex and CI Guide)

3) Establishment of OPSEC education and awareness training

4) Provisions for management, annual review, and evaluation of OPSEC programs

5) Oversight for accountability of OPSEC requirements to subcontractors

While performing aboard NAVAIR or NAVAIR sites, the contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts. Include OPSEC as part of its ongoing security awareness program and take all required Agency training. Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and contractor in support of the mission.

The Contractor shall prepare an Operations Security Plan for Government review in accordance with CDRL A00C.

3.2.22 Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

3.3 Detailed Support Requirements:

3.3.1 This contract will utilize the following appropriation types OMN, OMAF, RDT&E, and RDAF.

3.3.2 The contractor shall provide research, requirements definition, system-engineering services, and program planning assistance in support of the F-35 MPE IPT and Marine Corps Department of Aviation Headquarters.

Mission Planning Environment (MPE) Redesign Research, Planning and Management

3.3.2.1 The contractor shall assist the MPE IPT with research into how new technologies might resolve design deficiencies and provide solutions to operator desired capability. The contractor shall detail available modernization functionality, development of the program plan, contract documentation, budget documents, and technical requirements for the project. The contractor shall interface with the JPO, Lockheed Martin, and other technical and program management teams on a regular basis not less than weekly. The contractor shall provide the JPO reports on research completed, draft concept documents, program plans, and technical reports. The contractor shall develop an executive summary and corresponding Microsoft PowerPoint brief documenting this assessment. (CDRL A001)

3.3.2.2 Operational Representation Excursion Development

The contractor shall research concepts and create and maintain excursion products for Operational Representations and future operational environments. These modeling products shall contain the documentation of the concepts for how operational fielding of MPE will be implemented for locations requested by the JPO. The modeling products shall include the documentation of how the various services and/or countries will employ the F-35 MPE enterprise software and hardware in each unique configuration. The contractor shall deliver MERM products in x.pdf format. The contractor shall maintain a database of MERM products in native form (e.g., Visio, Excel, Word). This shall include the documentation of how the various services and/or countries will handle the use of F-35 MPE enterprise software and hardware in each unique configuration. (CDRL A002)

3.3.2.3 Mission Planning Environment Enterprise Representation Model (MERM) Baseline Maintenance The contractor shall update and maintain the MERM to ensure the product currency and accuracy. The model will be updated based on documentation from the JPO. This documentation may include design changes from the Lockheed Martin System Development and Demonstration contract baseline N00019-19-C-0010. Updates shall include operational threads representing in depth representations of specific work processes such as threat analysis or route planning. These updates include modifications to operational workflows, use case vignettes, and DoDAF products.

3.3.2.4 Mission Planning Environment Follow-on Modernization Trade Study & Analysis Development The contractor shall perform trade study activities as requested by the F-35 MPE IPT in support of Follow-on Development analysis. These trade studies may include development of operational workflows, use case vignettes, DoDAF products, or the development of analysis reports. The contractor shall provide an estimate for development scope and cost of desired products to the JPO. (CDRL A002)

3.3.2.5 F-35 Trial and Exercise Demonstrations

The contractor shall research concepts and supporting documentation. The contractor shall also observe and assist with Primary Analysis Laboratory Operations II trial planning, execution, data collection and refine and maintain the F-35 MPE Research Observations Database. The contractor shall also support F-35 user Technical Interchange Meetings events at Lockheed Martin for the purpose of gathering feedback for the Observations Database. The task will require contractor documentation of performance and risk analysis required by the JPO. The contractor shall provide Trial Execution and Test Plans, Operator Guidebooks, Data Collection Plans, Assessment Forms, F-35 MPE Observations Database, and Post Exercise Reports for trials planned and conducted during the period of performance as requested by the customer. The contractor shall plan and participate in annual NE international trials. NE trial planning will include Initial, Middle, and Final Planning Conferences as well as Test Readiness Reviews. (CDRL A002) (CDRL A003) (CDRL A004) (CDRL A005)

3.3.2.6 Training Systems Planning

The contractor shall assist the F-35 Training Systems IPT to develop concepts for training users how to use the MPE across the entire F-35 training spectrum from initial student exposure to advanced wing-level integrated multi-national training evolutions. These requirements include:

Activity-based training (e.g., pilot, administrator, hardware integrator) Training life cycle (e.g., ground school, basic, advanced, squadron, instructor, and coalition exercise). Training on applicable Government off-the-shelf software tools. The contractor shall deliver training systems technical reports, training systems presentation materials (e.g., PowerPoint) and memoranda. (CDRL A006)

3.3.2.7 Software Support Activity (SSA) Planning

The contractor shall develop requirements and concepts for establishing a SSA for the MPE system. (CDRLA007) This shall include:

Scope of support activities Distributed architecture International interface Government off-the-shelf sustainment

3.3.2.8 Government off-the-Shelf (GOTS) Software Re-Architecture Modeling Subject Matter Expert (SME) The contractor shall act in the role of process SME and model owner for the re-architecture activities for all participating GOTS software teams. This shall include training of personnel from each respective software development team on data strategy modeling techniques as well as managing the overarching model for the re-architecture effort. The contractor shall deliver training plans and summary reports of activities. (CDRL A006)

3.3.2.9 Government off-the-Shelf (GOTS) Mission Planning Software Re-Architecture Modeling The contractor shall participate in the JMPS Framework re-architecture workshops and design studies as a MPE operational SME. As a result of this participation, the contractor shall develop an F-35 excursion model which highlights the potential impacts of the planned JMPS Framework re-architecture to other GOTS and Prime Contractor developed software due to upgrading software programs to 64-bit products from an F-35 MPE perspective. The contractor shall deliver MERM products showing impacts of JMPS re-architecture plans, reports, and meeting summaries. (CDRL A002)

3.3.2.10 Collaborative Excursion Development

The contractor shall conduct onsite visits to external teams during the period of performance in order to participate in SME reviews and Technical Interchange Meetings for the development of collaborative model excursions. The contractor shall provide documentation on F-35 data strategy, process validation control, and will assist in the documentation of external team systems. A technical report will be provided for every visit. (CDRL A002) (CDRL A008)

3.3.2.11 Mission Planning Environment (MPE) Modeling Product Configuration Management The contractor shall produce updates for the MPE Data Strategy Model and the MERM products through formalized product configuration management and the execution of periodic product evaluations (to be performed on products targeted for formal delivery). The contractor shall utilize the Configuration Management Plan and Oracle Directory Services Management/MERM version configuration tracking mechanism utilized under N68936-14-D-0013-0006. (CDRL A002)

3.3.2.12 F-35 Operational Liaison for F-35 Joint Program Office (JPO) Mission Planning Environment (MPE) The contractor shall act as the F-35 Operational Liaison for the JPO MPE team. This includes interaction with Fleet Introduction Teams (FIT) and Operational Sustainment teams. The contractor shall participate as an operational environment SME assisting the Fleet user community in identification of critical or high-risk areas for MPE system integration into squadron daily operations for initial training, pilot continuation training and combat operations. This liaison role will include interaction with U.S. and Foreign National personnel, both uniformed services and civilian contractors. Operational liaison includes but is not limited to weapons school and operational test units (e.g., USAF Weapons School, TOPGUN, MAWTS, 422 TES, VX-9, VMX-1). (CDRL A008)

3.3.2.13 F-35 Scaled Agile Framework (SAFe) Next Generation Open Mission Services (NOMS) Software Development The contractor shall engage as required with the NOMS software development enterprise across all levels of the SAFe process. The contractor shall participate as an operational SME, assisting software architects, engineers, and developers with understanding mission planning requirements and priorities. The contractor shall provide Operational SMEs and Model Based Systems Engineering (MBSE) professionals to the Portfolio, Large Solution, and Essential levels along with the Spanning Palette to provide efficiency to the overall software development process while ensuring F-35 MPE vision is included.

3.3.2.14 F-35 Model Based Systems Engineering (MBSE)

The contractor shall participate in F-35 JPO MBSE activities and reviews, providing systems engineering expertise using the ARCHER method. Techniques include but are not limited to MBSE and System Modeling Language (SysML), Business Motivation Modeling (BMM), Workflow and Dataflow analysis, System Use Case Modeling using Unified Modeling Language (UML) and Business Process Modeling Notation (BPMN). The contractor shall aide the F-35 JPO in development of models that can communicate across the vast landscape of system stakeholders (end users, engineers, managers, and senior leadership), intuitively illustrating system requirements, capabilities, architectures, and constraints.

3.3.2.15 F-35 Mission Planning Environment (MPE) Weapons Integration The contractor shall provide expertise and support of Weapons Integration within the MPE for remaining JMPS-based activities and future integration with NOMS-based MPEs. Activities include but are not limited to weapon effectiveness, weaponeering, stores/suspension equipment loadout, limitations planning and validation, Network Enabled Weapons (NEW) planning, aircraft sensor planning required for weapons employment, and Electronic Countermeasures (ECM) planning. This task covers all current and future weapons and support equipment/sensors employed by any variant of the F-35. Examples of possible weapons systems shall include, but not be limited to, Joint Direct Attach Munitions (JDAM), Advanced Antiradiation Guided Missile-Extended Range (AARGM-ER), Small Diameter Bomb I/II (SDB I/II), Joint Standoff Weapon (JSOW), Advanced Medium-Range Air-to-Air Missile (AMRAAM), AIM-9X, GAU-22/A, and partner country comparable weapons.

3.3.2.16 International Agreements

The contractor shall assist Marine Aviation on the authorship and execution of all USMC arrangements with F-35 Partner and FMS nations. The contractor shall posture Marine Aviation for engagements with the JPO, Headquarters, Marine Corps (HQMC), Plans, Policies and Operations (PP&O), Secretary of the Air Force International Affairs, United States Marine Corps Forces Command (MARFORCOM), Wing, Group and Squadron personnel to develop, negotiate and produce agreements on the spectrum on F-35 Doctrine, Organization, Training, Materiel, Leadership and Education, Facilities and Policy (DOTMLPF-P) issues as they pertain to integration and pooling.

3.3.2.17 International Program Development and Execution

The contractor shall provide expertise in the F-35 Partner and FMS nation F-35 programs. Provide insight on these nations’ priorities for F-35 capabilities, and the programs and configuration required to deliver them. Provide expertise on international budget processes, requirements, and plans. Provide expertise on how these nations’ programs support their plan to employ F-35 tactically and operationally.

3.3.2.18 International Engagement

The contractor shall assist Marine Corps leadership in meetings with F-35 Partner and FMS nation officials, both in the U.S. and overseas; accompanies and advises DON officials on trips and meetings related to the U.S.’ relationship with those nations. Work with USN, USMC, Secretariat, and Office of the Secretary of Defense (OSD) staff to prepare background papers on key security issues involving USMC interests; prepares meeting papers and talking points for use by USMC principals, and maintains oversight on implementation of policy action-items following meetings and trips.

3.3.2.19 Joint Program Planning

The contractor shall support Marine Aviation in the following Joint F-35 program activities such as sustainment, preparing for joint decision forums such as the Configuration Steering Board and the Joint Executive Steering Board, and assisting in shepherding Marine Corps priorities through the processes necessary in the F-35 Joint Program.

3.3.2.20 Joint Program Execution

The contractor shall assist Marine Aviation in the planning, and execution of its Tactical Aircraft (TACAIR) transition. The contractor shall ensure that include SAP and TS/SCI capabilities are delivered to the fleet on a timeline which aligns with the deployment schedule and with the pacing threat. Assist in all capability and sustainment efforts which drive critical capability and readiness initiatives.

3.3.2.21 Advanced Capabilities and Integration

The contractor shall assist Marine Aviation in the identification, coordination and integration of emerging concepts, technologies, and capabilities to posture F-35 for current and future operations including SAP and TS/SCI in accordance with USMC Force Design. Explore and engage across Joint and Service(s) Science and Technology portfolios to identify and assess candidate capabilities that will enable F-35 within the Force. Provide recommendations to HQMC on activity relevant to F-35 within the evolving Joint Service System-of-Systems architecture.

3.3.2.22 Naval Integration Within the Maritime Construct

The contractor shall assist Marine Aviation in exploring, developing, defining, and vetting F-35 Concept of Operations (CONOPS) within the operational constructs encompassing USN and USMC operations in the Maritime. Investigate F-35 CONOPS within the emerging conceptual frameworks of Distributed Maritime Operations (DMO), Expeditionary Air Base Operations (EABO), Littoral Operations in a Contested Environment (LOCE) and other related and/or emerging concepts. Identify and understand enabling technologies and capabilities including SAP and TS/SCI related to F-35 within such frameworks and conduct examination and analysis through Live-Virtual Constructive environments.

3.3.2.23 Joint All-Domain Warfighting

The contractor shall assist Marine Aviation in enabling F-35 to be a fully-operational participant in Joint All-Domain Warfighting. Contractor shall support efforts to explore, integrate, communicate, and inform the ability of F-35 to operate as an organic, holistic, fully integrated, agile, and resilient element within evolving Command Control, Communications, Computers, Cyber Intelligence, Surveillance and Reconnaissance (C5ISR) architectures. Contractor will be knowledgeable, engaged and fully informed, including SAP and TS/SCI, to drive Service awareness and advocacy within emerging knowledge and data sharing constructs such as Joint Air Dominance Command and Control (JADC2) and Mission Partner Environment.

3.3.2.24 F-35 MPE UI

The contractor shall provide expertise and support of the new User Interface, including TS/SCI, concepts within the MPE for JMPS-based activities as well as future integration with NOMS-based MPEs. The contractor shall also support F-35 user Technical Interchange Meetings events involving Applied Minds products and developmental models to gather feedback for the Observations Database and the creation of prototypes for user trials.

3.3.2.25 Other Program Requirements

Government Furnished Information The following information will be required to perform and deliver the work described herein to the JPO and NAWCWD:

a) Technical data and programmatic information on involved programs that relate to JSF,

b) Classified and unclassified F-35 system characteristics and operational behaviors,

c) Data and results from tests and demonstrations of related combat systems,

d) Products developed and/or delivered under N68936-14-D-0013-0008 & N68936-14-D-0013-0010