A Cradle-to-Grave Solution for Inventory Managers and Through Life Support Staff The Material Management One-Stop Shop MMOSS

Transcription

1 A Cradle-to-Grave Solution for Inventory Managers and Through Life Support Staff The Material Management One-Stop Shop MMOSS World Codification Forum 24 th May 2017

2 Death by Power Point This is a workshop More interaction = Less Slides

3 Introductions The UKNCB s NATO Codification Partner As such, we are the ONLY Contractor able to create and amend NSNs for the UKNCB

4 WCF - MMOSS Workshop Introductions Suppliers of A leading NATO Codification and Cataloguing Solution Worldwide for Global Governments and Public Sectors

5 Why do we do NATO Codification? The primary goal of the NATO Codification System is to ensure that military personnel and their support chain can be assured of getting the right items at the right time But we know, many countries do it to be part of the club Therefore, NSNs are created with the resulting data not used to its full potential. Sometimes the NSN doesn t even leave the NCB! Lets explore what, where and how we can use the outputs of NCS within a Military Supply Chain

6 What are the outputs from the NATO Codification System? Basically, it is data about any Item of Supply An Approved Name the manufacturer could call different Items of Production different names Classification Part Numbering Information, including details of Items of Production Technical Characteristics All contained in an NSN Record an Item Identification

7 Usage of the Outputs Let s explore how and where the outputs from the NATO Codification System can be used to enhance the Logistic Supply Chain There are many elements of a Logistic Supply Chain, today we are concentrating on Inventory Management So what are the elements of Inventory Management? Identification of Spare Parts Purchasing Spare Parts Storage and Distribution Obsolescence Management Substance Identification and Reporting (RoHS, REACh etc)

8 Usage of the NCS Outputs Let s explore how we can have a solution that has NSNs at the centre

9 WCF - MMOSS Workshop What Items do we codify? Within the UK, any Item that will enter the Military Supply Chain must have an NSN. No NSN no receipt by MoD Why do we codify? Identification of Spare Parts Who requests us to codify items? Must definitively identify an Item of Supply Contracts MUST have a codification contract clause A robust definition of the meaning Source Data Equipment suppliers will want to mask the True Source

10 Purchasing Spare Parts Using the data contained within an NSN Purchasers can identify the true source or sources of an Item This can then be used to obtain pricing and subsequent purchase or used as the source material to contract with specialist supply organisations CMCA(UK) and ESG have created various procurement modules that have proven that the NSN can be the primary reference/identifier These tools can utilise the information contained within the NSN whilst still being able to select Item(s) of Production that meet the requirement of the end user Note:-All Items of Production recorded against an NSN (Item of Supply) may not meet the requirements of the end user By combining equipment structure and maintenance information the forecasting of required quantities can be based on future requirements not historical usage. In addition to placing contracts/orders the module can be expanded to include Goods Inward Inspection at each receiving site Counterfeit prevention

11 As part of the goods receipt process, items can be processed and stored by NSN or split according to the contract requirements and importantly into Batch/Lot/Date code etc to support traceability. But always stored by the Primary Element of the NSN Additionally documentation to support traceability can be stored and linked accordingly The storage module can identify the:- Preferred method of storage Preventative Maintenance requirements Manage items whilst they are in storage Aid in disposal (can be enhanced when substance info is available) Automatic Printing of Labels Storage

12 Picking as individual items or kits based on the information contained in the IPC/Data Collection (Equipment Structure) module Supporting documentation can be easily identified (automatically) Management of Special Packaging Automatic production of:- Labels A and R Notes C of Cs Invoices Distribution

13 Obsolescence Management Discuss what OM is and how the data contained within the NSN can be used with other modules to facilitate Component Monitoring, OMIs and Parts List updates

14 Substance Identification and reporting (RoHS, REACh etc) Discuss the recording of substances against an NSN and how this data could be used

15 Conditions Necessary to make this work Codification Clause in equipment purchase and maintenance contracts True source information The NSN database must be the only source for NSNs, Part Numbers and Characteristics. The modules must use this data and not store it locally Data must be accurate and maintained at all times The right software

16 Transformation (soapbox time!) Fully behind change But NATO Codification has 62 Participating countries and has been in existence since Different languages, different cultures, different software solutions, different processes and slightly different understanding (A-CodP1 not easy to understand), makes change difficult. Some decision-makers do not have the required knowledge and sometimes agree to changes without understanding the impact Work with what we have to make the NCS suitable for your Military Supply Chain AC135 have invested NATO Codification to the individual NCBs. NCBs can dictate a degree of localisation to meet their Military Supply Chain but ultimately they must adhere to NCS rules It must remain a tool to support the Military Supply Chain Do not always listen to individuals who do not fully understand codification who tell you there s a better way Forget about doing it cheaper and quicker, surely it is about doing it cost effectively whilst doing it Right And just because you are told it s cheaper and quicker another way it may not be!

17 Potential enhancements to the NCS A major issue with modules/systems that use the NSN as its primary driver is that an NSN can and does sometimes change. This tends to be changes to the NSC. Within the codification community this is not a different NSN, but appears to be for modules/systems/people that use the NSN. Potential Solution Remove the NSC from the NSN use only the NIIN Make the NSC an MRC You could then have different groups and classifications What about including additional data elements, specifically logistics information? Perhaps a short Item Description that can be used by the modules.

18 WCF - MMOSS Workshop