Checklist for Scheduling

Owned by Mac Jacob
Last updated: Mar 03, 2022 by Mia Nall
4 min read

Before Loading

  • "Complete" any committed orders you do not want to retain (like past orders).

  • "Commit" any scheduled orders that you want to retain.

  • "Uncommit" future "committed" items that you want to be deleted.

Existing Orders

Phenix will generate unique order numbers for all production orders that are imported to Phenix without an order number/identifier. Thus, Phenix will not be able to match new orders with the existing ones, and will accidentally create a new order rather than updating or ignoring.

If you would like to update an already created/imported order, please make use to import the order with it’s unique identifier/order number. Phenix will update the order quantity (if applicable), and change the order status to unscheduled. To make sure committed orders remain committed in Phenix, make sure they are not in orders import file.

Phenix offers the possibility to delete all orders or all non-committed orders during the import process. This means you may import all orders and schedule with only the orders from that import, with no orders from previous imports.

Load Production Orders

  • Obtain production order file in the correct format.

    • The file formatting instructions can be found in the Importing New Orders chapter.

    • If the orders file includes order numbers, make sure that orders committed in Phenix are not in the file.

    • If orders are imported without numbers, make sure that their due dates are outside of Phenix committed zone.

      • Normally orders that are in Phenix committed zone (opening weeks of time horizon) should be handled in the ERP system (e.g. SAP) directly.

  • Import production orders:

    • Go to Import->Orders.

    • Delete old conflicts (recommended).

    • Click and drag the production orders file to the box (or click in the box and navigate to the file).

    • Map Production order input file - below are minimum required mappings without and with order number (identifier)

  • If you want to transfer firmed orders with the scheduled dates from the ERP system, you will need to add 2 more fields to the file and map them to the respective Phenix order characteristics: "Status" and "Import Scheduled Date". More about this in the Importing New Orders chapter. Example of such mapping:

  • After mapping all required and desired mapping options Choose Ignore Unmapped or map them to existing or "New Attribute".

  • If mapping to a new attribute, give it a column name and choose type "Text".

  • Choose Continue.

  • Review messages - if everything is OK:

    • Tick the box marked "Delete existing uncommitted orders for selected lines".

    • Optionally tick the box marked "Also delete existing committed orders for selected lines".

    • Click confirm import

  • Return to import and review/address conflicts.

  • Check Production order load if desired.

Schedule each Line:

  • Lines -> Choose Line (330-1, 330-2, Hassia) -> Schedule

  • Check and adjust wheel cycles lengths and start dates

    • Each should be 7 days long and start on Monday

    • If showing longer, this could be one of several reasons

      • A week overflowed and a cycle was started early or late - this is legit, adjust the next cycle to bring back to Monday

      • A plant down is planned - this might result in a double length cycle for the week / cycle containing the down.

  • Select all unscheduled orders and schedule

    • Select first unscheduled (at bottom)

    • Click the box at top of table

    • Choose schedule

    • Alternatively,

      • Use select and Shift-select or ctrl select to select the orders to schedule

      • Choose schedule

  • Review "early" new (green) orders and decide disposition

    • Review SAP for each

    • Add them to current (adjusting other batches) - or -

    • Cancel them - or -

    • Move them to current planning week

  • Review "needs attention" list

    • Review SAP for each

    • Add them to current (adjusting other batches) - or -

    • Cancel them - or -

    • Move them to current planning week

  • Adjust production order week

    • Note production orders that were changed

  • Work through current planning week

    • Review Formulas and Days

      • Look at BOM 1 cumulative and target batches

        • For successive days of same type, previous day target is +1

      • Pull forward to fill days with formula and basic type

        • Look ahead for pull forward using Current Cycle, formula Frequency and SKU frequency

      • Notate RTO end of mix and pull forward batches in process note

      • Use copy order to bridge across day end

      • Use efficiency adjustment to fit orders into desired day

    • Note total days

    • After all lines are scheduled and days are known

      • Use delay to next availability to position orders into correct days

      • Use spoke add, copy order, create order to add brites appropriately

        • Note can code

  • Select and commit orders for week once created

  • Select modified production orders

    • Export orders

      • In the … choose export

      • File will appear at bottom of page

      • Check file

      • Load into SAP (list steps for load)

  • Select orders for week

    • Export orders

      • In the … choose export

      • File will appear at bottom of page

      • Check file

      • Load into SAP (list steps for load)