Exhibit A - Technical Requirements Document (TRD).pdf

Exhibit A PANAPG-26-P-0000 036818 Page 1 of 24

Issue: 07/09/2026

Version: 12 May 2023

TECHNICAL REQUIREMENTS

Mounted Family of Computer Systems (MFoCS) Block II Line Replaceable Units (LRU)

For

Joint Battle Command – Platform (JBC-P)

TABLE OF CONTENTS

CONFIGURATION BASELINE

Obsolescence Management Requirements / Obsolete Components and Materials / DMSMS

Definitions

DMSMS Management Program

Design Changes

Subcontractor Management

DMSMS Costs

DMSMS Contract Data Requirement List

Part Revisions

CHEMICAL AGENT RESISTANT COATING (CARC)

Paint Colors

Special Instructions

PACKAGING

Wood Packing Material

Military Packaging ............................................................................................. Error! Bookmark not defined.

SPECIALIZED TESTING..................................................................................... Error! Bookmark not defined.

TOTAL ASSET VISIBILITY-CONTRACTOR (TAV-C) ................................... Error! Bookmark not defined.

CONTRACT SECURITY REQUIREMENTS

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL List

Individual CDRLs

APPLICABLE DOCUMENTS

Military and Federal Standards

MIL-STD-129R(3) Military Marking for Shipment and Storage (25 Feb 2023)

MIL-STD-810H Environmental Engineering Considerations and Laboratory Tests

MIL-STD-2073-1E(4) Not 1 Standard Practice for Military Packaging (27 Jun 2024)

Military and Federal

Specifications

MIL-E-5400 General Spec for Electronic Equipment, Aerospace

MIL-HDBK-61A Configuration Management Guidance (Dated 7 Feb 2001)

Other Documents

PMMC-MFOCSII-0001_V1.1 MFoCS Block II Performance Spec

ISPM 15 Regulation of Wood Packaging Material in International Trade

(1 Apr 2009)

Commercial Documents

SAE EIA-649-1 Configuration Management Requirements for Defense Contracts

Security Documents

AR 381-12 Counterintelligence Awareness and Reporting

CONFIGURATION BASELINE

The applicable Configuration Baselines (CB), for the listed Configuration Item (CI) and/or Computer Software

Configuration Item (CSCI), are as listed in the table below.

NSN Nomenclature Part Numbers/Drawings

7025-01-623-5349 KEYBOARD, DATA ENTRY 9800-96830-0000

7021-01-718-8614 COMPUTER, DIGITAL (Block II V2 w/ MGUE) 9800-98600-6000

7021-01-737-4372 COMPUTER, DIGITAL 9800-98000-6000

7025-01-675-8118 DISPLAY UNIT (Block II) 9800-99120-0000

7025-01-677-7680 DISPLAY UNIT 9800-99210-0000

7035-01-675-7998 DOCKING STATION 9800-99300-5000

Commented [ZP1]: Will update table at the end

Commented [MT2]: -5349: SSPCL indicates 9800-96810-0000.

Commented [ZP3R2]: 96810 has been replaced by 96830

Each CI/CSCI, as developed/built and delivered, shall conform to the cited CB and (if applicable) all subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO). The

Contractor shall establish a Configuration Management Program in accordance with SAE EIA-649-1.

No changes or departures from the CB are acceptable except for changes or departures which are submitted in accordance with EIA-649-1, CDRL A001, and CDRL B001, and are approved by the Government

Configuration Manager (C Mgr.) or Configuration Management Officer (CMO) and which are made applicable to the contract by the PCO.

An Engineering Change Proposal (ECP) describes the changes to be made to the CI/CSCI and all associated

Government documents and data that are affected by the proposed engineering change. An ECP should be prepared in accordance with EIA-649-1, CDRL A001, and DI-SESS-80639E.

A Request For Variance (RFV) is a specific written authorization to depart from a particular requirement(s) of an item’s approved configuration documentation for a specific number of units or a specified period of time, either as an advance request or after the fact. The contractor shall identify the impact of the RFV on performance, operational readiness and logistics support of the affected CIs. The Government may require consideration for any RFV. RFV should be prepared in accordance with EIA-649-1, CDRL B001, and DI-

SESS-80640E.

Contractor shall provide all supporting program or cost data with the Configuration Control Documents. The contractor shall uniquely and sequentially identify (including the use of the contract number) each ECP or RFV.

The identification number should use less than 16 characters.

Obsolescence Management Requirements / Obsolete Components and Materials / DMSMS

Definitions.

For the purpose of this part –

An “Approved Item” is the resolution of an obsolescence issue by the use of items already approved for use on the drawing (e.g., an approved alternate part already on a specification control drawing). The use of an approved item does not require configuration management approval or the establishment of a DMSMS

