Attachment 01 - Draft SOW.pdf

STATEMENT OF WORK FOR

NAVAL AVIONICS PLATFORM INTEGRATION EMULATOR

TASK ORDER

Scope

As the organic Lead Systems Integrator® (oLSI®) for the Naval Air Warfare Center Aircraft Division (NAWCAD), Webster Outlying Field (WOLF) operates under a product-based business model whereby NAWCAD WOLF civilians lead and manage the execution of the requirements with combined Government-Industry teams. Using this oLSI® approach, the Government maintains control of intellectual property and data rights, enabling WOLF to rapidly adapt solutions to the dynamic needs of the warfighter.

The NAWCAD WOLF Airborne Systems Integration (ASI) Division provides the rapid insertion and transition of advanced technologies, systems, sensors, and weapons to enable Programs of Record (PoRs), as well as deliver direct insertion of capabilities to meet urgent fleet needs. The ASI Division works with customers and sponsors to identify capability gaps and requirements, develop programmatic strategies, conduct technology development, provide installation and integration services, support test and evaluation, and deliver capabilities to the fleet.

The NAWCAD WOLF ASI Division, operating under the oLSI® model, has requirements to provide support for Naval Avionics Platform Integration Emulator (NAPIE) technical development planning; NAPIE design, development, and prototyping; NAPIE surrogate design, development, and prototyping; NAPIE equipment integration; and NAPIE testing.

NAPIE is a set of platform integration tools designed to facilitate rapid prototyping of new concepts and can be implemented for flight tests on both military and civilian platforms. In generic form, NAPIE consists of a software, hardware, and a data recorder that interfaces to the relevant systems on the host platform systems, required sensors, data links, other systems, and simulation environments. NAPIE provides a quick-disconnect platform interface allowing the pilot to return the vehicle to its original configuration at any time, reducing airworthiness flight risks and providing a safe space to act as a technology incubator. NAPIE is an ideal platform that supports the Chief of Naval of Operations (CNO’s) Navigation Plan (NAVPLAN) capabilities and promotes the key enablers of live, virtual, and constructive and autonomous systems to be developed.

The Contractor shall perform the tasks described in this Statement of Work (SOW) for NAPIE systems relating to, but not limited to, the following systems:

Joint Precision Approach and Landing System (JPALS)

MQ-25 Stingray

E-2D Modified Aircraft Gamma Inceptor Control Platform Recovery Optimization Program (MAGIC PROP)

AN/APN-246

Aerial Refueling Store

Applicable Documents.

The following documents and document sources are provided for reference. The documents listed below are presented only as representative sources of the engineering and technical details that may be required during Task Order (TO) performance. The documentation listed is not all-inclusive but is representative of the type of information that may be necessary to perform the work. The document version applicable to tasking will be the most current published document at the time of TO award.

2.1 Department of Defense (DoD) Specifications.

2.1.1 DoD National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule.

2.1.2 DoDM 5200.01 Vol. 2, Marking of Classified Information, Change 4, 28 Jul 2020.

2.1.3 SECNAV M-5510.36B, Department of the Navy, Information Security Program, 12 Jul 2019.

2.1.4 DoDI 5200.48, Controlled Unclassified Information (CUI), 6 Mar 2020.

2.1.5 DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program, 5 Apr 2019.

2.1.6 DoDI 5230.24, Distribution Statements on Technical Documents, Change 3, 10 Jan 2023.

2.1.7 SECNAV M-5510.30C, Department of the Navy Personnel Security Program, 24 Jan 2020.

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

2.1.9 SECNAVINST 5239.20A, Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification, 10 Feb 2016.

2.1.10 DoDD 8140.01, Cyberspace Workforce Management, 5 Oct 2020.

2.1.11 DoDI 1035.01, Telework and Remote Work, 8 Jan 2024.

2.2 DoD Standards.

2.2.1 National Security Decision Directive 298, dated 22 January 1988 Public Law 100-235, Section 3(d)(4).

2.2.2 NAVAIR Operations Security (OPSEC) Requirements (DD-254 OPSEC Annex).

Requirements.

3.1 General Requirements.

General Requirements. Paragraph 3.1 from the Basic Multiple Award Contract (MAC) Contract, N00421-22-D-0006 through N00421-22-D-0068 and its deliverable products are required in support of this TO, unless specifically stated otherwise below to provide more detailed requirements or to provide Contract Line Item Number (CLIN) references.

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

Microsoft Windows 16 or greater Microsoft Project 2016 or greater Microsoft Office Professional Plus 2016 or greater Flank Speed Adobe Acrobat Internet access

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

3.1.2 Work Location, Facilities, and Telework.

3.1.2.1 Work Location. Approximately 55% of work will be performed at Government site and 45% of work to be performed at contractor site. Government site includes Naval Air Station (NAS) Patuxent River, MD.

3.1.2.1.1 Government Site Requirements. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access, including access to web servers and applicable databases or other applications necessary to carry out assigned tasks.

3.1.2.1.2 Contractor Site Requirements. The Contractor shall provide its own support facilities needed to perform the tasking of this TO within 50 drivable miles of Naval Air Station (NAS) Patuxent River, MD. All NAPIE software development is performed exclusively at the Patuxent River NAPIE Laboratory.

3.1.2.1.3 Meeting Support. In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at the classification levels up to Secret with the capacity to support a minimum of five persons. The meeting space shall have contractor-furnished telephone and Video Teleconference (VTC) capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in section

3.1.1. This support shall be provided at the contractor support facilities located within 50 driving miles of NAS Patuxent River, MD.

3.1.2.3 Reserved

3.1.2.4 Special Facilities.

3.1.2.4.1 Industrial Space. The Contractor shall provide sufficient industrial support space for the receipt, storage, inventory, shipment, and integration of equipment associated with assigned projects. Additionally, the space shall be equipped with Heating, Ventilation, and Air Conditioning (HVAC) systems capable of sustaining a controlled environment consistent with the storage, assembly, and operation of electronic equipment. The space shall be configured to meet requirements for receiving, material receipt inspection, storage awaiting build up, integration and testing, and storage of completed systems. The space shall be equipped to protect Government property and shall be located within 50 driving miles of NAS Patuxent River, MD. The Government will not have desk occupancy at the location and will not take possession of the facility at TO termination.

3.1.2.4.2 Reserved.

3.1.2.5 Reserved.

3.1.3 TO Status Reporting. The Contractor shall provide the following documentation.

