N00421-15-R-0014_-_Amendment_0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to revise the follow ing to provide clarif ication based on questions from industry:

1. SOW paragraph 2.11 in Section C is revised to show that CDRLs A00M and A00N w ill be submitted at the task order level rather than the contract level.

2. Paragraph 3.9.4 in Section L is revised to clarify the onsite contractor personnel.

3. CDRL A00N is revised to change the remarks in Block 12 to show that the preliminary draft OPSEC plan is required at the task order level rather than at the contract level.

All other terms and conditions of the RFP remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

1 44

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 03-May-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00421-15-R-0014

X 9B. DATED (SEE ITEM 11)

22-Mar-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

03-May-2016

CODE

NAVAL AIR WARFARE CENTER AD

CODE 2.5.1.11

21983 BUNDY ROAD

BLDG 441

PATUXENT RIVER MD 20670

N00421 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00421-15-R-0014

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

CLINs 0001 - 0019

PERFORMANCE-BASED STATEMENT OF WORK (PBSOW) FOR WARFARE ANALYSIS,

ENGINEERING & TECHNICAL SERVICES

1.0 INTRODUCTION

1.1 BACKGROUND

Assessments of the naval systems, concepts, force structure and the role of naval forces in supporting joint warfighting capability requirements are key to the development of investment strategies to obtain the Navy’s vision for future operations. The Office of the Chief of Naval Operations (OPNAV) provides analytic and capability assessments to guide naval programming and investment decisions necessary to achieve the warfighting capabilities envisioned for future operations. The naval analytic agenda and integration of analytic efforts are managed by

OPNAV N81, coordinated with OPNAV Resource and Warfare Sponsors and Commander, U.S. Fleet Forces

Command (CFFC), and supported analytically by the Systems Commands (SYSCOMs).

The Naval Air (NAVAIR) SYSCOM Mission Engineering & Analysis Department (AIR-4.0M) serves as

NAVAIR’s competency and authoritative source for naval aviation warfare analysis, providing Modeling, Simulation and Analysis (MS&A) support to NAVAIR program offices, OPNAV, and the fleet for analytically defendable acquisition decisions and acquisition program execution. Within the acquisition program, warfare analysis is used to ensure engineering level performance and design are in fact meeting campaign, mission, and engagement level warfighting capability requirements. Using campaign, mission and engagement level models as a foundation, AIR-4.0M assesses weapon systems in the context of Major Combat Operations (MCOs) to support capabilities based acquisition.

Central to AIR-4.0M’s Modeling and Simulation (M&S) capability is the Naval Aviation Enterprise Warfare

Analysis Environment (NAE WAE) that provides state-of-the-art M&S laboratories in which analyses are performed to simulate naval warfare at the engineering, engagement, mission, and campaign levels. Properly integrating naval aviation systems in an appropriate M&S architecture is essential for analysts to identify the optimal systems, systems of systems, operational concepts, tactics, and capabilities required to deal with current and emerging threats to the United States abroad and at home. The NAE WAE provides decision makers with a much-needed, low cost analysis environment to efficiently plan for optimum structuring, acquisition, and operation of naval aviation forces within the new capabilities-based paradigm.

AIR-4.0M tasking for warfare analysis stems from many demands such as:

(1) Office of the Secretary of Defense (OSD) and the Joint Chiefs of Staff (JCS) Analytic Agendas

(2) The Joint Capabilities Integrated Development System (JCIDS) process

(3) Quadrennial Defense Review assessments

(4) Chief of Naval Operations (CNO) guidance

(5) Sea Power 21 assessments

(6) Office of Naval Research (ONR) assessments

(7) Navy Warfare Development Command (NWDC) Concepts of Operations (CONOPS)

(8) OPNAV requirements development

(9) Defense transformation initiatives

Figure 1

(10) On-going analysis of acquisition systems

(11) Fleet support for fielded systems

Each of the above mentioned areas of demands may involve analysis at the operations at the campaign, mission, engagement or system level across a myriad of missions/warfare areas.

1.2 SCOPE

This contract requires the Contractor to provide warfare analysis, M&S, software development, architectures builds and assessments, acquisition analysis and support, and analytic program support. A broad spectrum of support for naval and joint warfighting capability assessments and M&S is required to support and enhance Government and military warfighting analytic efforts that are conducted in support of AIR-4.0M, Program Executive Offices (PEOs), the Naval Aviation Enterprise (NAE), Foreign Military Sales (FMS), and OPNAV. Additionally, analytic efforts may be assessed relative to joint capability requirements to provide time-phased capabilities within Joint Capability

Areas (JCAs).

MS&A support provided under this PBSOW will be performed at the campaign, mission, and/or engagement level to identify warfighting gaps, determine the effectiveness of various alternatives in meeting those gaps, and ensure engineering level performance and designs meet warfighting capabilities requirements – all of which will provide the analytic underpinning for capability based acquisition decisions. Conceptual, developmental, and existing subsystems, systems, System of Systems (SoS), and Family-of-Systems (FoS), with associated CONOPS and tactics, will be assessed within operational and tactical situations to derive optimal naval warfighting capability requirements. Naval mission areas that may be examined include, but are not limited to, the following:

Air Warfare (AW)

Amphibious Warfare (AMW)

Anti-Submarine Warfare (ASW)

Anti-Surface Warfare (ASuW)

Command, Control and Communication (CCC)

Cyber (CYBER)

Electronic Warfare (EW)

Expeditionary Warfare (EXW)

Intelligence, Surveillance and Reconnaissance (ISR)

Irregular Warfare (IW)

Logistics (LOG)

Mine Warfare (MIW)

Mobility (MOB)

Non-Combat Operations (NCO)

Naval Special Warfare (NSW)

Strike Warfare (STW)

Development and application of M&S and analysis techniques will be used to assess engineering designs and approaches, concepts and alternatives, weapons and their characteristics, and platforms and their performance for blue (friendly), red (threat), white (neutral), and green (coalition) systems. Support for AIR-4.0M M&S includes all associated technical support services required to operate the NAE WAE, ensure M&S is applied with engineering discipline with improved traceability of data through the modeling hierarchy, and ensure continuous improvement in the development and application of M&S in support of analysis. Related tasking will include support for M&S

Validation and Verification (V&V); configuration management; user/administrator training; execution and administration of policies and procedures that govern the administration of the laboratories; and development and maintenance of an MS&A data repository.

The scope of this effort includes all activities required to operate, maintain, and administer/manage all unclassified and SECRET WAD Laboratory infrastructure and IT Services which includes models identified in paragraph 2.4 as well as other commonly used applications. In an effort to further describe the 4.0M WAD Lab and IT Service environment, the following is a representative list of M&S and other commonly used applications currently being

Figure 2 used in support of the 4.0M Warfare Analysis mission. Additional applications and/or information systems may be identified during the execution of this effort:

- Advanced Framework Simulation (AFSim)

- Naval Simulation System (NSS)

- Active System Performance Estimate Computer Tool (ASPECT)

- Air Campaign Capability Evaluation and Prediction Tool (ACCEPT)

- At Risk Assessment Model (ARAM)

- Aviation Maintenance Model (AMM)

- Brawler engagement-level model

- Extended Air Defense Simulation (EADSIM)

- Enhanced Surface-to-Air Missile Simulation (ESAMS)

- FORCENet Active System Performance Estimate Computer Tool (ASPECT)

- General Campaign Analysis Tool Suite (GCAM)

- iGrafx Flowcharter

- JAEGER Anti-Submarine Warfare

- Joint Anti-Air Combat Effectiveness: Air Superiority (J-ACE)

- Joint Integrated Mission Model (JIMM)

- Matrix Laboratory (MATLAB)

- Portable Flight Planning System (PFPS)

- QlikView (QV)

- Scalable Tactical Acoustic Propagation Loss Engine (STAPLE)

- Shipboard and Aviation Force Effectiveness for General Air and Raid Defenses (SAFEGARD)

- SolarWinds

- Synthetic Theater Operations Research Model (STORM)

- Target Acquisitions Weapons Software (TAWS)

Per FAR 7.503(a), the Contractor shall not perform Inherently Governmental Functions (IGF). Guidelines for IGF can be found in the Office of Management and Budget, Office of Federal Procurement Policy Letter 11-01, Performance of Inherently Governmental and Critical Functions, at the following link:

http://www.gpo.gov/fdsys/pkg/FR-2011-09-12/html/2011-23165.htm

1.3 DATA HANDLING

The Contractor will have access to system performance, naval force structure, program/business sensitive, and pre-decisional material/data, which the Contractor (and its subcontractors) shall handle in accordance with the DFARS

252.227-7025 “Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive

Legends” clause. Further, copies of signed Non-Disclosure Agreements (NDAs) shall be provided to the

Contracting Officer’s Representative (COR) in accordance with CDRL A00L prior to contractor personnel starting work under a Task Order.

1.4 INFORMATION ASSURANCE PROGRAM - The Contractor shall not purchase any IT equipment on behalf of NAVAIR in support of this Contract, which reports to PBIS-IT, without a Naval Air Systems Command

(NAVAIR) Command Information Officer (CIO) approved NAV-IDAS ITPR. The procedures and applicable reference documentation are outlined in Appendix A to the Performance based Statement of Work.

2.0 REQUIREMENTS

2.1 Warfare Analysis and Assessments. The Contractor shall perform warfighting assessments and effectiveness analyses of operational nodes, systems, subsystems, SoS, and FoS in the operational context, including campaign, mission, engagement and force structure analysis at various levels of fidelity in support of the pre-acquisition, acquisition, modernization and sustainment of naval aviation systems and to determine naval warfighting capability and capacity required to address threats of the future. The Contractor shall perform the following efforts as delineated in task orders in the area of Warfare Analysis and Assessments. Any task order that requires the delivery of documentation/data will include a CDRL outlining the format and document requirements.

http://www.gpo.gov/fdsys/pkg/FR-2011-09-12/html/2011-23165.htm

2.1.1 Support in the development of Mission Technical Baselines (MTB) to outline problem spaces to facilitate

Integrated Warfighting Capabilities.

2.1.2 Support in the development of, or develop excursions to existing Integrated Security Constructs (ISCs), existing Major Combat Operations (MCOs)/Conventional Campaigns (CCs), and Steady State Security

Posture (SSSP) to serve as the analytic framework specific to naval aviation warfighting assessments.

2.1.3 Perform Integrated Capability Technical Baseline (ICTB) analysis. This includes end-to-end kill chain assessments of systems, SoS and FoS in the context of Mission Technical Baselines to assist in the determination of current and Program of Record (POR) system effectiveness against defined threats to identify naval warfighting gaps and the capability and capacity required to address current and emergent threats.

2.1.4 Support battle, warfare, and geopolitical experiments, and war-games.

2.1.5 Develop mission level metrics applying appropriate M&S tools to assess various options. Develop

Measures of Outcome (MOOs), Measures of Effectiveness (MOEs), and Measures of Performance (MOPs) for evaluating the relative merits of warfare systems. Metrics shall be reflective of effectiveness, performance, and overall military worth.

2.1.6 Provide analytic support to NAVAIR Program Executive Office (PEOs) and Program Manager, Air

(PMAs) in determining the contribution of their platforms to future naval and joint warfighting capability requirements.

2.1.7 Provide the tactical input across mission area pillars.

2.2 Architectures Builds and Assessments. The Contractor shall develop DoD Architectural Framework

(DODAF) version 2.02 compliant products in any or all of the mission level architectural areas, including All-View

(AV), Capability (CV), Operational (OV), Data and Information (DIV), System (SV) and Technical (Stdv)

Viewpoints. Support analyses of mission level integrated architectures that effectively meet the mission requirements.

2.3 Acquisition Analysis and Support. The Contractor shall provide analytic support for the pre-acquisition, acquisition, modernization, modification and sustainment of Navy, Joint, and allied systems acquisition process. The

Contractor shall perform the following efforts as delineated in task orders:

2.3.1 Provide support for Joint Capabilities Integration & Development System (JCIDS) analysis and documentation. Execute and/or participate in Capability Based Assessments (CBAs), Analysis of

Alternatives (AoAs), draft Integrated Capability Documents (ICDs), and post independent analyses.

2.3.2 Evaluate and compare the effectiveness, costs, and risk of alternates showing trade space and cost-effectiveness of potential weapon system alternatives in meeting defined naval requirements.

2.3.3 Conduct effectiveness analysis that will model the performance of alternative and determine the quantity and capability required to execute associated missions.

2.3.4 Provide support in establishing disciplined engineering processes and standards to ensure analyses are traceable to customer requirements.

2.3.5 Identify Doctrine, Organization, Training, Material, Leadership, Personnel and Facilities (DOTMLPF) implications resulting from the development and fielding of new warfighting capabilities.

2.3.6 Design and implement configuration management and quality assurance processes and procedures to support M&S based analysis including management support for the accreditation of models, application, data and scenarios.

2.3.7 Recommend standards for processes and employment of M&S in capabilities-based acquisition programs.

2.3.8 Perform warfighting training proficiency assessments.

2.3.9 Perform acquisition related assessments to assist the Government in preparation of documentation for the pre-acquisition, acquisition and sustainment of Navy, joint and allied systems to include:

1) Trade-off analysis

2) Make-buy analysis

3) Risk assessments

4) Mission Area Assessments (MAA)

5) Analysis of Alternatives (AOA)

6) Decision Analysis Support (DAS)

7) Capability Based Assessment (CBA)

8) Warfighting Utility assessments

2.3.10 Support and enable Concept of Operations (CONOPs) and Concept of Employment (CONEMP) efforts for mission areas, kill chains, FOS and SOS assessments by providing or working with Subject Matter Experts

(SMEs) in the mission areas specified in Section 1.2 Scope.

2.3.11 Provide warfare analyses and assessments support to the Government to assist in the preparation of documents to include, but not limited to:

1) Acquisition Plan (AP)

2) Acquisition Program Baselines (APB)

3) Advanced Concept Technology Demonstration (ACTD)

4) Analysis of Alternatives (AOA)

5) Capability Development Documents (CDD)

6) Capstone Requirements Documents (CRD)

7) Command, Control, Communications, Computers, and Intelligence Support Plans (C4ISP)

8) Decision Analysis Support (DAS)

9) Evolutionary Acquisition (EA)

10) Information Support Plans (ISP)

11) Modeling & Simulation Support Plan (MSSP)

12) Reliability, Availability, Maintainability and Cost Rationale Report (RAM-C)

13) Technology Development Strategy (TDS)

14) Test & Evaluation Master Plan (TEMP)

2.3.12 Perform force analyses to determine the Navy’s capability to meet peacetime deployment requirements and respond to transition-to war and contingency operations.

2.3.13 Support in the development of Operational Situation (OPSITs) and Tactical Situation (TACSITs) within the scope of the defense planning scenarios, which will allow performance of appropriate analyses under the desired operational conditions. OPSIT and TACSIT development shall include review of threat and friendly force lay-downs, CONOPS, tactical missions and timelines for use in analysis.

2.3.14 Perform readiness analysis of current and future systems to include readiness impacts of advanced technologies.

2.3.15 Provide analysis of integration impacts of aircraft operations, maintenance and support requirements aboard new ships/ship classes and in-service ships for both legacy and future aviation weapon systems.

