In last week’s post I walked through a manufacturing use case without Product Lifecycle Management (PLM). I hope you noticed the possible issues and costs related to restricting Manufacturing direct access to PLM and engineering data.
If you missed last weeks post, you can read it here:
Product Lifecycle Management in Manufacturing: Part 1
This week I will use the same use case story. The only difference will be manufacturing has access to PLM. I have also included manufacturing specific modules, which are run through PLM as well. Manufacturing has access to these modules and uses them for all Manufacturing planning.
As before, Engineering completes a new product design and starts a release process of the product in PLM. One major difference now, is Manufacturing personnel are included at appropriate points in the new release process. There is a full integration between PLM and Enterprise Resource Planning (ERP) systems as well. This integration allows for automatic transfer of the Manufacturing Bill of Materials (BoM) to Enterprise Resource Planning (ERP) when appropriate based on processes managed in PLM.
One thing to note on the outline below; each system task, since it is in PLM, has links to all the required information engineering released as well as any supporting information. This is including manufacturing information, customer specification, and supplier specifications on purchased parts.
Part 1: Release Process
The lead Manufacturing Engineer receives a PLM task asking him to begin manufacturing planning for this associated new products design.
Part 2: Manufacturing Planning
The manufacturing engineer begins the layout of manufacturing processes in the PLM Manufacturing Planning System. This includes planning at each work cell. Each cell is linked to required resources, parts, CAD data, and manufacturing documents required to complete that cell action. With the correct system, this will have included all metrics required to properly and completely plan a manufacturing process.
If required, a Manufacturing BoM is based off of, and linked to, the Design BoM. This allows the Manufacturing Engineer to restructure the BoM as needed to allow for the most efficient manufacturing processes without losing ties to the design BoM and parts the manufacturing BoM was created from.
Once complete, work instructions can be created in web form or be printed to paper from this plan. The work instructions would include links to the correct Engineering data and required manufacturing documentation.
Part 3: Release Process Continues
Once the Manufacturing Engineer completes their planning tasks, all required parts and Manufacturing BoMs, are automatically added and/or updated into the ERP system via an integration to PLM.
During this same process, PLM system tasks are sent to purchasing to start the procurement process.
Tasks are also sent to the tooling designers to start tooling generation.
As mentioned, these tasks are automatically linked to all the required engineering and manufacturing information to appropriately complete each task.
Part 4: Tooling and Controls Tasks
Tooling designers access PLM to generate their tooling data and controlling programs directly from engineering 3D data.
The resulting CAD and other tooling data are also saved to the PLM system. This data is linked to Engineering data, Manufacturing data, and the Manufacturing process plan.
Machining paths and other controlling programs generated are also created and saved to PLM with the same functionality mentioned above.
Having these links from manufacturing to engineering data allows for full impact analyses of any potential changes being planned for the product by the company. As well as insures all downstream data is updated appropriately when an engineering change does occur.
Part 5: In-Process Change by Engineering
While ramp up is happening, Engineering makes a last-minute change. Once the change is complete in Engineering, they start a change process that includes all downstream departments. Each department receives a PLM system task with the all required information related to the change linked to the task. This includes purchasing, manufacturing, tooling, etc. Each department acts upon the change, completing all internal department actions required.
Once all of the departments have completed their tasks in PLM, the change has been completed. Manufacturing ramp up continues leading into the initial manufacturing process.
Part 6: Issue Tracking and Correction During Manufacturing
During the initial manufacturing process, a manufacturing team member notices there is a clearance issue with the design. The team member verbally notifies their cell leader of this issue. The cell leader creates a change request in the PLM System. During that process, he creates a digital markup that is saved with the change request. The change request is created referencing the engineering data the issue is related to.
The engineer responsible receives a PLM system task notifying of this problem. The engineer takes the needed corrective actions and updates the CAD data. This CAD data is then revised released and included in the problem report.
The cell leader receives the notification the problem report was approved and corrected. The updated CAD data is included, the cell leader and the manufacturing floor team member can now reference the new data directly from PLM and make the needed correction.
This happens many times during the initial manufacturing process. The necessary PLM processes are initiated based on the issues found during the initial manufacturing run.
Manufacturing uses PLM to gain access to engineering data because it always references the latest released information. This insures nothing is made from outdated information.
Part 7: Final Product Release
The final product is released to the customer.
All as-built information has been saved in PLM, meaning most of the related engineering data has been changed via the PLM process capturing changes. Anything that hasn’t been corrected yet is also saved via electronic markups to be processed later.
Part 8: Another Manufacturing Run
One year later, the company needs to do a manufacturing run on this same product. However, they have a large turnover with their manufacturing employees. Only a few people are there that worked on the first production run of this product. Without the use of PLM, this could be a disaster. However, all as-built changes where captured in PLM for the first production run of this product and manufacturing is still using PLM to access all build information. This allows manufacturing the ability to properly prepare for the next run. This resulted in very few, if any, issues during the next production run.
Hopefully it is easy to see the benefits of giving manufacturing direct access to PLM, even based on this limited use case example.
There are many benefits to utilizing PLM in manufacturing. Much more than is appropriate to list in a blog. If you’d like to take a deeper dive, please contact one of our experts here at EAC. We would love to talk you through all the benefits PLM utilized in manufacturing could offer you.
In the meantime, reading our eBook, “Designing an Effective Change Control Process” may be helpful. We walk you through how to design a change control process to improve productivity and reduce quality issues.
While I’d like to think I’m a good storyteller and an artist, I’m pretty sure I’m not ‘awesome’ at either. That’s one more reason to pay attention to Augmented Reality (AR) these days.
As an engineer and a designer, I frequently find myself trying to explain a widget, a feature, or a design to someone. Often this takes lots of hand-waving, white-board markers, and innumerable sketches. This got better over time with improved drawing skills and communication techniques. It was even better still when I could put a physical model in someone’s hands by using a 3D printer for rapid prototyping. Well, things just got a lot more interesting when we started using AR through ThingWorx Studio to do virtual prototyping.
While I spend most of my time designing business strategies for the IoT and connecting products using ThingWorx as an IoT platform, the AR portion of ThingWorx is simply fun to use. One great way to employ the tool is to super-impose streaming data and information directly onto the product while looking through a mobile device. AR Prototyping, on the other hand, is the ability to superimpose alternate designs into the real world through a mobile device such that you can experience a design as it was intended. The kicker is that you can whip together a couple dozen designs, review them virtually — in person or remotely — and have a fabulous understanding of the design in less time than it takes to print even one prototype.
In the video below we’re playing with the app ThingWorx View by PTC. Watch this model of a motorcycle come to life with Augmented Reality (AR). We’ve used this technology for virtual prototyping. For some of our customers we are able to swap in and out CAD models to virtually prototype new designs and configurations.
So, if you’re like me and you want to convey a design idea in a hurry — even faster than a rapid prototype — you should really look into AR Prototyping. This has sliced-bread beat no problem.
If you want to start virtual prototyping, ask us how here! We’d love to help you transform the way you design and connect to your products.
In the last few weeks I’ve discussed the benefits and costs of customization. This week I will review deciding whether to customize or not. If you missed these posts, you can read them here:
So how can you weigh the benefits against the costs of customizing? If we examine the criteria outlined above, a general pattern emerges, which provides the key insight in making this decision:
Benefits mainly go to end users, and costs mainly go to developers and administrators.
Installations with large user bases, where the value of customizations can be maximized, are good candidates for customization. Also, organizations that have dedicated staff for maintaining the Arbortext system will have an easier time managing customized installations than organizations where maintenance and development is a part-time task for staff with other responsibilities.
In organizations that have a small number of users, it will be difficult to realize enough value in customizations to make it worth the expense of implementing them. In these instances, it makes sense to stick with a mostly out-of-the-box installation using a standard doctype like DITA or DocBook, possibly with some stylesheet adjustments to get the desired output appearance.
Consider standard features first.
With all software, you can get the most value from your investment if you maximize the use of its standard features. If you are new to the software or perhaps not leveraging everything the software offers, you should explore the best practices and benefits first to determine if customization is truly needed. With Arbortext, PTC recommends an implementation approach called “Value-ready Deployment” which leverages the value of Arbortext using standard features and recommended best practices to maximize the value to each customer before any customizations are made.
Also consider prepackaged add-ons.
EAC offers several prepackaged add-ons which add capabilities to the Arbortext platform at a lower cost than a customization. One of our add-ons is EAC QuickPubs.
QuickPubs allows users to create aesthetically pleasing Operator Guides, Service Manuals, and Parts Catalogs quickly while providing an easy way to style documents that fit your brand. If you decide to investigate customizing Arbortext for your environment, EAC can help you explore your options with a variety of prepackaged add-ons, training, and implementation services.
Transform the way you design and publish product information through QuickPubs, an EAC product for PTC Arbortext. For more information about QuickPubs, you can download the brochure here. Publish faster, cheaper, and better today!
In my last post, ‘The Benefits of Customization,’ I told you I would review the cost of customization in my next post. If you missed it, you can find it here:
Of course, the benefits of customization don’t come without some associated costs. Here are some examples of the cost of customizing PTC Arbortext:
Development Costs
The most obvious cost is the cost of initially developing and testing the customization code. This will vary based on how extensive the customizations are. Also, don’t forget to keep maintenance costs in mind. Bug fixing, adding new features, and adapting customizations to changing requirements all require additional investment.
Version Lock-In
When you develop customizations, you generally work with a specific version of Arbortext. Depending on how extensive the customizations are, there is a chance that some part of the customization will break when you upgrade your Arbortext software to a new release version. In that case, you have two choices: either spend the resources to update the customization for the new Arbortext version, or commit to remaining with an out-of-date version of Arbortext to keep your customizations running.
Proprietary User Skills
With customization, you will need to take user training into account. For new features that don’t come out-of-the-box, you will have to develop your own training and support materials, and make sure your end users are up to speed on how to use the new features. In addition to the direct costs, this can also make recruiting new staff more challenging. There is a lot of DITA expertise in the marketplace, which you can leverage if you are using standard DITA. But if you are using a custom doctype and customized Arbortext Editor interface, you may not be able to get the same advantage from potential employees’ previous experience with XML editing or with Arbortext.
Technical Support Complications
PTC’s tech support staff know the base products quite well, and can help troubleshoot problems with out-of-the-box installations pretty quickly. However, with a heavily customized environment, troubleshooting can be more challenging, for PTC tech support as well as for yourself. In some cases, it may take extra time to determine whether a problem is due to a bug in the base Arbortext software, or something wrong with your customization code, or some kind of interaction between the two. In some cases, PTC’s advice for resolving the problem may boil down to “remove the customization.”
EAC has created a tool to help eliminate some of these costs allowing you to publish faster, cheaper, and better. QuickPubs is an EAC product for PTC Arbortext that removes the cost of development and provides a user-friendly interface.
While Arbortext comes with some publishing capabilities right out of the box, most users will acknowledge that they often need to customize the document stylesheets to meet their publishing standards. Customizing the stylesheets isn’t difficult, but it often requires prior training or hiring someone with the appropriate skilled and experience, both of which have an impact to turnaround time and cost. EAC has packaged attractive stylesheets for Operator Guides, Service Manuals, and Part Catalogs into QuickPubs so you can publish manuals that look as good as your products from day one. Should you need to modify the document stylesheet, QuickPubs also offers an easy interface to customize the style layout and formatting with a few clicks.
Stay tuned for the next post where I will discuss things to consider when deciding to customize or not.
If you would like to learn more about EAC QuickPubs and how you can publish faster, cheaper, and better, download the brochure here!
This is part one of a three part series regarding PTC Arbortext, deciding whether to customize or not. In this series, we will discuss the benefits of customization, the costs of customization, and deciding whether to customize or not.
You’ll often hear of DITA in the technical documentation world. DITA stands for ‘Darwin Information Typing Architecture’ -it’s an XML-based open standard for structuring, developing, managing, and publishing content. Quite the mouthful huh? What you need to know about DITA is that it leverages XML to be used as a way of writing and storing your data so you can manage it like an asset. What does it have to do with PTC’s Arbortext? PTC was the first company to ever deliver a complete DITA solution – one where organizations can finally start to maximize their investment in service lifecycle management.
One of the most fundamental questions you have to face when considering an Arbortext implementation is whether to use the technical documentation software out of the box or develop customizations to adapt the software to your specific use cases and work processes.
In practice, this is not so much of an either/or decision, as a how-much decision. In other words, nearly every implementation has some amount of customization, even if it’s just tweaking a composition stylesheet to add your own appearance specifications to the composed output. For some applications, where one of the standard doctypes such as DITA or DocBook is adequate, that’s all you need. For other applications, you may want to add custom features, user interface elements such as toolbars and custom dialogs, a tailored doctype or schema to support specific data requirements, connections to other enterprise systems such as ERP systems, and so on.
Adapting Arbortext software to your specific business environment can provide a number of advantages. Here are some examples where customization can add value to your implementation:
Author Efficiency
Custom features and user interface controls allow the author to work more efficiently.
Example: if authors frequently need to change one type of element into another similar element, then adding a toolbar button and/or keyboard shortcut to trigger the operation can let authors do it with a single click or key press, as opposed to using the Change Markup dialog.
Workflow Integration
Custom integration with software can streamline processes in the workflow.
Example: Suppose you have part data stored in an ERP system, and you are writing support documents associated with the part data. In a stock Arbortext installation, you might need to export the part data as an Excel spreadsheet, and then copy portions of the exported data in Excel to paste into the XML document in Arbortext. In contrast, a customization could allow authors to click a toolbar button, make a few quick selections in a dialog box, and automatically extract, format, and insert the part data in the correct location in the document.
New Capabilities
Customizations allow you to add new features to Arbortext Editor.
Example: Suppose you have a metric that you want to track on your documents that depends on the number of specific elements in each document, such as graphic elements. You can easily add a feature that would count instances of a specific element and report that for a document. You could also generate a report for a set of documents found in a directory tree or a folder in a content management system (CMS). This would let authors get this information directly within Arbortext Editor, without having to switch to an external tool to do the analysis/reporting.
This publishing engine software can be customized in a number of ways, and frequently we see users customizing their stylesheets to make them look better or compliant with their publishing standards. Arbortext stylesheets are used to publish documents that have consistent styling and formatting, no matter who authored the document. Sometimes these stylesheet customizations can be significant and complex, but often we see a need to make simple modifications to the fonts, logos, and page margins. EAC QuickPubs provides users an easy way to make those simple style modifications and create great looking documents.
Stay tuned for the next post where we discuss the cost of customization.
If you’re looking for ways to adapt your environment to fit your organizations needs, EAC QuickPubs may be for you. It’s an add-on designed to style documents that fit your organizations brand at a lower cost than a customization to PTC Arbortext. You can create aesthetically pleasing part manuals, owner’s guides, service manuals and more with ease. Publish fast, cheaper, and better today!
Transform the way you design and publish product information through QuickPubs, an EAC product for PTC Arbortext. For more information about QuickPubs contact us. Publish faster, cheaper, and better today!
I applaud anyone currently considering how the Internet of Things (IoT) can transform their company and their approach to competition. This is what every industrial and consumer product company should be doing right now. While helping companies through the early stages of developing IoT strategies we’ve recognized a common challenge. Teams can get lost in the excitement of enabling their first “thing” and lose focus on their long-term vision and the value they can extract from streaming data. We get it! The IoT is exciting. That is why we always coach our clients to select an IoT platform (software) that allows them to quickly and easily develop applications that present valuable, digestible information to employees and customers – whether or not a role or data stream was part of the initial strategy.
This week provided me with a front row seat to unexpected value from streaming data. While working on an IoT proof of concept for a client, my team was able to refine a data stream and deliver a new application to an audience that was not part of the initial scope of the project. The only reason we were able to create this new application without charging an additional fee is because we selected ThingWorx, a solution by PTC as the application/mashup development tool. Thingworx helps teams create new applications in minutes.
I try to spend the majority of my time working on IoT strategies and how they can transform companies and competition. My background in engineering and software development provides me with a unique view into the time spent making things smart — providing sensor networks, communication layers, and ultimately enabling heretofore unseen analytics in real-time on remote products. The project the Connect Services team and I were working on this week involved developing mashups, which stemmed from earlier strategy work and team alignment. Mashups are the collection and presentation of data from smart things and systems enabling real-time business awareness and decision-making. For this project, we had already developed storyboards for the apps that would enable core product and service differentiation. Everyone was on board and excited.
Once the proof of concept device was wired and streaming data, we saw a whole new role that would benefit from the data that was streaming. Previously, the engineers would have been left hanging and the data would have been left alone and isolated. This is because developing an extra application for ancillary roles would have taken the project well off track. Leveraging ThingWorx as our application development environment, we were able to build a concept from scratch in literally seconds. What’s really cool is that it didn’t take any code at all either, just drag, drop, save, and we were in business. The concept made sense and in literally a couple of hours (not days or weeks) we had created an entirely new app and use case for the data. We were able to refine the data in real-time and create a whole new monitoring experience. Again, this was done without coding, just simply drag and drop.
So, here’s my recommendation — make sure your IoT platform supports your IoT strategy. And what’s more, be sure the platform you select is a tool that is flexible, fast, and fun — like ThingWorx. You will likely find more and more ways to consume, refine, and benefit from the data your connected products and enterprise produce just because it’s easy to do. And this, after all, is what your IoT platform should do — it should enable your existing business initiatives and accelerate your business initiatives.
EAC Connect Services is here to help you develop your IoT strategy, build and connect your proof of concept, and select the appropriate platform. Let us be your partner in the ever-changing world of the IoT. Please let us know if we can help you transform your business and help you beat your competition.
