Skip to main content
GullySystem
Manufacturing · SCADA System Integrator Management Software

One system for tag lists, screen design, point tests, licences and site support.

Run SCADA enquiries, point count quotations, I/O lists, mimic and alarm design, server orders, loop checks, acceptance tests, licence keys and support calls from one site record. Each site keeps its tag baseline, redundant server list, dongle serials and latest backup, from the first quote to years of remote support. Engineers, project managers and support staff open the same file.

  • Rates per analogue, digital and Modbus point, hardware lists and project types keyed the way your estimators price a job
  • Site lists, licence keys, dongle serials and open projects brought in
  • Loop check sheets and call categories adjusted by GullySystem staff on request

A SCADA integrator keeps quotes, I/O lists, mimic design, loop checks, server orders and support calls in one GullySystem site record. That record holds the tag baseline with every revision, loop check results by tag, the server and dongle register, backup dates and call history. Engineers begin each visit and remote call already informed.

Where it breaks today

What goes wrong before the software.

The point count grows after the quote

The customer adds transmitters, renames areas and moves Modbus addresses during the build, so the count that priced the job no longer matches the database being built. The extra engineering days fall on the integrator.

Point tests live in many spreadsheet copies

Every tag needs a loop check from field terminal to operator screen, yet results sit in separate workbooks, one per tester. Nobody can list the instruments still untested on the night before site acceptance. The site acceptance date slips.

Licence keys and dongles are with the installer

Keys, renewal dates and USB dongles are held by the engineer who set up the site. A failed server stops the rebuild while somebody phones round to find which drawer holds the dongle.

Remote support lacks the site file

A call arrives about a frozen trend, and the engineer needs the software version, driver list and last backup before saying anything useful. All three sit on a colleague’s laptop in another city. The operator waits on the line.

Site hours overrun without warning

Commissioning in a plant with permit-to-work rules and escorted access takes more days than planned, and the overrun surfaces only when the invoice is prepared. Then the customer disputes the extra days.

Network and server lists are out of date

Managed switches, protocol gateways and operator stations get swapped during outages. Records still show the original build, and a spare ordered from it fits nothing on site.

How it runs

How the work flows through it, step by step.

  1. 1

    Enquiry and quotation

    The plant description, instrument list and network sketch are logged, and a quote is built from points by type, mimic screens, servers and engineering days. Revisions stay.

  2. 2

    Tag list and design

    The I/O list becomes the tag baseline. Mimics, trend pages, alarm tables and shift reports are tracked from request to customer comment.

  3. 3

    Hardware and build

    Servers, operator stations and managed switches are ordered and received against the site. Drivers are configured for each PLC and RTU.

  4. 4

    Point-to-point testing

    Each tag is tested from field terminal to screen, covering engineering-unit scaling and alarm limits, while tester and date are recorded and the open points are listed by area. Nothing hides.

  5. 5

    Acceptance and handover

    Factory and site acceptance tests are signed off. The as-built database, backups and licence details are recorded against the site.

  6. 6

    Support

    Calls, patches, licence renewals and added tags are handled under the support contract, with the site history open beside the call and the last backup one click away. Nothing is searched for.

Modules

What is inside.

Every module can be switched on, left out or changed to match how your team already works.

Enquiry and point count quotation

Price a project by point count, mimic screens, servers and engineering days from your own rates, and keep every quote revision so an estimator can explain why the price moved.

Tag list and change baseline

Store each tag database revision, count points by type, and price customer additions as a change against the baseline, so the quote and the build stay comparable. The gap shows.

Screen and alarm design tracker

Each mimic, trend page, alarm table and shift report is tracked from the client’s request to sign-off, carrying one owner and one due date. Late items stand out.

Hardware orders and receipt

Order servers, operator stations, protocol gateways and managed switches against the site, then track delivery, serial numbers and warranty from the supplier’s dispatch to the cabinet. Receipts close the order.

Server and network register

Keep a current list of machines, operating systems, VLANs, switch ports and IP addresses for every site, with each change dated and the engineer who made it named.

Point-to-point test log

Record each tag’s loop check, scaling and alarm trip test with tester and date, and list what remains open by area before the engineer travels to site.

Factory and site acceptance

Define test steps for the factory and site acceptance, record results and punch items, and capture the customer’s signature at both stages. Open items stay on the list.

Licence and backup register

Hold licence keys, dongle serials, renewal dates and the latest project backup for each site, behind restricted views that record who opened them and when.

Site hours and visits

Book engineers to site visits, record hours, travel and permit delays, and compare them with the days quoted for the phase. Overruns appear early.

Support contracts and remote calls

Log calls against the site with version, hardware and past changes in view, then bill the contract or the extra visit once the engineer has closed the call.

Solutions inside

The business modules it is built from.

Each one is also available on its own, or inside a system built for you.

  • Quote & Proposal Management

    Quotes are priced by point type, mimic screens, servers and engineering days, and a revised I/O list produces a revised quote.

  • Task Management

    Each mimic, trend page and alarm table is a task with an owner and due date, from request to customer approval.

  • Purchase Order Management

    Servers, operator stations and switches are ordered against the site, and delivery dates and serial numbers are recorded on receipt.

  • Fixed Asset Register

    Servers, operator stations and gateways are listed per site with dates and changes, so the register matches what is installed.

  • Quality Control

    Every tag has a loop check, scaling test and alarm trip test with tester and date, and open points are listed by area.

  • Project Time Tracking

    Engineers book hours to the site and phase, so an overrun in a plant with escorted access shows before invoicing.

  • Ticket Management

    A call opens against the site and shows version, hardware and earlier changes, so remote help begins with the right file.

  • AMC and Service Contracts

    Support terms and licence renewal dates sit with each site, and a reminder goes out before cover or a key expires.

Services

How we would put it in.

Setup, data migration, integrations and anything built on top.

Who uses it

One system, each person sees their part.

For project managers

Read tag count, test progress, hardware status and hours for each site, and see which phase is running behind the commissioning plan. Slippage is visible.

For SCADA engineers

Receive tag revisions, build mimics and drivers, and log loop checks without a separate workbook, so the test status of a site is always the one everybody sees.

For commissioning engineers

Open the site’s test log, open points and server list on a laptop in the control room, and book hours before leaving for the airport. Handover is clean.

For support engineers

Open a call and see the version, backup date, dongle and earlier changes at once, then answer the operator on the phone without asking anyone for a file.

For account managers

Track contract renewals, licence expiry and extension requests for every customer, and ring the plant manager before a dongle or a support term lapses.

Reports

The numbers the owner asks for.

  • I/O points quoted against points built, by project
  • Loop check status by area and tester
  • Sites whose last backup is older than your rule
  • Licences, dongles and support contracts due for renewal
  • Calls by site, category and age
  • Engineering days booked against days quoted, by phase
  • Switches, gateways and servers received and outstanding by site
Good fit

Who this is built for.

  • Integrators who build supervisory systems for water and wastewater pump stations, treatment works and reservoirs
  • Firms that deliver SCADA for factories, substations and solar plants
  • Companies that configure HMI faceplates and historian databases for process plants
  • Control system houses that support installed systems under annual contract
  • Teams that retrofit ageing supervisory systems onto new PLCs and RTUs
Honest answer

When it is not the right choice.

Made to fit

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.

Point rates and project types

Rates per analogue, digital and communication point, mimic design charges and project types are set the way you price, so a quote looks like your own.

Test sheets

Fields for signal type, engineering range, alarm limits and trip checks follow your own procedure and are reviewed with your engineers before the first loop check is logged.

Security rules

Who may see licence keys and remote access details follows roles agreed with your security staff, and every view of a key is written to a log.

Existing sites brought in

Your registers supply site lists, server details, keys and renewal dates, and the engineers who own each site confirm them. Nothing is trusted blindly.

Hosting

GullySystem runs the hosting, so project and support teams open the same site record. Template edits come from GullySystem staff.

Works alongside

  • Email
  • Calendar
  • Remote access tool links
  • Accounting export
  • SMS
Common questions

Questions owners ask before a demo.

Can quotes be built from point counts?

Yes. Analogue, digital and communication points are counted and priced from your rates, and a revised I/O list from the customer produces a revised count and a revised quote.

Does it connect to the live SCADA?

No. Live plant data stays in the supervisory system you deliver. This product holds the project, the register and the support record.

How are point tests recorded?

Each tag carries a test line with result, tester and date. A list shows the tags still untested in every area, so the commissioning engineer knows where to walk next.

Where are licence keys kept?

Licence keys sit in the site record, limited to named staff. Each time someone opens one, the entry is logged. Storage and retention are agreed with your security staff before any dongle serial or licence file is loaded.

Can the system flag an old backup?

The last backup date is stored per site. A rule you set marks sites that exceed it, and the report lists them so a support engineer can chase the customer.

Can support be billed by contract or per call?

Both. A call under contract is recorded without a charge, and an extra visit is billed from the hours booked.

How would we start?

A short workshop covers rates, project types, loop check sheets and call categories. The register of plants and the list of software licences come in from your files, and your engineers verify them before the first support call, so nothing unchecked reaches the support desk.

How is the software priced?

Pricing depends on the number of engineers, the sites and every historian or PLC link involved. A demo on one of your plants comes first, and the proposal that follows lists each of those items.

Wondering what it would cost? Share your requirements and an engineer will come back with a scope.

Book a demo

See SCADA System Integrator 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