By getting the level of detail correct in the System Definition it will do far more than bound the system against which hazard identification and safety analysis activities are to be conducted.
The following problems can all stem from an inadequate System Defintion being employed on projects:
> Lack of clarity or confusion about what the system is supposed to do;
> Integration problems;
> Inadequate safety and authorisation activities;
> Weak control of suppliers/sub-contractors;
> Non-existent or inadequate test and acceptance strategy;
> Inadequate costing and time-scale estimation.
A system
definition that has had input from sponsor, engineering and project management
teams will help drive a number of key activities helping to prevent the problems identified above:
> Systems
Architecture diagrams and descriptions
>
Requirements capture and apportionment
> Interface
specifications and control documents
>
Stakeholder engagement plans
> Approvals
strategies
For details on how to find out more on our experience and how we can
bring this to your programme to make sure as little as possible falls through
the gaps please get in touch.
