Attachment 0005 Performance Work Statement.pdf

SEP 23

PERFORMANCE WORK STATEMENT (PWS)

FOR ENGINEERING SOFTWARE SERVICES IN SUPPORT OF THE

AN/AVR-2B(V) LASER DETECTING SET (LDS)

27 September 2023

Part 1

General Information

1.0 SCOPE

1.1 GENERAL

This performance work statement (PWS) establishes spares and software engineering services requirement for a five (5) year Indefinite Delivery Indefinite Quantity (IDIQ) contract for AN/AVR-2B(V) Laser Detecting Set (LDS) to ensure that U.S. Army Communications- Electronics Command (CECOM) has a contract vehicle in place for the provision of engineering software support services in Army fixed and rotary wing aircraft as the software for the AN/AVR-2B(V) LDS has transitioned to Software Engineering Center (SEC) in CECOM for support. The software engineering service will support potential hardware obsolescence efforts that arises in AN/AVR-2B(V) components installed in Army fixed and rotary wing aircrafts.

Elements of LDS program are classified up to the SECRET level. The U.S. Government (USG) will award a hybrid contract on a Cost-Plus-Fixed-Fee (CPFF) for services and Firm-Fixed- Price (FFP) for spares production.

1.1.1 DESCRIPTION OF SERVICES

This PWS establishes the acquisition requirement for a five (5) year IDIQ contract with a CPFF Contract Line-Item Number (CLIN) for engineering and technical services in support of software for AVR-2B(V) LDS. The service requirement is for software engineering task effort resulting from approved hardware obsolescence changes for unplanned AN/AVR-2B(V) LDS technical issues that arise during; depot operations, training, aircraft integration and system level fielding in Continental U.S. (CONUS) and outside Continental U.S. (OCONUS) locations where the U.S. Army Aircraft may be located. The contractor shall provide personnel, equipment, supplies, facilities, tools, materials, supervision, and other items and non-personal services necessary to perform the contractor support services (CSS) for LDS as defined in this PWS. The place of performance of the engineering software support services will take place at Tobyhanna Army Depot (TYAD) and at contractor’s facility in Danbury, CT. The software engineering services will be on an as required basis in CONUS and OCONUS locations as noted in appendix D of this PWS resulting from unforeseen hardware obsolescence issues.

Travel to OCONUS locations will be minimal or none, it is the contractor’s responsibility to abide by all laws and regulations of the host country. The CSS requirement is for the provision of software engineering services in support of AN/AVR-2B(V) components as listed in appendix C of this PWS. The contractor shall perform services requirement to the standards in accordance with (IAW) part 2 of this PWS. Task orders will be issued on a CPFF basis for specific services and defined tasks involving components of unknown risk. The major components of the AN/AVR-2B(V) LDS are signal comparator module and sensor unit. This PWS applies to the AN/AVR-2B(V)1 and AN/AVR-2B(V)2 LDS variants as identified in paragraph 5.0. appendix A of this PWS. in

1.1.2 BACKGROUND

The CECOM Integrated Logistics Support Center (ILSC) and SEC are delegated responsibilities to provide systems level support and sustainability of the software in fielded AN/AVR-2B(V) systems. Program Management Office (PMO) for Aircraft Survivability Equipment (PM ASE) awarded a five (5) year IDIQ sole-source contract to Danbury Mission Technologies (DMT) located in Danbury CT to provide the current technical and engineering services support for AN/AVR-2B(V) LDS and this contract expired in August 2023. This PWS effort will enable CECOM to include engineering software support services in the follow-on contract after CECOM’s current contract for spares expires in September 2023. The AN/AVR- 2B(V) LDS is manufactured by DMT and is a passive laser warning system that receives, processes, prioritizes, and displays threat information resulting from aircraft illumination by laser energy from laser designators, laser rangefinders, and laser beam-rider missile guidance systems. LDS serves to increase aircrew situational awareness when being actively targeted by weapon systems which utilize emitted laser energy as a function of their targeting or target engagement process.

1.1.3 PERIOD OF PERFORMANCE

1.1.3.1 The period of performance (POP) shall be in accordance with the IDIQ contract and subsequent follow-on contract. The AN/AVR-2B(V) LDS software, transitioned to sustainment(T2S) by SEC in 1QFY23 from PM ASE. The software portion of engineering support services in PM ASE contract will be incorporated into CECOM ILSC IDIQ spares contract to provide software engineering services that results from approved hardware obsolescence changes during the life-cycle sustainment of AN/AVR-2B(V) LDS. The PM ASE engineering services contract was awarded as sole-source IDIQ contract to DMT.

1.1.3.2 Other options within software engineering support services will be proposed, evaluated and negotiated at the time the requirement occurs. Proposals will be due 30 days after receipt of rough order of magnitude (ROM) from the USG.

1.2 CONTRACT MANAGEMENT

