Autodesk PLM 360 is the next generation of PLM solution which extends the benefit of PLM throughout an organization, connecting everyone involved in the product development process. For engineering, PLM 360 helps break down silos of information which traditionally cause wasted time and potentially costly errors. It also makes product information understandable to those outside of product development. Using the engineering applications, organizations can manage product items and bills of materials, change requests and change orders and other related information, such as material specifications, as well as facilitating effective design reviews and analytical reporting.
In this tutorial, you will learn how to:
| PLM 360 provides contextual access to users from any department. Users are presented all the information they need to perform their job without the data that is irrelevant to them, giving a high level of clarity and understanding. |
| PLM 360 gives fast access to real-time graphical reports which outline the status of any aspect of product development, giving everyone involved a clear view of the current situation. |
| The dashboard contains a report that depicts items by category in a pie chart. The pie chart shows a real-time view of all component parts within the organisation by their category. | |
| Any of the charts on a user’s dashboard can be viewed in more detail in a separate window, giving greater clarity. |
| The format in which charts are viewed in PLM 360 can be easily manipulated to give a different view. This is useful to gain a better insight into the statistics within the charts. |
| |
| |
| |
| Now let’s look in more detail at the bill of materials for a product, a flashlight assembly. | |
| This area is unique to each individual and contains links to items commonly referenced or used by that person, such as an assembly presently being worked on, or a supplier they often liaise with. This provides convenient access to the data accessed most frequently by that individual. |
| The information for the flashlight assembly is summarized across the various tabs in this workspace. | |
| The bill of materials for an assembly or subassembly can easily be accessed and interrogated in PLM 360. The BOM can be viewed as either a nested structure or a flat list. In the nested view, you can expand each subassembly to view the parts that make up that subassembly. This gives the product stakeholders a clear understanding of its constituent parts and the current revisions, reducing time wasted looking for that information and decreasing the risk of error due to referencing incorrect design revisions. |
| |
| The flat BOM list provides a line-item view of the entire flashlight assembly, along with a roll-up of total costs, ensuring the product team is aware of the current overall cost of the project at any time. |
| A preview of any item in PLM 360 can be viewed at any time by using this function. This gives users the ability to understand more about that item without having to navigate elsewhere, saving time and effort. |
| |
| There is a problem with our flashlight product, and an engineering change needs to be made. To do this, we will submit a change request to ask for a modification to be made. A change request has already been started, so we will pick it up from here. | |
| This workspace contains details of all current and previous change requests. In this case, there is only the one we need to work with, but, in reality, there will be details of all previous ones. By selecting a previous change request, anyone can see details of it, whether it was accepted or rejected, and why, and when this happened, as well as details of any change orders spawned as a result. This is an example of the comprehensive level of traceability offered by PLM 360 to assist with meeting compliance requirements. |
| Details of the change and the impact assessment have already been added, but we still need to identify the members of the approval board, or those who need to approve the change request. | |
| Any task in a process workflow in PLM 360 can be assigned a list of approvers, and only they have authority to progress that step. Approval can require all of these to sign off, or just one or another specific number of them. This helps to ensure processes are compliant and correct. |
| Processes in PLM 360 can automatically start, or ‘spawn’, other related processes, depending upon certain outcomes. For example, a failed inspection can automatically spawn a non-conformance process. In this case, the Change Request process will automatically create a Change Order if the request is approved by the approval board. This automation and linking of processes improves efficiency and ultimately reduces lead times. |
| |
| This is an example of a process workflow in PLM 360. Using workflow capabilities such as this, processes can be fully managed in PLM 360. All processes, from the overriding new product introduction (NPI) process to individual activities, such as inspections or quality documentation creation, can be addressed in this way. This leads to improved process efficiency, better understanding of what those processes look like, and who is responsible for each task, and improved visibility of the status of any process, helping to identify any delays or bottlenecks. |
| By progressing this step of the workflow, the approvals board will be immediately informed that the next stage has been reached, and they need to approve it. This task will be added to their home page in the ‘My Outstanding Work’ section of PLM 360, and they can even be informed by email if required. This means that this next step of the process will not fall through the net, and can be actioned in a timely manner, ensuring the process runs as efficiently as possible. |
| Selecting any current in-progress task box in a workflow map will allow anyone in the organisation to understand who needs to sign that stage off. This is a useful tool in understanding process bottlenecks, and who to liaise with to move the process forward. |
| Signing off a step in the workflow is an easy task using the graphical display of the workflow map, but only for those who have the authority. Then ability to add a comment when this is carried out ensures all information about the reason for sign off, and any additional detail, is captured, and can be traced back at any point in the future. |
| The approval team also includes Ed Engineer and Paul Projectmanager. Both Ed and Paul need to approve the change request in order for it to be able to move to the next stage. | |
| Ed logs into the same single, common, PLM environment as before, but sees his view of the world, with access to only the tools and data he needs. |
| Each user in PLM 360 has a ‘My Outstanding Work’ section, unique to them, which is their ‘to-do’ list of tasks. Every time a task is assigned to them, such as a workflow sign-off, that task is added to this section, as well as being emailed to them if appropriate. |
| |
| Now both you and Ed have approved the change request. However, because this step has to be signed off by the whole approval team, the item is still under review by the team until Ed Engineer approves it as well. | |
| Paul logs into the same single, common, PLM environment as everyone else to get his view of the world. |
| As a member of the approval team, Paul also sees the sign off task in his ‘My Outstanding Work’ section. |
| You will see that, this time, the ‘Final Approval’ transition in the workflow is highlighted in green, and the ‘Approval’ transition is not. Because Paul is the last of the approval team to sign the approval task off, he can move the process on to the next stage. PLM 360 now knows that the whole team is happy, and we can move forward with the change request. | |
| The ‘Final Approval’ step is only available once all members of the approvals team have agreed to move the change request forward. The workflow capability in PLM 360 will strictly work to the rules applied to it – the rules which govern your business. However, whilst enforcing those rules, it makes progressing the processes it managed as painless and easy as possible. |
| From this change request record we can link straight to the change order which it has spawned. Conversely, from the change order itself, we could link back to the change request which drove its creation. This is typical of PLM 360, where data in one record is linked to corresponding information, making it easy to fully understand a particular situation and providing traceability, which helps to meet ISO and associated compliance requirements. |
| You may remember that, when we created the change request, we specified that a change order be automatically created, or ‘spawned’, upon the approval of that change request. This is the change order spawned as a result of the change request the approval team just signed off. It contains some information automatically brought through from the change request, such as the description and reason for the change. | |
| |
| A key element of any change order is to define the items affected by it, or what parts, assemblies or documents the change will be applied to. In this case our affected item is a specific subassembly which has been identified as requiring modification to fulfill the change requested. | |
| This is another good example of the ease of obtaining and linking related information in PLM 360. It is easy to find the item to be modified, either from the list of all items, or via a simple search mechanism. |
| Revision control is a key requirement when making any engineering changes, and PLM 360 manages this within the change process workflow, ensuring that any item which is changed is moved to the next revision. In addition to this, administrative settings can be applied so that certain people can only see certain revisions. For example, Quality Inspectors may only have access to the latest production revision, whilst Design Engineers will need to see all working revisions. This ensures everyone in the organisation is working with the correct, and not out-of-date, data, which could potentially lead to very costly errors downstream. |
| Using the graphical representation of the process workflow, and the colour-coded transition arrows, it is easy for an individual to understand their options in moving the workflow forward, and what they are authorised to sign off. |
| The Change Control Board (CCB) will now need to review the change, taking into account all of the information filtered down from the change request, and all the additional information, such as the sub-assembly added earlier, which has been input into the change order. The CCB panel is that defined in the ‘Approvals’ section of the change order. You will remember that, in this case, you defined only yourself as a one-person CCB panel, so you are able to sign the review step off yourself, as indicated by the green colour of the ‘Final Approval’ transition arrow. | |
| |
| |
| |
| This is another great example of the importance of traceability in PLM 360. Any part or assembly can be investigated for where it has been the subject of a change, and all of the background information on that change accessed, giving a full understanding of the history behind that item. |
From this short tutorial, you will have seen how PLM 360 can provide teams with up-to-date, real-time analytical information on what is important to them regarding the product development process. You will also have seen how a product’s bill of materials can be easily accessed and understood by all stakeholders in the development of that process, and how PLM 360 can manage the engineering change process from an initial change request through to approving and applying that change. You will now have an understanding of how a change order processes can be started automatically, or ‘spawned’, by a change request, if approved, and how, conversely, there is full traceability back up through those processes to the initial change request.
This tutorial has also highlighted the tight linking together of related information, giving stakeholders in a particular product the right information they need to make decisions, and how processes can be fully managed and made visible in PLM 360, helping to reduce bottlenecks within them.
Please feel free to further explore the Engineering-related workspaces and capabilities in PLM 360, and how your processes might look, and be further improved, with this product.