Field Service Knowledge Site

Field Service Knowledge Start with the job in front of you A field-work starting point for technicians, dispatch, and technical support. This worked example is set at Northline Utilities, a fictional organization with field crews and central technical support. Use this site to organize approved resources and make the next handoff clear; it does not define operational policy or replace an applicable approved procedure. Choose the job-preparation page for a pre-travel check, the technical reference page to assess source fit, or parts support and escalation when a question remains unresolved. Go to a task Open the page that matches the question you need to resolve. Prepare for a Job Technical References Parts and Equipment Escalation Learning Your work dashboard Your personal work The task card shows your own authorized work when Tasks is available to you. Use the established dispatch channel for crew assignments and shared operational coordination. Your upcoming calendar events Your schedule The calendar shows your own upcoming events. Confirm crew scheduling and work changes through the established dispatch channel. Who owns the work Site content owner Field and Asset Operations Technical interpretation and specialist handoff Technical Support Prepare for a Job Resolve the work context before travel A coordination sequence for technicians preparing to leave base. Before setting out, match the work request to the equipment and location, identify the applicable approved reference, check the relevant parts information, and clarify any unresolved discrepancy with the responsible role. For regulated, safety-critical, or sensitive work, follow the applicable domain-owner-approved local material. Worked example: A Northline technician sees work request “Pump P-204” while the accompanying equipment list says “P-240.” Rather than assume the numbers refer to the same asset, the technician records the mismatch, checks the source and revision shown on the approved reference, and asks the responsible support role to confirm which identifier applies before travel. A practical pre-travel check The example is about resolving a documentation mismatch, not performing technical or safety work. Read the work context Capture the work request identifier, stated location, equipment identifier, and the question the visit is intended to resolve. Match the reference Compare the equipment identifier and stated scope in the approved reference with the work request. Note the source title and revision or currency information displayed. Check the parts question If a part is mentioned, record its identifier and the specific identification or availability question; do not treat a catalog match as confirmation that a part is available. Pause on a mismatch Keep both conflicting values in the handoff. Ask the responsible technical or dispatch role to clarify the work context before relying on the disputed detail. Carry forward the answer Record the confirmed source and next action in the established work record so the next person can see what was resolved. Open the related page Use the next page that fits the unresolved question. Check a technical reference Assess equipment identity, scope, and revision indicators. Resolve a parts question Prepare an identification or availability handoff. Ask for specialist support Structure a handoff when the answer remains unclear. Technical References Check whether the reference fits the work The approved source—not this page—governs technical work. Use an approved technical reference only when its equipment identity, scope, and applicability match the work context. This page explains how to check a reference; it is not itself a controlled procedure. For regulated, safety-critical, or sensitive work, use the applicable domain-owner-approved material for the relevant role and location. If the source is missing, its scope is unclear, or two sources conflict, stop relying on the disputed detail and request clarification from the responsible domain owner or technical support role. Four checks before relying on a reference Record what you checked so a colleague can follow the reasoning. Equipment identity Compare the identifier in the work request with the identifier named by the reference. A similar model or nearby asset is not enough to establish a match. Write down both identifiers when they differ. Do not silently normalize a mismatch. Scope and applicability Read the reference's stated equipment, task, and applicability boundaries. A company-wide page does not establish local or role-specific applicability. Check the scope stated in the approved source. Ask the domain owner when the location or task is not covered. Revision and currency Use the revision, effective-date, or currency indicator provided by the authoritative source. This site does not declare which version is current. Record the title and revision shown. If the indicator is absent or unclear, request confirmation. Conflicting information When two sources disagree, preserve the conflict and get an accountable technical or domain-owner decision before relying on either disputed detail. Name both sources and the conflicting statements. Route the question through the established support handoff. Continue with the right next step Prepare for a Job Use the coordination sequence to capture work context. Escalation and Specialist Support Prepare a handoff for a conflict or unclear scope. Parts and Equipment Support Make the parts question specific Start with the identifier and the discrepancy—not an assumption about availability. Capture the equipment identifier, the part identifier if known, the source consulted, and the exact question. Route identification or availability questions to the responsible parts or equipment support role. A listing or reference does not confirm stock, suitability, or delivery. If the answer depends on technical interpretation, a work-scope decision, or conflicting approved information, use the specialist handoff instead of guessing. Choose the handoff Keep the question within the responsibility of the receiving role; include enough context for that role to respond. Identification or availability question Use the parts or equipment support route for a part-number match, description check, or availability question. Include equipment and part identifiers as shown. Name the source and the specific mismatch or availability question. Ask the support role to confirm the result. Technical interpretation needed Use technical support or the relevant domain owner when the question changes what reference, scope, or equipment interpretation applies. Include both conflicting source details. State what decision is needed before proceeding. Keep the disputed detail clearly marked as unresolved. Related pages Technical References Check source scope and equipment identity. Escalation and Specialist Support Structure a handoff when interpretation or coordination is unresolved. Escalation and Specialist Support Make the handoff answerable Lead with the unresolved question and the decision needed. Include the work context, equipment identifier, source consulted, unresolved question, and action already taken. State whether you need dispatch coordination, technical interpretation, or a domain-owner decision. Use the established support channel for your organization; this example does not supply or promise a response route or timing. For urgent operational or safety concerns, follow the applicable approved local escalation procedure rather than relying on this knowledge site. Route the question by the decision needed A clear owner prevents the same question from being forwarded without context. Separate coordination from interpretation Ask: is the next decision about work timing, assignment, or access coordination—or about what a technical source means? Route coordination questions to dispatch Give dispatch the work request identifier, location as recorded in the work system, the coordination issue, and the decision needed. Route technical questions to technical support Provide the equipment identifier, reference title and revision shown, the conflicting or unclear detail, and what you have already checked. Involve the domain owner when applicability is unclear Ask the accountable domain owner to clarify which approved source applies when location, role, or task scope is not established by the reference. Carry the outcome back to the work record Record the response and next action in the established work record so dispatch and the field crew share the same resolved context. Responsibilities in the handoff Work coordination, assignment, and scheduling questions Dispatch Field Operations Technical source interpretation and specialist routing Technical Support Approved source scope and applicability decisions Domain Owner Field and Asset Operations Learning and Knowledge Sharing Learn from an approved source; raise what it does not answer Use the source for established guidance and the handoff for gaps or conflicts. When a learning resource points to an approved technical reference, check that the reference matches the equipment and work context before relying on it. If the resource is unclear, out of scope, or appears to conflict with another source, record the question and route it to technical support or the relevant domain owner. When the same question recurs, share the pattern with Field and Asset Operations through the established team channel. Include the source, the repeated point of confusion, and the decision or clarification needed; do not create a parallel procedure or mark an unreviewed answer as approved. Choose the right learning response Distinguish a question answered by an approved reference from a gap that needs review. The approved reference answers the question Use the source within its stated scope and retain its title and revision information in the work context. Match equipment and task scope. Use the source's displayed currency indicator. The source is unclear or incomplete Treat the gap as unresolved and ask the responsible technical support or domain-owner role for clarification. State what the source does not answer. Do not turn an informal explanation into a new procedure. The same question keeps returning Raise the recurring pattern with Field and Asset Operations so an accountable owner can assess whether the knowledge resource needs attention. Name the repeated question and affected work context. Include the sources people have consulted. Continue to a source or handoff Technical References Check how to assess source identity, scope, and currency. Escalation and Specialist Support Route an unclear or recurring question to the responsible role.