SERVICE 03
A three-week planning engagement for transit operators, regional authorities, and integrators examining how passenger information, ticketing, and customer support interact across Japanese transit nodes.
— WHAT THIS DELIVERS
After three weeks, you'll have a documented plan that maps how passenger information, ticketing, and customer support currently relate across your transit nodes — and sets out a considered path for improving those connections. The engagement concludes with a presentation to your client team, so the findings land in context rather than arriving as a document to interpret alone.
For operators, authorities, and integrators in the early stages of a coordination project, this provides the kind of structured starting point that internal planning rarely produces on its own — an external view, based on actual data, presented in a form suited to the next stage of your process.
EXPECTED OUTCOMES
— THE SITUATION TRANSIT TEAMS OFTEN FACE
Passenger information, ticketing, and customer support rarely sit under a single operational authority. They've developed at different times, often through separate procurement processes, and the teams responsible for each have their own documentation formats and review cycles.
The result is that no one holds a complete picture of how a passenger's experience flows across all three. When a disruption occurs — a ticketing failure during a service change, a passenger information lag at a major node — the gap between systems becomes briefly visible, then closes again without anyone producing a clear account of what happened or what would prevent it.
A coordination project needs a starting point that reflects the systems as they actually are, not as individual teams believe them to be. That starting point is what this engagement provides.
TYPICAL TRANSIT NODE — SYSTEM SEPARATION
— OUR APPROACH
We start by examining how passengers actually move through your transit nodes — where they encounter information, where they interact with ticketing, where they seek support, and what happens at the boundaries between those systems. This is observational work, grounded in current flows rather than theoretical models.
In parallel, we review whatever data sources are available: operational records, system documentation, any prior assessments. We're looking for where the evidence aligns with what we observe, and where it doesn't.
From that foundation, we assemble a written connectivity plan for improving how the three systems interact. The engagement concludes with a presentation to your team — not a document dropped into an inbox, but a structured walk-through of what we found and what the plan proposes.
This engagement is suited to operators, regional authorities, and integrators who are early in a coordination project and need a structured baseline before deciding what comes next.
We examine how passengers move through your transit nodes, focusing on the intersections between information, ticketing, and support. Observations recorded directly.
Available data sources are reviewed alongside observations. We identify where the evidence is strong and where the gaps are — and document both honestly.
The connectivity plan is assembled and reviewed internally before the client presentation. The engagement closes with a structured walk-through for your team.
— WHAT TO EXPECT
The first two weeks run largely independently on our side. Access to relevant data sources is arranged at the start, and we don't return with frequent requests for additional material.
The engagement closes with a structured presentation to your team — so the plan lands with context and your team has the opportunity to raise questions before the document becomes the record.
The written plan is designed as a coordination baseline — practical for the next stage of your project, whether that involves internal planning, authority review, or engaging further partners.
— INVESTMENT
The Transit Connectivity Planning engagement is priced at ¥31,000. The price covers the full three-week engagement — passenger flow examination, data source review, gap analysis, plan assembly, and the closing presentation to your team.
If your situation involves multiple transit nodes across a wider geography, we'll discuss the scope during the initial exchange and agree on any adjustment before work begins. Nothing is added after the engagement starts without prior agreement.
A written scope of work is available before any commitment is made, suitable for internal approval or authority review processes.
WHAT'S INCLUDED
TOTAL INVESTMENT
¥31,000
Three-week fixed-scope engagement
— METHODOLOGY
DAYS 1–5 — WEEK ONE
We examine how passengers move through the relevant transit nodes. Observations focus on the three system intersections: where information is accessed, where ticketing occurs, and where support is sought. Access to nodes is arranged during scoping.
DAYS 6–11 — WEEK TWO
Available data sources are reviewed alongside observations. We document where evidence is strong, where it's absent, and where observations and data diverge. The gap analysis is drafted in parallel.
DAYS 12–21 — WEEK THREE
The connectivity plan is assembled and reviewed. The closing presentation is prepared and delivered to your team. Questions raised during the presentation are addressed on the day and documented in the final record.
PLANNED STATE — COORDINATED TRANSIT NODE
— OUR COMMITMENT
The connectivity plan we produce reflects the passenger flows and data sources we actually examined. Where the evidence is limited, the plan says so. Where a gap is significant, the plan names it rather than smoothing it over. The point is to give your team a reliable starting point, not a document that looks complete but doesn't hold up when tested.
We don't carry vendor relationships that would influence the plan's direction. The systems we examine — information, ticketing, support — are reviewed on their own terms, not against a preferred technology platform.
If you'd like to ask about the engagement before deciding, an initial conversation involves no obligation. We're glad to discuss scope, the presentation format, or what the written plan typically covers.
The plan is grounded in what we examine across your transit nodes and data sources, not in assumptions imported from prior engagements or generic models.
We have no commercial relationship with any transit technology provider. The plan reflects the coordination challenge, not a preferred technology direction.
The written plan and scope of work are structured with the documentation expectations of Japanese public sector and authority review processes in mind.
— GETTING STARTED
Tell us briefly about your situation — the transit nodes involved, the systems in scope, and where you are in the coordination process. No detailed documentation needed yet.
We confirm the scope, access requirements, and who should be involved in the closing presentation. A written scope of work is provided if needed for approvals. No commitment at this stage.
The three-week engagement runs as agreed. We examine passenger flows and data sources during weeks one and two, then assemble and present the plan in week three.
After the closing presentation, the written plan is yours to use in your coordination process. What happens next is your decision entirely.
— TRANSIT CONNECTIVITY PLANNING
Three weeks, a written plan, and a closing presentation your team can work from. Reach out when you're ready to start — or to ask about the scope before deciding.
— OTHER SERVICES
SERVICE 01
A two-week site-survey engagement for municipal teams and property managers. We walk the defined area, review documentation, and return a written assessment covering coverage, gaps, and considered options.
SERVICE 02
Four working sessions for organisations connecting voice, messaging, scheduling, and field reporting tools into a coordinated arrangement suited to Japanese operational norms.