|
| 1 | +====== |
| 2 | +Delays |
| 3 | +====== |
| 4 | + |
| 5 | +.. |SO| replace:: :abbr:`SO (sales order)` |
| 6 | +.. |SOs| replace:: :abbr:`SOs (sales orders)` |
| 7 | +.. |MO| replace:: :abbr:`MO (manufacturing order)` |
| 8 | +.. |MOs| replace:: :abbr:`MOs (manufacturing orders)` |
| 9 | +.. |RfQ| replace:: :abbr:`RfQ (request for quotation)` |
| 10 | + |
| 11 | +Odoo's *Manufacturing* app displays *delays* in manufacturing orders through the :guilabel:`Delayed |
| 12 | +Productions` filter. If the |MO|'s end date exceeds its deadline, the deadline is highlighted in red |
| 13 | +to draw attention to the delay. |
| 14 | + |
| 15 | +.. image:: delayed/delayed-filter.png |
| 16 | + :alt: The delayed production filter in Odoo. |
| 17 | + |
| 18 | +Deadline calculation |
| 19 | +==================== |
| 20 | + |
| 21 | +The |MO| deadline depends on how the |MO| was created, and is calculated as follows: |
| 22 | + |
| 23 | +- **Make To Order**: the |MO| deadline is the *Sales Order Delivery Date*. |
| 24 | +- **Replenishment**: the |MO| deadline is *today + Manufacturing Lead Time*. |
| 25 | +- **Manually created MO**: the deadline field remains empty. |
| 26 | + |
| 27 | +.. important:: |
| 28 | + The |MO| *deadline* is not the same as the |MO| *end date*. |
| 29 | + |
| 30 | + The end date is computed as: |
| 31 | + |
| 32 | + .. math:: |
| 33 | + \text{End date} = |
| 34 | + \text{Scheduled start date} |
| 35 | + +\text{Total duration of all operations} |
| 36 | +
|
| 37 | +Filters |
| 38 | +======= |
| 39 | + |
| 40 | +Several additional filters are available to help track delays: |
| 41 | + |
| 42 | +- :guilabel:`Delayed Productions`: the |MO|'s *scheduled start date* is later than the deadline. |
| 43 | +- :guilabel:`Late`: the |MO|'s *scheduled end date* exceeds the deadline, highlighted in red. |
| 44 | +- :guilabel:`Late Availability`: one or more required components are not available before the |
| 45 | + deadline. For example, a confirmed purchase order or manufacturing order for components is |
| 46 | + scheduled to end *after* the |MO| deadline. |
| 47 | +- :guilabel:`Components Available`: all components are available to begin production. |
| 48 | + |
| 49 | +Use case |
| 50 | +======== |
| 51 | + |
| 52 | +Consider an |MO| with a deadline of **September 17th**: |
| 53 | + |
| 54 | +- If production on the |MO| starts after September 17th, it appears in the :guilabel:`Delayed |
| 55 | + Productions` filter. |
| 56 | +- If required components are scheduled to arrive after September 17th, the |MO| appears in the |
| 57 | + :guilabel:`Late Availability` filter. |
| 58 | +- If the |MO| has a scheduled end date after September 17th, it appears in the :guilabel:`Late` |
| 59 | + filter. |
| 60 | + |
| 61 | +.. image:: delayed/deadline.png |
| 62 | + :alt: An MO with the deadline emphasized. |
| 63 | + |
| 64 | +By combining these indicators, planners can quickly identify where production is at risk of missing |
| 65 | +delivery commitments. |
0 commit comments