When a machine installed in Turkey needs electrical or automation support, the manufacturer may be located thousands of kilometres away. The end user wants production restored, while the OEM needs reliable observations from the machine. A local field visit can connect these two needs, provided the work is clearly prepared. It should begin with a defined scope, available documents and a named contact on each side.

Farad Otomasyon provides industrial electrical and automation services and can discuss local field support requirements with international machine manufacturers. The company is based in Şekerpınar, Çayırova, Kocaeli, with a focus on the industrial areas around Tuzla, Gebze and nearby locations. Availability, travel, technical scope and required equipment are agreed for the particular request. A service enquiry does not create a distribution or stocking commitment.

1. Describe the machine and the reason for the visit

The machine model, serial number, production function and installation location should be provided first. A request such as “the machine is not working” leaves too many questions open. Does the HMI report an alarm? Is the problem present in every cycle? Did it begin after maintenance, a product change or a component replacement? Initial observations help define the visit without assuming a cause before the machine is examined.

The current operating condition should also be explained. The machine may be completely stopped, running with intermittent faults or waiting for commissioning. These situations require different preparation. The OEM and customer should distinguish their observations from conclusions. A suspected faulty drive, for example, is an investigation point until appropriate checks support that diagnosis.

2. Establish the roles of the OEM, local team and end user

The manufacturer may provide the original engineering knowledge and software, the local service team may carry out agreed field checks, and the customer may supply access and production materials. These responsibilities should be written down before travel. Decisions involving design changes, software ownership or production release need the appropriate responsible people. A local service visit should not leave these responsibilities unclear.

A named technical contact is more useful than a large message group with no decision owner. The team should know who can clarify a drawing, approve an agreed change, provide a product sample and accept a service report. If interpretation is needed for a meeting or document, it should be planned rather than assumed. Clear communication helps the visit remain focused on the actual machine requirement.

3. Prepare the technical package

Useful documents include the electrical drawing, device list, relevant project files, alarm description and previous service records. Their revision status matters. An old drawing may not represent changes made at the customer’s factory. The technical package should identify known differences, unavailable files and access restrictions. Missing information can increase the investigation time and should be visible in the agreed scope.

• Machine identification and installation address.
• Control hardware model information and relevant software versions.
• Electrical drawings and available PLC or HMI project files.
• Alarm records, observed symptoms and previous interventions.
• Required tests and the expected service deliverables.
• Site contacts, access arrangements and production availability.

4. Separate fault investigation from a confirmed repair scope

For an unfamiliar machine, the first visit may be an investigation. It can produce findings, measurements within the agreed scope and a proposed next step. It does not automatically mean every repair can be completed during that visit. A replacement part, source project or additional specialist may be required. This distinction should be understood before a fixed completion date is promised.

Where the fault and required work are already established, the repair visit can be prepared more specifically. The replacement device, documents and acceptance method should be checked against the actual application. Similar appearance or a matching power rating alone does not establish compatibility. The OEM’s requirements and the machine’s technical conditions must be considered by the responsible engineering personnel.

5. Coordinate remote engineering without uncontrolled changes

Remote discussion with the OEM can help explain the machine sequence and review observations from the site. Any access method should follow the customer’s information security rules and the agreed project arrangements. Field support does not imply unrestricted access to the factory network. Credentials and project files should be exchanged through approved channels with the authorised recipients.

Software changes should have a documented purpose and a known test plan. The previous available state and the delivered revision should be recorded as the scope allows. A screenshot of the machine working is useful evidence, but it is not a complete software handover. The customer and OEM need to know which changes were made and which functions were tested.

6. Agree on the testing conditions

A machine may need customer materials, mechanical readiness or assistance from a production operator before testing can begin. These prerequisites should be listed. If they are unavailable, the service report should state what could not be tested and why. An untested function should not be marked as accepted simply because the electrical work has been completed.

Functional tests, product quality checks and safety assessments are related but distinct activities. Safety functions must be addressed by competent personnel according to the machine risk assessment and applicable technical requirements. This guide is a planning document, not a substitute for machine safety engineering. Production release remains a decision for the relevant responsible parties based on the actual findings.

7. Use a service report that supports the next decision

The report should identify the machine, date, request, observations, agreed actions and test results. It should also list open items such as missing documents, parts to be supplied or another test under production conditions. Photos can support the report when the customer permits them. Confidential production information should not be included unnecessarily.

A useful handover answers three questions: what was done, what was demonstrated and what still needs attention? This format helps an OEM decide whether another engineering action is required and helps the customer continue the follow-up locally. Where project files or parameter records are part of the agreed delivery, their names and revision details should be connected to the service report.

Frequently asked questions

Can a visit be arranged without a distributor agreement?

A defined field service or commissioning request can be discussed separately from distribution. Stock, sales targets and commercial representation should not be assumed as part of a technical visit.

Can all issues be solved remotely?

No. Some requests require on-site inspection, appropriate measurements or physical work. The available information determines whether remote coordination is useful and what still needs a site visit.

What should we send to Farad Otomasyon?

Send the machine identification, location, fault description, available documents and requested outcome. Farad can then discuss the local electrical and automation support scope. Use the contact card below to start the conversation and the map to find the company location.

Farad Otomasyon ile iletişim ve konum

Cep / WhatsApp: +90 554 667 05 04 · WhatsApp üzerinden arıza bilgisi gönder

Adres: Şekerpınar Mahallesi, Muhsin Yazıcıoğlu Caddesi No:96/C, 41420 Çayırova/Kocaeli. Yol tarifi