Operational time and sessions
Sydney and Perth scheduling should be represented by separate named zones; their seasonal behavior differs. Agree which Australian location owns the deployment and avoid treating the whole country as one fixed offset.
Market data · deployment planning
Market Data for Brokers in Australia
Plan a market-data deployment for Australia around the actual source, hosting route, instrument calendars and consumer requirements.
Regional acceptance checks
Exercise a Sydney daylight-saving transition and a handover to Perth-based operations. For global instruments, verify the local date label against the UTC archive key so an overnight quote is not stored in the wrong daily bucket.
Requirements to confirm
- Deployment city and hosting environment
- IANA zones: Australia/Sydney and Australia/Perth
- Per-instrument holiday calendars
- Measured route and incident ownership
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.
Integration brief
A practical deployment brief for Australia
| Operating location | Identify the actual hosting city and consumer location before selecting the delivery route. |
|---|---|
| Time zones | Australia/Sydney and Australia/Perth. 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. |
Separate location from instrument policy
Australian operating zones do not all share the same seasonal clock behaviour. Choose the deployment city and instrument calendar explicitly.
What to test
- Test local date boundaries and the relevant daylight-saving cases before launch. A source trading day can differ from the date shown by an Australian consumer; retain both definitions in reporting.
- Check that incident ownership covers the sessions your consumers use.
- Compare source event time with receive time rather than reporting an unexplained latency number.