1. International Activities
Australia
Presented by:
Joerg Huber; Systemic Pty Ltd (Australia)

2. Scotts Valley, California
A4L – Australia
SIF3 Data Hubs
Scotts Valley, California
February 2017

3. SIF3 Data Hubs – Overview
Why a SIF3 Data Hub?
Motivation & Drivers
What do we understand under a SIF3 Data Hub?
Components of a SIF3 Data Hub.
SIF3 Data Hub Styles
Direct
Brokered

4. SIF3 Data Hubs – Motivation/Drivers
All public and private educational jurisdictions in Australia and all major vendors of educational software have agreed to use SIF 3.x as their integration standard in December 2013.
Having all Student Data available “Centrally”.
Having a well defined way (standard) to push and pull student and related data => SIF 3.x.
Easily add/extend student data
Add attendance, student wellbeing, assessment to core data.
Most likely be done with different products.

5. SIF3 Data Hubs – Motivation/Drivers
Allow an easy and efficient way for a state/territory to provide reports/data to schools and/or federal authorities & vice-versa.
NAPLAN Online
DoE: Get away from costly and propriety integration with each product.
Schools: Choice of applications/product that best meet their needs.
Move components around transparently to all parties (i.e. replace a SIS state-wide).
Provide an even playing field for all vendors.
Use the SIF standard and you are in the game.
All schools are potential clients.

6. SIF3 Data Hubs – What is it?
It is an “Eco-System” that uses SIF 3.x as its standard:
It is a place where we know that data can be:
Retrieved from without knowing how the data is maintained and who is providing it.
Push data to without knowing how it is maintained and which system is responsible for.
A platform/environment that ensures
That my data is kept up to date with changes or
I can put processes in place that my data is up-to-date
Data Model and Infrastructure is standardised.
Every participant knows what they “deal” with.

7. SIF3 Data Hubs – Components
The SIF3 Data Hubs that are either in place (NSW, RicOne in NY) or are being in development (WA, CEOM) consists of the following components:
A set of Providers (i.e. SIS, Human Resource System etc.)
A set of Consumers (i.e. Roster, Attendance, NAPLAN etc.)
Optionally: SIF3 Broker
Important: A SIF3 Broker alone is not the SIF3 Data Hub.
It encapsulates implementation details of the SIF3 Data Hub.
Enables some functionality such as Events and centralised Admin etc.
May help to simplify network and security management.

8. SIF3 Data Hubs – Components (cont.)

9. SIF3 Data Hubs – Hub Types
Direct
Suitable for smaller implementations.
One “Monolithic” Central Application that is the provider of all data.
Example: RicOne in NY
Challenges:
Switch components
Add providers
How do keep systems up-to-date?
Administration
Provider
Consumer A
Consumer B
Consumer C
App A
App D
App B
App E
App C

10. SIF3 Data Hubs – Hub Types (cont.)
Brokered
Transparent where each system resides.
Easy to add/remove/switch components.
Multiple providers.
Central Administration of Access Controls and Security.
Can use SIF Events to keep all participants up-to-date.
Suitable for large enterprise and/or state roll-outs that include many applications.
Example: NSW, WA
“Split”
App A
App A
(new)
Broker
App D
App B
App E
App C

11. Questions? ?