Exhibit_A_Statement_of_Work_10-18-2017.pdf

Statement of Work (SOW)

SPRBL1-18-Q-0010

18 October 2017

1.0 Scope. This Statement Of Work (SOW) defines the efforts required to produce the items required by this solicitation in accordance with the documents called out in the requirements section of the SOW. The items being purchased are modules and subassemblies of the AN/TPN-31, Air Traffic, Navigation, Integration, and Coordination System (ATNAVICS) and AN/FPN-67, Fix Base Precision Approach Radar (FBPAR).

2.0 Applicable Documents. The following documents are applicable to the extent cited.

2.1 Military Standards

Document No Document Title Applicability MIL-STD-129P(4) Military Marking for Shipment and

Storage Required

MIL-STD-130N Identification Marking of U.S.

Military Property

Required

MIL-STD-3046 Standard Practice Configuration Management, dated 6 March 2013

Required

2.2 Other Department of Defense Documents

Document No Document Title Applicability 57045-A-1006 System Specification for Air traffic

Navigation, Integration and Coordination System(ATNAVICS) and fixed Base Precision Approach Radar (FBPAR), Revision J, dated 28 September 2009

Required

DI-MGMT-81804A Item Unique Identification (IUID) Marking Activity, Validation and Verification Report

Required

DI-SESS-81656

(DMSMS)

Source Data For Forecasting Diminishing Manufacturing Sources and Material Shortages

DI-SESS-81880

Engineering Change Proposal

(ECP)

DI-MISC-80711A

Scientific and Technical Reports

AG00000601

CECOM Special Packaging Instruction

ANSI/ISO/ASQ(E) Q9001-2008 American National Standard, Required

Quality Management Systems-Requirements November 15 2008

2.3 Commercial Documents

Document No Document Title Applicability ISPM Number 15

Regulation of Wood Packaging Material in International Trade (2009)

Required

ASTM D3951-10 Standard Practice for Commercial Packaging

3.0 Requirements. When requested by the government via a Delivery Order, the contractor shall produce and test the items listed in Attachment 1 in the quantity set forth in Section B of the schedule and in accordance with Documents listed in Attachment 1 of this SOW. In the event of a conflict between the requirements of this SOW and any drawings for the item on contract, the requirements of this SOW shall govern. The Contractor shall make available for review upon request the acceptance and manufacturing documents listed in Attachment 1.

3.1 Requirements for Item Marking.

3.1.1. Part Number Marking. Each item delivered under contract, along with each assembly, sub assembly, and module, shall be legibly marked with the appropriate part number and manufacturer’s identification. Hardware such as screws, nuts, bolts, etc., need not be marked. The marking shall become permanently part of the item after it is applied, and can be applied using deformation, tag, rubber stamp with permanent characteristics, etc.

The marking shall not interfere with proper operation of the item, and shall have no deleterious effect on the item. Any item deemed unsuitable for marking as outlined herein shall be identified to the Contracting Officer for resolution as to marking requirement. This requirement may be entirely met by existing marking requirements contained within the drawings or specifications cited in this contract.

3.1.2. NSN Marking. In addition to the marking required by para 3.1.1 above, each item on contract listed in Section B of the contract, shall be identified with its Government assigned NSN. The intent of this requirement is to ensure that using personnel can identify the circuit card or assembly when it is removed from its assembly, and when it is received from stock as a spare part. The marking can be on a paper label, placed in a location that will not harm the item. If guidance is necessary to implement this requirement, contact the Contracting Officer for guidance.

3.1.3. Serial Number Marking.

3.1.3.1. Any item or subassembly which contains a serialization requirement shall have serial numbers applied to each item in the place provided (generally on a nameplate/serial number plate). In addition, the contractor shall obtain a block of serial numbers from the Government within 30 days of request from:

Commander, US Army Communications-Electronics Command

ATTN: AMSEL-LC-LCE-SAM

Aberdeen Proving Ground 21005

The contractor shall include the following information in the request:

1) Contract Number

2) Quantity of item on contract

3) Item’s part number as noted in Section B of the contract.

4) Contractor’s name and address.

