Data Item Descriptions (DIDs).pdf

DATA ITEM DESCRIPTION

Title: CONFERENCE AGENDA

Number: DI-ADMN-81249B Approved Date: 20160524 AMSC Number: F9658 Limitation:

DTIC Applicable: GIDEP Applicable:

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: ADMN-2015-002 Applicable Forms: None Use/Relationship: The Conference Agenda provides information concerning purpose, location, and schedule of conferences required to manage the acquisition of systems equipment, related items, and services.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

b. This DID supersedes DI-ADMN-81249A.

Requirements:

1. Reference documents. None.

2. Format. Contractor format is acceptable.

3. Content. The agenda shall include the following, where applicable:

a. The purpose and objective of the conference.

b. The conference location, date, and duration.

c. A daily chronological listing of each major topic or subtopic to be discussed and the time to be devoted to each topic.

d. A list of activities to be represented and identification of their responsibilities.

e. A list of subcommittees to be established during the conference and the proposed activity representation for each subcommittee.

f. Reference to and brief description of the results of previous meetings, when relevant.

g. Location, schedule, and purpose or subject area to be covered by each subcommittee, when applicable.

h. Names of the conference chairperson, co-chair, and subcommittee chairs, when applicable.

i. Information on billeting, messing, transportation, and administrative services available to conference attendees.

j. Complete list of all documentation to be available for review.

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

DI-ADMN-81249B

k. Brief description of progress on actions or problems identified at previous meetings, when applicable.

l. Other pertinent information such as Forms to be used, identification of any deviations or waivers, security classification, and clearance requirements.

End of DI- ADMN-81249B

Title: CONFERENCE MINUTES

Number: DI-ADMN-81250B Approved Date: 20160524 AMSC Number: F9659 Limitation:

DTIC Applicable: GIDEP Applicable:

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: ADMN-2015-001 Applicable Forms:

Use/Relationship: Conference minutes provide documentation of technical information provided and decisions and agreements reached at meetings.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

b. This DID supersedes DI-ADMN-81250A.

Requirements:

1. Reference documents: None.

2. Format. Contractor format is acceptable.

3. Content. The minutes shall include the following information:

a. A title page containing the following:

(1) Title – type of meeting and date.

(2) Identification of the acquisition (system, equipment, contract number) for which the meeting was held.

(3) Space for signatures of the designated representatives of the contractor and acquisition activity.

(4) The name of the contractor and address to which the acquisition activity should acknowledge receipt of comments.

b. The purpose and objective of the conference.

c. The conference location.

d. A summary of the discussions, decisions, agreements reached, and directions of the conference or individual subcommittees thereof.

e. A list of attendees by name, rank, grade or position, activity represented, activity symbol/code, phone numbers, and emails, as appropriate.

f. Action items resulting from the conference.

g. Briefing charts, if presented, shall be attached to the minutes for information only.

End of DI- ADMN-81250B

Title: REPAIR/MODIFICATION/OVERHAUL STATUS REPORT

Number: DI-MGMT-80933A Approval Date: 20170531 AMSC Number: 9812 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: MI Project Number: MGMT-2017-024 Applicable Forms: N/A

Use/relationship: This Data Item Description (DID) provides information on contractual maintenance programs applicable to military equipment.

a. This DID contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

b. This DID supersedes DI-MGMT-80933.

Requirements:

1. Reference documents. None.

2. Format. The Repair/Modification/Overhaul Status Report shall be in a contractor selected format.

3. Content. The Repair/Modification/Overhaul Status Report content shall be as follows:

a. Contract Number.

b. National Stock Number for each item prior to work.

c. Program quantity for each National Stock Number item.

d. Quantity completed to date on each National Stock Number item.

e. Work in process quantity on each National Stock Number item.

f. Unserviceable on hand quantity to date on each National Stock Number item.

g. Identification and explanation of delays, accelerations, and problems.

h. Consumption data.

i. Charges billed to date.

End of DI-MGMT-80933A.

Title: COMPREHENSIVE ENGINE MANAGEMENT SYSTEM (CEMS) REPORTING Number: DI-MGMT-81324C Approval Date: 20150505 AMSC Number: F9543 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing activity: 71 Project Number: MGMT-2015-018

Applicable Forms: CEMS Event Reporting Document, DD Form 2875 (GCSS), DD Form 2875 (CEMS), and Non- Disclosure Statement.

Use/relationship: CEMS reporting is required by all organizations possessing and/or maintaining Air Force (AF) engines or components on behalf of the AF to maintain a complete and accurate worldwide inventory of AF engines, installed assemblies and components. The CEMS reporting data consists of aircraft engine and maintenance status information as directed by the AF propulsion community.

a) This Data Item Description (DID) contains the instructions for reporting engine, assembly and/or component status data to the AF Accountable Property System of Record (APSR), CEMS. It also contains the format and content preparation instructions for the data reporting generated by the specific and discrete task requirement as delineated in the contract.

b) This DID is applicable when contractors are required to report engine and/or component status data to

CEMS.

c) Publications referenced below are available on the CEMS web site, https://www.my.af.mil/gimmsprod/cpmo/.

d) This DID supersedes DI-MGMT-81324B.

Requirements:

1. Reference documents: The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract. Definitions and/or descriptions of the various data codes authorized for entry in the specified blocks of the CEMS Event Reporting Document are contained in United States Air Force Technical Order (TO) 00-25-254-1.

2. Format. Unless an agreed upon approved interface exists, all required input is via the reporting process known as

CEMS.

3. Content.

3.1 Access to CEMS: In order to accomplish access to government computer systems for the purpose of reporting the following is required:

