HELLO CHINA

INDUSTRY CLUSTER · Digital commerce & services

Shanghai Changning industrial-internet platforms

To understand Shanghai Changning industrial-internet platforms, first follow order collaboration into port dispatch, then see how vehicle networks reaches the site. Platform, project and company pages support different stages and do not establish customer relations or live trading terms.

Formation and regional foundations

Changning industrial internet serves shop-floor orders, port-vehicle dispatch and automotive software development. A platform becomes dependable only when master data, interface permissions, logs and fault recovery are all traceable.

A Changning industrial-internet project may alter a factory order chain, dispatch port vehicles or support automotive software. Going live depends on data ownership, interfaces, fault recovery and site acceptance rather than the platform name.

Core geography: A Changning platform network across Shanghai Silicon Alley and East Hongqiao linking factory collaboration, port logistics, automotive software and industry services

How an order becomes a traceable site task

How dispatch, vehicle state and acceptance logs close the loop

The diagram follows data flow through autonomous transport and data interfaces; Shanghai Silicon Alley supplies regional context rather than navigation.

  • Order coordination — Order coordination aligns revision, quantity, date and change ownership.
  • Port scheduling — Port scheduling joins equipment, yards and operating windows.
  • Vehicle network — Vehicle networks carry tasks, status, alarms and permissions.
  • Data interface stack — Data interfaces first define master data, events and boundaries.
  • Acceptance log — Acceptance logs retain faults, recovery, operator and timestamp.

01 · 214 firms do not mean 214 equivalent platforms

Application scale, firm tiers and platform objects need separation.

The Changning cluster page reports 214 upstream and downstream firms and RMB 19.447 billion in revenue under its application scope, naming Black Lake, Westwell and Vector among representative actors. Black Lake addresses manufacturing execution, Westwell port-vehicle scheduling, and Vector automotive-electronics engineering tools. Their buyers and deployment sites differ. A regional total places them on one industry map without turning their business models into the same product. Once roles are separated, revenue and products need their own comparable definitions.

Upstream and downstream firms can include hardware, software, logistics and services, while revenue is not necessarily platform subscription revenue. Applying the total to one software product overstates comparability. Hardware revenue, implementation fees, software licences and operations services may all enter the total. Using it to estimate one platform’s market share mixes billing periods and deliverables, producing a ratio that cannot guide procurement. The total is not a valuation for one product.

Screening should create separate columns for factory collaboration, port logistics, vehicle software and industry services, then check legal name, Changning address and delivery object for each actor. Each column should state whether the offer is standard software, an integrated system or engineering service, and which legal entity contracts. Questions can then vary by site scale, interface count and support location instead of using one generic questionnaire. Service period and data ownership are completed by category.

  • The 214 firms and RMB 19.447 billion are application totals spanning hardware, software, logistics and services.
  • Hardware sales, implementation fees, licences and operations revenue cannot be turned into one platform market share.
  • The shortlist uses four columns for factory collaboration, port dispatch, vehicle software and industry services, with contracting entity and deliverable checked for each.

02 · Black Lake follows orders into production

Scheduling, process, reporting and fulfilment data sit around the factory floor.

Black Lake’s site describes orders, process, scheduling and fulfilment, while a Changning page places its headquarters node in the cluster. Company-reported customer counts are not treated as independently audited results. Orders, routings and schedules are different data objects; fulfilment becomes credible only when codes and versions connect. A product description shows direction, while each factory must confirm enabled modules and manually maintained data.

Whether a manufacturing collaboration system works depends on material codes, routings and shop-floor reporting quality. A feature-rich interface cannot compensate for disordered master data. Duplicate material codes or obsolete routings spread errors faster through planning and the shop floor. Cleaning codes, permissions and change procedures before deployment often reduces execution error more effectively than adding another dashboard. Code ownership and approval paths are fixed before deployment.

A pilot should select one product family, record order readiness, plan changes, exception closure and actual cycle, and assign interface responsibility with ERP, equipment or quality systems. The pilot family should include normal orders, urgent work, shortages and rework to expose real variation. Interface faults also need discovery, repair and manual-entry responsibility recorded, preventing a successful demonstration from hiding routine maintenance cost. Pilot closure also checks whether exception backlog is cleared.

  • Black Lake spans orders, routings, scheduling and fulfilment, but each plant must identify enabled modules and manually maintained data.
  • Duplicate codes or obsolete routings spread error into planning, so data ownership and change approval precede dashboards.
  • A pilot product family should face urgent work, shortages and rework, then close interface faults and the remaining exception backlog.

03 · Westwell extends the platform to port vehicles

Vehicles, yards, energy and dispatch create physical constraints.

District records place Westwell in port, rail and inland-port applications, and a public response covers a smart battery-swapping service-platform project. The project page supports only its stated year and scope. Ports, rail terminals and inland hubs all handle logistics but use different lane rules, communications and handling equipment. Battery swapping adds battery condition, charging schedules and safety isolation, so one site cannot simply be copied to another.

A logistics platform handles more than data; roads, parking, container positions, tides and vehicle range constrain it. Algorithm metrics are hard to assess outside throughput and safety rules. Higher throughput is not necessarily an improvement if manual takeover rises or safety buffers shrink. Vehicle scheduling should also track empty travel, waiting, intersection conflicts and weather degradation; an algorithm score is only one measure. Safety right-of-way rules override the shortest route.

Acceptance should record task completion, manual takeover, congestion, energy and recovery, separating responsibility for vehicle hardware, wireless network and platform software. Exception drills can add wireless loss, vehicle failure, an occupied swapping station and temporary road closure, testing safe rescheduling without lost tasks. Time synchronisation, alarm ownership and manual-takeover authority also belong in acceptance. Tasks cannot duplicate or disappear after manual takeover.

  • Ports, rail terminals and inland hubs have different lanes, communications and handling, while swapping adds battery scheduling and isolation.
  • Throughput gained through more manual takeovers or smaller safety buffers is not a reliable dispatch improvement.
  • Drills for wireless loss, vehicle failure, occupied swapping and road closure must show that takeover neither duplicates nor loses tasks.

04 · Vector serves the vehicle-software chain

Networks, testing, calibration and embedded tools differ from factory MES.

Changning records name Vector as a representative sample, while its China site covers vehicle networks, embedded software, testing and calibration tools. Global capability cannot all be assigned to the Shanghai entity. Automotive-network tools can span development, simulation, testing and calibration, but the China team’s actual portfolio and support need confirmation. If an overseas team delivers a global capability, contracting, data transfer and response time differ.

Vehicle-software tools handle communication matrices, diagnostics, bus load and configuration. Factory collaboration platforms handle orders and process execution. Buying departments and acceptance objects differ. Communication matrices and diagnostic databases change by vehicle version, while test scripts follow controller and software baselines. The purchase includes licence scope, updates, data conversion and engineering support, not merely a tool name, and cannot be compared with factory scheduling software.

A requirement should state bus protocol, controller count, software version, test coverage and data format, then confirm the split between local service, licences and global teams. The requirement should separate development seats, automated-test nodes and temporary peak use, and state whether data may leave the customer environment. Global troubleshooting also needs log redaction, access approval and time-zone response defined in service.

  • Vector China’s actual portfolio and support boundary require separate confirmation; global capability does not automatically belong to the Shanghai entity.
  • Communication matrices, diagnostics, bus load and software baselines belong to vehicle development, not shop-floor scheduling.
  • Requirements should state protocols, controllers, software revision, test coverage, seat types and handling of logs across borders.

05 · Black Lake, Westwell and Vector belong in separate quotation columns

Licences, equipment, implementation and continuing service have different boundaries.

Black Lake sits near manufacturing collaboration, Westwell connects vehicles and logistics, and Vector serves automotive software and testing. Changning lists them together without making them one procurement category. All three could serve one manufacturer: shop-floor software for production, Westwell for internal logistics and Vector tools for controller development. That is a possible architecture, not an existing bundle; interfaces and overall integration responsibility need project definition.

Subscription software may price by user or site. Logistics systems can include vehicles and site changes, while engineering tools involve licences and technical service. Total price first needs a boundary breakdown. Software subscriptions depend on users, functions and environments; logistics systems include vehicles, sites and modifications; engineering tools may charge by seat and service package. Separating one-time build from recurring expense is essential for meaningful ownership cost.

Comparison should separate initial implementation, interfaces, hardware, licences, training, maintenance and exit data, then evaluate each against its business measure. Exit data needs format, completeness and migration assistance, while interface cost separates build, modification and maintenance. Hardware life, software upgrades and training frequency belong to their own cycles so a five-year total does not hide dependencies. Each item states exit conditions for renewal or replacement.

  • Black Lake, Westwell and Vector may serve one manufacturer without becoming a pre-existing bundle.
  • Subscriptions, vehicles and site changes, and engineering licences use different prices, with build and recurring costs separated.
  • Comparison lists interfaces, hardware, training, maintenance and exit data, including migration terms at renewal or replacement.

06 · East Hongqiao is a connector, not transaction proof

Resource, application and market matching need later project records.

The establishment page for the East Hongqiao Industrial Internet Innovation Development Centre identifies a matching node for resources and applications, but gives no later implementation or acceptance results. The centre can organise roadshows, matching and joint events so unfamiliar firms meet quickly. It does not make technical commitments for each project; the contracting entity must still define staff, interfaces, schedule and support.

