Evaluación de la aptitud laboral a partir de las ofertas de empleo

As concluded by COOP,283 regional observing systems are critical building blocks of coastal

GOOS for both the GCN and regional observing systems that are explicitly designed to meet national and regional needs. Successful global evolution of the GCN depends on the development of national and regional observing systems that contribute to and benefit from the GCN and are interoperable in terms of the exchange of data and information on the states of their coastal ecosystems. National and regional bodies provide the most effective venues for (1) identifying user groups, (2) specifying data and information requirements that meet their particular needs for data and information on coastal and marine ecosystems, (3) assessing the current state of existing observing systems, (4) implementing an integrated system of systems, (5) refining data-products over time based on user feedback, new knowledge and advances in technology, and (6) reporting on and assessing the value and impact of observing systems for ecosystem-based management in the national and regional setting. Thus, decisions concerning

exactly what to measure, the time-space scales of measurement, and the mix of observing techniques are best made by stakeholders in the nations and regions affected.

RCOOSs are in various stages of development globally in terms of their readiness level, regional coverage and scope (number of phenomena of interest addressed). As articulated in “An Integrated Framework for Sustained Ocean Observing”, readiness levels fall into one of 3

categories: concept, pilot and mature.284 The concept phase includes research projects where

ideas are articulated, tested and peer reviewed. The pilot phase includes pilot projects where aspects of the system are tested and made ready for implementation as a mature contribution to GOOS. At maturity, the new capability becomes a sustained contribution to GOOS. For most of the developing world and emerging economies, sustained ocean observing is in the concept phase at best. This creates an enormous challenge to global implementation given that the majority of sentinel and reference sites lie in their EEZs and territorial waters (compare Figure 2 with Figures in sections 5.4.1 and 5.4.2). Among the more mature regional systems that can be used as models for design and implementation of RCOOSs are observing systems for the Baltic

Sea,285 the Mediterranean Sea,286 and coastal waters of Australia287 and the United States.288

5.6.2 Procedures for Design, Implementation and Evolution

Procedures for developing an RCOOS must enable the evolution of ocean observing systems that are interoperable on a global scale and, by definition, complex. This is a process driven by both the users and providers of data and services, i.e., the national and regional stakeholders. Users (decision makers from private and public sectors and scientists) must be at the table to specify their data and information needs. Data providers (from both operational and research communities) must be at the table to establish what is doable now and what the priorities for research and pilot projects should be to improve capacity to provide needed data and information to support timely decisions. The iterative cycle of steps to achieve this goal (Figure 25) is based

on a systems engineering approach289 and on “best practices” learned from implementing

regional systems that are most mature. The procedure takes into account the need to design, implement and evolve systems over time as scientific understanding of relationships between pressures, states and impacts improves; capacity increases (from interoperability among nations and regions to infrastructure readiness and modeling capabilities); more stakeholders become involved; and priorities change.

(1) Establish a multi-sector, stakeholder forum (Community of Practice290) to facilitate sustained and constructive dialogue among stakeholders to achieve consensus on priority phenomena of interest (PoIs), ecosystems to target, the need for an integrated and sustained ocean observing system, and a governance structure that oversees and manages the life cycle. Stakeholders include data providers, service providers, and users from government agencies, industries, non- governmental conservation groups, and academia (researchers and educators). Members of the forum should hold positions at the appropriate levels in institutional bureaucracies in terms of their technical expertise as a data and service providers, their knowledge of the local and regional ecosystems, the data and information requirements of the user groups they represent, and/or their ability to provide or attract the necessary funding.

As a first step, review the end-to-end systems identified in Chapter 3, determine which one are appropriate, and develop new ones as needed. This is an important step as it will guide the first iteration of the cycle and begin to achieve stakeholder “buy-in” and ownership. It will also be challenging as stakeholders will differ in their views on priority ecosystems and the goods and services they provide. Keeping in mind that developing an integrated observing system will be a stepwise, iterative process, this partnering and “scoping” stage must be consultative through directed meetings, workshops and dialogues that must be sustained to establish common ground throughout each iteration of the life cycle.

(2) Once the target ecosystems have been identified and priority PoIs agreed to, determine objectives of the observing system and identify priority pressures, states and impacts to be monitored and modeled. Objectives are guided by data, products and services specified by the users and informed by maps of the region (dominant features such as coral reefs, mangrove forests, water masses, coastal upwelling, fronts, seamounts, and submarine canyons; surface chlorophyll concentrations; spawning, nursery and feeding grounds of exploitable fish populations); an inventory of ecosystem goods and services currently used (fishing grounds, aquaculture sites, point source discharges, shipping lanes, recreational areas, etc.); and maps of land-cover and use in catchment basins draining into coastal ecosystems. These provide a framework for specifying data and information needed for IEAs and marine spatial planning. This stage concludes with the signing of a Memorandum of Agreement (MOA) by the stakeholders defining user expectations in terms of the provision of data and information and the roles and responsibilities of all stakeholders in the design, implementation, sustained operation, capacity building and funding of the observing system; and service level agreements that ensure

the provision of the required data and information.291 MOAs and service level agreements should

be “living” documents in that they are revised and updated with each iteration of the life cycle. Outcomes include an initial set of partners with well defined roles and objectives, a common language, agreed upon priorities, an inventory of current capacity, an empowered user community, and commitments by data and service providers to follow through on each stage of the life cycle.

Figure 25. Bottom-up, sustained and iterative life cycle for designing, implementing, evaluating, and improving an RCOOS over time.

(3) Given the results of stages (1) and (2), requirements for the sustained provision of data and information can now be determined, i.e., requirements for models, data management and observations. Requirements for observations should be guided by data requirements for

models292 and include the variables to be observed,293 time and space scales of resolution,

precision and accuracy, data delivery times (real time telemetry or delayed mode; if delayed mode, the acceptable lag time between in situ changes and their detection), platforms and sensors (remote sensing and in situ measurements) to be used, and locations to be sampled for in situ measurements.

In addition to observations of ecosystems, requirements for observations of external pressures on ecosystems and impacts of changes in ecosystems states must be determined. This should be done in the context of GEOSS since pressures occur on larger scales than targeted ecosystems within the region, and it would be prudent to engage representatives from the operators of adjacent RCOOS and basin scale observing systems. Observing system requirements set forth the sections above may be used to help guide this stage of the process.

(4) Given, objectives, priorities, and requirements, design the initial SoS and prepare a phased implementation plan (with milestones and cost estimates) with existing programs as the building blocks. The implementation plan should include procedures for coordinating and collaborating among programs; procedures for establishing common standards and protocols for measurements, data transmission, DMAC and modeling; and a business plan for acquiring and allocating the resources needed for integration and sustained operations of the SoS.

This is where what is “doable” in terms of existing resources and capabilities comes into play. On the technical front, existing observing, data management and modeling capabilities must be integrated vertically within participating organizations and horizontally among them. On the administrative front, the SoS life cycle must be managed in such a way that integration is achieved without compromising the ability of existing systems to perform their original missions and functions while enabling interoperability among them. Thus, establishing a hierarchical governance structure that harmonizes top-down (e.g., an Executive Council) bottom-up (Stakeholder Forum) responsibilities and authority is critical to successful integration of existing capabilities and implementation of the life cycle.

(5) All data providers (observations, models and data archives) collaborate to initiate phased implementation of the plans formulated in (4). Since data management and communications (section 5.4) are critical to linking observations and models and to the development of an integrated system, establishing this link in the observations to products chain should be the highest initial priority. Administratively and technically, this stage will be the most demanding in terms of the coordination, collaboration and training needed to make the implementation plan a reality.

(6) Sustained evolution of an RCOOS requires a systematic and rigorous process for periodic performance evaluations that ensure adherence to GOOS design principles. Performance metrics fall into two broad categories: (i) system performance and (ii) user satisfaction. System performance includes measures of data quality, continuity of data streams, data flow from measurements to models, model skill, and the diversity of user groups. User satisfaction is measured in terms of user “pull” (demand) and the timely provision of data and information that enable timely and informed assessments and decisions. Data providers, users of RCOOS data and information (clients), and funding bodies must be involved in specifying performance criteria. Where possible, existing national and international measures should be adopted to assess individual components of the system (e.g., Box6) and the achievement of objectives (e.g., long- term predictions of sea level rise) and societal goals.

(7) A gap analysis (assess current technical expertise and infrastructure assets for end-to-end systems, management capabilities and licenses against the requirements and objectives) is performed to set the stage for recommendations to the Stakeholder Forum on the way forward in terms improving performance to provide the data and information needed to achieve the objectives and inform ecosystem-based approaches to managing anthropogenic pressures and adapting to the impacts of climate change.

Ultimately the system must be cost-effective and designed to evolve over time as capacity is built, stakeholder numbers increase, new knowledge and technologies become available, and priorities for observing system data and information change or expand. Thus, periodic assessment by the stakeholders must result in satisfied users and the sustained evolution of more effective infrastructure and efficient operations from observation and data management to models and services.