2.3.16 Perform warfare analyses in support of vulnerability and survivability assessments of weapon systems, including determination of the contributions of various technologies to overall platform and SoS survivability.

2.4 Modeling & Simulation (M&S). The Contractor shall apply a uniform rigorous, structured methodology to create, verify, and validate physical, mathematical, or otherwise logical representations of systems, entities, phenomenon, or processes. The contractor shall use models and simulations, including emulators, prototypes, and simulators, either statically or over time, to develop data as a basis for supporting managerial, technical, strategic, or tactical decisions. Models and simulations must be traceable to requirements. The Contractor shall provide execution (the running of the models) and technical support for models including but not limited to the following:

1) Naval Simulation System (NSS)

2) Brawler engagement-level model

3) Synthetic Theater Operations Research Model (STORM)

4) OPNET Modeler/QUALNET

5) Multi-Static Planning Acoustic Tool-Kit (MPACT)

6) SUPPRESSOR

7) Advanced Framework Simulation (AFSim)

8) Shipboard and Aviation Force Effectiveness for General Air and Raid Defenses

(SAFEGARD)

9) JAEGER Anti-Submarine Warfare

10) MOSAIC

11) Aviation Maintenance Model (AMM)

12) Joint Integrated Mission Model (JIMM)

The Contractor shall perform the following efforts as delineated in task orders:

2.4.1 Provide support to engagement, mission, and campaign level M&S efforts including development of new

“discovery” type M&S efforts.

2.4.2 Develop M&S tools that support Joint and Navy resource allocation decisions including development of models and simulations for non-traditional warfare, Manpower Personnel Training & Education (MPT&E), and emerging Naval and Joint mission/warfare areas.

2.4.3 Provide support for M&S Validation, Verification & Accreditation (VV&A) activities including tasks associated with plan development, documentation review, and acceptance testing.

2.4.4 Perform V&V of M&S to ensure consistent and credible M&S results, informed decision-making, compliance with DoN Policy, and the cultivation of reusable M&S.

2.4.5 Develop, test, install, and support warfare models and related training in support of the numbered fleet commands or other operational units (i.e., Course-Of-Action tools and Tactical Decision Aids).

2.4.6 Provide analytic expertise in the use of operations research analysis tools, such as MATLAB, SAS, JMP and ACCEPT, to be used in addition to or conjunction with M&S warfare tools.

2.4.7 Provide analytic expertise in operations research areas, such as Design of Experiments, Response Surface

Methodology, and Regression Analysis to be used in addition to or conjunction with M&S warfare tools.

2.5 Decision Environment Support. The Contractor shall provide analytic support and expertise in the buildup and maintenance of the decision support environment. The Contractor shall perform the following efforts as delineated at the task order level:

2.5.1 Develop integrated software solutions to enable advanced Decision Support Environment development and employment.

2.5.2 Provide advanced software based business analytics tools and enhanced capability/data visualization in support of detailed programmatic decision-making.

2.6 Fleet Support. The Contractor shall perform efforts, as delineated in task orders, in the area of Naval

Tactical Reference Publication (NTRP)/Naval Aviation Technical Information Product (NATIP) and Naval Aviation

Training and Operating Procedures Standardization (NATOPS) Product Support (note: these flight clearance documents describe the capabilities and limitations of aircraft tactical systems and form the basis of fleet tactics).

The Contractor shall perform the following tasks:

2.6.1 Develop, prepare, and manage material that contains data required for the operator to safely and effectively employ the aircraft and its weapon systems, facilitating publication updates for new equipment authorized on aircraft as well as updating information for existing equipment and stores. Efforts include product lead, editorial, graphic arts, configuration management and defect-change request tracking support.

2.6.2 Technical/Programmatic Process Support. The Contractor shall support the analysis, review, definition, and execution of formally documented NAVAIRSYSCOM and other command processes to identify, define, and document changes required for the successful flow of technical data/information for F/A-18 weaponeering and F/A-18/EA-18G IFC, NATOPS, and NTRP (NATIP) products.

2.6.3 Naval Aviation Warfare Training Support. The Contractor shall have the ability to develop and present

Naval Aviation Missions and Capabilities (NAMC) training seminar material to PEO, PMA, NAVAIR competency and other DoD personnel.

2.6.3.1 Lectures shall address current threats, as well as carrier air wing and strike fighter capabilities, limitations and tactics.

2.6.3.2 Lectures shall be developed/presented at the executive level (equivalent to NSAWC SLATS course) and the engineering level (equivalent to TOPGUN Ground School).

2.6.4 Provide assessments of operational suitability of naval aviation platforms, weapons, sensors and systems.

These assessments may be associated with minor improvements, modernizations and/or improvements.

2.6.5 Provide test planning and analytical evaluation of results for the operational testing of naval weapon systems.

2.6.6 Provide tactical air evaluation of kill chain assessments.

2.6.7 Provide warfighting SME review and conduits for utility and gap assessments.

2.6.8 Provide analytic expertise to support technical exchanges, briefings, and workshops in support of recommended tactics, techniques, and procedures (TTPs).

2.6.9 Monitor and record test execution tactics, techniques, and procedures (TTPs).

