📘 [reference] What is a....[CAD system, on-board router, etc] and what does/should it do?

[e-lo]

Process checklist

• [ ] scope refinement/stakeholder research
• [ ] outline / review
• [ ] content research + dev’t
• [ ] content draft / review
• [ ] final draft / PR on github

Responsibilties

Author: @julieteldred Supported by: @e-lo Reviewers:
Approver: @e-lo

User Stories

As a transit agency staff I'd like to understand what various pieces of transit technology are and how they work in order to correctly plan, procure, and manage the overall transit technology system.

As a transit technology vendor I'd like to understand the basic requirements for my product and where and how it should plug into an overall transit technology "stack."

Specific users

• list of individuals or organizations who have expressed this as a need

Areas to address

For each component:

• purpose and need.
• typical functions.
• attributes.
• externally accessible interactions and methods.
• examples, including how it might relate to other members of a transit technology stack

Information sources

• [ ] transit stack interview report
• [ ] vendors for each component to help self-define (while doing this, please update the products list)
• [ ] FDOT Transit Technology Primer

Content Development Document

[julieteldred]

Question - would it make sense to split this one into a few separate playbooks by category? The original transit stack interview form divided tech into 4 categories (onboard systems, fareboxes/fare payments, scheduling/real time/trip planning, other systems (offboard signage, reporting software, etc) so we could use similar groupings.

[e-lo]

I think the initial task is to define "all the things" (we can always add to the list) and then subsequent tasks will be to organize them and describe how they work from various frames of references. For example: fare boxes would be both in "payment" and "on-board equipment" frames - in both cases we can reference our definition for "what is a fare box and what should it do".