Project Configuration
- Last UpdatedJan 08, 2026
- 2 minute read
The table below contains all the steps an administrator needs to check when he attempts to configure the MDS application for a project’s requirements.
|
Step |
Description |
|
1 |
From within the PARAGON Application, select Modify>MDS Application Defaults to display the MDS Admin Data form. Modify the defaults: Design Application Defaults for example, Clearance, Overlap, Pipe slope Application Support Type for example, FT03 not needed by project. Replacement Support Name for example, FT09 displayed in Design and Draft Application as PS132 Support Descriptions for example, Pedestal Support for Elbow required to be described as Duck Foot Available Support Ancillaries for example, AT01 not allowed on Support Type FT08 Modify the Hangers Configuration Description and Configuration name (optional). Remove configurations that are not used on the Project (optional). NOT RECOMMENDED. |
|
2 |
From within the PARAGON Application, select Modify>MDS Ancillary Defaults to display the MDS Ancillary Defaults form: Compete all dimensions (design parameters), weight, minimum and maximum values required by the project |
|
3 |
Modify the project specification to match settings used in step 2. For example the pipe class ‘CS’ for carbon steel to match the :MDSPipeMat uda at specification level in the project. |
|
4 |
From within the PARAGON Application, select Modify>MDS Application Defaults to display the MDS Admin Data form. Modify the support zone identification (Zone ID) settings. |
|
5 |
Modify DES-SUPP-NAMES* in the project default directory for: Auto naming files. |
|
6 |
Structural Design Templates - Refer to the MDS Framework Template Administration section for information on how to achieve this. |
|
7 |
Hanger Design Templates - Check that the Template represents the configuration defined in the MDS Admin Data and MDS Hanger Data forms (Modify menu in PARAGON). Not required if using a MDS Hanger Manufacturer Interface. |
|
8 |
Drawing Backing Sheets ‑ To be modified/created to suit project requirements. |
Figure 2:1. Project configuration checklist