1. Enterprise Viewpoint Tim Mackey Web Systems Manager Geoscience Australia

2. Business is the showstopper Technical problems are easy  People, skills, time, resources Business processes are hard  High level scepticism re “technology driven” approach  We need an elevator pitch  Challenging established systems – destroying empires  Changing legal processes (eg data licensing)  Governance

3. The Problem Agency A installs technology X X only supports restricted data formats  Format directly reflects data model of stored data “Big Mining” wants the same data theme from Agency A and Agency B over the same locality This can currently only happen if:  Agency B also uses software X;  Agency B uses the same data model as Agency A, and;  These two dependencies will always remain

4. The solution Feature type catalogues  Community data models (eg Geochemistry XMML)  Mechanisms/tools with which to use the community data model Method of accessing these catalogues  SEEGRID roadmap All you need in your databases  Translation path from your organisation’s data model into the community data model

5. Multiple thematic data layers GetFeature request: Web Feature Service (WFS) gets operable feature data from multiple servers Cities Borders Elevation Each layer is data, not merely a view: Country is: _ Name: Italy _ Population: 57,500,000 _ Area: 301,325 sq km... Carl Reed - OGC

6. Business Drivers Reduce time to market Client always gets latest data Client goes to one place for data from multiple data sources  No need to know all of the different data sources’ locations, access methods, formats, etc. No need to manage other peoples’ data Save “shop” staff time

7. Geoparser Advancing Spatial Data Infrastructure Via Interoperable Web Services Reduce deployment costs by reusing information from other communitiesReduce deployment costs by reusing information from other communities Meet requirements for client access.Meet requirements for client access. Foundation for interoperable service networksFoundation for interoperable service networks Easier access to multiple online info sources and services Easier access to multiple online info sources and services Use and reuse different vendor solutions. Use and reuse different vendor solutions. Clearinghouse Geoparser Vendor Data Local Government National Government Other Collections Clearinghouse Whoville Cedar Lake Whoville Cedar Lake Buildings Roads Images Targets Boundaries... Catalog View Common interfaces enable interoperability Queries extract info from diverse sources Integrated View Gazetteer Coordinate Transform Web Mapping Server, Web Feature Server, Web Coverage Server Catalog Services Other Services Metadata Data Metadata Data Metadata Data Metadata Internet Geoparser Geocoder Carl Reed - OGC

8. Who is doing what? CSIRO  Information viewpoint PMD*CRC, Social Change Online  Technology, Engineering, Computational viewpoints Geoscience Australia  Enterprise viewpoint 3 Geological Surveys volunteered time/data  WA, SA, GA GGIPAC/CGGC  sponsor

9. External links Started the process and established relationships:  ASIBA IDP  ASDI  AEON  GEON  NERC Datagrid  IUGS CGI This project provides a mechanism to understand and share practice with other domains  Community of Practice

10. Publish OGC Web Services: Computational View Map Viewer Client WMS Discovery Client Coord. Transf. Service Coverage Portrayal Service Data Type Registry Data Instance Registry Service Type Registry Service Instance Registry Data Services Portrayal Services Registry Services Processing Services Application Clients Bind Find Archives WFS WCS Catalog Expl. Client Expl. Client Encodings GML XIMA SLD Service Capabilities Metadata SensorML Obs&Meas SCS Image Metadata GeocodingChaining Gazetteer

11. OGC Web Services: Computational View Map Viewer Client WMS Discovery Client Coverage Portrayal Service Data Type Registry Data Instance Registry Service Type Registry Service Instance Registry Data Services Portrayal Services Registry Services Application Clients Bind Find Archives WFS WCS Catalog Expl. Client Expl. Client Encodings GML XIMA SLD Service Capabilities Metadata SensorML Obs&Meas SCS ASIBA CSIRO/SEEGrid Publish QLD NRE WA DLI CANRI Image Metadata Coord. Transf. Service Processing Services GeocodingChaining Gazetteer pmd*CRC GA WA DLI DSTO SEE Grid MCA/ SEEGrid ASDD

12. Existing policy framework Managing IP  Acknowledgement of the data source at the destination Copyright and licensing  Data is freely available  We still need to know who is using it Business process  Workflow  Data management

13. Governance Feature type catalogues  Who manages the business process? Conformance  Who defines the standards? How are they changed? Repository management  Who is responsible? What are the rules? Community standards and support technologies Hosting of services and standards  What is the level of availability required?  Defining an SLA?

14. Phase 1 - Demonstration Governance  Common information model and sample processing chain  Vocabularies of data services published as network resources  Registries Responsibility  SEEGRID Roadmap project team

15. Phase 2 – Initial capability Governance  Registries established under a SLA  Registries managed according to ISO19135  Feature Type Catalogues for all supported domain models  Components conformant to a registered domain model OR  Publish a completely new domain model Responsibility  ???

16. Phase 3 - DataGrid Governance  Data repository established  Data repository management  Access, Authentication, Accounting frameworks  Formal arrangements with other data GRIDS Responsibility  GRID computing infrastructure services

17. Issues to discuss “Big Mining” is now reliant on external 3 rd parties for its information systems. How does it gain sufficient confidence in SEEGRID for that to happen?  Is an SLA sufficient? With whom? Who has governance responsibility for the various components after this demonstrator?  Registries  Feature Type Catalogues

18. More issues to discuss Rights management – how big an issue is it for your organisation? Acknowledgement of data source in derived products? Chaining services  how do we manage indemnity and liability?