Management Case.

“Backorder Avoidance” is an estimate of the number of supply system backorders for the next higher assembly

(NHA) which would be avoided by resolving the case proactively. Backorder Avoidance is defined as the user demand for the NHA that would not have been filled as a result of the time spent resolving the issue had the issue been discovered reactively (i.e., the commencement of a contractual procurement or repair action).

A “Bill of Materials (BOM)” is a list of the items, including but not limited to: raw materials, sub-assemblies, intermediate assemblies, sub-components, parts, chemicals, software (SW), and the quantities of each needed to produce an end product. The BOM may include additional information that allows the user to determine the precise location of an item within an end product. A DMSMS BOM is limited to just those items selected for comprehensive monitoring by the DMSMS program.

A “Bridge Buy” is a subset of the “Life of Need Buy” resolution type where only the quantity of items needed until the next redesign event involving the item is procured. This is also done for Commercial Item assemblies to satisfy requirements while a replacement commercial item is being integrated into the weapon system

(including qualification).

“Case Resolution Time” is the cumulative time from when a DMSMS case is opened until it is closed, less any time spent in Hold status.

“Commercial item” and “commercially available off-the-shelf (COTS) item” are items that meet their respective definitions in FAR Part 2.101 – Definitions.

A “Complex Substitute” is the resolution of an Obsolescence Issue by the use of a replacement item that has different specifications which need to be researched and validated but requires no modification of the Next

Higher Assembly (NHA). The use of a complex substitute requires configuration management approval and the establishment of a DMSMS Management Case.

“Cost Avoidance” is the difference between the cost of the government approved proactive DMSMS Case resolution and the estimated cost of case resolution should the DMSMS issue have been discovered reactively

(i.e., the commencement of a contractual procurement or repair action). Note that this definition shall be used in lieu of the definitions in SD-22.

“Diminishing Manufacturing Sources and Material Shortages (DMSMS)” is the loss, or impending loss, of qualified source(s), manufacturers, or suppliers that may impact the production or sustainment of an item or system.

A “DMSMS Alert” is a record of government notification of a pending DMSMS Issue. An Open DMSMS Alert is one for which a DMSMS Case has not yet been established.

“DMSMS Backorders Avoided” is the number of backorders which would have occurred had the issue been discovered reactively caused by the delay in production resulting from the need to resolve the issue before commencing production. This can be approximated when using Just-in-Time supply chain management systems as the reactive resolution Case Resolution Time multiplied and the NHA NSN average monthly demand.

“DMSMS Cost Avoidance” is the cost difference between the proactive DMSMS resolution chosen and the cost the resolution which would have been likely adopted had the issue been discovered reactively.

“DMSMS Issues” are problems related to shortages or projected shortages of items caused by obsolescence or the loss of qualified manufacturers or suppliers of items. DMSSMS issues are further classified as:

“Documented DMSMS Issues” are DMSMS Issues for which there is documentation advising that an item is unavailable or will be unavailable at a specific date in the future. Documented DMSMS Issues tend to identify issues for which the Years to End of Life (YTEOL) is typically one year or less and rarely in excess of two years. A “Not Recommended for New Design” designation shall not be considered a Documented DMSMS Issue.

“Predicted DMSMS Issues” are DMSMS Issues predicted to occur that have been identified by analysis of the item, its technology and market forces affecting the future availability of this item. A number of vendors exist in the private sector with tools capable of predicting DMSMS issues beyond 2 years to as much as 10 years.

A “Reactive DMSMS Issue” is a DMSMS Issue which was not identified until the commencement of a current procurement or production action for the item or a higher assembly for which the item is a component.

A “DMSMS Management Case” is a project established to analyze and resolve DMSMS Issues.

DMSMS Management Case “Status”:

Open – The status of a case being actively worked prior to a recommended solution being approved.

Hold – An unresolved open case where active case management efforts have been suspended, typically because the issue resolution does not require immediate action. Cases in “Hold” status should continue to be monitored to ensure that this status remains warranted.

Resolved – The status of a case after a recommended solution is approved, and implementation has commenced.

Closed – The solution has been fully implemented.

“DMSMS Impact” is the negative effect of a DMSMS Issue on the ability to produce and/or support an item and/or its higher assemblies during its planned service life.

The “DMSMS Planning Horizon” is a continuously moving future period of time during which the items on the

DMSMS BOM are monitored for availability and if its discontinuance is identified or predicted to occur during this period, the discontinuance is documented as DMSMS Alert.

A “DMSMS Roadmap” is a data visualization tool, depicting the health of the product's as-sustained configuration that will be used to identify, manage, and plan for the resolution of DMSMS Issues at the sub-system or assembly level to include software.

