One Engineer, Every Day, On Site: Staff Augmentation for a Singapore Manufacturer

Short answer: A Singapore manufacturer that has grown past roughly 100 IT users and devices has usually already crossed the point where remote-only support stops fitting — and the decision is mostly arithmetic. At Brocent's published Singapore rates, a dedicated onsite engineer overtakes ad hoc dispatch at around 50 support hours a month. Floor complexity decides the rest.

Why Singapore manufacturers cross the remote-only line without ever deciding to

There is a specific kind of IT problem that only shows up in manufacturing, and it is not technical. It is a sizing problem that arrives without an announcement.

A Singapore manufacturer that employs sixty people can run its IT the way a professional-services firm does. Laptops, email, a file server or a cloud tenant, a switch in a comms cabinet, and a support arrangement where someone remote picks up the phone and fixes what can be fixed remotely. That model works. It works well enough that nobody revisits it.

Then the company wins a longer-term contract, adds a second shift, buys three more machines, and hires forty people to run them. Headcount goes from sixty to a hundred and fifty over two or three years. Nobody sat in a meeting and decided to change the IT support model, because nobody sat in a meeting about the IT support model at all. The arrangement that fitted sixty office-heavy staff is now carrying a hundred and fifty people, ninety of whom work on a floor, across two shifts, on equipment that did not exist when the arrangement was signed.

This is not a story about a bad provider. Remote support is genuinely good at what it is good at — password resets, mailbox problems, software installs, the long tail of end-user issues that make up most tickets in most companies. What changes in a manufacturing environment is the proportion of problems that are *physical*. A barcode scanner that has stopped pairing. A ruggedised terminal at the end of a line whose screen has gone dark. A cable run that has been clipped by a forklift. A label printer that prints blanks. A machine-side PC running the software that talks to a piece of production equipment, which needs someone standing in front of it.

None of those are hard problems. Every one of them requires a person in the building.

Singapore's manufacturing base makes this pattern common rather than unusual. The industrial estates around Kaki Bukit, Woodlands, Jurong and Tuas are full of contract manufacturers, sub-assembly operations, precision engineering firms and light-assembly plants in exactly this size band — big enough that IT downtime costs real money, not big enough to have built an internal IT department, and staffed by people whose job is production, not IT triage.

The scenario: a hundred and fifty-five people, two shifts, and a support model built for sixty

Consider an illustrative composite — not a named client, but a shape that recurs.

A Singapore contract manufacturer produces sub-assemblies for industrial equipment makers. It occupies two adjacent units in an industrial estate: a shop floor with assembly cells, test benches and a small clean area, plus a mezzanine office holding sales, planning, procurement, quality and finance. Headcount is a hundred and fifty-five. Around ninety-five of those people work on the floor, across a day shift and a late shift that runs until roughly ten at night.

IT support is remote, contracted years ago when the company was under seventy people and almost entirely office-based. The arrangement covers the helpdesk, the servers, patching and antivirus, and it does that competently. When something needs hands, an engineer is dispatched.

The operations manager holds the IT relationship, on top of running production planning. He is not an IT person and has never claimed to be. What he has instead is a growing sense that IT is taking up more of his week than it used to, in a way he cannot quite quantify.

Here is what that actually looks like week to week:

• A test bench PC loses its connection to a measurement instrument on a Tuesday morning. The remote engineer works through it over the phone with a production supervisor who is trying to run a shift at the same time. It takes ninety minutes and ends with a dispatch booking for the following day.
• Two handheld scanners in goods-in are unreliable. Nobody has raised a ticket, because raising a ticket means a phone call, and the workaround — keying part numbers by hand — takes an extra two minutes per receipt and works.
• The late shift has no support at all after roughly six in the evening. Anything that breaks after that waits until morning, which on a bad night means the second half of a shift runs on paper.
• A new assembly cell was commissioned three months ago. Its machine-side PC was configured by the equipment vendor's commissioning engineer. Nobody in the company knows what is on it, whether it is patched, or whether it is backed up.
• The operations manager has become the informal first line. People walk up to his desk with IT problems because that is faster than the process.

Not one of these is a crisis. Together they are a support model that no longer matches the operation, and the mechanism that would normally catch that — a review of whether the arrangement still fits — is not part of anyone's job.

What the delay actually costs, and why it stays invisible

The reason this situation persists is that its cost never appears on a single line anywhere.

A remote-only model in a manufacturing setting produces four kinds of loss, and all four are diffuse:

Extended resolution on physical faults. A fault that a person in the building would clear in fifteen minutes takes ninety minutes of remote diagnosis followed by a next-day visit. The ticket eventually closes and the metrics look acceptable. What the metrics do not capture is the production supervisor who spent that ninety minutes on the phone instead of running the line.

Suppressed demand. This is the expensive one. When getting help is inconvenient, people stop asking. The two flaky scanners in goods-in never became a ticket. Neither did the label printer that needs to be power-cycled every morning. A support model that people route around produces a clean-looking queue and a floor full of accumulated workarounds, and there is no report that shows you this.

Uncovered hours. A two-shift operation supported on a single-shift model has a structural gap. It is not that the late shift generates many incidents — it is that the ones it does generate land at the worst possible moment, with nobody to escalate to.

Unowned equipment. Machine-side PCs commissioned by equipment vendors are the classic manufacturing blind spot. They are production assets that behave like IT assets, and in most companies of this size nobody has decided who owns them. They sit outside patching, outside backup, and outside the asset inventory, until the day one fails and takes a cell down with it.

Add those up and the honest answer is that the operations manager's instinct is correct: IT is costing the company more than the invoice says. He just has no way to prove it, which is exactly why the conversation never gets started.

Brocent's perspective: this is an arithmetic question with a judgement attached

We have been placing onsite engineers in Asian offices and plants since 2007, and the single most common mistake we see companies make at this size is treating the staffing model as a matter of preference — "we would rather have someone here" or "we would rather keep it lean." It is not a preference. It is mostly a calculation, with one judgement call on top of it.

The arithmetic: where a dedicated engineer overtakes dispatch

Brocent publishes both sides of this so the comparison can actually be done. On our dispatch and FTE rate page, Singapore field dispatch is listed at US$85 for the first hour and US$78 for each additional hour — an indicative, fully-loaded Level 1 end-user-computing rate, next-business-day, standard 9×5, covering the first-hour minimum plus travel within the metro area. A dedicated full-time onsite engineer in Singapore is listed at US$4,160 a month.

Divide one by the other and you get the crossover. At those entry rates, a dedicated engineer breaks even at roughly fifty support hours a month at a single site — about twelve hours a week. Below that, dispatch is almost always cheaper. Above it, a placement usually is, and the gap widens quickly.

Two things about that number matter more than its precision.

The first is that most companies in this position have never measured their actual hours, so they are guessing on the wrong side of the line. Ninety minutes of remote diagnosis plus a next-day visit plus the supervisor's time is not "one ticket" — and once you count the suppressed demand, the real figure is usually higher than anyone expected.

The second is that the crossover is not the whole answer, because dispatch and a resident engineer are not the same product. Fifty hours of dispatch spread across ten separate visits gives you ten arrivals by people who each have to be told where the comms cabinet is. A resident engineer gives you continuity — someone who knows which cell has the temperamental terminal and which vendor to call about the test bench. That difference does not show up in an hourly rate.

The judgement: what the sizing ladder says, and where it stops

Brocent's own sizing guidance, published on the full-time onsite IT support page, is deliberately blunt:

• Under 50 users — ad hoc dispatch or remote managed IT support.
• 50 to 100 users — around a half FTE, a part-time onsite engineer.
• 100 to 500 users — one dedicated full-time L1/L2 engineer.
• 500 to 2,000 users — multiple FTEs with a team lead.
• 2,000 and above — an FTE team with a project manager.

The rule of thumb behind it: a full-time engineer is typically warranted once the environment passes roughly a hundred IT users *and/or devices*.

That "and/or devices" clause is where manufacturing diverges from the office-headcount reading of the ladder, and it is the judgement we would apply to the composite above. A hundred and fifty-five people sits inside the 100-to-500 band, so the ladder says one FTE. But the device count in a manufacturing environment runs well ahead of the headcount: every assembly cell terminal, scanner, label printer, test bench PC and machine-side controller is a managed device with a failure mode, and none of them are somebody's laptop. A hundred-and-fifty-five-person plant can easily carry two hundred and fifty managed endpoints. A hundred-and-fifty-five-person consultancy carries a hundred and seventy.

So the ladder is a starting point, and floor complexity moves you up it. Two shifts push the same way. A single-shift, office-heavy company at this headcount might genuinely be fine at a half FTE plus dispatch. A two-shift plant at the same headcount is a full placement, and the honest version of that conversation includes when the engineer's hours should sit — a placement that finishes at six in a plant that runs until ten has solved a different problem than the one that was raised.

What a dedicated onsite engineer actually includes

The phrase "dedicated onsite engineer" covers two very different products, and the difference is almost entirely in the parts nobody asks about during procurement.

The version that goes wrong is a body-shop placement: a contractor is found, sent to your site, and invoiced monthly. When that person is on leave, support disappears. When they resign, you are back at the start. Nobody has verified their background beyond a CV. There is no record of what they actually did, and no escalation path when the problem is above their level.

The version we place is an operational programme with the HR machinery attached, and it is worth being specific about what that means. Brocent's placement process runs as nine defined steps — a vetting call to establish the environment and the requirement; a hiring plan published to our sourcing network; sourcing, technical assessment and screening against your criteria by our HR recruitment team; candidate interviews that you conduct, with scheduling handled for you; NDA and offer, with background verification covering criminal, education and identity checks; formal HR onboarding including payroll, benefits enrolment, local labour law compliance and liability insurance; onboarding initiation, where our team prepares a takeover pack, a client IT manual and a shadow plan so the engineer arrives briefed rather than guessing; a three-month hyper care period with close performance monitoring and knowledge transfer; and then ongoing attendance management through our FTE management system, producing billable hours, absence rates and attendance reports.

Three parts of that deserve to be pulled out, because they are the ones that decide whether the placement holds up over years rather than months.

Leave cover. Your engineer will take annual leave and will occasionally be ill. Whether a trained replacement arrives from our pool during that time is a contract term, not an assumption — it is one of the twelve factors we price against, and it belongs in the quote rather than in the first awkward conversation about it.

The client IT manual. A resident engineer accumulates knowledge, and if that knowledge only lives in their head, you have swapped a support gap for a personnel dependency. The manual and the takeover pack exist so the environment stays documented independently of who is standing in it.

Attendance and reporting. A resident engineer with no reporting is invisible. Billable hours, absence rates and attendance reports are what let you see, a year in, whether the sizing decision was right — or whether the ladder has moved you to a half FTE, or on to two.

Placement pricing is not a single number, and we would rather explain why than publish a figure that misleads. It moves with contract duration (standard terms are six, twelve and twenty-four months, with longer commitments priced lower); job level and specialist skills, where a Level 2 engineer runs roughly 21% above entry and a Level 3 roughly 44%; years of experience; working language, where a bilingual engineer commands a premium; the work time window, since standard hours, extended hours, shift work and on-call are different products; site location and whether multiple sites are covered; resource type; whether a backfill resource is required; how client holidays are treated; paid leave entitlements under local labour law; handover days on a resource change; and acceptance of a standard severance clause on early termination. The published US$4,160 is a fully-loaded entry reference for a Singapore dedicated engineer, not a quote — and multi-FTE and multi-country programmes price lower than a single placement.

One more mechanic, because it changes the cash picture: dispatch visits are billed after the work, on standard thirty-day terms, itemised by ticket. FTE placements are invoiced monthly in advance. Local GST invoicing is handled the same way either side.

Three ways a Singapore manufacturer at this size can staff IT

Remote-only support, past its sizing point

• What it is: the arrangement that worked at sixty people, still running at a hundred and fifty-five.
• Where it genuinely wins: the long tail of end-user tickets — accounts, mailboxes, software, the things that are actually best solved remotely.
• Where it breaks: physical faults on the floor. Every one becomes a phone call plus a next-day visit, and the production supervisor absorbs the difference.
• The hidden failure mode: suppressed demand. People stop reporting problems that are annoying rather than blocking, and the ticket queue looks healthier than the floor is.
• Honest verdict: correct under fifty users, and increasingly wrong above a hundred — particularly once device count outruns headcount.

Ad hoc dispatch visits on top of remote support

• What it is: remote support as the baseline, with an engineer sent when hands are needed. Singapore dispatch is published at US$85 for the first hour and US$78 for each additional hour.
• Where it genuinely wins: genuinely intermittent need. No monthly commitment, no minimum, billed after the job on thirty-day terms. For a single-shift, office-heavy site under the crossover, this is the right answer.
• Where it breaks: frequency. Ten visits a month is ten arrivals, ten context re-explanations, and ten next-business-day waits. It does not become continuity by happening often.
• The economics: past roughly fifty hours a month at one site, you are paying placement money for dispatch service.
• Honest verdict: the right model below the crossover, and an expensive way to avoid a decision above it.

A dedicated onsite engineer with leave cover, sized to the floor

• What it is: a named, vetted engineer resident at your site — Brocent's model — placed through the nine-step process, with leave cover, a documented takeover pack and IT manual, attendance reporting, and Brocent's technical team and escalation network behind them.
• Where it genuinely wins: physical faults, continuity, shift coverage, and the accumulated site knowledge that makes the second year cheaper than the first.
• What it costs: US$4,160 a month as a published, fully-loaded Singapore entry reference, moving with level, hours, language and the other factors above.
• Where it needs care: sizing. Placing a full FTE at a site that needs a half is a real waste, and placing an engineer on day-shift hours in a plant that runs two shifts solves the wrong half of the problem.
• Honest verdict: the model that fits a two-shift plant past a hundred users and a device count well past that — provided the hours are sized to the shift pattern, not to the office.

Brocent's own framing of the commercial case is that a pay-as-you-go arrangement saves a minimum of 37% of the OPEX and CAPEX cost of hiring the equivalent role in-house, once payroll, tools and management time are counted. We would rather you test that against your own numbers than take it on faith — which is why both the dispatch rates and the FTE reference are published rather than quoted on request.

Frequently asked questions

At what headcount does a dedicated onsite engineer start to make sense?

Roughly a hundred IT users and/or devices, per our published sizing guidance — with one FTE indicated across the 100-to-500 band. In manufacturing, read the device half of that clause carefully: terminals, scanners, label printers, test bench PCs and machine-side controllers all count, and a plant's device count typically runs well ahead of its headcount. The practical test is the crossover: at Singapore's published rates, past about fifty support hours a month at one site, a placement is the cheaper model.

How is a dedicated engineer priced in Singapore?

The published entry reference is US$4,160 a month for a fully-loaded, dedicated onsite engineer, invoiced monthly in advance. That figure moves with twelve named factors — contract duration, job level and specialist skills (Level 2 roughly +21%, Level 3 roughly +44% against entry), experience, working language, coverage window, site location, resource type, backfill requirement, holiday treatment, paid leave compliance, handover days and severance terms. Multi-FTE and multi-country programmes price lower. Field dispatch, for comparison, is US$85 for the first hour and US$78 for each additional hour.

What happens when the engineer is on leave?

Whether a trained backfill arrives from Brocent's pool is a priced contract term, not an assumption — it is explicitly one of the twelve pricing factors, and paid leave entitlements under Singapore labour law are handled as part of the same arrangement. This is the question we would push hardest for a manufacturer to settle in writing, because an uncovered week on a two-shift floor is precisely when the model needs to hold.

Can this scale back down if headcount drops?

Yes, and the sizing ladder runs in both directions. Standard contract terms are six, twelve and twenty-four months, so the natural moment to re-sit the question is at renewal, using the attendance data the placement itself has generated. A move from one FTE back to a half FTE plus dispatch is a normal outcome, not a failure — and "hire for change," a change to an existing service plan, is a defined resource type we assess and re-scope against.

Does the engineer come from Brocent, or can we keep the person we already have?

Both are standard. A fresh hire is sourced, assessed and placed by us. A rebadge applies when you already have an onsite resource and want to change the contracting party while keeping the individual — we run an HR assessment covering job level, statutory benefits and a service continuity plan, so the person's employment moves without their service to you being interrupted. Hire to budget and hire for change cover the other two common cases. Resource type is one of the twelve pricing factors precisely because these carry different set-up and transition costs.

How is this different from just hiring an IT person ourselves?

Mechanically: you do not carry the recruitment cycle, the payroll and benefits administration, local labour law compliance, liability insurance, the tooling, or the single-person dependency. Operationally, the more important difference is escalation — a resident L1 or L2 engineer backed by a wider technical team can hand a network architecture or server problem to someone qualified, where a sole in-house hire has to become that person or wait for a vendor. Our published position is that this saves a minimum of 37% against the fully-loaded in-house equivalent; the part we would emphasise is the escalation depth, which is harder to price and usually matters more.

What background checks are involved, and who does them?

Brocent's HR recruitment team conducts background verification covering criminal record, education and identity as part of the offer stage, with a signed consent letter obtained first so the check is conducted lawfully and the individual is properly informed. NDAs and project documents are signed before the engineer arrives, and onboarding covers payroll, benefits, labour law compliance and liability insurance. For a manufacturer with customer-audited processes or confidentiality obligations to equipment makers, this documentation is usually the part that matters most in a supplier audit.

Do we still need a managed IT plan if we have someone onsite?

Yes — and this is the part most often got backwards. A resident engineer is a pair of hands and a source of site knowledge; they are not a 24/7 monitoring platform, a patching pipeline, a backup regime or a security governance function. The placement works because those things exist behind it. An engineer with no plan behind them is a single point of failure with a desk.

Where onsite staffing belongs: inside the plan, not beside it

The mistake we would most want a manufacturer at this size to avoid is treating a dedicated engineer as the answer on its own.

The reason the composite company above has a problem is not that it lacks a person in the building. It is that its support arrangement was sized for a different company and nobody re-sized it. Adding a resident engineer to an unreviewed arrangement fixes the response-time symptom and leaves the machine-side PCs still unowned, the late shift still uncovered after the engineer goes home, and the device inventory still incomplete.

What actually resolves it is a plan that covers the environment — 24/7 NOC monitoring, a helpdesk, managed firewall, patch management, endpoint protection, backup and disaster recovery, credential management, and a named vCIO who owns the roadmap and asks the sizing question at renewal so an operations manager does not have to — with the onsite placement sized as one component of that plan rather than bolted on beside it.

That is what Brocent's managed IT plans are: a per-user monthly plan carrying the monitoring, patching, security and governance layer, with onsite staffing, field dispatch and infrastructure add-ons sized on top of it for the sites that need them. Singapore per-user pricing is published on the pricing page alongside the dispatch and FTE references, precisely so a comparison like the one in this article can be run before a conversation rather than during one.

If you are running a Singapore plant somewhere past a hundred users, on two shifts, with a support arrangement you inherited from a smaller version of the company, the useful first step is not a quote. It is counting your actual support hours and your actual device count for one month. If the hours land past fifty and the devices past two hundred, the ladder has already answered the question — and we are happy to work through the sizing with you. Get in touch and we will start with your numbers rather than ours.

*The company described here is an illustrative composite of the manufacturing operations Brocent supports across Singapore and Asia, not a named client. Rates cited are Brocent's published indicative figures for Singapore and are confirmed at scoping. Brocent was founded in Beijing in 2007, opened its Hong Kong office in 2016, and has been headquartered in Singapore since 2021.*