OKTO BMS Commissioning
OKTOCIDE-OSStrata
BMS for M&E contractors · Northern Ireland
For M&E contractors

Six trades. One deadline. One answer: CIDE-OS.

On most jobs the controls go in last and get used for a fraction of what they could do. We have turned that round. First, it is your BMS package: Schneider or Tridium, priced as a BMS package. CIDE-OS comes with it. There is no separate line for it and no extra cost. It is your digital commissioning partner, working for your commissioning manager from the first day of commissioning. Keep the tools you already use. CIDE-OS reads from them and is designed to help you make even more profit.

From day one

From the first day of commissioning, a live view of the M&E systems, in plain English.

Each trade, your commissioning manager and you all get a specific visual, with the status of where everything sits.

The balancer sees one unit at a time: super simple.

The mechanical engineer sees everything he needs to: pumps, valves, fans, dampers.

The trades see only what they need to. Complexity is removed.

Your commissioning manager stays in charge of all of it.

You get one page that tells you in the 'language of consequence' whether you are on target for the date.

It starts on the plant

Everyone gets a screen made for their own jobs.

Screenshot of the balancer's page for one fan coil unit, example data
The balancer's page · the red line tells him the leg is shut before he walks to it · shown for a valve that measures its own flow · there are versions for valves set by hand · example data
Your own view

Everyone gets a screen cut to his own job.

For the engineers: the detail each trade needs and nothing else, flushing, balancing, primary circuit, secondary air, fire. Each view shows the number the engineer expects from the step he is on and the number he got back, with the band the consultant approved beside it. The judgement stays with the engineer and the consultant. For your commissioning manager and project manager: every service and every trade, where each one is and what it is waiting on. For you: the state of the whole package you are delivering, progress updated live, and anything that needs your attention, in plain English. Your own page is next.

What it does for your team

The balancers stop travelling to find a fan off or a valve shut. The sparks know which circuit before the phone rings. Night shifts go on balancing instead of looking for faults. Witness slots are not lost to a damper nobody knew was shut. Your commissioning manager stops spending his day on the phone passing messages. Before somebody asks who shut it, your commissioning manager has the answer in front of him. The log is his. During the job nobody else sees it. At handover it goes to your client if you wish.

Who owns the record

The record is yours.

Every trade sees what is shut, which trade shut it and when. Only you and your commissioning manager see names, the full history and who allowed what. We do not pass it to the main contractor, the consultant or your client. At handover you decide what goes to your client and what does not.

We bring our own

No network, no problem.

While the building's network is being installed we run our own in parallel: temporary switches built for site conditions, battery backup, and supplies where there is no power yet. Plant that has no power monitoring we read with our own temporary wireless sensors. All of it is part of our digital commissioning service, and it comes out when the permanent network is handed over.

Your page

You are on target for 2 December. Chiller 2 can move the date. Its full flow has to be proven by Wednesday night.

This is what all of it comes to for you as managing director. Every reading, test and sign-off the trades and your commissioning manager record ends up on one page. It tells you whether you are on target, what the plant is measuring against design, what can move the date, what a week late costs you and who you are waiting on. It counts your systems through seven levels, L0 to L6.

Made for a large screen. Your page is designed for a desktop monitor or a meeting room screen. On a phone it will be too small to read.

Screenshot of the managing director's page in CIDE-OS, example data
Your page · on target or not, what the plant measures against design, what can move the date, what a week late costs and who you are waiting on · example data · made for a large screen
The plant

What it is measuring against design.

Flows, temperatures, points proven and test lines passed, trade by trade. The one reading that is off is shown in red, with the reading beside it that shows why.

The date

On target or not, and what can move it.

One sentence at the top. Under it, what can move the date, who has to act and by when.

The cost

What a week late costs you.

Damages, prelims and the completion payment that is held back, from your own contract figures.

Waiting on others

Who is holding you up, with the dates.

What you asked for, when you asked and how many days you have waited. It supports a delay notice and the final account. It does not replace the notice your contract asks for.

What you can hold us to

Four things you can hold us to.

One

The controls price is the price, and it includes the commissioning tool and the commissioning time the job needs.

Yours or ours, line by line, before you order plant. Field wiring, valves, actuators and the MCC set out on the quotation. Points and interface schedules attached. Scope and exclusions itemised. Never "there is no driver for that". Schneider or Niagara.

Two

Our engineer is on site the day the plant is ready, and the controls are commissioned once.

Every interface with the plant you buy in is proven while the job is running, so there is nothing left to find at the end. At the start we give you a dated list of what we need from you and when: plant ready, power on, network live. Software fully commissioned off site in a lab that mirrors the job, eight phases and a two-week soak test. On the levels that is L1, done before anything reaches site. "We'll sort it out on site" is banned in OKTO.

Three

Certificates, backups, graphics, O&Ms and asset data on the day we witness.

Handover documents complete on the day of witnessing, with a front end the client's estates people can run. Controls commissioned and recorded to CIBSE Code C. Air and water balancing records held in the form Code A and Code W expect, so the record is the one the consultant will sign. Your client gets the passwords, the licences and the software files in their own name. Nobody is locked in to us.

Four

A named engineer, directly employed and based in Lisburn, on your job from start to finish.

The Lisburn office answers the phone and can see the programme. Every call and email gets a reply the same working day. Every week your contracts manager gets the integration schedule showing what is proven, what is not, and what it is waiting on. You get the same live screen we have, from the first day of commissioning. If there is ever a problem, Philip's mobile is at the foot of this page.

The whole team

What the whole team sees.

What it shows

Every plant item, right now.

Running or stopped. Power on or off at the panel. Valve and damper position. Flow, temperature and setpoint against design. Which rooms and risers have power and network. Which legs are isolated and which are free to be worked on.

Every change

Who changed it, and when.

Overrides, isolations, setpoint changes, schedule changes, plant switched off at the panel. When something is found shut, you can see who shut it and when, instead of three firms saying it was not them.

Check this first

A zero reading tells you why.

Before anyone walks to the plant, the screen says whether it is power, an isolation, an override, a schedule or a fault, and which panel, valve or pump to look at. Your electrician goes straight to the right board.

Design against actual

Every valve and terminal against its design flow, live.

The balancer sees what is off before he travels, which rooms are ready for him, and which are not worth the trip tonight. The valves that keep giving trouble are kept on a list.

Tonight's list

Commissioning mode.

The plant on tonight's list stays on. Time schedules and the valve exercise are suspended. The moment anything on the list stops, your commissioning manager gets a message saying what and why.

The record

Every test logged as it happens.

What was tested, when, by whom, the result, against the plant and the integration it belongs to. The witness list and the certificate tracker are kept up to date from it, so nobody has to type them up at the end. At handover it goes to your client if you wish.

The squeeze at the end of every job

The end of the job, when we are all commissioning at once.

You have more and better experience there than me, but I have spent 34 years at that end of jobs too, and we have found a way to take some of the pain out of it. On a big job the fire test trips the boiler room fans, the gas valve shuts and the boilers lock out. Nobody did anything wrong, and the same thing happens again tomorrow. Your commissioning manager has to hold every one of those sequences in his head while each trade gets on with its own part. On the levels this is L5, the first time the systems are made to work together.

Reportvalve opened · pump did not run · supply to pump possibly trippedActionPlease investigate Pump_b2-2206_R3
The answer

A digital commissioning partner, working for your commissioning manager.

CIDE-OS, our own software, sits over our BMS. It watches every system at once, and when something is off or out of sequence it tells him in plain English what to look at, and why, the same day. Any BMS keeps a log. Most of the time nobody reads it until something has gone wrong. CIDE-OS reads it as the plant runs, and when an expected outcome does not happen it says which pump, which panel, which valve. Every commissioning step has an expected result. CIDE-OS shows the engineer that number and the number he got, with the band the consultant approved beside it. The judgement stays with the engineer and the consultant. We hold the M&E and controls integration schedule from day one, so your commissioning manager sees what is proven and what is still open. CIDE-OS and Strata are proven at the Belfast Trust, where they are running the digitisation of the estate. On your job it is the same software with a different set of rules.

How it works

Four things go in. One plain sentence comes out.

It takes four things: what the plant is doing, the test results, your commissioning manager's own record of who is where and what is signed, and the order things have to happen in. Where any of it is already in your programme, snag list or test sheets, CIDE-OS reads it from there. Your commissioning manager stays in charge of all of it. It is the same system that is running the digitisation of the Belfast Trust estate, with commissioning rules instead of estates rules.

One · what the plant is doing

What is running, right now.

Read through our BMS and our own temporary sensors. Every pump, fan, valve and damper. Power at every board. Flows, temperatures and setpoints. Every change, who made it and when. If there is no network yet, we bring our own.

Two · the test results

What has been tested and what it read.

Every point proved, every reading taken, every sequence run, held in the record with a name and a time. Where a valve measures its own flow, the reading goes straight in. Where it does not, the balancer's sheet goes in once, against the design numbers and the band the consultant approved. Certificates go in as they arrive.

Three · your commissioning manager's record

What is being asked of the plant this week.

Your commissioning manager's record and the trades' own tabs: who is on which floor tonight, what is booked and when, what the consultant has signed and what he has not, which board the electricians have taken off, which legs mechanical have shut. The software cannot know this on its own. Your people put it in, and the page says so.

Four · the order things have to happen in

What has to happen before the next thing can.

Our rules, written in plain English with the CIBSE code beside each one: flushed and treated before anything is balanced; pumps proven and legs open before a chiller is run up; fans running twenty minutes before an air reading counts; bands approved before anything is tested against them. The rules are the same on every job. The plant, the numbers and the dates belong to your job.

CIDE-OS puts the four together. For the balancer that is "no flow on 7-06 because the leg was shut at 19:12, not because of the fan coil". For your commissioning manager it is what is proven, what is still open and what it is waiting on. For you it is one sentence: you are on target for 2 December, chiller 2 can move the date, and its full flow has to be proven by Wednesday night. It never decides for you. At the Trust the same software runs the digitisation of the estate with estates rules instead of commissioning rules. The rules are a page long. The software is proven.

Your own tools

Keep the tools you already use. CIDE-OS reads from them.

Your programme, your snag list and your test sheets stay where they are. CIDE-OS brings them together into one answer.

What it reads

The records you already keep.

The programme gives it the dates and what is critical. The snag list gives it what is open and how long it has been open. The test sheets, witness sheets and certificates give it what is tested, witnessed and signed off. Your people carry on using what they use now.

What we bring

The BMS is the source we bring ourselves. Along with our CIDE-OS.

What the plant is doing comes straight from our BMS and our own sensors. Nobody has to record it.

What is entered in CIDE-OS

Two things, and we tell you which at the start.

What has to happen before what is set up once, from the systems schedule. Anything witnessed or agreed that is not recorded anywhere else is logged by your commissioning manager.

Do you test, or only report?

OKTO commissions the BMS itself. CIDE-OS reports across every trade.

Our own engineers, directly employed, commission the controls: off site in the lab first, then on site with your plant. CIDE-OS then reports on all six trades, including the five we do not commission ourselves.

Your own levels

Keep the levels you already work to. CIDE-OS counts in them.

L1 to L5, as used on data centre jobs, with planning before and handover after. Seven levels, numbered L0 to L6. The numbers are fixed. The names are set to the ones your job uses.

The seven levels

From the plan to handover.

L0 planned: test scripts approved. L1 factory tested. L2 installed and checked. L3 set to work, every point checked. L4 proven: each system tested on its own. L5 proven together: the whole building tested as one. L6 signed off and handed over.

The gate

Nothing moves up a level without you seeing what is still open.

A system is at a level only when every item of plant serving it is. If something moves up with a defect open or a signature missing, your page says so, with who allowed it. CIDE-OS does not stop the job. It never decides for you.

Witnessing

Who has to witness, and whether they are booked.

Factory tests, system tests and whole-building tests usually need the client or the consultant present. Your page shows who is needed and whether the date is booked, so a test is not lost for want of a witness.

Where we sit

OKTO commissions the BMS itself from L1 to L5.

L1 is done in OKTOLabs before anything reaches site. L3 is where most of the work is: every point checked end to end. L5 is where controls faults that passed L4 show up, and testing off site first takes most of that risk out.

The chaos that can happen on site

Every one of these happened on our last job in London. Our engineers found each of them the hard way. CIDE-OS is built so the commissioning manager is told first.

