One system for components, boards, firmware loads, burn-in and repair history by serial.
Every avionics unit carries its own serial chain. Reel date codes, approved manufacturers, modification status, reflow profiles, X-ray and automated optical inspection findings, flashed firmware images and burn-in soak results sit against the unit, with every repair after it. Purchasing sees allocation risk on a long-lead connector before the kit comes up short, and quality can open any shipped serial. Nothing is rebuilt from memory.
- Bills of materials, build standards and approved source lists entered the way engineering holds them
- Open builds, serial history and stock migrated
- Changes to test forms and routings handled by GullySystem staff when asked
Avionics hardware manufacturers use this software to record how each unit was built. Capacitor date codes and approved sources, reflow profiles and AOI results, flashed firmware checksums and burn-in soak readings all attach to the serial. A repaired line replaceable unit returns to its current modification status. The whole chain opens from one number.
What goes wrong before the software.
How the work flows through it, step by step.
- 1
Order and build standard
A customer order is logged against unit part number, modification status and delivery date. Contract review notes stay with it.
- 2
Purchasing and goods inward
Parts are ordered from approved sources. At receipt the date code, lot, country of origin and packaging are recorded, and moisture-sensitive items are labelled before they reach the shelf.
- 3
Kitting
A kit is issued for the board lot at the current bill of materials. Reel numbers and the date codes used are written to the kit.
- 4
Board assembly
Paste is printed, parts placed and boards reflowed, then AOI or X-ray checks follow, with solder profile and result stored per lot. Through-hole parts, harness looms and conformal coating come next.
- 5
Firmware, burn-in and test
The unit is flashed with its firmware, soaked through the set burn-in cycle and put to acceptance test. Readings are logged. A failure holds the serial.
- 6
Dispatch and repair
Passed units ship with a certificate of conformance. A return reopens the serial, and the repair and any modification join its chain.
What is inside.
Every module can be switched on, left out or changed to match how your team already works.
The business modules it is built from.
Each one is also available on its own, or inside a system built for you.
- Bill of Materials
The bill of materials is held per build standard, and a dated alternate leaves earlier builds with their original part on record.
- Vendor Management
Approved manufacturers and distributors are listed against each part, and a purchase from a source outside the list is flagged to the buyer.
- Goods Receipt (GRN)
Date code, lot, quantity and packaging are noted at receipt, and a reel that fails inspection is held apart from usable stock.
- Batch and Serial Tracking
Kits record the reels used, so a unit serial leads back to the date code and lot of each component on its boards.
- Quality Control
Firmware version, burn-in duration and acceptance readings are logged per serial, and a unit that fails stays on hold.
- Production Planning
Orders are released at the correct build standard, and parts on allocation show which planned builds will be held.
- Service Reports and Proof of Visit
A returned unit receives a repair report with fault, part replaced and modification applied, filed against the same serial.
- Audit Trail
Each release, alternate approval and certificate carries a user and time, so the build chain of any shipped unit can be reviewed.
How we would put it in.
Setup, data migration, integrations and anything built on top.
One system, each person sees their part.
For engineering leads
Release build standards, approve alternates and read the full chain of any serial, from reel to repair.
For purchasing staff
Order from the approved list and see which allocated parts will hold up a board lot.
For line supervisors
Check kits, bag exposure and board lot progress before the placement line starts its changeover.
For test technicians
Flash firmware, run the burn-in chamber and enter acceptance readings against the unit serial.
For quality staff
Review nonconformance reports, repair records and certificates before a batch leaves the dock.
The numbers the owner asks for.
- Date codes and lots used in each unit serial
- Parts on allocation and the builds they affect
- Moisture-sensitive packages past floor life
- Firmware version loaded against build standard
- Burn-in and acceptance failures by fault and part
- Repairs by modification applied
Who this is built for.
- Makers of line replaceable units for aircraft avionics bays
- Builders of cockpit displays, radios and sensor boxes
- Contract assemblers of circuit cards for aerospace customers
- Harness and box build shops that serialise every unit
- Repair stations that return avionics to a current build standard
When it is not the right choice.
- A shop that builds general consumer electronics without serial chains or burn-in will find Electronic Product Manufacturer Management Software closer.
- A drone maker should look at Drone Component Manufacturer Management Software.
Adapted to your business before it goes live.
You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.
Works alongside
- Test equipment data import
- Firmware repository link
- Barcode and label printers
- Accounting export
Questions owners ask before a demo.
Can I see which date codes are inside a particular unit?
Yes. Kitting records the reels drawn, so a serial opens the date code and lot of each component on its boards, back to the goods inward entry.
How does the system handle approved alternates?
An alternate is added to the bill of materials with a date and a reason. Builds before that date keep the original part, and builds after it use the approved alternate.
Is a warning given for moisture-sensitive parts?
Yes. It logs when a dry bag is opened and compares the elapsed hours with the floor life of the package. A kit past the limit is flagged before it reaches the feeders.
Are firmware versions stored?
Yes. Image name, version and checksum are recorded when the unit is flashed. The acceptance test record then shows which version the unit carried when it passed.
How are repairs recorded?
A returned unit reopens its serial. The fault, the part replaced and any modification are added, and the unit must reach the current standard before retest.
Can we separate parts on allocation?
Yes. Parts marked as on allocation show which open builds depend on them and how long the shortage may last.
Will it certify us for airworthiness?
No. It stores the records. Airworthiness approvals and certification rules stay with your own engineering and quality staff, who answer to the authority.
Is test equipment connected?
Yes, through export files. Readings can be imported from CSV logs of a chamber or bench meter, and the instruments supported are agreed in the quotation.
What does it cost?
The number of users, lines and test stations decides the cost. First comes a demonstration on one of your units, and the written proposal arrives after it.
Can we take the serial histories with us later?
Yes. Build chains, test records and repair history can be exported by serial or part number, in a format fixed in the quotation.
Wondering what it would cost? Share your requirements and an engineer will come back with a scope.
Businesses that use this.
See Avionics Hardware Manufacturer Management Software with your own data.
Tell us how you run things today. We’ll show you the parts that matter to you and say plainly what would need changing.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements