COTS Based Approach to Implementing Enterprise GIS

Brian Cross and Greg PleissEsri Professional Services

Topics

1. Overview of the COTS approach (Brian)

2. ArcGIS 10 in COTS Implementations (Greg)

3. System Development using COTS (Brian)

4. Summary (Brian)

5. Questions / Discussion

Introducing the COTS Approach

What is the COTS Approach?

• Maximizing commercial off the shelf software in a GIS system

• System meets business goals by leveraging COTS- Configures and extends COTS- Avoids developing software

• Immediate capability… continually improving via COTS release cycles

• Users engaged early and often to iteratively improve system

Approaches to Building an Enterprise GIS

Comparing Approaches

COTS System follows standard system development lifecycles, but activities are different than traditional developmental systems

A Different Way of Thinking

• Challenges common procurement models- Requirements focused on business goals vice detailed

feature functions- Select COTS that best meets business goals and

implement “with the grain” for best results- Schedule linked to COTS release cycles

• Asks users to consider new business processes- New workflows based on COTS strengths (usually better)

- People resist change- Organizations resist change

• Avoid temptation to overly customize- Best intentions of many people often push systems

towards customization

ArcGIS System Concept

CloudServices

CloudServices

EnterpriseServices

EnterpriseServices

LocalLocal

•• MappingMapping•• AnalysisAnalysis•• CollaborationCollaboration•• EditingEditing•• CompilationCompilation

Rich ClientRich Client

MobileMobile

ArcGISArcGIS

Web BrowserWeb Browser ArcGISArcGISUsing & ManagingUsing & ManagingMap & GeographicMap & GeographicInformationInformation

Enterprise GIS System Pattern @ ArcGIS 10

Authoritative Content

ProducersBasemaps

& ArcGIS.com

Map & DataProducts

Services (Maps, Analysis)

Field Edits &Partner Input

Configurable & shared • workflows • production tools• business rules

COTS Technology Elements for Enterprise GIS

DataMaintenance

DataMaintenance DisseminationDisseminationGeodata ManagementGeodata Management

A COTS approach for Enterprise GIS

Production ManagementProduction Management

ProductionGeodatabase

PublicationGeodatabase

Web Services Web Services

Geodatabase Design

• Emphasize end-user capabilities- Define detailed information products- Build to deliver

• Embrace federated compilation and maintenance- Be realistic, prioritize compilation capabilities- Leverage data content provided by the enterprise- Integrate content at the service level, not RDBMS

• Design for COTS usability- Leverage geodatabase concepts (FCs, subtypes, etc)- Balance tradeoffs for maintenance and dissemination

Geodata Management

Geodatabase VersionsGeodatabase Versions

Connected ReplicasConnected Replicas

Disconnected ReplicasDisconnected Replicas

Check Out ReplicasCheck Out Replicas

ProductionGeodatabaseProduction

GeodatabasePublication

GeodatabasePublication

Geodatabase

One-WayReplica

•Read-Write Access•Tuned for Editing•Authoritative Content

•Read-Only Access•Tuned for Services•Approved Content

•Ideal for outsourcing work•XML-based transfer•Two-way exchange

•File-based GDB•Inhouse or Outsourced•One-time exchange

•Workgroups•Two-way exchange

•Direct editing•Basis for replication

Data Maintenance

• Model new and existing processes- Integrate GIS and non-GIS- Standardize and streamline- Continually evolve workflows

• Configure a common rule-base- Feature templates- Map templates- Quality Control rules

Data Maintenance

ESRI Production MappingESRI Production Mapping

QA\QCRules

QA\QCRules

FeatureTemplates

FeatureTemplates

MetadataRules

MetadataRules

MapTemplates

MapTemplates

ArcGIS Workflow ManagerArcGIS Workflow Manager

WorkflowsWorkflows ApplicationIntegrationApplicationIntegration

TaskAssistantManager

TaskAssistantManager

GIS Professionals

ArcGIS Server Workflow ManagerArcGIS Server Workflow Manager

ArcGIS MobileArcGIS MobileArcGIS Web APIsArcGIS Web APIs

ManagementServices

ManagementServices

ExecutionServices

ExecutionServices

TaskingServicesTaskingServices

MappingServicesMappingServices

Non-GISUsers

FieldUsers

Production

Silverlight

Silverlight

JavaScriptJava

ScriptFlexFlex AndroidAndroidWindowsWindowsiOSiOS

ArcGIS Desktop ArcGIS Server

Content Dissemination

• Deliver diverse information products- Visualization- Analysis- Geodata

• Enable search & discovery- Standards-based (OGC)- ArcGIS.com

• Support internal and external users- Web services (connected)- Traditional media (disconnected)

ConnectedConnected

Publication

ArcGIS Server & GeoPortal ExtensionArcGIS Server & GeoPortal Extension

Search &DiscoverySearch &Discovery

GeoprocessingServices

GeoprocessingServices

OGCServices

OGCServices

MapServices

MapServices

GeodataServicesGeodataServices

ArcGIS Server Web APIsArcGIS Server Web APIsJavaScript

APIJavaScript

APISilverlight

APISilverlight

APIFlexAPIFlexAPI

ManyUsers

ManyApplications

Content Dissemination

DisconnectedDisconnected

DistributedPublication

Node

Production Management

• Provide transparency- Task and manage production- Provide status and reporting

• Utilize role-based functionality- Targeted user experience- Keep it simple

• Extend the reach of GIS workflows- Simple, web-based access- Enable non-GIS users

Production Management

Production

ArcGIS Server Web APIsArcGIS Server Web APIsJavaScript

APIJavaScript

APISilverlight

APISilverlight

APIFlexAPIFlexAPI

Managers &Executives

ArcGIS ServerArcGIS Server

MappingServicesMappingServices

ArcGIS Server Workflow ManagerArcGIS Server Workflow Manager

ReportingServicesReportingServices

ManagementServices

ManagementServices

TaskingServicesTaskingServices

ExecutionServicesExecutionServices

Web Applications

ArcGIS.comArcGIS.com

Data Maintenance Data Maintenance

Dissemination(Connected/Disconnected)

Dissemination(Connected/Disconnected)

A Complete System for Enterprise GIS

Production ManagementProduction Management

Geodata ManagementGeodata Management

Reporting

Execution

Tasking

Management

Non-GIS Users

GIS Users

Web Apps

Field Users

GenerateProducts

Visualize

Analyze

Search &Discover

AccessData

ManyUsers

ManyApps

MultipleOptions

A Process for a COTS Based Approach

COTS Impacts to System Development Process

PlanningPlanning REQREQ DesignDesign DEVDEV TestTest ImplementImplement

PlanningPlanning REQREQ DesignDesign TestTest ImplementImplement

Accelerated Delivery

Traditional Approach

COTS Approach

Configuration Users Exercise System

Users Exercise System

Demos for Users

Planning

• Focus on business objectives and goals• What are you trying to accomplish?

- Improving productivity

- Increasing revenue

- Reducing cost

- Supporting regulatory requirements

• All system requirements and technical decisions should consider business goals

2

Remember you are trying to solve a business problem not engineer a new software module

Planning

• Plan project using multiple phases/iterations• Plan for heavy user interaction and validation of

capabilities• Allows for integrating new COTS releases• Provides an opportunity for intermittent training

2

Phases or iterations should focus on completing a use case or scenario

2

•• Implement base COTS Implement base COTS releaserelease

•• Data Model Data Model –– first first release release

•• Workflows Workflows -- initial initial configurationconfiguration

•• Usage Patterns Usage Patterns –– IdentifyIdentify

•• User Roles User Roles –– DefineDefine•• Architecture Architecture -- establish establish

initial infrastructureinitial infrastructure

Phase 1:Out of Box Phase 2:

Refine Phase 3:Finalize•• Implement incremental Implement incremental

COTS ReleaseCOTS Release•• Data Model Data Model –– modify modify

based on inputbased on input•• Workflows Workflows –– elaborate elaborate

and create newand create new•• Usage Patterns Usage Patterns -- refinerefine•• Architecture Architecture -- Integrate Integrate

with other systemswith other systems

•• Implement Final Implement Final COTS Deployment COTS Deployment ReleaseRelease

•• Data Model Data Model -- finalizefinalize•• Workflows Workflows -- finalize finalize

workflowsworkflows•• Architecture Architecture –– plan for plan for

system implementationsystem implementation•• Training Training –– develop develop

planplan

COTS Based Phased Planning

Continuous Learning & Improvement

Requirements

• Focus on the “what” NOT the “how”• Embrace the change – do not modify COTS

technology to support an inefficient process• Keep it simple

2

UsersCOTS Demos

Traditional COTS

Design

• Short focused interactive design sessions• Heavy use of prototyping and lab environment• End users along with COTS experts

- Defining user roles- Defining workflows- Identifying efficiencies- Understanding end user access

• Consider future COTS releases

2

Design should emphasize delivering immediate capabilities

COTS Design/Configuration Process

Develop

• Based on user input and feedback• Targeted to configuration not customization• 90% configuration 10% (or less) development

3

Users

Roles & Usage

Configuration Team

COTS Products

Data Model Workflows

Test

• Frequent user validation• Multiple user groups to verify usage patterns• Prioritize user feedback – leverage phases• Use validation as training opportunity

3

Real time feedback to Configuration Team

Use/Exercises FeedbackTraining Refine

UsersConfiguration

Team

Implementation

• Understand you are changing process not just technology

• Leverage COTS training• Data flow patterns• IT Specifications• Security considerations • Administration

- Who? What? Skills?

• Don’t forget about the data!

3

COTS Based Phased Implementation

Pilot

Deployment Phase 1

Deployment Phase 2

Summary

Benefits of a COTS Approach

• Minimized cost to implement• Shorter schedule – immediate exercising by users• Reduced risk (technology proven by user-base)• Lowered maintenance costs• Evolves with future COTS functionality• Wider range of qualified people to use and maintain

system

Summary

• COTS configuration is a more efficient way to approach system development

• The COTS Approach redefines system development process, with focus on mission instead of building software

• ArcGIS 10 provides a platform for configuration and rapid development – making the COTS Approach viable for many systems

Questions?

Thank you!

More Info:- COTS Approach ArcNews article (Winter 2011)

- http://www.esri.com/news/arcnews/winter1011articles/the- cots-approach.html

- COTS Approach white paper (Jan 2011)- http://www.esri.com/library/whitepapers/pdfs/cots-based-

approach-enterprise.pdf

Contact us:- Brian Cross, bcross@esri.com- Greg Pleiss, gpleiss@esri.com