Draft_SOW.doc

Statement of Work

11/5/2018 Joint Strike Fighter (JSF) Joint Program Office (JPO) Offboard Mission Support (OMS)

Systems Engineering and Analysis

1.0 Introduction

The Naval Air Warfare Center Aircraft Division (NAWCAD) provides global engineering expertise for Naval Aviation related Irregular Warfare/interoperable systems and is a world-class leader in secure and non-secure communications integration and interoperability. NAWCAD has a unique capability to leverage its wide expertise and laboratory infrastructure in order to produce rapid solutions for Irregular Warfare/Special Operations users to deliver mission effective and interoperable, communication capabilities, and provide disadvantaged users with capabilities heretofore only available to sophisticated Naval Aviation platforms.

Various Government agencies including Department of Defense (DoD), Department of Homeland Security (DHS), Intelligence Community and state & local law enforcement entities have tasked NAWCAD to produce and support CONUS and OCONUS rapid reaction capabilities to specific mission gaps related to global war on terrorism. This on-going requirement has resulted in a need within NAWCAD for expertise in production, engineering, analysis, integration and deployment of air systems and other technologies in support of rapid reaction, time-critical missions.

The Advanced Requirements Characterization, Engineering and Representation (ARCHER) is a defined process to simplify or abstract system engineering and integration tasks. The process utilizes a data focused approach to system definition and documentation. ARCHER applies high-level system design concepts and methodologies to large scale software applications and enables the capture of system to system integration requirements. ARCHER is a unique combination of several industry-recognized diagramming standards and techniques that was developed by Computer Systems Center Inc. (CSCI). These interactions will be documented using a comprehensive set of models (including workflow analysis, Department of Defense Architectural Framework (DoDAF), Use Case Analysis and other methods) that reflect the OMS system design, data/information exchanges, operational nodes and system-to-system interactions for land-based and afloat operational environments. These models and products will describe the OMS structure and data variables that it will need to support, while also documenting the capability gaps and shortfalls related to current requirements.

1.1 Background

The USMC, USN, US Air Force (USAF) and several Coalition Partners will use the F-35 aircraft. In order to ensure interoperability across the Joint-Coalition user community, it is necessary to develop a structured view of where data types reside, the various transport methods that will be used, how the data is handled and how to adequately provide required information to Joint-Coalition end users. The comprehensive set of models will aid in the recognition of capability gaps and potential enhancements.

The OMS system is a complex set of hardware and software components that gather various data types and information from internal databases and external sources (e.g., classified networks, portable media, and Intelligence, Surveillance, Reconnaissance and Targeting (ISR&T) feeds). It utilizes this information and produces specific data for the F-35 aircraft before flight. After mission completion, the OMS system is used to analyze recorded ISR information and distribute the data to external consumers. The JPO developed the OMS Enterprise Representation Model (OERM) products that reflect F-35 design changes, block upgrades, operational site representations and information gleaned from interoperability exercises. The government intends to pursue a comprehensive redesign of the OMS system to address design and performance shortfalls of the System Development and Demonstration (SDD) baseline version of OMS produced by the prime contractor, Lockheed Martin Aeronautics (LM). This OMS redesign project is referred to as “OMS Security Architecture Redesign” (OSCAR). Training on how the OMS system works and is maintained is not part of the current F-35 contract structure and process. The process of sustainment of the OMS software, both commercially developed and Government-Off-The-Shelf (GOTS), is not completely covered. The JPO conducts a series of OMS evaluation trials at the Primary Analysis Laboratory Operations II (PALO II) facility at NAWS China Lake, CA. These trials include a recurring annual international collaboration event titled Noble Endeavour (NE). NE events incorporate participation by selected Cooperative Participating Partner (CPP) nation representatives. In addition to the NE trials, the OMS IPT also conducts periodic technically focused concept assessments and user-based capability evaluations. This Statement of Work provides project management activity for OSCAR, delivery of training requirements and enterprise implementation options including cost and schedule estimates, and subject matter expert guidance and documentation for the design and implementation of the OMS SSA. The PWS requires updates to and delivery of OERM products that reflect updates and changes to OMS configuration as it is deployed in the United States and CPP nations.

1.2 Scope

