Magic Software
Ignition Community Conference 2026 · Sacramento

Running Ignition? Come meet the Premier Integrator that now owns the whole stack, floor to ERP.

MartinCSI has been building on Ignition since the Firebrand days and commissioning controls, robotics, vision, and safety systems since 1993. In 2026 we joined Magic Software Americas, which means the same engineers who wire your panel can now hand clean, contextualized Ignition data to SAP, JD Edwards, Epicor, Infor, or an AI agent. This page is the longer version of what we'll tell you at the booth.

When

September 22–24, 2026

Where

Sacramento, California

Who

MartinCSI · the Magic Americas automation team

The credentials behind the booth

Ignition Premier Integrator2016 Ignition Firebrand AwardCSIA Certified since 2002Rockwell Automation Recognized SIAuthorized FANUC System IntegratorCognex Certified System IntegratorOpto 22 Certified PartnerMitsubishi Electric Diamond PartnerTÜV Rheinland Certified SafetyControl Engineering SI of the Year (2011)
Who We Are

A 30-year controls integrator. Now the industrial automation business unit of Magic Software Americas.

MartinCSI started in 1993 as a Plain City, Ohio controls shop and grew into a CSIA-certified systems integrator with more than 1,900 completed projects across automotive, food and beverage, chemical, packaging, glass and plastics, life sciences, and OEM machine builders. We earned Ignition Premier Integrator status the hard way: by shipping Ignition SCADA, HMI, and Perspective projects that plants actually run on.

In April 2026, Magic Software Americas and Axiom completed the acquisition of MartinCSI. Magic is the enterprise integration company behind Magic xpi, FactoryEye, and the Magic MCP, backed by a top-10 publicly listed IT services firm with 15,000+ professionals. For you, that means one team that owns the panel, the gateway, the ERP connector, and the data layer in between. Same engineers. Same project plan. One PO if you want it.

1993

Founded in Central Ohio

1,900+

Automation Projects Delivered

80%+

Of Business From Repeat Clients

15,000+

Professionals (Matrix + Magic)

MartinCSI
A business unit of
Matrix + Magic Americas
What We Do for Ignition Users

Four things that typically come up right after “we run Ignition.”

Most Ignition shops don't have an Ignition problem. They have a controls backlog, an ERP that can't see the floor, or a leadership team asking what AI is supposed to do with all this data. Here's what we bring to each.

Build, upgrade, and scale Ignition

Greenfield Ignition SCADA and HMI, Perspective dashboards that run on whatever screens the plant already has, Edge gateways at the line, and 8.3 migrations that put gateway configuration in Git where it belongs. Premier Integrator status means we've done this at scale, not once.

  • Ignition 8.3 file-based config, Docker-first dev, and multi-site GitOps
  • OPC UA, MQTT with Sparkplug B, Kepware, and native Allen-Bradley and Siemens drivers
  • Tag Historian, alarming, and reporting designed around the plant's uptime windows
Read the IT/OT playbook

Commission the physical layer that makes data exist

Ignition is only as good as what's feeding it. MartinCSI engineers write the PLC code, build the panels, integrate the robots and vision systems, and certify the safety circuits. Rockwell, Siemens, Mitsubishi, Omron, FANUC, Cognex, Opto 22, AVEVA.

  • PLC programming, controls upgrades, motion, and control panel fabrication
  • Robotics and machine vision integration with TÜV-certified functional safety
  • Additive sensor layers (Opto 22 RIO) on legacy equipment, no control-system rewrite
See MartinCSI services

Get Ignition data into the ERP, and ERP context back to the floor

Magic xpi ships with 100+ connectors, including certified SAP, JD Edwards, and Epicor adapters. Job orders, BOMs, and delivery dates flow down to Ignition. Counts, downtime, quality, and OEE flow back up, validated and mapped, without a point-to-point script farm.

  • Bidirectional Ignition ↔ SAP / JDE / Epicor / Infor flows with retries and monitoring
  • MES, WMS, quality, and maintenance systems on the same integration plane
  • Loosely coupled, so ERP upgrades stop breaking plant integrations
See the OT-IT bridge offer

Put plant data in front of leaders and AI agents

FactoryEye layers ERP context on top of Ignition and historian data so OEE maps to job orders, cost, and delivery risk. The Magic MCP gives AI agents governed, real-time access to the connected landscape, so the plant question gets answered from live data instead of last week's export.

  • Operator-to-executive dashboards, one global manufacturer went 1 plant to 18 in 18 weeks
  • Secure, role-aware AI access to OT and ERP data together
  • From AI pilot purgatory to AI in operations
See FactoryEye
Why the Acquisition Matters to You

Ignition connects the floor. We now connect the floor to everything above it.

Every plant has a boundary between the OT network and corporate IT that nobody owns. The controls integrator stops at the gateway. The IT consultant stops at the DMZ. The integration between them gets handed to your team as a script, a flat file, or a project that never quite closes. Since joining Magic Americas, MartinCSI runs that boundary as one project, from the PLC through Ignition through Magic xpi to the ERP, and back.

See how the OT-IT bridge engagement works

What one team, end-to-end, actually means

  • Controls engineers who understand Ignition and Allen-Bradley, on the same project as architects who understand SAP and JD Edwards
  • Purdue Model segmentation, Dynics SDN, and ICS-aware security designed around real uptime windows
  • Magic xpi as the integration plane between Ignition and the enterprise, with validation, retries, and dashboards
  • Fixed-fee OT-IT assessment that ends in a real bill of materials and a real quote
  • No SI-versus-IT-consultant blame loop. One team. One accountable name on the audit.
Ignition 8.3

On 8.1 and wondering what 8.3 changes? Bring that question to the booth.

We've built our Ignition delivery practice around the 8.3 file-based model. Here's the short version of why it matters and what a migration looks like when a Premier Integrator runs it.

Config lives in files, so it lives in Git

Ignition 8.3 moved gateway configuration to the filesystem. That makes SCADA a first-class citizen in a real DevOps toolchain: branches, pull requests, CI validation on every commit, and a clean rollback story.

One repo, many gateways

Deployment Modes let a single repository drive dev, QA, and production gateways with environment-specific overrides. New plant? Clone the pattern instead of rebuilding it by hand.

Docker-first local development

Engineers build and test against containerized gateways with pre-loaded modules before anything touches a production line. Fewer surprises in the commissioning window.

Honest about the legacy side

FactoryTalk, AVEVA, iFIX, Citect, and pre-8.3 Ignition can't be version-controlled natively. We'll tell you that, and show you the overlay or integration-layer path that actually works.

Proof in Production

Plants you'll recognize. Problems you've had.

These aren't slideware. When we meet, ask us to put you on the phone with one of them. We do that regularly.

Ignition Firebrand Award

We've been part of this community for a long time.

In 2016, Inductive Automation recognized MartinCSI with an Ignition Firebrand Award for using Ignition to build a realistic training simulation of a water purification system used by the United States Army. Not a dashboard. A simulator that had to behave like the real equipment so soldiers could train on it safely.

Ten years and a Premier Integrator badge later, the same instinct still drives the work: use Ignition for what it's actually good at, and don't stop at the obvious.

2016

Firebrand Award

2023

Premier Integrator

2002

CSIA Certified

1993

Founded

What the Meeting Looks Like

No pitch deck. No SDR hand-off. Just the conversation about your plant you actually came to Sacramento for.

01

30 minutes, no slides

At the show or the week after. A working session with a controls engineer or integration architect who has actually commissioned this stuff, not an SDR working off a script. Bring one real line, one real problem.

02

Scope it live

We'll walk through the gateways, PLCs, and enterprise systems in play, the 8.3 or ERP-integration gotchas we already know about, and what a realistic first phase looks like.

03

A written architecture review

ICC attendees get a complimentary architecture review: what we'd build, in what order, with rough effort. Yours to keep, no commitment.

ICC 2026 · Sept 22–24 · Sacramento

Let's lock in time before the show fills up.

Tell us whether you want to talk controls and Ignition, or getting Ignition data into the enterprise, and we'll route you straight to the right calendar. Pick a slot during ICC or the week after. No form chains, no SDR queue.

  • Instantly routed to the right person on the MartinCSI / Magic team
  • Complimentary architecture review for ICC attendees
  • Zero pressure. Plenty of plants take multiple calls before deciding.

Ignition Community Conference 2026

Book your meeting

Pick a topic and we'll hand you straight to the right calendar. No waiting, no form chains.

What do you want to talk about?

We'll route you to the right person on our team.

Opens the calendar in a new tab. 30-minute meeting, no commitment.

Prefer email? info@magicsoftware.com Mention ICC 2026 and we'll route it to the MartinCSI team.