APPLICATION BUILDER FOR INDUSTRIAL AUTOMATION
A control system development platform is provided. The platform includes a shell component adapted to support development of a control systems application. An abstract model is associated with the shell component to facilitate development of the control systems applications.
1 . A control system development platform, comprising:
a shell component adapted with an abstract model to support development of a control systems application; and
a core component adapted to the shell component, the core component controls rights, security, or events processed by the control systems application.
2 . The system of claim 1 , the rights are employed to control access of plug-ins to an industrial application or to application data.
3 . The system of claim 1 , the rights control a set of features that are exposed to one or more other components, plug-ins, or functions of a control system.
4 . The system of claim 1 , the rights control access between plug-ins.
5 . The system of claim 1 , a namespace that is associated with a license manager, a roles manager, or a feature matrix.
6 . The system of claim 1 , further comprising an event logger that captures statements that are optionally linked with deployed code.
7 . The system of claim 6 , further comprising a log filter that is configured to avoid logging events.
8 . The system of claim 6 , further comprising a framework component to write events to multiple outputs.
9 . The system of claim 8 , the outputs include a database, a remote sink, a web service, a text file, or a target type.
10 . The system of claim 8 , the framework component includes a hierarchical logging set, where each component of the set includes its own logging component to capture events from members of a hierarchy.
11 . The system of claim 8 , the framework is configured programmatically.
12 . The system of claim 1 , the security is associated with one or more role mappings.
13 . The system of claim 12 , the role mappings are dynamic and based on business rules, process context, or user role.
14 . The system of claim 1 , the security is based on thread principles to support rich-client authorizations.
15 . The system of claim 1 , the security includes a logging component to record access attempts, policy violations, undefined user role memberships, or exceptions.
16 . A control system development method, comprising:
adapting a shell with at least one abstract model to support development of a control systems application; and
providing a core that controls component rights, security access, or logging events processed by the control systems application.
17 . The method of claim 16 , the abstract automation model is associated with abstract automation model or a concrete automation model.
18 . The method of claim 16 , further comprising filtering the logging events to prevent unwanted events from being recorded.
19 . The method of claim 16 , further comprising automatically auditing components to determine whether security violations have occurred.
20 . A control system development method, comprising:
means for interfacing to at least one abstract model to support development of a control systems application; and
means for controlling plug-in access to the control systems application.