Avoiding Improvisation and Unnecessary Costs

Every building project — whether a new design or an active construction — depends on a solid conceptualization and sizing phase for its systems. Architects and contractors routinely apply this discipline to traditional trades: power supply, lighting, HVAC, pumping, forced ventilation, fire protection, and similar "core" subsystems.

The same rigor rarely extends to what project managers loosely call "technology" — what we at Innotica call integration, or simply building management. That is changing. Builders are increasingly aware that they need documentation spelling out the minimum integration and management requirements each subsystem must satisfy.

In practice, most buildings go up without that documentation. The project team is left to improvise, and the improvisation usually takes one of two forms: purchasing the proprietary application bundled with each vendor's equipment (HVAC controls, energy metering, lighting, elevators, and so on), or engaging a large multinational manufacturer to supply an end-to-end solution.

The first path leaves the owner with a collection of isolated systems running on separate platforms — making coordinated action, cross-system optimization, and meaningful efficiency gains virtually impossible.

The second path typically means proprietary technology locked to a single vendor's ecosystem. The integration project is designed around that vendor's products, with the practical effect of binding the owner to that vendor's maintenance contracts for the entire life of the building.

Cost Overruns and Wasted Time

Isolated systems create duplicate costs and make integrated building management far harder than it needs to be.

Building supervision and control on a foundation of isolated systems will always cost more than a unified automation and control network. License and server costs can double — and worse, the resulting applications operate in complete silos.

Without an integrated data layer, there is no basis for a holistic assessment of the facility. Without that assessment, there is no reliable basis for decisions aimed at maximizing efficiency.

The cost problem compounds when a specific component is missing from the procurement scope and the gap only surfaces just before — or during — installation. Vendors recognize urgency. Emergency procurement means elevated prices that planned, competitive purchasing would have avoided.

The technology lead or project manager must be able to verify that every proposed component meets the performance expectations set by each engineering discipline. At the same time, both the placement of electronic instrumentation and the communication ports or gateways must be accounted for, so that every piece of equipment can be brought onto the facility's central management network.

That network must monitor and control every active system in the building — capturing variables and signals from each subsystem and triggering actions in others — while alerting operations and maintenance staff to relevant events.

Why an Integration and Control Network Matters

The integration, automation, and control network must be designed around open technologies, so the owner is never locked into a single product brand. The engineer responsible for the design needs a holistic view of the entire facility. Even without dictating technical choices to individual trade designers, this engineer must define the minimum requirements each vendor must meet in order to guarantee efficient management of the complete installation.

The design project produces the reference document the project manager needs: a clear statement of what to demand from each specialist or supplier, always viewed through the lens of integration and management.

Civil infrastructure — conduit runs and control panel enclosures — must also be sized at the design stage with the necessary provisions for integration and control. The critical principle throughout is that the network can be commissioned immediately or phased in over time, but the building must be ready for it from day one.

Service Phases and Deliverables

The two service phases structure the entire design of the automation and control network.

The design service unfolds in two distinct phases. Phase I provides advisory support to the builder, establishing the guidelines that will be passed to each engineering discipline responsible for designing or supplying their subsystem's equipment. Phase II uses the outputs of those individual discipline projects — and the considerations established in Phase I — to produce the full automation and control network design.

Phase I

Phase I requires active participation from the construction company: specific decisions, targeted procurement actions, and coordinated meetings with third-party firms. The guidelines produced in this phase direct each discipline team as they develop their individual project documents.

Phase I deliverable:

• Descriptive requirements report with supporting diagrams.

Phase II

Phase II produces the detailed design: the location of every network component, all conduit routing, and the placement of control panels. It must document the technologies to be used, the responsibility matrix, and the full functional scope of the supervision and control platform.

The following discipline projects are required as inputs for Phase II:

• Electrical project
• Lighting project
• HVAC project
• Forced ventilation project
• Plumbing and sanitary systems project
• Elevator supply project
• Emergency power project (generator)
• Telecommunications project (optional)
• CCTV project (optional)
• Any additional systems to be integrated or monitored (optional)

Every decision made in this phase must be captured in documentation that explains each solution in detail, always keeping the Phase I requirements in view. The Phase II deliverables are:

• Descriptive report
• Technical specifications
• Pre-installation drawings
• General network diagrams
• Control list and responsibility matrix
• Cost estimate (broken down by solution, so the cost of implementing each designed function can be evaluated independently)

The Owner's Decision

With a complete design in hand, management can plan a phased network rollout aligned with the project's business model.

With the full design package available, the project management team has everything needed to plan which portions of the network to activate immediately and which to phase in over time — always in line with the owner's business model for the building.

Buildings have long service lives. Their systems must be designed to serve both current requirements and future ones. Engaging integration and control specialists early is the most reliable way to avoid unnecessary expenditure down the road.

For this purpose, Innotica's team includes professionals certified by the leading international organizations in building automation and control: LonMark International and the KNX Association. Sustainability expertise is equally important: the U.S. Green Building Council LEED (Leadership in Energy and Environmental Design) certification framework provides detailed recommendations and a comprehensive project review aimed at ensuring energy efficiency and environmental protection.

At INNOTICA you will find engineers with extensive experience in this type of advisory work, certified by each of these international organizations, ready to support your project on the ground or remotely.

To discuss a network design for your project — anywhere in the region — reach us at info@innotica.com.ve or by phone at +58 212-6386541.

Carlos Dobobuto