Revised Business Plan Revised Business Plan Presented to the DC - PowerPoint PPT Presentation

Slide 1 DC GIS Strategic and Business Planning: Revised Business Plan Revised Business Plan Presented to the DC GISSC August 4, 2009

Slide 2 Wordle View

Slide 3 DC GIS Business Planning: Steps g p � Form Business Plan Subcommittee (BPS) at GISSC meeting (end of May 2009) meeting (end of May 2009) � Share draft document with BPS (start of June 2009) � Schedule teleconferences and meetings to get g g feedback and input from BPS and OCTO staff (June- July 2009) � Refine draft and derive presentation to make at next � R fi d ft d d i t ti t k t t GISSC meeting (August 4, 2009) o Provide Final Draft Business Plan document for o Provide Final Draft Business Plan document for GISSC Budget Meeting (September 2009) o Finalize Business Plan based on Budget Meeting

Slide 4 DC GIS Business Planning: Four-Month Schedule

Slide 5 DC GIS Business Planning: Background � We got a head start in 2008 with DC GIS Staff � Preliminary planning focused Data Applications Preliminary planning focused Data, Applications, and Services (i.e. Goals #2 and #3 from Strategic Plan) � � Develop and operate enterprise mapping data Develop and operate enterprise mapping data, geospatial applications, and Web services that enhance the utility, reduce the cost, and expand the interoperability of citywide and agency IT systems � Provide outstanding customer service and training that enable DC GIS users and stakeholders to leverage the full power of GIS technology � P Participatory: GISSC represented by Business Plan ti i t Subcommittee (BPSubcom)

Slide 6 DC GIS Business Planning: Portfolio Mgt � Applying “Portfolio Management” � � Projects have different life-cycles and Projects have different life-cycles and investment strategies: � Invest (build or enhance) � Maintain (provide basic support) • Keep status quo/minimal investment • Version upgrades only • Version upgrades only • No active development of new capabilities � Sunset (migrate toward retirement & end-of-life) ( g ) � Migrate (move to – or “reinvent” on – a new platform) � � Divest (shut off spending and “kill it”) Divest (shut-off spending and kill it )

Slide 7 DC GIS Business Planning: Platforms � A platform is: � A base technology (or technologies) on which � A base technology (or technologies) on which other technologies or processes are built � A whole “economic unit” for the purposes of aggregating and assessing costs for budget purposes

Slide 8 DC GIS Business Planning: Program Elements � Data � Applications & Web Services (Dev & Sys) � Applications & Web Services (Dev & Sys) � Customer Service

Slide 9 OCTO GIS Budget Allocation (Approximate) Program Element Percent of OCTO GIS Budget * g Data 34% Applications & Web pp 42% Services (Dev & Sys) Customer Service 17% Other (Admin, Supplies, 7% Dues) T t l (Mi Total (Mix of Cap. and Op. f C d O 100% 100% Funding) * Does not include stand-alone capital projects

Slide 10 DC GIS Data Platforms 1) Photogrammetric 6) Routing (pedestrian, vehicular, & mass transit) a) Orthoimages 7) 7) Aerial Oblique Imagery Aerial Oblique Imagery b) Planimetrics b) Planimetrics 8) Business Data c) Impervious Surfaces 9) LiDAR d) Elevation 10) Regional Data e) 3D Buildings 11) 11) Dynamic Data D i D t 2) Property 2) P t 12) Partner Data a) VPM 13) Utilities Data b) MAR 14) ) All Other c) Zoning ) g a) OCTO Maintained d) Planning b) Agency Contributed e) ROW f) Survey 3) Demographics 3) Demographics 4) Ground Imagery 5) Transportation

Slide 11 Data Platform Investment Strategies Data Type Investment Data Type Investment Strategy Strategy � Photogrammetric � Photogrammetric � Business Data � Business Data Maintain/Invest in Maintain/Invest in Invest Invest next cycle � Property � LiDAR Invest Invest � Demographics � Regional Data Invest Maintain � Ground Imagery � Dynamic Data TBD Invest � Transportation � Partner Data Maintain Maintain � Routing � Utilities Invest Invest � Aerial Oblique � All Other Maintain Maintain Imagery

Slide 12 DC GIS Application Platforms 10) MAR 1) Google Maps 11) ArcGIS Server (and 2) ) Google Earth g E t Extensions) i ) 3) Citrix 12) Oracle 4) EFS (Pictometry Family) 13) RouteSmart 14) VM Ware (OCTO 5) ArcGIS Desktop Environment) 6) ArcIMS 15) ) ArcPAD 7) 7) DC G id DC Guide DB DB 16) Others? 8) DC Guide WS 9) 9) DC Guide Link DC Guide Link

Slide 13 Application Platform Investment Strategies Platform Type Investment Platform Type Investment Strategy Strategy � Google Maps � Google Maps � Route Smart � Route Smart Invest Invest Invest Invest � Google Earth � Oracle RDBMS Invest Maintain � EFS (Pictometry � EFS (Pictometry � VM Ware � VM Ware Maintain Maintain Maintain Maintain Family) � ESRI ArcGIS � DC Guide DB Maintain Sunset Desktop � ESRI ArcIMS � DC Guide WS Sunset Sunset � ESRI ArcGIS � DC Guide Link Maintain Sunset Server (and ext ) Server (and ext.) � ESRI ArcPad � Citrix Maintain Maintain

Slide 14 Data Wish List c/o BP Subcommittee (1 of 3) 1) Maintain the current set of widely used data layers, for users of both ESRI and Google technologies and applications 2) Add OGC style web services to data offerings 3) Determine the level of essentialness of each layer 3) Determine the level of essentialness of each layer by monitoring demand and identifying application dependencies and willingness to cost-share when sensible sensible 4) Budget for recurring investment in data acquisition to update planimetric layers (e.g. photogrammetric flyovers to acquire new imagery should occur every flyovers to acquire new imagery should occur every two years; once the data is acquired, it needs to be maintained and distributed to DC GIS stakeholders that depend on it) that depend on it)

Slide 15 Data Wish List c/o BP Subcommittee (2 of 3) 5) Assess the update frequency required for other essential layers, since this is a cost-driver (i.e. for major data platforms should update frequency be major data platforms, should update frequency be increased, or decreased?) 6) Develop and refine data to support routing applications (e g oversized vehicle routing delivery applications (e.g. oversized vehicle routing, delivery of meals, trash pick-up, and property assessments); currently, multiple departments are in need of fully routable street networks, and there is a risk of , duplication of effort in acquiring suitable data sets 7) Complete the cadastral fabric needed for the District (i.e. property maps) and resolve ‘fitting’ ( p p y p ) g issues vis-à-vis what has been surveyed 8) Research the creation of photo-realistic building textures

Slide 16 Data Wish List c/o BP Subcommittee (3 of 3) 10) Strengthen methods of notifying data subscribers of changes subscribers of changes 11) Investigate geospatial data availability and suitability for areas adjacent to the District suitability for areas adjacent to the District 12) Monitor and investigate public data for usefulness and relevance to the District use u ess a d e e a ce to t e st ct (e.g. geo-tagged photos) 13) Support Utility and ROW data collection ) pp y and data management efforts

Slide 17 Application Wish List c/o BP Subcommittee (1 of 2) 1) As mentioned in the context of data, routing is emerging as a much needed application across many departments , and initiatives in this direction need to be coordinated and leveraged initiatives in this direction need to be coordinated and leveraged for maximum benefit to the enterprise 2) In addition to routing, new applications and/or integration to routing are needed to support mobile computing, green g pp p g, g buildings, tracking and dispatching 3) No new applications will be built on ArcIMS; it is being sunset by the vendor (ESRI) 4) Numerous applications are currently deployed on ArcIMS, which is a platform in its latter life stage; it would be disruptive to cease support for ArcIMS, but a migration strategy is needed for the applications and/or functionality currently in use including DC applications and/or functionality currently in use, including DC Guide and DC Atlas, to move or re-factor onto a new platform

Slide 18 Application Wish List c/o BP Subcommittee (2 of 2) 5) There are not enough resources to migrate everything in lock-step, so prioritization is needed y g p, p to designate the primary candidates; the Subcommittee consensus is that DC Guide Web Services and DC Atlas will be the first to migrate Services and DC Atlas will be the first to migrate and/or reinvent onto a new platform; there are Web services linked to DC Guide that also need to be migrated, before the current version of DC Guide can i t d b f th t i f DC G id be shut down 6) Applications that are not scheduled for migration 6) Applications that are not scheduled for migration and/or re-factoring will be left running on ArcIMS for the time-being, with minimal support