The first useful outcome of an automation discussion is a shared understanding of the work. Which machine is involved, what problem needs attention, and which function will be delivered? Clear answers provide a common basis for technical review, electrical panel requirements and software work.

Machine manufacturing, electrical panel manufacturing and industrial automation belong in the same project discussion. Mechanical requirements, electrical interfaces and control behaviour need to align. You can begin with the following six topics before preparing a detailed specification.

1. Identify the need and the first unit

Start with a particular machine or auxiliary unit rather than a broad request for “line automation”. Is this a new build or a modification to an existing machine? Describe the observed problem and the intended business outcome in your own words. Explaining when a problem occurs can be more useful initially than stating a capacity target that has not been measured.

2. Share the mechanical and process boundaries

Product dimensions and weight ranges, direction of movement, available space and cycle steps all affect the scope. Review these inputs with the team responsible for the mechanical design. A relevant drawing or a simple flow diagram may be sufficient at first; the entire project archive is not needed. Identify values that are still unknown.

3. Separate panel work from field connections

Will the existing panel remain, be modified or be replaced by a new panel? List the motors, drives, sensors and actuators. An input/output, or I/O, list can describe each signal, its direction and its function. If channel addresses, electrical characteristics or cabling responsibilities are unknown, record the information gap and its owner rather than treating them as settled.

4. Describe the expected control behaviour

Define manual and automatic modes, conditions for starting and running, operator displays and alarm requirements. If the machine communicates with an upstream line or plant system, specify the information exchanged. Controller details, software versions and the rights to use existing project files can then be clarified. Describe the required function before assuming a particular brand or programming language.

5. Make acceptance observable

Turn “the system will work” into testable scenarios. What state is expected for a given input, where will the result be recorded, and who will assess it? Speed, load and timing limits must come from project requirements. Functional testing does not replace an assessment of overall machine safety or process performance.

  • Example signal: product present; direction: field to controller; channel and electrical characteristics: to be defined for the project.
  • Example sequence: ready status → evaluation of defined operating conditions → the conveying step specified by the machine builder.
  • Example acceptance: compare the expected and observed states; no numerical acceptance threshold has been set.

6. Agree responsibilities and handover documents

Assign responsibility for mechanical work, electrical panels, control software, site installation and testing. Show included and excluded work together. The agreed handover may include electrical drawings, an I/O map, a functional description, software versions, backups and operating documentation. Clarify licensing and source-file delivery separately; unrestricted transfer of every file should not be assumed.

Close the discussion with one next action: sharing a missing drawing, reviewing a scope summary or arranging a second technical discussion. This brief is not a quotation with an agreed price or delivery date.

Frequently asked questions

Can we discuss the project before choosing a PLC brand?

Yes. The first discussion establishes functional and interface requirements. Hardware and software choices can then be assessed against the existing system and project conditions.

Which documents are needed for the first discussion?

A short description of the need, a relevant unit or layout drawing and any available equipment list are a useful start. Source files are requested only as needed, with the right to share them confirmed.

Does a functional test provide safety approval?

Not on its own. Risk assessment, mechanical limits and safety functions need separate consideration by the responsible project specialists.

Do these six topics constitute a quotation?

No. The brief supports scope development. Price, payment, delivery and acceptance terms are established separately through technical and commercial review.

Let’s define your project scope

Bring your machine, panel and control requirements into one discussion. Explore our industrial automation service or send a short brief through the project enquiry form. A general capabilities overview is also available as a Turkish or English PDF.

English technical overview (PDF) · Türkçe teknik tanıtım (PDF)