Optex Systems Holdings Inc (Form: 8-K, Received: 11/08/2011 12:23:24)

AWARD/CONTRACT	1. This Contract Is A Rated Order Under DPAS (15 CFR 700)	Rating DOA4	Page 1	Of	36 Pages
2. Contract (Proc. lust. ldent.) No.	3. Effective Date	4. Requisition/Purchase Request/Project No.

SPRDLl-12-C-0023	20110CT24	SEE SCHEDULE

5. Issued By	Code	SPRDLl	6. Administered By (If Other Than Item 5)	Code
	S4402A

DLA LAND – WARREN	DCMA DALLAS
ZGA	600 N PEARL STREET SUITE 163 0
ROBERT HARRISON (586) 282-3200	DALLAS TX 75201-2843
WARREN", MI 48397-5000
HTTP://CONTRACTING.TACOM ARMY. MIL
WEAPON SYSTEM: WPN SYS: JE

e-mail address: ROBERT.HARRISON9@US ARMY.MIL

SCD c

PAS

NONE

ADPPT

HQ0339

7. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)	8. Delivery
OPTEX SYSTEMS INC.	D FOB Origin	EJ Other (See Below)
142 0 PRESIDENTIAL DR	9. Discount For Prompt Payment
RICHARDSON, TX 75081-2439


	10. Submit Invoices	Item
TYPE BUSINESS: Other Small Business Performing in U.S.	(4 Copies Unless Otherwise Specified)	12

Code OBK64

Facility

Code

To The Address Shown In:

11. Ship To/Mark For	Code	12. Payment Will Be Made By	Code 1 HQ0339
SEE SCHEDULE		DFAS-COLUMBUS CENTER
		DFAS-CO WEST ENTITLEMENT OPERATIONS
		P.O. BOX 182381
		COLUMBUS, OH 43218-2381


13. Authority For Using Other Than Full And Open Competition:	14. Accounting And Appropriation Data

D 10 U.S.C. 2304(c)( )	D 41 U.S.C. 253(c)( )	SEE SECTION G
15A. Item No.	15B. Supplies/Services	15C. Ouantitv	15D. Unit	15E. Unit Price	15F. Amount
SEE SCHEDULE	CONTRACT TYPE:	KIND OF CONTRACT:
	Firm-Fixed-Price	Supply Contracts = d p iced Orders

15G. Total Amount Of Contract + $1,152,272.20

16 Table Of Contents

(X)	Sec.	Description	P3l!e(')	(X)	Sec.	Description	Paee(s)
		Part I - The Schedule		Part II - Contract Clauses
X	A	Solicitation/Contract Form	1	X	I	Contract Clauses	26
X	B	Supplies or Services and Prices/Costs	3	Part III- List Of Documents, Exhibits, And Other Attachments
X	C	Description/SpecsJWork Statement	6	X	J	List of Attachments	38
X	D	Packaging and Marking	8	Part IV- Representations And Instructions
X	E	Inspection and Acceptance	10		K	Representations, Certifications, and
X	F	Deliveries or Performance	13			Other Statements of Offerors
X	G	Contract Administration Data	20		L	Instrs., Conds., and Notices to Offerors
X	H	Special Contract Requirements	21		M	Evaluation Factors for Award

Contracting Officer Will Complete Item 17 Or 18 As Applicable

17. Contractor's Negotiated Agreement (Contractor is required to sign this document and return 2 signe<dopies to issuing office.) Contractor agrees to furnish and deliver all items or perform all the services set forth or otherwise identified above and on any continuation sheets for the consideration stated herein. The rights and obligations of the parties to this contract shall be subject to and governed by the following documents: (a) this award/contract, (b) the solicitation, if any, and (c) such provisions, representations, certifications, and specifications, as are attached or incorporated bv reference herein. (Attachments are listed herein.)

18. D Award (Contractor is not required to sign this document.) Your offer on Solicitation Number ____________________ including the additions or changes made by you which additions or changes are set forth in full above, is hereby accepted as to the items listed above and on any continuation sheets. This award consummates the contract which consists of the following documents: (a) the Government's solicitation and your offer, and (b) this award/contract. No further contractual document is necessary.

19A. Name And Title Of Signer (Type Or Print)

20A. Name Of Contracting Officer

MORRIS BELLEVILLE

MORRIS.BELLEVILLE@US .ARMY. MIL (586)282-3139

19B. Name of Contractor

19c. Date Signed

20B. United States Of America

20C. Date Signed

20110CT24

By				By	/SIGNED/
	(Signature of person authorized to sign)				(Signature of Contracting Officer)

AUTHORIZED FOR LOCAL REPRODUCTION	Standard Form 26 (Rev. 4/2008)
Previous edition is usable	Prescribed By GSA- FAR (48 CFR)53.214(a)

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 2 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

SECTION A - SUPPLEMENTAL INFORMATION

This solicitation contains a Restricted Technical Data Package (TDP). Please refer to Section C-1 52.210-4501 - DRAWINGS/SPECIFICATIONS for instructions on how to get access to restricted TDPs.

*** END OF NARRATIVE AOOOl

	g LQli ——————————— ill ——————————— — 1 —

A-1	52.204-4850 (TACOM)	ACCEPTANCE APPENDIX	APR/2011

(a) Contract Number SPRDLl-12-C-0023 is awarded to OPTEX Systems Inc.

(b) The contractor, in its proposal, provided data for various solicitation clauses, and that data has been added in this contract.

(c) Any attachments not included within this document will be provided by DLA Land Warren directly to the administrative contracting officer (ACO) via e-mail, as required. Technical data packages that are only available on CD-ROM will be mailed by DLA Land Warren to the ACO. Within one week of this award, any office not able to obtain attachments from TACOM's website (https://contracting.tacom.army.mil/) and still requiring a copy, can send an email request to the buyer listed on the front page of this contract.

(d) The following Amendment(s) to the solicitation are incorporated into this contract: 0001

[End of Clause]

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 3 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

0001

NSN: 1240-01-476-2613

FSCM: 19200

PART NR: 9377820-2

SECURITY CLASS: Unclassified

OOOlAA

PRODCUTION QUALITY

14,052,10000

1,152,272.20

NOUN: HEAD ASSEMBLY,GUNNE

PRON: M112A243Ml PRON AMD: 06 ACRN: AA

AMS CD: SM2B1100000

THERE IS A REQUIREMENT FOR FIRST ARTICLE TESTING.

See Data Item SubCLIN OOOlAB: First Article Test Report.

(End of narrative BOOl)

2ri li2M 2 L L l

TOP DRAWING NR: 9377820-2

DATE: 30-MAR-2011

.£.§Qk.§2i!lli_@Q____ !1 .rl;i:gg

PACKAGING/PACKING/SPECIFICATIONS:

SEE PACKAGING REQUIREMENTS CLAUSE

LEVEL PRESERVATION: Military

LEVEL PACKING: B

Inspection and Acceptance

INSPECTION: Origin ACCEPTANCE: Origin

Deliveries and performance

DOC

SUPPL

R.ille_.QJ:2 .!1I1.02RIT

EJ2;QR__ IQ_ Q ; Q MARK FOR TP CD

001 W52H091063H745

W562RP J 2

;Q.ille_fill1 Q;Q Q:rlMr'ITTL :QhY b.ET.f!R_bN_AR;Q

001 82 0330

FOB POINT: Destination

SHIP TO:

(W562RP)

SR WOLX ARMY GENERAL SUPPLY

CENTRAL RECEIVING POINT

7 FRANKFORD AVE

ANNISTON,AL,36201-4199

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 4 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

OOOlAB

DATA ITEM: FIRST ARTICLE TEST REPORT

$ **NSP**

1EA = 1 Each Test

Report on Contractor

Performed First

Article Test (FAT)

NSP = Not Separately

Priced.

(End of narrative BOOl)

FIRST ARTICLE TEST REPORT, PURSUANT TO THE

REQUIREMENTS OF THE CLAUSE ENTITLED "FIRST

ARTICLE APPROVAL - CONTRACTOR TESTING.

(SEE SECTION I OF THIS DOCUMENT.)

(End of narrative COOl)

Packaging and Marking

Inspection and Acceptance

INSPECTION: Origin ACCEPTANCE: Destination Goverrrment Approval/Disapproval Days: 30

Deliveries or Performance

DOC

SUPPL

REL CD

MILSTRIP

ADDR

SIGCD

MARK FOR

TPCD

001

DEL REL CD

QUANTITY

DAYS AFTER AWARD

001

0220

FOB POINT: Destination

SHIP TO:

(Y00006)

SEE FIRST ARTICLE TEST CLAUSE

FOR DISTRIBUTION

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 5 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

ITEM NO	SUPPLIES/SERVICES		QUANTITY	UNIT	UNIT PRICE	AMOUNT

OOOlAC	DATA ITEM: CDRL - DD FORM M23 (EXHIBIT A)			EA	$ NSP	$ NSP

	Submit m Accordance with Exhibit A a a necessary:

	AOOl - Engineering Change Proposal (ECP)

	A002 - Request for Deviation (RFD)

	A003 - Notice of Revision (NOR)

	(End of narrative EO 01)

	Inspection and Acceptance
	INSPECTION: Destination	ACCEPTANCE: Destination

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 6 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

	Regulatory Cite	Title	Date

C-1	52.210-4501 TACOM (RI)	DRAWINGS/SPECIFICATIONS	MAR/1988

In addition to the drawing(s) and/or specifications listed below, other documents which are part of this procurement and which apply to Preservation/Packaging/Packing and Inspection and Acceptance are contained elsewhere.

Drawings and Specifications in accordance with Technical Data Package/Technical Data Package Listing 9377820-2:19200, with revisions in effect as of 03/30/2011, are applicable to this procurement with the following exceptions:

DWG 9376993 - VENDORS 1, 4, 5 ARE THE ONLY VENDOROS QUALIFIED TO COAT,

INFRARED-EXTERIOR, PER DWG 9376977. REMOVE VENDORS 2, 3

VENDOR	- MERGED WITH JDSU CUSTOMS OPTICS

VENDOR 4	NEW NAME & ADDRESS
	EXOTIC ELECTRO-OPTICS
	36570 BRIGGS ROAD
	MURRIETO, CA 92563

DWG 5705438 SHT 1 - REMOVE IN TITLE BLOCK SHEET NO - FROM: 1 OF 5 TO: 1 OF 4

DOCUMENT:	DELETE:	REPLACE WITH:
12932490	MIL-M-81594	AS81531
9377819	MIL-C-46168	MIL-DTL-53039
9377153	QQ-A-200/3	AMS-QQ-A-200/3
	QQ-A-200/8	AMS-QQ-A-200/8
10556186	QQ-A-225/6	AMS-QQ-A-225/6
	QQ-A-225/8	AMS4116 or AMS4117
11727998	QQ-A-225/6	AMS-QQ-A-225/6
	QQ-A-225/8	AMS4116 or AMS4117
9377153	QQ-A-225/6	AMS-QQ-A-225/6
9377151	QQ-A250/4	AMS-QQ-A-250/4
	AMS-QQ-A-250Ill	ASTM B209
10556186	QQ-P-35	ASTM A967
	SAE-AMS-QQ-A-225/8	AMS4116 OR AMS 4117
QS 9377819 cht 1	MIL-C-46168	MIL-DTL-53039

9377106, vendor part number of MULTISORB TECHNOLOGIES INC. should be "02-01069CG01", not "02-011069CG01"

FOR RESTIRCTED TDPs:

Technical data packages (TDPs) and any other related documents, if applicable, for this solicitation are restricted and can be accessed electronically Vla the Federal Business Opportunities website with valid contractor login credentials.

To access the TDP, click directly on the link provided below to be directed to the TDP. You may also copy and paste the link into your browser and hit the Enter key.

Once directed to the Federal Business Opportunities Website:

1)	Log on the FBO

