pma 213-pws-DRAFT.pdf

DRAFT

PERFORMANCE WORK STATEMENT

FOR PMA-213

Naval Air Traffic Management Systems

FOR PROGRAM/PROJECT MANAGEMENT SERVICES

1.0 SCOPE

PMA-213 Naval Air Traffic Management Systems is a program office under the Program Executive Officer, Tactical Aircraft (PEO(T)). PMA-213 is responsible for providing relevant, sustainable, decisive air traffic management capabilities to get the warfighter to, through and back from the fight .

multi-pla tform capability enablers include: Ship Air Traffic Management (ATM) Systems: Joint Precision Approach and Landing Systems (JPALS), Radar Landing Systems (RLS), SPN-50 Maritime Air Radar for Tactica l Aircraft, Tactical Air Navigation (TACAN); Shore Air Traffic Management Systems: Shore Air Traffic Control Systems, Expeditionary Air Traffic Control Systems, Shore Landing Systems (Instrument Landing Systems and Precision Approach Radar); Combat Identification (CID): Air Systems, Ship Systems (Mode 5, OE-120, Real-Time Digital power system Simulator (RTDS), Emerging System), Next Genera tion CID; International Programs; Advanced Development: Technical Integration, Technology Development, Data Management Development, Readiness Cell.

This Performance Work Statement (PWS) supports domestic and foreign milita ry sales (FMS)/international products.

This PWS provides program/project management, administrative, budget financial management, and corporate operations support services for PMA-213 Integrated Product Teams (IPTs). PMA-213 planning, execution and management of PMA-213 programs/efforts. The effort to be provided to PMA-213 is outlined below and a ligned by contract line-item numbers (CLINs) for tracking and billing purposes. These efforts will utilize any combination of funding to include RDT&E, APN, OPN, OMN and FMS.

2.0 APPLICABLE DOCUMENTS

See the Basic Contract.

In addition to Section C Paragraph 2.0 of the Basic Award the following documents form a part of this PWS to the extent cited herein. All referenced documents are mandatory unless otherwise specified within the body of this PWS.

Document Number Date Document Title

DoD Directive

5000.1 (Change 1) 28-Jul-22 The Defense Acquisition System

DoD Directive

5000.2 (Change 2)

08-Jun-22 Opera tion of the Defense Acquisition System

SECNAVINST

5000-G 08-Apr-22

Department of the Navy Implementation of the Defense Acquisition System and the Adaptive Acquisition Framework

DoD 5010.12M 31-Aug-18

Procedures for the Acquisition and Management of Technical Data

SECNAV M 5216.5

CH-1

13-May-19 Department of the Navy Correspondence Manual

NAVAIRINST

4030.1 F

06-Apr-21 Naval Air Systems Command Configuration Management Policy

3.0 REQUIREMENTS

3.1 General Requirements

3.1.1 Compatibility

The Contractor sha ll maintain the capability to prepare documents and software packages compatible with the Government IT environment. The current opera ting environment required for this task order includes:

Microsoft Windows 11 Microsoft 365 Microsoft Project 2016 Adobe Acrobat (reader and pro) Internet access

The Contractor sha ll maintain the ability to interface with and transfer data to and from requiring office software applica tions and their upgraded versions. The Contractor shall maintain effective virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with PMA-213. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with PMA-213 during working hours whether a t the normal work site or on travel.

3.1.2 Work Location and Facilities

3.1.2.1 Work location

Approximately 100 percent of work will be performed a t Government site or an alterna te work site as designated.

Government site(s) include Patuxent River Naval Air Station, Patuxent River, MD and Lexington Park, MD.

Contractors performing a t Government site will be provided access to [workspaces, telephones, printers, facsimile/scanning machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary (keep all that apply, add any additional necessary)] to carry out assigned tasks.

3.1.2.2 Meeting support

In support of the tasking outlined in this PWS, the Contractor shall have the capability to support meetings at the classification levels up to Secret with the capacity to support a minimum of [50] persons and have contractor furnished telephone and VTC capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in Paragraph 3.1.1. This support shall be provided within 10 driving miles of Patuxent River, MD.

3.1.2.3 Telework: The Contractor may allow employees to telework with approval from the COR in writing, that a position tasking is eligible for telework. The Contractor may utilize alternate worksites/locations and telework to support continued performance of PWS/PWS tasks in accordance with 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.

3.1.3 Status Reporting

The contractor shall provide status reporting in accordance with the following Contract Data Requirement Lists (CDRLs).