2.7 Programmatic Support. The Contractor shall perform the following efforts, as delineated in task orders, in the area of Programmatic Support.

2.7.1 Develop analytic study plans to address specific requirements set forth in task orders including study objectives, assumptions, technical approach, methodology, products and a detailed Plan of Action &

Milestones (POA&M); support the coordination, tracking and reporting of analytic requirements, milestones and progress.

2.7.2 Document the use and roles of warfare analysis in capabilities-based acquisition and the systems engineering process.

2.7.3 Provide support in documenting the use and roles of warfare analysis within the NAVAIR command, NAE, Navy, and DoD.

2.7.4 Provide planning and operations support for warfare analysis requirements.

2.7.5 Provide technical training for which the application of specialized MS&A skills are required.

2.7.6 Prepare training and communication materials to capture AIR-4.0M strategic initiatives including briefings, brochures, and manuals.

2.7.7 Support the coordination, planning, preparation, and execution of briefings, meetings, and conferences.

2.7.8 Provide support for AIR-4.0MD leadership initiatives such as the development of strategic plans and

Standard Operating Procedures.

2.7.9 Provide assistance with the maintenance of logs and files in accordance with standard procedures.

2.7.10 Provide technical documentation support including development of briefs, white papers, and reports.

Technical documentation may be in the form of paper, electronic (digital), or interactive web-based computer systems.

2.8 Software Development. The Contractor shall perform software development efforts to update, enhance, and/or develop M&S applications or tools (note: M&S applications may include, but are not limited to, high fidelity engineering, engagement, mission, and campaign level models as well as database web application development).

The Contractor shall perform the following tasking in accordance with detailed requirements provided in individual task orders:

2.8.1 Develop Software Architecture.

2.8.2 Develop application or tool.

2.8.3 Develop detailed documentation of the development process, code architecture, code structure, and user’s manuals.

2.8.4 Utilize an established and recognized industry standard for Configuration and Risk Management.

2.8.5 Test the application or tool at a unit level as well as provide for user community testing during development and acceptance testing.

2.8.6 Provide support for VV&A of software and data. This includes tasks associated with plan development, documentation review, and acceptance testing.

2.8.7 Provide services and support for deployment of the application or tool.

2.8.8 Develop and implement a source code transition plan that provides a process to transition the completed source code to AIR – 4.0M which includes documentation for source code updating and recompiling.

2.8.9 Provide software development and maintenance support throughout the life cycle of the application or tool.

2.9 Data. The Contractor shall provide support and perform efforts relating to data used for DoN and DoD warfare analyses. The Contractor shall perform the following tasking in accordance with detailed requirements provided in individual task orders: :

2.9.1 Research and prepare materials that can be used to disseminate, understand, update, and project threat data information such as the Strategic Planning Guidance (SPG), including the identification of threat, friendly, and neutral actors, systems, system characteristics, strategies, and tactics.

2.9.2 Develop and support development of data sets representing United States, friendly, allied, coalition, neutral systems to be used in campaign, mission, engagement, and engineering level MS&A.

2.9.3 Implement procedures to extract data from data sources and statistically process data as required.

2.9.4 Develop and modify translators to construct input sets for models and simulations as required.

2.9.5 Provide general research and data collection support including data analysis, mining and archiving to support projects associated with warfare analysis.

2.9.6 Collect data from authoritative data sources and identify authoritative data sources for modeling efforts;

assist in accrediting data from authoritative data sources.

2.9.7 Propose specific metadata associated with classes of data.

2.9.8 Ensure all analytic products and data are hosted in the AIR-4.0M analysis repository including updates as iterations occur.

2.9.9 Support development, test, implementation, and maintenance of websites, content management, and

MS&A applications using computer security networks, protocols, firewalls and other computer and information, and network protection schemes currently in use by the DOD to include the planning, design, development, coding, population, testing and implementation of databases; create and distribute reports to support periodic management reviews.

2.9.10 Perform data assessments identifying, describing and recommending the types of data, data elements, data formats, and data structures for databases.

2.9.11 Develop database "filters" to allow users to sort through bodies of results, filter out what is not wanted, and allow quick access to the information and data sought

2.9.12 Perform and support V&V of data and databases.

2.10 Naval Aviation Enterprise (NAE) Warfare Analysis Division (WAD) Laboratory Requirements: the

Contractor shall perform this effort onsite. The contractor shall perform all activities required to operate, maintain, and administer/manage all unclassified and classified WAD Laboratory IT Services and its infrastructure.

2.10.1 ITIL Integration

2.10.1.1 The Contractor shall provide support for all (Warfare Analysis Division) WAD Lab IT Service in a manner that aligns to ITIL v3 processes within the ITSM framework.

2.10.1.2 Where ITIL aligned processes are not present, the Contractor shall assist the Government in developing and implementing these processes as required by the Government and in a manner deemed acceptable by the Government Technical Point of Contact (TPOC).

2.10.2 Service Strategy

2.10.2.1 The Contractor shall conduct workshops with relevant stakeholders to review WAD Lab IT

Services with emphasis on developing recommendations for improvement and cost optimization.

2.10.2.2 The Contractor shall assist the Government in ensuring the WAD Lab has sufficient Capacity to meet forecasted Demand.

