IQC for NSN 6110-01-485-9081

IQC Award for NSN 6110-01-485-9081 *** LTC PID Packaging Consolidated Text *** PLEASE SEE GLOSSARY AT THE END OF THE DOCUMENT FOR FULL TEXT OF THE ITEM DESCRIPTION AND PACKAGING REFERENCE NUMBERS CALLED OUT FOR EACH NSN. NSN: 014859081 REGULATOR, VOLTAGE REFERENCE NUMBER: ZD071 REFERENCE NUMBER: CA060 REFERENCE NUMBER: ZD017 CRITICAL APPLICATION ITEM NAVISTAR DEFENSE LLC DBA (338X5) P/N 3113485C1 NAVISTAR DEFENSE LLC DBA (338X5) P/N 3113485C1L C. E. NIEHOFF & CO. DBA (76761) P/N N3118 PREP FOR DELIVERY LINE ITEM 00002 TYPE OF COVERAGE: DLA DIRECT, CONUS PKGING DATA-QUP: 001 SHALL BE PACKAGED STANDARD COMMERCIAL IN ACCORDANCE WITH ASTM D 3951. ********************************************************* GLOSSARY ********************************************************* PACKAGING TEXT SHALL BE PACKAGED STANDARD COMMERCIAL IN ACCORDANCE WITH ASTM D 3951. Markings Paragraph When ASTM D3951, Commercial Packaging is specified, the following apply: - All Section "D" Packaging and Marking Clauses take precedence over ASTM D3951. - In addition to requirements in MIL-STD-129, when Commercial Packaging is used, the Method of Preservation for all MIL-STD-129 marking and labeling shall be "CP" Commercial Pack. - The Unit of Issue (U/I) and Quantity per Unit Pack (QUP) as specified in the contract take precedence over QUP in ASTM D3951. This solicitation is being issued under the First Destination Transportation (FDT) program. If this acquisition is for Foreign Military Sales (FMS) or has an APO/FPO ship?to address, FDT will not apply and normal procedures should be followed. For FDT program transportation requirements, see DLAD clauses 52.247?9059 F.O.B. Origin, Government Arranged Transportation and 52.247?9058, First Destination Transportation (FDT) Program - Shipments Originating Outside the contiguous United States (OCONUS). Additional information about FDT can be found on the FDT website (http://www.dla.mil/FDTPI/). THE FOLLOWING PARAGRAPH APPLIES TO ALL PACKAGING CALLED OUT IN THIS DOCUMENT: ITEM DESCRIPTION TEXT REFERENCE NUMBER ZD017 In addition to MIL-STD-129 markings, each MRAP palletized shipment shall include two, 10 inch by 10 inch fluorescent yellow sticker/sign/placard with the letters MRAP in 2 inch bold black letters and applied to one side and one panel of palletized load. For better visibility, place the MRAP sticker/sign/placard on the outside of the multiwall container(s) or the pallet, not under any shrink-wrap. The stickers are to be placed high on each side of each container, so they are visible at eye level. This sticker/sign/placard is required to expedite the receipt and inspection of these shipments. This requirement is only applicable for shipments directed to DDC depots and direct vendor deliveries to CCPs; and does not apply to direct vendor deliveries to the customer. ACCEPTABLE DEVIATIONS: Contractor is authorized to make adjustments to actual sticker size and font size when shipping containers are not large enough to adequately display all required MIL-STD-129 markings along with the standard size (as cited above). OEM MRAP STICKERS: Each OEM has a designated background color in lieu of the standard yellow background MRAP sticker in an effort to apply Lean Six Sigma principles and concepts to packaging, storage, and transport of MRAP material to theater. The following are the official designations (background color # text required): GREEN # MRAP BAE (TX) TEAL # MRAP OSHKOSH PURPLE # MRAP BAE (PA) ORANGE # MRAP FPII BLUE # MRAP NAVISTAR PINK # MRAP GDLS **NOTE: If MRAP stickers are missing or OEM is exhausting yellow background stickers, no quality notification shall be submitted to Contract Administrating Activity. REFERENCE NUMBER ZD071 Configuration Change Management - Engineering Change Proposal, Requests for Variance (Deviation or Waiver) February 2015 1. Requirements A. The Configuration Change Management section of SAE EIA-649-1 Configuration Management Requirement for Defense Contracts, Paragraph 3.3, shall be used for Configuration Control of material purchased under this contract. B. Furnished item(s) shall conform to the approved configuration requirements/revision specified, unless a Pre-Production Request for Variance (deviation) or a Post-Production Request for Variance (waiver), is processed and approved as provided by Paragraph 3 in this Standard Text Object (STO). Hereafter, the term #Request for Variance (RFV) # will also include Requests for Deviations and Waivers. 2. The definitions from EIA-649-1 apply to items being procured under this solicitation/contract, with the following clarification of Deviation & Waiver: A. Pre-Production RFV (previously known as deviation) requests permission to produce a product that does not conform to contract requirements/documentation for a limited amount of time and for specified effectivity. (A deviation differs from an engineering change in that an approved engineering change requires corresponding revision of the item's current approved configuration documentation, whereas a deviation does not.). B. Post-Production RFV (previously known as waiver) requests approval of product found during manufacture, or after having been submitted for Government inspection or acceptance, that departs from specified requirements, but nevertheless is considered suitable for use "as is" or after repair by an approved method. 3. Contractor responsibilities. A. An Engineering Change Proposal (ECP) is used to make permanent changes in the Government technical data package (TDP). Pending approval of an ECP, contractual relief should be requested in writing by the Contractor using a RFV. B. Refer to FAR Part 48 Value Engineering for cost saving improvements to the Technical Data Package (TDP). C. All ECPs submitted by the Contractor will be deemed routine. If the Contractor considers an ECP as an emergency or urgent; they shall include in their ECP submittal an explanation and all applicable supporting documentation. All ECPs will be reviewed for a determination on criticality, and, if concurred to be an emergency, the appropriate processing time-frame negotiated with the ESAs will be followed and the Contractor will be notified of anticipated response time. D. For ECPs, Specification Change Notices (SCNs) or RFV, the Contractor must submit the applicable documentation listed in sub-paragraphs D.(1) through D.(4)to the Administrative Contracting Officer(ACO), with an information copy to the Procuring Contracting Officer (PCO). Failure to submit a complete legible package may result in return of the ECP/RFV without processing. (1) Documentation listed in Paragraph 3.3.1 (for ECPs), 3.3.2 (RFV), 3.3.3 (for SCNs) or 3.3.4 (for Notices of Revision (NORs)) of the latest revision of EIA-649-1. (2) DD Form 1692 (current revision) for ECP. (3) DD Form 1694 (current revision) for RFV. (4) DD Form 1695 (current revision) for NOR. 4. DLA's responsibilities: A. Upon receipt of the ECP or RFV, the PCO will ensure that the applicable product specialist receives the copy from DCMA. B. Within five (5) working days from the date of receipt of the Contractor's ECP or RFV from DCMA, the PS must submit the requests and any supporting documentation via a 339 to the appropriate Engineering Support Activity (ESA), when applicable. C. Routine ECPs will be processed within 90 days from receipt by the ESA. RFVs will be evaluated and processed within 30 days from receipt by the ESA or as negotiated with the ESA. (1) The contractor will be notified in writing of approval by the return of an approved copy of the ECP or RFV. Approval will be reflected by signature of the contracting activity or a review activity specifically identified in the contract. (2) The contractor will be notified in writing of disapproval including reason(s) for disapproval. 5. For an approved RFV or an approved ECP, when the request affects the Contract, a modification will be issued to the contract incorporating the applicable requirement changes. Only a Contracting Officer is authorized to issue a modification incorporating the approved RFV and/or ECP. 6. Questions regarding the status of previously submitted ECP or RFV should be directed to the PCO. 7. The submission of an ECP or RFV by the Contractor does not affect the required delivery date of the contract. If a delivery date change is needed, it must be negotiated with the Contracting Officer and documented via modification to the contract. 8. The period of time for evaluation and approval/disapproval of an ECP and/or a RFV, as specified in Paragraph 4. C., shall not constitute excusable delay in the performance of this Contract by the Contractor or in any way relieve the contractor from compliance with the contract delivery schedule. The submission of an ECP and/or RFV by the Contractor shall not preclude the Government from exercising its rights under any clause of the Contract. (End) REFERENCE NUMBER CA060 NO DATA IS AVAILABLE. THE ALTERNATE OFFEROR IS REQUIRED TO PROVIDE A COMPLETE DATA PACKAGE INCLUDING DATA FOR THE APPROVED AND ALTERNATE PART FOR EVALUATION.