{# NEW-WEBSITE-VIEW: approved September preview, public presentation only. #}{% set website_title = 'Follow the work. Find the handovers. | HoneyBee' %}{% set p = prices|default({}) %}{% include '@HoneybeeWeb/website/header.html.twig' %}<section class="hero"><div class="wrap"><span class="eyebrow ">An illustrated workflow</span><h1>Follow the work.<br>Find the handovers.</h1><p class="lead">Explore how a project can move from engineering to delivery and site operations. Select a phase to see its role.</p><p class="note"><span class="chip amber">Conceptual demonstration</span> This is not a product screenshot, production test or customer case study.</p><div class="walkthrough"><nav class="walknav" aria-label="Workflow phases"><button data-step="0" aria-pressed="true">01 · Plan & engineer</button><button data-step="1" aria-pressed="false">02 · Deliver</button><button data-step="2" aria-pressed="false">03 · Commission</button><button data-step="3" aria-pressed="false">04 · Operate & maintain</button></nav><div class="walkcontent" id="walkcontent" aria-live="polite"><div data-workflow-panel="0"><span class="eyebrow ">01 / PLAN & ENGINEER</span><h3>Begin with a reviewed scope.</h3><p>A proposed energy project starts with design inputs and a defined engineering scope.</p><ul><li>Record site assumptions and constraints.</li><li>Review the layout, electrical scope and applicable storage needs.</li><li>Prepare engineering output for the next team.</li></ul><a class="textlink" href="{{ path('honeybee_honeywatt') }}">Explore HoneyWatt ↗</a></div><div data-workflow-panel="1"><span class="eyebrow ">02 / DELIVER</span><h3>Make procurement part of the project.</h3><p>Business workflows carry the commercial and delivery responsibilities.</p><ul><li>Review the proposal and approval requirements.</li><li>Work through purchasing, receiving and project records.</li><li>Keep import and delivery documentation in context where applicable.</li></ul><a class="textlink" href="{{ path('honeybee_business_suite') }}">Explore Business Suite ↗</a></div><div data-workflow-panel="2"><span class="eyebrow ">03 / COMMISSION</span><h3>Agree what the site handover proves.</h3><p>A commissioned deployment needs clear interfaces and acceptance criteria.</p><ul><li>Confirm equipment and point lists.</li><li>Verify supported integration behavior.</li><li>Record installation and acceptance responsibilities.</li></ul><a class="textlink" href="{{ path('honeybee_implementation') }}">Explore Implementation ↗</a></div><div data-workflow-panel="3"><span class="eyebrow ">04 / OPERATE & MAINTAIN</span><h3>Keep the operating context useful.</h3><p>Operational information and service records serve different roles. Define their relationship for the deployment.</p><ul><li>Review the information that is actually available.</li><li>Confirm how observations become reviewed service work.</li><li>Keep integration and bridge maturity explicit.</li></ul><a class="textlink" href="{{ path('honeybee_website_page', {'page':'energy-operations'}) }}">Explore Energy Operations ↗</a></div></div></div></div></section><section class="section white"><div class="wrap"><div class="split"><div><span class="eyebrow ">Evidence matters</span><h2>Review the real workflow<br>before choosing the scope.</h2><p>Ask for a walkthrough of the deployed product using appropriate demonstration data. Confirm the interfaces and handovers that are implemented for your configuration.</p></div><div class="proof-plate"><h3>What a useful review includes</h3><div class="featurelist"><div class="featureline"><b>01</b><div><h4>Authentic screens</h4><p>Current product behavior, with customer information protected.</p></div></div><div class="featureline"><b>02</b><div><h4>Clear boundaries</h4><p>Available functions separated from pilot or development work.</p></div></div><div class="featureline"><b>03</b><div><h4>A recorded scope</h4><p>Agreed requirements and acceptance criteria for your rollout.</p></div></div></div></div></div></div></section><section class="cta"><div class="wrap"><div><h2>Bring your own workflow to the discussion.</h2><p>Use a real requirement to test the fit.</p></div><a class="btn dark" href="{{ path('honeybee_contact') }}">Discuss your operation <span aria-hidden="true">↗</span></a></div></section>{% include '@HoneybeeWeb/website/footer.html.twig' %}