Inaportnet: a 264-port single window that is about more than go-live counts
Solution case studies are scenarios based on common industry problem patterns. They do not refer to any client and are not MarkasDev project portfolio items. Our client portfolio is published separately.
Industry context
Inaportnet is run by Kemenhub, not MarkasDev. Figures on this page are cited from official releases and publicly available regulations. Inaportnet is Indonesia’s electronic single-window system for ship and cargo services at ports, run by the Ministry of Transportation (Kemenhub) through the Directorate General of Sea Transportation. MarkasDev did not build, integrate, or operate Inaportnet, LNSW, or the National Logistics Ecosystem (NLE). This page is not our portfolio. We read Kemenhub/Dephub releases, ANTARA reporting that quotes the Director General of Sea Transportation, JDIH metadata for Ministerial Regulation PM 157/2015 and its replacement PM 8/2022, and the text of PM 157 from a regulation repository, to unpack how a national port single window scales.
According to JDIH Kemenhub, PM 157 of 2015 on the Implementation of Inaportnet for Ship and Cargo Services at Ports was enacted on 13 October 2015 and took effect on 21 January 2016 (later amended by PM 192/2015 and repealed by PM 8 of 2022 on Procedures for Ship Services through Inaportnet). The text of PM 157 defines Inaportnet as an internet/web-based electronic single-window that integrates standard port information systems to serve ships and cargo across agencies and stakeholders, and names six initial ports: Belawan, Tanjung Priok, Tanjung Perak, Makassar, Tanjung Emas, and Bitung.
A Dephub release (25 November 2023) states that from the 2016 launch of port-service digitalization through Inaportnet until that date, 264 ports had committed to implementing the system. ANTARA (18 January 2024) quotes Director General Capt. Antoni Arif Priadi that Inaportnet was implemented at 264 ports — described as all ports in Indonesia — including Tersus, TUKS, and port business entities (BUP). A Kemenhub release (16 July 2024) restates coverage of 264 sea-port technical implementing units (UPT) and integration with other licensing applications through the National Single Window Institution (LNSW), especially at 46 ports.
This case matters for logistics leaders, port operators, freight forwarders, port SOEs, and government digital teams weighing single-window designs, cross-agency integration, and IMO Maritime Single Window obligations. The hard problem is not “building a ship-form portal”; it is aligning arrival–berth–cargo handling–departure processes with Customs, Immigration, and Port Health, embedding them in the NLE, and keeping SOP, helpdesks, and transparent non-tax revenue (PNBP) reporting healthy as coverage grows from six starter ports to hundreds of UPTs.
Problem
Before electronic single windows were widely used, ship clearance at ports often meant separate queues and bilateral coordination across agencies. Friction on arrival permits, berthing, cargo operations, or departure lengthens time in port — and for containers, dwell time. Kemenhub (16 July 2024) explicitly links smoother ship arrival, cargo handling, and departure to how long containers stay in port. That is not “only an IT issue”; it is waiting cost, demurrage/detention exposure for business, and pressure on national logistics competitiveness that Minister Budi Karya Sumadi highlighted in 2023–2024 releases.
Institutional fragmentation makes the friction worse. Ship services touch Customs, Immigration, Port Health, and port business entities. Without a shared channel, businesses re-key data, officers work from silos, and oversight is hard to audit. ANTARA and Kemenhub (June 2023) stress that Inaportnet integrates those stakeholder services and sits inside the NLE and LNSW’s push for single submission, single processing, and single synchronizing and decision making — a context sharpened by the IMO Maritime Single Window obligation from 1 January 2024 (Facilitation Committee session 47, cited by Kemenhub and ANTARA).
On the state side, orderly transactions and service transparency also touch revenue. Dirjen Antoni (ANTARA, 18 January 2024) places port digitalization in a governance-cleanup frame supported by Stranas PK, while showing harbour-service PNBP rising from Rp2.2 trillion (2020) to Rp2.9 trillion (2023). Rising PNBP is not automatically “purely because of Inaportnet” — ship volumes, tariffs, and the wider economy also matter — but the official narrative links digitalization to faster, more efficient, transparent, competitive processes, logistics-cost cuts, and higher PNBP.
Indonesia’s geography adds load: hundreds of UPTs, newly split ports, Tersus/TUKS/BUP sites, and staged go-lives. Dephub (25 November 2023) records a 2023 digitalization target of 151 ports with 155 realized (including four pemekaran ports) across three go-live stages, plus Capt. Antoni’s instruction that committed ports must have SOP and a helpdesk. Without disciplined Operate, “go-live” only moves the queue from a physical counter to a ticket backlog.
Constraints
- Legal base: PM 157/2015 (enacted 13 October 2015; effective 21 January 2016) on Inaportnet implementation; amended by PM 192/2015; repealed and replaced by PM 8/2022 on ship-service procedures via Inaportnet — JDIH Kemenhub
- Public definition (PM 157): internet/web-based electronic single window integrating port information systems for ships and cargo; domain named in the regulation text: http://inaportnet.dephub.go.id — PM 157 text via Klaussa/repository
- Initial six ports under PM 157: Belawan, Tanjung Priok, Tanjung Perak, Makassar, Tanjung Emas, Bitung
- Coverage 2023–2024: 264 ports / 264 sea-port UPTs committed or implemented per Dephub (25 Nov 2023), ANTARA (18 Jan 2024), and Kemenhub (16 Jul 2024); Tersus, TUKS, and BUP also said to apply it (ANTARA)
- 2023 wave: target 151 ports digitalized; realized 155 including 4 pemekaran; three go-live stages; stage III adds 66 ports (examples: Namrole, Ampana, Paloh, Gilimanuk, Masalembu) — Dephub 25 Nov 2023
- June 2023: +40 ports (stage-1 go-live); cumulative since 2016 through June 2023 stated as 149; year-end 2023 target stated as 260 — Kemenhub/Dephub 26 June 2023
- LNSW integration cited especially at 46 ports (Kemenhub 16 Jul 2024); Customs, Immigration, and Port Health integration cited in ANTARA and Kemenhub June 2023
- International context: IMO Maritime Single Window obligation for member states from 1 January 2024 (Facilitation Committee 47 / FAL Convention amendment) — cited by Kemenhub and ANTARA; Inaportnet positioned inside NSW/NLE
- Post-commitment operating instruction: SOP, complaint/helpdesk service, and procedure-compliant execution — Capt. Antoni Arif Priadi via Dephub 25 Nov 2023
- We did not open production Inaportnet dashboards, second-level technical SLAs, or a PNBP audit that isolates Inaportnet’s causal effect from other factors; figures on this page come only from sources we successfully opened
Approach
Diagnose
This section is analysis: how a Diagnose phase would show up on a case like Inaportnet. It is not a claim that MarkasDev delivered work for Ditjen Hubla, LNSW, Customs, or a port operator.
Paid Diagnose is useful before a port organization, port SOE, or ministry locks budget to “roll a single window to N ports” without an inventory of decision rights. The questions are concrete. Which ship processes must go through the system (arrival, berth, shift/extend berth, cargo handling, departure, cancellation — the scope named in Inaportnet rules)? Which agency is system of record for each data field? Which ports enter the first wave (volume, connectivity, UPT readiness), and what separates “committed” from “truly live day to day”? What is the fallback when the system or network fails at a remote port?
The pattern visible in public sources is a split that must be mapped first: (1) regulation and mandatory use (PM then its replacement), (2) Inaportnet as the single-window platform, (3) integration into LNSW/INSW and the NLE, (4) links to Customs–Immigration–Port Health, (5) people and SOP readiness at each UPT including helpdesk, (6) transparency and governance (the Stranas PK narrative). Mixing all six in one SOW without acceptance criteria often produces ceremonial go-lives without healthy daily transactions.
For teams in logistics or government copying a single-window pattern, Diagnose also tests people–process–technology readiness: Training of Trainers (cited by Kemenhub ahead of the 2023 wave), user socialization, and complaint capacity. Without that, the IMO Maritime Single Window date is only a calendar deadline, not an operating capability. The Diagnose frame helps inventory that before port volume is locked.
Deliver
This is also analysis. Deliver breaks the work into milestones with testable acceptance criteria — a pattern that matches the staged 2023 go-lives reported by Kemenhub (stage 1 in June, stage 2 planned for September, stage 3 for November in the 26 June 2023 release; year-end results summarized by Dephub on 25 November 2023).
A sensible sequence from public descriptions: first, lock the legal base and ship-service scope (PM 8/2022 replaced PM 157/2015). Second, prepare LNSW and related-agency integrations before port volume peaks — Kemenhub (16 July 2024) cites licensing integration via LNSW especially at 46 ports, so depth of integration is not uniform across all 264 UPTs. Third, onboard UPT waves with TOT, user socialization, and commitment signing (integrity pacts are mentioned in 2023 go-live coverage). Fourth, run end-to-end tests: ship-service requests from arrival through departure processed and supervised in the system (as Antoni describes via ANTARA). Fifth, make SOP and helpdesk a condition of being “alive”, not an optional appendix (Capt. Antoni’s instruction, November 2023).
Example acceptance criteria (our analysis, not an official SLA with seconds we quoted from a public technical document): share of ship transactions completed end-to-end in Inaportnet per UPT; average cycle time for sample arrival–departure requests; successful data exchange with Customs/Immigration/Port Health at LNSW-integrated ports; helpdesk availability in service hours; and an offline fallback runbook. See Deliver and systems & API integration for cross-agency interface contracting patterns.
What to avoid: chasing “ports gone live” while LNSW integration or helpdesks are not ready. In the public narrative, Inaportnet’s value shows when ship processes are digitally handled and supervised and users feel faster service — not when a launch banner goes up.
Operate
This is analysis too. Once coverage reaches hundreds of UPTs, Inaportnet stops being a wave project and becomes an operating backbone. Capt. Antoni (Dephub, 25 November 2023) calls Inaportnet the “backbone of service for all ports in Indonesia” and stresses collaboration and ongoing oversight of implementation. Operate answers who watches daily system availability, who handles helpdesk tickets at small UPTs, who keeps LNSW integration healthy when FAL/IMO rules change, and what weekly report Ditjen Hubla leadership receives.
Published scale explains why Operate is not an add-on. From six initial ports (PM 157) to 149 (June 2023) then 264 (late 2023 / 2024), any interface regression or uneven SOP immediately becomes hundreds of failure points. Kemenhub (16 July 2024) still argues that improving sea-logistics service through Inaportnet “needs to be strengthened” — a signal that national go-live is not the finish line.
In the Operate frame, transaction monitoring, platform capacity and patching, UPT staff retraining, communication to users (ship agents, BUPs), and reconciliation with Customs/Immigration become routine work. The PNBP and Stranas PK narrative (ANTARA, January 2024) marks transaction transparency as a governance metric, not merely an “IT feature”. Without an operating owner after the go-live ceremony, a national single window easily becomes a half-filled portal at peripheral ports.
High-level architecture
This diagram is our simplification from public Kemenhub/ANTARA/JDIH descriptions — not an official architecture we audited in production. We did not open internal Ditjen Hubla, LNSW, or Customs diagrams, component names and flows come only from sources we successfully read. LNSW integration depth is not claimed to be uniform across all 264 UPTs, sources cite licensing integration focus at 46 ports (Kemenhub, 16 July 2024). The historical domain named in PM 157 text (inaportnet.dephub.go.id) is noted from the regulation, we did not test production availability or UI in this session.
Typical outcomes
Every figure below comes from sources we opened. Scope and dates differ, so do not mash them into one “national Inaportnet ROI” metric.
Port coverage. Dephub (25 November 2023): since the 2016 digitalization launch, 264 ports committed to Inaportnet; in 2023 three go-live stages targeted 151 and realized 155 ports (including four pemekaran); stage III added 66 ports. Kemenhub/Dephub (26 June 2023): +40 ports at stage-1 go-live; cumulative since 2016 through June 2023 = 149; year-end 2023 target stated as 260. ANTARA (18 January 2024, quoting Dirjen Antoni): Inaportnet implemented at 264 ports / all ports in Indonesia, including Tersus, TUKS, BUP. Kemenhub (16 July 2024): 264 sea-port UPTs; LNSW integration especially at 46 ports.
PNBP (ANTARA, 18 January 2024, quoting Dirjen Antoni Arif Priadi). Harbour services: Rp2.2 trillion (2020); Rp2.4 trillion (2021); Rp2.6 trillion (2022); Rp2.9 trillion (2023). Aids-to-navigation services: Rp573 billion (2020); Rp605 billion (2021); Rp695 billion (2022); Rp738 billion (2023). Concession services: Rp491 billion (2020); Rp540 billion (2021); Rp672 billion (2022); Rp697 billion (2023). The Director General places the rise mainly in harbour, navigation, concession, and maritime telecommunication services, and links Inaportnet digitalization to faster/more efficient/transparent processes and an expectation of significantly higher PNBP in 2024. We do not claim that all PNBP growth is solely caused by Inaportnet.
Regulation and international context. PM 157/2015 effective 21 January 2016; replaced by PM 8/2022 (JDIH). IMO Maritime Single Window obligation from 1 January 2024 is cited by Kemenhub (26 June 2023; 16 July 2024) and ANTARA (18 January 2024). Kemenhub (16 July 2024) mentions a joint LNSW presentation at the IMO Facilitation Committee in London and study visits by member states; Dephub (25 November 2023) names study visits from Tanzania, Zanzibar, Brunei Darussalam, and Timor Leste.
What we did not find in primary sources opened in this session: a national logistics-cost saving in percent or rupiah officially attributed only to Inaportnet; official before/after container dwell-time numbers we could verify; platform technical SLAs in seconds; the full list of 264 ports; or a causal PNBP audit versus ship volumes.
Typical or expected outcomes, not claims about MarkasDev project results.About this analysis
This page is compiled from open sources and is not a MarkasDev client project. We read Kemenhub/Dephub releases (26 June 2023; 25 November 2023; 16 July 2024), ANTARA (18 January 2024) quoting Director General Capt. Antoni Arif Priadi, JDIH metadata for PM 157/2015 and PM 8/2022, and the text of PM 157 (including the definition and six initial ports) from a regulation repository. Every figure on this page comes from a source we opened, with the scope we state.
Why this case matters for your organization
Port operators, freight forwarders, logistics SOEs, and ministry digital teams often face the same question: how do you unify cross-agency services without shipping a mere “forms portal”? The Inaportnet pattern — PM regulation, go-live waves across hundreds of UPTs, LNSW/Customs/Immigration/Port Health integration, IMO Maritime Single Window pressure, and PNBP/governance narratives — is a case worth dissecting through Diagnose, systems & API integration, and Operate. See also the logistics sector page and other case studies.
Reading the case through Diagnose, Deliver, Operate
Three questions in order. Who owns ship-process data across agencies, and which ports enter the first wave with clear criteria? That is Diagnose. How do you test arrival–departure end-to-end plus LNSW integration before chasing a site-count KPI? That is Deliver. Who keeps UPT helpdesks, platform availability, and data reconciliation healthy after 264 points are “live”? That is Operate. If you are weighing an initial mapping, also browse insights on technology decisions before building a large system.
Limits of this analysis
We did not interview Ditjen Hubla, LNSW, or Customs. We did not audit production Inaportnet. We did not test live UI/API. We present PNBP trends as official figures quoted by officials, not as single-cause proof. We did not find a full list of 264 ports or numeric dwell-time metrics in sources successfully opened in this session. Treat this page as discussion material for leaders, not an audit report.
Sources
Accessed on 1 October 2026 (WIB).
- ANTARA, Kemenhub: Digitalisasi layanan pelabuhan dorong peningkatan PNBP, 18 January 2024 (Dirjen Antoni Arif Priadi quotes; PNBP; 264 ports; NLE; IMO MSW).
- Ministry of Transportation / Dephub, 264 Pelabuhan Telah Terapkan Inaportnet, 25 November 2023 (2023 go-lives; target 151 / realized 155; SOP & helpdesk).
- Ministry of Transportation, Menhub: Digitalisasi Layanan Dorong Peningkatan Daya Saing Logistik, 26 June 2023 (40 ports stage 1; total 149; target 260; NLE; IMO).
- Ministry of Transportation, Peningkatan Layanan Logistik Transportasi Laut Melalui Inaportnet Perlu Ditingkatkan, 16 July 2024 (264 UPTs; LNSW integration at 46 ports; FAL/IMO).
- JDIH Kemenhub, metadata for PM 157/2015 (effective 21 January 2016; repealed by PM 8/2022).
- Text of PM 157/2015 (Inaportnet definition; six initial ports) via the Klaussa regulation repository.
- Aceh Transport Agency republish, 264 Pelabuhan Telah Terapkan Inaportnet, 28 November 2023 — brief corroboration of the Kemenhub release.