COMOS Standard Table Color Codes: RGB Integer Conversion

Overview: COMOS Standard Table Color Definition

COMOS standard tables drive presentation attributes across reports, P&IDs, and pipe line graphics in Siemens COMOS. The standard table address format @40|Y00|A10|B50|Y00N00338 references a single cell in a multi-tab table that supplies values such as line width, line type, and color. When the source specification provides color in RGB (Red, Green, Blue) triplets, the engineer must translate that triplet into the integer that COMOS expects in the color column. This reference documents the address notation, the integer encoding rule, the conversion workflow using the Object Debugger, and the four common storage patterns (direct integer, separate XValues, delimited string, preview symbol) used in production COMOS databases. It also covers the SubOnChange script wiring on the media attribute, the symbol-column preview technique, the standard pipe color codes per DIN 2403 / ISO 14726, a verification procedure, and a troubleshooting matrix derived from field commissioning experience.

COMOS Standard Table Address Notation

The address @40|Y00|A10|B50|Y00N00338 follows the COMOS cell-reference grammar. Each segment identifies a different scope level. Decoding the segments:

For color definition, one of the sub-rows (commonly B50) carries the integer color value that the COMOS graphic engine renders as the line stroke color. The remaining sub-rows carry width, dash pattern, layer information, and any other presentation attributes the customer requires. Always confirm the destination cell with the customer's COMOS administrator before bulk entry; the cell holding the color varies between base data releases and customer-modified base data sets.

RGB Color Model and COMOS Integer Encoding

The RGB color model is an additive model in which red, green, and blue light channels are combined to reproduce a broad spectrum of colors. Each channel is typically an 8-bit integer in the range 0-255, producing 256³ = 16,777,216 distinct values. A pure red is (R=255, G=0, B=0), pure green is (0, 255, 0), pure blue is (0, 0, 255), and white is (255, 255, 255). COMOS receives these triplets from the spec and must store them in the single integer field of the standard table cell.

COMOS encodes a color as a single 24-bit integer. The byte order used by COMOS for the standard table color cell is the Windows COLORREF / BGR layout, where the low byte carries red, the next byte green, and the high byte blue:

Worked examples for common pipe colors (assuming pure channel values):

Prerequisites