A service centre can reduce the cost of finding partners, but cannot assume supplier responsibility for interfaces, delivery or support. Event counts do not replace operating data from customers. Event activity does not translate directly into operating quality. Effective matching reaches a site problem, data conditions and budget boundary, then names owners and the next validation step rather than ending with an attendance list.

After meeting a firm through the centre, obtain project scope, implementation team, permission for reference cases and acceptance method before entering a pilot. A reference case needs customer permission and context on industry, plant scale and deployed scope; an anonymous major customer is insufficient. Before a pilot, confirm whether the same team will implement it and who can handle critical interface faults on site. Reusable and customised parts of a case are separated.

  • East Hongqiao can introduce supply and demand but does not promise interfaces, schedule or support for the contracting entity.
  • Event counts show contact opportunities; useful matching still needs a site problem, an owner and a next validation.
  • A reference case needs client permission, industry, plant scale and deployed scope; an anonymous major customer cannot support a pilot.

07 · Platform acceptance begins with logs

Workflow, data accuracy and recovery need reproducible records.

Factory, port and vehicle-software platforms generate different logs, yet version, time and responsible party must remain traceable. A district account does not set project acceptance thresholds. Shop-floor logs emphasise orders, operations and equipment events; port logs add vehicle location and task status; automotive tools track software versions and test results. Different fields still need a common clock and an audit trail that cannot be casually overwritten.

A dashboard can hide data delay, manual entry and interface failure. Stable operation depends on locating an exception, rolling back and restoring business. Manual entries need labels and approvers, and interface retries must retain the original failure. Otherwise a smooth dashboard can conceal duplicates or missing tasks. After recovery, business data still needs reconciliation to a consistent state.

A contract annex defines data source, refresh frequency, permissions, downtime window, recovery objective and log retention, then tests them with a real exception drill. A drill can use interface timeout, permission error or database rollback with an observable recovery target. Afterwards, record more than elapsed time: correct alarms, on-call responsibility and escalation paths so the next incident converges faster. Drill findings need an owner and closure date.

  • Shop-floor, port and vehicle-software logs differ, yet all need a common clock, version identity and an immutable trail.
  • Manual entries and interface retries must retain the original failure, or a smooth dashboard may hide duplicates and omissions.
  • A contract annex defines data sources, downtime, recovery and log retention, then tests them through timeout, misconfiguration or rollback.

08 · The 3+1 layout remains an action plan

2028 targets stay separate from the 2025 application figures.

The 2026 action plan proposes a 3+1 layout spanning industrial, aviation and energy internet plus cross-border commerce, with targets for 2028. Industrial platforms centre on process assets and production data; aviation adds flight operations and passenger information; energy involves metering and dispatch; cross-border commerce follows transaction and cross-border data rules. Their placement in one action layout describes development direction, not a claim that the four use one architecture or acceptance method.

Targets show policy direction; they do not mean aviation and energy platforms have equal maturity. Combining target firm counts with application counts would create artificial growth. A target count may include newly formed, relocated or transforming firms, while the application count reflects existing upstream and downstream actors. Without deduplication, dates and a firm definition, subtraction gives neither net growth nor platform maturity.

When reading the plan, mark build, promote and cultivate as future actions, list existing firms and projects separately, and update actual progress each year. Annual review should separately update operating projects, platforms still under construction and cancelled or revised tasks, comparing each with its milestone. This reveals which direction produces usable service and stops obsolete assumptions from carrying forward.

  • Industrial, aviation, energy internet and cross-border commerce operate under different data, regulatory and security boundaries.
  • The 2028 target and application count lack common definitions and deduplication, so subtraction cannot yield completion.
  • Build, promote and cultivate tasks need annual checks of operating, construction, cancellation and revision status.

Sources and reading notes

An industrial-internet project reaches actual use only after master data, interface permissions, fault recovery and site logs pass acceptance and the system runs for the agreed duration. A platform feature list alone does not establish factory use.

  • Shanghai Changning industrial-internet platforms — Upstream and downstream firms in the application account: 214.
  • Shanghai Changning industrial-internet platforms — Revenue in the application account: RMB 19.447 billion.
  • Shanghai Changning industrial-internet platforms — Target year in the three-year plan: 2028.
  • Shanghai Changning industrial-internet platforms — Industrial-internet layout in the action plan: 3+1.

Related companies

These companies have a locally relevant industry role supported by public information. Order is not a ranking, inclusion does not imply authorization, partnership or endorsement, and Hello China does not participate in or guarantee transactions.

A company may request a free correction or removal through the formal channel if its record is inaccurate or it does not wish to be shown. Do not send business licences, authorization letters or other sensitive files through insecure channels.

Sources

Use the original publishers to check dates, scope and definitions; public material is not a transaction guarantee.