Development Path Analyzer – OSAM – DRMIS 9 May2012

1. Development Path Analyzer – OSAM – DRMIS 9 May2012 • OmegaPSOSAM and Related Functionality • Frank Hallam

2. Starting Point • Analyzer and OSAM continue to evolve together • Analyzer leads in the development of the models with the assistance of DMGOR • Graham Brum will speak to the development planned for this year

3. Relationship • OSAM has always been related to Analyzer functionality from the start of development • Now there is a direct link between the two products • Demo

4. Relationship • OSAM will also indicate which version of both the DLL and Analyzer the OSAM release is related to • However – with the xml data files it is possible to transfer data back and forth regardless of product release level

5. Differences • Analyzer is a modelling tool and as such the results are to be used in comparative analysis • OSAM has the inherent ability to select a baseline solution that can be used to identify the fielded solution

6. Concept • The original concept behind OSAM was as follows: • Enable enterprise level data management • Enable analysis based on a simple data import capability • Enable a baseline • Demo

7. Material Data • Integration with a Material Management System is clear • Ability to define material distribution requirements at the PN level • Ability to identify the applicable NSN • Allow for the System Manager to set sparing level as required or accept OSAM baseline • Ability to adjust baseline based on field data • DRMIS SAP integration is based on the Material Data Protocol in OmegaPS • only semi-automated mechanism left for creating master data

8. Distribution • DRMIS SAP PPAs – Provisioning Parts – allows for the definition of what material needs to be stored at various levels in the support chain • DRMIS OmegaPS will create the PPA file for a Major Asset based on data held in Canadian Provisioning • OSAM integration with Canadian Provisioning will be available in R18

9. Material Authorization • DRMIS SAP PPAs are similar to Material Authorizations (MA docs) SPSx = Spare Parts or Self Sufficiency Stock type warehouses may be used for one of the two following functions: SSS type warehouse: this concept was carried forward from the legacy system. This type of warehouse is normally identified by a code of four alphanumeric characters consisting of SPSx or DETx, (x = sequential number of 1 to 9). Size or unit composition may dictate a different naming convention. SSS type warehouses are used to hold/record all materiel identified by Equipment Support Lists (ESL), as detailed by a LCMM or unit issue experience for such items as vehicle, weapon or lantern spare parts and consumables that are required to maintain equipment and support personnel of that unit or formation for a specified period of time, while deployed away from normal support facilities. The items detailed in Ships Automatic Replenishment Program (SHARP), Pack up Lists for aircraft, and the SPS1 warehouses at Land Force field units are examples of SSS materiel accounts.

10. Material Authorization

11. Canadian Provisioning • DND CP (Canadian Provisioning) module holds the approved scaling as defined by the System Manager • DND CP integrates with Commercial CP by accepting all CFP 214 data • DND CP also accepts net result of all material update data from DRMIS SAP • There are Navy/Army/Air Force Configurations for DND CP • Demo

12. Material Data Management • DRMIS OmegaPS has the following capacities for managing the material baseline for a complex asset • OSAM – baseline Sparing/LORA/Life Cycle Cost • DND CP – validated Part#, validate NSN, management of change to material solution • Planned material distribution • TA ownership management by ERN/EAC • Known ERN/EAC applicability • Note – ERN/EAC applicability update runs each day – DRMIS SAP no longer processes this data