Modern Solutions for Industrial Automation with No Ceilings

Icons help operators recognize actions, distinguish equipment states, and navigate an HMI. As a Perspective application grows, maintaining a consistent icon library becomes another part of managing the project. We developed the Icon Manager...

Industrial software is often expected to remain in service for years. During that time, equipment changes, production requirements evolve, new data sources are introduced, and different engineers may become responsible for maintaining the application. An application can work perfectly when commissioned and still be difficult to maintain. The difference often comes down to decisions made...

Connecting two systems is often the most visible milestone in an integration project. A PLC value appears in Ignition, an API returns a successful response, or an MQTT subscriber receives its first message. These are important milestones, but they establish only that communication works under the conditions tested. A successful data exchange is not the...

Modern industrial software platforms can do considerably more than display process values. Applications built with Ignition can communicate with PLCs, execute scripts, manage production workflows, query databases, and exchange information with enterprise systems. That flexibility is useful, but it also introduces an important architectural question: just because a supervisory application can perform a task, does...

Ignition offers two established visualization modules: Vision and Perspective. Both are capable of building industrial HMI and SCADA applications, but they take fundamentally different approaches to development and deployment. At No Ceilings, we’ve made a deliberate decision to use Ignition Perspective for all new visualization projects. We don’t take on new Vision development, but we...

An assembly station must do more than recognize a serial number. It needs permission to begin, an instruction appropriate to the unit, a way to execute that instruction, and a reliable means of returning the result to the manufacturing execution system (MES). This case study examines how an...

A medical equipment production program brought fabricated subassemblies into a main assembly line where a product traveled through multiple workstations on a guided cart for part of its route. The work at each station depended on the product, its order options, and the equipment available there. The instruction...

A bottle-closure manufacturer needed a consistent way to check production quality across multiple products and manufacturing locations. The work involved more than displaying a measured value beside a tolerance. Every result needed the right product, test, sampling definition, and location context so that operators could...

For an international oil and gas operator, getting operational data off a vessel was an integration challenge as much as a communications challenge. Ships carried several onboard systems, each with its own interface, while shore-side access depended on satellite connectivity at sea. The project...