Description:TECHNICAL FIELD
[1] The present disclosure generally relates to a means of transferring data between various networks. In particular, the present disclosure relates to a secure, simple, and effective means of configuring and migrating data between a conventional and utility network.
BACKGROUND
[2] Background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[3] The conventional data models are traditional data models to manage utilities of real-world objects in digital form. These data models correspond to a set of conceptual tools to describe data, its relationships, its semantics, and constraints of consistency. Examples for conventional data are geospatial layers in various industry standard formats, shapefiles, personal geodatabase / file geodatabase with or without geometric network, drawing files etc.
[4] A utility network is a system to manage utility and telecom networks in digital platform (e.g. ArcGIS platform), providing a comprehensive framework of functionality for modelling of utility systems such as electric, gas, water, storm water, wastewater, and telecommunications. These are designed to model all the components such as wires, pipes, valves, zones, devices, and circuits, which is used to build real-world behavior of a network.
[5] Prevalent mechanisms of configuring and migrating conventional data to a utility network data involve use of cumbersome manual processes producing results having a high probability of occurrence of errors. One of these mechanisms involves performing a manual configuration of the utility network model by using individual geo-processing tools in software (e.g. ArcGIS Pro software). While using this mechanism, the users need to execute approximately twelve individual geo-processing tools manually to create and configure the utility network model, and hence this mechanism is time consuming and involves possibility of occurrence of severe errors.
[6] Another mechanism involves using an asset package method (for example, by using a master geo-database) and has limited capabilities such as this mechanism does not have a flexibility of accepting changes as per user specifications and hence is unsuitable for data configuration and migration.
[7] There is therefore a need in the art to provide an improved mechanism that eases task of data configuration of a conventional network and migration of the configured data to the utility network.

OBJECTS OF THE PRESENT DISCLOSURE
[8] It is an object of the present disclosure to configure and migrate conventional network data to utility network data efficiently and correctly.
[9] It is an object of the present disclosure to enable a user to append additional configurations as per their specific requirements.

SUMMARY
[10] In a first aspect, the present disclosure provides a method for extracting, by a server connected to a plurality of client devices via a network, a source schema from a source database of a conventional network, where the source database comprises a plurality of source feature classes data and single source feature class data; generating, by the server, a target schema based on the extracted source schema; creating, by the server, a service area polygon based on plurality of coordinates (e.g. 3) recorded from the extracted source schema; creating, using a client device of the plurality of client devices, the utility network from the extracted source schema by auto extracting the plurality of recorded coordinates from the source schema; configuring, using the client device, a set of items in the utility network based on at least one of a relevant recorded coordinate of the extracted plurality of recorded coordinates; and migrating, by the server, the plurality of source feature classes data of the source database of the conventional network into a single target feature class of the target schema, and the single source feature class data of the source database of the conventional network into a plurality of target feature classes of the target schema, based on a predefined set of instructions.
[11] In some embodiments, the method further includes extracting, by the server, the source database by execution of an automatic tool, and wherein the extraction is performed upon a single click.
[12] In some embodiments, the method further includes auto-creating, by the server, the service area polygon from the source database.
[13] In some embodiments, the method further includes determining and appending, by the server, one or more additional configurations to the target schema.
[14] In some embodiments, the predefined set of instructions comprises mapping of one or more feature classes of the source database to corresponding one or more feature classes of the target schema for the data migration.
[15] In a second aspect, the present disclosure provides a system for configuration and migration of conventional network data to a utility network, said system comprising: a server connected to a plurality of client devices via a network, the server configured to: extract a source schema from a source database of a conventional network, where the source database comprises a plurality of source feature classes data and single source feature class data; generate a target schema based on the extracted source schema; create a service area polygon based plurality of coordinates recorded from the extracted source schema; create, using a client device of the plurality of client devices, the utility network from the extracted source schema by auto extracting the plurality of recorded coordinates from the source schema; configure, using the client device, a set of items in the utility network based on at least one of a relevant recorded coordinate of the extracted plurality of recorded coordinates; and migrate, by the server, the plurality of source feature classes data of the source database of the conventional network into a single target feature class of the target schema, and the single source feature class data of the source database of the conventional network into a plurality of target feature classes of the target schema, based on a predefined set of instructions.
[16] In some embodiments, the server is further configured to extract the source database by execution of an automatic tool, and wherein the extraction is performed upon a single click.
[17] In some embodiments, the server is further configured to auto-create the service area polygon from the source database.
[18] In some embodiments, the server is further configured to determine and append one or more additional configurations to the target schema.
[19] In some embodiments, the predefined set of instructions comprises mapping of one or more feature classes of the source database to corresponding one or more feature classes of the target schema for the data migration.

BRIEF DESCRIPTION OF DRAWINGS
[20] The accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[21] FIG. 1 illustrates a schematic representation of architecture 100 for implementation of a system implemented in a server for configuration and migration of data from a conventional network to a utility network, according to an embodiment of the present disclosure.
[22] FIG. 2 illustrates a schematic representation of the system 200 for configuration and migration of conventional network data to a utility network, according to an embodiment of the present disclosure.
[23] FIG. 3 illustrates a series of execution steps for configuration and migration of the conventional network data to the utility network, in accordance with an embodiment of the disclosure.
[24] FIGs. 4A to 4E illustrate detailed implementation of the execution steps of the system in accordance with an embodiment of the disclosure.
[25] FIGs. 5A to 5P illustrate detailed implementation of additional execution steps of the system in accordance with an embodiment of the disclosure.
[26] FIGs. 6A and 6B illustrate execution of a tool for data migration from a source model to a target utility network model, in accordance with an embodiment of the disclosure.
[27] FIG. 7 illustrates a schematic flow chart for a method 700 for configuration and migration of data from the conventional network to the utility network, according to an embodiment of the present disclosure.
[28] FIG. 8 illustrates an exemplary schematic block diagram of a computer system for implementation of the system of FIG. 2.

DETAILED DESCRIPTION
[29] Brief definitions of terms used throughout this application are given below.
[30] The terms “connected” or “coupled” and related terms are used in an operational sense and are not necessarily limited to a direct connection or coupling. Thus, for example, two devices may be coupled directly, or via one or more intermediary media or devices. As another example, devices may be coupled in such a way that information can be passed there between, while not sharing any physical connection with one another. Based on the disclosure provided herein, one of ordinary skill in the art will appreciate a variety of ways in which connection or coupling exists in accordance with the aforementioned definition.
[31] If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.
[32] As used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
[33] The phrases “in an embodiment,” “according to one embodiment,” and the like generally mean the particular feature, structure, or characteristic following the phrase is included in at least one embodiment of the present disclosure and may be included in more than one embodiment of the present disclosure. Importantly, such phrases do not necessarily refer to the same embodiment.
[34] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such details as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.
[35] The present disclosure generally relates to a means of transferring data between various networks. In particular, the present disclosure relates to a secure, simple, and effective means of configuring and migrating data between a conventional and a utility network.
[36] Conventional mechanisms of configuring and migrating utility network data involve cumbersome manual processes with higher probability of errors. The disclosure provides an improvised tool having a mechanism to create and configure the utility network data and migrate conventional network data to the utility network while incurring least number of errors. The disclosed system and method enables to extract source model configurations in a user friendly format and has flexibility to take updates for additional customer requirements. The disclosed system and method applies the source model configurations to a newly created utility network target data model.
[37] The disclosed system and method facilitates the user to append extra configurations as per their specific requirements by initially extracting all existing configurations from the source data model, taking updates for additional requirements and applying all these configurations (subtypes, domains, fields, relationships, feature classes, data sets) to the target data model.
[38] Those skilled in the art would appreciate that the utility network provide an operational view of how all dynamic devices of utility are currently configured and analyze how physical network of devices can be affected by real-world events such as storms, outages, or equipment failure, etc. The utility network enables to view inside complex assemblies of devices and lines, manage how assets are connected within the devices and visualize a selected pressure zone or circuit with a display filter. The utility network determines number of customers with access to a resource. For example, a user can create a load summary report to present number of customers being supplied by a specific circuit in an electric network. It is possible to model multiple utility systems within one utility network and run tracing analysis across all of them. For example, an outage from an electrical network can affect delivery of another resource, such as gas or water. The user can run a trace across all systems involved, see where the problems lie, and decide on best course of action.
[39] FIG. 1 illustrates a schematic representation of architecture 100 for implementation of a system for configuration and migration of data from a conventional network to a utility network, according to an embodiment of the present disclosure. The architecture 100 includes a server 102 implementing a system (e.g. system 200 of FIG. 2, described below), where the server 102 is connected to a source database 104 via a network. Those skilled in the art would appreciate that, the network may be wireless network, wired network or a combination thereof that can be implemented as one of the different types of networks, such as Intranet, Local Area Network (LAN), Wide Area Network (WAN), Internet, and the like. Further, the network can either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like. The server 102 may be an application server, a database server, a file server, a real time communication server and the like.
[40] A plurality of clients 106-1, 106-2…106-N (which may be collectively referred to herein as clients 106 and may be individually referred to herein as client 106) may be communicably coupled to the server 102. The clients 106 may be associated with the client devices 108-1, 108-2 … 108-N respectively (which may be collectively referred to herein as client devices 108 and may be individually referred to herein as client device 108), and may include, but are not limited to, personal computers, smart devices, web-enabled devices, hand-held devices, laptops, mobile phones mobile device, for example, personal digital assistant (PDA), smartphone, tablet, laptop or smart watch and the like, and may allow interaction with the server 102. By way of an example, the client devices 108 may be local, remote or cloud-based devices or a mix of local, remote and cloud-based devices and may facilitate migration of the data.
[41] FIG. 2 illustrates a schematic representation of the system 200 for configuration and migration of conventional network data to a utility network, according to an embodiment of the present disclosure. The system includes a processor 202 communicably coupled with a memory 204. The memory 204 stores instructions executable by the processor(s) 202 for configuration and migration of data. In some embodiments, the processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in the memory 204 for implementing the system 200. Any reference to a task in the present disclosure may refer to an operation being or that may be performed on data. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like. In some embodiments, the system 200 may include an interface 206. The interface 206 may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface 206 may also provide a communication pathway for one or more components of the system 200. Examples of such components include, but are not limited to, the processing engine 208 and the database 210. In an embodiment, the interface 206 may be communicatively coupled to, for example, a touch based display screen, keypad, trackball, or other components that receives mechanical, audio, or other input from the user.
[42] In some embodiments, the system 200 includes the processing engine 208. The processing engine 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine 208 may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine 208 may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine 208. In such examples, the system 200 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 200 and the processing resource. In other examples, the processing engine 208 may be implemented by electronic circuitry.
[43] In some embodiments, the processing engine 208 may include a data preparation engine 212, a data mapping engine 214, a staging database creation engine 216, a data loading to staging database engine 218, a post process data engine 220, a loading engine 222, and other engine(s) 224. The other engine(s) 224 may include engines configured to perform one or more functions ancillary functions associated with the processing engine 208.
[44] The system 200 facilitates to configure and migrate the conventional network data to the utility network. The system 200 includes a server connected to a plurality of client devices via a network.
[45] The data preparation engine 212 extracts a source schema from a source database of a conventional network. The source database comprises a plurality of source feature classes data and single source feature class data. The data preparation engine 212 is configured to extract the source database by execution of an automatic tool. In an embodiment, the extraction of the source database is performed upon a single click.
[46] The data mapping engine 214 generates a target schema based on the extracted source schema. In an embodiment, one or more additional configurations may be determined and appended to the target schema.
[47] The staging database creation engine 216 creates a service area polygon based on plurality of coordinates recorded from the extracted source schema. In an embodiment, the service area polygon is created from the source database.
[48] The post process data engine 220 facilitates a client device of the plurality of client devices to create a utility network from the extracted source schema by auto extracting the plurality of recorded coordinates from the source schema. The post process data engine facilitates to configure a set of items in the utility network based on at least one of a relevant recorded coordinates of the extracted plurality of recorded coordinates.
[49] The loading engine 222 migrates the plurality of source feature classes data of the source database of the conventional network into a single target feature class of the target schema, and the single source feature class data of the source database of the conventional network into a plurality of target feature classes of the target schema, based on a predefined set of instructions. The predefined set of instructions includes mapping of one or more feature classes of the source database to corresponding one or more feature classes of the target schema for the data migration.
[50] FIG. 3 illustrates a series of execution steps for configuration and migration of the conventional network data to the utility network, in accordance with an embodiment of the disclosure. With respect to FIG. 3, the execution starts with a source schema being extracted at 302, a target schema sheet preparation at 304, a service area polygon creation at 306, a utility network creation at 308, a utility network configuration at 310, and a data migration at 312.
[51] At 302, the source schema is extracted with a single click by executing a programming language based tool, for example, a python based tool, on a source database. The system 200 facilitates to accurately extract detailed schema in the single click and in minimal duration from multiple feature classes of a source GDB (Geo DataBase).
[52] At 304, a target schema sheet preparation is done by using an automation technique that auto updates the target schema sheet from the source GDB efficiently and error free. The target schema sheet is prepared such that duplicate fields are deleted and content from the source schema sheet is auto populated in the target schema sheet.
[53] At 306, a service area polygon is auto created by using recorded coordinates from the source GDB. The tool facilitates to auto extract plurality of coordinates from the source GDB and automatically create the “Service Area” polygon in the target schema in a limited time frame thereby reducing human errors.
[54] At 308, the utility network is created automatically and named spontaneously using a pre-available tool. The pre-available tool may auto extract coordinates from the source GDB and create the “service area” polygon in the target schema.
[55] At 310, the utility network is configured automatically using the pre-available tool that auto configures the target utility network geo-database model by reading data from the target schema sheet one by one based on the pre-defined order. At 310, a set of items are configured automatically. The set of items to be configured may include, for example, (a) Domain network Creation, (b) Network Category Creation, (c) Domains Creation, (d) Domain Values Creation, (e) Network Attribute Creation, (f) Asset Groups Creation, (g) Fields Creation, (h) Domain Assignment, (i) Network Attribute Assignment, (j) Terminals Creation, (k) Set Terminals, (l) Set Network Category, (m) Association Roles, (n) Tiers Creation, (o) Edge Connectivity, and (p) Sub-network Definition.
[56] At 312, a data migration operation is performed which involves migrating/transferring multiple source feature classes data into a single target feature class, and a single source feature class data into multiple target feature classes based on a predefined set of instructions. The pre-available tool may auto migrate the records from the source to the target model by just showing the source FC & target FC in simple tool dialogue box.
[57] With respect to the source schema extraction at 302, a set of parameters may be required to be populated in the tool. This is done to extract source geo-database schema to an external file, for example, an excel file. With respect to FIG. 4A is shown the set of parameters that are to be populated, for example, selecting a file GDB (input Geo DataBase), selecting an output folder location for saving an excel file, and entering name of an output excel file.
[58] The tool may extract a source GDB schema in an excel sheet having following worksheets: (a) GDB_Summary_Sheet, (b) Property_Sheet, (c) Domain_Sheet, and (d) Relationship_Class. By way of an example, the GDB_Summary_Sheet includes the GDB summary report i.e., total number of datasets, feature classes, standalone feature classes, relationship classes and tables. The Domain_Sheet worksheet includes the domain details which are used in form of pull-down menus in GIS data. The Relationship_Class worksheet includes a logical relationship built between feature classes, between feature classes and tables etc. in GIS.
[59] In an embodiment, with respect to the target schema preparation at 304, one or more configurations from the output excel files are updated in, for example, a standard excel template along with any additional requirements.
[60] As may be appreciated, the tool may be, for example, a python based tool and loaded in desktop GIS software, for example, in ArcGIS Pro environment as shown in FIG. 4B.
[61] Subsequently, with respect to a service area polygon creation at 306, the completed output excel files are sent as an input to the tool as shown in FIG. 4C. The tool may create a polygon feature class (i.e., Service Territory) in the target model, and may assign a projection system from the worksheet ServiceTerritory of schema. In an embodiment, the tool may create a polygon feature (record/object) in a service territory feature class as per coordinates available in the work sheet Service Territory, as illustrated in FIG. 4D.
[62] In another embodiment and as illustrated in FIG. 4E, once the tool is executed - the tool may configure the target model as per requirements/specifications available in the excel template sheet. The tool may create a name for the utility network and corresponding projection as per information available in the worksheet, for example, UN_Info of schema excel.
[63] Once the configuration tool is executed, next described couple of steps may be auto processed as these steps may be in-built in the tool.
[64] For domain network creation and as illustrated in FIG. 5A, the tool may create Domain Network Name, Domain Network Alias Name, Tier Definition and Subnet_Controller_Category from work sheet Domain_Network of the schema.
[65] Further, for network category creation, the tool may add the network category name to the utility network from the worksheet Network_Category of schema excel sheet as illustrated in FIG. 5B.
[66] As illustrated in FIG. 5C, for domains creation, the tool may extract domains from the work sheet Domains of the schema excel and assign the extracted domains to the target model.
[67] Also, for domain values creation, the tool may extract the domain values from the work sheet Domain values of schema excel and assign these values to the target model as illustrated in FIG. 5D.
[68] In addition, for network attribute creation, the tool may add the network attribute to each feature class from the work sheet Network Attribute of schema excel as illustrated in FIG. 5E.
[69] For asset groups creation, as illustrated in FIG. 5F, the tool may add the asset group (subtype name) and subtype code (subtype code) to each feature class of the target model as available in work sheet asset group of the schema excel.
[70] For fields creation, the tool may add the fields for all feature classes in the target model. This maintains field length, field type, field alias, is nullable, etc. details from the work sheet fields of schema excel sheet as illustrated in FIG. 5G.
[71] For domain assignment, the tool may assign the domain values to appropriate fields in the target model as per the work sheet Domain Assignment of schema sheet, as illustrated in FIG. 5H.
[72] For network attribute assignment, the tool may assign the network attribute to target model feature classes from the work sheet Network Attribute Assignment, as illustrated in FIG. 5I.
[73] For terminals creation, the tool may create and assign the Terminal Name, Directionality (1-way/2-way), Terminals (Source/Load), Upstream (True/False), Valid Configuration, Default Configuration to the terminals of the target model from the work sheet terminals of schema excel, as illustrated in FIG. 5J.
[74] For set terminals, the tool may configure the terminals to the asset group and asset type level from the worksheet Set Terminal of schema excel, as illustrated in FIG. 5K.
[75] For set network category, the tool may set the network categories to the asset group of each feature class in the target model from the work sheet set network categories of schema sheet, as illustrated in FIG. 5L.
[76] For setting association rules, the tool may create association roles for each feature class-asset group and asset type level such as Role Type (structure/container), View Scale, Deletion Schematics (restricted) from the work sheet Association Role of schema excel, as illustrated in FIG. 5M.
[77] For tiers creation, the tool may create Tier Name, Tier Rank, Topology Type in target model as per information available in the work sheet Tier of schema excel, as illustrated in FIG. 5N.
[78] For edge connectivity, the tool may create edge connectivity rules (such as any vertex rule) in the target model for each feature class on asset group and asset type level as per the information available in work sheet Edge Connectivity of schema excel, as illustrated in FIG. 5O.
[79] For Subnetwork definition, the tool may create subnetwork definitions for tiers such as TierName, Support_Disjoint_Subnetwork, Valid_Subnetwork_Controllers, Valid_Devices, Valid_Lines,Aggregated_Lines_Subnet_FeatClass,Subnetwork_Diagram_Templates as per the information available in work sheet Subnetwork Definition of schema sheet, as illustrated in FIG. 5P.
[80] In an embodiment, for data migration from the source model to the target utility network model, a tool, for example, “Data Translator.exe.” is executed as illustrated in FIG. 6A. Further, as illustrated in FIG. 6B, source feature class and target feature class are picked for an auto migration process.
[81] FIG. 7 illustrates a schematic flow chart for a method 700 for configuration and migration of data from the conventional network to the utility network, according to an embodiment of the present disclosure. With respect to FIG. 7, at 702, a server is configured to extract a source schema from a source database of a conventional network. The source database includes a plurality of source feature classes data and single source feature class data. At 704, a target schema based on the extracted source schema is generated. At 706, a service area polygon is created based on plurality of coordinates recorded from the extracted source schema. At 708, a client device creates the utility network from the extracted source schema by auto extracting the plurality of recorded coordinates from the source schema. At 710, the client device configures a set of items in the utility network based on at least one of a relevant recorded coordinate of the extracted plurality of recorded coordinates. Further, at 712, the server migrates the plurality of source feature classes data of the source database of the conventional network into a single target feature class of the target schema, and the single source feature class data of the source database of the conventional network into a plurality of target feature classes of the target schema, based on a predefined set of instructions.
[82] FIG. 8 illustrates an exemplary schematic block diagram of a computer system 800 for implementation of the system 200 of FIG. 2. As shown in FIG. 8, the computer system 800 can include an external storage device 810, a bus 820, a main memory 830, a read only memory 840, a mass storage device 850, communication port 860, and a processor 870. A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. Examples of processor 870 include, but are not limited to, an Intel® Itanium® or Itanium 2 processor(s), or AMD® Opteron® or Athlon MP® processor(s), Motorola® lines of processors, FortiSOC™ system on chip processors or other future processors. Processor 870 may include various modules associated with embodiments of the present invention. Communication port 860 can be any of an RS-232 port for use with a modem based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fibre, a serial port, a parallel port, or other existing or future ports. Communication port 860 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which computer system connects. Memory 830 can be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory 840 can be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or BIOS instructions for processor 870. Mass storage 850 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), e.g. those available from Seagate (e.g., the Seagate Barracuda 7102 family) or Hitachi (e.g., the Hitachi Deskstar 7K1000), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks (e.g., SATA arrays), available from various vendors including Dot Hill Systems Corp., LaCie, Nexsan Technologies, Inc. and Enhance Technology, Inc.
[83] Bus 820 communicatively couples processor(s) 870 with the other memory, storage, and communication blocks. Bus 820 can be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects processor 870 to software system.
[84] Optionally, operator and administrative interfaces, e.g., a display, keyboard, and a cursor control device, may also be coupled to bus 820 to support direct operator interaction with a computer system. Other operator and administrative interfaces can be provided through network connections connected through communication port 860. The external storage device 810 can be any kind of external hard-drives, floppy drives, IOMEGA® Zip Drives, Compact Disc - Read Only Memory (CD-ROM), Compact Disc-Re-Writable (CD-RW), Digital Video Disk-Read Only Memory (DVD-ROM). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[85] Thus, the disclosed method and system try to overcome the problem of migrating a conventional geometric model to latest utility network model for all utilities. Conventional method of configuring and migrating utility network data is a cumbersome manual process with higher probability of occurrence of errors. The disclosed method and system provides a tool that eases the task of migration of the data from the conventional geometric model to the utility network. The tool facilitates the user to append extra configurations as per end customer requirements not having any coding skills. The configurations include, for example, subtypes, domains, fields, relationships, feature classes, data sets and the like.
[86] As may be appreciated, the utility network leverages ArcGIS enterprise to create a seamless Web GIS and enables sharing of the utility network across an entire organization, thus providing an authoritative view of the organization’s assets. The utility network may be designed to allow for new levels of specification in analysis such as identifying areas of water loss or determining valves to close in the event of a water main break. Further, assets and customers affected by outages may also be identified.
[87] In addition, the created utility network may possess advanced asset modeling capabilities, a modern web GIS architecture, and analysis tools that provide unprecedented levels of information gathering for better operational awareness and decision-making. The utility network may also serve as a centralized system of record that may be accessed by everyone at the utility on any of a device at any time resulting in increased efficiencies in daily operations, planning projects, and responding to emergencies. The utility network may also be integrated with other business systems such as work order management and SCADA for a fully automated operational view in real time.
[88] Further, the utility network may enable utilities to model location of assets, including modeling of internal configurations of complex assemblies such as pump houses, meter pits, and valve assemblies. The flow of resources through these complex assemblies is accounted for during network analysis. Yet assets can also be hidden in map visualizations to de-clutter an operational view. The assets that control flow of commodities, such as valves, may be modeled to reflect a directional flow of those commodities through pipes and depict what is happening in real time for enabling additional analysis and visualizations of the network.
[89] Furthermore, network diagrams may be created from the utility network for providing a schematic view of network connections. These diagrams deliver a clear visualization of connectivity and relationships between features in the network that is not always apparent in a traditional map view.
[90] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refer to at least one of something selected from the group consisting of A, B, C ….and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc. The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the appended claims.
[91] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions, or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art. , Claims:1. A system implemented in a server for configuration and migration of conventional network data to a utility network, the server communicatively coupled to a plurality of client devices via a network, the system comprising:
a processor coupled with a memory, the memory storing instructions executable by the processor to:
extract a source schema from a source database of a conventional network, where the source database comprises a plurality of source feature classes data and single source feature class data;
generate a target schema based on the extracted source schema;
create a service area polygon based on plurality of coordinates recorded from the extracted source schema;
create, using a client device of the plurality of client devices, the utility network from the extracted source schema by auto extracting the plurality of recorded coordinates from the source schema;
configure, using the client device, a set of items in the utility network based on at least one of a relevant recorded coordinate of the extracted plurality of recorded coordinates; and
migrate the plurality of source feature classes data of the source database of the conventional network into a single target feature class of the target schema, and the single source feature class data of the source database of the conventional network into a plurality of target feature classes of the target schema, based on a predefined set of instructions.
2. The system of claim 1, wherein the server is further:
extract the source database by execution of an automatic tool, and wherein the extraction is performed upon a single click.
3. The system of claim 1, wherein the server is further:
auto-create the service area polygon from the source database.
4. The system of claim 1, wherein the server is further:
determine and append one or more additional configurations to the target schema.
5. The system of claim 1, wherein the predefined set of instructions comprises mapping of one or more feature classes of the source database to corresponding one or more feature classes of the target schema for the data migration.
6. A method for configuration and migration of conventional network data to a utility network, said method comprising:
extracting, by a server connected to a plurality of client devices via a network, a source schema from a source database of a conventional network, where the source database comprises a plurality of source feature classes data and single source feature class data;
generating, by the server, a target schema based on the extracted source schema;
creating, by the server, a service area polygon based on plurality of coordinates recorded from the extracted source schema;
creating, using a client device of the plurality of client devices, the utility network from the extracted source schema by auto extracting the plurality of recorded coordinates from the source schema;
configuring, using the client device, a set of items in the utility network based on at least one of a relevant recorded coordinate of the extracted plurality of recorded coordinates; and
migrating, by the server, the plurality of source feature classes data of the source database of the conventional network into a single target feature class of the target schema, and the single source feature class data of the source database of the conventional network into a plurality of target feature classes of the target schema, based on a predefined set of instructions.
7. The method of claim 6, further comprising:
extracting, by the server, the source database by execution of an automatic tool, and wherein the extraction is performed upon a single click.
8. The method of claim 6, further comprising:
auto-creating, by the server, the service area polygon from the source database.
9. The method of claim 6, further comprising:
determining and appending, by the server, one or more additional configurations to the target schema.
10. The method of claim 6, wherein the predefined set of instructions comprises mapping of one or more feature classes of the source database to corresponding one or more feature classes of the target schema for the data migration.