3.1.3.1 Monthly Progress and Financial Status Report. The Contractor shall provide a progress and financial status report in accordance with (IAW) the Contract Data Requirement List (CDRL). The report shall include work accomplished since submittal of the last report, both monthly and cumulative work hour labor costs expended by labor category and material and travel costs. (CDRL A001)

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 0730 to 1600 each Monday through Friday (except on the legal holidays as specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600 and end as late as 1800 Monday – Friday.

3.1.4.1.1 CWS. CWS is an alternative work schedule to the traditional 5 8.5-hour workdays (which includes a 30-minute lunch break) worked per week. Under a CWS schedule, an employee completes the following schedule within a 2-week period of time: 8 weekdays are worked at 9.5 hours each (which includes a 30-minute lunch break), 1 weekday is alternately worked at 8.5 hours (which includes a 30-minute lunch break), and 1 weekday is not worked by the employee. The result is 80 hours worked every 2 weeks, with 44 work hours 1 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 to the Contracting Officer’s Representative (COR)/Alternate Contracting Officer’s Representative (ACOR).

3.1.4.1.2 Holidays. The Government observes the Federal holidays identified on the Office of Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview. With the exception of the events in section 3.1.4.1.3 below, the Contractor is permitted to observe Federal holidays IAW its corporate policy.

3.1.4.1.4 Reserved.

3.1.4.1.5 Reserved.

3.1.4.1.6 Telework

The Contractor may allow contractor employees to telework IAW DoDI 1035.01, Telework and Remote Work and the table in section 3.4. The Contractor may utilize alternate worksites/locations to telework to support continued performance of SOW tasks IAW company policy. When using telework, the Contractor remains responsible for contract performance and compliance with any applicable cost accounting standards and contract cost principles/procedures.

Telework is defined as an alternative workplace arrangement under which a position performs the duties and responsibilities of the assigned position and other authorized activities from an approved alternative worksite but is required to report to the agency’s worksite on a regular and recurring basis. Telework can be either routine or situation. Routine telework is performed from an alternative worksite on regularly scheduled telework day(s), whereas Situational telework is authorized on a case-by-case basis as the need arises or when opting for unscheduled telework and may be authorized for routine teleworkers in such circumstances on regularly scheduled in-office days.

Telework eligible positions require routine on-site performance of two days per week. On-site performance may be required outside of routine on-site performance days, and shall be provided when requested by the Contracting Officer’s Representative (COR).

At any time during contract performance, the COR may determine that a position is no longer eligible for telework by providing a notice 30 calendar days in advance so the Contractor can address changes needed to support mission requirements.

3.1.5 Other Direct Costs (ODCs). (Research, Development, Test and Evaluation (RDT&E);

Procurement (PROC); Operations and Maintenance (O&M); and Working Capital Fund (WCF)).

3.1.5.1 Travel

3.1.5.1.1 General and administrative expenses. The Contractor shall complete travel request(s) IAW CTXT.232-9509, Travel Approval and Reimbursement Procedures. Upon completion of travel, the contractor employee shall complete a trip/travel report. The COR shall approve all travel performed in support of this TO prior to the commencement of the travel and travel shall result in a trip report. (CDRL A002)

3.1.5.1.1.1 Travel may include general and administrative expenses; however, shall not include profit. Temporary travel to other locations in support of program tasking is required.

Temporary travel locations include locations within the Continental United States (CONUS) to include travel to NAS North Island, CA; San Diego, CA; Melbourne, FL; Crane, IN; and Naval Station Norfolk, VA. This list is not all inclusive as locations may change over the life of the TO.

3.1.5.1.1.2 Local Travel Reimbursement. Reimbursement of local travel within 50 drivable miles of NAS Patuxent River, MD, and the Contractor’s facilities is not an allowable cost.

3.1.5.1.3 Reserved.

3.1.5.2 Material. Incidental material will be required in the performance of this TO, and all incidental material purchases shall be IAW CTXT.242-9520, Procedures and Approvals Required Prior to Incurring Direct Material Costs. All materials not depleted during the performance of this TO shall become Government property upon completion of this TO. The Contractor shall transfer all materials not depleted to the COR by way of a DD FORM 250, Material Inspection and Receiving Report. Material costs may include general and administrative expenses but shall not include profit/fee. (CDRL A003)

3.1.5.3 Reserved.

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

3.1.6.1 The Contractor shall submit a Small Business Participation Commitment Document

(SBPCD). (CDRL A004)

3.1.8 Transition-Out Plan.

The Contractor’s overall transition-out plan shall be built around maintaining the mission of the ASI Division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to the termination or expiration of the TO, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall submit a Transition-Out Plan, to include the minimum elements listed below IAW CDRL A005.

̶ 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 TO to the successor company and establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.

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

̶ Risk mitigation strategies. The Contractor shall provide a plan of action to mitigate TO 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.

3.1.9 Reserved

3.1.10 QA.

3.1.10.2 Reserved.

3.1.11 Technical Direction Letters (TDLs). When necessary, technical direction or clarification concerning the details of specific tasks set forth in the TOs will be given through issuance of written TDLs. TDLs will not, in any manner, alter the scope of the TO. For further direction see HTXT.242-9502, Technical Direction (Variation) in Section H of the Contract. The Contractor shall prepare and deliver a COR Management Report for TDLs IAW (CDRL A001).

3.2 Security.

Paragraph 3.2 from the Basic MAC Contract, N00421-22-D-0006 through N00421-22-D-0068, is required in support of this TO, unless specifically stated otherwise below to provide more detailed requirements.

3.2.2.2 Contractor Personnel Labor Category Security Requirements. All personnel shall have a Secret DoD Security Clearance or interim within 60 business days after issuance of the TO unless stated otherwise in the table below.

LABOR CATEGORY

DoD SECURITY

CLEARANCE

LEVEL (INTERIM

CLEARANCE

ACCEPTABLE)

REQUIRED DAYS AFTER

ISSUANCE OF TO

Network and Computer Systems Administrators – Intermediate (Systems Analyst) (Key)

Top Secret 30 business days

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

3.2.3.1 SAAR. All contractor personnel requiring access to Government IT systems shall have an approved DD Form 2875, System Authorization Access Request (SAAR) form on file and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within 30 business days of their first day of work. SAAR forms shall be submitted to the COR, Government Technical Point of Contact (TPOC), or to the assigned Government Mission Partner Identity, Credential, and Access Management (MP ICAM) Trusted Associate

(TA).

3.2.3.2 CAC/Local Badges. Contractor CACs and facility-specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges. All CACs and identification badges issued to contractor employees shall be returned to the TA following completion of the TO, relocation or termination of an employee, or upon request from the COR/Procuring Contracting Officer (PCO). The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this TO.

3.2.3.3 DD Form 254. The Contractor shall comply with security requirements specified in the DD Form 254 attached to this TO. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled as Controlled Unclassified Information (CUI). Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this TO shall be referred to the TPOC/COR of this TO for approval.

3.2.4 Information Security. If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and CUI and to control distribution of CUI IAW National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAV M-5510.36B, Department of the Navy, Information Security Program. If the work is performed at the Government's facility, the Contractor shall comply with that facility’s information and security policies.

All contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI including legacy For Official Use Only (FOUO) information and Covered Defense Information (CDI) (meeting the definition DFARS Clause 252.204–7012, Safeguarding Covered Defense Information and Cyber Incident Reporting) generated and/or provided under this TO shall be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled

Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF.

Any product containing CDI 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, Enclosures 3 and 4.

Distribution is authorized to the Requiring Office's Organization and supported Activity only.

Other requests for deliverables under this TO shall be referred to the TPOC/COR of this TO for approval.

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

Distribution Statement (Insert Appropriate Letter and Authorization Title), (Insert Appropriate Reason Category) (dated – (Date of Distribution Authorization)). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: COR, NAWCAD WOLF ASI, 17800 Moll’s Cove Road, St. Inigoes, MD 20684.

3.2.4.1 Marking. All information generated by the Contractor shall be properly marked.

Classified information shall be marked IAW DoDM 5200.01, Vol 2, Marking of Classified Information. CUI, including legacy FOUO information generated and/or provided under this TO, shall be marked IAW DoDI 5200.48, Controlled Unclassified Information (CUI). Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DoDI 5230.24, Distribution Statements on Technical Documents and program Security Classification Guidance.

3.2.4.2 Public Release. Any CUI pertaining to this TO shall not be released for public dissemination, including posting to any social media sites such as Facebook or X (formerly known as Twitter), unless it has been approved for public release by appropriate U.S.

Government authority. Proposed public releases shall be submitted for approval prior to release through the NAWCAD WOLF ASI COR: NAWCAD WOLF ASI Division, 17800 Moll’s Cove Road, St. Inigoes, MD 20684

3.2.4.3 Loss, compromise, and/or electronic spillage of classified information or CUI. All instances of loss, compromise, and electronic spillage of classified information or CUI shall be reported to the COR, TPOC, and Government Security Office within 72 hours of the incident occurring.

3.2.5 Operations Security (OPSEC). The ASI Division (the Requiring Organization) has made a determination that basic OPSEC measures are sufficient to protect the contracted related Critical Information associated with this TO. The NAVAIR DD254 OPSEC Annex, dated 2023, shall be included as an attachment to the DD Form 254. When basic OPSEC measures are prescribed, there shall be no required OPSEC CDRLs associated with this TO. However, the Contractor will adhere to all OPSEC requirements specified in the NAVAIR Operations Security (OPSEC) Requirements (the NAVAIR DD254 OPSEC Annex). The Contractor shall be responsible for subcontractor implementation of the OPSEC Program requirements for this TO.

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; and protect sensitive unclassified information and activities that could compromise classified information or operations or degrade the planning and execution of operations performed by the Requirements Owner and Contractor in support of the mission.

3.2.6 Antiterrorism Force Protection and Emergency Management. The work performed on this TO is not Emergency Essential IAW OPNAVINST 3440.17A, Navy Installation Emergency Management Program and Government Emergency Management, Antiterrorism, and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism, and/or Continuity of Operations Plans and directives.

Contractor personnel shall not report for work at Government facilities 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.2.12 Organizational Conflicts of Interest (OCI) Mitigation Plan and Non-Disclosure Agreement (NDA) Status Certification. The Contractor shall report OCI Mitigation Plan compliance and compliance status changes. (CDRL A006)

3.3 Specific Requirements.

3.3.1 Technical Development Planning.

3.3.1(a) (RDT&E) Provide technical development planning efforts for the research, development, and testing of NAPIE units. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.4.

3.3.1(b) (PROC) Provide technical development planning efforts to integrate, install, and certify NAPIE units. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.4.

3.3.1(c) (O&M) Provide technical development planning efforts to operate, maintain, and repair NAPIE units. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.4.

3.3.1(d) (WCF) Provide technical development planning efforts to improve, update, and replace outdated NAPIE units. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.4.

3.3.1.1 The Contractor shall support the development of project estimates to include cost, schedule, labor, resources, and Work Breakdown Structure (WBS).

3.3.1.2 The Contractor shall support trade-off and engineering approach analysis through identification, assessment, impact, metrics, and mitigation of risk and provide a Recommendation Report. (CDRL A007)

3.3.1.3 The Contractor shall support the development of milestone definitions that correspond to tangible products, procurement cycle requirements, or achievement levels and provide an Engineering Report. (CDRL A008)

3.3.1.4 The Contractor shall support the development of methodologies and management processes, metrics, tools, configuration, quality control measures, and procedures and provide a Recommendations Report. (CDRL A007)

3.3.2 NAPIE Design, Development, and Prototyping.

3.3.2(a) (RDT&E) Provide NAPIE design, development, and prototype efforts for the research, development, and testing of NAPIE units. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.9.

3.3.2(b) (PROC) Provide NAPIE design, development, and prototype efforts to integrate, install, and certify NAPIE units. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.9.

3.3.2(c) (O&M) Provide NAPIE design, development, and prototype efforts to operate, maintain, and repair NAPIE units. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.9.

3.3.2(d) (WCF) Provide NAPIE design, development, and prototype efforts to improve, update, and replace outdated NAPIE units. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.9.

3.3.2.1 The Contractor shall assist by deriving candidate ruggedized and non-ruggedized NAPIE system architectures based on Government-provided requirements and by providing Recommendation Reports, Interface Control Documents (ICDs), and Engineering Drawings.

(CDRLs A007, A009, A010)

3.3.2.2 The Contractor shall assist by providing documentation to support required System Engineering Technical Review (SETR) events and by providing ICDs, Engineering Drawings, Integrated Logistics Support Plans, Test Plans and Procedures, Technical Manual Revisions, Briefing and Presentation Material, Version Description Documents, and System Specification Documents. (CDRLs A009, A010, A011, A012, A013, A014, A015, A016, A017, and A018)

3.3.2.3 The Contractor shall support the design, development, and prototyping of NAPIE units in support of developmental and upgrade programs and provide Recommendation Reports, ICDs, and Engineering Drawings. (CDRLs A007, A009, and A010)

3.3.2.4 The Contractor shall assist with the integration of the NAPIE hardware components.

3.3.2.5 The Contractor shall support NAPIE software and firmware development and maintain the NAPIE development software licensing requirements at the NAS Patuxent River Landing Systems Test Facility (LSTF) and provide Software Requirements Specifications (SRSs), Software Design Descriptions (SDDs), and Software Development Plans (SDPs). (CDRLs A019, A020, and A021)

3.3.2.6 The Contractor shall assist by maintaining and providing NAPIE units for the ASI Division to integrate and test the units in various military and civilian platforms and shore-based test facilities and provide Configuration Drawings. (CDRL A022)

3.3.2.7 The Contractor shall support configuration management by providing NAPIE configuration documentation, both hardware and software, and by continuously updating the configuration documentation to reflect the latest configuration and provide Software Development Summary Reports, Version Description Documents, Configuration Drawings, and Configuration Documentation. (CDRLs A016, A017, A022, and A023)

3.3.2.8 The Contractor shall provide support by developing Model-Based System Engineering (MBSE) capabilities in the NAPIE laboratory and by creating and maintaining models related to NAPIE products.

3.3.2.9 The Contractor shall support the maintenance of a secure network by creating, maintaining, and performing IT and Information Assurance (IA) methodologies and management processes, metrics, tools, configuration procedures, and documentation IAW the NAPIEnet Authority to Operate (ATO).

3.3.3 NAPIE Surrogate Design, Development, and Prototyping.

3.3.3(a) (RDT&E) Provide NAPIE surrogate design, development, and prototype efforts for the research, development, and testing of NAPIE surrogate units. Applicable to SOW paragraphs

3.3.3.1 – 3.3.3.5.

3.3.3(b) (PROC) Provide NAPIE surrogate design, development, and prototype efforts to integrate, install, and certify NAPIE surrogate units. Applicable to SOW paragraphs 3.3.3.1 – 3.3.3.5.

3.3.3(c) (O&M) Provide NAPIE surrogate design, development, and prototype efforts to operate, maintain, and repair NAPIE surrogate units. Applicable to SOW paragraphs 3.3.3.1 – 3.3.3.5.

3.3.3(d) (WCF) Provide NAPIE surrogate design, development, and prototype efforts to improve, update, and replace outdated NAPIE surrogate units. Applicable to SOW paragraphs

3.3.3.1 – 3.3.3.5.

3.3.3.1 The Contractor shall support derivation of NAPIE surrogate system architectures based on Government-provided requirements and available relative navigation technologies and provide Recommendation Reports, ICDs, Engineering Drawings, System Specification Documents, Software Specification Documents, SDDs, SDPs, and SRDs. (CDRLs A007, A009, A010, A018, A019, A020, A021, and A024)

3.3.3.2 The Contractor shall assist by providing documentation to support required SETR events and provide ICDs, Engineering Drawings, Integrated Logistics Support Plans, Test Plans and Procedures, Technical Manual Revisions, Briefing Material, Version Description Documents, and System Specification Documents. (CDRLs A009, A010, A011, A012, A013, A014, A015, A017, and A018)

3.3.3.3 The Contractor shall assist with the procurement of NAPIE components and ancillary equipment.

3.3.3.4 The Contractor shall provide support by fabricating NAPIE components for NAPIE Surrogate systems.

3.3.3.5 The Contractor shall assist by creating and maintaining MBSE models relating to NAPIE surrogate products.

3.3.4 NAPIE Equipment Integration.

3.3.4(a) (RDT&E) Provide NAPIE equipment integration efforts for the research, development, and testing of NAPIE units. Applicable to SOW paragraphs 3.3.4.1 – 3.3.4.17.

3.3.4(b) (PROC) Provide NAPIE equipment integration efforts to integrate, install, and certify NAPIE units. Applicable to SOW paragraphs 3.3.4.1 – 3.3.4.17.

3.3.4(c) (O&M) Provide NAPIE equipment integration efforts to operate, maintain, and repair NAPIE units. Applicable to SOW paragraphs 3.3.4.1 –3.3.4.17.

3.3.4(d) (WCF) Provide NAPIE equipment integration efforts to improve, update, and replace outdated NAPIE units . Applicable to SOW paragraphs 3.3.4.1 –3.3.4.17.

3.3.4.1 The Contractor shall assist by prototyping and integrating NAPIE units in support of developmental programs and by providing Recommendation Reports, ICDs, and Engineering Drawings. (CDRLs A007, A009, and A010)

3.3.4.2 The Contractor shall assist by delivering NAPIE configuration documentation (both hardware and software); continuously updating the documentation to reflect the latest configurations; and providing Software Development Summary Reports, Version Description Documents, Configuration Drawings, and Configuration Documentation. (CDRLs A016, A017, A022, and A023)

3.3.4.3 The Contractor shall assist by performing NAPIE software integration at the NAS Patuxent River LSTF and by providing Software Development Summary Reports, Version Description Documents, Software Specification Documents, SRSs, SDDs, SDPs, Configuration Drawings, and Configuration Documentation. (CDRLs A016, A017, A019, A020, A021, A022, and A023)

3.3.4.4 The Contractor shall provide support by developing and executing NAPIE integration checkout procedures to ensure that equipment is successfully installed and integrated and by providing Test Plans and Procedures, Software Test Plans, and Software Test Reports for every functional system drop. (CDRLs A012, A013, A025, and A026)

3.3.4.5 The Contractor shall assist with the certification process by generating drawing packages for each installation. Drawing packages may need to be tailored for specific purposes such as IA accreditation approvals, Federal Aviation Administration (FAA) certification, Flight Certification/Worthiness, documentation archival, and configuration management processes.

Drawings shall include Engineering Drawings, Configuration Drawings, and Installation Control Drawings. (CDRLs A010, A022, A023, and A027)

3.3.4.6 The Contractor shall support the design, procurement, and fabrication of NAPIE enclosures for airframe and ground station installations and provide Engineering Reports, ICDs, Engineering Drawings, Test Plans and Procedures, Technical Manual Revisions, Version Description Documents, and Installation Control Drawings. (CDRLs A008, A009, A010, A012, A013, A014, A017, and A027)

3.3.4.7 The Contractor shall provide support by performing site surveys of candidate surrogate aircraft for the outfitting of prototype NAPIE systems and by providing Engineering Reports, ICDs, Engineering Drawings, and Installation Control Drawings. (CDRLs A008, A009, A010 and A027)

3.3.4.8 The Contractor shall support the installation, population, and integration of enclosures by performing cabling installations into designated NAPIE platforms (e.g., Ground Station, Lear Jet, heavy transport aircraft, etc.) and by providing Engineering Reports, ICDs, Engineering Drawings, Configuration Drawings, and Installation Control Drawings. (CDRLs A008, A009, A010, A022, A023, and A027)

3.3.4.9 The Contractor shall support the installation of antennas and associated cabling for all installation platforms and by providing Engineering Reports, ICDs, Engineering Drawings, Configuration Drawings, and Installation Control Drawings. (CDRLs A008, A009, A010, A022, A023, and A027)

3.3.4.10 The Contractor shall assist by staging the shipment and receipt of installation equipment by providing Government Property Inventory Reports, Configuration Drawings, and Configuration Documentation. (CDRLs A003, A022, A023, and A028)

3.3.4.11 The Contractor shall assist with shipping and receiving function by providing logistics support for installation activities and by providing Government Property Inventory Reports, Configuration Drawings, and Configuration Documentation. (CDRLs A003, A022, A023, and A028)

3.3.4.12 The Contractor shall provide system integration support of installed systems to include start-up, initialization, and set-up (including, but not limited to, bore sighting, lever arm inputs, alignments, troubleshooting, and running limited test cases) and provide Recommendations Reports, Engineering Reports, ICDs, and Engineering Drawings. (CDRLs A007, A008, A009, A010, and A027)

3.3.4.13 The Contractor shall assist by documenting integration issues with System Problem Reports and other approved processes implemented by the cognizant systems engineering team.

(CDRL A029)

3.3.4.14 The Contractor shall assist by acquiring the use of Surrogate Aircraft for NAPIE integration events.

3.3.4.15 The Contractor shall assist by coordinating with the FAA-Designated Engineering Representative.

3.3.4.16 The Contractor shall assist by providing Flight Certification information for hardware and software to NAVAIR Flight Certification representatives to facilitate test plan approvals and provide ICDs, Engineering Drawings, Test Plans and Procedures, Briefing and Presentation Material, Version Description Documents, and Acceptance Test Plans and Procedures. (CDRLs A009, A010, A012, A013, A015, A017, A027, A030, and A031)

3.3.4.17 The Contractor shall assist by contributing to required documentation in support of aircraft integration and test events by providing ICDs, Engineering Drawings, Test Plans and Procedures, Briefing and Presentation Material, Version Description Documents, and Acceptance Test Plans and Procedures. (CDRLs A009, A010, A012, A013, A015, A017, A027, A030, and A031)

3.3.5 NAPIE Testing.

3.3.5(a) (RDT&E) Provide NAPIE testing efforts for the research, development, and testing of NAPIE units. Applicable to SOW paragraphs 3.3.5.1 – 3.3.5.8.

3.3.5(b) (PROC) Provide NAPIE testing efforts to integrate, install, and certify NAPIE units.

Applicable to SOW paragraphs 3.3.5.1 – 3.3.5.8.

3.3.5(c) (O&M) Provide NAPIE testing efforts to operate, maintain, and repair NAPIE units.

Applicable to SOW paragraphs 3.3.5.1 – 3.3.5.8.

3.3.5(d) (WCF) Provide NAPIE equipment integration efforts to improve, update, and replace outdated NAPIE units. Applicable to SOW paragraphs 3.3.5.1 – 3.3.5.8.

3.3.5.1 The Contractor shall support the testing of NAPIE units in support of ASI programs and provide Recommendations Reports, Engineering Reports, Software Test Plans, Software Test Reports, Systems Problem Reports, and Acceptance Test Plans and Procedures. (CDRLs A007, A008, A025, A026, A029, A030, and A031)

3.3.5.2 The Contractor shall assist with testing and evaluation by developing Test Plans and Procedures as well as Acceptance Test Plans and Procedures to demonstrate NAPIE requirements compliance and by providing Engineering Reports, Software Test Plans, Software Test Reports, and Systems Problem Reports. (CDRLs A008, A012, A013, A025, A026, A029, A030, and A031)

3.3.5.3 The Contractor shall assist with configuration management by delivering NAPIE configuration documentation (both hardware and software); by continuously updating the configuration documentation to reflect the latest configuration; and by providing Engineering Drawings, Version Description Documents, and Configuration Drawings. (CDRLs A010, A016, A017, A022, A023)

3.3.5.4 The Contractor shall assist by acquiring the use of airfield facilities upon occasions when NAS Patuxent River facilities cannot be used for NAPIE integration and flight test events.

3.3.5.5 The Contractor shall assist by acquiring the use of Surrogate Aircraft for NAPIE flight events.

3.3.5.6 The Contractor shall assist with testing and evaluation by executing tests to verify Aerial Refueling Store system requirements compliance and by providing Software Test Plans, Software Test Reports, System Problem Reports, and Acceptance Test Plans and Procedures.

(CDRLs A025, A026, A029, A030, and A031)

3.3.5.7 The Contractor shall provide on-site maintenance support of NAPIE systems during integration and test events and by providing Test Plans and Procedures. (CDRLs A012 and A013)

3.3.5.8 The Contractor shall assist by performing analyses of NAPIE data collected during test events and by providing Recommendations Reports, Engineering Reports, Briefing and Presentation Material, Software Test Plans, Software Test Reports, Systems Problem Reports, and Acceptance Test Plans and Procedures. (CDRLs A007, A008, A015, A025, A026, A029, A030, and A031)

3.4 Personnel Qualifications.

Paragraph 3.4 from the Basic MAC Contract, N00421-22-D-0006 through N00421-22-D-0068, is required in support of this TO, unless specifically stated otherwise below to provide more detailed requirements and to define the required labor categories.

3.4.2 Key Personnel. Key personnel are those who will be performing in the Key Labor Categories as specified for applicable labor categories below. All other labor categories and Full Time Equivalent (FTE) employees (defined as 1,920 hours) are considered non-key. Key personnel are subject to the substitution restrictions within CTXT.237-9501, Additional or Substitution of Key Personnel (Services). Authorized Key Personnel are identified within Section J, Attachment XX – List of Authorized Key Personnel.

KEY LABOR CATEGORY

LEVEL

BUREAU OF LABOR

STATISTICS (BLS)

STANDARD

OCCUPATIONAL

CLASSIFICATION (SOC)

CODE

NUMBER OF

KEY

PERSONNEL

General and Operations Managers (Program Manager)

Senior 11-1021 One

Network and Computer Systems Administrators (Systems Analyst)

Intermediate 15-1244 One

Software Developers Advanced 15-1252 One

3.4.15 Labor Qualifications. The following lists the minimum labor category education and experience requirements, BLS SOC code, and functional descriptions for each labor category.

3.4.15.1 Computer and Information Research Scientists (Computer Systems Analyst), Journeyman, BLS SOC Code 15-1221.

Function: Conduct research into fundamental computer and information science as theorists, designers, or inventors. Develop solutions to problems in the field of computer hardware and software.

Experience: Of the minimum three years of experience required, at least three of those years of experience must include supporting U.S. military programs.

Education: Bachelor’s degree in an Engineering or Technical discipline or qualifying substitution.

3.4.15.2 Computer and Information Research Scientists (Computer Systems Analyst), Senior, BLS SOC Code 15-1221.

Function: Lead the execution of complex tasks and apply logical analyses or test and evaluation on all programs within the contractual scope. Perform comprehensive analyses of hardware/software concepts, designs, and test requirements. Review, analyze, integrate, and conduct tests and evaluations of contractor- or Government-generated source data and develop interim documentation. Perform system concept formulation, system design analysis, and subsystem design analysis with respect to DoD and airborne systems integration.

Required Experience: Of the minimum 10 years of experience required, at least 5 of those years must be experience with U.S. military systems.

Required Education: Master’s degree in an Engineering or Technical discipline or a qualifying substitution.

3.4.15.3 Computer Systems Analysts (Project Analyst), Journeyman, BLS SOC Code 15-1211.

Function: Analyze science, engineering, business, and other data processing problems to develop and implement solutions to complex applications problems, system administration issues, or network concerns. Perform systems management and integration functions, improve existing computer systems, and review computer system capabilities, workflow, and schedule limitations.

May analyze or recommend commercially available software.

Required Experience: Of the minimum three years of experience required, at least three of those years of experience must include supporting U.S. military programs.

Required Education: Bachelor’s degree in an Engineering or Technical discipline.

3.4.15.4 Computer Systems Analysts (Systems Analyst), Journeyman, BLS SOC Code 15-1211.

Function: Analyze science, engineering, business, and other data processing problems to develop and implement solutions to complex applications problems, system administration issues, or network concerns. Perform systems management and integration functions, improve existing computer systems, and review computer system capabilities, workflow, and schedule limitations.

May analyze or recommend commercially-available software.

Required Experience: Of the minimum three years of experience required, at least three of those years of experience must include supporting U.S. military programs.

Required Education: Bachelor’s degree in an Engineering or Technical discipline.

3.4.15.5 Drafters, All Other (Computer Aided Design (CAD) System Operator), Junior, (BLS SOC Code 17-3019.

Function: Research, design, develop, and utilize CAD methodologies, tools, templates, and processes to support CAD efforts. Recommend adjustments for CAD methodologies, tools, templates, and processes to improve efficiencies in project execution.

Required Experience: No specific field experience required other than what is identified in the function description above.

Required Education: Bachelor’s degree in an Engineering, Technical, or Business discipline or a qualifying substitution.

3.4.15.6 Drafters, All Other (CAD System Operator), Senior, BLS SOC Code 17-3019.

Function: Research, design, develop, and utilize CAD methodologies, tools, templates, and processes to support CAD efforts. Recommend adjustments for CAD methodologies, tools, templates, and processes to improve efficiencies in project execution.

Required Experience: Of the minimum 10 years of experience required, at least 5 of those years must be experience with U.S. military systems.

Required Education: Master’s degree in an Engineering, Technical, or Business discipline or a qualifying substitution.

3.4.15.7 Electrical Engineers, Junior, BLS SOC Code 17-2071.

Function: Research, design, develop, test, or supervise the manufacturing and installation of electrical equipment, components, or systems for test, integration, or use aboard military aircraft.

Required Experience: No specific field experience required other than what is identified in the function description above.

Required Education: Bachelor’s degree in an Engineering discipline.

3.4.15.8 Electrical Engineers, Journeyman, BLS SOC Code 17-2071.

Function: Research, design, develop, test, or supervise the manufacturing and installation of electrical equipment, components, or systems for test, integration, or use aboard military aircraft.

May design and layout circuit boards. May model Radio Frequency (RF) propagation or antenna coverage. May program microcontrollers or Field Programmable Gate Arrays (FPGA).

Required Experience: Of the minimum three years of experience required, at least three of those years must be experience with military systems.

Required Education: Bachelor’s degree in an Engineering discipline.

3.4.15.9 Electrical Engineers, Senior, BLS SOC Code 17-2071.

Function: Serve as a team leader for the support of tasks that involve the design, development, installation, integration, operational maintenance, and testing of baseband, RF, and electrical power and other systems. Perform system-level design and configuration of products including determination of hardware and other platform specifications to meet project requirements while maintaining interoperability with existing sponsor systems. Plan large-scale projects through contractor comparison and trade/cost studies. Perform a variety of electronics engineering tasks and activities that are broad in nature and are concerned with major systems design, integration, and implementation. Shall be called on to troubleshoot unique or complex problems.

Required Experience: Of the minimum 10 years of experience required, 5 of those years must be experience with military systems including circuit board design and layout with RF propagation modeling, antenna coverage modeling tools, microcontroller programming, or FPGA programming.

Required Education: Master’s degree in an Engineering or a qualifying substitution.

3.4.15.10 General and Operations Managers (Project Manager), Senior, BLS SOC Code 11- 1021.

Function: Plan, direct, or coordinate multiple projects within the NAPIE portfolio and pertaining to the NAPIE lab. Duties and responsibilities include formulating estimates, managing daily operations, and planning the use of materials and human resources, project management, such as personnel, purchasing, or administrative services.

Required Experience: Of the minimum 10 years of experience required, at least 3 of those years must have included planning, organizing, directing, and controlling multiple projects in the design, systems engineering, or field service of U.S. military providing installation and integration services, support test, and evaluation Additionally, at least five of those years must include management and supervisory experience.

Required Education: Master’s degree in an Engineering, Technical, or Business discipline or a qualifying substitution.

3.4.15.11 General and Operations Managers (Program Manager), Senior (Key), BLS SOC Code 11-1021.

Function: Plan, direct, or coordinate the operations of public or private sector organizations, overseeing multiple departments or locations. Duties and responsibilities include formulating policies, managing daily operations, and planning the use of materials and human resources that are too diverse and general in nature to be classified in any one functional area of management or administration, such as personnel, purchasing, or administrative services. May manage resources through subordinate supervisors. Act as the overall lead, manager, and administrator for major projects on the contracted effort. Serve as the primary interface and point of contact with

Government Project Leads (GPLs) and other Government program authorities on technical and project issues.