Plan a market-data deployment for Canada around the actual source, hosting route, instrument calendars and consumer requirements.
Canadian teams can span a substantial east-to-west time difference. Identify which operating location owns alerts and which calendar defines each instrument; a Toronto support shift does not define the session for every source.
Test handover between Toronto and Vancouver working hours, including overnight incidents. Validate the treatment of CAD quotation and local display time separately from the stored UTC event time.
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
| Operating location | Identify the actual hosting city and consumer location before selecting the delivery route. |
|---|---|
| Time zones | America/Toronto and America/Vancouver. Preserve source and archive timestamps in UTC. |
| Instrument calendar | Confirm the source calendar per instrument, including holidays and session breaks. |
| Acceptance evidence | Record the route, test window, clock synchronization and responsibilities for each layer. |
Canadian operating hours depend on the city and market being served. A single country label is insufficient for scheduling instrument sessions or maintenance.