JDAM_Combined_SOO_24_May_13.docx

1 April 2013

STATEMENT OF OBJECTIVES

FOR

JOINT DIRECT ATTACK MUNITION (JDAM)

INDEFINTE DELIVERY, INDEFINITE QUANTITY (IDIQ) Lots 18-22

Production and Technical Support Services

May 2013

PREPARED BY:

Mark Kiedrowski

AFLCMC/EBHGC

6034 Dogwood Ave

HILL AFB, UTAH 84056

Phone: 801-775-2220 Mark.kiedrowski@hill.af.mil

Introduction: Desert Storm demonstrated the need for more accurate delivery of munitions in adverse weather. The Joint Direct Attack Munition (JDAM), which evolved from that need, is a low cost GPS aided inertial guidance kit for inventory 500 lb., 1000 lb., and 2000 lb. bombs. This Requirements Document outlines the tasks needed to successfully produce the JDAM kit. The total quantities to be procured are to replace units used in test, training and operations. The specific and detailed tasks needed to accomplish this may be found in other program documentation. The overarching objective of this procurement is to acquire Joint Direct Attack Munition (JDAM) tail kits.

1. Production Objectives: This JDAM requirements document requires manufacture, test, and delivery of JDAM assets IAW Contract requirements. The following requirements describe general tasks/deliverables required by the contractor per this Contract.

The hardware provided by the contractor under this effort shall perform in accordance with the System Requirements Document (SRD) and be fully integrated and qualified for employment from the aircraft identified in the SRD.

1.1. GPS Procurement Authorization: To meet Selective Available Anti-Spoofing Module (SAASM) requirements for JDAM production, the contractor will be required to coordinate with the GPS Wing to obtain the necessary encrypted Global Position System (GPS) SAASM Receiver Modules.

1.1.1. The contractor shall submit ATP requests directly to the GPS Wing via the ACN/KLIF automated system. The GPS Wing will notify the contractor of approval/disapproval within 72 hours of submittal.

1.2. Program Management

1.2.1. The contractor shall assure programmatic updates, including, but not limited to, information on current production line status/issues, Engineering Change Proposal (ECP)/Deviation/Waiver status, sub-contractors status/issues, contracts/funding issues, and risk management reviews. Programmatic updates shall be provide through:

1.2.1.1. Weekly FOG telecoms.

1.2.1.2. Weekly engineering telecoms (as required).

1.2.1.3. Weekly Configuration Control Board (CCB) meetings (as required).

1.2.1.4. Reliability Assessment Team (RAT) meetings, 3 times per year.

1.2.1.5. Alternative Dispute Resolution Meetings (as required) or Program Execution and Planning Review (annually).

1.3. Systems Engineering: The contractor shall include tasks which ensure that performance, safety, reliability, software development, service life, product assurance, human factors, testability, logistics, and producibility are addressed throughout the program. The utilization of systems engineering practices to ensure that appropriate consideration of all aspects of the life cycle and utilization is expected.

1.3.1. Quality Assurance: The contractor shall include tasks to establish, implement, and maintain a quality assurance program acceptable to the Government. The quality program is expected to conform to the ISO 9000 series.

1.3.2. Reliability: The Contractor shall provide adequate production, test and logistics (warranty) support to ensure and maintain operational readiness and suitability of the JDAM weapon system.

1.3.2.1. The Contractor shall provide shipping to CONUS locations and meet any required First Article Testing within total funding available for weapons system production.

1.3.3. Acceptance Testing: The contractor shall provide an Acceptance Test Plan to detail criteria, performance objectives and list of tests to be performed by the contractor for acceptance tests on production systems and equipment. DI-QCIC-80553A

1.3.3.1. If required, the contractor shall coordinate with the Government Engineer on all Test Plans and submit the required documentation IAW DI-NDTI-80809B

1.3.4. Risk Management: The contractor shall keep an internal Risk Management plan/matrix to effectively evaluate, manage and resolve potential risks that may arise during production. This plan/matrix shall be discussed as needed in meetings per section 1.1 above.

