Milestone Planning - Intergraph Smart Materials - Version 2020 (10.0) - Help - Hexagon PPM

Intergraph Smart Materials Classic Help (2020)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
2020 (10.0)

On the Milestone Planning tab, you can perform all the tasks that are related to the tracking of milestone dates for the selected planned tagged item.

A milestone is a user defined event with a date that requires tracking. Each milestone is identified by a label and typically has three dates associated with it, a planned date, a forecasted date, and an actual date. The list of milestone labels is generated automatically upon creation of a planned tagged item, regardless of whether it has been created manually or by the MTO.

In order to work with the milestone date set, it is necessary to create the initial plan. Normally, you enter one planned date, save the record to the database, and then click the Calculate Planned button. You can enter a planned date for the first milestone, for the last milestone, or for any milestone in between; the system will always use the span days to calculate the date series upstream and downstream. The procedure for calculating the Planned values works in several steps:

It is only possible to work with just one milestone with a manually inserted value for Planned. If you assign values manually to more than one milestone, only the value of the milestone with the lowest sequence will be considered, and all other values will be deleted.

In the next step, the procedure searches for derivations to the milestones. For more information, see Milestone Labels. Because a derivation has priority over a manually inserted value, the found derivations will be inserted and will overwrite the manually inserted value.

In the next step, the procedure again searches for the first milestone with a given value for Planned to start the calculation.

The difference between two milestones must at least add up to the addition of ‘span days’ + ‘add days’. For more information, see Milestone Labels.

If a derivation is defined for a milestone, there are usually two possible values for the planned date of this milestone: the derivation and the addition to the value of the previous milestone. If the derivation of the second milestone is lower than the addition to the value of the first milestone, the given derivation of the second one will be overwritten by the addition. If the derivation lies more in the future than this addition, the derivation will not be overwritten and taken as the Planned value; nevertheless, this value is taken as the starting date for building the next Planned value.

The calculation procedure needs a starting point for its calculation, but it's not necessary in every case to insert a value manually. If one or more of the milestones have derivations, the value of the milestone with the lowest sequence will be taken as the starting point. If no milestone has a derivation and you did not insert a value for Planned, the procedure stops and an alert appears.

Example: Two milestones MS1 and MS2, for MS2 a derivation is defined, ‘span days’ and ‘add days’ adds up to 5.

Milestone

Before Calculation

After Calculation

MS1

01-JAN-2011 (manually entered)

01-JAN-2011

MS2

03-JAN-2011 (due to derivation definition)

06-JAN-2011

but:

Milestone

Before Calculation

After Calculation

MS1

01-JAN-2011 (manually entered)

01-JAN-2011

MS2

10-JAN-2011 (due to derivation definition)

10-JAN-2011

The software does not consider if any of these days is a working day or not.

To be able to create or modify the plan, you must have the SCHEDULE MILESTONES privilege granted. Otherwise, you will only be allowed to work with forecasted and actual dates.

Two-Phase Planning

With the 1st Pass and 2nd Pass check boxes, you can constitute the end of the first and the beginning of the second phase of planning if you want to set up a two-phase planning. For more information, see Milestone Sets. If you have selected these check boxes for a milestone set, you must define exactly two dates in the Planned field before you click the Calculate Planned button. The first date must be placed on or before the milestone that was marked as the first pass, and the second date must be placed on or after the milestone that was marked as the second pass. The second date must also lie after the first date.

When you click the Calculate Planned button, the two phases of planning will be executed. Beginning with the first date entered, the days will be calculated up to the milestone marked as the first pass and backward to the first milestone. Then beginning with the second date entered, the days will be calculated backward to the milestone marked as the second pass and forward to the last milestone. The planned days between the first pass and the second pass will not be filled.

If you have already executed the two-phase planning and click the Calculate Planned button again, all calculated planned dates will be deleted except the dates of the first and the second pass, which will be used as starting dates for the new calculation.

This two-phase planning has no effect on the calculation of the forecasted dates. If you calculate the planned dates and the forecasted dates are yet empty, the date of the second pass will be taken as starting date for calculating the forecasted dates.

With the Lock Plan button, you can lock the planned dates in order to protect them against updates. After you click the button, its label will change to Unlock Plan, and the Calculate Planned and Delete Planned buttons will disappear. To unlock the planned dates, you must have the UNLOCK MILESTONE SCHEDULE privilege granted. After the planned dates are unlocked, the before mentioned buttons will be visible again.

