Niagara 4 software development
Custom Java modules and drivers built natively for the Niagara palette — lean enough for JACE hardware, robust enough for Supervisors.
Niagara 4 · Native Java · Open protocols
Niagara 4 engineering for the problems the standard palette can’t solve
We build custom Java modules and drivers for the Niagara Framework, connect equipment the vendor calls unsupported, and turn station data into energy savings you can verify.
Field → Station → Insight
Field devices
BACnetModbusM-BusSerial
Niagara 4 station
Custom driversTaggingHistories
Insight
DashboardsM&VCloud APIs
- Custom modules shipped
- 50+
- Protocols integrated
- 12+
- Technical response time
- 24h
- Typical energy savings
- 15–30%
What we do
Three services, one platform
Everything we build runs inside — or connects to — the Niagara Framework, so it works with the station, the tools and the people you already have.
System integration
Bridging disparate protocols into one system — from 30-year-old serial equipment to PLCs and cloud data platforms.
Energy analytics & M&V
Turning station histories into financial metrics: IPMVP-aligned measurement and verification, fault detection and ESG-ready reporting.
Sound familiar?
Problems we’re called in to solve
Most of our projects start with one of these.
A device the vendor calls “unsupported”
Plant-critical equipment with an undocumented protocol and no gateway. If it communicates at all, we can usually decode it and bring it into Niagara as native points.
Wire-sheet logic that has outgrown the JACE
The same logic copied across hundreds of points, a station that keeps getting slower, and a fix that means editing every copy. A compiled module replaces all of it.
Energy numbers nobody trusts
Dashboards that disagree with the utility bill and savings claims that fall apart under questioning. The fix starts with tagging and a proper baseline.
Forty sites and no single dataset
Every site has its own station and head office wants one live view. We stream normalised, tagged data from each station into one place.
The foundation
Built on the Niagara Framework
Every solution we ship runs on Tridium’s open platform, from field protocols to cloud analytics. Niagara normalises data from any protocol into one object model — and because it can be extended in native Java, custom work behaves like a first-class part of the framework.
See how the layers fit together, and where our engineering adds value at each one.
L4
Enterprise & cloudDashboards, analytics, CMMS, data lakes
We analyseL3
Automation platformSupervisor & stations: alarms, histories, tagging
We extendL2
Controllers & edgeJACEs and field controllers running local loops
We connectL1
Field devicesAHUs, chillers, meters, sensors, actuators
We connectProcess
From site survey to signed module
A disciplined engineering lifecycle — every deliverable is tested in Workbench before it touches your station.
Discovery
Site survey, protocol analysis and station audit to define the real technical scope.
Architecture
Module design, point schemas and tagging strategy agreed before a line of code is written.
Engineering
Native Java development with versioned builds and continuous Workbench testing.
Deployment
Signed module delivery, commissioning support and documentation handover.
Why Fiabtec
Built by engineers, not resellers
Many integrators stop where the standard palette ends. We start there. Our team writes native Baja code, works with undocumented protocols and ships compiled, signed modules you actually own.
- Native Baja expertiseCompiled modules, not wire-sheet workarounds — lower CPU load and protected IP.
- Protocol depthSerial, IP and message-bus protocols handled at the frame level when needed.
- Data you can auditSemantic tagging (Haystack / Brick) so every analytics number is traceable.
- Long-term supportVersioned releases and upgrade paths across Niagara maintenance builds.
@NiagaraType
@NiagaraProperty(name = "status", type = "BStatus",
defaultValue = "BStatus.ok")
public class BFiabtecService extends BAbstractService {
public void doProcess() {
// Compiled logic, sized for JACE hardware
}
}Where we work
Industries we serve
Different buildings, the same need: equipment that talks, and data you can act on.
Commercial buildings
Mixed-vendor systems, tenant billing and portfolio reporting.
Industrial plants
PLCs, process equipment and utilities brought into one view.
Data centers
Power and cooling monitored together, efficiency tracked continuously.
Healthcare
Critical environments where conditions are requirements, not comfort.
Campuses
Dozens of buildings and decades of equipment, one operations team.
Energy & utilities
Metering at scale, generation assets and demand management.
Insights
Guides from our engineers
Practical, vendor-neutral writing on Niagara development, integration and energy verification.
Software development
Wire sheet or custom module? When native Java makes sense in Niagara 4
The wire sheet is the right tool for most station logic. Here is how to recognise the cases where a compiled Niagara 4 module is faster, safer and cheaper to maintain — and the cases where it isn’t.
4 min read
System integration
Integrating undocumented legacy equipment into Niagara 4
The manufacturer is gone, the manual is missing, and the equipment still runs the plant. A step-by-step look at how undocumented devices become native Niagara points — without putting operations at risk.
4 min read
Energy analytics
IPMVP options A to D, explained for building automation data
How the four IPMVP options work, which one fits your project, and what your Niagara station needs to collect for savings figures that survive an audit.
4 min read
Have a problem the standard palette can’t solve?
Describe your station, protocol or data challenge — an engineer replies within 24 hours.