Electronic Board Design and Manufacturing

What we do

We design and build electronic boards for other companies' products. Every job starts with a definition of need: what the device has to measure, which line it connects to, how it communicates, and in what environment and on what supply it has to run. From that definition we produce the schematic, the board layout, the part list and the firmware that runs on the board. Once the prototype is approved, we move to series production.

Because the team that designs the board also writes the firmware, the boundary between hardware and software never turns into a negotiation. When something goes wrong in the field, the same team looks at both the circuit and the code; you do not have to carry messages between two suppliers to find out which side the fault is on.

Process

1. Need and specification. The quantities to be measured, the communication interface, the supply, the environmental conditions, the mechanical constraints and the expected volume are written down.
2. Schematic and part selection. The circuit is designed; processor, radio, power stage and protection components are chosen with availability in mind.
3. PCB layout. Layer stack, ground plane, power traces, antenna area and test points are placed on the board.
4. Prototype and test. The first boards are assembled and tried on the bench and in the field together with the firmware; the findings are fed back into the design.
5. Series production. Production files are prepared for the approved revision: Gerber data, bill of materials and placement coordinates.
6. Revisions. Throughout the product's life, part changes, trace corrections and firmware updates run through the same file set.

Assembly and production

Prototypes and low-volume work are assembled in our own workshop at Sivas Cumhuriyet Teknokent. In practice this means the first boards and every revision come back on a short loop; a single trace correction does not have to wait for an external schedule. Higher volumes are assembled at partner manufacturing facilities. Volume, board complexity and the delivery schedule decide which route is taken, and that decision is made together at the specification stage.

Example work

For one of the building management platforms we design and produce the PTS IO vehicle access board, the boiler automation device and meter reading devices. In this work the board design, the firmware and the production are ours, while the device reaches the field as part of the customer's own platform.

Our own devices go down the same line. The M-Bus master converters, the RF + GSM collector terminal, the TCP-IP + RS485 input/output control board and the addressable RF fire detection infrastructure were all designed and built in this workshop. The method we apply when we work for other companies is the method we have already tried on our own products.

Scope and limits

What we do not do should be as clear as what we do:

• We do not disclose customer names, product names or specification details, which is why the examples above are unnamed.
• Ownership of the design files and the right to use them are agreed in writing at the start of the job.
• Mechanical enclosure design, mechanical production and on-site installation are not part of every project; if they are needed, we discuss them at the specification stage.
• For products that require certification, the scope of the conformity assessment process and the division of responsibility are defined separately in the contract.

If you have a board or a device in mind, send us your specification, or just a few lines describing what you need, through the contact page.