COMET - DRAFT SOW rev 03242020.docx

COMMAND, CONTROL, COMMUNICATIONS, COMPUTERS, AND INTELLIGENCE OPERATIONAL MAINTENANCE & ENGINEERING TRAINING

STATEMENT OF WORK

Scope: The Airborne Systems Integration (ASI) Division is engaged in the research; development; design; integration; test and evaluation; deployment; training; technical management; and maintenance support for integrated Command, Control, Communications, Computers, and Intelligence (C4I) life-cycle engineering systems supporting various sponsors to include Naval Air Systems Command (NAVAIR), Naval Sea Systems Command (NAVSEA), and other DoD and Federal organizations.

This Statement of Work (SOW) will provide information management architectures relating to interactive information and learning products to support the warfighter. These services include Maintenance and Materiel Management (3M); the development of logistics packages; software engineering, development, and integration; engineering support; and technical support to Naval Air Warfare Center Aircraft Division (NAWCAD) Webster Outlying Field (WOLF) and its customers.

Efforts accomplished under this Contract will encompass the engineering and analysis of complex DoD based C4I systems relating to and supporting innovative and interactive information and learning tool products. Efforts include in-service engineering approaches as it relates to planned maintenance and training covering both currently deployed C4I systems, as well as new and emerging C4I systems still under development. This effort will include design, development, implementation, and training utilizing electronically based engineering processes for maintenance and training techniques on sophisticated military systems. These engineering solutions and interactive products will support the various C4I equipment suites that are found aboard U.S. Navy and foreign surface and subsurface warships. The support will also include DoD based air platforms and ground systems involving various communication, weapon, and operational mission systems. In order to accomplish the associated tasking, the Contractor will also be required to interact with fleet personnel to ascertain not only inputs for the engineering design and development phases of these information and learning tool products, but to also support fleet personnel in their daily duties of in-service engineering and maintenance support for the mission based electronic equipment.

Applicable documents:

DoD specifications DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM), Change 2, Effective 18 May 2016.

DoDI 5230.24, Distribution Statements on Technical Documents, Change 3, Effective 15 Oct 2018.

DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), Change 2, Effective 28 Jul 2017.

DoDM 5200.01, DoD Information Security Program: Controlled Unclassified Information (CUI) Vol. 4, Change 1, Effective 9 May 2018.

DoDM 5400.07, Freedom of Information Act (FOIA) Program, Effective 05 Apr 2019.

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

OPNAVINST 4790.4F, Ship’s Maintenance and Material Management System Policy, 27 Oct 2014.

OPNAVINST 4790.13B, Maintenance of Naval Electronic Equipment, 23 Sep 2014.

OPNAVINST 4790.14B, Joint Depot Maintenance Program, 14 Feb 2013.

OPNAVINST 4790.16B, Condition-Based Maintenance and Condition-Based Maintenance Plus Policy, 1 Oct 2015.

SECNAV M-5510.30, Personnel Security Program, 1 Jun 2006.

SECNAV M-5510.36B, Information Security Program, 12 Jul 2019.

DoD Instruction 1000.13 Volume I DoD ID Cards.

2.1.14 DoD 8570.01-M, Information Assurance Workforce Improvement Program, December 19, 2005 (Incorporating Change 4, November 10, 2015).

DoD standards.

MIL-HDBK-29612/1A, Guidance for Acquisition of Training Data Products and Services, Part 1 of 5 Parts, Notice 1, 8 Jun 2006.

MIL-HDBK-29612/2A, Instructional Systems Development/Systems Approach to Training and Education, Part 2 of 5 Parts, Notice 1, 8 Jun 2006.

MIL-HDBK-29612/3A, Development of Interactive Multimedia Instruction, Part 3 of 5 Parts, Notice 1, 8 Jun 2006.

MIL-HDBK-29612/4A, Glossary for Training, Part 4 of 5 Parts, Notice 1, 8 Jun 2006.

MIL-HDBK-29612/5, Advanced Distributed Learning (ADL) Products and Systems, Part 5 of 5 Parts, Notice 1, 8 Jun 2006.

MIL-P-24534A, Planned Maintenance System (PMS): Development of Maintenance Requirement Cards (MRC), Maintenance Index Pages, and Associated Documentation, 21 Mar 1991.

MIL-PRF-35337B, Performance Specification: Manuals, Technical, Quality Assurance Program, 11 Apr 2012.

MIL-STD-3034A, Department of Defense Standard Practice: Reliability-Centered Maintenance (RCM) Process, 29 Apr 2014.

MIL-STD-4151-22-M, Condition Based Maintenance Plus (CBM+) for Material Maintenance, 6 Oct 2012.

Other Government documents.

CENNAVAVNTECHTRA INSTRUCTION 1554.1, Interactive Multimedia Instruction Developer’s Guide, 27 Jan 2014.

COMFLTFORSOMINS 4790.3 REV C, Joint Fleet Maintenance Manual, Change 7, Effective 05 Oct 2018.

DoD Cloud Computing SRG v1r3, Department of Defense Cloud Computing Security Requirements Guide, Version 1, Release 3, 6 Mar 2017.

NAVAIRINST 4120.11A, Policy for Preparation and Standardization of Naval Air Systems Command Interactive Electronic Manuals, 25 Oct 2012.

NAVSEAINST 4790.8C, Ships’ Maintenance and Material Management (3-M) Manual, Change 1, Effective 30 Nov 2015.

NSWCCD-20-TR2010/01, DoN S1000D Technical Manual Quality Assurance Guidance, March 2009.

US Fleet Cyber Command (FCC)/Space and Naval Warfare (SPAWAR) Command Navy Authorizing Official and Security Control Assessor Risk Management Framework Process Guide, Version 1.0, 31 Aug 2015.

Defense Manpower Data Center (DMDC) Trusted Associate Sponsorship Systems (TASS) Overview Guide, Version 5.3.2, Dec 2014 Industry documents.

SI1000D, International Specification for Technical Publications Utilizing a Common Source Database, Issues 3.0-5.0.

Requirements.

General requirements.

Compatibility. The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government Information Technology (IT) environment through the security classification specified on the DD-254, Attachment XX. The current operating environment required for this Contract includes:

Microsoft Windows 10 Microsoft Project 2016 Microsoft Office Professional Plus 2016 Adobe Acrobat DC 2015 Internet access

The current operating environment is Microsoft Office Professional Plus 2016. At the time of award, it is expected the Government will be operating with Microsoft Office 365.

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

Work location and facilities.

Work location. Approximately twenty-five (25) percent of work will be performed at Government site and seventy-five (75) percent of work will be performed at Contractor site. Government site(s) include NAS Patuxent River; Webster Field Annex, St. Inigoes, MD; and Norfolk, VA. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.

Meeting support. In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at the classification levels up to Secret with the capacity to support a minimum of five (5) persons and have Contractor furnished unclassified telephone and unclassified Video Teleconference (VTC) capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in paragraph 3.1.1. This support shall be provided within a fifty-mile driving distance of Patuxent River, MD and within a fifty-mile driving distance of Norfolk, VA.

Contract status reporting. The Contractor shall provide the following documentation.

Monthly progress and financial status report. The Contractor shall provide a progress and financial status report In Accordance With (IAW) the Contract Data Requirement List (CDRL). (CDRLs A008 and A009) Project/task closeout report. The Contractor shall provide a closeout report after completing the requirements of each Task Order (TO). (CDRL A017) Trip reports. The Contractor shall submit Trip Reports for travel required to support the performance of the tasks detailed in paragraph 3.3. (CDRL A018) Work schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.

Work schedule. The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually eight and a half (8.5) hours (including a 30-minute lunch break), from 0800 to 1630 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.

Compressed Work Schedule (CWS). CWS is an alternative work schedule to the traditional five (5) eight and a half (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 (8) weekdays are worked at nine and a half (9.5) hours each (which includes a 30-minute lunch), one (1) weekday is alternately worked as eight and a half (8.5) hours (which includes a 30-minute lunch), and one (1) weekday is not worked by the employee. The result is eighty (80) hours worked every two (2) weeks, with forty-four (44) work hours one (1) week and thirty-six (36) work hours the other.

The Contractor may allow its employees to work a CWS schedule provided the requirements of this SOW 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 Government to the Contracting Officer’s Representative (COR)/Alternate COR (ACOR).

Holidays. The Government observes the following holidays:

New Year’s Day, January 1 Martin Luther King Day, the third Monday in January Presidents 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 Veterans Day, November 11 Thanksgiving Day, the fourth Thursday in November Christmas Day, December 25 With the exception of the events in paragraph 3.1.4.1.3 below, the Contractor is permitted to observe the above holidays IAW its corporate policy.

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

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

Overtime. Overtime cannot be charged directly to the Contract unless first approved in writing by the Chief of the Contracting Office (CCO).

Other Direct Costs (ODCs). (CLINs 0008, 0009, 0010, 0012, 0013, 0014) Travel. Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking is required. If required, temporary travel locations include Continental United States (CONUS) and Outside CONUS (OCONUS) locations.

CONUS. CONUS locations may include travel to Mobile, AL; Long Beach, CA; Port Hueneme, CA; San Diego, CA; Groton, CT; Stratford, CT; Washington, DC; Jacksonville, FL; Mayport, FL; Orlando, FL; Pensacola, FL; Carderock, MD; Indian Head, MD; Lexington Park, MD; St. Inigoes, MD; Bath, ME; Gulfport, MS; Pascagoula, MS; Butte, MT; Philadelphia, PA; Norfolk, VA; Bremerton, WA; Everett, WA; and Marinette, WI. This list is not all inclusive as locations may change over the life of the Contract.

OCONUS. OCONUS locations may include travel to Manama, Bahrain; Santa Rita, Guam; Pearl Harbor, HI; Sicily, Italy; Sigonella, Italy; Yokosuka, Japan; and Rota, Spain. Travel may include travel to Unites States Central Command (USCENTCOM) locations. OCONUS travel shall be conducted IAW DFARS clause 252.225-7040. This list is not all inclusive as locations may change over the life of the Contract.

Synchronized Pre-Deployment & Operational Tracker (SPOT). The Contractor may travel in combatant command locations. SPOT enables the validation of Contractors Authorized to Accompany the Force (CAAF), (i.e. Contractor personnel associated with specific contracts and subcontracts); their authorization and eligibility for access to specific DoD facilities; and their eligibility for specific Government Furnished Support (GFS). The Contractor shall initiate a Letter of Authorization (LOA) for each prospective traveler. The Contractor shall use the SPOT link, https://spot.dmdc.mil to enter and maintain data with respect to traveling/deployment personnel and to generate LOAs. LOAs will identify local authorizations, privileges, etc. as specified by DoD requirements. All defense Contractors working under this Contract shall carry a LOA with them at all times while deployed.

Local travel reimbursement. Reimbursement of travel by the Contractor or Subcontractor located within fifty (50) driving miles of the work site shall not be authorized.

The Contractor shall complete their travel request(s) IAW NAVAIR Clause 5252.232-9509 TRAVEL APPROVAL AND REIMBURSEMENT PROCEDURES. Upon completion of travel, the Contractor shall complete a trip report. (CDRL A018) Material. All materials not depleted during the performance of this Contract shall become Government property upon completion of this Contract and subsequent TOs. The Contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administrative expenses but shall not include profit/fee.

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

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

Transition out strategy. The Contractor’s overall transition out strategy shall be built around maintaining the mission of the ASI Division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the Contract, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall submit a Transition Out Plan, to include the minimum elements listed below. (CDRL A019) Work turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the Contract to the successor company. The Contractor shall establish and maintain effective communication with the incoming contractor or Government personnel for the period of transition via weekly status meetings.

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

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

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

Quality management. The Contractor shall develop, implement, document, and maintain a quality management system to ensure conformance with contractual requirements and the specific quality and performance requirements of specific TOs to be issued under this Contract. The quality management system should meet the intent of the American National Standards Institute/American Society for Quality (ANSI/ASQ) ISO 9001:2018 or another equivalent authority on quality. Regardless of the standards that are applied, the Contractor’s quality approach should be clearly defined and recognize the need to focus on customer satisfaction, defect prevention over inspection, management responsibility and continuous improvement. (CDRL A012) Inspection System Plan (ISP). The Contractor shall submit an ISP. (CDRL A013) Planning review. The Contractor shall conduct a thorough review of TO quality requirements to identify the controls, processes, skills, fixtures, tools, and test equipment needed to ensure product quality. The planning review shall also update inspection and testing techniques, instrumentation, and manufacturing methods and processes. Standard program data (test results, defects/failures identified, calibration results, etc.) that may be required by the Government to compile trend evaluation shall be available upon request.

Process documentation. The Contractor shall deliver process documentation. The Contractor shall make these documents available to all employees supporting the specific tasks. (CDRL A016) Technical Direction Letters (TDLs). When necessary, technical direction or clarification concerning the details of specific tasks set forth in the TOs shall be given through issuance of written TDLs. TDLs will not, in any manner, alter the scope of the Contract.

Quality surveillance and performance standards. The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, and review of deliverables. The Government will evaluate Contractor performance as outlined in the Contract Surveillance Plan (CSP) (Attachment TBD).

Government Furnished Property (GFP) and Government Furnished Information (GFI). GFP and GFI requirements will be identified under each TO issued, as required. Any GFI and GFP required to support this tasking will be provided to the Contractor within five (5) days after the TO is issued or after the CLIN supporting the tasking is exercised. Disposition of GFI and GFP will be made at TO completion or upon completion of the specific requirement. The Contractor shall have an approved property management system.

Software Rights. The Contractor shall provide the Government with unlimited rights of software to use, modify, reproduce, release, perform, display, or disclose computer software or computer software documentation in whole or in part, in any manner and for any purpose whatsoever, and to have or authorize others to do so. The Government will own such software rights and any software developed, and the Contractor shall deliver all source code, media files, configuration files, and programming documentation developed under this Contract, including all ancillary files, required for the Government to maintain, document, and reproduce the product.

Training Requirements.

Certification and Training. The Contractor is responsible for ensuring all employees have the required training and certification by verifying experience, special training, and qualifications.

Additional Training Requirements. Contractor employees shall complete Government specific training as required by the COR, provided by the Government, at no cost to the Contractor. This training includes new and recurring Navy requirements not available commercially, Naval Aviation Survival Training Program (NASTP) and aircraft specific training (e.g., NATOPS), Operational Risk Management (ORM), Anti-Terrorism, Information Assurance (IA) and other safety and security training as required by the host command to include Safety Stand Downs.

Safety Training and Surveys. Contractor employees shall complete Safety Training as directed by the Safety Officer and the COR or as directed by local command or instruction. Additionally, the Contractor shall participate in the Safety Survey Process.

Corporate Applications and IA. The Contractor shall gain access to the appropriate corporate applications. These systems may include but are not limited to NMCI, Financial Management System Initial Support Team (FIST), One Touch, Navy Enterprise Resource Planning (N-ERP), DoD Electronic Mall (EMALL), Naval Logistics Library (NLL), Naval Air Technical Data and Engineering Service Center (NATEC), Web Centers for Automated Testing (WebCATs), Joint Deficiency Reporting System (JDRS), Naval Ordnance Safety and Security Activity (NOSSA). Contractor personnel assigned to perform work under this contract and who require access to Government IT Systems shall comply with DoN IA and Personnel Security Requirements for Accessing Government IT Systems.

Special Contract Requirement 18-01 Sexual Harassment/Assault Response and Prevention (SHARP).

Sexual Assault and Sexual Harassment Policy. The Contractor shall ensure all employees comply with the Sexual Harassment/Assault Response and Prevention (SHARP) criteria outlines in Attachment 10 of this Contract.

SHARP Compliance: The Contractor shall certify that all employees performing work under this contract have been fully trained per the requirements in Attachment 10. If an employee is not proficient in English, SHARP training must be given in the employee’s native language. The COR shall be provided with the following information at a minimum: a copy of the Contractor’s SHARP policy, training materials, employee’s name, civil identification number and date trained, including language of training. Proof of SHARP training compliance is due within five (5) days after TO award and within 48 hours after arrival of new personnel on site.

The Contractor shall conduct training of all employees annually to prevent sexual assault and sexual harassment. This training must, at a minimum, ensure that all the Contractor employees understand the definitions and information outlined in Attachment 10.

Compliance with required SHARP training for each employee shall be reported to the Contracting Officer Representative prior to the employee being allowed access to the worksite. The Contractor’s SHARP policy must comply with the Department of Defense (DoD) policy in the Army Central Command (ARCENT) Area of Responsibility (AOR).

The DOD has adopted a policy to prevent sexual assault and sexual harassment. This SHARP policy mandates that Contractors and contractor employees in the Army Central Command (ARCENT) Area of Responsibility (AOR) shall not –

(1) Commit acts of sexual assault against any person on any camp, post, installation, or other United States enclave within the ARCENT AOR; or

(2) Sexually harass any person on any camp, post, installation, or other United States enclave within the ARCENT AOR.

The Contractor shall enforce standards of discipline, appearance, conduct, and courtesy IAW the published CENTCOM, USFOR-A and/or Base Commander Standards. For Contractors at Bagram Airfield (BAF) or for contractors transiting BAF, they must abide by the Commander Bagram Airfield (COMBAF) Standards of Conduct while performing at any level (prime or subcontractor) on BAF and any other installation and facility for which COMBAF standards are applicable. COMBAF Standards are published at: http://usfora.afghan.swa.army.mil/baf/des/pmo/Shared%20Documents/COMBAF%20Standards%20Book%20as%20of%208OCT17.pdf#search=COMBAF%20Standards.

Security.

Citizenship requirements. Only 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:

Investigative requirements.

Unclassified: All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30. All Contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management (OPM). The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office shall initiate the Contractor's Electronic Questionnaire for Investigations Processing (eQIP), and shall do a preliminary screening of the Contractor's eQIP for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government Security Office may deny the Contractor access to Government facilities and information and may prohibit the Contractor from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor's eQIP. In such cases, the Contractor employee may not perform on the Contract.

The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of CUI and to control distribution of CUI IAW DoD 5220.22-M NISPOM and SECNAV M-5510.36. All Contractor facilities shall provide an appropriate means of storage for Controlled Unclassified Information (CUI) and materials. All CUI shall be appropriately identified and marked as For Official Use Only (FOUO) IAW DoDM 5200.01, Information Security Program: CUI Volume 4 (enclosure 3).

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

All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):

Distribution Statement D: Distribution authorized to the DoD and U.S. DoD Contractors only (Critical Technology) (dated - _______). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: (Program/User Agency mailing address).

Classified: 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 Secret, with a safeguarding level of Secret. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW DoDM 5220.22 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.

The Contractor shall comply with security requirements specified in the DD-254 attached to this Contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled IAW the appropriate designation (CUI; FOUO; Covered Defense Information). Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this Contract shall be referred to the Technical Point of Contact (TPOC)/COR of this Contract for approval.

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

Security Clearance Information. The Contractor shall be responsible for employing personnel having at least the minimum level of security clearance as stated under each labor category specified herein:

SECURITY CLEARANCE INFORMATION

*Indicates key personnel.

Key personnel shall have the appropriate DoD Security Clearance or Interim Clearance as stated in the table under SOW paragraph 3.2.2.3 at the time of proposal submission. The number of key personnel for each category is listed in the table under SOW paragraph 3.4.1.1.

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

SAAR-N. All Contractor personnel requiring access to Government IT systems shall have an approved SAAR-N Form OPNAV 5239/14 Rev Sep 2011 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.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf. SAAR-N forms shall be submitted to the COR, Government TPOC, or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted Associate.

CACs/local badges. Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to the DMDC TASS Overview Guide, Version 5.3.2, Dec 2014. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site IAW the DMDC TASS Overview Guide Version 5.3.2, Dec 2014 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.

