Pillar 6: Data Interrogation/Reuse (Optional) In Pillar 6 we propose to liaise with the OEM and stakeholders of other data sources that may wish to use the cleansed output. This will allow those with a vested interest to ascertain the consistency of their data against the curated IPCs. Any errors or anomalies identified that impact the cleansed IPCs are manually corrected, as appropriate, through liaison with the necessary stakeholders. Changes are reloaded and re-checked to produce a finalised and accurate data set. All changes are tracked. This activity ensures cohesion of parts data across multiple stakeholder systems and provides an accurate, curated data set for internal use or export to external systems such as MJDI, CRISP or Gold ESP. It also provides the means by which external lists of items (e.g., warehouse or stock holdings) can be speedily checked against multiple IPCs.

Pillar 1: Data Input

Pillar 2: Pre-Cleanse and CSIS Check Following population of the database a pre-cleanse activity is undertaken: • Each NSN is checked to ensure that it is correctly formatted and suitable for automated interrogation. • Each MPN is checked against known formatting criteria for correctness and suitable for automated interrogation. • Each NSN and MPN is cross referenced to the CSIS database. • Supply Management Data (SMD) which forms the basis of the item descriptions is extracted from CSIS. • An Anomalies Report is produced outlining all errors to be corrected.

The data derived from Pillar 3 and 4 (Optional) activities is loaded into a database and forms the basis for the cross references that are used to identify additional anomalies, errors or other issues arising. These are baselined in the database to provide the basis of a historical reference of activities and actions. The results of the cross-reference activities are also stored in the database and baselined; forming the core information which is used for the actual cleanse activities occurring in the next Pillar. Note: At this juncture, to maintain costs at a practical minimum, through a simplified output, an extract of all errors identified can be provided to the customer such that they can resolve issues using internal resources before supplying TMS with accurate data to re-load into the system.

Pillar 3: Data Cleanse Assistance (Optional) Following the check against CSIS undertaken in Pillar 2, errors identified in the Anomalies Report in terms of numerical formatting or nomenclature are corrected, processed automatically and rippled through where possible. More complex errors such as misaligned NSN to Part Number, descriptions or omissions etc. are manually corrected through liaison with the MOD or the OEM resulting in a curated and accurate data set with standard terminology and format across all information sets.

Pillar 4: Consistency Check (Optional) Pillar 4 activity is an adjunct to the Data Cleanse process and is deemed to be an optional function. Pillar 2 activity identifies the MPNs assigned to a given NSN and identifies additional element items such as manufacturer or platform applicability to ascertain the preferred MPN for a given NSN.

Pillar 5: Parts Catalogue Update (Optional) The cleansed and sanitised data is used to automatically generate a new Parts List or as a costed option, a regenerated equipment Illustrated Parts Catalogue (IPC) to match the format of the original AESP, BR or DAP. The update of the IPC is automated. However, the use of Microsoft Word means that formatting errors can creep in; therefore a manual 100% visual check is performed to ensure that the output format of the IPC meets the Defence Standard. Where fully electronic (S1000D) data modules are used there is no need for any visual check and the cost model can be altered accordingly.

Source information in MS Word document or Excel format, is processed so as to be able to extract the information into a database. The data set is manually checked (validated) for accuracy of content against the source material to assure the fidelity of the IPC/Parts List. The processing of the source material is a pre-requisite for enabling the automated, checking (Pillar 2) cleansing (Pillar 3) and update of the content (pillar 5). Typical data input sources would be an MS Excel file or AESP, BR or DAP, although the capability (with a few minor modifications) will be able to extract from an S1000D Data Module subject to access to the electronic reader.