San Francisco NDT Reports for Cable-Car Sheave Exchanges

An exchangeable machinery assembly has two histories: where it has been installed and what has happened to the physical item. A sheave removed from one location may go through workshop refurbishment and later return as a spare at another location. If its NDT report is named only after the original street vault, the evidence can become detached from the assembly. A useful San Francisco workflow preserves both the component identity and its confirmed location relationships.

SFMTA’s Cable Car Sheaves Upgrade Project and Cable Car Gearbox Rehabilitation Project provide public examples of local machinery maintenance context. They do not establish the fictional examination scope used in this guide, a universal NDT schedule or an endorsement of NDT Connect. The guide concerns report organization for exchangeable machinery, not instructions for maintaining or operating the real cable-car system.

The free editor supports user-entered examination information, DOCX and XLSX table imports with preview and editing, and browser-local PDF download. A free verified account adds private saves, report search, sequential numbering patterns and issued revisions. The product does not determine the condition of a sheave, authorize a rebuilt assembly for installation or update an operator’s asset system automatically. It helps keep the evidence chain readable for those responsible decisions.

Use the organization’s controlled physical identifier for the sheave or assembly, then record its installed position as a separate relationship. A location can retain the same operating label through several exchanges. The assembly identity should remain stable as it moves. This allows a reviewer to find the component’s examination history without mistakenly applying the old occupant’s report to the unit currently installed in the same vault.

Record movement events from authorized source information. Removal, workshop receipt, storage and installation are not interchangeable dates. A report may reference those events without claiming that the examination team witnessed all of them. Preserve the issuer or record reference that confirms the relationship. If the installation identity is not yet known, keep the report tied to the physical assembly and add the confirmed location mapping later.

Avoid changing the report number whenever the assembly changes location. The report number should identify the document, while the location history explains where the hardware went. A stable number with clear asset fields is easier to trace than a number whose embedded street or vault label becomes obsolete. The receiving team can still search by location if the confirmed reference is retained in the appropriate descriptive fields.

A rebuilt assembly may retain its main identity while bearings or other replaceable elements change. Record the scope at the level actually examined. A report on an accessible shaft feature should not appear to cover every newly installed part. Likewise, a supplier document for a replacement bearing is not an NDT report on the sheave structure. The handover index should show how these records relate without combining their technical meanings.

Where the organization controls individual part identities, retain them alongside the parent assembly. If it controls a replaceable element through a work order or supplied lot reference instead, preserve that authorized relationship accurately. Do not invent serial numbers for convenience. The record should reflect how the physical parts are actually identified and which evidence supports the rebuilt configuration that is being handed over.

Be especially careful when parts from several removed assemblies are handled together. A shared workshop batch or cleaning tray does not establish which part belongs to which parent. Resolve the identity relationship before merging examination rows. If the relationship cannot be confirmed, record the uncertainty and direct it to the responsible coordinator rather than assigning a plausible parent merely to complete the document.

Disassembly can make surfaces accessible that were not visible in the installed arrangement. State the actual condition at examination and identify the relevant feature locations. A report prepared in the workshop should not imply that the same coverage was achieved while the assembly was installed. Conversely, an installed observation may describe a condition that changed during cleaning. Preserve the distinction so a later reader can understand what evidence belongs to each stage.

Use stable feature references rather than relying only on the orientation of the item on a bench. The assembly may be turned several times during work. A controlled sketch, drawing view or authorized feature label can identify the examined area without assuming that top and bottom remain constant. The reporting author should confirm the supplied location description rather than invent a coordinate system that cannot be reconciled with the operator’s records.

If preparation removes or changes a surface condition relevant to the original observation, retain the before and after records separately. Do not replace the incoming description with the cleaned condition as though the first event never occurred. The responsible technical team decides how the findings affect the work. The report’s job is to preserve the sequence and scope, not to manufacture a repair conclusion from a tidy-looking final photograph.

Record the method, procedure revision and acceptance basis supplied for the assignment. The report template’s method selection does not establish that a technique is suitable for every material or component in the assembly. The responsible organization determines applicability and personnel authorization. If the received instruction does not match the identified item or condition, retain the question before issuing an evaluation rather than applying a familiar criterion by habit.

Separate the examiner’s observations from the authorized evaluation where those are distinct. A finding location, a dimensional value and an acceptance decision should not be compressed into one unexplained status. The receiving reviewer needs to understand the evidence and the basis used to evaluate it. If a required basis is missing, the report can remain a clear draft with an open technical question; it should not invent a threshold to make the form appear finished.

A completed NDT report contributes to a refurbishment packet but does not itself authorize installation or cable-car operation. Other records may address assembly, adjustment or functional checks through the operator’s process. Keep their references separate and attribute any overall disposition to the actual responsible issuer. The product does not combine individual documents into an automatic readiness decision.

A workshop workbook may list several removed assemblies and the spares intended to replace them. Before importing an XLSX table, confirm whether each row describes a removed item, a rebuilt item or an installed position. Those categories can appear beside each other in an exchange plan. A row labeled replacement should not inherit the removed assembly’s examination results simply because both rows refer to the same street location.

In the import preview, retain the parent assembly identifier, relevant subcomponent reference, actual stage and original report number. For DOCX tables, bring necessary scope context into the report fields if it appears outside the selected table. The editor supports restructuring the table; it does not promise identical Word layout. Use clear columns so a recipient can distinguish the physical item from the location it is intended to serve.

Check shorthand carefully. Ready, received and complete can mean different things in workshop and operating records. Use the actual defined status and identify its source rather than converting every positive-looking value to accepted. Review units and date meanings as well. A receipt date or rebuild completion date is not necessarily the examination date. The imported report should preserve these distinctions instead of flattening them into one apparent event.

A refurbished spare may spend time in storage before installation. Keep its examination reference tied to the physical assembly during that interval. The record should state the event it describes, not imply a continuously updated condition simply because the PDF is available in the account. Any later condition assessment or additional work belongs to its actual event and the responsible organization’s requirements.

If the intended destination changes, update the confirmed location relationship without rewriting the examination scope. The assembly may have been examined before any final destination was assigned. That is a legitimate sequence when described accurately. Do not create a false impression that the original examiner evaluated a particular installed arrangement that did not yet exist. Preserve the workshop scope and keep later installation evidence separate.

When a spare returns to the workshop after another period of use, connect the new event to the same persistent identity while retaining the new installed-history reference. This creates a useful chain through repeated exchanges. A series of disconnected location-named reports would force the reviewer to reconstruct that history manually and increase the chance of confusing one assembly with another that occupied the same position.

Imagine fictional assembly SF-EX-A12 removed from vault position LOC-EX-4. Refurbished spare SF-EX-A27 is intended to replace it. The exchange workbook initially lists the location tag beside the incoming report for A12. The author separates the two physical identities and records A27’s own applicable evidence. The familiar location label remains useful, but it no longer creates the false impression that the installed spare was examined under the removed assembly’s report.

During refurbishment, A12 receives a replacement part documented under work reference WR-EX-9. The author retains the main assembly identity and identifies the changed configuration separately. The workshop examination scope refers to the actual accessible features and stage. A future destination for A12 remains unassigned, so the report does not invent one. Its evidence stays searchable under A12 while the spare-pool and installation records develop independently.

The coordinator can now follow the removed unit, the installed spare and the rebuilt configuration without mixing their records. This example is fictional and does not describe SFMTA’s actual procedures. It illustrates a recordkeeping problem common to exchangeable machinery: a stable operating location can conceal a changing physical population unless the examination packet deliberately retains both identities.

An operating complaint can explain why an assembly was removed, but it is not itself an NDT finding. Retain the supplied symptom or maintenance reason as context and identify its source. The examination report should state what the actual examination established within its scope. Do not infer a cause from the complaint alone or claim that a particular indication explains the operating behavior without the responsible technical assessment.

The same caution applies after refurbishment. A later functional observation should not be entered as proof that every material concern has been resolved. Keep the operational check and the component examination as related but distinct records. This gives the maintenance reviewer a more useful evidence set than a single broad statement that the assembly is fixed, whose meaning may be unclear to everyone outside the original workshop discussion.

A workshop may issue a combined document for several sheaves while the operator wants a separate packet for each assembly. When separating the information, retain the original combined-report reference and the rows that actually apply to the selected unit. Do not copy a general conclusion onto every individual packet without checking its stated scope. A batch document can contain exceptions or limitations that apply to only one item.

Keep the parent report relationship visible in the new document. The separate packet is a presentation of identified source evidence, not a newly performed examination by the person who divided the files. Identify the original issuer and distinguish any new editorial clarification from the original finding. This is especially useful when a spare moves to another location and its recipient receives only the individual packet rather than the complete workshop batch.

Check the physical labels and digital file names together before delivery. A correctly written report can still be attached to the wrong crate or inventory entry. The reporting tool cannot verify that custody relationship automatically. Use the organization’s authorized dispatch information to confirm which assembly the document accompanies, and retain an explicit question when the mapping remains uncertain. A small reconciliation at that point prevents a later location change from magnifying an already incorrect record association.

The downloadable worksheet contains fictional examples of assembly, location and rebuild relationships. Use it to identify exactly what the next custodian needs: confirmation of a physical identity, a replacement-part reference or an applicable examination report. Assign each question to the party able to answer it. A broad request for all documents is less actionable than a precise request tied to the assembly and stage involved.

The equipment tracker can organize user-entered asset and instrument references; the calibration reminder and certificate manager can support dates and qualification-document organization. They do not authenticate the operator’s asset register or establish examiner authorization for the assignment. Confirm those matters through the responsible organization. The free tools support record preparation while the real evidence and technical authority remain with the people who supplied and reviewed the work.

Review the exported PDF against the confirmed exchange and rebuild records. Check that removed and replacement assembly identities cannot be confused, and that the relevant event dates and scope limits remain visible. Authorized company or client PNG and JPEG logos can be included, but should not imply operator approval or affiliation. Confirm the actual handover recipient separately because private saving does not automatically send the document to a transit operator.

A free verified account provides private drafts, report search, sequential-number patterns and immutable issued versions with revisions. Explain whether a revision corrects a location mapping, adds a replacement-part reference or records a later event. Keeping those changes explicit gives the next custodian a durable record of the physical assembly rather than a document that becomes obsolete as soon as the spare is exchanged again.