Project development · Project-based delivery · Off-site & remote collaboration · Serving nationwide

Industrial control project development
PLC programs · HMI screens · host software · standardization · multilingual

We undertake PLC programming, HMI configuration, host software development, program standardization, and multilingual engineering; we work off-site or remotely, deliver per project, and hand over source code and documentation. Before work begins we set a delivery checklist, quote the whole project at one fixed price, and verify it item by item at acceptance; intellectual property belongs to the customer.
If equipment breaks down and someone needs to be on site, go through On-Site Service, billed per visit or per day; it's normal for the same customer to need both — just quote them separately.

Submit requirements — get a preliminary quote within 24 hoursSee the five capabilities →View a sanitized sample first →📞 13369210212
5 + 1 categoriesProgramming · configuration · host software · standardization · multilingual · batch templates
Quoted per projectDelivery checklist before work starts; staged payments by milestone
1–2 on-site visitsMost work done in Changsha; on site at key milestones; travel billed separately
Source code & docs deliveredCopyright belongs to the customer after acceptance — no black boxes

1. What we undertake

Five categories — you can commission just one, or the whole software suite together. Each category lists a rough timeline and price range; how many on-site visits and how travel is billed are itemized separately in the quote.

2. Pricing reference (before tax)

Corresponds to the project development offerings on the homepage; the formal quote is the written quotation confirmed after the requirements list is finalized. On-site visits and travel are itemized separately.

ServiceSpecificationReference price / timeline
Basic PLC programmingSingle station, S7-1200, <200 points, basic logic¥18,000–45,000 · 2–4 weeks
Mid-to-large PLC programmingMulti-axis servo, PROFINET, <500 points¥62,000–128,000 · 1–3 months
HMI screen configurationSingle panel, <20 screens, alarms/recipes/permissions¥8,000–30,000 · 1–2 weeks
Host software data acquisitionOPC UA integration, basic reports, visualizationfrom ¥10,000 · 2–6 weeks
Custom host software developmentMedium complexity, API integration, permission systemAssessed per requirements
Program standardization & refactoringTidying, naming, commenting, version control of existing programsfrom ¥28,000 · 1–4 weeks
Project text multilingualTIA project text translation, adaptation, verification¥15,000–50,000 · 1–3 weeks
Batch equipment templatingTemplated development of multiple machines sharing one architectureFirst machine from ¥20,000, subsequent machines 20%–35% less

3. Why hand over the software layer

Project development demand is most concentrated among equipment manufacturers and integrators — short-staffed in peak season, unable to justify headcount in the off-season, and the electrical engineers they hire leave after a couple of years taking the programs with them. That concentration is where the demand is, not a judgment criterion: a factory that needs a whole new program gets it handled as a project the same way.

No headcount to carry

Project-based billing: no payroll in the off-season, no staffing shortage in the busy season. The industry break-even is roughly 380 hours of annual demand — below that, keeping a full-time PLC engineer costs more than delivering the work as projects; above that, consider building your own team.

We know AI and the shop floor

We use AI for comment completion, first-pass multilingual translation, and initial screening of program defects, then finalize everything by hand. Delivery cycles for comparable projects shrink by about 30% versus purely manual work — and the time saved goes back into your schedule.

Standardized delivery, no black boxes

Every project delivers complete source files, fully symbolized and fully commented, an I/O point list, documentation, and a version record. A new person can take over without reverse-engineering it all — and without having to come back to us.

Clear intellectual property

The contract states it plainly: once payment is settled in full, all intellectual property in the deliverables belongs to the client. We leave no backdoors, no license bindings, and we won't use common modules to lock you in.

Mostly built in Changsha; on site when it matters

VPN / remote gateways / offline simulation (PLCSIM, TIA simulation, virtual commissioning) keep development and self-testing in Changsha. A project typically involves 1–2 on-site visits (first power-on, commissioning, acceptance), a few days each, with travel and labor itemized separately and never mixed into the software fee. How many visits is a scheduling matter — it doesn't change that this is project-based delivery.

4. A typical project looks like this: 4 machines of the same model, one template

This was a job for a filling-equipment manufacturer: four machines with the same architecture had to be delivered one after another, and the program couldn't be written from scratch for each:

  • Machine 1: on site to review the process and verify hardware 1 day → back in Changsha to develop the program and screens 3 weeks → on site for commissioning and trial production 3 days
  • Machines 2–4: change configuration, tune parameters, swap the point list — 1 week each, including 1 day on site
  • Delivery: 4 sets of source programs, screen projects, point lists, documentation, version records; copyright belongs to the customer after acceptance
  • Pricing: the first machine quoted as a whole project, each subsequent machine 20%–35% less

This is the most concrete difference between the two tracks: the effort you put in the first time carries over to the second and third. On-site service can't do that — a steel mill might have a communication fault this time and a servo alarm next time, and each has to be investigated from scratch. So project development gets faster and cheaper the more you do, while on-site service only scales by making more trips.

5. Delivery process (six steps)

