At the heart of the System, there are some common Building Blocks, common Features and APPs, and a collection of 3rd Party Devices, APPs, and Services. The Reference Model is the overall System and how it fits together, and there are sub-Reference Models that cover the different Use-Cases.  These will evolve over time.

 

Standards and Common Feature/Design Requirements can sound very scary for those that have participated in them. While there is planned to be some competition with multiple companies developing the same or overlapping devices and services, the actual Standards and Guidelines, are mainly for the common elements that participating companies and organizations would have the same access to. Within certain parameters, abstract classes could be developed on top of the standard interfaces.

• Configuration Control of the Standards,  Common Features, Design Requirements, and Deliverables

• Maintain Common System, Device, Service, Feature, and Interface Requirements

• Maintain Common Documentation (Specs, Training, Demo, Installation, troubleshooting, Test, etc.)

• Maintain Common Development and Test Requirements, Standards, and Tools

• Maintain Common Demonstration and Training Requirements, Standards, and Tools

• Maintain Common APP and Device Delivery Requirements and Standards

• Maintain Common Development of Product Support Tools

• Maintain Common Development of On-Line Help

• Maintain Common Development Demo Tools

• Assist in the certification of Common Elements

• Maintain Reference Designs for different Use-Cases/Systems-in-a-Box

• Maintenance of 3rd Party Maintenance Packages (install and upgrade)

 

Note: Some of the Common Device Object Interfaces/Methods include  registration, provisioning, transfer, data collection, data synchronization, online modes, event logging and alerts, , schedule tasks with escalations, analysis tools, reporting tools, upgrade, remote support, record/playback, online help,  etc.