GIS Domain-Technology Reference Model vs 2.0

4.1 Introduction and Background

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.

4.2 Architectural Principles

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.

Principle 1: Spatial components
	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).

Principle 4: Integration/ Interoperability
	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.

Principle 5: Reuse before you buy and buy before you build
	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.

Principle 7: Information Access
	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.

Principle 8: Reengineer First
	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.

Principle 9: Total Cost of Ownership
	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.

Principle 10: Mainstream Technologies
	IT solutions will use industry-proven and “state-of-the-art” mainstream technologies. Rationale: Avoids dependence on weak vendors. Ensures robust product support. Enables greater use of commercial-off-the-shelf solutions. Complies with OMB Circular A-130 “Management of Federal Information Resources”, which requires the application of up-to-date information technology to take advantage of opportunities to promote fundamental changes in agency structures, work processes, and ways of interacting with the public that improve the effectiveness and efficiency of Federal agencies. Implications: Need to establish criteria for vendor selection and performance measurement. Need to establish the criteria to identify the weak vendors and poor technology solutions in compliance with Federal government contracting policy and procedures. Requires the technology portfolio to migrate away from existing weak products or products that are reaching obsolescence. We may be slow to adopt new technologies. The exploration of new technology will be managed and investigation results shared. Changing from mainstream vendor’s products within Geospatial technologies will incur significant conversion costs (e.g., maintenance of existing geospatial legacy data) and loss of support for our partners (e.g., other agencies, customers). Conversions may result in explicit loss of data (e.g., Michigan project with 2-5% of the data content was lost due to a format change).

Principle 11: Industry Standards
	Extra value will be given to products adhering to industry standards and open architecture. Rationale: Required to support data and process interoperability. Reduces risks. Reduces dependence on single vendor. Enables greater use of commercial-off-the-shelf solutions. Allows flexibility and adaptability in product enhancement, extensibility, and replacement. Implications: Need for Interior-wide core standards for exchanging geospatial data among bureaus. Need effective management process to identify and assess industry standards and share standards information across Interior. Participation in the development of open standards is mandatory. Training and education are required to promote the use of “open standards.” Public open standards will need to be used for distribution of geospatial data to “outside” participants (e.g., public) to avoid proprietary formats.

4.3 Technology Components

The Geospatial technology components in this domain include:

Integrated Development Environment-This consists of the hardware, software and supporting services that facilitate the development of software applications and systems.
Database- Refers to a collection of information organized in such a way that a computer program can quickly select desired pieces of data.
Utilities- Refers to software tools that address various miscellaneous processes for technology applications and users.
Reporting and Analysis- Consists of the tools, languages and protocols used to extract data from a data store and process it into useful information.
Middleware- This increases the flexibility, interoperability, and portability of existing infrastructure by linking or “gluing” two otherwise separate applications.

The classifications for any products or standards within this domain are:

Life Cycle Definition/

Classifications Meaning

Preferred Product/standard of choice; support available; recommended.

Contained Develop solutions using these standards or products only if there are no suitable alternatives categorized as preferred; if a preferred product is available that will meet the requirements, plans should be developed to move from contained to preferred as soon as practical.

Obsolete Being phased out; (e.g., vendor support ending); plans should be developed to rapidly phase out and replace (often to avoid substantial risks).

Research Product/standard to be used in conjunction with technology research efforts only (e.g., testing, pilots).

Rejected Product/standard has been evaluated and found not to meet technical architecture needs.

4.3.1 Integrated Development Environment

An Integrated Development Environment allows for the creation and support of geographical-based technology solutions that support business information needs. The Geospatial Components provide the functions and tools needed to store, analyze, and display information about places. Imaging & Remote Sensing Tools make imaging information for analysis more useful because they allow interpretation and analysis of simple pixel information.

Geospatial Components:

Use of the ESRI ArcView (version >8X) is classified as Preferred.

Use of the ESRI ArcInfo (version >8X) is classified as Preferred.

Use of the ESRI IMS is classified as Preferred.

Use of the ESRI ArcPad is classified as Preferred.

Use of the ESRI ArcPad App Builder is classified as Preferred.

Use of the ESRI Survey Analyst is classified as Preferred.

Use of the ESRI Network Analyst is classified as Preferred.

Use of the ESRI Tracking Analyst is classified as Preferred.

Use of the ESRI Spatial Analyst is classified as Preferred.

Use of the ESRI 3D Analyst is classified as Preferred.

Use of the ESRI ArcPress is classified as Preferred.

Use of the ESRI Publisher is classified as Preferred.

Use of the ESRI Geostatistical Analyst is classified as Preferred.

Use of the ESRI Street Map is classified as Preferred.

Use of the ESRI SDE Connects is classified as Preferred.

Use of the ESRI ArcView (version 3x to 8x) is classified as Contained.

Use of the ESRI ArcInfo (version <8X) is classified as Contained.

Use of the ESRI COGO is classified as Contained.

Use of the ESRI GRID is classified as Contained.

Use of the ESRI TIN is classified as Contained.

Use of MapInfo is classified as Contained.

Use of GeoMedia is classified as Contained.

Use of GeoGraphix is classified as Contained.

Use of IDRISI is classified as Contained.

Use of the ESRI ArcView (version <3x) is classified as Obsolete.

Use of the ESRI PC ArcInfo is classified as Obsolete.

Imaging & Remote Sensing Tools:

Use of ERDAS Imagine Suite is classified as Preferred.

Use of Research Systems PCI is classified as Preferred.

Use of Research Systems ENVI is classified as Preferred.

Use of LizardTech’s Mr. Sid is classified as Preferred.

Use of LizardTech’s déjà vu is classified as Preferred.

Use of Dynamic Graphics’ EarthVision is classified as Preferred.

Use of Integraphs Integraph Photogrammetry is classified as Contained.

Use of Earthware is classified as Contained.

Use of Earth Resource Mapping ER Mapper is classified as Contained.

4.3.2 Database

To provide the benefits of geospatial information, the backbone technology component is the traditional IT relational database management system (RDBMS). A RDBMS is an extremely complex set of software programs that controls the organization, storage and retrieval of data (fields, records and files) in a database. It also controls the security and integrity of that database. The RDBMS accepts requests for data from various application programs and instructs the operating system to transfer the appropriate data. The ability of these databases to easily and quickly find, update and report geospatial information is critical to the successful use of Geospatial technologies.

Use of Microsoft Access 2000 is classified as Preferred.

Use of Microsoft SQL Server is classified as Preferred.

Use of Oracle 9i (versions >7x) is classified as Preferred.

Use of Informix Dynamic Server is classified as Contained.

Use of IBM DB2 is classified as Contained.

4.3.3 Utilities

Utilities are software tools that address various miscellaneous processes to assist technology applications and users. For the Geospatial domain, the primary utility is a free reader for viewing geographical output without the need for a licensed software product (like Acrobat from Adobe).

Use of the ESRI ArcReader is classified as Preferred.

4.3.4 Reporting & Analysis

The value of the information contained within Geospatial databases is maximized with the use of quality reporting and analysis tools.

Use of Crystal Decisions Crystal Reports is classified as Preferred.

Use of the ESRI Map Suite is classified as Preferred.

Use of Microsoft’s Access is classified as Preferred.

4.3.5 Middleware

Middleware is a broad term for software that functions as a “translation layer” between two or more applications and/or between applications and shared services independent of the network and platform technologies. For Geospatial technologies with their use of encoded themed layers and both explicit and implicit geographic references, an important middleware component is a spatial database engine.

Use of the ESRI Spatial Database Engine (SDE) is classified as Preferred.

4.4 Select Best Practices

The Domain Principles, because they are derived from Interior’s business direction and strategies, provide the primary direction and guidance around technology decisions within this domain. Additional benefit may sometimes be obtained by reviewing Select Best Practices. These reflect the valuable insights from either domain team members’ experiences or other public sector organizations.

SRM Focused

Select

Best Practice 1: Stewardship – Establish an Interior data stewardship program with clearly defined roles and responsibilities.

Select

Best Practice 2: Classification – Establish and use a consistent process to classify the sensitivity of all data and information as a basis for ensuring the security, privacy and confidentiality of Interior's data and information assets.

Select

Best Practice 3: Data Quality – The Data Steward is responsible for determining the business rules for the data in their repository. Additionally, the steward is responsible for monitoring the quality of the data in the repository.

Select

Best Practice 4: Data Cleansing – Develop and use consistent data cleansing rules. Data Dictionaries and Data Models should assist in describing how the data should be cleansed. Knowledge of data dependencies, constraints, data types etc. is important.

Select

Best Practice 5: Geospatial references – Databases should incorporate geospatial references whenever applicable: Geospatial references should be retained when present, and added to legacy data when major updates occur.

Select

Best Practice 6: Data Archiving – Establish and follow a consistent standard & process for defining, maintaining and archiving Interior data.

Select

Best Practice 7: Data Exchange – Establish a process for determining data exchange protocols and identify the protocols to be used across Interior.

Select