The task is to perform concept development, requirements development and system-engineering services for the F-35 Lightning II Offboard Mission Support (OMS) Integrated Product Team (IPT) in support of the OMS system redesign project, aka OMS Secure Architecture (OSCAR). This effort will include direct support to the OMS 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 OMS operations for the F-35 community. The task includes international exercises researching multi-national collaboration functions designed to formulate future OMS capability and modernization definition. The contract also includes concept development, definition and documentation for full-spectrum training for the OMS enterprise and design and implementation planning for an OMS Software Support Activity (SSA). The contractor will provide research, requirements definition, system-engineering services and program planning assistance to the F-35 OMS IPT.

The effort includes research and development efforts for the OMS integrated product team (IPT) using modeling and analysis to evaluate cross-domain sensing (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.

2.0 Applicable Documents

2.1 Government Standards and Documents

2.1.1 Department of Defense Architecture Framework (DoDAF) Version 2.0, U.S. Department of Defense Chief Information Officer, http://dodcio.defense.gov/dodaf20.aspx

2.1.2 Unified Modeling Language (UML) version 2.4.1, Object Management Group (OMG), August 2011, http://www.omg.org/spec/UML/2.4.1/

2.1.3 NIST SP 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems

2.1.4 NIST SP 800-30 Guide for Conducting Risk Assessments

3.0 Requirements

The contractor shall provide research, requirements definition, system-engineering services and program planning assistance to the F-35 OMS IPT.

3.1 OMS Redesign Research, Planning and Management

The contractor shall provide the OMS 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 JPO, LM 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, technical reports and bi-weekly updates. The contractor shall develop an executive summary and corresponding MS PowerPoint brief documenting this assessment. (CDRL).

3.2 Operational Representation Excursion Development The contractor shall research concepts, 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 OMS 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 OMS enterprise software and hardware in each unique configuration. The contractor shall deliver OERM products in x.pdf format. The contractor shall maintain a database of OERM 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 OMS enterprise software and hardware in each unique configuration. (CDRL)

3.3 OMS Enterprise Representation Model (OERM) Baseline Maintenance

The contractor shall update and maintain the OERM 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 LM SDD contract baseline. 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. The contractor shall deliver OERM products in x.pdf format. The contractor shall maintain a database of OERM products in native form (e.g. Visio, Microsoft (MS) Excel, MS Word).

(CDRL)

3.4 OMS Follow on Modernization Trade Study & Analysis Development

The contractor shall perform trade study activities as requested by the customer 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 estimated development scope and cost of desired products shall be provided to the JPO as they are developed over the period of performance. (CDRL)

3.5 F-35 Trial and Exercise Demonstrations

The contractor shall research concepts, supporting documentation, observe and assist with Primary Analysis Laboratory Operations II trial planning, execution, data collection and refine and maintain the F-35 OMS Research Observations Database. The contractor shall also support F-35 user Technical Interchange Meetings (TIM) 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 F-35 JPO. The contractor shall provide Trial Execution and Test Plans, Operator Guidebooks, Data Collection Plans, Assessment Forms, F-35 OMS Observations Database (CDRL), and Post Exercise Reports (CDRL) for trials planned and conducted during the period of performance as requested by the customer. The contractor shall plan and participate in annual Noble Endeavour (NE) international trials. NE trial planning will include Initial, Middle, and Final Planning Conferences as well as Test Readiness Reviews. (CDRL,)

3.6 Training Systems Planning

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

a. Activity-based training (e.g. pilot, administrator, hardware integrator)

b. Training life cycle (e.g. ground school, basic, advanced, squadron, instructor and coalition exercise)

c. Training on applicable GOTS software tools

The contractor shall deliver training systems technical reports, training systems presentation materials (e.g. PPT) and memoranda. (CDRL)

3.7 Software Support Activity (SSA) Planning

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

a. Scope of support activities

b. Distributed architecture

c. International interface

d. GOTS sustainment

3.8 Government Off The Shelf (GOTS) Software Re-Architecture Modeling Subject Matter Expert

The contractor shall act in the role of process subject matter expert 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 (MS Word) (CDRL)

3.9 GOTS Mission Planning Software Re-Architecture Modeling

The contractor shall participate in the Joint Mission Planning System (JMPS) Framework re-architecture workshops and design studies as an OMS operational Subject Matter Expert (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 as a result of upgrading software programs to 64-bit products from an F-35 Offboard Mission Support perspective. The contractor shall deliver OERM products showing impacts of JMPS re-architecture plans, reports and meeting summaries. (CDRL)

3.10 Collaborative Excursion Development

The contractor shall conduct onsite visits to external teams during the period of performance in order to participate in subject matter expert (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 (CDRL) will be provided for every visit. The JPO will determine which meetings the contractor shall support (CDRL)

3.11 OMS Modeling Product Configuration Management

The contractor shall produce updates for the OMS Data Strategy Model and the OMS Enterprise Representation Model 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 ODSM/OERM version configuration tracking mechanism utilized under N68936-14-D-0013-0006. (CDRL)

3.12 F-35 Operational Liaison for JPO OMS

The contractor shall act as the F-35 Operational Liaison for the JPO OMS team. This includes interaction with Fleet Introduction Teams (FIT) and Operational Sustainment teams. The contractor shall participate as an operational environment Subject Matter Expert assisting the Fleet user community in identification of critical or high risk areas for OMS system integration into squadron daily operations for initial training, pilot continuation training and combat operations. This liaison role will include interaction with US and Foreign National personnel, both uniformed services and civilian contractors at the discretion / direction of the JPO. (CDRL)

4.0 Deliverables

All deliverables become the property of the United States Government in accordance with the terms of the contract. Unless otherwise stated, all deliverables will be submitted in both hardcopy and electronic media in Microsoft Word/PowerPoint/ Excel/Access/Visio/Project or appropriate softcopy format. All deliverables must be submitted to the COR with notification to the contract specialist.

4.1 Monthly Report

The contractor shall submit a summarized monthly report (CDRL), in contractor format that will include:

a. Task Status:

- Significant accomplishments during previous month;

- Recommendations related to the same,

b. Meetings attended/hosted

c. Status/results on previously identified problem areas

d. Impact on requirements (technical/cost/scheduling)

e. Products Provided / Actions / Performed

f. Planned Future Events

g. Problems encountered during this period

h. Financial data shall include amounts invoiced to date, remaining funds, and percent of funds expended should be submitted in a separate report (CDRL).

4.2 Technical Reports

The contractor shall report and summarize all operational analysis, technology review and assessment findings and investigations in memoranda (CDRL) and the monthly report (CDRL). 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.

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

4.4 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 (CDRL). Testing and evaluation will be described in test plan and report (CDRL) documents.

4.5 Software Items

All software, including source code, makefiles, 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 (CDRL). Software shall be accompanied by any necessary installation or build module instructions and/or administrator function descriptions.

4.6 Training Materials

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

5.0 Place of Performance and Travel

The contractor shall perform work at their facility in Springfield, VA. Briefings on findings, results, and products will be performed at F-35 JPO facilities in Arlington, VA, Fort Worth, TX, China Lake, CA, and Washington, DC.

The contractor shall conduct travel in order to complete delivery and training. The contractor should plan for the following travel:

Location

Number of persons Duration

Number of Trips

1. China Lake, CA

4 days

2. Washington, DC

4 days

3. Oslo, Norway

5 days

4. Amsterdam, Netherlands

5. Bristol, United Kingdom

6. Fort Worth, Texas

2 days

6.0 Government Furnished Information

The following information will be required to perform the work described herein and deliver products to the JSF 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 7.0 Security Requirements

Performance of work will require the contractor to have access to information at the Secret level. Contractors shall not divulge or release data or information developed or obtained in performance of this contract except to authorize Government personnel or upon written approval of the Contracting Officer. The Contractor shall not use, disclose, or reproduce proprietary data, other than as required in the performance of this contract. The limitations above do not apply to data or information that has been made public by the Government. All products produced and their associated work papers are to be considered the property of the Government. The final DD Form 254, Contract Security Classification Specification, will be incorporated into the award document.

7.1 The contractor shall have access and storage authority for SECRET information and products. This will include access and use of Secret Internet Protocol Router Network (SIPRNET) at contractor facilities in Springfield, Va. and government offices where feasible.

7.2 Activities performed by contractor personnel will be in accordance with the Operational Security (OPSEC) Plan (CDRL) submitted and approved for the contract. The Contractor’s Facility Security Officer (FSO) shall report immediately, in writing, to the Contracting Officer (CO) and Contracting Officer’s Representative (COR) any changes in the Contractor’s security status throughout the period of performance of the contract.

7.3 The Contractor shall comply with the DOD Customers Operations Security Program; specifically, DODD 5205.02 “DoD Operations Security (OPSEC) Program” dated March 6, 2006.

8.0

NMCI

The Government will certify any software tools or services developed that will be hosted by NAVY MARINE CORPS INTRANET (NMCI) or run on NMCI workstations and ensure that they comply with NMCI policy. Additionally, any servers supporting this SOW will be transitioned to meet the requirements of current NAVAIR Server Consolidation efforts.

�Per Sandy, Which task require software ?