TAP provides the consultancy and systems engineering that turn a transit authority’s objectives into a buildable, verifiable ITS design. Our work spans technology strategy, concept of operations, requirements and specifications, system architecture, business process design and independent design assurance.
We apply a structured systems engineering life cycle, in which every requirement is traced from the first stakeholder workshop through high-level and detailed design to the test that proves it has been met. Fare collection, fleet management, passenger information, security, networks, depot and energy systems are designed as one integrated whole.
Consultancy Services
From First Concept to Approved Design
Consultancy services cover the full front end of an ITS program. Each produces defined, reviewable outputs that carry directly into procurement, implementation and testing.
-
01
Technology Strategy & Feasibility
Assessment of operational needs, existing systems and market technology, leading to a recommended ITS roadmap, phasing plan and budget estimate for the program.
Key outputsFeasibility study · Options analysis · Technology roadmap · Cost estimate
-
02
Concept of Operations
A stakeholder-oriented description of how the system will be operated, maintained and used: who is involved, what the system does, where and when it operates, and why each capability is needed.
Key outputsConOps document · Stakeholder register · Operational scenarios · Use cases
-
03
Requirements & Specifications
Functional, technical and performance requirements written to be specific, measurable and testable, with output specifications that define outcomes without precluding alternative solutions.
Key outputsSystem requirements · Functional and technical specifications · KPI definitions
-
04
System Architecture & Design
High-level and detailed design of every subsystem, interface, hardware platform, software product, data flow and network, documented to a consistent engineering design framework.
Key outputsHigh-level design · Detailed design specification · Interface control documents
-
05
Business Process Design
End-to-end process models for fare sales and revenue management, fleet scheduling and control, passenger information, maintenance, incident management, change management and cyber security.
Key outputsProcess models · Activity diagrams · Use cases · Operation services plan
-
06
Design Assurance & Owner's Engineer
Independent review of third-party designs, specifications and submittals on behalf of the authority, confirming technical adequacy, compliance and readiness for implementation.
Key outputsDesign review reports · Compliance assessments · Technical due diligence
Systems Engineering Life Cycle
Every Design Decision Has a Matching Test
TAP follows the systems engineering V-model. Each level of definition on the way down is paired with a level of verification on the way up, so nothing is designed that cannot be proven and nothing is accepted that was not specified.
-
Validated by
Concept of Operations
Stakeholder needs and operational scenarios
Operational Acceptance
Trial operation confirms the system meets operational needs
-
Verified by
System Requirements
Functional, performance and KPI requirements
Site Acceptance Testing
End-to-end tests of the installed system against every requirement
-
Verified by
High-Level Design
System architecture, subsystems and interfaces
Integration Testing
Subsystems tested together across every defined interface
-
Verified by
Detailed Design
Equipment, software, data model and installation
Factory Acceptance Testing
Equipment and software proven against the detailed design before shipment
-
Verified by
Build & Configuration
Hardware, software and parameter configuration
Unit & Internal Testing
Component-level tests by the engineering team
Design Deliverables
A Complete, Controlled Design Record
Every design is delivered as a structured set of documents under version control, each with a defined purpose and a defined point in the program.
| Document | What it defines | Stage |
|---|---|---|
| Concept of Operations | Stakeholders, operational scenarios and the needs the system must satisfy | Concept |
| Requirements Compliance Matrix | Each requirement, its grade of compliance and the inspection, test or analysis that will confirm it | All stages |
| High-Level Design Document | System architecture, subsystem diagrams, process flows, security features and preliminary data model | High-level design |
| Detailed Design Specification | Every subsystem, device and software module, with interfaces, configuration and physical requirements | Detailed design |
| Interface Control Documents | Electrical, data and security elements of each interface within the ITS and with third parties | Detailed design |
| Data Model & Data Dictionary | Entities, attributes and metadata for all system data | Detailed design |
| Operation Services Plan | Objectives, activities, quality standards, staffing and the process for monitoring progress | Detailed design |
| Backup & Business Continuity Plan | Data backup, disaster recovery and continuity procedures | Detailed design |
| Test Plans & Procedures | Test cases traced to requirements for factory, integration and site acceptance | Verification |
| As-Built Documentation | Final design, configuration, manuals and drawings reflecting the system as delivered | Handover |
- 01
Review Schedule
A design review schedule is agreed at mobilization and updated with advance notice of each review.
- 02
Incremental Submittals
Design documentation is submitted progressively, with the complete package issued ahead of each review.
- 03
High-Level Design Review
Architecture, subsystems, interfaces and security are reviewed and actions agreed for the detailed design.
- 04
Detailed Design Review
A near-final specification, with draft manuals and training materials, is reviewed against every requirement.
- 05
Approval & Baseline
Resolved actions are approved and the design is frozen as the baseline for build, installation and testing.
Structured Reviews, Approved Baselines
Designs are agreed with the authority through formal review workshops, held at the high-level and detailed design stages and attended by specialists in every subject area under review.
Each review closes with a consolidated summary of design items, outstanding issues and agreed actions. Only once every action is resolved and approved is the design issued as the baseline for implementation.
Design Principles
Designed for Today's Corridor and Tomorrow's Network
- 01
Open Standards
Open interfaces and published data formats, so systems from different suppliers can be integrated and replaced.
- 02
Scalable by Design
Architectures that extend to additional lines, stations, vehicles and operators without redesign.
- 03
Vendor-Neutral
Requirements written around outcomes, keeping the authority free to select the best available technology.
- 04
Configurable Rules
Fare products, tariffs and business rules set by parameters, not by software changes.
- 05
Resilient Operation
Defined behavior during communication loss, with redundancy, backup and disaster recovery built in.
- 06
Secure by Design
Security architecture defined at the start of design, not added at the end of implementation.
Frameworks & Standards
Built on Recognized Frameworks
We design work references internationally recognized engineering frameworks and transit industry standards, applied consistently across every design document.
ISO/IEC/IEEE 15288
System life-cycle processes
ISO/IEC/IEEE 42010
Architecture description
BPMN & UML
Business processes, use cases and activity diagrams
ISO/IEC 27001
Information security management
PCI DSS
Protection of payment card data
ISO/IEC 14443 & EMV
Contactless fare media and bank cards
GTFS & SIRI
Schedule and real-time passenger information data
ONVIF
Video surveillance interoperability
Standards are selected for each program according to the authority's requirements and applicable regulations.
Engagement Models
Consultancy Where You Need It
TAP’s consultancy can stand alone at the start of a program or form the design phase of a complete design, supply, installation and maintenance contract.
Strategy & Feasibility
For authorities defining a new ITS program or modernizing an existing one.
- Needs assessment
- Options and costs
- Program roadmap
Specification & Procurement Support
For authorities preparing to procure systems from the market.
- Output specifications
- KPI framework
- Technical evaluation support
Design & Build
For programs where TAP delivers the system from design through operation.
- High-level and detailed design
- Design reviews
- Implementation and testing
Independent Design Review
For authorities that need an expert check on designs prepared by others.
- Design assurance
- Compliance assessment
- Technical due diligence
Related
Works Together With
Hardware & Software
Management
Comments are closed