During the past few years I have noticed that there is some confusion regarding the differences between a Job Plan, Work Procedure, Schedule Activities and finally the Work Package.
When together seem to be one of the same, however like many other things in our complex world... it is the subtle differences that often cause grief. Well the following are my understanding of the definitions, how each relates to one another and why we need each. First off...the definitions:
Job Plan: List of activities outlining requirements to complete a deliverable.
The job plan is created when the lead craft assigned to the deliverable reviews the scope, verifies location, defines what work is required and the magnitude of work involved. Upon investigation the risks, support, equipment (tools), material and duration estimate is compiled. The components of the plan are then entered ino the CMMS and queued for execution.
Work Procedure: Similar to a Job plan however a procedure is a more stringent approved document which includes or references an organizations policies, processes, checklists and instructions including but not limited to manufacturers instructions. The work procedure may also have an assigned expiration date as well as being subject to a process change control system. Organzations subscribing to ISO 900X may be more involved in creating and managing Work Procedures.
Work Package: From a project perspective the work package is the lowest level of the projects WBS. The work package is the group of documents that includes items such as the Job Plan, Work Procedure, P&ID, Detailed Safety Plan, Engineering Documentation, Blindsheets, Material Details, QA/QC Documentation etc...
Schedule Activities: Represents the sequencing, timing and duration of activites to be performed within a specified period. These activities relate to the scheduled completion of the deliverable of which the Job Plan or Work Procedure was created. With this said each planned activity does not necessarily need to be included within the schedule. The scheduled activities should, in my experience, enable clear understanding of deliverable completeness. For example, there may be 25 activities defining detailed information to clean an Exchanger; from a scheduling perspective these 25 activities often can be summarized to 5-10 schedule activities such as:
10 Blind Exchanger
20 Remove End Plates
30 Clean Exchanger
40 Inspect Exchanger
50 Install End Plates
60 Remove Blinds
Subscribe to:
Post Comments (Atom)
1 comment:
Good info Mike,
On a simplistic level I use the following.
Job Plan is what you are going to do divided into steps, what resources you need and probably how long it will take,
Work Procedure is how you will execute the Job Plan while considering procedural and process requirements.
Work Packages are the job plans along with all other required job information. (procedures, historic information, HAZOP, torque specs etc)
Work Schedule is the sequence of how you will execute the Jobs, actual as well as any perceived relationships and how long each task, job and the entire TA will take
Post a Comment