July 20, 2004 FGDC Coordination Meeting Summary

Host: Donald Draper Campbell, FCC


Ivan DeLoatch, FGDC
Alison Dishman, FGDC
Carol Brandt, USDOT/BTS
Rick Pearsall, USGS
Lesley Ogrosky, FGDC
Tricia Gibbons, LEAD Alliance
Bonnie Gallahan, FGDC/GOS
Anne O'Connor, Census
Shirley Hall, USDA/FSA
Tony LaVoi, DOC/NOAA
Leslie Weiner-Leandro, DHS/FEMA
Leslie Wollack, FGDC/GOS
Ingrid M. Milton, USDA/NRCS
Donna Scholz, FGDC/GOS
John Clark, GSA/OIS
Monica M. DeAngelo, FERC
Susan M. Hargrove, DOE
Alan R. Stevens, FGDC
Kathy Covert, FGDC
Bill Burgess, NSGIC
Brett Abrams, NARA
Jeff de La Beaujardiere, NASA
Rob Dollison, GOS
Julie Maitra, FGDC
Ralph Crawford, USFS
Wendy Blake Coleman, EPA
Lee R. Warren, NGA
Billy Tolar, USGS/National Atlas
Doug Nebert, FGDC
Betsy Kanalley, USFS
Mario Lopez-Gomez, DOJ/Civil Rights
Jon Sperling, HUD

On the Phone:
Barb White, FWS

Considering an Enterprise Architecture for the NSDI - Doug Nebert, FGDC

We need an NSDI Enterprise Architecture (EA) to agree on terminology across agencies and to facilitate communication between geospatial business professionals and IT CIO offices within agencies. An NSDI EA would improve communication between agencies and departments and would assist in sharing of common geospatial services across all levels of government, thereby strengthening service reliability. Constructing an EA for the NSDI would be a multi-agency enterprise. Partnerships between E-gov initiatives, DOI EGIM members, GEO partners, NASA, DHS, EPA, USDA, State government agencies and others could be used in this effort.

  • An Enterprise Architecture (EA) defines a framework for the current and future work activities and justifies the investment of an "enterprise".
  • A Business Reference Model (BRM) defines business processes in the EA.
  • A Technical Reference Model (TRM) describes information services that are needed to achieve the BRM.
  • A Data Reference Model (DRM) defines the data/information required by the BRM in the context of the TRM.

An EA can have different frameworks reflecting the varied views of the planner, owner, designer, builder, integrator and user. The EA becomes more complex, with more participants, as you move from ground-level workgroups all the way up to an entire community.

The phases to develop an NSDI EA:

  1. Establishing the objective and terminology.
  2. Developing the DRM and TRM.
  3. Validating the BRM, DRM, TRM via experiments and prototyping.

    Action: If you are interested in participating in this effort or for more information on building an NSDI EA, please contact Doug Nebert at 703.648.4151 or ddnebert@fgdc.gov.

Comments: EPA is currently building an EA and is reaching out to the States through an environmental exchange network and the CIOs from State Department of Natural Resources. FWS is working with EPA in this effort.

USDA and DHS are also developing their own EA with the goal to identify and defend investments by highlighting the services they provide to their consumers.

OMB will be interested in compliance with EA requirements.

Files: [PowerPoint 346KB]

Future Directions Action Plans - Tricia Gibbons, LEAD Alliance

Milo Robinson will serve as the Future Directions Project Manager.

Action: Please contact Milo (mrobinson@usgs.gov) if you would like to volunteer for one of the Future Directions Action Teams.

The Action Plans are posted at http://www.fgdc.gov/FutureDirections/action_plans/act_plans.html

GOS Fee For Service - Donna Scholz, FGDC/GOS

A model is being developed to allocate dollars from the various Federal agencies to maintain GOS. A FTE spreadsheet is being developed for FY06. A data producer might be charged differently than an agency that is solely a data user -- but criteria for high, medium and low users must be developed. The GOS efforts that Departments are undertaking internally should also be considered.

For more information please contact Donna Scholz at dscholz@fgdc.gov.

Next Coordination Group meeting:

September 21, 2003
USACE to host
(Due to the upcoming geospatial conferences and the Labor Day holiday we will not have an August meeting and our September meeting will be held later in the month than usual.)