Gateway architecture

Design and build of the Ignition platform itself: one gateway or many.

  • New gateway design, installation, and commissioning
  • Redundant gateway pairs (master and backup) with failover tests
  • Gateway network and remote tag providers for multi-site systems
  • Enterprise Administration Module (EAM) for central management of many gateways
  • Module, license, and database connection setup
  • Container deployments with Docker and Kubernetes

Ver: 8.1 / 8.3

Perspective and Vision

Operator and supervisor screens built on standard templates.

  • UDT-based screen templates for standard equipment
  • Responsive Perspective views for desktop, tablet, and phone
  • Vision client maintenance and extension
  • Alarm status, alarm journal, and notification pipelines (email, SMS, voice)
  • Navigation, user roles, and security zones
  • High-performance screen design with clear alarm and state colors

Ver: 8.1 / 8.3

Historian and databases

Store the right data at the right rate, and query it quickly.

  • Tag Historian configuration and tuning in 8.1
  • Core Historian and SQL Historian configuration in 8.3
  • Microsoft SQL Server, MySQL, PostgreSQL, and Oracle connections
  • Transaction groups, named queries, and stored procedures
  • Reporting Module: scheduled PDF and email reports
  • Retention, partitioning, and slow-query analysis

Ver: 8.1 / 8.3

MES functions

Production data functions built with native Ignition resources.

  • OEE: availability, performance, and quality by line and shift
  • Downtime tracking with reason codes and operator entry
  • Traceability and genealogy by serial number or lot
  • Barcode and label printing from Ignition
  • Production counts, shift reports, and dashboards
  • Recipe and setpoint management

Ver: 8.1 / 8.3

Integration and APIs

Connect the plant floor to devices, databases, and business systems.

  • ERP integration through database tables, REST APIs, or files
  • REST API endpoints (WebDev module) and outbound HTTP calls with OAuth 2.0
  • OPC UA server and client connections
  • PLC drivers: Allen-Bradley, Siemens, Modbus, and others
  • MQTT and Sparkplug B data collection
  • Event Streams and Kafka pipelines in 8.3

Ver: 8.1 / 8.3

Standards and DevOps

Control change across gateways, environments, and people.

  • Git version control of projects and gateway configuration (8.3 file-based configuration)
  • Deployment modes for development, staging, and production in 8.3
  • Gateway REST API for configuration automation in 8.3
  • Secrets management for passwords and keys in 8.3
  • Project inheritance and shared script libraries
  • Written standards for tags, UDTs, views, and naming

Ver: 8.3 / partial 8.1

Scripting and logic

Python (Jython) code that is readable, tested, and fast.

  • Gateway event, tag change, timer, and message handler scripts
  • Project script libraries with clear function boundaries
  • Sequential Function Charts for step-based processes
  • Performance fixes for slow scripts and blocked threads
  • Code review of existing scripts

Ver: 8.1 / 8.3

Migration to Ignition

Move from an older platform with a phased plan and a clear cutover.

  • FactoryTalk View, Wonderware (AVEVA) InTouch, and GE iFIX to Ignition
  • Vision to Perspective conversion
  • Sepasoft MES modules to native Ignition resources
  • Ignition 8.1 to 8.3 upgrades (see the 8.3 page)
  • Tag database, screen, alarm, and history migration

Ver: 8.1 / 8.3

Gateway Health Check

A fixed-scope first engagement. You send a gateway backup, and we review it together with a remote session on the live system. You get a written report with findings ranked by risk, and a recommended fix for each one.

Scope

  • Gateway configuration, modules, licensing, and versions
  • Memory, thread, and database load under normal production
  • Tag structure, UDTs, alarms, and history settings
  • Scripts: errors, blocking calls, and slow queries
  • Security: users, roles, TLS, and backups
Request a Health Check

Ways to work together

Project

A defined scope, from architecture to commissioning and handover. Best for new systems, upgrades, and migrations.

Engineering support

Ignition engineering inside your project, to your standards and your schedule. Best when your team needs more capacity.

Support retainer

A monthly block of hours for changes, fixes, and health checks. Best for systems that are in production.

Health Check

A fixed-scope review with a written report. Best as a first step with a new system or a new partner.

Questions

Do you work remotely?

Yes. Most development work is remote, through the remote access method that your IT policy permits (for example, VPN or remote desktop). On-site work is available within 300 miles of Grand Rapids, Michigan, for commissioning, startup, and workshops.

Which Ignition versions do you support?

Ignition 8.1 and 8.3. If your system uses an older version, the first step is an upgrade assessment.

Do you support Sepasoft modules?

Only for migration. Bosdale moves MES functions from Sepasoft modules to native Ignition resources: UDTs, database tables, scripts, and Perspective views.

Can you work on a system that another integrator built?

Yes. A Gateway Health Check is the recommended start, so that both sides know the condition of the system before the work begins.

What information helps with a quote?

Your Ignition version, the number of gateways, the devices and databases in use, what must change, and your target date. A gateway backup is useful, but it can come later.

Start a project

Describe your system and what must change. The reply comes by email.

Request a quote