MEAD_Warfare_Analysis _Engineering Services_Sources Sought DRAFT SOW.pdf
PDF 399 KB Posted
- Attached to
- The Mission Engineering and Analysis (MEAD) Warfare Engineering Services Federal contract opportunity
- Solicitation number
- Not on record
About this file
This sources sought notice requests capability statements from interested parties to provide warfare analysis engineering services in support of the Naval Air Warfare Center Aircraft Division's Mission Engineering and Analysis Department. Key details include:
-
The services include warfare analysis, modeling and simulation, architecture development, acquisition support, and program support. Approximately 20% of work will be on-site at Naval Air Station Patuxent River and 80% at contractors' facilities.
-
Capability statements are due by January 28, 2021. The anticipated contract is a single-award cost-plus-fixed-fee IDIQ for $100 million over five years from April 2022 to March 2027. The incumbent is ManTech International under contract N00421-17-D-0036.
-
Interested parties must have a facility clearance of Top Secret and safeguarding of Top Secret. Personnel security clearances of Secret or Top Secret will be required. At least 50% of work must be performed by the prime contractor.
View the file
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Statement of Work
1. 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 Mission Engineering & Analysis Department (MEAD), a department within the Digital Analytics Infrastructure and Technology Advancement (DAiTA) Group under the Naval Air Warfare Center Aircraft Division (NAWCAD), 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 acquisition programs, 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, MEAD assesses weapon systems in the context of Major Combat Operations (MCOs) to support capabilities based acquisition.
Central to MEAD’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.
MEAD 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) Office of Naval Research (ONR) assessments
(6) Navy Warfare Development Command (NWDC) Concepts of Operations (CONOPS)
(7) Office of the Chief of Naval Operations (OPNAV) requirements development
(8) Strategic Capabilities Office initiatives
(9) Naval Capability Improvement Process (NCIP)
(10) Warfare Capability Baseline (WCB)
(11) Defense transformation initiatives
(12) On-going analysis of acquisition systems
(13) Subject Matter Expertise 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, associated M&S and 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 MEAD, 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 SOW 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) Command, Control and Communication (CCC) Counter Unmanned Air Systems (C-UAS) Cyber (CYBER) Electronic Warfare (EW) Expeditionary Warfare (EXW) Intelligence, Surveillance and Reconnaissance (ISR) Irregular Warfare (IW) Logistics (LOG) Mine Warfare (MIW) Mine Countermeasure Warfare (MCW) Mobility (MOB) Non-Combat Operations (NCO) Naval Special Warfare (NSW) Strike Warfare (STW) Surface Warfare (SUW)
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 MEAD 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 following is a representative list of M&S and other commonly used applications currently being used in support of the MEAD Warfare Analysis mission. Additional applications and/or information systems may be identified during the execution of this effort:
- Advanced Framework for Simulation, Integration and Modeling (AFSIM)
- Active System Performance Estimate Computer Tool (ASPECT)
- Air Campaign Capability Evaluation and Prediction Tool (ACCEPT)
- Aircraft Conceptual Design Tools
- 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
- Joint Anti-Air Combat Effectiveness: Air Superiority (J-ACE)
- Joint Integrated Mission Model (JIMM)
- Matrix Laboratory (MATLAB)
- Naval Simulation System (NSS)
- Personal Computer Interactive Multi-sensor Analysis Training (PC-IMAT)
- Portable Flight Planning System (PFPS)
- QlikView (QV)
- Satellite Toolkit (STK)
- 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)
- Systems Modeling Language (SysML)
- Target Acquisitions Weapons Software (TAWS)
- Tabletop Wargaming Methods
This contract is a single award indefinite delivery / indefinite quantity contract to support the mission of the DAiTA Group, the MEAD Department and the associated mission and warfare analysis requirements. Specific requirements will be derived from the scope of this SOW and documented through individual Task Orders (TO).
Task Orders are expected to be a mix of Level of Effort and Performance Based Completion types and a mix of Cost Plus Fixed Fee and Firm Fixed Price.
1 Applicable Documents The following documents are applicable to the SOW as specified herein. This list is not all inclusive. This list is for reference only and defines the most common documents, policies, specifications that may be applicable in the performance of the duties defined within this SOW. New instructions, supplements, amendments, or revisions to documents may be issued during the term of the contract, and shall be in full force and effective immediately upon receipt by the Contractor. In the case of an inconsistency between the industry standards referenced herein and the Government documents referenced below, the Navy/DoD standard will always take precedence. Additional documents may be identified at the individual TO level.
1.1 Referenced Documents
1.1.1 Federal / DOD / Military Documents
Joint Travel Regulation (JTR) DODM 5200.01 – DoD Information Security Program: Controlled Unclassified Information (CUI) DODM 5220.22-M – National Industrial Security Program Operating Manual (NISPOM) DODD 5230.24 – Distribution Statements on Technical Documents
NAVY Documents EKMS-1b - Electronic Key Management System (EKMS) Policy and Procedures For Navy EKMS Tiers 2 & 3 NASPAXRIVINST 5100.12C Traffic Safety Program
NASPAXRIVINST 5100.35D – Safety and Occupational Health Manual NASPAXRIVINST 12610.7H – Employee Reporting Procedures During Emergencies OPNAVINST 3440.17A – Navy Installation Emergency Management Program OPNAV 5239/14 SAAR-N – System Authorization Access Request Navy (SAAR-N) OPNAVINST 5239.1D- US Navy Cybersecurity Program NASPAXRIV 5510.15Q- Base Access Regulation SECNAVINST 5100.13E – Navy Tobacco Policy SECNAV M-5510.30 – Personnel Security Program SECNAV M-5510.36 – Information Security Program SECNAVINST 5510.36- DoN Information Security Program (ISP) Regulation OPNAVINST 5530.14E Navy Physical Security and Law Enforcement Program NASPAXRIVINST 3440.17A- Installation Emergency Management Program NASINST 4010.5B Hazardous Material Control and Management Plan NASINST 5100.35C Occupational Safety and Health Manual NASINST 11320.1N Fire Bill
2. Requirements
1.2 General Requirements
1.2.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 unclassified. The current operating environment required for this contract includes:
• Microsoft Windows 10
• Microsoft Project 2016
• Microsoft Office Professional Plus 2016
• Microsoft SharePoint 2016
• 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. For contract administrative or indirect functions performed at the Contractor site, the Contractor shall ensure that all media delivered to the Government are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the Government.
Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the Government during working hours whether at Contractor work site or on travel.
1.2.2 Work Location and Facilities
Approximately 20 percent of work will be performed at a Government site and 80 percent of work to be performed at the Contractor site. Final performance location will be defined at the TO level. As defined at the TO level, the Contractor shall be required to provide short and/or long-term technical support services at both in Contiguous United States (CONUS) and Outside Continental United States (OCONUS).
Government onsite support does not include temporary and ad-hoc support performed away from NAVAIR/NAWCAD facilities. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, network access including web servers, tooling, and applications necessary to carry out assigned tasks.
1.2.3 Contract Status Reporting
1.2.3.1 Monthly Financial Status Report
The contractor shall provide a financial status report in accordance with the Contract Data Requirement List (CDRL A001). The report shall provide a total basic level contract financial summary and include separate sub reports for all active TO’s. 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 clearly identified by individual order and CLIN. The labor categories utilized in the financial report shall be consistent with those defined in Section 3.4.6 of this contract.
1.2.3.2 Monthly Progress Report
The contractor shall provide a monthly progress report in accordance with CDRL A002. This report shall list the monthly accomplishments and upcoming task order / project objectives for each task order/ project and each identified financially tracked project task. Trips and significant event shall also be addressed. The report shall be organized by task order, project, then by financially tracked task, as applicable.
1.2.3.3 Contractor Record Locator Report
The contractor shall provide a Contractor Record Locator Report in accordance with CDRL A003. This report shall identify all direct personnel supporting requirements under this contract. The report shall include name, labor category, employed by, security clearance level, assigned task order(s), and location of performance. The labor categories utilized in the report shall be consistent with those defined in Section 3.4.6 of this contract.
1.2.3.4 Additional Reporting Requirements
Additional reporting requirements will be defined at the individual TO level.
1.2.4 Work Schedule to include Compressed Work Schedule (CWS), holidays and installation closure This section applies to work performed at the Government facilities, as defined at the TO level.
The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0730 to 1600 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday–Friday. If different hours are needed by a Government team or the Contractor (e.g. individual groups or locations may allow or require different hours) on a long term basis, they will be coordinated through the Technical Point of Contact (TPOC) associated with that work and approved by the Contracting Officer Representative (COR).
The compressed work schedule (CWS) is an alternative work schedule to the traditional five 8.5 hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one Friday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one Friday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.
The Contractor may allow its employees to work a CWS schedule provided the requirements of the individual TOs are met. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the contract and individual TOs.
Holidays The Government observes the following holidays:
• New Year’s Day, January 1
• Martin Luther King’s Birthday, the third Monday in January
• President’s Day, the third Monday in February
• Memorial Day, the last Monday in May
• Independence Day, July 4
• Labor Day, the first Monday in September
• Columbus Day, the second Monday in October
• Veteran’s Day, November 11
• Thanksgiving Day, the fourth Thursday in November
• Christmas Day, December 25
The contractor is permitted to observe the above Holidays in accordance with its corporate policy.
1.2.4.1 RESERVED
1.2.4.2 Travel/Temporary Duty (TDY)
When personnel are temporarily deployed offsite, the Contractor shall modify the traveler’s working hours to best support the assigned tasking.
1.2.4.3 General Facility Access
When employees of a facility are officially excused from work due to a holiday, special event, severe weather, a security threat, or any facility related problem that prevents personnel from working at the facility, Contractor personnel assigned to work at that facility performing non-mission essential work in support of such employees shall follow their parent company’s policies and conform to one of the following possible courses of action:
1.2.4.3.1 Report for work at an alternate site if available, permitted by the terms of the contract, and they receive advance authorization from the COR or Contracting Officer; or
1.2.4.3.2 Telework, provided telework is permitted by the terms of the contract and they receive advance authorization to telework from the COR or Contracting Officer; or
1.2.4.3.3 Follow parent company’s policies regarding taking leave (administrative or other).
1.2.4.4 Emergency Conditions at Government Site
NASPAXRIVINST 12610.7H – Employee Reporting Procedures During Emergencies identifies procedures Government employees are to follow when an emergency condition is identified. The Contractors shall follow the procedures as defined with the exception of being granted administrative leave. Contractors that are at work when a delay or restricted access is announced shall cease work and exit the base as soon as it is safe to do so. The procedures are summarized below.
• OPEN WITH UNSCHEDULED LEAVE – Contractors that choose to stay home shall notify the order level Technical Point of Contact of their decision
• DELAYED ARRIVAL – The Contractor shall not show up to work prior to their normal start time plus the announced delay. With prior COR approval, the Contractor may be allowed to shift their work hours to make up the missed hours. Contractors cannot charge the contract for the delayed arrival hours and shall check with their employer as to how to code their time card for the delayed arrival hours.
• DELAYED OPENING – The Contractor shall not show up to work before the announced opening time. With prior COR approval, the Contractor may be allowed to shift their work hours to make up the missed hours.
Contractors cannot charge the contract for the delayed opening hours and shall check with their employer as to how to code their time card for the delayed opening hours.
• RESTRICTED ACCESS – The Contractor shall not show up to work. Contractors cannot charge the contract for the hours not at work and shall check with their employer as to how to code their time card for the day. See paragraph 3.1.4.3 General Facility Access.
• OPEN WITH STAGGERED DEPARTURE – The Contractor shall depart work at their normal end time minus the announced number of hours early. Contractors cannot charge the contract for the hours not at work and shall check with their employer as to how to code their time card for the day.
• OPEN WITH IMMEDIATE DEPARTURE – The Contractor shall depart work immediately. Contractors cannot charge the contract for the early departure hours and shall check with their employer as to how to code their time card for the delayed arrival hours.
• SHELTER IN PLACE – The Contractor shall shelter in place. Contractors that are sheltering and in a work status can charge the contract during regular work hours.
1.2.4.5 Telework
Telework may be permitted under this contract. However, not all labor categories may be able to take advantage of telework opportunities due to the nature of the work. Telework shall be addressed at the individual TO level.
The Contractor shall request approval from the COR for any position for which the Contractor proposes a teleworking situation. The contract request shall identify the labor category, equipment required (PCs, books, etc), the work to be accomplished or deliverables to be provided, the expected duration of the tasks, principal location where telework will occur, communication methods available to reach the Contractor during telework hours, supervisory method and the working hours the person shall be in a telework status and available for correspondence. Upon approval by the COR, the Contractor may telework within the parameters approved by the request at no additional cost to the Government.
1.2.5 Management of Contractor Personnel
The Contractor shall supervise its workforce and control the methods by which required tasks are performed. The Contractor shall assign tasks to and 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. All direction and clarification on work contained in this SOW shall come from the COR and/or the NAWCAD Contracts Office.
1.2.5.1 Personnel
Contractor personnel shall remain employees of the Contractor and will not be considered employees of the Government. The contract PM shall ensure the Contractor workforce understands this employer difference when issues come up that affect the Government, but does not include the Contractors. All subcontractors and subcontractor personnel working on this contract are viewed by the Government as part of the Prime’s workforce.
As such, there shall be no processes, requests, approvals, or other documents or procedures that are presented to the Government from the subcontractor. All subcontractors shall conform to the same processes and documentation as the Prime when interfacing with the Government.
1.2.5.2 Tobacco Use
IAW SECNAVINST 5100.13E – Navy Tobacco Policy, Tobacco use is only permitted in designated tobacco use areas.
Time spent for tobacco use (while on duty) shall occur only during approved break periods that will be designated by supervisors based on staffing and per Federal law, personnel policy, and union contracts. Break periods for tobacco users will be the same as for non-users. Under this contract, the tobacco policy shall also apply to vaping and e-cigarettes.
1.2.6 Contract Management
The Contractor shall manage the contract. The Contractor is expected to manage this contract in an effective and efficient manner. Management activities are expected to include but are not limited to:
• Overall administration and management of the contract
• Primary POC into the Contractor’s organization
• Support of standing weekly COR meetings to discuss contract issues
• Develop management procedures and controls
• Hiring to meet Contractor support requests
• Managing tasking, workload, and performance of individual TOs
• Monitoring and reporting progress of work tasks and contract management tasks
• Managing the financial and administration aspects of the contract
• Management of subcontracts
• Development and delivery of required CDRLs
• Completion of tasking in a timely manner
1.2.7 Training
1.2.7.1 New Hire Orientation
The Contractor is responsible for providing an orientation to new hires to enable them to adequately perform their tasking. Orientation shall include, but is not limited to:
• Physical knowledge of the base and Government facilities
• Contract information (Contractor/COR interaction and basic contract requirements)
• Their labor category requirements
• Specific process requirements (Government and Contractor)
• Org chart / hierarchy for both Contractor and Government
• Introductions (COR/ACOR, Government task lead, Contractor task lead, etc.)
1.2.7.2 Labor Category Requirements
The Contractor is responsible for providing individuals who are trained, certified, and qualified to perform the tasks outlined in the SOW. Training to meet labor category requirements is the sole responsibility of the Contractor— both initial training and required re-certifications. The Contractor is responsible for the cost of the training (class, travel, supplies) and the labor associated with the training. This training shall be met prior to the Contractor personnel reporting for duty except as identified in the specific labor category. Due to availability and location of some training classes, exceptions may be made to allow personnel to begin working while waiting for the training to become available with prior approval by the COR. In the case of re-certifications, the Contractor shall plan ahead of time so as to not impact workload due to missed days for training or expiring certifications.
1.2.7.3 Training
Due to the technical nature of the MEAD’s work, there may be special, unique, and emergent training required during the execution of this contract. This training may include, but is not limited to, specific software, hardware, and procedures required by MEAD. All requests for cost reimbursable training shall include a written justification by a Government Technical Point of Contact (TPOC) and course information including but not limited to the source of the training, the dates of the training, a training course description, and training cost including quotes from the vendor. General educational courses or programs for enhancement of basic qualifications or academic standing of employees shall not be accomplished at the Government’s expense. No cost reimbursable training shall be scheduled or executed without written approval from the COR in accordance with Section 3.3.9.
1.2.7.4 Mandated Training
For performance at Government facilities, this contract requires Contractor personnel to complete training such as Anti-Terrorism and Active Shooter (as referenced in paragraph 3.2.6), and any required Operational Security (OPSEC) topics (as referenced in paragraph 3.2.5). Also, during the course of the contract, the Government may mandate training for all personnel. This training may be computer or instructor based. Contractor personnel shall participate in these training requirements. Participation may be at live training events, computer based training, or via review of a provided set of PowerPoint slides. This training shall be provided and/or reimbursable by the Government. The Contractor Program Manager shall ensure all Contractors on the contract are trained and shall report compliance to the COR within five (5) working days after the announced deadline of the training.
1.2.8 Non-Disclosure Agreements (NDAs)
In the performance of the contract, the Contractor may have access to non-public proprietary information. The Contractor shall require that any employee performing services under the contract execute a NDA satisfactory to the Contracting Officer. The NDA shall acknowledge the Contractor and employees’ duties with respect to non-public information, and promise to comply with those obligations. A copy of the executed NDAs shall be provided to the Contracting Officer.
1.3 Security
1.3.1 Citizenship Requirements
Only United States (U.S.) citizens may perform under this contract. If the Contractor cannot find qualified U.S.
citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:
a) The individual's name, date and place of birth, position title, and current citizenship.
b) A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.
c) A statement of the unusual expertise possessed by the applicant.
d) A statement that access will be limited to a specific Government contract (specify contract number).
e) A statement that the Contractor has obtained an export license for the information required to perform the contract.
1.3.2 Investigative Requirements
A minimum of a SECRET security clearance is required for all positions on this contract. A complete ‘Day One’ staffing requirement will be provided by the Government NLT two (2) weeks after contract award. Positions required to possess TOP SECRET clearances with a current investigation or other special security requirements at the start of contract performance will be identified at the TO level.
All 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 NONE. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW DODM 5220.22-M – National Industrial Security Program Operating Manual (NISPOM). 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.
1.3.3 Common Access Card (CAC)/PKI, SAAR-N
1.3.3.1 SAAR-N
All Contractor personnel requiring access to Government IT systems shall access and operate IT systems and networks IAW shall have an approved OPNAV 5239/14 SAAR-N – System Authorization Access Request Navy form on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR-N forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.navsea.navy.mil/Portals/103/Documents/NSWC_Carderock/OPNAV-5239-14-SAAR-N.pdf forms shall be submitted to the COR, Government TPOC, or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted Associate.
1.3.3.2 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 http://www.navsea.navy.mil/Portals/103/Documents/NSWC_Carderock/OPNAV-5239-14-SAAR-N.pdf all requested information required to facilitate issuance of identification badges. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site following completion of the contract, relocation or termination of an employee, or upon request from the COR. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract.
1.3.3.3 DD-254
The Contractor shall comply with security requirements as specified in the DD-254 of 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 COR of this contract for approval.
“For Official Use Only” information 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.
1.3.3.4 Other Badging
Badges to special, classified, limited access, and/or commercial facility (e.g. Prime Contractor for a project or platform) areas may be required by the Contractor based on location and tasking. The Contractor shall adhere to the rules governing the issuance of those badges.
1.3.4 Information Security
The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI IAW DODM 5220.22-M – National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36
– Information Security Program. If the work is performed at the Government’s facility, the Contractor shall comply with instructions/guidance required by that facility.
1.3.4.1 Marking
All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked IAW DODM 5200.01 – DoD Information Security Program:
Controlled Unclassified Information (CUI). Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DODM 5220.22-M – National Industrial Security Program Operating Manual (NISPOM), SECNAV M-5510.36 – Information Security Program, and program Security Classification Guidance.
1.3.4.2 Public Release
No information pertaining to this contract shall 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 the appropriate U.S.
Government authority. Proposed public releases shall be submitted to the COR for initial approval and awareness.
Upon initial approval, the Contractor shall submit proposed public releases for approval prior to release through the Procuring Contracting Officer.
1.3.4.3 Loss, Compromise, or Spillage
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 twenty-four (24) hours of the incident occurring.
1.3.5 Operational Security (OPSEC)
The contractor shall comply with activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The contractor will include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The contractor will protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed by the RO and contractor in support of the mission.
While performing aboard NAVAIR or NAVAIR sites, the Contractor shall: (1) comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts; (2) include OPSEC as part of its ongoing security awareness program and take all required Agency training; (3) be responsive to the Supporting OPSEC Manager on a non-interference basis; and (4) protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the Requiring Office and contractor in support of the mission.
The Contractor shall develop, implement, and maintain an OPSEC plan (CDRL A003) to protect classified and sensitive information to be used at a contractor's and subcontractor's facilities during the performance of this contract. The Contractor is responsible for subcontractor implementation of the OPSEC program requirements for this contract.
1.3.6 Anti-Terrorism Force Protection and Emergency Management The work performed on this contract is not Emergency Essential IAW OPNAVINST 3440.17A – Navy Installation Emergency Management Program 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 in any event or emergency where Government official’s direct curtailment of operations to “Restricted Access” or “Mission Essential Only”. All Contractor personnel assigned to a Government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.
1.3.7 Communications Security (COMSEC)
The Contractor shall be required to access COMSEC material. The Contractor shall follow the guidance for handling COMSEC material as identified in EKMS-1b - Electronic Key Management System (EKMS) Policy and Procedures For Navy EKMS Tiers 2 & 3 and applicable local instructions.
1.3.8 Special Compartmentalized Information Facility Access
The Contractor shall require access to Special Compartmentalized Information Facilities (SCIF) in the performance of this contract. This contract does not include actual performance or delivery of SCI services or product.
1.4 Detailed Support Requirements
1.4.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.
1.4.1.1 Support in the development of Mission Technical Baselines (MTB) to outline problem spaces to facilitate Integrated Warfighting Capabilities.
1.4.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.
1.4.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.
1.4.1.4 Support battle, warfare, and geopolitical experiments, and war-games.
1.4.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.
1.4.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.
1.4.1.7 Provide the tactical input across mission area pillars.
1.4.2 Architecture 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.
1.4.3 Acquisition Analysis and Support
1.4.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.
1.4.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.
1.4.3.3 Conduct effectiveness analysis that will model the performance of alternative and determine the quantity and capability required to execute associated missions.
1.4.3.4 Provide support in establishing disciplined engineering processes and standards to ensure analyses are traceable to customer requirements.
1.4.3.5 Identify Doctrine, Organization, Training, Material, Leadership, Personnel and Facilities (DOTMLPF) implications resulting from the development and fielding of new warfighting capabilities.
1.4.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.
1.4.3.7 Recommend standards for processes and employment of M&S in capabilities-based acquisition programs.
1.4.3.8 Perform warfighting training proficiency assessments.
1.4.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:
a. Trade-off analysis
b. Make-buy analysis
c. Risk assessments
d. Mission Area Assessments (MAA)
e. Analysis of Alternatives (AOA)
f. Decision Analysis Support (DAS)
g. Capability Based Assessment (CBA)
h. Warfighting Utility assessments
1.4.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.
1.4.3.11 Provide warfare analyses and assessments support to the Government to assist in the preparation of documents to include, but not limited to:
a. Acquisition Plan (AP)
b. Acquisition Program Baselines (APB)
c. Advanced Concept Technology Demonstration (ACTD)
d. Analysis of Alternatives (AOA)
e. Capability Development Documents (CDD)
f. Capstone Requirements Documents (CRD)
g. Command, Control, Communications, Computers, and Intelligence Support Plans (C4ISP)
h. Decision Analysis Support (DAS)
i. Evolutionary Acquisition (EA)
j. Information Support Plans (ISP)
k. Modeling & Simulation Support Plan (MSSP)
l. Reliability, Availability, Maintainability and Cost Rationale Report (RAM-C)
m. Technology Development Strategy (TDS)
n. Test & Evaluation Master Plan (TEMP)
1.4.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.
1.4.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.
1.4.3.14 Perform readiness analysis of current and future systems to include readiness impacts of advanced technologies.
1.4.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.
1.4.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.
1.4.4 Modeling, Simulation, and Analysis
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, statically, 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:
a. Naval Simulation System (NSS)
b. Brawler engagement-level model
c. Synthetic Theater Operations Research Model (STORM)
d. OPNET Modeler/QUALNET
e. Multi-Static Planning Acoustic Tool-Kit (MPACT)
f. SUPPRESSOR
g. Advanced Framework Simulation Integration and Modeling (AFSIM)
h. Shipboard and Aviation Force Effectiveness for General Air and Raid Defenses
(SAFEGARD)
i. MOSAIC
j. Aviation Maintenance Model (AMM)
k. Joint Integrated Mission Model (JIMM)
l. Systems Modeling Language (SysML)
m. Cameo
The Contractor shall perform the following efforts as delineated in task orders:
1.4.4.1 Provide support to engagement, mission, and campaign level M&S efforts including development of new “discovery” type M&S efforts.
1.4.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.
1.4.4.3 Provide support for M&S Validation, Verification & Accreditation (VV&A) activities including tasks associated with plan development, documentation review, and acceptance testing.
1.4.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.
1.4.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).
1.4.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.
1.4.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.
1.4.5 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:
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.
1.4.5.1 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.
1.4.5.2 Implement procedures to extract data from data sources and statistically process data as required.
1.4.5.3 Develop and modify translators to construct input sets for models and simulations as required.
1.4.5.4 Provide general research and data collection support including data analysis, mining and archiving to support projects associated with warfare analysis.
1.4.5.5 Collect data from authoritative data sources and identify authoritative data sources for modeling efforts; assist in accrediting data from authoritative data sources.
1.4.5.6 Propose specific metadata associated with classes of data.
1.4.5.7 Ensure all analytic products and data are hosted in the MEAD analysis repository including updates as iterations occur.
1.4.5.8 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.
1.4.5.9 Perform data assessments identifying, describing and recommending the types of data, data elements, data formats, and data structures for databases.
1.4.5.10 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.
1.4.5.11 Perform and support V&V of data and databases.
1.4.6 Programmatic Support
1.4.6.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.
1.4.6.2 Document the use and roles of warfare analysis in capabilities-based acquisition and the systems engineering process.
1.4.6.3 Provide support in documenting the use and roles of mission and warfare analysis within the NAVAIR command, NAE, Navy, and DoD.
1.4.6.4 Provide planning and operations support for warfare analysis requirements.
1.4.6.5 Provide technical training for which the application of specialized MS&A skills are required.
1.4.6.6 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.
1.4.7 Administrative Support
1.4.7.1 The Contractor shall provide general administrative and organization support for the MEAD Department and Divisions as defined at the TO level.
1.4.7.2 Contractor personnel supporting functions…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .