Logo GISdevelopment.net

GISdevelopment > Proceedings > GITA > 2000


GITA 2002 | GITA 2001 | GITA 2000 | GITA 1999 | GITA 1998 | GITA 1997 |  
Sessions

Data development and evolution

Engineering and design applications

Exploiting field and mobile technologies

Invited presentations

It's a brave new world

Leveraging web-based technologies

Mobilizing the enterprise

Operations support

People issues

System architecture

The best of the rest

Uniting the enterprise

User perspectives

Work management solutions



GITA 2000


Engineering and design applications


Benefits of integrating engineering applications


Requirements
We've discussed the needs and benefits of integrated design and analysis, but there is still more information needed before taking full advantage of these systems. It must be said (i.e. stressed) that you need the data to support the intended application. That is, you can't do engineering analysis on data that only has size and material attributes. Data quality must be re-evaluated to ensure supporting attributes are available and network modeling considers the state of the system.

Network connectivity is something of an expectation in the digital world. But connectivity must be defined and the network must be built upon a model that will support continuous connectivity. Valves and switches must be able to operate and change the network structure to mimic real-life conditions. Taps must break into the source and be recognized as a change to the network as well. The system should support a trace function that identifies all connected facilities, while ignoring those features disconnected from the system.

GIS data that is intended to support design and analysis applications require a greater level of attribute information. This may require extending the data model to provide placeholders for the information. For example, the data model used for conversion tasks may not support design tasks, as it doesn't consider compatible unit information. Every utility has some level of attribute data. The question is what do you need, and what do you have. Sometimes the two don't match up, and field surveys need to be under taken, or default information used. Another solution to the "missing data syndrome" is supplemental data tables in the GIS. These tables may contain library/catalogue type of information without the need to have this data stored redundantly in all of your facility records.

Load information is necessary to properly design a subdivision. This information can be set up as a default, but when you want to do a full engineering analysis, actual load is desirable.

Since we're talking about a corporate repository for data, why not include load? Ties to Customer Information Systems provide load information accurate to the last meter reading. Seasonal peaks can also be accessed from this system. The GIS data model can accept this information on a periodic basis or via a real-time link, providing accurate information to users without suffering any performance penalties trying to figure out the load.

Engineering characteristics are also necessary when doing analysis. This information can be obtained from external look-up tables, but must be developed to provide information specific to the utility. Wire impedances, pipe roughness coefficients, etc., can all be obtained from manufacturer tables or as in most cases, are being used for manual calculations and can be readily brought into the system. Compatible unit information must be available and can be accessed directly from the work management system or from interface tables, or even down loaded into the GIS. The method for accessing this information depends on the system architecture and particular work management system. Compatible unit information is used to provide material lists, cost estimates and design rules to expedite the overall design process.

Security issues must be taken into consideration as well when you open up corporate data to the masses. Who should have access to look at the data, compared to who needs to be able to add as well as delete information in order to keep it up to date. Security can also involve quality control measures to ensure the integrity is not compromised with the additional use, but with this comes a process change to communicate user responsibilities.

If designers are now maintaining the GIS, they need to understand that every feature they place within the system will be considered part of the network. External systems, such as work management and outage systems will be getting some of their information from the GIS so it must be accurate. Many users have typically done designs in a graphic system, but never considered the data impact, as they were meant for hard copy, then the digital version is thrown away. Integrating design and analysis into the GIS means that the work being done is not "throw away". It is building the corporate database, not just the graphic picture, and care must be taken to ensure a viable data source is continually being built.

Page 2 of 4
| Previous | Next |

Applications | Technology | Policy | History | News | Tenders | Events | Interviews | Career | Companies | Country Pages | Books | Publications | Education | Glossary | Tutorials | Downloads | Site Map | Subscribe | GIS@development Magazine | Updates | Guest Book