2.10.2.3 The Contractor shall assist the Government in identifying the needs of existing and future WAD

Lab IT Service users, and ensuring the development of appropriate IT Services to meet those needs.

2.10.3 Service Design

2.10.3.1 The Contractor shall assist the Government in determining how new IT Services will be implemented, from both technical and managerial perspectives.

2.10.3.2 The Contractor shall conduct workshops with relevant stakeholders to assist the Government in negotiating Service Level Targets (SLTs), Service Level Agreements (SLAs), and Operational Level

Agreements (OLAs). Moreover, the Contractor shall assist the Government with designing IT Services in accordance with the agreed SLTs.

2.10.3.3 The Contractor shall provide a Service Level Management (SLM) Report that includes, but not limited to:

- Services covered by SLAs

- Services covered by OLAs

- Services where SLAs are backed up by corresponding OLAs

- Number of Incidents

- An Improvement Plan

- An explanation of how SLTs/SLAs/OLAs are fulfilled and monitored

2.10.3.4 The Contractor shall assist the Government to ensure that the Capacity of WAD Lab IT infrastructure is able to deliver the aforementioned SLTs in a cost-optimized manner.

2.10.3.5 A Capacity Management Report for all WAD Lab compute assets shall be provided to the

Government. The Capacity Management Report and the resulting Capacity Management Plan (a subsection of the Capacity Management Report), shall include:

- Identifying how capacity levels will be determined, monitored, and measured

- Incidents due to Capacity Shortages

- Unplanned Capacity Adjustments

- Capacity Reserve Identification

Percentage of Capacity reserves at times of normal and maximum demand

Percentage of Capacity Monitored

Percentage of Services and Components under capacity monitoring

- Additional information as deemed appropriate by the Government

2.10.3.6 The Contractor shall assist the Government in ensuring the WAD Lab can always provide minimum agreed SLTs, by reducing the risk from disaster events to an acceptable level and planning for the recovery of IT Services in a manner deemed acceptable by the Government.

2.10.3.7 The Contractor shall assist the Government to ensure all aspects of WAD Lab IT Service

Delivery comply with DoD/DoN mandated cyber security policies and federal/local legal requirements.

This includes, but is not limited to, actual implementation of Information Assurance Vulnerability Alerts and Bulletins (IAVA/B/Ms), INFOCON, Scientific and Technical Information Guidelines (STIGs) and all other IA requirements for all WAD Lab compute assets.

2.10.3.8 The Contractor shall prepare, and/or assist in preparing, all documentation and/or drawings required for the WAD Lab IT Service Delivery. (e.g., NAVAIR IT Approvals, accreditation artifacts, etc.)

2.10.3.9 The Contractor shall assist the Government in developing and maintaining a Technology Refresh

Plan/Schedule (A002) that addresses the future development of the WAD Lab's technological landscape.

This document shall take into account IT Service Strategy and will maintain cost-optimized alignment to newly available technologies.

2.10.3.10 The Contractor shall assist the Government in ensuring the implementation of a common technical framework that provides consistency across all physically separated constituent facilities, and utilizes centralized management and reconfiguration processes.

2.10.3.11 The Contractor shall assist the government in conducting market research on suppliers and vendors as it pertains to WAD Lab IT Service.

2.10.4 Service Transition

2.10.4.1 The Contractor shall assist the government in controlling the lifecycle of all WAD Lab IT

Changes, and the establishment and maintenance of a Change Management Strategy that fosters minimal disruption to IT Service Delivery and/or user work impact.

2.10.4.2 The Contractor shall assist the Government with coordinating the resources needed to deploy new

Releases within predicted cost, schedule, and performance estimates. (e.g., the installation and testing of new M&S hardware, software, and related support systems)

2.10.4.3 The Contractor shall plan, schedule and control the movement, patching, and/or upgrading of all software, hardware, and devices/components.

2.10.4.4 The Contractor shall assist the Government with defining and maintaining the Configuration

Items (CIs) required for appropriate WAD Lab IT Service Delivery, including their relationships and versioning.

2.10.4.5 The Contractor shall establish and maintain a Configuration Management System (CMS) that is used for collecting, storing, managing, updating, analyzing and presenting data about all CIs and their relationships.

2.10.4.6 Using industry standard tools and software suites, and/or in a format deemed appropriate by the government, the Contractor shall assist the Government with reducing the need for WAD Lab users to rediscover knowledge. (e.g., the implementation of documented lessons learned, desktop quick reference guides, and Standard Operating Procedures (SOPs)).

2.10.5 Service Operation

2.10.5.1 An Event is a change of state, which has significance for the management of a CI or IT Service.

Using industry standard tools and software suites, the Contractor shall constantly monitor events.

2.10.5.2 An Incident is an unplanned interruption to an IT Service or a reduction in the quality of an IT

Service. The failure of a CI that has not yet affected Service Delivery is also an Incident (e.g., the failure of one disk from a mirror set). The Contractor shall manage the lifecycle of all Incidents and ensure the timely return of IT Services within negotiated SLAs.

2.10.5.3 Service Requests (SRs) are requests from a user for information, advice, a standard change, and/or access to an IT Service (e.g., printer mapping, M&S system access, smart card assistance, new user assistance, etc.). The Contractor shall fulfill, manage, and track all WAD Lab SRs.

