Skip to content

Control systems for your plant, and the data to see how it runs.

We program PLCs, build operator screens, set up production monitoring and connect the floor to the systems your office already runs. Specified in writing before it’s quoted, and documented so your own engineers can maintain it.

  • Specified before it’s quoted
  • You own the code
  • Documented for your engineers
Plant control systemdiagram
  1. Business systemsERP · MES · reporting
  2. SupervisorySCADA · HMI · alarms
  3. ControlPLC logic · interlocks · sequences
  4. FieldSensors · drives · motors · valves
A plant control system in four layers: field devices, PLC control, supervisory screens and business systems. AutoPeritus works from the control layer up, connecting each layer to the next.
Services

What we do for plants and machine builders.

Most work starts at the controller and moves outwards: to the screens operators use, the data supervisors need and the systems the office runs.

  • PLC & control systems

    PLC programming and machine control

    We write, modify and fault-find the logic that runs your equipment: sequences, interlocks, timers, recipes. Structured, commented and version-controlled.

    For you: Control logic your own engineers can read, change and own, rather than a black box.

  • HMI & SCADA

    Operator screens and alarms

    We design operator displays that can be read at a glance on a long shift, and cut alarm lists down to the ones that need someone to act.

    For you: Operators see the state of the process quickly, and the alarms that matter stand out.

  • OEE & downtime tracking

    Production monitoring

    We read counts, machine states and stop reasons straight from the equipment and put them on a screen supervisors can use during the shift.

    For you: Output and downtime counted by the machine, while there’s still time to act on it.

  • Predictive maintenance

    Condition monitoring

    We collect vibration, temperature and run data from the equipment that matters most and raise a warning when it starts to drift from normal.

    For you: Maintenance gets a chance to plan a repair instead of reacting to a breakdown.

  • OT/IT integration

    Connecting the floor to the office

    We connect machine and production data to your ERP, MES or reporting tools, so an event is recorded once and everything else reads from it.

    For you: The plant and the office describe the same day, without re-keying.

  • We also build the software around the plant

    Internal tools, data dashboards and business process automation, usually where they connect to the industrial work above. If it isn’t something we can do well, we’ll say so.

    • Custom internal tools
    • Data and reporting
    • Business process automation
    • AI-assisted tools
    Ask us about it
About

An automation business built around the plant floor.

AutoPeritus is an industrial automation services business based in Kuala Lumpur, Malaysia. We work on the control side, the PLCs, operator screens and plant data, and on the software that connects it to the rest of the business.

Peritus is Latin for experienced, tested by practice. That’s the standard we hold the work to: logic that’s been tested before it runs your equipment, and documentation good enough for someone else to maintain it.

Where the work applies

  • Manufacturing

    Discrete and assembly lines, packaging, machine builders.

  • Process plants

    Pumps, tanks, dosing and batch processes.

  • Utilities and facilities

    Pumping stations, water treatment and building plant.

  • Warehousing and logistics

    Conveyors, sortation and material handling.

Why work with AutoPeritus

  • Controls and software, designed together

    The logic on the machine and the software above it are designed as one system, so the join between them isn’t somebody else’s problem.

  • Specified before it’s quoted

    We agree in writing what it has to do, what it connects to and how we’ll know it’s finished. That document is what you hold us to.

  • You own what we write

    Programs, screens and code are yours, with the notes explaining why they’re built that way. No licence on your own logic.

  • Built to be handed over

    Structured, commented work your own engineers can pick up. Keeping us on should be a choice, not a requirement.

  • Safety and security kept in their place

    Machine networks are kept separate from office networks. Safety functions stay in hardwired and safety-rated systems, not in standard PLC logic or software.

  • Straight answers

    If what you’re asking for isn’t possible with your equipment or network, you’ll hear it during design rather than at commissioning.

See how we work

Control logic you can inspect before you call.

The ladder logic below is drawn by a PLC simulator we built: a real scan cycle, timers, counters and machine models, with programs tested against written requirements. It powers AutoPeritus Learn, our training course.

  • Seal-in start/stop with a normally closed stop and overload, the way it’s wired on site
  • A no-flow alarm built from a timer, so a pump can’t run dry unnoticed
  • Course challenges are graded on the server against test scenarios, some of them hidden

This is a demonstration and teaching tool, not a client project, and the simulator is not a safety PLC or vendor software.

Explore the simulator in AutoPeritus Learn
RUN · PumpStation · online
0001P-101 start/stop, seal-in
START_PBStartStartPUMPPump P-101Pump P-101STOP_PBStop (NC)Stop (NC)OL_OKOverload healthyOverload healthyPUMPPump P-101RUN_LAMPRunning
0002No flow 5 s after start
PUMPPump P-101Pump P-101FLOW_OKFlow switchFlow switchTONT1PT 5 sET 0 msQ
0003Raise the alarm
T1.QFAILNo-flow alarm
How we work

Nothing gets quoted before we understand it.

Five stages, and each one produces something you keep whether or not you carry on with us. Most automation projects that go badly were mis-specified long before anyone wrote a rung of logic.

  1. 01

    We look at it with you

    We walk the process, read the existing programs and drawings, and talk to the people who run and maintain it. They usually know exactly what’s wrong. No proposal before this part.

    • What you have now, written down
    • Risks and constraints
    • How it runs today
  2. 02

    We agree what it has to do

    A written specification in language you can check: what it does, what it connects to, what happens when something fails, and the tests that mean it’s finished.

    • A specification you can read
    • Interfaces and I/O
    • Agreed acceptance tests
  3. 03

    We build and test it

    Logic and screens are built and tested off-site against the specification, with something you can review along the way rather than a long silence and a surprise.

    • Programs and screens under version control
    • Off-site test records
    • Regular reviews
  4. 04

    We commission it

    On site, tested against the acceptance criteria from stage two. Operators and maintenance staff are shown the system on the real equipment.

    • Site acceptance records
    • Operator and maintenance handover
    • As-built documentation
  5. 05

    We hand it over properly

    Support after go-live is agreed up front. If you’d rather run it yourselves, you get everything needed to do that.

    • Agreed support arrangement
    • Source and documentation
    • Help when something changes
Discuss a project

Tell us what the plant needs.

A sentence or two is enough to start. You don’t need a specification or a budget worked out. That’s what the first conversation is for.

What happens next

  • Your message comes to an engineerNot a sales team, and not a mailing list.
  • We reply to you directlyWith questions, or to suggest a call or a site visit.
  • No quote until we understand itWe won’t price work we haven’t looked at. An NDA is fine if you need one first.

Usually quicker for a site question.

Roughly what area?

Plain English is fine. A rough description beats a polished spec.

A range is fine.

No mailing list. We reply to you, and only about this.

Training

Building your own automation skills?

Alongside client work, we run a PLC programming course and a free skills assessment for people working in, or moving into, industrial automation.

Learn

AutoPeritus Learn

A ladder logic course from zero: nine levels, interactive lessons, a working PLC simulator, troubleshooting challenges and industry-style projects. For apprentices, technicians and engineers. Included with AutoPeritus membership.

SkillScan

A free technical assessment across sixteen automation competencies. About twenty minutes, no account needed. You see what your answers support and get a roadmap through the course.