Four disciplines, one aim
A system that does what it was meant to do, and evidence that it does. I work across the whole lifecycle, on client side or supply side: in delivery roles, in helping client teams specify and procure, and as an independent reviewer.
Systems engineering
Setting up and leading a systems-based approach to delivering a project, so that every discipline works to the same requirements and the same picture of the whole.
- Stakeholder and system requirements, written to ISO/IEC/IEEE 29148 and other best-practice standards
- Requirements management and traceability through design, build, and test
- Verification and validation planning and implementation
- Safety, RAM, EMC, and human factors engineering
ExampleLed the systems engineering team on the Bank Station Capacity Upgrade through detailed design, construction, and handover.
Technical assurance
Demonstrating, with evidence, that designs and completed works meet the client's requirements and standards, so they are accepted first time.
- Assurance regimes built around the client's own standards and frameworks
- Reconciling the expectations of several stakeholders into a single, consistent regime, without gaps or duplication
- Assurance of designs and of completed works
- Bringing assets into use and handing them over into operation and maintenance
ExampleDeveloping the assurance regime for the HS2 Euston project to meet the combined requirements of HS2 Ltd, London Underground, and Network Rail.
System integration
Bringing new and existing systems together safely, often while the railway keeps running.
- Technical integration strategy and plans
- Interface management across disciplines and contracts
- Railway migration planning: bringing new system configurations into use in stages
- Integrated, multidisciplinary design that is safe, operable, and maintainable
ExampleWrote and applied the Railway Migration Plan that took Bank station through three intermediate operational configurations into its final form.
Engineering management systems
Defining how engineering gets done on a project: a process framework, the individual processes beneath it, and the information systems that support them, designed to be pragmatic and actually used.
- Process frameworks for a whole project or organisation, down to individual processes
- Reviewing existing processes for gaps, overlaps, and inefficiencies, and integrating them so they work together
- Engineering management plans and the documents beneath them
- Training and mentoring to embed new processes
- Requirements and assurance environments built on IBM DOORS, with automated reporting
- Tracking the production and acceptance of engineering deliverables at scale: around 4,000 at Bank
- Software extensions to IBM DOORS, designed and built in-house, with users including the Ministry of Defence, NATS, Network Rail, Rolls-Royce, and NASA
ExampleRe-architected MaceDragados' engineering management system for the HS2 Euston project, and wrote its overarching management plan and supporting documents.
Need one of these on your project, or all four?
Get in touch