Stages - Intergraph Smart Materials - Version 10.2 - Help - Hexagon

Intergraph Smart Materials Classic Help

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.2

Planned

For the planned stage, the following objects are available:

  • Engineering requisitions for purchase for which no approved orders or notices of commitment have been placed so far.

  • Planned requisitions for purchase (requisition links defined on the P.60.03 Requisitions Planning screen); only requisitions for which a requisition link is neither present nor actually existing are available (that is, requisitions with 'Link to Req' = 'No Relation' are available).

  • Approved purchase orders.

  • Approved notices of commitment that so far have not been converted into an approved purchase order.

Change orders are taken into account in the way that they overwrite the corresponding information of the original order; that is, the order data that is shown already consider approved change orders.

If only some line items of a requisition have been placed on an order that is approved already, only these items disappear for a requisition from the planned stage. The requisition with its remaining line items is still displayed.

On the first level below 'Planned', those date ranges among the ones defined in PT.10.01 Date Ranges are shown for which at least one order or (planned) requisition exists with a non-empty preliminary packing list the forecasted delivery date of which fits within the range. Beyond this, a node 'Missing PPL/Packages' is displayed as long as at least one (requisition or order) line item or a planned requisition exists for which no preliminary packages (with sufficient quantities) have been created.

A date range always begins at the day following the end date defined for the previous date range and ends with its own end date. For example, if you have set up the following date ranges:

Date range

End date

JANUARY

31-JAN-2012

FEBRUARY

28-FEB-2012

MARCH

31-MAR-2012

then the first date range comprises all dates up to 31-JAN-2012, the second date range all dates between 01-FEB-2012 and 28-FEB-2012, and the last one all dates between 01-MAR-2012 and 31-MAR-2012.

If there are non-empty PPLs with a forecasted delivery date later than the end date of the last date range, you will also see a date range NN. This date range indicates that you should define additional date ranges.

The level below the date range nodes consists of the main destinations taken from the schedules of the routing methods defined on P.10.53 that have been assigned to preliminary packing lists (PPLs) of the relevant traffic objects. A special main destination node labeled 'Missing Routing Method' will be added if non-empty PPLs are found to which no routing method has been assigned yet.

The next lower level displays delivery places that have been assigned to the PPLs of the related traffic objects. Similar to the main destination level, a special delivery place node labeled 'Missing Delivery Place' will be added if non-empty PPLs exist, to which no delivery place has been assigned yet.

Below the delivery place nodes, the (planned) requisitions and orders are displayed for which a PPL has been created with a forecasted delivery date that fits within the date range, a routing method the schedule of which has the appropriate main destination, the matching delivery place, and that is non-empty (that is, it comprises at least one preliminary package). Below the requisitions and orders, these PPLs are shown, with their preliminary packages located on the next lower level.

Below the 'Missing PPL/Packages' node, the (planned) requisitions and orders with insufficient preliminary packing are shown.

The data below 'Planned' is subject to changes as long as the traffic data of the planned stage has not been frozen. After traffic data has been frozen, the 'Planned' node will appear as 'Frozen Planned', and the data below will not change any longer. For more information about freezing traffic data, read the description of the Freeze button in the Overall Totals block.

Forecast

For the forecast stage, release notes not placed on any means of conveyance so far are of interest. Furthermore, once planned data has been frozen and the Copy operation has been triggered, orders and (planned) requisitions that fulfill the requirements for appearing below the 'Planned' node will show up here, too. For more information, see the description of the Copy button in the Overall Totals block.

As with the 'Planned' node, the first level below 'Forecast' contains the date ranges including a 'NN' node if necessary.

If there are orders with item shipments having no routing method, you will see an additional 'Missing Routing Method' date range.

Below each date range you see the delivery designations, that is, all main destinations that you have set up on P.10.53 Routing Methods and for which data is available. Again, an additional 'Missing Routing Method' can occur as described for the 'Planned' branch.

Below each main destination, all delivery places for the selected date range and for which release notes exist fulfilling the following prerequisites are displayed, including an additional 'Missing Delivery Place' node if applicable.

Below a delivery place, you see release notes with item shipments of which the forecasted or actual date of the destination marked as 'Delivery Date' fits within the date range. The expediting dates of an item shipment can be seen on the P.70.72 Expediting Details screen. The marking of a destination within a routing method as 'Delivery Date' is done on the P.10.53 Routing Methods screen. Orders and (planned) requisitions - if displayed at all in the 'Forecast' branch - are assigned to delivery place nodes as described for the 'Planned' branch.

If packages have been defined for a release note, the node of that release note can be expanded so that you can see these packages on the child level.

Actual

Below the 'Actual' node, means of conveyance are visible.

On the next lower level, you see all date ranges (including another 'NN' node if required), and below each date range the loading points of all means of conveyance the actual (or, if that is not available, estimated) departure date of which fits within the date range. Note, however, that a means of conveyance which concludes a transport chain (that is, its unloading point equals a delivery designation) resides below the date range that refers to its actual (or, if that is not available, estimated) arrival date.

When a means of conveyance (MOC) is expanded, all its release notes are shown on the child level. Again for each release note, you can get all its packages by expanding the corresponding node (if available). You can create means of conveyance either on PT.20.11 Means of Conveyance or by entering a new means of conveyance on the traffic detail window that is opened when you select a 'Workload' node. See the description of the Traffic Details - Workload block for more information.

As long as the unloading point of a means of conveyance is not a delivery designation, transport of the material has not been completed. Such a means of conveyance creates another node labeled 'Workload' below the next potential loading point, which is identical to the unloading point of this MOC. The date range where that 'Workload' node resides refers to the actual (or, if that is not available, estimated) arrival date of the MOC that already exists.

Below 'Workload' all release notes are shown that have been placed on a means of conveyance the unloading point of which equals the loading point currently selected in the tree.

Example:

We assume that the following date ranges, release notes, and means of conveyance exist:

Date range

End date

JANUARY

31-JAN-2002

FEBRUARY

28-FEB-2002

MARCH

31-MAR-2002

Release notes

  • RN-100

  • RN-200

Means of conveyance (MOC)

  • Carrier-100, estimated time of departure: 21-FEB-2002, estimated time of arrival: 04-MAR-2002, loading point: A, unloading point: B

  • Release notes of the MOC: RN-100 and RN-200

In this case, the tree (excerpt) will look like this:

° JANUARY

° FEBRUARY

° A

° Carrier-100

° RN-100

° RN-200

° MARCH

° B

° Workload

° RN-100

° RN-200

When the system determines below which date range data is to be displayed, actual dates are always considered with higher priority. Only if an actual date is not available, the forecasted date (in the case of item shipments) or the estimated departure/arrival dates (in the case of means of conveyance) are taken into account.

With regard to the performance of the tree view: You may experience slight delays when collapsing the '(Frozen) Planned', 'Forecast', and 'Actual' nodes, depending on the data volume located below these nodes. Such delays are caused by a (partial) refresh of the internal cache that boosts overall performance of the tree. The cache contains nodes on the date range, main destination, delivery place (if available), and requisition/order/release note levels that are only reloaded from the database whenever one of the stage-level nodes named before is collapsed. In this way, a reasonable trade-off is achieved between keeping the data displayed in the tree view sufficiently up-to-date and providing acceptable performance of basic tree operations.