- Quick start guide
- Selecting, clipping, colouring and highlighting
- Line tracking
- Custom attributes
- Colouring Options
- File management
- Linking and API
- Advanced options
- Configuration file
- 360° panorama
- IntelliPID Module
- 2D to 3D Projection
- Appendix - How to use 3D PDF files
- Appendix - Performance optimisation
- Command line parameters
- MDP-Manager Quickstart
- PDS AdminTool
- PDS AdminTool Erweiterung Modell kopieren
- PIDDM2URS Converter
Supported operating systems:
Microsoft Windows XP
Microsoft Windows Server 2003
Microsoft Windows Vista
Microsoft Windows 7 or later
Microsoft Office XP or Microsoft Office 2003
Administrator rights are required on each computer to install CAXperts SpecManager.
Prerequisites and recommendations:
Environment variables TEMP and TMP have to be set to c:\temp
Program acceleration with Intergraph Batch Manager\Queue PDmodel_builder -> Properties -> Scheduling Set Run Limit to 4
All Libraries in PDS should be compressed and approved (with pjstl and pcdims)
To uninstall the software, select Control panel from the start menu. Then on
Windows 7-10: in large or small icon view, click Programs and features. If you're using category view, under Programs, click Uninstall a program.
Windows Vista: in classic view, double-click Programs and features. In control panel home view, under Programs, click Uninstall a program.
Windows XP/2000: (Double) click the Add or remove programs icon.
Select the program you want to remove, and click Uninstall/Remove. Alternatively, right-click the program and select Uninstall.
Setup command line (for administrators)
The following command line options are supported by the installer:
/S:<<optional ini file>>
Allow an install to be run in silent mode. As a result, no screens or dialogs will be shown.
This command line option also has an optional INI file that can be passed containing session variable values. For example:
This will cause the session variables in the INI file to be used for the setup. The INI file should be in the format:
/U:<<XML config file>>
This command line option must be used when calling the uninstall program from the command line. This command also has an optional XML file that can be passed containing session variable values. For example:
"C:\Program Files\MyProduct\uninstall.exe" "/U:C:\Program Files\MyProduct\irunin.xml"
Working with the SpecManager
Before you begin
Unlocking SpecManager with a licence key:
To purchase a licence key please contact CAXperts GmbH (firstname.lastname@example.org).
The Licence Key can be manually typed into the SpecManager.ini configuration file. The correct entry looks as follows (where x represents a digit):
Licence=xxxxxx;xx xx xxxx;xx xx xxxx|xxxxx
The templates file (i.e. Template_ANSI.ini) has to be renamed in projectname.ini (it is recommended to replace projectname with the name of the PDS project)
Project customization can be done by editing the projectname.ini file.
Location of the MS Access database files used for project administration with SpecManager.
The lowest subdirectory must exist before a new project project file can be created by SpecManager.
|npd_unit||Unit of measure for the nominal piping diameter ('IN' for inch or 'MM' for milimeters)|
|coord_unit||Unit of measure for model coordinate unit ('M' for meters, 'MM' for milimeters, 'IN' for inch)|
|user_defined_diameter_table||Define 0 as value for ‘No’, a value of 1 means ‘Yes’ (see also section user_defined_diameter_table)|
Defines the libraries that will be transferred to the MS Access database (pjstb and pc_dims). This process can take a very long time (up to one and a half hour!)
A value 0 means ‘No’, 1 stands for ‘Yes’ (only, if new ASCII file version)
Selection of approved or unapproved libraries and reference database
important: consider to synchronize seedfile ‘mdlsdz.dgn’, set all entries of Project Data Manager / Reference Database File Specification / Approval Status to ‘Approved RDB’ or ‘Unapproved RDB’
A value of 0 stands for ‘Unapproved’, value 1 means ‘Approved’ (Default setting)
|branches_all||placement of all branches (set to value 1) or only according to branch table (set to value 0)|
placement of flange unions, getting all bolts and nuts in report
Set to value 1 for ‘Yes’, a value of 0 means ‘No’
the program continues with next component or flange union after creation of 3 errors for a component or flange union with identical properties
Assign a value of 1 for ‘Yes’ of 0 for ‘No’
If this parameter is set to 1 the whole data will be loaded but without model creation and component placement.
This parameter may be useful for adaption of all parameters in an .ini file it is considered settings of extract_libs and extract_pcds in .ini file
Set to this parameter to a value of 1 to enable or 0 to disable this option.
|clear_mo del_after_last_run_with_errors||Set to this parameter to a value of 1 to enable or 0 to disable this option.|
|Section Design_Volume_Monum ent_in_Plant_Coordinate_System|
defintion of basis coordinates (easting, northing, elevation)
See Project Administrator / Project Data Manager / Seed / 3D Plant Design Data / Coordinate System
|Definition for 'PIPING'|
|alphanumeric model builder uses keyword 'PF' for flanges list of all abc codes for flanges entries according to number will be prefered for flange unions|
|all abc codes of components where npd1 > npd2|
where condition of components not placed by SpecManager
Components with nominal piping diameters (npd1, npd2) will only be placed by SpecManager, when reference table from pcdim library contain these nominal piping diameters. It should be used for components with different npd1 and npd2, because of defintion of ranges for npd1 and npd2 in piping commodity data (for example: reducing tee with model_code='TRB' and gcp_from_nom_diam=0.75", gcp_to_nom_diam=24", rcp_from_nom_diam=0.5", rcp_to_nom_diam=20". If no line exist for checking of 'TRB' in .ini file then the program would try to place a reducing tee from 20" to 2" (for example)).
You don't need any check, when gcp_from_nom_diam equal gcp_to_nom_diam
--> 'REDC_39_300_300_A for model_code 'REDC' and gcp_end_prep, rcp_end_prep between 300 and 399
SpecManager only uses npd's from this table for placement of components with model_code 'REDC'
|Examplary usage in .ini file:||
2_ct=Item_Name//Geo_Ind_S td//Term_Type_1//Pr_Rating_1//Te rm_Type_2//Pr_Rating_2//A#WHERE (model_code='REDC') AND (gcp_end_prep=401) AND (rcp_end_prep=401)
3_ct=Item_Name//Geo_Ind_S td//Term_Type_1//Pr_Rating_1//Te rm_Type_2//Pr_Rating_2//A#WHERE (model_code='REDC') AND (gcp_end_prep=421) AND (rcp_end_prep=421)
4_ct=Item_Name//Geo_Ind_S td//Term_Type_1//Pr_Rating_1//Te rm_Type_2//Pr_Rating_2//A#WHERE (model_code='REDC') AND (gcp_end_prep=441) AND (rcp_end_prep=441)
5_ct=Item_Na me//Geo_Ind_Std//Term_Type_1//Te rm_Type_2//Pr_Rating_2//A#WHERE (model_code='REDC') AND (gcp_end_prep between 300 AND 399) AND (rcp_end_prep=401)
6_ct=Item_Na me//Geo_Ind_Std//Term_Type_1//Te rm_Type_2//Pr_Rating_2//A#WHERE (model_code='REDC') AND (gcp_end_prep between 300 AND 399) AND (rcp_end_prep=421)
7_ct=Item_Na me//Geo_Ind_Std//Term_Type_1//Te rm_Type_2//Pr_Rating_2//A#WHERE (model_code='REDC') AND (gcp_end_prep between 300 AND 399) AND (rcp_end_prep=441)
**8_ct=Item_Na me//Geo_Ind_Std//Term_Type_1//Pr _Rating_1//Term_Type_2//A#WHERE (model_code='REDC') AND (gcp_end_prep=401) AND (rcp_end_prep between 300 AND 399)**
**9_ct=Item_Na me//Geo_Ind_Std//Term_Type_1//Pr _Rating_1//Term_Type_2//A#WHERE (model_code='REDC') AND (gcp_end_prep=421) AND (rcp_end_prep between 300 AND 399)**
**10_ct=Item_Na me//Geo_Ind_Std//Term_Type_1//Pr _Rating_1//Term_Type_2//A#WHERE (model_code='REDC') AND (gcp_end_prep=441) AND (rcp_end_prep between 300 AND 399)**
|allowed keywords for section [Check_Table_NPD]|
|#2 WHERE Condition||
|list of branches (if option 'Branches according to Branch Table' is selected then the list is used not to place the components with this abc codes, when they not exist in branch table)|
|alphanumeric model builder uses keyword 'PB' for branches which found in branch tables branches not in branch tables will be placed by alphanumeric model builder keyword 'PC' (Place Component)|
|Section Branches_on ly_Placing_acc_to_Branch_Table|
|List of abc codes for branches, which can only be placed according to the branch_table|
|compatibilty of pressures for placement of flange unions|
# pr_rat_1, pr_rat_2, npd_from, npd_to (pr_rat_1 < pr_rat_2)
1_pr=300 600 0.5 3
2_pr=900 1500 0.5 2.5
|compatibility of end preparations for placement of flange unions|
# first value lower/equal second value
|if user defined diameter should be used can be defined in program|
Start PDS -> Project Administrator -> Project Data Manager -> Seed -> Piping Model Data - Revise -> Piping Data Control
Set 'Maximum Number of Blocks for Piping Design File' to 0.
First Step (first test):
Select Create new project
Select projname.ini of edited .ini file
Definition of name and location of .mdb file (projname.mdb)
Set Nominal Piping Diameter: mm or in
Set Coordinate Placement Unit: mm, m, or in
Set Comparision Nominal Piping Diameter with: 'Diameter Table (Header)'
Set Extract Libraries (Ascii) from PDS: 'New / Changed Lib's'
Set Extract PCD (pdtable_202) from PDS: 'All Pcd's'
Set Load only Lib’s, Tables and PCDs to FALSE (Check Mark must not be active)
Set Number of AMB runs to 5 (Cancel alphanumeric model builder runs after 5 errors)
Please consider 1 run will take about 2 minutes.
Select only one piping material class, you want to check (for first test).
The import of libraries will take up to one and a half hour. For each alphanumeric model builder run will be needed about 2 minutes.
Model file will be created. The model file of test piping material class contain all components placed by spec manager.
After completion press Report Model Builder Runs to see the results
Open PDS and check the created model
Second Step (for .ini file revision of project):
Start Spec Manager
If you haven't changed reference tables in PDS (see 4.6 [Check_Table_NPD]) and limits, diameter or branch tables then Set Extract Libraries (ASCII) from PDS: Use last Extraction
Set Load only Lib’s, Tables and PCDs to TRUE (Check Mark must be active)
Select all piping material classes
After completion close program.
Use queries 'branches', 'endpreps' and 'npd2_greater_0' to revise following in .ini file:
Revise .ini file
Third Step (final):
Start Spec Manager
If you haven't changed reference tables in PDS (see 4.6 [Check_Table_NPD]) and limits, diameter or branch tables then Set Extract Libraries (Ascii) from PDS: Use last Extraction
Set Load only Lib’s, Tables and PCD’s to FALSE (Check Mark must not be active)
Set Number of AMB runs to 15 (Cancel alphanumeric model builder runs after 15 errors for each piping material class)
Select piping material classes, you want to check
After completion press Report Model Builder Runs to see the results.
Open PDS and check the created models
Revise the piping commodity data or tables in pcdim libraries, where spec manager has found an error according to Report Model Builder Runs
Load all revisions in PDS
Start SpecManager ...
If you have changed reference tables in PDS (see 4.6 [Check_Table_NPD]), limits, diameter or branch tables then Set 'Extract Libraries (Ascii) from PDS': 'New / Changed Lib's'
Repeat the third step until no more errors exist in piping material classes.
If you get errors with nominal piping diameters not in piping commodity data then set Comparision Nominal Piping Diameter with to Diameter Table (Header) and 'User defined Diameter Table (.ini- File)' and check [User_defined_Diameter_Table] in .ini file.