V1, 7/18/05 5 progress and successes can be measured and documented on an annual basis. It will also have information performance goals (how well does the new information satisfy the objectives of the research user community, the “client” agency (government) goals as well as the private sector user community). It needs to be a requirements-driven system, with specific sets of technology as well as “development” (societal) requirements, ConOPS and with specific design plans and plans for transitioning to operations. See response below · There needs to be throughout this program a rigorous process or approach–the systems engineering approach, which allows for rigor, accountability (not fiscal) and demonstrable design and build targets.   A recurring comment from the evaluators is the need for a systems engineering approach within SEACOOS as a methodology for developing a rigorous and defensible design and building plan for a regional COOS.  We have begun to investigate how this might be implemented and appreciate the suggestions about how we can cast our existing effort within the context of a systems engineering framework (in particular the discussion under Federal Partners about NASA’s methods).  This general recommendation is perhaps the most relevant to our program and will be carefully considered.  Because a number of the general recommendations (development of performance metrics, enumeration of user needs, credible cost estimates) can be captured within systems engineering development we will make a sustained effort to pursue this approach over the next few years. We also are only now in a position to begin implementing such a structure. Our view is that the COOS community is currently learning how best to design an RCOOS.  SEACOOS has many elements of an RCOOS, e.g. multiple platforms and measurement types that are being aggregated on a broad regional scale.   However, there are additional components needed, as envisioned by OceanUS, yet to be identified by regional stakeholders through the RA.  Our research is paving the way for defining how to design an RCOOS that is based on sound science and incorporates the capacity to serve a broad user community.  While we agree with the need for performance metrics, specific design plans, and plans for transitioning to operations, these concepts are still being developed.  Too much early emphasis on metrics could constrain the design and reduce ultimate efficiency and performance.  We need well thought out and articulated design criteria with metrics gauged on how well we follow these designs.  Our current status, after two and a half years of initial research, allows us to begin this process in earnest. · At present, this is an observing system configured for the answering the pressing needs of one user community- the research community.  It must be clear that the configuration of this system has been optimized to meet the needs of the user