* This site is based on internet standards not supported by IE 6.
wJones
EC Container 5

Automation Appliance Design

Planning Future Solutions

The Automation Appliance reference platform can help accelerate your move to intelligent Stored Purpose solutions.
Subscribe

<< Overview | Platform >>

Automation Appliance Publications

Overview
Design
Platform

Related Documents

Illustrations of Use

Hospital
Retail
All

Metacomputer Publications

What is a Metacomputer?
Labor and Automation
Automation and Small Business
Communicator
All

www.AutomationAppliance.com

Citation

Warren Jones, Lana Rubalsky (2010) "Automation Appliance Design", wJones Research, August 16, 2010
The metacomputer consists of three types of components: objects, symbols and logic.
  • Objects are the physical and data elements of the metacomputer and may include items such as: display instrument devices, lighting controllers, legacy stored program software and documents.
  • Symbols are the knowledge of the system and may include items such as: the Platonic Forms of a door or “Greek” yogurt, or a Purpose to maintain hospital lawn.
  • Logic is the algorithmic processing of the system and includes functions such as: processes of the General intelligence algorithm (Gia), the Synthetic File System (SFS) and curtailment.

User Space

System users are granted a personal assistant agent (a.assistant) that coordinates and configures technology on his/her behalf. Technology actions that could be performed by an agent are only limited by the symbols and objects of the metacomputer. They can include adjusting room temperature, displaying the expected diagnostic procedure on an imaging device menu, or gathering information needed to respond to a question asked during a mobile call.
GeneralIntelligenceAlgorithm
An Agent apparatus is a logical entity that runs in a Resource Soma. An Agent mind is composed of Identity, Knowledge and Technology. An Agent is instantiated and exists when:
  1. there is a working Soma running Gia on a metacomputer,
  2. the Soma has loaded a Patron certified Agent class,
  3. the Gia instantiation process has loaded base Identity
  4. any enhancement Purpose and related Knowledge Forms and Technology has been registered and mediated with the metacomputer,
  5. the metacomputer and Soma have compiled a Resource Synthetic File System for the Agent and exchanged access keys,
  6. the Soma indicates minimal or higher compute capacity is available to all Gia processes.
Agents use mobile device sensors (i.e. bluetooth, GPS, orientation) to gather user context information and use stored purpose awareness to predictively perform services that align technology with the needs of the user.

User Interface

Automation Appliance supports hosting virtualized stored program operating systems and applications and will provide full support for legacy user interfaces and peripherals.

Agents will communicate and exchange information with clients using available technology and based upon user preferences. Platforms used for human-agent coordination will include traditional mobile, laptop and desktop devices, electronic binders and body sensors. Current Automapp prototypes include mobile and large display templates for agent communication. The look and feel of these interfaces would be customized by product companies.
MultiPanelSupport
There are several considerations unique to developers of stored purpose systems that will impact user interface design:
  • Agents will be better than humans at controlling traditional automation technology
  • Human guidance to agents will work primarily without measurable communication, people will rarely touch or directly manipulate devices
  • The agent-human interface will be based primarily on a type of human-agent telepathy, called semantic communication, requiring changes to primary peripheral interfaces (i.e. personal body proximity and orientation vs. keyboard and mouse). Contextual coincident motion and prompting gestures will share little resemblance with today's user interfaces
  • Humans will gain the ability to join and surf consciousness with machine minds by "jacking-in" to an agent synthetic file system, browsing symbols and objects across time and context.

Physical System

The physical metacomputer host is composed of component Instruments that share compatible kernels, communications, memory storage and device capability registration such that computation can span physical devices of the metacomputer.
InstrumentDataFlow
All instruments include a kernel and may include sensors, controllers, media transfer, intent transfer, encryption, signal processing, complex instruction processing, communications, capacity inventory and media and program memory.

Physical setup requires installation of instrument adaptors as “controllers of” or “replacements for” technology in use by a person, home or organization. There are four classes of instruments including hardware adaptor, software adaptor, instrument device and instrument host. Together the instrument types are designed to make technology of an organization (doors, lights, environment control, mobile communications, display workstations, video cameras, audio system, etc.) part of a single metacomputer. Instrument types have large, medium and small configurations based upon X86, OMAP and CC430 processors respectively.

Each Instrument (i.e. mobile phone, HD Display, lighting system, medical instrument) has an inventory of Capabilities, that may be sensors, controllers, media or technologies that convert media. Capabilities are general technologies that can be explicitly or implicitly linked to Goal pursuit.
Symbolic_Network
Each Instrument can be designed as simple or intelligent (Gia compatible), the latter of which will provide services and resources necessary for a symbolic network and will extend the Metacomputer’s fabric. The former will a means for adding legacy stored program technology to the metacomputer.
StoredProgram_StoredPurpose
The agent entities and resources of a metacomputer are considered “in” the metacomputer. Computational services run “in” the metacomputer. All resources “in” the metacomputer are coordinated. This makes all operational parts of a metacomputer and all technologies linked to it subject to a single efficiency model.


<< Overview | Platform >>


EC Container 6