RELATED APPLICATION

[0001] This patent claims benefit from U.S. Provisional Application No.

61/223,299, which was filed on July 6, 2009 and is hereby incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

[0002] This disclosure relates generally to metering and control, and, more particularly, to metering and control systems and methods to operate the same.

BACKGROUND

[0003] Utility companies meter utility services via meters installed at service locations such as residences and/or places of business. Example utility services include, but are not limited to, a water service, an electrical service, a natural-gas service, a propane service, a fuel service, a heating-oil service, a waste-water service, a telephone service, an Internet service, or a television service. The meters are read and used to determine the amount of a commodity (e.g., gallons of water, kWh of electricity, units of gas, therms of heat, bytes transmitted and/or received, etc.) used by a customer and, thus, the amount of money the customer owes the service provider for the utility service. The meters may be read manually and/or remotely via, for example, wired and/or wireless telemetry. Meters may also be used by owners of apartment buildings, office buildings, marinas, campgrounds, etc. to allocate a portion of a utility bill to individual customers, renters and/or tenants.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 is an illustration of an example metering and control system (MACS).

[0005] FIG. 2 is an illustration of an example MACS network for the example MACS of FIG. 1.

[0006] FIG. 3 illustrates an example manner of implementing the example data logger and controller of FIG. 2.

[0007] FIGS. 4 and 5 are flowcharts representative of example processes that may be embodied as machine-accessible instructions and executed by, for example, one or more processors, to implement the example data logger and controller of FIGS. 2 and 3.

[0008] FIGS. 6 and 7 are flowcharts representative of example processes that may be carried out to operate the example MACS network of FIG. 2.

[0009] FIGS. 8-20 represent example graphical user interfaces that may be used to operate, configure and/or monitor the example MACS of FIG. 1.

[0010] FIG. 21 is a flowchart representative of an example process that may be carried out to add a customer for the example MACS of FIG. 1.

[0011] FIGS. 22-25 represent example graphical user interfaces that may be used to carry out the example process of FIG. 21.

[0012] FIG. 26 is a flowchart representative of an example process that may be carried out to update a prepaid account of the example MACS of FIG. 1.

[0013] FIG. 27 is a flowchart representative of an example process that may be embodied as machine-accessible instructions and executed by, for example, one or more processors, to generate a departure bill for the example MACS of FIG. 1.

[0014] FIGS. 28 and 29 illustrate example usage history reports that may be generated by the example MACS office modules of FIG. 1.

[0015] FIG. 30 represents an example graphical user interface that may be used to display information within the example MACS of FIG. 1.

[0016] FIG. 31 is a schematic illustration of an example processor platform that may be used and/or programmed to execute any or all of the example machine- accessible instructions described herein

DETAILED DESCRIPTION

[0017] Example metering and control systems (MACSs) and methods to operate the same are disclosed. Example applications of the disclosed example MACS include, but are not limited to, pulse automatic meter reading (AMR), absolute AMR, on/off control, utility limiting, automated shut down, secured utilities supply, auxiliary switching (e.g., night lights), gate and access control, security/presence detection, utility profiles, automated utility usage conservation management based on user defined limits, billing of utilities, utility user messaging, telemetry collection, environmental control, 3rd party hardware integration (e.g., weather, gauges, sensors, etc), and/or automotive electric vehicle (EV) charging, and/or system and user alarms. The examples disclosed herein may be used at, for example, campgrounds, recreational vehicle (RV) parks, mobile home parks, marinas, chalets, lodges, vacation properties, cabins, rental properties, factories, warehouses, workshops, offices, garages, office buildings, schools, medical buildings, etc.

[0018] The disclosed example MACSs enable a customer to securely access and/or discontinue services at any number and/or type(s) of locations, and to have those services metered, monitored and/or controlled. In some examples, a customer accesses a utility service by scanning and/or swiping an electronic identification module such as a smart card, an iButton®, a MIFARE card, a radio frequency identification (RFID) card, etc. and entering and/or providing a corresponding personal identification number (PIN) using, for example, a keypad. Additionally or alternatively, some example services may be accessed using only the electronic identification module. Disclosed example MACSs also enable customers to access services at different locations using the same electronic identification module and PIN. In other words, roaming customers (e.g., boat owners, campers, etc.) can access services at different locations and charge those services to the same account. For example, a boat owner on an island hopping vacation can purchase fuel, water and/or electricity at different marinas without having to establish a separate account at each marina.

[0019] The disclosed example MACSs may, additionally or alternatively, be used to collect information that may be automatically fed back to, for example, service and/or maintenance personnel, to allow service, repairs and/or maintenance to be performed in a timely and/or proactive fashion. For example, a sensor on a boat may record rough idling and report the same to a manna's service personnel as the boat pulls into the marina, a car may monitor operating performance and/or detect a fault and report the same to service personnel of a garage when the car is parked for the night, a chalet and/or cabin may monitor indoor temperature and/or monitor for leaks or other potential problems, a facility may be monitored for carbon emissions, etc. [0020] Further, the disclosed example MACSs may be used to restrict and/or limit access to services. For example, services may be accessed using a prepaid account such that services are automatically discontinued when the prepaid account no longer contains sufficient credit, services may be disconnected if an excess amount of electrical current is drawn, automated utility usage conservation may be performed based on target and/or synchronized profiles, etc.

[0021] Further still, the disclosed example MACSs may also be used to provide information to users. For example, text messages may be displayed on a display associated with a keypad that the person uses to enter their PIN. For example, a customer connecting to a service may be provided information regarding local attractions or area restaurants, a customer disconnecting their boat from electrical and water service (presumably to leave harbor) may be provided weather information for the upcoming 24 hour period, etc.

[0022] A disclosed example method to activate a utility service includes obtaining a first identifier from an electronic identification module, obtaining a second identifier from a keypad, querying a database with the first identifier to identify an account, comparing the second identifier with a third identifier stored in the account to validate a user of the account, and activating the utility service for access by the user when the user is validated.

[0023] A disclosed example apparatus includes a first interface to obtain a first identifier from an electronic identification module, a second interface to obtain a second identifier from a keypad, a memory to store a database including a plurality of accounts, and a controller to query the database with the first identifier to identify a first of the plurality of accounts, compare the second identifier with a third identifier stored in the first account to validate a user of the first account, and activate a utility service for access by the user when the user is validated.

[0024] Another disclosed method includes adding an account to a database, associating a first identifier assigned to an electronic identification module with the account, the first identifier being obtainable from the electronic identification module when a user electronically scans the electronic identification module and useable to locate the account in the database, and associating a second identifier with the account, the second identifier being obtainable from the user via a keypad, useable to validate an identification of the user, and useable to activate a utility service for the user when the user is validated.

[0025] A disclosed example method to access a utility service includes electronically scanning an identification module to provide a first identifier being associated with a service utility account, and entering a second identifier via a keypad to validate a person associated with the service utility account and to activate the service utility for use by the person.

[0026] FIG. 1 illustrates an example MACS 100 constructed in accordance with the teachings of this disclosure. The example MACS 100 of FIG. 1 includes one or more MACS networks, three of which are designated at reference numerals 105, 106 and 107, that are communicatively coupled via respective transceivers 110, 111 and 112 to a MACS server 115. An example manner of implementing the example MACS networks 105-107 is described below in connection with FIG. 2. Example transceivers 110-112 include, but are not limited to, a radio frequency (RF) mesh network transceiver (e.g., implemented in accordance with to the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standard a.k.a. ZigBee), a wired and/or wireless Ethernet transceiver, a wireless base station (e.g., implemented in accordance with any IEEE 802.11 x standard), a general packet radio service (GPRS) transceiver, a data over power-line transceiver, a digital subscriber line (DSL) transceiver, and/or an extended CAN-bus transceiver. The example transceivers 110-112 of FIG. 1 communicatively couple the MACS networks 105-107 to the MACS server 115 via any number and/or type(s) of public and/or private networks such as a public network 120 (e.g., the

Internet), a direct connection (e.g., a USB connection) and/or a private network 121 (e.g., a corporate local area network (LAN), a virtual private network (VPN), etc.). In some examples, communications carried over the example public network 120 are secured using a secure shell (SSH) protocol.

[0027] FIG. 1 is merely an illustrative example for purposes of discussion. Accordingly, while the example MACS 100 of FIG. 1 includes three MACS networks 105-107 communicatively coupled to the MACS server 115 via different technologies, a MACS may be implemented with the same or a different number of MACS networks and/or the MACS networks may be communicatively coupled to a MACS server via one or more similar or different technologies. For instance, another example MACS has all of its MACS networks communicatively coupled to its MACS server via the Internet. Further, the MACS server 115 may be local to and/or remote from any or all of the example MACS networks 105-107.

[0028] To store data, information, account information, customer records, configuration information, configuration data, etc, the example MACS 100 of FIG. 1 includes a MACS database 125. The example MACS database 125 of FIG. 1 may be implemented using any number and/or type(s) of data structure(s), and may be stored on any number and/or type(s) of volatile and/or non-volatile memory(-ies), memory device(s) and/or storage device(s).

[0029] The example MACS server 115 of FIG. 1 includes a MACS office module 130, a MACS console module 131 , and a MACS operating system (OS) module 132. The example MACS office module 130 of FIG. 1 enables a user to manage and/or perform customer billing, and/or administer the example MACS 100. The example MACS office module 130 may be used to generate customer usage reports from customer records and/or customer account information stored in the example MACS database 125. Example customer reports are described below in connection with FIGS. 28 and 29. Other example reports include, but are not limited to, global reports, site- based reports, area-based reports, location-based report, customer reports, utility provider based reports, synchronized reports, periodic reports, limit set reports, daily reports and/or adhoc user-defined reports. The MACS office module 130 may implement one or more sub-modules to enable the export and/or import of customer information into and/or out of the example MACS database 125 to, for example, integrate with third-party tools.

[0030] The example MACS console module 131 of FIG. 1 enables a user to add customers, remove customers, manage customers, assign customers to locations, and/or otherwise configure the example MACS 100. The customer and/or MACS information configured via the MACS console 131 is stored in the example MACS database 125. Example processes and example user interfaces that can be used to manage the example MACS 100 via the example MACS console 131 are described below in connection with FIGS. 8-26 and 30.

[0031] The example MACS OS module 132 of FIG. 1 configures elements of the MACS networks 105-107 based on information stored in the MACS database 125. For example, when a customer is added, configured and/or changed via the MACS console 131 , the example MACS OS module 132 configures the MACS network(s) 105- 107 associated with the customer to enable one or more configured services for the customer. The example MACS OS module 132 can also electronically upgrade elements of the example MACS networks 105-107. The example MACS OS module 132 communicates with elements of the MACS networks 105-107 using any number and/or type(s) of message(s) and/or protocol(s).

[0032] An example processor platform P100 that may be used to implement the example MACS server 115 of FIG.1 is described below in connection with FIG. 31. Users may access and/or use the example MACS server 115 using a keyboard, a mouse and/or a monitor directly connected to the MACS server 115, and/or via any number of MACS clients, two of which are designated at reference numerals 135 and 136. As shown in FIG. 1 , the MACS clients 135 and 136 may be communicatively coupled to the MACS server 115 and/or the MACS database 125 via the public network 120 (e.g., using an SSH protocol) and/or the private network 121. The example MACS clients 135 and 135 of FIG. 1 each implement a MACS office module 130 and a MACS console module 131 having functionality substantially similar to those described above in connection with the example MACS server 115. The example processor platform P100 of FIG. 31 may also be used to implement the example MACS clients 135 and 136.

[0033] In some examples the MACS networks 105-107 are geographically separate (e.g., implemented at different marinas and/or campgrounds in different cities) and a MACS client 135-136 is implemented at and/or in conjunction with each marina/campground to allow local personnel to add and/or manage customer accounts remotely from the MACS server 115 and/or MACS database 125. For example, the MACS server 115 and the MACS database 125 may be implemented in conjunction with a corporate office that overseas and/or manages the different

marinas/campgrounds.

[0034] As discussed in more detail below in connection with FIG. 2, customers use an electronic identification module such as a smart card, an iButton, a MIFARE card, an RFID card, etc. to access services provided and/or implemented by the MACS networks 105-107. To allow a user of the MACS clients 135 and 136 to configure customer accounts based on identifiers stored in electronic identification modules, the example MACS clients 135 and 136 of FIG. 1 are communicatively coupled to and/or include any number and/or type(s) of electronic reader(s) 140. When configuring a customer account, the MACS clients 135 and 136 obtain a customer's electronic identifier from their electronic identification module via the electronic reader 140. Example electronic readers 140 include, but are not limited to, a smart card reader and an RFID tag reader.

[0035] FIG. 2 illustrates an example MACS network 200 that may be used to implement any or all of the example MACS networks 105-107 of FIG. 1. The example MACS network 200 of FIG. 2 is implemented using plug-and-play modules that are adapted to implement, for example, any of the example metering, monitoring and/or control applications disclosed herein. In the illustrated example of FIG. 2, the modules are communicatively coupled to a data hub 205 via a controller area network (CAN) bus 210. The example data hub 205 of FIG. 2 is communicatively coupled to the example MACS database 125 via a respective transceiver 110-112 (FIG. 1 ). The example CAN bus 210 of FIG. 1 may be implemented in accordance with any past, present and/or future CAN-bus standard(s) and/or protocol(s) such as any of the International

Organization for Standardization (ISO) 11898-x family of standards.

[0036] Example plug-and-play modules include, but are not limited to, an electronic reader 215, a keypad 220, a universal interface 225, a data logger/controller 230, a power supply unit (not shown), and/or a CAN-bus power junction (not shown). The example plug-and-play modules 205, 215, 220, 225 and 230 of FIG. 1 may be electrically coupled using one or more RJ-45 cables.

[0037] The example electronic reader 215 of FIG. 2 is any type of device capable to, programmed to and/or configured to electronically scan, electronically read and/or otherwise electronically obtain a unique identifier associated with an electronic identification module 217 such as a smart card, an iButton, a MIFARE card, an RFID card, etc. Example electronic readers 215 include, but are not limited to, a smart card reader and an RFID tag reader.

[0038] The example keypad 220 of FIG. 2 is any type of keypad and/or keyboard via which a user may enter, type and/or otherwise provide a PIN. While not shown in FIG. 2, in some examples a voice recognition system may be implemented to allow a person to speak their PIN. In some examples, the keypad 220 includes a display 222 to prompt the user to enter their PIN and/or to present other information such as weather information, service information, local attraction information, etc.

[0039] The example universal interface 225 of FIG. 2 implements one or more bridges and/or interfaces between the example CAN-bus 210 and other communication protocol(s) and/or signal(s) such as RS-232, RS-485, analog signals and/or other digital signals.

[0040] The example data logger/controller 230 of FIG. 2 may be

communicatively coupled to one or more meters, four of which are designated at reference numerals 241 -244, via, for example, one or more RJ-11 and/or RJ-12 cables. Example meters 241 -244 include, but are not limited to, a water service meter, an electrical service meter, a natural-gas service meter, a propane service meter, a fuel service meter, a heating-oil service meter, a telephone service meter, a waste-water service meter, an Internet service meter, or a television service meter. The example meters 241 -244 may be smart or absolute meters and/or pulse-based meters. As described below in connection with FIG. 3, the example data logger/controller 230 can meter and/or control each of the meters 241 -244 individually to allow utility services for different customers to be metered individually. The example data logger/controller 230 may also be communicatively coupled to any number and/or type(s) of auxiliary devices, one of which is designated at reference numeral 245. An example manner of implementing the example data logger/controller 230 of FIG. 2 is described below in connection with FIG. 3.