None of it is anyone's fault. That is what a building under construction is like. CIDE-OS sees it first because it watches every panel supply, every valve and every change on the system, and joins up what each trade cannot see from their own end. The first three are the ones that cost the most time on any job.

The fire test

Boilers lock out and nobody links it to the fire test.

Everyone knows the fire alarm is being tested. What nobody has worked out is that the test is stopping the boiler room fans, the gas safety is shutting the gas, the boilers are locking out, and that is why there is no hot water up the building. So the boilers get reset, the next zone is tested, same again. We have the sequence, fans, gas, boilers, in order, so it is one conversation instead of a week of resets.

The sparks

Fans and dampers stop while the sparks are testing.

The sparks have a board off to test it, so every fan on it stops and the dampers do not move. Mechanical lose half a day thinking it is a fan fault. We see the supply go and tell you it is the board, not the fans.

Site transformers

Site transformers overloading circuits.

Site is still on 110V for tools, the building is coming up on 230V. Half a dozen transformers get plugged into sockets in the risers that are there for plant, the circuit overloads and trips, and a panel two floors away goes off with it. Nobody puts the two together. We see every panel supply, so when one drops we say which circuit went and when, and you go and unplug the transformers instead of hunting for a fault.

Isolations

Isolations nobody has been told about.

Mechanical find a crossed pipe and shut a branch to fix it. Nobody was told. Downstream, coils go cold, tests fail, everyone checks their own bit. For commissioning we put position sensors on the isolation valves. A valve closes, we say which one and when. Nothing gets isolated without everyone knowing. We fit them as part of our commissioning on the valves we agree on the points list. They are in our price, and they come out at the end.

Valves

Valves left open after balancing or a flush.

Balancing needs them open, controls need them shut. A week later the kitchens are roasting and nobody remembers who set it. If it was set through the system, it is an override, we list it with who set it and when, and it drops when the test is done. If it was clutched open by hand for a flush, the system cannot see that directly, so we compare where the valve says it is with what the flow is doing and tell you which valve is not where it should be.

Setpoints

Boiler setpoint turned down and never put back.

Dropped to fifty overnight for another trade. Plumbers arrive for tap temperatures, water is cold, nobody knows who did it. If it was changed through the system we show who and when, and it is back up before they arrive. If it was changed on the boiler itself we show when it changed and you know who was on the plant.

Nights

Heating valves shut themselves at midnight.

Controls run a valve exercise at twelve. Nobody told the balancing team on nights. We know it is scheduled and who is on the plant, so we move it or warn them.

For the mechanical team

A front end the balancing and mechanical lads use themselves.

This is what the BMS should have been and never was. It was always bolted on at the end of the job and never used. Most controls houses will not give a mechanical foreman a login. We do. The mechanical team get a front end of their own, written by us in Lisburn, on the mechanical system only. Flushing, water treatment, valve exercise, pump speeds, fan speeds, valves to full flow and back, flow rates read live.

Every override has a name and a time on it and expires on its own. The front end has limits, so a pump cannot be run flat out against closed valves. It never replaces a permit or a lock-off: it shows the isolations that have been logged, and the safety interlocks stay live. It is our software, so it is the same on Schneider or Niagara.

It also shows what is running on the system right now and which legs are free to be worked on. Water treatment is on, mechanical need a leg off to change a valve, they shut it, and the treatment has to start again. Nobody knew the two were on at the same time. With the front end the question gets asked before the valve is shut.

Every override

Logged with who set it and when, and it expires.

No phoning the controls engineer to put a pump to 90%. No waiting for someone to put the valves back in auto.

It does not have to stop at handover.

It is the same system that is running the digitisation of the Belfast Trust estate, with commissioning rules instead of estates rules. The same software that told your balancer which valve was shut on a Tuesday night can run the building for your client afterwards. The commissioning record stays with it, and the estates team measure against it for years.

The BMS belongs to your client, with the passwords, licences and software files in their name. CIDE-OS stays on only if your client wants it, on their own agreement with us. If they do not, it comes off and the BMS runs without it. Either way there is no charge to you.

Separately, when you want it proven

Does the building do what the employer's design said?

This is a different job from getting the plant commissioned, and we keep it separate. It is proving the result, in a form the consultant will sign, with the record to go with it, on the day you witness, not three months later.

The record, on every job

