Parts requirement (Gozintograph)
Description
Starting from parts scheduling, the production-specific parts lists selected there - sorted according to production stages - are summarised in so-called gozintographs. The parts request module(business pattern) described here is used to maintain such - automatically created - gozintographs.
The task of this module is to be able to carry out a purely logistical material planning in a first step. This is done in six steps:
- Determination of the disposition type of the parts
- Determination of the standard replenishment lead time according to the disposition type
- Scheduling of the necessary provision of parts
- Checking the availability of materials
- Triggering of production orders, purchase requisitions and stock reservations
- Release of the parts requirement
Steps 1, 2 and 3 can be called up and carried out directly and automatically as one process from parts planning. The "standard information" on the procurement type and time from the master information of the parts master is used as the basis. Steps 3 and 4 (planning) may have to be carried out iteratively several times after manually changing the disposition type and/or procurement time of individual parts so that the planned dates can be met. This planning can also be carried out graphically supported by means of a Gantt chart.
Post Calculation
In order to determine which costs have actually been incurred on a cost object (e.g. sales order), all costs ? its follow-on documents must be added up. These are, for example, goods withdrawal slips, BDE deregistrations, incoming invoices etc. Some parts that are required but not planned have no follow-on documents, but must of course still be debited to the sales order. This is done for these parts using the standard quantity specified in the parts list.
Only when the parts requisition is released (traffic light on green), all costs of the non-planned parts are allocated to the cost units via the final costing.
All further costs arise automatically with the posting of the follow-up document.
The following disposition types are available for disposition from the parts request:
Disposition type | Description | Dispo account | Stock withdrawal | Availability | Charged | Post Calculation | Identification symbol | |
---|---|---|---|---|---|---|---|---|
No disposition | Parts are needed but do not need to be planned, for example because they are still found somewhere or because the standard MRP type in the parts warehouse account is set to "manual warehouse". | 0 | 0 | 0 | 0 | Parts list | 0 | |
Material withdrawal | Parts are taken from the warehouse via the staging list. Planned material withdrawals appear in the MRP account of the relevant part | 1 | 1 | 1 | Mission | Material withdrawal | 1 | |
Order request | Parts are ordered as required and made available via a goods receiving department | 1 | 0 | 1 | Mission | Incoming invoice | 2 | |
Construction contract | Parts are manufactured. | 1 | 0 | 1 | Mission | Construction contract | 3 | |
Preliminary material withdrawal | A part has already been reserved via an advance requirement before the parts request is created, which is now used for this parts request item | 1 | 1 | 1 | Mission | Material withdrawal | 4 | |
Preliminary purchase requisition | A part has already been ordered via an advance requirement before the parts request is created, which is now used for this parts request item | 1 | 0 | 1 | Mission | Incoming invoice | 5 | |
Advance production order | A part has already been produced via a preliminary requirement before the parts request is created, which is now used for this parts request item | 1 | 0 | 1 | Mission | Construction contract | 6 | |
Special material withdrawal | Parts are provided via the staging list, but no material withdrawal is created for this purpose. The part requisition item that has not yet been staged does not appear in the MRP account for the part | 0 | 0 | 1 | Mission | Parts list | 7 | |
remaining quantity | When creating a parts request for a remaining quantity part, it is checked whether the stock level is still positive, regardless of the amount.
| 1 | 1 | 1 | Mission | Material withdrawal | 8 | |
Disposition type | Description | Dispo account | Stock withdrawal | Availability | Charged | Post Calculation | Identification symbol | |
JIT part | Is regularly delivered by the supplier without having to be ordered | 0 | 0 | 0 | Mission | Parts list | 9 | |
Kanban part | The part request item appears in the MRP account and is posted to the warehouse reservation status. A material withdrawal is not necessary. However, the required material appears on the production documents and the parts list. Level 0 and BOM items are staged via the staging list. The corresponding parts list items are selected here and the menu item "Create goods withdrawal document" is selected. This marks the items as staged, even if no document is generated (fictitious booking). The replenishment of the storage bin is done automatically by the employees bypassing the system. | 1 | 0 | 1 | Cost centre | Parts list | 10 | |
Hand bearing part | The part request item does not appear in the MRP account and is not posted to the warehouse reservation status. Staging and material withdrawal is not necessary. However, this material withdrawal appears on the production documents and the bill of material. | 0 | 0 | 0 | Cost centre (transfer to non-disp. warehouse) | Parts list | 11 | |
Material overhang | For the parts request, which was originally set to "purchase requisition" or "production order", a sufficient amount of stock is available. The disposition type was changed automatically or manually to material surplus. This item therefore does not need to be planned but can be taken from the warehouse. With the setting "Consider scheduled stock orders" the expected quantity can also be taken into account. | 1 | 1 | 1 | Mission | Material withdrawal | 12 | |
Disposition type | Description | Dispo account | Stock withdrawal | Availability | Charged | Post Calculation | Identification symbol | |
Internal provision: Production order | Material is provided to the customer. Typically, such parts are subsequently found in the parts request below an order part. A production order is created for this item. All parts required for this production order become visible in the parts request and must be planned. | 1 | 0 | 1 | Mission | Construction contract | 13 | |
Self-provision: Purchase requisition | Material is provided to the customer. Typically, such parts are subsequently found below an order part in the parts request. Material is ordered and then sent to the customer. | 1 | 0 | 1 | Mission | Incoming invoice | 14 | |
Own provision: Material withdrawal | Material is provided to the customer. Typically, such parts are subsequently found below an order part in the parts request. The material is taken from the staging list in the same way as for a normal material withdrawal and then sent to the customer. | 1 | 1 | 1 | Mission | Material withdrawal | 15 | |
Customer provision | The customer will deliver the material. The parts requisition item behaves like a purchase order. It expects a goods receipt and is planned after it has been made available | 1 | 0 | 1 | click="javascript:toggle_dynamic_var(" | ");" title="Click to edit dynamic variable: | ">No value assigned | 16 |
Kanban semi-finished products | Kanban semi-finished parts are parts that are manufactured from larger raw material. For example a holder plate which is punched from a large raw material sheet metal plate. | 0 | 0 | 0 | Mission | Parts list | 17 | |
Disposition type | Description | Dispo account | Stock withdrawal | Availability | Charged | Post Calculation | Identification symbol |
Explanation of the general term "Kanban
Kanban is Japanese and means something like "card". It is a practical system of warehouse management in which a card is placed in each box in which parts are managed in the warehouse, under all parts at the bottom of the box. When the box is empty, the card becomes visible. Now the employee who has taken the last part out of the box must take the card and give it to the buyer indicated on the card. Depending on the replacement time of the part, there must then be 2 or more boxes of this part.
Every time a box is empty, a new one is ordered. In the time in which the box is ordered but has not yet arrived or is being produced, the remaining boxes are used.
1. determination of the disposition type of the parts
Based on the standard logistic identification of a part (in-house production, purchased or externally produced part) and its provision identification (disposable part, stock part, etc.), the type of disposition is automatically determined for each part in the Gozintograph. Thus, for example, non-stock-managed in-house production parts are set to the disposition type "production order", non-stock-managed purchased parts to the disposition type "requirement request" and stock parts to the disposition type "material withdrawal".
Material staging indicators such as manual storage part are parts that actually have the MRP type "material withdrawal". However, since such parts are not taken from the warehouse on an order-related basis using material withdrawal slips, and are therefore not "processed", such parts are set to the MRP type "No MRP".
Another irregularity is the "special material withdrawal". If a part requisition item is set to special material withdrawal, this requirement does not appear in the MRP account, but the item still has the status warehouse reservation - and can therefore be found via the staging list. These items must also be staged here, but no goods withdrawal documents are created. These parts also appear in the production documents as being to be taken from the warehouse.
The determination of the disposition type can either be influenced automatically by separate control systems or changed manually. If, for example, a purchased part that is not normally kept in stock should have a stock (e.g. due to a return delivery from a previous order), the system automatically changes the disposition type from "requirement request" to"material surplus ". The same applies to a production part in stock that may have been "left over" from a previous order. The parts can then be taken directly from the warehouse. Parts requisitions marked with this MRP type appear in the staging list under "Stock reservation".
The disposition type defined in a gozintograph - automatically or manually - can therefore be quite different from the "standard" procurement type. The "standard" procurement type determines the generally valid case and is (should) not (be) changed (modified) for specific orders.
A gozintograph is used to completely record the fully resolved parts lists of all parts. If a part is located below or within an assembly whose MRP type is "requirement request" or "material withdrawal", then this part or its quantity share - together with all parts of its bill of material - need not be considered further for MRP, as it is already contained in its superior assembly. For such parts, the MRP type is set to "not required". Conversely, if the MRP type of the superior assembly is changed to "production order" (if it is also an in-house produced part), the subordinate parts are automatically taken into account again in the MRP - the quantities (parts) become visible again.
The MRP type"No MRP" thus refers to parts that are definitely needed or must be used, but should not be planned. The MRP type"not required", on the other hand, refers to parts that do appear in the combined bill of material but whose superior part is not to be produced (the superior part does not have the MRP type "production order").
The determined or manually defined disposition type is displayed in the column "Disposition". In the next column - if necessary - notes are displayed whether the disposition type could cause problems in the following processing stages. If the check fails, a red warning point is displayed:
Disposition type | Exam |
---|---|
Construction contract | Valid work plan, master work plan |
2. determination of the standard procurement time according to the disposition type
The standard procurement time or also replenishment lead time is taken from the production role for the MRP type "production order" and from the order article role of the part for the MRP type "requirement request". For production parts this is the pure procurement time of the corresponding level (total lead time of the routing only for this production part, not for its assemblies). It is therefore not the total "delivery time" of the part. For parts kept in stock (material withdrawals) a duration of 1 day is entered as standard.
In addition to the standard procurement time, it is also possible to have the procurement time determined dynamically. This dynamic determination only affects parts that have received the disposition type "production order". Here it is now checked whether a routing has already been exploded on the possibly already attached production order. If so, the total time of the exploded routing is saved as the lead time for the parts request item.
If a routing does not yet exist for the production order, or if no production order has yet been created at all, the total time of the master routing is saved as the lead time for the parts request item.
3. scheduling of the necessary provision of parts
Due to the sequence of the production stages and the procurement times of the individual parts, there is a scheduling network of the parts among themselves (order network), which is best represented in the form of a Gantt diagram.
In forward scheduling, this collective order starts on a predefined date (the default value is the day of planning itself). In backward scheduling, the delivery date (or the staging date, if available) is used as the starting point. It is not possible to schedule into the past, i.e. even with backward scheduling the delivery or staging date can be postponed to a later date than desired. (A corresponding warning message is automatically issued by the system, the system then automatically schedules forwards!)
An influence on the delivery or provision date can be achieved by changing (shortening or extending) the procurement time: this results in an extension or shortening of the entire order network.
The starting point of scheduling - e.g. the delivery or provision date in the case of backward scheduling - is first transferred to the collective order as the"latest finish date". If you subtract the procurement time from such a "latest end date", you get a"latest start date". The different lengths of the procurement times within a production stage result in"earliest start dates" for individual parts, which can be earlier than the latest start date. Adding the procurement time to the earliest start date then results in an"earliest finish date" again.
In automatic scheduling over a period of time (e.g. "3rd week 2014"), the last working day of the period is set as the latest end in backward scheduling. This results in the latest start. Subsequently, the earliest start is determined from the latest start by deducting the duration of the period and the earliest end is determined on the basis of this.
Excursus: The production orders are transferred to capacity planning with their respective earliest and latest completion dates .
Automatic (non-graphical) forward scheduling:
See the Automatic Terminationsection
See also operating calendar and buffer times
In the case of requirements from part requirements (departure date), the planned date is made up of the earliest and latest start, which also results in a time span.
With the evaluation type "Strict", the earliest date of this time span is always used for the evaluation, with the setting "Medium" exactly the middle and with "Soft" the end of the time span, i.e. there is the least buffer for the real requirement.
If planning (e.g. stock replenishment) is always to be carried out with a little air, the setting "Medium" is recommended, which is always set in the standard system.
However, if there is little space in the warehouse or if the warehouse budget is always to be kept as low as possible, the setting "Soft" is recommended, whereby planning is always carried out on the actual demand date.
Strictly means, therefore, that the goods are always already procured at the earliest possible date and may also lie in the warehouse for some time until they are needed, depending on how large the buffer times of the requirements were.
4. checking the availability of materials
Checking material availability on the basis of the earliest or latest date in the parts request. This can be moved forward (with -) or backward by days or weeks. This shift is not calculated in calendar days but in working days, i.e. holidays and weekends are not included.
During the check, the subsequent part requirements are normally also taken into account, i.e. parts that are available for the order are also displayed, but are in the red due to other orders. If you select the checkbox "Ignore later requirements", these subsequent part requirements will not be considered!
On the one hand, it is possible to check the availability of stocked material on the desired date by checking the respective MRP account. The entries with the unavailable material are displayed selected in the list.
On the other hand, material overhangs can be checked: If a part is by default a purchase or production part, but remaining stock (material surplus) from previous orders is still available, these entries of the list are also displayed selected for further checking. As a reaction, the MRP type can be changed, for example, from requirement request to material withdrawal, whereby this part is no longer procured via purchasing, but is instead withdrawn from existing (surplus) stock.
These checks can also be graphically supported by means of a Gantt chart.
5. triggering of production orders, purchase requisitions and stock reservations
Once the disposition types and dates for all parts have been defined within the gozintograph, the further documents such as production orders, purchase requisitions and stock reservations can be created automatically.
6. release of the parts requirement
The release of the parts request blocks it from subsequent modification.
A. Link with ex ante requirements
If a sales order item is planned and preliminary requirements have been created for it, the following query appears, for example
If you press "YES", it means that a remaining quantity still reserved over advance requirements will be withdrawn from this specific sales order, put into stock and thus released for general free disposal.
If you press "NO" it means that you still want a remaining reserved quantity to remain available for this sales order and its further future dispositions.
In case of doubt, you should therefore answer "NO" here, i.e. leave the reserved quantities with this sales order.
Double-clicking on the part request item opens the individual disposition. Among other things, the quantity of the part requirement item can be changed there. For this purpose the editing field must be activated with the button next to the quantity specification. The quantity change is also carried out in the exploded parts list (predecessor of the parts requirement item) when saving the individual planning run. If the part requirement item has several predecessors, the system tries to distribute the quantity to all predecessors. This can result in the quantity of a BOM item being set to 0 or being greatly increased. If it is not possible to split the new quantity, a corresponding error message is issued and the quantity change is not saved.
C. Deletion of direct follow-on documents(production order, requirement request, warehouse reservation)
When deleting direct follow-on documents, the respective identifiers within the part request must be deleted, otherwise direct follow-on documents can no longer be created for the affected items.
To remove the identifier, there is the menu item Delete in the parts request under Edit. The various identifiers can be removed with the submenu items below.
Functionality
- Main window
- Individual disposition
- Dispatching structure
- List window
- Selection window
- Automatic scheduling
- Required capacity
Main window
In this window, a parts request (gozintograph) is processed that has arisen from the production parts lists summarised according to production stages within the framework of parts scheduling. The type of display and further processing of the parts request can be controlled via the options.
In the main menu the activities related to the whole part request are summarised, functionality related to single selected lines of the part request can be reached by using the buttons or the context menu (right mouse button on a line).
Double-clicking on a list entry brings up the maintenance window for a single list entry, an individual scheduling.
The column "Work plan" is used for a quick overview of whether there is anything to be considered regarding the work plans for production parts:
- Red dot: There is no master routing for the production part, so a routing cannot be exploded during further processing.
- Green check mark: A work plan has already been exploded on the created production order (perhaps it has already been changed)
If neither of the two cases applies to the parts requirement item, the column remains empty.
Menu item | Description |
---|---|
Edit | - |
: Disposition | - |
: : : Determine disposition type | Transfer of the standard procurement type from the parts master. This procedure must always be carried out first. A manual specification is possible by double-clicking on the list entry. |
: : Determine procurement time | If standard values are selected, the procurement time is determined from the production or order part role - according to the previously defined MRP or procurement type. With Dynamic, the procurement time for production parts is taken from the sum of the lead times of the master routing. If a routing has already been exploded for the production order, the total sum of the individual work sequences is determined as the lead time for the production part. For order parts, the procurement time is also taken from the order part role. |
: Termination | - |
: : Graphic | Backward or forward scheduling is done using a graphical tool for editing the Gantt chart (a separate licence is required). In the case of rescheduling, the Gantt chart is only called up for parts request items that are not completely finished/ready. For parts request items already in further processing, the earliest start date and the latest end date are taken over as fixed points in the Gantt chart. These are (can) no longer be changed. The mode "Show current scheduling" only opens the graphical view of the current scheduling, i.e. it does not change the existing schedules! |
: : Automatic | Backward or forward scheduling is determined internally and written to the gozintograph. With "fixed scheduling", the same start/end date is entered in all lines of the parts request (e.g. pure orientation on the end date). You can choose whether you only want to reschedule the previously undermined parts request items (e.g. also those items whose dates were previously deleted with the menu item "Delete" below) or also those items that have already been processed further. More on the subject of automatic scheduling in the automatic scheduling window. |
: : Delete | The start and end dates are deleted. |
: Check | - |
: : Material availability | see |
: : Material overhangs | For all parts of the disposition type unequal to material withdrawal, a possible availability in the warehouse on the desired date is checked. If stock is actually available on the desired date, these parts are displayed in a separate list. Such parts could then, for example, be manually changed to the MRP type "Remaining quantity". |
: : Capacity requirements | All required workstations are checked for the capacity in the required week and displayed in a window "Required capacity". |
: : Changed dates | Display of all part requests that no longer match the dates of the successor documents due to rescheduling |
: : : Open preliminary requirements | Listing of all open preliminary requirements for orders processed in this Gozintograph |
: Set module type | - |
: : Constructive assembly | A part marked with the disposition type production order is completely removed from the part request. This part is treated as a constructive assembly, which lowers the production level of all parts flowing into this assembly by one level.(Business Pattern) |
Further processing | - |
: : : Part request in one edit | All necessary steps for further processing of the part request are carried out in one run: Create production order, purchase requisition, stock reservation, release. |
: : Create first production order | For all parts of the disposition type production order, the production orders are created as items within a common production order. The options can be used to control whether and how the production order is to be processed further. |
: : Create first purchase requisition | For all parts of the MRP type purchase requisition, the purchase requisitions are created as items within a common purchase requisition. |
: : Make a reservation for storage | A warehouse reservation is made for all parts of the disposition type material withdrawal, remaining quantity, special material withdrawal. |
: : Release parts request | Once all necessary steps have been carried out, the part request should be marked as released - and thus completely processed. |
: : Stragglers | - |
: : : Create another production order | If a first production order has already been created, but a further production order becomes necessary due to a replanning of another part, this can be created using this selection. |
: : : Create another order request | If an initial purchase requisition has already been created, but a further purchase requisition is necessary due to a replanning of another part, this can be created using this selection. |
: : : Create another camp reservation | If a stock reservation has already been made, but a further stock reservation becomes necessary due to a replanning of another part, this can be created subsequently using this selection. |
: : Subsequent calculation of the parts requirement | Post all parts of the part requirements for preliminary costing and "non-planned" parts (e.g. JIT) also for costing. |
: Delete | - |
: : : Cancel release of parts request | The release of the parts request is withdrawn. This is always the first thing to be done if changes have to be made to the part request or if the entire part request has to be deleted. |
: : Cancel production order | After the already created production orders have been deleted, the internal identification must also be deleted here within the part request. |
: : Cancel order request | After the already created purchase requisitions have been deleted, the internal identification must also be deleted here within the part requisition. |
: : Cancel storage reservation | The stock reservation of the parts awaiting material withdrawal is cancelled. |
: : Take back stock reserve documents | Each item of the parts request is checked to see if there is a stock reserve document as a successor, if so, it is cleared and deleted if necessary. |
: : Reset calculation of the parts request | Write off all parts of the part requirements from the preliminary costing and "not scheduled" parts (e.g. JIT) also from the costing. |
: : Delete entire part request | The part request is completely deleted, the part disposition can be carried out again - possibly in another combination of the primary orders. |
: End position | - |
: : Cancel remaining quantity | The quantity of the selected part request items not yet made available is cancelled |
Close | The window with the part request is closed. If the part request has not yet been released, a warning message appears. |
Navigate | - |
: Generated production order(s) | The production orders generated from the parts request are displayed. |
: Generated purchase requisition(s) | The purchase requisitions generated from the part request are displayed. |
: Triggering part dispositions | The primary triggers of the parts lists summarised in the parts request are listed. |
: Completion change management | All open reverse transactions (stop sign next to the quantity) due to changes are then displayed in the transaction window "Final Change Management". From here, the quantities that are no longer required can be unwound (return documents, putaway of goods...) |
Options | A special window for selecting list display and/or filtering options opens. If this option window is closed, the list is rebuilt according to the selected options. |
Search | The list window is displayed. |
Context menu
Menu item | Description |
---|---|
Navigate | - |
: Parts demand trigger | For the selected lines of the part request, the primary triggers (sales order, stock order or advance requirement items) are displayed. |
: Parent(s) | For a single, selected part of the part request, all the parts in which this part is used are additionally marked in the list. |
Allocated part(s) | - |
: : List view | For a single, selected part of the part request you can either a) In the list view, additionally mark the parts that are required for the selected part (allocated from the selected part) or |
: : Tree view | b) display the entire MRP structure in the tree view. These views are only activated after the disposition has been run, because only then it is determined which parts are needed and which are not. |
Capacity requirements of the selected items | Determines the capacity requirements per calendar week and work centre for the selected items |
Change check Main disposition | What would change if an order item had to be produced by the customer? A result window opens, in which the changes that would result are displayed |
Change main disposition | - |
: No disposition | For the selected lines of the part request, the disposition type can be manually specified. A part should always be manually set to "No MRP" if it is not to be processed for M RP, i.e. it should neither be kept in the MRP account nor taken into account in the scheduling of the remaining parts: It is still needed nevertheless. Such a part is therefore still included in the costs of the final costing. If a part is no longer required at all, its quantity should be set to zero (individual disposition). |
Material removal | The part is reserved in the warehouse and is removed from there by means of a material withdrawal slip. |
: Order request | A purchase requisition is generated by the system for the part and forwarded to the purchasing department. |
: Production order | The system generates a production order for the part. |
: Preliminary material removal | The part is confirmed as being in stock, but the material withdrawal has already been carried out - with a material withdrawal slip, related to this order (post-calculation!) |
: Preliminary purchase requisition | The part is confirmed as a disposable purchase part, but has already been ordered. This type of MRP is automatically assigned by the system if an advance requirement was created for this part and order. If this disposition type is assigned manually, care should be taken in the sense of the post-calculation that the purchase costs are booked to this order. |
: Advance production order | The part is confirmed as a disposable production part, but has already been manufactured. This type of MRP is automatically assigned by the system if an advance requirement was created for this part and order. If this MRP type is assigned manually, care should be taken to ensure that the production costs are posted to this order for the purposes of final costing. |
: Remaining quantity | such as "material withdrawal", different identifier as message to warehouse personnel. |
: Hand bearing part | The part is confirmed as being in stock, but is not to be processed by the planning department (corresponds to the planning type "No planning"). |
Special material withdrawal | such as "material withdrawal", different identifier as message to warehouse personnel. |
: JIT part | In ClassiX® standard processing as "purchase requisition", customer-specific adaptations as agreed. |
: Kanban part | In ClassiX® standard processing such as "material removal", customer-specific adaptations as agreed. |
Generate secondary disposition | In addition to the main disposition of a part, a partial quantity can also be disposed of in another way. For example, if production is very busy and therefore cannot produce 100 pieces of a product on time, a partial quantity can be ordered from a supplier. After posting the secondary planning, all quantities no longer required for production are also cancelled and a request is made for a return to stock via the list "Evaluation - Logistics - Completion Change Management". |
: Order request | A requirement request is created for the selected part and linked to the part request item. The quantity that is planned via a purchase requisition is cancelled from all subordinate parts lists and production orders. |
: Production order | Not possible. Production order must always be the main scheduling. Solution to the problem : Set the logistics indicator in the part to "production part". Subsequently, "Production order" is used as the main disposition when generating the part request. For existing stock quantities, you can then create a "Stock reserve" secondary disposition. This is created automatically if you have selected "Use surplus quantities automatically" in the options. |
: Stock reserve | A warehouse reserve document is created that exclusively binds a surplus quantity from the warehouse to the parts requirement item. This quantity is then no longer available for other orders |
: Self-provision | A self-supply for the marked part is created. However, it does not cover the requirements of the item, which must be received in full quantity and planned via the main MRP. |
: Customer provision | A customer provision document is created: The customer has this part himself and wants his own part to be built into the component. |
Perform (partial) cancellation | Cancellation of the entire part request or partial quantities with a cancellation document |
(Partial) supply correction | Concluding a still open part request with a correction document (no cancellation) ! |
Symbol | Description |
---|---|
Edit part | |
Display production part | |
Display stock movements | |
Show stock level | |
Display disposition movements | |
Show logistics account | |
Show parts usage | |
Display document history | |
Display parts list | |
Edit work plan | |
Print list | |
Copy to clipboard | |
List all preliminary requirements for part requests | |
Graphical view of the current scheduling, the part request must therefore be scheduled beforehand! | |
Number | Select part request directly |
Release parts request or reset release |
Option window
Each time the part request window is opened, the options described here are reset to the default settings.
Menu item | Description |
---|---|
Edit | - |
: Set default settings | all changed settings are reset to default |
Field | Description |
---|---|
Display | |
: Display | - |
: : : Do not show parts without disposition | Only those parts of the parts requirement are shown that are scheduled according to the agreed scheduling rules. |
: : Show parts without disposition | Also those parts of the part requirement are shown which are used according to the parts list but are not available (e.g. manual bearing parts). |
: : Show all parts ("without disposition" AND "not used") | All parts of the parts request are shown, i.e. all parts of the parts lists summarised in the Gozintograph, regardless of their disposition. |
Disposition | |
: Overhang quantities | - |
: : Consume overhangs automatically | Surplus quantities are consumed. |
: : Consider scheduled stock orders | Normally a part in the logistics account has MRP or stock management set as the provision. This option allows the linking of both staging types for production parts. An MRP part is produced when there is a demand (e.g. sales order). This setting allows quantities to be produced in advance as a stock order, if a sales order is now scheduled in the parts requisition and the finish date of the stock order is before that of the sales order, a stock return document is automatically created and the part is not produced in addition. This setting can be used to achieve an optimised capacity utilisation for special machines or test equipment for certain products, e.g: |
: : Until minimum stock level | Only selectable if the check box "Automatic consumption" is activated. Overhang quantity is consumed until minimum stock level. |
Scheduling | |
End date | - |
: : Delivery date | For scheduling and scheduling, the delivery date specified on the order item is used as the end date. |
: : Date of provision | For scheduling and dispatching, the end date is the provision date specified on the order item. |
: : Production date | For scheduling and dispatching, the production date specified on the order item is used as the final date. |
: Daily date determination | - |
: : First working day in period | Since the Gantt chart makes the planning on the basis of daily data, the dates specified as periods (e.g. a delivery date specified as a calendar week) must be converted to a daily date. This option is used to select the appropriate conversion method. Starting from the start of the period (calendar week = Monday, month = 1st of the month, etc.), going forward into the future, the first working day found is used as the planned day. |
: : Middle working day in period | Starting from the middle of the period (calendar week = Wednesday, month = 15th of the month, etc.) the first working day found is used as the planned day. |
: : Last working day in period | Starting from the end of the period (calendar week = Sunday, month = last day of the month, etc.) the first working day found is used as the planned day backwards in the past. |
Automatic adaptation of production work plans | When rescheduling via simple scheduling, the new dates are directly transferred to the exploded work plans. For this, it is not necessary to clear the work center times beforehand; this is done by the system. |
Avoiding bottlenecks | For production parts, the system checks whether all work on the exploded routing items can be carried out on time at the specified workstations (capacity check - CTP). If no routing has been exploded for the part requirement item, this is simulated. The date for the entire production is postponed by one week into the future until all work sequences can be executed directly one after the other. The finish date can therefore be postponed. This is only possible in forward scheduling. |
Construction contract | |
: Explode task list | - |
: : automatic | If the production order is created for the parts to be manufactured, the work plans should be automatically exploded. If this option is selected, then it can also be determined whether the production order should then also be booked on a capacity basis. |
: : manual | If the production order is created for the parts to be manufactured, the work plans should not be cancelled. This is the case, for example, if no routings have been created yet. |
: Book capacity requirements | - |
: : automatic | If the option "Explode routing automatically" was selected, it can be additionally specified here whether the capacitive posting of the production order should take place after the explosion. |
: : manual | Although the option "Expand work plan automatically" has been selected, the direct capacitive booking of the production order is waived. |
Advance requirements | - |
: : : The technical release must be executed! | Enables the check of the status of the advance requirement items to be considered for production parts. At least the technical release for the advance requirement must have taken place. Otherwise an error message appears. |
Presets | |
: Global presets | Standard options |
: User Presets | The shortcut menu allows you to save user preferences. |
button | Description |
---|---|
OK | The settings are saved and the window is closed. |
Individual disposition
In this window a single entry of the entire part request is edited.
Menu item | Description |
---|---|
Edit | - |
: Dates | - |
: : Set | |
: : Delete |
Field | Description |
---|---|
Mission | Output of the number of the FIRST primary order (for information). |
Part | Output of the part number. |
Designation | Output of the part designation. |
Quantity | Output of the quantity. The button behind it serves to release the quantity for editing. |
Disposition | Disposition type of the part. Can be changed here for the individual part. If a part is not needed at all, the quantity must be set to zero here. The disposition type Not needed is only assigned automatically for parts not needed. |
Procurement time | Procurement time of the part. Can be manually adjusted here after the automatic run of the procurement time determination. |
Earliest start | Manual maintenance of scheduling |
Latest end | Manual maintenance of scheduling |
button | Description |
---|---|
OK | The changed entries are saved. |
Close | The window is closed. |
Dispatching structure
Menu item | Description |
---|---|
Options | - |
: Parts without disposition | - |
: : Do not display | Parts without disposition are not displayed |
: : Display | Parts without disposition are displayed |
In this view, for a part selected in the list view of the part request, the entire, dispositive structure of the (sub-)parts actually required for this part is displayed. As it is only known after the disposition which parts are actually required, this disposition structure can only be called up after the disposition. Optionally, you can only choose whether you want to display the parts "without MRP".
Displayed are the part number, the description, the required quantity, the type of disposition and - in case of multiple use - also the number of parts in which the respective part is used. By double-clicking on an entry within the tree, you can go directly to the corresponding entry in the list view, where you can then also view any multiple use (in the higher-level parts). (If parts are not displayed in the list view, please check the display options)
Cancellation of part requests
By cancelling a requirement trigger document (warehouse order, sales order, advance requirement), the parts requirement must also be cancelled so that the requirement no longer appears in the MRP account.
When a part request is cancelled, all successors in the part request are also cancelled, e.g. in the case of production orders, all items belonging to them are cancelled.
The following rules apply to cancellations, which are shown here schematically:
Procurement type | ..is stopped and can be found in loggicid | ...is cancelled |
---|---|---|
Storage reservation | Goods removal document already created | No stock removal document created yet |
Construction contract | has started AFO or already has a provided quantity. Successors are only cancelled if the cancelled quantity is greater than the staged quantity of the production order. These are cancelled proportionally to the difference. | has no started work sequences |
Order request | an order has already been created | no order has been created yet |
Calculation of the remaining quantity in the case of shortfalls in completed storage contracts
If a storage order item is marked as finished before the complete quantity has been put away, the remaining quantities are written into the slot cancelled.quantity, the status of the storage order item goes to "put away".
To end a warehouse order item early, a partial quantity must be created via a posted goods receipt. Here, on the one hand, there is the possibility of reporting the warehouse order as finished with a short quantity by ticking "Cancel remaining quantity", on the other hand, there is the possibility of doing the same in the warehouse order item itself via the traffic light.
If a partial quantity for a stock order item has been placed into storage and the traffic light is then changed from green to red, the stock order item is not stopped or cancelled, but marked as finished.
In both cases, the system branches to a cancellation document. Only after posting this cancellation document is the remaining quantity cancelled and the order status changed to completed or cancelled.
Also all Gozinto positions are adjusted and the remaining quantity is written into the slot cancelled.quantity.
If several BOMs have been combined when creating the gozintograph, whereby only one BOM item is to be stopped, cancelled or reported finished, then the quantity of the item to be cancelled must be determined proportionately. The following graphic is helpful for this:
Subsequent conversion of the disposition type
If, for example, a part originally planned as an order part is to be converted to a production order after the parts requisition has been released, existing production orders, material withdrawals and purchase requisitions may change.
For this reason, the conversion of a scheduled parts request item is not quite simple.
First of all, it should be checked whether existing parts request items are changed/added by the changeover.
This is done via the context menu of the list.
- The entry to be changed over is marked in the parts request and the context menu is opened with the right mouse button.
- A result window appears, which contains all newly added or existing changing parts request items. It shows the original and the newly determined quantity, as well as the statuses before and after the simulated changeover. In this way, it is possible to check in advance which further changes are to be expected:
The tested position previously selected in the list appears as the topmost position as the entry object. If a previously "sleeping" part request item (old status "Not required") is now required,"New part request item" appears in the first column on the left. If the part requisition item already existed,"Changed part requisition item" appears here.
If no existing parts requisition items with an MRP type material withdrawal, purchase requisition or production order have been changed, the item can be converted without hesitation.
So in the example above you don't see any critical changes either, the only changed parts requirement items were and are set to "No disposition".
The box"Hide unneeded" controls whether or not the "sleeping" part request positions that are not needed even after the simulated changeover are also displayed.
However, if parts request items that have already been processed are changed, further quantity changes are necessary. This may require contacting the schedulers of existing purchase requisitions in order to adjust the quantity to be ordered and to coordinate the quantities and dates with the supplier. For production orders, existing production papers must be collected and reprinted. These scenarios are not yet implemented in ClassiX®, the changeover is aborted by an error message. - More about this later...
If the disposition type is changed now, exactly the part requirements are created which were previously already visible in the preview window. At present, only a subsequent change from purchase requisition to production order is supported.
Now, the new parts request items have not yet been scheduled, which must be done manually via graphic scheduling.
Before that, the lead times of the new parts request items should be reset. This is currently done automatically when switching the disposition type.
If the final dates are correct again after the adjustment, the project is updated via the menu "Edit"-"Update project" and the dates are written back.
Overhangs and splitting
If a quantity of a standard MRP part is still available in a warehouse because, for example, the requirement of an original requirement trigger has been reduced or cancelled completely, this warehouse quantity (the so-called overhang quantity, see also " Check material overhangs" in the Gantt chart for part requirements) should be used up as quickly as possible. Overhangs can also occur when a part that was initially in stock is converted to "dispositive": any quantities still in stock at this time are then also treated as overhangs by the system.
ClassiX® offers the functionality to consider surplus quantities already when creating the gozintograph. For this purpose, an option "Automatically consume surplus quantities" is available in all option windows for creating a gozintograph. If this option is set, an additional - initially still unposted - stock reallocation document is immediately created for each recognised surplus quantity when the MRP type is determined. This document serves as an identifier for the reservation of the surplus quantity for the order(s) processed in the gozintograph.
The stock quantity is not actually reserved for the processed order(s) until the stock reset document is posted. This booking is triggered either manually by the user or by further processing of the gozintograph (e.g. by executing "Create first purchase requisition" in the case of excess quantities of purchase requisitions). The booking fails if another user has already used these surplus quantities while processing the gozintograph.
If an excess quantity is recognised and booked for a production order, all - secondary - part requirements subordinate to this production order are automatically reduced by the corresponding quantity. If, for example, 1000 screws are needed for a production order of 100 pieces, but 20 pieces are withdrawn from stock as surplus quantity, the withdrawal quantity of the screws is automatically reduced to 800 pieces. The quantity of screws that is now no longer required (200 pieces) is marked as a cancelled quantity in the parts requisition item of the screws (during final posting, see above).
If excess quantities are taken into account for parts requisition items (production order or purchase requisition), this has no effect on the scheduling (e.g. in the Gantt chart) of the corresponding parts requisition items: it is assumed that the respective excess quantity is available "immediately", the lead time of the parts requisition item is only based on the "main MRP", i.e. the lead time of the production or order part.
This splitting (of parts dispositions) can not only take place automatically in the case of surplus quantities, but can also be triggered manually in the gozintograph via the menu selection "secondary disposition". For example, in the event of bottlenecks in production, a partial quantity can be ordered or, conversely, in the event of a supplier's delivery bottlenecks, a partial quantity can be produced by the supplier. In the latter case, however - due to secondary dispositions - the main disposition must be the production order, with the purchase requisition as secondary disposition.
Which additional disposition can I create for which main disposition?
To illustrate this, the following table:
Main disposition\Subordinate disposition | Construction contract | Order request | Material withdrawal |
---|---|---|---|
Construction contract | - | ||
Order request | - | - | |
Material withdrawal | - | - |
This table shows all types of ancillary planning. A few examples and an explanation are provided for clarification:
In the left column you can read which main disposition type is on the part request item. In the columns to the right you can read off in the respective line which secondary MRP type can be created. It becomes clear that no auxiliary MRP "production order" can be created for any main MRP, only a purchase requisition and/or a stock reserve document can be created as auxiliary MRP.
Since - as already explained above - the scheduling of a stock return document is irrelevant, only the secondary dispositions that are purchase requisitions (replenishment lead times) need to be taken into account additionally when scheduling a collective order. As can be seen from the table above, this only applies to the main disposition "production order" and "material withdrawal":
- If the main MRP is a "material withdrawal", only the secondary MRP (=order requisition) is taken into account in scheduling
- If the main MRP is a "production order", an additional date bar is displayed in the Gantt chart: One - as usual - for the original parts requisition item of the production order and an additional date bar for the auxiliary MRP "purchase requisition". Thus, the schedules can be set independently of each other.
Rescheduling
See also calendar of operations
A parts request that has already been started can be rescheduled in the same way as a parts request that has not yet been started.
Please note that before any change is made, the approval of the parts request must be cancelled (set the traffic light to red)!
To do this, select from the menu "Edit - Scheduling - Graphic - Rescheduling" or "Edit - Scheduling - Graphic - Backward / forward scheduling" and reschedule the part request.
After scheduling, all follow-on documents that may exist for the individual part request items must be checked to see if the dates still fit, because during rescheduling, the dates of the follow-on documents (production order / requirement request) are not automatically adjusted.
In order to know which parts requirement items have changed after rescheduling, a list is opened after "Update project" in the graphical scheduling, which shows all changed parts requirement items.
This window can also be opened again at any time after closing it via the menu item"Edit - Check - Changed dates".
If the dates are now to be transferred to the subsequent documents, select the respective entry from the list and open the context menu with the right mouse button. Here there is the entry "Copy appointments to follow-on documents". The latest end of the part request item is taken over as date for the follow-on documents.
Please note that the work sequences are only adjusted to the end date (the work sequences are postponed by the same number of working days as the end date of the part request has been postponed)!
If the duration of a production order has been changed via graphic scheduling, the routing is not automatically extended as well! This must be done manually afterwards! (The system cannot know which work sequence now takes longer or which work sequence has been added!)
- For production orders, the cancelled routing is booked out, changed and booked in again. If the production order item has already been printed, it gets a "repeat print" indicator and can be found again via the worklist. When the production order item is printed again, this indicator disappears again.
- In the case of requisitions that have already been ordered, the date on the order item (delivery schedule line) must first be adjusted. If this is not done before the transfer, a cancellation message appears with the information that the order must first be changed to the date xx.xx.xxxx. If the order date has been adjusted, the date can be transferred to the requirement request.
Material withdrawals whose dates have changed are ignored when the list of changed dates is reopened. Material withdrawals do not have a follow-on document and therefore do not need to be handled separately. When this list is opened automatically for the first time, directly after rescheduling from the graphical view, these material withdrawals appear additionally in the list, since at this point in time all changed part requisition dates are generally displayed here.
Changing the processing time
With this dialogue it is possible to increase the total cycle time for the gozintograph and to distribute this as a percentage to the cycle times of the parts on the individual positions of the gozintograph.
However, the lead times of individual work sequences of the production orders do not change, only the earliest start date and finish date are changed. This gives the individual cost centres/workstations more time to process the order and can thus avoid peaks.
Field | Description |
---|---|
Dates : Dates | |
: : Current | Current dates (these are only displayed and cannot be changed). |
: : New | Depending on the choice of "base", either a different start or end date (as a starting point) can be entered ( a new lead time is calculated from this) or a new lead time is entered, from which in turn (depending on the choice of "base") a new start or end date is calculated. |
: : : Diff. (days) | Difference in working days between the respective date in the "Current" column and the date in the "New" column. |
: : Basis | The selected row is the calculation basis for the changes, i.e. either the start date is the basis - then a new end date can be entered - or the end date is the basis, then a new start date can be entered. The entry in one of the fields causes the recalculation of one of the other fields, e.g. if one changes the lead time with a fixed start date, the end date is recalculated and output. |
: : Is | After the calculation, the possible result appears here. |
: : Start | Start date - the earliest start date of the gonzitograph. |
: : End | End date - the latest end date of the Gozintograph. |
: : Processing time days | The respective turnaround time in days. |
: Jobs | If a workstation is selected in the list, the work steps within this workstation are displayed in the lower list. |
: : Number | Unique identification of the workstation / resource. |
: : Description | Description of the workstation / resource. |
: : Start | Start date as calendar week. |
: : - New | New start date as calendar week. |
: : End | End date as calendar week. |
: : - New | New end date as calendar week. |
: Work sequences | |
: : | Work sequence number |
: : Start date - old | previous start date. |
: : Lead time - old | lead time to date |
: : start date - new | New start date |
: : Work plan | Identification of the work plan. |
: : Description | Description of the work plan. |
Button | Description |
---|---|
Calculate | Using the new data entered, the new start and end dates are recalculated for all entries of the parts request. In addition, the newly calculated start and end dates are displayed in the list of workplaces for the workplaces of the production parts. |
Apply | The newly calculated start and end dates are transferred to the parts request. |
Menu item | Description |
---|---|
Edit Resource | |
Worklist | |
Capacity overview | |
Capacity utilisation | |
Display current scheduling | Display of the gonzitograph |
Self-provision
If, for example, a "brick lining" service is ordered from a supplier, in which this supplier is to install something in a finished assembly (brick lining), the assembly must be built to schedule before the brick lining is ordered.
So from the parts list it must look like this:
Order part "brick lining" has the following parts list entries in its production role:
- Sub-assembly A
- Sub-assembly B
Sub-assembly A must be provided to the supplier in order to enable the supplier to perform the ordered service. Sub-assembly B is provided by the supplier himself.
In the parts request, there is therefore the brick lining with the procurement type "purchase requisition".
Now, however, a production order must be created below this purchase requisition so that the assembly is executed before the brickwork is ordered:
There are two ways to do this:
- Assembly A is generally a part that must always be manufactured and supplied. In this case, simply set the procurement type in the logistics account for the part to"In-house provision: MRP". With "Internal provision: warehouse" it is assumed that this part is in stock and the resulting part requirement item is automatically set to "material withdrawal".
- Only in this case assembly A is a self-provision: The option (option window via menu item "Options" in part request) "Show all parts (without MRP AND unused)" must be set in the part request. Then the list is sorted by part number and the assembly A is selected.
Subsequently, all parts that are not required or not planned are also displayed. Now the part to be provided is searched for and its main MRP type is changed to the corresponding in-house provision (production order, purchase requisition or material withdrawal). An internal provision document with all required data is created immediately. Now the items that are not required in the parts requisition can be hidden again via the options. When processing the parts request further, a production order, a purchase requisition or a warehouse reservation is now created for this item and its required sub-items, depending on the standard procurement type.
For information on the further course of the self-provision, see here.
List window
Serves to list or search for part requirements (Gozintographs).
All transaction types that exist in the ClassiX® system can be dragged into the list with the mouse.
If there is a follow-up parts requisition for the item dragged into the list, or for one of its sub-items, these are displayed in the list.
Menu item | Description |
---|---|
Edit | - |
: Successor | - |
: : Generated production order | If a production order has already been created for the selected part request, it will be opened |
: : Generated purchase requisition | If a requirement request has already been created for the selected part request, it will be opened |
: Precursor | - |
: : : Triggering part disposition | The sales order items for which the selected partial requirement was created are displayed in the parts planning list. |
Tests | Obsolete functions, do not use them anymore! |
: : Precursor parts | |
: : Full part number | |
: : Quantity | |
: : Disposition status | |
: Service | - |
: : Structure/order numbers | |
: : Index | - |
: : : Formation | |
: : : Delete | |
: : Repair release |
Symbol | Description |
---|---|
Edit part request | |
Print parts request | |
Copy all part requests to the clipboard |
Field | Description |
---|---|
Number | Search by number. If no number is entered, the last 100 part requests are listed |
1st order | Search for part requests that are successor documents to the entered job. If no job number is entered, the last 100 part requests are listed |
Not released | With the button "Display" you can display all the part requests that are not released |
Date (Created) | Search part requirements by date of creation |
Date (release) | Search for part requirements by date of release |
Editor | Search part requests by the processor. With the two radio buttons next to the "Editor" button, you can select whether you want to search for the creation or release editor. |
button | Description |
---|---|
Edit | The current part request is displayed in the main window. |
Close | The window is closed. |
Selection window
This window is used to select part requests (Gozintographs).
Field | Description |
---|---|
Number | Search by number |
1st order | Search by order |
button | Description |
---|---|
OK | The selected part request is accepted. |
Close | The selection is cancelled. |
Automatic scheduling
The automatic scheduling offers the possibility to schedule the entire part requirement either from a start date forward or from an end date backward fully automatically.
This type of scheduling simulates the resulting work sequences, if they have not already been resolved, and plans them into the actual utilisation of resources to identify bottlenecks.
Furthermore, in the automatic scheduling window it can be checked whether parts are/will be available on the specified date. Bottlenecks (material or capacity) are pointed out, or they are automatically bypassed by scheduling shifts. It is also possible to clear up the remaining bottlenecks later in the manual graphical scheduling.
There are two possibilities to circumvent the bottlenecks, or workplace-specific holidays or insufficient capacity:
: Seamless scheduling in case of bottlenecks | Tick: If a bottleneck occurs for a work sequence, not only is the deadline for this work sequence postponed, but the entire planning is postponed by one week until all the necessary work can be completed in one piece. Unchecked: If a bottleneck occurs for a work sequence, only the deadline for this work sequence is postponed, so that the total lead time for the production order is extended by a certain waiting time. If this check mark is set, an earlier finish date may be possible if there are bottlenecks with some resources. This scheduling is particularly suitable for stocking orders, whereby the scheduling only fills the open "gaps" in capacity utilisation. |
The set scheduling options are saved on the part request item (seamless scheduling and avoid bottlenecks).
If another work sequence is subsequently inserted into a production order, it is scheduled with the same settings as the entire parts requirement before it.
Note: The operating calendars of the individual workstations or production areas are taken into account for scheduling. For example, it is possible to schedule the welding shop fully in the first calendar week of the year, with all other production areas being free at this time.
After automatic scheduling, a message will appear to indicate whether the planned delivery date could be met, and information on capacity and material bottlenecks will also appear in the list in the scheduling window.
More about rescheduling and the general scheduling of the necessary provision of parts.
Symbol | Description |
---|---|
Print window | |
Display stock movements | |
Show stock level | |
Display disposition movements | |
Show logistics account | |
Edit workstation | |
Worklist | |
Graphic display of the utilisation of the selected resource / calendar week | |
Capacity overview | |
Capacity utilisation of the selected resource | |
Copy all list entries to the clipboard |
Field | Description |
---|---|
Direction | |
: Backwards | Scheduling starts with the date entered as the latest end date and subtracts the individual throughput times until start dates are reached for the individual production stages. |
: Forward | Scheduling starts with the date entered as the start date of the lowest levels and adds the throughput times until an end date for level 0 is reached. |
Start or end date | This date is used for scheduling. Either as a start date in forward scheduling or as an end date in backward scheduling. |
General | |
: Seamless scheduling in case of bottlenecks | Tick: If a capacity bottleneck or a production-specific holiday occurs for a work sequence so that the work sequence cannot be completed in the planned calendar week, not only is the date for this work sequence postponed, but the entire planning is postponed by another week until all the necessary work can be completed in one piece. Check mark not set: If a capacity bottleneck or a holiday specific to a production site occurs for a work sequence that the work sequence cannot be processed in the planned calendar week, only the date for this work sequence is postponed so that the total throughput time for the production order is extended by a certain waiting time. By ticking this box, the final date can be moved closer if there are bottlenecks with some resources. |
Material (ATP) | |
: Check material bottlenecks | Scheduling is checked for material bottlenecks. These bottlenecks found are then displayed in the results list of the scheduling window. The checked, uncorrected bottlenecks are marked in the list with a red stop sign. |
Capacity (CTP) | |
: Check capacity bottlenecks | In the case of production parts, it is checked whether all work at the production points can be carried out on time at the specified workplaces (capacity check - CTP). If no routing has yet been exploded for the parts request item, this is simulated. These bottlenecks found are then displayed in the results list of the scheduling window. The checked, uncorrected bottlenecks are marked in the list with a red stop sign. |
: Automatically bypass capacity bottlenecks | Any capacity bottlenecks found are bypassed by postponing them by one week until sufficient capacity is available (see also option "Seamless scheduling in case of bottlenecks" here in the table. Holidays at specific workstations / production sites are always bypassed regardless of this option. |
: Automatically adjust exploded production schedules | The determined dates are transferred directly to the exploded work plan items, so there is no need for subsequent adjustment. This option is only active if there is already an exploded production routing! |
List of results | Here, a red stop sign indicates the bottlenecks that have not been eliminated and a green check mark indicates those that could be bypassed. |
button | Description |
---|---|
OK | Starts the termination with all set parameters |
Close | The window is closed. |
Required capacity
This window provides an overview of all required workstation resources in the respective calendar weeks.
Even if routings or production orders have not yet been exploded, the system simulates the requirements and adds them to the actual current requirements.
Symbol | Description |
---|---|
Print window | |
Edit workstation | |
Worklist | |
Graphic display of the utilisation of the selected resource / calendar week | |
Capacity overview | |
Capacity utilisation of the selected resource | |
Copy all list entries to the clipboard |
Field | Description |
---|---|
List | All resources required for the partial request are displayed with the calendar week in the list. The planned, required and already booked capacity is displayed, as well as a green box if there is sufficient capacity for the planned sequence, or a red bitmap if there is not enough capacity for the planned sequence |
button | Description |
---|---|
Close | The window is closed |
Related topics
- Index
- Change management in general
- Change management: Change the quantity of the parts request item
- Gantt chart
- Operations calendar
- Parts scheduling
- Technical release
Technical documentation
- preConstraints-postConstraints Connections of the part requirement items to each other
- Overview
- Implementation
- Quality assurance
preConstraints-postConstraints Connections of the part requirement items to each other
The connection in a part request of the positions among each other still below (to dispose before me) and above (will be produced with me after me) is done by the connection preConstraints (before me) and postConstraints (after me).
This connection makes it very easy to determine for which part requirement item a different part requirement item is needed.
No need to go through the complicated BOM predecessor item.
If a part requirement item is to be cancelled, all part requirement items to be scheduled before this item must also be adjusted in the correct quantity ratio (or cancelled if cancelled item is the only predecessor) - these can now be determined very easily.
If a part is required at several points in the parts list across several production levels, it always appears at the lowest level in the parts request, since these are planned first (it is double-wired by postConstraints!).
Example:
A blower to be manufactured in-house is to be installed in a switch cabinet.
M6 screws are required for both the control cabinet and the blower (they are present in both parts lists).
So the parts lists look like this:
Switch cabinet:
- 4 support strips
- Metal cabinet
- 50 screws M6
- Blower
blower:
- Engine
- Controller
- Fan wheel
- Housing
- 20 screws M6
A total of 70 M6 screws are therefore required. In the part request, identical parts are grouped together (e.g. so that the same production order is not created 3 times for the same part). Therefore it is now necessary to procure the screws in their entire quantity at the earliest required date, i.e. at the time the fan is manufactured. The part request item appears with the highest required level and will be scheduled as early as possible.
Technically, the parts requirement position of the M6 screw is now connected to 2 postConstraints, namely that of the blower and that of the control cabinet.
If the blower is now cancelled via the parts list, the parts requirement position of the screws is reduced in quantity and moved directly below the level of the control cabinet.
Overview
Part requirement basic module
Module name
itdemand.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
Message | Parameters | Function | Security |
---|---|---|---|
ITEM_DEMAND_CHANGED | Part Request Object | Parts requirements have been changed | |
ITEM_DEMAND_CREATED | Part Request Object | Part request was generated | |
ITEM_DEMAND_DELETED | Part Request Object | Part request was deleted |
Message | Parameters | Function | Receiver module |
---|---|---|---|
EDIT_ITEM_DEMAND | NULL or part request object | Open the input window for part request | Part requirement editing module |
Part request editing module
Module name
itdemedt.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
Message | Parameters | Function | Security |
---|---|---|---|
DELETE_ITEM_DEMAND | |||
EDIT_ITEM_DEMAND | NULL or part request object | Open the input window for part request | |
ITEM_DEMAND_CHANGED | Part Request Object | Parts requirements have been changed | |
ITEM_DEMAND_CREATED | Part Request Object | Part request was generated | |
ITEM_DEMAND_DELETED | Part Request Object | Part request was deleted | |
LIST_ITEM_DEMAND | Collection part request objects or NULL | Open list window for part request | |
LOAD_ITEM_DEMAND | Import parts request | ||
PRODUCTION_ORDER_CREATED | |||
PRODUCTION_ORDER_DELETED | |||
TMP_DISPOSITION_WIN |
Message | Parameters | Function | Receiver module |
---|---|---|---|
APPEND_PURCHASE_REQUISITION | |||
CREATE_PRODUCTION_ORDER | |||
DELETE_ITEM_DEMAND | |||
EDIT_BILL_OF_MATERIAL | |||
EDIT_ITEM | |||
EDIT_ITEM_DEMAND | NULL or part request object | Open the input window for part request | Part requirement editing module |
EDIT_JOB_SCHEDULE | |||
EDIT_PRODUCTION_ORDER | |||
EDIT_PURCHASE_REQUISITION | |||
EDIT_STOCK_ACCOUNT | |||
ITEM_DEMAND_CHANGED | Part Request Object | Part requirement has been changed | |
ITEM_DEMAND_CREATED | Part Request Object | Part request was generated | |
ITEM_DEMAND_DELETED | Part Request Object | Part request was deleted | |
ITEM_DEMAND_RELEASED | |||
ITEM_DEMAND_UNRELEASED | |||
LIST_ALLOCATOR | |||
LIST_ITEM_DEMAND | Open list window for part request | Part requirement editing module | |
LIST_ITEM_DISPOSITION | |||
LIST_ITEM_STOCK_SUB_MONITORS | |||
SELECT_DISPO_ACCOUNT_LOGGINGS | |||
SELECT_STOCK_LOGGINGS | |||
SHOW_PREVIEW | Widget | Print Preview | Print Preview |
TMP_DISPOSITION_WIN |
Parts request selection module
Module name
itdemsel.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
Message | Parameters | Function | Security |
---|---|---|---|
ITEM_DEMAND_CHANGED | Part Request Object | Parts requirements have been changed | |
ITEM_DEMAND_CREATED | Part Request Object | Part request was generated | |
ITEM_DEMAND_DELETED | Part Request Object | Part request was deleted | |
SELECT_ITEM_DEMAND | Collection part request objects or NULL, recipient of the response | Call up selection window for part request |
Message | Parameters | Function | Receiver module |
---|---|---|---|
EDIT_ITEM_DEMAND | NULL or part request object | Open the input window for part request | Part requirement editing module |
ITEM_DEMAND_SELECTED | Part request object, recipient | Part request was selected |