2)	Log in your MPIN number

3)	If solicitation lS explicit, select "Request Explicit Access"

4)	If solicitation is Export Control, select "Verify MPIN"

5)	This will generate an email to the FBO System Administrator

6)	Please allow 2-3 working days to complete the FBO-TDP process from the FBO system

7)	The FBO Administrator will glve you access and you will receive a system generated email from FBO stating you now have permission for Vlewlng or downloading the TDP items.

TDP Link (URL):

https://www.fbo.gov/notices/243b7be58d99dab2b692a75177e0blf7

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 7 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

(CS6100)

(End of Clause)

C-2

52.211-4008

(TACOM)

DRAWING LIMITATIONS

NOV/2005

(a) The drawings supplied with this contract are rrQl shop or process drawings. They are engineering design drawings. They are adequate to permit manufacture, and:

(1) depict the completed (item(s), and

(2) serve as the basis for inspection of the completed item(s).

(b) These drawings DON'T cover intermediate drawings/specifications or steps in the manufacturing process. As a result, even if you meet all the dimensions and tolerances specified in the engineering design drawing for each individual part, a cumulative unacceptable fit for the contract item could result.

(c) YQ bR - EQN for producing the shop or process drawings needed to cover intermediate steps in the manufacturing process.

(d) You, the contractor, are responsible for obtaining all specifications and drawings necessary to manufacture the items being solicited in accordance with the TDP including all incorporated specifications and drawings. Delivery delays are not excusable where the contractor asserts that it did not have a specification or drawing and has failed to request, in writing, the specification from either the Contracting Officer or Contract Specialist prior to the solicitation closing date.

(e) If you fail to produce an end item with a cumulative fit that conforms to Government drawings, specifications or other supplemental manufacturing documentation, you'll be responsible for correcting this condition at no additional cost to the Government and no delivery schedule extension.

C-3

52.248-4502

TACOM (RI)

CONFIGURATION MANAGEMENT DOCUMENTATION

JUL/2001

The contractor may submit Engineering Change Proposals (ECPs), Value Engineering change Proposals (VECPs), (Code V shall be assigned to an engineering change that will effect a net life cycle cost), including Notice of Revisions (NORs), and Request for Deviations (RFDs), for the documents in the Technical Data Package (TDP). The contractor shall prepare these documents in accordance with the Data Item Descriptions cited in block 04 on the enclosed DD Form 1423, Contract Data Requirements List.

Contractor ECPs/\TECPs shall describe and justify all proposed changes and shall included NORs completely defining the change to be made. Contractors may also submit RFD, which define a temporary departure from the Technical Data package or other baseline documentation under Government control. The contractor shall not deliver any units incorporating any change/deviation to Government documentation until notified by the Government that the change/deviation has been approved and the change/deviation has been incorporated in the contract.

If the Government receives the same or substantially the same VECPs from two or more contractors, the contracts whose \TECP is received first will be entitled to share with the Government in all instant, concurrent, future, and collateral savings under the terms of the VE clause in the contract.

Duplicate \TECPs, which are received subsequently, will be returned to the contractor(s) without formal evaluation, regardless of whether or not the first VECP has been approved and accepted by the Goverrrment.

(CS7110)

(End of Clause)

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 8 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

SECTION D - PACKAGING AND MARKING

	Regulatory Cite	Title	Date

D-1	52.211-4501 TACOM (RI)	PACKAGING REQUIREMENTS (SPECIAL PACKAGING INSTRUCTIONS)	DEC/2007

A. Military preservation, packing, and marking for the item identified above shall be accomplished ln accordance with the specific requirements identified below, all the applicable requirements of, MIL-STD-2073-1, Revision D, Date 15 Dec 99 including Notice 1, dated 10 May 02 and the Special Packaging Instruction (SPI) contained in the TDP.

PRESERVATION: MILITARY

LEVEL OF PACKING: B

QUANTITY PER UNIT PACKAGE: 001

SPI NUMBER 9377820-2, Date 02-02-21 REV

B. Unitization: Shipments of identical items going to the same destination shall be palletized if they have a total cubic displacement of 50 cubic feet or more unless skids or other forklift handling features are included on the containers. Pallet loads must be stable, and to the greatest extent possible, provide a level top for ease of stacking. A palletized load shall be of a size to allow for placement of two loads high and wide in a conveyance. The weight capacity of the pallet must be adequate for the load. The pallet shall be a 40 x 48 inch, 4-way entry pallet although variations may be permitted as dictated by the characteristics of the items being unitized. The load shall be contained in a manner that will permit safe handling during shipment and storage.

C. Marking: In addition to any special markings called out on the SPI;

C.1. All unit packages, intermediate packs, exterior shipping containers, and, as applicable, unitized loads shall be marked in accordance with MIL-STD-129, Revision P, Change Notice 4, dated 19 Sep 2007 including bar coding and a MSL label. The contractor lS responsible for application of special markings as discussed in the Military Standard regardless of whether specified in the contract or not. Special markings include, but are not limited to, Shelf-life markings, structural markings, and transportation special handling markings. The marking of pilferable and sensitive materiel will not identify the nature of the materiel. Passive RFID tagging is required in all contracts that contain DFARS clause 252.211-7006. Contractors must check the solicitation and/or contract for this clause. For details and most recent information, see http://www.acq.osd.mil/log/rfid/index.htm for the current DoD Suppliers Passive RFID Information Guide and Supplier Implementation Plan. If the item has Unique Item Identifier (UII) markings then the concatenated UII needs to be 2D bar coded and applied on the unit package, intermediate and exterior containers, and the palletized unit load.

D. Heat Treabnent and Marking of Wood Packaging Materials: All non-manufactured wood used in packaging shall be heat treated to a core temperature of 56 degrees Celsius for a minimum of 30 minutes. The box/pallet manufacturer and the manufacturer of wood used as inner packaging shall be affiliated with an inspection agency accredited by the board of review of the American Lumber Standard Committee. The box/pallet manufacturer and the manufacturer of wood used as inner packaging shall ensure tractability to the original source of heat treabnent. Each box/pallet shall be marked to show the conformance to the International Plant Protection Convention Standard. Boxes/pallets and any wood used as inner packaging made of non-manufactured wood shall be heat-treated. The quality mark shall be placed on both ends of the outer packaging, between the end cleats or end battens; on two sides of the pallet. Foreign manufacturers shall have the heat treabnent of non-manufactured wood products verified in accordance with their National Plant Protection Organizations compliance program. In addition, wood used as dunnage for blocking and bracing, to include ISO containers, shall be ordered with ALSC certified marking for dunnage or the markings may be applied locally at two foot intervals.

E. This SPI has been validated and the method of preservation/packing has proven successful in meeting the needs of the military distribution system, including indeterminate storage and shipment throughout the world. Special instructions and/or tailoring of the SPI is detailed in the Supplemental Instructions below. A prototype package is required to validate the sizes and fit requirements of the SPI. Minor dimensional and size changes are acceptable provided contractor provides the PCO and ACO with notification 60 days prior to delivery. Any design changes or changes in the method of preservation that provide a cost savings without degrading the method of preservation or packing or affecting the serviceability of the item will be considered and responded to within 10 days of submission to PCO and ACO. Government reserves the right to require testing to validate alternate industrial preservation methods, materials, alternate blocking, bracing, cushioning, and packing.

F. Hazardous Materials (as applicable):

F.1..Hazardous Materials is defined as a substance, or waste which has been determined by the Secretary of Transportation to be capable of posing an unreasonable risk to health, safety, and property when transported in commerce and which has been so designated. (This includes all items listed as hazardous in Titles 29, 40 and 49 CFR and other applicable modal regulations effective at the time of shipment.)

F.2. Unless otherwise specified, packaging and marking for hazardous material shall comply with the requirements for the mode of transport and the applicable performance packaging contained in the following documents:

—International Air Transport Association (IATA) Dangerous Goods Regulations

—International Maritime Dangerous Goods Code (IMDG)

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 9 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

—Code of Federal Regulations (CFR) Title 29, Title 40 and Title 49

—Joint Service Regulation AFJMAN24-204/TM38-250/NAVSUPPUB 505/MCO

P4030.19/DLAM 4145.3 (for military air shipments).

F.3. If the shipment originates from outside the continental United States, the shipment shall be prepared in accordance with the United Nations Recommendations on the Transport of Dangerous Goods in a manner acceptable to the Competent Authority of the nation of origin and in accordance with regulations of all applicable carriers.

F.4. When applicable, a Product Material Safety Data Sheets (MSDS) is required to be included with every unit pack and intermediate container and shall be included with the packing list inside the sealed pouch attached to the outside of the package.

G. SUPPLEMENTAL INSTRUCTIONS: N/A

(DS6419)

(End of Clause)

CONTINUATION SHEET	Reference No. of Document Being Continued		Page 10 of 36
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

SECTION E - INSPECTION AND ACCEPTANCE

	g LQli ——————————— ill ——————————— — 1 —

E-1	52.246-2	INSPECTION OF SUPPLIES—FIXED-PRICE	AUG/1996

E-2	52.246-16	RESPONSIBILITY FOR SUPPLIES	APR/1984

E-3	52.246-11	HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT	FEB/1999

The Contractor shall comply with the higher-level quality standard selected below. [If more than one standard is listed, the offeror shall indicate its selection by checking the appropriate block.

Title	Number	Date	Tailoring
ISO	9001:2008	15 Nov 2008	Tailored by excluding paragraph 7.3

(End of Clause)

E-4

52.209-4512

FIRST ARTICLE TEST (CONTRACTOR TESTING)

MAR/2001

a. The first article shall be examined and tested in accordance with contract requirements, the item specification(s), Quality Assurance Provisions (QAPs) and all drawings listed in the Technical Data Package. The first article shall consist of: Two (2) of Part# 9377820-2

b. The first article shall be representative of items to be manufactured using the same processes and procedures and at the same facility as contract production. All parts and materials, including packaging and packing, shall be obtained from the same source of supply as will be used during regular production. All components, subassemblies, and assemblies in the first article sample shall have been produced by the Contractor (including subcontractors) using the technical data package applicable to this procurement.

c. The first article shall be inspected and tested by the contractor for all requirements of the drawing(s), the QAPs, and specification(s) referenced thereon, except for:

(1) Inspections and tests contained in material specifications provided that the required inspection and tests have been performed previously and certificates of conformance are submitted with the First Article Test Report.

(2) Inspections and tests for Military Standard (MS) components and parts provided that inspection and tests have been performed previously and certifications for the components and parts are submitted with the First Article Test Report.

(3) Corrosion resistance tests over 10 days in length provided that a test specimen or sample representing the same process has successfully passed the same test within 30 days prior to processing the first article, and results of the tests are submitted with the First Article Test Report.

(4) Life cycle tests over 10 days in length provided that the same or similar items manufactured using the same processes have successfully passed the same test within First Article Test Report. year prior to processing the first article and results of the tests are submitted with the

(5) Onetime qualification tests, which are defined as a one-time on the drawing(s), provided that the same or similar item manufactured using the same processes has successfully passed the tests, and results of the test are on file at the contractor's facility and certifications are submitted with the First Article Test Report.

d. The Contractor shall provide to the Contracting Officer at least 15 calendar days advance notice of the scheduled date for final inspection and test of the first article. Those inspections which are of a destructive nature shall be performed upon additional sample parts selected from the same lot(s) or batch(es) from which the first article was selected.

e. A First Article Test Report shall be compiled by the contractor documenting the results of all inspections and tests (including supplier's and vendor's inspection records and certifications, when applicable). The First Article Test Report shall include actual inspection and test results to include all measurements, recorded test data, and certifications (if applicable) keyed to each drawing, specification and QAP requirement and identified by each individual QAP characteristic, drawing/specification characteristic and unlisted characteristic. Evidence of the QAR's verification will be provided. One copy of the First Article Test Report will be submitted through the Administrative Contracting Officer to the Contracting Officer Morris.Belleville@us.army.mil and Contract Specialist robert.harrison9@us.army.mil with a copy furnished to ROCK-RDAR-QEP@CONUS.ARMY.MIL.

f. Notwithstanding the provisions for waiver of first article, an additional first article sample or portion thereof, may be ordered by the Contracting Officer in writing when (i) a major change is made to the technical data, (ii) whenever there is a lapse in production for a period in excess of 90 days, or (iii) whenever a change occurs in place of performance, manufacturing process, material used, drawing, specification or source of supply. When conditions (i), (ii), or (iii) above occurs, the Contractor shall notify the Contracting Officer so that a determination can be made concerning the need for the additional first article sample or portion thereof, and instructions provided concerning the submission, inspection, and notification of results. Costs of the additional first article testing resulting from any of the causes listed herein that were instituted by the contractor and not due to changes directed by the Government shall be borne by the Contractor.

(End of Clause)

CATEGORY 3 - Unless otherwise specified in the solicitation, contract or contract modification, all requirements contained in the directly cited document

and all reference and subsequently referenced documents are contractually applicable

to the extent specified.

Document Number
(Contract Reference)		Document Date/
Applicable Tailoring	Document Title	Document Category

la. N/A	Section c titled: Configuration Management Documentation	N/A Cat 2

lb. DI-CMAJ:\f-80639C	Engineering Change Proposal	30 Sep 00 (ECP)
(seq A001)		Cat

lc. DI-CMAJ:\f-80640C	Request for Deviation (RFD)	30 Sep 00
(seq A002)		Cat 1

ld. DI-CMAJ:\f-80642C	Notice of Revision (NOR)	30 Sep 00
(seq A003)		Cat 1

2. AN"SI/ISO/ASQC Q9001-2008	American National Standard Quality Quality Management Systems Requirements	15 Nov 08

3. MIL-PRF-13830 (REVB)	Optical Components for Fire	09 Jan 97
	Control Instruments; Gen. Spec.	Cat 2

END OF DOCUMENT SUMMARY LIST

ADDRESS LIST

Executive for Contracting DLA Land Warren

6501 E. 11 Mile Road

Mailstop 729

ATTN: (See Block 14 of DD Form 1423 for symbols that apply)

Warren, MI 48397-5000

Director

U.S. Army, Armament, Research, Development & Engineering Center

1 Rock Island Arsenal

ATTN: (See Block 14 of DD Form 1423 for symbols that apply)

Rock Island, IL 61299-7300

Commander

U.S. Army, Armament, Research, Development & Engineering Center

ATTN: (See Block 14 of DD Form 1423 for symbols that apply)

Picatinny Arsenal, NJ 07806-5000

END OF ADDRESS LIST

ADDRESS CODE DISTRIBUTION

FOR ECP/RFD/VECP

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		4

1. Concurrent distribution of Value Engineering Change Proposals (VECPs), Engineering Change Proposals (ECPs), Request for Deviations (RFDs) shall be submitted electronically to the below addresses:

a ROCK – ECP – INPUT@CONUS.ARMY.MIL if the item is NOT a chemical item

b. ROCK – ECBCCMActions@conus.army.mil if the item is a chemical item

c. Contracting Office: Provide to the buyers E-Mail address as reflected on the front page of the contract (or most recent modification if applicable)

d. The Administrative Contracting Officer.

(Submissions must be under lOMB), (electronic foms (DD Foms 1692, 1693, and 1694) are available for your use at h.til2§_;_il _,_I2i g gg,y ilLI2£9.9....i QhQ _Lg_ QQQ§.::.li..J1k§_,_h.Qg,

2. If hardcopies are submitted, the contractor shall submit copies as required and as identified below to:

Director, U.S. Amy Armament Research

Development and Engineering Center

ATTN: RDAR-EIS-PE (ECPs)

PICATINNY, NJ 07806-5000

Chemical items should be provided to RDCB-DEM, Rock Island, IL 61299-7410

a. VECPs -	original plus 3 COpleS
	original plus 3 COpleS	(Tools & Equipment)
	original plus 3 COpleS	(Navy or Air Force)

b. ECPs -	original plus 2 COpleS
	original plus 2 COpleS	(Tools & Equipment)
	original plus 2 COpleS	(Navy or Air Force)

c. RFDs -	original plus 2 COpleS
	original plus 2 COpleS	(Tools & Equipment)
	original plus 2 COpleS	(Navy or Air Force)

If submitting by mail, one copy designated Advance Copy to:

a. Contracting Office: Provide to the buyers E-Mail address as reflected on the front page of the contract (or most recent modification if applicable).

b. Administrative Contracting Officer.

3. When ECPs, NORs, RFDs are determined to be Urgent, Critical and/or Schedule impacting, an action copy shall be provided to RDAR-EIS-T via data facsimile (FAX) to 973-724-2082. This transmission is to be immediately followed with the usual hard copy mailing.

END OF ADDRESS CODE DISTRIBUTION

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE

DATA DELIVERY DESCRIPTIONS

ENGINEERING CHANGE PROPOSAL (ECP)

Requirements:

1. Reference documents. The applicable issue of any documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified ln the contract.

2. Format and content. The Engineering Change Proposal shall be prepared ln contractor format.

3. Supporting data. In addition to the information required below, the ECP shall include supporting data. Formal ECPs shall be supported by drawings and other data (e.g., Logistic Support Analysis (LSA) data, detailed cost proposal data, test data and analyses) as specified in the contract to justify and describe the change and to determine its total impact including assessments of changes to system operational employment characteristics. When a life cycle cost and/or operation and support cost model has been included in the contract, the ECP shall also include the costs expected to result from the implementation of the change into all future production and spare items projected to be procured for the program. Also for all projected operation and support costs for operation of the total inventory of items by the Goverrrment. A summary of any testing done to validate concepts or new technology to be employed in the proposed engineering change shall be presented in the supporting data. Details of such test data shall be provided if it is vital to the decision regarding acceptance of the change.

4. Distribution statement. The appropriate distribution statement shall be affixed to the ECP in accordance with the requirements of the contract.

5. Date. Provide the submittal date of the ECP or of the revision to the ECP.

6. Procuring Activity Number (PAN): Provide the PAN of the procuring activity, if known.

7. DODAAC. Provide the DODAAC of the procuring activity, if known.

8. Originator name and address. Provide the name and address of the contractor submitting the ECP.

9. Designate as either Class I or II. Proposed changes that do not meet the criteria for Class I shall be designated as Class II. The englneerlng change shall be Class I if:

The Functional Configuration Documentation (FCD) or Allocated Configuration Documentation (ACD) is affected to the extent that any of the following requirements would be outside specified limits or specified tolerances:

(1)

Performance.

(2)

Reliability, maintainability or survivability.

(3)

Weight, balance, moment of inertia.

(4)

Interface characteristics.

(5)

Electromagnetic characteristics.

(6)

Other technical requirements in the specifications.

NOTE: Minor clarifications and corrections to FCD or ACD shall be made only as an incidental part of the next Class

ECP NOR, unless otherwise directed by the Government.

A change to the Product Configuration Documentation (PCD) will affect the FCD or ACD as described in paragraph 9a or will impact one or more of the following:

(1)

Goverrrment Furnished Equipment (GFE).

(2)

Safety.

(3)

Compatibility or specified interoperability with interfacing Cis, support equipment or support software, spares, trainers or training devices/ equipment/software.

(4)

Configuration to the extent that retrofit action is required.

(5)

Delivered operation and maintenance manuals for which adequate change/revision funding is not provided ln existing contracts.

(6)

Preset adjustments or schedules affecting operating limits or performance to such extent as to require assignment of a new identification number.

(7)

Interchangeability, substitutability, or replaceability as applied to Cis, and to all subassemblies and parts except the pieces and parts of non-reparable subassemblies.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		2

(8)

Sources of Cis or repairable items at any level defined by source-control drawings.

(9)

Skills, manning, training, biomedical factors or human-engineering design.

Any of the following contractual factors are affected:

(1)

Cost to the Goverrrment including incentives and fees.

(2)

Guarantees or warranties.

(3)

Deliveries.

(4)

Scheduled milestones.

10. Justification code. Provide a justification code that is applicable to a proposed Class I engineering change. The justification code is not required for Class II ECPs. If more than one of the following codes are applicable, the one which is the most descriptive or significant shall be assigned to the ECP.

Interface. Code B shall be assigned to an engineering change proposal for correction of a deficiency which will eliminate interference or incompatibility at an interface between Cis.

Compatibility. Code C shall be assigned to an engineering change to correct a deficiency with the following characteristics:

(1)

The need for the change has been discovered during the system or item functional checks or during installation and checkout and is necessary to make the system or item work.

(2)

By assigning the compatibility code the contractor is declaring that the effort required to accomplish the change is considered to be within the scope of the existing contract except for changes caused by the Goverrrment.

(3)

Contractual coverage completing the formal documentation of the engineering change will not reflect an increase in contract price for the corrective action in production and to delivered items in-warranty or otherwise stipulated in the contract.

Correction of deficiency. Code D shall be assigned to an engineering change which is required to eliminate a deficiency, unless a more descriptive separate code applies. Such separate codes are used to identify deficiencies of the nature of safety, interface, or compatibility.

Operational or logistics support. Code 0 shall be assigned to an engineering change which will make a significant effectiveness change in operational capabilities or logistics support.

Production stoppage. Code P shall be assigned to an engineering change which is required to prevent slippage ln an approved production schedule. This code applies when production to the current configuration documentation either is impracticable or cannot be accomplished without delay.

Cost reduction. CodeR shall be assigned to an engineering change which will provide a net total life cycle cost savings to the Goverrrment, but which is not being submitted pursuant to the Value Engineering clause of the contract. The savings in life cycle cost should include all effects on cost and price for the effort and requirements covered by the contract(s) currently in effect for this contractor, plus the costs resulting from necessary associated changes in delivered items, and logistics support.

Safety. Code S shall be assigned to an englneerlng change for correction of a deficiency which lS required primarily to eliminate a hazardous condition. When this code is assigned, a system hazard analysis shall be included with the ECP. (See MIL-STD-882)

Value engineering (VE). Code V shall be assigned to an engineering change that will effect a net life cycle cost reduction and which is submitted pursuant to the VE clause of the contract.

11. Priority. A priority shall be assigned to each Class I ECP based upon the following definitions. Class II ECPs do not require a priority assignment. The proposed priority is assigned by the originator and will stand unless the Government has a valid reason for changing the priority.

Emergency (E). Shall be assigned to an engineering change proposed for any of the following reasons:

(1)

To effect a change in operational characteristics which, if not accomplished without delay, may seriously compromise national security;

(2)

To correct a hazardous condition which may result in fatal or serious injury to personnel or in extensive damage or destruction of equipment. (A hazardous condition usually will require withdrawing the item from service temporarily, or suspension of the item operation, or discontinuance of further testing or development pending resolution of the condition.); or

(3)

To correct a system halt (abnormal termination) in the production environment such that CSCI mlsslon accomplishment is prohibited.

Urgent (U). Shall be assigned to an engineering change proposed for any of the following reasons:

(1)

To effect a change which, if not accomplished expeditiously, may seriously compromise the mission effectiveness of deployed equipment, software, or forces; or

(2)

To correct a potentially hazardous condition, the uncorrected existence of which could result in injury to personnel or damage to equipment. (A potentially hazardous condition compromises safety and embodies risk, but within reasonable limits, permits continued use of the affected item provided the operator has been informed of the hazard and appropriate precautions have been defined and distributed to the user.); or

(3)

To meet significant contractual requirements (e.g., when lead time will necessitate slipping approved production or deployment schedules if the change was not incorporated); or

(4)

To effect an interface change which, if delayed, would cause a schedule slippage or lncrease cost; or

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		3

(5)

To effect a significant net life cycle cost savlngs to the Goverrrment, as defined in the contract, through value engineering or through other cost reduction efforts where expedited processing of the change will be a major factor in realizing lower costs.

(6)

To correct unusable output critical to mission accomplishment;

(7)

To correct critical CI files that are being degraded; or

(8)

To effect a change in operational characteristics to implement a new or changed regulatory requirement with stringent completion date requirements issued by an authority higher than that of the functional proponent.

Routine (R). Shall be assigned to a proposed engineering change when emergency or urgent is not applicable.

12. ECP designation.

Model/Type. Provide model or type designation of the CI for which this proposal is being submitted. For Computer Software Configuration Items (CSCI), enter the CSCI identification number.

CAGE code. Enter the CAGE code for the activity originating the ECP.

System designation. The system or top-level CI designation or nomenclature assigned shall be entered, if known.

13. ECP number. Provide an ECP number. Once an ECP number is assigned to the first submission of a change proposal, that number shall be retained for all subsequent submissions of a change proposal. One of the following methods of assigning ECP numbers may be used unless otherwise stated in the contract:

ECP numbers shall run consecutively commencing with number 1, for each CAGE Code identified activity, or ECP numbers may be assigned in a separate series for each system that the contractor is producing

When an ECP is split into a basic ECP and related ECPs, the basic ECP shall be identified with the number prescribed above and each related ECP shall be identified by the basic number plus a separate dash number. The number of characters in the ECP number, dash number, type, and revision identification shall not exceed 32.

Other systems may be used provided the ECP number is unique for any CAGE Code identified activity, and the 32 character limitation is not exceeded.

14. Type. For Class I ECPs, indicate either a "P" for preliminary, or "F" for fomal. A Class I ECP shall be preliminary if it meets the criteria below.

A preliminary change proposal is one that is submitted to the Government for review prior to the availability of the information necessary to support a formal ECP. It shall include a summary of the proposed change, its impact on related areas, and a justification. Examples are to furnish the Government with available information in order to pemit:

(1)

A preliminary evaluation relative to the merits of the proposed change (e.g. installation of a proposed change for the purpose of evaluation and testing prior to making a final decision to proceed with a proposed change);

or,

(2)

A determination regarding the desirability of continuing expenditures required to further develop the proposal.

(3)

To provide alternative proposals; or

(4)

To supplement a message relative to an emergency or urgent priority ECP when it is impracticable to submit a formal ECPwithin 30 calendar days; or

(5)

To obtain Government approval to proceed with software engineering development prior to the development of the actual coding changes.

A formal ECP is the type, which provides the englneerlng information and other data in sufficient detail to support fomal change approval/contractual implementation.

15. Revision. If an ECP is being revised, enter the proper identification of the revision, i.e., R1 for the first revision; R2, R3, etc. for subsequent revlslons. (The date submitted (paragraph 5) shall be the date of the revised ECP.)

16. Baseline affected. Indicate the baseline(s) affected (see MIL-HDBK-61).

17. Other systems/configuration items affected. If other systems/configuration items are affected indicate whether the effect on other systems or Cis requires the submittal of related Class I ECPs. Supply details in paragraphs 33a and c.

18. Specifications affected. If specifications cited in the contract are affected by the ECP, their identity by the CAGE code of the design activity, document number, revision letter, and the NOR number of the NOR being submitted with the ECP, shall be provided.

19. Drawings affected. If drawings are affected by the ECP, their identity by the CAGE code of the design activity, document number, revision letter, and the NOR number of the NOR being submitted with the ECP, shall be provided.

20. Title of change. Provide a brief title to identify the component or system affected by the ECP. For example: F-18 Aircraft Air Turbine Start Connector Backshell Replacement; AN/AYK-14(v) CP-1502/CP-1503 Reconfiguration to CP-1799; (CSCI name) Block Update.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		4

21. Contract number(s) and line item(s). Provide the number(s) of all currently active contract(s), and the affected contract line item number(s), at the originating CAGE-coded activity that are affected by the engineering change.

22. Procuring contracting officer. Provide the procurlng contracting officer's name, office symbol/code, and telephone number applicable to the CI shown ln paragraph 21.

23. Configuration item nomenclature. Provide the assigned name and type designation the CSCI name and number, if applicable, or authorized name and number of the CI(s) affected by the ECP.

24. Is the CI in production? If "yes", provide information as to whether deliveries have been completed on the contract(s). This data is not always applicable to software. If not applicable, so indicate.

25. All lower level items affected.

For hardware, an appropriate, complete descriptive name of the part(s) shall be provided as well as the quantity of the part(s). Additionally, applicable NSNs shall be provided.

For CSCI's, provide the name and identifier of each lower level CI and computer software unit affected.

26. Description of change. The description of the proposed change shall include the purpose and shall be given in sufficient detail to adequately describe what is to be accomplished. It shall be phrased in definitive language such that, if it is repeated in the contractual document authorizing the change, it will provide the authorization desired. Supporting data may be provided to the extent necessary to clearly portray the proposed change. If the proposed change is an interim solution, it shall be so stated.

27. Need for change. Provide an explanation of the need for the change to include specifically identifying the benefit of the change to the Government. The nature of the defect, failure, incident, malfunction, etc. substantiating the need for the change shall be described in detail. Full utilization shall be made of available failure data. If a new capability is to be provided, improvements in range, speed, performance, endurance, striking power, defensive or offensive capabilities, etc. shall be described in quantitative terms. Correspondence establishing requirements for the change and any testing accomplished prior to the submission shall be identified and summarized. If the ECP is needed to correct maintenance/ logistics problems, that fact will be included with sufficient detail to identify the lssues. If the ECP is being submitted as a response to a request for ECP or Government direction, cite that authority herein.

28. Production effectivity by serial number.

For hardware, provide the estimated production effectivity point for the production items including serial number, or other item identification (e.g., block or lot number) as approved by the Government. In determining the effectivity point for the proposed change, consider, in addition to the time factors, the availability of all support elements affected and the most economical point of introduction consistent with all the salient factors involved. The earliest production incorporation is not necessarily the singular or most important factor in the establishment of a proposed change effectivity point. The effectivity point shall be based on concurrent availability of all logistics support elements and materials affected by the change to the item.

For CSCI's, identify the CSCI version number, if known, into which the change will be incorporated. Where applicable, the effectivity of the end item CI and vehicle (aircraft, tank, ship, etc.) into which the capability represented by the new version of the software is proposed to be incorporated, shall also be provided. If the impact of the ECP merits the release of a new software version include a recommendation to this effect. Serial numbers may be used in lieu of version numbers if approved by the Government.

29. Effect on production delivery schedule. State the estimated delivery schedule of items incorporating the change, either ln terms of days after contractual approval, or by specific dates contingent upon contractual approval by a specified date. If there will be no effect on the delivery schedule, so state.

30. Retrofit.

Recommended item effectivity. When the contractor recommends that the engineering change be accomplished in accepted items by retrofit, the quantities and serial (or lot) numbers of accepted items in which the change lS proposed to be incorporated by retrofit shall be provided. Such statement regarding items currently in production shall be based upon the estimated approval date of the ECP.

Ship/vehicle class affected. When the delivered CI is installed ln one or more ship/vehicle classes, enter the identification of such classes.

Estimated kit delivery schedule. State estimated kit delivery schedule by quantity and date. When special tooling for retrofit is required for Government use, provide the dates of availability of tools, jigs, and test equipment required ln conjunction with the kits to accomplish the change.

Locations or ship/vehicle numbers affected. State the location(s) where retrofit is to be accomplished. If retrofit is to be accomplished in ships (or in vehicles for which the serial numbers are not shown ln paragraph 30b), enter the ship hull numbers or vehicle numbers.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		5

NOTE: The appropriate information shall be provided for CSCI changes that are to be incorporated as part of a hardware or equipment change; and implemented per a hardware retrofit schedule, or where the fielded version of the software lS to be replaced.

31. Estimated costs/savings under contract. Provide the total estimated costs/savings impact of the ECP on the contract for the subject CI. Savings shall be shown in parentheses.

32. Estimated net total costs/savings. Provide the total estimated costs/savings impact of the basic and all related ECPs, including other costs/savings to the Government. Savings shall be shown in parentheses.

33. Effects on Functional/Allocated Configuration Identification. This information is to be provided only if the proposed change affects the system specification or the item development specification(s). If a separate product function specification is used, effects on such specification of changes proposed after the Product Baseline has been established shall be described as required.

Other systems affected. Provide only if other systems/configuration items are affected as indicated in paragraph 17.

Other contractors/activities affected. Identify other contractors or Goverrrment activities that will be affected by this engineering change.

Configuration items affected. Enter the names and numbers of all Cis, maintenance and operator training equipment, and support equipment affected.

Effects on performance allocations and interfaces in system specification. Describe the changes in performance allocations and in the functional/physical interfaces defined in the system specification.

Effects on employment, integrated logistic support, training, operational effectiveness, or software.

(1)

For hardware, describe the effects of the proposed change on employment, deployment, logistics, and/or personnel and training requirements which have been specified in the approved system and/or CI specifications, including any changes or effects on the operability of the system. In particular, there shall be an entry detailing any effect on interoperability.

(2)

For CSCis, the following information shall be entered as applicable to the degree of design development of the CSCI at the time of ECP submission:

(a)

Identify any required changes to the data base parameters or values, or to data base management procedures;

(b)

Identify and explain any anticipated effects of the proposed change on acceptable computer operating time and cycle-time utilization;

(c)

Provide an estimate of the net effect on computer software storage; and,

(d)

Identify and explain any other relevant impact of the proposed change on utilization of the system.

34. Effects on configuration item specifications. The effect of the proposed change on performance shall be described ln quantitative terms as it relates to the parameters contained ln the CI development specifications. (See MIL-STD-961)

35. Developmental requirements and status.

For hardware, when the proposed engineering change requires a major revision of the development program (e.g., new prototypes, additional design review activity, tests to be reaccomplished), the nature of the new development program shall be described in detail, including the status of programs already begun.

For CSCis, identify the scheduled sequence of computer software design and test activities which will be required. ECPs initiated after preliminary design which affect the FBL and/or the ABL shall identify, as appropriate, significant requirements for computer software redesign, recoding, repetition of testing, changes to the software engineering/test environments, special installation, adaptation, checkout, and live environment testing. In addition, the specific impact of these factors on approved schedules shall be identified. The impact of the software change on the hardware design and input/output cabling shall also be detailed.

36. Date by which contractual authority is needed. Provide the date contractual authority is required in order to maintain the established schedule for:

a. Production

b. Retrofit

37. Effects on product configuration documentation, logistics and operations. Certain information required may have been supplied in paragraphs above or does not apply to computer software. When this information has already been supplied, a cross-reference to such information will be adequate.

For hardware, if any specific logistic interoperability factors are affected, provide information detailing the possible impact on the operational configuration.

For CSCis, the software engineering and test environments are usually not affected by changes in the product configuration of a CSCI. Provide information about the status of the software redesign and retesting effort. There shall also be a review of the intent to document CSCI impacts in these areas.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		6

38. Effect on product configuration documentation or contract. The effects on the approved CI product specifications shall be described by reference to the NORs or other enclosure(s) which cover such proposed text changes in detail. The effects on drawings, when not covered previously shall be described in general terms. Address nomenclature change when applicable. The effects on performance, weight-balance-stability, weight-moment, shall also be provided when applicable.

39. Effect on acquisition logistics support (ALS) elements. The effects of the engineering change on logistic support of the item shall be provided. These effects shall be explained in detail. The information required shall indicate the method to be used to determine the integrated logistic support plans and items which will be required for the support of the new configuration as well as retrofitting previously delivered items to the same configuration. The following shall be covered as applicable:

Effects on schedule and content of the ALS plan.

Effect on maintenance concept and plans for the levels of maintenance and procedures.

System and/or CI logistics support analysis (LSA) tasks to be accomplished and LSA data requiring update wherever it exists ln the contract. (MIL-PRF-49506)

Extension/revision of the interim support plan.

Spares and repair parts that are changed, modified, obsoleted or added, including detailed supply data for interim support spares. NOTE: Failure to include detailed supply data will delay ECP processing.

Revised or new technical manuals.

Revised or new facilities requirements and site activation plan.

New, revised, obsoleted or additional support equipment (SE), test procedures and software. For items of SE and trainers which require change, furnish a cross reference to the related ECPs, and for any related ECP not furnished with the basic ECP, furnish a brief description of the proposed change(s) in SE and trainers.

Qualitative and quantitative personnel requirements data which identify additions or deletions to operator or maintenance manpower in terms of personnel skill levels, knowledge and numbers required to support the CI as modified by the change.

New operator and maintenance training requirements in terms of training equipment, trainers and training software for operator and maintenance courses. This information should include identification of specific courses, equipment, technical manuals, personnel, etc. required to set up the course at either the contractor or Goverrrment facility.

Any effect on contract maintenance that increases the scope or dollar limitation established in the contract.

Effects on packaging, handling, storage, and transportability resulting from changes in materials, dimensions,

fragility, inherent environmental or operating conditions.

40. Effect on operational employment. The effects of the engineering change of CI utilization shall be provided. Quantitative values shall be used whenever practicable and are required when reliability and service life are impacted. Survivability includes nuclear survivability. The effects of the change proposal on safety, maintainability, operating procedures, electromagnetic interference, activation schedule critical single point failure items, and interoperability shall also be provided, if applicable.

41. Other considerations. The effects of the proposed engineering change on the following shall be identified:

Interfaces having an effect on adjacent or related items, (output, input, slze, mating connections, etc.

GFE or Government Furnished Data (GFD) changed, modified or obsoleted.

Physical constraints. Removal or repositioning of items, structural rework, increase or decrease in overall dimensions.

Software (other than operational, maintenance, and training software) requiring a change to existing code and/or, resources or addition of new software.

Rework required on other equipment not included previously which will effect the existing operational configuration.

Additional or modified system test procedures required.

Any new or additional changes having an effect on existing warranties or guarantees. h. Changes or updates to the parts control program.

Effects on life cycle cost projections for the configuration item or program, including projections of operation and support costs/savings for the item(s) affected over the contractually defined life and projections of the costs/savings to be realized in planned future production and spares buys of the item(s) affected.

42. Alternate solutions. When applicable, provide a summary of the various alternative solutions considered, including the use of revised operation or maintenance procedures, revised inspection or servicing requirements, or revised part replacement schedules. The contractor shall provide an analysis of the alternatives, identify the advantages and disadvantages inherent in each feasible alternative approach, and show the reasons for adopting the alternative solution proposed by the ECP. When contractors analysis addresses new concepts or new technology, supporting data shall be presented with the proposal to authenticate the trade-off analysis.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		7

43. Developmental status. When applicable, make recommendations as to the additional tests, trials, installations, prototypes, fit checks, etc., which will be required to substantiate the proposed engineering change. These recommendations shall include the test objective and test vehicle(s) to be used. Indicate the development status of the major items of GFE which will be used in conjunction with the change and the availability of the equipment in tems of the estimated production incorporation point.

44. Recommendations for retrofit. When applicable, make recommendations for retrofit of the engineering change into accepted items with substantiating data, any implications thereto, and a brief description of the action required. Where retrofit is not recommended, an explanation of this detemination shall be provided.

Work-hours per unit to install retrofit kits. Show the amount of work which must be programmed for varlous

activities to install retrofit kits. Estimate work-hours to install retrofit kits when weapon system is undergoing overhaul.

Work-hours to conduct system tests after retrofit. Provide the work-hours required to test the system or the item following installation of the retrofit kit.

This change must be accomplished. Where previously approved engineering changes must be incorporated in a specific order in relation to the proposed change, such order should be specified.

Is contractor field service engineering required? If "yes" attach proposed program for contractor participation.

Out of service time. Estimate the total time period from removal of the equipment from operational service until equipment will be returned to operational status after being retrofitted.

45. Effect of this ECP and previously approved ECPs on item. Summarize the cumulative effect upon performance, weight, electrical load, etc., of this ECP and previously approved ECPs when design limitations are being approached or exceeded. Provide consequences of ECP disapproval.

46. Production impact costs. Estimated costs/savings applicable to production of the item resulting from the change. Includes the costs of Redesign of the Cis or Components thereof, of Factory Test Equipment, of Special Factory Tooling, of Scrap, of Engineering Design, of Engineering Data Revision, of Revision of Test Procedures, and of Testing and Verification of Performance of New Items.

47. Retrofit impact costs: Estimated costs applicable to retrofit of the item including installation and testing costs. Includes Retrofit-specific Engineering Data Revision, Prototype Testing, Kit Proof Testing, Purchase of Retrofit Kits for Operational Systems, Preparation of Modification Instructions, Design and Manufacture of Special Tooling for Retrofit, Installation of Kits by contractor personnel, Installation of Kits by government personnel, Testing after Retrofit and Modification, and Testing and Verification of Performance of Government Furnished Equipment/Property (GFE/GFP).

48. Logistics support impact costs: Estimated costs/savings of the various elements of logistics support applicable to the item. Includes Spares/Repair Parts Rework, New Spares and Repair Parts, Supply/Provisioning Data, Support Equipment, Retrofit Kit for Spares, Operator Training Courses, Maintenance Training Courses, Revision of Technical Manuals, New Technical Manuals, Training/Trainers, Interim Support, Maintenance Manpower, and Computer Programs/Documentation.

49. Other costs/savings: Includes estimated costs of interface changes accomplished by other contractor activities. (Do not include costs if the changes are covered by related ECPs by other contractors. Also includes estimated costs of interface changes accomplished by the Government for changes which must be accomplished in previously delivered items (aircraft, ships, facilities, etc.), other interfacing products, and/or retrofit of GFE/GFP, to the extent that such costs are not covered under production, retrofit, or logistics support.

50. Estimated costs/savings summary, related ECPs. Provide a summary of the estimated net total cost impact of both the ECP and any related ECPs and other associated new requirements which are needed to support the modified items broken out by categories described in paragraphs 47 through 50 above.

Prime contractor. The prime contractor shall summarize the costs/savings of all related ECPs for which the contractor is responsible. If there is no system integrating contractor, the prime contractor submitting the basic ECP shall include the costs of related ECPs being submitted by other affected contractors to the extent such information is available.

System integrating contractor. When a system integrating contractor (or coordinating contractor) has contractual responsibility for ECP coordination, the contractor shall summarize the costs of related ECPs of the several primes involved in an interface or interrelated ECP.

51. Milestones. Provide milestones that show the time phasing of the various deliveries of items, support equipment, training equipment, and documentation incorporating the basic and related ECPs. Enter symbols and notations to show the initiation or termination of significant actions. Base all dates upon months after contractual approval of the basic ECP.

52. Signature. An authorized official representing the contractor submitting the ECP shall sign the ECP.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		8

REQUEST FOR DEVIATION (RFD)

This Data Delivery Description (DDD) contains the content and preparation instructions for the data product resulting from the work task specified in the contract.

Requirements:

2. Format and content. The Request for Deviation shall be prepared in contractor format. The RFD content shall be in accordance with the contractors processes and procedures, or as specified in the contract.

3. Distribution statement. The appropriate distribution statement shall be affixed to the RFD in accordance with the requirements of the contract.

4. Date. Provide the submittal date of the deviation.

5. DODAAC. Provide the DODAAC of the procuring activity, if known.

6. Procuring Activity Number (PAN). Provide the PAN of the procuring activity, if known

7. Originator name and address. Provide the name and address of the contractor submitting the request (inclusion of submitting individual's name is optional

8. Classification. The deviation shall be designated minor, maJor, or critical in accordance with the following criteria:

Minor. A deviation shall be designated as mlnor when:

(1) The deviation consists of a departure which does not involve any of the factors listed in Bb or Be or

(2) When the configuration documentation defining the requirements for the item classifies defects in requirements and the deviations consist of a departure from a requirement classified as minor.

Major. A deviation shall be designated as maJor when:

(1) The deviation consists of a departure involving:

(a)

health

(b)

performance

(c)

interchangeability, reliability, survivability, maintainability, or durability of the item or its repair parts

(d)

effective use or operation; (e) weight and size; or

(f)

appearance (when a factor) or

(2)

When the configuration documentation defining the requirements for the item classifies defects in requirements and the deviations consist of a departure from a requirement classified as major.

Critical. A deviation shall be designated as critical when:

(1)

The deviation consists of a departure involving safety or

(2)

When the configuration documentation defining the requirements for the item classifies defects in requirements and the deviations consist of a departure from a requirement classified as critical.

9. Designation for deviation.

Model/Type. Provide the model or type designation of the CI for which the request lS being submitted. For CSCis provide the CSCI identification.

CAGE Code. Provide the CAGE Code for the activity originating the deviation.

System designation. The system or top level CI designation or nomenclature assigned by the Government shall be entered, if known.

10. Deviation number. Deviation identification numbers shall be unique for each CAGE Code identified activity. Once a number is assigned, that number shall be retained for all subsequent submissions. Unless otherwise authorized by the Government, deviations shall be separately and consecutively numbered commencing with number one. As an alternative, numbers may be assigned from a separate series for each system that the contractor is producing. The number of characters in the deviation number, dash number, and type identification shall not exceed 32.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		9

11. Configuration baseline affected. Indicate the affected baseline (See MIL-HDBK-61).

12. Are other system/configuration items affected? If yes, provide summary.

13. Title of deviation. Provide a brief descriptive title of the deviation.

14. Contract number and line item. Provide the number(s) of all currently active contract(s) and the affected contract line item number(s) that are affected by the deviation.

15. Procuring contracting officer. Enter the procurlng contracting officer's name, office symbol/code, and telephone number applicable to the CI shown in paragraph 18.

16. Configuration item nomenclature. Provide the Government assigned name and type designation, if applicable, or authorized name and number of the CI to which the deviation will apply.

17. Classification of defect (CD).

CD number. If either a Government or contractor's CD applies, enter the number assigned.

Defect number. If a CD applies, enter the defect number(s) which correspond(s) with the characteristic(s) from which an authorized deviation is desired.

Defect classification. If a CD applies state the proper classification of the defect number(s) entered in paragraph 17b.

18. Name of lowest part/assembly affected. An appropriate descriptive name of the part(s) shall be given here without resorting to such tems as "Numerous bits and pieces"

19. Part number or type designation. Enter the part number(s) of the part(s) named ln paragraph 18 or type designation/nomenclature if applicable.

20. Effectivity. Define the effectivity of the proposed RFD by entering, as applicable, the quantity of items affected, the serial numbers of the items affected, or the lot number(s) applicable to the lot(s) affected by the deviation being requested.

21. Recurring Deviation. If this is a recurring deviation, reference the previous correspondence, the request number, and corrective action to be taken in paragraph 27. In addition provide rationale why recurrence was not prevented by previous corrective

action and/or accomplished design change.

22. Effect on cost/price. Provide the estimated reduction or price adjustment. If no change ln price, cost, or fee, so state with rationale. The request for deviation shall include the specific consideration that will be provided to the Government if this "non-confoming" unit(s) (See FAR Part 46.407) is accepted by the Government.

23. Effect on delivery schedule. State the effects on the contract delivery schedule that will result from both approval and disapproval of the request for deviation.

24. Effect on integrated logistics support, interface, or software. If there is no effect on logistics support or the interface, provide a statement to that effect. If the deviation will have an impact on logistics support or the interface, describe such effects.

25. Description of deviation. Describe the nature of the proposed departure from the technical requirements of the configuration documentation. The deviation or waiver shall be analyzed to determine whether it affects any of the factors listed below. Describe any effect on each of these factors (marked drawings should be included when necessary to provide a better understanding of the deviation):

Effect on Product Configuration Documentation or Contract.

(1)

Performance

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		10

(2)

Weight-balance-stability (aircraft)

(3)

Weight-Moment (other equipment)

(4)

Technical Data

(5)

Nomenclature

Effect on Operational Employment

(1)

Safety

(2)

Survivability

(3)

Reliability

(4)

Maintainability

(5)

Service Life

(6)

Operating Procedures

(7)

Electromagnetic Interference

(8)

Activation Schedule

(9)

Critical Single Point Failure Items

(10)

Interoperability

Other Considerations

(1)

Interface

(2)

Other Affected Equipment/Government Furnished Equipment (GFE)/Goverrrment Furnished Parts (GFP)

(3)

Physical Constraints

(4)

Computer Programs and Resources

(5)

Rework of other equipment

(6)

System Test Procedures

(7)

Warranty/Guarantee

(8)

Parts Control

(9)

Life Cycle Costs

26. Need for deviation. Explain why it is impossible or unreasonable to comply with the configuration documentation within the specified delivery schedule. Also explain why a deviation is proposed in lieu of a permanent design change.

27. Corrective action taken. Describe action being taken to correct non-conformance to prevent a future recurrence.

28. Signature. The RFD shall be signed by an authorized official representing the contractor submitting the RFD.

NOTICE OF REVISION (NOR)

This Data Delivery Description (DDD) contains the content and preparation instructions for the data product resulting from the work task specified in the contract. This DDD is used in conjunction with an Engineering Change Proposal (ECP). A requirement for ECPs should be contractually imposed in conjunction with this DDD. This DDD may also be used with Specification Change Notices (SCNs). Where NORs are required for changes to paper specifications, a requirement for SCNs may be contractually imposed in conjunction with this DDD.

Requirements:

2. Format and content. The NOR shall be prepared in contractor format. The NOR content shall be in accordance the contractors processes and procedures, or as specified ln the contract.

3. Distribution statement. The appropriate distribution statement shall be affixed to the NOR ln accordance with the requirements of the contract.

4. Date. Provide the submittal date of the NOR. Normally this date will be identical to the ECP submittal date.

	PIIN/SIIN		SPRDL1-12-C-0023
	MOD/AMD
	ATT/EXH ID		Exhibit B
	PAGE		11

5. DODAAC. Provide the DODAAC of the procuring activity.

6. Procuring Activity Number (PAN). Provide the PAN of the procuring activity, if known.

7. Originator name and address. Provide the name and address of the contractor submitting the proposed NOR (inclusion of submitting individual's name is optional).

8. CAGE code. Provide the CAGE code of the originator of the ECP.

9. NOR number. Unless the use of a Government assigned number is prescribed, the originator shall either assign a number or enter the document number and new revision letter as the NOR number. When the requirement in the contract identifies the NOR by ECP number, the originator shall attach a dash number (i.e., xxx-1).

10. CAGE Code. Provide the CAGE Code of the original design activity that appears on the document to which the revision applies. If the original design activity is not the current design activity, also enter the CAGE code of the current design activity.

11. Document number. Provide the number of the drawing, standard, specification, list or other document to be revised.

12. Title of document. Provide the title of the document to which the NOR applies.

13. Revision letter. Show the existing revision of the document for which the NOR lS prepared.

14. Outstanding NORs. Provide the NOR number of all approved unincorporated NORs for the affected document.

15. ECP number. Provide the number of the ECP describing the engineering change which necessitates the document revision covered by the NOR.

16. Configuration item (or system) to which ECP applies. Provide Government assigned system designation (if any); otherwise, enter the name and type designation of the Configuration Item to which the ECP applies.

17. Description of change. Describe the change in detail, giving the exact wording of sentences or paragraphs that are to be added, or that are to replace designated sentences or paragraphs of the current document. State the dimensions, tolerances and other quantitative requirements that are to replace current requirements. Attach a marked print when necessary to clearly explain the desired revision. Use a "From- To" format in the description of the change.

Delaware		000-54144		333-143215
(State or other jurisdiction of incorporation)		(Commission File Number)		(IRS Employer Identification No.)

1420 Presidential Drive, Richardson, TX		75081-2439
(Address of principal executive offices)		(Zip Code)

	Optex Systems Holdings, Inc.
	(Registrant)

	By:	/s/ Stanley A. Hirschman
		Stanley A. Hirschman
	Title:	President

E-5	52.246-4533	SURFACE QUALITY STANDARDS	MAR/2001
	TACOM (RI)

E-8	52.246-4028	INSPECTION AND ACCEPTANCE POINTS: ORIGIN	NOV/2005
	(TACOM)

	Reference No. of Document Being Continued		Page 11 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

	Reference No. of Document Being Continued		Page 12 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

INSPECTION	POINT:	OPTEX SYSTEMS, INC. OBK64
		1420 PRESIDENTIAL DRIVE, RICHARDSON	TX	75081



ACCEPTANCE	POINT:	SAME AS ABOVE

	Reference No. of Document Being Continued		Page 13 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

	g'dl i.QJ:;:y_Qil_	——————————————— ill ———————————————	—— 1 ——
F-1	52 .211-17	DELIVERY OF EXCESS QUANTITIES	SEP/1989
F-2	52 .242-15	STOP-WORK ORDER	AUG/1989
F-3	52 .242-17	GOVERNMENT DELAY OF WORK	APR/1984
F-4	52 .247-34	F O.B. DESTINATION	NOV/1991
F-5	52 .247-48	F O.B. DESTINATION— EVIDENCE OF SHIPMENT	FEB/1999
F-6	252 .211-7006	RADIO FREQUENCY IDENTIFICATION	FEB/2007

F-7	252 .211-7003	ITEM IDEN"TIFICATION AND VALUATION	AUG/2008

	Reference No. of Document Being Continued		Page 14 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

Contract Line,
Subline, or
Exhibit Line Item Number	Item Description

	Reference No. of Document Being Continued		Page 15 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

	Reference No. of Document Being Continued		Page 16 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

ITEM NO.	QTY	WITHIN DAYS AFTER DATE OF CONTRACT AWARD
0001AA	52	330

	Reference No. of Document Being Continued		Page 17 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

F-9	52.247-4009	DELIVERY OF SUPPLIES FROM FOREIGN FIRMS TO U.S. PORT OF ENTRY	AUG/2003
	(TACOM)

F-10	52.247-4017	DEPOT ADDRESS FOR THE APPLICABLE MODE OF SHIPMENTS:	IN-THE-CLEAR	NOV/2009
	(TACOM)	ADDRESSES

Rail/	MILSTRIP
Motor	Address	Rail	Motor	Parcel Post
_g_1,	QQQ —	hii2TQ_;_	il2...T_Q_:_	.!1.§i.l T_Q_;_

206721/	W25G1U	Transportation Officer Defense Dist Depot	Transportation Officer Defense Dist Depot	Transportation Officer Defense Dist Depot
209405		Susquehanna	Susquehanna	Susquehanna
		New Cumberland, PA	New Cumberland, PA	New Cumberland, PA 17070-5001

	Reference No. of Document Being Continued		Page 18 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

875670/	W62G2T	Transportation Officer	Transportation Officer	Transportation Officer
875675		XU Def Dist Depot	XU Def Dist Depot	Dist Depot San Joaquin
		San Joaquin	San Joaquin	P 0 Box 96001
		25600 S Chrisman Rd	25600 S Chrisman Rd	Stockton, CA 95296-0130
		Rec Whse 10	Rec Whse 10
		Tracy, Ca 95376-5000	Tracy, Ca 95376-5000

471995/	W31G1Z	Transportation Officer	Transportation Officer	Transportation Officer
471996		Armiston Army Depot,	Anniston Army Depot,	Armiston Army Depot,
		Bynum, AL	Bynum, AL	Armiston, AL 36201-5021

209741/	W25G1R	Transportation Officer	Transportation Officer	Transportation Officer
209770		Letterkenny Army Depot,	Letterkenny Army Depot,	Letterkenny Army Depot,
		Culbertson, PA	Chambersburg, PA	Chambersburg, PA 17201-4150

661136/	W45G19	Transportation Officer	Transportation Officer	Transportation Officer
661157		Red River Army Depot,	Red River Army Depot,	Red River Army Depot,
		Defense, TX	Texarkana, TX	Texarkana, TX 75507-5000

764538/	W67G23	Transportation Officer	Transportation Officer	Transportation Officer
764535		Tooele Army Depot,	Tooele Army Depot,	Tooele Army Depot,
		Warner, UT	Tooele, UT	Tooele, UT 84074-5003

	Reference No. of Document Being Continued		Page 19 of 36
CONTINUATION SHEET
	PIIN/SIIN SPRDLl-12-C-0023	MOD/AMD
Name of Offeror or Contractor: OPTEX SYSTEMS, INC.

	PRON/
LINE	AMS CD/	OBLG				OBLIGATED
l _!L	.!1l.ffi_____	.0ZbT_	.JQ_NQ_	b.QBH		b.!1Q1ITIT ____
OOOlAA	M112A243Ml	2		AA		1,152,272.20
	SM2B1100000

					TOTAL	1,152,272.20

ACCOUNTING CLASSIFICATION					OBLIGATED
					b.!1Q1ITIT_
97	X4930AC9D 6D	26KB	S20113		$ 1 2 J1J JQ

				TOTAL	1,152,272.20

LINE
l _!L	ACRN	EDI/SFIS ACCOUNTING CLASSIFICATION
OOOlAA	AA	97	OXOX4930AC9D	S20113	6DOOOOSM2B110000026KB	S20113	W56HZV

	g	LQli ——————————— ill—————————	—— 1 ——

G-1	52.204-4011	PAYMENT INSTRUCTIONS FOR THE DEFENSE FINANCE AND ACCOUNTING SERVICE	OCT/2005
	(TACOM)	(DFAS)

CONTINUATION SHEET	Reference No. of Document Being Continued	Page 20 of 36

	PIIN/SIIN SPRDLl-12-C-0023 MOD/AMD

H-1	252.222-7006	RESTRICTIONS ON THE USE OF MANDATORY ARBITRATION AGREEMENTS	DEC/2010

H-2	52.204-4005	REQUIRED USE OF ELECTRONIC CONTRACTING	SEP/2004

H-3	52.245-4500	DEMILITARIZATION AND TRADE SECURITY CONTROL REQUIREMENTS AND PROCEDURES	OCT/2006
	TACOM LCMC
	(RI)

CONTINUATION SHEET	Reference No. of Document Being Continued	Page 21 of 36

	PIIN/SIIN SPRDLl-12-C-0023 MOD/AMD

CONTINUATION SHEET	Reference No. of Document Being Continued	Page 22 of 36

	PIIN/SIIN SPRDLl-12-C-0023 MOD/AMD

CONTINUATION SHEET	Reference No. of Document Being Continued	Page 23 of 36

	PIIN/SIIN SPRDLl-12-C-0023 MOD/AMD

T l J	lli ri i _@Q Q lli ri i _@Q	liY Q § g QL
	g g - lii k- lri

	Demil Code	Demil Req'd	No Demil Req'd	TSC Required
Non-MLI/or Non-CCLI	A Commercial		X
MLI-Non-SME	B		X	X EUC DLA Form 1822
MLI/SME	C	X		X EUC DLA Form 1822
MLI/SME	D	X		X EUC DLA Form 1822
MLI/Non-SME	E	X		X EUC DLA Form 1822
MLI/SME	F	X		X EUC DLA Form 1822
MLISME	G	X		X EUC DLA Form 1822
MLI/SME	P	X		X EUC DLA Form 1822
EAR/CCLI	Q Dual Use/ Commercial		X	X EUC DLA Form 1822
HS7144