Continued from page 1

Defining Schema

It is critical to fully define the Pro/INTRALINK schema prior to implementation. Changing all or part of the schema after implementation is difficult, if not impossible. The following example of schema settings and their use in maintaining family tables are intended for reference only.

Release levels could be named “WIP” (pre-released or work in process), “active” (released), “change in process” (objects being changed or released by an ECN), and “inactive” (obsolete or no longer in the business system) to match the release levels used in an enterprise data management system. Using the same terminology allows everyone to have a common language. For example, generics are WIP unless they are a released or “active” object (in which case they would be set to Release Level “active”). Instances have whatever release level is indicated by the business system.

Admin support is required for check in of objects “not authorized to change or check in,” such as a family table containing an instance with the release level of inactive. The user gets temporarily assigned to a role that has “force check-in to same branch” marked as an option, allowing the user to override conflicts and check the files in.

Check out configuration preferences affect the list of objects being checked out and can be set by default for global use (Fig. 1). Each user can change or modify these options on the fly during the check out process.

• Include Drawings checks out the associated drawing for each of the objects being checked out. Note that the drawing formats for each drawing added to the check out list will not be included in the check out.
• Include Instances adds all instances and the generic to the check out list.
• Include Generics adds only the generic file for any instances being checked out to the check out list

Figure 1.

Pro/INTRALINK has two options for checking out family table objects:

1. Include Generics is required if you do not use Include Instances so that the generic file(s) for any instances being checked out are included in the list of files checking out to the workspace. Include Generics is not required if you use Include Instances.

2. Include Instances is required if you do not use Include Generics so that the generic file(s) for any instances being checked out are included in the list of files checking out to the workspace. All instances from the same family table are also included in the check out when you use the Include Instance option.

When should you use Include Instances? Anytime you need all of the instances in the workspace, e.g., when making a change to the entire family table or when family tables and models are small. This is the easiest, least complicated method of check out, although it can be time- and space-consuming if the models and tables are large. In that case, Include Generics may be used. Doing process and timing tests is recommended so that you arrive at the best possible configuration for your business.

When opening the generic or any instances in a Pro/ENGINEER session or when attempting to modify the table or generic model, if all of the instances are not checked out a storage conflicts message will appear (Fig. 2) with a warning that the family table is read only. This is because not all of the instances are checked out to the workspace. Selecting the OK button allows the retrieve to continue. Cancel ends the retrieval process.

Figure 2.

Opening an assembly that contains a generic or instance whose entire family table was not checked out results in the same storage conflicts dialog.

When attempting to modify a generic model whose instances are not checked out to a workspace, a warning dialog appears and the model stays read only until all of the instances are checked out to the workspace (Fig. 3).

Figure 3.

There are other drawbacks to not checking out all of the instances for a family table. For example, say a user has checked out an assembly file and its related components and used either the Include Generic or neither option. The user attempts to replace a component in the assembly that is a member of the same table as the component being removed. When selecting Component, Replace and then picking the component to be replaced, pick the option Family Table and a list of instances in the same family table appears. When selecting an instance that is not checked out, you will get an error message (Fig. 4).

Figure 4.

Select Cancel in the dialog to end the replace. At this point, it is not necessary to exit Pro/ENGINEER while getting the instances needed.