things@

Machine Genome

everything has context

Soon the world will have billions of connected actors and trillions of networked sensors. Each actor will create their own graph, defined by the sensor networks to which they connect.

you are one of the actors

In context of your actions, external neural systems will be available.

things@ is sense connecting the world, creating context in things to inform those neural systems

things change

Machine Genome

The Human Genome is an autonomous rule based framework which in each instance operates in around 37 trillion cells and houses self-directed adaptive intelligence that is currently second to none. Modelling the Human Genome, the Machine Genome is a reference architecture that underpins all Things@ technology. Each implementation of the Machine Genome creates a new genomic network, enabling the fabrication of a synthetic neural system. This links edge system sensor data and makes real time control and analytics on overall network performance possible.

Nucleus

Things@ Nucleus is a highly configurable domain controller which delivers a fully featured edge solution. Nucleus is a foundational component of the Machine Genome and the centrepiece of the Things@ product range. Nucleus provides automated sense control for local sensor / actuator networks of arbitrary complexity. While Nucleus edge devices operate as independant components, they are deployed, updated, and secured with Things@ remote device managment technologies. The deployment models can be either unrelated to third party PAAS or using secured integrations on GE Predix solutions

Relate

In things@ the relationships are as important as the nodes. Connection types and mechanisms are the relationships that give the nodes meaning. See what is connected to a given node. See the connection relationship. The connections may operate under a Quality of Service agreement, they may have metadata that has lifecycle relevance. The richness in things@ on the relationships between nodes means modelling an asset network like Water or Electricity distribution on things@ is a snap, Field services activity-management - same.

What is things@

Features

Its not just about your system - integration between systems can be painful enough, across organisation boundaries timely information sharing can often be an intractable problem. So - is it difficult is it to manage information flow through from your customer through your back office and on to your subcontractors. How difficult is it to get job completion details back on that work. Using the same graph, all the information is avaliable to all the people that need it. Cease and desist from those cumbersome gridlocked integration projects. Share a things@ graph with concerned stakeholders

The things@ REST API is designed with simpicity and ease of use in mind. The REST API uses HTTP and JSON, so that it can be used from many languages and platforms. Discoverability is key, so that you can start with a GET on Service root and from there discover URIs to perform all other avaialble requests. The API can be used as an M2M inteface or as part of a mobile/web client strategy.

As with any database, our graph serves a system that wil change over time. So what should we do when the graph evolves? In a graph, to add new facts or compositions, we can add new nodes and/or relationships rather than changing the model in place. Adding new kinds of relationships will not affect any existing queries, and is completely safe. Likewise adding new types of nodes, while the addition of new nodes of an existing type, connected by exisiting reliationship types is a business as usual field update activity