0 united states environmental protection agency office of environmental information enterprise...
TRANSCRIPT
1
United States Environmental Protection AgencyOffice of Environmental Information
Enterprise Architecture Program
Enterprise Architecture Working Group SessionJune 12, 2008
2
Agenda
9:00 a.m. Welcome & Introductions D. Prompovitch
9:05 a.m. EAWG Discussion Board E. Roberts
9:20 a.m. READ update R. Felver / J. Harman
9:35 a.m. 2008 Solution Architecture follow-up E. Pupo / J. Sullivan
11:00 a.m. Adjourn J. Sullivan
3
EAWG Discussion Board
An online discussion board has been established for EAWG members (see handout EAWG discussion board instructions)
To register, place a in the right column on today’s sign-in roster.
If you are not present at the meeting but would like to join, please email
Initial purpose:• To solicit feedback on 2008 architecture process, EA training, and EAWG
meetings.
• To evaluate whether it is useful to have an online discussion board, and if so, whether to use Oracle Collaborative Workspaces or try a different tool.
Intranet link (in slide show view)
4
Five forums established; more can be added later.
EAWG Discussion Board
5
READ Record Update
Statistics:• Initial deadline of April 30, 2008; review completed; new deadline of June 9, 2008• 105 records (all CPIC Majors and Lites)• 30 fields in record to be completed• 10 program offices
Changes this year:• Integrated EA READ data call with John Harman’s basic READ data call• 2006-2011 Strategic Plan added to READ• New fields required for EA compliance:
o Planned/Initial Operation and Termination Dates; Additional Details about your system; any Major Enhancements planned over the next year
Progress so far: 92% of all READ records updated
6
READ Record Update
Office # of Investments Current Completeness Level
OAR 17 99%
OARM 9 83%*
OCFO 2 70%*
OECA 6 83%
OEI 24 98%
OIG 4 100%
OPPTS 3 91%
ORD 8 100%
OSWER 15 100%
OW 17 92%
Current Level of READ Record Completeness
*Review of records incomplete due to data sensitivity issues
7
READ Record Update—Suggestions for Improvement?
Create ‘N/A’ fields in READ
Better alignment between READ data fields and what is required in the Exhibit 300s and CPIC Lite proposal forms
Any other suggestions?
8
Newly suggested steps for 2008
Conduct analysis
Solution Architecture – Progressing in Value
The 2008 solution architecture process is intended to provide increased business value by using solution information to result in business analysis.
Import information into ART
Update/submit investment/system
Information
Communicate gaps with stakeholders
Identify information gaps
Review information for completeness and
accuracy
Complete /submit investment/system
information
Import into ARTSubmit finalized information
Complete investment/system
information
Investment/System Owner
Investment/System Owner
EA Team
Investment/System Owner
EA Team EA Team Investment/System Owner
EA Team EA TeamEA Team
9
Conduct analysis
Solution Architecture – What is the expected timeframe?
Current resource allocation suggests analysis of solution information for business purposes is intended for completion within 2008.
Import information into ART
Update/submit investment/system
Information
Communicate gaps with stakeholders
Identify information gaps
Review information for completeness and
accuracy
Complete /submit investment/system
information
STATUS: Complete
STATUS: Pending
STATUS: Pending
STATUS: Pending
STATUS: Pending
STATUS: Pending
STATUS: Pending
EXPECTED:June
EXPECTED:Jul/Aug/Sep
EXPECTED:Sep/Oct
EXPECTED:June
EXPECTED:July/August
EXPECTED:Oct/Nov
Investment/System Owner
EA Team EA Team Investment/System Owner
EA Team EA TeamEA Team
10
Conduct analysis
Solution Architecture – What are the inputs and outputs?
Gap analysis, facilitated working sessions, and preparation of solution architecture data are key outputs for 2008.
Import information into ART
Update/submit investment/system
Information
Communicate gaps with stakeholders
Identify information gaps
Review information for completeness and
accuracy
Complete /submit investment/system
information
STATUS: Complete
STATUS: Pending
STATUS: Pending
STATUS: Pending
STATUS: Pending
STATUS: Pending
STATUS: Pending
EXPECTED:June
EXPECTED:Jul/Aug/Sep
EXPECTED:Sep/Oct
EXPECTED:June
EXPECTED:July/August
EXPECTED:Oct/Nov
Investment/System Owner
EA Team EA Team Investment/System Owner
EA Team EA TeamEA Team
Solution ArchitectureTemplates
Quality andContent Review
Architectural Analysis
Solution Architecture TemplateWorking Sessions
Updated Solution Architecture Template
Prepare Models,Views, and Reports
Analyze Models, Views, and Reports
11
Conduct analysis
Solution Architecture – What is the End Result?
Making the solution architecture process relevant to EA stakeholders is key to gaining further EA buy-in and ensuring a smooth process for years to come.
Import information into ART
Update/submit investment/system
Information
Communicate gaps with stakeholders
Identify information gaps
Review information for completeness and
accuracy
Complete /submit investment/system
information
Value Proposition:
Conducting analysis based off 2008 solution architectures provides stakeholders with relevant information that can be used to directly influence business-related activities such as planning, decision-making, portfolio management, and increased oversight and control
Stakeholder Benefits*:
Business Owner Can use analysis to determine how target solution milestones will affect business processes in multiple EPA program offices.
Investment/System/ Solution Owner
Can use analysis to determine if listed performance metrics are effective in gauging how well solution supports mission, customers, and processes
Architect Can use analysis to determine if solution architectures share similar data sources and information exchanges, allowing for the identification of reusable data services and shared data assets
Question: How can solution architecture information become relevant to EA stakeholders?Answer: By taking raw data of limited use (from solutions) and conducting analysis to turn data into valuable and relevant information for EA stakeholders.
*Note: stakeholder benefits are samples only
12
Contact Information
If you have any questions about the information presented today, please contact one of the following individuals
John SullivanEPA Chief Architect202.566.0328 (office)
Joanna HugneyPPC EA Program Manager
703.748.7094 (office)[email protected]
David PrompovitchEPA EA Team Lead202.564.0588 (office)