NOAA Observing System Architecture
This article may meet Wikipedia's criteria for speedy deletion as a very short article lacking sufficient context to identify the subject of the article. See CSD A1.
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this article has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by Dmfroehlich (contribs | logs) at 16:51, 29 June 2010 (UTC) (15 years ago) |
About NOSA
- NOAA Administrator's Direction
- During 2002 Vice Admiral Conrad C. Lautenbacher, Jr., USN (Ret.) called for a fundamental review of NOAA's strengths and opportunities for improvement. A Program Review Team reviewed and debated issues and developed suggestions for building a better NOAA. These suggestions led to 68 specific recommendations. Recommendation 32 addressed centrally planning and integrating NOAA observing systems and indicated a clear need for a NOAA-wide observing system architecture. The NOAA Administrator responded:I concur with the PRT recommendation that NOAA centrally plan and integrate all observing systems. I will assign this responsibility to a matrix management team, with NESDIS providing the program manager. I do not currently endorse the PRT recommendation to assign acquisition authority for all observing systems to NESDIS. NESDIS should lead a cross-cut team to develop an observational architecture commencing immediately. This should capitalize on on-going efforts (e.g., coastal observations). This architecture should capture the state today as well as the future state (e.g., 10 to 20 years). With this architecture, NOAA would be able to assess current capabilities and identify short-term actions. A cross-cutting team led by NESDIS should conduct a systemic review of all other observing systems. The following factors should be considered for observing systems to determine the desirability of consolidating them:
- The required characteristics of the system (i.e., reliability, performance, maintainability)
- The number of and types of users of the system
- The estimated value of the capital asset and its recurring maintenance cost
- During 2002 Vice Admiral Conrad C. Lautenbacher, Jr., USN (Ret.) called for a fundamental review of NOAA's strengths and opportunities for improvement. A Program Review Team reviewed and debated issues and developed suggestions for building a better NOAA. These suggestions led to 68 specific recommendations. Recommendation 32 addressed centrally planning and integrating NOAA observing systems and indicated a clear need for a NOAA-wide observing system architecture. The NOAA Administrator responded:I concur with the PRT recommendation that NOAA centrally plan and integrate all observing systems. I will assign this responsibility to a matrix management team, with NESDIS providing the program manager. I do not currently endorse the PRT recommendation to assign acquisition authority for all observing systems to NESDIS. NESDIS should lead a cross-cut team to develop an observational architecture commencing immediately. This should capitalize on on-going efforts (e.g., coastal observations). This architecture should capture the state today as well as the future state (e.g., 10 to 20 years). With this architecture, NOAA would be able to assess current capabilities and identify short-term actions. A cross-cutting team led by NESDIS should conduct a systemic review of all other observing systems. The following factors should be considered for observing systems to determine the desirability of consolidating them:
- NOAA's Response
- NOAA can manage its observation system more efficiently and effectively with an architecture that defines a consistent set of principles, policies, and standards. The NOAA Observing System Architecture (NOSA) Action Group, directed by the NOSA Senior Steering Group, was established to develop an observational architecture that helps NOAA:
- design observing systems that support NOAA's mission and provide maximum value,
- avoid duplication of existing systems, and
- operate efficiently and in a cost-effective manner.
- NOSA includes:
- NOAA's observing systems (and others) required to support NOAA's mission,
- The relationship among observing systems including how they contribute to support NOAA's mission and associated observing requirements, and
- the guidelines governing the design of a target architecture and the evolution toward this target architecture
- NOAA can manage its observation system more efficiently and effectively with an architecture that defines a consistent set of principles, policies, and standards. The NOAA Observing System Architecture (NOSA) Action Group, directed by the NOSA Senior Steering Group, was established to develop an observational architecture that helps NOAA: