WideQuick Modular Framework¶

Every HMI and SCADA project asks the same questions:

• How do you handle alarms?
• How does navigation work? Where does history live?
• How do operators log actions?

The answers rarely change, but most integrators rebuild them from scratch, project after project.

WideQuick MOD is Kentima's answer to that problem.

Since the early 2000s Kentima has built the motor behind powerful HMI and SCADA systems across industries: building management, water and wastewater treatment, process and batch. In WideQuick MOD, Kentima extracted what is universal and made it reusable. The result is a structured project foundation that ships with production-ready modules for the features every system needs, while staying fully open for system integrators to configure, extend, and tailor to any customer requirement.

The framework does not constrain what you build. It eliminates the work you should never have had to do twice.

A modular architecture¶

WideQuick MOD is built on a single idea: every feature is an independent module that you include only if you need it. The core application provides the runtime, navigation, user management, and data layer. Everything else is optional and additive.

The diagram below shows how the full stack fits together: from the WideQuick HMI/SCADA platform at the base, through WideQuick MOD and its module library, up to the concept applications built on top.

Start at the bottom. WideQuick HMI/SCADA is the platform layer: the runtime, graphical engine, communication protocols, and core capabilities like alarms, history, and user management. This is what every WideQuick project runs on.

One layer up sits WideQuick MOD. It adds a structured project model on top of WideQuick and a library of pre-built modules: alarms, maintenance, dashboards, history, navigation, and more. Integrators pick what the project needs and leave out the rest.

At the top are the concept applications, BMS and WWT. These are not separate products. They are pre-configured implementations of WideQuick MOD, built for a specific industry, with an opinionated module selection and project structure already in place.

The top tier is optional. Many projects run directly on WideQuick MOD without ever touching BMS or WWT. If your industry, customer, or project scope does not fit a concept application, build straight on MOD and assemble exactly the modules you need.

You only ship what the project needs. A simple process overview carries none of the weight of reporting engines, maintenance schedulers, or alarm-sender configuration. A complex multi-site installation can pull in every available module without any structural changes to the project.

Scope is a deliberate choice. Not an accident of what happened to be included in a starting template.

Many industries, one framework¶

The same framework runs across fundamentally different application domains. Building management systems track HVAC, access control, and energy. Water and wastewater installations monitor treatment processes, pump stations, and alarms. Batch and process industry applications manage recipes, production logging, and operator workflows.

What these have in common is that they are all built from the same WideQuick MOD foundation, with the same WideQuick Designer® toolchain, the same module library, and the same deployment model. The domain-specific logic lives in configuration and module selection, not in a different product.

This matters for integrators who work across industries: the knowledge, tooling, and project structure transfer directly from one vertical to the next.

Concept applications¶

Building Management System (BMS) and Water & Wastewater Treatment (WWT) are concept applications: complete, pre-structured implementations of WideQuick MOD targeted at specific industries. They ship with an opinionated module selection, navigation structure, and system views that reflect the typical requirements of that domain.

They are starting points, not constraints. An integrator can adopt a concept application as-is, extend it with additional modules, or use it as a reference when building a custom project from the base framework.

Many successful deployments never use a concept application at all. Batch production, food and beverage, and general process industry projects routinely run directly on WideQuick MOD with a custom module selection that fits the project exactly.

Module independence¶

Every module in the framework is independent. There are no hidden dependencies between, for example, the Calendar module and the Alarm module. Each can be included or excluded without affecting the others.

For a system integrator this means the delivered application can be scoped precisely to what the end customer needs. A smaller installation might run with Alarms, History, and a Dashboard. A larger one adds Maintenance scheduling, Reports, and Maps. Neither project requires workarounds or stub implementations for the features that were left out.

The practical workflow is to start from the template application, include the modules that are relevant, and remove the rest. What remains is a clean, purposeful application with no dead views or unused configuration.