2. Technical Support Services Objectives: The tasks listed below are the contractual objective and obligations to be fulfilled by the contractor. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the JDAM/LJDAM Technical Service Program via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.

2.1. Task 1: Tech Management/Coordination and Government Directed Support

2.1.1. Provide management for activities under this sustaining contract to include, but not limited to, task planning, scheduling, tracking, reporting progress/status, and financial reports.

2.1.2. Provide on-site, at Hill AFB, coordination and administration of miscellaneous sustaining technical support tasks and maintain cognizance over these activities to properly channel requests and directions and to ensure timely action and response, if required.

2.1.3. Answer or coordinate answers to quick reaction questions as they arise (e.g., quick reaction data tape review, engineering inquires, etc.)

2.1.4. Prepare and coordinate estimates and responses to a government-initiated Statement of Objectives (SOO) or Statement of Requirements (SOR) with a task description and a Cost Element Summary or proposal for all tasks. These products will be coordinated with appropriate government personnel and, if approved, the government will issue a delivery order or modification to a delivery order.

2.2. Task 2: JDAM Weapon System Program Support

2.2.1. Reserved for Eglin

2.3. Task 3: Non-Warranty Support

2.3.1. Support the induction, evaluation, and proposal preparation on JDAM/LJDAM Weapon System failures of Non-Warranted Kits.

2.3.2. Prepare a proposal to return the hardware to a serviceable condition and ship to a destination provided by the JDAM/LJDAM System Program Office (SPO). The proposal preparation charges for all tasks shall be funded under Task 1. This hardware will include, but is not limited to, guidance kits, telemetry kits, load trainers, Separation Test Vehicles, Enhanced Guided Test Vehicles and simulators. (Actual repairs will be accomplished via Task 5.)

2.3.3. Section H Clause, H-011 Non-Warranty Pricing Agreement applies to Non-Warranty production assets.

2.3.4. Modify existing web based JDAM/LJDAM Asset Tracking Database to specifically identify the status of Non-Warranted kits at Boeing.

2.4. Task 4: Aircraft/Weapon System Support

2.4.1. Reserved for Eglin

2.5. Task 5: System Field Support

2.5.1. Provide IPT ILS Support to JDAM/LJDAM field operations. This will include, but is not limited to, approximately 4 meetings per year, monthly telephone conferences and response to action items.

2.5.2. Support the fielded system support equipment.

2.5.3. Support the JDAM weapon as deployed in the field.

2.5.4. Review and update JDAM field support data, as required, including but not limited to: -7, –33 and -34 source data, Technical Data Packages, and Technical Publications.

2.6. Task 6: JDAM/LJDAM Asset Tracking Interface and Ordnance Information System (OIS) Interface

2.6.1. Maintain the Air Force web based JDAM Asset Tracking interface for production delivery assets, status updates, retrofit, repair/modification assets, and/or warranty/non warranty actions.

2.6.2. Report monthly or as required, warranty and non-warranty asset receipts and shipments from the repair facility.

2.6.3. The contractor shall maintain the Security Tracking and Authorization Request System (STARS) Account Custodian (SAC) responsibility reporting to the Key Data Processor (KDP) Loading and Installation Facility (KLIF) for Global Positioning System (GPS) Precise Positioning System (PPS) Host Application Equipment (HAE) transfer notices, receipts of delivery, destruction notices and lost or missing reports shall be reported to the KLIF by the SAC.

2.6.4. Provide the Ordnance Information System (OIS)-ATR for Navy/fleet returned assets only (IAW DI-MGMT-80321/T and per attachment 1).

2.7. TASK 7: Non-Warranty Repair

2.7.1. When directed by the PCO, return to serviceable condition, test and ship non-warranty hardware that requires repair.

2.7.1.1. Repair costs will be determined using Catalog Pricing established under contract FA8681-05-D-0277, Mod 00021 (Sep 2011 – Sep 2015). When that Contract Pricing expires, Boeing shall work with the JDAM Program office to establish updated Catalog Pricing for the remainder of the contract period (Sept 2015 – Jan 2020).

3. Contractor Cost and Data Reporting

3. The following forms/exhibits shall be completed by the contractor:

0. DD Form 1921 IAW DI-FNCL-81565C

0. DD Form 1921-1 IAW DI-FNCL-81566C

0. DD Form 1921-3 IAW DI-FNCL-81765B

0. DD Form 1921-4 IAW DI-FNCL-81831

0. Contractor Work Breakdown Schedule IAW DI-MGMT-81334D

Attachment 1

NAVSUP P-724 REV 18, CONVENTIONAL ORDNANCE STOCKPILE MANANAGEMENT

DATA ITEM DESCRIPTION: DID80321REVA

Title: AMMUNITION TRANSACTION REPORT (ATR) Approval Date: YY/MM/DD Number: DI-MGMT-80321A Limitation:

AMSC Number: 7295 GIDEP Applicable:

DTIC Applicable:

Office of Primary Responsibility: NAVSUP GLS AMMO Applicable Forms:

Use, Relationship: The ATR supports the reporting requirement for ammunition material located at commercial facilities. The ATR provides stock status data to the Ordnance Information System-Wholesale (OIS-W).

a. This DID contains format and c ontent preparation instructions for the data product resulting from the work task described in the contract SOW.

b. This DID supersede DI-MGMT-80321.

c. The reference documents contained in this DID may be obtained from NAVSUP GLS AMMO), 5450 Carlisle Pike, Code N41, Mechanicsburg, PA. 17055.

Requirements:

a. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, will be as cited in the current issue of the DODISS at the time of the solicitation.

b. Format. The ATR will be presented as shown in Figure 1 of this DID.

c. Content. The ATR will consist of the information as specified in the NAVSUP P- 724, paragraph 2.3.4. It will contain:

(1) In the message heading, a “P” in position 1 to indicate a priority report, "TT" in positions 2 and 3 to indicate the Language Media Format (LMF) Code, “U” in position 4 to indicate unclassified, and startup code of “NBAT” in positions 5-8.

(2) The “TO” address will be “NAVAMMOLOGCEN MECHANICSBURG PA//431//,” a “BT” will indicate the beginning of the transmission, and t he subject will be “AMMO TRANS RPT RCS NAVSUP P-724."

(3) Report Body. The body of the report will contain an A TR header line and one or more transaction lines.

d. Header line. The header line begins with four slashes, is left justified, contains one slash between each data field, and ends with three slashes. The header line consists of:

(1) Contractor Unit Identification Code (UIC). A 6-digit code consisting of a 1- digit alpha service code followed by a uni quely assigned 5-digit numeric identification code will be entered.

(2) ATR Serial Number. A 3-digit numeric code running sequentially from 001 to 999 will be entered. Upon reaching serial number 999, the unit reverts to 001 restarting the sequence.

(3) Activity Classification Code (ACC) - A 1-digit alpha code indicating the reason material is being held. “M” will be us ed for new production assets and “T” for repair of Navy-owned assets.

(4) Transaction Date. A 3-digit numeric Julian date entered to indicate the day the action occurred.

e. Transaction Lines. The ATR will contain as many transaction lines as necessary to report repair or new production actions which take place in a given day. Transaction lines begin with three slashes, are left justified, contain two slashes before each transaction code, one slash between other data elements, and end in three slashes. Continuation lines between sets of three slashes will be indented not less than three spaces. Transaction lines consist of:

