Vendor Progress - 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)

Milestones can be used for planning manufacturing activities and calculating both expected and actual progress of an order.

Activities could be for example:

  • engineering

  • manufacturing

  • documentation

  • inspection

  • packing

For each activity, the progress can be maintained. Based on this information, the actual progress for the requisition / tagged item and the order is calculated. Based on the actual start and/or end date of an activity and the actual system date, the expected progress for each activity is also calculated. Updates on the requisition level are populated to all tagged items of the requisition without individual data. Individual data means that any insert, update, or delete has been performed manually (on the tagged item level) for a tagged item. Updates on the tagged item level are always only processed for that individual item. When inserting milestones on the requisition level, they are also inserted for all tagged items without individual data. When deleting a milestone on the requisition level, this milestone is only deleted for a tagged item if no individual data exists, that is, if the data of the requisition and tagged item is still identical for all milestones.

  • Once data has been updated or inserted on the tagged item level, this data is regarded as individual data even if this data is once again identical with the data on the requisition level due to updates.

  • Any insert or update in this block is only reflected in the progress of the requisition/the tagged item and the order after you have committed the changes to the database.

If the project default ZP_VPAPRQ is set to N (default), data can be changed at any time by any user. If this project default is set to Y, only users that have been assigned to the current record as inspector can create and modify the vendor progress as long as the Ready for Approval indicator has not been set. Once the vendor progress has been marked as ready for approval, no one can apply changes to the vendor progress. In the next step, the vendor progress must be approved; the VENDOR PROGRESS APPROVAL privilege is required for the approval.

After the vendor progress has been approved, only users that have been assigned to the current record as expediter can modify the vendor progress.

The Seq field displays the sequence in which the activities have to be performed.

The Label field shows the name of the milestone label.

The weight factor of the milestone is displayed in the Weight Factor field. The weight factors of the assigned milestones must add up to 100.

If the project default ZP_MS_FDPD is set to N, the dates entered in the Planned Start and Planned End fields are used to calculate the expected progress based on these dates.

The date for which the start of this activity has been forecasted is displayed in the Forecasted Start field. The date must lie before or be equal to the forecasted end date.

The date for which the end of this activity has been forecasted is displayed in the Forecasted End field. The forecasted end date must be greater or equal to the forecasted start date.

The Expected Progress (%) field displays the expected progress for this activity based on forecasted start, forecasted end and actual date. If no forecasted start date or no forecasted end date have been entered the expected progress is 0%. If the actual date lies before the forecasted start date the expected progress is 0%. If the actual date lies after the forecasted end date the expected progress is 100%. If the actual date lies between the forecasted start and end date the expected progress is calculated on account of the actual date and the number of days required for this activity (formula: ((system date - start date) * 100) / days; days = forecasted end - forecasted start). If the forecasted end date has expired and the actual progress of this activity is not 100% the background color of this field and of the overall expected progress is changed to red.

The Actual Progress (%) field displays the actual progress of the activity. The value of this field must be entered by the user. The overall progress of the requisition/tagged item and the order is calculated based on this actual progress.

The date when the milestone actually starts is displayed in the Actual Start Date field. This date represents the date when the progress for this milestone starts. The value of this field must be maintained by the user.

The date when the milestone actually ended is displayed in the Actual End Date field. This date represents the date when an actual progress of 100% was reached. The value of this field must be maintained by the user.

To copy a pre-defined milestone set, you can select the name of this milestone set from the LOV in the Milestone Set field and the click the Copy button. The details (milestones) of this set will be assigned to the selected combination of order and requisition (or tagged item). Only milestones not yet attached are copied. Any milestones that have already been attached will be kept. Generally the weight factors entered on P.10.62 are copied over. But if milestones have already been assigned, the weight factors are set to zero so that they still add up to 100. If a milestone set is copied using the Copy button for a requisition, the details of the milestone set are also populated to all tagged items of that requisition.

Select the RfA indicator when the vendor progress is ready for approval. This indicator is only of interest if project default ZP_VPAPRQ is set to Y. In that case, a vendor progress must be approved before the workflow can continue. When you set this check box, an email is automatically sent to the expediter for the current record to inform him that the vendor progress is ready for approval. As a prerequisite for sending out this email, you must set up an email template on the A.10.51 screen for template type 'EXPEDITING' and assign this template to the project default ZP_EMT_VP.

The Approve button is enabled when the RfA check box has been selected. Click the button to approve the selected vendor progress. This fills the name of the user who has approved the vendor progress in the Approved by field and the date when the vendor progress has been approved in the Approved Date field. For approved vendor progresses, the Reverse Approval button is enabled. Click this button to reverse the approval of the vendor progress. It clears the Approved by and Approved Date fields.

The Overall Expected Progress field displays the expected progress of the requisition or the tagged item. For the calculation, the expected progress of each activity (milestone) and its weight factor are taken into account (formula: sum ((expected progress per activity * weight factor per activity) / 100) * 100). If the forecasted end date of any milestone has expired (that is, actual date > forecasted end) and the actual progress of this milestone is not 100%, the background color of this field is changed to red.

The value in this field always reflects all milestones. Even if you have restricted the display of records in the third block by entering conditions in enter-query mode, this has no effect on the overall progress shown here.

If you apply any changes to the milestones, the display is only changed after you have committed the modifications to the database.

The Overall Actual Progress field displays the global progress of the requisition or the tagged item based on the actual progress of each activity. For the calculation of the progress, the actual progress of each activity (milestone) and its weight factor are taken into account (formula: sum (((actual progress per activity / 100) * weight factor per activity) / 100) * 100).

The display of the actual progress always reflects all milestones. Even if you have restricted the display of records in the third block by entering conditions in enter-query mode, this has no effect on the progress shown here.

If you apply any changes to the milestones, the value shown here is only updated after you have committed the changes to the database.