PRIDE

Natural Resource Information Division

The PRIDE Project

I & M Data Managers Meeting

Las Vegas, April 2004

Doug Garnand, NRID

2Natural Resource Information Division

Overview of PRIDE

• What it is• Why are we doing it• History

• Enterprise Architecture• Draft Project plan• Your role

• Questions


Protecting

Resources through

Informed

Decisions and

Education


PRIDE in a Nutshell

• A project to define what information is needed for natural resource decision making, planning, and education


The Current PRIDE Project Team

• Gary Williams, I & M Branch Chief

• Marianne Tucker, Systems Mgmt Branch

• Doug Garnand, Systems Mgmt Branch

• Consultant, Commonthread Inc.


The Reasons for PRIDE

• Long Term Programmatic Goals from NPS-75 I & M Guideline (1992)

– Establish natural resource inventory and monitoring as a standard practice throughout the NP system which transcends traditional program, activity, and funding boundaries

– Inventory the natural resources and park ecosystems under NPS stewardship to determine their nature and status

– Monitor park ecosystems to better understand their dynamic nature and condition and to provide reference points for comparisons with other, altered environments

– Integrate natural resource inventory and monitoring information into NPS planning, management, and decision making

– Share NPS accomplishments and information with other natural resource organizations and form partnerships for attaining common goals and objectives


The Reasons for PRIDE

• Never a formal effort to:– Relate business requirements to information requirements– Examine needs at park, regional, and national levels

• From NPS CIO:– Superintendents report information systems aren’t giving

them the information they need

– There is a critical lack of information for top mgmt to make decisions


History of PRIDE

• Natural Resource Information Engineering Project planning meeting (NRPC, May 2000)

• Park Natural Resource Information Needs Workshop (Silver Creek, Sept 2000)

• Concept Paper: Business Requirements Assessment and Information Engineering for Natural Resource Stewardship and Protection by the NPS (Gary Williams, June 2002)

• Project Definition Workshop for Natural Resource Business Requirements and Information Needs Assessment (Denver, Sept 2002)


NR Business Requirements and Info Needs Assessment Project Definition Workshop

• Purpose: Develop a project plan– Info needs for decision making, planning, and

education– Park, regional, and national levels– Long-term protection of natural resources

• Outcomes:– PRIDE acronym created– Project plan and charter developed– Decision: move forward with project


PRIDE Gets Put on Hold

• NPS CIO had major concerns about PRIDE project– Felt it was an information systems project and

needed much more planning and documentation– Too expensive

• NRSS withdraws PRIDE from consideration for approval (June 2003)


External Influences

• OMB mandate for 3rd party NRSS evaluation– Are we doing the right things?– Are we doing them well?

• Federal Enterprise Architecture


Rethinking PRIDE

• What are we supposed to be doing• More of a management project than an

information systems project• Has Enterprise Architecture aspects but is not

a full-blown EA effort


What is Enterprise Architecture?



Enterprise Architecture “Definition”

EA, in essence, is just a more extensively documented business plan.

EA is a blueprint or modernization plan that enables the information technology of an organization to best support its missions and goals. The EA consists of models, diagrams and text that describe the business, performance goals, data, services, and technologies that form the framework for deploying information technology throughout the organization.


Building a House Analogy

• Use an architect to design a house• Homeowner has a desired house in mind• Ideas translated into plans/drawings

• Subcontractors need different levels of detail • All plans have to work/fit together• Homeowner drives the process




House Analogy Applied to Enterprise Architecture

• Enterprise = house– NPS, DOI, Federal Government

• Senior managers = homeowner• Models, diagrams of business, information,

technology = building blueprints– Different levels of detail– Plans have to fit/work together


Federal Enterprise Architecture

• Clinger-Cohen Act (1996) requires federal agencies to develop and maintain an EA


Business Reference Model (BRM)• Lines of Business• Agencies, Customers, Partners

Service Component Reference Model (SRM)• Capabilities and Functionality• Services and Access Channels

Technical Reference Model (TRM)• IT Services• Standards

Data Reference Model (DRM)• Business-focused data standardization • Cross-Agency Information exchanges

Bu

siness-D

riven A

pp

roach

Performance Reference Model (PRM)

• Government-wide Performance Measures & Outcomes• Line of Business-Specific Performance Measures & Outcomes

Federal Enterprise Architecture (FEA)C

om

po

nen

t-Based

Arch

itecture


DOI Enterprise Architecture

• Strategic: developing the DOI EA– Map to FEA Model

• Tactical: looking horizontally across DOI for opportunities to consolidate, eliminate redundancy

• For FY 04 working on the following business areas:– Recreation– Wildland Fire Management– Law Enforcement– Financial– Indian Trust


NPS Enterprise Architecture

• Waiting for DOI EA to become more mature• Going to work on 1 business area in FY 05


New Approach to PRIDE

• Add a goal clarification step- What are we supposed to be doing?

• Emphasize the high-level management aspects

• It is related to EA but is not a full EA effort• Use a less expensive approach


Steps Taken / Needed

• Got support of AD NRSS• Met with consultant (Commonthread Inc.)• Need to meet with NPS CIO


Overview of Major PRIDE Phases

I. ID comprehensive set of goals, get consensus on mission critical goals

III. ID business requirements necessary to accomplish goals

V. ID information necessary to support business requirements

VII. Gap analysis between information we have and what we need


Schedule for Phase I, Goals

• Review and summarize legislation and mgmt policies (May 2004)

• Refine Phase I project approach, develop project plan (June 2004)

• Workshop pilot (July 2004)• Hold workshop with NRSS and regional managers

(Sept 2004)


Do You Know of Other Summaries?

• NPS-77 NR Management Guidelines (1991)

• An Introduction to Selected Laws Important for Resources Management in the NPS (1994)

• Interim Technical Guidance on Assessing Impacts and Impairment to Natural Resources (2003)


Schedule for Phases II - IV

• Specifics not decided yet• Tentative completion in FY 05


Role of I&M Data Managers

• Help us to build from the good work you have already accomplished– Business requirements phase– Information requirements phase– Gap analysis

• Provide us with feedback


Summary of PRIDE

• A project to define what information is needed for natural resource decision making, planning, and education– It will utilize “blueprints” of goals and business

requirements

• For all NR programs, not just I & M• For park, regional, and WASO levels• A supplement/extension of what the Networks

have accomplished



Enterprise Architecture References

“Developing an Enterprise Architecture”, Paul Harmon, Jan 2003, white paper on popkin.com. A very readable introduction.

“A Practical Guide to Federal Enterprise Architecture”, CIO Council ver 1.0, Feb 2001, search on Google. Prior to new FEA Model but issues covered still pertinent.

http://www.zifa.com

http://www.popkin.com

http://www.doi.gov/ocio/architecture/index.html

http://www.feapmo.gov/

http://www.popkin.com/

http://www.doi.gov/ocio/architecture/index.html

http://www.feapmo.gov/

PRIDE

Business

information requirements

monitoring information

information systems

natural resource inventory

natural resource stewardship

natural resource organizations

critical lack of information

nps planning