Collaboratively Implementing Product Lifecycle Engineering Changes Using the Microsoft Office System

Often, there is a product life cycle management (PLM) system in place that makes it difficult to integrate and share data across the change management process. Many of these PLM systems are legacy systems with no easy access to the system data.

There is often an inconsistent technology approach inside manufacturing companies, requiring that many PLM systems and applications be integrated together. Key data such as engineering specifications, roles and assignments, and engineering costs are locked in other systems.

There is no easy way to track the status of the engineering changes. Often this requires that IT staff build a custom solution to address this isolated issue, which creates more in-house applications and maintenance needs.

Engineering change status reports are difficult to build and often require custom application development. Additionally, many reports are in static formats that require custom data extraction for business users who want new views or reports.

Interoperates with other systems using XML and Web services. This ensures that the existing PLM systems can integrate with the engineering change process.

Uses existing software applications that are in place and are well understood by end users. Most end users are familiar with Microsoft Office and other Microsoft Office System products and technologies such as Microsoft SharePoint Products and Technologies. This existing familiarity will help keep training costs low.

Deploys quickly with minimal IT impact. Deploying SharePoint Products and Technologies Web Parts is simple, straightforward, and can be done quickly.

Lowers total cost of ownership by using existing investments in Microsoft software products.

Offers a rich network of partners well versed with Microsoft Office technologies.