T53_DID_A002_DI_MGMT_81324A_CEMS.pdf

DATA ITEM DESCRIPTION

Title: Comprehensive Engine Management System (CEMS) Reporting

Number: DI-MGMT-81324A Approval Date: 20060519 AMSC Number: F7567 Limitation:

DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: F/OC-ALC/448EPSG PE Applicable Forms: AF Form 1534, AF Form 41, DD Form 2875 Use/relationship: CEMS reporting is used by the government to maintain a complete and accurate worldwide inventory of Air Force engines, assemblies and parts. The CEMS reporting data consists of aircraft engine and maintenance status information.

a. This Data Item Description (DID) contains the requirements, to include access to the Internet, Air Force Portal, Global Integrated Maintenance Management System (GIMMS) Application and D042 (Comprehensive Engine Management System (CEMS)) mainframe for the purpose of reporting to CEMS for engine, assembly and parts. 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 report engine and module status or other parts life and status tracking data to CEMS.

c. Publications referenced below are available on the CEMS web site, https://cews.tinker.af.mil, at the Oklahoma City Air Logistics Center (OC-ALC) 448 Eagle Propulsion Sustainment Group/PE (CEMS Division), Tinker AFB, OK. This is a secure web site, but can be accessed by providing information requested after clicking on

“CLICK HERE”.

d. This DID supersedes DI-MGMT-81324.

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 Air Force Form 1534 are contained in United States Air Force Technical Order (T.O.) 00-25-254-1.

2. Format. Contractor format is acceptable for electronic reporting. Manually prepared data shall be in the format outlined on AF Form 1534.

3. Content. Inputs to CEMS: In order to accomplish the required access to systems for the purpose of reporting as referenced above, the following is required:

a. A minimum of a favorable National Agency Check (NAC) is required for any contractor accessing a Department of Defense (DoD) Information System. Procedures concerning Industrial Security Clearances and Investigations can be found at http://www.dss.mil/epsq or http://www.dss.mil/isec/psc_contractors.htm.

b. An AF Form 41 must be completed and faxed to Commercial 334 416-1040 to obtain an AF Portal account. The Form 41, as well as additional information may be obtained at https://www.my.af.mil, by accessing “View Account Requirements”.

https://cews.tinker.af.mil/ http://www.dss.mil/epsq http://www.dss.mil/isec/psc_contractors.htm https://www.my.af.mil/

c. After AF Portal access is obtained, a DD Form 2875 and a Nondisclosure Statement must be completed requesting access to CEMS and GIMMS and forwarded to the CEMS Program Office. The form and Nondisclosure Statement may be downloaded from https://cews.tinker.af.mil, by clicking on the “Forms” folder and clicking “System Access”. Instructions are included with the form.

d. In order to access GIMMS via the Internet, Port 992 must be opened on the user’s firewall. The CEMS Program Office (405) 736-7630, should be contacted for further information.

3.1. Specific Instructions. The AF Form 1534 shall contain the following:

a. Block 1 – Report Control Symbol (RCS). The RCS is HAF-LEY (AR) 3215.

b. Block 2 – Subsystem Identifier. Indicate an “S” for status reporting or “C” for configuration reporting.

c. Block 3 – Configured Item Identifier (CII) Designation. The CII of the item being reported.

d. Block 4 – Serial Number. The item serial number.

e. Block 5 – Occurrence Date/Hour. The julian date and time the status change or event being reported occurred.

f. Block 6 – Stock Record Account Number (SRAN). The SRAN assigned to the reporting activity.

g. Block 7 – Command. The applicable major command (MAJCOM) and subcommand codes or contractor command code for the reporting activity.

h. Block 8 – Organization Code. Not applicable for contractor reporting.

i. Block 9 – Engine Ownership Account. The one position engine ownership account code.

j. Block 10 – Engine Type Report. The engine type report code.

k. Block 11 – Part Number. The part number is found on the data plate.

l. Block 12 – Transaction Code. The transaction code, selected from the codes contained in this block of the AF Form 1534, which describes the action being reported.

m. Block 13 – Condition Code. The condition code, selected from the codes contained in this block of the AF Form 1534, which describes the condition code applicable to the item being reported.

n. Block 14 – To/From Command/SRAN. The shipped to/from command and the SRAN. This block is blank for reports of transfer to or from classified projects.

o. Block 15 – Type of Shipping Device. The applicable four (4) position shipping device code selected from the codes contained in T.O. 00-85-20.

p. Block 16 – Sequence Control Number. The sequential control number assigned to each report prepared.

https://cews.tinker.af.mil/

q. Block 17 – Engine-Related How Malfunction (HOW MAL) Code. The appropriate engine-related HOW MAL code. This entry is not applicable to missile engines.

r. Block 18 – Reason for Return to Overhaul Code. The appropriate reason for return to overhaul code.

s. Block 19 – Reparable Engine Serial Number. The serial number of the reparable engine being replaced by the serviceable shipment.

t. Block 20 – Primary/Secondary HOW MAL. The HOW MAL code for a module removed from an uninstalled engine.

u. Block 21 – Security Assistance Program (SAP) number. On “K” reports for engines gain to or from a SAP country, the SAP identification number.

v. Block 22 – Document Number/National Stock Number (NSN).

(1) The debit or credit number from the document covering gain and loss transactions.

(2) A local document number is optional for transaction codes “F”, “N” and “P” for on-SRAN transfers of engines/modules.

(3) For uninstalled reimbursable account transfer (“K” type report) to a non-Air Force account (SAP, Navy, Army, Federal Aviation Agency (FAA), etc.), the requesting activity’s requisition number provided by the prime engine manager.

(4) The NSN, dashes omitted, for establishing and updating a cannibalization record for the item cannibalized (“2L” transaction code).

w. Block 23 – Engine Flying Time. Normally obtained from the AFTO Form 781J, Aerospace Vehicle Flight Document or the AFTO Form 95, Significant Historical Data.

x. Block 24 – Cycle Sortie Count. Normally obtained from the AFTO Form 781J, Aerospace Vehicle Flight Document or the AFTO Form 95, Significant Historical Data.

y. Block 25 - Error Sequence Number. The sequence number from the transaction for which an error correction is being submitted.

z. Block 26 – Type, Model, Series, Modification (TMSM). The TMSM of the engine being reported.

aa. Block 27 – Next Higher Assembly (NHA) Designator. The NHA designation of the item upon which the reported item is being installed.

bb. Block 28 – NHA Serial Number. The serial number of the NHA upon which the reported item is being installed.

cc. Block 29 – Position No. The digit indicates the position in which the engine is installed in the aircraft.

dd. Block 30 – Remarks. “AF 1557” is entered if additional forms for engine recorder device reports are attached.

4. End of DI-MGMT-81324A.