AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 25.10.2024, 17:13   #1  
Blog bot is offline
Blog bot
Участник
 
25,617 / 848 (80) +++++++
Регистрация: 28.10.2006
erconsult: Assistance and Secondary operations in D365 for SCM to separate machining costs from labour
Источник: https://erconsult.eu/blog/assistance...s-from-labour/
==============



Assistance and Secondary operations in D365 for SCM to separate machining costs from labour





In Dynamics 365 Supply Chain Management (SCM), in its recent internal MES incarnation called “Production Floor Execution” (PFE), there is a notion of Bundle and Assistance.

If workers handle several production orders at once it is called bundling. This setup shares labour costs across orders, lowering the cost per item: M orders : 1 worker. If multiple workers share one job, it is called assistance. A lead worker (Pilot) is assigned the production order job, and other workers join as assistants. The Pilot’s time is replicated into the Assistant’s time records, thus increasing the labour cost per item: N workers : 1 order.

In a general case, the relation between the orders and workers may be M:N, if a Team of assistants and the pilot takes on a bundle of production orders.

Now, the Assistance model help solve a controlling task: recording machine costs and labour costs separately. For example, setting a machine up consumes less energy than a full speed machine operation: during the setup operation, the labour cost prevails if we neglect the amortization. On a contrary, once a highly automated work cell is programmed and set up, the worker may leave and let the cell work on its own. The machine cost prevails. Consequently, instead of a blended rate of the machine hour, we may decide to split the hours into 2 different route categories: one for the machine, one for the worker, and even one for the energy consumption.

Primary vs. Secondary operations

In Dynamics 365, production steps are called operations. Some operations are “primary”, meaning they control the main task, usually involving a machine or workstation. Others are “secondary”, like additional labour or support roles, running alongside the primary task. These can help track labour costs separately and in real-time.

Primary and secondary operations share the same operation number but have different Operation IDs in Dynamics 365. They both run at the same time, and the primary operation controls how long the job lasts.
The key is, secondary operations allow for distinct cost recording for personnel assisting a machine operation.

Setting up secondary operations for labour cost tracking
  1. Define distinct Production control > Setup > Routes > Cost categories for the machining and for the labour.
  2. In Production control > Setup > Routes > Route groups, create one group and activate the Setup and/or Process jobs appropriately. Check Job management and Capacity to make the jobs visible on the PFE terminal. Turn on the Setup time and/or Run time estimation and costing.
  3. Define secondary operations in the Route: specify the main machine task as the primary operation and the labour support task as the secondary
  4. In Production control > Setup > Manufacturing execution > Configure production floor execution, choose Design tabs and make sure the button (Action) “Assistant” is placed onto one of the toolbars.
  5. Check if the system jobs Start assistance and Stop assistance exist under Time and attendance > Manage indirect activities > Indirect activities. Use Time and attendance > Setup > Wizards > Time and attendance configuration wizard if they don’t.
  6. Go to Production control > Setup > Manufacturing execution > Production order Defaults and check Assistants use secondary operations on the Operations tab. This setting lets assistants’ time be logged under the secondary operation, ensuring correct labour cost tracking.
  7. Make sure a dummy worker representing the machine exists alongside the real machine operator and they are activated for Time registration in the Time and attendance > Setup > Time registration workers.
  8. With the setup in place, Release a test production order.
  9. Open the Production control > Manufacturing execution > Production floor execution terminal.
  10. Let the machine “register itself” first with its fictive Badge ID. The primary jobs are listed:
  11. Let the machine “Start job“. The machine becomes “the Pilot”.
  12. In a “shared terminal” scenario such as ours, the PFE terminal usually immediately logs the user=machine off, otherwise click Leaving / Log off.
  13. Log in as a human worker (machine operator) with your own Badge ID.
  14. Use the Assistant button on the PFE terminal to “attach” yourself as an assistant to the Pilot=machine.
  15. You will see a “You are now registered as an assistant” message right after.
  16. Check Time and attendance > Inquiries and reports > Teams: there is now a Job pilot driving the primary operation and an assistant Worker attached to it. The Resource pilot is a remnant of a nice feature Assist Resource. The Assist Resource is supposed to be a machine or a similar asset acting as the Pilot instead of a dummy machine worker, making it simpler to track time. However, the corresponding function Assist resource is defunct on the modern PFE terminal: the necessary twin action Start resource jobs from the legacy Job card terminal is not implemented in the Production floor execution, so the Assist resource does not do anything meaningful.
  17. Check the time records of the day in the Time and attendance > Review and approve > Approve list: a Start assistance is recorded for the worker. The T&A module quietly listens to everything what the pilot does:
  18. After a while, Clock out the human worker.
  19. Check the time records in Time and attendance > Review and approve > Approve: the T&A module has now copied all the records of Pilot=machine to the Assistant during the active assistance period, yet the Process Job ID is not the same, it is the one of the secondary operation with its distinct cost rate! This does not work properly if you use register operations instead of jobs. Specifically, a Job level = Route is a no-go in Production order defaults.
  20. Check Time and attendance > Inquiries and reports > Teams again: the team is disassembled. If the worker mostly serves the same machine, you may activate the Permanent teams in the Production control > Setup > Manufacturing execution > Manufacturing execution parameters. This will auto-attach the human worker to the machine on subsequent clock-ins.
  21. At the end of the shift, assistants must clock out first: the Pilot can’t clock out until all assistants have done so. Alas, Clock out the machine.
Separate energy cost

In the above scenario, the human machine operator may come and leave at will, his or her working time is independent from the machine schedule. Recording a separate energy contribution is a slightly different, simple scenario.
Here we may use secondary operations, too. If we can attribute a certain volume of natural gas or electric energy to one hour of the machine’s operation or to a kilogram of the product / semi-finished product, then this overhead may be posted synchronously with every machine time/quantity route transaction.

Create a special Route group for the secondary operation. Deactivate Job management, because the electricity meter is not going to actively post its working hours. Turn on the Run time (=constant consumption in kWh per machine hour) or Quantity (=constant consumption in kWh per machined piece) in the Automatic route consumption group. Do it in sync with the Estimation and costing sliders.

Assign this cost group to the secondary operation on the route. This will be NRJ in the following example:









Production and Manufacturing blog series



Further reading:

Integrate APS with Dynamics 365 for SCM
D365 Mass de-reservation utility
Picking list journal: Inventory dimension Location must be specified
Consumable “Kanban” parts in D365 Warehouse management
Subcontracting with Warehouse management Part 2
Subcontracting with Warehouse management Part 1
Semi-finished goods in an advanced warehouse
The case of a missing flushing principle</p>





The post Assistance and Secondary operations in D365 for SCM to separate machining costs from labour appeared first on ER-Consult.



Источник: https://erconsult.eu/blog/assistance...s-from-labour/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
Assistance use secondary operations gerwald DAX: Функционал 1 28.05.2016 23:45

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 10:01.