DD-254. The Contractor shall comply with security requirements specified in the DD-254 Attachment XX to this Contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled as FOUO. 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.

Information security. If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and CUI and to control distribution of CUI IAW SOW Paragraph 3.2.5.

Marking. All information generated by the Contractor shall be properly marked. FOUO information generated and/or provided under this Contract shall be marked IAW DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DoDD 5230.24 and program Security Classification Guidance.

Public release for Classified and Unclassified Information. Any controlled information pertaining to this Contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release via the COR.

Loss, compromise, and/or electronic spillage of Classified Information or CUI. All instances of loss, compromise, and electronic spillage of Classified Information or CUI shall be reported to the COR, TPOC, and Government Security Office within twenty-four (24) hours of the incident occurring.

Operations Security (OPSEC). The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the Contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance (IA) and Communications Security (COMSEC). The OPSEC program shall be IAW National Security Decision Directive (NSDD) 298 and at a minimum shall include:

a. Assignment of responsibility for OPSEC direction and implementation.

b. Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

c. Establishment of OPSEC education and awareness training.

d. Provisions for management, annual review, and evaluation of OPSEC programs.

e. Flow down of OPSEC requirements to subcontractors when applicable.

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

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

Detailed Support Requirements.

3M Support. The NAVSEA 3M system is used throughout the U.S. Navy as part of the in-service engineering, maintenance, and reliability of installed C4I equipment by providing engineering management, readiness, and reporting procedures for U.S. Navy equipment suites.

