| Overview

The Web Control Namespace introduces a dedicated namespace in Hayloft for creating and managing Web Control Models.

Hayloft currently provides namespaces such as:

• Domain Models
• 75F Models
• External Models

The Web Control Namespace extends this model-management capability by providing a dedicated space for Web Control Models. These models can contain points and equipment definitions required for Web Control applications while following the existing Hayloft model-management and review workflow.

The Web Control Models section provides capabilities to:

• Create Web Control Models
• Build a model from an existing model
• Add and manage points
• Add child equipment
• Define model and point tags
• Define cascade tags
• Edit model data through JSON
• Submit models for review
• Review submitted models
• Manage models from the Web Control Models library

| Web Control Models

The Web Control Models tab is available alongside the existing model namespaces in Hayloft.

The Web Control Models page is divided into two primary sections:

Library

The Library displays Web Control Models that are available in the namespace.

The library includes information such as:

The screenshot also shows actions associated with individual models, allowing users to work with the model directly from the library.

In Review

The In Review section displays Web Control Model requests that have been submitted for review.

The review list includes information such as:

• Status
• Request Type
• Submitted By
• Rejection Note
• Rejected By
• Model Name
• Description
• Tags
• Available actions

A submitted model can therefore be tracked separately from models already available in the library.

| Adding a Web Control Model

To create a Web Control Model:

• Open Web Control Namespace
• Select Add Model / the appropriate model-creation option.
  • Profile Model/ Equip Model/ Device Mode/ Tuner Model

• Enter the model details.

  

• Add the required tags.

Note: The webctrlEntityId is a mandatory tag for any model created under the webctrl namespace.

• Click Add Points to add points to the model.

• Add the required points.

You can also search for tags and select the required points, as shown below.

The selected points are added to the model as below.

• Click Add Child Equip to add any child equip, if required.

• Select and add the required child equip from the list.

The selected child equips are added to the model.

• Use the edit/delete icon to edit further or delete points and sub-equips.

  

• Use the Add icon to add more points to the sub-equip added.

  

• Review the model configuration.
• Select Send for Review.

The Add Web Control Model screen contains the following major sections.\

| Build from an Existing Model

Alternately users can build webctrl models by reusing the existing model in all of the Domain, 75F and Webctrl namespaces. The Build from option allows a user to start a new Web Control Model using an existing model as the basis.

The available model-selection panel includes existing Web Control Models and other available models.

This approach can reduce duplicate configuration when a new model shares points, tags, or equipment relationships with an existing model.

| Bulk Edit Points

The Bulk Edit Points capability allows multiple points to be configured in a tabular format.

The screenshot shows fields including:

This provides an efficient way to configure multiple points without opening each point individually.

Example

Instead of configuring several points individually, a user can populate the required point definitions in the bulk-edit grid and apply the changes together.

| Point-Type Prototypes

The point-selection interface provides access to point-type prototypes.

Examples:

• Condenser water bypass pump
• Condenser water entering pump
• Condenser water leaving pump
• Hot water bypass pump
• Hot water entering pump

These points include attributes such as:

• Command
• Frequency
• Pump
• Speed
• Water
• VFD
• ID
• Kind
• Point
• Site reference

This allows a Web Control Model to reuse standardized point definitions instead of manually defining every point from scratch.

| Child Equipment

A Web Control Model can also contain Child Equips.

The Child Equips section allows users to search for and associate equipment with the model.

Child Equipment Workflow

Search Child Equip → Select Equipment → Add → Review Equipment Configuration

The resulting model therefore contains both:

• Points
• Child Equipment

This provides a hierarchical model structure for Web Control applications.

| Tags

Tags are used throughout the Web Control Model configuration.

There are two important concepts:

Model-Level Tags

These describe or classify the Web Control Model itself.

Examples:

dis, equip, id, siteRef, diag, floorRef, roomRef, tz

Point-Level Tags

Point-specific tags describe the characteristics or relationships of an individual point.

| Cascade Tags

Cascade Tags are available as a separate field when creating or editing a Web Control Model.

A cascade tag allows tag information to be propagated through the model hierarchy.

However, an important distinction :

Cascade behavior is relevant to the Hayloft model representation, while the CCU consumes the resulting point information.

The CCU does not need to know whether a tag was inherited through cascading or manually assigned.

For example, if a point receives a tag through cascading, the resulting point information sent to the CCU is still consumed as point information. The CCU does not necessarily need to distinguish whether the tag originated from a cascade operation.

| Editing a Model as JSON

The Web Control Model interface provides an Edit as JSON option.

This provides an alternate method of editing the model definition directly rather than configuring every field through the UI.

The option can be useful for:

• Reviewing the complete model structure
• Making structured changes
• Working with complex model definitions
• Troubleshooting model configuration
• Verifying point and equipment relationships

Users should validate the JSON before submitting the model for review.

| Submitting a Model for Review

After completing the model configuration, select Send for Review.

The model then moves from the creation/editing workflow into the In Review section.

The review record contains information such as:

• Status
• Request Type
• Submitted By
• Model Name
• Description
• Tags
• Review/rejection information

A reviewer can review the submitted model and either approve it or reject it based on the configured review workflow.

| Web Control Model Review Workflow

The expected high-level workflow is:

Rejected Models

When a model is rejected, the review information includes a Rejection Note and Rejected By information.

This allows the model creator to understand why the submission was rejected and make the required changes before resubmitting it.