2.10.5.4 A Problem is the cause of one or more Incidents, and Problem Management is the process responsible for managing the lifecycle of all Problems. The Contractor shall manage the lifecycle of all

WAD Lab IT Service Delivery Problems, with emphasis on preventing Incidents from reoccurring and minimizing the impact of non-preventable Incidents.

2.10.5.5 The Contractor shall monitor, administer, and control the delivery of all WAD Lab IT Services and the operations/maintenance of all underlying infrastructure (as listed in section 2.10.1through the execution of day-to-day tasking, as deemed appropriate and as approved by the Government TPOC or

COR. This includes, but is not limited the following:

- IAVA/M and patch management activities

- All routine Windows/Linux operating system(s) (OS) administrative actions/maintenance

- SharePoint administrative actions/maintenance

- Thin/Zero-Client management

- M&S applications support

- Virtual Machine(s) administrative actions/maintenance

- SAN administrative actions/maintenance

- Compute Node administrative actions/maintenance

- Video Teleconferencing (VTC) support

- Defense Connect Online (DCO) support

- Backup/restoral activities

- Lab opening and closing

2.10.5.6 The Contractor shall provide near real-time operational status updates (e.g., SharePoint

Homepage and/or electronic scrolling status boards). The Contractor shall also aid in the preparation and dissemination of outage notifications.

2.10.5.7 The Contractor shall provide systems administration and technical support on-site during the core hours of 7:00 am to 5:00 pm EST, Monday through Friday, 52 weeks per year (excluding federal holidays). Upon approval by the COR, who notifies the PCO, the Contractor shall also provide support after core hours and/or weekend hours, as needed. The Contractor shall assist the Government as needed with managing the physical environment where all WAD Lab Components/Devices are located; as stated in the facilities standard of procedures.

2.10.5.8 The Contractor shall assist the Government with managing WAD Lab administrative and M&S hosted applications throughout their lifecycle.

2.10.5.9 The Contractor shall provide technical expertise and assistance to the Government relating to all at meetings and/or briefings.

2.10.6 Continual Service Improvement – CSI

2.10.6.1 The Contractor shall assist the Government in identifying specific initiatives aimed at improving

IT Services and process improvements, based on the results of Service Reviews and Process Evaluations.

2.10.6.2 The Contractor shall assist the Government with validating improvement initiatives, and the introduction of corrective measures, when deemed necessary by the Government.

2.10.6.3 The Contractor shall develop and maintain a CSI Report aimed at improving IT Service quality, optimizing cost, and increasing WAD Lab IT Service Delivery efficiency. The CSI Report and its development shall include:

- Number of customer complaints, Events, SRs, and Incidents

- Average measured customer satisfaction for each IT Service, determined by means of

Customer Satisfaction Surveys

- Number of formal Process Benchmarking, Maturity Assessments, and other audits carried out during the reporting period

- Number of formal Service Reviews and Process Evaluations carried out and resulting

Improvement Initiatives

- Additional information as deemed appropriate by the Government TPOC

2.11 Deliverables and Documentation. Deliverables associated with CDRLs A00K and A00L below are to be submitted at the contract level. All other deliverables listed below shall be task order dependent and submitted at the Task Order level. Task orders may include one or more of the following:

A001 Briefings

A002 Technical Reviews, Reports & Papers

A003 Acquisition Documents

A004 Plan of Action & Milestones (POA&M)

A005 Modeling &Simulation (M&S) Support Plans

A006 Management Plans

A007 Project Review Material

A008 Software Descriptions

A009 Software

A00A Source Code

A00B Validation &Verification (V&V) Documentation

A00C User Manuals

A00D Technical Data/Metadata

A00E Tools, Databases & Websites

A00F Training Material

A00G Meeting Minutes

A00H Monthly Status Report - Technical & Cost

A00J Trip Reports

A00K Non-Disclosure Agreement (Company)

A00L Non-Disclosure Agreement (Individual)

A00M Information Technology Personnel Security Reports (COR)

A00N Operational Security (OPSEC) Plan

2.12 Security.

2.12.1 The security clearance levels provided below are the minimum levels required at the time of contract award for Key Personnel. Each task order, however, will identify the required security clearance level for contractor personnel performing under that order and may require a higher level of security clearance for some labor categories. Contractor personnel in the table below that are non-key must receive an eligibility determination for the required clearance level prior to performing under any task order issued under the contract.

Labor category Level of Required Security Clearance

Sr. Program Manager Top Secret

Sr. Warfare Analyst At least three individuals Top Secret and the remainder as Secret

Sr Engineer At least three individuals Top Secret and the remainder as Secret

Sr. Tactical Systems Analyst At least three individuals Top Secret and the remainder as Secret

Tactical Systems Analyst At least three individuals Top Secret and the remainder as Secret

Mission Integrator All Top Secret

All other Labor categories Secret

2.12.2 The Facility clearance and level of safeguarding required is TOP SECRET. Access to Government installations, aircraft, and ships requires proof of U.S. citizenship. The Contractor shall provide evidence (e.g.

certification) of a Top Secret Facility Clearance.

2.12.3 The provisions of the Military Security Requirement’s Clause of the General Provisions will govern the

Contractor and its personnel. The Contract Security Classification Specifications are set forth in the attached DD

Form 254. Access to the Secret Internet Protocol Router Network (SIPRNET) will be required to perform a significant level of tasking under this contract. The types and classes of data and information shall routinely include, but not be limited to:

1) Not Releasable to Foreign Nationals (NOFORN)

