Most of the steps described here will be performed by a system administrator or someone who is in a similar position. You may be able to change the order in which these steps are laid out, but it is recommended that you follow the order given below, at least in the beginning.
Every part you create will belong to a certain class and subclass, and will have certain attributes. For instance, if you want to create a part, say a threaded ball valve, it will be under the subclass "ball valve", which in turn will be under the class "valve". Some classes and subclasses are provided with the application, but most users will want to create others of their own. In addition, each part you create will have certain attributes, such as size. Attributes are also added in the feature dictionary.
(It is recommended that you do not keep your resources in the default installation. That is because when you install a service pack or new release your setup modifications may be overwritten. It is recommended that, after you install the application, you make a copy of the subdirectory ...intel_a\startup\EquipmentandSystems (maintaining the default directory structure) and store your resources at this location. The PRM file should point to resources at this location.)
The PRM file identifies resources to the application. Specifically, the PRM file identifies each resource and its location (directory path). The PRM file also organizes the resources by discipline and application, associating resources to specific applications. Therefore, you get the correct resource, equipment catalog for instance, for the resource you are working in.
The project administrator needs to define a PRM file for the project, identifying the location of all resources needed by the application. The file is in XML format and can be edited with any text or XML editor.
At this stage in the setup process you will not be able to enter the location and/or names of all resources, but you need to enter all that you can. You need to return to the project resource management file at the end of the process and enter names and locations of resources you will have created by then.
Every object that you create (except a run), or part that you place, in your design document can be given a unique identifier. This identifier usually consists of a prefix that identifies the type of object or part it is, followed by a unique number. When you create an object or place a part in your document the application will generate a name as defined by the naming rules that are associated with the object being created. A set of default rules is included with this application, but most users will want to modify these rules to suit their own requirements. You need to do it at this step.
This application incorporates intelligent design functions. This means that as you design, the application ensures your designing meets certain criteria. These criteria are established by the design rules. For instance, the compatibility design rules will match the threaded end of a pipe to the threaded end of a part.
There are different sets of design rules. Some are specific to a standard. Others are specific to a specifications catalog. And there are still others that apply every time you are placing a part. These last are known as "global" or "general" design rules. Although you cannot add a new design rule to the general design rules, you can modify existing ones; and, you can add attributes for informational purposes to the Design Rules Catalog.
Compartment and Access does not use general design rules.
The feature dictionary has both functional and physical classes. A functional class is a more abstract concept - it assigns a function to an object. Functional classes are used mostly in 2-D (schematic) designing, where designers only have to assign a function to objects they place in their designs, without having to specify exactly which physical part goes at that location.
In 3-D design you place physical objects, with unique part numbers. But you will use a schematic to assist in creation of 3-D design, which is why you need to link each physical class to a function. That is what is meant by mapping the functional physical classes. As an example, the physical subclasses butterfly valve and globe valve are mapped to the throttle valve function, whereas the subclass diaphragm actuator is mapped to the valve operator function.
You add these mappings in a mapping table. The application has one table that is global or general in nature. In addition, each specifications catalog has a separate mapping table. For this step you only need to map the general mapping table.
Raceway & Conduit Design, Hanger Design and Compartment and Access do not have functional physical mapping tables.
A sample standard is provided with this application but almost all users will be creating one or more standards. The simplest explanation of a standard is that it is a collection of specifications. You use a standard because it ensures that all the parts you place, and the manner in which you place them, will meet certain minimum requirements or their attributes will be within a certain range. The specifications themselves apply to many different properties, such as material or pressure ranges, maximum bend angles, maximum or minimum length, etc.
As an example, if you define your standard by material, then the list of allowable nominal sizes for stainless steel will be different than the sizes for carbon steel.
When you create a standard you should also create design rules specific to that standard. HVAC Design, Hanger Design and Compartment and Access do not have standard-related design rules.
You will need to build the parts you intend to use and place them in a master catalog. During actual use, the parts available to you will depend on the standard and specifications you are using.
When you modify the catalog (the most common occurrence is adding a new part) you must synchronize the specifications catalog. This is done by resolving the queries associated with the part type family.
You should synchronize the specification catalog whenever you modify the master catalog (the most common occurrence is adding a new part). This is done by resolving the queries associated with the part type family.
When you create a specifications catalog you should also create design rules for that specifications catalog, such as welding rules, turning rules, etc. You should also define the functional physical mapping table for the specifications catalog. Raceway & Conduit Design, Hanger Design and Compartment and Access do not have specifications-related design rules or functional physical mapping tables.
