Solution ApproachesSolution Approaches&&&&

Best Practices forBest Practices forEnterprise InteroperabilityEnterprise Interoperability

Jim VanOstenbridgeJim VanOstenbridgeEnterprise ConsultantEnterprise ConsultantEnterprise ConsultantEnterprise Consultant

ESRI Professional ServicesESRI Professional Services

Principal ReferencesPrincipal References

AgendaAgenda

•• IntroductionIntroduction•• IntroductionIntroduction•• Scenario Part 1: The New DashboardScenario Part 1: The New Dashboard•• Aspirations for a New Operating ModelAspirations for a New Operating Model

S i P 2 B F I biliS i P 2 B F I bili•• Scenario Part 2: Brute Force InteroperabilityScenario Part 2: Brute Force Interoperability•• Enterprise Maturity: Evolving the Operating ModelEnterprise Maturity: Evolving the Operating Model•• Scenario Part 3: Recasting the ProjectScenario Part 3: Recasting the Project•• Solution Design & Development/Operations & MaintenanceSolution Design & Development/Operations & Maintenance•• ESRI Resources and GuidanceESRI Resources and Guidance•• Additional ReferencesAdditional ReferencesAdditional ReferencesAdditional References•• Interoperability Best Practice SummaryInteroperability Best Practice Summary•• DiscussionDiscussion

Cl i R kCl i R k•• Closing Remarks Closing Remarks

Maps and GIS Are ChangingMaps and GIS Are ChangingBecoming Richer & More PervasiveBecoming Richer & More PervasiveBecoming Richer & More PervasiveBecoming Richer & More PervasiveNew Styles, Patterns & TechniquesNew Styles, Patterns & Techniques

New ServicesNew Services

WebMaps

e Se cese Se ces

Mashups

UGC

Web 2.0

GeodataReal-Time

Data

Maps

New MediaNew Media

MobileSocial

Networks

Enterprise InteroperabilityEnterprise Interoperability

•• Enterprise Defined (Enterprise Defined (MerriamMerriam--WebsterWebster))•• Enterprise Defined (Enterprise Defined (MerriamMerriam--WebsterWebster))–– “A unit of economic organization or activity; especially: a business “A unit of economic organization or activity; especially: a business

organization”organization”

Interoperability Defined (Interoperability Defined (CMU SEI SOSICMU SEI SOSI))•• “The ability of a set of communicating entities to…“The ability of a set of communicating entities to…

11 E h ifi d t t d t dE h ifi d t t d t d1.1.Exchange specified state data andExchange specified state data and2.2.Operate on that state data according to specified, agreedOperate on that state data according to specified, agreed--upon, upon,

operational semantics.”operational semantics.”

•• In practical terms…In practical terms…–– Getting the right information to the right place at the right time in the Getting the right information to the right place at the right time in the

right format to s pport orchestrated b siness acti itright format to s pport orchestrated b siness acti itright format to support orchestrated business activityright format to support orchestrated business activity

A Recent History of InteroperabilityA Recent History of InteroperabilityMainframes & Client/ServerMainframes & Client/ServerMainframes & Client/ServerMainframes & Client/Server

A Recent History of InteroperabilityA Recent History of InteroperabilityMiddleware & BrokersMiddleware & BrokersMiddleware & BrokersMiddleware & Brokers

Middleware/BrokersMiddleware/Brokers

A Recent History of InteroperabilityA Recent History of InteroperabilityServices Oriented Architecture (SOA)Services Oriented Architecture (SOA)Services Oriented Architecture (SOA)Services Oriented Architecture (SOA)

External ConsumerInternal Consumers

Pres

enta

tion

Laye

r

External ConsumerInternal Consumers

Portal

ess

er

InternetSOA Infrastructure

Tools – Security - Discovery

Bus

ine

Laye

Service A

Service B

Service C

Service D

atio

nye

r

Enterprise InformationSystems

