Software architecture for control systems
Should you develop a framework for software, for your control system project?
Generally, no. For one application, or project, use what is already established and tested inside your organization, even if it is not ideal for your application.
Because time spent on one particular project will be less, when focusing effort on this application, rather than coding support functionality and framework that is not likely to be reused in other projects anyway.
A framework must be planned properly, taking into account specific needs of the organizations software development. And consider what should be developed in-house, or sourced from outside. This was the concept of the CDP control development platform software, to be a framework that other companies could use to develop their own applications.
A larger company, with large teams of developers, can choose to make the framework in-house. To have full control of all code, and to tailor the framework to their requirements, optimize workflow and development methodology for the organization.
Would I make it again?
Back in the days, I created CDP, a software platform for control systems. Do mind, several other developers also participated, this evolved into a larger project.
Would I make this today?
Not in the same way. I would focus on system specification, less on making and coding parts of the system. I would also do the system architecture a bit different, though the basics of a message and component based structure, is how to it.