3.3.1(a) (CLIN 0001/0002) Provide 3M support and services throughout the operation and maintenance phase of the system’s lifecycle. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.14.

3.3.1(b) (CLIN 0001/0003) Provide 3M support and services throughout the research and development phases of the system’s lifecycle. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.14.

3.3.1(c) (CLIN 0001/0004) Provide 3M support and services throughout the production phases of the system’s lifecycle. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.14.

3.3.1(d) (CLIN 0001/0005) Provide 3M support and services to Foreign Military Sales (FMS) systems and equipment. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.14.

3.3.1(e) (CLIN 0001/0006) Provide 3M support and services to Working Capital Fund (WCF) systems and equipment throughout all phases of the system’s lifecycle. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.14.

3.3.1(f) (CLIN 0001/0007) Provide 3M support and services to non-Navy systems and equipment. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.14.

The Contractor shall analyze Planned Maintenance System (PMS) logistics packages for 3M systems including equipment maintenance requirements; PMS schedules; feedback reports; configuration change reports; procedural content; parts and material information; and distribution data.

The Contractor shall access the data maintained by NAVSEA Logistics Center (NAVSEALOGCEN) quarterly in February, May, August, and November using the Navy Marine Corps Intranet (NMCI) portal.

The Contractor shall demonstrate efficiency in the use of the Configuration Data Management Database Open Architecture (CDMD-OA) system, PMS Management Information System (MIS), and Ships 3M History Open Architectural Retrieval System (OARS).

The Contractor shall provide procedural analysis of changes that may have occurred in Maintenance Requirement Cards (MRCs) to include updated procedures, warnings, cautions, notes, and Maintenance Index Page (MIP) scheduling changes affecting an MRC.

The Contractor shall evaluate new MRCs to determine ship applicability and schedule impacts.

The Contractor shall determine which MRCs apply to specific ship configurations across the fleet. The Contractor shall consider Navy maintenance policies, application of maintenance guidelines, and maintenance audit/inspection criteria.

The Contractor shall develop standardized reports, dashboards, and metric reports as part of the data analysis of the various sources including shipboard data and shore based 3M and Navy Logistics data.

The Contractor shall produce logistics maintenance data packages for C4I equipment covering planned maintenance on systems found on DoD platforms. These data packages will directly support fleet personnel in their daily duties of planned maintenance activities covering a wide range of C4I systems based communication and weapon systems.

The Contractor shall execute production, distribution, integration, and training of 3M and Navy Logistics products to the fleet, air-based platforms, shore activities, and international partners under the FMS program.

The Contractor shall process PMS data to produce PMS Force Revisions (FRs) to include: creating PMS Change Indicator documents for each updated PMS document; managing the distribution of titles to control which documents go to which activities; and managing activity applicability to PMS titles to determine which titles go to which ships.

The Contractor shall develop a process to ensure the quality and correctness of each PMS and Tailored Force Revisions (TFR) title. (CDRL A012) The Contractor shall compile data, processes, and produce PMS FR packages to meet quarterly revision distribution schedule. (CDRL A010) The Contractor shall process PMS data to produce quarterly TFRs. (CDRL A015) In support of NAWCAD WOLF tasking for the maintenance of the official PMS content models and database schemas, the Contractor shall deliver content models that meet emerging requirements. (CDRL A004) The Contractor shall develop updates to 3M and Navy Logistics data structures including Document Type Definitions (DTD) and database schemas.

