Solar EPC Operations

    Solar O&M and AMC: turning monitoring alerts into tickets, visits and renewals

    Installed systems become a recurring-revenue book only if alerts become tickets, tickets become visits and contracts renew on time. A workflow from inverter alert to AMC renewal.

    GC
    GarunaCDX Editorial
    Editorial team
    Oct 19, 2026 4 min read
    Key takeaways
    • O&M is a loop: alert, ticket, dispatch, visit, report, renewal.
    • Attach every ticket to a site, a unit serial and an AMC contract so the technician arrives informed.
    • Compare expected generation to actual per site and set your own alert threshold from history.
    • AMC renewal dates are revenue dates. Alert 90, 60 and 30 days ahead.
    • Inverter makers typically provide a monitoring portal; whether an API or export is available varies. Check per brand.

    Quick answer

    Run O&M as a loop: monitoring detects a problem, the system raises a ticket against the right site and AMC contract, a technician is dispatched with the unit's serial and warranty history, the visit is logged with photos, and the customer gets a report. Track expected versus actual generation per site, set a threshold you choose from your own data, and put every AMC renewal date on an alert. Check each inverter brand's monitoring portal for API or export options.

    Why does O&M need its own workflow?

    Because once the system is commissioned, the sales team has moved on and the install team is on the next job. Faults surface as customer phone calls. Nobody can see the unit’s serial, warranty or last visit. AMC contracts expire silently. The installed base, which should be your steadiest revenue, is the least managed part of the business.

    What does the loop look like?

    The O&M loop

    site, serial, AMC statushistory attachedphotos, partsif unit defectdate alertMonitoring alertCustomer callTicket raisedTechnician dispatchedVisit loggedCustomer reportWarranty claimAMC renewal
    Our model. Each step writes to the same site record, so history builds up.

    What should a ticket hold?

    FieldWhy
    Site and customerWhere to go and who to tell
    Unit serial and warranty statusDecides who pays for parts
    AMC contract and entitlementCovered visit or chargeable
    Source: alert, call, scheduled visitTracks how issues are found
    Priority and target response timeSets expectations
    Technician and scheduled slotOwnership
    Visit notes, photos, parts usedEvidence and cost
    Closure date and customer sign-offEnds the clock

    Link the ticket to the unit record described in serial and warranty tracking, so a technician sees the unit’s history before leaving.

    How should monitoring data be used?

    Two simple signals carry most of the value:

    1. Device status and alerts. Inverter offline, grid fault, error codes. These become tickets automatically or after a short confirmation.
    2. Expected versus actual generation. From the design, you have an expected output for the site. Compare it to actual generation over a rolling period. A site persistently below expectation is a candidate for a visit, cleaning or inspection.

    Set the deviation threshold from your own data, not a borrowed number. Look at a few months of actual output per site, see what normal variation looks like, then choose a level that finds real faults without flooding the team.

    Integration reality. Most inverter manufacturers run a cloud monitoring portal. Some offer an API, some a scheduled export, some only alert emails. Availability and terms change, so check each brand’s current documentation before you commit to an integration. A fallback is parsing alert emails into tickets. We are not making brand-specific claims here.

    How do you protect AMC revenue?

    • Record each AMC with start and end dates, scope, visit frequency and fee.
    • Schedule preventive visits automatically from the contract.
    • Alert at 90, 60 and 30 days before expiry, and assign a renewal owner.
    • Send the customer a short performance and visit report. A renewal conversation is easier when the customer has seen value.

    What about batteries?

    As storage spreads (large battery tenders were reported awarded in September 2026, see the market piece), expect higher-value units, stricter handling and more detailed warranty terms. Capture serials and commissioning data the same way, and check the manufacturer’s service requirements.

    Where does this not apply?

    If you install and leave, with no AMC offer, you do not need an O&M workflow, though you still need warranty tracking. For a few dozen sites a sheet plus a monitoring portal can work. A system pays when volume is large enough that no one person remembers every site.

    What to do this week

    1. Count your installed sites and how many have an active AMC with a known end date.
    2. Pick five sites and compare expected versus actual generation for the last three months.
    3. List the monitoring portals you use and what each offers: API, export, alert email.

    Part of the guide Running a solar EPC business on connected systems.

    O&M check
    Tell us how many sites you maintain and how you hear about faults. We will sketch the ticket loop.
    Talk to us

    The O&M workflow is our own operating model. The battery tender reference is from Financial Express citing JMK Research (two tenders, 2,265 MW / 4,530 MWh, as reported). We have not verified any inverter manufacturer’s API and make no claims about specific brands.

    Your verdict
    Was this article useful?
    GC
    Written by
    GarunaCDX Editorial
    Editorial team

    Engineers, product and growth folks at GarunaCDX writing about the systems we build for clients.

    View all articles
    Share
    Planning something similar?

    Let's talk about your build.

    Tell us what you are building. A founding engineer replies within one working day with how we would approach it.

    FAQ

    Frequently asked questions

    Most inverter manufacturers run a cloud monitoring portal. Some offer an API, scheduled export or alert email. Check each brand's current documentation, then map alerts to tickets by site and serial number. Where no API exists, alert emails parsed into tickets are a fallback.

    Site, customer, unit serial, AMC contract status, fault description or alert code, priority, assigned technician, scheduled date, visit notes, photos, parts used and closure date.

    Start from your design estimate, compare to a few months of actual data per site, and set a deviation level that catches real faults without flooding the team. There is no universal number; calibrate to your own sites.

    An installed base with active AMC contracts produces recurring revenue and lets you catch faults before customers complain. It only works if renewals and service visits are tracked as carefully as new sales.

    The GarunaCDX build log

    Industry insights, once a month

    New case studies, healthcare, marketplace, B2B SaaS and industrial breakdowns, and the engineering notes behind what we ship. One short email a month, no fluff.

    We never share your data — see our Privacy Policy for details.