Skip to main content
Resources

Manufacturing, IoT & digital twins

Made Smarter funding: what manufacturers should have ready before their digital assessment

Preparing for a Made Smarter assessment in Yorkshire? Gather the workflow, systems, costs and questions that can help your team make the most of it.

Veda Software digital checklist cover for Made Smarter funding: what manufacturers should have ready before their digital assessment

7 minute read · Veda Software ·

Contents

If you run a manufacturing or engineering business in Yorkshire or the Humber, Made Smarter may be able to help you understand where digital technology could improve the way you work. The programme offers a digital readiness assessment and a roadmap, alongside other support for eligible businesses. You do not need to arrive with a perfect technical specification. A clear picture of the work, the sticking points and the people involved is more useful than a shopping list of software. This guide sets out what we suggest gathering before you speak to an adviser, and the questions to ask about funding before committing to a supplier or purchase.

What Made Smarter offers manufacturers in Yorkshire and the Humber

Made Smarter Yorkshire and Humber describes a digital readiness assessment and a tailored digital roadmap, alongside other forms of support for eligible manufacturers. The programme team can explain what is currently available and whether it applies to your business and proposed work.

Funding availability, eligibility and conditions can change. Speak to Made Smarter directly for the current details before making plans that depend on support. An assessment does not guarantee funding.

Made Smarter: Yorkshire and Humber adoption support

South Yorkshire Mayoral Combined Authority: Made Smarter

1. Follow one job through the business

Pick a recent, typical job and trace it from the first customer request through quotation, production, delivery and invoicing. Note the people and teams involved, what information each receives, and where the job changes hands.

A simple job map could cover these stages:

Enquiry and quote: Capture the request and prepare a price. Information: Specification, quantity, delivery date. Where it lives: Inbox, spreadsheet, CRM or estimating system. Possible friction: Missing details or repeated entry.

Production: Turn the agreed job into work for the floor. Information: Current specification, materials, schedule. Where it lives: Job system, shared folder or paper. Possible friction: Outdated details or waiting for clarification.

Dispatch and finance: Confirm completion and raise the invoice. Information: Delivered quantities, customer details, evidence. Where it lives: Delivery record and accounts system. Possible friction: Chasing paperwork or reconciling records.

These examples are an illustrative starting point, not a description of your business. Bring a redacted example where possible: the aim is to explain the process, not share sensitive customer or employee information unnecessarily.

2. Bring the problems, not just the proposed technology

Write down two or three recurring problems in ordinary language. “We re-enter every order into the production system” is more useful than “we need AI”. “The office cannot tell which drawing the workshop is using” is more useful than “we need a dashboard”.

For each problem, note:

Who experiences it and how often it occurs.

What happens next: a delay, a correction, a missed handoff or a decision made without information.

Whether it affects one team or crosses sales, operations and finance.

Any workaround that already helps, including the people who know how it works.

The adviser can help explore potential technology. Your knowledge of what actually happens on a busy day is the evidence they cannot get from a product brochure.

3. Gather a small baseline

Choose measures you can explain and check. Depending on the issue, that might be the number of orders re-entered in a week, the time taken to find an approved drawing, the frequency of production changes, or the time between dispatch and invoicing.

You do not need to manufacture precise figures. If you have only a rough estimate, label it as an estimate and explain how you arrived at it. A useful next step may be to measure the process for a few weeks before deciding whether a proposed solution is worth pursuing.

Illustrative example: a team records 20 jobs in a week and finds that six need someone to chase missing information. The first useful measure is the number of jobs needing a chase and why. That does not prove what a system will save, and the mix of jobs may change from week to week.

4. List your current systems and who owns them

Make a short inventory of the tools that hold important information: estimating, customer records, job management, production planning, stock, quality, maintenance and accounts. For each one, record what it does, who uses it, who supplies it and whether it has a supported way to share data with another system.

Include spreadsheets, shared folders and paper if the business relies on them. Note any contract renewal dates, access restrictions, support contacts and known limitations. You do not need to share passwords. Where a supplier controls an interface or data export, make a note of who can answer questions about it.

This helps the assessment distinguish between improving a process, configuring an existing tool, using a supported connection and replacing something that no longer fits. The answer may be a combination, rather than a new system for everything.

5. Bring the people who see different parts of the work

A senior decision-maker can explain the business priorities and what the company can support. Someone from the production floor can describe how the job works in practice. An office, finance or customer-service colleague can explain the information they need and the problems they chase.

You may not need everyone in every meeting. Make sure their perspectives are represented, and identify who could own a change after the assessment. Ask what training, time and support the team would need to use a new process consistently.

6. Understand the funding and cash-flow questions

Before ordering equipment, signing a contract or treating an expected contribution as available, ask your Made Smarter adviser:

Is our business eligible for the support currently available in our area?

What does the programme need to know about our project and intended outcome?

What costs, approvals and deadlines should we understand before committing to a supplier?

What should we plan for if our project scope or timetable changes?

These are questions to take to the programme, not a substitute for its application guidance. Grant availability and conditions can change; an assessment is not a funding award, and no supplier can promise that an application will succeed.

Our view: start with a decision your team can use

At Veda Software, we think the best assessment is one that helps a business make a better decision, even if that decision is to change less than expected. A grant can make a worthwhile improvement easier to afford, but it should not be the reason to buy a system that the team does not need or cannot maintain.

Start with a handoff that repeatedly slows the business down. Understand why it fails, agree who owns the information and consider whether the tools already in place can handle it. If a connection or new application is justified, define what it should do, how exceptions will be handled and who will support it after launch. Then measure the result against the baseline you agreed.

That approach also helps when funding is unavailable: you still have a clearer problem, an order of priorities and a way to judge the next investment.

A checklist to take into the assessment

A short description of the business, manufacturing activity and sites.

One typical job traced from customer request to delivery and invoice.

Two or three recurring problems, with the people and handoffs affected.

A small set of baseline measures, clearly separating estimates from recorded figures.

A list of important systems, spreadsheets and suppliers, with named internal owners.

The business outcome you want and any genuine timing constraints.

The people who can explain the work and make decisions about change.

Questions about eligibility, project scope, approvals and costs.

Register or ask about the current programme through Made Smarter Yorkshire and Humber. Its team can confirm the support and conditions that apply to your business.

If you would like an independent conversation about how information moves between your existing systems, see how Veda Software works with manufacturing and industrial businesses or book a free Systems Strategy Call.

Key takeaways

  • Follow one job through the business and identify the handoffs that cause friction.
  • Bring a small baseline, a list of current systems and the people who understand the work.
  • Ask Made Smarter directly about current eligibility and conditions before relying on funding.
  • Choose an improvement your team can use, own and support.

Business Improvement Partnership

Make the next improvement part of how your business works.

Work with us on the systems, software and automation that can save your team time. Start with your priorities and agree a practical plan for ongoing improvement.

Veda Software · Self-serve ordering portal build

One portal, every venue: decentralising print ordering across a national estate

Print ordering across a national estate ran through an awkward external experience and one central team. Veda Software designed and built a self-serve ordering portal: every venue orders directly, and the central team no longer has to push each order through by hand.