3.1.3.1 Monthly Status Report (CDRL A001)

The contractor shall provide a monthly status report in accordance with the CDRL A001. The report sha ll be cumulative and include work accomplished since submitta l of the last report.

3.1.3.2 Incurred Cost Report (CDRL A002)

The contractor shall provide a financial incurred cost report depicting the projected and actual expenditure of labor hours/cost, material cost, and travel costs in accordance with CDRL A002. The report shall a lso include both monthly and cumula tive man-hour labor costs expended by individual, by labor category, material and travel costs since submitta l of the last report.

3.1.4 Work Schedule to Include Compressed Work Schedule (CWS), Holidays and Overtime The Contractor sha ll provide the required services and staffing coverage during normal working hours. Normal working hours are 8.5 hours for a standard day and 9.5 hours for a CWS day (including a 30-minute lunch break), with core hours being 0830 to 1500 each Monday through Friday (except on the legal holidays specified in the basic contract). The Contractor has the flexibility to start as early as 0600 and end as late as 1800, Monday through Friday.

3.1.4.1 CWS

CWS is allowed in accordance with the terms of the basic contract . CWS is an a lternative 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 a t 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associa ted 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.

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

The Contractor is permitted to observe the above Federal Holidays in accordance with its corporate policy.

3.1.4.3 Overtime

Overtime is not allowed under this Task Order and shall not be charged directly to this task order.

3.1.4.4 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

While genera lly contractor personnel may not perform work on-site at a Government facility without oversight from Federal personnel, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant

Contracting Officer must concur with any determination that work being performed by con tractor personnel is mission essential.

3.1.5 Data Deliverables (Not Separately Priced)

The contractor shall provide data deliverables as required herein and specified on the approved DD Form 1423 Contract Data Requirements List (CDRLs) A001- A005 in Exhibit A.

3.1.6 Other Direct Costs (ODCs)

The Contractor sha ll conduct travel and provide materials to perform tasks contained within this task order tha t are integral to the execution of the program. ODCs are based on a per annum Not to Exceed (NTE) amount. Travel and material costs may include general and administrative expenses but shall not include profit/fee. Renting or leasing of facilities or vehicles will not be allowable as a direct charge to this task order. ODC expenditure documenta tion shall be delivered under CDRL A002.

3.1.6.1 Travel

Travel to other locations in support of program tasking is required for this task order. Travel locations may include

CONUS/OCONUS.

3.1.6.2 Material

Incidental material will be required in performance of this Contract, and all incidental material purchases shall be in accordance (IAW) C-TCT-242.95XX Procedures and Approvals Required Prior to Incurring Direct Material Costs (Sept 2021). All materials not depleted during the performance of this task order shall become Government property upon completion of this task order. The contractor sha ll transfer all materia ls not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administra tive expenses but sha ll not include profit/fee.

3.1.7 Increased Capacity Options

This task order includes option CLINs associa ted with each period of performance for an increase in capacity not to exceed ten percent (10%) of the tota l dollars of the Labor and ODC CLINs within the respective term. This option in accordance with the terms and conditions of this task order.

3.1.8 Transition-In Plan

The services required under this requirement are necessary to the Government and are required to be continued without interruption. The contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation within an estimated 30-day period after award.

3.1.9 Transition Out Strategy

-213 with minimal impact, not only in terms of timeliness of performance but also to ensure that critical da ta and knowledge transfer occurs. Upon termination or expiration of the task order, 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 in accordance with CDRL A003.

Work Turnover. The contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expira tion or termination of the contract to the successor company. The contractor shall effectively communicate with the incoming contractor and Government personnel for the period of transition.

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

Risk Mitigation Strategies. The contractor shall provide a plan of action to mitigate task order performance risks (cost, 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/information to the successor company.

3.2 Security

3.2.1 Investigative Requirements

The Investigative requirements for this task order shall be Classified. All Contractor personnel shall mainta in up to Secret security clearance eligibility, commensurate with the level of classification of the work performed as

Unclassified: All contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30C. All contractor personnel are required to have a favorably adjudica ted Tier-3 investigation from the OPM. The Contractor shall submit a request for personnel security investiga tion to the Government Security Office. The Government Security Office shall initia te the contractor employee's Electronic Questionnaire for Investigations Processing (eQIP) and shall perform a preliminary screening of the contractor employee'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 employee access to Government facilities and information and may prohibit the contractor employee from performance of sensitive duties for fa ilure to provide requested information or when derogatory or adverse information is present on the contractor employee's eQIP. In such cases, the contractor employee may not perform on the Contract.

AND/OR

Classified: All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract's DD-254, Contract Security Classification Specification Form. Contractor personnel shall require access to classified information in performance of this Contract up to and including Secret facility level, with a safeguarding level of Secret. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW National Industria l Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regula tion Part 117, NISPOM Rule. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Offeror employee may not perform on the Contract.

3.2.2 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request

(SAAR)

3.2.2.1 SAAR

All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR) Form DD Form 2875, May 2022 on file, and complete required Annual Information Awareness Tra ining. New employees must submit their SAAR forms within thirty

(30) days of their first day of work. Instructions for processing the SAAR forms are available at:

https://www.esd.whs.mil/Directives/forms/dd2500_2999/DD2875/) SAAR forms shall be submitted to the

3.2.2.2 Common Access Cards (CAC)/Local Badges

Contractor CACs and facility specific identification badges will be issued by the Government to on -site Offeror 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 contract, relocation or termination of an employee, or upon request from the Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract.

3.2.3 DD Form 254

The contractor shall comply with security requirements specified in Attachment (3) DD Form 254 attached to this contract. Information or data that the Contractor accesses shall be handled a t the appropria te classification level.

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 controlled unclassified information (CUI) and to control distribution of CUI in accordance with National Industrial Security Program

Operating Manual (NISPOM) codifying 32 Code of Federal Regula tions Part 117, NISPOM Rule and SECNAV M - 5510.36B, Department of the Navy, Information Security Program.

facility, the Contractor shall comply with Information Security Assurance Standard Guidance and comply with mandatory tra ining requirements.

CUI including Covered Defense Information (meeting the definition of 48 CFR 252.204 7012(a)) generated and/or provided under this contract sha ll be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled

Unclassified Information 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 Sta tements on Technical Documents); and have this statement displayed per DoDI 5230.24.

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

DISTRIBUTION STATEMENT D: D DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only (Critical Technology) (DATE). Other requests for this document shall be referred to Program Executive Office, Tactical Aircraft Programs (PEO(T)), Naval Air Traffic Management Systems (PMA-213), 46585 Expedition Drive, Expedition VII, Suite 300, Lexington Park, MD 20659.

3.2.4.1 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information:

All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR and Government Security Office within 72 hours of the incident occurring.

3.2.4.2 Compliance to NIST 800-171

In accordance with DOD INSTRUCTION 8582.01 SECURITY OF NON-DOD INFORMATION SYSTEMS PROCESSING UNCLASSIFIED NONPUBLIC DOD INFORMATION, the Contractor shall implement the CUI

Security Requirements (Requirements) and associated Relevant Security Controls (Con trols) in NIST Special Publica tion 800-171 (Rev. 1) (NIST SP 800-171), or establish a System Security Plans (SSP) and Plans of Action and Milestones (POAM) that varies from NIST 800-171 only in accordance with DFARS clause 252.204- 7012(b)(2), for all covered contractor information systems affecting this contract.

The Contractor sha ll, a t a minimum, meet the Basic Safeguarding Requirements as follows to meet the comparable security requirements of the NIST SP 800-171 as indicated.

BASIC SAFEGUARDING REQUIREMENT

NIST SP 800-171

REQUIREMENT

Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems) 3.1.1 Limit information system access to the types of transactions and functions tha t authorized users a re permitted to execute 3.1.2 Employ the principle of least privilege, including for specific security functions and privileged accounts 3.1.5 Monitoring and Controlling Remote Access 3.1.12 Encrypting CUI on Mobile Devices 3.1.19 Verify and control/limit connections to, and use of, external information systems 3.1.20

Control information posted or processed on publicly accessible information systems 3.1.22

Identify information system users, processes acting on behalf of users, or devices 3.5.1 Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems 3.5.2 Multifactor Authentication 3.5.3 Sanitize or destroy information system media containing nonpublic DoD information before disposa l or release for reuse 3.8.3 Limit physica l access to organiza tional information systems, equipment, and the respective operating environments to authorized individuals 3.10.1 Escort visitors and monitor visitor activity; mainta in audit logs of physica l access; and control and manage physical access devices

3.10.3, 3.10.4, and 3.10.5

Monitor, control, and protect organizational communications (i.e., information transmitted or received by organiza tional information systems) at the external boundaries and key internal boundaries of the information systems 3.13.1 Federal Information Processing Standard (FIPS) 140-2 Compliant Encryption 3.13.11 Protecting CUI at Rest 3.13.16 Implement subnetworks for publicly accessible system components tha t are physica lly or logically separated from internal networks 3.13.5 Identify, report, and correct information and information system flaws in a timely manner 3.14.1 Provide protection from malicious code at appropriate locations within organizational information systems 3.14.2 Update malicious code protection mechanisms when new releases are available 3.14.4 Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed 3.14.5

Government will conduct such reviews a t least every three (3) years (measured from the date of contract award) and may conduct such reviews at an

If the Government determines that the security controls do not adequately implement the requirements of NIST 800 - 171, then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

Upon the conclusion of the correction period, the Government may conduct a follow-facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies.

3.2.5 Public Release

Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. government authority. Proposed public releases sha ll be submitted for approval prior to release through: PEO(T) Public Affairs Office, 47123 Buse Road, RADM William A. Moffett Building, Patuxent River, MD 20670-1547.

3.2.6 Operations Security (OPSEC)

The Contractor sha ll develop, implement and maintain a facility level OPSEC program that entails security procedures and controls to prevent unauthorized disclosure and control the distribution of covered defense information, equipment, and material used or developed by the Government, Contractor and any subcontractor during performance of the task order. These procedures shall be in accordance with the DoDM 5200.01, Vol. 4, as well as the following OPSEC policies:

a) DoDD 5205.02, DoD Opera tions Security (OPSEC) Program

b) DoD 5205.02-M, DoD Operations Security (OPSEC) Program Manual

c) OPNAVINST 3432.1A, DON Operations Security

d) SECNAV 3070.2, Opera tions Security

The contractor shall implement countermeasures to protect all critical information (CI) associated with this task order. Especially, those activities and/or information which could compromise classified information, operations, or degrade the planning and execution of operations performed or supported by the contractor in support of the mission. Protection of CI will include the adherence to and execution of countermeasures which the contractor initia tes or are provided by NAVAIR in performance of this task order.

The Contractor sha ll prepare an OPSEC Plan for Government review in accordance with the CDRL A005.

3.2.7 Anti-Terrorism Force Protection and Emergency Management The work performed on this task order is not Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall not report for work a t Government facilities upon declaration of any Force Protection Condition above CHARLIE or in any event or emergency where Government officials Essential Only.

3.2.8 Non-Disclosure Agreements

In the performance of the task order, the Contractor may have access to non -public proprietary information. The Contractor shall require tha t any employee performing services under the task order execute a non -disclosure agreement satisfactory to the Task Order Contracting Officer. The non-disclosure agreement shall acknowledge the Contractor and employees' duties with respect to non-public, proprietary information and promise to comply with those obligations.

3.2.9 Cybersecurity Plan

For cybersecurity requirements see the Cybersecurity Plan, Attachment X. Specifically mentioned policies in the Cybersecurity Plan can be accessed via the Cybersecurity Policy Chart a t the following link:

https://dodiac.dtic.mil/dod-cybersecurity-policy-chart/.

The Contractor sha ll be required to deliver a Program Cybersecurity Implementation Plan (CSIP) or Annex CSIP to address each of the sections of the Cybersecurity Plan. The Contractor sha ll demonstra te its understanding of the Cybersecurity Plan and describe how the requirement of each of the sections of the Cybersecurity Plan will be achieved by the Contractor. Sections of the Cybersecurity Plan that are NOT applicable are required to be addressed.

The Contractor sha ll describe why a particular section is not applicable. The final Program CSIP shall be in Adobe Acrobat format with a digital signature from the contractor cognizant authority.

If no approved Program CSIP currently exists between the Contractor and the Government, then one must be created and submitted. If an approved Program CSIP already exists and sufficiently sa tisfies the Cybersecurity Plan requirements for the Contract, then no new CSIP delivery is required. In such cases, the Contractor in consultation with the Government sha ll only submit a Contract Letter to the Government stating that all Cybersecurity Plan requirements are satisfied by the existing Program CSIP.

If Cybersecurity Plan requirements are NOT adequately addressed by the existing Program CSIP, then an update to

Cybersecurity Plan requirements. An Annex CSIP shall address unique Cybersecurity Plan Section "G" Assessment and Authorization requirements if a system is being delivered under the Contract and unique Section "Q" Software requirements if software is being delivered. These Program CSIP updates or Annex CSIPs shall be submitted on a semi-annual (twice per year) basis IAW CDRL A00X.

3.2.9.1 Cyber Incident Response

The Contractor sha ll, within fifteen (15) days of discovering the cyber incident (inclusive of the 72 -hour reporting period, reference https://dibnet.dod.mil/portal/intranet/), deliver all data used in performance of the contract that the Offeror determines is impacted by the incident and begin assessment of potential warfighter/program impact.

Incident da ta shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3).

Reference https://www.dc3.mil/Organizations/DIB-Cybersecurity/DIB-Cybersecurity-DCISE/

In delivery of the incident data, the Contractor shall, to the extent practical, remove Contractor-owned information from Government covered defense information.

If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident da ta within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identifica tion.

The contracting officer will approve or disapprove the request a fter coordination with DC3.

3.2.9.2 NCIS/Industry Monitoring

In the event of a cyber-incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS) and associated law enforcement agencies, which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, or vendor logs that show network activity, including any additional logs the Contractor, subcontractor, or vendor agrees to initia te as a result of the cyber incident or notice of actual or potential vulnerability.

If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor shall cooperate with the NCIS to implement additional measures, which may include a llowing the installation of an appropria te network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of da ta gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alterna tive approach shall a lso be the subject of a separa te agreement negotiated between NCIS and the Contractor.

In all cases, the collection or provision of data and any activities associated with this Performance Work Sta tement shall be in accordance with federal, sta te, and non-US law.

3.3 Detailed Support

The Contractor sha ll provide project and acquisition management, administrative, data analysis, Configuration Management (CM), and Data Management (DM) services for PMA-213 projects/activities, resulting in the successful and efficient execution of programs, projects and the delivery of high -quality, timely documentation.

3.3.1 Research, Development, Test and Evaluation (RDT&E)

The Contractor shall provide project management and acquisition management services for PMA-213 development projects/activities. These services are integral to the execution of development projects/activities under the cognizance of PMA-213. As required, documentation shall be delivered under CDRL A001 and A002.

The Contractor sha ll, on an ongoing basis, provide the following:

3.3.1.1 Develop budgets, track execution, and generate/track financia l documents using Navy and DoD electronic data systems such as Navy Enterprise Resources Planning (NAVY ERP), Program Budget Information System (PBIS), SharePoint, Common Spend Plan Tool (CSPT), and Integra ted Data Environments (IDE).

3.3.1.2 Coordinate, update, and submit the Program Objective Memorandum (POM), Program Review (PR), develop issue sheets, conduct budget drills and reclamas, coordinate inputs, and ensure data is in an acceptable format for the IPT Leads.

3.3.1.3 Mainta in, consolida te and organize databases of budgetary status information based on information provided through Navy ERP and the PBIS.

3.3.1.4 Execute budget activities, including tracking the status of obligations and expenditures in detail by year, appropria tion, and project for financial reconciliation of all funds; update/develop spreadsheets and financial status briefs and presentations.

3.3.1.5 Track and monitor financia l documents through the routing and approval process.

3.3.1.6 Mainta in knowledge and awareness of a ll statutory and regulatory acquisition document requirements and advise the Government Acquisition Lead of policy changes.

3.3.1.7 Research, develop, review, analyze, revise, route, and track acquisition documentation for Government review and approval, including but not limited to DoDI 5000.02 documentation (i.e., Acquisition Stra tegy, Acquisition Program Baseline (APB), and Acquisition Decision Memorandum (ADM)), Acquisition Plans (APs), Justification and Approvals (J&As), and Determination and Findings (D&Fs) to facilitate contract efforts and milestone decisions.

3.3.1.8 Provide independent assessments and recommendations for improving program acquisition and processes.

3.3.1.9 Respond to da ta drills under the direction of the Acquisition Team Lead.

3.3.1.10 Develop, coordinate, and staff all required acquisition reporting documents, including Selected Acquisition Reports (SARs), Defense Acquisition Executive Summaries (DAES), and ASN(RD&A) Information System (RDAIS) inputs to facilita te annual, quarterly, monthly, and ad hoc submissions, audits, and reviews.

3.3.1.11 Participate in a ll Procurement Planning Conferences (PPCs), Data Requirements Review Boards (DRRBs), and Procurement Management Tool (PMT) reviews.

3.3.1.12 Develop, route, and maintain the status of Procurement Planning Agreements (PPAs), Procurement Initia tion Documents (PIDs), Rough Orders of Magnitude (ROMs), Certificates of Urgency (COUs) and provide weekly updates to the Government Acquisition Lead.

3.3.1.13 Work with the IPTs to establish and manage procurement timelines as a part of the overall acquisition process to meet cost, schedule, and performance goals; manage PMT updates.

3.3.1.14 Furnish general administrative service for procurement projects.

3.3.1.15 Mainta in knowledge, awareness, and usage as needed to assist the Acquisition Lead in command wide tools to include Acquisition Management Suite (AMS) and the Acquisition Program Health Monitor (APHM) Tool.

3.3.1.16 Provide Configuration Management (CM) to development projects in accordance with PMA-213 established processes, including: facilitation of configuration control boards (CCBs), track Engineering Change Proposals (ECPs) that have been requested or submitted and track ECP implementation after approval. (Reference Attachment (5), PMA-213 Configuration Management (CM) Plan.)

3.3.1.17 Conduct Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs), configuration status accounting, internal change control process and technical data package reviews.

3.3.1.18 Identify and review third-party provided contract deliverables for technical completeness, ensuring the distribution statements.

3.3.1.19 Prepare PWS/SOWs and CDRLs for use in contract documentation.

3.3.1.20 Download contract deliverables from third-party provided integrated data environments and disseminate the deliverables to Government team members.

3.3.1.21 Draft and route acceptance/rejection documentation for third -party provided deliverables for approval by the Government.

3.3.1.22 Ensure program documentation is stored in a Government -approved loca tion/site.

3.3.1.23 Perform foreign disclosure investigations and provide detailed preliminary release readiness analyses of hardware and software systems, specifica tions or other technical data for compliance.

3.3.1.24 Prepare meeting agendas, coordinate, attend and participate in IPT and prime Contractor meetings, requirements reviews, design reviews, logistics program reviews, system working group meetings, technical interchange meetings, project review meetings, test planning meetings, and other meetings as required/directed and prepare and distribute meeting minutes.

3.3.1.25 Collect and distribute action items from project meetings after receiving Government approval of the content and format of the documents. Maintain an issue and action item database to support the IPTs in managing the lifecycle of product issues and actions. Track action items to closure.

3.3.1.26 Coordinate and participate in working groups, meetings, and conferences with other Program Manager, Air (PMAs) offices, Program Executive Offices (PEOs), Navy and other military services to coordinate program plans, road maps, and reviews of potentia l technologies that may a id in accomplishing development projects.

3.3.1.27 Perform cost/benefit analyses, cost trade-off analyses, business case analyses, cost variance analyses, and/or present value analyses to support the projects in balancing mission requirements, system constraints, performance, and provide technical input to support the preparation or revision of related acquisition documentation.

3.3.1.28 Plan activities, presenting alterna tive funding or acquisition stra tegies and cost estimates for new project requirements for Government considera tion and appropria te action; Enter planning data in Government personnel planning tools.

3.3.1.29 Review project progress and track sta tus of vendor critical contract deadlines to identify and report potential problems and/or issues with prime Contractor schedule conflicts, resource scarcity, and proposed solutions.

3.3.1.30 Analyze requirements and schedules and evaluate and recommend changes to schedules and associated milestones to ensure compatibility with overa ll project objectives.

3.3.1.31 provide recommendations regarding potentia l returns on investment and associa ted risks to the project.

3.3.1.32 Recommend and provide alterna tives for project execution spend plan development, out -year planning, and the creation of POM issue sheets as related to the Planning, Program, Budgeting, Execution (PPBE) process.

3.3.1.33 Contribute to the development of white papers, quad charts and trade studies.

3.3.1.34 Develop and disseminate weekly status reports.

3.3.1.35 Develop, update and maintain the Flight Plan tha t supports capability strategies and industry day events.

3.3.1.36 Manage risk by analyzing opportunities and preparing plans and assessment methods, maintain tracking methods for project opportunities.

3.3.1.37 Mainta in a risk management da tabase. Ensure risks are current and actively managed by the risk owners.

Provide risk data to support briefings.

3.3.1.38 Facilita te risk management boards.

3.3.1.39 Develop an Integrated Government Schedule (IGS) that fully identifies and integrates Government -led milestones, accomplishments, deliveries, and exit criteria, including major interfaces and exchanges to/from any integrated master schedule, and sufficient detail to readily identify critical and high -risk efforts.

3.3.1.40 Prepare and maintain development schedules using critical pa th networks and track action items connected to these schedules.

3.3.1.41 Review the prime Contractor-provided segment and lower-level specifica tions for compliance with project security plans, procedures, and higher-level security directives per SECNAV M 5510.36B.

3.3.1.42 Provide analysis and documenta tion to meet Information Assurance (IA) requirements in support of the prime Contractor.

3.3.4 Aircraft Procurement, Navy (APN)

The Contractor shall provide project management and acquisition management services for PMA-213 modification projects/activities which incorporate improved performance, operational capabilities or safety. These services are integral to the execution of the retrofit/upgrade/modification projects/activities under the cognizance of PMA-213.

Tasking shall cover future OSIP support as identified in budget submissions. As required, documentation shall be delivered under CDRL A001 and A002.

The Contractor sha ll, on an ongoing basis, provide the following:

3.3.4.1 Develop budgets, execute tracking, and generate and track financial documents using various Navy and DoD electronic da ta systems such as Navy ERP, PBIS, SharePoint, CSPT and IDE.

3.3.4.2 Coordinate, update, and submit the POM, PR, issue sheet development, budget drills, and reclamas with IPTLs, as well as coordinate inputs and ensure tha t data provided is in an acceptable format.

3.3.4.3 Mainta in, consolida te and organize databases of budgetary status information based on information provided through Navy ERP and the PBIS.

3.3.4.4 Perform budget execution, including tracking status of obligations and expenditures in detail by year, appropria tion, and project for financial reconcilia tion for all funds; update and develop spreadsheets and financia l status briefs and presentations.

3.3.4.5 Prepare financial charts and input for briefings in support of mid-year reviews, budget execution reviews, spend plan reviews and various other project briefings.

3.3.4.6 Track and monitor financia l documents through the routing and approval process.

3.3.4.7 Participate in preliminary financial reviews and prepare monthly and quarterly reports for the IPT Leads.

3.3.4.8 Mainta in knowledge and awareness of a ll statutory and regulatory acquisition document requirements and advise the Government Acquisition Lead of policy changes.

3.3.4.9 Research, develop, review, analyze, revise, route, and track acquisition documentation for Government review and approval, including but not limited to DoDI 5000.02 documentation (i.e., Acquisition Strategy, APB, and ADM), APs, J&As, and D&Fs to support contract efforts and milestone decisions.

3.3.4.10 Provide independent assessments and recommendations for improving project acquisition efficiencies and processes.

3.3.4.11 Respond to da ta drills as directed by the Acquisition Team Lead.

3.3.4.12 Develop, coordinate, and staff all required acquisition reporting documents, including SARS, DAES, and RDAIS inputs to support annual, quarterly, monthly, and ad hoc submissions, audits, and reviews.

3.3.4.13 Facilita te all PPCs, DRRBs and PMT reviews.

3.3.4.14 Develop, route, and maintain sta tus of PPAs, PIDs, ROMs, and COUs, and provide weekly updates to the Government Acquisition Lead.

3.3.4.15 Establish and manage procurement timelines with the IPTs as a part of the overall acquisition process in support of meeting cost, schedule, and performance goals; manage PMT updates.

3.3.4.16 Furnish general administrative service for procurement projects.

3.3.4.17 Mainta in knowledge, awareness, and usage as needed to assist the Acquisition Lead in command wide tools to include Acquisition Management Suite (AMS) and the Acquisition Program Health Monitor (APHM) Tool.

3.3.4.18 Provide CM/DM support to procurement projects in accordance with PMA-213 established processes.

3.3 4.19 Facilita te CCBs and provide data required for their conduct.

3.3.4.20 Track ECPs that have been requested or submitted for review/approval to ensure completion in a timely manner. After ECP approval, assist the Government by tracking ECP implementation.

3.3.4.21 Conduct FCAs and PCAs, configuration status accounting, internal change control process, and technical data package reviews with the Government.

3.3.4.22 Identify and review third-party provided contract deliverables with the Government, including reviewing for technical completeness, ensuring data rights are consistent/appropria te, and verifying appropriate markings and distribution statements.

3.3.4.23 Prepare and route PWS/SOWs and CDRLs for use in contract documenta tion for the Government.

3.3.4.24 Download contract deliverables from third-party provided integra ted data environment(s) and disseminate the deliverables to Government team members.

3.3.4.25 Draft and route acceptance/rejection documentation for third -party provided deliverables for approval by the Government.

3.3.4.26 Ensure project documentation is stored in a Government-approved location/site.

3.3.4.27 Perform foreign disclosure investigations and provide detailed preliminary release readiness analyses of hardware and software systems, specifica tions or other technical data for compliance.

3.3.4.28 Prepare meeting agendas, coordinate, attend, and participa te in IPT and prime Contractor meetings, requirements reviews, design reviews, logistics program reviews, system working group meetings, technical interchange meetings, project review meetings, test planning meetings, and other meetings as required/directed, and prepare and distribute meeting minutes.

3.3.4.29 Collect and distribute action items from project meetings after receiving Government approval of the content and format of the documents. Maintain an issue and action item database to support the IPTs in managing the lifecycle of product issues and actions, and track action items to closure.

3.3.4.30 Coordinate and participate in working groups, meetings and conferences with other PMAs offices, PEOs, Navy and other military services to coordinate project plans, road maps and reviews of potential technologies that may aid in accomplishing procurement projects.

3.3.4.31 Perform cost/benefit analyses, cost trade-off analyses, business case analyses, cost variance analyses and/or present value analyses to support the projects in balancing mission requirements, system constraints, performance and provide technical input to support the preparation or revision of related acquisition documentation.

3.3.4.32 Plan activities to include presenting alternative funding or acquisition strategies and cost estimates for new project requirements for Government consideration and appropria te action, and enter planning data in Government personnel planning tools.

3.3.4.33 Review project progress and track sta tus of vendor critical contract deadlines to identify and report potential problems and/or issues with prime Contractor schedule conflicts, resource scarcity and proposed solutions.

3.3.4.34 Provide analyses of requirements and schedules and evaluate and recommend changes to schedules and associa ted milestones to ensure compatibility with overall project objectives.

3.3.4.35 Provide analyses of projected and actual systems cost, including project engineering requirements, logistics recommendations to support each initiative, their potentia l return on investment and associa ted risk to the project.

3.3.4.36 Provide recommendations and alternatives in support of project execution, spend plan development, out -year planning and the creation of POM issue sheets as rela ted to the PPBE process.

3.3.4.37 Contribute to the development of white papers, quad charts and trade studies.

3.3.4.38 Develop and disseminate weekly status reports on fielding and deployments to both government and industry.

3.3.4.39 Develop, update and maintain the Flight Plan tha t supports capability strategies and industry day events.

3.3.4.40 Provide risk management support for analysis of opportunities assessment and prepare plans and assessment methods; prepare and maintain opportunities tracking methods to assist in managing project opportunities.

3.3.4.41 Mainta in risk management database. Ensure risks are up to date and actively being managed by the risk owner. Provide risk data to support briefings.

3.3.4.42 Facilita te risk management boards.

3.3.4.43 Develop an IGS with the Government that fully identifies and integrates Government -led tasks, consistent accomplishments, deliveries and exit criteria, includes major interfaces and exchanges to/from any integrated master schedule, and is sufficiently deta iled so that critical and high-risk efforts are readily identified.

3.3.4.44 Prepare and mainta in product development schedules using critical path networks and track action items connected to these schedules.

3.3.4.45 Provide support of Post Production government-furnished equipment (GFE) and contractor-furnished equipment (CFE). Review and validate GFP/GFE/government furnished information (GFI) requirements, procurement planning, procurement initia tion, status tracking, management, risk reduction, integration and delivery schedules and costs in support of retrofit efforts.

3.3.4.46 Coordinate with original equipment manufacturer (OEMs) to ensure adequate lead times and timely procurement initia tion of equipment to support on-time deliveries. Review all pertinent PMA-213 contracts to ensure proper GFE specifications, budget and delivery schedules are met. Investigate/coordinate transportation requirements to ensure appropria te lead times are planned for freight forwarders or to co -production FMS manufacturers or staging a reas for modifications or kitting facilities. Provide recommendations on various acquisition strategies for aircraft, engines, a irframe GFE, CFE, ancillary equipment, peculiar support equipment (PSE), training or logistics.

3.3.4.47 Provide analyses and support of post-production Program Security Protection, Information Assurance, Foreign Disclosure and Technology Transfer Determinations, Arms Export Control Act (AECA), as amended Foreign Assistance Act (FAA) and the International Traffic in Arms Regula tions (ITAR). Review and maintain foreign disclosure support documentation, review documentation, review the release of all classified and sensitive unclassified documents to foreign nationals and their governments via Technology Transfer Security Assistance Review Boards (TTSARB) and National Disclosure Policy Committee (NDPC) Record of Actions (RAs).

3.3.4.48 Coordinate and conduct security reviews with the PMA-213 IPTs. Conduct briefings and provide foreign disclosure and technology transfer release awareness and briefings to PMA-213 personnel and assist with the releasability process for systems sourced from outside PMA-213 by coordinating with the necessary cognitive experts.

3.3.5 Other Procurement, Navy (OPN)

The Contractor shall provide project management, acquisition management, financial management, administrative, and technica l…