Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| nr:odm [11/08/07 @ 10:47:25] – removed justin | nr:odm [01/06/13 @ 20:54:14] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== ODM ====== | ||
| + | |||
| + | |||
| + | ===== Current Situation ===== | ||
| + | |||
| + | ODM stands for Operational Data Management. | ||
| + | |||
| + | * Data management for various safety and hazard registers (see [[specifics]] for more details. | ||
| + | * A level of image management (this is a future requirement) | ||
| + | |||
| + | Like Image management, ODM is done very much on an ad-hoc basis, often with the various registers held in a substantial number of MS Access databases floating around the company. | ||
| + | |||
| + | Some of the current issues around ODM are: | ||
| + | |||
| + | - Substantial distributed copies of data held in a number of different formats (ie. MS Access) | ||
| + | - Localisation of data storage vs. distribution to other Areas (see [[#org chart]] below for info) | ||
| + | - Validity / currency of data held (i.e. PB crash had out of date diagrams) | ||
| + | - Data Ownership | ||
| + | - Inconsistent metadata between similar applications | ||
| + | |||
| + | |||
| + | |||
| + | ===== Objectives ===== | ||
| + | |||
| + | //**TBC**// | ||
| + | |||
| + | ===== Informal Requirements ===== | ||
| + | |||
| + | The ODM solution needs to be able to provide the following: | ||
| + | |||
| + | * Version management and control of all registers and data. | ||
| + | * Internal access by desktop, laptop and mobile device | ||
| + | * External access in the future (?access methods, security?) | ||
| + | |||
| + | and will need to take account of: | ||
| + | |||
| + | * Current CMS (aka CCMS) - Documentum. | ||
| + | * Current ODM tool - APEXs (formerly Oracle HTML DB) | ||
| + | * In use for at least one of the primary registers. | ||
| + | * Current levels of mobile deployment (limited to Supervisory level trackside at the mo) | ||
| + | * Multiple delivery methods (i.e. network, MMS / SMS) | ||
| + | |||
| + | and must be: | ||
| + | |||
| + | * Easier and more efficient for the current workforce to use than the current tools in use. | ||
| + | |||
| + | ===== Quick Questions & Thoughts ===== | ||
| + | |||
| + | ====== Deliverables ====== | ||
| + | |||
| + | //**TBC**// but may include: | ||
| + | |||
| + | * Imaging Roadmap | ||
| + | * Infrastructure platform definition | ||
| + | * Personnel skills matrix and training requirements | ||
| + | |||
| + | ====== Infrastructure Maintenance Structure ====== | ||
| + | |||
| + | This section will grow as more details are available. | ||
| + | |||
| + | {{ nr: | ||