====== Image Management ======

===== Description =====

Image Management //(IM)// at NR is exactly as it sounds.  It is the storage and re-distribution of maintenance imagery. 

===== Current Situation =====

Image management is done very much on an ad-hoc basis, often with the images held in a substantial number of MS Access databases floating around the company.  


===== Objectives =====

//**TBC**//

===== Informal Requirements =====

The IM solution needs to be able to provide the following:

  * Storage and maintenance of both stills and videos.
  ** Stills are often generated from mobile phones etc. Videos from front of train capture
  * Version management and control of all images.
  * 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 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 =====

  *Q: Blob vs file system storage
  *T: Transcoding of video streams ? (have a chat to KJorg)
  *Q: How do we identify current MS-Access / other apps that hold this kind of information


====== Deliverables ======

//**TBC**// but may include:

  * Imaging Roadmap
  * Infrastructure platform definition
  * Personnel skills matrix and training requirements