Electrical &
mechanical
scope, priced to drawing.
RONCO reads the drawings, writes the scope and prices it — including the interfaces nobody prices. The work on the floor is Ahavah Automation’s: their crews, their license, their site. RONCO is the sales and estimating side of that arrangement: the quote, the scope and the exclusions come from here.
RONCO does not install. RONCO’s side of this is commercial and on paper: the take-off, the scope, the exclusions, the number, the contract. Ahavah Automation performs the work — their crews, their license, their site, their name on the safety file.
Packages
we price
Take the whole package or the single discipline holding your schedule up. Ahavah Automation performs all four; RONCO prices them and writes the interfaces into the scope before award.
Priced against Div. 26 Electrical · Div. 25 Integrated Automation · Div. 41 Material Processing & Handling · Div. 40 Process Interconnections
-
1.01
Mechanical scope
Conveyor runs, machine alignment and structural assembly set to tolerance by Ahavah’s crews, with as-built dimensions recorded on the way out.
Alignment
Conveyors
Steelwork -
1.02
Electrical engineering
Power distribution, panel build and field wiring designed for the load you actually run — drawn, labelled and traceable by Ahavah’s engineers.
LV distribution
Panel build
Schematics -
1.03
Commissioning & support
Functional tests, calibration and staged start-up run by Ahavah’s technicians, so the line proves itself before it carries product.
Loop checks
Dry runs
Punch list -
1.04
Turnkey electrical package
Planning through final energization quoted as one package: one scope, one number, one commercial point of contact. Ahavah’s crews carry it out.
Single scope
Energization
Handover
Where the scope
line falls
Every electrical package has the same arguments, and none of them are hard. They are only expensive when nobody priced them.
-
2.01
Who supplies the disconnect at the machine.
-
2.02
Who lands the leads on a vendor skid whose manual says only “field wiring by others.”
-
2.03
Who pulls through the sleeves the mechanical contractor cored.
-
2.04
Who buys the drive when the OEM quoted the drive and the panel both.
-
2.05
Who owns the network drop to the PLC.
-
2.06
Who fire-stops the penetration afterwards.
Ask every bidder to mark each one included or excluded, in writing, before you compare numbers. And name who holds the tag register at award. If nobody holds it, you hold it.
Method
Five stages — the first is RONCO’s, the other four are Ahavah Automation’s-
01
Survey
RONCO walks the floor before pricing, measures what is there and marks the constraints nobody drew.
-
02
Engineering
Ahavah issues layouts, single lines and panel schedules for review before material is cut.
-
03
Installation
Ahavah’s mechanical and electrical crews sequenced around your production windows.
-
04
Commissioning
Ahavah works the system loop by loop, then function by function, with results recorded on the way.
-
05
Handover
As-builts, test records and an Ahavah walkthrough with the people who will run it.
Written so each stage closes before the next opens.
Turnover
package
What leaves site with you. RONCO writes every line of it into the scope before award, and Ahavah produces it during the work rather than reconstructing it afterwards — which is the difference between a handover and a hand-wave.
-
3.01As-built drawings
Dimensions recorded on the way out, not measured back in once the crews have gone.
-
3.02Single lines & panel schedules
Issued for review before material is cut, and reissued to match what was actually installed.
-
3.03Loop check records
Signed by the technician who ran them, loop by loop, so the record is written during commissioning.
-
3.04Functional test records
Function by function through staged start-up, with the calibration figures attached.
-
3.05Punch list, closed
Closed before demobilization. An open list at handover is an open list forever.
-
3.06Operator handover
A walkthrough with the people who will run it, and the maintenance crew who will keep it running.
What a loop check
actually proves
A continuity test proves copper. A loop check proves the tag.
A loop check injects at the field device and walks it: 4 mA, 12 mA, 20 mA. It confirms the engineering-unit value at the controller and again at the HMI, at 0, 50 and 100 percent of range. It confirms polarity, the rack, slot and channel, the scaling, the fail direction on signal loss, and that the alarm annunciates where the operator will actually be standing. Then the final element is stroked, and watched to confirm it moves the right way.
Three years from now, when a transmitter reads wrong and nobody who was on the job still works there, that sheet is the only thing that says what good looked like.
- loop and tag number
- device make, model, serial
- cable and core numbers
- terminal numbers at every junction
- I/O address
- calibrated range and units
- as-found and as-left values at each test point
- test instrument ID and calibration due date
- date, technician, witness
Two kinds
of buyer
The same take-off answers both. The sentence they need first is different.
A priced package with the installer named
Priced against your drawings, installed by Ahavah Automation to your schedule, documented for your client's turnover pack.
- Bid-ready take-offs and fast RFI turnaround
- Interfaces with civil, HVAC and process trades written into the scope
- Punch list scoped to close before demobilization
Downtime treated as the budget
Work planned around shift patterns and shutdown windows, with the outage sequence and the start-up plan written into the scope before you award it — and executed on site by Ahavah Automation.
- Shutdown and weekend windows priced in
- Retrofits into live production areas, sequenced and priced
- Operator and maintenance training included in the scope
Five kinds
of downtime
Tell us which of the five you have and the number changes. Guess, and the estimate is fiction.
-
01 4–6 h
Sanitation window
Four to six hours, nightly. Area struck and re-sanitized before first product, so everything has to come out and go back every shift.
-
02 5–7 days
Changeover week
Planned a year out. The constraint is congestion, not access.
-
03 ~90 days
Retail freeze
Roughly October into January. The constraint is a calendar nobody on site controls.
-
04 gated, not fixed
Validated shutdown
Clean-side. Gated by cleaning and requalification on the way back in.
-
05 minutes
Hot tie-in
Minutes long, rehearsed dry beforehand, because there is no second attempt.
Column width is drawn to the length of the window.
The window is the outage, not the work. So the scope RONCO writes pushes everything that does not need the line down outside it — panels built and point-to-point tested on the bench, containment installed live, cable pulled, meggered and tagged, terminations dressed and waiting. What is left inside is only what cannot be done any other way, and Ahavah executes to that sequence.
What comes back
in 48 hours
A marked-up layout gets you a budget number. It comes back as four things, not a figure in an email.
-
5.01
Scope narrative
In plain sentences, saying what we read the drawings to mean.
-
5.02
Inclusions & exclusions
Line by line, covering the six interface items above.
-
5.03
Assumptions & allowances
Every place the drawing was silent and we picked a value, with the value shown.
-
5.04
Indicative schedule
Naming its own predecessor conditions: anchor bolts set and grouted, pad cured, penetrations cast, tray elevations reconciled against process and duct.
A budget number becomes a firm number when six things land.
- A load list or panel schedule.
- Available fault current, and where it came from.
- Equipment cut sheets with terminal counts.
- The area classification for every room the work passes through.
- Routing constraints — ceiling height, existing congestion, what the ductwork already claimed.
- And the window it has to fit.
Send drawings.
Get a scope,
a schedule
and a number.
No discovery call required to get started — a marked-up layout is enough.