Utility companies typically rely on meter reading to determine consumption of a utility by its customers. In some utility meter reading applications, operators drive vehicles equipped with radio-equipped data collection units around an area to read electric, gas, and/or water meters. The meters are equipped with modules that allow them to send and receive signals. This style of meter reading, sometimes referred to as mobile automatic meter reading (MAMR), allows meter reading to be completed without direct access to the meter.
MAMR is sometimes used in saturated areas where there may be large populations of meters, difficult-to-access meters, or hazardous-to-read meters. When used in such areas, MAMR can dramatically improve meter reading efficiency. For example, a single data command unit transceiver reads an average of 10,000-12,000 meters in an eight-hour shift, and can read up to 24,000 meters per day, depending on meter density and system use.
Routes for MAMR are typically defined geographically and may include hundreds or thousands of meters. The meters on the route are read using one or more techniques. For example, with a wake-up technique, a MAMR vehicle moves through an area and sends wakeup signals to notify the meters in the area to send meter reading data. With a bubble-up technique, the MAMR vehicle simply picks up broadcasted signals from all meters in its vicinity. To determine the endpoints in a route, MAMR systems typically rely on route information provided by the utility. In some cases, the route information includes a list that identifies each meter using a unique meter ID and address assigned to the meter. The route information is typically formulated in advance of driving the route, and is often based on the geographic location of each meter relative to other meters in the route. For example, a MAMR route may have starting and ending points, and meters are read according to proximity from a vehicle moving between the starting and ending points.
Routes consisting of lists of meter addresses are typically provided in advance of MAMR activities, typically in the form of a route file. Such route files typically contain street address information consisting of twenty or fewer characters for each endpoint, and are configured to be used in pre-existing head-end legacy systems, such as PreimerPlus4™, MV-RS™, and Integrator™, all by Itron, Inc. of Spokane, Wash.
The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the claimed invention. In the drawings, the same reference numbers identify identical or substantially similar elements or acts. To facilitate the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced (e.g., element 204 is first introduced and discussed with respect to
A portion of this disclosure contains material to which a claim for copyright is made. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure (including Figures), as it appears in the Patent and Trademark Office patent file or records, but reserves all other copyright rights whatsoever.
The invention will now be described with respect to various embodiments. The following description provides specific details for a thorough understanding of, and enabling description for, these embodiments of the invention. However, one skilled in the art will understand that the invention may be practiced without these details. In other instances, well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of the embodiments of the invention.
It is intended that the terminology used in the description presented be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific embodiments of the invention. Certain terms may even be emphasized below; however, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.
I. Overview
The method and system described herein provide an endpoint location file format that facilitates mobile automatic meter reading (MAMR) activities, such as route mapping. Some of the MAMR activities may occur at a mobile data collection system. The mobile data collection system may include a combination of components (including both hardware and software) that generally facilitate the collection of meter data from utility meters (e.g., electric, gas, water, etc.) and the graphical display of meter routes in progress via the use of maps or other features.
An endpoint location file configured in accordance with the endpoint location file format may originate in a customer information system associated with a utility provider. For example, the endpoint location file may contain location information for all endpoints recognized within the utility's customer information system. The location information allows the mobile data collection system to identify the location of each endpoint. For example, the endpoint location file may contain valid and complete address information that the mobile data collection system can use to calculate latitude/longitude for each endpoint. In addition, or alternatively, the endpoint location file may contain pre-determined location coordinates. Information from the endpoint location file may be used during operation of the mobile data collection system to facilitate the reading of meter data while traveling a route (e.g., route mapping). The information from the endpoint location file may also be used to review how a route was driven (e.g., route playback to assess efficiency of the driving route or identify issues related to the route).
In some embodiments, the endpoint location file is used in addition to one or more route files that contain information about specific routes in the meter reading system. Such route files may be created by the meter reading application and then imported and read into the mobile data collection system. When a route has been completed, the corresponding route file (containing meter reading data collected on the completed route) can be exported from the mobile data collection system back to the meter reading application and/or the utility main frame/billing system. Accordingly, in one embodiment, the endpoint location file may provide the information needed to map endpoints in a mapping interface provided by the mobile data collection system by matching the endpoint location file coordinates for endpoints to a route file.
The mobile data collection system may provide an editor component that allows the user to, for example, view, import, edit, and export endpoint location files. For example, an IMPORT function accessed through the editor component may allow the user to import a particular endpoint location file from the customer information system. In some embodiments, the editor component calculates location coordinates for a record, set of records, or the entire endpoint location file. Accordingly, an IMPORT AND CALCULATE function may allow the user to import a particular endpoint location file from the customer information system and then calculate location coordinates for all addresses that do not have them. Likewise, partially missing or incorrect address information can be determined based on provided latitude and longitude information for each endpoint (e.g., GPS coordinates generated by another system).
An UPDATE function allows the user to add to or update the information in an imported endpoint location file. For example, if the user has added additional endpoints to the meter reading system, the user might choose to update the mobile data collection system with the new information rather than importing (and thereby replacing) the entire endpoint location file.
The endpoint location file may be configured to allow the user to search for specific information contained within the endpoint location file. For example, a filtering technique may allow for a comparison of the endpoint location file to a route file that the user has imported into the mobile data collection system. For example, if the user has imported Route A into the mobile data collection system, the user may select to view the records in the endpoint location file that correspond to the records in Route A.
II. Representative System
Aspects of the invention can be embodied in a special purpose computer or data processor that is specifically programmed, configured, or constructed to perform one or more of the computer-executable instructions explained in detail herein. Aspects of the invention can also be practiced in distributed computing environments where tasks or modules are performed by remote processing devices, which are linked through a communication network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Aspects of the invention may be stored or distributed on computer-readable media, including magnetically or optically readable computer disks, as microcode on semiconductor memory, nanotechnology memory, organic or optical memory, or other portable data storage media. Indeed, computer-implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Internet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or may be provided on any analog or digital network (packet switched, circuit switched, or other scheme). Those skilled in the relevant art will recognize that portions of the invention reside on a server computer, while corresponding portions reside on a client computer, such as a mobile device.
Referring to
While not illustrated in detail, each meter (102, 104, or 106) includes a storage component (not shown) for storing collected data before transmission to a data collection system. The storage component may also store information identifying the meter, such as a meter identification number. In addition, each meter may be configured with a receiver/transmitter telemetry device (e.g., an encoder receiver transmitter (ERT)) capable of sending and receiving signals to and from a mobile data collection system 108. In general, these components (meter, storage, and telemetry device) may be collectively referred to as an “endpoint.” However, the term “endpoint” may herein refer to any one of a number of possible configurations for locally collecting data, such as utility consumption data, and not only the sample configuration described above.
In some embodiments, the mobile data collection system 108 may send a wake-up signal to an endpoint. The received wake-up signal prompts the endpoint to transmit meter reading data to the mobile data collection system 108. In alternative embodiments, “bubble-up” (broadcast) techniques may be used instead of the “wake-up” technique described above. In yet other embodiments, the mobile data collection system 108 may be capable of point-to-point communications with specific endpoints.
To facilitate MAMR or similar techniques, the mobile data collection system 108 may be installed in a vehicle 109 or be otherwise configured to be transported through a route. For example, the vehicle may include the appropriate antennas, power cables, mounts, etc.
The system 100 also includes a host processing system and meter reading application(s) 110 for processing collected meter reading data. In some embodiments, the host processing system and meter reading application 110 uses customer information to create route files used when driving the route to collect meter data. Accordingly, the host processing system and meter reading application 110 may be operating in association with systems operated by a utility company, such as a utility billing system 112 or, more generally, a customer information system (CIS). In this way, the host processing system and meter reading application 110 can also be used to communicate data to the mobile data collection system 108. This information may include both route file and endpoint location file data, which may be stored in a data store 114 prior to export from the billing system/CIS or utility host processor 110. However, in some embodiments, endpoint location files may also be transmitted directly from the billing system/CIS 112 to the mobile data collection system 108.
Data collected by the mobile data collection system 108 is returned to the meter reading application 110 for processing. Examples of meter reading applications may include MV-RS™, Premierplus4™, Viena™, and Integrator™, all by Itron, Inc. of Spokane, Wash.
Referring to
A processor 206 and memory or other data storage 208 provide capabilities to control several processes, including management of collected meter reading data and processing of input for purposes of determining an efficient route for meter reading. For example, the memory 208 can store not only collected meter data, but also route and other information. A CD ROM 209 may handle removable media in the mobile data collection system 108. A user input/output component 210 provides an appropriate user interface for an operator of the data collection system 108. For example, the mobile data collection system 108 may provide a color touch screen display for ease of use and clear graphical mapping displays. Other user input/output options may be used including mouses, microphones, speakers, joysticks, keyboards, LCD screens, audio, etc.
One application of the input/output component 210 includes displaying and controlling mapping images generated by a mapping component 212. In this way, the operator is provided with feedback, so that he or she can determine which meter readings have been completed on a particular route and so he or she can view meters on the route in relation to the vehicle and to other meters. The mapping component 212 (e.g., Microsoft MapPoint) may interface with the mobile collector applications component 204.
Any one of the components described above may be contained on a notebook computer or other device that can be easily removed from the vehicle when not in use, such as the Itronix™ GoBook MAX™.
In some embodiments, route data may be transferred to and from the mobile data collection system 108 using a removable flash card 213. For example, an operating system (not shown) associated with the mobile data collection system 108 may recognize the flash card 213 as a removable drive, allowing standard file access. In other embodiments, the routes may be transferred to the mobile data collection system via a local area network (LAN), a wide area network (WAN), etc. Periodic data backups to the flash card can be configured in the mobile collector applications component 204.
The mobile data collection system 108 also includes a radio based remote reading component 214, which, in some embodiments, may include a transceiver. The radio based remote reading component 114 may, via a radio antenna 215, send signals to wake-up meters that function in “wake-up” mode and to receive and manage incoming data. In addition to or as an alternative to the mapping component 212, the mobile data collection system 108 may also include a Global Positioning System (GPS) component 216, a Global Information Services (GIS) component 218, or like systems (e.g., systems that facilitate location determination via cellular telephone network), which may be used to facilitate mapping and other related functionality, such as route playback features.
In general, GPS uses a network of satellites that continuously transmit coded information that makes it possible to precisely triangulate locations on earth by measuring the distance from satellites. GPS signals broadcast line of sight, meaning that the signals will pass through clouds, glass, and plastic but will not pass through most solid objects, including people, buildings, and mountains. The GPS receiver provides increased accuracy of positioning data as the number of accessible satellites increases. Accordingly, aspects of the mapping component can be configured to inform the operator of the number of satellites available.
Where the GPS component 216 is implemented, operators of the mobile data collection system 108 can use latitude and longitude coordinates to locate endpoints in the field and to track the progress of the mobile collection vehicle while driving the route. In some embodiments, the GPS component 216 uses embedded mapping software to map the GPS coordinates in any given area (including geography, roads, landmarks, etc.). In some embodiments, an endpoint location file (shown as input 220) provided to the mobile data collection system 108 provides information on endpoint locations.
III. Data Structure and Format of Endpoint Location File
Referring to
In some embodiments, the endpoint location file is a comma delimited file, such as a comma separated variables (.CSV) text file. However, almost any type of file format can be used without departing from the scope of the invention. With a comma delimited file, a comma placeholder separates each field in the endpoint location file layout. Blank spaces between commas may be allowed as the mobile data collection system may be configured to calculate such missing information based on the provided information. In some embodiments, a verification process invoked during import of the endpoint location file to the mobile data collection system removes blank spaces at the beginning and end of fields, trims leading zeroes from endpoint ID numbers, and/or performs other data formatting.
IV. User Interface
Various user screens, views, and other interfaces may allow users to monitor and manage meter reading route activities using information from endpoint location files. Examples of such screens are described with respect to
In some cases, the screens or pages provide facilities to receive input data, such as a form with fields to be filled in, pull-down menus or entries allowing one or more of several options to be selected, buttons, sliders, hypertext links, or other known user interface tools for receiving user input. While certain ways of displaying information to users are shown and described with respect to certain Figures, those skilled in the relevant art will recognize that various other alternatives may be employed.
The pages or screens are stored and/or transmitted as display descriptions, as graphical user interfaces, or by other methods of depicting information on a screen (whether personal computer, PDA, mobile telephone, or other) where the layout and information or content to be displayed on the page are stored in memory, database, or other storage facility.
When implemented as web pages or wireless content, the screens are stored as display descriptions, graphical user interfaces, or other methods of depicting information on a computer screen (e.g., commands, links, fonts, colors, layout, sizes and relative positions, and the like), where the layout and information or content to be displayed on the page are stored in a database. In general, a “link” refers to any resource locator identifying a resource on a network, such as a display description provided by an organization having a site or node on the network. A “display description,” as generally used herein, refers to any method of automatically displaying information on a computer screen in any of the above-noted formats, as well as other formats, such as email or character/code-based formats, algorithm-based formats (e.g., vector generated), or matrix or bit-mapped formats. While aspects of the invention are described herein using a networked environment, some or all features may be implemented within a single-computer environment.
In general, for ease in describing features of the invention, aspects of the invention will now be described in terms of a user (e.g., a mobile data collection system operator) interacting with the mobile data collection system. However, one skilled in the art will recognize that the various functions and operations described below are facilitated by various routines and components within the system.
Referring to
The editor component may include a toolbar 402 by which the user may request to perform several functions on the endpoint location form. In the illustrated example, such functions include an IMPORT function 404, an IMPORT AND CALCULATE function 406, an EXPORT function 408, an EXPORT FILTERED function 410, an UPDATE function 412, an APPLY function 414, a CANCEL function 416, a CURRENT LOCATION function 418, a CALCULATE SELECTED function 420, a CALCULATE ALL function 422, and a FILTER function 424. Various aspects of such functions are described with respect to
A. Importing an EndPoint Location File and Related Functionality
Once an endpoint location file is created, a user can import it from a customer information system or other location into an application associated with the mobile data collection system. In the illustrated embodiment, importing can be associated with additional functionality such as calculating location coordinates and updating the endpoint location file. In some embodiments, file activities, including imports, updates, and calculations, create a file activity log. In the event of a failed process, the application of the mobile data collection system may prompt the user to view the log.
Referring to
This dialog box provides 504 the user with the option to verify the imported file to check for format and/or data type errors, and thereby prevent associated problems, such as halting the entire import. A failed verification may be analyzed via a file activity log 506 that corresponds to the endpoint location file, as shown in
Referring to
In some embodiments, when the user selects to import an endpoint location file, any previously existing endpoint location data used by the application (e.g., in a previous session) is replaced with information from the newly imported endpoint location file.
Referring again to
B. Filtering an Endpoint Location File
Because a utility provider may create a single endpoint location file that contains data for all of its endpoints, an imported endpoint location file may be quite large. Accordingly, the mobile data collection system may provide the FILTER function 424 that allows a user to work with only a portion of the endpoint data (e.g., only endpoint information for a particular route).
Referring to
Referring to
After the user inputs the filter criteria and selects an OK button 808, the mobile data collection system displays the filter results (see e.g.,
C. Calculating Location in an Endpoint Location File
Not all endpoint location files have complete location information (e.g., lat/long coordinates) for each record (e.g., endpoint). However, the mobile data collection system can still rely on such “blank” records provided that coordinate information can be calculated using address information (e.g., valid street address and a valid city or zip code) associated with such records. A similar operation may be performed to update incomplete or incorrect address information based on provided or calculated coordinate information (e.g., the mobile data collection system may update the city, state, zip, and/or country fields with correct data based on the given coordinates). For example, after the mobile data collection system calculates coordinates for a record with missing country information, the mobile data collection system may fill in the missing country information. Similarly, if the country was misspelled “Untd Staets,” the endpoint location file editor would correct it to “United States.”
In some embodiments, to calculate the current location (latitude and longitude) for a record or group of records the user highlights selected records and selects the CALCULATE SELECTED function 420 from the editor component toolbar 402 or a tools menu 902, as shown in
Referring to
D. Updating and Editing an Endpoint Location File
There may be more than one way to modify the contents of an imported endpoint location file. In some embodiments, it may be possible to add or delete complete records using the UPDATE function 412. For example, if the user has added additional endpoints to the meter reading system, the user might choose to update the mobile data collection system with the new information rather than having to report the information and then import a new endpoint location file. In some embodiments, updating an endpoint location file adds and/or overwrites records in the endpoint location file that has been imported to the mobile data collection system.
To add to or update information in an endpoint location file that the user has already imported into the mobile data collection system, the user may select the UPDATE function 412 from the editor component toolbar 402. The user then browses and selects the desired endpoint location file. When the update is complete, a message may appear indicating the number of records that have been updated, which can be viewed via filtering. In some embodiments, if the user selects another record before clicking update, an update confirmation dialog appears.
In addition to writing over or creating new records via the update feature, it may also be possible to edit existing records (e.g., add or correct missing or inaccurate information within a record) by using an editing feature accessed via the editor component 400. Referring to
In some embodiments, to make editing easier, the user can sort the data in the endpoint location file by clicking on a column head. For example, to sort by latitude, the user clicks on a latitude column heading 1106.
E. Exporting an Endpoint Location File
Once an endpoint location file has been imported and edited or updated, the mobile data collection system may enable the export of the endpoint location file back to the customer information system or to a backup location, or other location by using the EXPORT function 408 or EXPORT FILTERED function 410, which can be accessed from the editor component toolbar 402, as shown in
In general, the various depicted features and functions (e.g., import, update, calculate, export, etc.) can be applied to other features of the system in addition to the endpoint location files. For example, such features and functions may be applied in the context of route files, meter servicing files, or any other information used in the mobile data collection system.
F. Route Mapping Example
While information in the endpoint location file may be used for any number of purposes during meter reading route management, one application involves the use of route mapping, an example of which is provided with respect to
Referring to
In some embodiments, the map may be interactive by allowing users to drill down on specific endpoints. For example, clicking on or touching an endpoint on the map may result in the display of specific information regarding the endpoint.
V. System Flows
Referring to
Referring to
Referring to
While the above routine 1500 relates to calculating location coordinates for endpoints, other types of determinations related to the endpoint location file may be made in a similar way without departing from the scope of the invention. For example, a similar routine may be invoked to determine missing or incorrect address information. In another example, business rules may be applied to determine or assign specific mapping symbols to use (e.g., if endpoint A matches XYZ criteria, the use a pink star when displaying it on a map).
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. When the claims use the word “or” in reference to a list of two or more items, that word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above detailed description of embodiments of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific embodiments of, and examples for, the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number, respectively.
The teachings of the invention provided herein can be applied to other systems, not necessarily the system described herein. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description details certain embodiments of the invention and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the mobile data collection system may vary considerably in their implementation details, while still be encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the invention under the claims.
While certain aspects of the invention are presented below in certain claim forms, the inventors contemplate the various aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as embodied in a computer-readable medium, other aspects may likewise be embodied in a computer-readable medium. Accordingly, the inventors reserve the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the invention.
This application is related to commonly owned U.S. application Ser. No. 10,903,886, filed Jul. 30, 2004, entitled “Mapping in Mobile Data Collection Systems, Such as for Utility Meter Reading and Related Applications,” which is incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the invention.