Hi to all community members
Im find my sefl generating ideas about to design a traceability system, but issue is to exists different approaches and ways to perform it. The interesting for me is design and develop trought plant simulation a traceability system to identiy, register and analyze the generated data along supply and process chain of a product.
So I would like to know your suggestions of how to model this kind of behaviour in a manufacturing system.
1. Does anyone has modeled a similar system?
2. what kind of strategy did you use to model it? And finally...
3.what it would be the basic operational performance indicators to take into account before to start modelling?
I'm not an expert usin Plant Simulation, but constantly I'm learning so much about this tool. If someone has an example model to understand better this, I will be greatful.
Solved! Go to Solution.
I am no expert in Traceability or Plant simulation, but here are some ideas.
1. I haven't modelled a traceability system yet, but I have encountered some aspects relating to it.
2. In my opinion, the important part here is to identify the 'key'. A traceability system is more or less like a dictionary where it should be easy to just search for or refer to a word, number, or code to get production information. You will surely be using some tables.
We need to decide how we want to store this information as a part travels through the value chain.
User-defined Attributes may help you carry this information through the process chain. You can assign values to these User-defined attributes with Entrance/Exit controls(for example: when a part exits the Paint area, the attribute 'colour' is created and assigned a value).As long as Plant Simulation is concerned, each MU instance has a number (Entity:1, Entity:2... and so on) which can be used.
At the end of the process, all the values of the attributes may be used to generate a serial number for the part based on a formula. For doing this, certain tools are available at our disposal.
Looking up 'switch/inspect', 'Functions for Manipulating Strings' and 'regex_search' in the Help Topics might help you if you consider this method.
3. Deciding performance indicators can be tricky and will depend on what you expect from the simulation as Traceability is just the transfer and storage of information. Judging how easy or fast it is to derive the required information(by creating a User interface) can be one. When it is difficult to quantify information, a possible way may be to list the capabilities/considerations of the model and rate them as 'true' or 'false'( like comparing cars - ABS: Yes, Airbags: Yes, Sunroof: No )
you should try to use the attribute set of the original system (it is important for performance keys).
If you have a basic understanding for data bases, you can try to use the SQLite interface of Plant Simulation. You can define each MU as a data set and change the attributes along the supply chain (e.g. dispached, packed, handled to the carrier, arrived at warehouse...,connected with timestamps). Than you can use SQL to make your statistics.
I'm using SQLite since many years for this purposes.
freelance simulation specialist
Hi Mrs. Steffen
Thanks for your suggestions and share some tips based on your experience. However, I don't have experience using SQLite, but it sounds very interesting create a link between them. It could be a great moment to learn something new.