Info

rm Lay

MainframeHierarchical Database

External Systems

A Recent History of InteroperabilityA Recent History of InteroperabilityCentralized SolutionsCentralized SolutionsCentralized SolutionsCentralized Solutions

User User

RegionalOffice

FieldOffice

User Thin Client

Data CenterProgramOffice

A li ti D t

Thin Client Connections

Connections

Thin ClientConnections

Application Data

Thin ClientConnections

Lab

Citrix Server FarmWeb Servers

OracleArcSDE

User

A Recent History of InteroperabilityA Recent History of InteroperabilityDistributed SolutionsDistributed SolutionsDistributed SolutionsDistributed Solutions

Regional Office Field Office

UserApp.

&

UserData(“Replica”)

App.&

UserApp.

&Replicate Deltas Only

Data Center

Data (“Master”)

LocalServer

( Replica )

Replicate Deltas Only

Replicate Deltas Only

Master File

UserApp.

&User

App.&

DatabaseFileServer

RegionField User

A Recent History of InteroperabilityA Recent History of InteroperabilityWhere we are todayWhere we are todayWhere we are todayWhere we are today

•• Greater measures of organizational work involve informationGreater measures of organizational work involve information•• Greater measures of organizational work involve information Greater measures of organizational work involve information systemssystems

•• The internet has set expectations of onThe internet has set expectations of on demand access todemand access to•• The internet has set expectations of onThe internet has set expectations of on--demand access to demand access to networksnetworks

Wh t t h l i ill d “ h t’ t”Wh t t h l i ill d “ h t’ t”•• Whatever technology was, or is now will precede “what’s next”Whatever technology was, or is now will precede “what’s next”

•• Imagination still moves faster than implementationImagination still moves faster than implementation

Extraction, Transformation & LoadExtraction, Transformation & LoadThe Heavy Lifting of EIThe Heavy Lifting of EIThe Heavy Lifting of EIThe Heavy Lifting of EI

•• Access to data is the key point of interest in EIAccess to data is the key point of interest in EI•• Access to data is the key point of interest in EIAccess to data is the key point of interest in EI•• Data models for different solutions are differentData models for different solutions are different•• Interpretation of “common” content may be differentInterpretation of “common” content may be different

T i l f diff l i diffT i l f diff l i diff•• Transaction cycles for different solutions are differentTransaction cycles for different solutions are different

•• High Value Task: Figuring out ETL detailsHigh Value Task: Figuring out ETL details•• Low Value Task: Extracting, Transforming, and Loading DataLow Value Task: Extracting, Transforming, and Loading Data

Enterprise Architecture (EA)Enterprise Architecture (EA)

•• Enterprise Architecture has been around for a long time as a Enterprise Architecture has been around for a long time as a di i li t b b d i l b dl d fi d ddi i li t b b d i l b dl d fi d ddiscipline yet can be broad in scale, broadly defined and discipline yet can be broad in scale, broadly defined and organizationally personalizedorganizationally personalized

•• Enterprise ArchitectureEnterprise Architecture– “the organizing logic for business processes and IT infrastructure,

reflecting the integration and standardization requirements of the firm’s ti d l ”operating model.”

-- Jeanne Ross, MIT Sloan Center for Information Systems ResearchJeanne Ross, MIT Sloan Center for Information Systems Research

ArchitectureEnterpriseArchitecture =

Architecture of the

Enterprise

The “Why” of EIThe “Why” of EI

Operating ModelOperating Model

CoordinationCoordination UnificationUnificationCoordinationCoordination•Unique businesses with a need to know each other’s transactions

•Key platform capability: easy access to shared data for

UnificationUnification•Single business with global process standards and shared global data

•Key platform capability:standard business processes andH

igh

Hig

honon easy access to shared data for

customer service, decision making, and integration

standard business processes and global data access

DiversificationDiversification ReplicationReplicationss In

tegr

atio

ss In

tegr

atio

•Independent businesses with different customers and expertise

•Key platform capability: Provide economies of scale through h d i ith t li iti

•Independent but similar business units

•Key platform capability:Standard business processes and

t f l b l ffi i i

Low

Low

ines

s Pr

oce

ines

s Pr

oce

shared services without limiting independence

systems for global efficiencies

LowLow HighHigh

Bus

iB

usi

Business Process StandardizationBusiness Process Standardization

Best PracticesBest Practices

•• What are best practices?What are best practices?•• What are best practices?What are best practices?–– Results of “enlightened trial and error”Results of “enlightened trial and error”–– Community body of experienceCommunity body of experience

•• Where do they come from?Where do they come from?–– People who have traversed your path aheadPeople who have traversed your path ahead

•• Why does it look like more work than I do now?Why does it look like more work than I do now?–– These are the lessons learned by othersThese are the lessons learned by others–– You may need to learn some of these lessons yourself to appreciate You may need to learn some of these lessons yourself to appreciate

best practicesbest practices–– Delegating responsibility with technical solutions requires precisionDelegating responsibility with technical solutions requires precision

EI, Pragmatically speakingEI, Pragmatically speaking

•• What is it?What is it?–– Coordinated activityCoordinated activity–– based on contextual and efficient access based on contextual and efficient access

to shared informationto shared information–– to shared informationto shared information

•• Why is it important?Why is it important?

•• How do you get it?How do you get it?

•• How do you know when you’ve got it?How do you know when you’ve got it?

•• Pitfall to avoidPitfall to avoid–– Interoperability is about more than Interoperability is about more than

technologytechnology

What’s the main point of Enterprise What’s the main point of Enterprise Architecture?Architecture?Architecture?Architecture?

•• People working togetherPeople working together•• People working togetherPeople working together•• Using technologyUsing technology•• Executing an organization’s operating modelExecuting an organization’s operating model

T hi b i bj iT hi b i bj i•• To achieve business objectivesTo achieve business objectives

•• Enterprise Architecture is…Enterprise Architecture is…–– more than servers, networks, software, and datamore than servers, networks, software, and data–– the framework where interoperability requirements are managedthe framework where interoperability requirements are managed–– An approach for managing change for an organization’s application of An approach for managing change for an organization’s application of

technologytechnology--based solutionsbased solutions

•• Perhaps a scenario would help…Perhaps a scenario would help…

Enterprise Stakeholders & InteractionsEnterprise Stakeholders & Interactions

Apple CountyCommissioners

CIO

SteinbrennerSteinbrennerCounty Administrator

PetermanPeterman

Public WorksCrew Chief

KramerKramerIT Manager

GeorgeGeorgePlanning Dept.Supervisor

ElaineElaine

Crew Chief

NewmanNewman GIS Manager,Analyst

JerryJerry

Customer Service

EstelleEstelle

FrankFrank

State DOTGIS Manager

LeoLeo

y

TransportationPlanner

FrankFrankRPC GISManager

Mass Transit GIS Manager

PuddyPuddy

What the Scenario implies so farWhat the Scenario implies so far

•• Business caseBusiness case•• Business caseBusiness case–– Cost associated with cognitive synergy of system contentCost associated with cognitive synergy of system content–– Expensive and inconsistent environment for making decisionsExpensive and inconsistent environment for making decisions

•• Goal is improved coordination (new operating model)Goal is improved coordination (new operating model)–– Current operating model is diversificationCurrent operating model is diversification

C di ti th h “h l ”C di ti th h “h l ”•• Coordination through “human glue”Coordination through “human glue”

•• AssumptionAssumption–– Every member of our “cast” is competent in their role with the tools in Every member of our “cast” is competent in their role with the tools in

their environmenttheir environment–– There are realistic limits to each of their rolesThere are realistic limits to each of their roles

•• This looks like a oneThis looks like a one--off project to Jerryoff project to Jerry

Aspirations for a new Operating ModelAspirations for a new Operating Model

•• Current StateCurrent State CoordinationCoordination UnificationUnification•• Current StateCurrent State–– DiversificationDiversification

•• Future StateFuture State

CoordinationCoordination•Unique businesses with a need to know each other’s transactions

•Key platform capability: easy access to shared data for

t i d i i

UnificationUnification•Single business with global process standards and shared global data

•Key platform capability:t d d b i d

Hig

hH

igh

ratio

nra

tion

•• Future StateFuture State–– CoordinationCoordination

Wh t thWh t th

customer service, decision making, and integration

standard business processes and global data access

DiversificationDiversification•Independent businesses with different customers and expertise

ReplicationReplication•Independent but similar business unitswwPr

oces

s In

tegr

Proc

ess

Inte

gr•• What are the What are the

implications?implications?

p

•Key platform capability: Provide economies of scale through shared services without limiting independence

•Key platform capability:Standard business processes and systems for global efficiencies

Low

Low

Bus

ines

s P

Bus

ines

s P

•• What will have to What will have to change?change?

LowLow HighHighBusiness Process StandardizationBusiness Process Standardization

•• Let’s continue…Let’s continue…

Collecting field contentCollecting field content

Management PressureManagement Pressure

DOT Scripts and Schema ReadyDOT Scripts and Schema Ready

A Call from DOTA Call from DOT

The ReviewThe Review

Activity Diagram: All roads lead to JerryActivity Diagram: All roads lead to Jerry

FinancialFinancialExtractExtract

WO MgtWO MgtExtractExtract

411411ExtractExtractExtractExtract

CIP InvoiceCIP InvoiceDataData

ExtractExtract

WO MgtWO MgtDataData

ExtractExtract

CustomerCustomerCallsCalls

ManualManualTLTL

DOTDOT DOTDOT Courier toCourier to

DOTDOTDataData

Mass TransMass Trans

RidershipRidershipDataData

RPCRPC

TrafficTrafficCountsCounts

ExtractExtractDOTDOTDataData Apple Co.Apple Co. ExtractExtract ExtractExtract

Activity Diagram: All roads lead to JerryActivity Diagram: All roads lead to Jerry

FinancialFinancialExtractExtract

WO MgtWO MgtExtractExtract

411411ExtractExtract•• How durable is this process?How durable is this process?ExtractExtract

CIP InvoiceCIP InvoiceDataData

ExtractExtract

WO MgtWO MgtDataData

ExtractExtract

CustomerCustomerCallsCalls

•• How durable is this process?How durable is this process?

•• How has it evolved?How has it evolved?

ManualManual

•• How frequently does this need to run?How frequently does this need to run?

TLTL•• Can Jerry…Can Jerry…–– Take a day off?Take a day off?–– Go on vacation?Go on vacation?

DOTDOT DOTDOT Courier toCourier to

DOTDOTDataData

Mass TransMass Trans

RidershipRidershipDataData

RPCRPC

TrafficTrafficCountsCounts–– Win the lottery?Win the lottery?

•• What about Jerry’s “Day Job”?What about Jerry’s “Day Job”?ExtractExtract

DOTDOTDataData Apple Co.Apple Co. ExtractExtract ExtractExtract

•• What about Jerry s Day Job ?What about Jerry s Day Job ?

Why have many interoperability projects Why have many interoperability projects failed in the past?failed in the past?failed in the past?failed in the past?

•• Existing systems likely had few interoperability requirementsExisting systems likely had few interoperability requirementsg y y p y qg y y p y q

•• Technical issuesTechnical issues–– Structure and content of different systems are differentStructure and content of different systems are different

S l ti “t th” f ( d i i )S l ti “t th” f ( d i i )–– Selecting one “truth” from many (and gaining consensus)Selecting one “truth” from many (and gaining consensus)–– Even new solutions that have “standard interfaces” to interoperate with Even new solutions that have “standard interfaces” to interoperate with

other systems will not have the power to align data sourcesother systems will not have the power to align data sources–– Interfaces to legacy systems Interfaces to legacy systems –– scope scope gallop!gallop!

•• The issues are more than technicalThe issues are more than technical–– PolicyPolicy–– ProcedureProcedure–– Influence & controlInfluence & control

•• Funding Funding -- Interoperability occurs in the space between systems… and Interoperability occurs in the space between systems… and projectsprojectsprojectsprojects

CMU SEI: System of Systems InteroperabilityCMU SEI: System of Systems Interoperability(SOSI)(SOSI)(SOSI)(SOSI)

•• System Activities ModelSystem Activities Model –– Beyond the business caseBeyond the business case•• System Activities Model System Activities Model –– Beyond the business caseBeyond the business case

•• How does this influence the architecture of the enterprise?How does this influence the architecture of the enterprise?

4 Stages of Architectural Maturity4 Stages of Architectural Maturity

•• MIT Sloan Center for Information Systems ResearchMIT Sloan Center for Information Systems ResearchS oa Ce te o o at o Syste s esea cS oa Ce te o o at o Syste s esea c

•• Stage 1: Business SilosStage 1: Business Silos•• Stage 2: Standardized TechnologyStage 2: Standardized Technology•• Stage 3: Optimized CoreStage 3: Optimized Core•• Stage 4: Business ModularityStage 4: Business Modularity

•• The stages are cumulativeThe stages are cumulativeThe stages are cumulativeThe stages are cumulative•• Stages are generally not skippedStages are generally not skipped•• Advancement relies on practices more than technologyAdvancement relies on practices more than technology•• Practices avert risk with increasing maturityPractices avert risk with increasing maturity

•• An enterprise is more likely to mature in pieces rather than as a whole.An enterprise is more likely to mature in pieces rather than as a whole.

•• Why is this important?Why is this important?•• Why is this important?Why is this important?

Adopting a Solution Development ApproachAdopting a Solution Development Approach

•• Developing solutions inDeveloping solutions inDeveloping solutions in Developing solutions in the context of operations the context of operations is difficultis difficult

Stakeholder needs/Business Processes

•• Mitigate risk during Mitigate risk during requirements analysisrequirements analysis

–– Prototype during Prototype during requirements phasesrequirements phases

Marketplace

Programmatics/Risk

Architecture/Design

requirements phasesrequirements phases

•• Plan iterationsPlan iterations–– Prioritize requirementsPrioritize requirements Inception Elaboration Construction Transition

•• Interoperability occurs Interoperability occurs through focused effort.through focused effort.

pGather and define project scopeSurvey & try COTSPlan for business process changes

Refine, experiment, & select solutionTry & select COTSPrototype business process changes

Implement selected solutionApply & track COTSPrepare for business process changes

Field and support solutionTrack and update COTSChange business process

-- CMU SEI EPIC Phase ChartCMU SEI EPIC Phase Chart

The next day…The next day…

Stakeholder meetingStakeholder meeting

Leveraging EA to clarify requirementsLeveraging EA to clarify requirements

•• Solution VisionSolution Vision •• Impact of projects onImpact of projects on411 Calls411 Calls–– Provide County Senior Provide County Senior

Management with operational Management with operational views of transportation plans views of transportation plans and projectsand projects

–– 411 Calls411 Calls–– Asset/Pavement Management & Asset/Pavement Management &

Internal Work OrdersInternal Work Orders–– Traffic CountsTraffic Counts–– Traffic AccidentsTraffic Accidents

M t it id hiM t it id hi•• Planned ProjectsPlanned Projects•• Active ProjectsActive Projects•• Project StatusProject Status

–– Scope, Schedule, CostScope, Schedule, Cost

