A works order that reflects what is happening on the floor, not what was planned on Monday.

Early access

Manufacturing Software in Derbyshire

Manufacturing Software for businesses across Derbyshire. CubeERP supports Derby, Chesterfield and Swadlincote with implementation, data migration and UK-based support. Talk to us on 01234 672 617.

Book a walkthroughAbout CubeERP

We work with businesses right across Derbyshire, and the pattern is a familiar one: a system that was right when it was bought, extended past the point of sense, and now propped up by spreadsheets nobody wants to own.

Manufacturing is the part of that most people want to fix first.

Manufacturing software fails for one of two reasons: it assumes a factory that runs exactly to plan, or it demands so much data entry that the shop floor quietly stops feeding it. CubeERP takes the middle path. Multi-level bills of materials and routings define how something should be made; works orders, shop-floor booking and material issues record how it actually was. The gap between the two is the most useful report in the business. Sub-contract operations, scrap, rework, set-up time and part-completions are treated as normal manufacturing rather than as exceptions the system was not designed for.

  • Live

    Cost and progress from the shop floor

  • Full

    Genealogy, both directions

  • Mixed

    Make-to-order and make-to-stock together

What it does

Inside manufacturing software

The parts of CubeERP that make up manufacturing. Everything here shares one database, so nothing needs re-keying between them.

  • Multi-level bills of materials

    Assemblies, sub-assemblies, phantom levels, alternates and revision control - with where-used enquiry so you know what a component change affects before you make it.

  • Routings and operations

    Operation sequences with set-up and run times, work centres, machines, skills and sub-contract steps, including parallel and overlapping operations.

  • Works orders that live

    Issue, book, split, part-complete and close works orders, with shortages flagged before the job is released rather than discovered at the machine.

  • Shop-floor booking

    Touchscreen terminals or tablets for clock-on, quantity completed, scrap reason and downtime cause, so the data comes from the floor rather than a weekly transcription.

  • Traceability built in

    Batch and serial numbers carried through every level of the build, with certificates and test results attached, giving full genealogy in both directions.

  • Cost as it happens

    Material, labour, machine and sub-contract cost accumulating against the works order in real time, compared with the estimate that won the job.

In practice

Problems this actually solves

Anonymised, but not invented. These are the situations businesses describe to us before they change anything.

  • A whiteboard as the production system

    The situation

    A 60-person manufacturer scheduled from a magnetic whiteboard. It worked when everybody could see it, and stopped working the day a second shift started and half the team never walked past it.

    What changed

    The board is now a screen in three places, fed by works orders and shop-floor bookings. Priorities change once, centrally, and the second shift starts the right job.

  • BOMs in a drawing office

    The situation

    Bills of materials lived in CAD exports and a spreadsheet maintained by the design team. Purchasing frequently bought to a superseded revision, and nobody found out until assembly.

    What changed

    BOMs are held with revision control and effectivity dates, and purchasing buys from the live revision. Obsolete-part purchases dropped to close to zero.

  • Scrap that was never counted

    The situation

    Scrap was replaced from stock without a record. It was known to be "a few percent" and it was never quantified, so nobody could tell whether a process change had helped.

    What changed

    Scrap is booked with a reason code at the operation. Two causes accounted for most of it, one of which was a tooling issue fixed in a fortnight.

Local coverage

Manufacturing across Derbyshire

Our Derbyshire coverage includes Derby, Chesterfield, Swadlincote, Ilkeston, Long Eaton and Buxton, and the DE, S40, S41, S42 and S43 postcode districts. If you are in Derbyshire and not on that list, we almost certainly still cover you, so ask.

Postcode districts

  • DE
  • S40
  • S41
  • S42
  • S43
  • S44
  • S45

Areas we cover

Derby, Chesterfield, Swadlincote, Ilkeston, Long Eaton, Buxton, Belper and Ripley.

Getting to you

Roughly75miles from our Olney office

Discovery, training and go-live are done on site as standard - not because it looks good on a proposal, but because most of what a system needs to know is learned in the building.

Manufacturing elsewhere in Derbyshire

How it happens

What implementation actually involves

The same process wherever you are, and for Derbyshire it is done in person.

  1. 1

    Discovery

    A structured session mapping how you work now - the systems, the spreadsheets and the bits held together by one person’s memory. We come back with what the platform covers as standard, what needs configuration, and what needs building.

  2. 2

    Configuration

    Your sites, warehouses, price lists, approval limits, document templates, workflows and permissions set up to match the business - not a demo tenant with your logo dropped on it.

  3. 3

    Data migration

    Customers, suppliers, parts, bills of materials, price lists, open orders and stock balances brought across and reconciled. We migrate, you check the numbers against the old system, and only then do we cut over.

  4. 4

    Training & rollout

    Role-based training so the order desk learns the order desk and the warehouse learns the warehouse, with a pilot group first where it makes sense. Documentation and short screen recordings left behind for new starters.

  5. 5

    Ongoing support

    UK support from the people who built the platform, with a named contact, agreed response times, and a product roadmap you can influence.

You might call it something else

Manufacturing goes by a lot of names - if you are searching for any of these, this is the page you wanted.

Manufacturing ERPProduction softwareWorks order systemFactory management softwareManufacturing management systemShop floor control software

Questions

The things people ask first

Not on the list?01234 672 617hello@cubeerp.co.uk

  • Both, and mixed-mode - which is what most businesses actually run. Stocked items replenish to a plan while bespoke items are built against a specific order, on the same shop floor and in the same system.

  • Yes. A configurator generates the bill of materials and routing from options and dimensions, so a one-off can be quoted, planned and built without an engineer rebuilding the BOM by hand each time.

  • Sub-contract is a routing operation like any other. The purchase order is raised against the works order, material issued to the sub-contractor is tracked, and receipt books straight back into the job.

  • It has to be quicker than what it replaces or it will not be. Booking is a large-target touchscreen or a scan, typically two or three taps, and it is designed for gloved hands and poor light rather than an office desk.

  • Yes, via the API and webhooks. Machine counters, test rigs and existing MES layers can post completions and downtime directly, and we would rather integrate a system that already works than replace it for the sake of tidiness.

Related

Other things we can put right

Also available in Derbyshire.

Part of a bigger system

Manufacturing is one part of CubeERP. You can start here and switch the rest on later - it is the same system, not a separate purchase bolted on.

Explore the platform

Working in Derbyshire?

Manufacturing for your Derbyshire business

Tell us what your current system does badly. We will tell you whether CubeERP fixes it, and what it would take.

Start a conversationCall 01234 672 617