As the work on the planned tagged item makes more progress, more actual dates will be available. You can initiate the date derivation run anytime by clicking the Calculate Forecasted button. The system will then apply the derivation rules that have been set up on P.10.61 for each of the milestone labels and recalculate the forecasted date series.

The check boxes on the Milestone Planning tab allow you to lock selected forecasted dates, or to exclude selected actual dates from the derivation logic.

Additionally, the system will indicate which events are slipping by displaying any delay between the planned date and the forecasted date in the Days Late field.

If you have defined a planning group with its two budgets (see Planning Groups) and assign the shown tagged item to this planning group, a progress is calculated. If you have defined weight factors for the used milestone set on P.10.62 Milestone Sets and budgets for this tagged item on the General tab, the weight factors for all finished milestones are summed up and multiplied with the budgets of this tagged item. Because you can assign more than one planned requisition and also one or more tagged items to the same planning group, this summation will be done for them all. The sum of all will then be compared to the budget given for the planning group itself. Because it is not possible that the budget of the planning group is less than the sum for all assigned planned requisitions and tagged items, the value will be less than or equal to 100.

The Label field displays the name of the milestone as defined on P.10.61 Milestone Labels.

If there are detail milestones related to this milestone, the field is displayed with a magenta background color. In this case, you can double-click in this field to open Window 7, which displays these detail milestones.

In the first (Master Milestone) block the selected milestone is displayed with its name in the Label field, the order sequence in the Order Seq field, and the planned, forecasted, and actual dates in the Planned, Forecasted, and Actual fields.

Depending on the type of the detail milestones (inquiry, quote, agreement, or expediting), the layout of the second (Detail Milestones) block may vary, as some fields are not displayed for all types.

The first field is labeled either Inquiry Number or Agreement Number. The information displayed in this field depends on the type of detail milestones - inquiry, quote, agreement, or expediting. For inquiry-type detail milestones, the name (number) of the associated inquiry is shown. For quote-type detail milestones, this field displays the name (number) of the inquiry for which the associated quote summary has been created. If the detail milestones are agreement-type, it shows the name (number) of the associated agreement, and for expediting-type detail milestones the agreement number of the associated item shipment is displayed. Accordingly, you can double-click in this field to open P.30.11 Inquiries, P.30.22 Commercial Evaluation, P.50.07 Maintain Agreements, or P.70.72 Expediting Details.

The Suppl field shows the inquiry/agreement supplement. For inquiries, the Purchase indicator is displayed.

The Bidder field shows the name of the bidder of the associated quote summary. This field is only visible for quote-type detail milestones.

The Pos field shows the agreement line item number. This field is only visible for expediting-type detail milestones.

The Sub field shows the agreement sub line item number. This field is only visible for expediting-type detail milestones.

The IS Pos field shows the item shipment line item number, and the IS Sub field shows the item shipment sub line item number. These fields are only visible for expediting-type detail milestones.

The displayed detail milestones are based on item shipments or agreement line items found on the highest approved supplement of the corresponding agreement. You can select the History check box in order to incorporate detail milestones associated with item shipments or agreement line items from previous supplements.

The date the event tracked by this milestone is forecasted to occur is displayed in the Forecasted field. The date the event tracked by this milestone actually occurred is displayed in the Actual field.

Whenever the actual date of a detail milestone is changed, the CIP function m_pck_ms_custom. calc_actual_date_master is executed. This function recalculates and returns the actual date of the corresponding master milestone (specified by parameter 'p_ms_id') based on the change applied to its detail milestone(s). The parameters used with this CIP function are listed below.

Parameter

Description

p_ms_id IN m_milestones.ms_id%TYPE

Primary key value of the milestone for which a calculation is to be executed.

p_item_type IN VARCHAR2

For planned requisitions, ECI, and for planned tagged items, ENCI will be passed as the character string.

p_pk_id IN NUMBER

If the milestone denoted by p_ms_id belongs to a planned requisition, this parameter is the eci_id; for planned tagged items, the enci_id will be passed (that is, it depends on the value of parameter p_item_type).

p_mset_id IN m_ms_sets.mset_id%TYPE

This parameter is the primary key of the milestone set that the planning item denoted by parameter p_pk_id uses.

