Some starting for automatic production

Hello

Before answer you, I talk to you about n8n, but Axelor do « the same » but inside, it’s « BPM module »
You can find here a discussion recently I have with other French : Stratégie et feuille de route d'Axelor
Some questions and situation I asked kind of similar to you for specific automation.
(only french sorry. Translate all the conversation)

Axelor BPM could be an answer to you (probably not in 5 weeks). I won’t be useful for this, I don’t use BPM. But people here can help you.

I use n8n apps, because its external, so you can call everything with GET, PUT, POST, DELETE and change whatever you want from another app. Automatically and do a small interaction or a big one.
In you case, for a list of pieces to use for a production that is not standard, it could be very useful (I come back on it later :wink: )

I think you don’t use the stock module. You have to define stock location, it can be virtual (like when you buy pieces, it come from you manufacturer, but it a virtual one because you don’t have to handle it).
it can be physical (your storage1, your production place, your storage2 …).

If a delivery is validate, you should see the stock in you inventory (depend of the manufacturer parameter, product parameter, deliveryOrder …)
And you will have all the StockMove and StockMoveLine per product you want. Me, I use trackingNumber for my medical device.

All the documentation Axelor is here about stock :



I just made a test, I didn’t do it before (I will update my thread of n8n :smiley: ) : we can validate a step with the variable « satusSelect ».
I did it on accounts entry (com.axelor.apps.account.db.Move).
GET http ://localhost/ws/rest/com.axelor.apps.account.db.Move/1000 //Delete the space after http
it was a draft Move (accounts entry I create manualy)
POST http ://localhost/ws/rest/com.axelor.apps.account.db.Move/1000 //Delete the space after http
Body Parameters : { « data »: { « version »: 1, « statusSelect »:2 }}

And now the state of this document is not a draft anymore, « Count status » (or something like that)
StatusSelect: 3 will be « validate status » (or something like that)

→ So if axelor had already the production send and you want confirm it, juste update the satusSelect

I don’t know what the difference between :
ManufOrder/ProdProduct/ProdProcess/OperationOrder

I don’t use production module
So I will say « manufacturing » and manufacturingOrder


you have to decide who manages what, define every step. Everything should be possible, but you have to define your way to do it. My vision :

Axelor is you principal app for all logistic, manage manufacturing. information product, resupplying,…
your PLC don’t handle stock or information product, but for product a car, you have to make a manufacturingOrder, clearly the list of your pieces to product the car.
how handle this list ? for my point of view (not an expert),
If it’s standard so Axelor with template production
If depend and change few time in a day, it’s your PLC.

In case it’s your PLC, you will have to do a spreasheet, and try to send this data to your Axelor.
Axelor will inform you if there are no stock for some piece.
When the production are done, update the statusSelect of manufacturingOrder, or just valid it manualy (human confirmation).

1 « J'aime »