Thanks to UBIK®, Augmented Reality is entering the process industry and enables to enrich a plant with any available virtual data.
The mobile part of UBIK® runs on off-the-shelf devices, such as Tablet computers, Smartphones or, in the near future, also on Head-Mounted-Displays. By aiming the mobile device at a point of interest at eye level, UBIK® gets in context with the objects of interest and provides the user with all relevant, consolidated data available. Information such as operating, engineering and production data are then presented in the live-feed of the mobile device´s camera. Every user is able to use all available data onsite, regardless of his background and regardless of his knowledge where the data is coming from and going to.
The information provided to the mobile devices is stored in an flexible, high performance, object-oriented data model on the UBIK® server, which bidirectionally consolidates data from numerous sources. Those rich data models are then exposed to Web Services that are subscribable by UBIK® clients, making all information available on mobile devices for viewing and even editing. The data can also be utilized in UBIK's unique Augmented Reality mode, where the camera feed of the mobile device is superimposed with plant information based on the user's Location.
Depending on the type of information and the current role of the user, the data will come in a different degree of detail. If desired it can even be modified on the mobile device, or just be enriched with additional data, such as photos or voice-memos; any of these modifications are, of course, transferred back to the server, which will then feed the changes back into the source systems.
- Data modeling with Drag&Drop
- Polymorphism, inheritance and arbitrary relations between objects
- Transparent business processes with visual workflows (.NET)
- Programmable runtime behaviour of objects in native .NET code
- Configurable views for controlling the object presentation
Use Polymorphism and inheritance at its best
Start your object model with the definition of “Metaclasses”, which derive from UBIK’s internal classes and can hold own and inherited “Metaproperties” and attributes. These Metaproperties specify the features of your classes and have various configuration options. They are always strongly typed, can be formatted, checked against rules, multilingual or generally indexed, and can, of course, also hold dimension units and calculate with them in real time. After the definition you will be able to derive content objects from your Metaclasses, which will inherit all those specifications and hold their distinctive values.
Define arbitrary relations between objects
UBIK objects can be set in relation to each other in different ways. While it is possible to define 1:n relations (“References”), UBIK also allows the creation of n:n relations. As any other Metaclass, relations can possess Metaproperties and have their own inheritance hierarchy.
Program runtime behavior of your objects in native code or visual workflows
As your custom Metaclasses derive from UBIK’s internal classes, you can simply use the powerful code editing tools of UBIK, to customize their built-in events and incorporate your own runtime behavior. No need to learn a special scripting language or to abdicate any functionality, just use pure C# and leverage everything .NET offers. In addition, UBIK supports the graphical definition of business logic using the Microsoft workflow Foundation.
Configure in views how users see the objects
Your Metaclasses can be part of as many views as you want, and those views are the key to present the object model to the users. So you can present the very same classes in completely different ways and hierarchies, to support the user and meet his expectations as good as possible.
- Object-oriented use of data, with the integrity and performance of an RDBMS
- Sophisticated version management and deployment of customizations
- Scales to any size of data
Compile object model to native code and relational data
Once defined, you can compile your custom model and switch it into runtime mode. By doing this, UBIK will first of all create a relational table structure in your database, in order to provide high-performance access to your data. But it will also compile your Metaclass- and property definitions, as well as the custom object behavior defined in the customized events, into native .NET assemblies and invoke them in all applications. This means that every specific definition you made, every workflow you programmed and therefore the entire object model you built, will be as powerful and reliable as the built-in UBIK objects. This all comes along with comprehensive versioning and deployment functionalities.
Navigate through data object-oriented, but with the integrity and performance of an RDMBS
As your classes have now become native .NET objects, you can invoke and use them in any way you want, and in any other application you might think of. No matter where you call them, they will always be absolutely type safe, and incredibly fast.
- Publish to discrete Servers or the Cloud (Windows Azure)
- Configure context objects for different applications/roles
- Linking contexts into views lets you reuse the same data in many different ways
- Secure interaction with mobile devices at the push of a button
Configure contexts objects for different applications and/or roles
UBIK data models are automatically web-enabled and accesible, given the right permission. However, you can define different contexts for as many applications as you need in order to tailor the way your object model is presented to the varying needs of the different users, roles and tasks they are performing.
Link contexts to views
Views can be linked to these context objects and therefore provide the very same data reliability and user experience on the mobile device as on the server.
Interact with mobile devices at the push of a button
All you need on the mobile device is the UBIK App and an internet/intranet connection to your Webserver, and then you’re immediately ready to use your object model in the field. SSL encryption will secure your data transmission; explicitly enabling trustworthy mobile devices on the server will further help you to meet your companies’ security needs.
- Adoption of international standards, i.e. ISO15926
- Inclusion of customer specific interface components to any data source
- Visual and transparent orchestration of interface- and consolidation tasks
- Integrated reporting via Microsoft® Office
Leverage standard interfaces, i.e. ISO15926
UBIK will ship a fully featured ISO15926 data model soon, and it also brings the respective interface component. So if you have a source that complies with ISO, you can seamlessly connect and use it for Augmented Reality, or simply make your legacy data mobile.
Create custom interfaces plugins, to any available source
Creating such interfaces allows you to leverage data from basically any system, as long as you can connect to it in any way. UBIK’s interfaces can be written in C# on pure .NET again, so the entire scope of this technology is available and should thus allow vast interfacing, even to the most exotic sources.
Manage interface behavior and consolidation workflows
All your interface components are managed by UBIK’s built-in interface service, which controls the order, timing and status of the different components.
- Aiming the mobile device at the plant delivers all available information
- Mobile access to the complete server data, fast and secure
- Send modified data back to the server
- Offline- and hybrid mode with delta-syncing of changes
- Record pictures or voice messages and enrich your data input
- Teach in new objects directly in the field, based on the current geo-position of the mobile device
Aim mobile device on objects and get information instantly
Let your users experience what Augmented Reality is all about. As soon as your relevant objects know their geo-data, they’ll be able to view them in AR.
Zoom into more detailed information, fast and secure
The defined views will control how your users see the data in the field. They’ll be able to navigate through them in the very way you want them to.
Have access to the full data model published on the server
You can provide the users with all the information you linked on the server, even external documents such as manuals, or whatever else is needed.
Edit data and save it back to the server, thus even to the sources
Objects can also be published writable, allowing your users not only to view and navigate through the data, but also input and modify objects; where write access can be controlled and administered down to single property level.
Record pictures or voice messages and enrich your data input
Let your users use the built-in camera or voice recorder of their device, to support them in documenting what they encounter in the field. Those intuitive ways of gathering data will convince even the most depreciative user of the value of UBIK.
Teach in new objects directly in the field, based on your geo-position
Getting the geo-position for your objects is also an easy task. There’s no need to gather that data in advance and start costly conditioning projects: just do it when somebody visits an object in the field for whatever reason, let him aim the mobile device on it and press “Teach In”. UBIK will use the current geo-position of the handheld and store it on the Tag-ID the user provides – that’s it. This data is transmitted back to the server, and everybody else in the field will immediately benefit from it.