(1) Navy Ammunition Logistics Code (NALC) and N ational Item Identification Number (NIIN). A 4-digit alphanumeric NALC and 9-digit numeric NIIN that is combined together without separation by slashes or dashes. Items without a NALC may be reported using the NIIN only. Items with only one NIIN may be r eported by NALC only. The NALC/NIIN combination will be preceded by three slashes (///PM69013749533).

(2) Condition Code. A 1-digit alpha character used to indicate the condition of the ammunition at the time of transaction. The condition code will be preceded by a single slash (/F).

(3) Beginning Balance. Numeric digits indicating the beginning inventory balance for a NALC/NIIN in a given condition code. The quantity will be preceded by the letter “B” (beginning) preceded by a double slash (//B6).

(4) Transaction Code. A 1-digit alpha character describing the type of transaction, i.e. receipt (C), issue (D), or change of condition code (X) preceding numeric digits indicating the quantity effected by the transaction. The transaction code will be preceded by a double slash, Receipts (//C2). For reclassification of condition codes, the “X” will be preceded by a double slash followed by the new condition and quantity, Reclassifications (//XM2).

(5) Serial/Lot Number. NIINs assigned a M aterial Control Code (MCC) of “B” require lot number reporting. NIINs assigned an MCC “C” require serial number reporting. NIINs with the MCC “E” require both serial and l ot reporting with a period separating the serial and lot number. The serial and lot numbers will be pr eceded by one slash (/NX0034). For MCC “B” items, only one l ot number applies to the transaction quantity preceding it. For MCC “C” and “E” items, multiple serial or serial and lot numbers may apply. Multiple serial and l ot numbers are separated by a slash (/NX0034/NX00318) or (/NX00034.ABC/NX00318.XYZ). Following each serial number, in parentheses, will be a 1 -digit alpha Type Container Code, and a 3 -digit alpha or numeric Maintenance Due Date (MDD), (/NX00034 (X202)). The first digit of an MDD indicates the month (1-9 January – September; (alpha) O for October, N for November and D for December). The last two digits indicate the year.

(6) Source Code. Source codes are required on receipt, issue, loss, and transfer transactions. Source codes will follow the lot and s erial numbers proceeded by a slash or, follow the transaction quantity preceded by a slash when lot or serial numbers are not required. Non-serial or lot reportable (//C2/ASSEM). Serial reportable (//C2/NX00034 (X202C)/NX00318 (X102C)/ASSEM).

(7) Document Number. A document number will be ent ered when the Source Code is a U nit Identification Code indicating material was received from or issued to another activity. (//C2/NX00034 (X202C)/NX00318 (X102C)/N00109/N4993512578A01).

(8) Ending Balance. Numeric digits proceeded by the letter “T” indicating the ending inventory balance for a N ALC/NIIN in a given condition code. The ending balance is preceded by a double slash and ends with three slashes. The three slashes indicate the end of the transaction line (//T8///).

f. End of Ammunition Transaction Report. Four slashes left justified on the line below the last transaction indicate the end of an ATR. (////).

g. End of Transmission. Four “Ns,” left justified, on the line below the four slashes indicate end of transmission. (NNNN).

JDAM Lot 18-22 SOO/May 2013

FIGURE 1

PTTUNBAT

P 081500Z MAR 04

FM RAYTHEON BRISTOL TN

TO NAVAMMOLOGCEN MECHANICSBURG PA//431// BT

UNCLAS //N08015//

SUBJ: AMMO TRANS RPT RCS NAVSUP P-724

////Q94307/657/T/274///

///PM69013749553/F//B6//C2/NX00034(X202C)/NX00318(X102C)

/N00109/N4993512578A01//T8///

///PM69013749553/F//B8//XM2/NX00034(X202C)/NX00318(X102C)

//T6///

///PM69013749534/F//B0//C5/HXB0006369(YN01L)/HXB01090(YN01L)

/800697(YN01C)/800888(YO01L)/HXB00636(YN01C)/N00109/N4993512608A01//T5///

///PM69013749534/F//B5//XM5/HXB00636(YN01L)/HXB01090(YN01L)

/800697(YN01C)/800888(YO01L)/HXB00636(YN01C)//T0///

///PT35/F//B4//D2/88043(YO001C)/88077(YO01C)/RCNFG//T2///

///PL27/A//B2//D2/MVR01545(Y510L)/MYL00007(Y510L)/N60036

/N0010400CKA58//T0///

REMARKS: Point Of Contact (Name, Phone, and Email) BT

NNNN

FD2020-12-77178