Trauma Zer0
EN

Services

Trauma Zer0 pays off when someone looks after it every day.

We deploy it, train your team and, if your company prefers, run the environment day to day, with the same team that maintains the code. It costs less than keeping someone on it full time, and the environment is never left without an owner when a technician leaves.

What is included

Four fronts, from assessment to training.

Assessment

A review of the environment against good practice, pointing out gaps in configuration and in process — including what no tool will solve.

Installation and configuration

Planning, installation and configuration of the suite and its associated services, led by an experienced engineer.

Environment upgrades

Keeping versions current, remotely or on site, without stopping the operation.

Training

Training the IT team on the features and the day-to-day operation of each module, with course material provided.

How it usually goes

The order that causes the least trouble.

It is not a rule — it is what experience has shown works best on a large estate.

01 Assessment A survey of the environment and its gaps. 02 Pilot One module, one area, a measurable result. 03 Rollout Expansion to the whole estate. 04 Training The team takes over the daily operation. 05 Operation We run it, or your team does. Starting with one module in one department avoids the classic mistake: buying the whole suite and rolling out none of it for lack of people.

Managed service

After the rollout, who looks after it?

Agents have to keep reporting, the server needs updates, alerts need someone watching them. There are three levels, and you choose how much of that our team takes on.

Level 1

Sustain

The environment up and up to date. Your team uses the product; we make sure it works.

  • Environment check twice a day
  • Overnight updates, no one interrupted
  • Agent and antivirus exclusions kept current
  • Server operating system kept updated
  • Server monitoring

Not included: day-to-day administration, such as building rules, putting reports together and answering users.

Level 2

Manage

For companies without someone dedicated to Trauma Zer0. One of our technicians becomes the go-to person for the environment.

  • Everything in Sustain
  • A named technician for your company
  • Groups, policies, reports and alerts kept in order
  • Support during business hours
  • Monthly report on what was done and what needs attention

Not included: support outside business hours.

Level 3

Dedicated 24×7

For critical environments that cannot wait until the next day.

  • Everything in Manage
  • A technician dedicated to your environment
  • 24×7 on-call for incidents

Tailored: scope is agreed for your environment.

Prices come in the proposal, next to the cost of doing it in-house, which you can work out right now, further down.

How it works

What happens without anyone having to ask.

Twice a day, the team checks the environment: agents that stopped reporting, the task queue, disk space and server services.
Trauma Zer0 and server operating system updates are applied overnight, without interrupting anyone’s work.
The agent and antivirus exclusions are kept current, so one does not get in the way of the other.
On Manage, a named technician who knows your environment keeps groups, policies, reports and alerts in order.
Every month, a report on what was done and what needs attention, for IT and for whoever IT reports to.
Everything is logged: whoever picks it up tomorrow finds today’s history.

In-house or managed

What it would cost to do this with your own team.

Enter what a support analyst costs your company per month, including salary, payroll taxes and benefits. The calculation uses the hours each level actually takes.

US$
Starts with a reference value for a support analyst, fully loaded. Replace it with your company’s figure.

That is per hour, over 168 paid hours a month.

LevelWhat it takesPer monthPer year
Sustain26 hours a monthtwo checks a day plus updates——
Manage40 hours a monthabout 2 hours per working day——
Dedicated 24×74.6 analysts24 hours, 7 days, with leave and days off——

The hours are what these environments take in our day-to-day work. Covering 24 hours, 7 days a week takes 4.6 analysts once leave, days off and absences are counted.

In the proposal, the price of the service sits next to this calculation, line by line.

When the technician leaves

The cost that almost never makes it into the spreadsheet.

The technician who learned the product and your environment leaves. The position stays open, the new hire needs training and takes months to perform like the previous one. Meanwhile the environment pays the price: agents stop reporting without anyone noticing, exclusions go stale, alerts pile up and the report stops going out.

In IT, technicians change often. With the managed service, that cost never reaches you.

—in learning curve alone, every time: three months performing at about half, on full salary. Not counting the new hire’s training and the month the position stays open.

Month 1
Open positionThe environment has no owner until someone takes over.
Month 2
TrainingThe new hire learns the product and the environment from scratch.
Months 2–4
Learning curvePerforms at about half of the person who left.
Managed
None of this reaches youIf someone on our team leaves, whoever takes over already works with the product every day and finds the environment’s history on record.

What the numbers leave out

And there is what does not fit in a spreadsheet.

Leave, absences and resignations

The environment does not stop when someone on the team does. The rota is ours.

The people who answer wrote the product

The service team is the same team that maintains the code. A question gets an answer, not a ticket to the vendor.

Log and report

Every intervention is logged and goes into the monthly report. Management sees what was done.

IT free for its own projects

Your people take care of what only your people can do.

Add-ons

To round out the package.

Hosting

Server in the cloud

The Trauma Zer0 server in our cloud or yours (AWS, Azure), with backups. No hardware to buy or maintain.

Integration

Data load files

Recurring data loads from other systems, such as HR and cost centers, so Trauma Zer0 knows who each machine belongs to.

Technical hours

What falls outside the scope

One-off projects, new integrations, on-site visits: billed by the hour, no new contract.

Send us what your team costs. We will send back the numbers for your environment.

With the number of machines and the level you are interested in, the proposal comes with the price of the service next to the cost of doing it in-house. Rather talk first? The 30-minute technical call still stands, with no sales pitch.

    Comes from the calculation above. Clear it if you would rather not say.