Skip to main content
GullySystem
Other industries

Business solutions for Solar inverter manufacturers

Explore software for work such as “Datasheet packs written for engineers”. Review each business function below, including when it fits and what to check before implementation.

Solar inverter manufacturers

How the business operates.

An inverter is a small power plant in a box, sealed against dust and heavy rain and expected to run unattended on a roof for years. Electrolytic capacitors, IGBT modules, Hall-effect current sensors and the DSP board arrive from different suppliers in different lots. Parts change when a supplier revises a datasheet. A unit trips in the field after a year. Which parts did it contain?

Board and component lot receiving

Log IGBT modules, DC-link capacitors, PCBs and enclosures by lot, with supplier and storage bin, so each serial can name its parts.

Kits and work orders

Issue a kit per work order against the inverter’s bill of materials, and keep the board assembler’s deliveries visible beside it.

Firmware and configuration record

Store firmware image, grid-code parameter file and flashing operator against each serial.

Burn-in and final test results

Save chamber hours, ground-fault trips, output readings and MPPT efficiency points per unit, with the test rack and date.

Repair and return bench

Log a returned unit with its fault code, replaced boards and retest result, and link it back to the original serial.

Warranty and installation records

Hold dispatch, installation and commissioning dates per serial, with the terms agreed in the distributor contract.

Supplier lot complaints and returns

Faulty capacitor, MOSFET or board lots are logged with the supplier, lot number and the units affected. Credit notes are tracked. The purchase manager uses it when the next order is negotiated.

Test jig and equipment calibration

Burn-in chambers, load banks and power analysers carry a calibration date and the last check made. Overdue equipment is flagged. The test engineer avoids readings from an uncalibrated instrument.

Firmware release approval log

Every firmware version records what changed, who tested it and when it was cleared for production. Old versions stay listed. The engineering head decides which image the line may flash.

Field fault and service history

Repairs on a returned inverter are listed by fault, part replaced and technician. Repeat failures stand out. The service lead sends patterns back to design and purchase teams.

The records that hold the operation together.

  • Inverter model master and bills of materials. Record every model’s rating, control and gate driver boards, IGBT modules, heatsink, enclosure and nameplate labels. Earlier revisions are kept whenever the list is altered.
  • Component and board lot receiving. Log lots of power modules, DC link capacitors and populated boards, including deliveries from an outside board assembler, with supplier and stores bin.
  • Kits and work orders. Release a work order for a quantity of units and issue a kit to match. Any shortfall of boards or enclosures is shown to stores before the kit is picked.
  • Assembly station tracking. Record operator, station and torque wrench check against each serial as it passes through IGBT mounting and busbar wiring.
  • Firmware and parameter control. Store the approved firmware images and parameter sets, such as grid code and country settings, and log which version each unit received and when.
  • Burn-in rack records. Link each burn-in rack slot to a serial and save hours at load, heatsink temperatures and protection trips. A failure shows both the unit and the slot.
  • Final test limits and results. Set output, efficiency, insulation, protection trip and RS485 limits per model, store readings per serial and hold failing units for the repair bench.
  • Repair and return bench. Log a returned inverter with its fault code, the fans or fuses swapped and the retest result, and link all visits to the same serial.

Operational bottlenecks to check

Firmware images drift across a pallet

Units on one pallet carry different builds because the flashing station was updated mid-shift. Nobody can say which unit holds which. Support guesses from the label.

Component lots are not captured

Film capacitors and gate-driver chips come off open reels and trays. When a field failure points to one part, the affected serials cannot be listed.

Burn-in logs sit on a rack PC

Chamber hours, thermal trips and heatsink temperatures stay on a test rack computer. They never reach the order, so a distributor asking for proof starts a hunt.

Repair benches work from paper fault slips

A returned unit is opened, a driver board is swapped, and the slip stays in the tray. The same short circuit returns as a fresh complaint. Cost repeats.

Warranty start dates are guessed

Dispatch, installation and commissioning dates all differ, and the start depends on which one the contract names. Claims are argued from invoices instead of records.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Order and work order

    A buyer’s order names the model, kilowatt rating, phase and quantity. The planner issues a work order, which pulls a kit against the bill of materials.

  2. 2. Receiving and kitting

    Control boards, IGBT modules, DC link capacitors, inductors and enclosures are received by lot. Stores issue a kit and record which lots went to which work order.

  3. 3. Assembly

    Operators bolt the IGBT stack to the heatsink with thermal paste, wire the unit and torque the busbar terminals. Operator and station are recorded against the serial.

  4. 4. Flashing and burn-in

    The firmware image and grid-code parameter set are flashed and logged. The unit then runs at rated load in the rack, and hours and heatsink temperatures are saved.

  5. 5. Test and labelling

    Output voltage, efficiency points, residual current trips, insulation resistance and RS485 communication are checked against model limits. Passing units get the rating label with its serial.

  6. 6. Dispatch and warranty

    Scanning a carton at the dock checks it against the sales order, and the buyer receives the inverter serials packed inside. A warranty record opens with the dispatch and commissioning dates.

Roles and responsibility boundaries.

For the plant manager

Read units through burn-in, the final test pass rate by model, returns open and orders due, all from one screen.

For assembly supervisors

Release work orders, assign stations and see shortages of control boards, IGBT modules or enclosures before a line stops.

For test and firmware engineers

Maintain firmware images and test limits, and review burn-in and final test results by serial. A change to a limit carries its date.

For service engineers

Open a returned unit’s build history, log the fan or fuse replaced and book the retest. Repeat faults on one serial stand out.

For purchase and stores

Receive boards and capacitors by lot, kit work orders and reorder spares against minimum levels.

Reports your managers need.

  • Units by model through burn-in and final test
  • Firmware version installed, by serial and date
  • Failure codes by model and component lot
  • Returns and repairs by serial and visit count
  • Warranty claims against dispatch and commissioning dates
  • Spares used against reorder levels
  • Board assembler deliveries against work orders

Connections to scope

  • Email
  • SMS
  • WhatsApp or other messaging
  • Test rack file import
  • Label printer
  • Accounting export

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Models and bills of materials

Each inverter model with its boards, IGBT modules, heatsink and enclosure is entered in the form you build it, one revision at a time.

Parameter files and versions

Approved builds are stored, and the flashing step is set to record the image it loads along with the grid-code parameter file.

Test limits per model

Output tolerances, efficiency points and protection trips follow limits your test engineers supply, and are confirmed on a sample unit.

Open orders and stock migrated

Current orders, board and capacitor stock and earlier test sheets are entered, then sampled by your team before the first build.

Currency and tax

Quotations and invoices follow your currency and tax rules, set up and reviewed during implementation.

Limitations to settle before implementation

  • Component makers who only produce power modules or capacitors for others will need a different product.
  • Firms that only sell and commission inverters will find Solar Installation Management Software closer.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Datasheet packs written for engineers
  • Dealer and distributor recruitment
  • Installer training and certification days
  • Warranty and service claim tracking
  • Monitoring app demonstrations
  • EPC vendor registration
  • Dealer margin and stock communication
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements