Australian Government Architecture
Search

Enterprise architecture standard

This standard establishes the minimum requirements for Commonwealth agencies to harness the benefits of enterprise architecture (EA) to support digital transformation and embed digital thinking in all aspects of organisational, policy and systems design. 

Applicability of this standard 

These statements detail approaches that agencies can adopt to comply with the Digital Assistance policy. 

Maintain EA as a strategic capability and practice 

Applying EA practices ensures that agencies’ policies and strategies, goals, operating model, capabilities, structure, processes, information, systems and technology are aligned with the agency’s strategic goals and with relevant regulatory constraints. This practice enables optimal use and reuse of government resources and facilitates interoperability between agencies for efficient and effective service delivery. 

The best-practice EA frameworks that can help agencies to establish and maintain EA as a strategic capability include: 

Key practices to consider: 

  • Assess maturity of the EA capability and establish a roadmap, including next best steps, to achieving EA best practice appropriate to each agency’s organisational context 
  • Establish and maintain an EA governance model in line with overarching organisational governance 

Align with the Australian Government Architecture 

The AGA alignment is achieved through: 

  • ensuring that agencies’ ICT strategy, digital investment plans and projects are in line with and informed by AGA capabilities and their own approved EA models and transformation roadmaps 
  • contributing additional capabilities and associated knowledge resources to the AGA to assist with reuse and interoperability. 

Maintain AGA-aligned EA models, documentation and data sets 

Maintaining up to date models and documentation provides agencies with a greater ability to construct modular, interoperable information systems. It also enables joined-up reporting and systemic monitoring of outputs and outcomes, improving visibility of policy effectiveness and benefits realisation. 

The business architecture models should be relevant to agency and portfolios, including: 

  • separate models for distinct lines of business or sub-organisations 
  • a model for ‘corporate’ functions 
  • an overall model at the consolidated ‘group’ or whole-of-department level. 

The data architecture models should include conceptual information models, logical and physical data models.  

These models guide data constructs and the organisation of knowledge, information, data and metadata in line with relevant information architecture standards, to support integrated policy delivery, interoperability and data-sharing. 

The application architecture models should incorporate: 

  • conceptual information systems models spanning the enterprise and aligned with business, data and technology architecture models 
  • actual or planned information system application models, including details of vendor products, services and related agreements, vendor-customised software, configuration artefacts, in-house-developed software, versions, support status and integration components 
  • related documentation and data mapped to the business and information models. 

These models should illustrate how agencies are planning long term sustainability of information systems, including adoption of loosely coupled architectural designs to manage the risk of vendor lock-in and enabling innovation and agility to adapt to policy, business requirement and technology changes. 

The technology architecture models should incorporate: 

  • all technology platforms, tools, components and infrastructure wherever hosted, together with related documentation and data mapped to the agency’s information systems architecture 
  • up-to-date and accurate current state (as-is) and planned target state (to-be) models, data and documentation 
  • details of on-premises and off-premises (data centre) hardware and software, cloud architectures, vendor contracts, products and services, vendor-customised software, and configuration artefacts such as policy settings, in-house-developed software, versions, support status and integration components. 

The EA tools and information repository solutions may be used where scale and complexity require these in their organisational context. 

Proactively manage application and technology portfolios 

This policy requirement and standard statement relates to Application & technology portfolio management (ATPM) practice which is also called out as part of ICT Planning practice. 

ATPM, sometimes split into Application Portfolio Management (APM) and Technology Portfolio Management (TPM), and sometimes referred to as ‘Digital Portfolio Management’ (DPM) is an operational management process that: 

  • inventories and assesses all applications and technology components of an organisation 
  • evaluates lifecycle, cost, risk, compliance, and business value 
  • supports rationalisation, investment planning, and roadmap decisions. 

Relationship between EA and ATPM 

ATPM is best understood as a supporting process within Enterprise Architecture - it provides the data and evidence that EA uses to guide decisions and develop roadmaps. This is how TOGAF and other EA frameworks position ATPM. 

In practice, EA defines principles, target architectures, and standards, whilst ATPM maintains current-state information, tracks technology obsolescence, and informs transition planning. 

Proactive ATPM is called out in this EA policy and standard to ensure ICT Planning is not carried out in isolation from the strategic practice of EA, ensuring there is line of sight between government policy and priorities, organisational strategy, services and programs from a business perspective, and technology risks and opportunities from an ICT/ engineering perspective. 

Ensuring these practices align enables strategic and business-led ICT investment and rationalisation, and alignment between organisational strategy and technology. 

A comprehensive database of all agency’s applications, platforms and technologies is beneficial, including as-a-service components and cloud architecture components. This includes: 

  • all discernible, material components of software and hardware which are in use, or which present ongoing operational costs 
  • components that have not been formally removed from organisational devices or hosting environments 
  • purchases that have not been fully expensed, regardless of their state of use. 

Assessing each identified component of an application, platform or technology against a common rubric should cover as a minimum: 

  • fitness for purpose from an organisational needs and management perspective, including the ability to meet changing regulatory, organisational and government policy needs for the foreseeable future 
  • technical risks and alignment with policies and standards from a technical perspective 
  • risks from a commercial and workforce perspective. 

This assessment should inform and align with EA roadmap planning and help agencies to transition away from older software code bases, transaction processing, database and server environments toward modern, commodity, cloud computing environments. 

The assessment should also be used to manage the risk of shadow IT (ungoverned, unsupported and unmanaged software adoption within agency networks) by taking a proactive approach to: 

  • identifying and assessing risk of unmanaged software detected 
  • building awareness and a culture of compliance 
  • publishing and regular refresh of approved tools and applications 
  • monitoring of emerging technology trends to pre-empt new risks 
  • ensuring future-state application and technology portfolios represents the best strategic choice and optimal value for money for the agency and for the Australian Government, in line with government policies and the AGA. 

Align data and digital transformation investments with EA 

Aligning EA models and ICT strategies, digital investment plans and project proposals (including new policy proposals, associated solution architectures and other data and digital initiatives) helps agencies to maximise the value of their digital investments. 

Focus should be on improving outcomes, service delivery and value for money, including through more effective use of data and digital technologies. 

Enterprise transformation roadmaps that capture agencies’ current (as-is) state to their planned target (to-be) state, are accounting for: 

  • government policy priorities 
  • organisational needs 
  • regulatory compliance 
  • the balance of risks and opportunities. 

Furthermore, agencies’ digital investment plans, projects and ICT strategies also need to be aligned with these roadmaps. 

Embed EA governance 

Following TOGAF, NATO NAFv4 or UAF practice help agencies to establish and maintain an EA governance model in line with overarching organisational governance, incorporating: 

  • an implementation governance/design authority to ensure architectural alignment of solution designs and software component choices 
  • an architecture change management discipline to ensure architecture models, data and documentation represent accurate current state and agreed future state target architectures. 

Other key practices include: 

  • participating in cross-agency architecture forums to facilitate knowledge-sharing, enable interoperability and support progress towards modular digital government where common business capabilities, interoperable solution designs and reusable technology component building blocks support efficient government administration and agile policy implementation 
  • aligning EA security controls with the Protective Security Policy Framework (PSPF) for overarching security governance 
  • aligning EA security controls to the Information Security Manual (ISM) for system and data security requirements. 

Conducting architectural risk assessments at key stages of system development and digital transformation projects, ensures that: 

  • threat modelling is performed during the design phase 
  • security-by-design principles are embedded in architecture decisions 
  • risks are assessed and mitigated before deployment. 

Conducting regular security audits and compliance reviews of EA-driven initiatives is also relevant practice, and includes: 

  • annual security assessments to detect vulnerabilities 
  • compliance validation against whole-of-government cybersecurity policies 
  • ongoing monitoring of security risks throughout the system lifecycle. 

Senior Responsible Officers (SROs) should regularly review EA models for their areas of responsibility, certifying that the models and associated documentation and data: 

  • represent an accurate alignment of organisational capabilities, structure, processes, information, systems and technology with strategic outcomes, goals, strategy and priorities 
  • represent the current and foreseeable needs of the agency 
  • align with relevant risk frameworks and regulatory guardrails. 

Use EA practice and governance to incorporate emerging technologies 

By leveraging agencies’ EA practice and governance framework to evaluate emerging technologies (e.g. AI, blockchain, quantum computing) where applicable, agencies ensure they are adopted in a secure, ethical and strategically aligned manner that drives innovation and operational efficiencies. 

Also, ensuring that risks and opportunities are balanced will help agencies, including aspects such as: 

  • potential security, ethical and strategic impacts 
  • alignment with whole-of-government digital policies and strategies 
  • scalability and sustainability for future digital evolution. 

All automation, AI-driven capabilities and digital identity solutions to be considered by agencies include: 

  • reusing existing architectural and solution building block components where available 
  • Designing capabilities and systems for re-use wherever possible 
  • evaluating against security risks and compliance requirements 
  • Designing in a way to improve service innovation and operational efficiency 
  • integrating into EA roadmaps to support long-term digital transformation objectives.
Was this information helpful?

Do not include any personal information. We are unable to respond to comments or feedback. If you would like a response, please email, or phone us. Our details are on the AGA contact page www.architecture.digital.gov.au/contact-us.