Nuisance breaker tripping: separate the symptom from the mechanism
An open breaker is not a diagnosis. Thermal, magnetic, residual-current and electronic trips fail for different reasons — measurement names the mechanism.
Insights
Articles, guides and engineering notes — technical writing from the studio.
Harmonic distortion from nonlinear loads: heat, trips, and confused meters
Drives, LED drivers and IT supplies draw current in pulses. Harmonics heat neutrals and transformers, and a 60 Hz clamp can hide the thermal story.
Grounding investigation in commercial buildings: path, not a slogan
Earth resistance on a drawing is not a bonding path that can carry fault current and keep touch voltage low. Measure the path you actually have.
Electrical thermography as evidence, not a colourful gallery
A hot spot is a temperature difference under a named load and emissivity. The question is why it is hot and what fails next — not the prettiest palette.
UPS behaviour under the load you actually have
Ride-through, bypass and transfer follow the load shape you run. A factory resistor bank does not prove what the process will see in a sag.
Interpreting power-quality data: waveform first, flag second
Sag, swell, flicker and THD are labels on a capture. The job is to say which mechanism produced that shape — source, load, or the instrument setup.
Packet loss, latency and jitter: three numbers, three different jobs
Loss drops frames. Latency is path delay. Jitter is how that delay moves. Calling the network slow hides which of the three the process actually feels.
Intermittent network faults: the live path, not another cable certificate
A link that drops once a shift will pass a short certification. Errors, negotiation, power and the electrical room next door are the file — not a new cord.
EMI, SNR and communications: when the cable is a poor antenna
Signal-to-noise is why a link that certified last year throws errors beside a drive. Treat the electrical environment as part of the channel, not folklore.
OT and IT on industrial Ethernet: two definitions of “up”
IT counts tickets and pings. OT counts completed cycles. The same switch can satisfy one team and starve the other unless queues and ownership are written.
What Division 25 actually coordinates on a project
Division 25 is the integration spec: who owns points, networks, sequences and interfaces among mechanical, electrical and communications — not a second.
Division 25 versus Division 23: equipment versus operable control
Division 23 can specify a coil and a valve. Division 25 must say how that valve is commanded, proven, alarmed and handed to the operator — or the strip is the.
Building-automation network architecture: field, building, supervisory
A BAS is not one bus. Field trunks, building IP and supervisory servers differ in timing, security and ownership. Draw the layers before buying another gateway.
Coordinating BAS points and sequences before the panel lands
A points list without sequence ownership is a shopping list. A sequence without points is prose. Commissioning needs both, with a physical origin for every.
From sequence of operation to control architecture
A written sequence is intent. Architecture decides which controller executes which clause, what happens on network loss, and which alarm requires an operator.
BAS, OT and network coordination in a shared closet
Building automation, plant Ethernet and corporate IT often share a rack without sharing rules. The closet is an interface. Treat it as one, or the quietest.
When an engineering automation is worth building
If an engineer repeats the same transformation every week, a small tool can earn its keep. If the rule changes every job, a spreadsheet and a checklist stay.
Connecting engineering applications without a weekly spreadsheet
CAD, analysis and schedules rarely share a schema. A durable bridge names objects, units and identity. A CSV emailed every Friday is a process, not an.
Designing internal engineering utilities that stay beside the work
Internal tools fail when they impersonate a product: logins, dashboards, a second source of truth. They succeed next to the drawing or calculation, with a.
When the network problem is electrical
CRC on a switch is not always a cable. Sag, bonding, noise and a shared tray can raise a network ticket. Split the file: packets, then volts, then the coupling.
Engineering at system interfaces: where the drawing stops being true
Persistent faults live on a seam: power and control, OT and IT, Divisions 23 and 25, CAD and model. Name the seam, the owner and the test, or both sides look.
EE-Platform: an engineering system of record
Context, problem, approach, architecture, outcome: a studio platform that joined electrical workflows, documents and CAD outputs without inventing a second.
Context, problem, approach, architecture, outcome: keeping a power-system model and a CAD single-line on the same equipment identity, without a weekly manual.
Next
Have a technical problem that crosses systems?