Of all the Departments within the Federal government, the
Department of the Interior is arguably the one most closely tied to the land.
Most of the resources that the department is chartered with managing and
protecting are geographic in nature (e.g., National Parks, Mineral
Resources). Within the Information
Technology portfolio of services, Geospatial technologies, also, are the most
focused upon the land.
The heart of Geospatial technologies is concerned with
geographically referenced data and identifying and analyzing spatially defined
relationships that are associated with that data. Specifically, the data has either an explicit
geographic reference, such as latitude and longitude coordinates, or an
implicit reference such as an address, postal code, forest stand identifier, or
road name. From the creation of maps to
the analysis of potential flooding from a hurricane, geospatial information is
used for many and various purposes; both within Interior as well as by our many
outside partners (e.g., other Federal agencies, State and Tribal Governments
and the public at large).
But Geospatial technologies are much more than making
maps. It allows users to access,
examine, and analyze geographically referenced information and identify
spatially-defined relationships.
Traditional information technology or manual methods of mapping and data
analysis are severely limited when compared to Geospatial technologies. Simply put, Geospatial technologies extend
our reach and our ability to use complex information about the land and its
resources to simplify those complexities via Geospatial models and the visual
representation of the natural systems that the data represents. Geospatial
technology software has the ability not only to store graphic representations
of map features but also to access diverse types of data and records that have
a geographic component.
The focus of the Interior Enterprise Architecture is on
providing guidance for IT issues and initiatives that are Interior-wide or
multi-bureau in scope. The Geospatial technologies architecture defines the
standards, technologies and guidelines that relate to the use and sharing of
data that can be referenced geographically.
It includes any mapping activities such as geographic information
systems (GIS), global positioning systems (GPS), aerial photography, survey
data, remote sensing & imaging (e.g., satellite data), planetary GIS,
spatial modeling, visualization, Geospatial mapping products of Computer Aided
Drafting/Design (CAD), and “any data tied to a location”.
If used correctly, the Interior Enterprise Architecture will
act as a catalyst for those looking to capitalize on its contents and better
understand the full meaning of its guidance.
This understanding will permit IT personnel to better engage the non-IT
organization in discussions around tradeoffs and priorities within the proper
governance structure (e.g., Management Initiatives Team (MIT), Information
Technology Management Council (ITMC)). The Interior Enterprise Architecture is
not intended to be the “last word” (e.g., some automated checklist for product
selection). It is intended to be one of
the “first words” to assure that Interior’s mission priorities and its IT
priorities remain closely aligned.
Because Interior is incorporating the OMB’s Federal
Enterprise Architecture (FEA) models, the technical guidance provided by the
subject area experts within a domain spans both the Service Component Reference
Model (SRM) as well as the Technical Reference Model (TRM). For the Geospatial
domain, the SRM elements are as follows:
Service
Domain(s): The Business Analytical
Services Domain that defines the set of capabilities supporting the extraction,
aggregation, and presentation of information to facilitate decision analysis
and business evaluation.
Service
Type(s): Visualization -
defines the set of capabilities that support the conversion of data into
graphical or picture form.
Analysis and
Statistics - defines the set of capabilities that support the examination of
business issues, problems and their solutions.
Reporting -
defines the set of capabilities that support the organization of data into
useful information.
Component(s): Mapping / Geospatial / Elevation / GPS
- defines the set of capabilities that support the use of elevation, latitude,
and longitude coordinates.
CAD - defines the set of
capabilities that support the design of products with computers.
Imagery - defines the set of
capabilities that support the creation of film or electronic images from
pictures or paper forms.
Radiological – defines the set of
capabilities that support the use of radiation and x-ray technologies for
analysis and scientific examination.
Ad Hoc – defines the set of
capabilities that support the use of dynamic reports on an as needed basis.
Standardized / Canned –defines the
set of capabilities that support the use of preconceived or pre-written
reports.
These SRM service elements are likewise supported by
Interior’s IT (technical) infrastructure (e.g., servers, networks). Within this
infrastructure are individual TRM components for which this domain team is
providing guidance. The graphic below outlines those TRM elements for this
domain that support the service needs of the SRM.
Additionally, it’s doubtful that a single domain chapter
from the TRM can be used to address a substantive issue. More realistically, a few architecture
domains may need to be reviewed when addressing an important IT decision. For example, if Interior was considering the
creation of a new Interior-wide Geospatial technology mapping capability that
could be used both by the general public and Interior personnel, then the TRM
chapters like Geospatial Technologies, Information Security, Data Management
and Application Development might all need to be reviewed.
The
principles listed below provide guidance for the design and selection of
technology components that will support the Geospatial technology needs of Interior-wide IT
initiatives.
|
|
|
|
Most data within Interior has a Geospatial component; our
databases must reflect that fact.
Rationale:
- Interior is a geographically based
organization.
- Better communications and
decision-making can be made through the visualization of complex
information.
- Geospatial information adds
significant value to data.
- Geospatial
technology is the information and analytical tool for geographic
enterprises.
Implications:
- Adding Geospatial components to legacy
data may be expensive.
- Need common business model for
relational database (e.g., keys, data content, definitions).
- Need training for developers (both Geospatial and non- Geospatial knowledgeable) on using geospatial
information.
- Applications must not remove
geospatial references during processing.
- Need for Geospatial reference review
during system development process.
|
|
|
|
Principle 2:
Information is an Interior asset
|
|
|
Information is valued as an Interior asset to accelerate
decision-making, improve management, and increase accountability.
Rationale:
- The
value of information is not realized if it is held in isolated pockets.
- Information
must be shared to maximize effective decision-making across lines of
business and with partners.
- Information
is necessary for decision making to support accelerated business process
cycles.
- Increased
access leads to improved integrity and relevance of data.
- Supports
Office of Management and Budget (OMB) Circulars: A16 “Coordination of
Surveying, Mapping and Related Spatial Data Activities”; A-119 “Federal
Participation in the Development and Use of Voluntary Standards”; and
A-130 “Management of Federal Information Resources”.
- Supports
Executive Order 12906 “Coordinating Geographic Data Acquisition and
Access: The National Spatial Data
Infrastructure”.
Implications:
- Supporting
policies regarding security, privacy, confidentiality, information
sharing, information integrity, utility and data relevance must be
developed and implemented (e.g., as outlined in FGDC Privacy Act -
Newsletter Summer 1998; see: http://www.fgdc.gov/publications/documents/geninfo/fgdcnl798.html
).
- Need
to promote interoperable information management, such as data warehouses
and data access methods that facilitate information availability for
decision-making.
- Data
warehouses, metadata and data accesses may need to be developed to
facilitate information availability for decision-making.
- Information
needs to be structured for easy access and management, timely
availability, and use.
- Metadata
(information about the data, such as source, units of measurement, and
collection methods) will need to be developed and made available.
- Need
regular training on appropriate use of information and its quality
(e.g., refuge vs legal vs legislative boundaries).
- Need
to maintain currency of the data and the legacy data itself.
- Need
to assure the accuracy and accessibility of the data over time (e.g.,
mapping historical changes and maintaining it like wetlands).
- Need
a method for estimating the value of the information assets themselves
(e.g., specific Geospatial database is valued at $50M because it would
cost that much to recreate it).
|
|
|
|
Principle 3:
Data and Information Stewardship
|
|
|
Data and information must be managed and maintained as a
stewardship responsibility to support the mission of Interior.
Rationale:
- Data
is a resource important to the accomplishment of Interior’s work. In its broadest sense, it is
information including items like electronic and paper documents (e.g.,
maps), emails, film, etc. Like
natural resources, data needs stewards who are responsible for its
valuation, preservation, security, access and utilization across
Interior and with the public.
- Data
stewards will promote common business rules, which would facilitate
sharing information, communication, and improved data integrity.
- Supports
Office of Management and Budget (OMB) Circulars: A16 “Coordination of
Surveying, Mapping and Related Spatial Data Activities”; A-119 “Federal
Participation in the Development and Use of Voluntary Standards”; and
A-130 “Management of Federal Information Resources”.
- Supports
Executive Order 12906 “Coordinating Geographic Data Acquisition and Access: The National Spatial Data
Infrastructure”.
Implications:
- Recognition
that business area personnel need to be responsible for stewardship of
the data and the commitment of the resources necessary to make
stewardship happen.
- Stewardship
includes responsibility for clarification of the data’s meaning,
content, and reuse.
- Stewardship
includes responsibility for managing data’s consistency, timeliness,
accuracy and completeness.
- The
scope of stewardship must be very sensitive to the sources and uses of
the information, ensuring security, confidentiality and privacy are
protected.
- Need
to develop a data stewardship program that will transcend many
organizational boundaries (e.g., no current rewards for cross-bureau
cooperation) and include various levels of stewardship while leveraging
and adhering to Federal data programs and standards (e.g., Federal
Geographic Data Committee (FGDC), National Institute of Standards and
Technology (NIST)).
- Recognition
of the need to manage metadata; that is data “about” the data.
- Responsibility
of steward for training and education in a persistent and consistent
manner (e.g., software, data, and methodology changes regularly).
|
|
|
|
|
|
|
|
Systems must be designed, acquired, developed, or enhanced
such that data and processes can be effectively shared, for appropriate
purposes, across Interior and with our partners.
Rationale:
- Increased efficiency will
better serve our customers (e.g., the public, employees).
- Duplication of effort
will cause higher support costs.
- Ensures more accurate
information.
- Shared data and processes
lead to better decision-making and accountability.
- OMB Circular A16 “Coordination of
Surveying, Mapping and Related Spatial Data Activities”.
Implications:
- Will need common data
standards and consistent data management processes across Interior.
- Every systems analyst
needs to consider enterprise wide impacts when designing enhancing,
acquiring or extending the scope or use of applications.
- We will need new tools that
enable data sharing and the training for their proper use.
- Will need a method for
identifying data and processes that need integration, when integration
should take place, the degree of integration versus interoperability,
who should have access to the data, and cost justification for
integration.
- Over-integration can lead
to difficult data management and inefficient processes.
|
|
|
|
|
|
|
|
In considering system requirements (e.g., new functionality),
we should look to reuse existing components before we buy. If no components exist, purchased solutions
(e.g., commercial-off-the-shelf (COTS) or government-off-the-shelf (GOTS))
should be explored before we build.
Rationale:
- Complies with, the Privacy Act of 1974
and the Government Information Systems Reform Act (GISRA).
- Supports
Office of Management and Budget (OMB) Circulars: A16 “Coordination of
Surveying, Mapping and Related Spatial Data Activities”; A-119 “Federal
Participation in the Development and Use of Voluntary Standards”; and
A-130 “Management of Federal Information Resources”.
- The more you’re “like” everyone else
(e.g., same standard, same systems), the easier it is to share with
others.
- System development is not a primary
mission of Interior.
- Supports
Executive Order 12906 “Coordinating Geographic Data Acquisition and
Access: The National Spatial Data
Infrastructure”.
Implications:
- Need to define, identify and maintain
“reusable” components.
- Good system specifications will be
needed early in the planning cycle to evaluate alternatives.
- Business processes may need to be
"changed" but not compromised to ensure compliance with
Interior and Federal standards, to accommodate reuse or purchased
solutions.
- In-depth knowledge of system functions
may be outside of the organization, potentially increasing issues of
risk and cost. Therefore, it will require the metadata information like
the process, references (e.g., algorithms), and documentation (e.g., 50%
of programming code is remarks) as well as acquiring the digitally
delivered unencrypted original source code from the software vendor.
- Requirement for greater sensitivity to
the possibility of losing mission responsibility when using outside
resources.
- System design will migrate to “open” standards.
- When acquiring data from private
vendors, licensing restrictions should be considered.
|
|
|
|
Principle 6:
Enterprise Network as “Virtual” LAN
|
|
|
We must implement an Interior-wide “interoperable
network”; performing as if it were a virtual, Interior-wide Local Area
Network (LAN).
Rationale:
- Networks
are the essential enabling technology for client/server, Internet, and
collaborative computing (e.g., emails, file transfers (e.g., file
transfer protocol (FTP)), secure teleconferencing, workflow, geospatial
data).
- Knowledge
workers have increasing need for access to information across Interior;
this access must appear seamless.
- Lack
of a robust network architecture will impact the success of distributed
applications.
- Expands
the vision of organizations by reaching out to customers and suppliers.
Implications:
- Requires
higher speed and higher bandwidth networks.
- Will
need the interconnection of distributed LANs.
- Need
to create connections between legacy systems, client/server and Internet
applications.
- Need
to implement a robust, interoperable directory services capability.
- Need
to define guidelines around “who pays”, “who uses”, “who gets”, and “who
coordinates” these interoperable networks.
- Policies
and protocols on sharing and exchanging information with third parties
need to be addressed (e.g., restricted sub-nets will need to be
supported).
- Need
to accommodate remote locations with limited communications options.
|
|
|
|
|
|
|
|
Easy and timely access to data and information is the rule
rather than the exception without security, confidentiality, and privacy
being compromised.
Rationale:
- Productivity,
decision-making, and customer service all benefit from easy, direct, and
timely availability of information.
- In accordance with the
Paperwork Reduction Act (PRA, PL 104-13), employees and the public
should have efficient, effective, and economical access to Government
information.
- Information should be
attainable in the appropriate place, time, format and context.
- The Rehabilitation Act of
1998 requires executive agencies to develop, acquire and use information
technology that is accessible to individuals with disabilities.
- Under Electronic Freedom
of Information Act (E-FOIA) bureaus and offices are required to make
records that are frequently requested under the FOIA available for
public inspection. Further,
records created on or after November 1, 1996 must be available via the Internet or
other electronic means.
- The Government Paperwork
Elimination Act (GPEA) requires agencies to incorporate privacy
protections when developing electronic processes.
- Beyond the legal
requirements, easy and timely access to data and information makes sound
business sense.
Implications:
- Need to identify, publish
and keep the applicable policies and attendant interpretations current.
- For unclassified
information, the right to know should be presumed unless policy or law
specify otherwise; however, for information like “pre-decisional
information”, access would still be controlled.
- The business necessity of
sharing information must be established.
- Technology must be
deployed to distribute and allow access to information.
- Classification and
sensitivity of information must be clearly stated and the rules well
defined (e.g., locational precision protected where an archeologically
significant site or a nuclear power plant is located).
- Sensitive information
must not be accidentally released (e.g., copyright).
- A variety of public and
private access methods for public information in accordance with E-FOIA
will need to be provided.
- Every attempt will be
made to make information available in formats accessible to those with
sensory disabilities in accordance with Section 508 without incurring an
undue burden.
|
|
|
|
|
|
|
|
Business processes will be analyzed, simplified or
otherwise redesigned in preparation for and during information systems
enhancements, development, and implementation.
Rationale:
- Work
processes will be streamlined, efficient, and cost-effective.
- Work
processes, activities, and associated business rules will be well
understood and documented.
- Enables
E-Government initiatives.
- Potentially
reduces the total cost of ownership.
- Provides
better customer service.
- Required
by Clinger-Cohen and OMB Circular A-130 “Management of Federal
Information Resources” before an IT investment can be made, and promotes
compliance with the Government Performance and Results Act (GPRA).
Implications:
- Cultural
change may be required to implement reengineered business processes that
include geospatial technologies.
- Need
system sponsors to include the impact of geospatial data on their goals.
- Need
for system owners and developers to understand that visualization can be
used as a starting point for initial systems analysis and understanding
complex processes.
- Need
agreed upon business process re-engineering scope and results to enable
continual improvement through analyzing, simplifying and redesigning
work processes.
- New
technology will need to be researched and applied in conjunction with
business process review (e.g., don’t use “new” just because it’s new).
- Additional
time and resources will have to be invested in business analysis early
in the systems life cycle.
- Requires
all organizational levels, especially senior leadership to sponsor and
support reengineering efforts.
- Need
training for developers (both Geospatial and Non-Geospatial
knowledgeable) on using geospatial information.
|
|
|
|
|
|
|
|
Interior will adopt a total cost of ownership model (TCO)
for IT systems that includes costs like data acquisition and maintenance
(e.g., biggest costs of Geospatial elements).
Rationale:
- Leads to
better-informed decisions through an improved understanding of trade
offs.
- Enables improved planning and budget
decision-making.
Implications:
- For Geospatial
solutions,
the data sets have their own life cycle in addition to the software
itself (i.e., data is major cost driver with requirements like
compliance that add to expense).
- Geospatial
data never
really “goes away” so maintenance is high (e.g., 9 track tape of
satellite data needs to migrate to new media).
- Need for
coordinated management to mitigate data maintenance cost (e.g., National
Spatial Data Infrastructure (NSDI) framework data sets)
- Need to develop
a total cost of ownership model that explicitly includes geospatial data
management and educate system sponsors and decision-makers about how to
use it.
- Leads to
coordinated system replacements, enhancements and retirements.
- Need to apply
TCO to portfolio management and records management (e.g., geospatial
data sets and hardcopy are part of the data).
- Need to provide
tools for collection of the actual total cost of ownership.
|
|
|
|
|
|
|
|
IT solutions will use industry-proven and
“state-of-the-art” mainstream technologies.
Rationale: |
