Plant Data Management System

User Guide

PDMS Development Team

Cygna Energy Services, Inc.

1600 S. Main Plaza, Suite 120, Walnut Creek, CA 94526 Phone: 925.930.1111, Fax: 925.930.1111, Web: www.cygna.net Email:

V 3.4.1.0

September 16, 2008

Abstract

This document is a User Guide for the Plant Data Management System (PDMS).


Table of Contents

1. Conceptual Overview
What is the Plant Data Management System?
2. PDMS Help
How to use PDMS Help
How to Read this User Guide
3. Functional Overview
Data Display Tools
Sort button
Filter button
Add Bookmark button
Navigate button
Reports button
Summary / Multi-Row Display button
Multi-Row Display
Summary Display
Navigating Screens
Movement between screens
Updating Records
Menus
Sorting and Filtering Data
4. Analysis Overview
PDMS Analysis
Analysis Functionality
Cable Type - Cable Safety Group Compatibility Analysis (CS)
Cable - Raceway Safety Group Compatibility Analysis (SG)
Cable – Blocked Raceway Analysis (BK)
Cable Type – Color Code Compatibility Analysis (CC)
Cable - Missing Wires Analysis (MW)
Cable - Raceway Voltage Level Compatibility Analysis (VL)
Cable - Routing Continuity Analysis (CX)
Cable - Separation Group - Voltage Level Analysis (SV)
Cable Type - Cable Voltage Level Compatibility Analysis (CV)
Cable - Missing Block/Point Analysis (BP)
Cable - Routed through SD Raceway Analysis (SD)
Cable - Ampacity Analysis (LA)
Cable - Length Analysis (LN)
Cable - Terminal Point Analysis (WF, WT)
Fiber Cable Signal Loss Analysis (SL)
Minimums Analysis (MN)
Raceway - Combustible BTU Load Analysis (BA)
Raceway - Fill Analysis (AA, AB, DA, DB, SA, SB, N1, N2, N3, N4, N5, S1, S2, S3, S4, S5)
Raceway - Heat (Watts / Ft) Analysis (HA)
Raceway - Missing Length Analysis (MN)
Raceway - Missing Link Analysis (FT)
Raceway - Raceway Separation Group Compatibility Analysis (SG)
Raceway - Raceway Voltage Level Compatibility Analysis (VL)
Raceway / Room / Zone / Area - Missing Link Analysis (FZ)
Raceway Type - Raceway Commodity Compatibility Analysis (RT)
Raceway - Weight Analysis (WA)
Room / Zone / Area - Combustible BTU Load Analysis (B1)
Safe Shutdown Analysis (SS)
Wireway - Gutter Analysis (WG)
5. Modules
Module Security
System Settings / Preferences
User Information / Preferences
Active User/Locks
Preferences
Color Setting
System Information
User Information
Change Password
Change User Data
Change the Active Department / DCD
Documents
Document Overview
Document Selections : Documents / Images
Document Search Results
Design Change Document (DCD)
The DCD Process
Design Change Documents: DCD Types
Design Change Document (DCD): Functions
Design Change Document (DCD): Field Definitions
Design Change Document (DCD): Add a DCD
DCD Details
DCD Problems
Pending Details
Pending IDs
DCD Pending Cards
Statistics
DCD History
DCD Selection screen
DCD Search Results
ECF
Reference
Reference Detail Overview
Cable Type Details
Raceway Type Details
Extended Details
Extended Details
Column Association
Extended Detail Data ( Details(2) )
Column Association
Reference Detail Selection
List of Records
DCDs
Reference Search Results
Component
Component IDs
Component Overview
Functions
Auto Add / Delete
Copy Function
Renumber Function
Data Screens
Alias / Id
Allowable
Blocks
Cable Reels
Extended Detail Data ( Details(2) )
Combustible Load
Comments
Covers
Devices
Details
Extended Detail Data ( Details(2) )
Dimensions
Docs / Images
Fuse Data
History (Cards)
History (Renumber)
History (Revisions)
Instrument Data
IO Point Data
IO Point Signals
Links (Continuity)
Load Data
Locks
Notes
Pending Cards
Pending Changes
Problems
Problem Overrides
Quantities
Routing
Routing (Fire Area, Fire Zone, Room Number)
Splices
Summary
Terminal Points
Terminations
Terminations (All)
Tools
Wire Data
Wires
Wrap Data
Component Selection Screens
Documents / Images Selection
File of Records
Safe Shutdown (SS)
DCDs
Links
Routing / Incl Cables
Component Results
Installation
Installation Cards
Installation Module Overview
Alias / Id / Card No.
Pending Cards
DCDs
Installation Results
Safe Shutdown
Safe Shutdown / Combustible Load
Combustible Loading Overview
Safe Shutdown Overview
Safe Shutdown Equipment
Safe Shutdown Cables
Safe Shutdown Power Supply
Safe Shutdown Analysis
Safe Shutdown Strategy
Safe Shutdown Equipment by Fire Zone
Safe Shutdown Equipment by Fire Area
Fire Probabilistic Risk Assessment (PRA)
6. Reporting
Reports
Reports Menu
Report Options
7. Security
Security
Security Overview
PDMS Logins and User Information
Departments, Roles, and Levels of Authority
Roles
Departments
Users
8. Add Screens
Add Screens
Add Screen Overview
Add Menu
Add a Generic Id
Add Cable Ids
Add Raceway IDs
Add DCD
Add Detail
Add Document
9. Administration
Administration
Customer Preferences
Screen Settings
Report Settings
Report Section Data Types
Status
PDMS Statuses
10. Configuration
Configuration Overview
11. Verification
Software Verification
Analysis Process Verification
Database Verification
Automated Functional Testing
Manual Testing
12. Testing
A. Install
Installing the Plant Data Management System (PDMS)
Requirements
Manual install on Windows
Content of the installation directory
Acknowledgments
Glossary
Index

List of Figures

3.1. The Menu Toolbar
5.1. Active Logins
5.2. User Preferences
5.3. Color Settings
5.4. System Information
5.5. User Information
5.6. Change Password
5.7. Change User Data
5.8. The Menu Toolbar
5.9. Document Search
5.10. Document Search Results
5.11. Document Details
5.12. Document Search
5.13. Document Details
5.14. DCD Details
5.15. DCD Problems
5.16. DCD Pending Details
5.17. Document Search
5.18. DCD Statistics
5.19. DCD History
5.20. DCD Search
5.21. DCD Search Results
5.22. Cable Type - Voltage Level Compatibility
5.23. Cable Type - Separation Group Compatibility
5.24. Reference Search
5.25. Reference Search (File of Records)
5.26. Reference Search (DCD)
5.27. Reference Search Results
5.28. Auto-Routing Criteria
5.29. Component Alias
5.30. Component Allowable
5.31. Component Comments
5.32. Component Details
5.33. Component Docs / Images
5.34. Component History (Installation Cards)
5.35. Component History
5.36. Component Notes
5.37. Pending Cards
5.38. Component Pending Changes
5.39. Component Problems
5.40. Component Problem Overrides
5.41. Component Quantities
5.42. Component Routing
5.43. Component Summary
5.44. Component Terminations
5.45. Component Search Results
5.46. Installation Search
5.47. Installation Search Results
6.1. Report Options
7.1. Users
8.1. Add a DCD
8.2. Add a Reference Detail
10.1. Configuration Module

List of Examples

12.1. Sample Formula

Chapter 1. Conceptual Overview

What is the Plant Data Management System?

The Plant Data Management System (PDMS) is an analytical database that is used to manage and analyze engineering, maintenance, construction, and surveillance activities. The software provides appropriate screens and reports to manage and control changes that are made to data that is as-built and in-design. It further analyzes the data to determine if the data meets customer design criteria. PDMS identifies where existing conditions and proposed design changes may be in conflict with the given design criteria. As data is added and updated over the life of the database and facility it is continuously analyzed, increasing the quality of the analysis output. This accuracy leads to less dependency on an individual's power of recollection and technical knowledge. As new problems and potential conflicts are identified, pro-active improvements and/or design enhancements can be scheduled to improve compliance with safety, constructability, quality, maintenance, operational, and other standards, specifications, and procedures. PDMS has been designed with an intuitive user interface that makes it easy to select, review, update, and analyze data interactively from remote terminals.

The following list represents just a small subset of the analyses that PDMS can perform:

  • Voltage Drop

  • NEC Fill

  • Voltage Level

  • Conduit Sizing

  • Continuity

  • Circuit Protection

  • Separation Group

  • Fire Safety and Combustible Load

  • Weight/Foot and BTU/Foot

  • Cable Derating and Ampacity

Chapter 2. PDMS Help

How to use PDMS Help

The PDMS Help system is designed for two uses:

  • Online. PDMS Help is designed to function as an “online book”, by utilizing the table of contents as well as the ‘index’ and ‘find’ features.

  • Hardcopy. The PDMS Help documentation can be printed and referred to offline as a User Manual. Many topics contain illustrative graphics, or “screen shots”, which facilitate the written explanations.

How to Read this User Guide

The User Guide has been designed to have roughly the same flow as the PDMS system itself. Information pertaining to a particular module has been grouped by the Module Name and then by sub-category.

[Tip]Tip

The structure of the User Guide is similar to the actual PDMS system

Special Conventions Edit Masks, or Data Templates, describe the format of data that may be entered into PDMS. Many of the values in PDMS, such as DCDs and Component IDs, must conform to a specific pattern. Throughout this User Manual the following conventions will be used in terms of describing valid data entry:

  • n - a digit (0 through 9)

  • a - a letter (a through z)

  • x - any alphanumeric character (0 - 9, a - z, A - Z)

  • A - A constant in the form of a capital letter. The user must enter the value using the capital letter listed in exactly the place listed. Special characters, such as a hyphen, are also treated as literal constants.

  • Y - Year, normally in the form yyyy.

Some examples of edit masks found in PDMS, along with valid and invalid examples follows:

  1. DCD Type: DCP Edit Mask: DCPyy-nnnn

Valid values include: DCP99-1234, and DCP05-9999. Invalid values include: ECP99-1234, and ECPxa-000

Chapter 3. Functional Overview

Data Display Tools

Figure 3.1. The Menu Toolbar

The Menu Toolbar

Sort button

ToolsSort

Sorts DCD results data.

Filter button

ToolsFilter

Filters DCD results data.

Add Bookmark button

Adds bookmarks to DCD results data.

Navigate button

Permits drill-down through related information.

Reports button

Opens the Reports dialog box, permitting reports to be run against DCD results data.

Summary / Multi-Row Display button

Toggles DCD results display between Multi-Row and Summary display formats, as shown below.

Multi-Row Display

This format displays DCD results as selectable line-items of data.

Summary Display

This format displays DCD results in a printable report format.

Navigating Screens

Movement between screens

Each PDMS component and it's details are accessed via data selection screens and sub-screens. Through them, the user "drills down" to specific results by specifying general selection/search criteria on data selection screens, and by refining the search through subsequent sub-screens, as outlined below.

  • Selection Screens. Data selection screens include selection/search criteria areas comprising fields, drop-down menus, and other data entry areas. The data selection criteria can be processed via the function buttons at the bottom.

  • Results Screens. Results screens display horizontal line items of data segmented into vertical data columns. The line items of data can be selected individually or in multiples (according to standard Windows functionality; e.g., double-click, Shift+click or Ctrl+click and processed via the function buttons at the bottom.

  • Common Screens. Common screens are L-shaped "outer areas" that provide options and functionality for selecting specific screens (see below) nested within them. These options and functionality include a scrolling Screen Selection list, Data status radio buttons (e.g., As Built, My DCD, All DCDs) and a Filter/Sort option, Row Status fields for selected line-items of data, and function buttons.

  • Specific Screens. Specific screens are "nested" in the rectangular upper-right zone of common screens (see above), and display horizontal line items of data segmented into vertical data columns?the results of the final level of refinement specified on the common screen in which it nests.

Updating Records

To modify PDMS records you must first select the record or group of records you are interested in changing. Once these records have been selected to the appropriate "Results" screen, you can double click on them and proceed to the appropriate data screen to perform the modification. Following is a brief description of the basic update options in PDMS. Special purpose options are described in their respective modules.

Modifications

To modify a database record you must first go to the screen that contains the appropriate data and type the new information on top of the old information. PDMS automatically turns this transaction into a Delete transaction and an Insert transaction. On most screens you will see a (-) symbol on the row that will eventually be deleted. You will see a (+) symbol on the row that will be inserted. Both rows are highlighted with a different background color.

Inserts

To insert new rows of data to the PDMS database simply go to the appropriate screen and depress the Insert button, and type the new data on the blank row. The new row is highlighted as changed and marked with the (+) symbol.

Deletes

To delete a row of data from the database, simply go to the appropriate screen, point to the row you intend to delete, and depress the Delete button. The row is highlighted as changed and marked with the (-) symbol.

Menus

Add Menu

The Add menu permits the addition of components, details, documents and DCDs.

Menu items

  • AddId Used to create and format new component Ids such as cables, raceways, fire areas. They can then be located in the database via the Component module.

  • AddReference This screen is used to create and format new reference library details such as cable types, separation groups, and voltage levels. They can then be found in the database via the Reference module.

  • AddDCD Create a new Design Change Document (DCD).

  • AddDocument Create an additional document or drawing.

File Menu

The File menu provides access to file/document functions.

Menu items

  • FileClose Close the active file or document.

  • FileSave As Save the active file or document under a different filename.

  • FilePrint Print the active file or document.

  • FilePrint Preview Print Preview. Preview the active file or document for printing.

  • FilePrint Setup Change print settings (destination printer, number of copies, etc.).

  • FileExit Exit the PDMS application.

[1]

Help Menu

The Help menu displays PDMS Help (this Help file), Windows Help, and About Cygna Energy Services, Inc.

Menu items

  • HelpHelp Topics Opens the PDMS Help index window.

  • HelpProject Guide (Web) Opens a Project Guide web page (See Customer Preferences).

  • HelpContact System Administrator Send an email to the System Administrator.

  • HelpUser Guide Opens the PDMS User Guide.

  • HelpAbout Opens the PDMS About file.

Module Menu

The Module menu provides PDMS module selection.

Menu items

  • ModuleDocument Document module search screens.

  • ModuleDCD DCD module search screens.

  • ModuleReference Reference Detail module search screens.

  • ModuleComponent 1 Component module search screens (Basic).

  • ModuleComponent 2 Component module search screens (Advanced).

  • ModuleInstallation Installation module search screens.

  • ModuleSecurity Select the Security module. (System Administrator Only).

  • ModuleConfiguration Select the Configuration module. (System Administrator Only).

  • ModuleAdministrator Select the Administrator module. (System Administrator Only).

  • ModuleVerification Select the Verification module.

Report Menu

The Reports menu allows for report selection.

Menu items

  • ReportReports This option appears when Ids are selected or 'marked'. It opens the report selection screen.

  • ReportAdhoc Reports Permits ad-hoc reporting (without first selecting Ids).

  • ReportPSR Files PowerBuilder Format…To be used only between PDMS users.

  • ReportPrint Window Print active PDMS window.

  • ReportPrint Screen Prints the current active screen contents.

Tools Menu

The Tools menu permits user and system settings to be specified.

Menu items

  • ToolsSettings / Preferences Open the System Settings / User Preferences screen.

  • ToolsChange Department / DCD Specify a different department / Design Change Document (DCD) to associate with the active file/document.

  • ToolsAnalysis Gauge Summarizes the analysis activity that takes place using a background server process. The gauges on this screen provide the user with a percent completion status.

  • ToolsCheck Analysis Verifies that Analysis is/is not running.

  • ToolsScreen Authority (System Administrator Only). Allows alteration of screen visibility by authority level.

  • ToolsGo to Bookmarks Open bookmarked file(s)/document(s).

Window Menu

The Windows menu permits standard windows display options.

Menu items

  • WindowVertical Arrange open windows vertically.

  • WindowHorizontal Arrange open windows horizontally.

  • WindowLayer Arrange open windows in symmetrical layers.

  • WindowCascade Arrange open windows in cascade layout.

  • WindowArrange Icons Organize desktop icons.

  • WindowToolbars Specify Toolbar preferences.

[2]

Sorting and Filtering Data

To sort the data on a screen different than the default sort, there is sometimes a Sort option. Likewise, there is also the Filter option narrow the scope of selected rows. To use these options, either click the screen's Sort and Filter options, or use the Tool menu, Sort or Filter options.

[3]



[1] Any PDMS windows left open upon Exit will not re-open the next time PDMS is launched. Only the User Preferences Screen will appear at start-up.

[2] **Active Windows can be accessed from the list following the above options.

[3] Some of the reports have a fixed sort order so that the output remains meaningful

Chapter 4. Analysis Overview

PDMS Analysis

The default procedure for PDMS is to post each id to an analysis queue and analyze everything about the id whenever anything about the id is modified. This process is done on the server computer.

A second procedure is for the user to select ids to the component result screen, mark the ids to be analyzed, and press the Analyze function. A list of analysis types is provided and the user can select the type of analysis that is desired. The user can also choose whether or not to perform the analysis on the workstation (On-Line) or post the ids for analysis on the server (Post).

A third alternative is for the user to go to the Analysis screen and use the "Audit" function. The function reanalyzes the id for the pertinent analysis and provides an audit report itemizing the inputs and outputs for the analysis.

[Note]Note

Where it is prudent, PDMS also performs analysis as data entry is performed.

For example:

  • When route points are inserted into a cable’s routing, instant continuity analysis is performed.

  • When a color code detail is inserted on the detail screen, instant analysis is performed to warn you if the color code is incompatible with the cable code.

  • When a raceway is linked to another raceway, instant analysis is performed to warn you if the separation groups for the two raceways are incompatible.

Following is a general discussion of each PDMS analysis process. Per customer requirements, variations of the following analyses are provided, and some of these analyses may be turned off on your project. The software shall analyze the following data relationships to determine if a specific design criterion is being met. In general, if no problem is posted, the design meets requirements. If problems are posted, they need to be addressed by the customer and shall either be corrected or overridden before any design change document (DCD) associated with the id can be advanced to its next higher status level.

Where practical, the system administrator shall have the capability to adjust the data contained in the appropriate underlying data tables to override certain functions of the analysis software. Where appropriate, data analysis shall have the capability to differentiate between records that are as built and records that are in-design.

Analysis Functionality

Cable Type - Cable Safety Group Compatibility Analysis (CS)

When a cable type detail is added to a cable, the software will determine if the cable type is compatible with the cable’s separation group. If not, a problem will be posted with the cable. Valid separation groups for each cable type are stored on cable type compatibility table.

Cable - Raceway Safety Group Compatibility Analysis (SG)

When a cable is routed through a raceway, the software determines if their separation groups are compatible. If not, a separation group (S1) problem is posted. Valid combinations of cable - raceway separation groups are stored on a separation group compatibility table by the system administrator.

Cable – Blocked Raceway Analysis (BK)

When a cable is deliberately routed through a blocked raceway, the software will post a problem with the cable if the raceway was assigned to the cable’s routing after the raceway was designated as blocked.

Cable Type – Color Code Compatibility Analysis (CC)

When a color code detail is added to a cable, the software will determine if the color code is compatible with the cable’s cable type. If not, a problem will be posted with the cable. Valid color codes for each cable type are stored on a cable type compatibility table.

Cable - Missing Wires Analysis (MW)

When a non-spared cable is not assigned at least one non-spare wire, the software will post a problem with the cable. This problem is a reminder that the user added a new cable to the database, but forgot to assign wire numbers to it.

Cable - Raceway Voltage Level Compatibility Analysis (VL)

When a cable is routed through a raceway, the software determines if their voltage levels are compatible. If not, a voltage level (V1) problem is posted. Valid combinations of cable - raceway voltage levels are stored on a voltage level compatibility table by the system administrator.

Cable - Routing Continuity Analysis (CX)

When a cable is routed, the software will determine if the cable's adjacent route points are pre-designated as linked to each other. If not, a problem will be posted. Valid raceway from / to links will be specified on a raceway linkage table.

Cable - Separation Group - Voltage Level Analysis (SV)

When a cable's separation group is not compatible with a raceway's voltage level, the software will post a problem with the cable.

Cable Type - Cable Voltage Level Compatibility Analysis (CV)

When a cable type detail is added to a cable, the software will determine if the cable type is compatible with the cable’s voltage level. If not, a problem will be posted with the cable. Valid voltage levels for each cable type are stored on a cable type compatibility table.

Cable - Missing Block/Point Analysis (BP)

The default configuration for non-spare cables will be to provide block and point termination information for the non-spare wires at both of the cable’s ends. Cable terminations may also be designated as "Not Required". When terminations are required, and no block and point information exists for the non-spare wires, the software will post a problem with the cable and indicate which end of the cable has the problem.

Cable - Routed through SD Raceway Analysis (SD)

When a cable is routed through a raceway that is scheduled for deletion, the software will post a problem with the cable.

Cable - Ampacity Analysis (LA)

The software will calculate the derated circuit ampacity of the cable at each of its route points and post a problem with the cable if its derated ampacity is less than its load.

When a cable cannot be properly analyzed because of insufficient load or raceway data, the software will post an incalculable ampacity (IL) problem with the cable.

The allowable ampacity for each cable is calculated by the software based on the cable’s ambient temperature, raceway fill percentages, raceway wrap statuses, raceway cover statuses, and whether or not the cable Id is routed through fire seals. When the cable’s load is larger than its allowable ampacity in a raceway the software will post a problem with the cable.

Cable - Length Analysis (LN)

When a cable is routed, the software will sum the lengths of the cable's route points to determine the calculated length of the cable. The calculated length of the cable will be stored on the database and if the calculated length of the cable is longer than its allowable maximum length, a problem will be posted. If no allowable length is provided, no problem will be posted.

If a cable's length cannot be calculated properly (usually a raceway is missing a length) an incalculable length (IN) problem is posted with the cable.

If a cable is associated with an allowable length and the calculated length exceeds its allowable length, an over length (ON) problem is posted with the cable.

Cable - Terminal Point Analysis (WF, WT)

When changes are made to a cable’s terminations, the software will analyze each cable’s wires to determine if any of their terminal points have more than two wires associated with it. If so, a problem will be posted with the cable indicating which wire at which end of the cable has the problem. If a wire number is prefixed by an asterisk (*), it will be ignored by the cable - terminal point analysis process. The software will allow for multiple *GND wires (>2) and multiple *SHLD wires (>2) to be terminated on ground and shield buses.

Fiber Cable Signal Loss Analysis (SL)

When a cable is a fiber optic cable, the software will calculate the signal loss for the cable based on its length, type of fiber cable, splices, and other pertinent criteria. When the calculated signal loss for the cable is more than the allowable signal loss for the cable, the software will post a problem with the cable.

Minimums Analysis (MN)

When a detail or note or quantity or other data element is considered to be important "minimum" elements of data for a component Id, the software determines if the data is missing. If it is missing, a problem is posted. "Minimum" data types are specified in tables and maintained by the System Administrator. Minimum data elements can be specified for aliases, allowables, details, documents, notes, and quantities. For example, if it is specified that each cable should have separation group and a voltage level details, the software will post a minimum (MN) problem on the problem table if at least one voltage level and separation group is not specified for the cable.

Minimum Detail Analysis (MN). When a detail is considered to be an important 'minimum' data for a component Id, the software determines if the detail is missing. If it is missing, a problem is posted. 'Minimum' detail types are specified on data tables and maintained by the System Administrator.

Minimum Quantity Analysis (MN). When a quantity is considered to be important 'minimum' data for a component Id, the software determines if the quantity is missing. If it is missing, a problem is posted. 'Minimum' quantity types are specified on data tables and maintained by the System Administrator.

Minimum Note Analysis (MN). When a note is considered to be important 'minimum' data for a component Id, the software determines if the note is missing. If it is missing, a problem is posted. 'Minimum' note types are specified on data tables and maintained by the System Administrator.

Minimum Allowable Analysis (MN). When an allowable is considered to be important 'minimum' data for a component Id, the software determines if the allowable is missing. If it is missing, a problem is posted. 'Minimum' allowable types are specified on data tables and maintained by the System Administrator.

Raceway - Combustible BTU Load Analysis (BA)

The software will calculate the combustible load of each raceway section by summing the BTU/ft values for its included cables.

When a raceway cannot be properly analyzed because of insufficient BTU data, the software will post an incalculable BTU (IB) problem with the raceway.

Raceway - Fill Analysis (AA, AB, DA, DB, SA, SB, N1, N2, N3, N4, N5, S1, S2, S3, S4, S5)

The software will calculate the fill of each raceway section by either of several methods, based on the commodity type and voltage level of the raceway. Some trays will have their fill calculated using a depth (DA, DB) methodology, some using a spacing (SA, SB) methodology, and some using a random area (AA, AB) fill methodology. Conduits will have their fills calculated using a random fill methodology.

Based on the customer option, the NEC series of fill methodologies will be substituted for the above described methodologies.

When a raceway cannot be properly analyzed because of insufficient fill data, the software will post an incalculable fill (IF) problem with the raceway.

The default allowable fill and weight for each raceway commodity / voltage level combination will be stored on a data table by the System Administrator. When the calculated fill for the raceway is more than the allowable fill for the raceway, the software will post a problem with the raceway.

Raceway - Heat (Watts / Ft) Analysis (HA)

The software will calculate the watts/foot each raceway section by summing the cable load watts/wt values for its included cables.

?When a raceway cannot be properly analyzed because of insufficient watts/ft data, the software will post an incalculable heat (IH) problem with the raceway.

Raceway - Missing Length Analysis (MN)

When a raceway has not been assigned at least one length, the software will post a minimum problem with the raceway. (See Minimums Analysis for additional information.)

Raceway - Missing Link Analysis (FT)

When a raceway doesn’t have at least one raceway from/to continuity link, the software will post a problem with the raceway.

Raceway - Raceway Separation Group Compatibility Analysis (SG)

When a raceway is linked to another raceway, the software determines if their separation groups are compatible. If not, a separation group (S2) problem is posted. Valid combinations of raceway - raceway separation groups are stored on a separation group compatibility table by the system administrator.

Raceway - Raceway Voltage Level Compatibility Analysis (VL)

When a raceway is linked to another raceway, the software will determine if their voltage levels are compatible. If not, a voltage level (V2) problem is posted. Valid combinations of raceway - raceway voltage levels are stored on a voltage level compatibility table by the system administrator.

Raceway / Room / Zone / Area - Missing Link Analysis (FZ)

When a raceway is not linked to at least one room or a room is not linked to at least one zone or a zone is not linked to at least one area, the software will post a problem with the appropriate raceway, room, zone, or area.

Raceway Type - Raceway Commodity Compatibility Analysis (RT)

When a raceway type is associated with a raceway, the software will determine if the raceway type is compatible with the raceway’s commodity type. If not, a problem will be posted with the raceway. Valid commodities for each raceway type are specified on a raceway type compatibility table.

Raceway - Weight Analysis (WA)

The software will calculate the weight per foot of each raceway section by summing the weight / ft values for it’s included cables and the weight/foot value for the raceway.

When a raceway is specified as covered, the top and/or bottom cover weight / foot will be included in the raceway’s weight / foot value.

When a raceway is specified as thermolagged, the thermolag weight / foot will be included in the raceway’s weight / foot value.

When a raceway cannot be properly analyzed because of insufficient weight data, the software will post an incalculable weight (IW) problem with the raceway.

The default allowable weight per foot for each raceway type will be stored on a data table for the raceway type. When the calculated weight / foot for the raceway is more than the allowable weight / foot for the raceway, the software will post a problem with the raceway.

Room / Zone / Area - Combustible BTU Load Analysis (B1)

The software will calculate the combustible load of each room by summing the BTU/ft values for its included raceways, and the BTU values for additional combustibles associated with the room.

The software will calculate the combustible load for each zone by summing the loads for each of the rooms linked to the zone.

The software will calculate the combustible load for each area by summing the loads for each of the zones linked to the area.

The default allowable BTU/ft for each room will be stored on a data table for the room zone. When the calculated BTU/ft for the room is more than the allowable BTU/ft for the room the software will post a problem with the room.

Safe Shutdown Analysis (SS)

The safe shutdown analysis will manage the cable and raceway safe shutdown details to assure that safe shutdown equipment, safe shutdown cables, associated cables, and associated raceways are identified appropriately per customer requirements.

Wireway - Gutter Analysis (WG)

When a raceway is designated as a wireway or gutter and contains more than 30 wires, the software will post a problem with the raceway. Refer to National Electrical Code (NEC) requirements.

Chapter 5. Modules

Table of Contents

Module Security
System Settings / Preferences
User Information / Preferences
Active User/Locks
Preferences
Color Setting
System Information
User Information
Change Password
Change User Data
Change the Active Department / DCD
Documents
Document Overview
Document Selections : Documents / Images
Document Search Results
Design Change Document (DCD)
The DCD Process
Design Change Documents: DCD Types
Design Change Document (DCD): Functions
Design Change Document (DCD): Field Definitions
Design Change Document (DCD): Add a DCD
DCD Details
DCD Problems
Pending Details
Pending IDs
DCD Pending Cards
Statistics
DCD History
DCD Selection screen
DCD Search Results
ECF
Reference
Reference Detail Overview
Cable Type Details
Raceway Type Details
Extended Details
Extended Details
Column Association
Extended Detail Data ( Details(2) )
Column Association
Reference Detail Selection
List of Records
DCDs
Reference Search Results
Component
Component IDs
Component Overview
Functions
Auto Add / Delete
Copy Function
Renumber Function
Data Screens
Alias / Id
Allowable
Blocks
Cable Reels
Extended Detail Data ( Details(2) )
Combustible Load
Comments
Covers
Devices
Details
Extended Detail Data ( Details(2) )
Dimensions
Docs / Images
Fuse Data
History (Cards)
History (Renumber)
History (Revisions)
Instrument Data
IO Point Data
IO Point Signals
Links (Continuity)
Load Data
Locks
Notes
Pending Cards
Pending Changes
Problems
Problem Overrides
Quantities
Routing
Routing (Fire Area, Fire Zone, Room Number)
Splices
Summary
Terminal Points
Terminations
Terminations (All)
Tools
Wire Data
Wires
Wrap Data
Component Selection Screens
Documents / Images Selection
File of Records
Safe Shutdown (SS)
DCDs
Links
Routing / Incl Cables
Component Results
Installation
Installation Cards
Installation Module Overview
Alias / Id / Card No.
Pending Cards
DCDs
Installation Results
Safe Shutdown
Safe Shutdown / Combustible Load
Combustible Loading Overview
Safe Shutdown Overview
Safe Shutdown Equipment
Safe Shutdown Cables
Safe Shutdown Power Supply
Safe Shutdown Analysis
Safe Shutdown Strategy
Safe Shutdown Equipment by Fire Zone
Safe Shutdown Equipment by Fire Area
Fire Probabilistic Risk Assessment (PRA)

Module Security

The PDMS menus are designed to restrict access to modules based on a user's authority level. For instance, access to the Configuration module is inappropriate for general users. The system administrator should have user authority levels set up so only users with very high levels of authority can display these screens and only the system administrator should be able to update the data on these screens.

Security at this level is done on the System Administrator / Modules screen. The Auth_Display data field is the key data field that should be adjusted. In most cases the default Labels for the menu items and the default micohelp (Description) for the items should not require alteration. If need be; however, the system administrator can also manipulate these data fields.

[Tip]Tip

The PDMS Result screen command buttons are each associated with a level of authority. Each button should be associated with an appropriate level of authority. To manage these levels of authority, use the Security / Module Functions screen.

System Settings / Preferences

User Information / Preferences

Active Logins

Each PDMS user must have a valid user Login Id and password. Logins and passwords are issued by the PDMS System Administrator.

Figure 5.1. Active Logins

Active Logins

Each time a user enters a valid login and password, PDMS starts and presents the user with a "System Settings / User Preferences" screen. This screen provides the user's login characteristics and previous settings and is a VERY IMPORTANT screen. Included on the screen is the user’s Department, Project, Role, Level of Authority, and associated Design Change Document (DCD). The screen also provides the user with appropriate screens to change his Password and other personal information. Briefly, the data on this screen determines the user’s capabilities within PDMS.

For example, if the user is associated with a "Display Only" role, the user cannot make changes to the database. If the user is associated with a Design Change Document that is not editable, the user cannot make changes to the database using that DCD. If the user is associated with a certain department, he may or may not be limited to making changes to data owned by another department.

In addition to the User Information screen, each user can alter some display characteristics of PDMS by changing the settings on the Preferences and Row Color Setting screen.

Active User/Locks

Lists the currently active PDMS users. This screen is used by the system administrator to in notify users when the system is going to be unavailable. The system administrator can also "kill" active sessions if it is determined the user should no longer be connected to PDMS.

Data Columns

Last Name

User's last name.

First Name

User's first name.

M.I.

User's middle initial.

Auds ID

SID

Serial

Status

Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

Work Phone

User's work phone number.

Fax Phone

User's fax number.

Home Phone

User's home phone number.

Tab-specific Buttons

Kill

Ends the current PDMS session for specific user.

Refresh

Data refresh.

Buttons

OK

Opens selected row(s) of data or performs requested operation(s).

Close

Closes the selected row(s) of data.

Preferences

Defines the customizable preferences within the PDMS application. The Users Department and Authority level will determine the availability of certain options.

Figure 5.2. User Preferences

User Preferences

User Preferences

Add Debugging Information to display Messages?

This option adds information that is useful to the PDMS Development Team. From time tom time you may be asked to check this box in order to provide more information on an issue which may be slowing your workflow.

Automatically fill in DCD on Selection screens?

This option makes data selection faster by adding your active DCD to the selection screens which will use it.

Display tooltip popup boxes on PDMS screens?

This option will produce a balloon tip when the mouse is held over the line number for a related ID, such as a Route Point or a Continuity Link. This avoids the need to drill-down in order to see a detailed description of the related Component ID.

Hide As-built Problems?

As Built problems will be filtered out of view if this option is enabled. The user can choose to view As Built problems on the Problem screen directly, if so desired.

Ignore Problems at Close Out?

If you have run the PDMS Verification process, you are familiar with this option. This option allows the DCD process to continue despite any problems that were created by changes in a package.

Initial Role Guest?

This option makes the user a guest when first logging into PDMS.

Open Component Selections (1) screen upon startup?

A user will often open a Component Selection screen when starting up PDMS for the first time every day. This option saves the extra work of opening the search screen at startup time.

Open only one selection screen per module?

When this option is selected then the user will return to the existing module selection screen whenever they click on the module search button. Otherwise, multiple search screens per module will be opened. The downside to opening multiple search screens for the same module is application clutter, where there are so many windows open at one time that it is difficult to manage the PDMS desktop efficiently.

Open the Module Query selection screen upon startup?

A user will often open a Module Query screen when starting up PDMS for the first time every day. This option saves the extra work of opening the search screen at startup time.

Save Changes without prompting for confirmation?

This allows the more advanced user to continue working without having to confirm each change to the database.

Save screen column width/order settings?

This option allows the user to override the factory default settings for screen sizes and column layouts. The user can customize the order of columns, the width of columns, and the size of windows that display this data. If the option is disabled then all objects will appear with sizing/order settings that are factory settings.

Save Settings on Exit?

When checked, user settings will be saved.

Show Text on the Toolbar?

When True the toolbar options will be shown in larger boxes with full text descriptons. This option can also be found by clicking the right mouse button while the mouse pointer is over the toolbar. A good deal of screen space is lost using this option, but new users may benefit from the text in the toolbar.

Sort the screen by clicking on the column heading?

Many times a PDMS user would like to sort the data on the screen by the values contained in one column, such as Component ID. When this option is on then many of the screens will allow the user to sort the contents by clicking on the column heading. The sort operation works at first as an ascending sort and then as a descending sort.

Use Composite Interface (PDMS 3.0)?

The new PDMS version 3.0 interface allows the user to view and manage data for multiple Component IDs within the same window. If a user is uncomfortable with the new interface they can revert to the old interface by unchecking this option.

Color Setting

Allows the user to specify display color preferences. The screen foreground and background colors are based on either the Windows settings or the PDMS color scheme, which is a gray-scale pattern similar to ButtonFace.

The In Design change indicator may also be selected on this screen. These values are specific to each user that has an independent login ID in PDMS.

Figure 5.3. Color Settings

Color Settings

Elements

  • Red slide bar - Settings for the color red.

  • Green slide bar - Settings for the color green.

  • Blue slide bar - Settings for the color blue.

  • Current Row Color Setting - Display settings for the current (selected) row.

  • Color bar - Displays available color options.

Buttons

  • Save button - Save changes.

System Information

This screen provides the user with host machine, display, operating system, database, and application information. The build date of the application is available, as well as the version of the database client (e.g. Oracle client 9i). This screen can be very useful when technical details are required for debugging application problems.

Figure 5.4. System Information

System Information

User Information

Provides important administrative data about PDMS users, such as departmental and DCD associations, role and authorization. The DCD can be changed from this screen directly, though the user will need to confirm the new settings on the Department / DCD screen. The authority level can be lowered on this screen, but it can only be restored to its original level from the Department / DCD screen.

Figure 5.5. User Information

User Information

Fields

  • Date/Time - The Date and Time the record was last updated.

  • User Name - User name.

  • Department - The user's current department or departments.

  • Role/Authority - User role and authorization level.

  • DCD - Design Change Document association.

  • DCD Status - Design Change Document status.

  • Broadcast Message - Broadcast messages (e.g., PDMS maintenance down times, etc.) from the system administrator.

Buttons

  • Change User Info - Permits the system administrator to change information in selected user records.

  • Change Password - Permits the system administrator to change password(s) associated with selected users.

  • Change Department - Permits the system administrator to change departmental associations for selected users.

  • Change Role - Permits the system administrator to change role(s) associated with selected users.

  • Change DCD - Permits the system administrator to change Design Change Document(s) associated with selected users.

Change Password

This screen enables users to change their password. This password is the database password that is used to connect to the RDBMS. PDMS does not maintain passwords for users of the system – PDMS relies on the password management features of the RDBMS exclusively.

Figure 5.6. Change Password

Change Password

Change User Data

This screen enables users to change phone numbers, e-mail and other personal data. The email address is an important attribute if the automated email functions have been enabled in PDMS. The ACTIVE switch is intended to disable future access into PDMS for the user. Because there is history in the PDMS archive tables for all users a User ID is not removed from the system, but is instead Deactivated. This allows the historical reports to continue to display information about users that performed actions in the past but who may be no longer authorized for system access.

Figure 5.7. Change User Data

Change User Data

Change the Active Department / DCD

Whenever a user logs into the PDMS system they are connected to a Department and a DCD. If, during the course of a PDMS session, the user needs to switch to another Department or DCD, then they will choose the "Change Department / DCD" option which will produce the following screen:

Figure 5.8. The Menu Toolbar

The Menu Toolbar

The user can filter the list to "Open DCDs" – those DCDs that have Pending Changes, or "All" DCDs - where Historical DCDs are also made available. As the user types in the "Search as you type" DCD field the list of available DCDs is automatically repositioned to the nearest correct choice.

Documents

Document Overview

Documents

The Document module is used to define valid documents such as drawings, specifications, procedures, and manuals. As different types of documents are defined in the Configuration module, each type of document is associated with a network path pointing to the document’s location, and a filename identifying the document. Each type of document is also associated with a "Viewer" so the document can be viewed from within PDMS.

Document Selections

The Document Selection screen allows the user to specify which document or group of documents they are interested in. The result of each selection is presented on the Document Results screen.

Figure 5.9. Document Search

The PDMS Document Search screen

Document Search Results

The Document Results screen provides a list of selected documents. From this list the user can add, change, copy, and delete documents from the database.

Figure 5.10. Document Search Results

The PDMS Document Search Results screen

Document Details

The Document Details screen is used to revise the attributes of a document, including Document Type (WIRING DIAGRAM, etc.), File Location, Title, and Active Status.

Figure 5.11. Document Details

The PDMS Document Details screen

Description/Remark

The Description/Remark screen is used to revise the description of the document and to add a remark to the document.

Component IDs

The Component IDs screen displays all Components that are linked to a Document. This is a very useful data navigation screen, as it allows the user to double-click and drill-down to any Component ID in the list.

Statistics

The Statistics screen summarizes how many records on the database use the document.

Creating a New Document

To create a new document on the database:

  1. Select the Add Document option from the main PDMS Add menu.

  2. Fill in the appropriate information about the document.

  3. Click on Save and exit the screen.

Copying a Document

To create a new document by copying an existing document:

  1. From the Document Results screen, point to a similar document and depress the Copy button.

  2. Fill in the appropriate information about the new document.

  3. Click on Save and exit the screen.

Document Selections : Documents / Images

Searching for a Document

Documents can be located in PDMS using search criteria such as Document (with wildcard options), document type, unit, and title.

Other options include searching by Classification (an internal list of Document Tags), and File of Records (an external file of Documents). If the Documentum Interface has been installed then the Documentum Search Tab is enabled. See the Documentum interface documentation for more information.

Figure 5.12. Document Search

Document Search

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Document Search Results

The Document Results screen provides a list of selected documents. From this list the user can add, change, copy, and delete documents from the database.

Figure 5.13. Document Details

Document Details

Data Columns

Row Numbering. Row numbers for current screen.

Selection box ?. This box can be checked / unchecked using the click, shift-click, and control-click features of the mouse.

Type. Indicates the type of document.

Document. Indicates document.

Sh. Indicates the sheet number.

Rev. Indicates revision number.

Title. Indicates document title.

Filename. Indicates document filename.

Function Buttons

Open. Opens the selected line-item of data (same as double-click).

Close. Closes the screen and returns to the appropriate Document Module selection screen.

New. Creates a new line-item.

Copy. Copies the highlighted line-item to another line-item named by the user.

Rename. Renames selected document.

Delete. Deletes the detail.

Sort. Opens Select Sort Order window and sorts results according to specified sort columns.

Filter. Opens Filter window and filters results according to specified filter criteria.

Design Change Document (DCD)

The DCD Process

The primary goal of the "DCD Process" is to maintain control over the PDMS data configuration so it accurately reflects the plant’s As-Built configuration. By assuring that uncontrolled changes are not made to the As-Built data, you are always able to determine what the plant As-Built configuration is, how DCDs will affect the As-Built configuration, and what actual changes are being staged through the design, installation, inspection, and feedback processes.

DCD Status: Advanced, Released and Demoted.

Parent and Child DCDs can be Advanced, Released, or Demoted to a higher or lower status. DCDs are Closed-Out when the intended changes have been approved and completed.

The DCD Advance function allows a DCD to be "promoted" from "New DCD" status to a higher status for Design Review, or "Advanced". Since each DCD status is associated with an "Editable / Not Editable" setting, the DCD can / cannot be used to make any more database changes. The toggle setting is defined by the status of the DCD. The software contains several DCD statuses. Other statuses are customizable by the system administrator from the Configuration module. A child DCD cannot be advanced beyond the status of its Parent DCD.

The DCD Release function promotes a DCD to "Released" status. "Released" status implies that the DCD has been reviewed and approved and is ready for implementation. This status is significant because non-preliminary installation cards can now be printed for the Ids in the DCD.

[Note]Note

Before a DCD can be "Released":

  1. All problems posted for the Ids in the DCD must be either corrected or overridden. A child DCD cannot be released beyond the status of its Parent DCD.

  2. The changes to the Ids in the DCD must have bee approved and feedback data recorded.

DCD Relation to Data in PDMS (As Built vs In Design): Each record on the PDMS database is either at "As-Built" status or at "In-Design" status. To update data in PDMS you must first be linked to an appropriate Design Change Document (DCD) that will be used to record and approve the changes you make to the database. When you log into PDMS, the first screen you see after the login screen (User Information) allows you to select a valid DCD.

If the DCD you have selected is "Uneditable", you will be placed in "Display Only" mode.

[Note]Note

Make sure you are linked to a valid "Editable" DCD before attempting to make changes to the PDMS data. If you do not see the appropriate DCD on the list of DCDs you can select from, contact the System Administrator. It probably means your department has not been authorized to use the DCD, or the DCD has already been advanced in status, and no further changes are allowed using the DCD.

When changes made with a DCD are completed, the System Administrator "Advances" the status of the DCD, and when the changes have been reviewed and approved, the System Administrator "Releases" the DCD. Depending on how the PDMS decision tables are set up, the DCD is usually "Uneditable" when it reaches "Released" status and further changes related to the DCD’s scope should be entered with a "Child" DCD, or, the System Administrator can "Demote" the DCD to a lesser status. If the DCD is demoted, it should go through another review and approval process. If the "Child" DCD is used for the supplemental changes, only the supplemental changes need to go through the review and approval process.

Eventually, when the changes have been implemented, the DCD and its child DCDs will be "Closed-Out." This means the former "As-Built" data is deleted from the database and is replaced with the new "In-Design" data. If for some reason a DCD is canceled before it is "Closed-Out", the System Administrator has the capability to automatically "Undo" the changes that were made using the DCD.

Design Change Documents: DCD Types

The DCD Type is one of several defined categories of DCD. The DCD type reflects if the DCD is a parent or child DCD. The system administrator defines valid DCD types.

The Parent field is used to specify the parent of a child DCD. If a DCD is a parent DCD, the Parent data field is the same as the DCD data field. Parent DCDs must be defined before child DCDs are defined.

The DCD field is the name of the DCD.

The Description field is used to describe the DCD.

The Project field is used to specify which project(s) the DCD is linked to.

The Department field is used to specify which department has lead responsibility for the DCD.

The Status field defines the status of the DCD and if the DCD is editable or NOT editable.

History (DCD). The History (DCD) screen displays a DCD’s status history in chronological descending order.

Pending Details. When changes are made to reference module records, the changes are recorded on log (Tracer) tables. The Pending Details screen summarizes the reference module changes that have been made using the DCD. From this screen the user can mark the rows that are intended for Close-Out and perform a full or partial close-out of the detail records.

Pending Cards. When changes are made to component module records, installation cards are generated and transactions regarding these cards are recorded on a log (Tracer) tables. The Pending Cards screen summarizes the changes that are pending for the DCD. From this screen the user can perform feedback for cards and indicate whether the card is at Check / Card Completed status.

Pending Ids. When changes are made to component module records, the changes are recorded on a log (Tracer) table. The Pending Changes screen in the component module and the Pending Changes screen in the reference module summarize the changes that have been made using the DCD. From this screen the user can mark the rows that are intended for Close-Out and perform a full or partial close-out of the id records. This screen also has an Undo function so changes can be undone on an Id basis.

Creating a New DCD. To create a DCD for tracking changes on the database:

1.Select the Tools; Add New DCD options from the main PDMS window menus.

2.Fill in all of the required data fields and save the changes.

If you wish to make changes to component or reference module data that is pertinent to this DCD, return to the User Preferences screen and link yourself to the new DCD.

Design Change Document (DCD): Functions

Copy. The DCD Copy function is used to copy one DCD to another DCD. The records associated with the DCD are not copied. To move records from one DCD to another, use the Move DCD function.

Delete. The DCD Delete function is used to delete a DCD and "Undo" all of the DCD’s changes. This function should be used carefully and only authorized users should be allowed access to it. If a DCD has progressed to "Released" status, only a superuser can Delete the DCD. All child DCDs must be deleted before a parent DCD can be deleted.

Move. The DCD Move DCD function is used to move all of a DCD’s Ids to another DCD. The target DCD must be defined before the move process can commence. The target DCD must be at a status less than or equal to the source DCD. At the end of the move process, the source DCD is disassociated from its records. Specific Ids in a parent DCD can be moved to a child DCD by marking the Ids on the component module Results screen and using the Chg DCD function.

Close-Out. The DCD Close-Out function controls additions, modifications, and deletions of approved designs to the As-Built database. Before a DCD can be "Closed-Out" 1) all problems associated with the DCD’s Ids record must be either corrected or overridden, and 2) it’s installation cards must be at Card Checked (CC) status. Id’s linked to the DCD that have no cards and problems will be closed out. If a DCD is closed out, and Ids are remaining because of problem or card issues, the status of the DCD becomes "Partial Close Out".

Design Change Document (DCD): Field Definitions

The Parent field is used to specify the parent of a child DCD. If a DCD is a parent DCD, the Parent data field is the same as the DCD data field. Parent DCDs must be defined before child DCDs are defined.

The DCD field is the name of the DCD.

The Description field is used to describe the DCD.

The Project field is used to specify which projects or renovations the DCD is linked to.

The Department field is used to specify which department has lead responsibility for the DCD.

The Status field defines the status of the DCD and if the DCD is editable or NOT editable.

History (DCD). The History (DCD) screen displays a DCD’s status history in chronological descending order.

Pending Details. When changes are made to reference module records, the changes are recorded on log (Tracer) tables. The Pending Details screen summarizes the reference module changes that have been made using the DCD. From this screen the user can mark the rows that are intended for Close-Out and perform a full or partial close-out of the detail records.

Pending Cards. When changes are made to component module records, installation cards are generated and transactions regarding these cards are recorded on log (Tracer) tables. The Pending Cards screen summarizes the changes that are pending for the DCD. From this screen the user can perform feedback for cards and indicate whether the card is at Check / Card Completed status.

Pending Ids. When changes are made to component module records, the changes are recorded on a log (Tracer) table. The Pending Changes screen in the component module and the Pending Changes screen in the reference module summarize the changes that have been made using the DCD. From this screen the user can mark the rows that are intended for Close-Out and perform a full or partial close-out of the Id records. This screen also has an Undo function so changes can be undone on an Id basis.

Design Change Document (DCD): Add a DCD

To create a DCD for tracking changes on the database:

1.Select the Add option from the main PDMS window menu then select Add DCD.

2.Fill in all of the required data fields and save the changes.

[Note]Note

If you wish to make changes to component or reference module data that is pertinent to this DCD, return to the User Preferences screen and link yourself to the new DCD. All changes occur within the user's associated DCD. Be sure to check you DCD before beginning design changes.

DCD Details

When changes are made to reference module records, the changes are recorded on log (tracer) tables. The Pending Details screen summarizes the Reference module changes that have been made using the DCD. From this screen the user can mark the rows that are intended for close-out and perform a full or partial close-out of the detail records.

Figure 5.14. DCD Details

DCD Details

Data Fields

DCD Type. Displays the type of Design Change Document (DCD).

DCD. Design Change Document (DCD) association.

Parent. Displays the parent DCD.

Project. Displays the associated project.

Description. Summary description of the DCD.

Lead Department. Departmental association.

Status. Displays DCD status.

Date / Time. Date and time record is created.

Revised By. Displays the name of the person who last revised the record.

DCD Status radio buttons

Parent. Selects only parent DCDs.

Active. Selects only active DCDs.

Editable. Selects only editable DCDs.

/*Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

DCD Problems

This screen displays the system-generated problems. Each Problem is associated with an Id that has been altered by that DCD. All Problems must be resolved or overridden before the DCD can be closed out.

Figure 5.15. DCD Problems

The PDMS DCD Problems screen

Pending Details

When changes are made to reference module records, the changes are recorded on log (tracer) tables. The Pending Details screen summarizes the reference module changes that have been made using the DCD. From this screen the user can mark the rows that are intended for close-out and perform a full or partial close-out of the detail records.

Figure 5.16. DCD Pending Details

The PDMS DCD Pending Details screen

Data Fields

DCD Type. Displays the type of Design Change Document (DCD).

Parent. Displays the parent DCD.

Project. Displays the associated project.

Description. Summary description of the DCD.

Lead Department. Each DCD is linked to a single department. Only users that are in the department may use the DCD to make changes on the database.

Status. Displays DCD status.

Date / Time. Displays the date and time the record was created.

Revised By. Displays the name of the person who last revised the record.

Database. Displays the associated database.

DCD Status Radio Buttons

Parent. Show only parent DCDs.

Active. Show only active DCDs.

Editable. Show only editable DCDs.

/*Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Pending IDs

When changes are made to component module records, the changes are recorded on a log (tracer) table. The Pending Changes screen in the Component module and the Pending Changes screen in the Reference module summarize the changes that have been made using the DCD. From this screen the user can mark the rows that are intended for Close-Out and perform a full or partial close-out of the ID records. This screen also has an Undo function so changes can be undone on an Id basis.

Figure 5.17. Document Search

Document Search

Data Columns

Row Numbering. Row numbers for current screen.

DCD. Indicates Design Change Document (DCD) by name.

Type. Indicates document type.

Card No. Indicates card number.

Reqd. Checkmark indicates "required".

Card Status. Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

Workorder. Summary description of workorder.

/*Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

DCD Pending Cards

This DCD module screen itemizes the installation cards associated with the component Ids that are linked to the Design Change Document (DCD).

Statistics

Displays DCD-related statistics. This includes a count of Commodities at certain statuses within their given unit.

Figure 5.18. DCD Statistics

DCD Statistics

Data Fields

DCD Type. Displays the type of Design Change Document (DCD).

DCD. Design Change Document (DCD) association.

Parent. Displays the parent DCD.

Project. Displays the associated project.

Description. Summary description of the DCD.

Lead Department. Departmental association.

Status. Displays DCD status.

Date / Time. Date and time record is created.

Revised By. Displays the name of the person who last revised the record.

DCD Status radio buttons

Parent. Selects only parent DCDs.

Active. Selects only active DCDs.

Editable. Selects only editable DCDs.

/*Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

DCD History

The History (DCD) screen displays a DCD’s status history in chronological descending order.

Figure 5.19. DCD History

DCD History

Data Fields

DCD Type. Displays the type of Design Change Document (DCD).

DCD. Design Change Document (DCD) association.

Parent. Displays the parent DCD.

Project. Displays the associated project.

Description. Summary description of the DCD.

Lead Department. Departmental association.

Status. Displays DCD status.

Date / Time. Date and time record is created.

Revised By. Displays the name of the person who last revised the record.

DCD Status radio buttons

Parent. Selects only parent DCDs.

Active. Selects only active DCDs.

Editable. Selects only editable DCDs.

/*Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

DCD Selection screen

The DCD Selection screens allow the user to specify which DCD or group of DCDs they are interested in. The result of each selection is presented on the DCD Results screen.

Figure 5.20. DCD Search

DCD Search

Data Fields

DCD. Specify a desired DCD.

Parent. Specify a DCD parent.

Project. Specify an associated project.

User. Specify an associated PDMS user.

Department. Specify an associated department.

From - Through Dates

From field. Specify selection begin date.

Dates button. Opens Date Range for DCD date functions window. Specifications include:

Month to Date, Last Month, Same Month Last Year, Last Year, Last 3 Years, Last 5 Years, Fiscal Quarter to Date, Last Fiscal Quarter, Same Fiscal Quarter Last Year,

Fiscal Year to Date, Last Fiscal Year, Last Fiscal Year to Date.

Through field. Specify selection end date.

Radio Buttons

Active Status. Specify active DCDs.

Closed Status. Specify closed DCDs.

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

DCD Search Results

The DCD Results screen provides a list of selected DCDs and their statuses. From this list the user can add new DCDs, change DCD statuses, and drill down for more specific DCD information. From this screen the user can Advance, Release, Demote, or Delete a DCD.

Figure 5.21. DCD Search Results

DCD Search Results

Data columns

Row Numbering. Row numbers for current screen.

Selection box. For selecting line-items of data.

DCD. Indicates Design Change Document (DCD) by name.

Parent. Indicates the parent DCD, if any.

Status. Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

Edit. Checkmark indicates editable DCD.

Description. Capsule description of the DCD.

/*Open. Opens the selected row(s) of data.

Close. Closes the selected row(s) of data.

New. Creates a new line-item of data.

Copy. Copies the selected row(s) of data.

Advance. Advances the selected DCD(s).

Release. Releases the selected DCD(s).

Demote. Demotes the selected DCD(s).

Renumber. Renumbers the selected row(s) of data.

Analyze. When the user marks rows of data on the Component Results screen and depresses this button, the records are analyzed either on-line or they are posted to the background process so the user's terminal is not tied up during the analysis process.

Delete. Deletes the selected row(s) of data.

ECF

Reference

Reference Detail Overview

Reference Library Detail Records

Reference Library detail records are used to define detail elements such as cable types, raceway types, voltage levels, and separation groups. Each reference detail is stored in the Reference module.

Reference Selections

The Reference Selection screens allow the user to specify which detail or group of details they are interested in. The result of each selection is presented on the Reference Results screen.

Reference Search Results

The Reference Results screen provides a list of selected details and their statuses. From this list the user can add new details, modify existing details, and drill down for more specific detail information.

Pending Changes

When changes are made to reference module records, the changes are recorded on a log table. The Pending Changes screen in the reference module summarizes the changes that have been made using DCDs.

Description/Remark

The Description/Remark screen is used to revise the description of the detail and to add a remark to the detail.

Component IDs

The Component IDs screen displays all Components that are linked to a Reference Detail. This is a very useful data navigation screen, as it allows the user to double-click and drill-down to any Component ID in the list.

Statistics

The Statistics screen summarizes how many records on the database use the detail.

Quantity Details

The Quantity Details screen describes the estimated, procured, and installed quantities that are associated with the item.

Purchase Details

The Purchase Details screen itemizes the procurement information such as Manufacturer, Model Number, Purchase Order/Item, and Specification that is associated with the item.

History

The History screen summarizes which Design Change Documents (DCDs) have altered the record in the past.

Creating a New Reference Detail

Procedure 5.1. Creating a New Reference Detail

To create a Detail on the database:

  1. Select the Tools, Add Detail option from the main PDMS Add menu.

  2. Enter the appropriate Unit, Detail Type, Detail Value, and Description for the detail. Depress the Save button.

  3. From the Reference Results screen, if appropriate, go to the special screens associated with the type of detail and append additional data about the detail.

  4. Save the data and exit the screen.

Deleting an Existing Detail

To delete a Detail on the database:

  1. From the Reference Results screen, point to the appropriate detail and review the Statistics about the detail. If the detail is linked to any Ids, the detail cannot be deleted. You must first edit the ids that refer to the detail. Use the component module Details screen to perform these delete transactions.

  2. From the Reference Results screen, point to the appropriate detail and depress the Delete button. If it is a "New Detail" and no ids are referring to the detail, the detail will be deleted from the database. If it is an "As Built" detail it will be "Scheduled for Deletion" and the DCD module Close Out process will remove it.

Modifying an Existing Detail

To modify a Detail on the database:

  1. From the Reference Results screen, point to the appropriate detail and go to the appropriate Description/Remark or other screen to modify technical data about the record. The status of the detail will change from "As Built" to "Modified". When the DCD associated with the modification is "Closed Out" the as built version of the detail will be replaced by the modified version of the detail.

Cable Type Details

CT Details (1)

Provides the procurement details for cable types.

Fields

Specification.

Purchase Order.

Manufacturer.

Q. Quality Assurance attribute.

Remark.

Buttons

Insert. Inserts row for data entry

Delete. Deletes selected row of data.

Synch. Synchronizes As Built and In Design data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

CT Details (2)

Provides more descriptive details for cable types.

Fields

Rating.

Conductor Material (Basis / Manufacturer).

Jacket.

Insulation.

Shield.

Configuration.

Conductors: Live & Total. Number of conductors

Triplexed.

4/0 or Larger.

Remark.

Buttons

Insert. Inserts row for data entry

Delete. Deletes selected row of data.

Synch. Synchronizes As Built and In Design data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

CT Details (3)

Provides the technical details for cable types.

Fields

Standard.

Diameter (C) (Basis / Manufacturer).

Conductor (C) (Basis / Manufacturer).

Diameter (in) (Basis / Manufacturer). Diameter in inches

Area (sq in) (Basis / Manufacturer). Area in square inches

Alarm Length (ft).

Tray Amps.

Conduit Amps.

Duct Amps.

AC/DC.

BTU/lb. BTUs generated by one foot.

Comb lb/ft.

Total lb/ft.

Remarks.

Buttons

Insert. Inserts row for data entry

Delete. Deletes selected row of data.

Synch. Synchronizes As Built and In Design data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

CT Details (4)

Provides the pulling tension details for cable types.

As Built Fields

Side Wall. [need definition]

Friction. [need definition]

Training Radius. [need definition]

Pull Radius. [need definition]

Pull Eye Tension. [need definition]

Basket Weave Tension. [need definition]

Remark. [need definition]

In Design Fields

Side Wall. [need definition]

Friction. [need definition]

Training Radius. [need definition]

Pull Radius. [need definition]

Pull Eye Tension. [need definition]

Basket Weave Tension. [need definition]

Remark. [need definition]

Buttons

Insert. Inserts row for data entry

Delete. Deletes selected row of data.

Synch. Synchronizes As Built and In Design data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

CT Color Codes

This reference module screen defines the valid color code sequence that is associated with a cable mark number. This entry is used by PDMS for auto-population of a compatible color code if the customer preference INFER CCCOMPAT is set to Y (Yes). If a color code is associated with a cable or jumper, and the color code has not been listed among the color codes that are compatible with the cable mark number, then a problem will be generated for the Component ID.

CT-VL Compatible

Defines the voltage levels that are compatible with cable types.

Figure 5.22. Cable Type - Voltage Level Compatibility

Cable Type - Voltage Level Compatibility

Data Columns

Row Numbering. Row numbers for current screen.

Voltage Level. Identifies voltage level.

Unit. Identifies unit.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user's DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

CT-SG Compatible

Defines the separation groups that are compatible with cable types.

Figure 5.23. Cable Type - Separation Group Compatibility

Cable Type - Separation Group Compatibility

Data Columns

Row Numbering. Row numbers for current screen.

Separation Group. Identifies separation group.

Unit. Identifies unit.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

CC Colors

This reference module screen defines the sequence of colors that are associated with a "Color Code".

Raceway Type Details

RT Details (1)

This reference module screen provides the procurement details for "Raceway Types".

RT Details (2)

This reference module screen provides the descriptive details for "Raceway Types".

RT Details (3)

This reference module screen provides the technical details for "Raceway Types".

RT-RW Compatibles

This reference module screen defines the valid raceway commodities that can be linked to each "Raceway Type".

RT Watts (ICEA)

This reference module screen defines the allowable watts/foot for each "Raceway Type" for each value of percent fill.

Extended Details

Extended Details

The Extended Detail Model uses Detail Types as a basis and "extends" the information known about that specific Detail. The Process Begins in the Configuration Module where the user can define the columns needed to track the additional data.

There are 4 steps one must take to begin Tracking Data

  1. Define custom columns in the Column Definition Table in the Configuration Module.

  2. Associate Columns to a detail in the Reference Module.

  3. Add the Detail to the Details screen for a component.

  4. Add the Data to the Details(2) screen.

Column Association

Once the Columns are defined, they can be associated with a Detail. Any detail in the Reference Module can be used.

By going to the Column List screen for a specific Detail, the custom defined Columns from the Configuration module can be added to the Detail. There are several Attributes that can be set:

Minimum. If the user chooses, this column can be specified as a required value. Analysis will d\post a problem if the column is null.

Print. Should this column be included in a report.

Auth Display. Specifies the level a user must be to view the data in this column.

Auth Update. Specifies the level a user must be to update the data in this column.

Default Value. A default value for the column that is left null.

Extended Detail Data ( Details(2) )

There are columns associated with some details that allow for the tracking of additional data. In the Details(2) screen data can be added to any component described with the given detail. The validation of the data occurs according to the definition of the specific column.

The data added or deleted via the Details(2) screen is tracked by DCD process.

Column Association

Once the Columns are defined, they can be associated with a Detail. Any detail in the Reference Module can be used.

By going to the Column List screen for a specific Detail, the custom defined Columns from the Configuration module can be added to the Detail. There are several Attribues that can be set:

Minimum. If the user chooses, this column can be specified as a required value. Analysis will d\post a problem if the column is null.

Print. Should this column be included in a report.

Auth Display. Specifies the level a user must be to view the data in this column.

Auth Update. Specifies the level a user must be to update the data in this column.

Default Value. A default value for the column that is left null.

Reference Detail Selection

This screen allows the user to select reference details by unit, detail type, value or detail and description of the detail type.

Figure 5.24. Reference Search

Reference Search

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

List of Records

This selection screen allows the user to select a list of reference details from an external file. The file must have been exported and saved by PDMS.

Figure 5.25. Reference Search (File of Records)

Reference Search (File of Records)

DCDs

Allows selection of Reference Detail records by Design Change Document (DCD) selection criteria. By entering selection criteria in some or all of the data fields, users can focus on one or many detail records.

Figure 5.26. Reference Search (DCD)

Reference Search (DCD)

Fields

DCD. Design Change Document (DCD) association.

Parent. Displays the parent DCD.

Project. Displays the associated project.

User. Displays the associated user.

Department. Departmental association.

From-Through Selection

Selects the appropriate from-through date with field scroll buttons and a calendar utility.

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Reference Search Results

Provides a list of selected details and their statuses. The user can add new details, modify existing details, and drill down (by double-clicking) for more specific information about each detail.

Figure 5.27. Reference Search Results

Reference Search Results

Data columns

Row Numbering. Row numbers for current screen.

Selection box ?. This box can be checked / unchecked using the click, shift-click, and control-click features of the mouse.

Detail Type. Indicates the type of detail record.

Detail. Indicates the name of the detail.

Status. Indicates the status of the detail.

Edit. Checkmark indicates an editable detail.

Description. Description of the detail.

Function Buttons

Open. Opens the selected line-item of data (same as double-click).

Close. Closes the screen and returns to the appropriate Reference Module selection screen.

New. Creates a new detail.

Copy. Copies the highlighted detail to another detail named by the user.

Delete. Deletes the detail.

Sort. Opens Select Sort Order window and sorts results according to specified sort columns.

Filter. Opens Filter window and filters results according to specified filter criteria.

Save List. Provides the user with the ability to save marked (checked) rows to an ASCII text file. The file can later be used to re-select the details.

Classify. Opens the Class Maintenance window and allows the user to create a classification of the marked (checked) rows, or append the rows to an existing classification.

Save Sort. If the default sort sequence of this Results screen is not appropriate for the user, the user may change the sort criteria using the Sort function button (above), and then save the new criteria using the Save Sort function button. The next time the user goes to this screen, his personal sort criteria will be used to sort the data rows.

Component

Component IDs

Component Overview

Component Ids

The component module manages equipment, instrument, valve, tray, conduit, cable, penetration seal, fire area, and other commodity data. Virtually any type of commodity can be tracked from within the PDMS component module.

Component Selections

The Component Selection screens allow the user to specify which component id or group of ids they are interested in. The result of each selection is presented on the Component Results screen.

Component Results

The Component Results screen provides a list of selected ids and their statuses. From this list the user can add new ids, copy existing ids, spare ids, and delete ids from the database.

Data Screens

There are numerous data screens in PDMS that display and manage the details about component ids. Please refer to the Help system for more specific information.

Pending Changes

When changes are made to component module records, the changes are recorded on log tables. The Pending Changes screen in the component module and the Pending Changes screen in the reference module summarize the changes that have been made using the DCD.

Creating a New Id

To create a new id for tracking changes on the database:

  1. Select the Add Id option from the main PDMS Add menu and select the appropriate commodity.

  2. Enter the appropriate data on the add screen.

  3. Save the data and exit the screen.

Functions

Auto Add / Delete

The Auto Add Delete Capability allows the user to automatically populate details, notes, and other items to all selected Ids. The process is as follows:

  1. Select the list of Ids you want to populate with the same value.

  2. Click on the Add/Delete button on the Selection Results screen.

  3. You will be prompted to confirm the fact that this is the "Mode" you want to use.

  4. Click "O.K.".

  5. Go to the detail screen of the highlighted Id by double clicking on that Id.

  6. Choose the detail and insert the value.

  7. Click "Save".

  8. Confirm the message that states that the values will be populated to the remainder of the marked Ids.

[Caution]Caution

You must be associated with an Editable DCD in order to use this function.

Auto Routing

Auto Routing is designed to provide options for the routing of a cable through as many routing iterations as selected. An Iteration is one layer, or route point, coming from each end point of the routing. The default value for the iterations of a given routing is five, meaning, that up to 9 route points may be returned (5 iterations includes the From or To end of the cable, and the middle routing would be the same.).

Figure 5.28. Auto-Routing Criteria

Auto-Routing Criteria

This pop-up selection screen allows for parameters to be specified for the routing of the cable.

Selection Criteria:

Voltage Level Compatibility: Checking this box ensures that the voltage level of all route points used will comply with that of the cable being routed.

Separation Group Compatibility: Checking this box ensures that the separation group of all route points used will comply with that of the cable being routed.

Exclude Blocked Raceways: Checking this box will allow raceways which are blocked from further routings to be used in the result set for the auto routing of the cable.

Exclude Overfilled Raceways: Checking this box will allow raceways which are overfilled to be used in the result set for the auto routing of the cable.

Iterations: Specifies the number of route points coming towards each other from both ends of the routing.

**When a path is chosen, the route points are inserted into the routing screen at the point of the highlighted row.

The Select button chooses all the route points in the "selected" path. The user can choose any number of route points from any of the paths. Validation will occur once the route points are chosen.

Copy Function

The Copy function does precisely what it implies, it copies an Id, it's attributes and details. The Id must be given an alternate Id, and usually the description should be altered as well. Any other changes must be made on an Id basis after the Id has been successfully copied.

Renumber Function

The Renumber Function is used to change a components Id, and description if desired. The Status of the Id will be changed to "Pending Renumber To" and the new Id will remain at status "Pending Renumber From" until the DCD is closed out. After the DCD is closed out the status of the New Id will acquire the status of the old Id (assuming no other modifications were made), and the old Id will be saved as a "Renumbered Id".

Data Screens

Alias / Id

The Alias / Id screen allows the user to link multiple Aliases, or ways to refer to a Component ID, to a single Component. If an external system at the site has a different reference for a Component, then that external reference can be entered here and the PDMS search screen will use the alias an another way to find the Component ID. This option is extremely useful if data will be exchanged with external systems, or if there are new users that are familiar with naming conventions used in an external system. The ID Alias type is permanent, and may not be edited. An example of an Alias Type is TPNS. The alias value, then, would be the TPNS equivalent for a Component ID in PDMS. Alias Types must be created in the Configuration module before they can be used for data entry in PDMS.

Figure 5.29. Component Alias

Component Alias

Data Columns

Row Numbering. Row numbers for current screen.

Alias Type. The Alias Type is defined in the Configuration Module and refers to What the Alias represents. One example could refer to an older naming scheme from a former system or from a Manufacturer.

Alias. How the Id could also be referred to.

Perm. Is this alias a permanent value that can not be removed? If so, be sure to check the box.

Buttons

Insert. Inserts an Alias.

Delete. Deletes a selected Alias.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected Alias’ record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the data from the Alias screen.

Preview…. Previews print jobs for selected Alias records.

Save As…. Saves the selected screen of data to a file.

Allowable

This screen is used to store "Allowable" values that are pertinent to a component Id. For example, a conduit may have a default allowable percent fill based on a table of default allowable fills. When it is appropriate to override an allowable value, this screen is also used to store the override value. PDMS uses the Allowable value that has been set for a Component in order to determine if a Problem Condition exists, where appropriate. Examples of this relationship include:

  1. Allowable Fill (for Raceway Fill analysis)

  2. Allowable Weight (for Raceway Weight analysis)

  3. Allowable Length (for Cable Length analysis)

  4. Allowable BTU (for Fire Zone BTU / Fire Severity analysis)

  5. And others…(see Analysis for more information)

Figure 5.30. Component Allowable

Component Allowable

Data Columns

Row Numbering. Row numbers for the visible data

Allowable. Allowable identification.

Allowable Type. Indicates allowable type.

Reference. Reference Id.

Perm. Some detail values such as voltage level, system, and separation group are imbedded in a component’s Id. These are classified as "permanent" details because they should not be deleted from the details screen without renumbering the Id. Some types of aliases and quantities are also classified as permanent because they are key values needed for proper operation of the system.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Blocks

This component module screen associates Ids with "Block" types such as overfill block, or weight/foot block, etc.

Cable Reels

This component module screen associates cables with the cable reels used to supply the cable material.

Extended Detail Data ( Details(2) )

There are columns associated with some details that allow for the tracking of additional data. In the Details(2) screen data can be added to any component described with the given detail. The validation of the data occurs according to the definition of the specific column.

The data added or deleted via the Details(2) screen is tracked by DCD process.

Combustible Load

This component module screen itemizes and summarizes the combustible materials that are associated with a room, fire zone, or fire area. Included in the summary are the Combustible Materials associated with the area and the amount of cable material that is routed through the room, zone, or area.

Comments

This topic is in development.

Figure 5.31. Component Comments

Component Comments

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Covers

This component module screen displays the types of covers that are on a raceway. The values include TOP, BOTTOM, or BOTH. The presence of Tray covers can influence the weight calculation for a tray. The Raceway Mark Number has an optional "Tray Cover Weight/ft" field that is used to add additional weight during the raceway weight calculation. If the value entered on the Cover screen is either BOTTOM or TOP, then the cover weight per foot is added to the overall weight calculation for the tray. If a value of BOTH is found then the value is doubled, and then added to the overall raceway weight figure.

Devices

This component module screen associates a component Id with its appropriate devices. Devices include such things as a Terminal Block, Ground, Tape, or other device that is referred to in PDMS (e.g. Terminations, SS Devices, etc.). Terminal Points are defined for a Terminal Block, so the Device must be entered before the Terminal Points can be defined.

The relationship is Cable ID - Wire : Equipment ID - Device/Point.

Details

The Details screen is used to link Component IDs to Reference module details such as cable types, raceway types, voltage levels, separation groups, and other type of custom details. The data on this screen is entered first as a Detail Type (i.e. CT for Cable Type, RT for Raceway Type, ..) and then as a Detail Value (i.e. CT300). The combination would then be CT/CT300. After saving the data the PDMS system will display the description of the Reference Detail. The right mouse button will provide a valid list of Reference Details (linked to the Commodity Type of the Component ID) in the Detail Type column, and a list of valid values for the Type in the Detail Value column. A double-click on a row in the Details screen will open the Reference Detail module directly. This is referred to as a drill-down operation in PDMS.

Detail Types/Values that comprise any part of a Conforming Component ID pattern are marked as Permanent – they cannot be edited directly. They are altered when the Component ID is Renumbered, and will conform to the Plant Numbering scheme.

Figure 5.32. Component Details

Component Details

Data Columns

Row Numbering. Row numbers for current screen.

Detail Type. Indicates document type.

Detail. Detail identification.

Description. Description of the DCD.

Perm. Some detail values such as voltage level, system, and separation group are imbedded in a component's Id. These are classified as "permanent" details because they should not be deleted from the details screen without renumbering the Id. Some types of aliases and quantities are also classified as permanent because they are key values needed for proper operation of the system.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Extended Detail Data ( Details(2) )

There are columns associated with some details that allow for the tracking of additional data. In the Details(2) screen data can be added to any component described with the given detail. The validation of the data occurs according to the definition of the specific column.

The data added or deleted via the Details(2) screen is tracked by DCD process.

Dimensions

This component module screen associates a room, fire zone, or fire area with its appropriate dimensions. The dimension (area in square feet) is used to calculate the Fire Severity for a Room, Fire Zone, or Fire Area. It is also used to post problems where a Fire Zone has exceeded its allowable value for BTUs/sqft.

Docs / Images

This screen provides a list of Documents and Images that are linked to a Component ID. The data is organized by Document Type (e.g. WIRING DIAGRAM) and Document, which is a value that must exist in the Document module. An optional list of Sheet Numbers can be provided. If a server location and file name, or a link to an external document system, are in place the system can automatically launch the document or image and pull it up for review by the user. The user can drill-down to the Document module by double-clicking on an entry in this screen.

Figure 5.33. Component Docs / Images

Component Docs / Images

Data Columns

Document. The drawing number. It must exist in the Document module.

Sheet. An optional list of sheet numbers where the Component ID is referenced in the Drawing. This list of sheet numbers will either be automatically created, or will be verified against a list of valid sheets, depending upon the customer preferences selected by the system administrator for this site..

FM/TO. Certain drawings have an implied From/To relationship, such as Wiring Diagrams. This field allows the user to designate which end of a cable the drawing addresses.

Document Type. The Document Type of the Drawing listed. The default document type can be overridden, if necessary. This value is defaulted, however, from the default document type value that is listed for this drawing in the Document module.

Coordinate. The coordinate on the drawing/sheet where the Component can be located.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes selected row(s) of data.

View. When a Filename is present the system retrieves that file and launches the application that has been associated with the document type (or externsion). If a link to an external document management system is enabled, then PDMS will retrieve the content from the external system for review by the user.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Fuse Data

This component module screen associates an Id with its appropriate fuses.

History (Cards)

This screen displays the installation cards that are/have been associated with the component Id.

Figure 5.34. Component History (Installation Cards)


Data Columns

Timestamp. Date and time of data record creation or modification.

DCD. Indicates Design Change Document (DCD) by name.

Card Number data column. Associated card number.

Type. Indicates document type.

Status. Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

Workorder. Summary description of workorder.

WBS FIELD. WORK BREAKDOWN STRUCTURE [need definition]

RE. [need definition]

Remark. Remarks.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user's DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OKCloses the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

History (Renumber)

This screen displays the old Id for the current Id if it has been renumbered.

Data Columns

Unit. Unit identification.

CT. Commodity Type. (Also an abbreviation for Cable Types.)

Former Id. Old Id.

Sub Id. When an equipment Id is subdivided into smaller entities such as cubicles, breakers, or subcabinets, the Sub Id can be used to specify the entity.

Status. Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user's DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

History (Revisions)

This screen displays in descending chronological order the DCD closeout history for the Id.

Figure 5.35. Component History

Component History

Data Columns

Date/Time. Captures date and time data record is created or updated.

DCD. Indicates Design Change Document (DCD) by name.

Remark. Remarks.

Re. [need definition]

Checker. Name of data record checker.

Approver. Name of data record approver.

Rev. Summary description of revision.

Rev Date. Date of revision.

Work Order. Associated work order.

WBS FIELD. WORK BREAKDOWN STRUCTURE This "Work Breakdown Structure" data column is used to specify the WBS (if any) for installation cards.

Status. Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user's DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Instrument Data

This component module screen associates the Id with its appropriate instrument setpoint and other technical data.

IO Point Data

This component module screen associates an Id with its appropriate computer IO point description and details.

IO Point Signals

This component module screen associates an Id with its appropriate computer IO point description and details.

Links (Continuity)

This component module screen associates an Id with other related Ids. The linked Ids form the basis for valid cable routings.

Links (Supports)

This component module screen associates a raceway Id with its appropriate hanger supports.

Load Data

This component module screen associates a cable with the data that characterizes its electrical load.

Locks

This component module screen is used to lock Ids so no further changes can be made against them. The screen also itemizes what types of locks exist for the Ids.

Notes

The Notes screen is used to store information and comments about a PDMS component Id. The System Administrator defines what types of notes are valid for each PDMS commodity, and also designates whether or not the note type is a minimum or disposable note type. Note Types are referred to by the PDMS when note text is to be displayed on a screen or report, as in the case of Installation Notes (Type C1). The C1, or construction note, is displayed on Cable Pull cards and Raceway cards. A F1 or T1 note will be displayed on a From or To termination card.

Figure 5.36. Component Notes

Component Notes

Data Columns

Row Numbering. Row numbers for current screen.

Note Type. Indicates document type.

Seq. This column displays the numerical sort sequence for the data on the screen.

Note. The note! (up to 100 Characters)

Min. Some types of details, notes, and quantities are classified as "Minimum" details, notes, and quantities. For example, as a minimum, every cable should have a cable type detail. When the Min data column contains a check mark, the entity is a minimum entity.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Pending Cards

Figure 5.37. Pending Cards

Pending Cards

Data Columns

Selection Box ?. This box can be checked / unchecked using the click, shift-click, and control-click features of the mouse.

DCD. Identifies associated DCD.

Type. Identifies card type.

Card No. Identifies card number.

Reqd. Indicates that the selected card is required.

Card Status. Identifies card status.

Workorder. [need definition]

Buttons

Refresh. Refreshes line items of data.

Check. Checks selected pending change and records the user name in the Checker data column.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Pending Changes

When a DCD is used to make a change to a component Id, the transaction is recorded on a table. The Pending Changes screen displays which DCDs have modified a record. All Pending Changes will list the Responsible Engineer, DCD, and Table/Screen that the changes are based upon in PDMS. It is possible to configure PDMS to insist that all Pending Changes have been checked by an independent reviewer before they can be advanced and approved.

Figure 5.38. Component Pending Changes

Component Pending Changes

Data Columns

Selection Box ?. This box can be checked / unchecked using the click, shift-click, and control-click features of the mouse.

Date / Time. Captures date and time of the pending change.

DCD. Identifies associated DCD.

Screen. Identifies screen for pending change.

Last Name. Identifies user responsible for pending change.

Action. Identifies an action, usually New or Deleted.

Checker. Identifies user who ‘checked’ the transaction for pending change.

Approval. Identifies user who ‘approved’ the transaction for pending change.

Buttons

Refresh. Refreshes line items of data.

Check. Checks selected pending change and records the user name in the Checker data column.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Problems

The Problem Screen reflects Problems that are posted due to conditions set in the Configuration module; for example missing data may be considered a "Minimum" for that component, and thus a problem is posted. Each Problem has a type, value and reason. Problem types can either originate from a missing Reference detail or the Analysis Process which determines that a value falls outside the Allowable range for the component, given its details and the current system configuration. When problems are posted for an exceptional Circumstance, the can be Overridden.

Figure 5.39. Component Problems

Component Problems

Data Columns

Row Numbering. Row numbers for current screen.

Selection Box ?. This box can be checked / unchecked using the click, shift-click, and control-click features of the mouse.

OR. When this box is checked, an "override" exists for the problem. Go to the Problem Override screen to see the override. Overrides provide justification for the existence of a given problem.

PT. The Problem Type defines the origin of the problem such as

Problem. Describes the type of problem.

Value.

Reason. The reason for the problem.

Reference Id. The Id to which the current component is linked and in conflict. Voltage Level, Separation Group and certain links are examples where this conflict can occur.

Analyze Date. Indicates the timestamp of the analysis, or when the problem was posted.

Val Id. Indicates the validity of the Id.

Buttons / Checkbox

Refresh. Refreshes the Current list of problems (Analysis must be running)

Override. Allows the user to "justify" or override the highlighted problem.

Hide As Built Problems. Displays In-Design problems only.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Problem Overrides

The Problem Overrides screen displays the manual overrides that have been entered to override system-generated problems. The overrides are related to a DCD, and will become As Built problem overrides when the DCD / Component changes are closed out and made final.

Figure 5.40. Component Problem Overrides

Component Problem Overrides

Data Columns

Override Description. Description of the override.

Override DCD. Indicates Design Change Document (DCD) by name.

ProbType. Indicates problem type.

Problem. Indicates the nature of the problem.

Value. Value.

Analyze Date. Date when Analysis posted the problem.

Val Id. Indicates the validity of the Id.

Reference Id. [need definition].

Buttons

Insert. Inserts a detail.

Delete. Deletes a selected detail.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Quantities

This screen displays the quantities and types of quantities that are linked to a Component Id. A quantity is entered as a General Type (e.g. LENGTH) and an order of precedence (e.g. Estimate, System Calculated, Feedback, ..). the higher the order of precedence, the value accurate the value will be. PDMS uses the highest order of precedence for a quantity type when the user requests to report on a Component, or when the system is analyzing problem conditions. LENGTH Estimated may be 100, while the LENGTH Feedback may be 103. The 103 value is considered to be of greater value than 100 because it is based on an actual measurement in the plant. The 103 (Feedback) value will supersede the 100 (Estimated) value. Valid quantity types are defined and configured in the Configuration module by the System Administrator. Quantities that are marked as PERMANENT are based on the Reference Details linked to the Component ID, and are based upon values that can be found in the Reference Detail module (typically for a Cable Type or Raceway Type).

Figure 5.41. Component Quantities

Component Quantities

Data Columns

Row Numbering. Row numbers for current screen.

Quantity Type. Indicates document type.

Quantity. Quantity data.

Description. Capsule description of the DCD.

Perm. Some detail values such as voltage level, system, and separation group are imbedded in a component's Id. These are classified as "permanent" details because they should not be deleted from the details screen without renumbering the Id. Some types of aliases and quantities are also classified as permanent because they are key values needed for proper operation of the system.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Routing

This screen provides a sequential list of raceway route points for the cable. The top of the list is the "From" end of the cable and the bottom of the list is the "To" end of the cable. All route point entries are checked for the following properties:

  1. Continuity

  2. Separation Group Compatibility (optional)

  3. Voltage Level Compatibility (optional)

  4. Blocks (is the raceway physically blocked and unsuitable for further use?)

  5. Overfill (Is the Raceway already overfilled per Plant Design basis?)

Any changes to the Routing screen trigger a series of analyses in PDMS for both the cable and all route points. The Routing screen is truly the heart of the PDMS system, and its effects are far reaching. Changes to the Routing data will impact the Safe Shutdown analysis as well as the Ampacity and Voltage Drop calculations.

A Component ID can only be used as a route point if the Unit and Commodity Type are listed as a valid route type in the Configuration Module.

Figure 5.42. Component Routing

Component Routing

Data Columns

Unit. The unit for the commodity.

CT. Commodity Type.

Route Point. Route point Ids.

Sub Id. When a major equipment Id is subdivided into smaller entities such as cubicles or breakers the Sub Id can be used to specify the entity.

Fill. Indicates the fill percentage of the raceway that the cable is routed through.

# Cables. Indicates the number of cables routed through the raceway

Length. Displays the length of the route point as it is found on the Quantity screen.

Wrap Length. Displays the length of wrap as it is found on the Wrap screen.

Block. Indicates presence and number of raceway blocks. (No more cables can be routed through it.)

Cover. Indicates position of cover raceway cover (top or bottom).

SG. The Separation Group for the route point.

VL. The Voltage (or Service) Level for the route point.

Seq(uence). Indicates route sequence. (From end = 1, To end = 9999)

Fields

From Description. Displays the description of the "From" Id as found on the Description screen.

To Description. Displays the description of the "To" Id as found on the Description screen.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes selected row(s) of data.

Analyze. When the user marks rows of data on the Component Results screen and depresses this button, the records are analyzed either on-line or they are posted to the background process so the user’s terminal is not tied up during the analysis process.

Auto Route. This feature enables a cable to be routed automatically from point A (route sequence 1) to point n (route sequence 9999).

Copy. Using the highlighted row as a starting point, the Copy function provides the ability to enter a cable Id that is already routed and it’s routing will be inserted into the current cable’s routing.

Link. Using the highlighted row as a starting point, the Link function will provide a screen of raceways that are linked to the Id on the highlighted row. The user can then select the next one or several route points that should be inserted into the cable’s routing.

Checkboxes

Analysis. When this box is checked (default), each time a route point is inserted, modified, or deleted, the routing analysis will analyze the entire routing for continuity problems. To turn this function off, uncheck the Analysis box.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Auto Routing

Auto Routing is designed to provide options for the routing of a cable through as many routing iterations as selected. An Iteration is one layer, or route point, coming from each end point of the routing. The default value for the iterations of a given routing is five, meaning, that up to 9 route points may be returned (5 iterations includes the From or To end of the cable, and the middle routing would be the same.).

This pop-up selection screen allows for parameters to be specified for the routing of the cable.

Selection Criteria:

Voltage Level Compatibility: Checking this box ensures that the voltage level of all route points used will comply with that of the cable being routed.

Separation Group Compatibility: Checking this box ensures that the separation group of all route points used will comply with that of the cable being routed.

Exclude Blocked Raceways: Checking this box will allow raceways which are blocked from further routings to be used in the result set for the auto routing of the cable.

Exclude Overfilled Raceways: Checking this box will allow raceways which are overfilled to be used in the result set for the auto routing of the cable.

Iterations: Specifies the number of route points coming towards each other from both ends of the routing.

**When a path is chosen, the route points are inserted into the routing screen at the point of the highlighted row.

The Select button chooses all the route points in the "selected" path. The user can choose any number of route points from any of the paths. Validation will occur once the route points are chosen.

Routing (Fire Area, Fire Zone, Room Number)

The Routing (FA/FZ/RN) screen provides a sequential list of fire areas, fire zones, and rooms that are linked to a cable’s raceway route points.

Data Columns

Row Numbering. Row numbers for current screen.

Unit. Unit identification.

CT. Commodity Type. Also an abbreviation for Cable Types.

Area/Zone/Room. This column displays the Areas, Zones, and/or Rooms that are linked to a cable’s route points.

Sub Id. When a major equipment Id is subdivided into smaller entities such as cubicles, breakers, or subcabinets, the Sub Id can be used to specify the entity.

Seq. This column displays the numerical sort sequence for the data on the screen.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes selected row(s) of data.

Radio Buttons

Fire Area. Filters for fire area-specific data.

Fire Zone. Filters for fire zone-specific data.

Room. Filters for room-specific data

All. Displays all data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Splices

The Splices screen Is used to track where cables are spliced.

Data Columns

Row Numbering. Row numbers for current screen.

Unit. Unit identification.

CT. Commodity Type. (Refers to a Raceway where the splice can be found)

Location. Room, Zone or Area.

Sub Id. When a major equipment Id is subdivided into smaller entities such as cubicles, breakers, or subcabinets, the Sub Id can be used to specify the entity.

Splice Kit. This column is used to specify the type of splice kit that was used to make the cable splice.

Splice Date. The Timestamp from the date the Splice was entered into PDMS.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected Cable’s Routing.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Summary

Displays a formatted, printable summary of the component details selected from the Component Results screen.

Figure 5.43. Component Summary

Component Summary

Summary Window

Displays a formatted, printable summary of component details selected from the Component Results screen.

Buttons

Insert. Disabled for this screen.

Delete. Disabled for this screen.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Terminal Points

This component module screen is used to define the valid terminal blocks and points that are contained in an instrument or equipment cabinet.

Terminations

The Terminations screen displays a cable's wires and the blocks and points that are associated with those wires.

Figure 5.44. Component Terminations

Component Terminations

Data Columns

Row Numbering. Row numbers for current screen.

FM Device. Devices such as Terminal Blocks, Relays, Circuit Breakers are usually associated with equipment Ids. The FM device is the device at the "From" end of the cable. See To Device for the other end of the cable. The FM device is the device at the "From" end of the cable. See To Device for the other end of the cable.

Point. The point data column defines the termination point that is used to terminate a cable.

FM Side. When a terminal block is the type of device, it can sometimes be terminated on the "Field" or "Vendor" or "Left" or "Right" side of the terminal block. This column specifies which side of the terminal block should be used.

TR. This "Termination Required" column, when checked, indicates that non-spare wires need to be terminated at this end of the cable.

Color. Wire color information.

Wire. Specifies the designation for each cable’s wire.

TO Device. Devices such as Terminal Blocks, Relays, Circuit Breakers are usually associated with equipment Ids.

Point. The point data column defines the termination point that is used to terminate a cable.

To Side. [need definition]

TR. [need definition]

Remarks (From). This data column is used to enter remarks that are pertinent to the termination at the "from" end of the cable.

Remarks (To). This column is used to enter remarks that are pertinent to the termination at the "to" end of the cable.

Fields

From:. [need definition]

To:. [need definition]

Checkboxes

No Termination Required. When the Termination Required box is checked, the non-spare wires for the cable must be linked to a device such as a terminal block.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Terminations (All)

This topic is in development.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Tools

The Tools screen displays the tools that may have been used to terminate or perform an operation on a component Id.

Data Columns

Location. Tool location.

Sub Id. When a major equipment Id is subdivided into smaller entities such as cubicles, breakers, or subcabinets, the Sub Id can be used to specify the entity.

Tool. Tool description.

Tool Id. Tool Ids.

Buttons

Insert. Inserts a row for data entry.

Delete. Deletes selected row(s) of data.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Wire Data

This topic is in development

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user's DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Wires

This component module screen is used to assign the appropriate wire number to each of a cable’s wires.

Wrap Data

This component module screen associates an Id with its appropriate type of fire wrap as well as the location and length of the wrap.

Component Selection Screens

Documents / Images Selection

Select Component data by an associated document or image.

Fields

Document. Document name.

Document Type. Document type.

Viewer. [definition]

Title. [definition]

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

File of Records

Allows selection of Component Module records by File of Records. If an ASCII text file of detail value records has been created, this selection tab provides the capability to select the records that are specified in the file.

Data Field and Button

File field. Specify file name containing known details.

Browse button. Browses directory tree to assist in locating an appropriate file of details.

File Counters

Read. Indicates number of details read for the file.

Found. Indicates number of details found on the database.

Rejected. Indicates number of details that were not found.

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Location

Select Component data by location. This screen associates an Id with its building, area, elevation, and Cartesian (X, Y & Z axis) coordinate information.

Fields

Unit. Unit identification.

CT. Cable type.

Area.

Building . Building identification

Elevation.

North/South.

East/West.

Description. Additional descriptive information explaining location.

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Safe Shutdown (SS)

Select Component data by safe shutdown criteria.

Fields

Id/Alias. The Id for which you need the SS information.

Unit. The Unit for which you need the SS information.

CT. The Commodity Type for which you need the SS information.

Status. The Status of the Ids for which you need the SS information.

Radio Buttons

Safe Shutdown, Associated, or Either. Ids which are SS, Associated to SS Ids or both.

As Built, In Design, or Either. Specifies the status of the Ids.

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

DCDs

Allows selection of Component Module records by Design Change Document (DCD) selection criteria. By entering selection criteria in some or all of the data fields, users can focus on one or many detail records.

Fields

DCD. Design Change Document (DCD) association.

Parent. Displays the parent DCD.

Project. Displays the associated project.

User. Displays the associated user.

Department. Departmental association.

From-Through Selection

Selects the appropriate from-through date with field scroll buttons and a calendar utility.

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Links

Selects Component data based on specified links criteria.

Fields

Component Id. Specify component Id selection criteria.

Unit. Specify unit selection criteria.

Commodity. Specify commodity selection criteria.

Radio Buttons

Continuity Links or Fire Area Links. Select for continuity links or fire area links data only.

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Routing / Incl Cables

Selects Component data based on specified cable and route point criteria.

Fields

Cable or Route Point. Specify cable or route point selection criteria.

Unit. Specify unit selection criteria.

Commodity. Specify commodity selection criteria.

Radio Buttons / Checkbox

Route Points or Included Cables radio buttons. Select for route point or included cable data only.

Safe Shutdown Only? checkbox. Selects for SS data only.

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Component Results

The Component Results screen is the second stage in the drill-down toward desired (filtered and sorted) component data records.

Figure 5.45. Component Search Results

Component Search Results

Data Columns

Row Numbering. Row numbers for current screen.

Checkbox. For selecting line-items of data.

Unit. Unit identification.

CT. Commodity Type. (Also an abbreviation for Cable Types.)

Id. Component Id / Number / Name

Sub Id. Used for further delineation of records sharing the same or similar Id.

Status. Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

##. Number of Items for the Id.

Edit. Checkmark indicates editable DCD.

Lock. Checkmark indicates non-editable DCD.

Buttons

Open button. Opens the selected row(s) of data.

Close button. Closes the selected row(s) of data.

New button. Creates a new line-item of data.

Copy button. Copies the selected row(s) of data.

Analyze button. When the user marks rows of data on the Component Results screen and depresses this button, the records are analyzed either on-line or they are posted to the background process so the user's terminal is not tied up during the analysis process.

Delete button. Deletes selected row(s) of data.

Undo button. Undo last operation.

Lock button. Locks selected row(s) of data (uneditable status).

Unlock button. Unlocks selected row(s) of data (editable status).

Renumber button. Renumbers the selected row(s) of data.

Sort button. Sorts selected line-items of data according to selected criteria.

Filter button. Filters selected line-items of data according to selected criteria.

Save List button. Saves selected line-items of data as a list.

Classify button. Classifies selected line-items of data.

Save Sort button. Saves selected sort criteria.

Cards button. Associates selected line-items of data with specific cards.

Installation

Installation Cards

Installation Module Overview

Installation Cards

Installation Cards are used to define what type of physical work must be done in the plant based on the changes that have been made to the database records. The Installation module manages the generation of unique installation card numbers, the printing and reprinting of the cards, and the collection of feedback information for the cards.

Each DCD’s cards will eventually be printed, issued for construction, used to perform work, used to record who did the work, and be used to record who inspected the work. After the work is completed, the software will be used to record what materials were used and what additional data changes may be necessary for the database. When all of a DCD’s cards are accounted for, the DCD cards can be "Closed Out."

Not all records require installation cards. It is the responsibility of the system administrator to define which commodities require installation cards. Card requirements are defined by the system administrator in the Configuration module.

When an unofficial or "Preliminary" installation card is required for Information Only, or when cable or termination tags need replacement, the cards or tags can be printed at any time from the main Report menu.

The difference between an official card and a preliminary card is as follows: An official card is associated with a serial number. A preliminary card has the characters "Preliminary" in the data field where the serial number would normally be printed. The Preliminary card is clearly marked "For Information Only".

Installation Card Process

When changes are made to database records, the software automatically assumes that an installation card is required to record the transaction. Accordingly, a record is added to the database indicating that a card is required for the DCD that made the data modification.

The user responsible for the data modification should review all card requirements prior to approving the DCD package to determine if the modification requires field work. If no field work is required, the card requirement should be cancelled before the DCD is advanced to an approved status. This can be done from the Pending Card screen.

When a DCD has been approved and it’s status has been advanced to "Released" status, official cards become available for printing. The cards are listed on the Installation module Results screen at "Preliminary" status.

To print installation cards, Mark all of the appropriate rows on the Installation results screen and use the Print function. The status of the card will change to "Printed".

If the data pertaining to a printed card is changed the printed card will receive a "Superceded" status. A new card with a new serial number and "Preliminary" status will also be generated.

When a card is lost and needs to be reprinted, use the Print function. If the status of the card is already "Printed", the new status of the card will be "Reprinted."

Installation Card Selections

The Installation selection screen allows the user to specify which card or group of cards they are interested in. The result of the selection is presented on the Installation Results screen.

Installation Results

The Installation module Results screen provides a list of cards and their statuses. From this list the user can control the printing and reprinting of cards. It is from this screen that feedback is also performed.

Work Orders and Work Breakdown Structures

The Installation module Results screen provides the capability to assign Work Order (WO), Work Breakdown Structure (WBS), Installation Date, and Inspection Date information to each card.

To associate a WO or WBS number with a card, mark the desired cards and depress the Work Order or WBS button. You will be prompted for a WO or WBS number and the number will be applied to the installation cards. If a WO number is associated with the card before it is printed, the number will appear on the card.

To associate an Installation or Inspection date with a card, mark the desired cards and depress the Install Date or Inspect Date button. You will be prompted for a date and a date will be applied to the installation cards.

Feedback

To enter feedback about a record, select the appropriate card on the Installation Results screen and depress the Feedback button. When feedback changes are made to the database from the Installation Results screen, the card status changes to "Partial Feedback" and these changes must be reviewed before the DCD is closed-out.

To indicate approval for feedback changes, you should mark the appropriate rows and depress the "Check CC" button. The status of the cards will be changed to "Card Complete" status.

Only the ids whose required cards are at "Card Complete" status will be closed out when the DCD is closed out.

History

When cards are printed, superceded, or have been used in the past to perform work, they are recorded on a history table. The History (Cards) screen displays a records’ card history in descending chronological order.

Installation Cards

Following are samples of installation cards for the cable, jumper, tray and conduit commodities. See the attached examples for what the installation cards look like.

Cable Card

This installation card provides the data that is necessary to install the cable. It also provides an area for feedback comments and sign-off signatures.

Jumper Card

This installation card is very similar to the cable card and provides the data that is necessary to install the jumper. It also provides an area for feedback comments and sign-off signatures.

From/To Termination Card

These installation cards provide the data that is necessary to terminate the from and/or to end of a cable. It also provides an area for feedback comments and sign-off signatures.

Raceway Card

This installation card provides the data that is necessary to install a conduit, tray, and special raceway. It also provides an area for feedback comments and sign-off signatures.

Alias / Id / Card No.

The Alias / Id tab allows the entry of document / record selection criteria according to component, DCD, details or notes criteria.

Figure 5.46. Installation Search

Installation Search

Fields

DCD field. Design Change Document (DCD) association.

Card No field. Associated card number.

Status field. Defines the status of the DCD and whether the DCD is editable or non-editable.

Work Order field. Associated work order.

WBS field. Work Breakdown Structure

Activity Since Buttons / Selection Boxes

Printed button / selection box. Indicate "printed" status.

Feedback button / selection box. Provide feedback.

Component Fields

Id / Alias field. Id / alias identification.

Unit field. Unit identification.

Commodity field. Each PDMS component Id is categorized by a commodity (Examples: Cable = CA; Equipment = EQ; etc.). The commodity is used to define the appropriate kind of details that should be linked to the Ids belonging to the commodity. A commodity is also used to specify which types of screens are appropriate for the category of Ids.

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Pending Cards

When changes are made to component module records, installation cards are generated and transactions regarding these cards are recorded on a log (tracer) tables. The Pending Cards screen summarizes the changes that are pending for the DCD. From this screen the user can perform feedback for cards and indicate whether the card is at Check / Card Completed status.

Data Columns

Row Numbering. Row numbers for current screen.

DCD. Indicates Design Change Document (DCD) by name.

Type. Indicates document type.

Card No. Indicates card number.

Reqd. Checkmark indicates "required".

Card Status. Indicates DCD status (e.g., New DCD, Advanced DCD, etc.).

Workorder. Summary description of workorder.

Insert. Inserts a row for data entry.

Delete. Deletes the selected row(s) of data.

DCDs

Allows selection of Component Module records by Design Change Document (DCD) selection criteria. By entering selection criteria in some or all of the data fields, users can focus on one or many detail records.

Fields

DCD. Design Change Document (DCD) association.

Parent. Displays the parent DCD.

Project. Displays the associated project.

User. Displays the associated user.

Department. Departmental association.

From-Through Selection

Selects the appropriate from-through date with field scroll buttons and a calendar utility.

Buttons

Select. Select using specified criteria.

Close. Close selection screen.

Reset. Reset selection fields to their default values.

Reports. Run reports using specified criteria.

Installation Results

The Installation Results screen is the second stage in the drill-down toward desired (filtered and sorted) installation data records. The lower portion of the window displays the running history of the installation card, including Date Printed, Installed and Inspected.

Figure 5.47. Installation Search Results

Installation Search Results

Data Columns

Row Numbering. Row numbers for current screen.

Checkbox. For selecting line-items of data.

Reqd Checkbox. Indicates required.

Type. Indicates type.

Card No. Indicates card number.

Card Status. Indicates card status.

DCD. Indicates associated DCD.

DCD Status. Indicates associated DCD.

Unit. Indicates unit type.

CT. Indicates cable type.

Id. Indicates unit Id.

Subid. Indicates unit sub-Id.

Buttons

Feedback. Opens the Installation Feedback dialog box.

Close. Closes the Installation Results screen.

Regen. Regenerates the Selected Cards

Print Card. Prints card(s) for selected row(s) of data.

Check CC. [definition]

Delete. Deletes selected row(s) of data.

Work Order. The work order number from external Work Flow Management System

WBS FIELD. Work Breakdown Structure

InstDate. Display installation date.

InspDate. Display last inspection date.

Safe Shutdown

Safe Shutdown / Combustible Load

Combustible Loading Overview

Fire Protection Data and Screens

Following are discussions of the important data relationships in PDMS related to Fire Protection commodities. For information regarding other commodities and screens, please refer to the User Guide or the Help screens.

Cables

BTU combustible data is stored with each type of cable in the Reference module, on the CT Details (3) screen. When a cable is assigned a type of cable on the Component module Details screen, and routed on the Routing screen, the BTU load of each raceway, room, zone, and area is automatically updated.

Raceways

BTU/Ft combustible data is stored with each raceway. To modify a raceway’s BTU/Ft data go to the raceway’s BTU screen. To see a raceway’s included cables, go to the raceway’s Included Cables screen.

Each raceway in PDMS must be linked to at least one room and ambient temperature. To modify a raceway’s linked rooms and ambient temperature, go to the raceway’s Links (Room) screen. To prorate the length of each raceway over several rooms, adjust the length value in the length column for each room it is linked to.

Rooms

PDMS multiplies the length of each raceway in a room by its BTU/Ft value to determine the room’s cable BTU load. To see which raceways are located in a room, go to the room’s Links (Raceway) screen.

To modify the ambient centigrade temperature of a room, go to the Links (Raceway) screen for the room. The "Ambient Data" function on this screen will provide you with current statistics about the room’s ambient temperature, and provide you with the opportunity to change some or all of the linked raceway ambient temperatures.

Dimensions

Dimension information in PDMS is stored with each room. To modify the length, width, height, and area data about a room, go to the room’s Dimension screen. To adjust the area of a room, simply adjust the length or width dimensions of the room.

Combustibles

Combustible information in PDMS is stored with each room. To modify the combustibles that are located in a room, go to the room’s Combustible Material screen. As discussed above, the BTU/ft data for each raceway is calculated separately.

To create additional types of combustible materials or adjust the BTU per unit value for existing materials, depress the Comb Type button. A Configuration module screen will appear and allow you to Insert / Delete / Modify combustible types.

Fire Load

To see the total fire load for a room, go to the room’s Combustible Material screen and depress the Fire Load button. A summary screen combines all of the combustible data with the cable data and shows both the As-Built and In-Design combustible loads for the room.

Allowable Fire Load

Allowable BTU loads are store with each room. To modify a room’s allowable BTU load, go to the room’s Allowable screen.

Fire Zones

Each fire zone in PDMS must be linked to at least one room. Otherwise, a problem is posted with the fire zone. To modify a fire zone’s linked rooms, go to the fire zone’s Links (Room) screen.

To see the combustible load for a fire zone, go to the Combustible Material screen for the zone. This screen subtotals and totals all of the data for the rooms linked to the zone.

Fire Areas

Each fire area in PDMS must be linked to at least one fire zone. Otherwise, a problem is posted with the fire area. To modify a fire area’s linked fire zones, go to the fire area’s Links (Fire Zone) screen.

To view the combustible load for a fire area, go to the Combustible Material screen for the area. This screen subtotals and totals all of the data for the zones and rooms linked to the area.

Fire Seals

Cables that are routed through Fire Seals undergo a special derating process to assure their ampacities are sufficient to support the electrical load they are expected to carry. To determine which cables are routed through Fire Seals, select the appropriate fire seal(s) to the component Results screen and go to the seal’s Included Cable screen.

Fire Wraps

Cables that are routed through thermolagged (wrapped) raceways undergo a special derating process to assure their ampacities are sufficient to support the electrical load they are expected to carry. To determine which raceways are wrapped, go to the component module selection screen and use the Wrapped Raceway selection criteria to select the appropriate wrapped raceways. Once the wrapped raceways are presented on the component Results screen, go to the raceway’s Wrap screen to see its wrap characteristics.

Each raceway that is wrapped must also be wrapped in a specific room. Before the raceway can be wrapped in a room it must first be linked to the room using the Links (Room) screen.

Fire Protection Reports

Following are discussions of the special purpose reports designed to assist fire protection operations. For information regarding other reports, please refer to the User Guide or the Help screens.

To request these reports, go to the Component Results screen for a fire zone and mark the zones that should appear on the report. Next, go to the Report menu, and select the appropriate report.

Combustible Loading for Safety Related Areas

This [MC5800-1] report subtotals the combustible materials in rooms and grand totals the materials to the fire zone level.

Safe Shutdown Overview

The Safe Shutdown screens and reports in PDMS are designed to manage and report on Safe Shutdown Components, both in terms of their location in the plant as well as their dependency on certain Safe Shutdown Cables and Raceways. To that end, the following screens are used to manipulate the Safe Shutdown settings in PDMS:

Safe Shutdown Detail Value

A Safe Shutdown Component is marked as such by entering a value of Y (Yes) for the Safe Shutdown Reference Detail (Type = SS) in the Reference Details screen. The SS Detail is a mandatory data entry requirement for all Equipment (and possibly other commodity types in PDMS). If an Equipment ID is not required for Safe Shutdown of the plant then the value for Safe Shutdown is set to N (No).

For all Safe Shutdown Components there are other data entry requirements:

  1. Fire Zone link.

  2. Safe Shutdown Cables required for operation of this SS Equipment ID.

  3. Power Supply information.

  4. Failure Position and Hot/Cold Shutdown information.

  5. Basic Event Reference Details.

All cables marked as REQUIRED for the operation of a Safe Shutdown Equipment ID are automatically set to a status of Safe Shutdown themselves. As a result, all raceways that the cable passes through are also marked as Safe Shutdown.

Safe Shutdown Revisions

PDMS allows the system administrator to create a Safe Shutdown Revision, which is a snapshot of all Safe Shutdown data that exists at one point in time. By creating snapshots at different times and running the ‘Diff’ report on the SS Revision screen, the administrator can clearly see what aspect of the Safe Shutdown relationships has been modified between snapshots. Due to the excessive overhead on the system during the creation of a SS Revision it is strongly urged that only the System Administrator perform this task, and if possible, not during the peak online hours of the day.

Safe Shutdown Application Programming Interface

The safe shutdown data in PDMS is accessible through a set of API calls. See the SS API guide for more information on this topic.

Safe Shutdown Equipment

This screen displays the Hot and Cold Shutdown settings for a Safe Shutdown Equipment ID. It also displays the Failure Position information based on a list of values contained in the POSITION table, which is found in the PDMS configuration module.

Data Columns

Cold Shutdown Position.

Hot Shutdown Position.

Normal Position.

Failed Air Position.

Failed Ele Position.

Cold Shutdown. Yes or No (or unknown).

Hot Shutdown. Yes or No (or unknown).

Hi Lo Pressure Interface.

Comments. General purpose comments.

Buttons

Insert. Inserts an empty row on the screen.

Delete. Deletes an In Design row, and marks as built data for deletion.

Audit. Produces a Safe Shutdown Equipment Audit report.

Safe Shutdown Cables

Lists the Safe Shutdown Cables related to a Safe Shutdown Component ID. The Route Points for all cables defined as REQUIRED FOR SAFE SHUTDOWN will also be given a status of SAFE SHUTDOWN.

Data Columns

Unit. Unit of the Cable ID.

CT. Commodity Type of the Cable.

ID. The Component Id of the Cable.

SubID. An optional Component SubID.

Required. Indicates whether or not the cable is required for the operation of the Safe Shutdown Component. If YES, then the cable is given a Safe Shutdown status in PDMS. If NO, then the cable is not considered a Safe Shutdown cable for this component. It may appear as a Safe Shutdown cable for another Component Id, however.

Items. Number of Cables.

Status. Indicates the Component status (e.g., New, Modified, As Built, etc.).

Analysis. This is the rational that is the basis for the REQUIRED setting.

Remarks. A general purpose comment field.

Tab-Specific Functionality

There are a number of tabs that provide a ‘seeding’ list of cables as a way to improve the data entry for safe shutdown cables. An entry in any of the tabs can be ‘dragged’ onto the Safe Shutdown cable list screen and the entry will be automatically populated. The seeding list screens are described below:

Included Cables. A list of all cables that are terminated to the Safe Shutdown Component.

IDs by Document. DA list of all cables that share a common drawing (scheme).

Cable IDs. General purpose Cable ID search result list.

Buttons

Insert. Inserts an empty row on the screen.

Delete. Deletes an In Design row, and marks as built data for deletion.

Doc List. Launches the IDs by Document Search TAB.

ID List. Launches the Cable IDs Search TAB.

Audit. Produces a Safe Shutdown Equipment Audit report.

Safe Shutdown Power Supply

Lists the Safe Shutdown Power Supplies related to a Safe Shutdown Component ID.

Data Columns

Unit. Unit of the Power Supply.

CT. Commodity Type of the Power Supply.

ID. The Component Id of the Power Supply.

SubID. An optional Component SubID.

Status. Indicates the Component status (e.g., New, Modified, As Built, etc.).

Required. Indicates whether or not the power supply is required for the operation of the Safe Shutdown Component. If YES, then the power supply is given a Safe Shutdown status in PDMS. If NO, then the power supply is not considered a Safe Shutdown cable for this component. It may appear as a Safe Shutdown power supply for another Component Id, however.

Remarks. A general purpose comment field.

Buttons

Insert. Inserts an empty row on the screen.

Delete. Deletes an In Design row, and marks as built data for deletion.

Audit. Produces a Safe Shutdown Equipment Audit report.

Safe Shutdown Analysis

This screen shows the Safe Shutdown status for a Component. A Component can be considered Safe Shutdown in either the In Design calculation, the As Built calculation, or both. The reason for the Safe Shutdown status is shown in the Related ID and Source columns.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Safe Shutdown Strategy

This component module screen is used to define the safe shutdown strategies for a cable within a specific Fire Zone or Area. This is useful in cases where the cable is not identified with a specific Safe Shutdown Component but has been analyzed in terms of an overall Fire Zone or Fire Area impact.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Safe Shutdown Equipment by Fire Zone

Displays Safe Shutdown Equipment IDs and their related Safe Shutdown cables and route points for a given Fire Zone. The user can drill-down to the Safe Shutdown components that are displayed on the screen. This is an extremely helpful navigation tool from the Fire Zone perspective.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user’s DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Safe Shutdown Equipment by Fire Area

Displays Safe Shutdown Equipment IDs and their related Safe Shutdown cables and route points for a given Fire Area. The user can drill-down to the Safe Shutdown components that are displayed on the screen. This is an extremely helpful navigation tool from the Fire Area perspective.

Data Sort / Filter Box

As-Built radio button. Sorts / filters for as-built components.

My DCD radio button. Sorts / filters for records associated with the user's DCD.

All DCDs radio button. Sorts / filters for records associated with all DCDs.

Filter/Sort checkbox. Applies the selected sort / filter criteria.

Row Status Fields

Provides the DCD status of the selected detail record.

Function Buttons

OK. Closes the screen and returns to the Reference Results screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Help. Opens context-sensitive Help.

Print. Prints the selected detail record.

Preview…. Previews print jobs for selected detail records.

Save As…. Saves the selected screen of data to a file.

Fire Probabilistic Risk Assessment (PRA)

Chapter 6. Reporting

Reports

Reports Menu

The Reports menu allows for report selection.

Menu items

Reports. This option appears when Ids are selected or ‘marked’. It opens the report selection screen.

Adhoc Reports. Permits ad-hoc reporting (without first selecting Ids).

PSR Files. Power Builder Format…To be used only between PDMS users.

Print Window. Print active PDMS window.

Print Screen. Prints the current active screen contents.

Report Options

All section-based reports, such as the DCD Impact report, Component report, Reference Detail report, and Document report have several options that can be set before running the report. The report option screen appears after marking the items to be included in a report and pressing the Report / Report option in the PDMS menu structure.

Figure 6.1. Report Options

Report Options

Some of the options include:

  1. Initial Page Number (if treated as a project insert)

  2. Orientation (Portrait or Horizontal)

  3. As Built versus In Design Data Filter

  4. Page Break on Id (Start a new page for each Component ID)

A report can be copied so that a customized version of a report can be made that suits the needs of a specific site. The COPY and MODIFY buttons will allow the user to create these customized reports.

Adhoc Reports

The Ad Hoc Reporting Screen allows the user to run reports using selection criteria as opposed to a selected list of Ids, DCDs or Details.

Chapter 7. Security

Security

Security Overview

PDMS Logins and User Information

Each PDMS user must have a valid user login id and password. Oracle logins and passwords are issued by the Oracle System Administrator. PDMS logins and passwords are usually the same as the Oracle logins and passwords. The PDMS System Administrator determines which users can access the PDMS database.

Each time a user enters a valid login and password, PDMS starts and presents the user with a "System Settings / User Preferences" screen. This screen describes the user's session settings. The data on this screen is important because it determines the user's capabilities within PDMS. Included on the screen is the user’s Department, Project, Role, Level of Authority, and associated Design Change Document (DCD). The screen also provides the user with appropriate options to change their password and other personal information.

Usually, when you first enter PDMS you are assigned an authority level of a Guest user. Not until you deliberately link yourself to an appropriate Design Change Document are you able to make changes to the database.

For example:

  1. If the user is associated with a "Display Only" role or "Guest" department, the user cannot make changes to the database.

  2. If the user is associated with a Design Change Document that is at an Uneditable status, the user cannot make changes to the database using the DCD.

  3. If the user is associated with a certain department, the user may or may not be limited to making changes to data owned by another department.

Departments, Roles, and Levels of Authority

The PDMS System Administrator, through a series of decision tables, determines what minimum level of authority is required to access a module, display data screens, and update data on the screens. Usually, only personnel in the electrical department have enough authority to update information about electrical commodities; however, almost anyone else can browse through the data in display mode. To enforce this strategy, each user is linked to one or several departments and each user is associated with a role. The PDMS role determines what level of authority a user has. For example the Guest role may be limited to displaying data and the System Administrator role may be allowed to perform any function. Most users are provided with at least a display-only role.

The PDMS application is constantly turning on and off the valid and invalid menu options and function keys that a user can select. If in the course of performing your job you feel that you need additional access to data in the update mode, please contact the PDMS System Administrator. The System Administrator will increase your level of authority by changing your role or will place you in another department that has update capabilities for the data.

Roles

This system administrator screen defines the valid roles that are used to define permissions throughout the PDMS system. Each role is associated with a level of authority.

Some of the typical Roles found in a PDMS deployment include:

GUEST

This is a READONLY role, and is assigned an authority level of 1.

RESPONSIBLE ENGINEER

This role can perform basic data entry, but cannot approve changes or advance/release a Design Change Document. The role is typically in the authority level range of 2 to 3.

CHECKER

This role has all of the privileges of the RESPONSIBLE ENGINEER role, but it has the additional privilege of CHECKING pending changes to prepare for a DCD Closeout. This role is often set to an authority level of 4.

APPROVER

All of the privileges of prior roles, with the additional privilege of Releasing a DCD. This is a critical operation in PDMS, as it permits the printing of final installation cards and the permanent closing out of In Design changes. This role is typically provided only to a PDMS system coordinator or department manager without oversight responsibility. This role is often set to an authority level of 5 or 6.

SUPER USER

This role is awarded to those people who will be able to perform special operations in PDMS. It is typically an authority level of 7. This role is distributed very selectively, as there are a number of special purpose screens and functions in PDMS that are to be used only by very knowledgeable users, or Super Users.

SYSTEM ADMINISTRATOR

This is an important role, and it is typically only linked to one or two people per site. This role allow the user to reconfigure virtually the entire system.

DEVELOPER / DBA

This is a role that is reserved for Cygna Energy Services.

Departments

This system administrator screen defines the valid departments that are used to define permissions throughout the PDMS system. The Component Module data that is referenced in PDMS can be limited by department by associating Units with a specific department. When this is done a user that is currently associated with the department will only be able to see data in the units that have been linked to the department. If no units have been linked to the department then all data is available to the user/department, pending other restrictions that have been put in place ono other screens.

Users

Figure 7.1. Users

Users

Each PDMS user must have a valid user Login Id and password. Logins and passwords are issued by the PDMS System Administrator.

Each time a user enters a valid login and password, PDMS starts up and presents the user with a "System Settings / User Preferences" screen. This screen Provides the user’s login characteristics and is a VERY IMPORTANT screen. Included on the screen is the user’s Department, Project, Role, Level of Authority, and associated Design Change Document (DCD). The screen also provides the user with appropriate screens to change his Password and other personal information. Briefly, the data on this screen determines the user’s capabilities within PDMS.

For example:

?If the user is associated with a "Display Only" role, the user cannot make changes to the database.

?If the user is associated with a Design Change Document that is at an Uneditable status, the user cannot make changes to the database using the DCD.

?If the user is associated with a certain department, he may or may not be limited to making changes to data owned by another department.

In addition to the User Information screen, each user can alter some display characteristics of PDMS by changing the settings on the Preferences and Row Color Setting screen.

The System Information screen provides the user with other machine, display, operating system, database, and application information.

Chapter 8. Add Screens

Add Screens

Add Screen Overview

The Add Screen module in PDMS is the entry point for adding Component IDs, Reference Details, Design Change Documents, and Documents. Some of these items are highly formatted, and must conform to a pattern. As such, customized screens have been created to make the addition of this data a simple task, while still conforming to the plant numbering conventions.

In some cases an Edit Mask, or data format, will be shown on the screen next to the field that must conform to a pattern. The Edit Mask will have the following properties:

n - a digit (0 through 9)

a - a letter (a through z)

x - any alphanumeric character (0 - 9, a - z, A - Z)

A - A constant in the form of a capital letter. The user must enter the value using the capital letter listed in exactly the place listed. Special characters, such as a hyphen, are also treated as literal constants.

Y - Year, normally in the form yyyy.

Some examples of edit masks found in PDMS, along with valid and invalid examples follows:

DCD Type: DCPEdit Mask: DCPyy-nnnn

Valid values include: DCP99-1234, and DCP05-9999

Invalid values include: ECP99-1234, and ECPxa-000a

Component ID Add Screens are provided for the commodities that have a conforming format. The following Commodity Types will often have a custom add screen:

  1. Cable

  2. Raceway

  3. Equipment

Other Component Types, such as Junction Boxes, Pull Boxes, etc., are often managed in the Add Any ID screen. This is a general purpose screen that will support the addition of any Commodity Type to the PDMS database. An example of a Cable and Raceway Add Screen have been included in the User Guide as a sample – your add screens may not look exactly like the examples shown in this document.

You may also add new Reference Details, DCDs, and Documents from the Add Screen module. See Add Detail, Add DCD, and Add Document for more information regarding these functions.

Add Menu

The Add menu permits the addition of components, details, documents and DCDs.

Menu items

Add Id. Used to create and format new component Ids such as cables, raceways, fire areas. They can then be located in the database via the Component module.

Add Reference. This screen is used to create and format new reference library details such as cable types, separation groups, and voltage levels. They can then be found in the database via the Reference module.

Add DCD. Create a new Design Change Document (DCD).

Add Document. Create an additional document or drawing.

Add a Generic Id

This screen provides the capability to add an unformatted id to the database. When customer component numbering systems dictate the formatting of ids, special add screens are provided for each commodity. For example, an Add Cable screen would be provided for adding formatted cables and an Add Conduit screen would be provided for adding formatted conduits.

Buttons

Hint. Display a list of IDs that match the partial value in the ID field.

OK. Save the new ID and close the screen.

Save. Save the new ID and leave the screen open for further data entry.

Cancel. Cancel any pending changes and exit the screen.

Open. Open the newly added ID in the PDMS Component module.

Reset. Reset the screen to the default values present when the screen first opened.

NOTE: Not all commodities have custom "Add" screens. This screen should be used to add new Ids to the database if the commodity to be added does not have a custom screen.

Add Cable Ids

This screen provides the capability to add a formatted cable Id to the database. A conforming cable ID varies from plant site to plant site, so the cable add screen is customized for every location. The example shown on this page may not be the exact layout that is found at your site. As a general rule you may use the "right click" in any field for a popup list of valid values.

Mandatory Fields

The fields on the TOP LEFT of the Add Cable screen will be used to construct a Component ID that conforms to the plant numbering convention for a cable. These fields are mandatory – the cable cannot be saved without entering a value for all fields on the top left of the screen.

Optional Fields

All other fields on the screen are there for the convenience of the user so that data entry may be greatly expedited. This screen is not intended as a way to perform regular data entry for cables in PDMS, it is simply an entry point for creating, copying, or renumbering a cable. After a cable is created it will be maintained by using one of the many highly specialized screens in PDMS, such as the Routing screen.

Buttons

OK. Save the new ID and close the screen.

Save. Save the new ID and leave the screen open for further data entry.

Cancel. Cancel any pending changes and exit the screen.

Open. Open the newly added ID in the PDMS Component module.

Reset. Reset the screen to the default values present when the screen first opened.

Add Raceway IDs

This screen provides the capability to add a formatted raceway Id to the database. A conforming raceway ID varies from plant site to plant site, so the raceway add screen is customized for every location. The example shown on this page may not be the exact layout that is found at your site. As a general rule you may use the "right click" in any field for a popup list of valid values.

Mandatory Fields

The fields on the TOP LEFT of the Add Raceway screen will be used to construct a Component ID that conforms to the plant numbering convention for a raceway. These fields are mandatory – the raceway cannot be saved without entering a value for all fields on the top left of the screen. The Commodity field will determine the type of raceway that will be added to the data (e.g. Conduit – CO, Tray – TR, ..). If the Commodity Type is changed you may notice that fields will become disabled or enabled (e.g. Branch ID will become enabled for a Conduit and disabled for a Tray).

Optional Fields

All other fields on the screen are there for the convenience of the user so that data entry may be greatly expedited. This screen is not intended as a way to perform regular data entry for raceways in PDMS, it is simply an entry point for creating, copying, or renumbering a raceway. After a raceway is created it will be maintained by using one of the many highly specialized screens in PDMS, such as the Continuity Links screen.

Buttons

OK. Save the new ID and close the screen.

Save. Save the new ID and leave the screen open for further data entry.

Cancel. Cancel any pending changes and exit the screen.

Open. Open the newly added ID in the PDMS Component module.

Reset. Reset the screen to the default values present when the screen first opened.

Add DCD

This screen provides the capability to add a Design Change Document (DCD) to the database.

Figure 8.1. Add a DCD

Add a DCD

Data Columns

DCD Type. DCD Type dictates the DCD Format, Parent status, and whether or not a DCD will generate Installation Cards. Right-click in this column for a popup list of valid DCD Types.

DCD Format. The DCD Format is based upon the DCD Type. It is an edit mask that dictates the pattern of the characters that can be entered for a new DCD. An example of a DCD Format is "DCP-yy-nnn", where "DCP" is an uppercase constant, dash is a special character constanct, "yy" is a two-digit year, and "nnn" is any three digit number.

DCD. Design Change Document. The value entered must comply with the DCD Format that is based on the DCD Type.

Parent. DCD Parent. For a Child DCD a Parent DCD is required. A Parent DCD is its own parent, so no value is required in this case.

Project.

Description.

Lead Department. A value in this column will limit the availability of the DCD to those users that are linked to this Department.

Buttons

OK. Save the new DCD and close the screen.

Save. Save the new DCD and leave the screen open for further data entry.

Cancel. Cancel any pending changes and exit the screen.

Add Detail

This screen provides the capability to add a Reference Detail to the database.

Figure 8.2. Add a Reference Detail

Add a Reference Detail

Data Columns

Unit. Reference Details can be associated with a specific unit. They are most often common to all units, and in this case they are linked to the Common Reference Unit.

Detail Type. The Detail Type defines the value being entered, as in CT (Cable Type), or RT (Raceway Type). The Detail Type may also supply an edit mask so that all values conform to a plant convention for the type of Reference Detail being entered.

Detail Value.

Description.

Buttons

OK. Save the new Detail and close the screen.

Save. Save the new Detail and leave the screen open for further data entry.

Cancel. Cancel any pending changes and exit the screen.

Add Document

This screen provides the capability to add a Document to the database.

Data Columns

Document.

Unit. Documents can be associated with a specific unit. If they are common to all units, then they are linked to the Common Reference Unit.

Doctype Default. The default Document Type associated with this document (e.g. WIRING DIAGRAM). The Document Type may supply an edit mask so that all values conform to a plant convention for the type of Document being entered.

Title.

Buttons

OK. Save the new DCD and close the screen.

Save. Save the new DCD and leave the screen open for further data entry.

Cancel. Cancel any pending changes and exit the screen.

Chapter 9. Administration

Administration

Customer Preferences

This system administrator screen defines the database preferences that control some of the variable behaviors of the PDMS software.

Each customer preference is described in detail below:

ABBREVIATED TITLE

This is the title that will appear on the title bar of the PDMS application. This title is also displayed on some screens and reports where space is at a premium. The abbreviated title will sometimes display the database instance that PDMS is directed toward. An example of this would be "PDMS DEV". The full title of the system can be specified with the SYSTITLE customer preference.

ALWAYS DETERM SPARE CABLES

When a cable is spared PDMS presents the user with an option to determ the wires. If a customer finds that the answer to this question is always YES then they can opt to avoid the popup question and proceed automatically with the determ operation.

ANALYSIS MEMORY LIMIT

This option is reserved for Cygna Energy Services so that the performance of the Analysis process can be refined on a site-by-site basis.

ANALYSIS TOLERANCE

Some of the calculations in PDMS produce results that have a decimal value in the thousandths place. At times a customer will want to set an additional tolerance limit for posting problems, such as .005, so that results rounded down in the thousandths place do not result in problem conditions.

APPLICATION VERSION

This is a number in the format N (Major Version).N (Minor Version). An example of this value would be 3.1. The version number is used to prevent users with obsolete versions of the application from connecting to the PDMS software and manipulating data. The application version number is set during system upgrades.

ARCHIVE PENDING CHANGES

A customer may opt to save the pending changes, along with checker and approver information, when a DCD closeout occurs in PDMS. If the ARCHIVE option is set to Y (Yes), then the pending changes that will be closed out are written to an archive table for later review. If this option is set to N (No) then the pending changes are simply deleted and removed from the system at the time of the DCD closeout.

ASBUILT DOCUMENT

The document module in PDMS can be set to record DCD Pending Changes for data such as ‘Document Type’, ‘Description’, etc. The default setting is N (No), meaning that document data is manipulated directly without any relation to a DCD.

AUTOCHECK

Set this value to Y (Yes) if your site will not be checking and approving pending changes. In this instance the pending changes are automatically checked and approved when a DCD is released. If this preference is set to N (No) then all of the pending changes will need to be checked and approved before a DCD can be released.

AUTOFILL DEPARTMENT

If this option is set to Y (Yes) then the active DCD is automatically filled-in on search screens in PDMS.

BROADCAST MESSAGE

This message is displayed on the PDMS User Information / System Settings screen. This screen is prominently displayed at the time that the user logs into the system. This is a convenient way to broadcast information to the PDMS user community.

CLIENT

This is a customer code that is required for the proper operation of the PDMS software at a specific customer site. PDMS customizations are enabled based on the customer code that is found in the Customer Preferences table. This value is manipulated directly by Cygna energy Services. Do not alter the value of this preference without contacting Cygna Energy Services.

CUST COMPONENT SORT

Each customer may override the default Component ID Search sort setting (Unit, CT, ID, Sub ID) with their own sort setting. An example of a custom sort option would be "Unit A, Ct A, ID A", which translates to Unit Ascending, Commodity Type Ascending, and Component ID Ascending. Another example might be "ID A", which would sort by Component ID in Ascending order regardless of Unit and Commodity Type. The default setting is N/A, which indicates that there is no sort override present.

CUST DEF REF UNIT

Customer Default Reference Unit. This is the common unit for the plant, where the Reference Details common to all units will be stored. Examples of this value include A, S, and 0 (zero). When Reference Details are validated for a Component ID the Component Unit and Common Unit (CUST DEF REF UNIT) are valid choices for the source of a Reference Detail.

CUST INSTALLATION FILTER

Each customer may override the default Installation Search filter setting (required = ‘Y’) with their own filter setting. An example of a custom filter option would be "required = ‘Y’", which translates to "Only display Required Cards". A value of "N/A" indicates that there is no filter override present. The default installation filter value is "(required = ‘Y’)".

CUST INSTALLATION SORT

Each customer may override the default Installation Search sort setting (Unit, CT, ID, Sub ID, Card Type, Card Number) with their own sort setting. An example of a custom sort option would be "Cardno A", which translates to Card Number Ascending. The default setting is N/A, which indicates that there is no sort override present.

CUST NAME

This is a complete, unabbreviated customer name meant for display on screens and reports in PDMS. An example of this value is "Cygna Energy Services, Inc.".

CUST REFERENCE SORT

Each customer may override the default Reference Detail Search sort setting (Unit, DT, DV) with their own sort setting. An example of a custom sort option would be "Unit A, Dt A, Dv A", which translates to Unit Ascending, Detail Type Ascending, and Detail Value Ascending. Another example might be "DV A", which would sort by Detail Value in Ascending order regardless of Unit and Detail Type. The default setting is N/A, which indicates that there is no sort override present.

DM DOCBASE

Documentum DOCBASE value. "N/A" indicates that the Documentum interface is not active at this customer site. An example of this value is "dmpdmsdb".

DM DOCBROKER

Documentum DOCBROKER value. "N/A" indicates that the Documentum interface is not active at this customer site. An example of this value is "pdms01.cygna.net".

DM DRL COMMAND

Documentum DRL (Document Resource Locator) command. "N/A" indicates that the DRL search mode is not active at this customer site. An example of this value is "dccomponentlauncher".

DM METHOD

Documentum Search method. Values for this preference include:

Method 1) "DRL CHRONICLE_ID" - Access content via DRL format through the Documentum Desktop client. DRL format includes DMS_OBJECT_SPEC = CHRONICLE_ID and DMS_VLAB=CURRENT.

Note: This method requires the Documentum Desktop client to be installed on the client PC.

Method 2) "DRL OBJECT_ID" - Access content via DRL format through the Documentum Desktop client. DRL format includes DMS_OBJECT_SPEC = OBJECT_ID.

Note: This method requires the Documentum Desktop client to be installed on the client PC.

Method 3) "DRL PREDICATE" – Return Search Results via DRL format through the Documentum Desktop client. DRL format includes DMS_OBJECT_SPEC = PREDICATE and a DQL query.

Note: This method requires the Documentum Desktop client to be installed on the client PC.

Method 4) "URL" - Access content via URL passing OBJECT_ID via the Documentum Webtop client.

Method 5) "EXPORT" - Access content and/or Search Results via Documentum DFC.

DM URL

This customer preference provides the root address of the Documentum interface on a web server. An example would be "http://lt3:8080/dmsearch".

DM WEBTOP URL

This value is required if the Documentum Interface will be using the URL method, as outlined in the DM METHOD customer preference. This provides the base url address to which PDMS will pass OBJECT_ID information.

DOCTYPE DEFAULT FILTER

When this option is set to Y (Yes) then the PDMS system performs document validation using the Document Type associated with the Document in the Document Module. If this value is set to N (No) then the system validates the entry based upon the document and sheet, and document type (e.g. WIRING DIAGRAM) is not factored into the validation process.

EMAIL COMMAND

This preference contains the external email command syntax. This is useful in the case where a customer cannot use the RDBMS to forward email directly, but where UTL_FILE has been enabled and an external email process has been setup to handle PDMS email messages. Contact Cygna Energy Services for assistance with this customer preference.

EMAIL HOST

This is the EMAIL Host at the customer site that will be used by the RDBMS to distribute email to PDMS users and administrators. An example of this value is "smtp.cygna.net".

EMAIL NOTIFICATION ID

This is the email address of the person that is acting as the administrator for the PDMS system. System errors and requests for assistance will be directed to this email address.

EMAIL SEVERITY

This is the PDMS error message severity level that will trigger email notification (see EMAIL NOTIFICATION ID). All PDMS errors have a severity associated with them, and any error events that occur that are equal to or greater than this setting in severity will be emailed directly to the system administrator.

ENABLE ARC INTERFACE

When a PDMS upgrade occurs this preference will be set to N (No) so that access to PDMS via a third party package (e.g. ARC) will only be possible if the system administrator has enabled the access directly. This should only be done if the system administrator has received confirmation that the third party application that depends upon PDMS has been re-verified and can demonstrate that it is in a state of readiness. When the preference is set to N (No) then only existing Safe Shutdown Snapshots can be accessed through the interface. Otherwise, the Safe Shutdown Snapshots and Actual Live data can be accessed through the PDMS - ARC Application Programming Interface.

EXPAND DESCRIPTION

Search Results that contain a ‘Description’ column will use a tokenized pattern if this preference is set to Y (Yes). An example of the token list is "DCDS,DESCRIPTION", which would result in the display of all active DCDs and the description value from the description table. The tokens can be placed in any order, and are comma-separated. Available description tokens include:

Component Module

DCDS – A list of active DCDs.

DESCRIPTION – The Component ID description.

AT – Alias Type (e.g. AT(TPNS)).

DT – Detail Type (e.g. DT(CT), for Cable Type).

DC – Document Type (e.g. DC(SCHEMATIC)).

DC (frm) – Document Type for the FROM ID (e.g. DC(WIRING DIAGRAM (frm))).

DC (to) – Document Type for the TO ID (e.g. DC(WIRING DIAGRAM (to))).

NT – Note Type (e.g. NT(C1)).

QT – Quantity Type (e.g. QT(LENGTH)).

FM – Cable FROM ID (e.g. FM).

TO – Cable TO ID (e.g. TO).

FILL – Fill Percent for Tray and Conduit IDs.

SN – Snubber Reference Detail description.

Reference Module

DCDS – A list of active DCDs.

DESCRIPTION – The Reference Detail description.

Document Module

DCDS – A list of active DCDs.

DESCRIPTION – The Document description.

DOCDATA – Document Details.

[Note]Note

The EXPAND DESCRIPTION option will cause system overhead when enabled. If this preference is set to N (No) then the description will be shown and the Description template will be ignored.

FALINK STRATEGY

This preference indicates how trays and conduits are linked into the Fire Protection hierarchy. The valid choices for this preference are:

FA – Fire Area.

FZ – Fire Zone. The Fire Zones connect to a Fire Area.

RN – Room Number. The Room Numbers connect to a Fire Zone.

FEEDBACK TOLERANCE

This option is intended to identify feedback data entry values that are outside of acceptable bounds. This option has not been implemented at this time, and is reserved for future use.

FIELD LEVEL VERIFICATION

If this preference is set to Y (Yes) then a Verification column will appear on the Component Module data entry screens. The Verification column indicates whether or not the data value has been verified and is in a known state.

HDG1

Report heading 1. This is the first of three heading lines that will appear on some of the PDMS reports. An example of this value would be "Cygna Energy Services, Inc.".

HDG2

Report heading 2. This is the second of three heading lines that will appear on some of the PDMS reports.

HDG3

Report heading 3. This is the third of three heading lines that will appear on some of the PDMS reports.

ID WIDTH

The Component ID column as been set to a default width that works well at most commercial power plant sites. There are cases, however, where the length of a Component ID is vastly different than the default length. In this case the customer can specify the length of a Component ID and the screens that display Component ID will be automatically adjusted to accommodate this custom length.

IMAGE PATH

This option is not longer in use by PDMS. It is described here for backwards compatibility. It was originally intended as a way to provide a network address for images. This is not accomplished through the Document Type settings screen.

INCLUDE DCD FAMILY

This preference determines whether or not PDMS will operate in a Parent - Child mode (One Parent has many Child packages but the changes of the Child packages are not inter-related), or in a Parent – Child – Child .. mode where a Parent has multiple Child packages and all of the DCDs with the same family operate on the same scope of data. The most recent Child package to be Released assumes ownership of the ‘leading’ installation cards for the entire DCD Family. This option has major ramifications for the modification of data in PDMS using Child DCDs.

INFER CCCOMPAT

When this option is set to Y (Yes), a compatible color code will be automatically inserted as a Reference Detail when a Cable Mark Number detail is entered for a Cable or Jumper Component ID. This is based upon the compatible color code that has been selected for the Cable Mark Number in the Reference Detail module.

INFER DVCOMPAT

This allows the Compatibility of the same Reference Detail to be inferred during PDMS Analysis. Set the value to Y (Yes) to allow the inference of compatibility, and N (No) to force the lookup of an entry for the Reference Detail in the Configuration Compatibility tables.

INFER FEEDBACK LENGTH

At times the estimated length value for some commodities, such as Conduits, varies very little from the actual length reported in feedback from the actual installation in the field. In such cases the user performing feedback is able to infer the actual length value from the estimated length value in order to save data entry time and effort. If the value is set to Y (Yes) then a prompt will appear asking the user if they would like to infer the length value for certain commodities. When set to N (No) the system simply bypasses this option and the user must input the actual length directly.

INFER POINT

When this option is set to N (No) then all Blocks and Points for a given Equipment ID must be predefined before a Cable can be terminated to it. When the option is set to Y (Yes) then the Blocks and Points are inferred automatically. This can result in a greater amount of typographic errors for the Blocks and Points defined for a given Equipment ID.

INFER SHEET

Then this option is set to N (No) then all Sheets for a given Document must be predefined. When the option is set to Y (Yes) then the Sheet Numbers are inferred automatically. This can result in a greater amount of typographic errors for the Sheet Numbers defined for a given document.

LIBRARY LIST

This option allows PDMS to add a dynamic library to the PDMS application after initial deployment. This would be useful for cases where new customer reports are needed but could not be included at the time of the initial production release. New reports can be added in a temporary library, and used in this manner until the time of the next production release. Objects in the temporary library will be relocated to a permanent library when the next production cycle occurs. This option adds the ability to extend the application between production upgrades. It is suitable for non-QA objects, such as stand-alone reports and queries. An example of this value is "pdmsext.pbd".

LOG SEVERITY

This is the severity at which PDMS error messages will be written to a log file on the user’s hard drive. This feature works in exactly the same way as the EMAIL SEVERITY option. If an error level exceeds this number (1 to 9) then the user’s local log file will be appended with the new error information.

PREVENT LOGIN

When this value is set to Y (Yes), only users with an authority level that is greater than or equal to SUPERUSER will be able to log into the system. This can be useful during system upgrades where the general user population should not be using the system until it has been verified and approved for use. Another option is to set this value to R (Readonly), so that users can still access the system but in readonly mode. No data changes will be permitted for users with an authority level lower than SUPERUSER.

[Important]Important

If this option is set to N (No) then normal access to the system is enabled.

PROJECT GUIDE

The Help menu in PDMS has an entry for customer-specific instructions covering the use of the PDMS system. This is a url address, such as "http://internalsite/pdmsdoc". This allows the user to construct a custom help guide that is targeted to their own department. This will complement the PDMS User Guide.

PURGE ID

When a Component ID is deleted from PDMS it is only physically deleted from the database if this preference is set to Y (Yes). If this value is set to N (No) then the ID status is changed to "Deleted and Removed", and it is no longer editable. This is a good choice for sites that do not allow the reuse of previously deleted Component IDs. All PDMS Component IDs are archived at the time that they are deleted, so there is a reference point to previously used components even if this option is set to Y (Yes).

RUN WORD PDMS MACRO

PDMS has the ability to run OLE automation using Microsoft Word. Some of this functionality depends upon a macro, and the customer may opt to allow or disallow the running of a Word macro from PDMS for security reasons.

SD NEW ID

Schedule for Deletion New IDs. If this option set set to Y (Yes) then NEW Component IDs must be Scheduled for Deletion using a Child DCD. When the Child DCD is Closed out the New Component ID will be deleted. If this option is set to N (No) then the Delete operation is carried out directly on the NEW Component ID.

SERVER LICENSE KEY

A server license key will be provided by Cygna Energy Services. The server license key insures that a valid, authorized version of PDMS is being used to manipulate data. Do not alter the value of this customer preference without contacting Cygna Energy Services.

SERVER PATH

This option is not longer in use by PDMS. It is described here for backwards compatibility.

SHEET LEADING ZEROES

The number of leading zeroes to pad in front of a document sheet number. An example of this value is "2", as in "00". A resulting sheet number with this setting would be "001", or "010".

SINGLE LOGIN

This preference, when set to Y (Yes), will prevent the same user_id from logging into the system from more than one instance of PDMS. If this option is set to N (No) then a user will be able to start up more than one instance of PDMS per user_id.

SUPER USER

Some of the functions in PDMS are enabled only for users with an authority level equal to or greater than Super User. The level, a number between 1 and 9, should be set fairly high (e.g. 7). Please contact Cygna Energy Services if you plan to alter this preference.

SYSTITLE

The application title, "Plant Data Management System". The title can be altered if the customer has a requirement for a specific application title.

UNIT ID POSITION

The Unit ID Position preference value informs PDMS where to find the Unit designator in Conforming Component IDs. This is useful information for the cross-unit copy operation. It is used along with the UNIT LENGTH preference to create and populate a Component ID dueing a cross-unit copy operation.

UNIT LENGTH

The Unit Length works hand-in-hand with the Unit ID Position preference value so that Component ID copy functions will work properly across units. Unit length is normally a value of 1, but it can exceed this value (e.g. 4).

UPPER CASE ALIAS

A customer may choose to allow the user to search for external system aliases using only Upper Case alias values to save the user from frustration. If the external system is case-sensitive, then the PDMS Upper Case Alias option should be set to N (no). Otherwise, the default setting is Y (Yes) which will convert all search values for ALIAS to uppercase.

UTL_FILE DIRECTORY

This is the UTL_FILE directory that has been setup for Oracle on the host operating system. This value is used when formatting external email instructions (see EMAIL COMMAND). An example of this value is "/home/pdmsora/email". A value of N/A indicates that the Oracle instance has not been setup to write external files on the host.

VALIDATE CLIENT

The System Administrator will typically run the automated V&V process to insure that PDMS is in the correct state for operation at a customer site. At the end of a successful V&V test the administrator is given the choice to record the client objects (exe, dll, pbd files) that have been used to complete the test successfully. If this preference is set to Y (Yes) the system will check the user’s installation and compare this set of files with those used by the System Administrator at the time that the V&V testing was performed. If there is a difference in any of the files the user will be informed of the difference, asked to contact the System Administrator, and the application will terminate. If the preference is set to N (No) the system will not attempt to compare the System Administrator’s installation image with that of all of the users attempting to log into the PDMS system.

VALIDATE SHEET

If this option is set to Y (Yes) then all of the sheet numbers listed for a document on the Document / Images screen in the Component Module will be verified for correctness. If an entry is not located, then the "INFER SHEET" customer preference is used to either allow or disallow the automatic creation of the sheet number that was entered. If this preference is set to N (No) then the sheet number is not verified and is treated as a text field.

VERIFICATION SCHEMA

An example of this value would be "Vdata Export Date 29-APR-05". This value is updated whenever a VDATA System Import is performed in PDMS. This value should not be directly manipulated. Do NOT alter this value without contacting Cygna Energy Services.

XML INSTALLATION CARD

Installation cards are generated in one of two ways in PDMS. The first way, which is backward compatible, involves the use of separate executable files based on the C programming language. These installation cards cannot easily be reviewed before printing, and they cannot be saved to a PDF file format. The second method involves Java and XML, and results in a visual installation card that can be saved to a PDF file.

Screen Settings

The system administrator may change a screen's title, description, active status, and association with specific data types (such as Cables or Trays). The order of screens in the screen display list can also be customized by altering the Screen Sequence value of a screen. Screens will appear within a module in PDMS. This screen - module association can also be changed within PDMS.

Data Columns

Screen. This is the internal application screen name.

Label. This is the short description for the screen, often used in screen list displays.

Screen Sequence. This is the order in which the screen will appear in the list.

Active. If checked, the screen is available. Otherwise, the screen is unavailable in PDMS.

Display Only. If checked, the screen will operate in READ ONLY mode.

Description. The detailed screen description that appears in the title bar.

Other. All other screen attributes are set by Cygna Energy Services directly.

Buttons

OK. Performs SAVE processing and closes the screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Insert. Inserts an empty screen row for data entry.

Delete. Deletes a screen. The operation is not finalized until the user presses OK or SAVE.

Copy. Inserts a new screen row and copies the settings from the highlighted row.

Screen Departments

This system administrator screen defines the level of authority required by each department to display and update the data on the screen. The departments listed at the bottom left of the screen may be selected and moved to the list at the bottom right of the screen. This movement enables the screen for the selected department(s). The administrator must then enter a minimum authority level within that department for either viewing or updating data.

Screen ModulesActive_Logins

The system administrator may define the module under which a screen will appear in PDMS. The system administrator should consult with Cygna Energy Services before attempting this operation.

Screen Data Types

The system administrator may limit the display of screens to a list of specified data types, based on Unit and Commodity or Unit and Detail Type (in the case of the Reference Detail module screens). A good example of this setting would be the Routing screen, which is typically enabled to CA (Cable) and JU (Jumper), but is disabled for TR (Tray) and CO (Conduit). The factory settings attempt to set reasonable defaults for screen versus commodity/detail type settings, but there are times when a system administrator will need to further refine the list.

Report Settings

Data Columns

Name. This is the report description that will appear in the report display list.

Report. This is the internal application report name.

Active. If checked, the screen is available. Otherwise, the screen is unavailable in PDMS.

Reporttype. For section-driven reports that can be copied, this is the base report type.

Orientation. For section-driven reports, this is the print orientation (Portrait or Horizontal).

Module. The module association for the report.

Other. All other report attributes are set by Cygna Energy Services directly.

Buttons

OK. Performs SAVE processing and closes the screen.

Save. Validates and saves pending changes.

Cancel. Cancels operation and closes the window without saving changes.

Insert. Inserts an empty report row for data entry.

Delete. Deletes a report. The operation is not finalized until the user presses OK or SAVE.

Copy. Inserts a new report row and copies the settings from the highlighted row.

Report Departments

This system administrator screen defines the level of authority required by each department to execute a report. The departments listed at the bottom left of the screen may be selected and moved to the list at the bottom right of the screen. This movement enables the report for the selected department(s). The administrator must then enter a minimum authority level within that department for executing the report.

Report Sections

This system administrator screen defines the sections that are appropriate for each report, where applicable. Some of the reports in PDMS are section driven, such as the DCD Impact Report, the Component Report, the Reference Detail Report, and the Document Report. The system administrator may customize these reports so that they contain concise content that is appropriate for their site by subtracting sections that will likely contain no data.

Report Section Data Types

This system administrator screen defines the commodity / report section relationship. If no entry is present then all commodities will display a section. If the valid list of commodities has been populated then the report section will only be displayed for this exact list. This is another way of limiting report material to that which is mot appropriate for specific commodity types, such as Routing information for a Cable or Jumper, but not for a Conduit or Tray.

Status

PDMS Statuses

DCDs, component ids, reference details, and installation cards are all associated with a status.

Component id records are usually at "As Built", "Modified" or "New Id" status. Special purpose statuses are "Pending Renumber From", "Pending Renumber To", "Scheduled for Spare", "Spare", "Scheduled for Deletion", and "Deleted and Removed".

Reference detail records are usually at "As Built", "Modified", or "New Detail" status.

Installation cards are usually at "Preliminary", "Printed", "Reprinted", "Partial Feedback", or "Feedback Approved" status.

DCDs are usually at "New DCD", "Advanced DCD", "Released DCD", "Demoted DCD", and "As Built" status.

A status can be set to be editable or read-only. The status link screen controls the movement from one status to another, and is based on authority level. This allows the customer to control the work flow in a way that conforms to their specific site. The system administrator should always contact Cygna Energy Services before changing the Status attributes.

Chapter 10. Configuration

Table of Contents

Configuration Overview

Configuration Overview

The Configuration Module is used by the PDMS System Administrator to create the "rule set", or valid options for relationships among items of data in the PDMS database. Compatibility between Units, Details, Commodities, Analyses, Documents, Classes, DCDs, etc., are all created in the configuration module.

Figure 10.1. Configuration Module

Configuration Module

Units

This system administrator screen defines the valid database "Units". Each plant, facility, or database can be subdivided into logical "Units" to control access and changes to data in the units. This screen also allows the administrator to set the authority levels for the display and update of a specific unit. The label, description and active switch reside here, as well.

Commodities - This screen allows the administrator to create commodities, set their active switch, label, and the screen used to add, edit or copy the commodity. This screen is key in creating associations for most other configurations. The Unit/Commodity combination is seen throughout the application and is often the root of incompatibility issues.

Alias TypesAlias_Types. – This screen allows the administrator to create and edit alias types and to associate alias types to given unit and commodity combinations. An example of an Alias Type is: TPNS, which would allow for the storage of an ID reference through a TPNS Alias value.

Allowable TypesAllowable_Types. - – This screen allows the administrator to create and edit allowable types, or allowable quantities, and to associate allowable types to given unit and commodity combinations. An example of an Allowable Type is: FILL, set to 40, for all Trays.

Analysis TypesAnalysis_Types. - This screen allows the administrator to edit analysis labels and descriptions and to associate analysis types to given unit and commodity combinations.

Block TypesBlock_Types. - This screen allows the administrator to create and edit cable routing block types and to associate block types to given unit and commodity combinations.

ClassesClassification_1. - This screen allows the administrator to create and edit classes, and to associate specific commodities to those classes.

Column Definition. – PDMS allows the system administrator to define dynamic column types for flexible data entry. These columns are stored in a configuration table. Each Column Has Several Attributes.

Column Id. Ad distinct number identifying the column. This number is managed by PDMS.

Screen Label. This is the Label that will be seen while using PDMS fr data entry, configuration, etc. SCREEN LEBELS MUST BE UNIQUE AS WELL.n

Report Label. This label is used during the execution of reports within PDMS.

Active. Is the Column currently usable/visible.

Format.* This field will represent the datatype of the column.

Specification.*

Edit Mask.* This column will provide a display format. For example, for monetary values, one might type $###,###.00, meaning that the dollar sign and up to 6 digits will show. There will always be "$.00" when the column is null.

The columns added or deleted via the Column List screen are tracked by the DCD process.

*Future Enhancements

Combustible TypesCombust_Types. - This screen allows the administrator to create and edit combustible types and their description, label, units of measure and active switch. This screen defines the valid types of combustible material that can be associated with rooms, fire zones, and fire areas. Each type is defined with associated units (i.e. OIL / Gallons, Carpet / Lbs, ..) and a BTU Factor per Unit. This value allows PDMS to compute BTU totals for combustible material. The combustible types can be optionally categorized so that BTU totals can be rolled up into meaningful categories (i.e. Class A, PVC, Misc., etc.).

DCD TypesDCD_Details. - This screen allows the administrator to create and edit DCD types and their description, whether they are a parent, the format of the DCD Id and the active switch.

Detail TypesReference_Selection_Screen. - This screen allows the administrator to create and edit detail types. They are associated with given unit and commodity combinations. Details have several switches including:

Active – Is the detail an active detail type

Minimum – Is this a minimum required detail for an associated commodity? (Should a problem be posted if one does not exist?)

Inferable – Can the detail be inferred? (auto generated by PDMS)

Card - Inactive

Post - Inactive

Preexist - Inactive

Limited - Limits the commodity to having only one of that detail type.

Device TypesDevice_Types. – Device types used to represent non-commodity items. The description and label along with the Active, Termination Device, and Load Device switches are on this screen.

Document TypesDocument_Types. - This screen allows the administrator to create and edit document types and their description, label, document path (Drive letter, e.g.) and viewer.

Active - Is the detail an active detail type

Minimum - Is this a minimum required detail for an associated commodity? (Should a problem be posted if one does not exist?)

Inferable - Can the detail be inferred? (auto generated by PDMS)

Preexist - Inactive

FT Code - Does this document type have a from and to drawing

A Document Type is used to identify a drawing or document in terms of its intended purpose. Layout Drawings are typically associated with raceway systems, Wiring Diagrams are often seen at routing terminations, equipment Ids and Panels. The Document Selection Screen allows the user to select drawings by the type of document they are. Additionally some document type have a From and To code so as to show the "Connection". Vendor drawings are Also common among sites to track installation and design of Manufactured components

Document ViewersDocument_Viewers. - This screen allows the administrator to include viewer types and their description, label active switch and executable.

This system administrator screen is for defining the valid viewers such as DEFAULT, WORDVIEW, NOTEPAD, EXCEL that can be used to view a document.

Fill TypesFill_Types. - This screen allows the administrator to create and edit Fill types. This screen includes the analysis types for a fill calculation, allowables for the calculation according to the raceway it also includes the depth and space factors. It also is used for categorizing raceways either as a type of conduit or type of tray for the purpose of calculating percent fill.

KVA Codes. – (Circuit Evaluation Module)

Link TypesLink_Types. - This screen allows the administrator to associate commodities which can be legally linked together, or are compatible continuity or fire safety links. The description, label and active switch can be edited here.

Load Steps. - (Circuit Evaluation Module)

Mode Names. - (Circuit Evaluation Module)

Note TypesNotes. - This screen allows the administrator to create, edit and activate note types and their unit/commodity combinations.

Problem TypesProblems_1. - This screen allows the administrator to create, edit and activate problem types.

Quantity TypesQuantities. - This screen allows the administrator to create, edit and activate quantity types as well as associate them with their unit/commodity combinations. Quantities also have the Minimum switch and the inactive Post switch.

Route TypesRoute_Types. – This screen sets the rules for legal routing combinations, based on unit and commodity type. An example of a valid route type is: Unit 1 TR (Tray).

Scenarios. - (Circuit Evaluation Module)

VL ClassesVL_Class. - This screen allows the administrator to create, edit and activate VL Classes.

Examples of VL Classes include: "Control", "Power", and "Instrumentation".

VL Default Fills. - This screen defines the default type of percent fill that should be used for each raceway that is assigned this type of "Voltage Level".

Cable SG CompatibilityCable_Type_-_Cable_Safety_Group_Compatibility_Analysis_(CS). - This screen allows the administrator to create, edit and activate Separation Group Compatibilities between Cables and certain unit/commodity combinations.

Cable VL CompatibilityCable_Type_-_Cable_Voltage_Level_Compatibility_Analysis_(CV). - This screen allows the administrator to create, edit and activate Voltage Level Compatibilities between Cables and certain unit/commodity combinations.

Raceway SG CompatibilityRaceway_-_Raceway_Separation_Group_Compatibility_Analysis_(SG). - This screen allows the administrator to create, edit and activate Separation Group Compatibilities between Raceways and certain unit/commodity combinations.

Raceway VL CompatibilityRaceway_VL_Compats. - This screen allows the administrator to create, edit and activate Voltage Level Compatibilities between Cables and certain unit/commodity combinations.

Chapter 11. Verification

The PDMS verification process uses both automated and manual test steps to assure that the software and database are in the correct state for operation by the PDMS user.

The Verification Wizard leads the user through a series of steps that will eventually result in a solid audit trail that assures correct configuration of the PDMS system. The wizard leads the user through the following steps:

Software Verification

The PDMS Software synchronization screen records changes that have just occurred to the software installation prior to beginning this test, if any. This list is printed and saved with the verification results.

Analysis Process Verification

The Automated Testing phase of the verification relies on the PDMS Analysis engine. If it is not running the Verification process is halted.

Database Verification

All database objects are compared to a certified list of required triggers, procedures, java programs, tables, and views and all objects are checked to make sure they are in the correct state. If any objects are either not located or are in an invalid state the verification process is halted and the invalid objects are prominently display on the screen. This list of invalid objects can be printed or saved as a spreadsheet or PDF file. If all objects are located and valid, then the verification process continues forward.

Automated Functional Testing

A series of well-devised automated test plans is now executed to "stress test" the core PDMS software. Component IDs, such as cables and trays, are created along with their related properties (such as Reference Details, Documents, Notes, and Quantities). All of these changes are linked to a Design Change Document. Conditions such as Overfilled Raceways, Separation Group incompatibility, and Voltage Level incompatibility are verified against a known "valid" answer set that has been manually calculated and certified.

All critical aspects of the PDMS system that do not involve a direct human interface are exercised through the automated functional test.

[Important]Important

An initial step in this process is to remove and reload the Verification test data that resides in the VDATA schema. This may take up to five minutes to complete, so please be patient if the reload is in process.

Manual Testing

The manual test is optional, but highly recommended, as it is the only way for the system administrator to exercise the manual interface of the PDMS system. A manual set of steps has been defined that will lead the user through the process of conducting the most critical aspects of PDMS processing. The manual test is heavily focused on the DCD process and the printing of Installation Cards. The user performing the test will be asked to record all results in the verification manual that is provided by Cygna Energy Services.

[Note]Note

The results of the manual test should be stored as part of the QA record for the software upgrade.

Chapter 12. Testing

Example 12.1. Sample Formula

∑Ei2


Appendix A. Install

Installing the Plant Data Management System (PDMS)

Requirements

  • At least 512Mb of memory and a 1GHz CPU.

  • 60Mb of free disk space.

  • What else...?

PDMS is officially supported on Windows XP and Vista.

Manual install on Windows

[Tip]Tip

On Windows, it is strongly recommended to download and install the auto-installable setup.exe file.

  1. PDMS is intended to be used directly from the CYGNA/PDMS/ directory. That is, you can start PDMS by simply executing:

    C:\Program Files\PDMS\pdms.exe

    After that, you may want to add a shortcut to "C:\Program Files\Cygna\PDMS\pdms.exe" on your desktop.

Content of the installation directory

bin/

Contains XXE code (.jar files) and many scripts used to start XXE and its associated utilities.

bin/xxe, xxe.bat

Scripts used to start XXE. Use xxe on any Unix system. Use xxe.bat on Windows.

bin/xxe.exe, xxe.jstart

Only when installing XXE on Windows using any of the *setup*.exe distributions. File xxe.exe is XXE launcher and xxe.jstart is its (plain text, UTF-8 encoded) associated parameter file.

bin/*.jar

All the (non-system) Java™ class libraries needed to run XXE:

  • xxe.jar contain the code of XXE.

    xxe_help.jar contains the online help of XXE.

    xsc.jar contains the code of the spell checker engine developed by XMLmind.

  • jh.jar is the standard Java™ help engine.

    xerces.jar contains Xerces 2.9.1 XML parser. (The version included in the Java™ runtime 1.6 has bugs which have been fixed in bundled version.)

    resolver.jar contains Apache XML Commons Resolver which implements catalog-based entity and URI resolution.

    Substantial parts of xsdregex.jar, James Clark's XSD to Java Regular Expression Translator, have been directly added to xxe.jar (which is why file xsdregex.jar is not included in the distribution). Download original package from http://www.thaiopensource.com/download/.

    Package com.jclark.xsl.expr contains the implementation of XPath 1.0 used by XT, James Clark's XSLT engine. A modified version of this package, renamed com.xmlmind.xmledit.xpath, has been directly added to xxe.jar (which is why file xt.jar is not included in the distribution). Download full XT from http://www.jclark.com/xml/xt-old.html or from http://www.blnz.com/xt/index.html.

    relaxng.jar is Jing version 20030619, James Clark's RELAX NG validator, slightly modified for use in XXE. The details of the modifications are found in relaxng.README.

    saxon.jar is Michael H. Kay's XSLT 1 engine. See http://saxon.sourceforge.net/.

    These excellent packages have not been developed by XMLmind. Copyright information is contained in the corresponding .LICENSE file. Read the corresponding .README file to have more details about these packages.

bin/legal/, legal.txt

Contains legal information about XXE and about third-party components used in XXE.

bin/icons/

Contains desktop icons for XXE.

doc/

Contains XMLmind XML Editor documentation in HTML and PDF (Acrobat) formats.

Note that:

doc/user/

Contains this User's Guide in HTML and PDF (Acrobat) formats.

The source of the User's Guide is also available in DocBook format (userguide.xml) in case you want to open it in XXE.

Acknowledgments

On Windows, the PDMS installer (i.e. *setup*.exe) is built using Inno Setup™ by Jordan Russell's software. Cygna Energy Services highly recommends this excellent and free-to-use tool.

Glossary

B

Branch

A section of raceway including exposed path or conduit joining two nodes.

See Also Raceway.

C

Conduit

A raceway that is solid, round in shape, and unventilated.

See Also Raceway.

D

DCD

Design Change Document

See Also Design Change Document.

Design Change Document

All changes in PDMS are tracked according to a Design Change Document.

E

Exposed Path

An exposed path is one which is not in any physical confinement or support such as a tray or conduit. Exposed paths are treated like base conduits without size restrictions.

See Also Raceway.

F

File

A collection of data which is saved by the computer in storage for later use.

Fire Area

An area in the plant that has been designed for Safe Shutdown and Combustible Loading analysis. A Fire Area contains one or more Fire Zones.

Fire Zone

An area in the plant that has been designed for Safe Shutdown and Combustible Loading analysis. A Fire Zone may contain one or more Room Number links, but should have at most ONE Fire Area Link.

R

Raceway

A term usually meaning anything used primarily to support and/or physically protect cable. Generally, the term designates conduit or tray, though it is also used to designate trenches and exposed cable paths.

See Also Branch, Conduit, Exposed Path, Tray.

T

Tray

A raceway that is rectangular in shape. It may or may not be covered on the Top and Bottom. It may also be ventilated.

See Also Raceway.

X

XML

Extensible Markup Language

See Also File.

Index

A

Analysis, PDMS Analysis

D

Design Change Document, Design Change Document (DCD)
Details, Details
Docs / Images, Docs / Images
Documents, Documents