Kenexis - Functional Safety Podcast
Jun 16, 2026 · 45 min · 11 segments
At the risk of saving you from hours of unnecessary work, in our latest episode, we tackle a surprisingly common habit: trying to do application program design and implementation at the exact same…
No entities detected.
All right, now that we've gotten through the application program design, we can get into the application program implementation.
It took us a couple, did it take us three weeks or two weeks? Two to three weeks to get through application program design.
And theoretically, we should have written a bunch of documentation, paper, databases, free form charts, whatever it is you're using to do your documentation these days, not necessarily pen and paper.
But after we do our design, now we're in the implementation phase where we make that design tangible by making it code.
So the executable code that's gonna be running in the safety PLC is what we are generating right now.
Typically that means we're gonna be doing a lot of work in the maintenance and engineering interface tool that we use to generate that application code.
which then gets turned into executable or object code and then uploaded into the actual processor itself.
So in theory, We put together a big long plan about how we're gonna write code and then we're gonna write the code.
Now, in a lot of cases, we're gonna go pretty direct where the most common approach is I'm gonna just start writing code directly off of my cause and effect diagram.
And as we travel into the future, more and more of this is going to get automated.
I mean, if you think that AI coding is going to be limited to people creating web pages, let me assure you that it is not.
All right, now that we've gotten through the application program design, we can get into the application program implementation.
It took us a couple, did it take us three weeks or two weeks? Two to three weeks to get through application program design.
And theoretically, we should have written a bunch of documentation, paper, databases, free form charts, whatever it is you're using to do your documentation these days, not necessarily pen and paper.
But after we do our design, now we're in the implementation phase where we make that design tangible by making it code.
So the executable code that's gonna be running in the safety PLC is what we are generating right now.
Typically that means we're gonna be doing a lot of work in the maintenance and engineering interface tool that we use to generate that application code.
which then gets turned into executable or object code and then uploaded into the actual processor itself.
So in theory, We put together a big long plan about how we're gonna write code and then we're gonna write the code.
Now, in a lot of cases, we're gonna go pretty direct where the most common approach is I'm gonna just start writing code directly off of my cause and effect diagram.
And as we travel into the future, more and more of this is going to get automated.
I mean, if you think that AI coding is going to be limited to people creating web pages, let me assure you that it is not.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.