Build a system around your projects, your I/O lists and your commissioning records.
An automation company sells projects more than products. A line is wired, programmed, tested at the works and then commissioned at a customer’s site, often by people who did not build it.
The records for that work are scattered. Electrical drawings sit with design. Program files sit on engineers’ laptops. Punch lists from site arrive as photographs in a chat group.
Software built by GullySystem for this kind of company would keep one record per project. The scope, the bill, the program version, the test results and the site visits would all hang off it.
Companies this can be built for.
A panel builder works from someone else’s drawing. An integrator owns the design, the code and the site. The software needs differ, and the build follows who owns what.
- PLC panel builders
- Industrial automation companies
- Robotic systems integrators
- Machine vision companies
- SCADA (supervisory control) system integrators
- Automation equipment manufacturers
- Industrial sensor suppliers
- Special purpose machine builders
- Conveyor and material handling integrators
- Motion control and drive suppliers
- Test and measurement system builders
- Process instrumentation contractors
- Building automation contractors
- Automation service providers
The modules, and what each one covers.
Nothing here is a fixed package. Each module is built, left out or changed to match how your organisation already works.
Enquiry, scope and proposal
Sales engineers turn a customer’s process description into a scope that can be priced.
- Enquiry with process description
- Scope of supply and exclusions
- Assumptions listed in the proposal
- Site survey notes
- Option pricing
- Proposal revision history
- Customer clarifications
- Lost enquiries with the reason
Project costing and bill of material
- Engineering hours by discipline
- Panel and field hardware bill
- Brand and model by customer standard
- Software licences included
- Site and commissioning days
- Contingency noted separately
- Cost against quote during the project
- Variation orders priced and approved
Hardware prices and lead times move quickly. The system stores the quote date next to each rate so a stale price is visible.
I/O list and instrument index
The input and output list is the document every discipline works from.
- Tag number and description
- Signal type and range
- Panel, rack and channel address
- Field device and location
- Cable and termination reference
- Alarm and interlock linked
- Revision and change log
- I/O count against the quote
Electrical drawings and revisions
- Schematic and layout drawings
- Cable schedule
- Revision number and date
- Customer approval of drawings
- Red-line markups from the shop
- As-built set after commissioning
- Drawings released to the shop
- Superseded versions withdrawn
Program and configuration versions
Controller (PLC) code, operator screens (HMI) and robot programs change often during commissioning. Every version is named by who changed it and when.
- PLC program file and version
- HMI and SCADA project files
- Robot program and calibration data
- Vision recipe and lighting settings
- Drive parameters
- Change note with reason
- Version loaded at site
- Backup taken before changes
The software stores the files and the history around them. It does not replace the engineering tools used to write or run the code.
Purchase and long-lead items
- Requirement raised from the bill
- Controllers, drives and sensors
- Robot and vision hardware
- Delivery date promised
- Goods receipt and inspection
- Supplier follow-up
- Items held for a specific project
- Alternate parts approved by the customer
Panel build and wiring
Panel shop teams build from the released drawing and tick off each stage.
- Enclosure preparation
- Mounting plate layout
- Component mounting
- Power wiring
- Control wiring
- Labelling
- Continuity check
- Power-on test
- Work order per panel
- Technician and hours
- Wire and ferrule consumption
- Rework recorded
- Photographs before closing the door
Factory acceptance test
The customer often witnesses a test before the system leaves the works.
- Test procedure by project
- I/O check results
- Interlock and alarm checks
- Simulated process runs
- Deviations recorded
- Customer witness and sign-off
- Open points carried to site
- Report generated from the results
Site installation and commissioning
- Site team and travel plan
- Installation progress by area
- Loop checks at site
- Site acceptance test results
- Punch list with photographs
- Items closed and by whom
- Customer signature on handover
- Commissioning days booked against plan
Project schedule and milestones
- Milestones by project
- Engineering, build and site phases
- Dependencies on customer decisions
- Delay with the cause noted
- Billing milestones linked
- Engineer allocation across projects
- Projects at risk this month
Billing and retention
- Milestone invoices
- Advance and balance
- Retention held by the customer
- Variation invoices
- Tax invoice in the customer’s currency
- Payment follow-up
- Bank guarantee tracking
- Project margin at closing
Service, spares and support contracts
Service teams support installed systems long after the project closes.
- Installed base by customer and site
- Equipment and software versions installed
- Support contract terms
- Fault ticket with severity
- Remote support session notes
- Site visit report
- Spares recommended at handover
- Obsolete part notices
Product makers and sensor suppliers
For companies that sell their own devices as well as projects.
- Device bill of material
- Firmware version per unit
- Serial number and calibration record
- Test fixture results
- Distributor orders
- Returns and repair
- Warranty by serial
- Datasheet and manual versions
Who logs in, and what they see
- Owner
- Sales engineers
- Project managers
- Design engineers
- Software engineers
- Panel shop supervisor
- Site engineers
- Service team
- Purchase team
- Customer project contact
One connected workflow, end to end.
Every stage below can sit in one system, so nobody re-enters what the last stage already captured.
- Enquiry
- Proposal
- Order
- Design and I/O list
- Purchase
- Panel build
- Programming
- Factory acceptance test
- Dispatch
- Site commissioning
- Handover
- Support
You do not have to replace everything at once.
Each phase is usable on its own, so the system earns its place before the next part is built.
- 1
Projects and bills
Enquiries, scope, project costing, hardware bills and I/O lists, so each order starts from a record the whole team reads.
- 2
Panel shop and purchasing
Long-lead purchase, panel work orders, wiring stages and stores, with each panel tied to its released drawing.
- 3
Tests, versions and site
Program versions, factory and site acceptance records, punch lists and commissioning plans for field engineers.
- 4
Billing and support
Milestone invoices, retention, installed base, support contracts, fault tickets and spares.
How a build actually runs.
- 01
Follow a finished project
We take one closed project and rebuild its history from drawings, emails, program files and site photographs. The gaps show what to capture.
- 02
Agree who owns each record
Design owns the I/O list. Software owns program versions. The site lead owns the punch list. The build respects that split.
- 03
Design for the site engineer
Site screens work on a phone with a poor signal, and a punch item can be closed with one photograph.
- 04
Build the project record first
Scope, bill, I/O list and drawing control come first, since every later stage reads from them.
- 05
Run one live project
A project in progress moves onto the system at its next stage, and the team compares it against the old trackers each Friday.
- 06
Add service
Installed base, tickets and contracts follow when the project side is steady.
What you bring, and when.
The build moves at the speed of the answers. These are the things we ask for, in the order we ask.
- 01
Past proposals, BOMs and I/O lists
Send some completed project folders: costing sheets, I/O lists, drawing revisions and test reports. How you name program backups matters. The design mirrors a project folder.
- 02
Project engineer, panel shop lead and buyer
Each handles an area and checks every demonstration. Design and purchase needs can diverge. The technical head decides.
- 03
Margin rules, vendor lists and test formats
Margin rules, preferred vendors, long-lead items and test sheet formats are decided as the build goes on. Standard component masters help. Every module is reviewed when it is shown.
- 04
Open projects and program archives
Running projects, open purchase orders and program version history come across at go-live. Access to your existing drives must be arranged. The managing director accepts the cutover.
Systems we can put together for you.
- Automation project management
- Panel builder production tracking
- I/O list and tag management
- Program and configuration version control
- Factory and site acceptance test records
- Site punch list apps
- Robot cell project tracking
- Machine vision recipe records
- Installed base and service ticket systems
- Support contract management
- Project costing and variation tracking
- Serial number and firmware records
- Customer project portals
- Management dashboards
Questions owners ask before starting.
What does custom software for an automation company change?
It keeps the scope, the I/O list, the program version and the test results on one project record. Site engineers stop working from old emails.
Can it store PLC and robot program files?
Yes, as versioned files with a change note and an owner. It stores and tracks them. Your engineers still edit them in their own tools.
Can an I/O list be imported from a spreadsheet?
Usually. We load your current format at the start, then maintain the list inside the project.
Does it support factory and site acceptance tests?
Yes. Procedures, results, deviations and customer sign-off are recorded for each test, and open points travel with the project to site.
Can site engineers use it without a stable connection?
Entries can be saved on the device and sent when a connection returns. We confirm this for your sites during design.
Can it track the installed base?
Yes. Each customer site lists the equipment and software versions installed, which helps when an obsolete part notice arrives.
Does it connect to running machines?
Not by default. Live machine data is a separate build and depends on the controllers and networks involved.
Can product makers use it too?
Yes. Serial numbers, firmware versions, test fixture results and warranty are held per device.
Would a ready product be enough?
For panel builders, often. Our panel builder and integrator software covers common records, and custom work suits firms with unusual project flows.
How we work with this trade.
Ready products for this work.
If one of these fits, it is cheaper and faster than building from scratch. We will say so.
Build a system that remembers the project after the engineers leave the site.
Automation work is handed over many times: sales to design, design to the shop, the shop to site, and site to service. Every handover loses something if it is not recorded.
Bring us one project file and its punch list. We will show which of those records could live in one system, and which of them our ready products already hold.
Tell us how your industrial automation and robotics companies runs today.
We will tell you what can be digitised, what can be connected, what is worth automating, and what you should leave alone.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements