About Ignition 2027 Early Access

Same, I'm very excited about it. Spoke to our sysadmin to give him a heads up so we can start experimenting with it as soon as it comes out. I'm also planning to try it with a local model on my DGX Spark too

Was at ICC. Excited to get my hands on Ignition 2027. Def following this thread.

I saw its functionality at ICC 2026, and it was amazing.

1 Like

they say great minds think alike... I just wish I wouldn't have went with the name catalyst for my project a month ago!

1 Like

You should at least provide a link to whatever resource you are talking about. Catalyst does not appear to be very unique name in the software world. :upside_down_face:

1 Like

If you are talking about a link to my software it’s proprietary to my company. It uses ignition though so I imagine it will cause confusion in my company in the future (at-least to our controls department)

Anyone else get the feeling the old designer staging/publish workflow might make a reappearance?

I originally thought the 8.3 Gateway config resource backup feature would adopt the same functionality …

Also perhaps Catalyst is the Jev to Ignition?

I think someone asked about this in one of the sessions and the answer was a pretty unambiguous "no, it's not coming back".

2 Likes

This will have onscreen keyboard popup for perspective on login page and on all numeric input object ?

3 Likes

I would love to Beta test this in my lab with my students.

Do real projects. You'll find a lot more of the bugs if you're doing real projects even if they aren't production ones.

2 Likes

This is exciting! After getting core and gold certs, I am heavy internal developer at my org. Can't wait to see what's in store! I'm in Ignition every single day. For the last 2 years.

2 Likes

Any updates on the date that the beta will launch? Cant wait to get our hands on it

1 Like

Yes, within Perspective Workstation. the On Screen Keyboard uses the Keyboard Layout resources in the designer that vision clients were already using. The reason its in workstation is so it persists on all navigation, including external IDPs.

@hunterdg

Anyone else get the feeling the old designer staging/publish workflow might make a reappearance?

I don't expect this exactly, but we are definitely looking at better mechanisms to review and audit changes which are applied by agents within the Designer.

@hunterdg

Also perhaps Catalyst is the Jev to Ignition?

well, I know this is a bit of a non-question, so Ill give an answer for something you never asked. Jev has a lot of buzz right now, and some of us internally see some really nice utility here, but we haven't come up with a concrete plan for something like this yet... but its very appealing.

Excited for a Designer MCP module. Hoping it comes out soon.

There are a number of things that have to happen here to make this a reality, but its high on our TODO list!

4 Likes

I'm really excited about the perspective workstation OSK. That was such a needed feature...

I do a lot of SCADA migrations for touchscreen apps written on legacy platforms. The lack of an OSK has been a challenge to implementing replacement SCADAs in Perspective.

yeah Workstation did have support for "OS" OSKs, however it was pretty terrible and riddled with issues. this is a first-party solution which works the same, always, on any page, and on any OS, so its a big improvement

3 Likes

Will it prevent the OS's OSK from displaying so that there's not conflicting keyboards when a user tries to use it?

Will it prevent the OS's OSK from displaying so that there's not conflicting keyboards when a user tries to use it?

Currently this is defined at the OS level, and typically All or Nothing. I am hoping to have a section in the user manual about this. However, I have a proof of concept and ticket to allow us to work around this and we will see if it makes it into the 2027.2.0 release. If so, you would be able to leave the OS OSK enabled globally and it works in other parts of the system, and ours just opts-out of it when using our packaged OSK.

2 Likes

I'm really looking forward to Ignition 2027!

I'm a SCADA engineer in South Korea, mainly working on EPMS and BMS projects for data centers.

I'm especially interested in Ignition Catalyst and how AI-assisted development could improve workflows involving large numbers of tags, UDTs, and Perspective views.

I would also love to see improvements in bulk tag management, reusable components, and automated device mapping for large-scale SCADA projects.

Looking forward to trying the beta and seeing what's coming next. Great work, Inductive Automation team!

Great to see the sneak peek of Ignition 2027! Having witnessed the demonstration of Ignition 2027’s AI capabilities at ICC, I highly anticipate that it will significantly reduce our future development timelines and improve the consistency of our development outcomes.

However, as we look into adopting the Catalyst Assistant within the Designer, I have a few questions regarding its system impact. Specifically, how will the collection of project context information and the processing of AI requests/responses affect JVM memory utilization and overall response performance? We are particularly interested in understanding the extent of this impact within large-scale projects.

Looking forward to hearing thoughts from the community or the IA team!