N68520-21-RFPREQ-680000A-0004_SOW d1.docx

N68520-21-RFPREQ-680000A-0004

Statement of Work Version D1

STATEMENT OF WORK

Command Fleet Readiness Center Headquaters Logistics Technical Data Department National Contract

1.0 Scope: This non-performance based Statement of Work (SOW) supports the mission of the Naval Air Systems Command (NAVAIR) Command Fleet readiness Center (COMFRC) Headquarters (HQ) Logistics Technical Data Department to the extent defined herein. The Logistics Technical Data Department provides lifecycle support for technical data products to naval aviation weapons systems. Primary products include Technical Manuals (TMs), Technical Directives (TDs), Technical Data Packages (TDPs), Job Performance Aids (JPAs), 3D Simulations, Multimedia Files, Digital Graphics forms (e.g. Graphics and Wiring Diagrams for Wire Tracing and Illuminator Functionality), Project Management, Weapon System Configuration Data, and other related Logistical Data Products.

The NAVAIR COMFRC HQ FST Logistics Technical Data Department requires support as specified in individual task orders. The support may include either utilization of government facilities or Contractor work sites. Potential customers requiring support include the following sites: Fleet Readiness Center East (FRCE) at Cherry Point, NC; Naval Air Technical Service Center (NATEC) and Fleet Readiness Center West (FRCW) and Naval Air Warfare Center (NAWC), Weapons Division (NAWCWD) Detachment at North Island, CA; NAWC AD China Lake, CA; Fleet Readiness Center Southeast (FRCSE) at Jacksonville, FL; Naval Air Systems Command (NAVAIR) Patuxent River, MD; Naval Air Warfare Aircraft Division (NAWCAD) Patuxent River, MD; Naval Air Warfare Center Training Systems Division (NAWCTSD) Orlando, FL, and NAWCAD, Lakehurst, NJ.

The scope of this contract includes support to the NAVAIR COMFRC HQ FST Logistics Technical Data Department in the following areas: (1) technical data management support, (2) technical publishing support, (3) technical library/repository/Data Control Center (DCC) support, (4) logistics information technology support, (5) independent quality assurance support, (6) digital & physical access, control, content, transaction/exchange, and protection, (7) technical data content’s suitability & completeness for intended use analysis and configuration audits (e.g. DODI5010.12M, ASME , ASME Y14.41 & Y14.42, S1000D), and (8) reporting.

Note: Preparation and publishing products may be ordered in either of two methods: fixed price CLINs or non-fixed price CLINs. Under both methods, a task description will accompany the task order defining specifics of the task. For example, all task orders requiring delivery of Technical Manual (TM) Issues (I.e., Basic, Revision, Change, Rapid Action Change (RAC), Interim Rapid Action Change (IRAC) or Change Notice) shall be described in a Technical Manual Contract Requirements (TMCR) included in the Task Order. The types of TMs included in the Naval Aviation inventory include, but are not limited to, those listed in Attachment 01 (Technical Manual Types). Task orders for technical manuals may require use of a combination of fixed-price and CPFF CLINs.

2.0 Applicable Documents

See Attachment 1, Applicable Specifications and Standards

DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM) 28 Feb 2006

SECNAV M-5510.36 Information Security Program, 30 Jun 2006

DoD 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18) 24 Feb 2012

DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42) Sep 1998

DoD 5230.24 Distribution Statements on Technical Documents, Change 1, Effective 28 Apr 2016

SECNAV M-5510.30 Personnel Security Program Jun 2006

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

2.1 Acronyms

COR – Contracting Officer’s Representative – a Government Representative assigned by the Contracting Officer to perform surveillance and to act as liaison with the Contractor.

TPOC – Technical Point of Contact – Technical Advisor to the Contracting Officer’s Representative

CDRL – Contract Data Requirements List

DCC – Data Control Center

DID – Data Item Description

ECP – Engineering Change Proposal

LSA – Logistic Support Analysis

IA/IT/PS – Information Technology/Information Assurance/ Physical Security

JEDMICS – Joint Engineering Data Management Information Control System

JTDI – Joint Technical Data Integration

