Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Sign up

Sign up | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Job Plan Duration?
January 3, 2012
11:20 am
Avatar
DaveC
Member
Members
Forum Posts: 3
Member Since:
August 7, 2013
sp_UserOfflineSmall Offline

We have had Job Plan DURATION explained several different ways. Is there a document available that explains JP DURATION, WO DURATION?

 Current thought, DURATION is the total number of hours available for a PM generated WO to be completed. If you have 1 weeks time available then the JP duration would be 168 hours and the tasks document the time needed to complete the WO.

 

Thanks for any info

Dave   

January 3, 2012
2:14 pm
Avatar
Chon
Stoneham, MA USA
Admin
Forum Posts: 1118
Member Since:
March 2, 2009
sp_UserOfflineSmall Offline

Hello, Please register to see the Admin’s answer!

August 8, 2012
10:55 am
Avatar
bgsands71
Member
Members
Forum Posts: 3
Member Since:
August 7, 2013
sp_UserOfflineSmall Offline

Hey Dave,

A little late to the party, but my understanding is that jpduration is the total time to complete a job (jptaskdurations), but also may include any downtime needed, ie, waiting for a motor to cool down.  That may not a specific job plan task, but still needs to be accounted for.  For example, total jptasks = 2 hours, but you need 30 minutes for a motor to cool, thus jpduration = 2:30.

And I have not seen any specific documentation related to this topic.

August 8, 2012
11:22 am
Avatar
bgsands71
Member
Members
Forum Posts: 3
Member Since:
August 7, 2013
sp_UserOfflineSmall Offline

Just to finish that thought, the jpduration is copied to the work order, which again reflects total time of job (tasks plus downtime) and the work/resources can be more accurately planned from that duration. 

I’d also be interested to hear anyone else’s thoughts on this subject, especially since it is not documented anywhere.

July 22, 2013
11:45 am
Avatar
QASuper
New Member
Members
Forum Posts: 1
Member Since:
August 7, 2013
sp_UserOfflineSmall Offline

We are using it for the duration of the actual work. This leads to the total backlog for a specific craft or person assigned. There is now a function in the Oil and Gas version of Job Plans to limit the actual work date range by adding Start and Finish Constraints, linked to the Scheduled Start Date if I remember right.

August 29, 2014
5:40 pm
Avatar
cgregory
Member
Members
Forum Posts: 45
Member Since:
August 7, 2013
sp_UserOfflineSmall Offline

I totaled the tasks durations as the job plan duration. The wo generates with the parent displaying total duration for my supervisors to plan with, while the task duration display on a printed WO for the technician.

June 17, 2020
7:42 pm
Avatar
Thiago Pereira de Oliveira
New Member
Members
Forum Posts: 1
Member Since:
June 17, 2020
sp_UserOfflineSmall Offline
Good evening,

I consider the downtime of the equipment in this field of duration of the maintenance plan. 
For example, there may be steps for scaffolding assembly that do not need the equipment stopped so I 
disregard the scaffolding assembly and disassembly times in the total duration of the work plan. 
If the scaffolding, for example, is in a pot then I consider the total time. It is a rule that I created for my planning. 
That's right? It's wrong? I don't know, I just know that I do it like this. ;>;> 
Forum Timezone: America/New_York

Most Users Ever Online: 54

Currently Online:
1 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

sun kim: 60

madd0g17: 59

v.barsamov: 51

Maximofresher: 45

cgregory: 45

matta0990: 33

Member Stats:

Guest Posters: 0

Members: 14009

Moderators: 0

Admins: 3

Forum Stats:

Groups: 1

Forums: 8

Topics: 1564

Posts: 4277

Newest Members:

Daniel Trujillo, Madge Stringfield, Sima Howard, Columbus Ainsworth, R B, Maricruz Kabu

Administrators: Chon: 1118, kristensibilia: 0, Joe Grassia: 0