DI-PSSS-82324
Training System Sparing Product Data
Training System Sparing Product Data captures support and support-related engineering and logistics data from contractors resulting from product support analysis during design, development, and initial fielding of a training system.
Approval DateJuly 28, 2020
AMSC NumberN10189
Preparing ActivityAS
Project NumberPSSS-2020-006
OPR—
DTIC Applicable—
GIDEP ApplicableNo
LimitationNone
Applicable FormsNone
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
Training System Sparing Product Data comprises the support and support-related engineering and logistics data acquired from contractors generated as a result of the product support analysis conducted during the design, development, and initial fielding of a training system or training end item. This includes data for maintenance planning; logistics design requirements, reliability and maintainability, system safety, supply support, initial sparing, and item management.
This Data Item Description (DID) contains the format, content, and intended use information for the data product resulting from the work task described in the contract.
Preparation Instructions
1Reference 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.
2Format.The Training System Sparing Product Data shall be delivered in table form with columns for each element contained in section 3.2.
3.1The report shall contain a row for each item recommended by the contractor to maintain the delivered training system or end item at an operational availability (AO) of 90% for a time period specified in the applicable Statement of Work (SOW).
3.2The report will contain a column for each of the following fields:
3.2.1PROVISIONING LIST ITEM SEQUENCE NUMBER (PLISN)An alpha numeric sequentially assigned value for each item contained in the system/equipment breakdown (EXAMPLE-A001-Cockpit, B001-Visual, C001-IOS, etc. This alphanumeric format will allow for separate System Sorting. Once a PLISN NUMBER has been assigned to an item, that number may not be used again.
3.2.2TYPE OF CHANGE CODE (TOCC)This block, which is blank on initial submissions of provisioning data, shall be used as a type of change code that indicates deletions, modifications, typographical errors, quantity changes (increase, decrease), and limited part applications as follows:
3.2.2.2D - Indicates a deleted item.
3.2.2.3G - Deletion of a data element.
3.2.2.4L - Item is replaced during production and support of the old part may be required for prior production quantities.
3.2.2.5M - Indicates a modified item.Required to identify entries for those items changed as a result of either administrative or engineering requirements (not for initial entry of NSN) before or during production. Examples of changes are as follow:
3.2.2.5.1Prime contractor's reference number.
3.2.2.5.3Manufacturer's reference number.
3.2.2.5.5Other data elements, as may be subsequently defined, wherein the hardware is not affected.
3.2.2.6Q - Used to make quantity field changes.
3.2.2.7T - Used to make a typographical error correction.
3.2.3MANUFACTURER'S COMMERCIAL AND GOVERNMENT ENTITY (CAGE) CODEA five-character code assigned by the Defense Logistics Information Service (DLIS) to the design control activity or actual Manufacturer/Supply Company of an item as contained in the Cataloging Handbook H4/H8 Series.
3.2.4ORIGINAL EQUIPMENT MANUFACTURER'S PART NUMBER (OEM/P/N)The actual Original Equipment Manufacturer's part, model or drawing number used by the manufacturer to identify their item of supply.
3.2.5ITEM NAME/NOMENCLATUREAn identifying noun with appropriate adjective modifier, as contained in Cataloging Handbook H6. Item names contained in Cataloging Handbook H6 cannot be abbreviated unless approved by the requiring authority.
3.2.6QUANTITY PER END ITEMThe quantity per end item of the system/end item as a model ("A" indentured) item. Exception: If the item does not have a NHA, the Quantity per End Item should be blank. The total number of times the line item is used in the complete system/equipment. If the quantity is unknown or cannot be determined specify the quantity by "V" (variable) or as specified by the provisioning activity.
3.2.7UNIT OF ISSUE (UI)A code that indicates the UI quantity of an item. The UI quantity is the managing activity's established accounting unit upon which the smallest unit pack is based, accountable records are maintained, and requirements are computed. For applicable codes see DLA Cataloging Data and Transaction Standards, Volume 10, Table 53.
3.2.8UNIT OF ISSUE PRICEAn estimated cost associated with each performing activity recommended requirement for budgeting and planning.
3.2.9TOTAL QUANTITY RECOMMENDEDA recommended quantity of an items required to support a specific number of applications for a specific period of time (see para 3.1). The applications may be to a system, end item, component, or combinations thereof, which are contained in the applicable contract.
3.2.10TOTAL PRICEThe total price after multiplying the UI Price and the Total Quantity Recommended.
3.2.11NATIONAL STOCK NUMBER/NATIONAL ITEM IDENTIFICATION NUMBER (NSN/NIIN)A NIIN provides a unique identification of an item of supply within a specified FSC. The combination of the two identifiers (FSC and NIIN) constitutes the NSN (see Appendix B for a complete definition of NSN and Related Data). The nine digit NIIN is made up of a two-digit NATO Codification Bureau (NCB) code indicating the assigning country (e.g., the United States uses "00" and "01") and the final seven digits are assigned sequentially and have no inherent significance. The NIIN relates to one and only one item of supply within the codifying country. It can consist of one or many "items of production" (i.e., a product of a specific manufacturer) having equivalent "fundamental characteristics".
NOTE: An alphanumeric NIIN is used to document management control or temporarily assigned numbers prior to final NIIN assignment. Final NIINs are completely numeric. For applicable codes, see DLA Cataloging Data and Transaction Standards, Volume 10.
3.2.12LONG-LEAD ITEMThe computed or expected time interval expressed in months between placement of a new contract and shipment of the first deliverable quantity.
3.2.13ESSENTIALITY CODEA numeric code to indicate the degree to which the failure of the part affects the ability of the end item to perform its intended operation.
Codes are as follows:
1 - Failure to this part will render the training system completely inoperable.
2 - Failure to this part will not render the training system inoperable, but will reduce the training capability of the system by over 50%.
3 - Failure to this part will not render the training system inoperable, will reduce the training capability of the system by less than 50%.
4 - Failure to this part will not render the training system inoperable, but procurement time of a replacement item may cause an extended period of trainer down time that exceeds 6 months.
3.2.14MEAN TIME BETWEEN FAILURES (MTBF)Mean time between failures (MTBF) for a particular interval is calculated by dividing total functional life of a population of an item by total number of failures within the population during the measurement interval. The definition holds for time, rounds, miles, events, or other measure of life units. MTBF is documented as both technical and operational characteristics. Technical parameters reflect the technical reliability that the system/equipment must demonstrate. In determining these parameter values, all failures and resultant actions to restore the item will be considered (e.g., a broken tail light is a technical, but not operational characteristic). Operational parameters reflect operational RAM characteristics that the system must demonstrate. Only operational mission failures and the resultant tasks are included (e.g., engine failure will result in mission abort that is both an operational and technical failure). The contractor shall obtain approval from Government IPT on formula(s) to derive MTBF and MTTR calculations not supplied by item manufactures. MTBF should be expressed in hours.
3.2.15PART AVAILABILITY CODEA numeric code showing the manufacturer's estimated time before the part becomes discontinued and unavailable.
(1) 1 - 6 months
(2) 7 - 12 months
(3) 1 - 2 years
(4) 2 - 5 years
(5) Greater than 5 years
3.2.16TRAINING DEVICE SERIAL NUMBERThe training device serial number that the items will be procured to support. Enter "NA" in the field if a singular device or item will be supported.
3.2.17SUPPORTING DATAReference to data that provides definitive information on the supportability, reliability, maintainability, availability of the item. For Commercial Off the Shelf (COTS) items, an active hyperlink to manufactures' data sheets may be provided.
3.2.18PROVISIONING REMARKSNarrative clarification of provided data or any information required for procurement of the item.
Schema v3.0Community-maintained · Verify against ASSIST