Software package and information systems

Tender description

The purpose of this PIN is to commence market engagement and request information to support the building of a business case for this requirement. LNER are seeking to identify a supplier who could deliver sensor technology, including hardware and supporting software elements across our fleet (see appendix for details on our current fleet) which will enable us to collect and utilise capacity/occupancy information in real-time. LNER are seeking to understand the capacity/occupancy of the following on-board spaces: — Priority 1: Every Seat, — Priority 2: On board luggage and storage areas: —— shelved luggage racks and bulk luggage storage areas; —— on-board bike storage areas. Hardware The supplier will provide all on-board sensor equipment including sensors themselves and any additional management equipment. Hardware must be able to be controlled and configured remotely and on-train, with the ability to transfer data-off train throughout every train’s service. Any provider must work with both LNER and our train provider’s teams to develop the design, installation and removal processes for all on-board hardware elements (sensors and any control units) which must strictly adhere to health and safety and asset management guidelines. The supplier will work alongside our train supplier’s teams to install commission and test all equipment. Once installed, commissioned and tested the support and maintenance of all hardware components will be the responsibility of our train supplier. While we would want visibility of the service status ongoing monitoring and support should sit with the supplier. We expect the service to be fully managed and supported by the supplier for the life of the contract (include maintenance of equipment and support). The ‘Occupancy sensing’ must be able to distinguish between a person and luggage or belongings and system restarts must be easy to reset. Data integration and software support We would expect the system to provide an API which connects to website, apps (for both staff and consumer channels), data management and train planning systems, plus other additional LNER and industry systems. This API connection must be able to transfer the following information elements: — real-time information about occupancy at a seat, luggage unit level (based on the sensor reading and versus expected booked capacity), — real-time information about the type of occupancy of the seat (e.g. person or human) and percentage available capacity per luggage unit, — real-time information about unoccupied seats including – time unoccupied for, waypoint vacated. This information must be captured via the sensor units and transferred in real-time throughout every train’s full service diagram. Data transfer should be secure (any system will be subject to PEN testing) and the system should comply with LNER data and architecture principles which can be found in the appendix. The software system must be clearly documented, easily manageable and configurable with remote reset capability. The longer term objective of the sensor program is to enable real-time management of on-board capacity based on real-time occupancy data, including enabling in transit seat sales/reservations (after the train has left it’s station of origin). This will be realised through the release of unoccupied seat reservations and the facility to generate additional reservations/advanced purchase bookings through live amendments to reservations and on-board displays. This will require further real-time data generation and integration with: — on-train reservation screens, — industry-wide reservation systems. We can share additional information on API and architecture principles with you to support our request for information on request.