• COMOS 10.x or COMOS Walkinside with administrative rights on the base project (read/write on standard tables and the affected tabs).
• Object Debugger access (Tools > Object Debugger) for direct value extraction and quick evaluation of color expressions.
• Knowledge of the target tab (typically Y00) and the column holding the color integer (commonly B50 in the pipe-line standard table; verify against the customer's base data set).
• Customer-supplied color list in RGB triplets (R, G, B), 0-255 per channel. The list may be delivered as CSV, Excel, or a printed specification; all three forms are accepted workflows.
• Optional: a script editor (COMOS script editor or an external editor such as Notepad++) for the SubOnChange wiring script on the media attribute.
• Optional: a color picker utility for quantitative verification of the rendered pipe line color against the customer specification.
• A non-production copy of the base data for byte-order verification and bulk-import dry runs.

Conversion Methods: From RGB Triplet to COMOS Integer

Four practical methods are used in production COMOS deployments. Choose based on the volatility of the customer color list, the bulk-import tooling available, and the audit trail required for the project quality record.

Method 1: Direct Extraction via Object Debugger

The Object Debugger can produce a usable integer if the source object already exposes a color attribute at the desired RGB value.

1. Open Object Debugger on any object that has a color set to the desired RGB value (for example, a pre-formatted pipe segment from the customer's previous project).
2. Evaluate the color expression. The COMOS Color function returns the integer directly. A common evaluator expression is Color(255, 0, 0) for pure red; the function returns 255 as the integer that the standard table accepts.
3. Copy the returned integer and paste it into the standard table cell. The cell type is integer; do not enter the triplet string in the same field.

Method 2: Manual Calculation (Spreadsheet)

For batch conversion of a customer color list (often delivered as a CSV or Excel sheet with columns R, G, B), apply the formula directly in a spreadsheet before pasting into COMOS.

Where A2, B2, and C2 are the cells holding R, G, and B respectively. Round the result to the nearest integer (the formula is integer-only, but the spreadsheet may display a floating-point value; format the column as integer with no decimal places). The output column is then imported into the COMOS standard table cell using the COMOS CSV import on the tab, or via a script loop for very large lists.

Method 3: Separate XValues Storage

When the customer's source data is volatile or the color may need to be updated without re-importing the full table, store each channel as its own XValue on the standard table row.

1. Add three XValue columns to the row: R_val, G_val, B_val, each an integer in the range 0-255.
2. On read time, compute the integer via a calculation attribute or a script call: Color_int = R_val + (G_val * 256) + (B_val * 65536).
3. Bind the result to the color attribute (for example, Y00N00338) using a calculation attribute or a script call.

This pattern allows the customer to update any single channel without recomputing the integer, reduces the risk of byte-order errors at import time, and produces an auditable trail of the source RGB triplet in the standard table itself.

Method 4: Delimited String Storage

For a compact storage representation, the three channels can be stored as a single delimited string, e.g., 255;0;0 (semicolon delimiter). On read time, split the string on the delimiter and apply the formula.

channels = Split(color_str, ";")
If UBound(channels) = 2 Then
    Color_int = CInt(channels(0)) + (CInt(channels(1)) * 256) + (CInt(channels(2)) * 65536)
End If

This pattern is the most space-efficient in the database but requires the script to handle malformed strings gracefully. Validate the length and channel count before evaluation; reject values outside 0-255 and reject strings that do not split into exactly three elements. Log the rejection to the project quality record if the customer may want to see which rows were skipped.

Wiring the Standard Table to a COMOS Media Attribute

For pipe line color driven by media, the standard table is bound to the media attribute, and a SubOnChange script propagates the color, line width, and line type to the runtime attributes on tab Y00T00039 when the user selects a media. The wiring sequence is:

1. Add a standard table reference on the media attribute (commonly the Media tab in the attribute dialog of the pipe object).
2. Populate one row per media. Columns: media code, line width, line type, color integer (in the convention chosen for the project).
3. Write a SubOnChange script on the media attribute. The script reads the standard table row that matches the selected media code and writes the three values (width, type, color) to the destination attributes on tab Y00T00039.
4. Trigger the script when the user changes the media code on any pipe object; COMOS propagates the new color to the pipe's runtime attributes automatically.

SubOnChange script skeleton (COMOS VBScript, structure only; adapt to your base project's attribute names and standard table layout):

Sub MediaAttr_OnChange()
    Dim stdTab, mediaCode, row
    mediaCode = Me.Media
    Set stdTab = GetStandardTable("@40|Y00|A10|B50")
    row = stdTab.FindRow("MediaCode", mediaCode)
    If row >= 0 Then
        Me.LineWidth = stdTab.GetValue(row, "LineWidth")
        Me.LineType  = stdTab.GetValue(row, "LineType")
        Me.LineColor = stdTab.GetValue(row, "ColorInt")
    End If
End Sub

The user selects the media once on the pipe; the rest of the line styling is automated. This pattern keeps the customer color list in a single editable location (the standard table) and prevents per-pipe color drift caused by manual line color assignment. The script also reduces the time required to apply a customer color change across an entire project: updating the standard table propagates to all pipes on the next OnChange event or next standard table redraw.

Color Preview and Self-Documenting Standard Tables

To make the standard table self-documenting, add a symbol column that previews the color. The symbol is bound to the color integer via a graphic reference; the COMOS graphic engine renders the symbol with the fill color set to the cell value. The engineer opening the standard table sees a swatch in the row, which makes it easy to spot wrong integers without launching a P&ID. Implementation outline:

1. Add a Symbol column to the standard table (right-click the column header in the standard table editor and choose Insert Symbol Column).
2. Bind the symbol's fill color to the ColorInt column via attribute reference. The symbol's fill attribute reads from the same standard table cell that drives the pipe line color.
3. When the ColorInt value changes, the swatch updates on the next standard table redraw. No manual refresh is required if the standard table is set to auto-refresh on cell change.

Best practice: add the symbol column as the first column after the media code so the swatch is immediately visible. Color the symbol border in a neutral gray to avoid introducing additional color noise in the table.

Standard Pipe Color Reference (DIN 2403 / ISO 14726)

Customer pipe specifications commonly follow DIN 2403 (identification of pipes according to the fluid conveyed) or ISO 14726 (ships and marine technology). Pre-computed COMOS color integers for the most common media are provided below for quick reference; always use the customer's exact RGB triplet in production, since the values from the specification govern the rendered color.

Verification Procedure

1. Open a test P&ID that contains at least one pipe per media code in the customer color list. If a dedicated test P&ID is not available, create one and place one pipe object per media code.
2. Trigger a redraw (View > Refresh or F5). The COMOS graphic engine re-reads the standard table on the next render cycle.
3. Inspect each pipe line. Compare the rendered color to the customer's RGB triplet using a color picker on a screenshot, or visually if the hues are well separated. For grayscale cases (e.g., drain black, vacuum gray), verify against a grayscale reference.
4. For a quantitative check, use a third-party color picker on the rendered graphic and confirm that the read-back R, G, B channels match the customer's specification within +/- 2 per channel. Anything outside this tolerance indicates a byte-order error or a mis-formatted integer.
5. Verify the standard table symbol column renders the same swatch. A mismatch between the symbol swatch and the pipe line color indicates that the binding of the color integer to the pipe attribute is broken or that the pipe is reading from a different standard table cell than the symbol.
6. Document the verified color list in the project quality record; include the COMOS color integers, the customer's RGB triplets, and the screenshot evidence. Archive the verification artifacts with the as-built project documentation.
7. Repeat the verification after any change to the base data (COMOS update, base data migration, customer base data update). The byte order has been observed to change between major COMOS releases in some customer environments.

Troubleshooting Matrix

Field-Proven Best Practices

• Always perform a byte-order verification on a non-production copy of the base data before bulk import. The cost of the verification is small compared to the cost of a project-wide color correction.
• Use the symbol column from the start. Engineers reviewing the standard table years after the initial configuration will rely on the swatch to interpret the integer values; a column of bare integers is not self-documenting.
• Keep the customer color list in the standard table, not in a separate project document. The standard table is the single source of truth for the project; any external document is a candidate for drift.
• For very large color lists (1000+ rows), generate the integer column in a spreadsheet and import via CSV rather than entering integers in the COMOS standard table editor one at a time. The COMOS editor is not optimized for bulk numeric entry.
• Document the byte order convention in the project quality record. Future engineers working on the project will need to know whether the integers are BGR or RGB, since the formula depends on the convention.
• When the customer issues a color change, update the standard table first and let the OnChange event propagate. Do not edit the line color attribute on individual pipe objects; manual edits will be overwritten by the next OnChange event and will create drift between the standard table and the runtime attributes.
• Back up the base data before any bulk import. A failed import may leave the standard table in an inconsistent state, and the only recovery is a base data restore.

FAQ