p_mc_id IN m_ms_configs.mc_id%TYPE

This parameter is the primary key of the milestone label related to the milestone for which the function has been called.

Click the Close button in order to close the window and return to the Milestone Planning tab.

On the Milestone Planning tab, the Order Seq field displays the sequence number uniquely identifying the milestone label.

The date the event tracked by this milestone is planned to occur is shown in the Planned field.

The Span Days field shows the number of scheduled days between two milestones.

The date the event tracked by this milestone is forecasted to occur is shown in the Forecasted field.

The date the event tracked by this milestone actually occurred is shown in the Actual field.

The Orig. Days field displays the original number of days between this milestone and its successor. The Days field displays the actual number of days between this milestone and its successor.

The Days Late field shows the difference between the forecasted date and the planned date, if the forecasted date is later than the planned date. Depending on the project default ZP_DELAY, the background color of this field is changed. If the number of days is less than or equal to the value defined by ZP_DELAY, the color will be set to yellow. If the number of days is greater than the setting of ZP_DELAY, the background color is red.

The 1st Pass indicator shows if this milestone marks the end of the first phase of planning.

The 2nd Pass indicator shows if this milestone marks the beginning of the second phase of planning.

The value of the first/second weight factor is displayed in the Weight Factor 1/2 field.

The Locked Forecasted indicator shows that the forecasted date for this milestone label has been locked for calculations. If the forecasted date has been populated by a derived actual date by the milestone calculation/derivation run, this check box will be set to locked; however, you can always lock or unlock it manually.

If you select the Manual Actual check box, the system will not derive the actual date for this milestone label by applying the derivation rule that has been set up on the P.10.61 Milestone Labels screen. Instead, the date must be entered manually.

You can enter an external activity in the External Activity field. The Ext. Amount field can be used to link milestone planning data to an external or third party system. There is no application logic associated with this external float amount within the system. The External Activity and External Amount fields are used to identify those activities that are not a part of the actual milestone set but noted as having an impact on the overall schedule. An example of this is a client requested change that would stop the cycle for an uncertain amount of time and, for later reference, requires a log.

The Plan Comment field can be used to enter a comment regarding the planned date of this milestone. The Forecast Comment field can be used to enter a comment regarding the forecasted date of this milestone.

The Actual Derivation field indicates which module or sub module calculated the derived actual date for this milestone. It will either display a module code such as 'P.60.03' or indicate that the derivation took place by the automatic tracking feature for one of the supported events.

You can click the Order By ... button to change the order by criteria for the displayed records. An LOV opens where all fields currently visible on the screen are listed. Select the field by which you want the data ordered by in the first place and click OK. The LOV opens again allowing you to select a second field, and so forth. Click the Cancel button to complete the field selection. Your last query will be performed again, using the new order by criteria. The order by criteria are displayed in the Ordered by field on the top of the tab.

At least one planned date must be set before you click the Calculate Planned button. If you click this button all planned dates not yet set are calculated (backwards and forwards) starting from the planned date you have entered. This button will only be active if you have the SCHEDULE MILESTONES privilege granted. If you have locked the planned dates using the Lock Plan button, this button will not be available.

When you click the Delete Planned button, all planned dates of the tagged item currently selected will be cleared. If you have locked the planned dates using the Lock Plan button, this button will not be available.

Click the Lock Plan button to lock the planned dates. The Calculate Planned and Delete Planned buttons will disappear, and the label of this button will change to Unlock Plan. You can click the Unlock Plan button to unlock the planned dates. The Calculate Planned and Delete Planned buttons will be enabled and this button will be relabeled to Lock Plan. This button is only available if you have the UNLOCK MILESTONE SCHEDULE privilege granted and the planned dates are not locked/are locked.

If you click the Calculate Forecasted button, all forecasted dates of the milestone plan are calculated and actual dates are derived based on the settings on P.10.61 Milestone Labels.

When updating forecasted or actual dates of milestones, the software automatically recalculates the forecasted dates of the respective milestone plan, starting with the milestone succeeding the one that has been updated. Thus, forecasted dates of the updated milestone itself or of milestones preceding the updated one are not touched in this scenario, this is, their values will be preserved.

If you click the Delete Forecasted button, all forecasted dates of the selected planned tagged item will be cleared, and the Locked Forecasted check box will be cleared for all milestones.