Building an Enterprise Data Portal

Agenda  The basics  What is a portal  SOA Primer  The supporting pieces  Putting the pieces together  Why build it  Thinking of the future  With a sprinkle of case studies throughout

What is a Portal???  Wikipedia – “A web portal is a site that provides a single function via a web page or site. Web portals often function as a point of access to information on the World Wide Web. Portals present information from diverse sources in a unified way…”World Wide Web

What is a Portal???  My definition: “An easy-to-use, one-stop-shop, for geographic data.”  Information repository  Geospatial  Textual  Search engine  Map viewer  Service Provider  Web  Data  Download/Retail???

A Visual Primer on SOA

Let’s Take Geek Speak Out of the Equation  The Players  You the customer (client)  The espresso machine (system)  The barista (enterprise service bus)  The Problem  A couple of years ago Starbucks started upgrading the espresso machines  The Order  “Quad venti non-fat, no-whip, 170° white mocha”  The Beauty of it all  Did you have to change how you ordered because the espresso machine was upgraded?  No. The order was abstracted from the “making” via a service layer (barista)

The supporting pieces

Metadata services  Probably the most overlooked part of standing up an enterprise GIS  Most people create metadata  Few implement a metadata server  Highly critical to data sharing  Internal  External  Inter-organization

Metadata services

Map Viewers

Web Services Customer Call Find Address Forward Call Dispatch Crew Create Workorder Close out Send GIS FindAddress UpstreamTrace CRM LogCall AssignCall CMMS AuthorizeWor k ChargeLabor CreateReport Billing SendBill ChargeCC ReceiveParts Service Layer (Security, Orchestration, Scalability) …and so on

Web Servers  OGC  KML

Data retrieval/Retail

Putting the pieces together MetadataVisualization Web Services/ Web Servers Data Retrieval Enterprise Portal

Why (from a business perspective)???  To better server your customers  Assistance finding data of interest  Visual access to geospatial information  Provide direct access to routinely updated data  OGC  KML  Ability to download/purchase data  Save time/money View Query Print Identify

Why (from a technology perspective)???  It’s the right architecture  Systems communicate when it makes sense so they aren’t joined at the hip  It’s modular  Systems are tied together at the points where it makes sense, not across the board  It’s standards based  Stop writing custom code that is not reusable, or at least is less prone to “rev-locking”  Hide complexity rather than introducing it  It means your solutions…  Can more easily grow and evolve with our information systems  Can more easily and reliably be expanded to additional information systems

Thinking of the future  Adopting to users needs  Constantly changing  Increasingly complex  Building demand  Accepting of change  More access to data  Less inter-personal interaction  Getting it right the first time  …and the second time  …and the third time

Who wins???

Who we’ve implemented it for  City of Phoenix, Sky Harbor International Airport  City of Bellingham, WA  US Army Corps of Engineers, Mobile District  Paulding County, GA  Arizona High Intensity Drug Trafficking Area, AZ  City of Indianapolis, IN  City of Miami, FL

Any questions???