RSSB2679 - Support tool for systems approaches and programme management of technology development and demonstration - Pre-Market Engagement

The Industry's Rail Technical Strategy (RTS) was published in 2012. It has four strategic and long-term goals for the railway to achieve while safeguarding its safe operation: 1. Reduce costs by 50% or more 2. Double capacity 3. Halve carbon emissions 4. Improve customers experience The Rail Technical Strategy Capability Delivery Plan (CDP) builds on the RTS, aiming to manage the changes effectively and meet these challenges. The CDP has been developed through consultation with experts from across the rail industry and the supply chain, and is endorsed by the industry's Technical Leadership Group (TLG), the Rail Supply Group (RSG) and the Rail Delivery Group (RDG). Therefore, the CDP approach has high-level support across the rail industry and represents an agreed common vision and plan. The CDP is composed of twelve 'Key Capabilities' (KCs) that the railway needs to develop to meet the long-term goals. The twelve KCs are: 1. Running trains closer together 2. Minimal disruption to train services 3. Efficient passenger flows through stations and trains 4. More value from data 5. Optimum energy use 6. More space on trains 7. Services timed to the second 8. Intelligent trains 9. Personalised customer experience 10. Flexible freight 11. Low-cost railway solutions 12. Accelerated research, development and technology deployment Each of these capabilities is led by a Work Package Owner (WPO), who is an experienced and delivery focussed professional drawn from the industry. These KCs align the development, deployment and delivery of technologies with the RTS vision. There is significant level of ambition in all the KCs. Each comprises a number of subsystems and these need to work together to achieve success. Additionally, the KCs themselves need to work together effectively to enable the evolution of the wider system. Given much of the activity is about developing and integrating novel technologies and associated changes, the complexity and risks are further emphasised. An enterprise architecture/systems engineering framework will be used to manage this complexity. Scenarios, operational concepts and architectures will need to be developed and captured as they evolve so that they are applicable to defined future timeframes. It will be necessary to understand the linkages, interfaces and dependencies, and most importantly to capture the requirements and make visible their traceability throughout the development process through to verification and validation of the finished product.

If you're organisation believes that you can provide the services & tool required as described in this document please provide a basic proposal to the following email address:

[email protected]

Please provide your proposal by Friday 2nd March 5pm.

Note: At this stage RSSB is not conducting a formal procurement exercise. The purpose of this document is for that of Pre-Market Engagement to understand market interest and potential capability.