The Problem - A Data Mountain
A modern engineering project generates vast amounts of data. In order to manage effectively and facilitate intelligent decision making, the data must be brought under control.
Many projects fail to meet objectives because the information driving the project is not properly managed, is inaccessible, incomplete or inaccurate.
The data mountain can be quite overwhelming. For example a typical large infrastructure Project may generate:
• 10,000 contract requirements (which can change!)
• 80,000 letters & transmittals
• 100,000 document/drawings/revisions
• 250,000 derived requirements & Control measures
• 100,000 test items
• 250,000 emails
• >1million files on project servers
Everything is Connected
In addition to being an overwhelming volume of information, the data sets do not exist in isolation. A change in one can affect the state of the others.
For example,
• A SCADA alarm point is defined by a requirement
• Which lives in a document,
• Whose status is determined by transmittals
• The SCADA alarm point is also a test item
• The test item is based on other requirements
• The tested item is a particular piece of hardware
• The hardware is running a particular version of software
• The software is part of an overall system configuration
• The SCADA alarm point is also and Interface
• And so on…
Given the interconnected nature of project information a set of spreadsheets or stand alone databases cannot provide clear visibility of the state of your project.