The practical answer
Connect a cooling-pipe marker to the identified system, fluid, documented service role, and direction for that segment. Compare the installed marker with the controlling drawing and record any disagreement. Do not infer flow direction from an ambiguous nearby pipe or transfer a color meaning from another system without the applicable legend and review.
The method, examples, and sources below explain the scope and checks.
Examples are fictional local conventions. Unless another location is shown, the scope is DC01 / H1. Keep that scope with shortened identifiers.
When to use#
Use this survey when a fixed cooling-pipe marker cannot be matched confidently to the facility drawing. Focus on the system carried through a defined pipe segment. Use guide 17 for individual replaceable hoses and their connection endpoints.
What to gather#
Gather the approved piping diagram, loop schedule, fluid description, marker specification, location plan, and facilities reviewer. Note drawing revisions and the viewing location for each observation.
ASME A13.1 covers identification of fluids in aboveground piping and their characteristics. Its public overview is not a complete color or placement specification. ASME scope
Identification workflow#
These steps are this library's recommended recordkeeping method.
- Bound the segment. Name the room and two landmarks that distinguish the visible pipe run from adjacent runs. Assign a survey reference if its permanent identity is missing.
- Copy the marker literally. Record visible system text, service wording, and any arrow. Describe an arrow relative to a fixed landmark, not simply 'left.'
- Compare the facility record. Extract the loop ID, approved fluid description, and supply/return role from the correct diagram. Retain observed and documented information separately.
- Escalate directional uncertainty. If the marker and record conflict or the diagram does not establish direction, record needs review. Do not infer flow from color, touch, or apparent pipe temperature.
- Review the marker schedule. Have facilities confirm the intended identity and applicable marker scheme. Record the accepted correction and evidence after the authorized labeling work.
The expanded procedures and fictional case below are original editorial recordkeeping guidance to adapt to the site's approved process.
Decide which part of the pipe identity is uncertain#
A pipe marker can disagree with the record in several independent ways. The loop name may be wrong, the fluid description may be incomplete, the supply or return role may conflict, or the arrow may point toward a different landmark. Start by naming the disputed field. A matching arrow does not resolve an incorrect role, and a familiar loop name does not establish the fluid description. Keep those comparisons separate so the facilities owner can address the actual uncertainty rather than reviewing a vague report that the pipe label looks wrong.
First decide whether the object belongs in this fixed-pipe survey. The subject is a bounded pipe segment within a documented facility system. A replaceable hose between two equipment connectors needs the hose relationship described in guide 17. If a photograph includes both, assign distinct identities and make the boundary clear in the observation. Do not give an entire loop the ID of one hose or carry a manifold nickname into the fixed-pipe record without the approved system relationship that explains it.
If the visible segment cannot be matched to a drawing object, create a temporary survey reference and describe its limits using stable landmarks. Mark the permanent segment or loop identity unresolved. A useful finding can begin with an exact location and a clear evidence gap. Do not choose the nearest drawing line just to populate the worksheet. The owner should be able to locate the surveyed segment again and understand why the current records do not yet establish its identity.
Establish the system boundary and viewing reference#
Gather the approved piping diagram, system schedule, fluid description, and marker specification by their actual references and revisions. Read which system and equipment boundary the role describes. The words supply and return should be connected to that context rather than used as free-standing names for every visible cooling connection. If the documents describe multiple loops or sides of equipment, keep their identities separate and record which one the surveyed segment belongs to. The survey should not infer a system boundary from physical closeness alone.
Describe direction with fixed landmarks. For a plan view, state the orientation and identify the relevant start and destination references. For a field observation, record which way the observer is facing and relate the arrow to a named bay, column, wall, or equipment reference. Avoid writing simply left, because another person approaching from the other end may mean the opposite direction. A photograph that is rotated or mirrored during handling also needs enough orientation context to preserve the original observation's meaning.
Keep the source of each statement visible. Observed marker means the words and arrow actually seen on the segment. Documented role and direction mean the values extracted from the approved reference. A statement about actual operating flow would require its appropriate technical basis and is outside this identification worksheet. If the diagram does not establish the direction needed for the label review, record needs review and identify the missing system information. Do not fill the gap from touch, appearance, pipe temperature, or an assumed color convention.
Compare and prepare the marker schedule#
Work through the fields in a stable order: segment location, loop identity, fluid description, service role, and direction. Check the parent system before debating the arrow, because a correct arrow on the wrong documented loop still produces an unreliable record. Copy the approved fluid description exactly enough for the site's marker specification and records process. If the observation only says water but the approved record uses a more specific description, preserve both and let the facilities owner determine the accepted text for this application.
When a difference is found, describe it in a sentence that includes the segment and both claims. For example, PIPE-G16-301 is marked RETURN with its arrow toward CDU-G16-301, while drawing MEC-G16-301 revision 3 identifies that same bounded segment as SUPPLY toward CDU-G16-301. This distinguishes a role conflict from a direction conflict. It also shows that the segment relationship itself must be supported before the wording can be corrected. Attach the context observation and the exact drawing detail used for the comparison.
Draft the proposed marker text only after the owner resolves the identity inputs. Keep the selected fluid wording, loop reference, service role, and directional landmark in the schedule, even if the physical face expresses some of them through the site's approved scheme. Review the actual design and placement against the applicable project and facility requirements. This page adds an editorial record workflow; it does not derive universal marker colors, lettering sizes, intervals, or distances from the public ASME overview.
Worked case: the role is wrong while the arrow agrees#
In this fictional DC01 / H1 case, survey PIPCASE-G16-301 covers PIPE-G16-301 between column N3 and cooling bay C3. The installed face says LOOP-G16-301 RETURN and points toward CDU-G16-301. The approved reference MEC-G16-301 revision 3 describes the bounded segment as the loop's supply toward that same unit and records the fluid description separately. The observer captures the exact text and the fixed directional landmark. The first diagnosis is a service-role mismatch; the agreement of the arrows does not settle that conflict.
The facilities owner reviews the segment identity and current system documentation. In fictional decision DEC-G16-301, the owner confirms the documented supply role and selects the accepted marker wording through the applicable scheme. The change record identifies the affected segment and face. The arrow remains directed toward CDU-G16-301; the role word changes from RETURN to SUPPLY. The register retains the original marker text and the decision basis so the case history explains precisely what was corrected and why other fields remained unchanged.
Final evidence EV-G16-303 shows the corrected face within the same bounded segment and records the viewing orientation. The reviewer compares loop, fluid wording, role, and arrow independently with the accepted schedule. If the photograph shows only SUPPLY without identifying the segment, it is incomplete closure evidence. The completed case states that the surveyed marker now matches the reviewed identity inputs. It does not claim a hydraulic test, an operating-flow measurement, or authorization to manipulate valves or equipment.
Variations to keep visible in the register#
Parallel runs need distinct segment identities and landmarks, even when they share a route. Record each visible marker against its own segment rather than assuming the upper or nearer pipe always has a particular role. If the record uses a positional aid, state the viewpoint and treat it as supporting location context. A plan that shows two adjacent lines should be linked through its identified system references, not matched to the field solely by whichever pipe appears first in a photograph.
Where a run changes direction, keep the arrow's meaning tied to the local segment and documented destination. One horizontal sketch cannot describe every turn in a route. Bound the part being surveyed and identify any continuation or branch that the record needs to distinguish. If the facility policy uses a single run ID across several marked sections, retain that parent identity while giving observations enough local detail to locate each face. This prevents a corrected marker at one bend from closing unexamined markers elsewhere.
An equipment replacement or loop rename can leave valid older aliases on drawings, schedules, and field text. Preserve those aliases as historical data and ask the system owner to establish the current relationship. If the change affects only naming, record that limited disposition. If the documentation also changes system boundaries or service roles, keep those questions separate for the responsible technical review. An identity crosswalk should not be used to imply that an altered system configuration has been validated through a label survey.
Failure patterns and closeout evidence#
Watch for descriptions that are too broad to repeat: north wall pipe, cooling return, or arrow left may identify several possible objects. Improve the accepted location description using the actual landmarks and system record while preserving the original wording in the finding. Also watch for copied loop names on adjacent rows and the use of a hose reference to identify fixed piping. A cross-check of segment, system, role, and destination often reveals whether the discrepancy lies in the label text or the assumed parent relationship.
Close each marker finding against its accepted disposition. Link the original observation, source revision, owner decision, final face, and segment context. Identify any remaining unresolved field instead of marking the row generally verified. If only the wording was corrected, say so; if an arrow remains unconfirmed, retain its owner and required evidence. Record the actual review date and the included population so a few corrected labels cannot be interpreted as a complete survey of the whole loop or facility.
Worked example#
Example only: fictional pipe survey.
SCOPE: DC01 / H1
Segment PS-03: H1 north wall -> CDU bay
Observed: LC-01 RETURN; arrow toward CDU bay
Drawing: LC-01 SUPPLY; toward CDU bay
Finding: service wording requires review
The matching arrows do not resolve the contradictory supply/return wording.
Common mistakes#
- Calling every cooling pipe 'water' without the approved description.
- Using an arrow without a stable directional landmark.
- Applying a hose's identity to an entire pipe loop.
- Assuming one color establishes fluid, role, and flow.
Verification#
Worksheet: Cooling pipe-marker survey#
| Field | Definition |
|---|---|
| Segment ID | Identity or survey reference for the bounded run. |
| Location | Room and fixed segment landmarks. |
| Loop ID | System identity from facility documentation. |
| Fluid description | Exact approved service description. |
| Documented role | Supply/return or other approved service role. |
| Documented direction | Direction expressed using fixed landmarks. |
| Observed marker | Literal wording and arrow orientation. |
| Finding | Specific discrepancy or review status. |
| Evidence | Piping diagram revision and observation reference. |
| Owner | Facilities reviewer for system identification. |
| Verification date | Actual date the identity review is completed. |
Filled example row - fictional; no live verification.
| Segment ID | Location | Loop ID | Fluid description | Documented role | Documented direction | Observed marker | Finding | Evidence | Owner | Verification date |
|---|---|---|---|---|---|---|---|---|---|---|
| PS-03 | H1 north wall to CDU bay | LC-01 | Example treated cooling water | Supply | Toward CDU bay | LC-01 RETURN; toward CDU bay | Service wording mismatch | Fictional M-12 rev 2; EX-16 | Example facilities team | Not verified (fictional) |
FAQs#
Does supply mean the same thing at every connection?#
Read the diagram's system context. Record which loop and equipment boundary the role describes.
Can this worksheet choose marker colors?#
No. Use the applicable project specification and approved marking scheme; the worksheet records their identity inputs.
Can two pipes carry the same loop name?#
They can be related to the same documented system while representing distinct segments or roles. Preserve the parent loop identity and the segment-level details needed to distinguish them. The loop name alone does not decide whether a particular segment is supply, return, or another role in the approved record.
What should I do when an arrow is visible but the wording is unreadable?#
Record the arrow against a fixed landmark and describe the unreadable text separately. Keep the role and fluid comparison unresolved until the approved record and owner review establish them. A readable direction indicator should not be used to reconstruct the missing words from assumption.
May I describe the fluid simply as water?#
Transcribe that word if it is the observed marker text, but use the approved facility description for the documented field and proposed schedule. Preserve any difference for review. This guide does not decide which description or marker design is acceptable for every system or exposure.
Can an old drawing still be evidence?#
Yes, as a clearly identified historical source or competing claim. Record its revision and what relationship it states. The facilities owner must determine its applicability to the current segment before it becomes the basis for an accepted correction. Do not substitute file age for that decision.
More worked label examples
Two additional ways to apply this guide. Keep the exact identifiers and relationships consistent with your own approved records.
GUIDE 16 / EXAMPLE 1
Show documented supply and return on two distinct pipes
Each marker carries the loop, service role, and direction for its own pipe segment; the local view is stated so arrows are interpretable.
SCOPE: DC01 / H1; plan view: west left, east right
DRAWING: MEC-G16-101 r3; fluid: facility cooling water
SUPPLY SEGMENT PIPE-G16-101
PLANT SIDE ===== PIPE-G16-101 ================= CDU-G16-101
[LOOP-G16-101 | COOLING WATER SUPPLY | FLOW --->]
RETURN SEGMENT PIPE-G16-102
PLANT SIDE ===== PIPE-G16-102 ================= CDU-G16-101
[LOOP-G16-101 | COOLING WATER RETURN | FLOW <---]
RECORD PAIRS
PIPE-G16-101 -> LOOP-G16-101 / supply / toward CDU-G16-101
PIPE-G16-102 -> LOOP-G16-101 / return / toward plant side
Marker face includes the actual service description
Direction source: MEC-G16-101 r3, not appearance of pipe- Replace the fluid description, loop name, endpoints, and directions with the approved mechanical documentation. A supply or return role is meaningful only relative to its stated system.
- Have the facility owner select the applicable marker design, color, size, and placement requirements. This example specifies no universal color rule and does not infer flow from temperature or pipe position.
GUIDE 16 / EXAMPLE 2
Handle a flow arrow that conflicts with the drawing
The record distinguishes the observed arrow from the documented direction and keeps correction on hold until the mechanical owner resolves it.
SCOPE: DC01 / H1; PIPE-G16-201 at overhead grid E4
VIEW: facing north; west is left, east is right
OBSERVED MARKER FACE
[LOOP-G16-201 | RETURN | FLOW --->]
OBSERVATION: arrow points east, EV-G16-201
DRAWING: MEC-G16-201 r5 shows return toward west
DISPUTED FIELD: flow direction for PIPE-G16-201
STATUS: unresolved; owner Mechanical facilities
ILLUSTRATIVE RESOLVED FACE, IF DRAWING IS CONFIRMED
[LOOP-G16-201 | RETURN | FLOW <---]
Decision DEC-G16-201 -> replacement CH-G16-201
Final comparison EV-G16-202 -> same recorded viewing position- Document the observer viewpoint and drawing orientation so a reversed photograph does not become a false discrepancy. Include the segment limits if the pipe changes direction nearby.
- Confirm the applicable drawing revision and operating configuration with the mechanical owner. Do not reverse a physical marker merely because one drawing arrow looks different.
Sources and applicability
- ASME: A13.1 piping identification ↗
Public scope overview only; no complete color or placement specification was accessed.
Read scope and linked guides
Planning guides and companion documents
- Data center labeling standards: build a project requirements map
- Cooling and facility signage crosswalk