1. Progressive Assurance
Using system engineering tools and techniques to support project managers
Simon D’Cruz
Head of Rail Systems and Projects

2. Synopsis
 System Engineering Tools and Techniques can enable Project and Programme Managers
• Decomposition and Traceability
• Real-time Reporting
Stakeholder
Management
• Complex Software Development
• Progressive Assurance
Progress
Monitoring
• Impact on RequirementsChange

3. Delivering Railway Safety
 Signalling has developed since the birth of rail
nearly 200 years ago
 Signalling systems have evolved with technology
 Mechanical Locking
 Relay Interlocking
 Software Safety Systems

4. ERTMS – the European Rail Traffic
Management System
 December 1989: EC started investigations in S&T issues
 June 1991 : Eurosig and UIC agreed on the principle
 December 1993: TSI conceived
 Summer 1998: UNSIG Formed of the key system suppliers
 April 2000: ERTMS Specification Issued
 Objective:
 Provide interoperability across international boundaries
 Standardisation through replacement of national ATP systems
 Reduce whole life cycle costs
 Increase network capacity, flexibility and capability

5. Deployment to Date
Over 80,000km worldwide and over
10,000 vehicles fitted
Worldwide deployment
In the UK
 One trial site on the Cambrian Line
 Projects underway on Thameslink
and Crossrail
 Future deployment being led by the
Digital Rail team in Network Rail

6. Paper Driven?
 Consider a modern infrastructure programme
 5 yrs, USD 300M, Owner’s or General Contractor’s viewpoint
 50,000 Document & drawing items
 10,000 Formal letters
 30,000 Test items
 >1,000,000 files and other objects on shared servers
 Thousands of other related lists and items such as change requests, punch
items, permits, certificates, interface data etc.

7. A requirement life cycle
 The Need: Passengers expect internet access during their journey
 The Requirement: the train shall be fitted with wi-fi technology that can be
accessed in parts of the carriage
 The requirement lives in a document,
 The requirement is then defined in design documents and drawings
 The requirement is validated by a test item
 The test item is based on requirements
 The tested item is a piece of hardware
 The hardware is running a version of software
 Which belongs to a system configuration

8. Requirements on a Safety Critical Project
Source 6,000
Requirement
50 Safety
Requirements
Preliminary
Design
5000
Requirements
30 Safety
Requirements
Detailed
Design
13,000
Requirements
300 safety
requirements
Final
Handover
23,000
Requirements
400 Safety
Requirements

9. Results
97%
6
Contractors
55 Changes
5,000 Req

10. Stakeholder Management / Requirement Management
Identify
Plan
Manage
Control
Engagement
Capture
Decompose
Trace
Validate

11. How does Progressive Assurance help Project
Managers?
Progressive
Assurance
Config-
uration
Design
Review
Safety
Assurance
Assumptions
Schedule
• Configuration Control version control,
baselines and change control
• Online Design Reviews enabling full design
life traceability
• Requirements Schedule planning
• Assumptions management

12. Streamlining the design governance

13. Planning for Progressive Assurance
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
PRELIMINARY
DESIGN
FINAL DESIGN MANUFACTURE INSTALLATION COMMISSIONING OPERATION AND
MAINTENANCE
PROGRESSIVE ASSURANCE
Planned
Actual

15. In Conclusion
System Engineering can provide the techniques
to
 Better stakeholder management
Progressive Assurance provides the Tool
 Enables assurance through the project
process and not just at the end
 Real time management and reporting
 Reduces reliance on design submissions

16. This presentation was delivered
at an APM event
To find out more about
upcoming events please visit our
website www.apm.org.uk/events