{% include '@Application/inc/central_header.html.twig' %}
{% include '@HoneybeeWeb/pages/inc/pp_style.html.twig' %}
{# WEB-2 §23 — /honeycore/bms. Focus on outcomes (HVAC/pumps/chillers/lighting/sensors/
energy/alarms/visibility/integration); the data-point mathematics lives LOWER DOWN.
ONE primary CTA (§28): Request BMS Assessment. #}
{% set p = prices %}
<div class="pp-wrap">
<div class="pp-hero">
<span class="kicker">HoneyCore BMS</span>
<h1>Building intelligence without enterprise software complexity.</h1>
<p class="sub">HVAC, pumps, chillers, lighting, sensors, energy and alarms in one view —
installed on industrial hardware you own, priced from €{{ p.bms.essential }}/month,
without the enterprise-BMS procurement saga.</p>
<a class="pp-cta" href="#request">Request BMS Assessment</a>
</div>
<div class="pp-sec">
<h2>What it takes over</h2>
<div class="pp-grid c3">
<div class="pp-card"><h3>Comfort systems</h3><ul>
<li>HVAC scheduling & setpoints</li><li>Chillers & pumps</li><li>Lighting control</li></ul></div>
<div class="pp-card"><h3>Watchkeeping</h3><ul>
<li>Sensors & environmental monitoring</li><li>Alarms with escalation</li><li>Equipment runtime & faults</li></ul></div>
<div class="pp-card"><h3>Energy & integration</h3><ul>
<li>Building energy metering</li><li>Open protocols — no vendor lock-in</li><li>Feeds HoneyCore EMS & HoneyBee ERP</li></ul></div>
</div>
</div>
<div class="pp-sec">
<h2>Why facility teams pick it</h2>
<div class="pp-grid c3">
<div class="pp-card"><h3>Visibility first</h3><p>Every floor, plant room and panel in
one live view — before automation, you finally see the building.</p></div>
<div class="pp-card"><h3>Your hardware, your data</h3><p>Runs on HoneyCore 4.0 on site.
No cloud dependency for control, no data hostage situation.</p></div>
<div class="pp-card"><h3>Grows point by point</h3><p>Start with one plant room. Add
floors and systems as points — the price follows the points, not a licence tier
negotiation.</p></div>
</div>
</div>
<div class="pp-sec">
<h2>Pricing — per month, by billable data points</h2>
<div class="pp-grid c4">
<div class="pp-card"><span class="pp-chip">Essential</span>
<div class="pp-price">€{{ p.bms.essential }}</div>
<p style="margin-top:6px;">Up to {{ p.bms.points.essential }} points</p></div>
<div class="pp-card"><span class="pp-chip">Advanced</span>
<div class="pp-price">€{{ p.bms.advanced }}</div>
<p style="margin-top:6px;">Up to {{ p.bms.points.advanced|number_format(0, '.', ',') }} points</p></div>
<div class="pp-card"><span class="pp-chip">Professional</span>
<div class="pp-price">€{{ p.bms.professional }}</div>
<p style="margin-top:6px;">Up to {{ p.bms.points.professional|number_format(0, '.', ',') }} points</p></div>
<div class="pp-card"><span class="pp-chip">Enterprise</span>
<div class="pp-price">from €{{ p.bms.enterprise_from }}</div>
<p style="margin-top:6px;">Up to {{ p.bms.points.enterprise|number_format(0, '.', ',') }} points & beyond</p></div>
</div>
<p class="pp-note">A billable point is a monitored or controlled I/O value — a temperature,
a valve position, a runtime counter. Hardware, engineering and commissioning quoted per building.</p>
</div>
<div class="pp-band" id="request">
<h2>Get a BMS assessment for your building.</h2>
<p>Building type, systems on site, rough point count — we map the tier and the effort.</p>
</div>
{% include '@HoneybeeWeb/pages/inc/intent_form.html.twig' with {
'intent': 'bms', 'cta': 'Request BMS Assessment',
'extras': [
{'name': 'project_type', 'label': 'Building type', 'options': ['Office', 'Factory', 'Retail / mall', 'Hospital / campus', 'Warehouse', 'Other']},
{'name': 'capacity', 'label': 'Approx. data points (if known)'},
{'name': 'stage', 'label': 'Stage', 'options': ['Exploring', 'Replacing an old BMS', 'New building', 'Ready to deploy']}
]
} only %}
</div>
{% include '@HoneybeeWeb/footer/central_footer.html.twig' %}