2) Proprietary

3) Business Sensitive

4) For Official Use Only (FOUO)

5) Confidential

6) TOP SECRET

7) TOP SECRET NOFORN

8) Controlled Unclassified Information (CUI)

2.13 Operational Security (OPSEC) Plan. The Contractor shall provide OPSEC protection for all sensitive information (as defined in Title 15, United States Code, Section 278g-3(d)(4). The Contractor shall use

OPNAVINST 34321.1 and National Security Decision Directive (NSDD) 298 for the concept of OPSEC, and apply the framework for telecommunications security in Defense Federal Acquisition Regulation Supplement (DFARS)

Clause 252.239-7016, as appropriate. The Contractor shall apply to meet and use Distribution Statements following the provisions of Exhibit 8A, SECNAVINST 5510.36. In order to meet this requirement, the Contractor shall develop, implement and maintain a facility level OPSEC program to protect sensitive information to be held, provided, used, handled, discussed, processed, stored, transmitted, or delivered at a Contractor's or Subcontractor's facilities during performance of this contract. The Contractor shall submit the document in MS Word 6.0 (or later) format by electronic means and in hard copy to the Government (AIR-7.4.4) for approval.

2.14 Identification Badges (ID). The Contractor shall furnish all the information required to facilitate the issuance of identification badges, and shall conform to all applicable regulations concerning their use and possession. ID media is U. S. Government property and shall be surrendered to the assigned Trusted Agent (TA) upon expiration or termination of employment. The Government will not check out Contractor personnel unless all media, including Common Access Cards (CACs), are returned IAW NASPAXRIV Instruction 5510.15Q, Regulations Governing Admission to Naval Air Station Patuxent River (NAS PAX River), and Maryland.

2.15 Control of Contractor Personnel. The Contractor shall comply with Navy Security Regulations. All persons engaged in work while on Government property shall be subject to search of their person and vehicle at any time by the Government, and shall report any known or suspected security violations to the Security Department.

The Contractor shall remove from performance any person who endangers life, property, or national security through improper conduct.

3.0 TRAVEL, MATERIALS, AND NMCI

3.1 Travel (CLIN 0007). The contractor will be required to travel in support of this effort. Travel will be coordinated and approved by the COR prior to travel. Travel will be reimbursed in accordance with NAVAIR clause 5252.232-9509. Travel will include trips to/from other Navy and Marine Corps facilities, other DoD facilities, and various contractor facilities, test ranges, operational activities, project/program offices, and support activities.

OCONUS travel may be required in NATO countries.

3.2 Material (CLIN 0008). Per NAVAIR clause 5252.242-9515, material may be purchased incidental to the tasking and must be approved by the Contracting Officer’s Representative (COR).

3.3 Navy Marine Corps Intranet (NMCI). Effective 01 October 2015, the Government will provide all NMCI services; to include IT related hardware, software, and support, necessary for the performance of this order.

Implementation of these services shall be coordinated and conducted through the COR.

4.0 PERSONNEL QUALIFICATIONS

The Contractor is responsible for providing personnel fully qualified and competent to perform the scope of the effort set forth herein. The Government reserves the right to review the position descriptions of Contractor employees performing under the contact for the purpose of ascertaining required qualifications. Accordingly, the

Contractor shall furnish such position descriptions upon request by the COR or Contracting Officer. An asterisk (*) denotes key labor categories. See NAVAIR Clause 5252.237-9501 in section H for more information on the addition or substitution of key personnel.

DEFINITIONS

As used in the minimum personnel qualification descriptions for this contract, the terms indicated shall be defined or their meanings qualified as follows:

- Academic year - a full or complete year of study at a junior college, college, university, or other academic institution toward which at least 30 semester hours or 45 quarter hours of undergraduate study, or 18 semester hours or 27 quarter hours of postgraduate study, were completed.

- Accredited institution - a post-secondary educational institution (junior college, college, university, or technical trade, or professional school) which was approved by an accrediting agency listed as nationally recognized by the U.S. Department of Education.

- Accredited program - an educational program or course of study offered by a post-secondary educational institution which was approved by an accrediting agency listed as nationally recognized by the U.S.

Department of Education.

- Degree - an academic title conferred by an educational institution upon completion of a unified course of study; if not otherwise qualified, the term shall mean a degree at the bachelor's, master's, or doctoral levels only.

- Experience and Years of Experience –

a) When used in relation to requirements for past participation in professional work or employment activities, "experience" shall mean full-time (on the basis of a standard forty hour work week) participation, at least one-half of which time was spent performing qualifying functions as a practitioner or employee.

b) When used in relation to requirements for a particular term or period of participation, "years of experience" shall mean full, productive years of participation. Productive years are work years of fifty-two weeks reduced by reasonable amounts of time for holiday, annual, and sick leave.