Exhibit A - Tech Requirements Data Package.pdf
PDF 484 KB Posted
- Solicitation number
- SPRBL1-22-R-0011
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Exhibit A SPRBL1-22-R-0011 Page 1 of 28 Issue: 23 June 2022
TECHNICAL REQUIREMENTS
MX-11617 Light Interference Filter
Exhibit A SPRBL1-22-R-0011 Page 2 of 28
DOCUMENT REVISIONS
Date Section / Paragraph / Item Revision
Exhibit A SPRBL1-22-R-0011 Page 3 of 28
TABLE OF CONTENTS
DOCUMENT REVISIONS
APPLICABLE DOCUMENTS
CONFIGURATION BASELINE
Obsolescence Management Requirements / Obsolete Components and Materials
Definitions
DMSMS Management Plan
Design Changes
Subcontractor Manangement
DMSMS Costs
DMSMS BOM Establishment & BOM Monitoring
DMSMS BOM Delivery
DMSMS Alert Notice
Case Management
DMSMS Case Management Reports
Paint Colors
PACKAGING
Wood Packing Material
Military Packaging
SPECIALIZED TESTING
CONTRACT SECURITY REQUIREMENTS
SURGE AND SUSTAINMENT PLAN
Definitions
Surge and Sustainment Capabilities Assessment Plan
CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1
CDRL List
Individual CDRLs
Exhibit A SPRBL1-22-R-0011 Page 4 of 28
APPLICABLE DOCUMENTS
Military and Federal Standards MIL-STD-129R Military Marking for Shipment and Storage MIL-STD-2073-1E Standard Practice for Military Packaging
Commercial Documents ISPM Number 15 Regulation of Wood Packaging in International Trade ANSI/ISO/ASQ(E) Q9001-2015 American National Standard, Quality Management Systems
Requirements EIA-649-1 Configuration Management Requirements For Defense Contracts ANSI/NCSL Z540.3-2006 Requirements for the Calibration of Measuring and Test Equipment ANSI/ASQ Q10012-2003 Measurement Management Systems – Requirements for
Measurement Processes and Measuring Equipment ANSI/ASQ Z1.4-2003 (R2013) Sampling Procedures and Tables For Inspection By Atrributes
Security Documents Security Classification Guide (SCG) for Image Intensifier Devices
Dated 27DEC2017, PEO Soldier / PM Soldiers, Sensors, and Lasers
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 5855-01-379-1410 Light Interference Filter 5009737 / A3144282
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 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, CDRL B001, and CDRL C001, 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. ECP should be prepared in accordance with EIA-649-1, CDRL A001, and DI-SESS-80639.
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, Exhibit A SPRBL1-22-R-0011 Page 5 of 28 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-80640.
A Notice of Revision (NOR) shows the detailed changes that must be made to technical documentation, except specifications, following approval of an ECP. A NOR shall be submitted for each document affected by an ECP. NOR should be prepared in accordance with EIA-649-1, CDRL C001, and DI-SESS-80642.
Obsolescence Management Requirements / Obsolete Components and Materials
Applicable CDRLS are to be listed in the CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1 Section below.
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.
“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 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.
Exhibit A SPRBL1-22-R-0011 Page 6 of 28
“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 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.
“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 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.
“Item” means any part, assembly, software, material, chemical, etc., used in the manufacture, assembly, or operation of deliverables of this contract.
“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.
Exhibit A SPRBL1-22-R-0011 Page 7 of 28
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 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 Plan The Contractor’s plan to conduct the DMSMS/Obsolescence program shall be documented in a DMSMS Management Plan (DMP) prepared and delivered IAW DI-MGMT-81948, DMSMS Management Plan (CDRL K001) and this TRD. The Contractor is encouraged to make use of or tailor any existing inhouse corporate DMSMS or Obolescence management plans as the government would like to utilize existing contractor best pratices where practical.
The Contractor’s DMP shall include a description of their process and procedures for selecting parts and whether they utilize a PPL (or equivalent) to accomplish this.
The DMP shall state the frequency of monitoring items on the DMSMS BOM and this can vary for different types of items (e.g., different electronic, electrical and electromechanical (EEE) component types, commercial assemblies and commercial SW).
With regard to predicting DMSMS issues over the 5 year planning horizon, the DMP shall identify any
Exhibit A SPRBL1-22-R-0011 Page 8 of 28 predictive tools or services which the contractor intends to use to accomplish this.
The DMP shall also document the procedures for participation with the Government.
Design Changes Design changes 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 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;
- Implementing the selected solutions, including redesign;
- System compatibility assurance;
- Interface with the Army Network; and
- Non-government qualification testing.
DMSMS BOM Establishment & BOM Monitoring For the equipment under DMSMS management, the contractor shall develop, with the government concurrence, a DMSMS BOM of those items on the manufacturing BOM which are planned to be proactively monitored for availability. For the purpose of this task, the initial baseline of the DMSMS BOM shall be all electronic, electrical and electromechanical components; all commercial SW and all commercial assemblies. This initial baseline may be revised at the time of award by the government acceptance of recommended changes offered by the contractor in their proposal. After award, further revisions may be proposed to the PCO or OWG. If multiple OCM parts have been already approved to meet the requirements of an OEM part number, they shall also be listed on the DMSMS BOM. Once the DMSMS BOM is established, the contractor shall monitor each item on the DMSMS BOM for DMSMS issues IAW the frequency defined in the DMP and ensure that the DMSMS BOM accurately reflects the current approved design.
In the special case of items which meet the FAR definition of a commercial item, the Contractor shall monitor these items as a single line BOM entry working with the design owner to forecast when the item will no longer be available. In the case of NDI developed exclusively at private expense which do not meet the FAR definition of a commercial item, the Contractor shall include all EEE components; all commercial SW and all commercial assemblies in the DMSMS BOM baseline as stated above.
Commercial SW may also be represented on the BOM as a single line entry at the level where it exists, identified by a definitive part/version number.
Exhibit A SPRBL1-22-R-0011 Page 9 of 28
Firmware need not be separately represented on the BOM. They are considered part of NVM component or assembly on which the firmware resides (see definition).
DMSMS BOM Delivery The Contractor shall deliver and update semiannually the current DMSMS BOM. The DMSMS BOM shall be submitted IAW the CDRL for DI-MGMT-82274; DMSMS Life Cycle Management Data, BOM (CDRL L001) and this TRD. The BOM may include single line entries for commercial items (as defined in the FAR) and commercial SW.
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 IAW the CDRL for DI-MGMT-82274, DMSMS Life Cycle Management Data; Alerts/Case Mgmt Reports (CDRL M001) and this TRD.
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 benefits to the government (including estimates of both the Cost Avoidance and Backorder Avoidance achievable by resolving this issue proactively), its estimated cost and a timeline for implementation upon approval by the government.
All open cases shall be discussed at the OWG.
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 M001) and this TRD. The initial Case Management Report (after the Alert Notice) 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 completion of the case efforts. 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 contractual deliveries, satisfactory resolution, a change in status, a revised solution or schedule, etc.). Upon submittal of a case solution for government approval, the Case Management Report shall also report the estimated Cost Avoidance and Backorder Avoidance for the recommended solution. Any supply data needed to estimate Cost or Backorder Avoidance will be provided by the government at OWG meetings.
Exhibit A SPRBL1-22-R-0011 Page 10 of 28
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 X Other: Area enclosed by dotted line Green (Olive
Drab) 34087
Exhibit A SPRBL1-22-R-0011 Page 11 of 28
PACKAGING
Wood Packing Material 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
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-22-R-0011 Page 12 of 28
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) 5855- 01-379-
Military
MIL-
STD-
2073-
1E B 001 10 1 00 DA NA B D4 ED 00 BC
Exhibit A SPRBL1-22-R-0011 Page 13 of 28
SPECIALIZED TESTING
The contractor shall perform First Article Testing, herein after referred to as Initial Production Testing (IPT), and Conformance Inspection (CI) IAW MIL-PRF-49257, and this document. Test methods for the IPT and CI shall be in accordance with (IAW) the Government approved Quality Validation Plan (QVP) and Test Procedures.
The Government may require IPT be repeated over the life of this contract to requalify the product; should the contractor fail to deliver any of these items for a period of one year, make changes to products and/or processes, change a supplier of a component, or move the production line.
The Government reserves the right to waive IPT for contractors that have previously qualified by Product Manager Soldier Manuever Sensors and have completed Initial Production Testing. The contractor shall be required to provide relevant contract numbers, the Government’s technical POC for the corresponding efforts, and a copy of the FAT/IPT test report approved by the Government’s technical POC. In addition to proof of Government-approved qualification test results, the contractor shall be required to provide evidence that it has maintained production, with deliveries to the Government, prior to the Governemnt approving a waiver.
The Government reserves the right to conduct an operational test (OT), to include compatibility testing, to ensure the system is operationally effective and suitable, and interoperable with other Army equipment. If an OT is required, IPT approval is contingent on a successful OT.
As part of IPT, the contractor shall:
a) Develop the test procedures and plans necessary to demonstrate that these units conform to the requirements established by the applicable specification(s) and other technical data provided in this contract.
b) Notify the Government and test the IPT units.
c) Provide an Initial Production Test Report to the Government which documents the IPT results.
d) Ensure all equipment used to take performance readings for acceptance tests are kept within the performance parameters delineated by the manufacturer of that equipment and capable of satisfying the performance parameters of this contract. All equipment manufactured by the contractor shall be listed and the parameters established and maintained for this equipment also.
The Contractor shall test 20 unit(s) of Lot/Item 5855-01-379-1410 as specified in this contract. At least 30 calendar days before the beginning of first article tests, the Contractor shall notify the Contracting Officer, in writing, of the time and location of the testing so that the Government may witness the tests, in accordance with 52.209-3 First Article Approval-Contractor Testing. All IPT samples shall be assembled at the same location at which production units will be assembled, using the same parts, materials, and manufacturing processes to be employed for subsequent production.
The contractor shall submit a First Article Qualification Test Plan in accordance with CDRL D001 and this document. IPT and Conformance Inspection shall be performed in accordance with the Government approved QVP. In addition to the information required by DI-NDTI-81307A, this submission shall contain:
Exhibit A SPRBL1-22-R-0011 Page 14 of 28
a) The delineation and allocation of tests to be performed on each of the Initial Production units and the order of such tests.
b) The delineation and allocation of tests to be performed as Conformance Inspection on subsequent production lots, to include the order of tests and the sampling plan.
c) Step-by-step test procedures for each test and the data sheets to be employed to document the results of testing. Test procedures may be submitted separate from the QVP, in accordance with CDRL E001.
d) Identification of required test facilities, equipment and personnel.
e) Test milestones schedules and the contractor's test readiness posture.
f) A table which cross references the paragraph number of the specification requirement (including a brief description of the requirement) and the associated paragraph number of the QVP.
The contractor shall submit an Initial Production Test Report in accordance with CDRL F001 and this document. Initial Production Test approval shall be contingent upon the submission of a complete and acceptable IPT Report to include verification of corrective action for reported IPT Failures to include adequacy of identified changes to the design/manufacturing process. IPT samples shall meet all contractual requirements or all variances shall be documented by Government approved waivers.
The IPT Report shall be complete, accurate, and readable and shall provide sufficient data to determine that the hardware item meets all the requirements delineated in the contract. The report will include the following:
a) Contractor's name and address.
b) Contract number.
c) Name and address of plant where Initial Production units were fabricated and assembled.
d) Place and date of performance of tests.
e) Identification of applicable test and inspection equipment used in performance of Initial
Production Test.
f) Sample size or quantity submitted for test or inspection.
g) A table which cross-references the paragraph numbers of the specification, the test procedures, and data sheet entry.
h) Complete test results showing actual or quantitative observations and all required calculations, allowable tolerances for each parameter, date the test was performed, the name and signature of tester, name and signature of the Government verifier/witness, and serial number of the equipment.
i) The final revision of the Government approved FIAR for each failure that occured.
The contractor shall report all IPT Failures and submit a Failed Item Analysis Report (FIAR) IAW CDRL G001 and this document. For any failure that occurs in a Government conducted Operational Test (OT), the contractor shall submit a FIAR and incorporate corrective actions.
The IPT samples shall NOT serve as a manufacturing standard. Upon successful completion of IPT, Items which are refurbishable and made fully compliant with contractual requirements shall be delivered as production items. The Government shall determine the acceptability of all IPT samples. Those items which are not refurbishable shall not be delivered as production items.
Exhibit A SPRBL1-22-R-0011 Page 15 of 28
The contractor shall conduct Conformance Inspections for all product delivered in accordance with MIL-PRF- 49257, the Government approved Quality Validation Plan, and the requirements of this document.
Conformance Inspection procedures used to test production units shall be identical to those used to test IPT samples. Sampling for conformance inspections shall be per MIL-PRF-49257. After IPT is approved, any proposed changes to the QVP and/or production test procedures will be submitted per CDRL D001 and E001 for evaluation. Such submissions will provide complete justification for the change. Changes to the approved test procedures shall not be implemented without written Government approval.
Delivery of subsequent lots shall not be made prior to successful completion of Conformance Inspection.
The contractor shall notify the cognizant Government Quality Assurance Representative (QAR) in writing at least 2 days in advance, of the time and place for each Conformance Inspection. The contractor shall notify the QAR in writing within 2 working days of completion of Conformance Inspection for a specific production lot.
The contractor shall notify the PCO and Technical Activity in writing upon completion of Conformance Inspection. This notification will be submitted by email not later than 10 days after the test is completed, and will include:
- Contract Number.
- Item Identification (Nomenclature and/or Part Number)
- Date of Testing
- Lot Size, Number, and time frame represented
- Sample Size
- List of any associated failures
The contractor shall report each IPT Failure and each Conformance Inspection failure occurring in Test Groups B, C, and D, to the Government Quality Assurance Representative (QAR) and the Technical Activity (see Block 16 of DD Form 1423 for CDRL G001) within 48 hours of failure occurrence. Within 10 working days of failure occurrence, the contractor shall submit a Failed Item Analysis Report (FIAR) through the cognizant QAR to the Technical Activity as required by CDRL G001. In addition to the information required by DI- SESS-81315B, the report shall include:
a) Contractor's name, address and applicable contract number
b) Identification of failed item
c) Number of units in lot and sample size
d) Date and time of failure occurrence
e) Failure Mode
f) Summary of failure analysis
g) Root cause of failure
h) History of the failure
i) Proposed Corrective Action to eliminate root cause, contain the failure, and prevent re-occurrence
j) Re-inspection plan to validate the corrective action
k) Proposed disposition of failed item and lot
l) Verification that Corrective Action was effective.
Exhibit A SPRBL1-22-R-0011 Page 16 of 28
The contractor shall implement the proposed corrective action on all units in the lot, select new samples and conduct re-inspection and other required re-testing in accordance with the re-inspection plan in the FIAR.
Results of the re-inspection and validation of the corrective action shall be included in the FIAR.
Final acceptance and shipment approval will be withheld until results of the re-inspection substantiate that the corrective action was effective and the FIAR was accepted, as authorized by the PCO.
CONTRACT SECURITY REQUIREMENTS
The contractor shall adhere to the requirements of the signed DD-254 Contract Security Classification Specification and "Security Classification Guide (SCG) for Image Intensifier Devices". In the event of a discrepancy between the signed DD 254, included as an attachment to the solicitaition/contract, and the language in this section, the signed DD 254 information shall take precedence.
Access to Controlled Unclassified Information (CUI) is required in the performance of this contract.
Information designated as CUI, generated or provided under this contract shall be controlled, handled, stored, marked, safeguarded, transmitted, and destroyed IAW DoDM 5200.01 Vol 4, DoDM 5400.0, AR 380-5, AR 25-55, AR 25-2, and the following guidance:
• Electronically transmitted CUI shall be sent via:
1) Encrypted email
2) Password protected/encrypted document
3) If Contractor chooses to use DoD Safe it must first send email request to the Contracting Officer
(KO) and Contracting Specialist (KS). DoD Safe Access File Exchange at https://safe.apps.mil.
4) An accredited information system with proper security controls.
• The contractor may disseminate CUI to their employees and subcontractors that have a need-toknow.
• Disposal/destruction shall be by means of shredding when no longer needed. If shredding capabilities are unavailable on contractor site – contractor may coordinate with government representative for shredding services.
• The contractor shall report the unauthorized disclosure of CUI to the Contracting Officer, or Contracting Officer Representative.
Contractor is authorized to receive, store, and generate classified material at the contractor’s facility. Contractor will reference the appropriate security classification guidance when generating or deriving classified material or hardware. All classified information received or generated will be properly stored and handled according to the markings on the material. All classified information received or generated is the property of the U.S.
Government. At the termination or expiration of this contract, the U.S. Government will be contacted for proper disposition instructions.
If performing on contractor site, the contractor shall develop an OPSEC Plan IAW AR 530-1 as listed in the TRD CDRL number I001. Requirring Activity (RA) is responsible for providing to the contractor a current and https://safe.apps.mil/
Exhibit A SPRBL1-22-R-0011 Page 17 of 28 valid program/command OPSEC Plan. The contractor will use the program/command OPSEC Plan to ensure the contractor developed OPSEC Plan includes the same Critical Information List (CIL) and OPSEC measures.
SURGE AND SUSTAINMENT PLAN
Definitions As defined in the Defense Logistics Acquisition Directive (DLAD) Procurement Notes – Updated January 10, 2022 (https://www.dla.mil/HQ/Acquisition/Policy-and-Directives/):
“Surge and sustainment (S&S)” means increased quantities and accelerated delivery rates required to meet Military Service requisitions across a broad spectrum of contingencies. The increased quantity and accelerated delivery rate are above and beyond the normal peacetime requirements. S&S quantities are identified as MWR, D1-D6 schedule, or a surge quantity event.
“Capability Assessment Plan (CAP)” means the offeror’s plan for covering S&S requirements, identification of competing priorities for the same resources, and date when the S&S capability can be attained. The offeror must provide the CAP as an attachment to its proposal when S&S items are identified in the solicitation. If the offeror cannot meet S&S quantity and delivery needs, the CAP must identify the shortfall and provide best value solutions, to include a proposed Government investment strategy to help offset the shortfall if needed.
Surge and Sustainment Capabilities Assessment Plan A Surge and Sustainment Capability Assessment Plan (CAP), developed in accordance with DFARS 217.208– 70(b), may be requested by the Government.
CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1
CDRL List
CDRL
Data Line No. DID Identification Title
A001 DI-SESS- 80639 Engineering Change Proposal B001 DI-SESS- 80640 Request for Variance C001 DI-SESS- 80642 Notice of Revision D001 DI-NDTI- 81307A First Article Qualification Test Plan – Quality Validation Plan E001 DI-NDTI- 80603 Test Procedures F001 DI-NDTI- 80809B Test/Inspection Report – Initial Production Test Report G001 DI-RELI- 81315 Failure Analysis and Corrective Action Report I001 DI-MGMT- 80934C Operations Security (OPSEC) Plan K001 DI-MGMT- 81948 DMSMS Management Plan L001 DI-MGMT- 82274 DMSMS Life Cycle Management Data, BOM M001 DI-MGMT- 82274 DMSMS Life Cycle Management Data; Alerts/Case Mgmt Reports
Exhibit A SPRBL1-22-R-0011 Page 18 of 28
Individual CDRLs
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
Original Form Approved OMB No. 0704-0188
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
A001 TDP X TM OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
LIGHT INTERFERENCE
FILTER
1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE
GROUP
Engineering Change Proposal Configuration Management
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-SESS-80639 AMSEL-LCE-INV 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 N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
Draft Final
SEE ITEM 16
Reg
Repro
16. REMARKS:
The contractor shall prepare and submit Engineering Change Proposal in accordance with EIA-649-1 and this DID when a change to a contractual baseline document is deemed necessary.
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 30 days after receipt of Government comments. The Government will have 30 days to review, accept, and/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.
E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
FCDD-IS-HDD
QAR
PCO
ACO
15. TOTAL 0 5 0
G. PREPARED BY H. DATE I. APPROVED BY J. DATE
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
FCDD-IS-HDD
Branch Chief
Exhibit A SPRBL1-22-R-0011 Page 19 of 28
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
B001 TDP X TM OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
Request For Variance Configuration Management
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-SESS-80640 AMSEL-LCE-INV 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 N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
Draft Final
16. REMARKS: The contractor shall prepare and submit Request For Variance in accordance with EIA-649-1 and this DID when a departure from a contractual baseline document is deemed necessary.
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 30 days after receipt of Government comments. The Government will have 30 days to review, accept, and/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.
E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
FCDD-IS-HDD
QAR
PCO
ACO
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
Exhibit A SPRBL1-22-R-0011 Page 20 of 28
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
C001 TDP X TM OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
Notice of Revision Configuration Management
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-SESS-80642 AMSEL-LCE-INV 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 N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
Draft Final
16. REMARKS: The contractor shall prepare and submit Notice of Revision in accordance with EIA-649-1 and this DID when a change to a contractual baseline document is deemed necessary.
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 30 days after receipt of Government comments. The Government will have 30 days to review, accept, and/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.
E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
FCDD-IS-HDD
QAR
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
Exhibit A SPRBL1-22-R-0011 Page 21 of 28
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
D001 TDP TM OTHER NDTI
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
First Article Qualification Test Plan Quality Validation Plan
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-NDTI-81307A AMSEL-LCE-INV INSER
T
7. DD 250 REQ 9.DIST STATEMENT
REQUIRED
10. FREQUENCY 12. DATE OF FIRST
SUBMISSION 14. DISTRIBUTION IN
DD ONE/P 30 DAC b. COPIES
SECT.
B
8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
Draft Final
A SEE ITEM 16
16. REMARKS: Submit draft via LT. Government requires 30 days for review/comments. Submit final within 15 days of receipt of Government comments, via DD 250. The Government will require 15 days for review/comments for each subsequent 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.
E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
FCDD-IS-HDD
15. TOTAL 4 4 0
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
Exhibit A SPRBL1-22-R-0011 Page 22 of 28
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
E001 TDP TM OTHER NDTI
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
Test Procedures
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-NDTI-80603 AMSEL-LCE-INV INSER
T
7. DD 250 REQ 9.DIST STATEMENT
REQUIRED
10. FREQUENCY 12. DATE OF FIRST
SUBMISSION 14. DISTRIBUTION IN
DD OTIME 180 DAC b. COPIES
SECT.
B
8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
Draft Final
16. REMARKS: Submit draft via LT. Government requires 30 days for review/comments. Submit final within 30 days of receipt of Government comments, via DD 250.
Each draft and the final submissions shall be delivered in a format, compatible with Microsoft Office software delivered by e-mail.
Alternative delivery media may be discussed with the Contracting Officer prior to delivery. E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
FCDD-IS-HDD
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
Exhibit A SPRBL1-22-R-0011 Page 23 of 28
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
F001 TDP TM OTHER NDTI
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
Test/Inspection Report Initial Production Test Report
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-NDTI-80809B AMSEL-LCE-INV INSER
T
7. DD 250 REQ 9.DIST STATEMENT
REQUIRED
10. FREQUENCY 12. DATE OF FIRST
SUBMISSION 14. DISTRIBUTION IN
DD OTIME 180 DAC b. COPIES
SECT.
B
8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
16. REMARKS: Submit report of Initial Production Testing results via DD 250. Government requires 14 days to provide comments/approval.
Submit revised report within 7 days after receipt of government comments. Government requires 7 days to provide comments/approval.
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.
E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
FCDD-IS-HDD
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
Exhibit A SPRBL1-22-R-0011 Page 24 of 28
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
G001 TDP TM OTHER SESS
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
Failure Analysis and Corrective Action Report
Failed Item Analysis Report
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-SESS-81315B AMSEL-LCE-INV 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 N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
16. REMARKS: Data Item Description (DID) reference to MIL specs/stds is for guidance only.
Failure reports shall be submitted within 10 days of failure occurrence.
Technical Activity Representative is Steve Wolbach.
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.
E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
FCDD-IS-HDD
PCO
ACO
QAR
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
Exhibit A SPRBL1-22-R-0011 Page 25 of 28
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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
H001 TDP TM OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
Operations Security (OPSEC) Plan
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED
TOTAL PRICE
DI-MGMT-80934C AMSEL-LCE-INV INSERT
7. DD 250 REQ 9.DIST STATEMENT
REQUIRED
10. FREQUENCY 12. DATE OF FIRST
SUBMISSION
14. DISTRIBUTION IN
NO ASREQ 90 DAC b. COPIES SECT. B
8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT
SUBMISSION
a. ADDRESSEE
Draft Final
16. REMARKS: Submit OPSEC Plan within 90 Days After Contract Award.
All deliveries shall be delivered in a format, compatible with Microsoft Office software delivered by e-mail. Alternative delivery media may be discussed with the Contracting Officer prior to delivery.
E-mail notification is required with any electronic submission.
AMSEL-LCE-INV
15. TOTAL 0 3 3
Steve Wolbach
FCDD-IS-HDD
Electrical Engineer
Daniel Webster
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .