1 / 38

Evaluating the Potential of Commercial GIS for Accelerator Configuration Management

Evaluating the Potential of Commercial GIS for Accelerator Configuration Management. T. Larrieu, Y. Roblin, K. White, R. Slominski Jefferson Lab, Newport News, VA 23606, USA. Jefferson Lab has a Large and Complex Infrastructure. CEBAF ( 24/7 electron utility ) 7 km of beamline

kent
Download Presentation

Evaluating the Potential of Commercial GIS for Accelerator Configuration Management

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. Evaluating the Potential of Commercial GIS for Accelerator Configuration Management T. Larrieu, Y. Roblin, K. White, R. SlominskiJefferson Lab, Newport News, VA 23606, USA

  2. Jefferson Lab has a Large and Complex Infrastructure • CEBAF ( 24/7electron utility ) • 7 km of beamline • 2000+ magnets & power supplies • 338 5kW klystrons • 42 Cryomodules each with 8 RF cavities • 400,000L Low Conductivity Water system • A 2K helium refrigeration plant • 65,000 I/O Control Points • 250,000 EPICS records, 140 IOCs, 80 Unix hosts

  3. So does Salt Lake City, Utah… • Water Utility District • 29 pump stations with 104 pumps • 1,400 miles of pipeline • 15,000 valves • 8500 Hydrants • 48,000 wastewater connections • 181,000 customers

  4. Or Sacramento, California… • Municipal Electrical Utility District • 900 square miles service area • 553,337 customers • 10 Transmission bulk substations • 500 circuit miles of Transmission lines • 9,885 circuit miles of Distribution lines

  5. The Premise Most Utility Companies use Geographic Information Systems (GIS) to operate and manage their large and complex infrastructure networks. According to American Waterworks Association 90% of water agencies now use GIS at least partially in their daily operation

  6. What is GIS? A GIS is a computer system capable of capturing, storing, analyzing, and displaying geographically referenced information; that is, data identified according to location. Practitioners also define a GIS as including the procedures, operating personnel, and spatial data that go into the system. *Source USGS Geographic Information Systems Poster http://erg.usgs.gov/isb/pubs/gis_poster/

  7. GIS Software (General) • Database View • A GIS is a structured database that can describe the world spatially. • Map View • A GIS is a set of intelligent maps and other views that show features and feature relationships spatially • Model View • A GIS is a set of information transformation tools that derive new datasets from existing datasets.

  8. Utility GIS Usage Examples • Inventory (mains, valves, hydrants, meters, etc.) • Water distribution system master planning • Population and demand projections • Groundwater management/modeling • Water quality monitoring • Hazardous materials tracking • Site analysis • Development review and approval • Right-of-way engineering • Water flow analysis • Automated mapping • Capital improvement project tracking • Underground service alert

  9. Analagous (Possible) JLAB GIS Usage • Inventory (iocs, camac crates, power supplies, etc.) • Configuring online model server • 12 GeV upgrade planning/tracking • Hazardous materials tracking • Radcon tracking/mapping • Environmental Regulatory Compliance • Fault analysis • Spatial selection & display of PVs

  10. Commercial GIS vendors *Source GISmonitor, November 7, 2002, http://www.gismonitor.com/articles/comment/110702_Daratech.php

  11. GIS Software (ArcGIS) • Data Management Tools • (Geo)Database • CAD File Integration • UI Tools • View/Query • Add/Edit data • Other • SDK • Tracking Server/Analyst • Schematics

  12. Geodatabase sits on RDBMS *Source M. Zeiler, “Modeling our World” ESRI Press, Redlands, CA 1999

  13. Geodatabase Versioning • Conceptually similar to CVS • Version is named state of geodatabase • Multiple versions can coexist • A user can connect to any version • Differences between versions can be merged/reconciled

  14. Versioning Benefits • Could create named versions at useful savepoints such as the completion of an experiment, or just prior to or following a maintenance period. • Tables containing CAD objects, software configuration info, Optics could all be versioned consistently.

  15. Spatial Indexes & Operators • Allow efficient queries based on geometric relationships such as proximity, adjacency, and overlay. • Select Objects that: • intersect • are within a distance of • contain • are contained by • share a line Segment with • crossed by outline of • have their center in

  16. Via ArcObjects (Microsoft COM) Available in the Unix SDK via MainWin As Simple Features (ArcSDE) Java & C APIs • Via SQL • Provided by RDBMS vendor *Source M. Zeiler, “Modeling our World.” 199pp., Environmental Systems Research Institute, Redlands, CA, 1999.

  17. CAD drawings have limitations: CAD Files • Engineering staff who maintain drawings must be notified to make changes by installers or Survey & Alignment team. • Changes to the as-built drawings are made separately from changes to software configuration and physics models. • The CAD drawings are tiled. • The CAD annotation is static.

  18. ArcGIS can Integrate CAD • Option 1 - Use entire file as a layer. • Option 2 - Decompose the CAD file and import its contents into geodatabase. • Objects now stored in DB can be extended with additional attributes. • Can be joined/related to other DB tables. • Can be used to generate new CAD files, not constrained to tiling, labelling of original.

  19. CAD Superimposed on Magnet Centers obtained from Survey & Alignment

  20. Overlay CAD on Alignment Magnet Centers

  21. User Interfaces • Data Source Management (ArcCatalog) • Usable by non-programmers • Wizard-like toolboxes Import/Export/Convert etc. • Graphical Display (ArcMap) • View/Display Data Layers • Search/Query Data • Add/Edit Data

  22. ArcCatalog

  23. ArcMap Display

  24. ArcMap Query

  25. Beamline Editing w/ArcMap

  26. Beamline Editing OptiM Style

  27. Tracking Server We could write a CA plugin… Realtime display of spatially-selected PVs. Playback archiver data super-imposed over as-built drawings to give context. http://www.esri.com/trackingserver

  28. Schematics • Select a magnet and on-the-fly generate a schematic of all magnets, shunts, and shunt-adders in its circuit. • Select a rack containing Camac crate and click to generate a schematic showing logical connectivity of iocs, gpib devices, serial devices, and cables http://www.esri.com/schematics

  29. Benefits • Highly functional UI without custom programming. • Complementary to non-spatial database-building efforts (à la IRMIS). • Location-awareness fits operational goal of region-centric rather than system-centric control system. • Potential to manage controls, engineering, and model data consistently.

  30. Drawbacks • The software is not free. • The software might be overkill. • There is limited Prior Art to emulate.

  31. Exploratory Project • Use ArcGIS and Geodatabase for configuration of new Art++ model server • Import data from OptiM, DIMAD, and CAD • Maintain/Update in Geodatabase • Export Up-to-date layout & element properties to Art++

  32. Exploratory Project

  33. No problem importing Optim, DIMAD

  34. Importing CAD - Troublesome • Songsheets in arbitrary drawing units. • Must open each, define pair of matchpoints to correlate drawing coordinates to accelerator coordinate system. • Songsheets make no use of layers. • Cross-section, plane-view, annotation, and page template are all intermingled in a single drawing layer, • Elements are all lines, not polygons. • Processing is required to merge related lines into a single geodatabase polygon object. • Annotation is simply written onto page. • Not attached to elements as Xdata

  35. But Exploration Can Proceed • Interface for Model Server to Read GIS • Geodatabase  AML  Art++ • Work around or fix CAD limitations • Heads-up digitizing of some components • Collaborate with ME to update standards • Outsource retrofit of old drawings? • Work on additional layers • Control System Data for example (IRMIS)

  36. Summary • The ArcGIS software appears to be a capable framework to consistently manage Engineering, Controls, and Optics data. • The ability to buy a ready-made interface for displaying, querying, and analyzing data could free us to concentrate on data and processes rather than GUI development.

  37. “The application of GIS is limited only by the imagination of those who use it”. Jack Dangermond, founder of ESRI

More Related