The Contractor shall establish key personnel as a focal point to the two areas: first (1st) Contractor Program Manager (CPM) for technical areas and second (2nd), Contracting Representative Manager (CRM) for contractual areas—to accomplish both aspects of this contract. The names of these persons and alternates who shall act for the Contractor when CPM & CRM Managers are absent shall be designated in writing to the USG contracting officer (KO). The CPM shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. Please provide an organization chart for all Contractor personnel associated with LDS program.

1.3 PROGRAM MANAGEMENT

1.3.1 The contractor shall establish a program for the fully integrated AN/AVR-2B(V) production that provides for planning, monitoring and reporting system performance, control of costs, risk and schedule as related to the software services portion. This program shall be presented during the post award conference for Government review and approval.

1.3.2 The contractor shall provide program management support for the AN/AVR-2B(V) program review meetings. Depending on the size and dollar amount, some task orders shall require a technical interchange meeting (TIM), the number and type of reviews shall be detailed in the individual delivery order.

1.4 DATA MANAGEMENT

The contractor shall establish a centralized system for management of all data required under this contract. The contractor, in developing information that will be furnished to the Government, shall make the maximum use of existing data and provide maximum multiple use of technical information. Specific data management functions shall include schedule control for deliverables, maintenance of deliverables and approval of deliverable format, distribution and delivery of data products. The system shall include facilities for storage of all data developed or utilized for this contract and shall provide equal access to data by the Government. The Government reserves the right to review all data associated with and developed for the

AN/AVR-2B(V) LDS.

1.5 QUARTERLY INTEGRATED PROGRAM REVIEWS (QIPRS)

1.5.1 The contractor shall host and support QIPRs on dates mutually agreed upon by the Contractor and the Government, the number and type of QIPRs shall be detailed in the individual delivery order for spares production in technical requirement document (TRD). Each QIPR shall be held for a maximum of two days. The QIPR location is the contractor’s facility in Danbury, CT. The purpose of the QIPRs shall be to:

1.5.2 Assess the progress and status of the AN/AVR-2B program. At a minimum, the contractor shall present an update of overall program status, cost, schedule, status of CDRL deliverables, as well as programmatic concerns, to include DMSMS, for spares and engineering services efforts at each QIPR.

1.5.3 The contractor shall, IAW TRD for spares CDRL A011, DI-ADMIN-81249C, conference agenda, prepare an agenda and deliver it to the Government for approval. Additionally, draft briefing charts will be provided to the Government NLT three (3) working days prior to the QIPR. The contractor shall provide meeting minutes IAW TRD CDRL A012, DI-ADMIN- 81250C, conference minutes.

1.6 GOVERNMENT FURNISHED PROPERTY (GFP)/GOVERNMENT FURNISHED

EQUIPMENT (GFE) ACCOUNTING AND REPORTING

1.6.1 GFP/GFE may be provided and authorized for use to support this effort. In addition, the contractor shall use GFP/GFE that has previously been provided under PM ASE engineering services contract W58RGZ-13-D-0147 and CECOM spares production contract SPRL1-19-D- 0076. The GFP/GFE listing is provided in this PWS in appendix E and as attachment 1 to this

PWS.

1.6.2 All equipment purchased, manufactured, or received as GFP/E shall be accounted for IAW Army total asset visibility-contractor (TAV-C) as part of Army Materiel Command (AMC) approved contractor internal property controls.These controls shall be established and maintained to manage all property provided as GFP/E, purchased, or otherwise acquired for use in this effort.

1.6.3 Army Materiel Command (AMC) and its units use TAV-C capability in its logistics management program (LMP) to account for Government furnished equipment, materiel, or property (GFE/M/P) placed in the possession of contractors to support contracts for: 1) repair, modification, or upgrade work; 2) materials held for tock, store and issue (SSI), or 3) new production. Accounting records within LMP for this inventory are subject to verifying physical inventories and audits by the Army to ensure accuracy.

1.6.4 To use TAV-C, contractors shall request one of the two TAV-C access methods to exchange required inventory data with LMP: (1) defense logistics management standards (DLMS) interface or (2) the Army TAV-C portal. Approval of the contractor’s access method will be based first on the type of work being performed, second, the sufficiency of the contractor’s existing property accountability and connectivity to LMP, and third, request by the contractor to use the portal based on economic factors.

1.6.4.1 Contractor or contracted firm-The contractor shall provide to the COR a physical inventory plan demonstrating how the contractor will achieve a 100% physical inventory count of all material in the contractor’s custody over the length of period of performance or 1 calendar year for the start of the period of performance. Inventory records are subject to verification by the government. Contractor must maintain record of physical inventory counts performed to be provided in the event of an inspection. The report shall consist of the following, as a minimum and follow TRD CDRL A009 DI-MGMT-80441D for quarterly:

1.6.4.1(a) National stock number (NSN) 1.6.4.1(b) Manufacture part number 1.6.4.1(c) Item name/nomenclature 1.6.4.1(d) Serial number (if available) 1.6.4.1(e) Quantity 1.6.4.1(f) Unit of measure 1.6.4.1(g) Condition code 1.6.4.1(h) Storage location 1.6.4.1(i) Sub-location (if applicable)

