How Do I Export the Routing Tree View?
Assembly Planner users generally separate physical lines and sub lines within the routing section of the application. Smaller, more understandable physical lines being easier to comprehend and deal with as separate entities, rather than having them all within one routing.
However, multiple users have asked how they can see the full picture of what an End Item (orderable part) will go through en-route to completion.
It may go through multiple areas, even multiple buildings over the course of days or weeks. Using logic that is custom for a certain customer, a framework was created to export raw data into a specified tab, allowing excel lookups and macros to fill a report as needed.
All fields from related entities can be added to the report by adding the fieldname to the header of the Excel template in the template manager. This includes all fields in the Routing, operation, activity, and consumption tabs. Multiple excel templates for different functions and roles can be housed at the same time, selection of which to run happens at execution. Upon running the Routing Tree report from the ‘Deployment’ report option, users select the date filters, the excel template that they would like to use, and the End Item that is being made (in this case, the End Item is a model that is specified by country).
I choose my template and run the report for ITA models. The excel file is then created with the Inputs tab created showing my filter criteria and the Routing Tree tab bringing in all fields (standard and custom) that exist in the header of the excel.
The data is presented in a relatively bland way to encourage the use of macros and lookups to fill our other tabs within the excel that may be useful to other departments and roles. The idea here is to give users access to the FULL path a part might take and components it may require before being completed, rather than a single station or even routing. The logic in the report in this environment is set to jump from routing to routing as it finds matches between parent parts in use in one routing that are marked as the top level of another.
In the example, I asked what it takes to make an ITA model. The report grabs all activities and consumption from the routing (FinalAssembly), scanning all other routings for a match on ParentID and Model, when it finds it (127605440 parent exists in another routing), it pulls all the same information for the second routing and begins to scan for all parents in that routing, finding yet another match and bringing in another routing and all of its information. This process is iterative and can traverse routings until it finds no matches. This takes us, in practice but not in my simple example, from the final assembly of a model, through sub-assemblies, programming, and machining of piece parts. Each area and process is represented and the fields that might be relevant to the area can be shown.
Most of the reports in Assembly Planner focus on the details of Work Instruction, timing at the lowest level of detail, and part consumption within a station or operator. However, many users required a ‘higher view’ in order to gauge the impact against MRP or across areas of the plant that may not have the same level of detail. This routing tree creates a process diagram (including parts if needed) showing everything that must be done in the plant to complete a finished good. It pulls data from across all of these related routings in an easily manipulated format and variable format, essentially allowing the creation of user-controlled process/consumption reports.
If you have questions about our software solutions we'd be happy to help.
Join our mailing list to be informed of the newest blog posts.