Here’s why engineering processes affect services and why streamlining information could solve the whole problem. 

The Problem: Lack of Communication

Let’s be honest, engineering and manufacturing departments do not always communicate product changes to service. This is just the start of how your engineering processes affect services. 

The Result: High Costs

When technicians reference outdated product information and arrive with incorrect parts, this leads to longer service visits, extraneous costs, longer downtime, and lowered customer satisfaction.

The Solution: Streamlining Information

Streamline the way you service teams access and use product information. The best way to accomplish this involves accurately transforming eBOMs (engineering bill of materials) to sBOMs (service bill of materials) and maintaining the fidelity of that information after engineering changes.

It’s time to stop letting your engineering processes affect services.

Take full advantage of the product data your organization has already created.

Structure service manuals and part information based on how a specific product is configured and serviced. Reuse engineering and manufacturing data in the service environment. Provide configuration-specific information to service technicians. Create a single point of access for your service content. Avoid text – use and repurpose graphics, animations, and CAD information when possible. And link service information to engineering information so changes propagate.

Next: Identify Your Service Needs 

Identify what should go in your sBOM to ensure your sBOMs meet the needs of the service department. Examples might include what is serviceable versus what is replaceable, the status of a part, the components, models, grouped items, and more.

The Goal: Transforming Your Services

Remember: the ultimate goal is to make your customers happy. As a result of combining best practices with the right technology to support service and parts information management and publication you will see a higher customer satisfaction, improved technician effectiveness, improved brand reputation, higher profitability (due to lower revenue and service cost), time savings, and higher revenue (from repeat business and customer loyalty).

We have a team of technical communications specialists that would love to talk with you about your current state and current initiatives.

One challenge when working with technical information is that publications can be very large. Several hundred pages is not unusual and in some cases over a thousand pages are necessary to describe complex service procedures and part catalogs.
Authoring and assembling large books can be a painful process as the sheer size can be taxing to software. XML, DITA, and managing content objects do ease the pain, it is what industrial strength publishing software is designed to do. However, there is only so much information the average workstation can process.

Many creative solutions have been implemented to meet unique business requirements for book assembly. The business requirements and data sources vary from company to company, such as selecting lessons individually to create a complete custom course; or selecting individual part list and image pairs to create a complete part catalog. As an application expert, I have personally coded many custom solutions to support cobbling books together over the years and I know that many other equally creative solutions exist.

PTC’s Service Information Manager adds three advanced capabilities to the XML authoring and content management system:

Publication Structures are the least sexy of the three and the one that truly revolutionizes the book assembly process. Publication Structures are used to assemble information objects that are to be published. Essentially each Publication Structure represents a book. You can add a table of contents, a parts list, or any other XML content object or images to the book right in the Windchill SIM web browser user interface.

Without Publication Structures, books are typically assembled manually in Arbortext Editor. Someone would still have to assemble the book manually in a Publication Structure, but the user experience is very different. To get a sense of this, in Arbortext Editor, if a writer wants to move a chapter to a different location, they would edit the document, select content, cut it, move to the new location, and then paste. In a Publication Structure, the user can drag and drop chapter or section objects in the structure without ever opening the book to edit it.

Publication Structures provide an out-of-the-box method of assembling publications for the technical documentation community without customizing. As a result, organizations are able to greatly improve the process of information delivery and are able to leverage dynamic publishing capabilities to bring products to market faster, and keep customers better informed.

Learn More

EAC information solution experts have decades of reliable XML solution experience. Explore the EAC website to learn more about our products and services or review the Product Development Information Services Brochure.