Home >> ICT Strategy & Governance >> Australian Government Architecture >> AGA Reference Models version 3.0 >> Text Descriptions

Text Descriptions

Figure 2-1: Australian Government Architecture (AGA)

This image represents the AGA framework. This framework includes the following parts:

• The Framework, a meta-model defining the linkages between the 5 Reference Models
• 5 inter-related Reference Models. These models are: 
• Performance or PRM – this model consists of two components “Outcome” and “Requirement”, “Requirement” being a sub-level component
• Business or BRM – this model consists of two components “Capability” and “Process” sub-functions. Process is a sub-level component. The PRM and the BRM share a relationship through their sub-level components, Requirement and Process, respectively
• Service or SRM – consists of the two components 'Shared Component' and 'Shared Service'. Shared Service is a sub-level component. The BRM and the SRM share a relationship through their sub-level components, Process and Shared Service, respectively
• Data or DRM – consists of the two components 'Data Asset' and 'Exchange Packet'. Exchange Packet is a sub-level component. The SRM and the DRM share a relationship through their sub-level components, Shared Service and Exchange packet, respectively.
• Technical or TRM – consists of the two components 'Product' and 'Standard'. Standard is a sub-level component. The DRM and the TRM share a relationship through their sub-level components, Exchange Packet and Standard, respectively.
• 5 components that support the Reference Models, including:  Principles; Patterns; Standards; SOA Repository; and the Service Catalogue Repository.

This document describes the Reference Models.

Back to Figure 2-1

Figure 4.2: Linking the PRM to the AGA Reference Models and Agency Architecture

Figure 4-1 illustrates the connections between the five AGA Reference Models and Agency Architecture elements consisting of Programs and Capabilities, Services and Components, Technology and Data.
For example, of the PRM domains;

• Outcomes link to Agency Programs and Capabilities;
• Outputs and usage link to Agency Programs and Capabilities, and Agency Services and Components;
• Work activities link to Agency Services and Components; and
• Inputs link to Agency Technology and Agency Data.

BRM domains link to Agency Programs and Capabilities.
SRM domains link to Agency Services and Components.
TRM domains link to Agency Technology.
DRM domains link to Agency Data.

Figure 4.3: Combining the BRM and the PRM

BRM =

• What services do we deliver?
• What functions of government do we enable?
• What is our organisation structure?
• What are our business capabilities?

BRM + PRM =

• How effectively do we deliver services?
• How effective are we in securing outcomes for government?
• Is our structure optimal for our business?
• How well are our business capabilities performing?

Back to Figure 4-3

Figure 4-4: Combining the SRM and the PRM

SRM =

• What are our business processes?
• What shared services do we have?
• What processes have we automated?
• What are our service capabilities?

SRM + PRM =

• How efficient are our business processes?
• What processes should we be improving?
• Do our shared service areas have capacity?
• Are our service capabilities performing to the required level?

Back to Figure 4-4

Figure 4.5: Combining the TRM and the PRM

TRM =

• What products do we use?
• What infrastructure do we have?
• What standards do we embrace?
• How many products have we got?

TRM + PRM =

• How much does our technology portfolio cost us?
• How much capacity do we have on our infrastructure?
• How readily can our systems interoperate with one another?
• How reliable is the infrastructure we have?

Back to Figure 4-5

Figure 4.23: Forms of Work

Figure 4-23 illustrates the three forms of work: Ad-hoc, Operations / Business as Usual, and Projects, and how they are impacted by:

• the duration of the process or activity involved (short to long);
• the amount of control required (informal to highly formal);
• frequency of process execution (one-off to highly repetitive); and
• the effect on business operation (always change to always stable).

This is explained further in the surrounding text.

Back to Figure 4-23

Contact for information on this page: AGA@finance.gov.au

Back to top