Electric Utilities and Corporate GIS: The Case of Lebanon
Samir Chahrouri
Formerly GIS Project Management Team Leader, Electricity of
Lebanon
Beirut, Lebanon
Jacques Ekmekji
Director, GIS Services Division, Khatib & Alami
Beirut, Lebanon
Faris Sayegh
Manager of Design & Development, GIS Services Division,
Khatib & Alami
Beirut, Lebanon.
| Abstract Of The Paper & The Profile of The Speaker | Speaker Index | Paper Title Index |
1. Introduction:
In December 29, 1993 the Electricité du Liban (EDL) commissioned Khatib & Alami, in association with Environmental Systems Research Institute (ESRI) of Redlands California, to initiate a comprehensive study of EDL Geographic Information System (GIS), otherwise known as project GISEL, at a company-wide level.
The GIS scope covered five (5) main study tasks, two computer based GIS application, and procurement, installation and licensing of ESRI's GIS software.
The study tasks included (i) orientation seminars, (ii) user needs survey, (iii) needs assessment and requirement analysis, (iv) concept design of the GIS database model, and (v) implementation plan.
The computer based GIS application tasks covered (i) the development of a prototype which included the map of Lebanon at a scale 1:100,000 with relevant cartographic features and electric power generation and transmission features, and (ii) the development of a pilot project as a proof of concept for an area of 35 hectares within municipal Beirut.
Many benefits had been envisaged to result from project GISEL. It is important to note that some benefits are tangible while others are intangible and realized in the longer term of the life of project GISEL. Almost every "Service" within EDL uses spatially represented data as an important resource in performing their jobs. Electric utilities estimate that 87 percent of their data has location as an important characteristic; that is, 87 percent of the information that electric utilities use is spatial in nature. Mapping provides a foundation for much of the information used. The following broad categories summarize the benefits that are expected to be drawn from the successful implementation of project GISEL. The Need Assessment & Requirement Analysis report discussed the benefits of GIS for each Service more comprehensively and in detail.
1. By implementing project "GISEL" EDL has chosen to enter the Information Age of the 21st Century. EDL will be making a radical shift from the conventional organization to the Knowledge-Based Organization.
2. The Knowledge-Based Organization based on the geographic information systems (GIS) technologies will allow EDL to process, input, manipulate, update, track and share complex and geographically referenced information swiftly and correctly among the different 'Services / Authorities' within EDL.
3. The EDL operation will start relying on modern scientific methods rather than guesswork and it will base its operations on verified data rather than assumptions, thus applying the Fact-Based management principles.
4. Powerful visual statistical tools would be readily available to EDL to organize geographically referenced data and draw inferences. This should ultimately allow EDL to simulate the real world electric power system of Lebanon on its computer screens on real time basis once all the phases of the project are realized as stipulated in the implementation plan .
5. Experimentation within EDL will become a way of conducting business. Small experiments will provide EDL with incremental gains in knowledge while demonstration projects will involve holistic system-wide changes.
6. Failures, if inevitable, would be productive, and learning from past experience will ultimately lead to insight, understanding, and an addition to the wisdom of the organization.
7. New outside perspectives will be opened to EDL which will stimulate learning.
8. All Services within EDL would be able to obtain up-to-date information, comparisons, insight into changing inferences and trends.
9. Project "GISEL" will foster an environment inductive to learning, reflection, analysis and diagnosis. It will provide the proper environment for solving complex power problems in a reasonably short time.
The cumulative benefits of the above points will allow EDL to provide much better services to its customers with less cost and higher returns.
2. User Needs Survey (UNS):
Immediately upon receiving the notice to proceed, a series of orientation seminars were scheduled. Over 150 people from EDL attended those seminars and participated in the discussions and GIS ideas' development. Various reactions were expressed from participants in those orientation seminars. Such reactions, irrespective of their tone or appearances, were considered very constructive. They involved the participants in the modernizing, automating and informating processes that EDL embarked on by initiating GISEL project. Several specific concerns were raised by the participants in relation to the components and functionalities of GIS. Finally the seminars were evaluated jointly by the EDL Project Management Team (PMT) and the K&A GIS team. The main achievements from these seminars were the introduction of the GIS culture into EDL and paving the road to a successful user needs survey.
Immediately after the completion of the seminars, over 120 People were interviewed by a team of four GIS specialists from K&A and ESRI over a period of three months. Almost all 'Services' were revisited for more clarification.
At the end of this phase a presentation was made to the Board of Directors of EDL summarizing progress to date and highlighting remaining works. During the presentation a live computer-based demonstration was also conducted showing the preliminary results of the GISEL prototype. This prototype was prepared to give EDL a feel of the GIS concept at an early stage of the project.
To develop a full profile of GISEL needs and requirements, the User Needs Survey was structured along the following components and issues: procedures, data, hardware, software, and people.
The main issues addressed were related to (i) mandates, (ii) benefits, (iii) problems, and (iv) needs. During the course of the interviews all types of data records were collected. These data records were, in general, related to the current tasks each 'Service' was undertaking. Almost three hundred tasks were identified and 600 data records collected. The data type were in the form of charts, databases, maps, drawings, reports, tables, and forms.
The results of the initial interviews and the follow up interviews and discussions with the personnel of each of the eighteen (18) 'Services', the Electronic Center (EC) and the General Directorate, as it was shown on the organization chart of EDL at the time of the user needs survey, were documented in the User Needs Survey Report (UNSR).
3. Needs Assessment & Requirement Analysis (NARAR):
3.1 General: The UNSR identified many common data needs and application requirements among various 'Service's at EDL. These requirements were addressed to provide a common, coordinated information system. Many of these needs utilize spatial or locational information (i.e., maps and map-related information), and various spatial analysis tools including simultaneous display of different map information, query of related tabular data, and aggregation of information for specific areas.
In addition to common data and applications needs, the UNSR revealed that many EDL departments utilize similar data and perform similar functions using those data. By building a GIS to incorporate as many of these common needs as possible, GISEL provided useful, consistent, and non-repetitive data and applications to all 'Service's. Utilizing a common database, where possible, was to help reduce data redundancy, ambiguity, and duplication of effort between various 'Service's.
The NARAR identified the general functions of each EDL 'Service' and general tasks which utilize or produce locational information (i.e., maps and associated attribute data). An analysis of these functions and data was conducted and relationships between data and applications, applications and 'Service's, and applications and tasks were charted. This analysis helped in prioritizing GIS applications and data, and to identify which 'Service' will need what data and when. Also, major potential issues which affect the implementation of the GIS were identified and discussed.
3.2 Existing System Overview: The methods and procedures, the activities seen through a business perspective, the spatial and related tabular data, hardware and software, and the organizational structure were all identified.
3.2.1 The methods and procedure addressed issues such as: (i) What separate processes, steps, or functions make up the tasks of each 'Service'?, (ii) What triggers each task?, and (iii) How do work and products flow? The initiation of tasks, steps within tasks and flow of documents were documented.
3.2.2 The activities, defined as the operations which would be performed by any business institution in order to maintain and run its operations, and the information about these activities were classified. The 'General' activities, which are generic and apply to any type of business were charted against the task which EDL uses to maintain and run electrical power services.
3.2.3 The data samples were inventoried in two different database files which were used during the GISEL study to manage and analyze data requirements. In this phase the data records were analyzed and charted against their respective tasks.
3.2.4 The current staffing situation at EDL is, as elsewhere in the public sector, facing severe problems. All 'Service's were staffed at just around 50% of their mandated levels (when not taking into account part-timers). In addition, the civil war had also led to a lowering of technical levels due to a number of reasons, one of which was isolation from exposure to new technologies.
3.3 Proposed System Overview: In light of the existing system the proposed system was developed. It addressed how it should allow for better work methods and procedures, GIS applications needed, data required to support such applications, hardware, software, and communications requirements to handle data flow and passage between the different 'Service's, and the organizational structure that will support the new information age technology. The requirements themselves, against which subsequent system design and development work were carried out, tested, and accepted were described in detail in the NARAR.
3.3.1 Methods and Procedures at EDL, under the GISEL proposal, will be improved with resultant benefits to the organization. Significant features, advantages, and potential benefits of the proposed system affect mainly: management, productivity and efficiency, access and security, time, data accuracy and currency, and quality assurance.
3.3.2 Applications identified in the NARAR were defined in such a way that they can generally be implemented as discrete programs or sets of procedures within the GIS. Some applications are specific to a process which may involve a single EDL user group, while others are relatively general and usable by multiple 'Service's or user groups to help achieve specific objectives. It is important to note that these applications were identified based on examination of the individual needs of all 'Service's of EDL. In studying the existing tasks at EDL, nine such applications were identified that would benefit from GIS. Each task was charted against all identified applications to show applicability or the lack of it. The definition of these applications also came about through a comparative study of other similar electrical utilities. Six (6) additional applications which were defined as benefiting from Management Information Systems (MIS) were identified. Tasks were registered for the MIS applications only in the case where it interfaced to a GIS application which had registered a benefit to that particular task.
The applications identified were by no means exhaustive. They deal mainly with the existing mandated tasks, and the implementation plan is a long term one. It is envisaged that as GIS becomes implemented and EDL's staff acquire the necessary skills, more GIS applications will be identified and incorporated but these will meet the requirements of tasks that currently do not exist at EDL. The major applications of GISEL project are:
3.3.2.1 Ad Hoc Query, Display, and Reporting (AH): This application will allow users to accomplish many different queries using both spatial and attribute data. These queries may result in the generation of non-standard reports or maps.
3.3.2.2 Districting (DI): This application will allow EDL to analyze, add, modify (if necessary) boundaries of, and number EDL divisions, collection areas, collection routes (tournées) and the like.
3.3.2.3 Facility Siting (FS): An application which involves determining the ideal placement of point features such as production plants, substations, or warehouses, and linear features such as high tension lines. A number of data sets will be accessed such as physical geography (vegetation, topography) and man-made geography (roads, human settlements).
3.3.2.4 Maintenance (MA): This application is the primary vehicle for all aspects of the facilities data that deal with routine maintenance. It will offer the possibility of geographically consolidating such maintenance within specific areas and time periods. It will also automatically access the relevant database for updating.
3.3.2.5 Map Editor (ME): The editor/QA application provides a mechanism for the maintenance and updating of the EDL database, both cartographic and attributes, except updates performed as part of the Maintenance, Work Order, or Trouble Call applications. It will also be used for numbering streets and buildings.
3.3.2.6 Map Products (MP): This application will replace manual methods for standard map production. Other specialized maps will be provided using a combination of generic tools and Ad/Hoc display tools.
3.3.2.7 Power Flow and Fault Analysis (PF/FA): Power Flow & Fault Analysis refers to a variety of operations that use a model of the electrical transmission system in order to evaluate its performance. It will allow the user to define models of the transmission system, and then extract information from the models and/or perform analysis functions on those models. This application will incorporate PSACP for certain functions. PSACP stands for Power Systems Analysis and Control Program, a third party product developed by the Faculty of Engineering and Architecture at the American University of Beirut. The interface of the PSACP with project GISEL is a topic of a separate paper that was first presented at ESRI's 14th annual conference in May 1994. It is also a topic of a technical paper presented to IEEE for evaluation and publication.
3.3.2.8 Trouble Call (TC): This application provides the primary mechanism for updating and maintaining the TC database, viewing TC outage analyses graphically, and demonstrating dispatch decision support capabilities from within the GIS. The application applies to the main substations, medium tension lines, substations, and low tension lines.
3.3.2.9 Work Order (WO): The work order process deals with the spatial aspects of the work order process (such as sketches and as-built drawings), and interfaces to the work order management system which is normally built as part of the MIS and deals specifically with material and equipment databases (tabular). Work orders include all work that initiates new connections, expansion, or upgrades of the existing electric system, but not including any work which is a result of routine maintenance
3.3.2.10 Other Applications: Six non-GIS applications have been identified. These systems are: Accounting, Billing, Customer Information, Payroll, Warehouse Inventory, and Work Management. Such systems are standard business systems and do not fall under the GISEL contract. However, the GISEL studies gave all the necessary requirements of these systems where relevant to the running of the GIS applications.
3.3.2.11 Supervisory Control And Data Acquisition (SCADA): Decision Systems International (DSI) of Atlanta, USA, presented EDL with a feasibility and requirements study for a control center (April 1994). This study included a SCADA system.
3.3.3 Developing a GIS database, which accurately represents features relative to their location on the ground, was valued highly by most of the 'Service's. All the interviewed groups identified many useful GIS applications which could be performed utilizing existing sources such as maps referenced to ground locations. Based on an evaluation of the source materials, the data were categorized into types and broken down into groups, the objective of categorization being to identify potential data redundancy. The larger and more complex the organization, the more data will typically be found to be redundant. Data were grouped into twelve (12) data groups depending on how they may be used in the database and, taken as a whole, the data groups form EDL's data base which will be accessed by all applications (GIS and others). This model took into account data of similar nature or that are normally used, gathered, updated in conjunction with each other. Later on, these data groups formed the basis for the conceptual database design. The data groups were categorized as follows:
3.3.3.1 Control/Base Map Data: Provides registration and spatial referencing for all other spatial layers of the database.
3.3.3.2 Customer Database(s): Includes customer files, billing files and records, customer requests, and customers complaint files.
3.3.3.3 Electric Generation Data: Includes maps, drawings, site and building plans, general power schematic diagrams, details related to equipment, and technical books for operation, monitoring, and maintenance of all production plants.
3.3.3.4 Electric Transmission Data: Includes features and attributes of high and medium voltage transmission facilities such as lines, support structures, devices, and maintenance database.
3.3.3.5 Electric Substation Data: Includes all features (along with their attribute data files/systems) that are between, but not including, transmission and distribution features (substation boundaries, circuits, buses, protective devices, transformers, capacitors, etc.).
3.3.3.6 Electric Distribution Data: Includes all those electric features downstream from the distribution substation feeder protective devices.
3.3.3.7 Landbase: Includes all land-related data layers and files (such as parcel boundaries and database, cadastral data, and legal deeds), transportation features and attributes, address systems, administrative and political boundaries, electric boundaries for regions/divisions/districts and their attributes, landmarks, etc.
3.3.3.8 Legal/Personnel/Payroll Database: Groups all data related to EDL employees, legal matters, and payroll.
3.3.3.9 Natural Resources Database: Includes all data layers and attributes related to physical geography (such as topography, geology, soil, and contour lines), hydrology features, and vegetation.
3.3.3.10 Socio-economic Data: Includes layers related to population characteristics and demography, economic data, census data, villages, towns, cities, and others.
3.3.3.11 Warehouse, Buildings, and Grounds Data: Includes all data files and systems related to warehouse management and control.
3.3.3.12 Non-GIS-Related Data: All other data files that do not have any relevance to GIS.
3.3.4 Hardware & Software: The GISEL applications will operate in a client/server computing environment, with display and control of the applications provided to users' desktops by emulation software. All graphic data, application executables, and topology data will be locally stored on a workstation/server. Attribute data to support the applications will be located on at least one centralized server. Certain attribute data sets pertain to regional offices and would therefore be stored on regional servers. There should be between four to eight locations all over Lebanon other than the EDL Headquarters that will have specific GIS application capabilities.
3.3.4.1 Hardware: Each GIS setup was recommended to have a UNIX workstation connected to a number of PC workstations over a local area network. It was also recommended that the EDL corporate databases reside on a server connected to the network. The regional sites and Headquarters would be connected via a wide area network.
3.3.4.2 Software: The ESRI software products that were identified for inclusion in the GISEL recommended long term configuration are: ARC/INFO, NETWORK, TIN, ArcScan, ArcStorm, and ArcView.
3.3.4.3 Databases: The database structure and location would be established to optimize performance within the distributed client/server environment. It should be possible for data to be distributed physically and/or logically, with remote system, data, and application management tools organized around LAN and WAN connectivity capabilities.
3.3.4.4 Peripherals: Several network communication products would be part of the configuration. These products will support communications between LANs, among client machines, and with the main attribute database. These communications will occur through a variety of network communication channels.
3.3.5 Organizational changes could be required as part of implementing project GISEL because changing business processes may eventually lead to or require such organizational changes. While these longer-term organizational requirements cannot be completely defined at this time, it is possible to identify short-term organizational requirements for GIS-related staffing. Several 'Service's could plan on requiring staff in each of the following categories: system management, system support, and end users. As the implementation progresses, the extent of this requirement will expand; however, it was anticipated that a small project team of two or three individuals can support all GIS activities during the first year.
The introduction of any system into a well established institution will necessarily take some effort so that staff can adapt. Not only would this be the case where work procedures would actually be changed but, also would be true where doing the same work in a computerized manner may appear to be a change. The conclusion to be drawn here is that great attention is to be paid to staff training and awareness.
Several matrices were drawn up based on tasks performed by different Services at EDL versus the GIS and MIS related applications. After redressing the imbalances and looking specifically at which 'Service's would benefit from the GIS applications, it was clear that there were three at the top of the list: Distribution, Studies, and Regions. Medium users being Dispatch & Transport, Measurement & Protection, and Consumers, and light users being Organization & Numbering, Production, and Customers. The remaining 11 'Service's only benefit from the Ad Hoc application. This three way division clearly indicates the varying needs for staff hiring and training for GISEL.
3.3.5.1 Level of Activity
Probably the most active application in the long run will be the Maintenance once the EDL has completed the rehabilitation program. In the short to medium term, the more active applications will be the Power Flow & Fault Analysis, Trouble Call, and Work Order due to the currently poor state of the electrical network. All of these applications will see daily usage. Also of extensive usage but restricted in the number of users will be the Map Editor and Map Products applications. Of infrequent and random usage will be the Districting and Facility Siting applications. Finally, the Ad Hoc will be substantially though randomly used by a large number of users.
3.3.5.2 Type of Activity
A number of applications fit into the Operations & Maintenance aspect. These are Maintenance, Power Flow & Fault Analysis, Map Products, Trouble Call, and Work Order. Their users will thus be field engineers and their supervisors, in addition to the relevant heads of 'Service'. As for the Planning aspect, Facility Siting will be used more by office engineers, while Map Editor by drafters and CAD operators. The Ad Hoc will obviously be used by all sorts of staff.
3.3.5.3 Training and Awareness
The above distinctions will be the basis of determining the staff qualifications necessary for using GIS. These requirements were discussed in detail in the NARAR, specifically with regards to general computer literacy, specific GIS training, database knowledge, simple data input, application, and procedure awareness. Procedure awareness is important because information technologies may make work procedures more abstract and removed (physically speaking), and thus staff should be more aware of the new approach to procedures so that they still retain an understanding of their specific relevance in the larger picture.
4. Conceptual Database Design and Implementation Plan (CDDIP):
4.1 General: The conceptual database design and implementation plan report presented (i) a detailed description of the applications and their requirements, (ii) a number of issues relating to geographic data, (iii) a detailed description of the database model recommended for GISEL, and (iv) a detailed implementation plan over a period of five years till the end of 1999.
4.2 Generic Application Function Flow: Each application was defined in detail providing a complete understanding of how, when, where, why, and by whom applications are used, and elaborating on the data, system, and organizational requirements.
4.3 Corporate and Subject Data Bases: The shared data base concept provides for sharing of commonly used map and attribute data among users within the framework of a land information system. Much of the map and attribute data in GISEL will be accessed by more than one 'Service' at EDL and is thus labeled "corporate" data. The term corporate data refers to data that are used by multiple departments and/or agencies for various applications throughout the "corporation" (i.e., EDL).
Not all data in GISEL project will require multi-organizational access. Some data, primarily attribute files, may be unique to one 'Service's activities, of no general utility or interest to other 'Service', or require special security arrangements. These data which are accessed by only one 'Service' and are maintained by that same 'Service' are called "subject" data. These data are considered proprietary and do not result in significant corporate value if included in the GIS as a shared resource. The figure below illustrates the corporate and subject data base concept as it relates to GISEL users.
4.4 GISEL Database: Based on the GISEL generic applications presented earlier as to which data layers were required by applications, and building on the data requirements identified in the NARAR the relevant layers and files within the twelve data groups were been detailed. While this detailing was at the conceptual level, it was sufficient to fully indicate the elements and structure of each layer and file and through which items they are linked.
4.5 Implementation Plan: The overall objective of the implementation plan were for the long term implementation of all GISEL applications and data base within all relevant Services at EDL. The Implementation Plan provided information to be used in planning and directing the development of GISEL. The costs for implementation were estimated based on the information currently available, on previous projects of a similar nature, and on current prices for hardware, software, and other components of the GIS technology. The benefits expected to result from GISEL project were also identified. Finally a strategy for development of the database, system (applications, hardware, software), and other resources was provided.
4.5.1 General: The Implementation Plan is intended to serve as a guideline for the considerations necessary to successfully implement project GISEL. This guideline must be combined with careful planning and inter-department coordination. The Implementation Plan cannot account for unforeseeable technological (e.g., hardware and software) advances, or economic, political, and administrative changes that could change the assumptions under which the plan was developed. The intent of the plan is to be flexible enough to allow for changes in response to current realities, yet be specific enough to provide clear direction for GISEL's development efforts.
4.5.2 The implementation Plan: The implementation strategy was presented in ten (10) tracks (not presented chronologically) over a period five years. The GISEL project shall start with the establishment of a GIS Task Force (see Task 10.1). Three of these tracks, Database (Track 3), Applications (Track 4), and System Development (Track 5) were also presented in a two phase approach. Phase 1 was primarily concerned with expanding the GIS to cover the Greater Metropolitan Beirut Area (GMB), focusing on the priority applications. Phase 2 dealt with the expansion of the GIS to the regions and the development of other GIS applications and interfaces. Although the strategy describes two phases for these three tracks, these phases do not necessarily have to completely follow each other. Some tasks of Phase 2 may very well be developed in parallel with others.
Track 1: Expand GIS Awareness
Task 1.1 Use of Pilot Prototype and Materials
Task 1.2 GIS Seminars and Demonstrations
Task 1.3 GIS Local and International Conferences
Task 1.4 Build GISEL Library:
Track 2: Detailed Applications Functional Requirements, Database Design, and GIS Specifications
Task 2.1 Preparation of GISEL Applications Functional Requirements
Task 2.2 Development of GISEL data structure and data dictionary
Task 2.3 Development of data conversion specifications and standards
Task 2.4 Development of quality assurance procedures and programs
Track 3: Database Development
Task 3.1 Preparation of Data Development Tender
Task 3.2 Evaluation of the proposals and selection of data development contractor(s)
Task 3.3 Development of data collection, automation, and conversion management plan
Task 3.4 Data Collection, Compilation, and Conversion
Phase 1 Data Collection, compilation, and conversion for Greater Metropolitan Beirut (GMB)
Phase 2 Data Collection, compilation, and conversion for the Regions:
Track 4: Applications Development
Task 4.1 Preparation of Applications Development Tender
Task 4.2 Evaluation of the Proposals and Selection of Applications Development Consultant(s)
Task 4.3 Applications System Design and Development
Task 4.4 Priority application on site training
Task 4.5 Integration of GIS with Other Systems
Task 4.6 Develop Other Applications/Expand Priority Applications
Track 5: Hardware/Software (System)
Task 5.1 Preparation of the Hardware/(Software) Expansion Tender for GMB Area
Task 5.2 Hardware Vendor Evaluation, Selection and Procurement for GMB
Task 5.3 Site Preparation, Installation and Testing for GMB
Task 5.4 Hardware Vendor Evaluation, Selection and Procurement for the Regions
Task 5.5 Installation and Testing of Hardware and Software for the Regions
Task 5.6 Installation of communications lines/links between Headquarters and regional offices
Track 6: Maintenance and Administration
Task 6.1 Establish Database Maintenance Procedure
Task 6.2 Database Maintenance
Task 6.3 System Maintenance
Task 6.4 System Administration
Track 7: Funding/Staffing
Task 7.1 Develop Funding Plan
Task 7.2 Develop Staffing Plan
Task 7.3 Select/Hire GIS Staff
Track 8: Training
Task 8.1 Development of Training Plan
Task 8.2 Implementation of the Training Program
Track 9: Implementation Management and Administration
Task 9.1 Management and Administration of GISEL Implementation
Track 10: Institutional/Organizational Development
Task 10.1 Establish GISEL Task Force
Task 10.2 Formalize Institutional/Organizational Structure
Task 10.3 Establish/Expand GIS Center and GIS Unit
Task 10.4 Establish Coordination and Information Sharing Strategy and Procedures.
4.5.3. Time Schedule: The schedule described an overall timeline of GISEL Implementation Plan. It called for a five-year plan during which, priority GISEL applications and data will be developed along with the expansion of the hardware, software, and communications system to support these applications and data.
4.5.4. Cost Schedule: Costs estimates provided were based on current knowledge of GISEL operations and current prices for GIS hardware, software, and services. Each element of the implementation plan was priced separately. The figure below provides a breakdown of the cost per GISEL main component.
5.0 GISEL Immediate Applications:
During the study and design stage two GIS immediate applications were developed.
5.1 Prototype: This prototype was prepared to give EDL a feel of the GIS concept at an early stage of the project. It included digitizing the map of Lebanon at a scale 1:100,000 (six sheets) with relevant geographic features and features attributes. Themes present in the prototype, from different sources, included:
Roads; Railroads; Rivers; Administrative boundaries; EDL boundaries; Lakes; High tension lines; Substations; Power plants; Towns & villages; Warehouses; and sample details (a high tension line; Cadastral; Spot elevations; a substation and a power plant).
This prototype was used to provide hands-on experience to EDL's GIS staff. It also provided the PSACP project with the required geographical features to adequately complete the interface.
5.2 Pilot Project: The pilot project was primarily a 'proof-of-concept' for a selected set of functions and their applications as defined in NARAR and detailed in the CDDIP. In addition, conducting the Pilot Project allowed K&A to test a part of the Implementation Plan that dealt with data (mainly distribution) collection, conversion, and entry, thereby enhancing the time and budget allocations.
In this phase of the project K&A/ESRI GIS team administered a limited part of the CDDIP for an area of 35 hectares, which was defined by the EDL staff. The important layers of the database were automated for this pilot area. These data groups were: Control/Base Map, Customer, Distribution, and Landbase. Consistency and quality assurance checks were performed on the data prior to its usage.
The Pilot Project chiefly addressed the Map Editor application. It provided drawing tools, symbols, plotting and analysis functions in a single environment to support most distribution system design requirements. The priority parts of the application were built at the Application Development Center (ADC) at ESRI headquarters in Redlands, California.
5.3 The PSACP interface with GISEL: this work was carried out by the Faculty of Engineering and Architecture (FEA) at the American University of Beirut (AUB), and as mentioned earlier, was a topic of a separate paper. The interface integrated the GIS technologies and the well developed software packages for power system operation and control. The first integration provided GISEL users extremely useful map algebra analysis involving many needed coverages (geographical locations, geometrical shapes, population densities, roads, etc...). Also, it added a lot to the graphical interfacing and flexibility of the power tool. The second integration involved building a new database hierarchical structure that included detailed specifications of power elements. This had the merit of narrowing down the gap between technical and managerial issues to serve a wide variety of goals mainly to support the complex decision making process at EDL at a time where major rehabilitation and development was being undertaken by EDL.
6.0 'GISEL'95', Year '1' Implementation:
The recommendations set forth in the GISEL plan are presently being implemented. The focus of year one being mainly on the following:
6.1 Building the GIS task force and work force at EDL;
6.2 Developing the Functional Requirements and the Physical database Design;
6.3 Developing three applications out of the nine applications identified in NARAR, Namely: (i) Ad Hoc, (ii) Map Editor, and (iii) Map Product; and
6.4 Extending the pilot area (35 ha) to the entire Municipal Beirut (2000 ha).
7.0 Conclusion:
The GIS team of project GISEL is confident that the GISEL initiative will achieve the expected benefits in spite of the many difficulties facing Lebanon which might hinder its timely progress. The GIS team is also certain that EDL will soon start meeting the business challenges of the coming years with the knowledge base and the appropriate technologies offered by project GISEL.
BIOGRAPHIES:
Samir Chahrouri: B.S Electrical Engineer (1963) from the American University of Beirut (AUB). Over thirty years with power utility companies. Presently Head of Receiving Committee and formerly Chef De Service at EDL in charge of Purchasing and Warehousing. Appointed as the GIS Project Management Team (PMT) leader to supervise and implement the GISEL project.
Jacques Ekmekji: B.S civil engineering (1971) from the American University of Beirut (AUB). He is an associate of the firm Khatib & Alami (K&A), a multidisciplinary engineering firm ranked among the top ten international design firms in the Middle East. Presently he is Director of the Geographic Information Systems (GIS) Services Division at K&A and Principal-in-Charge of the design office in Al-Khobar Saudi Arabia. GIS projects under Mr. Ekmekji's directorship include the Electricity of Lebanon's GIS project otherwise known as project GISEL, Lebanon's Staged Wastewater Program (LSWWP), SOLIDERE's Integrated Spatial Information Systems (ISIS), and a 300 hectares community development project in the township of Mechref in the environs of Beirut.
Faris Sayegh: B.Architecture (1987) from AUB, Master in City Planning (1991) from MIT. A GIS specialist with K&A since 1992, he is in charge of the GIS Design and Development unit at K&A, which includes Application and Database Design, Cartographic Production, Multidisciplinary Specialities, and System Administration. His main work to date has been as project manager for the GISEL project. Also retained by the World Bank as a GIS consultant.
REFERENCES:
Drucker, Peter F. 1989. The New Realities. Harper & Row, New York,
Garvin David A. Building A Learning Organization. Harvard Business Review (July-August) 1993.
Geographic Information Systems , Tor Bernhardsen, 1992
Geographic Information Systems, edited by D. J Maguire,
GISEL Conceptual Database Design & Implementation Plan (CDDIP)- Electricité du Liban, Khatib & Alami, 1994.
GISEL Needs Assessment and Requirements Analysis (NARAR) - Electricité du Liban, Khatib & Alami, 1994.
GISEL User Needs Survey Report - Electricité du Liban, Khatib & Alami, 1994.
M F Goodchild, and D. W Rhind, 1991 a Compendium of GIS articles,
Nonaka Ikujiro. The Knowledge-Creating Company. Harvard Business Review (November-December 1991).
Northern States Power Company Production GIS Physical Database Design Document, ESRI, 1993.
Oman Land Information System - Implementation Plan, ESKA, 1989.
Oman Land Information System - System Design Report, ESKA, 1989.
Power System Analysis and Control Package - User's Guide, Power Engineering Group, American University of Beirut, Faculty of Engineering and Architecture, March 1994.
Pueblo County GIS - Database Concept Working Paper, ESRI, 1991.
Sanitary Sewer Collection Facility Mapping and Management System - Conceptual Design Report, ESRI, 1991.
Software Development for EDL's Dispatching Center - Final Report, Yehia et al, American University of Beirut, Faculty of Engineering and Architecture, March 1994.
Physical Database Design, Miner & Miner 1994.
Journals & Publications: ESRI's ArcNews, GIS World, and Geoinfo System.
| Abstract Of The Paper & The Profile of The Speaker | Speaker Index | Paper Title Index |
|
|
|
| |
