Abstract: This disclosure relates to methods, systems, and devices for detecting an operational mode of a building component of an environmental control system. In some instances, the apparatus may include a sensor for outputting a signal related to a measure of power drawn by the building component. The sensor may be a current sensor associated with a power cord of an air conditioning unit. The signal output by the sensor may be received by a signal conditioning circuit for conditioning the signal received from the sensor such as, for example, by amplifying and/or filtering. A comparator may be configured to compare the conditioned signal to a specified threshold associated with an ON condition and/or an OFF condition of the building component. The apparatus may include a wireless interface configured to wirelessly transmit a determination of whether the building component is ON or OFF based on the result determined by the comparator.

Abstract: This disclosure relates to methods, systems, and devices for detecting an operational mode of a building component of an environmental control system. In some instances, the apparatus may include a sensor for outputting a signal related to a measure of power drawn by the building component. The sensor may be a current sensor associated with a power cord of an air conditioning unit. The signal output by the sensor may be received by a signal conditioning circuit for conditioning the signal received from the sensor such as, for example, by amplifying and/or filtering. A comparator may be configured to compare the conditioned signal to a specified threshold associated with an ON condition and/or an OFF condition of the building component. The apparatus may include a wireless interface configured to wirelessly transmit a determination of whether the building component is ON or OFF based on the result determined by the comparator.

Abstract: This disclosure relates to methods, systems, and devices for detecting an operational mode of a building component of an environmental control system. In some instances, the apparatus may include a sensor for outputting a signal related to a measure of power drawn by the building component. The sensor may be a current sensor associated with a power cord of an air conditioning unit. The signal output by the sensor may be received by a signal conditioning circuit for conditioning the signal received from the sensor such as, for example, by amplifying and/or filtering. A comparator may be configured to compare the conditioned signal to a specified threshold associated with an ON condition and/or an OFF condition of the building component. The apparatus may include a wireless interface configured to wirelessly transmit a determination of whether the building component is ON or OFF based on the result determined by the comparator.

Abstract: This disclosure relates to methods, systems, and devices for detecting an operational mode of a building component of an environmental control system. In some instances, the apparatus may include a sensor for outputting a signal related to a measure of power drawn by the building component. The sensor may be a current sensor associated with a power cord of an air conditioning unit. The signal output by the sensor may be received by a signal conditioning circuit for conditioning the signal received from the sensor such as, for example, by amplifying and/or filtering. A comparator may be configured to compare the conditioned signal to a specified threshold associated with an ON condition and/or an OFF condition of the building component. The apparatus may include a wireless interface configured to wirelessly transmit a determination of whether the building component is ON or OFF based on the result determined by the comparator.

Abstract: A protocol independent programming tool for constructing control logic. The control logic may be constructed without dealing in the details of an underlying protocol. The protocol details may be abstracted and exposed and generic points used in constructing the logic. The tool may automatically map or translate the points used in the logic to protocol specific entities.

Abstract: A priority selection mechanism for driving outputs from control logic which can be automatically translated to controllers of various protocols. The priority selection mechanism may assign a priority to the outputs and select the output having the highest priority as the output of the control logic. There may be an abstract representation of the priority logic which may permit a protocol mechanism to be used in the logic without the designer or user needing to know the details of the mechanism.

Abstract: A graphical approach to setup data sharing between two controllers. Symbols that represent controllers may be placed on a wiresheet. A link may be constructed between the controllers by connecting the symbols with a line drawn between them. The resulting link information may lead to a compile and download of binding tables to the pertinent controller. The designer or user need not setup several levels of mapping by populating multiple tables to effect the binding for a link between the controllers. This binding may be done automatically under a hood without the designer or user needing to be aware of the binding activity. This approach for graphically constructing a link may be particularly applicable to BACnet controllers.

Abstract: A mechanism for constructing generic control logic with versions of the logic automatically generated and stored for one or more protocols. The complexity of the one or more protocols may be hidden under a hood of the mechanism from the view of engineers, programmers and users so as to improve their productivity relative to control logic designs and applications.

Abstract: A repository contains multiple versions of an object but only a single version of the object is supplied when a query is made. The single version is automatically selected from among a number of versions, based on a configuration associated with a workspace in which the query originates. The selected version is presented in a version resolved view, without exposing any information related to versioning of the object. A number of configurations are established, each configuration containing no more than one version of each object in the repository. However, only one configuration is associated with each workspace from which a query can originate. A single configuration is commonly associated with the workspaces of all developers. When developers decide that a set of objects in the repository is ready for use in live operation, the set of objects is “deployed” by copying the design time configuration to generate a new configuration.

Abstract: A metadata validation process that allows for deferring object model validation until after the objects are created. The process also allows for multi-threaded processing of the validation rules, thus increasing overall performance. Validation is performed by enforcing a series of validation rules on an appropriate subject. Rules are specified according to the subject that they are validating (i.e., attribute level, association level, object level or collection level). The metadata driven validation process implements several validation types on different validation units. Correctness validation rule types ensure that a validation unit satisfies all semantic rules defined for it. Completeness validation rule types ensure that a validation unit contains all the necessary data and is ready for further use. At design time, only correctness type validation is performed. Thus, the present invention advantageously allows for incomplete objects to be created at design time.

Abstract: A mechanism for constructing generic control logic with versions of the logic automatically generated and stored for one or more protocols. The complexity of the one or more protocols may be hidden under a hood of the mechanism from the view of engineers, programmers and users so as to improve their productivity relative to control logic designs and applications.

Abstract: A priority selection mechanism for driving outputs from control logic which can be automatically translated to controllers of various protocols. The priority selection mechanism may assign a priority to the outputs and select the output having the highest priority as the output of the control logic. There may be an abstract representation of the priority logic which may permit a protocol mechanism to be used in the logic without the designer or user needing to know the details of the mechanism.

Abstract: A graphical approach to setup data sharing between two controllers. Symbols that represent controllers may be placed on a wiresheet. A link may be constructed between the controllers by connecting the symbols with a line drawn between them. The resulting link information may lead to a compile and download of binding tables to the pertinent controller. The designer or user need not setup several levels of mapping by populating multiple tables to effect the binding for a link between the controllers. This binding may be done automatically under a hood without the designer or user needing to be aware of the binding activity. This approach for graphically constructing a link may be particularly applicable to BACnet controllers.

Abstract: A protocol independent programming tool for constructing control logic. The control logic may be constructed without dealing in the details of an underlying protocol. The protocol details may be abstracted and exposed and generic points used in constructing the logic. The tool may automatically map or translate the points used in the logic to protocol specific entities.

Abstract: A metadata validation process that allows for deferring object model validation until after the objects are created. The process also allows for multi-threaded processing of the validation rules, thus increasing overall performance. Validation is performed by enforcing a series of validation rules on an appropriate subject. Rules are specified according to the subject that they are validating (i.e., attribute level, association level, object level or collection level). The metadata driven validation process implements several validation types on different validation units. Correctness validation rule types ensure that a validation unit satisfies all semantic rules defined for it. Completeness validation rule types ensure that a validation unit contains all the necessary data and is ready for further use. At design time, only correctness type validation is performed. Thus, the present invention advantageously allows for incomplete objects to be created at design time.

Abstract: A metadata validation process that allows for deferring object model validation until after the objects are created. The process also allows for multi-threaded processing of the validation rules, thus increasing overall performance. Validation is performed by enforcing a series of validation rules on an appropriate subject. Rules are specified according to the subject that they are validating (i.e., attribute level, association level, object level or collection level). The metadata driven validation process implements several validation types on different validation units. Correctness validation rule types ensure that a validation unit satisfies all semantic rules defined for it. Completeness validation rule types ensure that a validation unit contains all the necessary data and is ready for further use. At design time, only correctness type validation is performed. Thus, the present invention advantageously allows for incomplete objects to be created at design time.

Abstract: A repository contains multiple versions of an object but only a single version of the object is supplied when a query is made. The single version is automatically selected from among a number of versions, based on a configuration associated with a workspace in which the query originates. The selected version is presented in a version resolved view, without exposing any information related to versioning of the object. A number of configurations are established, each configuration containing no more than one version of each object in the repository. However, only one configuration is associated with each workspace from which a query can originate. A single configuration is commonly associated with the workspaces of all developers. When developers decide that a set of objects in the repository is ready for use in live operation, the set of objects is “deployed” by copying the design time configuration to generate a new configuration.

Abstract: A repository contains multiple versions of an object but only a single version of the object is supplied when a query is made. The single version is automatically selected from among a number of versions that are otherwise returned in response to the query, based on a configuration associated with a workspace in which the query originates. The selected version of the object is then presented in a version resolved view, without exposing any information related to versioning of the object. Specifically, a number of configurations are established, each configuration containing no more than one version of each object in the repository. However, only one configuration is associated with each workspace from which a query can originate. The configuration that is associated with the workspace depends on whether the workspace is to be used for design of the repository or for use of the repository during live operation.

Abstract: A system for generating outgoing and translating incoming messages, comprising a core engine and a plurality of plug-ins; outgoing system further comprising a trading partner agreement database (TPAD). For the outgoing message, the TPAD identifies a particular extensible document format protocol plug-in and a particular extensible exchange protocol plug-in from plurality of plug-ins based on the parties' agreement. The core engine translates and constructs the message by encoding it with the identified plug-ins respectively. For the incoming message, the core engine examines every extensible exchange protocol, identifies the particular extensible exchange protocol, and decodes the incoming message with the identified exchange protocol. The core engine then examines every extensible document format protocol, identifies the particular extensible document format protocol, and processes the decoded message with the identified document protocol.

Abstract: A repository contains multiple versions of an object but only a single version of the object is supplied when a query is made. The single version is automatically selected from among a number of versions that are otherwise returned in response to the query, based on a configuration associated with a workspace in which the query originates. The selected version of the object is then presented in a version resolved view, without exposing any information related to versioning of the object. Specifically, a number of configurations are established, each configuration containing no more than one version of each object in the repository. However, only one configuration is associated with each workspace from which a query can originate. The configuration that is associated with the workspace depends on whether the workspace is to be used for design of the repository or for use of the repository during live operation.