Cataloging in NATO Today and the Vision for Tomorrow Logistics Data & IT Solutions Defense Logistics Information Service Mr. Steven Arnett Deputy Chief, International Cataloging Division Hart-Dole-Inouye Federal Center 74 Washington Ave N Suite 7 Battle Creek, MI 49017-3084 (269) 961-7299 DSN 661-7299 FAX (269) 961-4760 EMAIL: Steven.Arnett@dla.mil Overview of Presentation • History and scope of the NATO Codification System (NCS) • The current process of cataloging within the NCS • Vision for the future of the NCS with eOTD What Is The Purpose Of NATO Codification? • To establish a common supply language throughout all logistic operations • To enable interoperability • To optimize resource management by minimizing duplication in inventories Codification Answers Logistics Questions Characteristics? How to purchase? How to dispose? How to order? How to store? What is it? How long to keep? Price? ANSWER = The NSN and reference related data The questions are based on National requirements of logisticians!!! Codification In Logistics The U.S. Cataloging System Today ONE ITEM OF SUPPLY SINGLE MANAGER SINGLE NSN DLA NSN 1 Each military service uses their own logistics “language” DLA Army NSN 1 NSN 2 In The Days of WWII Marine Corps NSN 3 Navy NSN 4 Air Force NSN 5 Potential for: - Multiple NSNs, based on service and weapon system NATO NSN 6 NSN 8 NSN 7 - Multiple buying activities - Multiple corporate contracts - Loss of Interoperability/Asset Visibility NSN ? Codification Chronology 1945 WWII 1949 PL152 SUPPLY CLASSIFICATION 1952 PL436 CODIFICATION SYSTEM US/UK/CA CLASSIFICATION 1954 STANAG 3150 NATO 1956 STANAG 3151 1966 DLSC 1974 NCB CODE 1978 CD-ROM 1991 PFP DESERT 1994 PACS STORM BASELOG 1999 e-Commerce 2002 2006 eOTD / ISO Costs Of A Weapon System Weapon system Fuel, spare parts, work... acquisition costs operations costs 1/3 2/3 Political decision = specific budget Operating budget of the armed forces Life cycle cost NCS is Language Interoperable ŚRUBA,MASZYNOWA BOLT,MACHINE BOUT, MACHINE PERNO, TORNEADO BULLONE PER METALLO SCHRAUBE MIT KOPF SVORNÍK, STROJNÍ Polish English Dutch Spanish Italian German Czech Scope of the NCS • 16 million NATO Stock Numbers have been assigned – 7 million by the U.S. and 8 million by the other NATO countries – 31 million reference numbers have been registered on these NSNs – These NSNs contain more than 22 million user registrations • 1.5 million manufacturers and other organizations are registered Nations Using the NCS NATO countries Sponsored countries Nonparticipating countries Traditional NATO Cataloging Data Vendor Data NCS Design, Manufacturing and Enterprise Management Applications Graphics Documents Acod-P1 Data ERP Application NCB Structured Data eOTD Enabled Cataloguing Use eOTDi-XML as export filter Allows NCB to define and publish their data requirements in terms of the data elements they need (FIIG in XML) eOTD tagged Data Vendor eOTD export enabled Design, Manufacturing and Enterprise Management Applications eOTDr-XML eOTDi-XML Segment V data Acod-P1 Data Data NCS eOTDr-XML enabled Cataloguing Application NCB Validation Vision for the Future What is impossible to do right now, but, if you could do it, would fundamentally change your business? 1990 Joel Arthur Barker • Cataloging at source (vendor supplied data)! – – – Common metadata through ISO 22745 • an end to data mapping Requirement specifications • an end to incomplete data Data quality through ISO 8000 • an end to inaccurate information • Lowers the cost of cataloging and increases long term data reliability! How NATO Will Realize the Vision • NATO AC/135 is working with ECCMA, a defense company called Patria, and NCS application software providers on a project to apply the principles of eOTD and SSC to a weapons system: – – – – The weapons system is called the Patria Armoured Modularized Vehicle (AMV) The NCS software applications are SICAD Plus, N-CORE, AURA MC Catalogue, and OLCIMS The National Codification Bureaus involved are Finland, Poland, Spain, United Kingdom, and United States (DLIS) National softwares like ADAGIO (France), CENCAT3 (Australia), and ISIS (United Kingdom) may also be included in SSC Phase II ERP eOTD Data Flow N-CORE MC Catalogue Native CAD eOTD item data OLCIMS SICAD Plus STEP CENCAT3 eOTD Catalogs on Web National Systems ADAGIO eOTD: Link to Industry Classifications eOTD is Classification Neutral ECCMA Standard Class Name Used to access many classifications ISIC HS FSC / NSC eCl@ss Industry Classifications UNSPSC NAICS CPV Benefits for Government • Opportunities for improvement of the NATO Codification System through increased industry participation • Promotes NCS approach as an ISO standard • Lower cost of cataloging: Reduction of labor hours • Higher quality data through direct import of manufacturers’ data Goal: Electronic transfer of descriptive data from our suppliers and manufacturers to NCBs Vision of the Future The ultimate goal has been met: to provide a means of describing product data through the life cycle of a product, independent of any particular computer system Towards an Enterprise IDE Integrated Data Environment How else does IDE contribute to asset visibility and overall interoperability? Vision: the DOD logistics enterprise is executing practices, processes, applications, and decision support in an integrated logistics data environment, thereby achieving logistics data interoperability within a Net Centric Community of Interest (COI). USMC Air Force Navy USTC DLA Enterprise Integrated Data Environmen t Army Contemporary Systems Asset Visibility TODAY Stovepipe systems High cost Limited data interoperability Allies USCG Data Warehous e Commercial Trading Partners Logistics data interoperability identified in FLOW99. Revalidated in FLOW01 and FLOW03. TOMORROW EIDE Eliminate stovepipes Lower costs (reduced interfaces) Enable system-wide interoperability Precision Logistics Reducing footprint through AIT and data standards – interoperability solutions! Unique Identification (UID) Integrated situational awareness of people, places, and things Today – No UIIs No integrated planning view Requirement: capability to integrate force structure planning for identifying and constituting deployable combined force modules. • • • • RFID Tracking Questions To Be State – UIIs Integrated planning view People, things and property related to force structure. Deployment and constitution options can be continuously evaluated. Required items identified, preWho is available? positioned and With what tracked with RFID. equipment? Where are they People and things now? can be identified to How long can we sites and facilities for support them? rapid deployment response. Questions answered Presenter Details • • • • • • • • • • • Steven Arnett Defense Logistics Information Service Deputy Chief, International Division DLIS-KI/U.S. National Codification Bureau Federal Center 74 North Washington Avenue Battle Creek, MI 49017-3084 USA PHONE/FAX: 269-961-7299 E-MAIL: Steven.Arnett@dla.mil Web: http://www.dlis.dla.mil/nato/default.asp Web Links Recommended for Contractors • Commercial and Government Entity Codes (CAGE) - http://www.dlis.dla.mil/cageserv.asp • NATO Codification System - http://www.nato.int/structur/AC/135/NCS/index.htm. • NATO National Codification Bureau (NCB) Points of Contact http://www.nato.int/structur/AC/135/NCS/contact.htm • Central Contractor Registration (CCR) Homepage – http://www.ccr.gov • Federal Business Opportunities - http://www.dodbusopps.com. • U.S. General Supply Services Administration (GSA) Federal Supply Service Information http://www.fss.gsa.gov/ • How to Become a GSA Federal Supply Schedule Partner http://www.fss.gsa.gov/schedules/do_biz.cfm • FLIS on the Web - https://webflis.dlis.dla.mil • Interactive Government Industry Reference Data Edit and Review (iGIRDER)- http://www.dlis.dla.mil/igirder/default.asp