DriveWorks Pro 15: How To: Implementation Guide (KB12121022) [send feedback...]

Introduction

DriveWorks has been developed with Ease of Use in mind. The intention and practise at most companies is that Engineers can implement DriveWorks for themselves.

DriveWorks Administrator is the module of DriveWorks Pro that is used to implement your products.

All other modules of DriveWorks Pro assist in the running of a DriveWorks implementation.

This document provides guidance on getting started with DriveWorks Pro Administrator and provides guidance on maintaining an implementation going forward.

Using DriveWorks

There are three elements to every DriveWorks Implementation:

Setting upRunningGenerating the Outputs

Who Implements DriveWorks?

The most successful DriveWorks cases are those where a DriveWorks Champion is appointed from within the company.

This should be someone with good product knowledge as they will be documenting the product and company rules that will be brought into DriveWorks and which will be used for automating the design process.

Click here to see who the Project Team should involve

Training

DriveWorks training is essential to establish a good understanding of DriveWorks Pro Administrator. Only the personnel responsible for implementing your products in DriveWorks Administrator need trainng.

Click here to see the topics covered in DriveWorks Pro Administrator training

Once your products are implemented only an understanding of how to use the User Forms and maybe an understanding of how a specification is processed is required. This can be conducted internally by the team who have implemented DriveWorks.

Implementation Methods

Products, designs and data constantly evolve. So unlike a custom written solution DriveWorks needs to (and does!) allow for change.

When implementing DriveWorks it is important to remember that nothing has to be set in stone on the first day. The use of DriveWorks and scope of work will change as the users become more familiar with the features of DriveWorks.  This is normal, and should be factored in.

Click here to see the methods of implementing DriveWorks

Implementation Plan

Regardless of the Implementation Method selected the steps involved in setting up a DriveWorks implementation generally follow:

1. Decide on the product to be automated.2. Decide what information and input fields are required on the user forms.3. Decide what outputs are required4. Decide what data is required or can be re-used.5. Determine the rules required to automate the product.6. Test.7. Add the detail to the project8. Deployment


Knowledge Base Article Ref:KB12121022

The forms used to enter or select data for the specification.

A text box, check box, or some other control added to the form designer.

The forms used to enter or select data for the specification.

The forms used to enter or select data for the specification.

Each time you run your project to automate a new set of models, you are creating a specification. The specification keeps a history of the outputs that are created throughout the lifetime of the specification.

Capturing is the process of telling DriveWorks what documents, models and drawings you want to automate, and what features in those models and drawings are going to change.

Value can be controlled by a rule.

Table of Contents