TDP – Technical Data Package

TD – Technical Directive

TM – Technical Manual

TMAPS – Technical Manual Application System

TMCR – Technical Manual Contract Requirements

QA – Quality Assurance – actions taken by the Government to assure services meet the requirements of the Performance Work Statement.

JPA – Job Performance Aid

JDRS – Joint Deficiency Reporting System

RO – Requiring Office

3.0 Requirements

Start of Work Meetings: All task orders will have a Start of Work meeting. Start of Work meetings will be scheduled within 10 working days of the task order award. If there are extenuating circumstances, i.e. both the contractor and Task Order Contracting Officer’s Representative (TOCOR) are not available within the 10 working days, the TOCOR shall request permission from the Contracting Officer Represenitive (COR) Manager to delay the Start of Work meeting.

3.1 Compatibility - The Contractor shall maintain the capability to receive, protect, analyze, prepare, and deliver reports, documents, digital media, and software packages compatible with the Government IT, IA, and PS environment through the security classification specified on the task order.

The current NAVAIR Next Generation Enterprise Network (NGEN) IT operating environments hardware and software core build configurations will be defined at contract award. The configuration compatibility required for this contract is updated and posted at Homeport quarterly (https://www.homeport.navy.mil). These are Microsoft™ operating system based.

The current NAVAIR Technical Manual authoring, presentation, software, and media conformity environment is defined at Naval Air Technical Data and Engineering Service Center (NATEC) website [https://mynatec.navair.navy.mil/] under appropriate topic of “NAVAIR Policies, Briefings and Guidelines”.

The Contractor shall maintain the ability to interface with and transfer data to and from the requiring NGEN software applications and their upgraded versions. The Contractor shall maintain, and apply state-of-the-art virus software at all transactions (incoming and outgoing) so as to ensure that all media are virus free when delivered. IA, IT, and PS requirements dictate conformance. The Contractor shall be capable of Internet and LAN communications with 6.8.5 personnel. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with 6.8.5 personnel during working hours whether at Contractor work site or on travel.

3.1.2 Work Locations and Facilities

3.1.2.1 Work Location(s) - Approximately 45 percent of work will be performed at the Government site and 55 percent of work to be performed at Contractor site. The place of performance under this contract will vary and will be specified in each task order. Government site(s) include: Fleet Readiness Center East (FRCE) at Cherry Point, NC; Naval Air Technical Service Center (NATEC) and Fleet Readiness Center West (FRCW) and Naval Air Warfare Center (NAWC), Weapons Division (NAWCWD) Detachment at North Island, CA; NAWC AD China Lake, CA; Fleet Readiness Center Southeast (FRCSE) at Jacksonville, FL; Naval Air Systems Command (NAVAIR) Patuxent River, MD; Naval Air Warfare Aircraft Division (NAWCAD) Patuxent River, MD; Naval Air Warfare Center Training Systems Division (NAWCTSD) Orlando, FL, and NAWCAD, Lakehurst, NJ. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.

3.1.2.2 Meeting(s) Support - The Contractor shall have the capability to conduct meetings within 50 miles of the following Government locations: Cherry Point, NC, Patuxent River, MD, Jacksonville, FL, North Island, CA and Lakehurst, NJ The contractor meetings shall be capable of accommodating a minimum of 25 persons and have a Video Teleconference (VTC) capability (non-GFE). Additionally, the contractor shall ensure there is capability to conduct meetings with presentations. This contract does not include the leasing or renting of facilities.

3.1.3 Contract Status Reporting – To be relased with the Request for Proposal (RFP).

3.1.4 Work Schedule to include Compressed Work Schedule (CWS), Overtime, Holidays, and Installation Closure

3.1.4.1 Normal Working Hours: The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are 8.5 hours (including a 30-minute lunch break), from 0700 to 1530 each Monday through Friday (except on the holidays specified in paragraph 3.1.4.1.2). Certain tasking, to be specified in individual task orders, will require 7-days a week/365 days a year, including holidays. Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday –Friday.

3.1.4.1.1 Compressed Work Schedule (CWS): 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 weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday 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.

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 when required by the Government.

3.1.4.1.2 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 Birthday, the third Monday in February Memorial Day, the last Monday in May Juneteenth, June 19 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

With the exception of the events in section 3.1.4.1.3 below, the contractor is permitted to observe the above Holidays in accordance with its corporate policy.

3.1.4.1.3 Installation Closure: 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 performing non-mission essential work shall follow their parent company’s policies.

While generally contractor personnel may not perform work on-site at a Government facility without Federal personnel present, 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. Any mission essential services to be provided will be identified at the task order level, if applicable.

3.1.4.1.4 Overtime: Overtime cannot be charged directly to the contract unless first approved in writing by the TOCOR and the Chief of Contracting Office (CCO).

3.1.5 Other Direct Costs - ODCs are based on a per annum amount.

3.1.5.1 Travel -Travel will be allowable only when it is essential to the performance of the task detailed in Section 3.3. Reimbursement for travel performed shall be in accordance with the Department of Defense Joint Travel Regulation (http://www.defensetravel.dod.mil/site/travelreg.cfm). The TOCOR shall approve all travel performed in support of this contract at least five (5) days prior to the commencement of the travel. TOCOR approval for local travel expenses is required. 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 all government and DOD contractor sites within CONUS. Locations may change over the life of the Contract.

3.1.5.2 Material - Contractor shall comply with the procedures set forth below.

(a) This is a service contract and the procurement of material of any kind that is not incidental to and necessary for contract performance may be determined to be unallowable costs pursuant to FAR Part 31. The term “material” supplies and materials. Any material provided by the contractor is subject to the requirements of the Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and the applicable Department of Navy regulations and instructions.

The costs of general purpose business expenses required for the conduct of the contractor’s normal business operations will not be considered an allowable direct cost in the performance of the contract. General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies. The items previously listed are allowable if it is equipment incorporated into systems delivered under the contract. The term “other direct costs” includes incidental services performed by other than the prime contractor or approved subcontractors in performance of this contract.

(b) List of Allowable Material:

Material includes, audio/video support, binders, CDs, copies. The material expenses shall be authorized by the TOCOR/TPOC, only those material expense having prior TOCOR/TPOC approval shall be reimbursed to the Contractor. Reimbursement for material shall be in accordance with FAR 31.201 and Section H clause 5252.232-9509.

c) In addition to TOCOR concurrences and Contracting Officer approvals listed below, IT resources may not be procured unless the approvals required by Department of Defense purchasing procedures have been obtained. IT resources are defined as any equipment and or interconnected system and/or subsystem of equipment used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data information. IT resources include personal computers, laptops, printers, software, servers, hubs, routers, phones, facsimile machines and any related maintenance, telecommunications, training, or other support services. To obtain IT approval the contractor shall prepare an IT Request within the Navy Information Dominance Approval System (NAV-IDAS) with a complete list of items to be obtained. The approved IT Procurement Request (ITPR) shall be provided to the TOCOR prior to procurement of IT resources.

(d) Prior written concurrence from the TOCOR and approval from the Contracting Officer shall be required for all purchases of material (IT resources or non-IT resources) in accordance with the dollar thresholds listed in paragraph (e) below. Requests for approval shall include a list of the material to be procured, an explanation of the need for the material, approved NAV-IDAS ITPR (if applicable), a listing of quotes received, the reason for the selected source, and the determination of price reasonableness. If the procurement is sole sourced to a particular supplier, include the rationale for limiting the procurement to that supplier.

Only material included in the above List of Allowable Material may be procured under this contract. No material with a single unit cost of $150,000.00 or greater shall be procured under this contract. No single procurement with a total value, that is the sum of all items, of $750,000.00 or greater may be procured under this contract. Procurements shall not be split to circumvent these thresholds.

When it is necessary for the contractor to procure material to immediately respond to emergency requirements, the contractor shall obtain prior verbal authorization from the TOCOR. Contractor shall then request authorization in writing to the TOCOR within the next business day of the procurement. The written authorization must reference when the verbal authorization from the TOCOR occurred. These emergency requirements are for any items with a total value greater than $10,000.00.

For procurement of all software licenses, regardless of total value, TOCOR concurrence and Contracting Officer approval is required. If the TOCOR concurs with the request, the TOCOR will provide the request for the approval to the Contracting Officer. The Contracting Officer will provide notification of disapproval or approval to the TOCOR and Contractor.

(e) Approval Thresholds:

For procurements with a total value of $10,000.00 and below, no prior TOCOR concurrence or Contracting Officer approval is required.

For procurements with a total value between $10,000.01 and $150,000.00, prior TOCOR concurrence is required.

For procurements with a total value between $150,000.00 and $750,000.00, both TOCOR concurrence and Contracting Officer approval is required prior to purchasing the material. If the TOCOR concurs with the request, the COR will provide the request for approval to the Contracting Officer. The Contracting Officer will provide notification of disapproval or approval to the TOCOR and Contractor.

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

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

3.1.8 Non-Disclosure Agreements (NDAs) And Organizational Conflicts Of Interest (COIs) - In the performance of the contract, the Contractor may have access to non-public information. The Contractor shall require that any employee performing services under this contract execute a non-disclosure agreement satisfactory to the Contracting Officer Representative and Contracting Officer. The non-disclosure agreement shall acknowledge the Contractor and employees’ duties with respect to non-public information and promise to comply with those obligations. The Contractor shall provide signed Non-Disclosure Agreements for each employee supporting NAVAIR COMFRC HQ FST Logistics Technical Data Department Contracting Officer Represenattive Manager no later than five (5) business days after task order award.

Consistent with the terms and conditions of paragraph (e)(5) of NAVAIR 5252.209-9510 Organizational Conflicts of Interest (Services), with respect to proprietary data of third parties, and DFARS 252.227-7025, Limitations on the Use Or Disclosure of Government-Furnished Information Marked with Restrictive Legends, with respect to technical data, the Contractor shall not use, modify, reproduce, release, perform, display, and disclose any non-public information provided to or obtained by the Contractor in the course of performing this contract for other than Government purposes, and shall not do so for any commercial or personal purpose.

In the event that the Contractor knows of or identifies that it has a commercial interest in the subject matter of any proposed or on-going agreement with respect to which contract services are to be performed, the Contractor shall consider such interest a potential conflict of interest under NAVAIR 5252.209-9510(g) and promptly disclose it to the Contracting Officer Representative and Contracting Officer.

3.1.9 Transition Strategy - The overall strategy shall be built around maintaining the mission of NAVAIR COMFRC HQ FST Logistics Technical Data Department 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.

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

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

· 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.

- IA/IT/PS provisions for facility and personnel and pertinent technical data marking, protection, consumption, transfer, and reporting criteria are immutable and fully apply, before, during, and after transfer.

3.2 Security

3.2.1 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. Note: Waivers not applicable for Distribution Statement B & F Export Controlled technical data work. 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.

3.2.2 Investigative Requirements - 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 Specification. Additional classification levels may be defined at the task order level.

Classified: All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the task order, Contract Security Specification. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

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

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

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

3.2.3.2 Command Access Cards (CAC) / Local Badges - Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges. 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 Contracting Officer’s Representative, the Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract.

3.2.3.3 DD-254 - The contractor shall comply with security requirements specified in the task order. 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. Contractor personnel shall be subject to a government security investigation and must meet eligibility requirements for access to classified information at the level noted in the Attached DD254 (Attachment 4).

3.2.3.3.1 Security Requirements: Minimum Security Requirements are defined in Attachment 4 DD254.

3.2.3.3.2 Sensitive Information: Contractor employees shall not discuss or disclose any sensitive information to which they have access to during performance under this contract.

3.2.4 Information Security - 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 controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), SECNAV M-5510.36, and DFARS 252.204-7012. If the work is performed at the Government’s facility, the Contractor shall comply with OPNAVINST 5239.1B or other applicable government site policy and instructions.

3.2.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 in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance.

3.2.4.1.1 Existing IP markings shall not be altered or edited. NDAs must be in place for all participants prior to any work being performed either in house or by subtier Contractors. Non-conforming IP markings are not viable deliverables and require direction from COTR and TOCOR/CO to treat/mitigate (e.g. MIL PRF 32216A release).

3.2.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 for approval prior to release through the NAVAIR public affairs office.

3.2.4.3 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information.

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

Additionally, for all CUI categories, cyber incident and compromise reporting, including flow down, are as defined at DFARS 252.204-7012.

3.2.4.4 Prescreening - The Contractor shall, upon receipt of any and all data, use appropriately vetted and authorized personnel to immediately prescreen data for pertinent, conforming CUI and Classified markings (both human eye readable and IT/IA based) prior to start of work. Any nonconforming markings (including CUI marking involving conforming Limited Rights markings or non-conforming Intellectual Property (IP) assertion markings shall be reported the same day via telephone and email notification to COR via TOCR, and necessary data segmentation/protection shall be implemented until pertinent instructions are received from COR for disposition.

In the case of mismarked, loss, compromise, or suspected compromise, IA/IT security process reporting shall conform to the pertinent NISPOM section for “Reports of Loss, Compromise, or Suspected Compromise”, and for CUI issues, shall conform to the pertinent DFARS 252.201-7012 incident reporting.

Additionally, for any conformingly IP assertion marked data received (i.e. other than Unlimited Rights), the Contractor shall not proceed with work until receipt of written Contracting Officer (CO) remediation clearance (i.e. either via remediated data or negotiated Special License, or, USG CO release to use as per DFARS inherent and default intellectual property license), and, Contractor subsequently receives requisite DFARS Clause Non-Disclosure Agreement (NDA) from IP holder. COR shall be provided copies of all NDAs. All delays associated with nonconforming markings and NDAs are included in deliverable’s cycle times and performance reporting.

Note: If non-conforming IP markings and/or NDA obtainment causes a work stoppage beyond the negotiated period of performance, a normal contract notification and change processes applies.

3.2.5 Operation 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 Requiring Office (RO)and contractor in support of the mission.

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

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

3.3 Detailed Support: The Contractor shall provide the following detailed support to be determined and defined at the task order level:

3.3.1 Technical Publication Support Requirements

3.3.1.1 Develop, update/edit/prepare and deliver technical publications including, but not limited: original research and writing, engineering prints for Engineering Change Proposal (ECP) data, Logistic Support Analysis (LSA) data for logistics inputs, Installation drawings, preliminary parts lists, and validation/verification changes.

3.3.1.2 Produce, update/edit/prepare & deliver existing technical publications in accordance with NAVAIR approved standards including, but not limited to S1000D, MIL-STD-3001 and/or MIL-DTL-81310, MIL-PRF- 81927/28/29, MIL-PRF-81919, MIL-STD-38784, MIL-DTL-81927, MIL-PRF-87269 and in accordance with and the policies and procedures within NAVAIR 00-25-604 and NAVAIR 00-25-100.

3.3.1.3 Develop, update/edit/prepare/sanitize Technical Publications for Foreign Military Sales (FMS) programs utilizing NAVAIR sanitization processes as defined at the task order level.

3.3.1.4 Participate in Quality Assurance (QA) events (in-process reviews, on object or table top validations or verifications) associated with the development and sustainment of NAVAIR Technical Publications. The location of the QA events may be hosted at either the Contractor or at a Government site. Examples of types of efforts to be coordinated and supported include, but are not limited to: Planning Meetings, Start of Work Meetings, In-Process Reviews, Adequacy Reviews, Validation, Verification, Validation/Verification, and contractual Deliverable Technical Acceptance Reviews. Assess quality plans and processes and related documentation.

3.3.1.5 Maintain (operate/administrate) the Government's in-house Common Source Data Base (CSDB) system at designated sites. The functionality of this Government controlled CDSB is to store, manage the NAVAIR Technical Publication source content (text, graphic, multimedia) source files. The Contractor shall interface to the NAVAIR Common Source Data Base (CSDB) Content Management System (CMS) for Technical Publication data modules and supporting files. Support files are to be determined by program specific requirements as defined in the task order. The Contractor shall administer the government designated CSDB CMS for limited, controlled access to program specific Technical Publication related files.

3.3.1.6 Develop, update, deliver and sustain, NAVAIR Technical Publications utilizing NAVAIR distribution processes in accordance with NAVAIR 00-25-604. Analyze and report (monitor quality) of all fielded NAVAIR Technical Publications, via data analysis of JDRS and TMAPS

3.3.1.7 Maintain/manage sanitized Technical Publications for Foreign Military Sales (FMS) program customers utilizing NAVAIR FMS distribution processes in accordance with NAVAIR 00-25-604.

3.3.1.8 Track the digital distribution process for all fielded NAVAIR Technical Publications, via data analysis of the ELMS data table within TMAPS, and the information available via integrated toolset within Joint Technical Data Integration (JTDI).

3.3.1.9 Sustain (monitor status) of the digital distribution process for all FMS Technical Publications, via data analysis of the FMS version of the ELMS data table within TMAPS, and the information available via integrated toolset within JTDI.

3.3.1.10 Sustain, monitor inventory of all fielded NAVAIR Technical Publications (Domestic and FMS), via data analysis of the ELMS data table within TMAPS.

3.3.1.11 Update, modify, and maintain any of the NAVAIR digital technical data presentation systems. (Standard Interactive Electronic Technical Manual (IETM) Viewer (NSIV) and the NAVAIR Technical Publication Management Console (NATPMC) are examples of a NAVAIR digital technical data presentation system). Perform Information Technology obsolescence engineering, system engineering including managing information technology refresh, system integration, system test and on-going sustainment and training of NAVAIR digital presentation systems.

3.3.1.12 Provide independent QA reviews, or other related quality services relating to technical data developed by third party technical data preparation agents as designated by task order. On an as needed basis, the contractor may perform independent QA assessments of technical data products developed by third parties such as OEMs. Forward the results of such reviews to the Government for review and further action.

3.3.1.13 Document findings, furnish findings, and manage remediation activities for technical data QA program. Efforts shall be designed, implemented, administered, or assessed as defined in ISO-9000 type quality program policy. The contractor shall use statistical quality controls and metrics for identification, reporting, analysis, and resolution of critical, major, and minor defects.

3.3.1.14 Develop JPAs for inclusion in existing IETMs or augmenting existing TMs in the formats identified in task orders. Minimum baseline application requirements for output of FAM compliant, MPEG, JPEG or other similar multi-media file types. All task orders requiring use of applications other than specified as baseline requirements shall require approval of AIR-6.8.5 HQ before task order is awarded. Applicable specifications, look and feel requirements, and content shall be specified in individual task orders.

3.3.2 Logistics Configuration Management and Technical Directive Support

3.3.2.1 Develop, update, maintain and support status accounting of weapon system configurations, via data analysis of Deckplate, TDRS data, and associated systems as directed in the specific task order.

3.3.2.2 Prepare and coordinate requests for Nomenclature and National Stock Number (NSN) for configuration items.

3.3.2.3 Prepare, review, and coordinate engineering changes and associated documentation, such as ECPs, requests for deviation (RFDs), Notices of Revision (NORs), TDs, Specifications, and Specification Change Notices (SCNs).

3.3.2.4 Perform analysis of equipment and associated documentation to determine recommended Work Unit Code (WUC) assignments.

3.3.2.5 Develop, update, improve, maintain, and provide curriculum and training or workshops in the areas of technical data and related configuration management activities.

3.3.2.6 Update, maintain and improve Optimized Organizational Maintenance Activity (OOMA)) baselines, update, maintain and improve Type Equipment Codes.

3.3.2.7 Support weapon system changes through the development of tech directives and supporting change control board actions. Develop, update, maintain, and improve fleet bulletins and Rapid Action Maintenance/Minor engineering Change (RAMEC).

3.3.3 Technical Libraries, Repositories, and Data Control Center (DCC)

Note: The term library (ies) shall be used herein to mean library, repository, or DCC. The library (ies) are located at the Government’s facilities.

3.3.3.1 Operate and maintain designated libraries/repositories/DCCs maintained for storage, retrieval, replication, distribution, archiving, and customer service. Operate libraries and provide to the Government data/media management, confidential, unclassified, and sensitive administrative project support.

3.3.3.2 Operate and maintain a secret/classified document control process to provide accountability of data/media and to perform data management functions necessary to support the various libraries, when secret/ classified data/medium is maintained.

3.3.3.3 Operate, maintain, store, manage and support the Navy’s digital and non- digital drawing files, TM libraries, TDP repository, configuration management and other programmatic data files and databases. Tasks may include:

a. Data/Media receipt, review and entry

b. Data/Media Control

c. Data/Media Management

d. Inventory and Audit

e. Data Reproduction

f. Data Archiving

g. Data Acquisition and retrieval support

h. Management of Master Data Packages or Master Files

i. Management of Technical Publication Deficiency Reports (TPDRs), Interim Rapid; Action Changes (IRACs), Local Engineering; Directives (LEDs) and other documents

j. Technical Documentation Research

k. Relocation of data and satellite libraries

l. Data Dissemination/Courier Service

m. Mail Operations

n. Administrative Support

Operate libraries in accordance with NAVAIR 00-25-100, Naval Air Systems Command Technical Publication Library Management Program, and any local instructions that apply. It is the Contractor's responsibility to maintain the most current issue or changes of instructional documentation and to ensure that the Contractor's employees have a thorough working knowledge of these instructions and procedures and that they are kept abreast of any changes that apply to the technical tasks defined in this SOW. Such documentation shall include, but not be limited to, those listed in Attachment 6.

3.3.4 Logistics Information Technology

3.3.4.1 Develop improve, enhance and maintain requirements analysis, programming, system documentation, maintenance and training for NAVAIR digital tech data systems. Requirements include developing functional descriptions, systems design, systems specifications, data dictionaries, and user documentation. These products shall be forwarded to the Government for review and approval prior to implementation. All supported IT systems shall be web based using current, FAM approved development tools and web technologies.

3.3.4.2 Improve and update design, and maintain database schemas using industry standard relational databases, e.g. Oracle, SQL Server and Sybase. Database schemas shall be forwarded to the Government for review, concurrence, and approval prior to implementation.

3.3.4.3 Assess system interface requirements, and analyze and design required interfaces using current server to server standard software technology, e.g. web services. Proposed interfaces shall be forwarded to the Government for review and approval prior to implementation.

3.3.4.4 Apply applicable and current DoD security policies and requirements and implement systems that adhere to current Information Assurance Management directives. Systems must be flexible enough to rapidly change in concert with new security policies.

3.3.5 Technical Data Package (TDP) - Acquisition and sustainment support.

3.3.5.1 Provide TDP assessment support to assist AIR-6.8.5 and acquisition program’s efforts in determining maturity of engineering data and the impact of data rights restrictions on system development costs. Assist in development of program IP Strategies and Technical Data Rights Strategies, and TDP Strategies.

3.3.5.2 Provide TDP review and assessment support for Systems Engineering Technical Reviews to include, but not limited to System Functional Review (SFR), and Preliminary Design Review (PDR). Contractor will evaluate TDP maturity, compliance with American Society of Mechanical Engineers (ASME) Y14.100 Engineering Drawing Practices. Engineering Drawing Practices, Computer Aided Drafting (CAD) practices to include, but not limited to modeling practices, modeling organizational schemas, and model validation practices. Contractor personnel will require expertise in multiple CAD software packages such as Autodesk AutoCAD ®and Inventor®, Siemen’s NX ® and Solid Edge®, Assault Systems CATIA® and Solidworks®, and PTC CREO®, as well as model validation software packages such as CADIQ®.

3.3.5.3 Provide support in development and implementation of Product Lifecycle Management (PLM) software solutions in support of TDP Management and establishment of a TDP authoritative source. Support will consist of application software administrative support, database administration, and establish processes for delivery of the TDP to the PLM environment hosted by the Government. The contractor will verify and validate the TDP metadata requirements when designing standardized processes for TDP delivery to the Government PLM repository.

3.3.5.4 Provide support in designing, developing, and establishing a 3D PDF publishing capability utilizing Anark ® Core software. Support will consist of application software administrative support and 3D PDF publishing from multiple proprietary CAD models. Contractor personnel will require expertise in multiple CAD software packages such as Autodesk AutoCAD ®and Inventor®, Siemen’s NX ® and Solid Edge®, Dassault Systems CATIA® and Solidworks®, and PTC CREO®.

3.3.6 Software Development Plan (SDP)

3.3.6.1 Define a software development approach appropriate for the computer software effort to be performed under Task orders for this solicitation. This approach shall be documented in a Software Development Plan (CDRL A004). The contractor shall follow this SDP for all computer software to be developed or maintained under this effort.

3.3.6.2 The SDP shall define the offeror's proposed life cycle model and the processes used as a part of that model. In this context, the term “life cycle model” is as defined in IEEE Std. 12207-2017. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of this solicitation. In accordance with the framework defined in IEEE Std. 12207-2017, the SDP shall define the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks. Because IEEE Std. 12207-2017 does not prescribe how to accomplish the task, the offeror must provide this detailed information so the Navy can assess whether the offeror's approach is viable.

3.3.6.3 The SDP shall contain the information defined by IEEE Std. 12207-2017 for generic content and the plans or procedures as described in IEEE Std. 12207-2017. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, at a minimum, specific standard, methods, tools, actions, strategies, and responsibilities associated with development and qualification.

3.3.7 Conversion/ digitization support

3.3.7.1 Convert/digitize technical data furnished by the government into task order specified baseline capability outputs listed within Attachment 02 Contractor capability Requirements. These outputs will provide current, FAM compliant DON XML, CGM4, SVG, or other similar standards-based technical data products, including, but not limited to:

a. Image Scanning;

b. Optical Character Recognition (OCR);

c. XML authoring and/or editing to approved schemas, Document Type Descriptions (DTD), and/or Format Output Specification Instances (FOSI);

d. Conversion of SGML based legacy products into MIL-STD-3001, MIL-DTL-81310, or S1000D Standards compliant XML, CGM4, or SVG files using appropriately FAM sanctioned applications of Parametric Technology Corporation (PTC) Arbortext and IsoDraw family;

e. Conversion of Quicksilver/Interleaf - based legacy products into XML format for use with the MILSTD-3001, MIL-DTL-81310 or S1000D Standards;

f. Conversion of Portable Document Format (PDF), Postscript, proprietary or other legacy product formats into appropriately FAM sanctioned applications of PTC Arbortext and IsoDraw family for use with the MIL-STD-3001, MIL-DTL-81310 or S1000D Standards;

g. Illustration/Engineering Drawing editing, cleanup, development;

h. Error free integration of text, graphics and hyperlinks into style guide compliant tagged instance and parsed runtime instances;

i. Conversion to raster and vector image formats including but not limited to: JPEG, PNG, TIFF, CGM, CGM4, and/or SVG;

j. Industry compliant Quality Assurance best practices and metrics (e.g., for OCR’ed text from paper – Industry Standard for QA practice providing textual accuracy of 99.995%, or 5 errors in 100,000 characters);

k. Create or revise Technical Manual data for use with government owned NAVAIR wire trace out functionality tools in accordance with the MIL-STD-3001, MIL-DTL-81310 or S1000D Standards.”

Convert/digitize legacy data from existing systems/formats to the formats identified in task orders. Minimum baseline application requirements for output of FAM compliant DON XML, CGM4, SVG, or other similar standards-based technical data products are described in Attachment 2; all other task orders requiring use of applications other than specified as baseline requirements shall require approval of AIR-6.8.5 HQ before task order is awarded. Applicable specifications, schemas, FOSIs, DTDs and like applicable structure and content (including appropriate versions), shall be specified in individual task orders. Selected conversion and digitization requirements may include but are not limited to, those prescribed by the following:

a. S1000D, International Specification for Technical Publications.

b. MIL-STD-3001, Preparation of Digital Technical Information for Multi-Output Presentation of TMs.