Stephen Kennett presentation


Published on

Published in: Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Stephen Kennett presentation

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