EP2811417A2 - Systeme und Verfahren zur Synchronisierung der Netzwerkmodelle eines geografischen Informationssystems (GIS) - Google Patents

Systeme und Verfahren zur Synchronisierung der Netzwerkmodelle eines geografischen Informationssystems (GIS) Download PDF

Info

Publication number
EP2811417A2
EP2811417A2 EP20140170924 EP14170924A EP2811417A2 EP 2811417 A2 EP2811417 A2 EP 2811417A2 EP 20140170924 EP20140170924 EP 20140170924 EP 14170924 A EP14170924 A EP 14170924A EP 2811417 A2 EP2811417 A2 EP 2811417A2
Authority
EP
European Patent Office
Prior art keywords
model
utility grid
cim
difference
grid
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP20140170924
Other languages
English (en)
French (fr)
Other versions
EP2811417A3 (de
Inventor
Michael Stanislawski
Enrique Cano Carballar
Lee Hill
Glenda Paulette Simons
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
General Electric Co
Original Assignee
General Electric Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by General Electric Co filed Critical General Electric Co
Publication of EP2811417A2 publication Critical patent/EP2811417A2/de
Publication of EP2811417A3 publication Critical patent/EP2811417A3/de
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G06F30/10—Geometric CAD
    • G06F30/13—Architectural design, e.g. computer-aided architectural design [CAAD] related to design of buildings, bridges, landscapes, production plants or roads
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/29—Geographical information databases
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Definitions

  • the invention relates generally to geographic information systems, and more specifically to methods and systems for synchronizing models of the geographic information systems.
  • a geographic information system (GIS), sometimes referred to as a geographical information system or a geospatial information system, is a system for capturing, storing, analyzing and managing data and associated attributes which are spatially referenced to, for example, the planet Earth.
  • GIS systems may integrate hardware, software, and data for capturing, managing, analyzing, and displaying all forms of geographically referenced information.
  • GIS systems may provide information about the location of items, such as buildings, streets, sewers, lamp posts, etc., as well as information about the items themselves.
  • GIS systems may be also subject to frequent updating to reflect changes in the geographically referenced information, while other external systems depending on the GIS systems may not receive frequent updates. It may be useful to provide methods to synchronize the geographically referenced information of the GIS systems with other external systems.
  • a system in a first embodiment, includes a processor configured to identify a modification to a utility grid, and to derive a first model of the utility grid and a second model of the utility grid.
  • the second model of the utility grid includes a modification of the first model of the utility grid.
  • the processor is configured to compare the first model of the utility grid to the second model of the utility grid, and to derive a difference between the first model of the utility grid and the second model of the utility grid based at least in part on the comparison.
  • a non-transitory computer-readable medium having code stored thereon includes instructions to identify one or more modifications to a geographic information system (GIS) model, derive a first model of the GIS model and a second model of the GIS model.
  • the second model includes a modification of the first model.
  • the code includes instructions to compare the first model to the second model, and to derive a difference between the first model and the second model based at least in part on the comparison.
  • GIS geographic information system
  • a Geographic Information System includes a processor configured to generate a representation of an electric power grid in a first state, receive an input as an indication to change the representation of the electric power grid to a second state, and derive a first model of the electric power grid in the first state and a second model of the electric power grid in the second state.
  • the second model of the electric power grid includes at least one difference from the first model of the electric power grid.
  • the processor is configured to compare the first model of the electric power grid to the second model of the electric power grid to quantify the at least one difference, and to derive a Common Information Model (CIM) representation of the at least one difference between the first model of the utility grid and the second model of the utility grid based at least in part on the comparison.
  • CIM Common Information Model
  • the techniques described herein enable the communicative coupling and synchronization between GIS systems to a variety of external systems.
  • open standard models are used to share information between the communicatively coupled systems. By using open standards, any system that supports the standards may participate. However, changes to models may result in the entirety of the changed model being transmitted to interested systems.
  • the techniques described herein may derive model changes and transmit only a subset of the changed model, rather than the entirety of the changed model. Changes may be derived based on localized searching of a graph (e.g., a representation of a utility network model), rather than be searching the entire graph for differences.
  • a graph e.g., a representation of a utility network model
  • the techniques described herein may improve information synchronization between a variety of systems and may reduce transmission times and cost by transmitting the derived differences only.
  • CIM Common Information Model
  • the GIS system 10 may include a spatial server 12, and a number of client computers 14 communicatively coupled to the spatial server 12.
  • the client computers 14 may execute a web browser and/or a client software application, such that spatial server 12 is accessible to client computers 14 over a network, such as the Internet and/or an intranet.
  • Client computers 14 may be interconnected to the Internet through many interfaces including a network, such as a local area network (LAN), a wide area network (WAN), dial-in-connections, cable modems, wireless modems, and/or special high-speed Integrated Services Digital Network (ISDN) lines.
  • client computers 14 may be any device capable of interconnecting to the Internet, including, for example, a personal computer, portable computer, a tablet, a server, a router, a network computer, a vendor or manufacture's computing device, smart grid components, a peer device, a smart phone, etc., and may allow a GIS client 16, such as a human user or a software entity, to use the GIS system 10.
  • the plurality of GIS clients 16 may connect to the spatial server 12.
  • the spatial server 12 may include memory capable of containing information on a variety of matters, such as information relating to one or more areas of interest of the GIS client 16, executable computer instructions, and the like, as well as a processor suitable for executing the computer instructions. Information from the spatial server 12 may be accessed by potential clients or users (e.g., GIS clients16) at one of the client computers 14 by logging onto the spatial server 12. In an additional or an alternative embodiment, memory may be stored remotely from the spatial server 12, and may be non-centralized.
  • the spatial server 12 may functionally interface with one or more databases to store geospatial information and/ provide for a variety of functions, such as but not limited to publishing maps, sharing maps, providing for web services, providing for spatial analysis (e.g., vector, raster, network, and/or 3D analysis), providing for geographic display of conflicts and conflict resolution, delivering development tools and tool support, transforming between coordinate systems, managing versioned data stores, and so on.
  • functions such as but not limited to publishing maps, sharing maps, providing for web services, providing for spatial analysis (e.g., vector, raster, network, and/or 3D analysis), providing for geographic display of conflicts and conflict resolution, delivering development tools and tool support, transforming between coordinate systems, managing versioned data stores, and so on.
  • geospatial information may include, for example, a model related to the areas of interest, equipment information (e.g., location of power producing equipment and conduits, location of utility equipments and conduits, such as gas equipment, sewage equipment, location of computing equipment and conduits) weather conditions related to the areas of interest, and/or terrain data related to the areas of interest.
  • equipment information e.g., location of power producing equipment and conduits, location of utility equipments and conduits, such as gas equipment, sewage equipment, location of computing equipment and conduits
  • weather conditions e.g., weather conditions related to the areas of interest
  • terrain data e.g., weather conditions related to the areas of interest
  • the spatial server 12 may be coupled to a spatial relational database 20, as well as other files or databases 22.
  • the spatial relational database 20 may be an integrated set of functions and procedures that enables spatial data to be stored, accessed, and/or analyzed more quickly and efficiently in a database, such as the spatial server 12.
  • the spatial relational database 20 may provide a structured query language (SQL) or similar schema and functions that facilitate the storage, retrieval, update, and query of collections of spatial features in a relational database.
  • the database 20 may include the following components: a schema that prescribes the storage, syntax, and semantics of supported geometric data types; a spatial indexing mechanism; a set of operators and functions for performing area-of-interest queries, spatial join queries, and other spatial analysis operations; and administrative utilities.
  • the database 20 and other files or databases 22 may include data relating to modifications (e.g., due to physical and/or virtual retrofitting) to GIS networks and/or other management networks.
  • the spatial server 12 may be used to generate one or more Common Information Model (CIM) files 24 based on, for example, data included in the spatial relational database 20, the other files or databases 22, and/or data received from one or more external data services.
  • CIM file 24 may include any open systems management standard that may be used to model and export a network model (e.g., electric power network model, gas line network model, water systems network model, and so forth) over a communications network 26 to, for example, one or more external data systems 28.
  • a network model e.g., electric power network model, gas line network model, water systems network model, and so forth
  • the external data systems 28 may include various data and/or data management systems such as, for example, an outage management system (OMS) (e.g., electric power outage management), a distribution management system (DMS) (e.g., suitable for routing electric power, water, and/or gas through corresponding networks or grids), a Meter Data Management (MDM) system (e.g., useful in management of large quantities of utility data), an Engineering Analysis (EA) system, a customer information system (CIS), a work management system (WMS), a supervisory control and data acquisition system (SCADA), an enterprise resource planning (ERP) system, a customer relationship management (CRM) system and/or other external data and/or data management systems.
  • OMS outage management system
  • DMS distribution management system
  • MDM Meter Data Management
  • EA Engineering Analysis
  • CIS customer information system
  • WMS work management system
  • SCADA supervisory control and data acquisition system
  • ERP enterprise resource planning
  • CRM customer relationship management
  • the CIM file 24 may, in some embodiments, include the only changes (e.g., additions, deletions, modifications, and so forth) made to the utility networks of the GIS system 10. Indeed, by providing for CIM files 24 or electronic transfer of CIM data and/or CIM XML files, the spatial server 12 may share GIS data to a wide variety of external systems 28. However, changes in CIM model, including simple changes such as the addition of a conduit, or complex changes such as the addition of a subnetwork, would then be communicated to the external systems 28 by transmitting the entire model containing the changes. The techniques described herein may accurately derive only the portions of the model that have been changed, and then transmit the changed portion.
  • changes in CIM model including simple changes such as the addition of a conduit, or complex changes such as the addition of a subnetwork, would then be communicated to the external systems 28 by transmitting the entire model containing the changes.
  • the techniques described herein may accurately derive only the portions of the model that have been changed, and then transmit the changed portion
  • the changed portion may be transmitted as a standard model (e.g., a Resource Description Framework (RDF) difference model, or other similar difference model) using techniques further described below, rather than as a proprietary differential model.
  • RDF Resource Description Framework
  • the spatial server 12 may more efficiently synchronize with the external systems 28 and reduce transmission times and cost.
  • FIG. 2 illustrates an example block diagram of the spatial server 12, which may be useful in modeling utility networks and generating and exporting a CIM file 24 based on changes made to, for example, a pre-existing utility network (e.g., electrical network).
  • a pre-existing utility network e.g., electrical network
  • the present techniques may be applicable to any of variety of utility networks, utility management systems, and any underlying system modeled via CIM and/or similar standard models. Accordingly, as depicted in FIG.
  • a model 30 of an electric power network in a pre-existing state may be generated (e.g., generated by the spatial server 12 as discussed above with respect to FIG. 1 ) and stored in memory and/or in the databases 20, 22.
  • the electric power network model 30 may include, for example, one of many power distribution feeders that form a power distribution grid. Accordingly, as shown, the power network model 30 may include a model of a power source 34 (e.g., distribution substation or other transformer) and a model of a number of nodes 36A-36E.
  • the nodes 36A-36E may represent poles (e.g., including smaller transformers) and the lines connecting the nodes 36A-36E may represent conductors (e.g., overhead and/or underground power lines) of the distribution grid. Specifically, the nodes 36A-36E may represent points on the distribution feeder where distribution voltages may be transformed or regulated before being distributed to electric power consumers along the distribution feeder or along laterals extending from the distribution feeder.
  • a model 32 of an electric power network in a modified state may be generated by the spatial server 12.
  • the electric power network model 32 may include substantially the same components and/or configurations as the power network model 30.
  • the power network model 32 may include one or more modifications 38 not previously included within, for example, the power network model 30.
  • the modification 38 may, in some embodiments, include an addition, a deletion, an update, or any combination thereof, of one or more components of the network models 30 and 32.
  • the spatial server 12 may generate (and store) respective CIM network models 30 and 32 based on the power network in each of a pre-existing state and a modified state.
  • the spatial server 12 may then compare the network models 30 and 32 via a comparison block 40 (e.g., a comparator or similar software and/or hardware system).
  • a comparison block 40 e.g., a comparator or similar software and/or hardware system.
  • the spatial server 12 may compare the network models 30 and 32 to derive a CIM model 42 of only the differences (e.g., additions, updates or deletions of certain components or other modifications) existing between the network models 30 and 32. Upon deriving the differences between the network models 30 and 32, the spatial server 12 may store only the modifications to, for example, the model 32 in the generated CIM file 24 (e.g., generated based on the network models 30 and 32) for exporting to the external data systems 28 (e.g., DMS, OMS, MDM systems).
  • the external data systems 28 e.g., DMS, OMS, MDM systems.
  • the CIM model 42 may include only a subset of the differences, such as the subset applicable to a CRM system related to customer changes, a SCADA system related to control changes, and so on. It is to be understood that the CIM model 42 and the CIM file 24 may also include all of the model 30 and the computed differences between model 30 and model 32, or both models 30 and 32 and the computed differences. In this way, the spatial server 12 may not only expedite synchronization of the power network models 30 and 32 with the external data systems 28, but also improve efficiency in the transmission and importing (e.g., loading) of the CIM file 24 by the external data systems 28.
  • the CIM file 24 may, in some embodiments, include only the portion(s) (e.g., a truncated network model) of the power network model 32, for example, that is different from the power network model 30.
  • the file 24 may include an extensible markup language (XML) file compliant, for example with class-based uniform modelling language (UML) CIM models, including CIM schemas provided by the Distributed Management Task Force (DMTF).
  • DMTF Distributed Management Task Force
  • the CIM models may include xmlCIM encodings.
  • the xmlCIM encoding may include a specification that defines XML elements, written in Document Type Definition (DTD), which can be used to represent CIM classes and instances.
  • CIM models may further include a CIM Operations over HTTP specification which defines a mapping of CIM operations onto HTTP that allows implementations of CIM to interoperate in an open, standardized manner and completes the technologies that support the Web Based Enterprise Management (WBEM) initiative.
  • WBEM
  • the spatial server 12 may also include within the generated CIM file 24 a number of sections (e.g., a forward-differences section, a reverse-differences section, and so forth), which may include partial and/or detailed information (e.g., data and/or metadata) relating to the network models 30 and 32.
  • a forward-differences section may include information relating to the modifications (e.g., the one or more modifications 38) that were added and/or inserted into the pre-existing CIM network model 30.
  • the information included within forward-differences section of the generated CIM file 24 may allow a recipient resource (e.g., operator of the external data systems 28) to determine the CIM network model 30 (e.g., including connections and other parameters) based on knowledge of the modifications (e.g., forward-differences).
  • a reverse-differences section may include information relating to the pre-existing CIM network model 30 (e.g., without the one or more modifications 38).
  • the reverse-differences section may allow a recipient resource (e.g., operator of the external data systems 28) to determine modifications that may include deletions of certain components of the CIM network model 30.
  • the forward-differences section and the reverse-differences section may include information relating to modifications including updates to components of the CIM network model 30.
  • FIGS. 3-8 depict various examples of the presently disclosed techniques. It should be appreciated that the illustrations of FIGS. 3-8 are included merely for the purpose of example. That is, although power network models of FIGS. 3-8 may be limited to, for example, modifications to single network nodes 36 and/or connecting network nodes 36, it should be appreciated that in an actual implementation, any of a number of modifications such as large-scale additions or deletions of components (e.g., adding or removing substations, feeders, transformers, power conductors, and so forth) and small-scale modifications (e.g., adding, removing, or changing of switches, relays, or other protective devices) may be made to the power network GIS models 30 and 32.
  • large-scale additions or deletions of components e.g., adding or removing substations, feeders, transformers, power conductors, and so forth
  • small-scale modifications e.g., adding, removing, or changing of switches, relays, or other protective devices
  • FIG. 3 depicts a power network model including the source 34 and network nodes 36A-36E similar to those as discussed above with respect to the power network models 30 and 32 of FIG. 2 .
  • FIG. 4 illustrates the power network model of FIG. 3 with the exception that the network node 44B has been modified.
  • the spatial server 12 may generate before and after (e.g., without modification and with modification) CIM models of the power network models of FIGS. 3 and 4 .
  • the spatial server 12 may then derive and/or determine the differences between the before and after CIM models. Specifically, as illustrated in FIG.
  • the spatial server 12 may determine that only the network node 44B has been modified, and consequently only store the network node 44B to CIM file 24, for example, before exporting the CIM file 24 to the external data systems 28 (e.g., DMS, OMS, MDM, and so forth).
  • the difference may be exported as compliant with a number of CIM standards, including CIM UML-compliant standards, and/or XML CIM representations including Document Number DSP0201 version 2.3.1 or newer available from DMTF, Inc. of Portland, Or.
  • FIGS. 6-8 illustrate examples of before and after (e.g., without modification and with modification) CIM models of the power network models (e.g., power network models 30 and 32 of FIG. 2 ).
  • FIG. 7 illustrates the power network model of FIG. 6 with the exception that the network node 44B, network node 46C, and the line (e.g., power line) connecting the network nodes 44B and 46C have each been modified.
  • the spatial server 12 may generate before and after CIM models of the power network models of FIGS. 6 and 7 . In a similar aforementioned manner, the spatial server 12 may then derive and/or determine the differences between the before and after CIM models of FIGS. 6 and 7 . Indeed, as illustrated in FIG.
  • the spatial server 12 may then determine that only the network node 44B, the network node 46C, and the line (e.g., power line) connecting the network nodes 44B and 46C have been modified. Thus, the spatial server 12 may only store the network the network node 44B, the network node 46C, and the connecting line to CIM file 24, for example, before exporting the CIM file 24 to the external data systems 28 (e.g., DMS, OMS, MDM, and so forth).
  • the external data systems 28 e.g., DMS, OMS, MDM, and so forth.
  • the spatial server 12 may keep a running log of changes, for example in memory or in the databases 20, 22, and use the running log as the differences.
  • the running log may include extraneous information, such as a node that was inserted and then deleted, and thus is not in a previous or present model. Accordingly, the running log may be applied to the new model 32, for example, to determine changes that would desirably be communicated versus changes that would not be as useful to communicate.
  • node objects in the running log may be navigated, for example through breadth-first and/or depth first searches to determine other objects (e.g., links and/or nodes) that may have also changed.
  • changed links may be navigated to find local nodes and other links that also may have changed.
  • FIG. 9 a flow diagram is presented, illustrating an embodiment of a process 48 useful in synchronizing network models (e.g., power network models) between a GIS and an external data system (e.g., DMS) by using, for example, the spatial server 12 included in the GIS system 10 depicted in FIG. 1 .
  • the process 48 may include code or instructions stored in a non-transitory machine-readable medium (e.g., a memory) and executed, for example, by one or more processors included in the spatial server 12.
  • the process 48 may begin with the spatial server 12 identifying (block 50) changes or other modifications to a utility network topology.
  • the spatial server 12 may identify one or more modifications 38 not previously included within, for example, a GIS representation of the network.
  • the process 48 may continue with the spatial server 12 deriving (block 52) CIM models based on the utility network topology before and after such modifications.
  • a CIM network model e.g., model 30 of FIG. 2
  • a CIM network model e.g., model 32 of FIG. 2
  • a modified state e.g., after undergoing one or more modifications
  • the process 48 may then continue with the spatial server 12 comparing (block 54) the CIM network model of the pre-existing state (e.g., before modifications) to the CIM network model of the modified state (e.g., after modifications).
  • the spatial server 12 may compare the before and after CIM models (e.g., network models 30 and 32) to determine only the differences (e.g., additions, updates, or deletions of certain components or other modifications) existing between the two CIM models.
  • the process 48 may then continue with the spatial server 12 generating (block 56) a CIM file (e.g., CIM file 24) including the differences between the pre-existing state CIM network model (e.g., model 30) and the modified state CIM network model (e.g., model 32). Indeed, as previously noted, upon determining the differences between the CIM models, the spatial server 12 may generate the CIM model 42 and CIM file 24 (e.g., generated based on the network models 30 and 32) that includes the modifications and/or other information relating the modifications.
  • a CIM file e.g., CIM file 24
  • the spatial server 12 may generate the CIM model 42 and CIM file 24 (e.g., generated based on the network models 30 and 32) that includes the modifications and/or other information relating the modifications.
  • the CIM model 42 may not include in the entire CIM network models 30 and 32, but instead only the portion(s) corresponding to the differences between the CIM network models 30 and 32.
  • CIM file 24 may include a forward-differences section (e.g., section of data relating to components added and/or inserted) and a reverse-differences section (e.g., section of data relating to components deleted) in addition to the differences between the CIM network models 30 and 32.
  • the spatial server 12 may expedite the synchronization of the power network models 30 and 32 with external data systems 28 by generating a CIM file 24 that may include only a truncated model (e.g., a CIM model 42 of only the differences) of the pre-existing network model, and thus improve efficiency in the transmission and later importing (e.g., loading) of the CIM file 24.
  • the process 48 may then conclude with the spatial server 12 exporting (block 58) the generated CIM file 24.
  • the spatial server 12 may export the CIM file 24 to the external data systems 28, which may include a DMS, OMS, MDM, or similar external data system that may require synchronization with the GIS system 10.
  • the external systems 28 may then import the file 24 to synchronize with the spatial server 12.
  • the techniques described herein may also be used, for example, by the external systems 28 to produce an equivalent file 24 and thus maintain synchronization across the enterprise.
  • inventions include systems and methods to enable the communicative coupling and synchronization between GIS systems to a variety of external systems.
  • open standard models are used to share information between the communicatively coupled systems. By using open standards, any system support the standards may participate.
  • changes to models may result in the entirety of the changed model being transmitted to interested systems.
  • the techniques described herein may derive model changes and transmit only a subset of the changed model, rather than the entirety of the changed model. Changes may be derived based on localized searching of a graph (e.g., a representation of a utility network model), rather than be searching the entire graph for differences.
  • the present embodiments may improve information synchronization between GIS systems and external systems, and may reduce transmission times and cost by deriving and transmitting the derived differences only.
  • CIM Common Information Model

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Remote Sensing (AREA)
  • Data Mining & Analysis (AREA)
  • Geometry (AREA)
  • Computer Hardware Design (AREA)
  • Structural Engineering (AREA)
  • Evolutionary Computation (AREA)
  • Architecture (AREA)
  • Computational Mathematics (AREA)
  • Mathematical Analysis (AREA)
  • Mathematical Optimization (AREA)
  • Pure & Applied Mathematics (AREA)
  • Civil Engineering (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Instructional Devices (AREA)
  • Image Processing (AREA)
  • Apparatus For Radiation Diagnosis (AREA)
  • Processing Or Creating Images (AREA)
EP20140170924 2013-06-03 2014-06-03 Systeme und Verfahren zur Synchronisierung der Netzwerkmodelle eines geografischen Informationssystems (GIS) Ceased EP2811417A3 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/908,966 US20140358492A1 (en) 2013-06-03 2013-06-03 Systems and methods for synchronizing geographic information system (gis) network models

Publications (2)

Publication Number Publication Date
EP2811417A2 true EP2811417A2 (de) 2014-12-10
EP2811417A3 EP2811417A3 (de) 2014-12-17

Family

ID=50884725

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20140170924 Ceased EP2811417A3 (de) 2013-06-03 2014-06-03 Systeme und Verfahren zur Synchronisierung der Netzwerkmodelle eines geografischen Informationssystems (GIS)

Country Status (8)

Country Link
US (1) US20140358492A1 (de)
EP (1) EP2811417A3 (de)
JP (1) JP2015007968A (de)
KR (1) KR20140142167A (de)
AU (1) AU2014202866A1 (de)
BR (1) BR102014013328A2 (de)
CA (1) CA2851927A1 (de)
IN (1) IN2014CH02618A (de)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106055592A (zh) * 2016-05-20 2016-10-26 浙江大学 一种地图中电力系统电压或负荷的监控方法
CN108566208A (zh) * 2017-12-29 2018-09-21 中国人民解放军战略支援部队信息工程大学 一种层次格网的编码方法及装置
CN111130569A (zh) * 2019-12-17 2020-05-08 佛山科学技术学院 一种空间信息数据自适应容错处理方法及系统

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104463968B (zh) * 2014-12-22 2017-09-05 山东鲁能软件技术有限公司 基于电网gis三维平台的遥感影像双目立体视觉匹配及三维重建方法
US10785107B2 (en) * 2018-05-16 2020-09-22 Microsoft Technology Licensing, Llc Method and apparatus for optimizing legacy network infrastructure
KR102063024B1 (ko) * 2018-08-30 2020-01-07 한국전력공사 스마트시티의 데이터 통합 처리 시스템 및 방법
KR102020339B1 (ko) * 2019-05-07 2019-09-10 홍익대학교 산학협력단 상수도관망 특성을 반영한 무작위 네트워크 모델링 방법 및 장치
CN110737722B (zh) * 2019-09-29 2022-07-05 国网福建省电力有限公司检修分公司 变电站监控后台数据库、scd及rcd的同步系统及方法
CN111026733B (zh) * 2019-12-06 2024-01-30 中国南方电网有限责任公司 版本化电网模型建立方法、装置、计算机设备和存储介质
CN112507501B (zh) * 2020-12-16 2024-04-12 中国南方电网有限责任公司 一种电网接线结构识别方法及系统
CN113343044A (zh) * 2021-07-08 2021-09-03 南方电网数字电网研究院有限公司 一种基于变电站cim图模与配电线路拼接的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106055592A (zh) * 2016-05-20 2016-10-26 浙江大学 一种地图中电力系统电压或负荷的监控方法
CN108566208A (zh) * 2017-12-29 2018-09-21 中国人民解放军战略支援部队信息工程大学 一种层次格网的编码方法及装置
CN111130569A (zh) * 2019-12-17 2020-05-08 佛山科学技术学院 一种空间信息数据自适应容错处理方法及系统

Also Published As

Publication number Publication date
BR102014013328A2 (pt) 2015-06-02
US20140358492A1 (en) 2014-12-04
KR20140142167A (ko) 2014-12-11
JP2015007968A (ja) 2015-01-15
IN2014CH02618A (de) 2015-07-03
CA2851927A1 (en) 2014-12-03
AU2014202866A1 (en) 2014-12-18
EP2811417A3 (de) 2014-12-17

Similar Documents

Publication Publication Date Title
EP2811417A2 (de) Systeme und Verfahren zur Synchronisierung der Netzwerkmodelle eines geografischen Informationssystems (GIS)
CN102750406B (zh) 一种基于模型集和差异模型的电网模型多版本管理方法
CN106777808B (zh) 一种基于标准化cad图纸的网络资源生成方法
CN111274282B (zh) 一种空气质量挖掘系统、方法及数据采集监控装置
CN102685221A (zh) 一种状态监测数据的分布式存储与并行挖掘方法
CN109245923B (zh) 通信光缆路由资源管理方法及系统
CN103606032B (zh) 一种二维电网gis数据集中的方法
CN109523423A (zh) 一种应用系统生成方法、装置、设备及存储介质
Kim et al. A metamodeling approach to unifying IEC 61850 and IEC 61970
CN103226794A (zh) 一种输配电线路数据处理的方法
Bakalov et al. A network model for the utility domain
Ten et al. Extraction of geospatial topology and graphics for distribution automation framework
Hoel et al. Moving beyond transportation: utility network management
CN107357900A (zh) 一种电力系统模型数据版本的控制方法及装置
Ponjavic et al. Spatial data integration in heterogeneous information systems’ environment
Beck et al. Seeing the unseen: delivering integrated underground utility data in the UK
Wuergler et al. Use of CIM for workflows across network operation, asset management and Network planning systems at a distribution utility
Huang et al. Research on WebGIS application based on edge computing
Braun Microservice-based Reference Architecture for Semantics-aware Measurement Systems
Phadnis et al. Platform for Querying CIM-based Models and Data of the Electrical Distribution Network
Shin et al. Cross‐domain approach for operation support in smart grid
El Samad et al. A monitoring service for large-scale dynamic query optimisation in a grid environment
Anderson et al. Enabling Data Exchange and Data Integration with the Common Information Model: An Introduction for Power Systems Engineers and Application Developers
Luhai et al. Research on Operation and Maintenance Data Synchronization Method of Substation Monitoring System based on SCD Model
Ravikumar et al. Towards cim based control centers

Legal Events

Date Code Title Description
PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140603

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 17/22 20060101ALI20141113BHEP

Ipc: H04L 29/08 20060101ALI20141113BHEP

Ipc: H04B 1/66 20060101ALI20141113BHEP

Ipc: H03M 7/30 20060101ALI20141113BHEP

Ipc: G06F 17/30 20060101AFI20141113BHEP

Ipc: H04L 12/24 20060101ALI20141113BHEP

R17P Request for examination filed (corrected)

Effective date: 20150617

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

17Q First examination report despatched

Effective date: 20151103

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20170405