[0041] While an example manner of implementing the example MACS networks 105-107 of FIG. 1 has been illustrated in FIG. 2, one or more of the elements, processes and/or devices illustrated in FIG. 2 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example CAN- bus hub 205, the example electronic reader 215, the example keypad 220, the display 222, the example universal interface 225, the example data logger/controller 230 and/or, more generally, the example MACS network 200 of FIG. 2 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example CAN-bus hub 205, the example electronic reader 215, the example keypad 220, the display 222, the example universal interface 225, the example data logger/controller 230 and/or, more generally, the example MACS network 200 could be implemented by the example process platform P100 of FIG. 31 and/or one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), field-programmable gate array(s)

(FPGA(s)), fuses, etc. When any apparatus claim of this patent incorporating one or more of these elements is read to cover a purely software and/or firmware

implementation, at least one of the example CAN-bus hub 205, the example electronic reader 215, the example keypad 220, the display 222, the example universal interface 225, and/or the example data logger/controller 230 are hereby expressly defined to include a tangible article of manufacture such as a tangible computer-readable medium storing the firmware and/or software. Further still, the example MACS network 200 of FIG. 2 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIG. 2, and/or may include more than one of any or all of the illustrated elements, processes and devices. For example, there may be more than one electronic reader 215, more than one keypad 220 and/or more than one data logger/controller 230 in the MACS network 200. [0042] As used herein, the term tangible computer-readable medium is expressly defined to include any type of computer-readable medium and to expressly exclude propagating signals. Example computer-readable medium include, but are not limited to, a volatile and/or non-volatile memory, a volatile and/or non-volatile memory device, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a read-only memory (ROM), a random-access memory (RAM), a programmable ROM (PROM), an electronically-programmable ROM (EPROM), an electronically-erasable PROM

(EEPROM), an optical storage disk, an optical storage device, a magnetic storage disk, a magnetic storage device, a cache, and/or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information) and which can be accessed by a processor, a computer and/or other machine having a processor, such as the example processor platform P100 discussed below in connection with FIG. 31. As used herein, the term non-transitory computer-readable medium is expressly defined to include any type of computer-readable medium and to expressly exclude propagating signals.

[0043] FIG. 3 illustrates an example manner of implementing the example data logger/controller 230 of FIG. 2. To communicate with other modules via the CAN- bus 210, the example data logger/controller 230 of FIG. 3 includes a CAN-bus interface 305. The example CAN-bus interface 305 of FIG. 3 can be used to receive a first identifier from the example electronic identification module 217 via the example electronic reader 215, and a second identifier (e.g., a PIN) from the example keypad 220 (FIG. 2). The example CAN-bus interface 305 is also used to receive firmware updates and/or upgrades and to receive MACS network and/or customer account configuration information from the example MACS OS module 132 (FIG. 1 ). In some examples, the example data logger/controller 230 may include and/or directly interface to an electronic reader 310 and a keypad 315. The example electronic reader 310 and the example keypad 315 have functionality substantially similar to those described above in connection with the example MACS network 200 of FIG. 2. [0044] To interface with and/or control the example meters 241 -244 and/or the example auxiliary device 245, the example data logger/controller 230 of FIG. 3 includes any number and/or type(s) of meter interfaces 320. The example meter interfaces 320 of FIG. 3 can be used to send a command to and/or receive a response from a respective meter 241 -244 and/or auxiliary device 245 to, for example, enable a utility service, disable a utility service, and/or obtain a value representative of a meter reading.

[0045] To store customer account information, the example data

logger/controller 230 of FIG. 3 includes a service database 325. For each customer, the example service database 325 includes, among other things, the electronic identifier of their electronic identification module 217, their PIN, a list of which utility services they may access, the meter(s) 241 -244 associated with their services, prepayment credit information for prepaid accounts, service usage information, and/or any number of other parameters that may control, configure and/or limit their utility services. Information may be stored in the example service database 325 using any number and/or type(s) of data structures, and the example service database 325 may be implemented by any number and/or type(s) of volatile and/or non-volatile memory(-ies), memory device(s) and/or storage device(s).

[0046] To control the operations of the example data logger/controller 230, the example data logger/controller 230 of FIG. 3 includes a controller 330. In general, the example controller 330 of FIG. 3 receives customer identification information from a customer via the CAN-bus interface 304, the electronic reader 310 and/or the keypad 315, compares the received information to account information stored in the service database 325 and, if the provided information is validated (e.g., the provided PIN corresponds to the identifier of the scanned electronic identification module 217), the service(s) configured in the customer's account are activated and/or deactivated. Only those meters 241 -244 associated with a customer's account are affected. That is, the example meters 241 -244 operate independently of each other to allow each customer to be directly charged for only those services that they utilize. Further, the example meters 241 -244 and/or the example meter interfaces 320 may be associated with individual sockets and/or connectors (e.g., a single electrical outlet in an office building) to enable more granular service utility control, monitoring and/or metering.

[0047] While an example manner of implementing the data logger/controller 230 of FIG. 2 has been illustrated in FIG. 3, one or more of the elements, processes and/or devices illustrated in FIG. 3 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example CAN-bus interface 305, the example electronic reader 310, the example keypad 315, the example meter interfaces 320, the example service database 325, the example controller 330 and/or, more generally, the example data logger/controller 230 of FIG. 3 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example CAN-bus interface 305, the example electronic reader 310, the example keypad 315, the example meter interfaces 320, the example service database 325, the example controller 330 and/or, more generally, the example data logger/controller 230 could be implemented by the example process platform P100 of FIG. 31 and/or one or more circuit(s), programmable processor(s), ASIC(s), PLD(s) and/or FPLD(s), FPGA(s), fuses, etc. When any apparatus claim of this patent incorporating one or more of these elements is read to cover a purely software and/or firmware implementation, at least one of the example CAN-bus interface 305, the example electronic reader 310, the example keypad 315, the example meter interfaces 320, the example service database 325, the example controller 330 and/or, more generally, the example data logger/controller 230 are hereby expressly defined to include a tangible article of manufacture such as a tangible computer-readable medium storing the firmware and/or software. Further still, the example data logger/controller 230 of FIG. 3 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIG. 3, and/or may include more than one of any or all of the illustrated elements, processes and devices.

[0048] FIGS. 4 and 5 are flowcharts representative of example processes that may be embodied in machine-readable instructions that may be executed to implement the example data logger/controller 230 of FIGS. 2 and 3. A processor, a controller and/or any other suitable processing device may be used, configured and/or programmed to execute the example machine-readable instructions represented in FIGS. 4 and/or 5. For example, the machine-readable instructions of FIGS. 4 and/or 5 may be embodied in coded instructions stored on a tangible computer-readable medium. Machine-readable instructions comprise, for example, instructions that cause a processor, a computer and/or a machine having a processor to perform one or more particular processes. Alternatively, some or all of the example processes of FIGS. 4 and/or 5 may be implemented using any combination(s) of ASIC(s), PLD(s), FPLD(s), FPGA(s), discrete logic, hardware, firmware, etc. Also, some or all of the example processes of FIGS. 4 and/or 5 may be implemented manually or as any combination of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. Further, many other methods of implementing the example operations of FIGS. 4 and/or 5 may be employed. For example, the order of execution of the blocks may be changed, and/or one or more of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, the blocks of any or all of the example processes of FIGS. 4 and/or 5 may be carried out sequentially and/or carried out in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc.

[0049] The example process of FIG. 4 may be used to activate one or more service utilities for a customer. The example process of FIG. 4 begins with the example controller 330 receiving a first identifier from a customer's electronic identification module 217 via the CAN-bus interface 305 and/or the electronic reader 310 (block 405) and receiving a second identifier (e.g., a PIN) via the CAN-bus interface 305 and/or the keypad 315 (block 410).

[0050] Based on the first identifier the controller 330 identifies a customer account in the service database 325 and obtains the PIN number associated with the identified account (block 415). If the received PIN and the PIN obtained from the identified account match (e.g., the customer's identification is verified) (block 420), the controller 330 determines whether identified account is a pre-paid account (block 425). [0051] If the identified account is not a pre-paid account (block 425), the controller 330 sends one or more commands via the meter interface(s) 320 associated with the service(s) specified in the customer's account to enable metering of those services (block 430), and sends one or more commands to the meter interface(s) 320 to activate (e.g., turn on) those service(s) (block 435). In some examples, the same command(s) may be used to activate metering and activate the service(s). Control then exits from the example process of FIG. 4.

[0052] Returning to block 425, if the identified account is a pre-paid account (block 425), the controller 330 determines whether sufficient pre-paid credit remains in the account (block 440). For example, the controller 330 may compare the remaining credit to a pre-configured threshold, which may be different for different users. If there is insufficient remaining credit (block 440), a message indicating insufficient credit is presented to the customer (block 445) and the example process of FIG. 4 is ended. In some examples, an emergency pre-paid credit may be granted at block 440, as defined and/or configured in the identified account, with control proceeding to block 430 rather than presenting the message at block 445. Otherwise, control proceeds to block 430 to activate metering and services.

[0053] Returning to block 420, if the customer is not verified, a message indicating customer not authorized is presented to the customer (block 450) and control exits from the example process of FIG. 4.

[0054] The example process of FIG. 5 may be used to deactivate one or more service utilities for a customer. The example process of FIG. 5 begins with the example controller 330 receiving a first identifier from a customer's electronic identification module 217 via the CAN-bus interface 305 and/or the electronic reader 310 (block 505) and receiving a second identifier (e.g., a PIN) via the CAN-bus interface 305 and/or the keypad 315 (block 510).

[0055] Based on the first identifier, the controller 330 identifies a customer account in the service database 325 and obtains the PIN number associated with the identified account (block 515). If the received PIN and the PIN obtained from the identified account match (e.g., the customer's identification is verified) (block 520), the controller 330 sends one or more commands via the meter interface(s) 320 associated with the service(s) specified in the customer's account to deactivate (e.g., turn off) those service(s) (block 525), and sends one or more commands to read the meter(s) 241 -244 (e.g., obtain one or more values representative of how much of the service(s) were consumed) (block 530). In some examples, the same command(s) may be used to deactivate the service(s) and read the meter(s) 241 -244.

[0056] If the identified account is a pre-paid account (block 535), a charge corresponding to the used amount of services is subtracted from the account's pre-paid credit (block 540). The charge associated with used services may be based on one or more tariffs. For example, there may be different tariffs (e.g., standard, economy, etc.), different tariffs for different days of the week (e.g., weekend), and/or different tariffs for different utility providers. Further, the charge may be based on one or more standing charges based on, for example, per unit and/or per day. The account is updated to record the amount of each service that was used for subsequent billing and/or historical analysis (block 545). Control then exits from the example process of FIG. 5.

[0057] Returning to block 520, if the customer is not verified, a message indicating customer not authorized is presented to the customer (block 550) and control exits from the example process of FIG. 5.

[0058] FIGS. 6 and 7 illustrate example processes that may be carried out by, for example, a customer to operate and/or use the example MACS network 200 of FIG. 2 and/or, more generally, the example MACS 100 of FIG. 1. Other methods of carrying out the example operations of FIGS. 6 and 7 may be employed. For example, the order of carrying out the blocks may be changed, and/or one or more of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, the blocks of the example processes of FIGS. 6 and 7 may be carried out sequentially and/or carried out in parallel by, for example, different persons.

[0059] The example process of FIG. 6 may be carried out to activate a utility service. The example process of FIG. 6 begins with a customer electronically swiping and/or scanning their electronic identification module 217 using the electronic reader 215 or the electronic reader 310 (block 605). The customer enters their PIN using the keypad 220 or the keypad 315 (block 610), and connects one or more customer devices (e.g., a boat, a camper, a car, etc.) to one or more of the example meters 241 -244 via appropriate cables, connectors, hoses, etc. (block 615). Assuming the entered PIN is associated with the electronically obtained identifier, the customer may start using their contracted and/or pre-paid services (block 620).

[0060] The example process of FIG. 7 may be carried out to deactivate and/or discontinue a utility service. The example process of FIG. 7 begins with a customer electronically swiping and/or scanning their electronic identification module 217 using the electronic reader 215 or the electronic reader 310 (block 705) and entering their PIN using the keypad 220 or the keypad 315 (block 710). Assuming the entered PIN is associated with the electronically obtained identifier, the customer's utility service(s) will be discontinued and the customer can disconnect from the one or more meters 241 -244 associated with their discontinued service(s) (block 715).

[0061] FIGS. 8 - 20 represent example graphical user interfaces (GUIs) that be implemented by the example MACS console 131 of FIG. 1 to enable a user to configure and/or manage the example MACS 100. The example GUI of FIG. 8 is a graphical depiction of an example marina showing the location of the CAN-bus hubs 205 (one of which is designated at reference numeral 805) of respective MACS networks 105-107. In the illustrated example of FIG. 8, a MACS network 105-107 is implemented for each pier/pontoon of the marina.

[0062] The example GUI of FIG. 9 represents the logical configuration of the MACS network 105-107 for the example Pontoon A of FIG. 8. The example MACS network 105-107 represented in FIG. 9 includes four keypads (KPI) 220, and four data logger/controllers (DLC) 230.

[0063] The example GUI of FIG. 10 represents the physical layout of the MACS network 105-107 for the example Pontoon D of FIG. 8. The example MACS network 105-107 represented in FIG. 10 includes four keypads (KPI) 220, and ten data logger/controllers (DLC) 230. Elements of the illustrated example of FIG. 10 may be highlighted and/or emphasized to signify that some condition and/or alarm is present and/or needing rectification. For example, KPI 2 is shown as being in an alarm state. [0064] The example GUI of FIG. 11 represents the current usage of the example MACS network 105-107 for the example Pontoon D example of FIG. 10. As shown in FIG. 11 , different locations 000-040 can be color coded to indicate the status of their corresponding meter 241 -244 and/or service. For example, location 004 in FIG. 11 is flagged as exceeding a configured current limit.

[0065] FIG. 12 is an example GUI representing the status of location 001 of the example Pontoon A of FIG. 9. As shown, the location 001 is associated with customer Lord Nelson and the boat associated with that location is HMS Victory. As shown, electrical (E), water (W), gas (G) and fuel (F) services are current active, the account is a pre-paid account, and an alert is set to trigger if/when the remaining prepaid credit becomes low (CL).

[0066] FIG. 13 is an example GUI representing the identifiers currently associated with the example Lord Nelson account of FIG. 12, and includes elements that can be selected to enable a user to assign other existing identifiers to the account and/or the create new identifiers for use with the account.

[0067] FIG. 14 is an example GUI representing the controls currently configured for the example Lord Nelson account of FIG. 12. As shown in FIG. 14, each account can have the different services individually enabled. Also, each service can be set to auto-disconnect. An auto-disconnect service is one for which the meter is read and the account charged automatically when the service is disconnected without the user having to first scan their electronic identification module 217 and/or enter their PIN. For example, removal of a plug from a socket may be automatically detected and used to automatically disconnect the associated utility service. As shown, service limits can be set (e.g., a current limit), and the account can be suspended.

[0068] FIG. 15 is an example GUI representing the current meter readings for the example Lord Nelson account of FIG. 12.

[0069] FIG. 16 is an example GUI that may be used to view the remaining pre-paid credit of and/or to add/remove additional pre-paid credit to the example Lord Nelson account of FIG. 12. Pre-paid credit may be added and/or removed via, for example, a money transfer, a credit card, a check and/or cash. [0070] FIG. 17 is an example GUI allowing the user to associate the example Lord Nelson account of FIG. 12 with a different location. For example, selecting "select location" in the example GUI of FIG. 17 causes the example GUI of FIG. 27 to be presented to allow the user to select a new location for Lord Nelson's boat.

[0071] FIG. 18 is an example GUI that enables the user to search for and find an account associated with a particular customer. FIG. 19 is an example GUI representing search obtained by using the example GUI of FIG. 18. The example GUI of FIG. 19 provides basic information such as the location(s) associated with the customers and includes the ability to display additional information concerning a particular customer by, for example, double-clicking their name. When a customer name is double-clicked, the example GUI of FIG. 20 is presented, which provides additional details for the customers and provides additional options to edit, manage, credit reports and/or bill the customer.

[0072] FIG. 21 is a flowchart representative of an example process that may be carried out by a user to add a customer to the example MACS 100 of FIG. 1. For illustrative purposes, the example flowchart of FIG. 21 will be described with reference to the example GUIs of FIGS. 18 and 22-25. Other methods of carrying out the example operations of FIG. 21 may be employed. For example, the example process of FIG. 21 may be carried out as part of an automated procedure that imports customer account information from a data file and/or an integrated third-party tool. Accordingly, a processor, a controller and/or any other suitable processing device may be used, configured and/or programmed to execute the example processes represented in FIG. 21. For example, the processes of FIG. 21 may be embodied in machine-readable coded instructions stored on a tangible computer-readable medium. Machine-readable instructions comprise, for example, instructions that cause a processor, a computer and/or a machine having a processor to perform one or more particular processes. Alternatively, some or all of the example operation of FIG. 21 may be implemented using any combination(s) of ASIC(s), PLD(s), FPLD(s), FPGA(s), discrete logic, hardware, firmware, etc. Also, some or all of the example operations of FIG. 21 may be implemented manually or as any combination of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware.

Further, many other methods of implementing the example operations of FIG. 21 may be employed. For example, the order of execution of the blocks may be changed, and/or one or more of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, the blocks of any or all of the example operations of FIG. 21 may be carried out sequentially and/or carried out in parallel by, for example, multiple persons, separate processing threads, processors, devices, discrete logic, circuits, etc.

[0073] The example process of FIG. 21 begins when, for example, a user selects "add user" in the example GUI of FIG. 18 to initiate the addition of a new customer (block 2105). Using, for example, the example GUI of FIG. 22, customer details such as name, address, etc. are entered and/or provided (block 2110). By, for example, selecting "manage customer" in the example GUI of FIG. 22, the example GUI of FIG. 23 may be initiated to enable selection of a customer type (e.g., resident, visitor, staff, business, contract, etc. (block 2115), selection of an account type (e.g., pre-paid or not pre-paid) (block 2120), selection of whether the account is associated with a roaming customer (block 2125) and selection of the services to be made available to the customer (block 2130). By selecting "grid" in the example GUI of FIG. 23, the example GUI of FIG. 24 can be initiated and used to select one or more locations to be assigned to and/or associated with the new customer (block 2135).

[0074] Using, for example, the example GUI of FIG. 13 and/or FIG. 25, the user can issue, assign and/or associate a PIN and an electronic identification module with the new customer (block 2140). When, for example, the example customer account is saved, the MACS OS module 132 configures one or more MACS networks based on the just created customer account (block 2145).

[0075] If the customer account is a pre-paid account (block 2150), pre-paid credit is added to the account using, for example, the example GUI of FIG. 16 (block 2155), and the pre-paid credit is sent by the MAC OS module 132 to the one or more MACS networks (block 2160). Control then exits from the example process of FIG. 21.

[0076] FIG. 26 represents an example process that may be carried out by, for example, a user to update the pre-paid credit of a pre-paid customer account. Other methods of carrying out the example operations of FIG. 26 may be employed. For example, the order of carrying out the blocks may be changed, and/or one or more of the blocks described may be changed, eliminated, sub-divided, or combined.

Additionally, the blocks of the example operations of FIG. 26 may be carried out sequentially and/or carried out in parallel by, for example, different persons.

[0077] The example process of FIG. 26 begins when, for example, "prepaid" is selected in the example GUI of FIG. 20 to initiate the example GUI of FIG. 16 (block 2605). Using the example GUI of FIG. 16, the user updates and/or adds prepaid credit to the customer's account (block 2610). When, for example, the customer account is saved, the updated pre-paid credit is sent by the MAC OS module 132 to one or more MACS networks associated with the customer (block 2615).

[0078] FIG. 27 is a flowchart representative of an example process that may be embodied in machine-readable instructions that may be executed to generate departure billing for a departing customer. A processor, a controller and/or any other suitable processing device may be used, configured and/or programmed to execute the example process represented in FIG. 27. For example, the process of FIG. 27 may be embodied in machine-readable coded instructions stored on a tangible computer- readable medium. Machine-readable instructions comprise, for example, instructions that cause a processor, a computer and/or a machine having a processor to perform one or more particular processes. Alternatively, some or all of the example operations of FIG. 27 may be implemented using any combination(s) of ASIC(s), PLD(s), FPLD(s), FPGA(s), discrete logic, hardware, firmware, etc. Also, some or all of the example operations of FIG. 27 may be implemented manually or as any combination of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. Further, many other methods of implementing the example operations of FIG. 27 may be employed. For example, the order of execution of the blocks may be changed, and/or one or more of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, the blocks of any or all of the example operations of FIG. 27 may be carried out sequentially and/or carried out in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc.

[0079] The example process of FIG. 27 begins with the example MACS office module 130 determining whether the customer is a pre-paid customer (block 2705). If the customer is a pre-paid customer (block 2705), the example MAC OS module 132 retrieves the metering reading(s) and pre-paid credit remaining from the MACS network associated with the customer's location (block 2710). Otherwise, the example MAC OS module 132 retrieves the metering reading(s) from the MACS network associated with the customer's location (block 2715).

[0080] The example MACS office module 130 generates a history report (block 2720), generates an invoice (block 2725), and saves the customer's data for future reference (block 2730). Example history reports are illustrated in FIGS. 28 and 29. Control then exits from the example process of FIG. 27.

[0081] FIGS. 28 and 29 illustrate example customer reports that may be generated by the example MACS office 130 of FIG. 1. The example customer report of FIG. 28 depicts a usage report for a customer named John R. Smith who used services on different days at a same location PonA 001. The example customer report of FIG. 29 depicts a usage report for a customer named John A. Smith who used services at different locations PonA 001 , PonB 023 and Pon5 031 on different days.

[0082] FIG. 30 represents an example GUI that may be used to generate and send a text message for presentation at, for example, the example display 222 of FIG. 2.

[0083] While example graphical user interfaces are shown in FIGS. 8-20, 22- 25 and 30, one or more of the user interface elements, logos, buttons, menus, displays, lists, text boxes, check boxes, etc. illustrated in FIGS. 8-20, 22-25 and/or 30 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example graphical user interfaces are shown in FIGS. 8-20, 22-25 and/or 30 may include one or more user interface elements, logos, buttons, menus, displays, lists, text boxes, check boxes, etc. in addition to, or instead of, those illustrated in FIGS. 8-20, 22-25 and 30, and/or may include more than one of any or all of the illustrated user interface elements, logos, buttons, menus, displays, lists, text boxes, check boxes, etc.

[0084] FIG. 31 is a block diagram of an example processor platform P100 that may be used and/or programmed to implement the example MACS server 115, the example MACS clients 135 and 136, the example data logger/controller 230, and/or to execute any or all of the example machine-accessible instructions and/or processes described herein. One or more general-purpose processors, processor cores, microcontrollers, etc may be used to implement the processor platform P100. The processor platform P100 can be, for example, a server, a personal computer, an embedded controller, and/or any other type of computing device.

[0085] The processor platform P100 of the instant example includes at least one programmable processor P105. The processor P105 executes coded instructions P110 and/or P112 present in main memory of the processor P105 (e.g., within a RAM P115 and/or a ROM P120). The processor P105 may be any type of processing unit, such as a processor core, a processor and/or a microcontroller. The processor P105 may execute, among other things, the example machine-accessible instructions and/or the example processes of FIGS. 4-6, 7, 21 , 26 and/or 27. Thus, the coded instructions P110, P112 may implement the example processes of FIGS. 4-6, 7, 21 , 26 and/or 27.

[0086] The processor P105 is in communication with the main memory including a ROM P110 and the RAM P115 via a bus P125. The RAM P115 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of RAM device. The ROM P110 may be implemented by flash memory and/or any other desired type of memory device. Access to the memory P115 and the memory P120 may be controlled by a memory controller. The example memory P115 may be used to, for example, store the example service database 325 and/or the example MACS database 125.

[0087] The processor platform P100 includes an interface circuit P130. Any type of interface standard, such as an external memory interface, serial port, general- purpose input/output, as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface, etc, may implement the interface circuit P130.

[0088] One or more input devices P135 may be connected to the interface circuit P130. The input device(s) P135 may be used to, for example, permit a user to enter data and commands into the processor P105 and/or to implement the example CAN-bus interface 305, the example keypads 220 and 315, and/or the example electronic readers 140, 215 and 310, and/or the example meter interfaces 320.

Additionally or alternatively, the input device(s) P135 can be implemented by, for example, a keyboard, a mouse, a touch screen, a track-pad, a trackball, isopoint and/or a voice recognition system.

[0089] One or more output devices P140 are also connected to the interface circuit 1020. The output devices P140 can be implemented, for example, by display devices (e.g., a liquid crystal display, a cathode ray tube display (CRT), a printer and/or speakers). The interface circuit P130 may, thus, include a graphics driver card. The input device(s) P135 may be used, for example, to implement the example CAN-bus interface 305 and/or the example meter interfaces 320.

[0090] The interface circuit P130 may also includes a communication device such as a modem, transceiver or network interface card to facilitate exchange of data with external computers via a network (e.g., the networks 120 and 121 ).

[0091] In some examples, the processor platform P100 also includes one or more mass storage devices P145 to storing software and data. Examples of such mass storage devices P145 include a floppy disk drive, a hard disk drive, a solid-state hard disk drive, a CD drive, a DVD drive and/or any other solid-state, magnetic and/or optical storage device. The mass storage device P145 may implement the example MACS database 125 and/or the example service database 325.

[0092] The coded instructions described herein may be stored in the mass storage device P145, in the RAM P115, in the ROM P120, and/or on a removable storage medium such as a CD or a DVD

[0093] From the foregoing, it will appreciate that the above disclosed metering and control systems and methods to operate the same. Although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the claims of this patent.