3.1.3.2 The contractor shall maintain an accurate, current list of serial numbers for all manufactured items under this contract. Dates of manufacture, substitutions, shop changes, etc. shall be included on this list. The list shall be available for inspection by the PCO or government representative at any time during the life of the contract and for a period of 3 years following the completion of the contract.

3.2 Requirements for Item Unique Identification (IUID). The contractor shall mark all contract deliverables (see attachment 2 of this SOW) In Accordance With (IAW) DFARS clause 252.211-7003 in Section F of this contract and the following requirements.

3.2.1 IUID Marking.

3.2.1.1. New items: The contractor shall provide IUID, or DoD recognized equivalent, for all items delivered with an acquisition cost of $5000 or more, or any item the Government requires to be serial numbered. For long term contracts, the Contractor shall implement IUID markings IAW MIL-STD-130N for any item that will exceed the $5,000.00 unit price for any range quantity or contract year. This requirement is effective throughout the life of this contract.

3.2.1.2. The contractor shall also provide IUID, or DoD recognized equivalent, for all items delivered that are marked with a Government provided serial number in accordance with paragraph 3.1.3.1.

3.2.1.3 Commercial Markings. All other items shall have acceptable commercial markings that meet the guidelines in Department of Defense (DoD) Guide to Uniquely Identifying Items http://www.acq.osd.mil/dpap/pdi/uid/index.html.

3.2.1.4 Permanency and Legibility. The IUID marking and identification plates, tags, etching, or labels when used on equipment, parts, assemblies, subassemblies, units, sets, groups, or kits shall be as permanent as the normal life expectancy of the item and be capable of withstanding the environment, test, cleaning, repair, and rebuild procedures specified for the item. Legibility shall be as required and verified for ready readability per

MIL-STD-130N.

3.2.1.5 Deleterious Effect. Marking of items shall be accomplished in a manner that will not adversely affect the life and utility of the item. Marking materials creating hazardous conditions shall not be used. Placement and choice of the marking shall not create hazardous conditions.

3.2.1.6 Mandatory Information Reporting for all items requiring IUID marking. The contractor shall include the National Stock Number (NSN), if the item has a NSN, the Serial Number marked on the item, if a Serial Number is marked on the item, the original part number, the current part number (only if not the same as the original part number), the current part number effective date (only if the current part number is used) and the USARMY as the SERVICE /AGENCY/COMMAND data element in the information reported to the IUID Registry, in addition to the information required to be reported to the IUID Registry by DFARS clause 252.211- 7003.

3.21.6.1 Wide Area Workflow (WAWF) users shall report this mandatory information to the IUID Registry by Direct submission via an X12 Ship Notice/Shipment and Billing Notice (856/857) transaction, an IUID XML http://www.acq.osd.mil/dpap/pdi/uid/index.html transaction, an IUID flat file transaction or a WAWF IUID Material Inspection and Receiving Report/Combo UDF through the Global Exchange (GEX) Service, or manually, via the IUID Web Entry Site at http://www.bpn.gov/iuid. For WAWF users, these methods do not replace the current WAWF interaction, but are performed in addition to it after the shipment has been accepted to provide IUID data that cannot be provided via WAWF.

3.2.2-The contractor shall provide a report of all the data reported to the IUID Registry for the first item delivered for all CLINs and SLINS items that require IUID marking in accordance with this statement of work in a IUID Marking Registration Report in accordance with the CDRL for DI-MGMT-81804A.

3.2.2.1 The IUID Marking Registration Report tabular report shall include the following alphanumeric fields:

3.2.2.1.1 Unique Item Identifier.(UII).

3.2.2.1.2 UII type.

3.2.2.1.3 Issuing agency code (if concatenated unique item identifier is used).

3.2.2.1.4 Enterprise identifier (if concatenated unique item identifier is used).

3.2.2.1.5 Original part number (if there is serialization within the original part number).

3.2.2.1.6 Lot or batch number (if there is serialization within the lot or batch number).

3.2.2.1.7 Current part number (optional and only if not the same as the original part number).

3.2.2.1.8 Current part number effective date (optional and only if current part number is used).

3.2.2.1.9 Serial number (if concatenated unique item identifier is used).