1.6.4.1(j) Date of last physical inventory 1.6.4.1(k) Quantity adjusted (if applicable).

1.6.5 It is now a DoD policy that all GFP/E be reported in the GFP module or Wide Area Workflow module of the Procurement Integrated Enterprise Environment (PIEE) as required by the DFARS clause 252.245-70XX, Management and Reporting of GFP/E. This clause provide guidance on what is an acceptable system or systems for managing and accounting GFP/GFE.Contractors will use this methods for accounting Government property as further described below:

1.6.5.1 GFP Module of PIEE: The Contractor shall use the (GFP) module of (PIEE) to-:

1.6.5.1(a) Report physical receipt of GFP/E.

1.6.5.1(b) Report the loss of Government property, in accordance with paragraph (f)(1)(vii) of the FAR 52.245–1 clause. Unless otherwise provided for in this contract, this requirement applies to a loss of GFP/E that results from damage that occurs during work in process.

1.6.5.1(c) Report the transfer of GFP/E to another DoD contract.

1.6.5.1(d) Report the shipment of GFP/E to the Government or to a contractor. The GFP module generates the electronic equivalent of the DD form 1149, DD form 1348–1, or other required shipping documents.

1.6.5.1(e) Report when serially managed items of GFP/E are incorporated into a higher-level component, assembly, or end item.

1.6.5.1(f) Complete the plant clearance inventory schedule in accordance with paragraph (j)(2) of the FAR 52.245–1 clause unless disposition instructions are otherwise included in this contract. The GFP module generates the electronic equivalent of the Standard Form (SF) 1428, Inventory Disposal Schedule.

1.6.5.1(g) Submit a request to buy back or to convert to GFP/E items of Contractor-acquired property.

1.6.5.2 Information regarding the GFP module is available in the GFP Module Vendor Guide at https://dodprocurementtoolbox.com/site-pages/gfp-resources. Users may also register for access to the GFP module and obtain training on the PIEE home page at https://wawf.eb.mil/ piee-landing.

1.6.5.3 In complying with paragraphs 1.6.5.1(a) through (g) of this clause, the Contractor shall report the updated status of the property to the GFP module within 7 business days of the date the change in status occurs, unless otherwise specified in the contract.

1.6.5.4 The Contractor shall use Wide Area Workflow in accordance with DFARS Appendix F Chapter 2, Reparable Receiving Report or DD Form 250, to report the shipment of reparable items after completion of repair, maintenance, modification, or overhaul.

1.6.5.5. When Government property is in the possession of subcontractors, the Contractor shall ensure that reporting is accomplished using the data elements below of this clause.

https://dodprocurementtoolbox.com/site-pages/gfp-resources https://wawf.eb.mil/piee-landing https://wawf.eb.mil/piee-landing

1.6.5.5(a) National stock number (NSN). If an NSN is not available, use either the combination of manufacturer's CAGE code and part number, or model number.

1.6.5.5(b) CAGE code on the accountable Government contract.

1.6.5.5(c) Received/sent (shipped) date.

1.6.5.5(d) Accountable Government contract number.

1.6.5.5(e) Serial number (for serially managed items that do not have a UII) 1.6.5.5(f) Supply condition code (only required for reporting of reparable items).

1.7 SECURITY REQUIREMENT

1.7.1 Security requirement and classification of information and materials utilized or produced under this program shall be assigned IAW security & AT-OPSEC appendix to PWS/SOW/SOO included in DD form 254 package, as specified by CECOM G2-office and the current security classification guide (SCG) for ASE family of systems provided by PM ASE office. The AT- OPSEC appendix to PWS is provided in this PWS as an attachment 2.

1.7.2 This acquisition action will require the contractor to have access to classified information up to SECRET to submit a proposal. The resultant contract will require the contractor to have access to classified information and the secret internet protocol router network (SIPRNet) during performance of the contract. Per AR 530-1 operations security, the CECOM OPSEC plan, and AR 350-1 Army training and leader development contractor employees must complete AT level I awareness training and iWatch training within 30 calendar days of reporting for duty and annually thereafter.

1.7.3 Level 1 AT OPSEC training- As required by the applicable service task order, all contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT level I awareness training within 30 calendar days after task order start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer (KO). If a COR is not assigned, within 30 days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://jkodirect.jten.mil/ for CAC holders. Non-CAC-holders may go to: http://jko.jten.mil/course/atl1/launch.html.

1.7.4 iWatch Training- As required by the applicable service task order, this standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the ILSC COR. This training shall be completed within 30 calendar days of task order award and within 30 calendar days of new employees commencing performance with the results reported to the ILSC COR no later than 30 calendar days after task order award.

http://www.myarmyonesource.com/familyprogramsandservices/iwatchprogram/default.aspx http://jko.jten.mil/course/atl1/launch.html http://www.myarmyonesource.com/familyprogramsandservices/iwatchprogram/default.aspx

1.8 QUALITY ASSURANCE/ QUALITY ASSURANCE SURVEILLANCE PLAN

1.8.1 The Government will evaluate the contractor’s performance of service requirements in accordance with the Government’s quality assurance surveillance plan (QASP) and PWS performance standards herein. The QASP is an organized written document provided by the Government, specifying the surveillance methodology that the Government will use to conduct surveillance of the contractor’s performance to verify contractor has performed services to the standards required for each PWS requirement specified herein. The Government relies on the contractor to monitor daily performance using internal quality procedures and practices (e.g., a quality control plan that describes the internal staffing and procedures that the Contractor uses to meet the quality, quantity, timeliness, and responsiveness requirements/goals to achieve customer satisfaction).

1.8.2 The performance requirements summary in the QASP summarizes the performance objectives, standards, performance threshold, and methods of surveillance the Government will use to conduct surveillance of and assess contractor’s performance of service requirements against the PWS performance standards..

1.9 FAILURE NOTIFICATIONS AND GOVERNMENT REMEDIES

1.9.1 The contractor shall notify the Government via electronic means of any contractor, subcontractor, or supplier qualification test failures and factory acceptance test failures, or any safety related failures within 24 hours of contractor awareness of the failure.

1.9.2 The Government Procuring Contractor Officer (PCO) shall pursue remedies for the contractor’s failure to perform satisfactory services of failure to correct non-conforming services IAW the terms and conditions of the contract.

1.10 INSPECTION AND ACCEPTANCE

1.10.1 The inspection requirements, frequency and procedures shall be IAW AN/AVR-2B(V) performance specification.

1.10.2 For any services applicable, the free on board (FOB) shall be at destination as specified for spares production in this contract. The contractor shall request the “ship to” address from the PCO if the “ship to” address is not specified in section B of this contract award.

RIC: AN5 & DODAAC: W25G1W

W1A8 Defense Logistics Agency (DLA) DIST-TOBYHANNA Gibbs and Fifth Streets Warehouse 6 Bay 4 Tobyhanna PA 18466-5059

1.11 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

1.11.1 The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor the contractor's performance and notify both the PCO and contractor of any deficiencies;

coordinate availability of Government furnished property, and provide site entry of contractor personnel.

1.11.2 A letter of designation issued to the COR, a copy of which is sent to the contractor, states the responsibilities and limitations of the COR especially regarding to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the contract. The COR designated for this contract will provide the contractor access to all available Government furnished information, facilities, material, equipment, services, etc. as required to accomplish the effort.

1.12 CONTRACTUAL AUTHORITY AND COMMUNICATIONS

1.12.1 The PCO is the only person authorized to approve changes in any of the requirements of this contract, notwithstanding provisions contained elsewhere in the contract, the said authority remains solely the Contracting Officer's. The contractor shall not comply with any order, direction or request of Government personnel that would constitute a change, unless it is issued in writing and signed by the KO. No order, statement, or conduct of any Government personnel who visit the contractor's facilities or in any other manner communicates with contractor personnel during the performance of this contract shall constitute a change under the changes clause of this contract and no adjustment will be made in the contract price to cover any increase in charges incurred as a result thereof. Therefore, in no event will any understanding, agreement, modification, change order, or other matter deviating from the terms of the basic contract between the contractor and any other person be effective or binding on the Government. If, in the opinion of the contractor, an effort outside the existing scope of the contracts is requested, the contractor shall promptly notify the PCO in writing. No action shall be taken by the contractor unless the PCO or basic contract PCO has issued a formal modification.

1.12.2 Upon identification of the need for a task order in the software services requirement, the designated PCO will issue a request for task execution plan (RTEP) to the contractor. The contractor shall respond to requests from the designated PCO only. The Government’s RTEP does NOT constitute an authorization to start work. The Government is not required to approve the resulting task execution plan (TEP) and issue a task order.

1.12.3 It is the Government’s intent to issue RTEPs that reflect a performance-based contracting approach. In a performance based RTEP, the Government will specify requirements in terms of performance objectives and the contractor will propose “how to” best satisfy those objectives. The RTEP will contain a PWS vice a TRD/SOW and will require the contractor's TEP to address all resources to perform the tasks of the PWS. The TEP shall provide a breakout by year of all labor categories, hours, total amount as well as all other direct costs (ODCs) (e.g., travel, miscellaneous, etc.) and materials with completion dates.

1.12.4 The Government will strive to award a task order within a reasonable and customary time frame of receipt of TEPs. The Government will either approve the TEP or enter discussions as soon as practical after TEP receipt. When requested, the contractor shall provide an updated TEP to address the results of such discussions.

1.12.5 Upon Government approval of the TEP and designation of an appropriate fund cite, the PCO will issue a delivery order to the contractor. Contractor work shall commence only after issuance of the delivery order by the PCO.

Part 2 Baseline Tasks

2.0 ENGINEERING SOFTWARE SERVICES REQUIREMENTS (Cost-Plus- Fixed- Fee)

Part 2 of the PWS is for contractor technical/engineering, management support, and services in support of the software for AN/AVR-2B(V) program. The services will be on an as-required basis as a result of a hardware obsolescence replacement solution.

2.1 SOFTWARE (S/W) SUPPORT SERVICES (S/WSS)

2.1.1 The Contractor shall provide software support services (S/WSS) to the AN/AVR-2B(V) program as directed by the USG. The contractor shall provide S/WSS to the AN/AVR-2B(V) program to change the AN/AVR-2B(V) software baseline if needed as a result of a hardware obsolescence replacement solution. Upon the SEC’s approval via the KO to develop a hardware replacement, the following sub tasks will be performed as indicated below:

2.1.1.1 Perform requirement and software system analysis for the AN/AVR-2B(V) software baseline and the on-Aircraft Flight Test software. The software/firmware change request IAW contract data requirements list (CDRL) B001, DI-MISC-81807, shall describe the necessary software changes (e.g., interface, algorithm or performance) needed to support a change to the hardware due to hardware obsolescence and estimated cost of the software changes).

2.1.1.1(a) Standard: All changes due to hardware obsolescence shall be evaluated for potential software impacts.

2.3.1.1(b) Acceptance Quality Level (AQL): 100% compliant

2.1.1.2 Upon approval from SEC via KO of software changes, the contractor shall perform software design, development and unit testing to deliver those changes to the AN/AVR-2B(V) SW baseline and/or the on-Aircraft Flight Test software. The deliverable shall consist of software installation plan package CDRL B002, DI-IPSC-81428A, with instructions on how to perform the installation (unless already accurately described in previously delivered documentation) and any on-Aircraft system test procedures.

2.1.1.2(a) Standard: For Government approved engineering change proposals (ECPs) requiring a change that addresses the approved requirement and software system analysis impact report(s) the contractor shal deliver an updated baseline that meets the requirements of section 2.3.1.2 and is free of category 1 or 2 level defects. Category 1 and 2 level defects are defined in attachment 4, categorization of software anomalies/problems policy, SEC-SS- Policy-001-V02.

2.1.1.2(b) AQL: 100% compliant

2.1.1.3 The contractor will produce documentation changes/maintenance manual changes IAW CDRL B003, DI-TMSS-81666B, for any SEC via KO approved requirement that included changes to user or maintainer documentation.

2.1.1.3(a) Standard: Deliver required documentation changes in electronic format.

2.1.1.3(b) AQL: 100% compliant

2.1.1.4 The contractor will either produce updates to the following CDRLs or document that the software change did not impact or alter the Government furnished information(GFI) version of the CDRL.

2.1.1.4(a) Software safety program plan CDRL B004 DI-SAFT-81626 2.1.1.4(b) Software development plan CDRL B005 DI-IPSC-81427B 2.1.1.4(c) Software safety critical function analysis matrix with associated hazard risk index report CDRL B006, DI-MISC-80711A 2.1.1.4(d) Software design description CDRL B007, DI-IPSC-81435B 2.1.1.4(e) Software requirements specification CDRL B008, DI-IPSC-81433A 2.1.1.4(f) Software interface requirements specification CDRL B009, DI-IPSC-81428B 2.1.1.4(g) System/subsystem requirements trace matrix to the SDD CDRL B0010, DI-IPSC- 81283 2.1.1.4(h) Software test plan CDRL B0011, DI-IPSC-81438A 2.1.1.4(i) Software test description CDRL B0012, DI-IPSC-81439 2.1.1.4(j) Software test report CDRL B0013, DI-IPSC-81440 2.1.1.4(k) Software failure modes effects and criticality analysis CDRL B0014, DI-SESS- 81495B, Part 3 Deliverables

3.0 Contract Data Requirements Lists (CDRLS) DD Form 1423

The contractor shall prepare and deliver documentation IAW the CDRLs in section J of the contract entitled “list of attachments.” The services CDRLs is referenced in appendix B in paragraph 5.1. Complete CDRL listing is shown in attachment 3 of this PWS.

3.1 CONTRACTOR MANPOWER REPORTING(CMR)

3.1.1 Contract manpower reporting: The contractor shall report manpower data (including contractor labor hours, subcontractor labor hours) relating to the performance of services contracts into the system for award management, https://www.sam.gov consistent with existing contract reporting requirements under the federal acquisition regulation (FAR) that is currently applicable only to federal civilian agencies. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2024. Contractors may direct questions to the help desk at help desk at: https://www.sam.gov.

The required information includes:

3.1.1.1 Contracting office, KO, Contracting officer's technical representative (COTR)

3.1.1.2 Contract number, including task and delivery order number

3.1.1.3 Beginning and ending dates covered by reporting period

3.1.1.4 Contractor name, address, phone number, e-mail address, identity of contractor employee entering data

3.1.1.5 Estimated direct labor hours (including sub-contractors)

3.1.1.6 Estimated direct labor dollars paid this reporting period (including sub-contractors)

3.1.1.7 Total payments (including sub-contractors)

3.1.1.8 Predominant federal service code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different)

3.1.1.9 Estimated data collection cost

3.1.1.10 Organizational title associated with the unit identification code (UIC) for the Army requiring activity (the Army requiring activity is responsible for providing the contractor with its UIC for the purposes of reporting this information)

3.1.1.11 Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website)

3.1.1.12 Presence of deployment or contingency contract language

3.1.1.13 Number of contractor and sub-contractor employees deployed in theater this reporting period (by country)

Part 4

Applicable Documents

4.0 Government and Industrial Documents

The following documents (or latest revisions thereof) are required for the performance of this effort and applicability to the PWS requirements herein are referenced below and shall comply with the most current version of referenced documents:

4.1 GOVERNMENT DOCUMENTS

4.1.1 Department of Defense Specifications

Document Identification Title Date https://www.sam.gov/ https://www.sam.gov/

Defense Federal Acquistion Regulations Supplement (DFARS) 252.232-7006

Wide Area Workflow Payment Instructions

05 November 2005

Defense Federal Acquistion Regulations Supplement (DFARS) 252.211-7006

Radio Frequency Identification

(RFID)

07 February 2001

4.1.2 Department of Defense Standards

MIL-HDBK-61A Configuration Management 03 October 2015

MIL-STD-38784(1)

Notice 2

Standard Practice for Manuals,Technical:

Gen Style & Format Requirement

01 December 2000

MIL-STD-130M Identification Marking of U.S. Mil Property 02 December 2005 MIL-STD-129R Military Marking for Shipment and Storage 29 October 2004 MIL-STD- 2073-1E Standard Practice for Military Packaging 09 July 2018 MIL-STD-3046 Defense Interim Std Practice – Configuration

Management 03 June 2013

DLAI 4140.55 Reporting of Supply Discrepancies 21 January 1999 DoD 8570.01 Baseline Certifications 02 November 2014

4.1.3 Other Government Documents

Signed Memo Security Classification Guide (SCG) ASE

Family of Systems 04 February 2014

DoD 4100.39-M FLIS Procedures Manual 28 February 1985 DoD 5220.22-M National Industrial Security Program Operating

Manual 28 February 2006

SP L31-0034, Rev. B AN/AVR-2B(V) LDS Performance Specification 12 October 2004 TM-11-5865-1032-13NP Operator and Field Maintenance Manual 01 February 2012 CM Plan AN/AVR-2B(V) LDS Configuration Mgmt. Plan 13 December 2006 DD 254 Package Contract Security Classification Specification 01 April 2018 Acq Plan Acquisition Strategy Plan for AN/AVR-2B(V) 17 February 2012

4.1.4 Industrial Document

ISO 9001:2015 Quality Management Standard 01 December 2015

Part 5 Appendixes and Attachment Listing

5.0 Appendixes

5.1 APPENDIX LISTING

5.1.1 Appendix A- AN/AVR-2B(V) Summary Configuration Matrix

LDS LRU DESCRIPTION AN/AVR-2B(V)1 AN/AVR-2B(V)2

National Stock Number (NSN) 5865-01-515-0444 5865-01-515-0458 CM-493B Signal Comparator Module 1 1 SU-130B Sensor Unit 4 6 Electronic Key Management System 1 1

5.1.2 Appendix B- Contract Data Requirements List (CDRL)

CDRL

Number

DID Reference Number

Data Item Title PWS Paragraphs

A009 DI-MGMT-80441D TAV-C Monthly Report 1.6.4.1 A011 DI-ADMN-81249C Conference Agenda 1.5.3 A012 DI-ADMN-81250C Conference Minutes 1.5.3 B001 DI-MISC-81807 S/W Firmware Change Request 2.1.1.1 B002 DI-IPSC-81428A S/W Installation Plan 2.1.1.2 B003 DI-TMSS-81666B S/W Maintenance Manual Changes 2.1.1.3 B004 DI-SAFT-81626 S/W Safety Program Plan 2.1.1.4(a) B005 DI-IPSC-81427B S/W Development Plan 2.1.1.4(b) B006 DI-MISC-80711A S/W Safety Critical Function Analysis 2.1.1.4(c) B007 DI-IPSC-81435B S/W Design Description (SDD) 2.1.1.4(d) B008 DI-IPSC-81433A S/W Requirements Specification 2.1.1.4(e) B009 DI-IPSC-81428B S/W Interface Requirements Specs 2.1.1.4(f) B0010 DI-IPSC-81283 S/W System/Sub-system

Requirements Trace Matrix 2.1.1.4(g)

B0011 DI-IPSC-81438A S/W Test Plan 2.1.1.4(h) B0012 DI-IPSC-81439 S/W Test Description 2.1.1.4(i) B0013 DI-IPSC-81440 S/W Test Report 2.1.1.4(j) B0014 DI-SESS-81495B S/W Failure Modes, Effects &

Criticality Analysis 2.1.1.4(k)

5.1.3 Appendix C- Estimated Engineering Software Services Workload

Year Oct 2023 Sep2027

Engineering Software Services Direct Labor Hours

Base Period Software Engineering Support 1824 Base Period 2 Software Engineering Support 1824 Base Period 3 Software Engineering Support 1824 Base Period 4 Software Engineering Support 1824 Base Period 5 Software Engineering Support 1824

Total 9120

5.1.4 Appendix D- Place of Performance for Services

Engineering Requirement PWS

Paragraph Place of Performance

Software Services Support

2.1.1 through 2.1.1.4(k)

Contractor’s Facilities at Danbury, Tobyhanna Army Depot and other CONUS and OCONUS sites as needed

5.1.5 Appendix E- Government Furnished Property (GFP)/ Government Furnished Equipment

(GFE)

Project Name

Equip #

(UID)

Property Control Tag

Nomenclature Mfg. Name Model # Serial Number

AVR-2B 04793 000000026189 NOTEBOOK

PANASONIC

TOUGHBOOK 29

PANASONIC NONE 4JKSA60972

AVR-2B 05751 000000030708 TEST ADAPTER,

RADAR SET

UTAS-ISR-

DANBURY

MX9848A/APR-

39(V)

313AA

AVR-2B GP00173 000000037698 TEST ADAPTER,

RADAR SET

NORTHROP

GRUMMAN

MX9848A/APR-

39(V)

317AA

AVR-2B GP00174 000000037707 TEST ADAPTER,

RADAR SET

NORTHROP

GRUMMAN

MX9848A/APR-

39(V)

94AA

AVR-2B GP00175 000000037697 TEST ADAPTER,

RADAR SET

NORTHROP

GRUMMAN

MX9848A/APR-

39(V)

076AA

AVR-2B 000000037701 000000037701 RADAR DATA

PROCESSOR

NONE CP-1597B/APR

39A(V)

281AA

5.2 ATTACHMENTS

5.2.1 Attachment Listing

Attachment Number Attachment Description 1 Government Furnished Property/Equipment (GFP/GFE) 2 AT-OPSEC Appendix to PWS

3 Contract Data Requirements Lists (CDRLs) DD Form 1423 4 Categorization of Software Anomalies/Problems Policy, SEC-SS-

Policy-001-V02.

PART 6

DEFINITIONS & ACRONYMS

6. Definitions and Acronyms

6.1 Definitions: Although not inclusive of every term used within this PWS, the following provides a list of definitions used throughout this PWS and commonly used in the acquisition field.

Contracting Officer – means a person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

Contracting Officer's Representative (COR) – As defined in DFARS 202.101, means an individual designated and authorized in writing by the Contracting Officer to perform specific technical or administrative functions. DoD Instruction (DoDI) 5000.72, Part II Definitions states the following when defining a COR: “Defined in subpart 202.101 of Reference (f). Any individual delegated responsibilities pursuant to subpart 1.602-2 of Reference (e), regardless of local terminology, must be certified in accordance with this instruction. For example, local terminology can be COR, Contracting Officer’s technical representative, technical point of contact, technical representative, alternate COR, administrative COR, assistant COR, line item manager, task order manager, quality assurance personnel, quality assurance evaluator, or COR management.” In addition, Army Regulation 70-13, Chapter 2, paragraph 2-2g, states, in part, the following when providing other surveillance support personnel to assist the COR when needed, “…These other surveillance support personnel may serve as on-site representatives of the COR in performance of actual contract surveillance if they meet all COR requirements and have been appointed by the Contracting Officer as alternate CORs.”

Contractor – means a supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

Contractor-acquired Property - means property acquired, fabricated, or otherwise provided by the Contractor for performing a contract and to which the Government has title.

Day – means, unless otherwise specified, a calendar day.

Defective Service – means a service output that does not meet the standard of performance associated with the Performance Work Statement.

Deliverable – means anything that can be physically delivered but may include non-manufactured things such as meeting minutes or reports.

Government-Furnished Property – As reflected in FAR 52.245-1, Government-furnished Property “means property in the possession of, or directly acquired by, the Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes Contractor-acquired property if the Contractor-acquired property is a deliverable under a cost contract when accepted by the Government for continued use under the contract

Government Property - means all property owned or leased by the Government. Government property includes both Government-furnished and Contractor-acquired property. Government property includes material, equipment, special tooling, special test equipment, and real property. Government property does not include intellectual property and software.

Property Administrator - means an authorized representative of the Contracting Officer appointed in accordance with agency procedures, responsible for administering the contract requirements and obligations relating to Government property in the possession of a Contractor.

High Level Objective (HLO) – means a key overarching result-based objective for a project necessary to achieve the project’s vision. HLOs are similar to Level 2 in a Work Breakdown Structure. Each HLO may contain several statements to flesh out the areas necessary to meet the objective.

Physical Security – means that part of security concerned with physical measures designed to safeguard personnel; to prevent unauthorized access to equipment, installations, material, and documents; and to safeguard against espionage, sabotage, damage, and theft.

Quality Assurance – (or Government contract quality assurance) means the various functions, including, inspection, performed by the Government to determine whether a Contractor has fulfilled the contract obligations pertaining to quality and quantity.

Quality Assurance Surveillance Plan (QASP) – means the key Government-developed surveillance process document and is applied to Performance-Based Service Contracting (PBSC). The QASP is used for managing Contractor performance assessment by ensuring that systematic quality assurance methods validate that Contractor quality control efforts are timely, effective, and are delivering the results specified in the contract or task order. The QASP directly corresponds to the performance objectives and standards (i.e., quality, quantity, timeliness) specified in the Performance Work Statement (PWS). It provides specific details on how the Government will survey, observe, test, sample, evaluate, and document Contractor performance results to determine if the Contractor has met the required standards for each objective in the PWS. The QASP, with very few if any exceptions, is an internal to Government document.

Quality Control – means all necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

Statement – means the specific results-based activities required to satisfy HLOs. A statement contains a result, the context of the statement, and the required action(s). Statements focus on “what” is to be accomplished; however, they are not prescriptive in describing “how” the outcome is to be achieved. Each HLO may have several statements to flesh out the areas necessary to meet the objective. Statements are similar to Level 3 in a Work Breakdown Structure.

Subcontractor – means one that enters into a contract with a prime Contractor. The Government does not have privity of contract with the Subcontractor.

Work Day - The number of hours per day the Contractor provides services in accordance with the contract.

Work Week - Monday through Friday, unless otherwise specified.

6.2 Acronyms: Although not inclusive of every term used within this PWS, or that may be included in an acquisition, the following provides a list of acronyms commonly used in the acquisition field.

ACO Administrative Contracting Officer ACOR Alternate Contracting Officer's Representative AE Army in Europe AFARS Army Federal Acquisition Regulation Supplement AHA Activity Hazard Analysis AMC Army Materiel Command AOR Area of Responsibility AQL Acceptable Quality Level AR Army Regulation ASE Aircraft Survivability Equipment AT Anti-terrorism ATCTS Army Training Certification Tracking System ATP Acceptance Test Procedures BIT Built-In Test CAC Common Access Card CB Configuration Baseline

CCB Configuration Control Board CCDR Contract Cost Data Report CCE Contracting Center of Excellence CDRL Contract Data Requirements List CECOM Communications-Electronics Command CFE Conventional Forces Europe CFR Code of Federal Regulations CLS Contractor Logistics Support CM Configuration Management CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer’s Representative COTS Commercial-Off-the-Shelf CPM Contractor Program Manager CPFF Cost Plus Fixed Fee CRM Contracting Representative Manager CSS Contractor Support Services CWBS Contract Work Breakdown Structure DA Department of the Army DCMA Defense Contract Management Agency DD250 Department of Defense Form 250 (Receiving Report) DD254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DID Data Item Description DMDC Defense Manpower Data Center DMS Diminishing Manufacturing Sources DMSMS Diminishing Manufacturing Sources Material Shortages DMT Danbury Mission Technologies DO Delivery Order DoD Department of Defense ECP Engineering Change Proposal ESS Engineering Support Services FAR Federal Acquisition Regulation FFP Firm-Fixed Price FMECA Failure Modes Effects and Criticality Analysis FOUO For Official Use Only FRG Federal Republic of Germany GFE Government Furnished Equipment GFI Government Furnished Information GFP Government Furnished Property HLO High Level Objective HIPAA Health Insurance Portability and Accountability Act of 1996 IA Information Awareness IAC Installation Access Control IACO Installation Access Control Office IAW In Accordance With ID Identification

IGCE Independent Government Cost Estimate IEWS Intelligence Electronic Warfare & Sensors ILS Integrated Logistics Support ILSC Integrated Logistics Support Centre IPT Integrated Product Teams ISO International Organization for Standardization IT Information Technology JTR Joint Travel Regulation JPAS Joint Personnel Adjudication System KO Contracting Officer LDS Laser Detecting Set LRU Line Replaceable Unit MIL-STD Military Standard NRE Non-RecurringEngineering OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs OPSEC Operations Security PA Property Administrator PCO Procurement Contracting Officer PIEE Procurement Integrated Enterprise Environment PII Personally Identifiable Information PIPO Phase In/Phase Out PMO Product Management Office PM Program Manager POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program QIPR Quarterly Integrated Program Review RA Requiring Activity RCO Regional Contracting Office RFID Radio Frequency Identification ROM Rough Order of Magnitude SCG Security Classification Guide SEC Software Engineering Centre SIGE Safety and Health Protection Plan SIPRNet Secret Internet Protocol Router Network SOO Statement of Objective SOW Statement of Work SRU Shop Replaceable Unit SWAP Space, weight and power

TDP Technical Data Package TE Technical Exhibit TEP Task Execution Plan TSP Training Support Package UID Unique Identifier USAG United States Army Garrison USG United States Government USAREUR United States Army Europe UOM Unit of Measure VECP Value Engineering Change Proposal WBS Work Breakdown Structure