CIDE-OS checks the end result and keeps the record.

The valve opened and the room got to temperature. Every test is logged against the plant and the integration it belongs to: what was tested, when, by whom and the result. You and your commissioning manager see the same record we do, so there are no surprises at the witness test. At handover it goes to your client, if you wish, for the O&Ms and the consultant's sign-off.

Verification of Performance, when you want it

Every room, every tap, every grille, pass or fail.

Every room held at full cooling, full heating and comfort for days at a time, measured by CIDE-OS and by independent calibrated loggers placed where the person sits. Floor temperatures by thermal camera. Air volumes at every grille against design. Noise at every fan speed. Hot water run-out and recovery, and the seconds to the agreed temperature at every tap. Interlocks and the fire sequence. Water samples to the lab. Pass or fail against bands agreed with the consultant before we start. The report your client's consultant signs. The result is yours and your client's; nobody else gets it. It is a priced service, and we do it at no charge on your first two projects with us.

What is proven and what is new

The controls are proven, the software is proven, what is new is the two together on an M&E job.

Proven

The BMS package.

Schneider or Niagara. Our own panel shop in Lisburn, over 400 panels last year. Directly employed commissioning engineers. 34 years commissioning buildings, the last twelve mostly on London jobs under main contractors. Sir Robert McAlpine will take a call.

Proven

CIDE-OS and Strata.

Running the digitisation of the Belfast Health and Social Care Trust estate across the Royal and City sites. The same software, built and supported in Lisburn.

New

The two together, for your commissioning manager.

Putting CIDE-OS over our BMS on an M&E job, as a digital commissioning partner with a tab for each trade, is new, and we want to do it with you. We would rather say that plainly than pretend otherwise. Your jobs are mostly in GB and so are ours; the idea is to work with Northern Ireland contractors from home, wherever the job is. On the first job together, the tabs are in your commissioning manager's hands by the end of week one, and if they are not helping him you tell us and we take them off. The price does not change.

Who we are

OKTO, Lisburn. Over three decades. Schneider or Niagara. Our own panel shop.

For over three decades we have written the software that ties heating, cooling, lighting, fire, video and access control, metering and power into one building. Our own panel shop built over 400 panels last year. For the last dozen years we have worked mostly with GB contractors on London jobs, from our office in Pimlico. Our largest job at home is with the Belfast Health and Social Care Trust, where we are digitising the estate across the Royal and City sites. CIDE-OS and Strata are the software running there. The Trust uses it to digitise an estate. Your commissioning manager uses it to commission a building. Same software, different rules. We would like to work with Northern Ireland contractors, wherever the job is. Our digital building work is Cyber Essentials Plus certified and built in line with ISO 27001 and ISO 19650-5. If it helps, we also act as master systems integrator (MSI) and take the whole specialist systems package as one subcontract, one point of contact for you: BMS, lighting control, AV, IT, Genetec video and access control management, and the digital building work that ties them together.

Reference

"The factory acceptance tests we have been involved with the last couple of days have been a resounding success and cement the positive influence OKTO have had on the Peninsula project. OKTO have continued to outperform the norm at every turn."

Matt Howe · Building Services Manager · Sir Robert McAlpine · The Peninsula London · will take a call

Trusted by · Sir Robert McAlpine · The Peninsula London · Schneider Electric · Allstate

The BMS line on your next tender

Have you anything live or coming up where the BMS package is still open?

The controls price is the price, and it includes the commissioning tool and the commissioning time the job needs. Send it over and we will quote it. Points and interface schedules come back attached to the quotation. Scope and exclusions line itemised. Or earlier than that, send us the tender pack and we will flag the controls risks before you price it. You also have an open invitation to Lisburn to see OKTOLabs, or Philip will come to you.

Philip Dowds · Managing Director · OKTO Integrated Services Ltd

Lisburn office +44 (0)28 9266 7030 · Philip's mobile 07860 356124

[email protected]

Unit 1 Crescent Business Park · Lisburn BT28 2GN

www.oktotechnologies.co.uk

Schneider EcoXpert · Tridium Niagara · BCIA · Safe-T-Cert · ISO 9001 · Cyber Essentials Plus

OKTO Integrated Services Ltd · Lisburn · London · Registered in Northern Ireland NI691500
OKTO