1 / 12

Standardisation

Standardisation. Informal summary of ABS Perspective. Context. A comprehensive “whole of enterprise” business transformation program, named ABS 2017, was initiated a couple of years ago Aims for standards based modernisation Aims for “interoperability” leading to “economies of scale”

kale
Download Presentation

Standardisation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standardisation Informal summary of ABS Perspective

  2. Context • A comprehensive “whole of enterprise” business transformation program, named ABS 2017, was initiated a couple of years ago • Aims for standards based modernisation • Aims for “interoperability” leading to “economies of scale” • within the ABS • in partnership with other producers of official statistics • with vendors • Business role for standards championed by DG at the strategic level.

  3. Definition of “Standard” • Recognise need for scoping • Content : classifications, variables, questions… • Information Arch : GSIM, SDMX, DDI, *GSBPM* • Other : UML, BPMN, Applications Arch (eg SOA) • Haven’t had resources to undertake detailed foundational work on definitions and frameworks related to standards themselves • Now unnecessary – SoS has done the “heavy lifting” (Thanks!) • There don’t appear to be sound reasons why we should be different.

  4. Inventory • Have recognised value, but not built • ABS refers to those listed in NTTS paper • It is very welcome news there will be a more detailed common template for recording and registering content. • During a time of transition, particularly important, but difficult to know, currency of “other normative documents” • We have started doing some mapping of this against layers of architecture (business, information etc)

  5. Standardisation Process • SoS sets out a good high level standards lifecycle model. • ABS is very active in standards development under UNECE, DDI Alliance and (lesser) SDMX • Have bodies at two levels (technical and business strategy) to review case for adoption, guide implementation, input to development. • Adoption : How we will apply the standard, in conjunction with others, is critical • Beyond “yes, we’ll use it”, define role of the standard in our architecture. • SWOT for standards selection would be useful

  6. Business Architecture • A strong focus – but still initial phase – on business architecture • includes “to be” after transformation • reasons include those articulated in the NTTS paper • Top perspective similar, not the same, as SoS • Most/all top level divergence seems coincidental • Engagement on SoS top level (by whom?) beyond ESS soon so differences don’t become entrenched (eg in documentation, training) • It is elements less in scope for CSPA that are most different?

  7. Capability Architecture A business activity surrounded by all 6 capability elements gives the ABS the capability to perform that activity processes methods = systems people other resources standards frameworks

  8. Scenarios for integration • ABS mainly looking at the middle two

  9. SWOT • ABS decisions about areas for standardisation, form of standardisation and standards to choose have mainly been based on informed “gut feel” • Lots of questions about business case, added business value. • SWOT approach proposed by SoS appears to be a reasonable middle ground option. • A check list that “all the angles” have been considered, and context based weighting applied

  10. Consideration : Selection • Often relevant as an industry and agency to select a standard (eg not specifically statistical) and define in more detail how we are going to use it to support interoperability within our industry. • Not necessarily “black or white” on whether to adopt an existing standard, otherwise too much black and too many poor fits. • Can lead to sufficient interoperability within industry and improved interoperability (economies of scale) beyond. • Concept of “industry profile” • INSPIRE, FGDC, ANZLIC geospatial on ISO 19115 • W3C profile on ISO standard for representing time • Eg “DDI based implementation of GSIM” in future?

  11. Consideration - Perspective • Top down selection and adoption of standards is powerful • Should also consider mechanisms for looking sideways • What standards are used in related industries (eg research community, media content)? • Don’t necessarily want to inventory these comprehensively but have defined, strong connections with relevant standards experts and use them when questions arise. • Build on “map” in HLG Implementation Strategy for informing what communities are relevant for what aspect? • EU CROS mechanism provides a better starting point than we have in Australia, but we are growing links.

  12. Conclusion • I have discussed SoS outputs with a number of ABS colleagues already, including division head • Very impressed with outputs • A number of elements will be of direct value to the way we approach standardisation in the ABS. • Beyond ESS (eg New Zealand, Canada too) we are keen to see development of “industry standardisation” being a global undertaking. • recognise ESS has particular considerations and opportunities • Interested in contributing to upcoming ESSnet as observer if the ESSnet organisers were comfortable with that.

More Related