NexusY is the foundation build under Goal 4, Excellence, and the keystone of the FY27-30 technology work. Operational dashboards, automated compliance reporting, financial reconciliation and unified impact measurement all sit on top of it and cannot be built ahead of it. The data governance framework runs alongside.
It is the secure environment where data from our operating systems lands automatically, without anyone touching it. Perfect Gym, SAP, Tanda and Xplor are the core. Others connect as projects need them (Microsoft 365 and SharePoint, Jira, service-specific platforms), and each connection is a deliberate decision based on whether the data is needed for reporting and whether it can be handled safely. Children's Services is live now, the rest follow through FY27.
Sitting over the top is a semantic layer, where we agree and hold the organisation's definitions once (what counts as attendance, revenue, a target) so every dashboard, report and AI answer reads from the same source. Change a definition there and it changes everywhere.
Access is by role, personal information is masked by audience, actions are logged for NQF, and anything touching safeguarding, incidents or financial adjustment requires human approval.
Once the foundation is in, most of what departments want stops being a project. Automated OSHC KPI reporting, POS-to-bank reconciliation, gymnastics class mismatches, offboarding provisioning: individually these are days or weeks of work, not quarters, and there will be many more of them than anyone can name today. Carding each one up front is impossible, and scheduling them a year out is fiction.
So a fixed slice of build capacity is reserved for the queue rather than allocated to named projects. Requests land in Ideas and requests, get verified and sized, then are prioritised at the quarterly review. "When is my thing happening" becomes a position in a queue with a known cadence, instead of a place on a roadmap that never arrives.
No external customer waiting, same people doing it, never competes for the focus slot. Shown here so six months of policy work does not look like six months of nothing.
How to read the focus slots. One focus project per quarter, with its subtasks delegated inside it. Q1 is delivered and Q2 is committed, so the live decisions are Q3 and Q4. Holding is assessed work that does not fit this year and needs a resource, a partner, or a decision that it will not happen. Ideas and requests is the intake tray, where anything new lands until it has been looked at properly.