Basic Rules for the Construction Call Forward Sheet Generation:

 

The relationship of tasks in the call sheet is critical to the scheduling and planning of the building process. This is done by qualifying tasks three ways.

 

 

Free Task

Free tasks are regular tasks in the call sheet.  Estimated Start dates of free tasks are determined by the completion of another task (Precedents). 

It should have one (or more) precedents.
It should not have “Linked Parent” or “+/- Days” mentioned.
For planning purposes it can have a delayed start by the inclusion of Delta days in the precedence specification.
Simplest of the call-sheets may just have a list of free tasks each with a precedent, telling the system the order in which they have to be completed.

 

 

Key Task

Key tasks are similar to free tasks. Wherein, the estimated Start dates are determined by the completion of another task. For planning purposes it can have a delayed start by the inclusion of Delta days in the precedence specification. An example would be the delay between the slab being laid and the bricklayer commencing.

It should have one (or more) precedents.
It should not have “Linked Parent” or “+/- Days” mentioned.
Find a trade that is hard to schedule.
Make sure they aren't optional tasks (unless all the linked tasks assigned to it are optional too)

 

Linked Task

Linked tasks are linked to the key tasks. They do not have precedents. Their start date is determined by the start date of their key task.


For example:

It should have an existing ‘Key Task’ mentioned under the column “Linked Parent”
It cannot have a “Precedent “
It should have “+/- Days” mentioned in order to determine the start date, which is the number of days before or after the Key Task start date.
A task cannot be linked to a linked task.
It is not advisable to have linked tasks with more than 5 “+/- Days”. Try to convert them to Free or Key Task.


Key and Linked Tasks usage:

Key and Linked tasks are used when there is a block of tasks with one critical task on which the others depend.  The critical task is the key task (often the tradesman) and the dependant tasks are linked tasks that are scheduled in relationship to the scheduled key task.

Example: 
The classic example is ‘Brick Layer’ as the key task and the delivery of the bricks, site shed, lintels, etc. are related to it as Linked tasks.
Brick delivery, sand delivery etc can have the linked parent ‘Brick Layer’ and may be linked with ‘-2 Linked days’. This way, when the supervisor calls up the brick layer to come in on the 15th of the month, deliveries are scheduled to be there on 13th of that month (2 days before).


The key task and linked tasks should be used in moderation. We usually suggest key tasks to be labour tasks. The linked tasks should be the deliveries to those trades, or other tasks that are interlinked with the key labour task. We should also to have as few "+" days assigned to linked tasks as possible. Since any delay in the key task would mean a reschedule for all associated linked tasks. For "–" days this is no problem as they will just happen a few days early and not impact all the other associated linked tasks.



Explained further:

Enter a Lead Time for each Task. If it is a Key Task make sure the Lead Time is sufficient to cover the longest lead time plus the ‘– days’ of the Linked Tasks (that happen before that Key task.)



Example:
‘Timber Joinery’ set to be triggered 7 days before the ‘Bricklayer’ starts the work. ‘Timber Joinery’ also has a lead time of 10 days and duration (time taken to complete) of 1 day. So the ‘Timber Joinery’ will be ordered 18 days before the ‘Bricklayer’ starts work.
 
‘Bricklayer’ has a lead time of 5 days.
 
‘Timber Joinery’ is ordered on the 1st of the month, we are expecting the bricklayer to start work on 18th of that month, but he is only called up on the 13th. Whereas the Timber is ordered 13 days in advance.
 
In such a situation, there is a need call up the bricklayer on the 1st on the month, which means Task ‘Bricklayer’ should have a lead time of 18 days. 



FAQ:

 

1) For ‘Delivery’ if we have 2 cabinet making companies, how do I distinguish between the two? As in which supplier should be receiving the call-up. Is that done in the programming?

A supervisor will get an option to choose from the list of suppliers (That have the Resource Code (defined below) assigned against that task). For example: Task ‘Toilet Hire’ may be done by Supplier with the resource code ‘Toilet Hirer’. All the suppliers with that resource code will be in the list to be chosen from.
 
If you have opted PO Matching, the supplier mentioned on the purchase order would be called up. However, if you want to do it in any other way we can accommodate it. For example: On an alternative basis etc.

  

2) What are the following columns for?


Resource Code:

Resource codes are used in grouping the suppliers. As to which supplier should come up in the drop down when you call a certain task up (Schedule) from the IPad/Tablet.
For example: Task ‘Toilet Hire’ may be done by Supplier with the resource code ‘Toilet Hirer’. All the suppliers with that resource code will be in the list to be chosen from.
Ex of Resource Codes:
Resource code      –          Resource code Description
280                        –          Bricklayer
or
CARP                    –          Carpenter
 
However most of our clients keep the same as the PO Cost Code to avoid redundancy.

 

PO Cost Code:

The cost codes may come from the existing system you use.

 

PO Supplier/Allocate the supplier from the PO:

This just means that the system will be choosing the Supplier from the purchase order number mentioned. This supplier will be locked for that task and the supervisor will not be able to change it.

 


Reference/Show PO on the Ipad:

It is advisable to have reference to all your tasks. This provides transparency in dealing with the Purchase Orders. This allows the trades to look up the Purchase Order Info.

 

Reminder days: 

See Call Up Reminders

 

Admin Task:

These are the tasks that someone from the office would work on (from the desktop Version). Supervisors won’t see this on their IPads/Tablets.  An example would be a claim job or ‘Contact Client for Handover’ etc

  

Auto Scheduled Task:

When selected these tasks auto schedules themselves, once their precedent task is completed.
Example auto- generated emails to the account department, informing them file for a claim and the Accounts Staff can complete the task after sending the email.
If a normal call-up task is set up to be auto schedule, a call-up will be sent to the supplier when its precedent has been completed.

 

Auto Complete task:

When selected these tasks are automatically completed as they are triggered.
Example auto-generated emails are sent to the accounts department, informing them about the completion of a particular stage. 
The task is closed as soon as the Accounts department is informed (i.e mail sent).