3.2.2.1.10 Government’s unit acquisition cost.

3.2.2.1.11 Unit of measure.

3.2.2.1.12 National Stock Number (NSN)

3.2.2.1.13 Serial Number marked on the item, if a Serial Number marked on the item

3.2.2.1.14 Service/Agency/Command.

3.2.2.2 When IUID, or DoD recognized equivalent is required by this contract for embedded subassemblies, components, or parts, the IUID Marking Registration Report tabular report for embedded subassemblies, components, and parts that require IUID or DoD unique item identification shall include, the following information:

3.2.2.2.1.Unique item identifier of the parent item that contains the embedded subassembly, component, or part.

3.2.2.2.2 Unique item identifier of the embedded subassembly, component, or part.

3.2.2.2.3.Unique item identifier type.

http://www.bpn.gov/iuid

3.2.2.2.4 Issuing agency code (if concatenated unique item identifier is used).

3.2.2.2.5 Enterprise identifier (if concatenated unique item identifier is used).

3.2.2.2.6 Original part number (if there is serialization within the original part number).

3.2.2.2.7 Lot or batch number (if there is serialization within the lot or batch number).

3.2.2.2.8 Current part number (optional and only if not the same as the original part number).

3.2.2.2.9 Current part number effective date (optional and only if current part number is used).

3.2.2.2.10 Serial number (if concatenated unique item identifier is used).

3.2.2.2.11 Description.

3.2.2.2.12 National Stock Number (NSN)

3.2.2.2.13 Serial Number marked on the item, if a Serial Number marked on the item

3.2.2.2.14 Service/Agency/Command.

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 Advise 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: 0001

0002 A TDP TM OTHER MGMT

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

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

E001 Item Unique Identification (IUID) Marking Activity, Validation and Verification Report

IUID Marking Registration Report

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

TOTAL PRICE

DI-MGMT-81804A

(see Block 16) SOW PARA. 3.2.2 AMSEL-LC-LCE-SAM

AMSEL-LCL-M

INSER

T

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

see item

ASREQ see item 16 b. COPIES

SECT.

B

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

N/A N/A N/A Reg

Repro

16. REMARKS:

Item 4: Delete the second and third sentences in the USE/relationship paragraph. Delete Requirements paragraphs 1.

Through 5. of Data Item Description (DID) and prepare in accordance with this CDRL & the Statement of Work paragraphs

3.2.2.1 and 3.2.2.2.

Item 12: Delivery of shall be NLT 14 days after government acceptance of the items.

Item 14:. Each draft and the final submissions shall be delivered in a format, compatible with Microsoft Office 2007 software delivered by e-mail and by CD-R, CD+R Compact Disc, DVD-R or DVD+R 4.7GB Digital Versatile Disc. Alternative delivery media may be discussed with the Contracting Officer prior to delivery.

AMSEL-LC—LCE-SAM

AMSEL-LCL-M

CARLOS.DIAZRIVERA.

CIV@MAIL.MIL

JACOB.S.DOZIER.CIV.@

MAIL.MIL

ROXANNA.M.BROWN-

MELLO.CIV@MAIL.MI

L

15. TOTAL 5 5 0

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

Carlos Diaz Electronics Engineer

18 October

Anthony D. Santarsiero Chief Airborne Mission/Night Vision Branch

Based upon DD Form 1423-1, 1 Jun 90 mailto:carlos.diazrivera.civ@mail.mil mailto:carlos.diazrivera.civ@mail.mil mailto:roxanna.m.brown-mello.civ@mail.mil mailto:roxanna.m.brown-mello.civ@mail.mil

3.2.3 IUID Coding. IUID markings and readability requirements shall comply with MIL-STD-130N.

3.2.3.1 Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD 130N. First priority is the 2D data matrix symbol (machine readable) IUID is the minimum requirement when there are severe space limitations. The second priority is the human readable characters. The third priority is the Linear Bar Code.

3.2.3.2 If the technical data has not specified the marking location, markings shall be located such that they are visible during item use, provided that sufficient space is available, and does not interfere with equipment operations.

