What to define before an on-site engineering assignment
A technical issue is easier to assess when its symptoms, the affected system and working conditions are understood. Preparing that context helps establish useful scope.

Describe the need and system state
Explain what happens, when it occurs and the expected behaviour. State whether the need concerns a fault, an incomplete integration or verification of a modification. Separate observed facts from hypotheses and describe checks already performed.
Identify available documentation
Identify relevant schematics, drawings, software versions, specifications and previous reports. Do not send them through an open form: state their availability and agree a sharing channel. An incorrect revision can lead to a misunderstanding of the configuration.
Define boundaries and responsibilities
Agree who authorises access, checks and any modification. Safety conditions, permits, resources and competencies need to be established before intervention. Requesting support does not itself authorise changes to equipment or processes.
Agree how the result will be verified
Link the objective to a defined check of a function, interface or requirement. Depending on scope, records may include test conditions, observations, results and open items. A partial test should not be presented as full system validation.
Prepare the assessment
Provide the location, requirement, requested date and technical contact. ASSEL GROUP will review the information to assess diagnostics, integration or functional verification within an agreed scope. Availability and scheduling are established after reviewing the context.