Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/20—Software design
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B19/00—Programme-control systems
  • G05B19/02—Programme-control systems electric
  • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
  • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
  • G05B19/0426—Programming the control sequence
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B2219/00—Program-control systems
  • G05B2219/20—Pc systems
  • G05B2219/24—Pc safety
  • G05B2219/24168—Identify connected programmer to allow control, program entry
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B2219/00—Program-control systems
  • G05B2219/20—Pc systems
  • G05B2219/24—Pc safety
  • G05B2219/24169—Identification of last person who changed program

Definitions

• the invention relates to generation of audit trails particularly for production environments where compliance with auditing standards and/or policies is required.
• a central production system connected to distributed controllers for machines such as a machine vision system, a placement machine, and a reflow oven.
• distributed controllers for machines such as a machine vision system, a placement machine, and a reflow oven.
• Each of the distributed controllers performs machine control operations as part of which data is logged concerning parameter change events.
• One such event may for example be change-over from production of one batch to another, or a change in a vessel temperature.
• a code generation module scanning each linked control in turn and automatically providing capture code for, during runtime, causing an audit log update to be made in response to a user input;
• the hidden window components operate to create an access control database structure having a record for each window, for each control, and for each of a plurality of user groups.
• the method comprises the further step of, after compiling in step (g), populating the access control database structure with user access permissions on a per-control and per-window basis.
• step (e) comprises the code generation module selecting pre-stored capture code segments according to nature of the control or window.
• the pre-stored segments are indexed on events.
• the events are user input categories.
• the events include text box change, drop down list check, drop down list change, window commit button press, and check box activation.
• each hidden window component comprises a database logging function
• the capture code for a linked control includes code to call said function when it detects a user input in runtime.
• said function includes code to, in turn, instruct an external program to perform a database write to complete the update.
• the external program is a dynamic linked library program.
• the method comprises the additional step of linking the application to an audit log database using an object linking and embedding database mechanism.
• the invention provides a control system comprising machine controllers for production machines, application software code for executing production control logic, an access control database, and an audit trail logging database, wherein the system further comprises: security software comprising capture code for automatically capturing operator input change events, wherein the capture code is embedded within the application code, and it calls a separate program to perform a logging database update so that low-level database parameters are transparent to the embedded capture code.
• the security software allows the access control database to be updated during run-time with permissions on a user group basis.
• the permissions are also set for each user data/instruction input control, and for each window containing controls.
• the security software comprises a hidden window component associated with each application input window, the hidden window component being hidden from users during runtime, and being linked with capture code segments.
• each hidden window component comprises a logging function
• linked capture code segments call said logging function in real time when an input is detected.
• the logging function calls an external logging function to perform the logging database update.
• the external logging program is a dynamic linked library program.
• FIG. 1 is a block diagram showing a production control system of the invention
• Fig. 2 is a diagram showing a controller of the system.
• Fig. 3 is diagram showing relationship between hidden window components and application controls;
• Fig. 4 shows a screen shot of representations of a component and linked controls
• Fig. 5 is diagram illustrating structure of an access control database
• Fig. 6 is a diagram showing how capture code is generated and used.
• a production control system 1 comprises a central production controller 2 having a primary production control database 3.
• the controller 2 is connected to workstations 3 in a local area network. It is also connected to distributed production machine controllers including a solder paste reflow oven controller 6, a machine vision system controller 7, and a placement machine controller 8.
• distributed production machine controllers including a solder paste reflow oven controller 6, a machine vision system controller 7, and a placement machine controller 8.
• the controller 2 comprises: a hardware layer 20 linked to a camera 21, an audit log database 22, an access control database 23, a PLC 24, and a network channel 25 for communication with the machine controllers 6, 7, and 8; an operating system 30; a vision toolset 31 for camera control and data capture; a PLC interface 32 for control of the PLC 24 and data capture from it;
• the application software 34 manages the functions 31, 32, and 33 together for synchronised real time production control. For example it ensures that tlie PLC 24 controls the motion system in synchronisation with the camera 21 for effective image acquisition.
• the security software 35 is integrated with the application software 34.
• the application software 34 is developed in a conventional manner without security considerations.
• development of this software is complete, a connection between the application and the audit log database 22 is established, the security software 35 is developed and integrated in, and the database 23 developed.
• the connection to the audit log database 22 is established using an object linking and embedding database (OLEDB) mechanism.
• OLEDB object linking and embedding database
• This mechanism creates a connection between the application and the database while making physical location of the database transparent. This allows database write operations from within the application.
• the mechanism stores a set of application database credentials for each application. There may be many one-to-one application-database links.
• Each ActiveX TM window control introduced for the security code is hidden, i.e. it is not associated with a visible user display. It is henceforth referred to as a "hidden window component”. For clarity, only two hidden window components 42, are illustrated. Each hidden window component 42 is linked with the family of application controls for that particular window (or "form").
• Each hidden window component 42 then automatically scans the application code and generates a list of application controls that can be tracked, and the developer confirms which are to be tracked.
• the term "tracked" in this context means that user activity involving the application control during runtime will give rise to a log entry.
• Fig. 3 a hidden window component 42 and application controls 40 which are tracked, as viewed on-screen by the developer, are shown.
• the characteristics of the three application controls 40 are shown, and the display indicates how the developer may enable or disable a link to each AC 40 after it has been automatically detected.
• the component 42 which is "dropped” then executes to automatically generate part of the structure of the access control database 23, having a record 51 for each window of the application, and a record 52 for each control (button, data input field, etc) of each window.
• a table 50 having a record for each application. This provides a hierarchical structure from top down of application, window (form), and control, as illustrated in Fig. 5.
• an access control permissions table 55 having a set of blank records for access control permissions for access to all of the three levels above by user groups.
• the hidden window component 42 introduced by the developer of the security software has established tracking links with all of the application controls 40 of that window for which user inputs are to be tracked.
• a fresh hidden window component 42 is introduced for each window of the application and the steps of llinking with controls within that window are repeated.
• it has established an empty access control database 23 having records for the tracked controls and windows.
• a code generation module scans through the database 23 and, for each application control record 52 identified, automatically generates and inserts capture code in the application code.
• the capture code is for, during runtime of the application, automatically logging a user data/instruction input at the control to the audit log database 22.
• the code generation module includes a library 60 of capture code segments.
• Each segment 60 is associated with a control event 61 i.e. an event associated with user input of data or an instruction for production control.
• the examples of events 61 given include text box change, namely user editing or inputting of data in a text box.
• Another example is pressing of a window commit button, which causes all data or instructions inputted at controls of a window to be simultaneously committed to the production control database.
• the code generation module scans the access control database 23 and selects an appropriate capture code segment 60 for each event of each control and each window. It then inserts the selected capture code segments 60 in the application code.
• the application code is of the event-driven type, and so there is no need to insert the capture code segments at any particular locations.
• capture code segments 60 are given below. Each segment is between the instructions “Private Sub” and “End Sub”. These code samples include comments indicating to another developer how the code came about. Private Sub Checkl_Change()
• the "end-product" security software 35 comprises the capture code segments and hidden window components embedded in the application code 34, the access control database 23, and the audit log database 22 and DLL programs.
• an access control module of the security software populates the access control database 23 with inputs from a supervisor.
• the supervisor is allowed input an access permission for each authorised user group for each control and each window. This task may be re-done at any future stage without modification of the compiled application and security code.
• the applications 34 execute to perform production control.
• the security software allows only authorised inputs at the controls of tlie applications, both at the window level and at the lower level of controls within the windows. This is performed in accordance with the permissions of the access control database 23.
• a control button comprehensive data concerning this is captured. For example if an operator changes a temperature display from 60°C to 59°C and then back to 60°C the security software detects this change as events. It logs to the database an event for each of the temperature setting digit changes: (a) 6 -> 5, (b) 0 -> 9, (c) 5 -> 6, and (d) 9 -> 0.
• the invention provides for development of comprehensive security software which operates within the applications for very fast and effective access control and audit trail logging. Also, because the capture code is embedded in the application code it is exceptionally difficult for an unauthorised user to circumvent. These advantages have been achieved without need for the security software to be developed at the same and/or by the same team as the application software. It can be developed separately, after development of the application code, but before it is compiled. Also, because of the compact nature of the capture code, it imposes very little processor overhead. The comprehensive and embedded nature of the security software allows it to be deployed in production control environments where accountability and audit trail tracking is of paramount importance, such as in pharmaceutical manufacturing.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Automation & Control Theory (AREA)
• Stored Programmes (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=34385747

Family Applications (1)

Country Status (3)

Families Citing this family (1)

Family Cites Families (2)

• 2004
  • 2004-09-24 IE IE20040650A patent/IES20040650A2/en not_active IP Right Cessation
  • 2004-09-24 EP EP04770405A patent/EP1665037A1/de not_active Withdrawn
  • 2004-09-24 WO PCT/IE2004/000130 patent/WO2005031567A1/en not_active Application Discontinuation

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events