1 / 28

Pilot Study of a Configuration Management Application in a GIS Environment November 28, 2006

Montgomery County, Maryland Department of Technology Services (DTS) Geographic Information Systems (GIS). Pilot Study of a Configuration Management Application in a GIS Environment November 28, 2006 ESRI Mid-Atlantic User Group Conference 2006. Presentation Outline. Introduction

eithne
Download Presentation

Pilot Study of a Configuration Management Application in a GIS Environment November 28, 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Montgomery County, MarylandDepartment of Technology Services (DTS)Geographic Information Systems (GIS) Pilot Study of a Configuration Management Application in a GIS Environment November 28, 2006 ESRI Mid-Atlantic User Group Conference 2006

  2. Presentation Outline • Introduction • GIS Organization • Customer – Public Safety 911 • Issues and Challenges (for GIS and CM) • Configuration Management Overview • CM Processes and Fundamentals • Software Development versus Data Management • CM Application in a GIS Environment • Implementation • Process Improvements for GIS and CM • Parallel Development and Repeatable Processes • Improved Quality Control and Quality Assurance • How You Can Get Started • For GIS CM and GIS Industry Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  3. Chief Information Officer (CIO) Alisoun Moore Chief Technology Officer (CTO) Mike Knuppel Enterprise Applications Enterprise Services Enterprise Infrastructure Telecommunications • Project Requirements • Application Development • “e-Montgomery” • Enterprise Systems Services • Geographic Information Systems (GIS) • Client Computer Support • Help Desk Services • Server Support • Public Safety Support (24/7 DTS Support) • Host Operations • Data Security • Fibernet / Wide Area Network (WAN) Support • Telephone Services • 800 Mhz Radio Management and Repair • Engineering Services MCG Department of Technology Services • Also, Other Departments and Agencies May Have Small Technology Teams as Well • Health and Human Services (HHS) • Department of Liquor Control (DLC) • Department of Finance • Department of Public Works and Transportation (DPWT) Decentralized Technology Teams Across County Government; Often use Workgroups to Enable Teamwork and Collaboration Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  4. County-wide GIS Services • GIS Team • 14 GIS Specialists • 8 Servers • 90+ Databases • 200+ Layers • Services • Produce Maps for County • County and Enterprise -Wide Geospatial services (Web, Geo databases) • Special projects • Board of Elections • Board of Education • Public Safety • Etc. • The Customer – Public Safety • Public Safety Data System (PSDS) • Emergency 911 System • Data Center Operations • 24 X 7 • Police and Fire/Rescue Geo Data • Critical Data • Maps in all Police Cars & Fire Apparatus, Stations • Dispatch • Vehicle Routing • Address Verification & Location Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  5. Operational GIS Process, Procedures Social Comfort Zones Data Nature of Geo Data Changing, Growing Database Integrity Missing, Null fields Data Accuracy Wrong police beat assignments Issues and Challenges • System Complexity(Business Systems vs. GIS Systems) • Mainframe: Traditional, tabular, data entry, long time • GIS: New, non-traditional, complex, constantly changing, no long-term testing • Public Safety Data • Data Experts and Specialists • In GIS, not Public Safety • Nature of Data • Public Safety in Infancy stage Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  6. Institutionalize Begin to Adapt Commitment Trial Use Understanding Time Phases of Commitment Awareness Carnegie Mellon University, Software Engineering Institute (SEI), from D.R. Conner and R.W. Patterson “Building Commitment to Organizational Change”, Training and Development Journal, 18-30; April 1982. Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  7. Receptiveness to New Technology Carnegie Mellon University, Software Engineering Institute (SEI), from E.M. Rogers “Diffusion of Innovation”, Free Press, New York, NY; 1983. Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  8. Configuration Management • Engineering Discipline • Processes and technologies to identify and control items • Engineering, Software Development, IT fields • Standards: DOD, MIL, IEEE, ISO… • What is CM? • Identification of the system being created or released • Control over the items making up the system and changes to the system • Auditing and analyzing what is being created and released • Reporting and tracking events on the system • Where is CM in the GIS field? • Does not exist • No case studies • Little or no resource information Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  9. Identification Identify configuration items of a system Requirements, deliverables, end products, pieces of a deliverable, code, designs, executables, tools, test cases Create a baseline (snapshot) Control Control changes to configuration items Version control, change control, build management (software), release engineering CM Tools CM Fundamentals • Audit • Analyze the baselines and processes • Assign action items for issues and non-compliance • CM Improvement • Status Accounting • Report on events • Systematically collect, record and report meaningful CM data • Measurable, repeatable • Includes metrics, audit results, history, tracking effort, traceability Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  10. Data Production Group GEO Load for PSDS is not Software Development Lifecycle of Software Development is not the same as Data Mgt Spiral Model – maybe CM Tools GIS data managed by GIS software Proprietary database Incompatible tools CM tool like ClearCase cannot recognize the ArcInfo data structures The CM Challenge for GIS • CM Methodologies • Around for Software Development • Shared terminology • Shared culture and discipline Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  11. Software Development CM Processes: exist, tried-tested, improved CM Tools: exist, tried-tested, improved Models, Patterns, Terminology established Data Management CM Processes: No case studies CM Tools: Not created for DM Models: Database Management Models, Data Management Techniques are used Software Development vs. Data Management versus Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  12. GIS Side Formalize Processes Data Management Quality Control / Assurance According to industry AND to department culture Team Receptiveness Automate as much as possible Writing scripts; documenting expert procedures Leverage in-house expertise Ensure 100% Data Integrity Goes back to issues with missing fields, links, keys or null values What Can Be Done? • CM Side • Match CM concepts to GIS processes • Identification of layers, modules • Control changes at high level • Report on changes per release • Establish business rules to enforce CM concepts • Apply CM tools where applicable • Problem Management • Version Control • Scripts and automated QC tools • SQL stored procedures • Not for layers or workspaces • Maybe for workspace baselines Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  13. Improvement Goals Decrease Mean Time Between Deliveries Frequent deliveries = better QC and management of changes Error fixes manageable per delivery Establish Release Dates Consistent delivery schedule increases customer satisfaction, trust and manages expectations Don’t keep customer waiting Always know when new Geo Data is arriving QC Automation Catch systematic errors with tool Decrease manual labor efforts Configuration & Process Management for GIS Public Safety Requires Frequent Updates to Map & Geo Data • GIS Data Management Process • Formalize the Process • GIS has control over this process • Re-use current ideas and move forward with progress • Add new process design, make formal procedures, repeatable • Requirements Management • Communication with End-Users on requirements • Quarterly CAB Meetings • Freeze Requirements • Change Control Process for new requirements Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  14. Change Advisory Board (CAB) Quarterly Meetings with Key Personnel DTS GIS DTS Public Safety Support Police Department Fire/Rescue Services Requirements Freeze & Sign-Off Requirements Form Change Management Change Request Form Requirements Changes DTS Issues Tracking System Data Changes Specific Police/Fire Data Changes Data Repositories (Directories) Source Master copy of all layers Owner can copy over data No edits made in source directories Workspace Copy from Source directory to Workspace directory Owner makes edits QA/QC on layer in workspace before copy back to Source Release Final QA/QC on layer(s) to be released Only 1 Owner GIS Manger authorizes release Change Control Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  15. Category# Layers Owner Basemap 22 Lian Census 7 Lian DEM 3 Lian DHCA 1 Lian DHHS 1 Dan Elections 7 Vicky Environmental 7 Lian Finance 3 Lian Fire 14 Vicky Grids 6 Barb Historic 2 Barb Landuse 5 Barb Locations 19 Tim Metadata 177 Lian OCE 10 Carol Category # Layers Owner Orthophotos 6 Apollo Permitting 3 Lian Planning 5 Yanli Police 4 Vicky Political_mc 4 Celina Political_other 1 Celina Property 3 Lian DPW&T 9 Barb Recreation 4 Dan Regional 2 Celina Schools 10 Tim Sheriff 2 Celina Utilities 15 Carol USPS 2 Celina GIS Source Server - Responsibilities Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  16. GIS QC Process GIS QC Process GIS QC Process Release A Release B Release C GIS Data Freeze GIS Data Freeze GIS Data Freeze GIS DM Process GIS DM Process GIS DM Process Mainline Development PS Conversion Process PS Conversion Process PS Conversion Process Public Safety Branch (for delivery only) Release A-PS Release B-PS Release C-PS Parallel Development & Repeatable Process • Repeatable Process • GIS Data Management • Quality Control Process • Automation when possible • Lifecycle of the GIS DM/QC Process – from release to release • Repeat after each GIS product Release • Public Safety Release Process • Consists of a snapshot of the GIS product Release • Conversion process applied • Lifecycle ends with delivery to Public Safety • Repeat upon next GIS Release product • GIS Work on Mainline Branch • Copy from Source to Workspace • Edits Made in Workspace Directory Only • Public Safety Release on PS Branch • Allows for Parallel Working Environment • Data Freeze • Copy from Source to Staging Area (PSDS) • Final QA/QC on ALL Layers • Release Dates Established Quarterly • Regular Intervals, Do Not Change Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  17. CM Implications on GIS System Development Life-Cycle Create Manage Publish Maintain Automated QA/QC in Public Safety Database Development Matching Geo Databases between Development and Production Version Control Data Acceptance QA/QC and Output Process Source Code Revisions Data Preparation Map File Conversion Tiling Output Delivery Automated QA/QC Concept Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  18. GIS Public Safety Data Delivery Process • 1. Data Readiness • Create Data Layer • Topology Check • QA/QC Automation • Arc/Info & GeoDB • Tier 1 – Data Owners • Tier 2 – QC Team • Tier 3 – Final QC • QA/QC Report & Fixes • Agency Owner QA • Police / FRS • Sign off from Customer • Data Freeze • 2. Pre-Conversion • Copy Layers from Source to Staging Area • Add Common Convert Items • Run Convert Tools, AML to Copy Source Fields to Converted Items • Drop Unnecessary Fields (Keep Convert ID#, etc.) • Replace “null” With “.” For Each Converted Layer • QA/QC: Unique ID, Full Population, Null Values • LUT Tables (street type, turn tables, etc.) Data Freeze • 3. Conversion • One AML Calls All Routines • No Menu Selection (no prompts) • QA Conversion Results • e.g., Layer / Feature / Text Conversion • Link With Source Layer to Check Attribute Conversion • 5. Tiling / Output • Automated Tiling • QA Tiled PLP Files Per Subdirectory – Feature Count Must Match by Layer • Public Safety Check List • Public Safety Export List • Notify PSDS Team • Police/FRS On-site Validation • User Feedback • 4. Post-Processing • Single AML to Create ply, lin, pnt files (PLP) • Batch Program to Delete or Create PLP Directories • QA the PLP Output Files; Feature Count by Layer • Batch Program to Move PLP Files to Associated Directories • QA “Clines” Line Files Ready For Release to PSDS Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  19. CM Analysis October 2005 for Public Safety February 2006 for GIS GIS CM Stage Between “Trial Use” & “Begin to Adapt” CM Plan Change Advisory Board (CAB) Requirements Management Change Control Process Issues Tracking (Problem Tickets) Formalized Process Edit/Update Geo Data QA/QC Layers and Databases Streamline Delivery Process CM Tools In-house scripts Forms Issues Tracking System (enterprise-wide) MCG/DTS: GIS CM for Public Safety • CM Tools Needed in GIS Software: • Change Tracker • Versioning of Layers Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  20. Create a CM Plan Use Existing Templates as a Guideline Assessment & Risk Analysis Management Support How Receptive is Team? Start Changing Mindset Now Get Used to Formalized Procedures (such as CM) Establish CAB or CCB Implement Manual Processes for Operations/Business Use CM Tools When Possible: AML, Scripts, Stored Procedures, Documents Use Version Control Forms, Lists, Spreadsheets Track Changes on High Level Excludes: Data Edits, Layer Versioning ** ** Need support from GIS Software vendors Your Roadmap to GIS CM Plan According to Your Organization’s Needs Need Integrated CM Tools in GIS Software CM Acceptance in GIS Industry Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  21. Contact Information • Department of Technology Services (DTS) - GIS 21 Maryland Ave., Suite 350 Rockville, MD 20850-2390 • Enterprise Applications Division, Geographic Information Systems (GIS) • Apollo Teng, GIS Manager • apollo.teng@montgomerycountymd.gov • 240-777-2883 • Yanli Gong, Sr. GIS Specialist • yanli.gong@montgomerycountymd.gov • 240-777-2886 • Enterprise Services Division, Public Safety (PS) • Heba Elbadawi, Public Safety Configuration Manager • heba.elbadawi@montgomerycountymd.gov • 240-773-7234 • Presentation Can Be Downloaded from the DTS GIS Website at • http://www.montgomerycountymd.gov/content/gis/docs/mug06_CM.ppt Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  22. Supplements • CM Plan • Outline Template • Change Advisory Board Process • Flowcharts • Requirements Form (Template) • Release Plan and Schedule (Template) • Change Control Process • Change Request Form (Template) • Issues Tracking - Sample Problem Ticket Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  23. Introduction Purpose CM Overview Scope Definitions, Acronyms, Abbreviations References Management & Organization Organization Responsibilities CM Policy Procedures, Methodology & Tools Configuration Management Process Configuration Identification Identification Methods Labeling Conventions Project Baselines CM Repositories Configuration Control Change Control Change Advisory Board (CAB) Configuration Status Accounting Peer Review CM Status Reports CM Logs and Database Audit and Review Function Configuration Audit (FCA) Physical Configuration Audit (PCA) Project Media Library Vendor / Contractor Control If applicable Resources, Schedules, Points of Contact CM Roll-Out Schedule Geo Data Delivery Plan & Schedule CM Risks and Opportunities Supplemental Information CM Plan Outline (Sample 1) Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  24. Introduction CM Management Organization Responsibilities Project CM Dataset CM Developed Application CM Final Product CM Applicable Policies, Directives, Procedures CM Activities Configuration Identification Identification Methods Naming, Labeling Conventions Acquiring Configuration Items Configuration Control Change Process: Request, Evaluate, Approve, Implement Change Control Board (CCB) Configuration Status Accounting Configuration Audit and Review Function Configuration Audit (FCA) Physical Configuration Audit (PCA) Interface Control Records Inventory Resources and Points of Contact Software Resources Training Requirements in Support of the Plan CM Plan Maintenance References CM Plan Outline (Sample 2) Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  25. Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  26. Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  27. Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

  28. Magic Ticket # 159305 has been assigned to the DTS_GIS group by DTS_PS Incident Number: 159305 Open Date: 7/11/2006 9:36:55 AM Client Name: Trent Bishop Client ID: BISHOT Client Phone: (240)773-7027 Client Department: Police Subject ID: PS_CAD_DATA Subject Description: PS CAD - Data Incident Description: Addressed CADLIVE b 106.2-107.3 / AVS 31.1 Address Discrepancy 1. Flagship Car Wash @ 2100 Chapman Ave, Beat 1A1, Atom 271. Verizon and the MD tax records show the above locations address listed as 975 Rollins Ave not 2100 Chapman Ave. The manager of the business states that he has documentation from Rockville City Planning that the address should be 2100 Chapman Ave. The 2100 Blk Chapman Ave is not in the address server. The range ends at 2099 Chapman Ave. The building footprint is displaying 975 on the map. Please create a CPN for the location when the correct address is established. ____________________ J. Miller, 7/14: On Live - Extended street address range from 2099 to 2199. Added CPN. _____________________ J. Miller, 7/14: GIS Team, please correct street addess range and building footprint as described above. Contact Trent Bishop if you have questions. C. Azevedo, GIS, 9/1/06: The 2100 block is in place on Chapman Ave. and will go into the upcoming delivery. C. Azevedo, GIS, 10/17/06: Checked the converted data. The 2100 block is in place. _____________________________ J. Miller, 10/31: GIS Team: Trent thinks that the building footprint labeled 975 Rollins, should be labeled 2100 Chapman. Please look at this and relabel it if it is labeled incorrectly. If it is labeled correctly, please give Trent a call. DTS_GIS - PS ticket assigned to group Montgomery County, Maryland DTS GIS ESRI-MUG 2006 Conference

More Related