Best Practice 8: Reusability- Reuse data models and data sets to facilitate sharing of Data across the Department and with business partners.

Select

Best Practice 9: Authoritative Sources- Minimize data duplication by identifying and using authoritative data sources. Data Management Steering Committee guidance required.

Select

Best Practice 10: Backup and Recovery- Develop and document back-up and recovery procedures to support the published Continuity of Operations Plans (COOP).

Select

Best Practice 11: Metadata Definitions- Establish and follow a consistent process for determining and maintaining metadata definitions. Look for guidance from Federal Geographic Data Committee (FGDC) and Bureau Data Stewards. Adopt existing national / international standards based on OMB Circular A16, A119, and A130.

Select

Best Practice 12: Metadata Process- Integrate metadata into all data management processes not only as a documentation tool but also as a dynamic reference for all applications that access or update data.

TRM Focused

Select

Best Practice 13: Data Compatibility- Compatibility with ESRI SDE is required for Geospatial applications.

Select

Best Practice 14: Browser Compatibility- Minimum version 6.x of Internet Explorer is required for Geospatial applications.

Select

Best Practice 15: Desktop Configuration- For Geospatial Applications, minimum configuration for ArcPad needs to be met.

Select

Best Practice 16: Collaboration- Any collaborative solutions (e.g., email, NetMeeting) need to recognize the large data files and bandwidth needs of Geospatial applications.

Select

Best Practice 17: Planning- Before deploying Geospatial solutions, sizing for the audience (e.g., gateways, servers, ports) should be completed.

Select

Best Practice 18: Intranet- Intranet should be designed for department-wide usage and not just for a bureau. While access to resources on the Intranet should be as easy as access to the Internet (if not easier).

Select

Best Practice 19: Compliance 508- Geospatial applications are not Section 508 compliant and therefore should be remembered when proposing solutions to customers.

Select

Best Practice 20: Hosting- Use of 3rd parties to Host Geospatial data/ applications should be available as optional delivery vehicle. Use of standard contract with acceptable language covering security, etc. should be in place for any Hosting providers (e.g., 3rd party).

Select

Best Practice 21: Network Planning- Changes to existing networks should include dialogue with Geospatial developers to avoid severe service level impacts. Network planning should explicitly include Geospatial data transport needs.

Select

Best Practice 22: Secure FTP- Secure FTP should be provided for Geospatial file transfers between agencies and external partners.

Select

Best Practice 23: Multiprocessors- For high-end GIS users, multiprocessors are traditionally needed to deliver Geospatial solutions.

Select

Best Practice 24: Servlets- The appropriate servlet for Geospatial applications are often unique (e.g., IMS servlet engine & J2EE) and detailed installation instructions are often critical.

Select

Best Practice 25: Portals- Leveraging the existing Geospatial One-Stop (GOS) can avoid the need for additional portals.

Select

Best Practice 26: Thin Clients- Investigating whether all required functions of ArcGIS are supported with a "thin client" arrangement should be determined. Licensing should be investigated because restrictions may exist (e.g., running out of the number of valid licenses when a "call" is made to different servers).

Select

Best Practice 27: Modeling- Design object oriented spatial databases using UML.

Select

Best Practice 28: Network Bandwidth- Use of higher quality and quantity of network bandwidth will reduce the amount of storage by removing the need for additional duplication/ replication.

Select

Best Practice 29: Plotters- Use plotters that are supported by ESRI Level 1 support drivers.

Select

Best Practice 30: Network Speeds- Use of 100 MB switch to the workstation is ideal. Gigabit switches between data servers and application servers is also ideal. GB should be used for all full time geospatial end users.

Select

Best Practice 31: Administrative Rights- Many GIS users/ developers need to be provided with additional rights to access and use the GIS software.

Best Practice 32: Metadata- All Geospatial data must have FGDC compliant metadata.

4.5 Contributors

The quality of the Interior-wide guidance provided within this TRM chapter is a reflection of the efforts of the Geospatial technologies Domain team. The members of the team are:

Organization Name

Bureau of Indian Affairs Richard F. Moore

Bureau of Land Management Jim Turner

Jim Scrivner

Bureau of Reclamation Lorri Peltz-Lewis

Minerals Management Service Michele Daigle

National Park Service David Duran

Office of Surface Mining Alan Wilhelm

US Fish and Wildlife Service Deb Green

US Geological Survey Bob Pierce

Chapter 4. Geospatial Technologies Architecture

Principle 2: Information is an Interior asset

Principle 3: Data and Information Stewardship

Principle 6: Enterprise Network as “Virtual” LAN