A19-Att.Technical Requirements Document 6.26.2023.pdf

Exhibit A SPRBL1-23-R-0019 Page 1 of 15

TECHNICAL REQUIREMENTS DOCUMENT

MPM-3000 Satellite Modem

NSN 5895-01-706-4392

Warfighter Information Network – Tactical Increment 2

26 June 2023

Exhibit A SPRBL1-23-R-0019 Page 2 of 15

TABLE OF CONTENTS

APPLICABLE DOCUMENTS

CONFIGURATION BASELINE

Obsolescence Management Requirements / Obsolete Components and Materials / DMSMS

Part Revisions

CHEMICAL AGENT RESISTANT COATING (CARC)

Paint Colors

Special Instructions

PACKAGING

Wood Packing Material

Military Packaging

VERIFICATION

CONTRACT SECURITY REQUIREMENTS

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL List

Individual CDRLs

Exhibit A SPRBL1-23-R-0019 Page 3 of 15

APPLICABLE DOCUMENTS

Military and Federal Standards MIL-STD-129R w Change 2 Military Marking for Shipment and Storage MIL-STD-130N Identification Marking of U.S. Military Property MIL-STD-2073-1E w/CHANGE 4 Standard Practice for Military Packaging

Military and Federal Specifications

DFARS 252.211-7003 Item Identification and Valuation DFARS 252.211-7006 Passive Radio Frequency Identification FAR 42.503 Post Award Conferences

Other Documents

Commercial Documents

ANSI/ASQ 9001:2015

ISPM-15 Regulation of Wood Pakaging Material in International Trade Security Documents

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

5895-01-706-4392 MODEM,COMMUNICATIONS 1052-0001-1

Exhibit A SPRBL1-23-R-0019 Page 4 of 15

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 supply system backorders for the 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., during market research when commencing a contractual procurement or repair action).

Backorder Avoidance can be approximated by multiplying the average monthly demand of the NHA by the estimated Case Resolution Time.

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 a 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” resolution type where we procure only the quantity of items needed until the next redesign event involving the item. 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).

“Commercial Item” and “Commercially Available Off-The-Shelf (COTS)” are items that meet their respective definitions in FAR Part 2.101 – Definitions. Note that privately developed NDI which do meet the requirements of definition subparagraph (8) can be considered commercial items (i.e., sold competitively in substantial quantities).

A “Complex Substitute” is the resolution of an Obsolescence Issue using a replacement item that has different specifications which need to be researched and validated but require 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 had the DMSMS Issue been discovered reactively (i.e., during market research when commencing a contractual procurement or repair action).

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

“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. DMSMS Issues are further classified as:

“Documented DMSMS Issues” are DMSMS Issues for which there is documentation advising that an

Exhibit A SPRBL1-23-R-0019 Page 5 of 15 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 1 year or less and rarely in excess of 2 years.

“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 service providers 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 Resolution Time” is the cumulative time from when a case is opened until it is closed, less any time spent in Hold status.

DMSMS Management Case “Status”:

Open – Self-explanatory.

Hold – An unresolved open case where active case management efforts have been suspended, typically because issue resolution does not require immediate action.

Resolved – The recommended solution is approved.

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.

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.

“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 LNB)” 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”. This typically applies to

Exhibit A SPRBL1-23-R-0019 Page 6 of 15 discontinued parts and only and not NHA’s.

“Non-Development Items (NDI)” shall be as defined in the FAR Part 2.101 – Definitions. Note that NDI’s can be treated as Commercial Items when they meet sub-paragraph (8) of the FAR Part 2.101 definition of a Commercial Item.

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

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.

A “Simple Substitute” is the resolution of a DMSMS Issue by its replacement with an existing item that meets all 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, 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 DMSMS Management Program in accordance with (IAW) this SOW for the period of performance of this contract. The government’s objective in this program is to efficiently and effectively identify, report, and resolve DMSMS Issues before they impact supply and readiness, eliminate unplanned redesigns and maintain alignment to the objective that at the last OWG meeting on this contract (i.e., the approximate conclusion of this contract), there shall be no unresolved documented DMSMS Issues and all DMSMS Issues predicted to occur during the 5-year period commencing that date shall have a DMSMS Management Case established.

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

Exhibit A SPRBL1-23-R-0019 Page 7 of 15 the end of life (YTEOL) to the maximum practical extent. The program shall also include procedures for sharing information with GIDEP and participating with the government in a Obsoecence Working Group

(OWG).

Design Changes. Design changes (including Simple Substitutions) shall be made in accordance with the Configuration Management requirements of this contract.

SubContractor Manangement. The Contractor shall ensure that its SubContractors (see SubContractor definition) adhere to the DMSMS/Obsolescence requirements of this SOW.

DMSMS Costs. The contractor shall be responsible all DMSMS Management Program Costs leading up to the government approval of a Case (i.e., until Resolution). The Government shall be responsible for contractual implementation.