“End of Life” is the last date for which the item can be purchased. In the case of software, it represents the last day a software license is available for purchase.

“End of Support” is the last date for which software support is provided by the software licensor and occurs when either software updates or technical support ends.

“Firmware” is software contained on Non-Volatile Memory (NMV) for which updates occur via either the replacement of the NVM component or by replacement of an assembly containing the NVM component.

Software on NVM components which is updated by any other means shall not be considered Firmware.

The “Impact Date” is the estimated date by which a case must be closed to prevent an adverse impact. The

“Impact Date” is synonymous with “Date Implementation Needed Date,” in DI-MGMT-82275A.

“Item” means any part, assembly, software, material, chemical, etc., used in the manufacture, assembly, or operation of deliverables of this contract.

A “Life of Need Buy (LON Buy or LONB)” is the purchase of a sufficient quantity of the item to sustain the product until a planned redesign or the discontinuance of the host assembly. When the purchase quantity is only enough until the next redesign, this is sometimes referred to as a “Bridge Buy.”

“Non-Development Items (NDI)” shall be as defined in the FAR Part 2.101 – Definitions. Privately developed

NDI which do meet the FAR definition of a commercial item are considered commercial items.

“Obsolescence” is the condition when a needed item is out of production.

An item is “Obsolete” where the exact part number has no available manufacturing sources.

The “Original Component Manufacturer (OCM)” is the organization responsible for the component design, specification, and its production.

The “Original Equipment Manufacturer (OEM)” is the organization responsible for the equipment design, specification, and its production.

The “Obsolescence Working Group (OWG)” is a joint contractor – government working group which meets periodically during the course of the contract to discuss DMSMS management matters relevant to the contract.

A “Simple Substitute” is the resolution of a DMSMS Issue by its replacement with an existing item that meets all the items Form, Fit & Function (F3) requirements and does not require modification to either the item or its

NHA but has not yet been approved by the design approving authority. Simple substitutes typically require only minimal qualification. The use of a simple substitute requires configuration management approval and the establishment of a DMSMS management case.

“Standard Parts” or “Commonly Used Parts” are those parts identified in the contractor’s Parts Management or

Parts Selection processes as preferred for use by their design engineers. These parts are typically documented on Preferred Parts List (PPL) or equal.

“Subcontractor” is a person or entity to which the prime Contractor has delegated part or all of its obligations.

Note that by this definition, most suppliers will not be considered “Subcontractors”, and as such, would not be automatically subject to the flow down of DMSMS program requirements.

“Technology Insertion” is a defined programmatic system management strategy to redesign an LRU or subsystem to provide new capability or improved performance to the weapon system.

“Technology Refreshment” is a defined programmatic system management strategy to replace the electronics

(including software/firmware) in a system over a specific period of time, usually with the goal of resolving multiple DMSMS issues or to prevent the occurrence of DMSMS Issues preemptively by upgrading the technology of the design. From a DMSMS perspective, Technology Refreshment events should be planned to coincide with Technology Insertion events whenever possible.

DMSMS Management Program

For the weapon system or items on contract, the Contractor shall establish and execute a proactive DMSMS management program in accordance with (IAW) this Technical Requirements Document (TRD) for the period of performance of this contract. The Government’s objective in this program is to efficiently and effectively identify and report DMSMS issues.

The program shall include processes or procedures to identify or predict DMSMS issues over a minimum five-year planning horizon, assess risk and develop obsolescence mitigation strategies to determine the most cost effective solution to DMSMS issues. The program shall also include processes and procedures for selecting standard or commonly available parts and parts with more than one source of supply and with at least five (5) years to the end of life (YTEOL).

Commented [ZP4]: Just monitor, and reporting

Commented [ZP5]: Contractor traveled for the PM, should we add section for travel? How should we handle PMR meetings and such?

Commented [LH6R5]: Contract cannot have services involved at all.

DMSMS Life Cycle Management Data

On this contract, the contractor shall record DMSMS activity using DI-MGMT-82274, DMSMS Life Cycle

Management Data as required below. The data will be an indentured spreadsheet keyed to the parts selected for proactive monitoring (i.e., DMSMS BOM) with DMSMS Alert and Case Management data added to the spreadsheet as they become available during the contract.

DMSMS BOM Establishment

For each item on this contract, the contractor shall deliver to the government an indentured DMSMS BOM IAW the CDRL for DI-MGMT-82274; DMSMS Life Cycle Management Data: BOM/Alerts/Case Mgmt. Reports

(CDRL C001).

If a DMSMS BOM has already been established as part of a government required DMSMS management program on a previous contract, it may be used. If not, the BOM shall include all electronic, electrical and electromechanical (EEE) components, all commercial SW and all commercial assemblies on the item. Each part on the BOM shall include both the OEM part number (P/N) and the OCM P/N & CAGE code. If multiple OCM parts are approved for use in production to meet the requirements of a single OEM part number (e.g., on a specification control or source control drawing), they shall each be individually listed in the DMSMS BOM.

In the special case of Commercial Items and privately developed items which meet the FAR definition of a

Commercial Item, the contractor shall identify these items as a single line BOM entry with a part number which definitively describes the items unique configuration.

In the case of items developed exclusively at private expense, which do not meet the FAR definition of a commercial item, the BOM shall include all EEE components.

Commercial SW may also be represented on the BOM as a single line entry identified by a definitive part/version number and owner/vendor.

Firmware shall not be separately represented on the BOM but considered part of NVM component or the commercial assembly on which the firmware resides.

The contractor shall ensure that the DMSMS BOM delivered accurately reflects the current approved design

IAW the contractor’s configuration management procedures.

DMSMS BOM Monitoring

Once the DMSMS BOM is established, the contractor shall monitor the BOM to identify or predict any item on the BOM which may become unavailable over the 5-year DMSMS planning horizon. The frequency of the monitoring effort shall be at a rate sufficient to identify and resolve DMSMS Issues for that item to minimize adverse impact on this contract. When an item on the BOM is identified as having a DMSMS Issue, the contractor shall record the issue as a DMSMS Alert IAW the CDRL for DI-MGMT-82274; DMSMS Life Cycle

Management Data, BOM/Alerts/Case Management Reports (CDRL C001). If an identified issue is forecast to occur with the next 24 months, the contractor shall also advise the PCO of this issue in writing within 5 working days of its discovery.

Reactive DMSMS Issues

If the contractor discovers that an item not on the DMSMS BOM has a DMSMS Issue, they should promptly notify the PCO within 5 working days of discovery. The item for which the Reactive DMSMS Issues has been identified shall also be added to the DMSMS BOM.

Design Changes

Design changes shall be made in accordance with the Configuration Management requirements of this contract.

Subcontractor Management.

The Contractor shall ensure that its Subcontractors (see Subcontractor definition) adhere to the

DMSMS/Obsolescence requirements of this TRD.

DMSMS Costs

The Contractor shall be responsible for all costs associated with mitigating DMSMS Issues, including:

- Monitoring parts, material and software availability;

- Locating alternate/substitute parts and/or material and software;

- Vendor interface and communication;

DMSMS Contract Data Requirement List

Refer to the applicable Contract Data Requirement Lists (CDRLs).

Part Revisions

Each CI, as developed/built and delivered, shall conform to the cited CB and (if applicable) all subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO). Configuration changes not directly affecting the configuration baseline do not require Government approval prior to incorporation but must be documented by the contractor and shall be made available to the Government upon request.

CHEMICAL AGENT RESISTANT COATING (CARC)

Paint Colors

X =

Applicable Location Color

Color No.

FED-STD 595

Exterior – Lusterless Green Green 383 34094

Exterior – Camouflage – Desert Colors Green 383 34094

Black 37030

Tan 686A 33446

Green 24533

Brown 383 30051

White 27875

Interior Shelter Surfaces Green 24533

(White or Green) White 27875

Other: Area enclosed by dotted line Green (Olive

Drab)

34087

Special Instructions

X =

Applicable Location or Part Instruction

Antenna Elements, including protective covers, i.e. fiberglass shields.

Non-Applicable

Part that conforms to a Government requirement.

Finish as required by the individual part requirement.

Parts subject to temperatures in excess of 400 degrees F (205 degrees C).

Paint with heat resistant paint.

Parts which can be flexed. Do not paint with CARC.

CARC Marking Stencil “CARC” in CARC paint in close proximity to the nameplate using a contrasting color, or use plates or embossed lettering.

Marking shall be durable enough to withstand all environmental conditions during field use.

Commented [ZP7]: Engr thinks this section does not apply to our contract, consider removing this section.

Gov’t doesn’t own the TDP.

Commented [T(8R7]: I believe call-out for CARC & color is contained within MFoCS TDP which is proprietary to DRS Corp. I believe Tan 686A is called-out for the several DRS P/Ns in this contract.

Commented [LH9R7]: This section is good to keep - DRS will provide their required CARC/colors if that is listed in their TDP. If what we have on this chart is accurate then it is good to go per KS.

PACKAGING

Wood Packing Material

Wood Packaging Material in compliance with ISPM-15, Regulation of Wood Packaging Material in International Trade, is applicable.

Wood packing material includes pallets. See DLAD T/Q Requirement RP001 DLA Packaging Requirements for Procurement, which includes requirements for treatment of wood packaging material.

Military Packaging

DS7029 and/or DS7033 Preservation, Packing and Marking Instructions

Military packaging in accordance with MIL-STD-2073-1 is applicable.

DS7029 - DS7033 LEGEND

Qty Quantity

Prot Req Protection Required

PKG-REF Packaging Reference (Military/Federal Specification or Standard)

SPI Special Packaging Instruction

LPK Level of Packing

QUP Quantity per Unit Pack

ICQ Intermediate Container Quantity

Pkg Reqmt Codes Packaging Requirement Codes when PKG-REF cites MIL-STD-2073

The below codes are for special markings:

PC Project Code

WG Warranty/Guarantee

SL Shelf Life

BC Bar Code

FMS Foreign Military Sales

Commented [ZP10]: Final determination: Military Packaging

DS7029 - DS7033

NSN Prot Req PKG-REF or SPI LPK QUP ICQ

Special

Markings

Pkg J. J J J J J J J J J

Reqmt I. II. III. IV. V. VI. VII. VII.a IX X

Codes (MP) (CD) (PM) (WM) (CD) (CT) (UC) (IC) (PK) (SM)

7025-01-623-5349 Military MIL-STD-2073-1E B 1 - *ZZ 1 00 00 NA A ED 00 Q 00 BC

7021-01-718-8614 Military MIL-STD-2073-1E B 1 - 41 1 00 00 NA D ED 00 Q 00 BC

7021-01-737-4372 Military MIL-STD-2073-1E B 1 - 41 1 00 00 NA H ED 00 Q 00 BC

7025-01-675-8118 Military MIL-STD-2073-1E B 1 - 41 1 00 00 NA D ED 00 Q 00 BC

7025-01-677-7680 Military MIL-STD-2073-1E B 1 - 41 1 00 00 NA F ED 00 Q 00 BC

7035-01-675-7998 Military MIL-STD-2073-1E B 1 - 41 1 00 00 NA F ED 00 Q 00 BC

*ZZ = INDIVIDUAL MOP 31 FOR KEYBOARD AND CORD

CONTRACT SECURITY REQUIREMENTS

Per AR 530-1, Operations Security, the contractor employees must complete Level I OPSEC

Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

Controlled Unclassified Information (CUI). Include DFARS clause 252.204-7012, which requires the contractor to comply with NIST 800-171.

Also include DFARS provision 252.204-2019 into solicitations. Acquisition officials should follow procedures outlined in DFARS 204.73 and verify vendors have an adequate NIST SP 800-171 summary assessment score within the Supplier Performance Risk System (within PIEE). If the score doesn't show a medium- or high-level assessment with a score of 110 or better (as described in the "NIST SP 800-171 DoD Assessment

Methodology"), include clause 252.204-7020 and obtain the vendor's "system security plan" and "plan of action" for NIST SP 800-171 verification and assurance by Army security officials.

Security Training. Several training requirements exist for contractor personnel per DoD and Army regulation/ directives. On-site contractors may receive training briefs from the government appointed Security Manager;

however, contracting companies will be required to provide training to offsite contractor employees. Training is tailored to the organization’s requirements as well as local policy. Some examples of Security training provided to integrated/embedded contractors may include, but is not limited to, the following:

• Counterintelligence Awareness and Reporting (CIAR) (required for all contractors with security clearances) - Per AR 381-12 Counterintelligence Awareness and Reporting (CIAR), cleared contractor employees must receive annual CIAR training by a CI agent or other trainer as specified in 2-4b.

• Initial / Annual Security Orientation: Online training available on Army Training Information System

(ATIS) at https://learn.atis.army.mil. Search for Information Security Program Training.

• Derivative Classification Training: Online training available via CDSE STEP, DoD 5200.01 and memo for Chief Management Officer of the Department of Defense dated 31 January 2019 - annual requirement reference

• DA, AMC, and/or commander directed security stand-downs, e.g., ad-hoc refresher training

In the event of a discrepancy between the signed DD 254 Contract Security Classification Specification, included as an attachment to the solicitation/contract, and the language in this section, the signed DD 254 information shall take precedence.

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

Commented [ZP11]: Leave it to contracting team

Commented [ZP12R11]: Copy standard language from

AT/OPSEC sheet https://learn.atis.army.mil/

CDRL List

CDRL Data

Line No. DID Identification Title

A001 DI-SESS- 80639E Engineering Change Proposal

B001 DI-SESS- 80640E Request for Variance

C001 DI-MGMT- 82274 DMSMS Life Cycle Management Data - DMSMS

BOM/Alerts/Case Management Reports

D001 DI-MGMT- 80227 Contractor’s Progress Status and Management Report -

Contract Status Report (CSR)

E001 DI-MGMT- 81466A Contract Performance Report - Contract Financial Report

F001 DI-MISC- 80711A Scientific and Technical Reports - System Security Plan

G001 DI-MGMT- 80555A Program Progress Report - Configuration Control

Documentation (CCD)

H001 DI-SESS- 81639 Warranty Performance Report

Individual CDRLs

Commented [ZP13]: Review CDRL List later

Commented [LH14]: These 2 CDRLs are not listed in Notes to

KO

Commented [LH15R14]: DI-MISC-80711A – Scientific and

Technical Reports – Configuration Control is missing. This CDRL is listed in Notes to KO

Commented [LH16R14]: C001: DI-MGMT-82275A –

Diminishing Manufacturing Sources and Material Shortages (DMSMS) Metrics Data - this CDRL is also missing but listed in notes to KO

Commented [ZP17]: Review CDRLs and include them in body of TRD, or remove if not needed

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Original Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

MFoCS TBA TBD

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE GROUP

A001 Engineering Change Proposal

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-SESS-80639E Exhibit A-Technical

Requirements

AMEL-LCW-NRC

INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

IN

LT

ASREQ See Item 16

b. COPIES

SECT. B

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

N/A

See Item 16 See Item 16 Reg

Repro

16. REMARKS:

The contractor shall prepare and submit an Engineering Change Proposal (ECP) in accordance with the Technical Requirements Document section for Configuration Control when a change to or departure from a contractual baseline document is deemed necessary.

An ECP shall be submitted using the latest revision of DD Form 1692.

The Government will have 30 days to review, accept, and/or comment on the draft submission. The contractor shall incorporate changes into the electronic deliverable within 15 days after receipt of

Government comments. The Government will have 30 days to review, accept, and/or comment on the final submission.

Item 9: The contractor shall apply the following distribution statement to each deliverable:

DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense agencies and their contractors. Reason: Export Controlled. Date of Determination: 11 May 2017. Other requests for this document shall be referred to U. S. Army, CECOM, 6565 Surveillance Loop, C3-322, CMDI

Branch, Aberdeen Proving Ground, MD 21005-1846.

All deliveries shall be in digital format, compatible with Microsoft Office and Adobe Acrobat and delivered by email or via DoD SAFE (Secure Access File Exchange) website (https://safe.apps.mil/) in case the deliveries can't be sent through the email services. Request Code is required for the use of

DoD SAFE. Contact the Government Procuring Contracting Officer (PCO) or Engineer for the

Request Code. Alternative delivery media may be discussed with the Government PCO prior to delivery. The Government personnel listed in the distribution list will receive a copy of the submittal.

Name and electronic address of the Government personnel are specified below:

AMEL-LCW-NRC (Technical POC): JONATHON SALSBURY, jonathon.j.salsbury.ctr@army.mil

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil

Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

ACO: TBA

QAR: TBA

If the CDRL Data Deliverable is priced and is not NSP (Not Separately Priced), then an electronic

DD Form 250 will be required via the Wide Area Workflow website in order for the contractor to receive payment for the data deliverable (see section G of the Contract). E-mail notification is required with any electronic submission.

AMEL-LCW-NRC

PCO

ACO

QAR

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jonathon Salsbury

FCDD-ISE-RCD

Mechanical Engineer

07/23/2026 Alyssa Iadanza

AMEL-LCW-NRS

ILSC Branch Chief

07/23/2026

Commented [ZP18]: Once these POCs are determined, will

DLA update the CDRLs to add in their contacts?

Commented [ZP19]: Since there are 4 POCs listed for our office, should this number be changed to 4?

mailto:jonathon.j.salsbury.ctr@army.mil mailto:alyssa.g.iadanza.civ@army.mil mailto:bryce.t.schweers.civ@army.mil mailto:mandy.l.lockhart.civ@army.mil

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER CMAN

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

MFoCS

B001 Request for Variance Request for Deviation/ Request for

Waiver

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-SESS-80640E Exhibit A-Technical

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

SUBMISSION

a. ADDRESSEE

Draft

Item 4: Contractor may propose alternative format.

Item 12/13: NLT 30 days prior to the deviation of the product/system affected by the proposed change, variance, or modification.

Government requires 14 working days for review and approval. Resubmission only required if changes are made to the Request for Deviation/Waiver.

Item 14: All deliveries shall be in digital format, compatible with Microsoft

Office and Adobe Acrobat and delivered by email or via DoD SAFE (Secure

Access File Exchange) website (https://safe.apps.mil/) in case the deliveries can't be sent through the email services. The Government personnel listed in the distribution list will receive a copy of the submittal. Name and electronic address of the Government personnel are specified below:

AMEL-LCW-NRC (Technical POC): JONATHON SALSBURY, jonathon.j.salsbury.ctr@army.mil

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil

Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

PCO

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jonathon Salsbury

FCDD-ISE-RCD

Mechanical Engineer

07/23/2026 Alyssa Iadanza

AMEL-LCW-NRS

mailto:jonathon.j.salsbury.ctr@army.mil mailto:alyssa.g.iadanza.civ@army.mil mailto:bryce.t.schweers.civ@army.mil mailto:mandy.l.lockhart.civ@army.mil

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER

C001 DMSMS Life Cycle Management Data DMSMS BOM/Alerts/Case

Management Reports

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MGMT-82274 Exhibit A-Technical

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

XX

QUARTERLY See Item 16

SUBMISSION

a. ADDRESSEE

Draft

DMSMS Life Cycle Management Data is a spreadsheet record of the parts being monitored proactively for obsolescence and any DMSMS Alerts or case management data resulting from DMSMS Issues that have been identified on this contract. Should a DMSMS Issue be discovered for a part not being proactively monitored, the part should be added to the BOM and its Alert and Case Management data recorded as applicable.

DMSMS BOM. The DMSMS BOM shall be recorded in the first submission. Updates from additions and deletions to the DMSMS BOM will be recorded in the next CDRL submittal after they occur. The following data elements from Table 1 of DI-MGMT-82274 shall be provided for the BOM: Data

Elements 1-3, 5-6, 9-12, 17-19, 25.

Alerts. The contractor will monitor the BOM for DMSMS Issues and when identified record the following data elements from Table 1 of DI-MGMT-82274 Data Elements:

44-50 & 52-53 in the next monthly update to the Life Cycle Management Data record.

Cases Management Reports. If a government task order authorizes the establishment of a DMSMS

Management Case to mitigate the issue, the contractor shall record the data related to each case to the

DMSMS Life Cycle Management Data record. The following data elements from Table 1 of DI-MGMT-

82274 apply: Data Elements 26, 30-38 & 39.

The first submission shall be made 60 days after contract award.

Subsequent quarterly submissions shall highlight new or revised data.

The data shall be provided in a supported version of Microsoft Excel (unless otherwise approved by the government)

Item 14: All deliveries shall be in digital format, compatible with Microsoft Office and Adobe Acrobat and delivered by email or via DoD SAFE (Secure Access File Exchange) website (https://safe.apps.mil/) in case the deliveries can't be sent through the email services. The Government personnel listed in the distribution list will receive a copy of the submittal. Name and electronic address of the Government personnel are specified below:

AMEL-LCW-NRC (Technical POC): JONATHON SALSBURY, jonathon.j.salsbury.ctr@army.mil

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil

Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

ACO: TBA

QAR: TBA

AMEL-LCW-NRC

PCO

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jonathon Salsbury

FCDD-ISE-RCD

Mechanical Engineer

07/23/2026 Alyssa Iadanza

AMEL-LCW-NRS

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER MGMT

D001 Contractor’s Progress Status and Management

Report

Contract Status Report (CSR)

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MGMT-80227 Exhibit A-Technical

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

MONTHLY See Item 16

SUBMISSION

a. ADDRESSEE

Draft

Item 4: Prepare in Contractor format.

Item 12/13: Submit first report NLT 15 days after the close of the first full accounting month and at one month intervals thereafter through the end of the contract.

Item 14: All deliveries shall be in digital format, compatible with

Microsoft Office and Adobe Acrobat and delivered by email or via

DoD SAFE (Secure Access File Exchange) website

(https://safe.apps.mil/) in case the deliveries can't be sent through the email services. The Government personnel listed in the distribution list will receive a copy of the submittal. Name and electronic address of the Government personnel are specified below:

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil

Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

PCO

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jonathon Salsbury

FCDD-ISE-RCD

Mechanical Engineer

07/23/2026 Alyssa Iadanza

AMEL-LCW-NRS

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER MGMT

E001 Contract Performance Report Contract Financial Report

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

18. ESTIMATED

TOTAL PRICE

DI-MGMT-81466A Exhibit A-Technical

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

QUARTERLY See Item 16

SUBMISSION

a. ADDRESSEE

Draft

Item 4: Contractor format is acceptable. Reporting Levels shall be IAW contractor’s WBS.

Item 9: Distribution Statement D. Distribution is authorized to DOD and DOD contractors only. Reason To protect administrative or operational use.

Item 10: Last day of contractor’s quarterly accounting period. Item 12/13: The

Contract Performance Report shall report cost performance up to the end of each accounting quarter. The initial Contract Performance Report shall be submitted 15 days after the end of the first accounting quarter and quarterly thereafter through the end of the contract.

Item 14: All deliveries shall be in digital format, compatible with Microsoft

Office and Adobe Acrobat and delivered by email or via DoD SAFE (Secure

Access File Exchange) website (https://safe.apps.mil/) in case the deliveries can't be sent through the email services. The Government personnel listed in the distribution list will receive a copy of the submittal. Name and electronic address of the Government personnel are specified below:

AMEL-LCW-NRC (Technical POC): JONATHON SALSBURY, jonathon.j.salsbury.ctr@army.mil

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil

Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

ACO: TBA

QAR: TBA

Significant Cost and Schedule Variances (positive and negative) will be explained in the CPR Format 5 at the DO level.

The Contractor may combine the CSR and CPR as one deliverable or submit both reports concurrently if desired.

AMEL-LCW-NRC

PCO

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jonathon Salsbury

FCDD-ISE-RCD

Mechanical Engineer

07/23/2026 Alyssa Iadanza

AMEL-LCW-NRS

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER MISC

F001 Scientific and Technical Reports System Security Plan

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MISC-80711A Exhibit A-Technical

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

SUBMISSION

a. ADDRESSEE

Draft

Item 4: Contractor may propose alternative format.

This is the formal document that provides an overview of the security requirements for the system and describes the security controls in place or planned for meeting those requirements. The plan shall contain supporting appendices and references, other key security-related documents such as a risk assessment, privacy impact assessment, system interconnection agreements, contingency plan, security configurations, configuration management plan, and incident response plan. The Contractor shall submit the MFoCS security plan documents for each specific hardware variant and all associated LRUs.

Item 12: Initial submission due 60 days prior to the first delivery order. Government requires 30 working days for review/comment.

Item 13: Final due 30 working days after receipt of Government comment. Update as required thereafter.

Item 14: All deliveries shall be in digital format, compatible with Microsoft Office and

Adobe Acrobat and delivered by email or via DoD SAFE (Secure Access File

Exchange) website (https://safe.apps.mil/) in case the deliveries can't be sent through the email services. The Government personnel listed in the distribution list will receive a copy of the submittal. Name and electronic address of the Government personnel are specified below:

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

ACO: TBA

QAR: TBA

AMEL-LCW-NRC

PCO

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jonathon Salsbury

FCDD-ISE-RCD

Mechanical Engineer

06/25/2026 Alyssa Iadanza

AMEL-LCW-NRS

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER MGMT

G001 Program Progress Report Configuration Control Documentation

(CCD)

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MGMT-80555A Exhibit A-Technical

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

SUBMISSION

a. ADDRESSEE

Draft

Item 4: Contractor may propose alternative format.

Item 12: The Contractor shall submit the MFoCS Configuration Control

Documentation for each specific hardware variant, and all associated LRUs.

First submission shall be made 60 days after delivery order award. Government requires 30 days for comments.

Item 13: NLT 30 days prior to the proposed shipment of any product/system affected by the proposed change, variance, or modification. The contractor shall deliver Configuration Control Documentation Covering each hardware configuration item.

Item 14: All deliveries shall be in digital format, compatible with Microsoft

Office and Adobe Acrobat and delivered by email or via DoD SAFE (Secure

Access File Exchange) website (https://safe.apps.mil/) in case the deliveries can't be sent through the email services. The Government personnel listed in

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil

Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

ACO: TBA

QAR: TBA

AMEL-LCW-NRC

PCO

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jonathon Salsbury

FCDD-ISE-RCD

Mechanical Engineer

07/23/2026 Alyssa Iadanza

AMEL-LCW-NRS

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collectionof information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER SESS

H001 Warranty Performance Report Warranty Performance Report

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-SESS-81639 Exhibit A-Technical

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

SEMIANNLY See Item 16

SUBMISSION

a. ADDRESSEE

Draft

Item 4: The contractor shall provide a warranty report on items under warranty;

contractor repair, replacement, and reimbursement, and equipment failure data.

Item 12/13: Data should be provided 6 months starting at the first submission of an item for warranty and semi-annual after that.

Item 14: All deliveries shall be in digital format, compatible with Microsoft

Office and Adobe Acrobat and delivered by email or via DoD SAFE (Secure

Access File Exchange) website (https://safe.apps.mil/) in case the deliveries can't be sent through the email services. The Government personnel listed in

Alyssa Iadanza alyssa.g.iadanza.civ@army.mil

Bryce Schweers bryce.t.schweers.civ@army.mil

Mandy Lockhart mandy.l.lockhart.civ@army.mil

PCO: TBA

ACO: TBA

QAR: TBA

AMEL-LCW-NRC

PCO

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Jon…