–– Mass transit ridershipMass transit ridership–– Temporal ContextsTemporal Contexts

»» Today, week to date, last Today, week to date, last weekend, Calendar Month, weekend, Calendar Month, Season, YearSeason, YearA i t tiA i t ti

–– What is the business value of What is the business value of the solution?the solution?

»» Appropriate aggregationsAppropriate aggregations

the solution?the solution?

–– Identify 3 performance Identify 3 performance indicators that indicate indicators that indicate successsuccess

–– Development ResourcesDevelopment Resources

successsuccess

Leveraging EA to clarify requirementsLeveraging EA to clarify requirements

•• Business ArchitectureBusiness Architecture•• Business ArchitectureBusiness Architecture

Senior Manager• View maps and operational content

GIS Manager•Operations Support (50%)

•Transition GIS tools to PlannersTransportation Planner• Manage transportation plan data for review• Monitor authorization of plan content• Promote authorized plan or project data

Transition GIS tools to Planners• Implement Print on Demand solution•Coordinate training for new users •Provide technical support to new users

•Solution Development Support (50%)p p j• Retire unneeded plan and project content

Solution Development Support (50%)•PM for GIS projects•Provide domain expertise in solution design activities •Design and Develop Data Models

Database & Systems Administrators• Monitor enterprise databases (O&M) Design and Develop Data Models

• Design and Develop GIS processes• Guide web application development•GIS Solution Governance

Monitor enterprise databases (O&M)• Support development

Enterprise Architect• Solution guidance and coordinationSolution guidance and coordination

Change Management Plan

Leveraging EA to clarify requirementsLeveraging EA to clarify requirements

•• Data ArchitectureData Architecture•• Data ArchitectureData Architecture–– Databases of RecordDatabases of Record

•• Where each “truth” to be presented by the solution will come fromWhere each “truth” to be presented by the solution will come from–– Data modelsData modelsData modelsData models

•• Source DataSource Data•• Transformation RequirementsTransformation Requirements•• Production Database(s)Production Database(s)

–– Administrative DataAdministrative Data–– Mobile DataMobile Data–– Business ContentBusiness Content–– Publication ContentPublication Content–– Base map contentBase map content

–– Web service schemasWeb service schemas•• Content & StandardsContent & Standards

–– MetadataMetadata

Leveraging EA to clarify requirementsLeveraging EA to clarify requirements

•• Application ArchitectureApplication Architecture•• Application ArchitectureApplication Architecture–– Web consumerWeb consumer

•• ArcGIS Server Flex applicationArcGIS Server Flex application–– Web service consumerWeb service consumer

–– Web Service DesignWeb Service Design•• Map services (cached, dynamic)Map services (cached, dynamic)•• LocatorsLocators•• GeoprocessingGeoprocessing

–– Domain Application Admin (Transportation Planner)Domain Application Admin (Transportation Planner)•• ArcGIS Desktop (initial)ArcGIS Desktop (initial)

W b li ti / P i t O D dW b li ti / P i t O D d blitblit ( t l)( t l)•• Web application w/ Print On Demand Web application w/ Print On Demand capablitycapablity (eventual)(eventual)–– Mobile SolutionsMobile Solutions

S l ti D l t RS l ti D l t R–– Solution Development ResourcesSolution Development Resources

Leveraging EA to clarify requirementsLeveraging EA to clarify requirements

•• Technology ArchitectureTechnology Architecturegygy–– Where is the prototype running now?Where is the prototype running now?

•• Jerry’s operational server?Jerry’s operational server?

–– Need to formalize solution development, test, and production resourcesNeed to formalize solution development, test, and production resourcesp , , pp , , p

–– Tailor the system for appropriate performance, availability, scalabilityTailor the system for appropriate performance, availability, scalability•• What are the needs today?What are the needs today?•• What do you expect in 6What do you expect in 6--12 months?12 months?y py p•• What can you expect over the next several years?What can you expect over the next several years?•• Consider computing Consider computing andand network performancenetwork performance•• Plan ahead.Plan ahead.