The Contractor shall maintain the PMS procedure content model for MIPs and MRCs using Standard Generalized Markup Language/Extensible Markup Language (SGML/XML) DTD and XML Schemas. This includes data transformation scripts using eXtensible Style Language for Transformations (XSLT) for presentation in NAVSEA approved viewers. Required outputs include on screen and printed layouts. The PMS DTD is the authoritative data structure used for storing PMS documents and 3M data.

The Contractor shall have the ability to adapt to the various presentation methods and approaches required to support tasking.

The Contractor shall install and maintain certification requirements for Navy maintenance applications on multiple existing and emerging IT server and network resources throughout the Fleet including the Navy Information and Application Product Suite (NIAPS) and Consolidated Afloat Networks and Enterprise Services (CANES) infrastructure or their replacement systems as defined by NAWCAD WOLF and its customers.

The Contractor shall perform software engineering and life-cycle maintenance support for 3M scheduling, viewing, and authoring applications. (CDRL A004) The Contractor shall prepare and update requirement traceability matrices. (CDRL A005) The Contractor shall prepare and update software design and testing documentation IAW standard quality management plan. (CDRLs A024, A026, A027) The Contractor shall provide PMS applications development support for the PMS Maintenance Management, Viewing, and Scheduling Systems. This is a fleet-wide (surface and subsurface) system to automate all scheduling and administrative tasks associated with the Navy PMS.

Supporting the fleet 3M Requirements Management Board (RMB), the Contractor shall assist NAWCAD WOLF in providing total development support, including installation, configuration management, implementation of fleet training, user technical support, business process revisions, and deployment planning. Installation environments include Common PC Operating System Environment (COMPOSE), NMCI, Total Ship Computing Environment (TSCE), NIAPS, CANES, and other future shipboard and shore IT environments.

The Contractor shall provide application lifecycle support for the NAVSEA PMS document authoring systems and tools. These systems are used by Commodity Specialists and ISEAs to author PMS MRCs and MIPs. The software allows authors to create and edit complex engineering and technical documents stored in multiple markup language formats. These systems and tools are designed to be NMCI-compliant.

As authorized by the Navy and as allowed by ship deployment schedules, the Contractor shall conduct installation, training, and technical tasking of various 3M, technical manual, and other Navy logistics systems aboard the Navy’s surface and subsurface fleet.

The Contractor shall install Navy maintenance applications on multiple existing and emerging IT server and network resources throughout the fleet and ashore while maintaining certification requirements for installation on these networks.

The Contractor shall coordinate with the appropriate fleet authorities and the current shipboard hosting agencies.

The Contractor shall provide and report on troubleshooting support services for PMS applications to meet fleet requirements via phone, e-mail, message, or on-site visit.

The Contractor shall assist NAWCAD WOLF to provide shipboard support in all of the major fleet concentration areas in CONUS and OCONUS. The Contractor shall be prepared to handle surge capacities, response times, and the flexibility to recognize the fleet’s deployment needs.

The Contractor shall prepare cybersecurity documentation for application Certification & Accreditation (C&A) of Government software and systems as dictated by specific TOs (CDRL A002) The Contractor shall support classic tools and design, develop, and support emerging tools, database platforms, and technologies in PMS applications supported by NAWCAD WOLF. Examples include cloud hosting, containers, micro-services, XML/XSLT, JavaScript Object Notation (JSON), .NET Core, Agile Core Services, Microsoft SQL (MS SQL) Server, SQLite, Oracle IaaS, and PostgreSQL. (CDRLs A004, A024, A025) The Contractor shall support the NAWCAD WOLF PMS applications in migration to and interfacing with next generation, enterprise-level maintenance management systems, pilots, and prototypes being developed by the Navy. Possible examples include the Naval Operational Business Logistics Enterprise (NOBLE), Naval Operational Maintenance Environment (NOME), Naval Aviation Maintenance System (NAMS), Naval Operational Supply System (NOSS), Integrated Data Environment (IDE), Light Fidelity (LiFi) Networks, Electronic Remote Monitoring (eRM), and Tactical Advancements for the Next Generation (TANG).

Software engineering, development, and integration. The Contractor shall provide software engineering, development, and integration support and services.

3.3.2(a) (CLIN 0001/0002) Provide software engineering, development, and integration support and services throughout the operation and maintenance phase of the system’s lifecycle. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.10.

3.3.2(b) (CLIN 0001/0003) Provide software engineering, development, and integration support and…