Are you ready for change?
Open Automation Object Model (OAOM) will enable programmers throughout the world on how to program these devices from common object model. It will engage the programmer in the automation industry without necessary knowledge of controls drawings and engineering specific diagrams.
What is OAOM going to be?
It will be standard form of creating automation objects which later can be used in automation applications.
How is this standard going to be formed?
We will create a chapter with oasis as soon as we can gather enough attention.
How OAOM will change the industry?
There is actually couple reason why it will change the industry. The main reason is the programmer will be able to program devices without the need of the control drawings. Programmers will be able to focus on what they do best which is programming.
Automation industry is changing rapidly. We need better tools for programming automation devices. Object Automation Model will enable us to have the programming and documentation done with one standard location.
Could you explain how OAOM will help with documentation of Automated Devices?
First of all, OAOM will be just standard for input and output devices so the standard can be used to build submittals, engineering tools, etc.
Why do you think there is a need for a standard like this?
Actually, I was looking into a way to make programming easier and jotting down ideas on the way to Connectivity Week. During the meeting, I attended OpenADR conferences and started to understand how standardization works. Laurant from OASIS (Executive manager) was insistently explaining t
he standardization process. In one meeting, ASHRAE’s president elect at the time was pointing the need of standardization processes like BIM (Building Information Model). At that moment, I realized the need of an open system like this. I introduced the idea to Toby Considine and Laurent Liscia and got back positive feedback.
In my opinion, the need of an OAOM will be seen when systems like OpenADR comes into play. When utility companies try to save energy by either lowering temperature on thermostat or ramping down VFD’s or shutting down lights, we will need programmers to make those changes to the BMS system. Without a set of tools to communicate to the BMS, programs needs to commission from the BMS technician level. If we have a standard application like OAOM, these sets of applications can be programmed from the utility or engineering level and can be handed to the BMS contractor for commissioning.
Another reason why we need a standard is the technology that we use every day is changing rapidly. We have seen a vast information changes and tools like M2M. The amounts of devices that are connected are increasing not in the amount but also in the types. We have phones with different operating systems. Our buildings talk different protocols but they are not programmed in a way that would not make it easier for the programmers to write a code to integrate a phone to a car.
How can we help you?
Please email the following paragraphs along with this interview. We are trying to find sponsors in order to open a chapter in OASIS community.
I am looking for people interested developing a standard XML-based vocabulary for device centric automation and control, initially for use in programming Building Automation Systems (BAS) . The work will be known as Open Automation Object Models (OAOM).
Current methods for cataloging components of an automation system are proprietary. Programming methods are often too low-level (lists of points) to work with without referring to external diagrams and documentation. Configuration and operation of automation systems often use different interaction models. This adds complexity to installation and configuration of systems and makes building system commissioning difficult, expensive, and often unverifiable.
A common framework for describing and programming low level automation objects would enable standardized commissioning and encourage the development of higher functionality system configuration and automation programming tools.
Today, every automation company is repeating tasks every time but the devices do not change. While specifications change slowly, the underlying code may not change at all. If we are able to create a framework for lower end controls that supports advanced functions, it will help the automation industry and improve outcomes and accelerate innovation.
In the automation industry what needs to be controlled does not change. It is either based on temp, temp & pressure, Temp & Pressure & Outside air. These are the event parameters of the code. This initiates part of the function. These parameters can be easily selected dragged and dropped a canvas and easily be commissioned the controller. Once we are done defining our events, we need to define our control object. These are Dampers, Valves, Fans, Coils, and Compressors. Our events will dictate our control objects. There will be parameters section on event objects which can be animated and the links can be made right from the canvas.
Such standard may also enable ‘”plug and play commissioning”
If you are interested in discussing these issues, with a goal of discovering is there is sufficient interest to form an OAOM Technical Committee to create an OAOM standard, please contact signup@oaom.org.