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 guide when a hose label no longer identifies its intended manifold or equipment endpoint. The output is an individual hose register. Guide 16 covers fixed pipe-system identity; this page records which particular hose belongs to which documented connections.
What to gather
Gather the equipment model and configuration, OEM hose diagram, existing hose and manifold IDs, local connection register, and approved replacement record where relevant.
Lenovo's N1380 documentation identifies manifolds and includes a hose-guide label for its serial-flow configuration. These details are equipment-specific. Lenovo source
Identification workflow
These steps are this library's recommended recordkeeping method.
- Identify the configuration. Record the actual equipment model and the applicable diagram revision. A similar-looking rack is not sufficient evidence of the hose arrangement.
- Separate identities. Record the hose's local ID, any factory marking, and each parent equipment identity. Preserve OEM wording instead of replacing it with a simplified nickname.
- Capture two exact endpoints. Include the manifold or unit ID plus its connector designation. Keep observed connections distinct from the arrangement stated in the approved record.
- Record uncertainty precisely. Flag a missing port suffix, unreadable hose tag, or configuration mismatch separately. Use the equipment owner to resolve the relationship; this survey involves no reconnection.
- Maintain replacement history. When approved records identify a replacement hose, link the old and new identities. Review both endpoint references and the register after the authorized work.
The expanded procedures and fictional case below are original editorial recordkeeping guidance to adapt to the site's approved process.
Choose the identity problem before changing the register
Start by distinguishing the individual hose from its intended connection position. A hose label may be unreadable while the two documented endpoints remain clear. A connection schedule may omit a port suffix even though the hose ID is readable. A replacement may have been recorded against the former hose identity. A model-specific routing reference may describe a configuration different from the installed equipment. Each condition needs a different finding and evidence path; none should be repaired by assigning a convenient destination from a similar rack.
If the equipment model or configuration is uncertain, resolve that reference before using its connection names to approve a mapping. If the configuration is established but one endpoint cannot be read or observed, keep that endpoint unconfirmed and record the evidence needed. If two labels disagree on hose identity, preserve both observed faces and their locations. A complete-looking row can otherwise hide the fact that the physical assembly, connector position, or source document has never been positively associated with the other fields.
Define the included hose population. A survey may cover one replacement, one manifold's connections, or a named installation package. Record the full site and hall scope and identify any endpoint outside the inspected area. Distinguish this task from the fixed-pipe marker survey in guide 16. The hose register describes which individual assembly is associated with which exact equipment connections; it should not become a general fluid-system map that loses the replaceable object's identity and history.
Establish configuration and preserve factory information
Collect the installed equipment model, configuration information, applicable OEM diagram, and its revision or other identifying reference. Connect those records to the actual parent equipment identities in the facility inventory. The record should show why a particular diagram applies to this installation, not merely that a manufacturer's name is familiar. If an equipment change affected the configuration, retain that change reference and review the hose relationship through it. A similar connector arrangement in a neighboring rack is context for investigation, not approval evidence.
Keep the local hose ID, factory marking, and equipment connection references in separate fields. They may follow different naming systems and serve different purposes. A local asset tag helps find the facility record; a factory marking can relate to the manufacturer's assembly or routing information; a manifold connector designation identifies a position on a parent object. Do not overwrite one with another to simplify the worksheet. Preserving all three relationships makes the record useful when an assembly is replaced or a vendor reference changes.
Record the actual observation limits around factory information. If a factory mark is hidden or damaged, describe its visible portion and cite the applicable equipment record separately. Do not recreate a factory label from an invented local abbreviation. Any additional marker placement or material should follow the accepted equipment and application process while keeping existing information available. The examples here show identity content, not an installation technique, connector-compatibility determination, or permission to disturb a hose in service.
Describe the endpoints completely
An endpoint consists of a parent equipment identity and the exact connection designation within that parent. MAN-G17-301 alone identifies a manifold but may not identify one connection. MAN-G17-301 / S05 names a particular fictional position when that notation is established by the applicable record. Use the actual installed designations rather than translating them into a universal supply-port scheme. At the other end, preserve the device or tray identity and its connector reference with the same precision.
Keep observed connections separate from the arrangement stated by a diagram or schedule. A label that says TO AST-G17-301 / CI2 is an observed destination claim; it is not by itself proof that the hose currently reaches that endpoint. Link the accepted identification evidence that supports the relationship and state what remains unconfirmed. If the available evidence establishes the manifold end only, complete that field while leaving the other end unresolved. Avoid marking the whole assembly checked because one face is readable.
Compare the service role only within the documented equipment context. If the local register uses supply or return, retain the OEM and facility references that explain what the role describes for this connection. Do not derive the role from hose appearance or color, and do not apply one model's convention to another. If the role and endpoint map disagree, record the disagreement as a configuration or naming question for the equipment owner. This survey does not resolve it through reconnection or operational experimentation.
Worked case: replacement history was attached to the old hose
In this fictional DC01 / H1 case, HOS-G17-301 formerly connected MAN-G17-301 / S05 to AST-G17-301 / CI2. An authorized replacement package HCH-G17-301 introduces physical hose HOS-G17-302 for that same documented connection position. The current schedule still lists HOS-G17-301, while the replacement's accessible local face carries HOS-G17-302. Survey HCASE-G17-301 records the old schedule, the new observed identity, and the replacement reference. The first finding is a lifecycle discrepancy, not an assumption that the endpoint arrangement changed.
The equipment owner reviews the replacement record and the applicable configuration reference OEM-G17-301 revision 3. In fictional decision DEC-G17-301, the owner confirms that the new physical assembly is HOS-G17-302 and that the accepted endpoints remain MAN-G17-301 / S05 and AST-G17-301 / CI2. The register records the new assembly's factory marking and part or revision information separately. HOS-G17-301 is retained as the former object with its previous relationship, rather than overwritten to make it appear to be the replacement.
Closeout compares both new end faces with the accepted mapping and records the final evidence under EV-G17-303 and EV-G17-304. The connection position now resolves to HOS-G17-302, while the old hose's disposition remains linked to the replacement package. Any location card or related connection list identified in the change is reviewed for the obsolete hose ID. The completed case states which identity and history records were reconciled after authorized work; it does not supply a coupling procedure or establish leak-free performance through a label check.
Variations that need explicit history
Some facilities use a durable connection-position identifier alongside an individual assembly ID. Preserve both meanings when that is the approved policy. The position can remain associated with the same two documented equipment connections while different physical hoses occupy it over time. Record the effective event for each association and make the former assembly visibly historical. Without that distinction, an investigation may find a correct connection row but be unable to determine which manufactured assembly was installed during the period being reviewed.
A manifold or endpoint unit replacement can change the parent asset identity even when a connector has the same short name. Review both parent objects and the configuration reference before carrying the hose relationship forward. S05 on a replacement manifold is not a complete endpoint until its new parent identity is established in the record. The worksheet should show whether the change preserved the position reference, replaced the physical parent, or changed the accepted mapping; those are different lifecycle facts.
For identical-looking hose assemblies, keep staging or replacement-package references connected to individual identities. A common part number may describe a type without distinguishing two separate physical hoses. Use the local identity method approved for the application and preserve factory information rather than assuming the part number alone is a unique object key. If the survey cannot distinguish the assemblies from available evidence, record that limitation and obtain the equipment owner's accepted resolution before issuing completed endpoint faces.
Failure patterns and closure checks
Look for endpoint names missing their parent, hose IDs copied from the previous replacement, and role words substituted for exact connectors. Another recurring failure is a correct new label applied while an old active schedule still names the retired assembly. Review the linked record set identified by the change rather than updating only the worksheet in front of you. A useful closeout names the physical assembly, accepted two-endpoint relationship, applicable configuration reference, and the history event that made that relationship current.
Final evidence should distinguish what was observed from what was accepted through records. Keep the original conflicting values, owner decision, and final two-end comparison together. Confirm that both faces use the same current hose identity and that counterpart endpoint text follows the chosen local/fixed-end convention. Record any unobserved endpoint separately and name its required follow-up. Enter the actual completed review date only for the supported scope; a replacement completion notice alone does not establish that every hose label or adjacent connection was reviewed.
Worked example
Example only: invented equipment and port names.
SCOPE: DC01 / H1
HOSE H-004 OEM MARKING: XQ-17
Endpoint 1 MF-02 / S04
Endpoint 2 TRAY-09 / IN-1
Reference Example model HX, routing rev 2
S04 and IN-1 are fictional designations, not Lenovo port names or a connection instruction.
Common mistakes
- Applying one model's hose scheme to another configuration.
- Treating color as the complete endpoint identity.
- Naming the manifold without its connector.
- Reusing a replaced hose's record without history.
Verification
Worksheet: Liquid-cooling hose connection register
| Field | Definition |
|---|---|
| Hose ID | Local identity of the individual hose. |
| Equipment model | Model and configuration governing the diagram. |
| Factory marking | OEM identification preserved as observed. |
| Manifold endpoint | Parent manifold and exact connector designation. |
| Other endpoint | Other parent equipment and connector designation. |
| Role | Documented supply/return role for this connection. |
| OEM diagram | Applicable model diagram and revision. |
| Status | Identity-review state or unresolved detail. |
| Evidence | Observation and equipment-record references. |
| Owner | Team responsible for the equipment configuration. |
| Verification date | Actual date the connection identity is reviewed. |
Filled example row - fictional; no live verification.
| Hose ID | Equipment model | Factory marking | Manifold endpoint | Other endpoint | Role | OEM diagram | Status | Evidence | Owner | Verification date |
|---|---|---|---|---|---|---|---|---|---|---|
| H-004 | Fictional HX / configuration 2 | Example XQ-17 | MF-02 / S04 | TRAY-09 / IN-1 | Example supply | Fictional HX routing rev 2 | Pending endpoint comparison | Fictional EX-17; hose register r2 | Example cooling equipment owner | Not verified (fictional) |
FAQs
Can the local hose ID replace the factory label?
Keep factory identification available. Record the local ID as an additional reference using the equipment owner's accepted method.
Should a replacement inherit the same hose ID?
Follow the site's lifecycle policy and preserve history. Distinguish the connection position from the physical hose when those have separate identities.
Can a part number serve as the hose ID?
Keep the part number as factory or assembly information and check what it distinguishes. If several physical hoses share that part number, the record still needs the local identity or relationship reference required to tell them apart. State whether each field names an individual object, an assembly type, or a connection position.
What if only one hose-end face is readable?
Record that face and its exact endpoint context, then identify the evidence gap at the other end. Do not duplicate the readable face's destination into an assumed mapping. Keep the overall pair unconfirmed until the equipment owner's accepted identification process supports both endpoints and their relationship to the hose.
Should the register change when a connector nickname changes?
Preserve the former wording and record the approved crosswalk to the current designation. Determine whether the change affects only an alias or describes a different connection position. Update affected faces and records through the accepted process without erasing the historical name that older work packages may still reference.
Can the worksheet confirm that a replacement hose is suitable?
No. It records identity, model-specific references, endpoints, and history. Suitability and installation acceptance belong to the applicable equipment and technical review process. Link those controlled references where needed, while keeping the label comparison's conclusion limited to the relationship actually reviewed.
More worked label examples
Two additional ways to apply this guide. Keep the exact identifiers and relationships consistent with your own approved records.
GUIDE 17 / EXAMPLE 1
Label one replaceable hose with exact connection names
Both hose ends retain the hose identity and the exact counterpart connection from a fictional equipment-specific mapping.
SCOPE: DC01 / H1; hose HOS-G17-101
EQUIPMENT REFERENCE: OEM-G17-101 r2, installed model recorded
MANIFOLD END: MAN-G17-101 / SUPPLY PORT S03
DEVICE END: AST-G17-101 / COOLANT INLET CI1
END LABEL FACES
+------------------------------+
| HOS-G17-101 |
| TO AST-G17-101 / CI1 |
+------------------------------+
+------------------------------+
| HOS-G17-101 |
| TO MAN-G17-101 / S03 |
+------------------------------+
MAN-G17-101 / S03 ==== HOS-G17-101 ==== AST-G17-101 / CI1
Role: supply in this equipment map; factory marks retained- Use the connection names on the actual manifold and equipment. CI1 and S03 are fictional references and do not imply compatibility with a manufacturer or hose assembly.
- Check the model-specific identification and placement instructions before selecting a hose marker. Keep the factory markings visible and record any installation or access constraint separately from identity verification.
GUIDE 17 / EXAMPLE 2
Retire a replaced hose while preserving endpoint history
A replacement assembly receives a new hose ID and inherits the verified endpoint relationship through a documented change.
SCOPE: DC01 / H1; change HCH-G17-201
ENDPOINTS: MAN-G17-201 / R02 <-> AST-G17-201 / CO1
OEM REF: OEM-G17-201 r4; role: return in this map
BEFORE FACE: [HOS-G17-201 | MAN-G17-201/R02 | AST-G17-201/CO1]
AFTER FACE: [HOS-G17-202 | MAN-G17-201/R02 | AST-G17-201/CO1]
RELATIONSHIP HISTORY
HOS-G17-201 -> former connection -> retired under HCH-G17-201
HOS-G17-202 -> current connection -> verified EV-G17-201
Replacement assembly: part/revision recorded in REC-G17-202
Old hose labels: disposition recorded with old assembly
New end faces: same HOS-G17-202; reciprocal endpoint text- Apply the identity policy for replaceable assemblies: a new hose may need a new ID even when its endpoints are unchanged. Retain manufacturer part and revision data alongside the facility ID.
- This example records a completed, authorized replacement; it provides no connection or disconnection procedure. Release the current mapping only after the actual endpoints and required handoff evidence are confirmed.
Sources and applicability
- Lenovo: N1380 manifold instructions ↗
N1380-specific hose and manifold identification context; its colors, routing, and procedures do not apply universally.
Read scope and linked guides