incubator-iota git commit: Platform description documents directory

[to...@apache.org]

Repository: incubator-iota
Updated Branches:
  refs/heads/asf 74cb7979d -> dcc608bf4


Platform description documents directory


Project: http://git-wip-us.apache.org/repos/asf/incubator-iota/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-iota/commit/dcc608bf
Tree: http://git-wip-us.apache.org/repos/asf/incubator-iota/tree/dcc608bf
Diff: http://git-wip-us.apache.org/repos/asf/incubator-iota/diff/dcc608bf

Branch: refs/heads/asf
Commit: dcc608bf498ff372b13ac725023f2efaafbb55c5
Parents: 74cb797
Author: Tony Faustini <to...@apache.org>
Authored: Thu Jun 2 09:26:46 2016 -0700
Committer: Tony Faustini <to...@apache.org>
Committed: Thu Jun 2 09:26:46 2016 -0700

----------------------------------------------------------------------
 Platform Description Documents/Overview.txt | 41 ++++++++++++++++++++++++
 1 file changed, 41 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-iota/blob/dcc608bf/Platform Description Documents/Overview.txt
----------------------------------------------------------------------
diff --git a/Platform Description Documents/Overview.txt b/Platform Description Documents/Overview.txt
new file mode 100644
index 0000000..23a9d56
--- /dev/null
+++ b/Platform Description Documents/Overview.txt	
@@ -0,0 +1,41 @@
+Basic ideas
+
+The Internet of Things consists of 'things' such as sensors, devices, machines, and intelligent edge nodes of all
+types. These things have existed at the edge since the earliest days of the Internet and have becoming increasingly
+popular in recent times. These 'things' exist in both the consumer space and the industrial application spaces.
+Let's call these 'things' points. These points are able to generate data with a volume, variety and velocity that
+surpasses anything we have seen from human input. An IOT platform is one that embraces  the diversity of these
+points at the edge and facilitating their orchestration as a coherent realtime dataflow network.
+Thus enabling action based on their collective input.
+
+Examples
+1) A large building with embedded sensors that efficiently manages the consumption of energy resources
+2) A complex machine such as a car or aircraft
+3) A home
+4) An industrial manufacturing plan
+5) A complex network of inner city traffic controllers
+
+What are the basic requirements of an IOT platform that would enable the broad vision given above? Lets begin by
+looking at the points on the edge
+
+Points
+1) Able to deal with a variety of protocols both legacy and modern (e.g. Bacnet, Modpus, IP, etc)
+2) Able to translate the data into a standard format from any protocol (e.g. id, timestamp, value)
+3) Able to deal with the velocity of real-time data on ingress and egress
+
+Computing at the Edge
+1) Able to intelligently filter data at the edge
+2) Able to intelligently transform data at the edge
+3) Able to intelligently control points on the Edge
+4) Able to operate safely when disconnected from the network (important if you are controlling expensive equipment)
+5) Able to detect errors on the Edge
+6) Able to restart failed filters, transformers and standalone processes (Observation and Supervision of edge processes)
+
+Dataflow Networks
+1) Able to create, update and delete dataflows that define a solution
+2) Able to define rules that enable decisions in dataflows
+3) Able to define actions that are called based on decision rules
+4) Able to monitor actions and rules and restart flows if any of these fail
+5) Able to define a broad class of actions that can be executed if a decision is made via set of rules
+6) Ability to run dataflow networks at different levels of the IOT "hierarchy" - in devices, in connected
+   standalone servers or in clusters.
\ No newline at end of file