Industry Input Wanted On Proposed OSIPS Framework-ANSI Standard

Dec 4, 2007 3:35 PM

The Security Industry Association (SIA) has announced the opening of the third formal Public Review of BSR/SIA OSIPS-01-200x, Open, Systems Integration and Performance Standard (OSIPS) -- Framework as an American National Standard. SIA is an American National Standards Institute (ANSI) accredited Standards Developing Organization. The public comment period is open until Jan. 7, 2008.

The OSIPS Framework is the foundational standard for the OSIPS family of standards. Since OSIPS is directed at enabling the open integration of so many various types of components, it is essential to establish precise definitions of shared system elements and common means to communicate. OSIPS Framework provides the requisite definition needed to create this goal including interface infrastructure requirements and special interfaces for shared activities such as event reporting, schedules exchange and other common functions.

"The OSIPS Framework redefines product innovation and development in our industry," says Hunter Knight, chair of SIA Standards Pan Industry Data Models Subcommittee. "Prior to OSIPS anything played; today a baseline for professional performance is in place."

Developed in conjunction with other OSIPS standards activities such as the Digital Video Interface (OSIPS-DVI-01) standard, the Access Control Role (OSIPS-ACR-01) and Access Point Controller (OSIPS-APC-01) efforts, the OSIPS Framework document is referenced by every OSIPS standard as the foundational framework for the program.

Sections of the Framework document address the following areas:

* The OSIPS Framework General Elements section defines a host of model elements that require a global use to ensure proper implementation. This includes globally recognized data element definitions.
* The Component Connection Interface data model details the mechanism by which a consumer connects to a component to obtain a globally unique identifier (GUID) needed to use other component services.
* Capabilities Exchange Interface details the mechanism for consumers learning about the capabilities of a component.
* The Event Reporting interface details the mechanism by which a component may report events.
* The Authentication and Authorization Interface defines a mechanism through which a consumer may manage the authorizations of consumers to use component services.
* The IO Point Interface section defines a model for the messages used to provision, control and monitor IO Points.
* Finally, the Schedules Exchange Interface defines a model for the exchange of schedule information.

Want to use this article? Click here for options!
© 2008 Penton Media Inc.

This month in Access Control

• Targeting The Customer
• Electronic Pedigrees
• One Hero Among Many
• Who? What? When? Where? Why?
• More from September's issue