1. An overview of the electronic work permit system in use at the ISAC facility ISAC Electronic Work Permit System Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 1

2. History Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 98 – 2001:Paper permit system in use based on previously existing system 2001:Switched to electronic permit system designed by co-op student Wendy Wiggins 01 – present: Electronic permit system in use at ISAC facility to schedule and catalogue all work done on commissioned systems 2

3. Motivation Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 33 Database structure allows for very rapid searches of the archived permits with queries that can be fully customized

4. Motivation Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca Database structure allows for very rapid searches of the archived permits with queries that can be fully customized Web-based interface facilitates remote access to the permit system Remote access improves ease of use and convenience for users and reduces traffic in the control room 4

5. Database containing all permit and user information Interactive, web-based interface Support Applications Designed with scheduled maintenance periods in mind Structure of the ISAC WPS Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca Database User Interface Support Applications 5

6. Structure of the ISAC WPS Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca Interface: Interacts with the database based on input from user Used for viewing, writing and editing of permits Provides several admin functions not directly associated with permits 6

7. Structure of the ISAC WPS Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca Input from the user must be simple Calculations should be automated wherever possible Default selections can save time but can also be dangerous Familiar look and feel can make the transition to any new system easier 7

8. Structure of the ISAC WPS Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca Electronic form was based on existing paper system 8

9. Permits receive a unique id as soon as they are submitted as Pending Id includes the current date and a number that is incremented for each permit Increment begins at 1 each day Pending permits are distinguished from other permits by a negative number This simple system allows a fair amount of information to be conveyed at a glance Permit Numbering Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 9

10. Status indicates progress of job – Pending – Active – Completed – Closed Certain statuses require approvals first  Area Supervisor  Safety  Operations Permit Status &Permissions Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 10

11. ● Log in required for actions affecting database ● Strong constraints on input to database ● Different user types with specific privileges Security: Managing DB Integrity Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 11

12. Rigorous testing of computer code prior to release Maintain a schedule for software upgrades and bug fixes Security: Managing DB Integrity Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 12

13. The cron utility is an easy way to run tasks with scheduled frequency Backups of database content Updates of user email and password lists Weekly notices to users and administrators An ideal system would be one where WPS and other such electronic applications are able to communicate between each other. This would help eliminate duplication of information by users. ex. A permit being filled out in response to a fault report. Support Applications Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 13

14. Change of programming language – Database: MySQL --> PostgreSQL – User Interface: PHP --> Perl Improve Area/System differentiation More extensive use of user qualifications Integration of WPS with other electronic utilities such as log book, fault reports, etc. Site-wide adoption of electronic system What Does the Future Hold? Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 14

15. Based on paper permit system already in use on site Consists of Database, user interface and support utilities Security achieved through access control and user privilege levels Constantly developing Summary Rob Shanks, TRIUMF, Vancouver CANADA, roberts@triumf.ca 15