Job Costing - Job Cost Control File - Change Management - Tab

Sample of the Change Management tab in the JC Control File

Pgm: JCCTRLFM – JC Control File; standard Treeview path: Job Costing > Setup > Local Tables > Control File – Change Management tab

This tab is used to set the change order defaults for jobs.

Self Performed Work

This is the self-performed work code for work to be carried out by the company itself, instead of using outside vendors/subcontractors.

Owner Change Text Type

Select the default text type code.

Subcontract Text Type

Select the default text type code.

Project Management Object’s Change Order Defaults

The following provides details about the table used to set the defaults for a Project Management object’s created change orders (change items):

Column		Description
Project Management Object		This column contains the different Project Management objects, for which their created change orders defaults can be set.
CM Type		This column specifies the default change order type to use when change orders are created for the Project Management object type.
Desc		Description of the Change Management Type field’s value.
Status		The default status of the created change order.
Desc		Description for Status field’s value.
The following settings are for the selected row in the table:
Status	Displays the default change order type and its status for the selected Project Management object.
Proceeding – Checkbox	Indicates whether or not the change order will be carried out.
Included in Forecast – Checkbox	Indicates whether or not the change order is to be included in the contract forecast.

Allow Unposted PCI To Be Assigned To Subcontract Change Order − Checkbox

When checked, unposted potential change items (PCIs) will be available to be assigned to subcontract change orders (COs).

Populate PCI Name On Subcontract Change Order − Checkbox

When checked, the system uses the PCI name as the subcontract change order’s task description. When unchecked, the system uses the PCI long description, if it exists.

Category For Entry Of Cost Code Budget Changes − Checkbox

If checked, a default category code can be set to use in bid item entry and PCI entry when entering cost code budgets. If set, the 'Category For Entry Of Cost Code Budget Changes' checkbox displays the category code, which is set via Change Management’s Control screen.

Phase Description Taken From Bid Item List − Checkbox

When updating budget from PMJSP bid item, if this option is checked, it will update any new budget line with a description from the project bid item rather than the phase master.

Allow PCIs On An Owner Change Order − Checkbox

There is now more flexibility in the types of PCIs (external, internal, transfer, original budget) that can be selected for inclusion in an owner change order (no longer restricted to only external and original budget).

These four checkboxes are used to allow both external and original budget change orders on owner change orders.

Default RFQ Review Period

The Default RFQ Review Period field is added to the sent date to automatically update the due date on the RFQ tab of PCIs. If the default value is null at the project level, the system will check the company level default and use that value if it is not null as well. The due date that is calculated is based on the project calendar working days.

Change Item Entry Mode

This indicates the mode of entry for PCI details – whether they are entered as amounts or quantities.

Lum Sum PCI Cost Code

This is the cost code to use for internal lump sum PCIs.

Lum Sum PCI Category

This is the category code to use for internal lump sum PCIs.

Category For Entry Of Cost Code Budget Changes

This is the category code that is to be used in bid items entry and PCI entry when entering cost code budgets. The value is defaulted from the Change Management Control screen.