Premier data: read-only in, tools out

Premier data: read-only in, tools out A data-flow diagram generated by Archify. 01 / Premier sources 02 / Access 03 / Iris 04 / Outputs 05 / Readers Premier SQL · riggerdb1 · 01 / Premier sources · 5 databases Premier SQL riggerdb1 5 databases Cloud sources · ScotPac · HF API · 01 / Premier sources Cloud sources ScotPac · HF API Read-only access · VPN SQL · HTTPS APIs · 02 / Access Read-only access VPN SQL · HTTPS APIs Iris + Brain · analysis · checks · 03 / Iris Iris + Brain analysis · checks Premier Cashflow · :8652 · Postgres · 04 / Outputs Premier Cashflow :8652 · Postgres Premier Portal · Firebase · 04 / Outputs Premier Portal Firebase Intranet pages · Laravel sandbox · 04 / Outputs Intranet pages Laravel sandbox Luke · cashflow owner · 05 / Readers Luke cashflow owner Premier staff · finance · ops · 05 / Readers Premier staff finance · ops Premier IT · production · 05 / Readers Premier IT production SQL over VPN HTTPS API · scrape read-only SELECT · GET builds 13-week model deploys HTML + data designs sandbox browser local browser portal app handoff IT ports it Legend primary data policy / PII async batch data store data flow

Read-only by design

  • • Premier SQL (riggerdb1): Exo, EPOS, Micropay, HF, Intranet
  • • SQL uses a reader-only login; Micropay still uses Luke's own

What gets built

  • • Premier Cashflow: 13-week actuals and forecast
  • • Portal analyses; intranet pages IT ports to production

Scheduled checks

  • • Docket wrap-up weekdays 16:00; payroll audit Wednesdays
  • • ScotPac collections 08:00; a cash pulse 3 times a day