®Jixing SoftwareYangzhou Jixing Software Technology Co., Ltd

Yangzhou Jixing Software Technology Co., Ltd

Production systems that actually run on the shop floor

We are a software company in Yangzhou, Jiangsu, China. We build production management and data systems for factories in three industries: semiconductor test and packaging, apparel manufacturing, and printing. Not a generic platform — each system is built around one plant’s actual process.

Client names are withheld under confidentiality agreements. Everything else on this site is either verifiable against public company records or a list of modules we have actually delivered.

  • Semiconductor test & packagingWhole-line test production management; CP test-data processing
  • Apparel manufacturingAI document import, fabric and trim, cut-piece bundling, production boards
  • PrintingOrders, production orders, shipping, billing and reconciliation

Systems in production

Apparel manufacturing

Apparel production management system

Export apparel manufacturer, both woven and knit lines

Documents come in through AI fabric-sheet and AI order import; fabric-and-trim management and BOM integration cover materials; production work orders, cut-piece bundling and packing cover the floor; the handhelds cover trim and print/embroidery in and out, bundle pick-up and finished-goods receiving; management sees four boards — order production, cutting, sewing and packing.

How the AI import actually works — what code reads, what the model reads →

Semiconductor test and packaging

CP wafer-sort line management and test-data system

Covers the whole wafer-sort line: receiving → AI parsing and cross-checking of the order → lot creation → process configuration → station check-in and check-out → visual inspection → data conversion → shipping, and on to forwarding and reconciliation. The floor works by handheld scan. Test programs are resolved and downloaded from the bound IP and the current CP1–CP4 station. Desktop tools handle the specialist data and engineering work. Test data from probers and testers is uploaded and backed up, converted, and checked for low yield and anomalies automatically, with alerts pushed to WeCom.

Full module list →

Semiconductor test and packaging

FT final-test packing and shipping management system

Covers the whole final-test line: receiving → order → lot creation → station check-in and check-out → visual inspection → inner box → outer carton → delivery note, and on to forwarding and reconciliation. Shipping labels for all four levels — bag, reel, box and carton — are generated in one pass.

How four label levels stay consistent on a mixed reel →

Printing

Printing production management system

Printing plant running two process lines, sheet-fed and roll

Covers the line from order to payment: customer, paper and roll stock records → order → production order → station check-in and check-out → inner boxes and delivery notes → billing and reconciliation statements. On the floor, handhelds pull up the production order by scan and handle station check-in, check-out and repair. A desktop client at the machine reads the work-order QR code and shows, right there, which order that machine is running and which station it has reached.

Where the rule lives when two customers want different statements →

Module-by-module list of what each system delivered →

Three industries, one capability

Semiconductor, apparel and printing could hardly be less alike. What it takes to get a system running inside the plant is the same in all three:

We go to the floor

For this kind of system the hard part is rarely the technology. How cut pieces are bundled, how a production order moves between machines, when a tester decides to retest — none of that is in the specification. You only get it by standing in the plant and asking.

We understand the process

Every industry we work in has its own rules: how fabric and trim map onto the BOM, which billing lines should merge into one, how yield is counted — and they differ from plant to plant. Turning those into configuration, rather than coding one plant’s version, is what lets a system survive its second customer.

What can be read exactly is not guessed

In document parsing, whatever can be pinned down by table rules and row-column position is not handed to a model to guess. Code reads the data rows; the model only has to recognise the header, which is what differs between customers. Less surface for error, and stable results.

We stay until it is actually running

Go-live is not delivery. The system is running when operators are willing to scan, when the line leader trusts the number on the board, and when the people doing reconciliation accept the document it produces. That stretch is often more work than the development itself.

When a system fails, it is usually not a technical problem

In our experience, production management projects stall for three reasons:

  • The process does not match: a system built from a generic template does not line up with the plant’s real operations, materials and paperwork, so the plant ends up running the system and the paper forms side by side.
  • Nobody wants to use it: every extra scan is extra work for the operator, and if the line leader cannot see a number that is useful to them, data entry stops within weeks.
  • The data cannot leave: yield, cost and capacity are core secrets. Which data stays inside the plant, which may leave, and exactly where it goes has to be settled before the system is discussed — a proposal that cannot answer this is rejected in the first round at many plants.

None of the three is solved by writing code. You have to understand the work on the floor first — which is why we turn each plant’s rules into configuration instead of hard-coding them.

Semiconductor test and packaging

  • Binary prober MAP parsing and validation: per-die bin results are read out and checked item by item against lot number, total tested and good count; a mismatch stops the run and is logged
  • Rule-based treatment of fail dies: the surroundings of a fail cluster, a good die isolated inside failures, GDBN 3×3 weighted scoring, controlled margins around particular bins, and fail regions that persist across a stack of wafers from the same lot. Connectivity is configurable — 8-neighbour including diagonals, or Manhattan distance D=N, a diamond. Rules are applied in order, then merged and de-duplicated before being written back to the map.

Prober MAP files and each fab’s text map files follow no common standard — this part has to be worked through one source at a time.

Full capability list →

Contact

A concrete question works best — which operation you are stuck on, which report does not reconcile, which file format you cannot parse. We are happy to talk technical details before talking business.

Company details can be verified by Unified Social Credit Code in China’s National Enterprise Credit Information Publicity System.Credit code and other company records →