Contractor Costs. The cost of the following Work Breakdown Structures (WBS) elements shall be priced in the Contractor’s RFP submittal and included in the basic contract price at time of award. The following should be considered the WBS structure of the government’s DMSMS Management Program:

- DMSMS Program Management Oversight

- DMSMS BOM establishment & monitoring

- Case Management activities

- OWG participation and support

- A WBS for each contract CDRL’s

Government Costs. Upon government acceptance of a proposed DMSMS Issue resolution, the PCO may request that the Contractor submit a priced proposal and/or ECP for implementing the solution. Upon receipt of this proposal or ECP, the government will evaluate it and determine if it wishes to contractually implement the solution on this contract.

DMSMS Alert Notice. For the weapon system under DMSMS management, the Contractor will monitor the parts and commercial software identified on the DMSMS BOM for DMSMS Issues. Should a documented or predicted DMSMS Issue be identified, the Contractor will submit a DMSMS Alert Notice within 15 days of discovering the issue IAW the CDRL for DI-MGMT-82274, DMSMS Life Cycle Management Data;

Alerts/Case Mgmt Reports (CDRL B001).

Case Management. Concurrent with the delivery of the Alert the Contractor shall establish a case to investigate and resolve it. Case management efforts shall commence when case is established and shall include Contractor efforts to analyze the issue, its impact, develop candidate solutions and recommend to the government a solution for approval. The recommended solution shall be accompanied with supporting rationale for its selection, its estimated cost, and a timeline for implementation upon approval by the government. The contractor shall also develop estimates of both the Cost Avoidance and Backorder Avoidance achievable by resolving this issue proactively. In support of this effort, the government will provide to the contractor on request estimates of stock-on-hand and the monthly demand for the assembly containing the to be discontinued part. All open cases shall be discussed at OWG meetings.

Exhibit A SPRBL1-23-R-0019 Page 8 of 15

DMSMS Case Management Reports. Once a DMSMS Case is established, the Contractor will report the status of each case to the government IAW the CDRL for DI-MGMT-82274, DMSMS Life Cycle Management Data;

Alerts/Case Mgmt Reports (CDRL B001). The initial report will be largely administrative and should include a summary of the issue, an initial assessment of its impact, potential solutions and a proposed timeline for the completion of the case. Subsequent Case Management Report updates are only required when there is a significant matter or change on the case to report (e.g., issues impacting contract schedule, satisfactory resolution, a change in status, a revised solution or a change in cost or schedule, etc.). The Case Management Report submitted when the case is resolved shall include the contract cost, the implementation schedule, the estimated Cost Avoidance and the estimated Backorder Avoidance quantity for the selected solution.

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

Exhibit A SPRBL1-23-R-0019 Page 9 of 15

Special Instructions

X = Applicable Location or Part Instruction Antenna Elements, including protective covers, i.e. fiberglass shields.

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.

Exhibit A SPRBL1-23-R-0019 Page 10 of 15

PACKAGING

Packaging shall be in accordance with MIL-STD-2073-1E w/CHANGE 4 Standard Practice for Military Packaging.

Marking shall be IAW MIL-STD-129R. MIL-STD-129R is applicable.

Wood Packing Material

Wood Packaging Material in accordance with ISPM-15, Regulation for Wood Packaging Materials 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 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

Exhibit A SPRBL1-23-R-0019 Page 11 of 15

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) 5895-01-706-4392 Military MIL-STD-2073-1E B 001 - 10 1 00 00 NA D ED 00 - 00 BC

Exhibit A SPRBL1-23-R-0019 Page 12 of 15

VERIFICATION

All development, testing, and demonstration necessary to meet the requirements of the subject NSN must be done at the full cost of the vendor. Those that are proposing an alternative part must demonstrate that their product is equal to or better than form, fit, and function of the subject NSN, and was developed prior to contract award. Those that are proposing an alternative part must demonstrate full mission readiness when their product is integrated with the WIN-T Inc 2 system. All testing of an alternative part, including First Article Testing (FAT), must be completed and demonstrated prior to government receipt of the items.

METHODS OF VERIFICATION

a. Analysis. An element of verification that utilizes established technical or mathematical models or simulations, algorithms, charts, graphs, circuit diagrams, or other scientific principles and procedures to provide objective evidence that stated requirements have been met.

b. Demonstration. An element of verification that generally denotes the actual operation, adjustment, or re-configuration of items to provide objective evidence that designed functions were properly accomplished under specified scenarios. The items under test may be instrumented and quantitative limits or measurement criteria may be monitored.

c. Inspection. An element of verification that consists of investigation of items to determine conformance to those stated requirements which can be determined by such investigations. To constitute inspection, said investigations must be able to be accomplished without the use of special laboratory appliances, procedures or equipment. Inspection is generally non-destructive and typically includes the use of sight, hearing, smell, touch and taste; simple physical manipulation; mechanical and electrical gauging and measurement; and other forms of investigation.

d. Test. An element of verification which generally denotes the determination, by technical means, of the properties or elements of items, including functional operation, and involves the application of established scientific principles and procedures. Test verification typically involves the actual measuring of some technical functional or performance parameter, with the resultant data being available for evaluation against set criteria directly traceable back to specific requirement(s) of a performance or some other technical specification.

Exhibit A SPRBL1-23-R-0019 Page 13 of 15

CONTRACT SECURITY REQUIREMENTS

The contract has been deemed Controlled Unclassified Information (CUI)/UNCLASSIFIED. The Contractor shall be required to have CUI/UNCLASSIFIED facility clearance with appropriate CUI/UNCLASSIFIED safeguarding capability.

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

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL List

CDRL

Data Line No. DID Identification Title A001 DI-MISC- 80711A Scientific and Technical Reports – Configuration Control B001 DI-MGMT- 82274 DMSMS Life Cycle Management Data - Alerts/Case Management Reports

Exhibit A SPRBL1-23-R-0019 Page 14 of 15

Individual CDRLs

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

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 and Communications 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 collection of 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

A

C. CATEGORY:

TDP TM OTHER

MISC

D. SYSTEM/ITEM

Mission Network On-the-Move

(WIN-T Inc 2)

E. CONTRACT/PR NO.:

F. CONTRACTOR:

TBD

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Scientific and Technical Reports

3. SUBTITLE

Configuration

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80711A

5. CONTRACT REFERENCE

Tech Requirements

6. REQUIRING OFFICE

AMEL-LCC-NB

7. DD 250 REQ

N/A

9. DIST STATEMENT

REQUIRED

N/A

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

BLOCK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

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

SUBMISSION

BLOCK 16

Draft Final

Reg Repro

16. REMARKS

BLK 4: Data Item Description DI-MISC-80711A: Delete block 10 instructions entirely and follow instructions in this Technical Requirements. WIN-T Increment 2 Hardware Spares.

The Contractor shall prepare and submit a Request for Variance (RFV) for Government review in accordance with this Technical Requirements section for Configuration Management when there is a change or departure from a contractual baseline.

All RFVs for changes shall be submitted for Government review or notification within 5 business days of Contractor approval and prior to presentation of the product for acceptance, but not later than 30 calendar days, of any such product. The Government shall review, accept, and/or comment on the draft submission in 30 calendar days. The Contractor shall incorporate changes and re-submit within 30 calendar days. The Government will have 30 calendar days to review, accept, or comment on the final submission.

Data shall be submitted and exchanged electronically in Microsoft Office suite of applications (MS Word, Excel, Power Point, Access, and Project). Alternate formats may be allowed subject to Government review and approval.

PCO 0 1 0

AMEL-LCC-NB 0 1 0

15. TOTAL 0 2 0

G. PREPARED BY

H. DATE

I. APPROVED BY

J. DATE

Exhibit A SPRBL1-23-R-0019 Page 15 of 15

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

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 collection of 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

A

C. CATEGORY:

TDP TM OTHER

D. SYSTEM/ITEM

Mission Network On-the-Move

(WIN-T Inc 2)

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

B001

2. TITLE OF DATA ITEM

DMSMS Life Cycle Management Data

3. SUBTITLE

Alerts/Case Management Reports

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-82274

5. CONTRACT REFERENCE 6. REQUIRING OFFICE

AMEL-LCC-NB

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

Block 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE 11. AS OF DATE

Block 16

13. DATE OF SUBSEQUENT

SUBMISSION

Block 16

Draft

Final

Reg Repro

16. REMARKS

Submit Alerts within 15 calendar days of discovering the DMSMS Issue.

The DMSMS Alert will provide the following data elements from Table 1 of DI-MGMT-82274: Data Elements 1-3, 5, 11, 17-19, 44-50 & 52-53.

The initial Cases Management Report shall be submitted NLT 45 days after submitting the DMSMS alert and shall summarize the issue, its impact and describe the contractors proposed plan and timeline to resolve and close the case. Subsequent updates to the case report shall occur whenever there is: a change in status, cost, schedule, impact or in the proposed mitigation strategy.

A Case Management Report will be submitted 60 days before the end of the contract for any open cases which will not be closed by the end of the contract. This will include the contractor’s recommendation for any post contract government actions.

The report shall contain:

The report will review and update the Alert data elements previously provided and provide the following additional data elements from Table 1 of DI-MGMT-82274:

Data Elements 25-26 & 30-41.

Data Element 35 shall include a description of the impact on all NHA's affected.

Data Element 37 shall include a summary of other mitigation strategies seriously considered and why they were not pursued.

Data Element 38 shall be a proposed case implementation schedule identifying key events from the case approval (resolved) to completion (closed).

Submit electronically in a supported version of Microsoft Excel (unless otherwise approved by the government).

PCO 0 1 0

FCDD-ISE-HDA 0 1 0

15. TOTAL 0 2 0

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

DD FORM 1423-1 FEB 2001