Page 43 - Ranger Demo

So, NCGI needs to think in terms of describing our capability differently. The Fig 2 is a generic data
reference architecture, not specific to NCGI, that describes a data-centric capability and the description of the functions within an organisation. Culturally we are starting to think in this way rather than starting with an organisational hierarchy diagram in the hope that data moves through it correctly by buying some technology. There is significant natural and cultural inertia to the change in thinking. However, we are working hard to upskill our workforce that resets the cultural default away from organisational hierarchies towards describing functions and how data should flow through the organisation. The reference architecture describes functions, where the data goes, where is it stored, how is it analysed, and how is it presented.
Figure 2
Describing NCGI’s operating model in terms of functions that connect data sources to data consumers, human or machine1, should be the primary view of how an organisation operates, drives the processes, what can be automated and how data is pushed or pulled through the diagram flow. Then you define where you have people in, on or outside the system, their numbers, training, skills and expertise required. That then determines where and what type of technology you need. Backing all that up is the data governance, audibility and accountability that supports this.
Data Ingest
Consider one element of the whole data chain – the front end that collects and ingests data that we have culturally ignored for too long. We have focussed on Data Sources and collection capabilities and, in loading that data into whatever system is available, hope that magic happens at the user end. But we have missed two fundamental processes in the data ingest chain and have routinely under- resourced it from an enterprise perspective.
1 Could be through dash boards, batched mission data, dynamic or static web content or paper product
41