Item 1 · Indonesia market positioning & compilation baseline date
🇮🇩 Indonesia Hub · Scenarios & Local Deployment
Connecting Indonesian scenario demand with Chinese embodied-AI solutions: start from public records, verify stage by stage, deliver locally.
Figures are taken live from the indonesia data domain (C0 candidate pool) — public-sourced records only, updating automatically with the data.
Public-data compilation baseline date for the market positioning and statistics caliber on this page: 2026-08-30. The statistics above come from a dynamic public-data pool and change automatically as data updates; evidence status across this page follows the labeled verification dates and authorization statuses.
Item 2 · Post-expo scenario progress funnel
From public records to verified cases (C0→L3)
Every lead starts from the public record pool (C0): curated into a potential scenario (L1), confirmed with the parties (L2), and finally becomes a mutually confirmed verified case (L3). No presupposed demand, no skipped stages.
01C0 Public-data candidate
Public record pool
Public-sourced Indonesia enterprise records (C0), for search and candidacy only, no contact details
02L1 Potential scenario
Scenario lead
Curated into a potential scenario (L1), tagged with industry, region, tasks and conditions
03L2 Contact confirmed
Contact confirmed
Contact established with the parties to confirm the demand is real (L2)
04L3 Verified
Verified
Demand, budget and delivery conditions confirmed (L3), moving to deployment services
Stage caliber: C0 → L1 → L2 → L3 form the demand-verification main chain (C0 public-data candidates, L1 candidate scenarios, L2 contact-confirmed, L3 verified). P0-P2 are verification-execution stages (P0 scope drafted, P1 verification started, P2 acceptance completed), D1 is formal delivery, and R1 is a replicable case. The public layer only discloses stage statuses that are authorized and redaction-reviewed; conversion counts between stages are not published, and no operating-progress targets appear on this page.
Item 3 · Authorized L2/L3 scenario summaries
Verified scenario cases (L3)
Only L3 cases with written publication consent are shown (anonymized summary cards).
Public summaries only show content that is authorized and has passed redaction review; there is currently no authorized L2/L3 scenario summary in the public layer. Nothing is pre-listed here — a summary appears only after written authorization and redaction review are completed.
Item 4 · Key industries & first-batch blueprints
Key Industries & First-Batch Blueprints (Reference)
All four first-batch Indonesia blueprints carry the "reference blueprint" attribute — derived from industry knowledge and public evidence, not tied to any verified demand side; they are not written as projects before L2 demand is confirmed.
Industrial parks serve as the concentrated verification carrier for BP-02 "Unmanned Inspection of Hazardous Areas" and are not set up as a separate item; marine equipment enters the second-batch reserve and will be upgraded only after a clear task, purchasing entity, working conditions and delivery criteria are formed. The four blueprints remain reference blueprints before L2 demand is obtained and do not correspond to any project or case.
Item 5 · Local partner capability network
Local deployment partner network
Local deployment partners are Indonesia-based service providers (integrators, agents and maintenance providers) covering installation, operation, spare parts and training. Cooperation is project-based: the platform curates demand, matches and verifies solutions; partners handle local delivery and after-sales.
- Project delivery: verified solutions are installed, commissioned and maintained by local partners
- Channel and lead referral: partners refer local demand; the platform provides solution matching and verification
Item 6 · Expo enterprise showcase
Expo Enterprise Showcase (Three Solution Enterprises in Phase One)
Relationship types are limited to six labels: public data, expo contact, negotiation in progress, authorized display, verified partner, verified demand; no other relationship wording is used without a written basis. Before written public-display authorization is obtained, only text-only capability cards are published — no company logos, images or material excerpts. The past-expo page (/expo/) remains a historical archive; the "expo contact" label records that contact occurred at an expo and does not imply any relationship between the platform and the expo organizer or the enterprise.
Item 7 · PoC, short-term lease & on-site research entry
Verification first: how paid PoC engagements work (past engagements)
For confirmed scenarios (L2 and above), the platform provides paid PoC (proof-of-concept) services: scope and acceptance criteria are signed before execution. The following is a generic description of past engagements — for illustration only, not a sales entry.
- Campus inspection PoC: several weeks of on-site validation of wheeled/quadruped inspection solutions, delivered with a comparison report and deployment advice.
- Line-tending PoC: validating cycle time, success rate and exception recovery for machine-tending tasks, with clear retrofit boundaries and payback framing.
The above describes service forms only; PoC scope, acceptance criteria and commercial terms are contracted separately after mutual confirmation. This page is for display only.
Besides paid PoC, the verification-first service includes two more entry forms: short-term lease — equipment and solutions enter verification scenarios via short-term leasing, with lease terms agreed after scope confirmation; on-site research — remote or on-site research for L2-or-above scenarios, producing site information and risk lists. Scope and arrangements for both entries are agreed separately after mutual confirmation, and no commitment is made on this page. Common entry: /services/poc/
Item 8 · Data, wording & authorization notes
Data, Wording & Authorization Notes
- Data caliber: every public card shows its source type, verification status and latest verification date; statistics come from the dynamic public-data pool. Valuation, ranking, pricing, production, delivery and financing information must carry a source and date, and is marked "to be verified" until evidence is obtained.
- Wording discipline: relationship wording between enterprises is limited to the six relationship labels (public data, expo contact, negotiation in progress, authorized display, verified partner, verified demand); no wording implying cooperation, purchasing or successful delivery is used without a written basis.
- Authorization rule: public display requires written authorization and is labeled per the granted scope; upon revocation, related public content is removed from the next release package.
- Privacy boundary: this page shows no natural-person means of reaching individuals, budgets, detailed addresses, unpublished project plans or talk records.
Indonesia local compliance & delivery essentials
General guidance for project planning only; specific requirements follow current local regulations and professional advice. No specific regulations are cited on this page.
- Local agent: most B2B deliveries involve a locally registered entity or authorized agent for contracting, customs and after-sales
- Compliance: equipment import, installation and use may involve certification, licensing and personnel qualifications — verify case by case in advance
- Language and culture: contracts, training and documents are recommended in Bahasa Indonesia; respect local processes on site
- Logistics and installation: archipelago shipping times and site conditions (power, space, network) should be part of the delivery plan
Delivery principle: build local service capability first, then execute overseas delivery.