a. The minimum of a favorable National Agency Check with Inquiries (NACI) is required for any contractor accessing Department of Defense (DoD) information systems. Procedures concerning Industrial Security Clearances and Investigations can be found at http://www.dss.mil/isp/index.html.

b. An DD FM 2875 must be completed and sent by fax or signed email to the AF Portal Program Office:

gcssaf.opsandsupport@gunter.af.mil, or faxed to the AF Portal Program Office (DSN 596-5771, or faxed to the AF Portal Program Office DSN 596-5771, Commercial 334-416-5771; Option 7) to obtain an AF Portal Account. DD FM 2875, as well as additional information may be obtained at https://www.my.af.mil, by accessing “View Account Requirements & Benefits.”

c. After AF Portal access is obtained, a DD Form 2875, a copy of the DoD Information Assurance Awareness Training Certificate (Course: ZZ133098) and a Nondisclosure Statement must be completed requesting access to CEMS and e-mailed to CEMS.PMO.Security@us.af.mil. The form and Nondisclosure Statement may be downloaded from https://www.my.af.mil/gimmsprod/cpmo/, by clicking on the “Forms” folder and clicking “System Access.” Instructions are included with the form. The DoD Cyber Awareness Challenge (Course: ZZ133098) may be completed:

DI-MGMT-81324C

https://golearn.csd.disa.mil/kc/login/login.asp?kc_ident=kc0001&blnAccess=TRUE for Dot-Mil Users and http://iase.disa.mil/eta/cyberchallenge/launchPage.htm for Dot-Com users.

d. You can only access CEMS via the AF Portal. The CEMS PMO, (405)734-7874, DSN: 884-7874, or Toll Free: 1-800-956-7351, should be contacted for further information.

3.2 Inputs to CEMS: Description of Entries on the CEMS Event Reporting document.

Block 1 - CII Designation. Direct reporting and mail-in enter CII as shown in the CII table.

Block 2 - S/N (10 Max Alpha Numeric characters). Enter the S/N as express below for position 1 thru 4 and using the last 6 characters listed on the data plate. CEMS does not recognize a dash (-). If dashes (-) are encountered on the engine, assembly or part data plate, the dash will be replaced with a zero for reporting purposes. If data plate contains any other special character, contact the CEMS PMO for instructions.

Example: 629-1234 will be input to CEMS as “0062901234.” The standard method of structuring serial numbers in CEMS is as follows:

MM = Manufacturer’s Code (two position) Z = Zero (0) C = Engine module symbol as follows:

Basic Engine E Augmentor A Fan F Compressor C Turbine (LPT) L Turbine (HPT) H Gearbox G Turbine T

X= An alpha or numeric character

NOTE

With the exception of the F107 engine, all century series engines (i.e. F100, F101,etc.) and T56 engines use structure MMZCXXXXXX, where column 5 through 10 are the values obtained from the last 6 positions on the data plate. The field will be moved to the right and zero filled on the left.

Examples: F100-100 Engine “PW0E680092.” “T56 engine S/Ns prior to 113432 will reflect the old S/N structure in CEMS of MMZZXXXXXX. T56 gearbox S/Ns prior to S/N 33641 will reflect the old S/N structure in CEMS of ZZMCXXXXXX. T56 engine 113432 and beyond will use MMZCXXXXXX.”

Example: (AD0E113432), Gearbox 33641 and beyond will use MMZCXXXXXX.

Example: (AD0G033641), All other aircraft engines use structure MMZZXXXXXX, where column 5 through 10 are values obtained from the last 6 positions on the data plate. The field will be moved to the right and zero filled on the left.

Example: J75-17 Engine “PW00611438.” All tracked assemblies and parts and all non-F100 modules use structure 10 positions. All 10 positions are values obtained from the data plate. The field will be moved to the right and zero filled on the left. The alpha O will be converted to numeric 0 and the alpha I will be converted to numeric 1 for reporting purposes.

Block 3 - Occurrence Date and/or Hour. Enter the actual Julian date and time the status change occurred.

Block 4 - SRAN. Enter SRAN of the activity preparing report.

Block 5 - Command. Enter the applicable major and subcommand codes.

Block 6 - Organization Code. Alpha characters for local use and is one position alpha, excluding “X” or a numeric “1” to indicate engine(s) in a deployed status.

Block 7 - Engine Ownership Account. Enter the one position engine ownership account code. Account codes A, B, C, E, G, K, L, N, P, R, S, and Z are Air Force engines. Transfers between these accounts will be made on routine reports (code R, block 8). Account codes D, F, H, J, T, and W are other than Air Force engines. Transfer between Air Force and other than Air Force accounts will be made on K type report (block 8). All uninstalled engine transfers on K type reports must be documented and a copy of the document maintained as prescribed in referenced TO. If account code J is reported, see instructions (block 19). Engines transferred to classified project (L account, routine report) will not be reported thereafter until returned or until the classified project is canceled. Returns from a classified project will be reported as a receipt to the A-account on a routine report. Engines assigned to ground training (S account) require no subsequent reporting except when engines are installed, removed, or transferred, or when assignment to S account terminates. Engines installed and removed for training are to be considered as installed at all times. Engines received from other than Air Force activities for repair and return are to be retained in the activity’s account while on hand. If an exchange of engines with the Air Force is to be accomplished, the transfers between accounts will be made on K type reports.

Block 8 - Engine Type Report. Enter the appropriate report code IAW the referenced TO.

Block 9 - Part Number. Enter the part number from the data plate.

Block 10 - Transaction Code. Circle the appropriate transaction code.

Block 11 - Condition Code. Circle the appropriate engine condition code.

Block 12 - Miscellaneous System Update. Circle the appropriate system update code.

Block 13 - To-From Command and/or SRAN. Enter the shipped to-from SRAN. Report the owning command code for tenant shipments and receipts. Block will be blank for reports of transfer to or from classified projects.

Block 14 - Type of Shipping Device. Optional.

Block 15 - Engine Related How Mal Codes. Enter the engine related How Mal Code that best identifies the symptom that is causing the removal.

Block 16 - Reason for Return to Overhaul. Enter appropriate reason for return to overhaul code.

Block 17 - Reparable Engine S/N. Optional or enter the S/N of the reparable engine being replaced by the serviceable shipment. This number or the word stock will be furnished by the EIM. If a number or the word stock is not furnished by the EIM, enter “Not Furn.”

Block 18 - PRIMARY/SECONDARY HOW MAL INDICATOR, P (Primary) S (Secondary) (CIRCLE ONE)

Block 19 - SAP number. On K reports for engines gained to or from a SAP country, enter the six position SAP ID number contained in the supplementary address field, card columns 45 through 50, of the DD Form 1348-1A. If the SAP number is not listed in the supplementary address field, contact the prime EIM.

Block 20 - Document Number-NSN. Enter the debit or credit number from the document covering gain and loss transactions. For all shipments and receipts of uninstalled engines to-from a different SRAN reporting activity, enter the TCN from card columns 30 through 43 of the DD Form 1348-1A or block six of DD Form 1149, REQUISITION AND INVOICE/SHIPPING DOCUMENT. If not received with the engine, contact the previous SRAN EM for the TCN the engine was shipped with.

Also, if the shipment has been reported to CEMS, the TCN will appear on part 2 of the EMDL. For uninstalled reimbursable account transfer (K type report), to a non-Air Force account (SAP, Navy, Army, FAA, etc.), report the requesting activities requisition number obtained from the prime EIM.

Document numbers are constructed following the guidance in DOD 4000 25-1-M, Military Standard Requisitioning and Issue Procedures (MILSTRIP), or per instructions in AFM 23-110 and/or applicable Supply Local Operating Instructions.

Position 1-6 DOD Activity Address - Code of Activity assigning the num-ber e.g. FJ2039 (FJ suffix is used for Air Force reporting and EJ suffix is used for Contractor)

Position 7 Last digit of the calendar year Position 8-10 Julian day of document assignment Position 11-12 S/N assigned by activity Position 13-14 Two digit alpha engine ID code

NSN is constructed as follows:

Position 1-4 Federal Stock Class, e.g., 2840 Position 5-6 Country Code, e.g., 01 (USA) Position 7-13 National Item Identifier Number (NIIN) e.g., 5869746 Position 14-15 Material Management Code (MMC), e.g., RU, if applicable

Block 21 - Engine Flying Time. For non-parts tracked (status) engines, enter TSO. Time is recorded in days, hours, or minutes as required by engine TMSM. The number is right justified with a single decimal place. The fraction of hours is rounded (up or down) to the nearest tenth of an hour. Time will be reported in whole minutes for the J69- 406 engines. Time will be recorded in whole calendar days on the F107 and F112 engines.

Block 22 - Cycle Sortie Count. Enter cycle sortie count.

Block 23 - TMSM. Enter the TMSM for the engine that is being reported. TMSM is defined as a 12 position field for TMS and Modification of a given engine family.

Position 1-3 Type (alphanumeric, right justified, prefix with spaces) Position 4-7 Model (alphanumeric, right justified, prefix with zeros) Position 8-10 Series (alphanumeric, right justified, prefix with zeros) Position 11-12 Modification (alphanumeric, left justified, suffix with spaces)

Reference TMSM table.

Block 24 - NHA Designation. When entry is required and the NHA is an aircraft, enter the seven position alphanumeric MDS; or enter the NHA seven position alphanumeric CII code. When entry is required and the report initialized (TCC 6N) an uninstalled tracked item, fill all seven positions with nines.

Standard MDS structure is as follows:

Position 1-3 Mission (alphanumeric, right justified, prefix with spaces)

Position 4-6 Design (alphanumeric, right justified, prefix with zeros) Position 7 Series (alphanumeric)

Block 25 - NHA S/N Structure. For aircraft S/N, use YYNNNNNNNN where YY is year of manufacture and NNNNNNNN is the tail number prefixed with zeros. When an initialization entry (TCC 6N) is required on an uninstalled tracked item, fill all 10 positions with nines.

Block 26 - Position Number. If the engine being reported is applicable to a single QPA, enter the digit one. For multiple engine aircraft, engines will be numbered from left to right from pilot’s position. Missiles and tracked assemblies/parts are exempt from this entry.

Block 27 - Is used when additional information is required on CEMS Event Report, i.e., Reason for Delay Codes.

End of DI-MGMT-81324C

1. CII DESIGNATION 2. SERIAL NUMBER 3. OCCURRENCE 4. SRAN 5. CMD 6. ORG 7. ACCT

3a. DATE 3b. HOUR

8. Type Report 9. PART NUMBER 14. SHIPPING DEVICE 13a. CMD

12. MISC SYSTEM UPDATES

GAIN SERVICEABLE COMMAND CODE CHANGE 2C 15. ENG RELATED 16. REASON FOR 17. REPARABLE ENG

NEW PRODUCTION A BUILT-UP B ACCOUNT CODE CHANGE 2D HOW MAL CODE RETURN TO OVHL SERIAL NUMBER

REIMBURSABLE B RAW R ORG CODE CHANGE 2M

NON-REIMBURSABLE C MDS/POSITION CHANGE 2P

EXCHANGE D REVERSE SHIP/TRANS 2R 18. PRIMARY/SECONDARY HOW MAL 19. SAP NUMBER

REPARABLE ADD TIME 6A INDICATOR (CIRCLE ONE) P S

LOSS CONDEMNED C REACTIVATE CONDEMN (PARTS) 6B

ATTRITION W WITH QEC F CONDEMN (PARTS) 6C 20. DOCUMENT NUMBER/NSN

FOR PARTS X WITHOUT QEC G UPDATE TO UNKN (PARTS) 6D

SALVAGE/DPDO Y MINOR OVHL K ENGINE ID CHANGE 6E

OTHER Z MAJOR OVHL L AIRCRAFT TIME UPDATE 6F 21. ENGINE FLYING TIME 22. CYCLE/SORTIE

QUICK TURN Q MASS LOSS (PARTS) 6G

INSTALLED SINGLE ENGINE UPDATE 6H

RECEIVED R INSTALLED MASS INITIALIZATION (PARTS) 6I 23. TMSM 24. NHA DESIGNATOR

TRANSFERRED T ACTIVE A INITIALIZE/SRAN CHG (PARTS) 6N

TRANSIENT U INACTIVE Z MAINTENANCE UPDATE 6P

OTHER V SUBTRACT TIME 6S 25. NHA SERIAL NUMBER 26. POSITION

INITIALIZE WINDOW VALUES 6T

UNINSTALLED UPDATE 6U

ENMCS E EGT UPDATE (F108 ONLY) 6W 27. REMARKS

WORK COMPLETED F MANUAL TIME CHANGE 6X

TEST CELL REJECT G

WORK STOPPED H

WORK STARTED J

REMOVED TRANSIENT K

REMOVED OTHER L

CHANGE IN MAINT M

AWAIT DISPOSITION N

ISSUE MAINTENANCE P

RECEIVED R

SHIPPED S

STORAGE STORAGE

STORAGE INSTALLED 8 THREE POINT CONNECTION Z

CEMS EVENT REPORTING,Dec-14

10. TRANSACTION 11. CONDITION

CEMS EVENT REPORT

13. TO/FROM

13b. SRAN

Title: COMMERCIAL ASSET VISIBILITY AIR FORCE (CAV AF)/GOVERNMENT

FURNISHED MATERIAL REPORT

Number: DI- MGMT-81634C Approved Date: 20150911 AMSC Number: 9581 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFMC/A4RM) Project Number: MGMT-2015-025 Applicable Forms: N/A Use/Relationship: CAV AF is a web based system used to permit the reporting of end item repair and Government Furnished Material (GFM) transactions incident to the execution of Contract Depot Maintenance (CDM) contracts for the purpose of providing visibility and oversight of these assets.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.

b. This DID may be used on any depot-level repair contract.

c. This DID supersedes DI-MGMT-81634B.

Requirements:

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

2. Format. Format. The CAV AF System transactions are processed via the World Wide Web, https://www.cavaf.com. Input formats are found in the CAV AF Users Guide. Repair contractors will be furnished with a copy of the CAV AF Users Guide.

3. Content. The contractor reporting shall contain the following transactions and report types as described in the CAV AF Users Guide:

a. End Items:

(1) Receipt

(2) Induction

(3) Awaiting Parts (AWP)

(4) Re-induction

(5) Survey/Scrap

(6) Completion

(7) Shipment

(8) Proof of Shipment

(9) Reversals

DI-MGMT-81634C

(10) Assets Beyond Economic Repair (BER) and Maintenance Expenditure Limit (MEL)

(11) Bulk Process

(12) Borrow/Payback

b. Government Furnished Material (GFM):

(1) Requisitions:

(a) Create

(b) Modify

(c) Cancel

(d) Follow-up as appropriate

(2) Receive material:

(a) Modify/reverse material option

(3) Issue material:

(a) Reverse issue of material

(4) Transfer material.

(5) Turn-in material:

(a) Reverse material turn in

(6) Condemnation/Plant Clearance of material:

(a) Condemn an item

(b) Reverse Condemnation

(c) Plant Clearance

(d) Reverse Plant Clearance

(7) Shipping of material:

(a) Material Release Order (MRO)

(b) Redistribution Order (RDO)

(c) After Receipt of Order (ARO)

(d) Reverse Material Shipment

End of DI-MGMT-81634C

Title: Contract Invoicing and Payment Report

Number: DI-MGMT-81651 Approval Date: 14 January 2005 ASMC Number: A7545 Limitation: NA DTIC Applicable: NA GIDEP Applicable: NA Office of Primary Responsibility: AR Applicable Forms: NA Use/relationship: The Contract Invoicing and Payment Report collects financial and accounting information associated with contract line item numbers (CLINs) and accounting requirements classification numbers (ACRNs) within an awarded contract, which will be used to manage obligations, disbursements, un-liquidated obligations, and canceling accounts associated with appropriated funds.

This Data Item Description (DID) contains the content, preparation instructions and intended use information for the data product resulting from the work task described in the contract.

Requirements:

1. Format. Data will be submitted electronically and may be in contractor format.

2. Content. This report shall include:

a. A listing of each CLIN and subline item number (SLIN) along with the following information for each CLIN/SLIN:

1. ACRN for the CLIN/SLIN.

2. Total CLIN/SLIN value as contained in the contract.

3. CLIN/SLIN funded amount.

4. Cumulative amount invoiced for the CLIN/SLIN.

5. CLIN/SLIN funds remaining. (Difference between CLIN/SLIN funded and invoiced amounts)

6. Percent invoiced of funded amount. (Invoiced amount as a percentage of funded amount)

7. Deductions for the period. (Amount of any performance deductions taken against the

CLIN/SLIN during the reporting period)

8. Cumulative total of all deductions taken against the CLIN/SLIN.

9. Amount of payment received against the CLIN/SLIN.

b. Totaled amounts for all entries for items a.2 through a.9.