3.2.3.3 If items are not described by Government Product Technical Data (i.e. Commercial Items), the contractor shall submit diagrams showing placement and description of the IUID marking and applicable installation and processing instructions for government review and approval IAW with CDRL for DI-MISC- 80711A and this SOW.

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 Advise 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:0001

0002 A TDP TM OTHER MISC

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

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

E002 Scientific and Technical Reports

IUID Marking Diagram/Instructions

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

TOTAL PRICE

DI-MISC-80711A

(see Block 16) SOW PARA. 3.2.3.3 AMSEL-LC-LCE-SAM

AMSEL-LCL-M

INSER

T

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

See item

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

N/A See item 16

Item 4: Delete Block 10.2 of Data Item Description (DID) and prepare in accordance with this CDRL & the Statement of Work.

Item 12: Delivery of draft shall be 120 after award of Delivery Order. Government has 30 days to review/comment.

Item 13: Delivery of final shall be 30 days after receipt of Government comments. Government has 60 days to determine acceptance. Contractor to submit DD250 upon acceptance of IUID Marking Diagram/Instructions.

Item 14: Each draft and the final submissions shall be delivered in a format, compatible with Microsoft Office 2007 software delivered by e-mail and by CD-R, CD+R Compact Disc, DVD-R or DVD+R 4.7GB Digital Versatile Disc. Alternative delivery media may be discussed with the Contracting Officer prior to delivery.

AMSEL-LC-LCE-SAM

AMSEL-LCL-M

CARLOS.DIAZRIVERA.

CIV@MAIL.MIL

JACOB.S.DOZIER.CIV.@

MAIL.MIL

ROXANNA.M.BROWN-

MELLO.CIV@MAIL.MI

L

15. TOTAL 5 5 0

Based upon DD Form 1423-1, 1 Jun 90 mailto:carlos.diazrivera.civ@mail.mil mailto:roxanna.m.brown-mello.civ@mail.mil

3.2.3.4 The contractor shall maintain an accurate, current list of IUIDs for all manufactured items on this contract. Dates of manufacture, substitutions, shop changes, etc. shall be included on this list. The list shall be available for inspection by the PCO or other Government representative at any time during the life of this contract. The contractor shall provide this list to the government at the end of the contract.

3.2.4 Correction of Noncompliant Equipment and Technical Data.

3.2.4.1 If this contract contains configuration control requirements, the contractor shall initiate the appropriate configuration control document to correct all affected drawings/specifications which conflict with or omit the marking requirements stipulated above.

3.2.4.2 If configuration control requirements do not apply and the equipment on order is defined by technical data which conflicts with or omits the marking requirements stated above, the contractor shall advise the PCO.

Such advice shall list the number of each deficient drawing/specification and a brief description of the deficiency.

3.2.4.3 If the item on order is defined by existing Government technical documentation and such documentation is in conflict with the requirements of this SOW, production of equipment with revised markings shall not proceed until Government approval is received.

3.2.5 Government Purchase of Product/Technical Data.

3.2.5.1 Specifications. If the Government is procuring any equipment specification(s) on this contract, such specification(s) shall include a requirement to mark the appropriate items with IUID.

3.2.5.2 Drawings. If the Government is procuring engineering drawings or drawing revisions on this contract, the contractor shall include IUID marking requirements on each applicable drawing. Location shall be depicted on the pictorial and other details presented in the notes.

3.2.6 Pricing of IUID Requirements. All efforts required by this SOW and contract, including, but not limited to, the preparation of ECPs or notification of marking deficiencies, serial number data reporting at end of contract and the actual marking of hardware, will be included in the base contract price.

3.3. Additional Higher-Level Quality Requirements using ANSI/ISO/ASQ(E) Q9001-2008.

3.3.1 The government shall have access to the contractor's quality manual at the contractor's facility at any time.

3.3.2 The Government has the right to audit and/or examine the contractor’s quality management system, inspection system and quality management system documentation including documented statements of a quality policy, documented quality objectives, quality manual, documented procedures and records required by the quality management system standard, documents including records determined by the contractor to be necessary to ensure the effective planning, operation and control of its processes. The documentation can be in any form or type of medium and software. Government has the right to audit, examine and test hardware used for quality management, test or inspection. The Government's audit and/or examination shall be on the premises of the contractor or supplier, to the extent practicable, at all places and times. The Government’s audits and/or examination of the contractor’s quality management system, inspection system and quality management system documentation will be conducted in a manner that will not unduly delay the contract work. The Government's audit and/or examination, whether exercised or not, does not relieve the Contractor of the obligations under the contract.

3.3.2.1 If the Government performs audits and/or examinations of the contractor’s quality management system, inspection system, quality management system documentation and test hardware used for quality management, test or inspection on the premises of the Contractor or a subcontractor, the Contractor shall furnish, and shall require subcontractors to furnish, at no increase in contract price, all reasonable facilities and assistance for the safe and convenient performance of these duties.

3.3.2.2 The Government’s right to audit and/or examine the contractor’s quality management system, inspection system and quality management system documentation including documented statements of a quality policy, documented quality objectives, quality manual, documented procedures and records required by the quality management system standard, documents including records determined by the contractor to be necessary to ensure the effective planning, operation and control of its processes will be limited to the contractor’s facility and also to suppliers facilities that provide products and/or services valued over 20% of the contract total cost.

3.3.2.3 Inspections and Test Records - The contractor shall maintain records (including subcontractor’s records) of all inspections and tests to demonstrate that the quality approach satisfies contract requirements. Records shall be made available to the Government for review upon request. Records shall be maintained for two years after contract completion.

3.4 Requirements for Configuration Control.

3.4.1 Configuration Baseline. The applicable Configuration Baseline (CB) for the listed Configuration Item (CI)/Computer Software Configuration Item (CSCI) is as follows:

CI/CSI CB

Part Numbers and NSNs listed in Columns 2 and 3 of Attachment 1.

1. System Specification for Air Traffic Navigation, Integration and Coordination System (ATNAVICS) and Fixed Base Precision Approach Radar (FBPAR), 57045-A-1006, dated 28 September 2009, Revision K.

2. Documents listed in Column 1 of Attachment 1.

3.4.2 Configuration. 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). 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. The contractor may use MIL-STD-3046 as guidance for establishing a Configuration Management Program.

3.4.3 Departures from CB. No changes or departures from the CB are acceptable except for changes or departures which are submitted in accordance with the Data Item for DI-SESS-81880, 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. Configuration Control shall be affected by the Configuration Control Documents (CCDs) as follows:

3.4.3.1 Engineering Change Proposal (ECP) includes both the engineering change and the supporting documentation by which the change is described and suggested. An ECP is a document used to describe, justify and (if approved) implement a proposed engineering change. ECPs shall be submitted using DD Form 1692 in accordance with DI-SESS-81880 and MIL-STD-3046. The contractor submitting the request for change shall prepare and submit DD Form1692 together with one or more DD Form 1695 (Notice of Revision) for each affected document.

3.4.3.1.1 Notice of Revision (NOR) A document submitted with an ECP that shows the detailed changes that must be made to specific technical drawings, specifications, Model Based Definition data, associated lists or other referenced documents, (one NOR per document). A NOR shall be submitted using DD Form 1695.

3.4.3.1.1.1 NOR Use/Relationship: An NOR describes the proposed changes to a technical document being requested by an ECP (one NOR per document) following approval of an ECP.

3.4.3.1.1.2 NOR Content: The NOR shall be prepared in accordance with MIL-STD-3046 . Other formats and submittal means are acceptable provided the data content requirements of MIL-STD-3046 are met.

3.4.3.1.2 Changes to specifications shall be submitted in a NOR used to delineate the exact change(s) in a specification that will be distributed to users when the ECP is approved except military or federal specifications. The proposed change to a specification is submitted as part of the ECP. The ECP process is not used for a proposed change to a military or federal document, only a Request for Variation can be used for those documents.

3.4.3.1.3 Value Engineering Change Proposal (VECP) - The contractor shall follow the guidance in Section I of this contract for VECPs. The contractor shall uniquely and sequentially identify (including the use of the contract number) each VECP. The identification number should use less than 16 characters.

3.4.3.2 Request For Variation (RFV). A RFV is a specific written authorization to depart from a particular requirement(s) of an item’s approved configuration documentation 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. A RFV shall be submitted using DD Form 1694. The Government may require consideration for any RFV.

3.4.3.2.1 RFV Use/Relationship: An RFV describes a proposed departure from (i.e. a nonconformance with) the contractually-specified configuration documenation for a specific numberof units for a specified period of time.

A RFV is the MIL-STD-3046 term for what is formerly known as a Request for Deviation (RFD) or a Request for Waiver (RFW). A RFV enables the Government to determine the impact on performance, operational readiness, logistics support or other affected areas.

3.4.3.2.2 RFV Content: The RFV shall be prepared in accordance with MIL-STD-3046. Other formats and submittal means are acceptable provided the data content requirements of MIL-STD-3046 are met. The RFV content shall include the consideration the government is due to the nonconformance.

3.4.3.3 Contractor shall provide all supporting program or cost data with the CCD. The contractor shall uniquely and sequentially identify (including the use of the contract number) each ECP, NOR, or RFV. The identification number should use less than 16 characters.

3.4.4 Identification of Authorized Personnel. The contractor shall identify to the PCO, Administrative Contracting Officer (ACO), and the technical office identified on the DD Form 1423 for DI-MISC-80711A, the name(s) of the official(s) of its organization who are authorized to submit CCDs 30 Days after Contract (DAC).

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:0001

0002 A TDP X TM OTHER

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

ATNAVICS/FBPAR

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

E003 Engineering Change Proposal (ECP) Configuration Control

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

TOTAL PRICE

DI-SESS-81880 SOW Para 3.4.3 AMSEL-LC- SAM

AMSEL-LC-LEO-E-ET

AMSEL-LC-LEO-E-AV

INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

SEE

ITEM 16

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

16. REMARKS: Data Item Description DI-MISC-81880: Use as wrtten for an ECP. Delete the first two paragraphs under the Use/Relationship section and replace with SOW Para 3.4.3.1.1.1 for a NOR and SOW Para 3.4.3.2.1 for a RFV.

Delete paragraph 2. in the Requirements section and relace it with SOW Para.

3.4.3.1.1.2 for a NOR and SOW Para 3.4.3.2.2 for a RFV.

The contractor shall prepare and submit Configuration Control Documents in accordance with the SOW for Configuration Control (Para 3.4.3) when a change to or 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 a format, compatible with Microsoft Office 2007 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. Alternate formats may be allowed subject to Government review and approval.

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.

AMSEL-LC-LCE-SAM

PCO

ACO

QAR

AMSEL-LC-LEO-E-ET

AMSEL-LC-LEO-E-AV*

*1 COPY VECP ONLY

CARLOS.DIAZRIVERA.

CIV@MAIL.MIL

15. TOTAL 0 7 0

Based upon DD Form 1423-1, 1 Jun 90

3.4.5 Documentation. The contractor shall document by serial number each products configuration, applicable documentation, maintenance support requirements and spares in relation to the contractor’s configuration baseline. The data in use shall be available for government review and use.

3.4.6 Use of CB Data. The contractor shall assure that all necessary contractors’ activities have access to and use of the contractually specified configuration baseline(s), approved changes and departures, and effectivity data. The data in use shall be available for government review and use.

3.5 Requirements for Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.5.1 The contractor shall develop the forecasting source data that will enable the identification, forecasting and management of piece part obsolescence impacts and mitigations as a part of the Department of Defense (DoD) Program Managers’ Total System Life Cycle Management responsibilities. This data is planned for use in DMSMS forecasting tools using a common data standard that enhances efficiency across programs that may share the data on common items. The data may be obtained during any program life cycle phase using sources such as the preferred parts list, build-of materials, vendor surveys, inspections, etc. The DMSMS data shall be developed in accordance with this SOW and the CDRL (DD Form 1423) for DI-SESS-81656.

(1 Data Item)

Form Approved

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:0001

0002 A TDP TM OTHER SESS

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

ATNAVICS/FBPAR Raytheon

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

E004 Source Data For Forecasting Diminishing Manufacturing Sources and Material Shortages (DMSMS)

