{% include '@Application/inc/central_header.html.twig' %}{% include '@HoneybeeWeb/inc/_web_design_system.html.twig' %}{# ─── SOLUTION LANDING — ERP for O&M Companies ─── #}{% include '@Application/framework/_web_solutions_css.html.twig' %}<section class="sl-hero"> <div class="n-wrap"> <div class="sl-hero-inner"> <span class="n-label">Project ERP · O&M</span> <h1 class="n-hero-h1">ERP for <em>O&M</em> Companies</h1> <p class="n-hero-desc" style="max-width:640px"> Run operations and maintenance contracts on one platform — service contracts, ticketing, spares inventory, field crews, SLA tracking, and recurring billing — with HoneyCore EMS streaming live asset data into your workflow. </p> <div class="n-hero-actions"> <a href="{{ url('honeybee_contact') }}" class="n-btn n-btn-primary">Request Workflow Audit <i class="fa-solid fa-arrow-right"></i></a> <a href="{{ url('honeybee_pricing') }}" class="n-btn n-btn-outline">Explore pricing</a> </div> </div> </div></section><section class="n-sec sl-problem"> <div class="n-wrap-sm"> <span class="n-label">The problem</span> <h2 class="n-h2">O&M contracts <em class="n-em">erode</em> without live data.</h2> <ul> <li><i class="fa-solid fa-triangle-exclamation"></i><span>Tickets, site visits, and maintenance schedules live in spreadsheets and messages.</span></li> <li><i class="fa-solid fa-triangle-exclamation"></i><span>Spares consumption is never tied to the asset or the contract that should bear the cost.</span></li> <li><i class="fa-solid fa-triangle-exclamation"></i><span>SLA breaches and downtime go unnoticed until the client complains.</span></li> <li><i class="fa-solid fa-triangle-exclamation"></i><span>Recurring billing is manual, so revenue leaks and renewals slip.</span></li> </ul> </div></section><section class="n-sec sl-solution" style="padding-top:0"> <div class="n-wrap-sm"> <span class="n-label">The HoneyBee solution</span> <h2 class="n-h2">Contracts, crews, and assets in <em class="n-em">one loop.</em></h2> <p class="n-body n-mt-6"> HoneyBee ties service contracts, preventive and corrective tickets, spares inventory, field crews, and recurring billing to each asset and client. HoneyCore EMS connects the plant — inverters, meters, batteries, generators, and sensors — so condition and downtime data drive maintenance, SLA reporting, and monitoring revenue automatically. </p> <ul> <li><i class="fa-solid fa-circle-check"></i><span>Service contracts, tickets, and PM schedules per asset and client.</span></li> <li><i class="fa-solid fa-circle-check"></i><span>Spares inventory and field crews tied to the right contract cost.</span></li> <li><i class="fa-solid fa-circle-check"></i><span>HoneyCore EMS streams condition, generation, and downtime data.</span></li> <li><i class="fa-solid fa-circle-check"></i><span>Recurring monitoring and AMC billing with renewal tracking.</span></li> </ul> </div></section><section class="n-sec" style="padding-top:0"> <div class="n-wrap"> <div class="n-center"> <span class="n-label">Workflow example</span> <h2 class="n-h2">An O&M contract, <em class="n-em">end to end.</em></h2> </div> <div class="sl-flow"> {% set _steps = ['Service Contract', 'Asset Onboarding', 'HoneyCore EMS Monitoring', 'Ticket / PM Schedule', 'Field Crew Dispatch', 'Spares Issue', 'SLA Reporting', 'Recurring Billing', 'Renewal'] %} {% for step in _steps %} <span class="sl-flow-step"><span class="sl-num">{{ loop.index }}</span>{{ step }}</span> {% if not loop.last %}<span class="sl-flow-arrow"><i class="fa-solid fa-arrow-right"></i></span>{% endif %} {% endfor %} </div> </div></section><section class="n-sec" style="padding-top:0"> <div class="n-wrap-sm"> <span class="n-label">FAQ</span> <h2 class="n-h2">Questions from <em class="n-em">O&M</em> teams.</h2> <div class="sl-faq"> <div class="sl-faq-item"><h3>Can it connect to live plant data?</h3><p>Yes. HoneyCore EMS connects inverters, meters, batteries, generators, and sensors, so condition and downtime drive tickets, SLA reporting, and billing.</p></div> <div class="sl-faq-item"><h3>Does it track spares against contracts?</h3><p>Spares inventory and field crew time are tied to the asset and contract, so each O&M agreement carries its true cost and margin.</p></div> <div class="sl-faq-item"><h3>Can it handle recurring AMC billing?</h3><p>Recurring monitoring and AMC invoices are generated on schedule, with renewal tracking so contracts don't lapse silently.</p></div> </div> </div></section><section class="n-sec" style="padding-top:0"> <div class="n-wrap-sm n-center"> <h2 class="n-h2">See the loop on <em class="n-em">your</em> O&M contracts.</h2> <p class="n-body n-mt-6" style="max-width:54ch;margin:0 auto">We map your contracts, ticketing, spares, and billing flow — then show HoneyBee plus HoneyCore EMS running on it. EUR pricing, EU data residency.</p> <div class="sl-explore" style="justify-content:center"><a href="{{ url('honeybee_contact') }}" class="n-btn n-btn-primary">Request Workflow Audit <i class="fa-solid fa-arrow-right"></i></a></div> </div></section><section class="n-sec" style="padding-top:0"> <div class="n-wrap-sm n-center"> <span class="n-label">Explore more</span> <div class="sl-explore" style="justify-content:center"> <a href="{{ url('honeybee_product') }}" class="n-btn n-btn-outline">Platform</a> <a href="{{ url('honeybee_pricing') }}" class="n-btn n-btn-outline">Pricing</a> <a href="{{ url('honeybee_contact') }}" class="n-btn n-btn-outline">Contact</a> </div> </div></section>{% include '@HoneybeeWeb/footer/central_footer.html.twig' %}