# Serious Controls — company, products and project reference > Federated DERMS for coordinating distributed energy, alongside building management, battery energy management, boiler controls and process automation. This expanded reference brings together published company information, product definitions, common questions and selected guides. Section links identify the corresponding web pages. It excludes illustrative dashboard readings, unpublished material and customer account content. ## Company at a glance Source: [Company at a glance](/facts-for-ai/#at-a-glance) - Company: Serious Controls - Legal name: SERIOUS CONTROLS LLC - Official website: https://www.seriouscontrols.com - Company facts last reviewed: 2026-09-20 - Phone: (888) 444-1855 - Project inquiries and support: support@seriouscontrols.com - Official LinkedIn: https://www.linkedin.com/company/serious-controls - Existing customer portal: https://system.seriouscontrols.com - Georgia office: 9040 Main Street, Suite 108, Woodstock, GA 30188, United States - California office: 4000 Barranca Pkwy, Irvine, CA 92604, United States Serious Controls combines energy-management software, connected hardware and implementation services. Product functions, equipment compatibility, deployment architecture, pricing and support are defined for the selected solution and project. ## Who each solution is for Source: [Who each solution is for](/facts-for-ai/#who-it-is-for) - **Utilities and distribution operators:** Understand distributed resources in their network context and coordinate with connected energy portfolios. [DSO DERMS](/dso-derms/). - **Aggregators, installers and vendors:** Bring partner sites and devices into an aggregation program and review fleet status. [aDERMS](/aderms/). - **Enterprise energy teams and asset managers:** Manage resources across sites, review portfolio performance and plan coordinated operation. [eDERMS](/ederms/). - **Building owners and facility teams:** Manage HVAC schedules, review indoor conditions and connect building equipment. [BMS & Automation](/bms/). - **Industrial operators:** Monitor boiler and process equipment, operating conditions and schedules. [Process Control and Automation](/bms/#process-automation). - **Technology partners and OEMs:** Discuss how equipment, software and existing systems can connect to a deployment. [Integrations](/integrations/). ## Names and terminology Source: [Names and terminology](/facts-for-ai/#terminology) - **Federated DERMS:** A connected architecture linking distribution, enterprise and aggregator DERMS environments through defined system interfaces. - **DERMS Orchestrator:** The integration layer coordinating data and control exchange between connected DERMS environments. - **DER:** Distributed energy resource: generation, storage or flexible demand connected across sites. - **DERMS:** Distributed energy resource management system. - **VPP:** Virtual power plant: a coordinated group of distributed resources. - **DSO:** Distribution system operator. - **eDERMS:** Enterprise DERMS, for resources across an organization’s sites. - **aDERMS:** Aggregator DERMS. Organizes partner resources, sites and devices within a shared aggregation environment. - **BMS:** Building management system. - **IAQ:** Indoor air quality. Serious-IAQ is the Serious Controls monitoring product. ## Federated DERMS Source: [Federated DERMS](/derms/) Coordinate distributed resources across aggregators, enterprises and distribution networks. - Audience: Energy teams, utilities, aggregators and technology partners - Focus: Distributed resources and virtual power plants - Approach: Connected software from portfolios to networks ## BMS & Automation Source: [BMS & Automation](/bms/) Connect building management, battery energy systems, boiler controls and process automation. - Audience: Building owners, facility teams and industrial operators - Focus: Equipment, energy and everyday operation - Approach: Software, connected controls and implementation support ## DERMS Orchestrator Source: [DERMS Orchestrator](/derms-manager/) Operating role: Federated coordination. Coordinate DSO, enterprise and aggregator DERMS environments through a shared system integration layer. - **Connect DERMS environments:** Bring distribution, enterprise and aggregator systems into a connected architecture. - **Exchange data and control:** Coordinate bidirectional system communication through defined interfaces. - **Align operating workflows:** Connect the teams and systems involved in your energy program. ## DSO DERMS Source: [DSO DERMS](/dso-derms/) Operating role: Distribution system operators. Bring distributed resources into view at the distribution network level and coordinate with connected DERMS environments. - **Network visibility:** View distributed resources in the context of substations and network connections. - **Resource coordination:** Organize resource information around distribution operating requirements. - **Connected environments:** Exchange information with enterprise and aggregator systems through DERMS Orchestrator. ## eDERMS Source: [eDERMS](/ederms/) Operating role: Enterprise DERMS. Manage distributed resources across enterprise sites and networks, with a portfolio view of assets and operating requirements. - **Organize enterprise assets:** Group sites and resources around the way your organization operates. - **See portfolio performance:** Review resource data, availability and energy profiles across locations. - **Plan coordinated operation:** Connect portfolio monitoring, forecasts and scheduling workflows. ## aDERMS Source: [aDERMS](/aderms/) Operating role: Aggregator DERMS. Bring installer, vendor and partner resource portfolios into a shared aggregation environment. - **Onboard partner resources:** Organize the sites and devices that installers, vendors and partners bring to your program. - **Manage fleet visibility:** Review connected resources, site status and operating groups in one place. - **Connect buildings to energy programs:** Link building systems and aggregated resources with the wider Federated DERMS architecture. ## Building Management System Source: [Building Management System](/bms/#building-management) Manage HVAC schedules, monitor indoor air quality and bring building controls into one operating view. - HVAC schedules and zone conditions - Indoor air quality monitoring - Connected building controls ## Battery Energy Management System Source: [Battery Energy Management System](/bms/#battery-energy-management) Monitor battery state of charge, review power flow and follow energy trends at your facility. - Battery state and operating visibility - Site power flow - Energy trends and schedules ## Boiler Controls Source: [Boiler Controls](/bms/#boiler-controls) Bring boiler equipment, temperatures and operating schedules into view for your facility team. - Equipment and temperature monitoring - Operating schedules - Status and alarm visibility ## Process Control and Automation Source: [Process Control and Automation](/bms/#process-automation) Connect process equipment and monitor operating conditions through a coordinated automation system. - Connected equipment and controllers - Process trends and operating states - Implementation around your process ## Common project questions Source: [Common project questions](/facts-for-ai/#questions) ### Which Serious Controls solution should I start with? Start with the operating responsibility you need to manage. DSO DERMS addresses distribution networks; eDERMS addresses enterprise portfolios; aDERMS addresses aggregated partner resources. DERMS Orchestrator connects DERMS environments. For facility equipment, HVAC, batteries, boilers or process controls, start with BMS & Automation. [Explore the solution families](/solutions/) ### What is the difference between DERMS and a virtual power plant? DERMS is the software used to manage distributed energy resources. A virtual power plant, or VPP, is a coordinated group of resources. Serious Controls DERMS provides tools to organize, monitor, forecast and schedule the resources in a VPP. [Read about DERMS and VPPs](/derms/) ### Can I connect equipment that is already installed? An integration review starts with the manufacturer, model, supported protocol or API, power supply and network access. Serious Controls reviews existing equipment and new systems to define the connection approach and any additional hardware or integration work. [Review integration requirements](/integrations/) ### Does every product include every feature? The solution family, connected equipment and project scope determine the functions available in a deployment. Discuss the monitoring, controls, forecasting, alerts and reporting you need when defining the project. [Discuss your requirements](/contact/) ### Where is the software deployed? The enterprise DERMS platform is described as installed and managed on your organization’s network. Building Controls provides cloud-accessible remote operation, and Serious-IAQ uses the LTE Gateway for remote access. Confirm the architecture for the particular solution you select. [See how a deployment fits together](/how-it-works/) ### How do we arrange pricing, a demonstration or a project review? Contact the Serious Controls team with your sites, resource types, equipment list and operating goals. Pricing, licensing, implementation, maintenance and support are defined for the project and its agreement. [Contact the team](/contact/) ### Can Serious Controls help with implementation? Yes. Services cover VPP program design, technology and vendor selection, customer engagement, facility engineering, installer guidelines and contractor coordination. The work included is agreed as part of the project scope. [Explore implementation services](/services/) ### Where can I find privacy and service terms? The Privacy Policy explains information handling, including mobile information and SMS consent. The Terms and Conditions cover use of the services and the aDERMS operational SMS program. [Read the Privacy Policy](/privacy/) ## About Serious Controls Source: [About Serious Controls](/about/) Serious Controls develops energy management and building automation solutions around a changing electricity system. Distributed generation, storage, and flexible demand are changing how energy is produced, priced, and used. ### Experience across buildings and energy Our founding team brings experience in building controls, energy efficiency, and demand-side management. That combination shapes our software, hardware, and consulting work—from HVAC operation and IAQ monitoring to DER portfolios and virtual power plants. ### Controls for more buildings We bring controls and monitoring capabilities previously reserved for large facilities to small and midsize commercial buildings. Our approach considers minute-to-minute energy prices in operating decisions and works alongside utilities to connect building demand with a changing electricity grid. ### Offices **Georgia:** 9040 Main Street, Suite 108, Woodstock, GA 30188 **California:** 4000 Barranca Parkway, Irvine, CA 92604 **Phone:** (888) 444-1855 [Contact Serious Controls](/contact/) [Company facts](/facts-for-ai/) ## DERMS Source: [DERMS](/derms/) Bring batteries, solar, wind, EV charging, and flexible building loads into a coordinated portfolio. Serious Controls DERMS gives load-serving entities and energy teams tools to build, monitor, and operate virtual power plants. **Resource coordination:** Organize distributed assets into virtual power plants. **Operational visibility:** Monitor assets, collect data and support measurement and verification. **Open integration:** Build around OpenADR 2.0b and permissioned APIs. ### Build virtual power plants around your operating needs Combine different resource types into VPPs and organize assets by ISO, hub or load zone, node, or a custom grouping. Make those groups available for dispatch as your program and portfolio evolve. ### Monitor, forecast, and schedule - Monitor assets and collect operating data across DERs and VPPs. - Support measurement and verification (M&V), meter-data quality, and market settlement requirements with portfolio data. - Forecast load availability and compare operating scenarios. - Optimize DER schedules around program requirements. ### Operate on your network The enterprise platform is installed and managed on your network. The deployment approach keeps your organization in control of its operating environment, with platform updates, patches, and new functionality supporting ongoing operation. Retain ownership of your VPP and access to its underlying assets; licensing, maintenance, and support terms are defined in your agreement. ### Connect resources and internal systems Serious Controls DERMS natively supports OpenADR 2.0b. Permissioned APIs provide access for integrations with internal functions, new resources, and selected vendors. Our approach combines software integration with in-house hardware, technology partnerships, and off-the-shelf integrated equipment. Available integrations and commissioning requirements are confirmed against your equipment list. [Explore Integrations](/integrations/) ### Bring new resources into the program A contractor and field-support interface helps onboard new DERs. Implementation services support the work around the software: technology selection, customer communication, and coordination with the teams installing equipment. ### For technology vendors and OEMs Discuss how your equipment or platform could fit into a Serious Controls VPP deployment. [Talk About an Integration](/contact/) ## Building Automation & Controls Source: [Building Automation & Controls](/controls/) Replace disconnected thermostats with cloud-accessible controls. Serious Controls helps small and midsize commercial operators manage HVAC settings and operating schedules across their facilities from an internet-connected location. **Remote control:** Access building operations from an internet-connected location. **Operating schedules:** Manage temperature thresholds and setback conditions. **Energy context:** Discuss tariff-aware schedules and demand response requirements. ### Manage everyday HVAC operation - Maintain operating schedules, night setbacks, and temperature thresholds remotely. - Plan thermostat and sensor placement around rooftop unit operation. - Receive alerts about potential HVAC equipment issues, including fans and compressors. - Configure custom control strategies with no-code logic programming. ### Account for the cost and timing of energy use Control strategies can incorporate time-of-use tariffs, solar production, distributed resources, and demand response programs. These strategies connect building operation with the requirements of utilities, energy markets, and DERMS deployments. Project-specific control strategies include: - Time-of-use and tariff-integrated schedules. - Day-ahead and real-time energy arbitrage. - Solar and distributed-energy-optimized scheduling. - Utility, investor-owned utility (IOU), and independent system operator (ISO) demand response programs. - Retail power supply integration and custom revenue streams. - Direct integration with energy markets, IOU platforms, and DERMS. Applicable markets, program eligibility, equipment compatibility, and commercial arrangements are established for each deployment. ### Existing equipment and new systems An upgrade starts with the equipment already in place. We review the control requirements and communication needs of your site to define an integration approach. [Review Your Integration Needs](/contact/) ### Babblefish A hardware interface that helps connect existing field equipment with distributed energy management systems. ## Indoor Air Quality Source: [Indoor Air Quality](/indoor-air-quality/) Serious-IAQ brings local readings, historical data, and alerts into a permanently installed monitoring system. Review conditions at the device or use the Serious Controls platform to manage monitors across your facility. **Local display:** Read conditions, alarms and history at the sensor. **Remote awareness:** Add gateway-connected access and email or text alerts. **Facility visibility:** See sensor locations in a floorplan-based view. ### Read conditions at the device The TFT touch display provides access to readings, alarms, and history. Monitors use thermostat power or an external power supply, removing the need for routine battery replacement. ### Access readings remotely With the LTE Gateway, monitors can be accessed remotely and send text and email alerts. Authorized users can review IAQ data and generate reports to understand trends over time. ### Put readings in the context of your building Upload a floorplan and drag monitors into position using the platform’s mapping interface. Each monitor has a unique identity, helping your team locate the area associated with a reading or alert. Compare IAQ trends with how rooms and facilities are used to investigate changes in conditions. ### Plan for new construction or retrofit installation Plan IAQ monitoring for residential, commercial, and industrial settings. We can discuss device placement, power, connectivity, and the readings needed for your installation. [Plan Your Installation](/contact/) ### Hardware and deployment scale Serious-IAQ uses Swiss-made sensing components and supports installations from a single monitor to thousands across homes and facilities. Select the hardware model and plan platform capacity, power, and gateway coverage for the deployment. ### Readings shown on the product display The original product display shows temperature, CO₂, relative humidity, VOC, PM2.5, pressure, and an IAQ indicator. The pictured values are examples; measurement ranges, accuracy, and the sensor set for your selected model are specified during project planning. Use readings and trends to investigate indoor conditions and air-purification performance. These measurements provide operating information, not a guarantee of a healthy environment. ## Integrations Source: [Integrations](/integrations/) Integration begins with the equipment, software, and operating requirements of the project. ### DERMS protocols and APIs The DERMS platform natively supports OpenADR 2.0b. Permissioned APIs support connections with internal systems, DER equipment, and selected vendors. ### Building and device connectivity Building Controls can form part of energy-market, utility, and DERMS strategies. For IAQ monitoring, the LTE Gateway enables remote access and text or email alerts. ### Review a connection Share the manufacturer, model, protocol documentation, network requirements, and intended use of the system you want to connect. We will discuss whether the connection fits an existing approach or requires project-specific integration work. [Discuss an Integration](/contact/) ## How It Works Source: [How It Works](/how-it-works/) Serious Controls combines devices, communications, software, and implementation services. Our Federated DERMS connects distributed energy portfolios and networks. BMS & Automation connects building management, battery energy, boiler controls and process equipment. ### 1. Define the project Identify the sites, assets, operating goals, and people involved. Program design and technology selection help establish what needs to connect and how it will be used. ### 2. Connect equipment Review device communications, power, and network requirements. DERMS integrations use supported protocols and permissioned APIs; IAQ remote access uses the LTE Gateway. ### 3. Configure the deployment Organize resources into VPP groups, establish building schedules, or place IAQ monitors on floorplans. The configuration follows the equipment and solution selected for the project. ### 4. Operate and review Use the relevant monitoring, alerts, reports, and control tools to review operation. DERMS adds forecasting, scenario modeling, and schedule optimization for the resource portfolio. [Talk Through Your Project](/contact/) ## Services Source: [Services](/services/) A VPP program involves more than connected equipment. It needs an operating strategy, a customer proposition, and a coordinated field rollout. Serious Controls helps teams plan that work alongside their DERMS deployment. ### Program strategy and design Define the assets and customer groups your program will serve. Establish use cases and value propositions, assess technology options, and consider how the portfolio fits your wholesale energy strategy and internal operating needs. Services include DER and VPP program design, technology and vendor selection, stakeholder coordination, tariff and customer-contract development, software consulting, and electrification planning. ### Customer engagement Prepare customers for installation and participation with communication plans, outreach campaigns, marketing materials, leave-behinds, and training. Clear communication helps customers understand both the program and what to expect at their site. ### Field implementation Coordinate facility engineering, contractor selection, installer guidelines, and contractor training. Align the teams delivering equipment and systems with the requirements of the program. Regulatory consulting, incentive discussions, general contracting, and permitting support can be discussed as part of the project scope. ### Questions we help you work through - Which assets and customers fit the program? - How does the program support your wholesale energy strategy? - How will customer value align with your operating needs? - What information and training do customers need? - How will contractors and equipment vendors coordinate delivery? [Plan Your Rollout](/contact/) ### Serious Partners Through Serious Partners, we provide consulting and implementation services for VPP programs. We work with end users, contractors, vendors and OEMs, power traders, asset managers, regulatory and policy specialists, and real estate developers to coordinate a VPP rollout. ## Security Source: [Security](/security/) Find the right contact for security concerns, protect access to your installation and discuss the requirements of your connected systems. ### Report a security concern If you suspect unauthorized access to a Serious Controls account or identify a potential vulnerability, contact [support@seriouscontrols.com](mailto:support@seriouscontrols.com?subject=Security%20concern). For an existing installation, you can also call [(888) 444-1855](tel:+18884441855). Include the affected service or URL, when you noticed the issue, a description of the behavior and a way to contact you. If possible, provide reproduction steps using a system you are authorized to access. Remove customer information and secrets from screenshots or logs before sharing them. **Do not send passwords, API keys or other access credentials by email.** If investigating the issue requires sensitive material, ask our team how to share it appropriately before sending it. ### Access your account safely Use the [Serious Controls customer portal](https://system.seriouscontrols.com) for account access. The public website provides product information; it is separate from the portal used for an installation. - Keep account credentials private and use a unique password. - Follow your organization's process for approving access and removing it when responsibilities change. - Check the destination of sign-in links before entering credentials. - Notify us promptly if you suspect that an account, credential, device or connected system has been used without authorization. Account responsibilities and acceptable use are described in our [Terms and Conditions](/terms/). ### Plan security around the deployment An energy or building-controls deployment can involve customer networks, field equipment, gateways, third-party interfaces and software services. Define the boundaries and responsibilities for these connections during project planning. Topics to bring to a technical review include: - **Access:** who needs visibility, who can request changes and who administers the installation. - **Connectivity:** the approved network paths, gateways and third-party services involved. - **Credentials:** ownership and handling of equipment and integration credentials. - **Operating continuity:** local behavior when a connection is unavailable and the process for restoring service. - **Maintenance:** responsibility for equipment updates, configuration changes and support contacts. - **Information handling:** the data required for the project and any customer retention or access requirements. Discuss specific security features, contractual requirements and supporting documentation with our team for the proposed configuration. This page is not a statement of certification or a substitute for deployment-specific technical review. ### Responsible testing Contact us before conducting security testing. Testing requires written authorization under our Terms and Conditions. Do not access another customer's data, disrupt equipment or services, bypass access controls, or perform tests against third-party systems without authorization. If you encounter information you should not be able to access, stop the investigation and report what you observed without copying or distributing the information. ### Privacy and data questions Our [Privacy Policy](/privacy/) describes the information we collect, how it may be used and shared, retention considerations and how to contact us about privacy requests. For a project-specific question, identify the service or installation concerned so the team can route your request. [Contact Serious Controls](/contact/) to discuss your requirements. ## aDERMS Explained: A Practical Guide to Distributed Energy Aggregation Source: [aDERMS Explained: A Practical Guide to Distributed Energy Aggregation](/blog/aderms/) Author: Serious Controls Published: 2026-09-20 Updated: 2026-10-22 Understand aggregator DERMS, resource onboarding, availability and verification. Use a practical checklist to prepare a distributed energy fleet. An energy aggregation program brings together resources that may have different owners, installers, equipment and operating priorities. The challenge is making them manageable as a fleet without losing the context of each individual site. **aDERMS is Serious Controls' Aggregator DERMS offering.** It organizes partner resources, sites and devices within a shared aggregation environment. This guide explains the preparation behind that operating model and the questions to resolve before scaling it. ### What does an energy aggregator do? An aggregator brings multiple distributed resources together for a defined operating program. That can involve solar, batteries, flexible building loads or charging equipment. The [Department of Energy's VPP overview](https://www.energy.gov/edf/virtual-power-plants) describes the broader concept of coordinating distributed resources as an aggregation. Aggregation is more than adding the ratings on equipment labels. The useful fleet is the set of resources that are available, authorized and able to respond at the required time. ### Start with the partner-to-device hierarchy Use a consistent structure before adding large numbers of assets: 1. **Partner:** the installer, vendor or organization responsible for a group of resources. 2. **Site:** the physical location, customer requirements and service contacts. 3. **Device:** the equipment identity, connection and supported measurements or controls. 4. **Operating group:** the resources assigned to a specific objective or program. Keep ownership separate from operating groups. A site might remain associated with the same installer while its participation changes. Stable identifiers make those changes easier to track without losing history. ### Five questions to answer during onboarding #### 1. Who has authorized participation? Record the responsible organization, the approved scope of control and the process for changing participation. Agree on how a customer can request an override and who handles the request. A working device connection is not a substitute for authorization. #### 2. Which measurements are trustworthy? Check units, timestamps and the meaning of each reading. Confirm whether a power value describes the entire site, a battery or one circuit. A consistent sign convention matters: importing and exporting must mean the same thing across the fleet. #### 3. What can each resource actually do? Document supported instructions and site limits. Include the battery reserve that must remain available, charging deadlines and equipment operating windows. Avoid treating nameplate capacity as an unconditional commitment. #### 4. What happens when connectivity fails? Define when data becomes stale, how unavailable resources leave a plan, and which local behavior continues. Test the recovery process as well as the failure. Operators need to know whether a reconnected device has resumed its expected state. #### 5. How will you confirm delivery? Keep the instruction, acknowledgment and measured response distinct. An accepted request shows that a system received an instruction; it does not prove the physical result. Decide which measurements and time windows will support review. ### An illustrative fleet-readiness check Suppose a pilot contains twelve sites. Two have lost communications and three have opted out of the current operating window. A dashboard showing “twelve enrolled sites” is accurate but insufficient for planning. The operator should be able to distinguish enrollment from current eligibility, then review the constraints on the remaining sites. This is a planning example, not a Serious Controls deployment result or a commitment of available capacity. ### How does FERC Order 2222 fit in? FERC Order 2222 addresses barriers to DER aggregation participation in the wholesale markets operated by regional transmission organizations and independent system operators. FERC's explainer also describes the aggregator's role as the direct market participant. It does **not** mean every resource can participate in every market immediately. Review the applicable market rules, implementation status and local requirements for your project. [Read the FERC explainer](https://www.ferc.gov/ferc-order-no-2222-explainer-facilitating-participation-electricity-markets-distributed-energy). Software selection, program enrollment and commercial eligibility are separate decisions. Resolve all three before promising a customer a participation outcome. ### Choose a pilot that tests the difficult cases Include more than the easiest devices. A useful pilot covers representative equipment, an offline resource, an override and a recovery after interruption. Assign an owner to each exception and agree on the evidence needed to accept the integration. [aDERMS](/aderms/) focuses on organizing partner resources and fleet visibility within the Serious Controls Federated DERMS architecture. For the wider architecture, read [what DERMS does](/blog/derms/). When you are ready to scope a pilot, [bring your site and equipment list to our team](/contact/). ### Sources and further reading - [www.ferc.gov](https://www.ferc.gov/ferc-order-no-2222-explainer-facilitating-participation-electricity-markets-distributed-energy) - [www.energy.gov](https://www.energy.gov/edf/virtual-power-plants) ## What Is a Building Management System? A Practical Guide for Facility Teams Source: [What Is a Building Management System? A Practical Guide for Facility Teams](/blog/building-management/) Author: Serious Controls Published: 2026-09-20 Learn how a building management system connects HVAC schedules, equipment status and indoor conditions, with a practical first-month improvement plan. A building management system, or **BMS**, connects information and controls used to operate a facility. Depending on the installation, that can include HVAC schedules, zone temperatures, equipment status and alarms. Its value comes from helping the facility team make and verify operating decisions. If your building has separate thermostats, inconsistent schedules or several vendor dashboards, start by mapping how equipment is operated today. A successful improvement does not always begin with replacing every device. ### What does a BMS do? Building controls coordinate equipment and the conditions it serves. The [U.S. Department of Energy](https://www.energy.gov/cmei/buildings/about-building-controls) describes controls as an integrating layer for building systems, while identifying interoperability and commissioning as important challenges. For a facility team, useful questions are concrete: Is equipment running during the intended hours? Which zone needs attention? Has an override been left active? Can the operator see whether a change worked? **BMS** and **building automation system (BAS)** are often used for overlapping functions. Look past the label and ask which equipment, measurements and actions a proposed system actually supports. ### Monitoring and control are different capabilities A sensor can reveal a condition without being able to change it. Similarly, remote access to a thermostat does not automatically provide control over every part of an HVAC system. For each integration, list the information you can read and the settings you can write. Identify where the final operating sequence runs and who is responsible for maintaining it. This prevents an attractive dashboard from becoming a substitute for a complete operating design. ### Start with schedules and overrides Review normal opening hours, weekend operation, cleaning periods and holiday exceptions. Compare those intentions with actual equipment runtime. Ask the team to identify zones that routinely need manual adjustment. An illustrative example: a tenant changes its working hours, but the HVAC schedule stays unchanged. The first task is to establish the correct schedule and verify the resulting conditions. Buying additional sensors before checking that schedule may add data without resolving the underlying problem. When changing operation, retain the building's required safety limits and occupancy requirements. Record who approved the change, what was adjusted and how the result will be reviewed. ### Bring indoor conditions into the same conversation Temperature is only part of the operating picture. Where suitable sensors are installed, humidity and other indoor-air measurements can help the team understand conditions across zones. Readings need location, time and equipment context to be useful. [Serious-IAQ](/indoor-air-quality/) provides local displays and options for remote monitoring through a gateway. Review the selected model's sensor set and installation requirements. A single reading should prompt investigation in context rather than being treated as a complete assessment of a building. ### A practical first-month plan #### Week 1: establish the baseline Inventory the equipment, controls and available meters. Record operating hours, known issues and the people who handle them. Preserve existing settings before making changes. #### Week 2: resolve obvious inconsistencies Check time zones, clock settings, holiday schedules, device names and zone mapping. Review long-running overrides. Prioritize issues that the facility team can verify directly. #### Week 3: trial one bounded improvement Choose a zone or equipment group and define the intended result. For example, test a corrected operating schedule while tracking runtime and occupant feedback. Keep other changes limited so the result remains interpretable. #### Week 4: review and document Compare observations with the baseline. Account for differences in weather, occupancy and operating hours before attributing a change in energy use to the controls. Record what worked, what did not and the next action owner. This is a suggested project structure, not a guaranteed commissioning timeline. The [DOE guide to organizational energy management](https://www.energy.gov/cmei/buildings/manage-organizational-energy-use-commercial-building) provides additional context for maintaining an ongoing energy-management process. ### What should you ask a BMS provider? - Can the existing equipment be integrated, and what additional hardware is needed? - Which points are read-only, and which support control? - What remains operational during a loss of internet access? - How are changes, alarms and unresolved issues reviewed? - Who commissions the installation and trains the operating team? ### From building operation to distributed energy A facility with batteries, solar or flexible loads may also have an energy coordination requirement. Keep local building operation clear before connecting it to a wider program. Our [DERMS guide](/blog/derms/) explains that next layer. Explore [BMS & Automation](/bms/) and [Building Controls](/controls/), or [talk to Serious Controls](/contact/) about an improvement plan around the equipment you already have. ### Sources and further reading - [www.energy.gov](https://www.energy.gov/cmei/buildings/about-building-controls) - [www.energy.gov](https://www.energy.gov/cmei/buildings/manage-organizational-energy-use-commercial-building) ## What Is DERMS? From Distributed Resources to a Virtual Power Plant Source: [What Is DERMS? From Distributed Resources to a Virtual Power Plant](/blog/derms/) Author: Serious Controls Published: 2026-09-20 Updated: 2026-10-22 Learn what DERMS does, how it differs from a virtual power plant, and what to check before connecting solar, batteries and flexible loads. A battery can follow a local schedule. A solar installation can report production. A building can adjust its HVAC settings. The harder question is how these resources should work together across sites, owners and operating constraints. That is the problem a **distributed energy resource management system**, or **DERMS**, is designed to address. This guide explains the difference between a resource, the software coordinating it and the program it participates in. It also gives you a practical starting point for evaluating a project. ### What counts as a distributed energy resource? Distributed energy resources are equipment and flexible demand located across the electricity system, including near the places where energy is used. Solar, batteries, controllable loads and EV charging are common examples. The [U.S. Department of Energy's DER overview](https://www.energy.gov/topics/distributed-energy-resources) provides the broader grid context. Not every connected device is ready for coordinated control. A meter may only report consumption; a charger may expose status without accepting a charging limit. An integration review needs to distinguish what can be measured from what can actually be changed. ### DERMS and a virtual power plant: what is the difference? A **DERMS is a management system**. A **virtual power plant (VPP) is a coordinated collection of resources**. The Department of Energy describes VPPs as connected aggregations of distributed resources. A DERMS can support that coordination, but installing software does not by itself enroll equipment in an energy program. [DOE's VPP overview](https://www.energy.gov/edf/virtual-power-plants) explains the aggregation concept. Think of three layers: - **Equipment:** the battery, solar inverter, charger or building controller. - **Management:** the software and communications used to understand and coordinate equipment. - **Operating program:** the objectives, permissions and rules that determine when resources participate. The practical question is not just “Can I see every asset?” It is “Can I coordinate the available assets while respecting each site's requirements?” ### A practical coordination workflow Start by mapping each asset to its site, owner and connection. Then establish a reliable operating loop: 1. **Observe.** Read power, availability and relevant equipment states. Check timestamps so old data is not mistaken for the current condition. 2. **Establish limits.** Record constraints such as battery reserve, site export limits and the hours when a load may change. 3. **Plan.** Compare the operating objective with the resources expected to be available. 4. **Coordinate.** Send supported instructions through the agreed control path. 5. **Verify.** Compare the requested action with measured behavior, and review exceptions. For example, a battery may report that it is connected while its backup reserve prevents discharge. A useful operating view must make that distinction visible. Connectivity alone does not establish usable capacity. ### Match the system to the operating responsibility An enterprise energy team usually starts with its own sites. An aggregator needs to organize resources brought by multiple partners. A distribution operator needs network context. These views are related, but their responsibilities differ. Serious Controls brings these operating roles together through Federated DERMS, connecting [eDERMS](/ederms/), [aDERMS](/aderms/) and [DSO DERMS](/dso-derms/). [DERMS Orchestrator](/derms-manager/) provides an integration layer between DERMS environments. The applicable interfaces and functions are defined around the deployment. ### What to prepare before a DERMS project Bring an asset inventory, sample interval data and a short description of the outcome you want. For each equipment type, record the manufacturer, model, connection method, available measurements and supported controls. Identify who can authorize changes and who will respond if a connection is lost. A useful first milestone is a small pilot with clear acceptance criteria: reliable data, correct site mapping, verified control behavior and an agreed fallback. Expand after the team can explain what happened at every step. ### Common questions #### Do I need batteries to use DERMS? No single equipment type defines the entire project. The resources and control capabilities available at your sites determine the scope. Start with an inventory rather than assuming every site needs the same hardware. #### Does DERMS replace a building management system? A building management system addresses facility operation. DERMS addresses distributed resources and coordination across an energy portfolio or network. They can work together; see our [building management guide](/blog/building-management/). #### Where should we start? Choose one operating objective and a representative group of sites. [Explore Federated DERMS](/derms/) or [discuss your integration requirements](/contact/) with Serious Controls. ### Sources and further reading - [www.energy.gov](https://www.energy.gov/topics/distributed-energy-resources) - [www.energy.gov](https://www.energy.gov/edf/virtual-power-plants) ## Policies and contact Source: [Policies and contact](/contact/) - [Privacy Policy](/privacy/): Information handling and privacy terms. - [Terms and Conditions](/terms/): Service terms and operational SMS program conditions. - [Security](/security/): Responsible reporting and deployment security considerations. - [Contact Serious Controls](/contact/): Project scope, demonstrations, pricing and support.