NOAA CIO Council Informational Briefing Enterprise Architecture Committee

1
NOAA CIO CouncilInformational BriefingEnterprise
Architecture Committee

• David Layton, Acting Chair
• NOAA Enterprise Architecture Committee
• November 28, 2006

2
Outline

• Purpose
• Background Discussion
• Coordination Views
• Status / Summary

3
Purpose

• Information Brief
• Status of annual
• NOAA EA Update
• OMB Architecture Assessment
• Committee plans for FY-07
• Discussion of NOAA EA principles
• Discussion of next steps guidance for the
  future

4
Background DiscussionEA Update Drivers

• Annual NOAA EA Update
• Required by OMB
• Must be completed prior to start of the next IT
  Budget Cycle
• Intent is for Architecture to precede guide IT
  Capital Planning
• Due Jan 12, 2007

• EA Revisions Needed to Reflect
• Changes to the Target Architecture to meet
• New mission requirements from Strategic Planning
  / PPBES
• Federal mandates such as IPV6, eGov, FTF, etc.
• Refresh As-Is Architecture baseline
• Capture latest transition sequence plans

5
Background DiscussionGetting to Green

• Annual OMB EA Assessment
• Assessment performed at the DoC Level (not NOAA
  specific)
• DoC EA submission is due to OMB Feb 28, with
  assessment taking place in March/April timeframe
• Rated on a maturity scale of 1-5, similar to CMM
  model
• Evaluated on three dimensions

• Completeness, Usage Results
• Rated Green in FY06 assessment, but same scores
  equal Red with FY07 criteria

• FY07 Green gt4 on Completion and gt3 on Both
  Usage Results

Impact for NOAA Exhibit 300 EA scores can be
rated no higher than the Departments overall EA
rating in the OMB Assessment. Red or Yellow on
EA jeopardizes ALL exhibit 300s.
6
Background Discussion NOAA Architecture Model
The NOAA EA is shifting from a view based
architectural model to the FEA reference model
paradigm
7
Background DiscussionEA Update Strategy

• Strategy for NOAA EA update EA Assessment
  preparations
• Divide conquer
• NOAA EA Organized by Mission/Goals
• Mission/goal sections allocated to LO reps based
  on affinity access to relevant business leads
  and info
• e.g., NMFS rep does Ecosystems, NWS rep does
  Weather Water
• Collaboration on Mn relationships between IT
  investments Goals
• Leverage existing information processes
• PPBES documentation for business performance
  architecture
• Exhibit 300s for target performance, service
  technical components and transition planning
• GEO-IDE / DMIT for portions of the target data
  architecture
• etc.
• Prioritize focus on
• Known OMB focus areas for FY07 (e.g., transition
  planning)
• Criteria and artifacts for getting to Level 4 in
  EA Completeness

8
Background DiscussionFY-07 Committee Plans

• Committee Plans for FY-07
• Draft AOP Milestones for EA
• Publish revised NOAA EA Q2
• Define repeatable EA process lifecycle Q3
• Develop, vet publish NOAA TRM Q4
• Other priorities
• Revisit Committee TOR recommend changes
• Revise and vet EA principles
• Outreach to Goal Team leads
• Develop recommendations strategy to address EA
  staffing gaps
• Based on EA process requirements agency
  benchmarking

Primary FY07 Goal Make NOAA EA Practical
Relevant
9
Recurring Deliverables
10
Coordination

• Goal Teams / Program Leads
• Work closely with Program Leads to identify
  requirements ensure they are captured in the
  target architecture
• Line Offices
• Commitment of resources
• Championing of EA principles in local IT
  initiatives

• Other CIO Council Committees
• NAC (IPv6 planning, telecom standards)
• IT Security (Security Privacy Profile)
• IT Services Planning
• Other NOAA-wide initiatives
• GEO-IDE (SOA strategy)
• DMIT DMAC (data architecture)
• IOOS
• NOSA

• EA Committee Strategy
• Outsource EA domains where possible
• Focus on framework analysis to integrate domain
  views
• Cross-pollinate teams through formal liaisons

11
Status

• Interim NOAA EA deliverable provided to DOC Nov
  15
• Formal feedback on interim due Dec 15
• Revised NOAA EA Self-Assessment due to DoC Jan
  12
• Informational brief to CIO council prior to
  submission
• NOSA Segment Architecture being packaged
  separately
• Due to DoC in early-to-mid February
• Informational brief to CIO council prior to
  submission
• DoC Architecture (including NOSA segment
  architecture) due to OMB Feb 28
• OMB EA Assessment results typically released in
  April timeframe

12
The Architecture Elephant

• The gap between EA requirements our capacity to
  keep pace is widening
• OMB is raising the bar each year, FY08 will be
  no different
• Our capacity (i.e., resources) to respond has
  remained constant at best
• NOAA EA is currently in an answer the OMB mail
  mode
• Requires a heroic effort each year
• Not sustainable in FY08
• OMB specifically looks for evidence of real EA
  usage results
• Little local ROI, except maintenance of Green
  status for exhibit 300s
• Need to transition the NOAA EA to a practical,
  engaged relevant IT planning exercise
• Requires substantial LOE, but returns value to
  local IT planning decisions
• Automatically answers the OMB mail as a by-product

13
The Elephant Continued

• Making the transition requires rethinking our
  current approach
• Need to revisit validate the EA Committee TOR
• Consider repositioning the Committee to serve as
  a steering group
• Current model of using LO Committee reps to do
  the heavy lifting of EA is not sustainable
• Significant time commitment
• Competing demands from real job often take
  precedence over EA
• Arguably not consistent with the TOR
• Beyond the EA Committee
• Need to validate EA staffing requirement
  acquire resources
• Requirements should be driven by
• New EA lifecycle process
• Benchmarking against successful EA programs
• Adequate staffing is a Critical Success Factor!

14
NOAA Architecture Principles

• Example NOAA EA Principles
• Global principles
• IT decisions driven by total business worth to
  NOAA
• Use vendor neutral standards defacto industry
  standards
• Optimize business processes before acquiring or
  developing solutions
• Data principles
• Data is a corporate resource
• Data will be entered and captured only once
• Data will be kept separate from applications
• Application principles
• User requirements drive application development
• COTS/GOTS are preferred over home-grown solutions
• Use proven software engineering methodologies
• Technology principles
• Technologies will be chosen to enhance mission
  capabilities, improve customer service, support
  scalability, portability, operability,
  compatibility evolutionary changes
• Emerging technologies will be evaluated in pilot
  projects

15
What Do We Need From You?

• Guidance on Architecture Objectives
• Do we just Meet the Mail or
• Re-invent the NOAA EA as a relevant value-added
  process?
• Continued dialog guidance on EA principles
• Review and approval of approach
• Commitment of resources