UIT Code in FLIS. FCS Policy and Systems. Defense Logistics Information Service. David Osburn Supply Systems Analyst. Hart-Dole-Inouye Federal Center 74 Washington Ave N Suite 7 Battle Creek, MI 49017-3084 www.dla.mil/dlis. (269) 961-4708 DSN 661-4708 FAX (269) 961-4708
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
FCS Policy and Systems
Defense Logistics Information Service
Supply Systems Analyst
Hart-Dole-Inouye Federal Center
74 Washington Ave N Suite 7
Battle Creek, MI 49017-3084
FAX (269) 961-4708
June 8, 2006
DLIS currently produces a quarterly CD ROM product which contains approximately 12,500 items including National Stock Numbers (NSNs) and Army Management Control Numbers (MCNs).
Eight programs have been identified that require a UIT indicator with one additional code to be used to identify a UID tracking requirement. The need for a UID code is under review.
AAA DoD Small Arms Serialization Program (DoDSASP)
AAB Security Risk Category I Non-Nuclear missiles and Rockets
AAC Radiation Testing and Tracking System (RATTS) Program
AAD Navy Depot Level Reparables (NDLR) Program
AAE The Army Maintenance Management System (TAMMS) Equipment Data Base (TEDB)
AAF Aviation Component Tracking Program
AAG Tritium Unique Item Tracking Program
AAH Controlled Cryptographic Items (CCI)
UID Assets which meet DoD UID criteria for UID marking, but which are not subject to DoD UIT program/tracking requirements.
Establish a DOD UIT Designator (UITD) Code on the item of supply record in FLIS.
Provide visibility of the UITD on FLIS products and Services (e.g. FEDLOG, WEBFLIS, Data Extracts, etc.)
Output the UITD with standard FLIS catalog data to Service/Agency Legacy/ERP data systems as required.
Need to identify location of source data or method to link UITD to a NSN and pass this information to DLIS.
Need to identify activities and data systems to accept the output data that is pushed from FLIS.
Need to identify any system edits to ensure data quality. (e.g. valid data submitters, UITD codes, FSCs, etc.).
How will we handle non stock listed items (Army MCNs)?
How can Disposal use the UIT and what can we do to facilitate business rules changes?
What interfaces do we establish with BSM? Will the UITD code be established in SAP? How will it work?
What are the business rules for dealing with cancellations? E.g. Cancelled/replaced – Do we automatically code the replacement NSN with the same UITD code?
DLIS must arrange for the UITD code to be in FLIS in a manner that is usable to all Services.
DLIS unsure of Service requirements for the UITD code. Need functional requirements from the Services so we can design the best FLIS solution.
UITD in FLIS may be impacted by the scope of a UID indicator in FLIS.
Services should develop business rules for use of UITD code, incorporate into their data systems, and pass requirements to DLIS for incorporating the UITD code in FLIS.