3. End of DI-MGMT-81651

Title: DISTRIBUTION OF DEPARTMENT OF DEFENSE (DoD) DEPOT MAINTENANCE

WORKLOAD (50/50) REPORT

Number: DI-MGMT-81749B Approved Date: 20160322 AMSC Number: F9645 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (HQ AFMC/A4FD) Project Number: MGMT-2015-032 Applicable Forms: N/A Use/Relationship: The 50/50 Report Data Item Description (DID) will be used to obtain the essential information required by Title 10 United States Code (USC) Section 2466, also known as the 50/50 law, as amended by the National Defense Authorization Act (NDAA) of Fiscal Year 1998 (FY98).

a. The FY98 NDAA limited the Air Force to not more than 50 percent of the funds managed by the Air Force be used to contract for non-Federal Government personnel to perform depot-level maintenance. Prior to this NDAA, the limit for contract depot-level maintenance was 40 percent. The National Defense Authorization Act for FY02 created an exemption for non- Federal Government personnel performing depot-level maintenance at a Center of Industrial and Technical Excellence (CITE) if the personnel are provided by private industry pursuant to a public-private partnership, as outlined in Title 10 USC Section 2474. Consequently, the law requires the depot-level maintenance organic/contract/partnership dollar information be reported to Congress. As the Product Support Integrator (PSI), the contractor supports the Government in compiling this data to comply with the law.

b. This DID contains the format and content preparation instructions for the data product generated by the specific task requirement delineated in the contract.

c. This DID supersedes DI-MGMT-81749A.

Requirements:

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

2. Format. Contractor is acceptable.

3. Content. The 50/50 Report shall include all costs required under the contract, regardless of the type of funds used by the Government or who is performing the task. This requirement shall also include work funded under the contract but performed by government personnel, as in the case of direct sales agreements under public-private partnerships. Specific reporting requirements are as follows:

3.1 Basis reporting guidelines:

3.1.1 Factors of production. The Department of Defense, in its published guidance related to 50/50 data collection, requires all depot-level maintenance workload figures to include, in addition to direct labor, all other factors of production in support of that workload. These factors include direct materials, overhead, and other indirect costs that apply in direct support of or associated with the direct labor.

DI-MGMT-81749B

3.1.2 Dollars obligated in the previous fiscal year. This figure shall represent the dollars provided from the Government to the contractor during the previous fiscal year (October through September) for all tasks required on the contract. In the case of partnership workloads, in which a portion of these dollars is passed to a government organization to have work performed by government personnel, the amount to be reported is to be the dollars provided from the contractor to the Government during the previous fiscal year, including all factors of production in support of that government workload. This figure would typically be available from government accounting and financial data sources. It is the contractor’s responsibility to break out the dollars reported as being obligated into the various tasks on the contract.

3.1.3 Projected obligations. This figure shall represent a forecast, based on known task requirements and the Government funded position for those requirements, of anticipated obligations, by fiscal year, for the five year period beyond the previous fiscal year. Dollars will be in terms of then-year dollars, with inflation factors applied.

3.2 Major workload categories. Based on the types of funds provided from the Government to the contractor, all dollars reported shall be broken out into the following major workload categories:

3.2.1 Contract Logistics Support (CLS). Typically funded with AF Appropriation 3400 (Operations and Maintenance (O&M))/ Element of Expense Identification Code (EEIC) 578, it can also include AF Appropriation 3600 (Research, Test, Development & Evaluation (RDT&E). It can also include other EEICs such as 554 (Critical Space Operations) and 592 (Miscellaneous Contract Services). CLS is designed to be a long-term sustainment concept, often for commercial or commercial-derivative systems having at least a portion of their logistics support provided by a contract source. Any extended or negotiated warranty costs funded with the same dollars will also be reported in this workload category. Costs associated with warranty in this category shall be identified as warranty costs.

3.2.2 Interim Contractor Support (ICS). Typically, this workload is funded with AF Appropriations 3010 (Investment – Aircraft), 3020 (Investment – Missiles), or 3080 (Investment – Other). Tasks in this category involve maintenance and repair of material and not the installation of modifications, which are funded with the same type of dollars. Any extended or negotiated warranty costs funded with the same dollars will also be reported in this workload category. Costs associated with warranty in this category shall be identified as warranty costs.

3.2.3 Other Contract Depot Maintenance (CDM). Typically, this workload is funded with Appropriation 3400 (O&M)/EEIC 560XX. The EEICs used in this category are known as Depot Purchased Equipment Maintenance (DPEM). This workload can also be funded within various appropriations in the Air Force Working Capital Fund (WCF) associated with Consolidated Sustainment Activity Group (CSAG) – Supply, dollars that are typically used for exchangeable component repair.

3.2.4 Modification Installation (not in Integrated Budget Documentation and Execution System Support (IDECS II)): Modification installations are normally funded using Appropriation 3010, 3020, or 3080/Budget Program (BP) codes 11, 21, or 81, respectively. When funded in this manner, Air Force analysts are able to identify the dollars associated with modification installations, a depot-level maintenance task, using automated data systems, typically IDECS II. The purpose of this category is to capture those modification installations or any non-ICS maintenance using other Budget Program codes such as BP10 or BP19.

3.2.5 Partnership. This workload is a subset of the CLS, ICS, or CDM workload categories.

It is broken out based on whether the work is performed by government or contractor personnel and how the dollars flow between the two organizations.

3.2.5.1 Organic partnership:

3.2.5.1.1 Workshare Agreement (WSA). Under a WSA, the Air Force program office passes funding directly to the partner performing the workload. In this case, the Air Force program office has complete visibility over the dollars provided to the Government organization or depot performing the work. However, the contractor would be responsible for reporting any dollars associated with direct support of any WSA workload, such as contractor- furnished material.

3.2.5.1.2 Direct Sales Agreement (DSA). Under a DSA, the Air Force program office passes funding directly to a contractor, who, in turn, partners with a depot or other government organization, and provides funds to that organization to perform work, in the form of a work order. In this case, it is the contractor’s responsibility to identify all dollars provided or planned to be provided to the Government organization, to include all factors of production in direct support of that organic workload (contractor-furnished materials, overhead, and other indirect costs).

3.2.5.2 Contract Partnership (CITE exemption). Under 10 USC 2474, any depot- level maintenance workload performed by contractor personnel, located on a CITE, under a public-private partnership has to be reported. In the Services’ 50/50 report, this workload must be reported separately but can be subtracted from the Service’s contract totals. As with the other workload categories, dollars reported under this workload category will include all factors of production.

3.3 Task breakdown. Within each workload category identified above in 3.2, all costs will be allocated to the following depot-level maintenance or non-depot-level maintenance task categories.

3.3.1 Depot-level maintenance. The tasks in this section are completely or at least partially considered depot-level maintenance and, if reported, should include all factors of production.

Factors of production costs associated with these tasks can be included in the costs for the individual task or can be identified separately, such as depot material.

3.3.1.1 Programmed Depot Maintenance (PDM): Depot-level inspections and maintenance scheduled on a cyclic basis. The term is typically associated with weapon system or major end item scheduled workload in a Department of Defense (DoD) depot but can apply to similar work in a contractor facility.

3.3.1.2 Analytical Condition Inspection (ACI): A systematic disassembly and inspection of a representative sample of aircraft to find hidden defects, deteriorating conditions, corrosion, fatigue, overstress and other deficiencies in an aircraft structure or systems. ACIs are normally over and above those inspections specified in a technical order or PDM work specifications.

3.3.1.3 C-Check: Commercial version of a depot-level airworthiness and analytical condition inspection.

3.3.1.4 Repair/Overhaul – Recoverable Items/Special Repair Activity (SRA): Repair and/or inspection of major end items or exchangeable components.

3.3.1.5 Software maintenance: Costs associated with any change to a software product after operational acceptance. These costs will include any activities to correct faults (corrective maintenance), improve performance or other attributes (perfective maintenance), or to adapt the weapon system or equipment to a changed environment within the bounds of existing top-level system specifications (adaptive maintenance). Definition adapted from Department of Defense Directive (DoDD) 4151.18, Maintenance of Military Materiel, and ISO/IEC/IEEE 24765, Systems and software engineering - Vocabulary.

(Copies of the DoDD are available online at http://www.dtic.mil/whs/directives/index.html and copies of the IEEE document are available online at http://www.ieee.org.)

3.3.1.6 Speedline: A streamlined process used to perform specific depot-level maintenance services or modifications. Any depot-level maintenance in which the normal process is streamlined or accelerated through a reduced amount of steps or sub-processes.

3.3.1.7 Storage: Tasks associated with maintaining assets in storage.

3.3.1.8 Decommissioning/Demilitarization: Activities involving the preparation of an item for disposal or salvage. Usually involves destruction, recovery or removal of militarily sensitive or precious/hazardous materials or components.

3.3.1.9 Contract Field Teams: Contractor personnel dispatched from a vendor facility to a field location. When the task is complete, the personnel return to the vendor’s home location. Similar to a depot field team. Not the same as field service representatives, which are permanently assigned to the field location.

3.3.1.10 Flying Hours: This relates to a contract support concept in which the Government pays a flying hour rate that covers the support costs for an entire program. Also known as “Power by the hour”. In this case, the contractor shall break out the flying hour costs associated with tasks that are considered depot-level maintenance.

3.3.1.11 Over and Above: Unprogrammed depot-level maintenance workload not previously identified in an original contract or work order.

3.3.1.12 Maintenance (Shop Floor) Engineering: Engineering activities in direct support of and usually co-located with depot-level maintenance functions.

3.3.1.13 Extended/Negotiated Warranty Costs: Warranty terms and costs beyond the standard product warranty, which usually is provided without cost. Warranty costs that actually result in a cost to the Government in addition to the acquisition cost for the end item or commodity.

3.3.1.14 Service Support Agreement: Same as extended warranty – this is a flat rate paid by the customer, the Government, over a set period of time, beyond the scope of the actual mean time between failure period.

3.3.1.15 Subcontracted/Routed Workload Costs: Tasks originally planned and funded as part of organic depot maintenance workload that are routed to a contractor due to backlog, insufficient capacity, or a need to utilize a proprietary process. Recent reported examples have been material plating sub-processes and aircraft paint.

3.3.1.16 Depot Material: A factor of production that may be included in one of the tasks listed above or broken out separately. Includes all government and contractor-furnished material, both consumable and recoverable items.

3.3.1.17 Logistics/Program Support: Management activity in direct support of depot-level maintenance. Often an overhead task and considered a factor of production. Can be included in one of the tasks listed above or broken out separately.

3.3.2 Non-Depot-Level Maintenance Tasks: The tasks in this section are not considered depot-level maintenance. However, they will also be reported along with the costs associated with them. While these costs will not factor into the calculations used for reporting depot-level maintenance and in measuring 10 USC 2466 compliance, details in these task categories are necessary for audit purposes and to ensure 10 USC 2466 reporting accuracy. Non-depot-level tasks are listed in, but not limited to, the tasks below:

3.3.2.1 Advisory and Assistance Services (A&AS)/Engineering Support Services: Tasks associated with general technical and engineering support services such as technical analysis, database development and maintenance, cost analysis, document preparation, special studies, etc.

3.3.2.2 Contractor Operated and Maintained Base Supply (COMBS) Operations: Base supply, material handling and turn-in, and distribution functions performed by a contractor. A supply chain management task.

3.3.2.3 Field Service Teams: Field representatives located permanently on-site at field locations performing organizational or intermediate-level maintenance, supply chain management tasks, training, or advisory services.

3.3.2.4 Modification Kit Procurement: Purchase of modification kits (not including installation of kits).

3.3.2.5 Software Development: The creation of new software code or programs to meet customer operations or support requirements.

3.3.2.6 Spares Procurement: Initial provisioning or replenishment of components not used in the performance of depot maintenance. An example would be the replacement of condemned line replaceable units for a weapon system.

3.3.2.7 Sustaining Engineering: Engineering tasks associated with all aspects of product support. Includes tasks related to reliability and maintainability analysis, product design, technical data development and changes, configuration management, etc.

3.3.2.8 Tech Data Maintenance: Activities associated with maintaining government technical orders (TOs) or commercial tech data (commercial maintenance manuals).

3.3.2.9 Depot Activation: Costs associated with establishing the ability to perform depot-level maintenance, such as procurement of support equipment or upgrading a facility.

3.3.2.10 Software License/Rental Fees: Costs associated with permission to use software.

Not considered repair or maintenance of that software.

3.3.2.11 Satellite Bandwidth Use: Costs associated with rental or use of bandwidth available from a satellite with which to transmit or operate data.

End of DI-MGMT-81749B

DI-MGMT-81804A

DATA ITEM DESCRIPTION

Title: Item Unique Identification (IUID) Marking Activity, Validation and Verification Report Number: DI-MGMT-81804A Approval Date: 20130212 AMSC Number: F9335 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: 70 (OO-ALC) Applicable Forms: N/A

Use/relationship: The Item Unique Identification (IUID) Marking Activity, Validation and Verification Report is a tabular list providing IUID marking activity, validation and verification data such as: physical asset marking, registration, inventory audits, quality audits, and verification/validation results.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID may be applied in any contract which contains a requirement for marking parts and equipment with IUID encoded in data matrix symbols.

Requirements:

1. Reference document: MIL-STD-130. The applicable issue of MIL-STD-130 shall be the latest version cited online at Acquisition Streamlining and Standardization Information System (ASSIST) Update, at the time of the solicitation. Other documents referenced in MIL-STD-130 shall also be applied.

2. The Contractor’s format is acceptable. Recommend electronic transfer of information.

3. A representative sample of IUID-related data matrix marks on items in each delivered Contract Line Item Number/Sub-Contract Line Item Number/Exhibit Line Item Number (CLIN/SLIN/ELIN) shall be validated and verified. Verification and validation results shall be provided using this report format. Marks failing verification or validation must be replaced with compliant marks prior to government acceptance of the items.

4. The tabular report shall include the following alphanumeric fields:

4.1 Unique Item Identifier (UII).

4.2 UII Type (Construct).

4.3 Enterprise Identifier (EID).

4.4 EID Type (CAGE/NCAGE, DUNS, etc).

4.5 Original Equipment Manufacturer (OEM) Part Number.

DI-MGMT-81804A

4.6 Service Assigned Serial Number (if assigned).

4.7 Original Equipment Manufacturer (OEM) serial number.

4.8 Equipment Nomenclature (name and type).

4.9 National Stock Number (NSN).

4.10 Validation Date.

4.11 Validation Result (Pass/Fail).

4.12 Verification Date.

4.13 Verification Result (Pass/Fail).

4.14 Other Event/Activity Date* (optional).

4.15 Other Event/Activity* (optional).

4.16 For items marked that “Fail” IUID validation or verification, identify corrective action (whether the item has been re-marked or scrapped).

*Other Event/Activity will be defined in the Contract Data Requirements Lists (CDRLS) if required.

5. The Key attributes for the report are the validation and verification columns which each indicate (Pass/Fail). (NOTE: Most verification apparatus provide electronic records with pass/fail summaries for both verification and validation.)

A “Pass” validation value shall be assigned to records whose data matrix symbol(s) properly encode Item Unique Identification data as prescribed in MIL-STD-130 DoD Standard Practice Identification Marking of U.S. Military Property requirements for machine readable information (MRI) marking.

A “Pass” verification value shall be assigned to records whose data matrix symbol(s) meet or exceed MIL-STD-130 DoD Standard Practice Identification Marking of U.S. Military Property requirements for data matrix symbol quality.

6. The Contractor shall ensure machine-readable IUID marks required under this contract are permanently placed on the items subjected to contractually-required performance testing prior to that testing; and further shall include all mark serviceability problems in the item’s test report(s).

7. End of DI-MGMT-81804A.

Title: CONTRACTOR’S PROGRESS AND STATUS REPORT

Number: DI-MGMT-81928 Approval Date: 20130701 AMSC Number: N9391 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Office of Primary Responsibility: SH/PEO IWS F Applicable Forms: N/A

Use/Relationship: Contractor’s Progress, Status and Management Report provides the progress of work and the status of the Program and assigned task, report cost and informs management of existing or potential problem areas.

This Data Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

Requirements:

1. Format. The Contractor’s Progress and Status Report shall be in format similar to that of Figures 1, 2 and 3 of this DID.

2. Content. The report shall contain a cover sheet identifying the following:

a. Title of the Report

b. Contractor’s name and address

c. Contract Number

d. Date of report and period by the report

e. Data Item Number listed on the CDRL DD FORM 1423-1

2.1. Results positive or negative obtained related to previously identified problem areas, with conclusions and recommendations shall be identified.

2.2. Any significant changes to the contractor’s organization or method of operation, to the project management network, or to the milestones shall be included.

2.3. Problem areas affecting cost elements, technical or scheduling elements, with background and any recommendations for solutions beyond the scope of the contract shall also include the following items:

a. Funding Issues

(1) Shortfalls

(2) Overfunding

b. Task Area Issues

DI-MGMT-81928

2.4. The report shall contain cost curves showing actual projected conditions throughout the contract and any cost incurred for the reporting period and total contractual expenditures as of the reporting date.

2.5. The report shall contain Man-hours expended for the reporting period and cumulatively for the contract for the following areas:

a. Trip(s) outside the local area, site visited and purpose.

b. Contract schedule status.

c. Plans for activities during the following reporting period.

d. Name and telephone number of signer of the report.

e. Appendixes for any necessary tables, references, photographs, illustrations, and charts.

2.6 The report shall contain all of the information specified in Figure 3, and shall identify Employee movement, color coded/highlighted in comments column.

2.7. The report shall contain also all of the information specified in Figures 1, 2, and 3.

2.8. The report shall identify the following:

a. Title i.e.: Professional Support Services for the Program Executive Office (PEO)

Integrated Warfare System (IWS)

b. Contract Number

c. Latest Contract Modification (# and Date)

d. Period of Performance

e. Reporting Period

f. Contractor’s POC

g. Government PM

h. Government COR

2.5 Financial/Labor Data. The report shall contain all of the information contained to Figure 1 including:

a. Contract Value

b. Funded to date

c. Cost of work performed during period (period to be defined as CY)

d. Planned travel for the upcoming Calendar Month to include location, number of contractor personnel and purpose.

e. Actual: Monthly Hours Burned by each contractor/employee

f. Invoice Date/Amount/Number

3. End of DI-MGMT-81928.

DI-MGMT-81927

Task Sub-task Nr. Task Description Customer Name/Employee Labor or ODCs

(Fully Burdened) Value Funded to Date

Funding Required to End of CY

(Cost)

Funding Required to End of CY

(Fixed Fee)

Funding Required to End of CY

(Total) ACTUAL: Mthly Hours Burned Invoice Number Invoiced Amount Invoiced To Date

Red indicates costs have exceeded funding

Yellow indicates costs are close to exceeding funding.

1.1 1.1.1 NMCI, NAVSEA CIO and Enterprise primary coordinator Jane Doe Labor

ODCs

1.1.2 Assist in Strategic Planning John Smith Labor

ODCs

1.1.3 Portfolio Management. John Doe Labor

ODCs

3.1 3.1.1 ACTD Operations Specialist support John Doe Labor ODCs

Totals

Page 3 of 5 Pages

FINANCIAL/LABOR HOUR DATA BY TASK- FIGURE 1

WORK COMPLETED BY TASK

CLIN/SLIN ACRN PR Number Ref Doc/ACRN MOD Appropriation Subhead OBJ PARM RFM AAA TT PPA Project Unit Funded Expended Balance

Totals $ - $ - $

Totals $ - $ - $

Totals $ - $ - $

Totals $ - $ - $

Totals $ - $ - $

Totals $ - $ - $

Grand Totals $ - $ - $

Page 4 of 5 pages

WORK COMPLETED BY CLIN/SLIN - FIGURE 2

STAFFING PLAN - FIGURE 3

NAME/EMPLOYEE LABOR TASK AREA CONTRACTOR / COMPANY GOVERNMENT FTE HOURS COMMENT

CATEGORY SUPPORTED SUBCONTRACTOR NAME SITE

Page 5 of 5 pages

Task 1 -

Task 2 -

Task3 -IWS Technical - Provide Support to PEO IWS Advanced Technology

Title: DIMINISHING MANUFACTURING SOURCES AND MATERIAL

SHORTAGES (DMSMS) MANAGEMENT PLAN

Number: DI-MGMT-81948 Approval Date: 20130918 AMSC Number: N9433 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: YES Office of Primary Responsibility: SH/SEA 00 Applicable Forms: N/A

Use/relationship:

The Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan shall document the processes used by the contractor to implement a proactive DMSMS Management Process. The plan will enable the identification, forecasting and management of piece part obsolescence impacts and mitigations as a part of the Department of Defense (DoD) Program Managers’ Total System Life Cycle Management responsibilities and identify how application of cross platform commonality can reduce DMSMS issues.

This Data Item Description (DID) contains the format and content preparation instructions for data generated by the specific and discrete task requirement as delineated in the contract.

ANSI/Techamerica STD-0016-2012, SD-22 Guidebook and MIL-STD-3018 may be used for guidance.

The following should be considered as applicable when using this DID: DI-SESS-81656 Source Data for Forecasting DMSMS; DI-MGMT-81772 Lead Free Control Plan; DI- QCIC-80125B GIDEP Report; and DI-SDMP-81748 Parts Management Plan.

1. Format. The DMSMS Management Plan shall be in contractor’s format.

2. Content. The DMSMS Management Plan shall contain the following information:

a. Introduction

b. Scope/Purpose

c. References

d. DMSMS management products, approaches, and processes

e. DMSMS risk assessment and prioritization approaches

f. DMSMS sustainment strategy, when sustainment is included in the contract

g. Software obsolescence and life-cycle supportability

h. DMSMS Management Team (DMT) structure and membership

DI-MGMT-81948

i. Roles and responsibilities of the DMT and each member of the DMT

j. DMSMS Operations

k. DMSMS contractual requirements flow-down to subcontractors

l. DMSMS management tools, databases, and systems used.

m. DMSMS monitoring and surveillance approach; alert notification

n. Approach for DMSMS monitoring of COTS equipment

o. DMSMS case management process

p. Design techniques for mitigating DMSMS…