Main heading goes in here second line of main heading

Document Sample
Main heading goes in here second line of main heading Powered By Docstoc
					Australian Government Architecture
                 November 2007



                Trevor Smallwood
     Department of Finance and Administration
        trevor.smallwood@finance.gov.au
                    6215 1679
         Agenda

Who are we?
What have we done?
Why have we done it?
How will it make a difference?
                                    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
                       Responsive
                       Government


Investing for Growth

Government Online

Better Services, BetterGovernment

Responsive Government
                                  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.
Governance
                       Framework
Australian Government Architecture
                                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
Australian Government
Architecture (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!
Reference Models
     - SRM Services level 2
                                                                                                                                                                          Finance - AGA and NPPs

Business Case                          Business Case                          Business Case                          Business Case
T his is a paaper that has been        T his is a paaper that has been        T his is a paaper that has been        T his is a paaper that has been
written to                             written to                             written to                             written to

demonstrate                            demonstrate                            demonstrate                            demonstrate
What a document looks like             What a document looks like             What a document looks like             What a document looks like
When it is written up and              When it is written up and              When it is written up and              When it is written up and
produced                               produced                               produced                               produced

On an etremely small type face,        On an etremely small type face,        On an etremely small type face,        On an etremely small type face,
but it will show people looking at     but it will show people looking at     but it will show people looking at     but it will show people looking at
this slide that it does represent a    this slide that it does represent a    this slide that it does represent a    this slide that it does represent a
document covered with text             document covered with text             document covered with text             document covered with text

T he structure of the document is      T he structure of the document is      T he structure of the document is      T he structure of the document is
not at all obvious but I may           not at all obvious but I may           not at all obvious but I may           not at all obvious but I may
become clearer                         become clearer                         become clearer                         become clearer
Google News Alert for:                 Google News Alert for:                 Google News Alert for:                 Google News Alert for:
'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'
Putting the A into SOA is a vital      Putting the A into SOA is a vital      Putting the A into SOA is a vital      Putting the A into SOA is a vital
step                                   step                                   step                                   step
Computerworld New Zealand -            Computerworld New Zealand -            Computerworld New Zealand -            Computerworld New Zealand -
Auckland,New Zealand                   Auckland,New Zealand                   Auckland,New Zealand                   Auckland,New Zealand
Having (and following) an              Having (and following) an              Having (and following) an              Having (and following) an
e nte rprise architecture can also     e nte rprise architecture can also     e nte rprise architecture can also     e nte rprise architecture can also
avoid a classic mistake: treating      avoid a classic mistake: treating      avoid a classic mistake: treating      avoid a classic mistake: treating
SO A as a departmental issue.          SO A as a departmental issue.          SO A as a departmental issue.          SO A as a departmental issue.
SO A is too big to tackle all at ...   SO A is too big to tackle all at ...   SO A is too big to tackle all at ...   SO A is too big to tackle all at ...
See all stories on this topic          See all stories on this topic          See all stories on this topic          See all stories on this topic
Java Feature — T he Holy Grail         Java Feature — T he Holy Grail         Java Feature — T he Holy Grail         Java Feature — T he Holy Grail
of Database Independence               of Database Independence               of Database Independence               of Database Independence




Business Case
T his is a paaper that has been
written to

demonstrate
What a document looks like
When it is written up and
produced
                                       Business Case
                                       T his is a paaper that has been
                                       written to

                                       demonstrate
                                       What a document looks like
                                       When it is written up and
                                       produced
                                                                              Business Case
                                                                              T his is a paaper that has been
                                                                              written to

                                                                              demonstrate
                                                                              What a document looks like
                                                                              When it is written up and
                                                                              produced
                                                                                                                     Business Case
                                                                                                                     T his is a paaper that has been
                                                                                                                     written to

                                                                                                                     demonstrate
                                                                                                                     What a document looks like
                                                                                                                     When it is written up and
                                                                                                                     produced
                                                                                                                                                               Map
On an etremely small type face,        On an etremely small type face,        On an etremely small type face,        On an etremely small type face,
but it will show people looking at     but it will show people looking at     but it will show people looking at     but it will show people looking at
this slide that it does represent a    this slide that it does represent a    this slide that it does represent a    this slide that it does represent a
document covered with text             document covered with text             document covered with text             document covered with text

T he structure of the document is      T he structure of the document is      T he structure of the document is      T he structure of the document is
not at all obvious but I may           not at all obvious but I may           not at all obvious but I may           not at all obvious but I may
become clearer                         become clearer                         become clearer                         become clearer
Google News Alert for:                 Google News Alert for:                 Google News Alert for:                 Google News Alert for:
'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'
Putting the A into SOA is a vital      Putting the A into SOA is a vital      Putting the A into SOA is a vital      Putting the A into SOA is a vital
step                                   step                                   step                                   step
Computerworld New Zealand -            Computerworld New Zealand -            Computerworld New Zealand -            Computerworld New Zealand -
Auckland,New Zealand                   Auckland,New Zealand                   Auckland,New Zealand                   Auckland,New Zealand
Having (and following) an              Having (and following) an              Having (and following) an              Having (and following) an
e nte rprise architecture can also     e nte rprise architecture can also     e nte rprise architecture can also     e nte rprise architecture can also
avoid a classic mistake: treating      avoid a classic mistake: treating      avoid a classic mistake: treating      avoid a classic mistake: treating
SO A as a departmental issue.          SO A as a departmental issue.          SO A as a departmental issue.          SO A as a departmental issue.
SO A is too big to tackle all at ...   SO A is too big to tackle all at ...   SO A is too big to tackle all at ...   SO A is too big to tackle all at ...
See all stories on this topic          See all stories on this topic          See all stories on this topic          See all stories on this topic
Java Feature — T he Holy Grail         Java Feature — T he Holy Grail         Java Feature — T he Holy Grail         Java Feature — T he Holy Grail
of Database Independence               of Database Independence               of Database Independence               of Database Independence




Business Case                          Business Case                          Business Case                          Business Case
T his is a paaper that has been        T his is a paaper that has been        T his is a paaper that has been        T his is a paaper that has been
written to                             written to                             written to                             written to

demonstrate                            demonstrate                            demonstrate                            demonstrate
What a document looks like             What a document looks like             What a document looks like             What a document looks like
When it is written up and              When it is written up and              When it is written up and              When it is written up and
produced                               produced                               produced                               produced

On an etremely small type face,        On an etremely small type face,        On an etremely small type face,        On an etremely small type face,
but it will show people looking at     but it will show people looking at     but it will show people looking at     but it will show people looking at
this slide that it does represent a    this slide that it does represent a    this slide that it does represent a    this slide that it does represent a
document covered with text             document covered with text             document covered with text             document covered with text

T he structure of the document is      T he structure of the document is      T he structure of the document is      T he structure of the document is
not at all obvious but I may           not at all obvious but I may           not at all obvious but I may           not at all obvious but I may
become clearer                         become clearer                         become clearer                         become clearer
Google News Alert for:                 Google News Alert for:                 Google News Alert for:                 Google News Alert for:
'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'    'e nte rprise archite cture ','soa'
Putting the A into SOA is a vital      Putting the A into SOA is a vital      Putting the A into SOA is a vital      Putting the A into SOA is a vital
step                                   step                                   step                                   step
Computerworld New Zealand -            Computerworld New Zealand -            Computerworld New Zealand -            Computerworld New Zealand -
Auckland,New Zealand                   Auckland,New Zealand                   Auckland,New Zealand                   Auckland,New Zealand
Having (and following) an              Having (and following) an              Having (and following) an              Having (and following) an
e nte rprise architecture can also     e nte rprise architecture can also     e nte rprise architecture can also     e nte rprise architecture can also
avoid a classic mistake: treating      avoid a classic mistake: treating      avoid a classic mistake: treating      avoid a classic mistake: treating
SO A as a departmental issue.          SO A as a departmental issue.          SO A as a departmental issue.          SO A as a departmental issue.
SO A is too big to tackle all at ...   SO A is too big to tackle all at ...   SO A is too big to tackle all at ...   SO A is too big to tackle all at ...
See all stories on this topic          See all stories on this topic          See all stories on this topic          See all stories on this topic
Java Feature — T he Holy Grail         Java Feature — T he Holy Grail         Java Feature — T he Holy Grail         Java Feature — T he Holy Grail




                                                 NPP’s, Business Cases
of Database Independence               of Database Independence               of Database Independence               of Database Independence




                                                                                                                                                                                                         Analyse
                                                                                                                                                                          Why no business
                                                                                                                                                                            capability?


                                                                                                                                                            Why no data
                                                                                                                                                             involved?




                                                                                                                                                                                                    12
                                                                                                                                                                          Opportunity for service
                                                                                                                                                                                 reuse?
                                            Projects
                                             Project C

                                                  Project B

                                                     Project A




                                                              Re-use,
                                                              shared services,
                                                              patterns, templates


        ICT Investment
          Proposals
                                                                                           Implemented
New Policy
Proposals
                         Investments                                                         Solutions
Business
Cases
                          Mapping                                              Patterns,
                                                                              templates




                                       Gaps,
                                                               Capabilities
                                       overlaps



                                          Capability
                                         Assessments
Sample Budget Assessment
                                      Decision-making

Yesterday    Today       Tomorrow       Opportunity    Possibility


                                                        Strategy


                                        Architecture    Demand


                          Program         Portfolio
                         Management      Management



                           Project
            Operations   Management



 Review
                                                           Capability
                                                  Era
                              Yesterday          Today           Tomorrow
    Perspective                       Policy/Technology Continuum
      Policy Strategy          Safety Net        Participation      Attainment
        Policy Target          Symptoms            Barriers           Causes
        Policy Driver           Poverty           Economy           Well-being
     Customer Focus          Circumstance         Behaviour       Responsibility
    Delivery Output            Payments           Referrals        Pre-emptions
   Delivery Structure           Central             Local             Virtual
         Value Model          Value Chain        Value Shop       Value Network
Application Architecture       Procedural      Service Oriented    Event Driven
    Technology Focus            Database         Connectivity       Embedded
     Locus of Contact      Processing Agency   Provider Nodes       Individual
Delivery Provisioning         Assessment        Service Offer     Orchestration

                             Reactive             Proactive          Preventive
                          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.
                                            Services & Reuse

                            Government
                              Service




    Inbound         Assessment          Review         Outbound
    Services         Services           Services       Services


   Eg.                            Eg.               Eg.
   Registration                   Case Management   Notification
   Authentication                 Compliance        Payment
   Circumstances

 More                         More                              More
Generic                      Specific                          Generic
                Services & Reuse
Presentation                More
                           Flexible




Orchestration




Resources



                           More
                           Stable
1
        Safety-net                   Participation                                          Responsible
2                                                                                                         Straight-through   Event Automated
              No-one left out           No Wrong Door   One Stop Shop            Self Service
                                                                                                               Service           Service

3
     Intensive Service                    Assisted Service                   Self Service                      Event Service
4
    3rd
    Parties                       On Site                    On Phone                 On Line
                                                                                                                 Event Process
                                                                                                                 Management
5                                                                                                                 (back office)
Community
 Access                         Government Business Process Management
  Point


6
                                  Lead            Lead                                                          Org 1          Org n
                                                                 Agency C        Agency Z
                                 Agency A        Agency B
    Service
     Finder




7
                                                                        Employment
                                                            Health
                                                          International Travel
                                              Justice
                                                                        Education
                                                         Welfare
                                                               Security
•   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.
•   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.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:9/24/2012
language:English
pages:22