One NOAA Success Story

1
One NOAA Success Story

• Effecting Collaborative Change for the NOAA Web
  Presence

Warrenton, Virginia August 23, 2005
Presented by Allison Soussi-Tanani for the NOAA
Mid-Level Retreat
2
Change is good

• Problems
• Headquarters-centric OAR IT organization
• Disjointed and unorganized Web presence
• Little to no focus on external Web presence
• No coordination to or between field offices

• Improvements
• In 1998, the first CIO was recruited - Nancy
  Huang
• Focus on IT activities for the Web
• Asked What do you want to do?

3
The OAR WebShop was born

• Initial Goals
• Improve communications
• Share skills
• Meet national counterparts

• Long-term outcomes
• Increased efficiencies from shared concepts
• Targeted training for broad Web topics
• Increased engagement from previously disjointed
  group

4
The word gets out

• NOAA-wide participation begins
• Subject matter experts invited to speak
• NOAA spouses invited to attend
• In 2003, the program went NOAA-wide
• NOAA-wide planning committee
• Formal call for papers
• Other agencies invited to speak
• Exhibit hall for Web-related products and
  services
• In 2004, the WebShop moved to the next level
• R E S U L T S

5
The CIOs Get Involved

• WebShop Program Changes
• Organized program around 6 themes
• Web Content Management - Web Security
• Web Consolidation - Use of GIS Technology
• Web Tools, Techniques Talent - Web Policies
  Standards
• Added facilitated sessions resulting in 275
  recommendations spanning all categories

6
Summary of WebShop Recommendations

• Support a NOAA Web team that reports to the CIO
  Council and addresses Web policy, standards,
  collaboration consolidation
• Create a forum for sharing information on use
  and implementation of various Web standards
• Increase training and awareness of Web security
• Establish a mechanism for communicating policy,
  standards best practices for various Web
  activities
• Support a NOAA-wide content management
  initiative to develop and deploy a NOAA
  intranet

7
Then what?

• October 2004, NOAA Web Committee established to
  address recommendations
• December 2004, NOAA SES Retreat NOAA Web on
  the agenda
• March 2005, NOAA Web Committee re-chartered to
  include oversight and improvement of the NOAA
  Web Presence
• Representation from across NOAA for Steering
  Committee, Working Groups and Task Teams (HQ and
  field)
• Effecting positive change to NOAAs vast Web
  offerings

8
Understanding the NOAA Web Presence

• 05 Inventory finds 500 web sites on 300
  servers amounting to millions of pages in the
  noaa.gov domain
• Structured primarily through organizational lines
• Maintained by Webmasters through the IT chain
  of command
• No central direction for Web projects or services
• Little coordination for content on high-level
  sites
• Stale content

Google search on .noaa.gov returned 15.4
million pages 06/29/05
9
The Up Side

• Vast offerings 500 web sites amounting to
  millions of pages in the noaa.gov domain
• The noaa.gov domain is consistently rated at or
  near the top of the Neilsen Net Ratings for
  Government Sites
• Great diversity creativity in NOAA programs
  translates to sites and pages
• Reaching a variety of audiences effectively
• Identified Web Community (WebShop Conferences)
• Leadership committed to making a change
• Inline with other Federal Web efforts

Google search on .noaa.gov returned 15.4
million pages 06/29/05
10
NOAA Web Objectives

• Clear NOAA branding for all sites pages
• Unified view of NOAA data and information
  independent of business lines - MyNOAA -
  internal /external sites
• Improved content sharing across NOAA lines of
  business internal / external sites
• Enhanced awareness of NOAA information
  services by all stakeholders
• Improved access to data sets by specific audiences

11
Project Milestones
12
Create a NOAA Intranet

• Objectives
• Unity of Vision single, unified vision to all
  NOAA employees
• Unity of Access organize and simplify access to
  internal NOAA information currently aggregated
  across many locations
• Rapid ROI maximize time-to-value using a phased
  approach to deliver immediate and visible results
• Concept
• Single most important communication tool to and
  among employees
• Useful, organized, current, user friendly
• Vision
• Phased approach
• Focus on high priority content relevant to
  majority of employees
• Integration of key internal applications,
  collaboration features and line office content
• Knowledge management and support for external
  partners

13
Create a NOAA Intranet inside.noaa.gov
14
Create a Web Resources Site

• One-stop shopping for policy guidance
• Single voice for Web community
• Reduces resources dedicated to Web researching
  solutions

15
Establish a Web Governance Structure

• Web Governance is the structure of people,
  positions, authorities, roles, responsibilities,
  relationships, and rules involved in managing an
  agencys Web site.
• Serves as a Web communications map within the
  organization
• Organizational Effectiveness
• Align with federal contract recruitment process
  (PDs, SOWs)
• Create e-learning modules for each level
• Create NOAA Certification process to ensure
  ongoing effectiveness compliance (tied to
  e-Learning)

16
Proposed Web Governance Structure
Vision

Vision Planning

Planning Oversight


Oversight
Advisory

Advisory
Implementation Implementation
Application Application
Development

Development
17
Interim Web Governance Structure
Authority

Authority Corporate

CorporateSupport

Support
Vision, Planning,
Vision,
Planning Oversight Advisory
Oversight
Advisory
Implementation Implementation
Application Application
Development

Development
18
Whats next
gtgt

• Begin work on OneNOAA Concept site
• NOAA Storm Page NWS leading with NOAA-wide
  input
• Redesign of noaa.gov high-level NOAA sites
• Define business model for content contribution
• Create standards for common page elements
• Implement an enterprise search solution
• Continue talking to other agencies and
  organizations about their quest to become one
  continually apply lessons learned
• Establish a baseline for content technology and
  Define target information infrastructure
  architecture
• Communicate internally and externally to ensure
  we are meeting customer expectations

19
(No Transcript)
20
(No Transcript)