S i iS i i–– Security requirementsSecurity requirements•• Initial implementation will be intranet onlyInitial implementation will be intranet only•• Working with external agencies (DOT’s web services)Working with external agencies (DOT’s web services)•• What about public participation?What about public participation?

Implications for system configurationImplications for system configuration•• Implications for system configurationImplications for system configuration

Prioritize. Develop an Iteration PlanPrioritize. Develop an Iteration Plan

Rational Unified Process: Resource AllocationRational Unified Process: Resource Allocation

Development Process ConsiderationsDevelopment Process Considerations

•• Mitigate risk while gathering requirementsMitigate risk while gathering requirements•• Mitigate risk while gathering requirementsMitigate risk while gathering requirements–– Requirements cost least when capturing them matters mostRequirements cost least when capturing them matters most

•• Design: $1Design: $1•• Development: $10Development: $10Development: $10Development: $10•• Testing: $100Testing: $100•• Production: $1000Production: $1000

–– Allocate resources for prototypingAllocate resources for prototyping•• COTS, Open Source CustomCOTS, Open Source Custom•• You are responsible for the operation of your solutionYou are responsible for the operation of your solution•• Products were designed with requirements in mind, but not Products were designed with requirements in mind, but not allall of your of your

requirementsrequirementsrequirementsrequirements•• It’s easier to predict the behavior of complex systems through trial and errorIt’s easier to predict the behavior of complex systems through trial and error

•• Test rigorouslyTest rigorouslyConfidence is the best way to win advocacy of highConfidence is the best way to win advocacy of high profile audiencesprofile audiences–– Confidence is the best way to win advocacy of highConfidence is the best way to win advocacy of high--profile audiencesprofile audiences

GovernanceGovernance

•• In DevelopmentIn Development•• In DevelopmentIn Development–– Configuration ManagementConfiguration Management

•• Baseline development environmentBaseline development environment–– OS, Software, HardwareOS, Software, Hardware, ,, ,–– External system dependenciesExternal system dependencies

•• Documentation (yes, documentation)Documentation (yes, documentation)

•• In Operations and MaintenanceIn Operations and Maintenance–– Understand dependenciesUnderstand dependencies–– Manage transition of new or evolved capabilities from developmentManage transition of new or evolved capabilities from development–– Provide feedbackProvide feedback

Candidate Solution ArchitectureCandidate Solution Architecture

WebWebUserUser

WebWebUserUser

WebWebUserUser WebWeb

UserUser WebWebUserUser

RemoteRemoteSystemSystem

Web ApplicationWeb Application(Flex, Custom)(Flex, Custom)

MobileMobileGISGIS

DesktopDesktopGISGISUserUser

UserUser UserUser

(Flex, Custom)(Flex, Custom)UserUser

ArcGIS ServerArcGIS Server CustomCustomWeb ServicesWeb Services

ScheduledScheduledTasksTasks

PubPubGDBGDB

AdminAdminGDBGDB

MobileMobileGDBGDB

AppAppDBDB

Bus.Bus.ContentContent

GISGISAdminAdmin

Best PracticesBest Practices

•• Decide on your operating modelDecide on your operating model -- set expectationsset expectationsDecide on your operating model Decide on your operating model set expectationsset expectations•• Separate Development from Ops & MaintenanceSeparate Development from Ops & Maintenance•• Build solutions iterativelyBuild solutions iteratively•• Manage Change (Governance & Solution Portfolio Management)Manage Change (Governance & Solution Portfolio Management)g g ( & S g )g g ( & S g )•• Consider Solution Architectural MaturityConsider Solution Architectural Maturity

–– Silo, Standardization, Optimized Core, Business ModularitySilo, Standardization, Optimized Core, Business Modularity–– Cumulative, not exclusiveCumulative, not exclusive–– Cultural appreciation of Architectural Maturity is importantCultural appreciation of Architectural Maturity is important

•• Practices in development are as important as those in O&MPractices in development are as important as those in O&M•• Business Case DevelopmentBusiness Case Development

I ROI th I t d th RI ROI th I t d th R–– In ROI, the I must precede the RIn ROI, the I must precede the R–– Identify your RsIdentify your Rs

•• Interoperability happens because you “will it” into existenceInteroperability happens because you “will it” into existence•• Interoperability happens because you will it into existenceInteroperability happens because you will it into existence

ESRI Solution ApproachesESRI Solution Approaches

•• Embrace established GIS and IT practicesEmbrace established GIS and IT practicespp–– A lot of lessons to learn fromA lot of lessons to learn from

•• Be pragmaticBe pragmatic–– Realizing you vision will take timeRealizing you vision will take timeg yg y–– Take deliberate & methodical stepsTake deliberate & methodical steps

•• Change can be challengingChange can be challenging–– The practice of GIS is changingThe practice of GIS is changingp g gp g g–– Technological advancesTechnological advances–– More information available in digital form than ever beforeMore information available in digital form than ever before–– Greater demand across organizations to access, apply, interact with, & transact Greater demand across organizations to access, apply, interact with, & transact

upon informationupon information

•• Introducing technology that changes the way people work and changes Introducing technology that changes the way people work and changes organizational behaviororganizational behavior

–– In addition to the roles of others, your role may also need to evolveIn addition to the roles of others, your role may also need to evolve

ESRI Guidance: PatternsESRI Guidance: Patterns

Data Data ManagementManagement

Planning &Planning &AnalysisAnalysis

WorkforceWorkforceOptimizationOptimization

OperationalOperationalAwarenessAwareness

CustomerCustomerContactContact

A Complete Integrated SystemA Complete Integrated SystemStore, manage, & Store, manage, &

maintain maintain accurate data accurate data

recordsrecords

Get information Get information Into and out of Into and out of

the fieldthe field

Transform data Transform data into actionable into actionable

intelligenceintelligence

Support for Support for decision makers decision makers

& knowledge & knowledge workersworkers

Disseminate Disseminate knowledge & knowledge &

gain consensus gain consensus

A Complete Integrated SystemA Complete Integrated System

recordsrecords workersworkers

DesktopDesktop ServerServer OnlineOnlineMobileMobile

ESRI Online ResourcesESRI Online Resources

•• ESRI Enterprise Resource CenterESRI Enterprise Resource Center•• ESRI Enterprise Resource CenterESRI Enterprise Resource Center–– Application ArchitecturesApplication Architectures–– SecuritySecurity

Performance and ScalabilityPerformance and Scalability–– Performance and ScalabilityPerformance and Scalability

•• Transportation Data ModelTransportation Data Model

ESRI Press BooksESRI Press Books

•• Thinking About GISThinking About GIS•• Thinking About GISThinking About GIS–– Guidance remains relevantGuidance remains relevant

•• Building a GISBuilding a GISSystem Design GuidanceSystem Design Guidance–– System Design GuidanceSystem Design Guidance

•• Modeling Our WorldModeling Our World–– Techniques for designing Techniques for designing geodatabasesgeodatabases

•• Designing Designing GeodatabasesGeodatabases for Transportationfor Transportation–– DomainDomain--focused design guidancefocused design guidance

DiscussionDiscussion

The DinerThe Diner

Solution ApproachesSolution Approachespppp&&

Best Practices forBest Practices forEnterprise InteroperabilityEnterprise InteroperabilityEnterprise InteroperabilityEnterprise Interoperability

Thank you!Thank you!

Jim VanOstenbridgeJim VanOstenbridgeEnterprise ConsultantEnterprise ConsultantEnterprise ConsultantEnterprise Consultant

ESRI Professional ServicesESRI Professional Services