presentation slides

22
Australian Government Architecture November 2007 Trevor Smallwood Department of Finance and Administration [email protected] 6215 1679

Upload: zubin67

Post on 19-Jan-2015

178 views

Category:

Documents


2 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Presentation Slides

Australian Government Architecture

November 2007

Trevor SmallwoodDepartment of Finance and Administration

[email protected] 1679

Page 2: Presentation Slides

Agenda

Who are we?What have we done?Why have we done it?How will it make a

difference?

Page 3: Presentation Slides

About AGIMO

• The Australian Government Information Management Office (AGIMO), Department of Finance and Administration is working to make Australia a leader in the productive application of information and communication technologies (ICT) to government administration information and services.

• AGIMO fosters the efficient and effective use of information and communications technology (ICT) by Australian Government departments and agencies.  It provides strategic advice, activities and representation relating to the application of ICT to government administration, information and services.

• www.agimo.gov.au

Page 4: Presentation Slides

Responsive Government

Investing for Growth

Government Online

Better Services, BetterGovernment

Responsive Government

Page 5: Presentation Slides

Capability Goal

• Our aim is to produce a portfolio of ICT assets that can be reused in new combinations across government agencies. The purpose is to improve citizen service, to better respond to government change, to improve government efficiency and to provide capabilities that will support future policy needs.

• To do this we are developing an Australian Government service-oriented architecture to define the frameworks, components, standards, patterns and principles that will guide government investment decision-making and government project development.

• We are also developing a series of frameworks, tools and governance structures that will support increased standardisation, reduced duplication and improved collaboration between agencies.

Page 6: Presentation Slides

Governance

ManagementAdvisory

Committee

Secretaries’Committee

on ICT

Business ProcessTransformation

CommitteeCIO Committee

AGSAWG

Page 7: Presentation Slides

Australian Government ArchitectureFramework

Page 8: Presentation Slides

Principles

• Cross-Agency Services Architecture Principles

• Published in April 2007• Summary of the principles

– Bi-fold brochure

• Full text of the principles– agimo.gov.au

Page 9: Presentation Slides

Australian GovernmentArchitecture (AGA)

• Endorsed by CIOC • Published in June• Focus on:

– Service Reference Model (SRM)

– Data Reference Model (DRM)

– Technical Reference Model (TRM)

• Full text of the Reference Models

– Hard copy reference

– agimo.gov.au

• Funding proposals for 2008/09 will be mapped to the SRM

Note!

Page 10: Presentation Slides

Reference Models - SRM Services level 2

Page 11: Presentation Slides

NPP’s, Business Cases

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

Business CaseThis is a paaper that has been written

to

demonstrate

What a document looks like

When it is written up and produced

On an etremely small type face, but it

will show people looking at this slide

that it does represent a document

covered with text

The structure of the document is not at

all obvious but I may become clearer

Google News Alert for: 'enterprise

architecture','soa'

Putting the A into SOA is a vital step

Computerworld New Zealand -

Auckland,New Zealand

Having (and following) an enterprise

architecture can also avoid a classic

mistake: treating SOA as a

departmental issue. SOA is too big to

tackle all at ...

See all stories on this topic

Java Feature — The Holy Grail of

Database Independence

MapA

nalyse

Finance - AGA and NPPs

Why no business

capability?

12Opportunity for service

reuse?

Why no data

involved?

Page 12: Presentation Slides

New Policy ProposalsBusiness Cases

Project C

Project B

Project A

Capability Assessments

ICT Investment Proposals

Projects

Implemented Solutions

Capabilities

Re-use, shared services, patterns, templates

Gaps, overlaps

Patterns, templates

Mapping

Investments

Page 13: Presentation Slides

Sample Budget Assessment

Page 14: Presentation Slides

Decision-making

Yesterday Today Tomorrow Opportunity Possibility

ProjectManagement

Architecture

ProgramManagement

Strategy

Operations

Review

PortfolioManagement

Demand

Page 15: Presentation Slides

Reactive Proactive

PerspectiveYesterday Today Tomorrow

Era

Policy/Technology Continuum Policy Strategy Safety Net Participation Attainment

Policy TargetPolicy Driver

Customer FocusDelivery Output

Delivery StructureValue Model

Application Architecture

Technology FocusLocus of Contact

Delivery Provisioning

Symptoms Barriers CausesPoverty Economy Well-being

Circumstance Behaviour ResponsibilityPayments Referrals Pre-emptionsCentral Local Virtual

Value Chain Value Shop Value NetworkProcedural Service Oriented Event DrivenDatabase Connectivity Embedded

Processing Agency Provider Nodes IndividualAssessment Service Offer Orchestration

Preventive

Capability

Page 16: Presentation Slides

Using the Reference Models

• Common language for classification of ICT asset base’• Project footprint, revealing work impact, relevance to

priorities and need for cooperation and collaboration.• Asset footprint, revealing health and supporting

change impact assessment.• Strategy footprint revealing strategic needs and gaps

on the ICT asset-base.• Investment footprint, showing investment strengths,

weaknesses, overlaps and gaps. • Strategy repository holding principles, standards and

patterns to be implemented to meet future strategic needs.

• Communication tool to discuss impacts and implications with stakeholders.

• Knowledge footprint, to be used with “customers” and stakeholders to reveal knowledge gaps in necessary information to complete a strategy or project.

Page 17: Presentation Slides

Services & Reuse

MoreGeneric

MoreGeneric

GovernmentService

InboundServices

Eg.RegistrationAuthenticationCircumstances

Eg.Case ManagementCompliance

Eg.NotificationPayment

MoreSpecific

AssessmentServices

ReviewServices

OutboundServices

Page 18: Presentation Slides

Services & Reuse

Presentation

Orchestration

Resources

More Flexible

More Stable

Page 19: Presentation Slides

3rd Parties

No-one left out No Wrong Door One Stop Shop Self ServiceStraight-through

ServiceEvent Automated

Service

On Phone On Line

Event Service

On SiteEvent ProcessManagement(back office)

Government Business Process ManagementCommunityAccessPoint

Lead Agency A

Lead Agency B

Agency C Agency ZService Finder

Org 1 Org n

Intensive Service Assisted Service Self Service

Safety-net Participation Responsible

EmploymentHealth

International TravelJustice

EducationWelfare

Security

GovernmentService DeliveryBlueprint

1

2

3

4

5

6

7

Page 20: Presentation Slides

• The individual outcomes layer (1) represents a high level view of recipient behaviours that recognises variant abilities and also policy vision. There are people who will not be able to look after themselves and will need a safety net. These are typically people with severe disabilities, deprivations or strong anti-social proclivities. There are people who lack motivation and/or skills to look after themselves and will need assistance and encouragement to participate in the society and the economy. The majority of people are capable and willing to be responsible in their relationship with government policy and programs. Harnessing this responsibility will help improve efficiency, effectiveness and satisfaction while at the same time releasing resources for more intensive work.

• The quality of service layer (2) defines the service delivery value that the strategy offers Australians and our visitors. Qualities of service are strongly focussed on the capabilities of people represented in the individual outcomes layer. At the intensive end, we need to ensure that no one is left out. We need to help those who can get on their own two feet with a little assistance, we need to give control to those who want to be in control and we should make things as convenient and automated as is efficient and effective.

• The service type layer (3) lists the four main approaches available for service delivery. These relate closely with the individual outcomes and quality of service layers and make optimal use of the channel layer for their different approaches. This could also be called the delivery strategy layer and it represents core ideas in the strategy.

• The channel layer (4) represents the different ways of interacting with people and exchanging information. It includes the usual set of on-site, on-phone and online channels. It does not specifically include on-paper, though the strategy will need to allow for paper for some time. It also includes an automated back-office channel. This might be considered as a version of on-line, but is mentioned separately as it is not a personal channel – it is organisation to organisation – automatically updating information that changes in one organisation with another that has a legitimate and approved interest in that information. Agencies are venturing into these updates now, eg getting earnings data on a weekly basis from employers.

Page 21: Presentation Slides

• The Government Business Process Management layer (5) is the core element of the model that connects agencies and channels together and permits interoperability, service continuity and consistency. This layer represents the design and definition of government business processes as well as the technology needed to support their sharing and integration. It does not include the processes or systems themselves. They remain with their responsible agency. This is the layer that should be the key focus of the Business Process Transformation Committee (BPTC). In architecture terms, this is where the business reference model (BRM) sits, though elements of the BRM will reside with agencies. In technology terms it also represents the orchestration layer and services platform for a whole of government service oriented architecture (SOA).

• The agency layer (6) recognises the role and accountabilities of individual agencies in the strategy. Agencies are responsible for specific processes and make these available as services in the process management layer. They also use services provided by other agencies. This is one reason why agencies need to adopt SOA

• The portfolio layer (7) is a sample of the portfolio interests that can served by this strategy and demonstrates how they might fall in across the elements of the strategy.

Page 22: Presentation Slides