ATCH 08_Statement of Work_30Jun22.pdf
PDF 355 KB Posted
- Attached to
- COMFRC Headquarters Technical Data Department Federal contract opportunity
- Solicitation number
- N68520-22-R-0004
About this file
This solicitation requests proposals for technical data support services. The Naval Air Systems Command Commander, Fleet Readiness Center seeks proposals for an indefinite delivery, indefinite quantity contract with cost-plus-fixed-fee level of effort contract line items for support services and firm-fixed-price contract line items for various technical publications and corresponding cost reimbursable contract line items for other direct costs. The scope of work includes technical data management, technical publishing, technical library support, logistics information technology support, quality assurance support, and technical data access, control and protection. The period of performance is a five year ordering period. Proposals are due by August 15, 2022, and award is anticipated by May 14, 2023 if discussions are held. This procurement is set aside as a 100% small business 8(a) competitive set-aside. Place of performance includes sites in North Carolina, Florida, California, Maryland, and New Jersey.
View the file
Other files for this federal contract opportunity
Show all 50
COMFRC Headquarters Technical Data Department has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFP: N6852022R0004
Attachment 08
STATEMENT OF WORK
Command Fleet Readiness Center Headquarters
Logistics Technical Data Department National Contract Technical Data and Support Services 30Jun22
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), Cherry Point, NC; Fleet Readiness Center Southeast (FRCSE) at Jacksonville, FL Fleet Readiness Center South West (FRCSW), San Diego, CA; FRC Mid-Atlantic, Patuxent River, MD; Naval Air Technical Data and Engineering Service Center (NATEC) at North Island, CA; NAWC-Weapons Division (NAWCWD) China Lake, CA; NAWC-Aircraft Division (NAWCAD) Patuxent River, MD and Lakehurst, NJ, and NAWC- Training Systems Division (NAWCTSD) Orlando, FL.
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. DoD 5010.12M, ASME , ASME Y14.41 & Y14.42, S1000D), and (8) Contract Data Requirement List (CDRL) reporting.
Note: Preparation and publishing products may be ordered in either of two methods: fixed price CLINs or Cost Plus Fixed Fee (CPFF) 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).
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.36B Information Security Program, 12JUL2019 − 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.30C Personnel Security Program 24JAN2020 − OPNAVINST 3440.17A Navy Installation Emergency Management Program, 1Aug 2014
2.1 Acronyms
Acronym Title ASME American Society of Mechanical Engineers BLS Bureau of Labor Statistics CAC Common Access Card CAD Computer Aided Drafting CDRL Contract Data Requirements List CDSB Common Source Data Base CGM Computer Graphics Metafile CGM4 Computer Graphics Metafile Version 4 CLIN Contract Line Item Number CMS Content Management System COMFRC Command Fleet Readiness Center CONUS Continental United States COR Contracting Officer's Representative CPFF Cost Plus Fixed Fee CUI Controlled Unclassified Information CWS Compressed Work Schedule DCC Data Control Center DFARS Defense Federal Acquisition Regulation Supplement DID Data Item Description DoD Department of Defense DoDI Department of Defense Instruction DoDM Department of Defense Manual DON Department of the Navy DTD Document Type Descriptions ECP Engineering Change Proposal ELMS Electronic Library Management System FAM Functional Area Manager FAR Federal Acquisition Regulation FMS Foreign Military Sales FOSI Format Output Specification Instances FRCE Fleet Readiness Center East FRCSW Fleet Readiness Center South FST Fleet Support Team GED General Education Degree IA Information Assurance IAW In Accordance With IEEE Institute of Electrical and Electronics Engineers
IETM Standard Interactive Electronic Technical Manual IP Intellectual Property IRAC Interim Rapid Action Chance ISO International Organization for Standardization IT Information Technology JDRS Joint Deficiency Reporting System JEDMICS Joint Engineering Data Management Information Control System JPA Job Performance Aids JPEG Joint Photographic Experts Group JTDI Joint Technical Data Integration JTR Joint Travel Regulation KO Contracting Officer LAN Local area network LED Local Engineering Directives LSA Logistic Support Analysis MA / MS Master of Arts / Master of Science MIL-DTL Military Detail Specification MIL-PRF Military Performance Specification MIL-STD Military Defense Standard MPEG Moving Picture Experts Group NATEC Naval Air Technical Data and Engineering Service Center NATPMC NAVAIR Technical Publication Management Console NAVAIR Naval Air Systems Command NAWC Naval Air Warfare Center NAWCAD Warfare Center Aircraft Division NAWCTSD Naval Air Warfare Center Training Systems Division NAWCWD Naval Air Warfare Center Weapons Division NDA Non-Disclosure Agreement NGEN Next Generation Enterprise Network NISPOM National Industrial Security Program Operating Manual NOR Notices of Revision NSIV Standard Interactive Electronic Technical Manual Viewer NSN National Stock Number OCONUS Outside Continental United States OCR Optical Character Recognition ODC Other Direct Cost OEM Original Equipment Manufacturer OOMA Optimized Organizational Maintenance Activity OPNAV Office of the Chief of Naval Operations OPSEC Operation Security
PDF Portable Document Format PDR Preliminary Design Review PKI Public Key Infrastructure PLM Product Lifecycle Management PNG Portable Network Graphics PS Physical Security PTC Parametric Technology Corporation QA Quality Assurance QPP Quality Program Plan RAC Rapid Action Change RAMEC Rapid Action Maintenance/Minor Engineering Change RFD Requests for Deviation RFP Request for Proposal RO Requiring Office SAAR-N System Authorization Access Request SCA Services Contracting Act SCN Specifications Change Notices SDP Software Development Plan SGML Standard Generalized Markup Language SOC Standard Occupational Classification SOW Statement of Work SVG Scalable Vector Graphics TBD To Be Determined TD Technical Directive TDP Technical Data Package TDRS Technical Directive Reporting System TIFF Tag Image File Format TM Technical Manual TMAPS Technical Manual Application System TMCR Technical Manual Contract Requirements TO Task Order TOCOR Task Order Contracting Officer Representative TPDR Technical Publication Deficiency Reports TPOC Technical Point of Contact VTC Video Teleconference WUC Work Unit Code XML Extensible Markup Language
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 ten (10) working days of the task order award. If the contractor or the Task Order Contracting Officer’s Representative (TOCOR) is not available within the 10 working days, the TOCOR shall request permission from the Contracting Officer Representative (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 Information Technology (IT), Information Assurance (IA), and Physical Security (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 NAVAIR Technical Data personnel. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with NAVAIR Technical Data personnel during working hours whether at Contractor work site or on travel.
3.2 Work Locations and Facilities
3.2.1 Work Location(s) - Approximately 45 percent of work is estimated to 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), Cherry Point, NC; Fleet Readiness Center Southeast (FRCSE) at Jacksonville, FL Fleet Readiness Center South West (FRCSW), San Diego CA, Fleet Readiness Center Mid-Atlantic, Patuxent River, MD; Naval Air Technical Data and engineering Service Center (NATEC) at North Island, CA; Naval Air Warfare Center (NAWC), Weapons Division (NAWCWD) China Lake, CA; Naval Air Warfare Center Aircraft Division (NAWCAD) Patuxent River, MD; and Naval Air Warfare Center NAWCAD, Lakehurst, NJ.
Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network including web servers and applicable databases or other applications necessary to carry out assigned tasks.
3.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, China Lake, CA, and Lakehurst, NJ. The contractor meetings shall be capable of accommodating a minimum of 25 persons and have real-time collaboration, communications, and file sharing capability. This contract does not include the leasing or renting of facilities.
3.1.3 Deliverables. The Contractor shall provide the following IAW the specified Contract Data Requirements List (CDRL) (CLIN 0010). CDRLs at the Indefinite Delivery Indefinite Quantity (IDIQ) level may be utilized and updated at the TO level.
3.1.4 Work Schedule to include Compressed Work Schedule (CWS), Overtime, Holidays, and Installation Closure
3.1.4.1 Work schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0630 to 1500 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to deviate from normal working hours, as approved by the TOCOR.
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.
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 and approved by the TOCOR/COR.
3.1.4.1.2 Holidays: The Government observes the holidays listed below. With the exception of the events in section 3.1.4.1.3 the contractor is permitted to observe the below Holidays in accordance with its corporate policy.
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
3.1.4.1.3 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 TPOC must concur with any determination that work being performed by contractor personnel is mission essential.
3.1.4.1.4 Overtime: Overtime is not authorized under this contract.
3.1.5 Other Direct Costs - ODCs are based on a per annum amount.
3.1.5.1 Travel (CLIN 0008): Travel will be allowable only when it is essential to the performance of the tasks detailed in individual TOs. Reimbursement for travel performed shall be IAW the Department of Defense Joint Travel Regulation (JTR) (http://www.defensetravel.dod.mil/site/travelreg.cfm). The TOCOR shall approve all travel performed in support of individual TOs under this contract. IAW NAVAIR Clause 5252.232- 9509 Travel Approval and Reimbursement Procedures, travel within a 50-mile radius of the Contractor’s regular worksite is considered the Contractor’s official station and therefore not subject to reimbursement. Travel may include general and administrative expenses as appropriate, but shall not include profit. Temporary travel to other locations in support of program tasking may be required. Temporary travel locations include CONUS & OCONUS locations, which will be identified in individual TOs. Locations may change over the life of the contract.
Travel authorization requests shall be submitted to the TOCOR for approval 30 days in advance of required travel, when possible, but no less than 10 business days prior to travel. Contractor required access to Government-owned facilities will be authorized with the proper clearances and visit requests. The Contractor shall provide all necessary information, as required, to support such clearances and visit requests.
3.1.5.2 Material (CLIN 0009): For material not depleted during the performance of this contract, the contractor shall notify the Contracting Officer Representative (COR) Manager.
At the discretion of the COR Manager, all materials not depleted during the performance of this contract shall become Government property. The Contractor shall transfer all materials not depleted to the TOCOR by way of Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administrative expenses as appropriate, but shall not include profit.
http://www.defensetravel.dod.mil/site/travelreg.cfm
The Contractor may be required to incur incidental supply and material costs in support of this effort as ODCs as specified within individual Task Orders. Incidental supply and material purchases shall be reimbursed in accordance with Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable DON regulations and instructions. NAVAIR Clause 5252.242-9515 details allowable costs and restrictions on the direct charging of material costs. Only those material expenses as specified in individual task orders shall be reimbursed to the Contractor.
The costs of general purpose business expenses required for the conduct of the Contractor’s normal business operations are not an allowable direct cost in the performance of this 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.
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 communicate 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 Transition Out 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.
3.1.8.1 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.
3.1.8.2 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.
3.1.8.3 Risk Mitigation Strategies - The contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.
3.1.8.4 Data/Information Transfer - The contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.
3.1.8.5 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.1.8.6 For Task Orders with an active Period of Performance under IDIQ N00421-19- D0064 after 15 JUNE 2023: shall be the responsibility of the incumbent of said IDIQ until the active TO’s POP expires.
3.2 Security
3.2.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. Contractor personnel working at government sites and in the contractor’s own facilities supporting government work shall undergo the company internal vetting process prior to gaining access to U.S.
Government controlled unclassified information, or performing government-related sensitive duties. All personnel working under the resultant contract shall be U.S. citizens. Foreign nationals are prohibited from using FRC assets, and they will not be allowed to access any resource of the FRC legacy network at any time, this includes both the legacy network and the NMCI network.
3.2.2 Investigative Requirements: (3.2.2.1 Unclassified or 3.2.2.2 Classified will be determined in individual TOs based on classification of work performed):
3.2.2.1 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.
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), 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 Controlled Unclassified Information (CUI) and to control distribution of CUI IAW DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36B. All Contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI shall be appropriately identified and marked as For Official Use Only IAW DoD Instruction 5200.48, Controlled Unclassified Information (CUI).
3.2.2.2 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 may require access to classified information in performance of this contract up to and including Secret, with a safeguarding level of None as specified in the DD254, and determined by the TO. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW DoDM 5220.22-M, National Industrial Security Program Operating Manual. 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 as Controlled Unclassified 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 TPOC/COR of this contract for approval.
3.2.2.3 - CUI including For Official Use Only 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 DoDI 5200.48 Controlled Unclassified Information (CUI)) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.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 distribution statement(s) as identified and required in the TO CDRL document.
Deliverables with a Distribution Statement authorized to DoD components only. Shall direct requests to Commander, Fleet Readiness Centers, 47060 McLeod Road, Building 447, Patuxent River, MD 20670.
3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).
3.2.3.1 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) 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 TOCOR/COR, Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.
Contractor personnel shall be in the Defense Information Security System (DISS) for Information Technology II and III positions. IT I position requires that an SF-86 (Questionnaire for National Security Positions) be provided to the cognizant FRC site Facility Security Officer (FSO). IT-II & III positions are those that require a Contractor to have non privileged access to data or application. An IT-I position shall have root level access to servers and be a privileged user. For purposes of this contract, all Contractor personnel shall be required to be IT-II and hold/maintain a secret clearance, unless IT-I is required by individual TOs.
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 and shall conform to local installation badge policy and guidance. All CACs and identification badges issued to contractor employees shall be returned to the Government Security Department at the Government site IAW local installation badge policy and guidance 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 badged Contractor https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf access to Government facilities, as required, for performance of tasks under this contract.
Contractor personnel shall comply with local installation badge policy and guidance.
3.2.3.3 DD-254: 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 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, request under individual TOs shall be referred to the TOCOR/TPOC identified in the TO.
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 National Industrial Security Program Operating Manual (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. All CUI shall be appropriately identified in accordance with DoD Instruction 5200.48, Controlled Unclassified Information (CUI).
3.2.4.1 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 COMFRC public affairs office.
3.2.4.2 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 TOCOR, TPOC and Government Security Office immediately.
3.2.4.3 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 Manager via TOCOR, and necessary data segmentation/protection shall be implemented until pertinent instructions are received from the COR Manager for disposition.
In the case of mismarked, loss comprise, or suspected compromise, IA/IT security process reporting shall conform to the pertinent NISPOM section for “reports of Loss, Comprise, or Suspected Compromise, and for CUI issues, shall conform to the pertinent DFARS
252.2010012 incident reporting
3.2.5 Operation Security (OPSEC) - The contractor shall comply with requiring activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The contractor shall include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The contractor shall protect identified critical information, unclassified information and activities, which, if divulged, could further compromise unclassified or classified information or operations, or degrade the planning and execution of operations performed by the Task Order Requirements Office (RO) and contractor in support of the mission.
While performing aboard Government 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: 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.
3.3 Detailed Support:
The Contractor shall provide the following detailed support to be determined and further defined at the task order level. The associated funding types include Operation and Maintenance, Navy (O&M, N), Procurement, Research and Development (R&D), Foreign Military Sales, (FMS), Navy Working Capital Funds (NWCF), and Operating Expense Coast Guard (OECG). The funding type(s) will be aligned to the tasks, services, technical data, material development, and information, identified in individual task orders (TOs).
3.3.1 Technical Publication Support Requirements
CDRL(s) A001 - A005, and A007 CLIN(s) 0002 - 0007
3.3.1.1 Develop, update/edit/prepare and deliver technical publications including, but not limited to: Original research and writing, engineering analysis and data 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 Support Government Lead 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 will be determined by the Government Lead. 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, 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 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 TBD at task order level fielded NAVAIR Technical Publications, via data analysis of Joint Deficiency Reporting System (JDRS) and Technical Manual Application System (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 TBD at the task order level for all fielded NAVAIR Technical Publications, via data analysis of the electronic Library Management System (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 TBD at task order level 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 TBD at task order level 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. The NAVAIR 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 TPOC 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 recommend 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 and applicable specification content identified in task orders. Minimum baseline application requirements for output of FAM compliant, MPEG, JPEG or other similar multi-media file types. Applicable specifications, format requirements, and content shall be specified in individual task orders.
3.3.2 Logistics Configuration Management and Technical Directive Support CDRL(s) A001 - A005, and A007 CLIN(s) 0002 - 0007
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 and maintain 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, and maintain fleet bulletins and Rapid Action Maintenance/Minor Engineering Change (RAMEC).
3.3.3 Technical Libraries, Repositories, and Data Control Center (DCC) CDRL(s) A001 - A005, and A007 CLIN(s) 0002 - 0007
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 and will require onsite support.
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 controlled unclassified 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 TBD at task order level.
3.3.4 Logistics Information Technology
CDRL(s) A001 - A005, and A007 CLIN(s) 0002 - 0007
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 deliverables will be forwarded to the Government TPOC 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 TPOC 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 TPOC 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.
CDRL(s) A001 - A005, and A007 CLIN(s) 0002 - 0007
3.3.5.1 Provide TDP assessment support to assist NAVAIR COMFRC HQ FST Logistics Technical Data Department 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 shall 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. The TDP will be prepared using 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 shall 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 shall 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.
Utilizing 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)
Update Annex A for any changes required during the life of the IDIQ IAW CDRL A0005.
3.3.7 Conversion/ Digitization Support
CDRL(s) A001 - A005, and A007 CLIN(s) 00011 - 0039
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 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 (five) 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.”
3.3.7.2 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. Applicable specifications, schemas, FOSIs, DTDs and like applicable structure and content (including appropriate versions), will 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.
c. MIL-DTL-81310 Technical Manuals: Airborne Weapons/Stores Loading/Weapons
Assembly/Support Equipment Configuration.
d. MIL-DTL-81927, Manuals, Technical: General Style and Format of (Work Package
Concept).
e. MIL-STD-38784 Standard Practice for Manuals, Technical: General Style and Format
Requirements.
f. MIL-DTL-87269 Data Base, Revisable Interactive Electronic TMs.
3.3.7.3 Convert/digitize legacy engineering drawings and associated data from existing systems/formats to JEDMICS compliant image formats, including requisite indexing data.
Processes utilized for migration of data into repository acceptable formats shall ensure compliance with USN and/or DoD standards as shown in Attachment 01 and policies as applicable. Output format will be identified in task orders.
3.3.7.4 Convert/digitize/create/update engineering drawings and associated data in intelligent source formats (e.g., Autocad) and output formats as identified in task orders.
Requirement shall include, but are…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .