1. GEOSS ADC Architecture Workshop Break-out summaries: Initial Operating Capability (IOC) Doug Nebert U.S. Geological Survey ddnebert@usgs.gov February 5, 2008

2. GEOSS IOC Architecture: Input to AIPilot-II Core architecture refined by increasing collaboration with GEOSS SBAs –Work with GEO Committees, Communities of Practice and other relevant GEO Tasks. Increase commitment to Operational requirements to support persistence Clarify operational approach for core components: GEO Web Portal, GEOSS Clearinghouse & user help desk Architecture refinement and extension: –scenarios using an enterprise modeling approach; –workflow for observation processing and decision support, e.g., results of Fed Earth Observation (FedEO) pilot; –include observation/sensor nodes to support such use cases as inter-calibration

3. GEO Web Site Client Tier Business Process Tier Access Tier GEOSS Web Portal GEOSS Registries Services Components Standards GEONETCast Other Services Data Access Services Model Access Services Community Portals Decision-Support Applications Requirements Community Catalogues Portrayal Services Workflow Management Processing Services Other Services GEOSS Clearinghouse CSW/ISO23950 Get list Register CSW/SRU/UDDI Sensor Access Services IOC Architecture – Technology Viewpoint

4. IOC Issues – Going to the next level Systematic registration of Components and Services Support of registered standards by offerings Quality and availability of services Promoting the ability to integrate data and services towards additional SBA application domains Strengthening the use of the Web Portals to access and integrate all GEOSS resources Improving the interaction of the GEOSS Web Portals, Registries, and Clearinghouse

5. Systematic registration of Components and Services Request by ADC co-chairs on behalf of ADC to get the message out – message content, tools, assistance Tools: powerpoint walkthrough of registration, screen captures, tutorials, UIC and ADC assistance in getting the word out Develop small package to brief other committees Identify benefits of registration Identify how non-members (non-countries M&PO) organizations can participate, also commercial Identify what user types/requirements can be handled

6. Support of registered standards by offerings Clarify Component, Service and find out why incomplete registrations are taking place Increase awareness and understanding of service registration (process and benefits) for both standards-based and special arrangement cases Is there a possibility to have a read-only access license for GEO participants to ISO (for-fee) standards? Users may need to view a standard before it can be applied… National and Intl standard cross-walk or equivalency support in Standards reg?

7. Quality and availability of services Identify metrics of numbers and types of resources, users, applications for mid-term review (2009) Monitor queries, types of users, support feedback loops on core services Encourage a public service level declaration/intention (assertion) GEO- wide to improve quality of service What are the issues of liability (commitment) in meeting SLA targets? Consider having service checking and testing mechanism, who would evaluate QoS? Communities of Practice could evaluate services for fitness for use What would QoS values look like, how would it be organized? Track the operational/experimental nature (QoS) for services, including maintenance, lifecycle stage Some qualities are not easily measured (qualitative vs quantitative) Identify small set of properties on services that characterize QoS from service and consumer points of view Organizational commitment

8. Promoting data and services integration How to promote access to services to encourage their use in more complex service chains? Back the data content behind a service with a standard ontology (activities, processes, observables) re-use existing systems/ontologies Integrating local data into regional/global data: demonstrate how to engage local authorities to promote data/service integration – scaling data local/regional/global as similarly structured Can we promote templates to develop access to data and services? Integrate services into local solutions Involve different levels of data provider in the integration task Use registries to include more data schema/descriptions and compile best practices or as special arrangements as GEO-wide standards (global, national, regional) Develop better understanding of human interface to the invocation and presentation of interaction with Web Services Track and promote access Focus on decision support clients to use the Core infrastructure and standards to tailor access to GEOSS resources

9. Infrastructure maturity (registries, web portals, etc) Core services need to be reliable Quantify reliability of the core services.999 availability Define QoS assertions by the service operators, identify what level of commitment is required Performance, reliability, accuracy, failover, model for user loads – web portals, clearinghouse, registries

10. Messages for CFP What is the defined scope of the IOC? Who are the anticipated users (producers & users)? What are the next steps? Clarify/differentiate OGC role/scope within AIP Identify the foci of the upcoming CFP/AIP –Increase the role of the end-user/client/DSS –Improve the uptake of the core infrastructure –Operational end-user needs are met (real-world systems and solutions) –Carefully define the objectives of Phase 2 and service (core & offered) expectations