DMSMS Data

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

TOTAL PRICE

DI-SESS-81656 SOW Para 3. 5.1 AMSEL-LC-LCE-SAM INSER T

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

SEE

ITEM 16

Semiannual SEE ITEM 16 b. COPIES

SECT.

B

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

SUBMISSION

a. ADDRESSEE

Draft Final

SEE ITEM

SEE ITEM 16 ^

Item 12: Delivery of DMSMS Data shall be within 60 days after award of contract. Subsequent reports to be submitted semiannually (every 180 days) until conclusion of contract.

Government has 60 days to review and determine acceptance.

See DI-SESS-81656 for DMSMS Data Format and Content requirements.

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

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.

AMSEL-LC-LCE-SAM

AMSEL-LC-LEO-E-IE

CARLOS..DIAZRIVERA.CIV

@MAIL.MIL

15. TOTAL 3 0

DD Form 1423-1, 1 Jun 90

3.6. Requirements for Packaging. Preservation, packing and marking for shipment shall be in accordance with Section "D" of the contract. The packaging for all Circuit Card Assemblies shall be in accordance with CECOM Special Packaging Instruction AG00000601. Level of Preservation (LOP): Military, Level of Pack (LPK): Minimal, Quantity Unit Pack (QUP): 001. The packaging/packing for all remaining components shall be in accordance with ASTM D3951-10, Standard Practice for Commercial Packaging. Level of Protection (LOP): Commercial, Level of Pack (LPK): Commercial, Quantity Unit Pack (QUP): 001. Some supplies may need Military packaging depending on the destination and intended use.

Packaging requirements for those items will be provided with the delivery order. Marking for all items shall be in accordance with MIL-STD-129P with Change 4. Radio Frequency Identification (RFID) Requirements shall be IAW Section "F" clause, DFARS 252.211-7006, of the contract. MIL-STD-129P with Change 4 is applicable. Wood Packaging Material (WPM) shall meet the requirements below.

3.6.1. Wood packaging material (WPM) includes but is not limited to pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frame and cleats. This requirement excludes materials that have undergone a manufacturing process, such as corrugated fiberboard, plywood, particleboard, veneer, and oriented strand board

(OSB).

3.6.2. All WPM shall meet the requirements of International Standards for Phytosanitary Measures (ISPM) Number 15, Regulation of Wood Packaging Material in International Trade. DoD shipments inside and outside of the United States shall meet the requirements of ISPM 15 whenever WPM is used to ship DoD cargo.

3.6.3. All WPM shall comply with the official quality control program for heat treatment (HT) or kiln dried heat treatment (KD HT) IAW American Lumber Standard Committee (ALSC), Incorporated, Wood Packaging Material Program and WPM Enforcement Regulations (see http://www.alsc.org/).

3.6.4. All WPM shall include certification/quality markings IAW the ALSC standard. Markings shall be placed in an unobstructed area that will be readily visible to inspectors. Pallet markings shall be applied to the stringer or block on diagonally opposite sides of the pallet and be contrasting and clearly visible. All containers shall be marked on a side other than the top or bottom, contrasting and clearly visible. All dunnage used in configuring and/or securing the load shall also comply with ISPM 15 and be marked with an ASLC approved DUNNAGE stamp.

3.6.5. Failure to comply with these requirements may result in refusal, destruction, or treatment of materials at the point of entry. The Government reserves the right to recoup from the contractor any remediation costs incur.

3.7 Obsolescence In the event that the contractor determines that one or more LRUs are obsolete or cannot be procured, the contractor shall notify the Government, via letter, within five (5) calendar days from date the obsolescence is noted. This notice shall include the contractor’s written recommendation to correct the problem and should recommend one of the following courses of action: (a) identify alternate sources within industry, or (b) redesign hardware. The contractor shall also include with the recommendations the contractor’s assessment of any cost and schedule impacts associated with the recommendation. The Government will respond within 30 days approving/disapproving Contractor’s recommended course of action. If the contractor’s recommendation is approved by the government, the contractor shall effect the required configuration changes in accordance with paragraph 3.4, and related subparagraphs, of this SOW.

http://www.alsc.org/