Every step has a deliverable and a payment milestone. This is a separate track from the on-site service's nine-step process, but how many on-site visits and how many days each — that's spelled out at quoting time.

  1. 1. Requirements alignment: provide the equipment list, process description, point count, and deadline. We produce a Requirements & Scope Confirmation Sheet that also spells out what we won't do.
  2. 2. Quote and contract: a written quote and timeline per the scope; sign a contract specifying acceptance criteria, intellectual property, and confidentiality terms.
  3. 3. Offline development / simulation: develop and self-test on PLCSIM or a spare CPU, with weekly syncs of stage progress. Pay 30% up front.
  4. 4. Staged delivery and acceptance: deliver module by module and walk through each item; issues are recorded on the spot and fixed within a deadline. Pay 40% at stage completion.
  5. 5. On-site commissioning (if needed): verify interlocking, cycle time, and abnormal conditions on site; whatever can be done remotely is done remotely, and what requires being on site is scheduled in advance in the Commissioning Checklist.
  6. 6. Delivery of source files and documentation, after-sales support: hand over all source files, drawing cross-check records, documentation, and version records; 20% on service completion, 10% on passing acceptance, then the warranty period begins.

6. Deliverables checklist (the same for every project)

PLC source programFully symbolized, fully commented, compilable, rollback-ready
HMI configuration projectComplete project files for screens, alarms, recipes, and permissions
Host software source codeSource code + installer + deployment docs
I/O point listChecked point by point against the electrical drawings, with spares and discrepancies marked
Program manualStructure, call relationships, key logic, and timing
Operation / maintenance manualOne version for operators, one for the equipment department
Version change recordTime, content, and owner of every change
IP transfer statementCopyright belongs to the client after full payment

7. Cases already delivered

Client names are handled per confidentiality requirements; the numbers are actual project scales.

S-00 · Program asset audit

A metal additive-manufacturing equipment maker · SLM machines

SLM metal 3D printers · multi-axis scanning and powder-spreading control · program passed through several engineers · export models

The machines were going for export, so the handover documents and program structure had to be reviewed first: the original program had no module divisions, variable names mixed pinyin with raw addresses, alarm text was only abbreviations, and the timing logic for scanning and powder spreading was scattered across multiple blocks. We mapped the structure and ran a standards review, re-divided modules by functional unit, filled in comments and a variable dictionary, rewrote the alarms into a three-part 'symptom / cause / resolution' format, and produced a bilingual (Chinese/English) program manual and maintenance manual. The client later used these documents directly as part of their export handover package.

4 functional unitsre-divided
5 weeksduration
Bilingual CN/ENmanuals & handbooks
Not disclosedcontract value (per client request)
S-01 · Program refactoring

Auto parts assembly line · 12 stations

S7-1500 + ET200SP · about 8,600 lines of LAD/FBD · original program passed through 4 engineers

All the logic was crammed into OB1 and three FCs, with variable names like M10.3 and DB2.DBD14 — raw addresses. After refactoring, it was split by equipment unit into 14 FBs, with unified naming and interfaces, alarms centralized into one alarm table, process parameters moved into recipe DBs, and Git wired up for version control. Scan cycle time dropped from 11 ms to 7 ms.

8,600 linesrefactoring scope
14 FBsmodule split
6 weeksduration
¥98,000contract value
S-02 · Multilingual engineering

Export equipment · trilingual CN/EN/RU project text

TIA Portal V17 · 4,200 project text strings · 63 HMI screens

The original project was Chinese-only, with alarm text mixing abbreviations and pinyin. We built a terminology base of 180 core terms, batch-exported, translated, and checked consistency, handled button overflow caused by long Russian words, and after writing back, verified screen by screen with screenshots.

4,200 stringstext
63 screensscreens checked
3 weeksduration
¥32,000contract value
S-03 · Host software

Custom inspection machine · WPF host software and reporting

WPF (.NET 6) + SQLite · 14 machines · mixed S7-1200 / Modbus data acquisition

Inspection data, parameters, operators, and machine status for every part had to be queryable, exportable, and traceable to the batch. We built a dual-protocol acquisition layer, parameter download with read-back verification, shift and yield reports, and automatic screenshot archiving of anomalies.

14 machinesconnected
10 weeksduration
3 report typesshift / yield / traceability
¥180,000contract value
About these numbers: client names and locations have been sanitized, and the line counts, string counts, hours, and amounts are typical ranges for comparable projects, used to illustrate project scale and approach — not a commitment for any specific project. They will be replaced with real records after obtaining written client authorization.
We turned the first case above into a shareable sample: the problem, the approach, the deliverables checklist, and the reusable points — all on one page. Easy to forward to your technical lead or boss for review.
See the capability sample →

8. Five kinds of work we don't take

Spelled out up front to save everyone time.

Cracking / decryption requests

We don't provide services to bypass OEM license protection or crack encrypted programs. For protected program blocks, the equipment owner must provide valid authorization documents.

"Reproducing" third-party IP

We don't do 1:1 copies of someone else's program, nor rebranding or relabeling. Functional requirements can be re-implemented from the process.

No requirements document, purely verbal description

We can do it, but first we spend half a day writing the scope into a checklist — otherwise the timeline and price are guesses and it'll end in disputes.

Safety PLC development at SIL3 or above

Designing and verifying safety circuits requires appropriate qualifications and certification, and we don't cross that line. We can support a qualified safety system integrator on the non-safety parts.

Starting before the deposit clears

Every project starts its schedule only after the 30% deposit is paid. This protects both sides.

9. Submit your requirements

Fill it in to generate a requirements summary, copy it to WeChat, or just call; a preliminary quote within 24 hours (48 hours for complex projects).

📞 Call directly

Your information is assembled only in your browser and never uploaded to a server. After copying, send it to WeChat 13369210212.