Your lead engineer and programme manager, inside the team from design to handover.
Our engineers are embedded with owners, designers, integrators and contractors on complex public transit programmes. They carry IEC 62443 and CLC/TS 50701 through the programme, and use the cyber digital twin to hold every drawing, document and decision in one model.
A transit programme
Thousands of documents, a dozen disciplines, one handover date.
Many disciplines
Civil, mechanical, architectural, systems and control teams each issue their own drawings and specifications. Security cuts across all of them, and no single drawing shows it.
Many parties
Owner, operator, designers, integrators, contractors and regulator each hold part of the picture and answer to a different contract.
Many years
Decisions taken at design are tested at factory acceptance and practical completion, years later, when people have moved on. The reasons go with them.
A checklist can record that a requirement was ticked. It cannot say whether a control works in this station, or whether it was worth what it cost. That needs a model of the whole programme.
Embedded, not visiting
Our engineers work inside your team, from design to handover.
Lead IEC 62443 engineers and programme managers sit with the owner, the designers, the integrators and the contractors. They take the compliance and risk decisions with you, in the room, and answer for them. Delivered by Eigenia and its partner network.
Lead IEC 62443 engineer
Technical authority for OT security. Owns the requirements, zones, conduits and target security levels, and signs off design and test.
Programme manager
Runs the compliance programme across parties and contracts, keeps the register of risks, decisions and deviations, and protects the investment the owner approved.
Systems and control engineer
Reviews integrator designs and witnesses factory and site acceptance of the security functions.
Discipline liaison
Works with the mechanical, architectural and civil teams so that security is designed into stations, tunnels and plant rooms, not added afterwards.
Institutions, disciplines, sector
We understand how transit gets built, and who has to agree.
Institutions
Owners, operators, funders, regulators and the contractors who deliver for them: who decides what, who carries the risk, and where a requirement has to be written into a contract to be met.
Disciplines
Mechanical, architectural, civil, electrical and control engineering, and how each one changes the security of the whole. A ventilation plant room and a station network belong in the same risk model.
Sector and reference architecture
Stations, tunnels and depots, with network, wireless, CCTV, building management and physical access, as on City Rail Link. A reference architecture gives every party the same starting point, and the model records where a project departs from it, and why.
Standards, applied as one programme
IEC 62443 and CLC/TS 50701, carried through the whole programme.
IEC 62443 gives the structure, from the owner's security programme to the component. CLC/TS 50701 applies cybersecurity to railway applications. Our engineers apply both together and take the decisions between them with you.
IEC 62443-2-1
The asset owner's security programme
IEC 62443-3-2
Risk assessment, zones, conduits and target security levels
IEC 62443-3-3 and 4-2
Verification of system and component requirements
IEC 62443-2-4
Requirements on integrators and service providers
CLC/TS 50701
Cybersecurity for railway applications
One model
A cyber digital twin holds the programme's drawings, documents and decisions.
The twin ingests engineering diagrams and documents as they are issued and turns each into a connected record, not a file in a folder. The models of each discipline join into one model for risk and threat management.
- 01
Ingest
Complex engineering diagrams and documents are read into the model as they are issued.
- 02
Join
The mechanical, architectural, electrical and control views join, so they describe one facility.
- 03
Assess
Risk and threat are assessed once, on the unified model, against IEC 62443 and CLC/TS 50701.
- 04
Ask what if
Changes, controls and investments are tested on the same model.
- 05
Record
Every answer is kept with the decision it supported.
What if, not a checklist
Which controls will work here, and what is the best use of the money?
A checklist confirms that a requirement was met. The model shows whether a control reduces the risk in this design, and what a change does to the risk and to compliance, before anyone commits.
Which controls are effective
Each control is tested against the threats and the design it sits in. The programme keeps the ones that reduce risk, not the ones that fill a row.
What a change does
A change to a design, a supplier or a schedule is run through the model first: its effect on risk, on compliance and on the other disciplines.
Where the money goes
Investment options are compared by the risk they remove and the time and effort they take, so funds go where they matter most.
What was accepted, and why
Where a requirement cannot be met, the deviation is recorded with its reason and the control that stands in for it.
Questions the room asks
- What if the station network design is simplified?
- What if a wireless system is delivered a year late?
- What if this control is dropped to save budget?
Case study
City Rail Link, Auckland. Lead IEC 62443 engineer, for more than a year and a half.
A new underground rail line produces documents faster than anyone can read them. The twin read them: more than 4,000 engineering documents, from low-level designs and interface control documents to safety and reliability cases, minimum operating requirements, hazard and risk registers, audits, test results, threat and vulnerability assessments, security-related application conditions, handover documentation and training.
Each became a connected record of the system rather than a file in a folder, and operations used the same model to run what-if scenarios on investment decisions.
Handover
A durable record for factory acceptance, practical completion and the operators.
Everything the programme decides is kept in the model: requirements, test evidence, hazards, controls and who is responsible. At factory acceptance and practical completion the record is complete, and the operators receive it, not a pile of documents.
- Factory and site acceptance evidence, traced to the requirements
- The practical completion record: what was built, tested and accepted
- Hazards and operational controls, in the operators' terms
- Governance: who is responsible for what after handover
- Training, built from the same model
Across jurisdictions
Transit is procured under national law. We start from the record.
Eigenia has researched 226 of 249 jurisdictions, every fact sourced, with the dates that apply. An engineer embedded in a programme in a new country starts from that country's law and standards, not from a blank page.
Research by countryScoped to the facility
Every engagement starts from the facility's country, sector, type, supply chain and external pressures. The researched record for the country, and the origins of its parts and software, set what the work has to cover.
Where this has been done
- Public transit
- Lead IEC 62443 engineer on New Zealand's City Rail Link · network, wireless, CCTV, building management and physical access for new stations and tunnels
- Railroad
- Segmented OT architectures and Positive Train Control programs for North American Class I freight railroads · field operations bridged to enterprise systems
- Nuclear energy
- Security architecture and cyber-physical patterns for a nuclear installation · where the safety case is everything and the margin for error is zero
Start with the facility
Send the country, the sector and the facility type. The enquiry form carries the service with it.
This Site Uses No Cookies
Eigenia does not set cookies. The only thing stored in your browser is one preference, saved in local storage, noting that you have seen this notice.