Integrations and source ownership

• Identity provider. Map staff user accounts to team membership and remove access when a member becomes inactive.
• Fleet system. Agree how external driver authority and fleet IDs map to driver and vehicle records, and which system owns readiness updates.
• Location or routing service. If used, map its stop and time observations to the correct run and ordered stop before accepting them as operating evidence.
• Student information system. Keep personal student identity in its designated system; use route, authorized stop, boarding time and passenger count for the transport record.

Name the source of each identifier and the person responsible for resolving a conflict. If a connection is implemented, use stable event or operation keys for retries. When an action has an uncertain result, inspect any original operation receipt and external reference before repeating it. Agree the organization’s time zone and how late or corrected observations are represented. Limit each connection to the data needed for the operational record and test access with the actual role accounts.

Use the implementation plan to rehearse the first connected case.