INTEGRATION PLATFORM TO ENABLE OPERATIONAL INTELLIGENCE AND USER JOURNEYS FOR SMART CITIES AND THE INTERNET OF THINGS

• US 20160239767A1
• Filed: 02/16/2016
• Published: 08/18/2016
• Est. Priority Date: 02/13/2015
• Status: Active Grant

• Current Assignee: Eutech Cybernetics
• Original Assignee: Eutech Cybernetics
• Inventors: WEWALAARACHCHI, Bandu J., SHIVANAN, Haran, GUNASINGHAM, Haritharan
• Granted Patent: US 11,023,845 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/28 Databases characterised by their database models, e.g. relational or object models
• CPC Class Codes: G06F 16/9024 Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: G06Q 50/163 Real estate management

Abstract

A “metadata model of a city'"'"'s Internet of Everything and use thereof to implement citizen engagement through ‘user journeys’ and system intelligence through automated response logic. A framework that allows system integrators to build a metadata model of a city'"'"'s IoE, which metadata model then enables city managers to implement user journeys and system intelligence, in incremental fashion, as the business needs of the city evolves.

Claims

1. A system for integrated management of the infrastructure of a community, where the infrastructure comprises a plurality of network-connected infrastructure systems, subsystems, devices, and applications, and where the systems, subsystems, devices and applications are independent and unintegrated, the system comprising:

a user-defined machine-readable metadata model comprising predefined metadata node templates defining metadata structures for said infrastructure systems, subsystems, devices, and applications;

connector modules configured to collect metadata from said infrastructure systems, subsystems, devices, and applications;

an event engine that receives metadata from said connector modules and which populates metadata node templates using said metadata to create populated metadata nodes;

a dynamic metadata map/model assembled by said event engine, comprising populated metadata nodes, including relationships between nodes based on said collected metadata, and pre-defined operation sequences, based on the occurrence of events received from the connector modules, which pre-defined operation sequences define a set of operations according to predicted end-user requirements in response to pre-selected events.

2. A system according to claim 1, wherein said community is a city.

3. A system according to claim 1, wherein said community is a single building.

4. A system according to claim 1, wherein said community is a collection of buildings.

5. A system according to claim 1, wherein said community is a workplace or single-tenant space within a multi-tenant building where some subsystems (such as air conditioning) belong or are operated by the building and/or building management, while other subsystems (such as card access &

CCTV) are owned and/or managed by the tenant.

6. A system according to claim 1, further comprising cross references between existing metadata nodes.

7. A system according to claim 1, wherein the event engine is configured to build the dynamic metadata map automatically, continuously, and dynamically, modifying the metadata map as collected metadata changes.

8. A system according to claim 1, wherein the event engine is configured to use metadata relationships to extract metadata from existing nodes or from subsystems to build and update metadata nodes.

9. A system according to claim 1, wherein said dynamic metadata map/model contains metadata notes for a plurality of infrastructure systems, subsystems, devices, and/or applications that are involved in a service workflow, wherein a service workflow comprises a set of pre-selected information that presented to an end user and said predefined operation sequences.

10. A system according to claim 1, wherein said predefined operation sequences comprise an end-to-end service workflow for end-users of the system by having metadata model undertake integration with multiple subsystems involved in the service workflow.

11. A system according to claim 1, further comprising an analytics engine configured to identify and correlate events and to update existing events or create new events based on identified correlations.

12. A system according to claim 1, wherein the event engine is configured to send commands to one or more of said infrastructure systems, subsystems, devices, and applications based on the receipt of one or more event conditions received by the event engine.

13. A system according to claim 1, wherein the network comprises the Internet.

14. A system according to claim 1, wherein the network comprises only private networks.