Getting Started


Domain Models


A good place to start getting an overview of the Telemetry Integration Framework is the Telemetry Domain Models.  They will give you a general 'big picture' of how the technology fits together. You can drill down from the overview model to a specific domain, for more detail. Each domain provides an overview of it's functions and data.


You can use the domain model to provide knowledge management categories for documents and artefacts belonging to a domain or a domain entity.  A simple way to do this is by providing HTML links within the diagrams, which can be published later as HTML documentation, containing the links.  The HTML can then be added to enterprise knowledge and content management systems.


Application Entity Models


The application entity models provide a context for application design. The application functions are mapped in an integration context. This enables a recognition of the boundaries of the common software infrastructure.


All of the applications represented 

- mobile item tracking

- vehicle tracking

- asset tracking

- biometric sensor tracking


may be deployed on a common set of integration software.


Take a look at the application Entity Models, e.g. for Asset Maintenance, Vehicle Tracking, etc, that are relevant to your business. This will give you a good overview of the business processes that will be required for each application.


These models are intended to display a contextual overview of the essential entities of the business application, in context of the telemetry integration.


Functions are represented in the domain model as conceptual classes.


All of the data classes, integration and application metadata, provide the logical data model.


The prefix on the class name, indicates that the class belongs to a different package. e.g. a Telemetry Device has been defined as belonging to the Network package.


Information Models


The Information Models are the logical representations of data elements that are used in software applications and infrastructure platform.


Major types are logical entities, interface schema, message schema and physical data schema.


With an overarching architecture across all data elements, and a semantic approach to mapping disparate data, using common models, redundancy and duplication of data and development effort can be reduced to relative insignificance.  A substantial benefit of information models is the ability to do semantic mapping in real time, when the technology is configured for real time event processing.



Metadata


Application and Integration metadata provide the basis for semantic integration of different data elements across applications and software infrastructure.  They provide a logical and common data model for mapping across different physical data schema, with either direct or logically derived corresponding elements.