Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Stephen Kennett presentation


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Stephen Kennett presentation

  1. 1. Dealing Effectively with the data legacy of your organisation Dr Stephen Kennett
  2. 2. Defence Science and Technology Organisation (DSTO) <ul><li>Australian Government's lead agency dedicated to providing science and technology support for the country's defence and security needs. </li></ul><ul><li>DSTO: </li></ul><ul><li>Seeds and shapes the perceptions and priorities of Defence for the use of science and technology. </li></ul><ul><li>Provides scientific and technical support to current Defence operations. </li></ul><ul><li>Investigates future technologies for Defence and national security applications. </li></ul><ul><li>Ensures Australia is a smart buyer and user of Defence equipment. </li></ul><ul><li>Enhances existing capabilities by increasing performance and safety, and reducing the cost of ownership of Defence assets. </li></ul><ul><li>Assists industry to become better at supporting Defence’s capability needs. </li></ul>
  3. 3. DSTO <ul><li>DSTO employs around 2300 staff in facilities at </li></ul><ul><li>Edinburgh (SA), Melbourne, </li></ul><ul><li>Canberra, Sydney, Brisbane, </li></ul><ul><li>HMAS Stirling (WA), Scottsdale (TAS), and Innisfail (QLD). </li></ul><ul><li>DSTO's budget represents </li></ul><ul><li>approximate 2% of the Defence budget. </li></ul>
  4. 4. Legacy Data Replace? Paper based System COTS Solution Reporting needed Legacy Data Manual Effort
  5. 5. Legacy Data Replace? Information needed COTS Solution Modification needed Modify Code More Hardware Legacy Data Requirements Change
  6. 6. Why keep legacy (Maintenance) data? <ul><ul><li>Parts usage </li></ul></ul><ul><ul><li>Work area usage </li></ul></ul><ul><ul><li>Time between jobs – work rate </li></ul></ul><ul><ul><li>Failure Patterns </li></ul></ul><ul><ul><li>Usage pattern </li></ul></ul><ul><ul><li>Comparative histories </li></ul></ul><ul><ul><li>Life of type information </li></ul></ul><ul><ul><li>Legal requirement </li></ul></ul><ul><ul><li>Accountability </li></ul></ul>
  7. 7. Legacy Data Choices <ul><li>Import into current database </li></ul><ul><li>- Missing fields </li></ul><ul><li>- Duplicate data </li></ul><ul><li>- Handling exceptions </li></ul><ul><li>- Audit trail </li></ul><ul><li>Retain as separate entity </li></ul><ul><li>- Reporting tool </li></ul><ul><li>- Database translation </li></ul><ul><li>- Remove front end? </li></ul>
  8. 8. Who needs the data? <ul><li>Engineer </li></ul><ul><li>problem solving </li></ul><ul><li>best possible answers </li></ul><ul><li>Life of asset </li></ul><ul><li>Auditor </li></ul><ul><li>Individual records as entered </li></ul><ul><li>Who altered what? when? </li></ul><ul><li>Five years </li></ul><ul><li>Asset Manager </li></ul><ul><li>Overview of system </li></ul><ul><li>Two or more asset lifetimes </li></ul>
  9. 9. Army Helicopters <ul><li>Aging Aircraft Audit </li></ul><ul><li>DSTO request to examine Cost of Ownership – CN </li></ul><ul><li>Cost </li></ul><ul><ul><ul><ul><li>engineering point of view </li></ul></ul></ul></ul><ul><ul><ul><ul><li>EE500, EE508 </li></ul></ul></ul></ul><ul><ul><ul><ul><li>accountant point of view </li></ul></ul></ul></ul><ul><ul><ul><ul><li>ROMAN, SDSS </li></ul></ul></ul></ul>
  10. 10. <ul><li>Designed to answer maintenance question on </li></ul><ul><li>Parts usage </li></ul><ul><ul><li>Work area usage </li></ul></ul><ul><ul><li>Time between jobs – work rate </li></ul></ul><ul><ul><li>Failure Patterns </li></ul></ul><ul><ul><li>Usage pattern </li></ul></ul><ul><ul><li>Comparative histories between aircraft </li></ul></ul><ul><li>In a graphical and intuitive way? </li></ul>Army Helicopters
  11. 11. Paper based Maintenance Records
  12. 12. Data Input
  13. 13. Data Trending
  14. 14. Maintenance Location
  15. 15. MSD Data Quality <ul><li>DSTO was requested to investigate the Quality of Data within the Maritime Systems Division of the Defence Material Organisation (DMO). </li></ul><ul><li>Limited resources  </li></ul><ul><li>Focused on the Quality of Maintenance Data in Asset Maintenance planning system (AMPS) </li></ul>
  16. 16. Legacy Data <ul><li>AMPS Current State </li></ul><ul><li>Ingres database with an proprietary user interface running across the defence intranet using Citrix. Separate analysis and reporting program requiring knowledge of both SQL and data table structure. </li></ul><ul><ul><li>800+ flat tables </li></ul></ul><ul><ul><li>No normalisation </li></ul></ul><ul><li>Preferred state: </li></ul><ul><li>Intuitive Web interface to multiple databases for both input, analysis and reporting. </li></ul><ul><ul><li>Normalised database </li></ul></ul>
  17. 17. <ul><li>AMPS data quality has been found insufficient for both engineering and costing analyses. MAIT addresses these issues and introduces new features to promote the collection of high quality maintenance data. </li></ul><ul><li>Analysis capability </li></ul><ul><li>Web interface to AMPS data </li></ul><ul><ul><li>Class wide queries </li></ul></ul><ul><ul><li>System Status </li></ul></ul><ul><ul><li>Job search </li></ul></ul><ul><ul><li>Maintenance history </li></ul></ul><ul><li>Input capability with online feedback </li></ul>MAIT
  18. 18. MAIT Architecture
  19. 19. MAIT <ul><li>Data Quality Reporting </li></ul><ul><li>RAM Analysis with Quality Indication </li></ul><ul><li>System Analysis and job tracking </li></ul><ul><li>Failure Data </li></ul><ul><li>Readings Trending and Validation </li></ul><ul><li>System Status Reporting </li></ul><ul><li>Performance Indicator Reporting </li></ul><ul><li>Audit and tracking </li></ul>
  20. 20. IIS MAIT Ingres DB Ingres DB CITRIX AMPS IIS MAIT MSQL DB Transition
  21. 21. Summary <ul><li>Effective Use of Legacy Data. </li></ul><ul><li>Know who is target audience </li></ul><ul><li>Suggest </li></ul><ul><li>Web user interface </li></ul><ul><li>Integrate old and new data on the fly? </li></ul><ul><li>Separate application layers and data layer </li></ul><ul><li>Maintain primary data </li></ul>