diff --git a/landing/templates/mms-client-iec61850.html b/landing/templates/mms-client-iec61850.html index b34b0bf20..1afc02717 100644 --- a/landing/templates/mms-client-iec61850.html +++ b/landing/templates/mms-client-iec61850.html @@ -1,24 +1,62 @@ - - MMS Client, IED Browser dan IP-to-SCL IEC 61850 | ARSAS - - - - - - + + + Cara Pakai MMS Client IEC 61850 dan Browse IED | ARSAS + + + + + + + + + + + + + + + + + + + + + + + + + + {{> header}}
-
Beranda / MMS Client
MMS client IEC 61850 · complete live discovery · Windows

Telusuri live server model dan pertahankan sebagai engineering context yang reusable.

ARSAS membangun association MMS ke endpoint yang disetujui, discovery complete typed model, lalu menjaga value, quality, timestamp, DataSet, RCB, control dan diagnostik dalam konteks IED yang benar. Full discovery yang berhasil dapat dilanjutkan menjadi IID Edition 2 atau ICD Edition 1.

Unduh ARSASLihat workflow MMSLanjutkan ke IP-to-SCLEnglish
-
Complete discoveryPhysical identity, Logical Device, Node, object, attribute dan type
Value bertipeValue, quality, timestamp dan live MMS type context
Objek engineeringDataSet, BRCB, URCB dan control model
Output reusablePertahankan complete model untuk generate IID atau ICD
-
Workflow praktis

Dari alamat IP yang disetujui menuju live evidence yang dapat dicari dan digunakan ulang.

Expose protocol evidence tanpa membangun ulang konteks yang sama di beberapa aplikasi terpisah.

01

Tambahkan endpoint IED

Buat association MMS independen agar kegagalan service tetap dapat dikaitkan dengan perangkat asal.

02

Discovery complete server model

Enumerasi physical identity, full logical hierarchy dan live type information yang diperlukan untuk value, report, control dan generate SCL.

03

Cari dan pilih operational signal

Filter model besar untuk FAT, SAT, commissioning atau troubleshooting tanpa membuang complete engineering model yang dipertahankan session.

04

Amati evidence yang attributable

Pertahankan identity IED, quality, timestamp, perubahan terakhir dan acquisition source terverifikasi.

05

Pertahankan hasil discovery

Generate IID Edition 2 atau ICD Edition 1 saat integration baseline yang reusable dibutuhkan dan discovery sudah complete.

-
Screenshot aplikasi nyata

Satu model browser, satu live-value workspace, satu konteks IED.

Periksa perilaku perangkat saat ini dan jangan hanya bergantung pada tree dari engineering file statis.

Workspace awal MMS client IEC 61850 ARSAS

01Mulai dari perangkat

Tambahkan endpoint tanpa wajib memiliki CID, ICD atau SCD vendor yang usable untuk discovery read-only pertama.

Live value IEC 61850 dengan quality dan timestamp di ARSAS

02Live value yang dapat dicari

Lihat perangkat, quality, timestamp, source dan konteks perubahan dalam satu tempat.

-
Berguna untuk

FAT, SAT, commissioning dan recovery integrasi

  • Konfirmasi IED menerima association MMS
  • Recovery current model evidence saat vendor file hilang atau stale
  • Temukan DataSet dan RCB sebelum uji reporting
  • Periksa ctlModel sebelum uji control
  • Pertahankan complete model untuk generate SCL
  • Pisahkan masalah model, service dan komunikasi
Batas engineering

Koneksi MMS bukan bukti interoperabilitas lengkap.

Association atau generated file yang berhasil belum membuktikan reporting, control, file service, GOOSE binding, acceptance receiving system atau seluruh object model sudah benar. Validasi tetap dilakukan eksplisit.

-
Workflow acquisition berikutnya

Lanjutkan ke monitoring berbasis report.

Periksa DataSet coverage, ownership BRCB/URCB, trigger option serta fallback.

Smart Reporting
Workflow integrasi berikutnya

Generate atau bandingkan SCL dari complete model yang sama.

Buat IID/ICD dari live discovery, normalize opened SCL atau siapkan CID selected-RCB.

Buka IP-to-SCL
+
Beranda / Pusat Belajar / MMS Client
Tutorial praktis · mulai read-only · IEC 61850 MMS

Hubungkan IED. Discovery live model. Baca satu value yang dapat dipercaya.

Gunakan ARSAS sebagai MMS client IEC 61850 untuk berpindah dari alamat IP yang disetujui menuju model yang dapat diperiksa dan value yang dapat dijelaskan. Indikator hijau “Connected” baru langkah awal: hasil yang berguna adalah IED, object reference, value, quality, timestamp dan acquisition source yang benar tetap berada dalam satu konteks.

Ikuti tutorialTakeaway 30 detikPusat BelajarEnglish
+ +
Takeaway 30 detik

MMS adalah pintu client/server menuju IED IEC 61850.

Melalui MMS, ARSAS dapat membangun association, discovery function dan data yang memiliki nama, membaca typed value, memeriksa DataSet dan Report Control Block, mengambil file yang didukung serta menyiapkan workflow control yang disetujui. Perbedaannya sederhana: connection membuktikan reachability; discovery membuktikan model; value, quality, waktu dan identity membuat observation berguna.

Mulai dari alamat IP
+ +
Kapan memakai MMS Client

Mulai di sini saat task dimulai dari endpoint IED.

Workflow ini cocok sebelum pengujian Reporting, SCL, file transfer atau control yang lebih dalam.

Koneksi pertama

Pastikan IED yang dimaksud benar-benar menjawab

Pisahkan IP reachability, TCP port 102, association MMS dan usable model discovery—jangan menyebut semuanya hanya sebagai “connected.”

Recovery model

Periksa apa yang benar-benar diekspos server aktif

Gunakan live discovery saat file vendor tidak tersedia, stale atau perlu dibandingkan dengan IED online.

Persiapan monitoring

Temukan value, DataSet dan RCB

Konfirmasi object reference dan Functional Constraint sebelum memilih point untuk Reporting atau bounded polling.

Output integrasi

Pertahankan baseline model yang reusable

Saat discovery lengkap, lanjutkan menuju IID Edition 2 atau ICD Edition 1 dan validasi receiving system secara eksplisit.

+ +
Sebelum mulai

Kumpulkan fakta target.

  • Nama IED, bay atau function yang disetujui
  • Alamat IP, subnet dan route yang disetujui
  • Ekspektasi availability TCP port 102
  • Identity vendor atau model yang diharapkan
  • Izin connect dari engineering workstation ini
Batas keselamatan

Pertahankan session pertama sebagai read-only.

Live discovery dan value read harus dipisahkan dari active control, modifikasi RCB dan perubahan konfigurasi IED. Jangan melakukan write atau operate sampai procedure, plant authority dan rollback plan mengizinkannya secara eksplisit.

+ +
Langkah di ARSAS

Dari alamat IP yang disetujui menuju satu value yang attributable.

Jangan melewati pemeriksaan identity dan quality hanya karena association berhasil.

01

Konfirmasi target dan jalur network

Catat identity perangkat yang diharapkan dan verifikasi network interface, subnet, route serta VLAN yang disetujui. Ping dapat membantu membuktikan IP reachability dasar, tetapi tidak membuktikan service MMS IEC 61850.

Diagnosa port 102
02

Pilih Add IED

Buka General IEC 61850 Testing, pilih Add IED, masukkan nama device yang jelas, alamat IP yang disetujui dan port 102 kecuali project menentukan endpoint lain.

03

Selesaikan association MMS

Connect dan pertahankan diagnostic exact bila association ditolak, timeout atau closed. TCP socket yang berhasil belum sama dengan MMS association yang diterima.

04

Periksa identity dan live-model discovery

Pastikan physical identity hasil discovery masuk akal, lalu periksa Logical Device, Logical Node, Data Object, Data Attribute, DataSet dan RCB. Tree yang terlalu kecil atau kosong adalah evidence yang harus diselidiki.

05

Temukan object dan Functional Constraint yang benar

Cari indication atau measurement yang familiar. Pertahankan IEC reference lengkap dan pilih Functional Constraint yang benar—misalnya status, measurement, configuration atau control context—bukan sekadar nama yang terlihat mirip.

06

Verifikasi trustworthy value pertama

Baca value bersama identity IED, full reference, MMS type, quality, device timestamp, capture time ARSAS dan acquisition source. Bandingkan dengan plant state yang diketahui secara independen sebelum menjadikannya evidence.

+ +
Success criteria

Session pertama yang berguna menjawab lebih dari “connected atau tidak.”

Endpoint benarIED yang diharapkan menjawab pada alamat yang disetujui
Model usableLogical hierarchy, data dan engineering object berhasil ditemukan
Reference benarObject dan Functional Constraint yang dimaksud eksplisit
Observation terpercayaValue, quality, timestamp dan source dapat dijelaskan
+ +
Konsep di balik layar

Lima istilah membuat browser lebih mudah dipahami.

MMS association

Session client/server pada application layer. Tahap ini berada setelah network dan TCP reachability serta sebelum service IEC 61850 yang berguna.

Object reference

Identity lengkap data di dalam IED. Pertahankan reference ini; short display label tidak cukup untuk evidence yang reproducible.

Functional Constraint

Service context dari attribute, misalnya status, measurement, configuration atau control. Nama mirip di FC berbeda tidak boleh dianggap interchangeable.

Quality dan timestamp

Quality menunjukkan apakah observation dapat dipercaya. Timestamp menunjukkan kapan IED atau process mengaitkan perubahan dengan waktu.

DataSet dan RCB

DataSet memilih member; Report Control Block mengatur bagaimana perubahan terpilih dikirim. Discovery adalah persiapan—bukan bukti Reporting berhasil.

Live model dibanding SCL

Live model adalah evidence server aktif. SCL mewakili configured engineering intent. Bandingkan keduanya saat integrasi bergantung pada konsistensi.

Bandingkan live model dan SCL
+ +
Bila gagal

Gunakan milestone yang gagal untuk memilih pemeriksaan berikutnya.

Tidak ada IP reachability

Periksa kabel, alamat adapter, subnet, route, VLAN, duplicate IP dan batas network yang disetujui.

Ping berhasil, TCP port 102 gagal

Periksa MMS enablement, firewall, ACL, service binding dan apakah interface IED lain yang seharusnya digunakan.

Buka panduan koneksi

Port 102 berhasil, association gagal

Capture exact diagnostic. Selidiki server limit, concurrent client, access policy, authentication atau behavior edition tertentu.

Association berhasil, model tidak lengkap

Periksa access right, discovery diagnostic, model limit dan apakah endpoint tersebut benar-benar server yang dimaksud.

Value terlihat salah atau stale

Konfirmasi object reference, Functional Constraint, type, quality dan timestamp. Bandingkan dengan SCL serta indication plant independen.

Read berhasil, perubahan tidak masuk

Masalah berikutnya adalah coverage Reporting, ownership, trigger option atau delivery—bukan basic MMS discovery.

Diagnosa Reporting silent
+ +
Evidence aplikasi nyata

Pertahankan model dan live observation dalam konteks IED yang sama.

Workspace awal ARSAS untuk menambahkan IED IEC 61850

01Tambahkan endpoint yang dimaksud

Mulai dari identity dan alamat IP IED yang disetujui tanpa wajib memiliki file SCL vendor yang usable untuk discovery read-only pertama.

Live value IEC 61850 ARSAS dengan identity quality timestamp dan source

02Verifikasi observation

Review device, full reference, value, quality, timestamp dan acquisition source secara bersamaan.

+ +
Yang dapat dibuktikan ARSAS

Live server evidence yang attributable

ARSAS dapat mempertahankan endpoint mana yang menjawab, model apa yang diekspos, object apa yang dibaca dan konteks quality, waktu serta source yang menyertai value.

Batas engineering

MMS discovery bukan bukti interoperabilitas lengkap.

Association dan discovery tidak membuktikan Reporting, file service, GOOSE binding, control, acceptance receiving system, kebenaran model atau conformance IEC 61850. Semua itu tetap menjadi validasi service-specific yang terpisah.

+ +
Apakah koneksi MMS dapat berhasil tetapi datanya belum dapat digunakan?
Ya. Koneksi TCP atau association MMS belum membuktikan model yang dimaksud sudah ditemukan atau value memiliki quality, timestamp dan identity yang dapat dipercaya.
Apakah ARSAS dapat discovery IED tanpa file SCL?
Ya bila IED mengizinkan live MMS discovery. SCL tetap berguna sebagai configured intent dan pembanding integrasi.
Apa yang harus dicek sebelum lanjut ke Reporting?
Konfirmasi identity IED yang benar, model discovery yang cukup lengkap dan minimal satu trustworthy read dengan object reference serta Functional Constraint yang diketahui.
+ +
Pelajaran berikutnya

Berpindah dari satu trustworthy read menuju delivery perubahan kontinu.

Pelajari bagaimana DataSet memilih signal, bagaimana BRCB dan URCB mengirim update, bagaimana ARSAS memvalidasi exact coverage dan mengapa polling fallback yang terlihat lebih baik daripada gap tersembunyi.

Pelajari Smart ReportingLanjutkan ke IP-to-SCLKembali ke Pusat Belajar
{{> download-cta-id}}
{{> footer}} diff --git a/landing/templates/mms-client.html b/landing/templates/mms-client.html index 48e622f3a..d3005e993 100644 --- a/landing/templates/mms-client.html +++ b/landing/templates/mms-client.html @@ -1,24 +1,62 @@ - - IEC 61850 MMS Client, IED Browser and IP-to-SCL | ARSAS - - - - - - + + + How to Use an IEC 61850 MMS Client and Browse an IED | ARSAS + + + + + + + + + + + + + + + + + + + + + + + + + + {{> header}}
-
Home / Capabilities / MMS Client
IEC 61850 MMS client · complete live discovery · Windows

Browse the live server model and preserve it as reusable engineering context.

ARSAS connects to an approved IEC 61850 endpoint over MMS, discovers the complete typed model and keeps values, quality, timestamps, DataSets, Report Control Blocks, controls and diagnostics inside the same per-IED session. A successful full discovery can continue into Edition 2 IID or Edition 1 ICD generation.

Download ARSASSee the MMS workflowContinue to IP-to-SCL
-
Complete discoveryPhysical identity, Logical Devices, Nodes, objects, attributes and types
Typed valuesValue, quality, timestamp and live MMS type context
Engineering objectsDataSets, BRCBs, URCBs and control models
Reusable outputPreserve the complete model for IID or ICD generation
-
Practical workflow

From an approved IP address to searchable and reusable live evidence.

Expose useful protocol evidence without reconstructing the same context across several disconnected applications.

01

Add the IED endpoint

Establish an independent MMS association and keep service failures attributable to the originating device.

02

Discover the complete server model

Enumerate physical identity, full logical hierarchy and live type information required for values, reports, controls and SCL generation.

03

Search and select operational signals

Filter large models for FAT, SAT, commissioning or troubleshooting without discarding the complete engineering model retained by the device session.

04

Observe attributable values

Retain quality, timestamps, recent-change evidence and the verified acquisition source.

05

Preserve the discovery result

Generate Edition 2 IID or Edition 1 ICD when a reusable integration baseline is needed and the discovery is complete.

-
Real application evidence

One model browser, one live-value workspace, one IED context.

Inspect current device behavior rather than relying only on a static engineering-file tree.

ARSAS IEC 61850 MMS client first-launch workspace

01Start from the device

Add the intended endpoint without requiring a usable vendor CID, ICD or SCD for the first read-only discovery.

ARSAS IEC 61850 MMS live values with quality and timestamps

02Searchable live values

Review device, quality, timestamp, source and change context together.

-
Useful for

FAT, SAT, commissioning and integration recovery

  • Confirm that the IED accepts an MMS association
  • Recover current model evidence when a vendor file is unavailable or stale
  • Find DataSets and Report Control Blocks before reporting tests
  • Inspect ctlModel before control tests
  • Preserve a complete model for downstream SCL generation
  • Separate model, service and communication problems
Engineering boundary

An MMS connection is not proof of complete interoperability.

A successful association or generated file does not prove reporting, controls, file services, GOOSE binding, receiving-system acceptance or every modeled object is correct. ARSAS keeps those validations explicit.

-
Next acquisition workflow

Move from discovery to report-based monitoring.

Inspect DataSet coverage, BRCB and URCB ownership, trigger options and fallback behavior.

Explore Smart Reporting
Next integration workflow

Generate or compare SCL from the same complete model.

Create IID or ICD from live discovery, normalize opened SCL or prepare selected-RCB CID output.

Explore IP-to-SCL
+
Home / Learning Center / MMS Client
Practical tutorial · read-only first · IEC 61850 MMS

Connect an IED. Discover its live model. Read one trustworthy value.

Use ARSAS as an IEC 61850 MMS client to move from an approved IP address to a model you can inspect and a value you can explain. A green connection indicator is only the beginning: the useful result is the correct IED, object reference, value, quality, timestamp and acquisition source kept together.

Follow the tutorialGet the 30-second answerLearning CenterBahasa Indonesia
+ +
30-second takeaway

MMS is the client/server doorway into an IEC 61850 IED.

Through MMS, ARSAS can associate with the IED, discover its named functions and data, read typed values, inspect DataSets and Report Control Blocks, transfer supported files and prepare approved control workflows. The important distinction is simple: connection proves reachability; discovery proves a model; value, quality, time and identity make an observation useful.

Start from the IP address
+ +
When to use the MMS Client

Start here when the task begins with an IED endpoint.

This workflow is useful before deeper Reporting, SCL, file-transfer or control testing.

First connection

Verify that the intended IED answers

Separate basic network reachability, TCP port 102, MMS association and usable model discovery instead of calling all four “connected.”

Model recovery

Inspect what the running server exposes

Use live discovery when a vendor file is unavailable, stale or needs comparison against the online IED.

Monitoring preparation

Find values, DataSets and RCBs

Confirm object references and Functional Constraints before selecting points for Reporting or bounded polling.

Integration output

Preserve a reusable model baseline

When discovery is complete, continue toward IID Edition 2 or ICD Edition 1 generation and explicit receiving-system validation.

+ +
Before you start

Collect the target facts.

  • Approved IED name, bay or function
  • IP address, subnet and approved route
  • Expected TCP port 102 availability
  • Expected vendor or model identity
  • Permission to connect from this workstation
Safety boundary

Keep the first session read-only.

Live discovery and value reads should be separated from active control, RCB modification and IED configuration changes. Do not write or operate until the project procedure, plant authority and rollback plan explicitly permit it.

+ +
Step-by-step in ARSAS

From approved IP address to one attributable value.

Do not skip identity and quality checks merely because the association succeeds.

01

Confirm the target and network path

Record the expected device identity and verify the approved network interface, subnet, route and VLAN. Ping can help with basic IP reachability, but it does not prove IEC 61850 MMS service.

Diagnose port 102
02

Select Add IED

Open General IEC 61850 Testing, choose Add IED, enter a clear device name, the approved IP address and port 102 unless the project specifies another endpoint.

03

Complete the MMS association

Connect and retain the exact diagnostic if the association is refused, times out or closes. A successful TCP socket is not the same as an accepted MMS association.

04

Inspect identity and live-model discovery

Confirm that the discovered physical identity is plausible, then inspect Logical Devices, Logical Nodes, Data Objects, Data Attributes, DataSets and RCBs. An unexpectedly small or empty tree is evidence to investigate.

05

Find the intended object and Functional Constraint

Search for a familiar indication or measurement. Keep the complete IEC reference and choose the correct Functional Constraint—for example status, measurement, configuration or control context—rather than selecting a similar-looking name.

06

Verify the first trustworthy value

Read the value together with IED identity, full reference, MMS type, quality, device timestamp, ARSAS capture time and acquisition source. Compare it with an independently known plant state before treating it as evidence.

+ +
Success criteria

A useful first session answers more than “connected or not.”

Correct endpointThe expected IED identity answered at the approved address
Usable modelLogical hierarchy, data and engineering objects were discovered
Correct referenceThe intended object and Functional Constraint are explicit
Trustworthy observationValue, quality, timestamp and source are understandable
+ +
Concepts behind the screen

Five terms make the browser easier to understand.

MMS association

The application-level client/server session. It comes after network and TCP reachability and before useful IEC 61850 services.

Object reference

The full identity of the data inside the IED. Preserve it; a short display label is not enough for reproducible evidence.

Functional Constraint

The service context of an attribute, such as status, measurement, configuration or control. Similar names under different FCs are not interchangeable.

Quality and timestamp

Quality says whether the observation can be trusted. Timestamp says when the IED or process associated the change with time.

DataSet and RCB

A DataSet selects members; a Report Control Block governs how selected changes are delivered. Discovery is preparation—not proof that reporting works.

Live model versus SCL

The live model is current server evidence. SCL represents configured engineering intent. Compare both when integration depends on consistency.

Compare live model and SCL
+ +
If it fails

Use the failed milestone to choose the next check.

No IP reachability

Check cable, adapter address, subnet, route, VLAN, duplicate IP and approved network boundaries.

Ping works, TCP port 102 fails

Check MMS enablement, firewall, ACL, service binding and whether another IED interface is intended.

Open connection guide

Port 102 works, association fails

Capture the exact diagnostic. Investigate server limits, concurrent clients, access policy, authentication or edition-specific behavior.

Association works, model is incomplete

Check access rights, discovery diagnostics, model limits and whether the connected endpoint is really the intended server.

Value looks wrong or stale

Confirm the object reference, Functional Constraint, type, quality and timestamp. Compare with SCL and an independent plant indication.

Reads work, changes do not arrive

The next problem is Reporting coverage, ownership, trigger options or delivery—not basic MMS discovery.

Diagnose silent reporting
+ +
Real application evidence

Keep the model and the live observation in the same IED context.

ARSAS first-launch workspace used to add an IEC 61850 IED

01Add the intended endpoint

Start from the approved IED identity and IP address without requiring a usable vendor SCL file for the first read-only discovery.

ARSAS IEC 61850 live values with device identity quality timestamp and source

02Verify the observation

Review the device, full reference, value, quality, timestamp and acquisition source together.

+ +
What ARSAS can establish

Attributable live server evidence

ARSAS can preserve what endpoint answered, what model it exposed, what object was read and what supporting quality, time and source context accompanied the value.

Engineering boundary

MMS discovery is not complete interoperability proof.

Association and discovery do not prove Reporting, file service, GOOSE binding, controls, receiving-system acceptance, model correctness or IEC 61850 conformance. Those remain separate service-specific validations.

+ +
Can an MMS connection succeed while the data is still unusable?
Yes. A TCP connection or MMS association does not prove that the intended model was discovered or that a value has acceptable quality, timestamp and identity.
Can ARSAS discover an IED without an SCL file?
Yes when the IED permits live MMS discovery. SCL remains useful as configured intent and for integration comparison.
What should I check before moving to Reporting?
Confirm the correct IED identity, complete enough model discovery and at least one trustworthy read with a known object reference and Functional Constraint.
+ +
Next lesson

Move from one trustworthy read to continuous change delivery.

Learn how DataSets select signals, how BRCB and URCB deliver updates, how ARSAS validates exact coverage and why visible polling fallback is better than a hidden gap.

Learn Smart ReportingContinue to IP-to-SCLBack to Learning Center
{{> download-cta}}
{{> footer}} diff --git a/landing/templates/smart-reporting-iec61850.html b/landing/templates/smart-reporting-iec61850.html index cdd27dc95..c8d315df1 100644 --- a/landing/templates/smart-reporting-iec61850.html +++ b/landing/templates/smart-reporting-iec61850.html @@ -1,24 +1,65 @@ - - Smart Reporting IEC 61850 — BRCB, URCB dan Fallback | ARSAS - - - - - - + + + Cara Kerja Reporting IEC 61850 — BRCB, URCB dan DataSet | ARSAS + + + + + + + + + + + + + + + + + + + + + + + + + + + {{> header}}
-
Beranda / Smart Reporting
BRCB · URCB · coverage DataSet · fallback yang terlihat

Pilih signal yang dibutuhkan. ARSAS membangun jalur acquisition yang dapat dipertanggungjawabkan.

Smart Reporting bukan janji bahwa semua value pasti datang melalui report. Workflow ini memulai MMS read, mengevaluasi report yang sudah dikonfigurasi, membuktikan coverage secara tepat, memulihkan gap tertentu bila diizinkan, dan mempertahankan polling untuk point yang masih belum tercakup atau belum terverifikasi.

Unduh ARSASLihat workflowEnglish
-
Langsung aktifMMS read berjalan saat reporting dievaluasi
Configured firstDataSet, BRCB dan URCB existing diprioritaskan
Coverage tepatMember dan urutan divalidasi, bukan diasumsikan
Fallback dipertahankanPoint uncovered atau degraded tetap masuk bounded polling
-
Rencana acquisition per IED

Static report lebih dulu. Recovery spesifik untuk gap. Polling bila diperlukan.

Setiap keputusan tetap terikat pada association IED yang menghasilkan evidence, sehingga state satu perangkat tidak diam-diam mengubah perangkat lain.

01
Mulai MMS read terpilih

Tampilkan value awal, quality dan timestamp sambil memeriksa object report.

02
Discovery reporting existing

Baca DataSet, BRCB, URCB, reference, reservation state dan option yang relevan.

03
Validasi coverage secara tepat

Bandingkan signal terpilih dengan membership dan urutan DataSet aktual, bukan nama saja.

04
Pulihkan gap tertentu

Gunakan temporary DataSet dan RCB yang sesuai hanya saat IED serta prosedur proyek mengizinkan write.

05
Pertahankan fallback yang terlihat

Point rejected, uncovered, unverified atau degraded tetap berada dalam bounded polling.

Tidak ada report dead end.DataSet kosong, RCB occupied, write ditolak atau stream silent tidak harus menghentikan live-value workspace.Kembali ke MMS Client →
-
Masalah yang dibuat terlihat

Association berhasil belum membuktikan reporting berhasil.

Negative evidence tetap terlihat agar engineer dapat membedakan masalah association, configuration, ownership, trigger dan delivery.

DataSet kosong atau tidak lengkap

RCB dapat tersedia tetapi DataSet yang direferensikan kosong, tidak lengkap atau berbeda dari kebutuhan test.

RCB sudah reserved

Report dapat dimiliki client lain, reserved oleh konfigurasi atau tidak tersedia untuk association saat ini.

Coverage tidak sesuai

Nama DataSet yang terlihat benar bukan bukti setiap signal terpilih tersedia dalam urutan yang diperlukan.

GI berhasil, update spontan tidak ada

General interrogation dapat mengembalikan initial image sementara report perubahan tetap tidak muncul.

Dynamic recovery ditolak

IED dapat menolak write karena capability, access control, configuration atau ownership aktif.

Report stream degraded

Perubahan yang hilang, association loss atau delivery yang tidak valid dapat mengembalikan point ke polling.

-
Evidence yang dipertahankan

Setiap update tetap memiliki asal.

  • Konteks IED dan association
  • Value dan quality
  • Timestamp IED atau proses
  • Report reason bila tersedia
  • Sumber report, polling atau acquisition lain
  • Diagnostik coverage dan degradation
Batas engineering

Otomasi tidak menghapus persyaratan approval.

  • Configured report diprioritaskan sebelum write dipertimbangkan
  • Dynamic recovery bersifat conditional dan eksplisit
  • Polling adalah fallback yang sah, bukan kegagalan tersembunyi
  • Access IED dan kewenangan test tetap berada di luar aplikasi
  • Tidak ada klaim universal reporting interoperability
-
Live value multi-IED dengan evidence reporting di ARSAS

EvidenceWorkspace live value terpadu

Signal dari session IED independen tetap membawa device, value, quality, waktu dan sumber acquisition.

+
Beranda / Pusat Belajar / Smart Reporting
Tutorial praktis · DataSet · BRCB · URCB · fallback terlihat

Jangan menebak apakah update datang dari report atau polling.

Smart Reporting mengubah signal IED terpilih menjadi acquisition plan yang terlihat. ARSAS mulai dari read yang usable, memeriksa configured DataSet dan Report Control Block, membuktikan exact coverage, memakai recovery yang disetujui hanya bila diizinkan, lalu menjaga polling tetap terlihat untuk point yang belum tercakup atau belum terverifikasi.

Ikuti workflowTakeaway 30 detikPusat BelajarEnglish
+ +
Takeaway 30 detik

DataSet memilih signal. RCB mengatur delivery.

Reporting IEC 61850 memungkinkan IED mengirim perubahan terpilih tanpa menunggu client membaca semua point berulang kali. BRCB dapat menyimpan report entry selama interruption client sementara; URCB mengirim saat association aktif tanpa buffered continuity. ARSAS menunjukkan apakah setiap update berasal dari report atau polling dan tidak menyembunyikan gap di balik label “live” yang generik.

Bandingkan BRCB dan URCB
+ +
Kapan memakai Smart Reporting

Gunakan setelah MMS discovery dan satu trustworthy read.

Reporting bergantung pada IED yang diketahui, object reference yang diketahui dan requirement acquisition yang dapat diperiksa terhadap membership DataSet aktual.

Monitoring kontinu

Terima perubahan terpilih secara efisien

Gunakan report saat IED harus mengirim event dan perubahan value tanpa polling semua object pada interval yang sama.

FAT dan SAT

Buktikan bagaimana setiap point diperoleh

Pertahankan evidence report, polling dan fallback secara eksplisit saat memvalidasi indication, measurement dan sequence behavior.

Troubleshooting

Pisahkan connection success dari report success

Association dapat bekerja sementara DataSet kosong, RCB occupied, trigger salah atau tidak ada report yang dikirim.

Pekerjaan multi-IED

Pertahankan acquisition lifecycle setiap IED independen

State Reporting, ownership dan degradation satu IED tidak boleh diam-diam mengubah behavior session lain.

+ +
Sebelum mulai

Konfirmasi prerequisite Reporting.

  • IED yang benar sudah associated dan discovered
  • Object reference dan Functional Constraint terpilih diketahui
  • Minimal satu direct read memiliki quality dan timestamp yang dapat dipahami
  • Expected update behavior sudah didefinisikan
  • Setiap write DataSet atau RCB diizinkan secara eksplisit
Batas default

Prioritaskan configured report sebelum mempertimbangkan write.

ARSAS pertama-tama harus memeriksa DataSet, BRCB dan URCB existing. Dynamic DataSet atau RCB recovery bersifat conditional, device-dependent dan hanya tepat bila capability IED serta procedure yang disetujui mengizinkan modifikasi.

+ +
Konsep inti

Pahami tanggung jawab setiap object Reporting.

DataSet

Daftar data member berurutan yang terikat ke report. Nama yang terlihat meyakinkan bukan bukti point yang dibutuhkan benar-benar tersedia.

Report Control Block

Control object yang mereferensikan DataSet dan mengatur enablement, trigger option, integrity period, optional field serta delivery behavior.

BRCB

Buffered Report Control Block dapat mempertahankan report entry untuk delivery berikutnya bila buffering didukung, dikonfigurasi benar dan client melanjutkan dalam batas continuity yang berlaku.

URCB

Unbuffered Report Control Block mengirim selama association aktif. Event yang terjadi saat disconnected tidak dipulihkan sebagai buffered history.

GI dan integrity

General Interrogation meminta current image. Integrity reporting dapat refresh DataSet secara periodik. Keduanya belum membuktikan trigger perubahan spontan bekerja.

Trigger option

Data change, quality change dan data update trigger menentukan perubahan mana yang dapat menghasilkan report. Stimulus test harus sesuai dengan configured trigger behavior.

+ +
Langkah di ARSAS

Bangun acquisition path yang dapat dipertanggungjawabkan per IED.

Workflow dimulai dari evidence yang bekerja sekarang, lalu meningkatkan report coverage tanpa mengubah unavailable report menjadi kehilangan data yang tersembunyi.

01
Konfirmasi discovery dan trustworthy read

Mulai hanya setelah model IED yang dimaksud diketahui dan point terpilih dapat dibaca dengan identity, quality serta timestamp yang dapat dipahami.

02
Pilih signal yang dibutuhkan

Definisikan point untuk monitoring atau test evidence. Pertahankan full object reference dan Functional Constraint.

03
Periksa configured DataSet dan RCB

Baca DataSet member, reference BRCB dan URCB, reservation atau ownership state, trigger option, optional field serta enablement condition.

04
Validasi exact coverage

Bandingkan setiap signal terpilih dengan membership dan urutan DataSet aktual. Jangan menyimpulkan coverage dari nama DataSet atau RCB.

05
Gunakan report path yang disetujui

Prioritaskan configured reporting yang sesuai. Pertimbangkan temporary DataSet atau RCB recovery hanya saat write diizinkan, target tersedia dan rollback didefinisikan.

06
Verifikasi delivery dan pertahankan fallback terlihat

Ubah test point yang diketahui, konfirmasi report reason dan source bila tersedia, lalu pertahankan point uncovered, rejected atau degraded dalam bounded polling.

Tidak ada report dead end tersembunyi.DataSet kosong, RCB occupied, write ditolak atau stream silent harus tetap terlihat di diagnostik sementara polling usable berlanjut dalam batas eksplisit.Buka panduan Reporting silent →
+ +
Success criteria

Workflow Reporting berhasil saat coverage dan source dapat dijelaskan.

Coverage diketahuiSetiap point terpilih reported, polled atau unresolved secara eksplisit
Source diketahuiSetiap update mengidentifikasi report, polling atau acquisition path lain
Konteks diketahuiIED, reference, value, quality dan waktu tetap terikat
Degradation diketahuiAssociation loss atau delivery silent mengubah state yang terlihat
+ +
Cara membaca hasil

Tiga outcome acquisition valid bila semuanya eksplisit.

Reported

Point terpilih tercakup dan delivery terverifikasi.

Update membawa konteks IED yang attributable, report source serta quality dan time evidence. Behavior BRCB atau URCB tetap spesifik terhadap konfigurasi IED aktual.

Polling fallback

Point tetap observable tanpa berpura-pura Reporting bekerja.

Polling dapat menjadi bounded fallback yang disengaja untuk report path uncovered, occupied, rejected atau degraded. Source dan interval harus tetap terlihat.

Unresolved

Evidence yang dibutuhkan belum tersedia.

Invalid quality, unknown ownership, incomplete coverage atau ambiguous delivery harus tetap unresolved dan tidak dipromosikan menjadi false pass.

+ +
Bila Reporting silent

Periksa acquisition chain secara berurutan.

Association atau discovery tidak stabil

Konfirmasi IED session dan direct read sebelum mengubah konfigurasi report.

DataSet kosong atau tidak lengkap

Baca actual member list lalu bandingkan dengan point terpilih.

Diagnosa DataSet kosong

RCB reserved atau occupied

Periksa ownership dan reservation tanpa memaksa takeover dari client lain.

Periksa ownership RCB

GI bekerja tetapi report spontan tidak masuk

Periksa trigger option, data-change behavior, report enablement dan apakah stimulus test mengubah attribute yang benar.

Coverage terlihat benar tetapi update hilang

Periksa report reason, sequence, entry state, optional field, association continuity dan diagnostic sebelum mempercayai stream.

Report path degraded setelah reconnect

Evaluasi ulang ownership, enablement, BRCB continuity dan fallback state. Jangan menggunakan kembali acquisition claim stale dari association sebelumnya.

+ +
Evidence aplikasi nyata

Setiap live value mempertahankan asal acquisition.

Workspace yang sama dapat menampilkan selected value dari session IED independen sambil mempertahankan device, reference, quality, timestamp, recent-change evidence serta report atau polling source.

Workspace live value IEC 61850 ARSAS yang menunjukkan evidence report dan polling

EvidenceWorkspace live value yang attributable

Selected signal mempertahankan identity IED, value, quality, waktu, recent-change state dan acquisition source tanpa menggabungkan semua update menjadi satu generic live state.

+ +
Yang dapat dibuktikan ARSAS

Acquisition plan yang terlihat dan current evidence-nya

ARSAS dapat menunjukkan configured report object, exact selected-point coverage, current delivery source, fallback state dan negative diagnostic untuk active IED session.

Batas engineering

Otomasi tidak menciptakan interoperabilitas universal.

Reporting yang berhasil pada satu IED, DataSet atau RCB tidak membuktikan seluruh implementasi vendor, trigger, buffered continuity atau receiving system berperilaku sama. Configuration write dan active test stimulus tetap memerlukan approval.

+ +
Apa perbedaan DataSet dan RCB?
DataSet menentukan data member yang dikelompokkan. Report Control Block menentukan bagaimana dan kapan perubahan dari DataSet tersebut dikirim.
Apakah General Interrogation yang berhasil membuktikan spontaneous Reporting bekerja?
Tidak. GI dapat memberikan initial image sementara delivery data-change spontan tetap tidak ada, salah konfigurasi atau terblokir.
Apakah polling selalu berarti gagal?
Tidak. Bounded polling adalah fallback yang sah dan terlihat saat report coverage tidak tersedia, tidak lengkap, occupied, ditolak atau belum terverifikasi.
+ +
Pelajaran berikutnya

Gunakan disiplin evidence yang sama untuk GOOSE dan pengujian proyek.

Setelah report delivery menjadi attributable, lanjutkan ke analisis sequence GOOSE, FAT IO List atau workflow FAT yang lebih luas tanpa kehilangan identity perangkat, quality, waktu dan source.

Pelajari GOOSEBuka FAT IO ListKembali ke Pusat Belajar
{{> download-cta-id}}
{{> footer}} diff --git a/landing/templates/smart-reporting.html b/landing/templates/smart-reporting.html index 46060ace0..dc77c44f1 100644 --- a/landing/templates/smart-reporting.html +++ b/landing/templates/smart-reporting.html @@ -3,10 +3,10 @@ - IEC 61850 Smart Reporting — BRCB, URCB and Fallback | ARSAS - + How IEC 61850 Reporting Works — BRCB, URCB and DataSets | ARSAS + - + @@ -19,84 +19,47 @@ - - + + - + - - + + - + {{> header}}
-
-
-
Home / Smart Reporting
- BRCB · URCB · DataSet coverage · visible fallback -

Select the signals. ARSAS builds a defensible acquisition path.

-

Smart Reporting is not a promise that every selected value will arrive through a report. It is a failure-aware workflow that starts useful MMS reads, evaluates configured reports, proves exact coverage, recovers specific gaps when permitted and retains polling for anything still uncovered or unverified.

-
Download ARSASSee the acquisition workflow
-
-
+
Home / Learning Center / Smart Reporting
Practical tutorial · DataSet · BRCB · URCB · visible fallback

Stop guessing whether updates came from reports or polling.

Smart Reporting turns selected IED signals into a visible acquisition plan. ARSAS starts with usable reads, inspects configured DataSets and Report Control Blocks, proves exact coverage, uses approved recovery only when permitted, and keeps polling visible for anything still uncovered or unverified.

Follow the workflowGet the 30-second answerLearning CenterBahasa Indonesia
-
ImmediateSelected MMS values begin while reporting is evaluated
Configured firstExisting DataSets, BRCBs and URCBs are preferred
Exact coverageMembers and order are validated instead of assumed
Fallback retainedUncovered or degraded points remain in bounded polling
+
30-second takeaway

A DataSet chooses the signals. An RCB controls their delivery.

IEC 61850 Reporting lets the IED push selected changes instead of waiting for the client to read every point repeatedly. A BRCB can buffer report entries across a temporary client interruption; a URCB delivers while the association is active without buffered continuity. ARSAS shows whether each update came from a report or polling and does not hide gaps behind a generic “live” label.

Compare BRCB and URCB
-
-
-
Per-IED acquisition plan

Static reports first. Specific recovery for gaps. Polling when required.

Every step remains attached to the IED association that produced the evidence, so reporting decisions from one device cannot silently change another.

-
-
01
Start selected MMS reads

Show initial values, quality and timestamps while report objects are inspected.

-
02
Discover configured reporting

Read available DataSets, BRCBs, URCBs, references, reservation state and relevant options.

-
03
Validate exact coverage

Compare selected signals with actual DataSet membership and order rather than relying on names alone.

-
04
Recover specific gaps

Use temporary DataSet coverage with a suitable available RCB only when the IED and approved procedure permit writes.

-
05
Retain visible fallback

Keep rejected, uncovered, unverified or degraded points in a bounded polling schedule.

-
-
No report dead end.An empty DataSet, occupied RCB, rejected write or silent stream does not have to block the live-value workspace.View the complete capability scope →
-
-
+
When to use Smart Reporting

Use it after MMS discovery and one trustworthy read.

Reporting depends on a known IED, known object references and an acquisition requirement that can be checked against actual DataSet membership.

Continuous monitoring

Receive selected changes efficiently

Use reports when the IED should deliver events and value changes without polling every object at the same interval.

FAT and SAT

Prove how each point was acquired

Keep report, polling and fallback evidence explicit while validating indications, measurements and sequence behavior.

Troubleshooting

Separate connection success from report success

An association can work while the DataSet is empty, the RCB is occupied, triggers are wrong or no report is delivered.

Multi-IED work

Keep each acquisition lifecycle independent

Reporting state, ownership and degradation for one IED must not silently change the behavior of another session.

-
-
-
Problems the workflow makes visible

Communication success does not prove reporting success.

ARSAS keeps negative evidence visible so the engineer can distinguish association, configuration, ownership, trigger and delivery problems.

-
-

Empty or incomplete DataSet

An RCB can exist while its referenced DataSet is empty, incomplete or different from the signals required for the test.

-

RCB already reserved

An unbuffered or buffered report may be owned by another client, reserved by configuration or unavailable for the current association.

-

Configured coverage mismatch

A promising DataSet name is not proof that every selected signal is present in the required order.

-

GI without spontaneous updates

A successful general interrogation can return an initial image while change-triggered reports remain absent or incomplete.

-

Rejected dynamic recovery

The IED may reject DataSet or RCB writes because of capability, access control, configuration or active ownership.

-

Degraded report stream

Missed changes, association loss or invalid delivery evidence can return affected points to bounded polling.

-
-
-
+
Before you start

Confirm the reporting prerequisites.

  • The correct IED is associated and discovered
  • Selected object references and Functional Constraints are known
  • At least one direct read has understandable quality and timestamp
  • The required update behavior is defined
  • Any DataSet or RCB write is explicitly authorized
Default boundary

Prefer configured reports before considering writes.

ARSAS should first inspect existing DataSets, BRCBs and URCBs. Dynamic DataSet or RCB recovery is conditional, device-dependent and only appropriate when the IED capability and approved procedure permit modification.

-
-
-
Evidence retained

Every update keeps its origin.

  • IED and association context
  • Value and quality
  • IED or process timestamp
  • Report reason where available
  • Report, polling or other acquisition source
  • Coverage and degradation diagnostics
-
Engineering boundary

Automation does not remove approval requirements.

  • Configured reports are preferred before writes are considered
  • Dynamic recovery is conditional and explicit
  • Polling remains a valid fallback, not a hidden failure
  • IED access, project procedure and test authority remain external requirements
  • No universal reporting interoperability claim is made
-
-
+
Core concepts

Know what each reporting object is responsible for.

DataSet

The ordered list of data members attached to a report. A convincing name is not proof that the required points are present.

Report Control Block

The control object that references a DataSet and governs enablement, trigger options, integrity period, optional fields and delivery behavior.

BRCB

A Buffered Report Control Block can retain report entries for later delivery when buffering is supported, correctly configured and the client resumes within the applicable continuity limits.

URCB

An Unbuffered Report Control Block delivers while the association is active. Events that occur during disconnection are not recovered as buffered history.

GI and integrity

General Interrogation requests a current image. Integrity reporting can periodically refresh the DataSet. Neither alone proves spontaneous change triggers work.

Trigger options

Data change, quality change and data update triggers determine which changes can produce reports. The expected event must match the configured trigger behavior.

-
-
Real application evidence

Live values remain attributable across multiple IEDs.

The same workspace shows selected values, quality, timestamps, source and recent-change evidence while each IED retains an independent acquisition lifecycle.

ARSAS IEC 61850 live-value workspace with multi-IED reporting evidence

EvidenceUnified live-value workspace

Selected signals from independent IED sessions retain device, value, quality, time and acquisition context.

-
+
Step-by-step in ARSAS

Build a defensible acquisition path per IED.

The workflow starts with evidence that works now, then improves report coverage without turning unavailable reports into invisible data loss.

01
Confirm discovery and trustworthy reads

Start only after the intended IED model is known and selected points can be read with understandable identity, quality and timestamp.

02
Select the required signals

Define the points needed for monitoring or test evidence. Keep their full object references and Functional Constraints.

03
Inspect configured DataSets and RCBs

Read DataSet members, BRCB and URCB references, reservation or ownership state, trigger options, optional fields and enablement conditions.

04
Validate exact coverage

Compare every selected signal with actual DataSet membership and order. Do not infer coverage from a DataSet or RCB name.

05
Use the approved report path

Prefer suitable configured reporting. Consider temporary DataSet or RCB recovery only when writes are permitted, the target is available and rollback is defined.

06
Verify delivery and retain visible fallback

Change a known test point, confirm report reason and source where available, and keep uncovered, rejected or degraded points in bounded polling.

No hidden report dead end.An empty DataSet, occupied RCB, rejected write or silent stream must remain visible in diagnostics while usable polling continues within an explicit bound.Open the silent-reporting guide →
+
Success criteria

A reporting workflow is successful when coverage and source are explainable.

Known coverageEvery selected point is reported, polled or explicitly unresolved
Known sourceEach update identifies report, polling or another acquisition path
Known contextIED, reference, value, quality and time remain attached
Known degradationAssociation loss or silent delivery changes the visible state
+ +
How to read the result

Three acquisition outcomes are valid when they are explicit.

Reported

The selected point is covered and delivery is verified.

The update carries attributable IED context, report source and supporting quality and time evidence. BRCB or URCB behavior remains specific to the actual IED configuration.

Polling fallback

The point remains observable without pretending Reporting works.

Polling can be a deliberate bounded fallback for uncovered, occupied, rejected or degraded report paths. Its source and interval must remain visible.

Unresolved

The required evidence is not available yet.

Invalid quality, unknown ownership, incomplete coverage or ambiguous delivery should remain unresolved rather than being promoted to a false pass.

+ +
If Reporting is silent

Check the acquisition chain in order.

Association or discovery is unstable

Confirm the IED session and direct reads before changing report configuration.

The DataSet is empty or incomplete

Read the actual member list and compare it with the selected points.

Diagnose an empty DataSet

The RCB is reserved or occupied

Inspect ownership and reservation without forcing takeover from another client.

Inspect RCB ownership

GI works but spontaneous reports do not

Check trigger options, data-change behavior, report enablement and whether the test stimulus changes the correct attribute.

Coverage appears correct but updates are missing

Inspect report reason, sequence, entry state, optional fields, association continuity and diagnostics before trusting the stream.

The report path degrades after reconnect

Re-evaluate ownership, enablement, BRCB continuity and fallback state. Do not reuse stale acquisition claims from the previous association.

+ +
Real application evidence

Every live value keeps its acquisition origin.

The same workspace can show selected values from independent IED sessions while preserving device, reference, quality, timestamp, recent-change evidence and report or polling source.

ARSAS IEC 61850 live-value workspace showing reporting and polling evidence

EvidenceAttributable live-value workspace

Selected signals retain IED identity, value, quality, time, recent-change state and acquisition source instead of collapsing all updates into one generic live state.

+ +
What ARSAS can establish

A visible acquisition plan and its current evidence

ARSAS can show configured report objects, exact selected-point coverage, current delivery source, fallback state and negative diagnostics for the active IED session.

Engineering boundary

Automation does not create universal interoperability.

Successful Reporting on one IED, DataSet or RCB does not prove all vendor implementations, triggers, buffered continuity or receiving systems behave the same. Configuration writes and active test stimuli still require approval.

+ +
What is the difference between a DataSet and an RCB?
A DataSet defines which data members belong together. A Report Control Block defines how and when changes from that DataSet are delivered.
Does a successful General Interrogation prove spontaneous Reporting works?
No. GI can provide an initial image while spontaneous data-change delivery remains absent, misconfigured or blocked.
Is polling always a failure?
No. Bounded polling is a valid visible fallback when report coverage is unavailable, incomplete, occupied, rejected or not yet verified.
+ +
Next lesson

Use the same evidence discipline for GOOSE and project testing.

After report delivery is attributable, continue to GOOSE sequence analysis, IO List FAT or broader FAT workflows without losing device identity, quality, time and source.

Learn GOOSEOpen IO List FATBack to Learning Center
{{> download-cta}}
{{> footer}} diff --git a/scripts/validate-adoption-proof.py b/scripts/validate-adoption-proof.py index dd296a6d8..f3c23ba40 100644 --- a/scripts/validate-adoption-proof.py +++ b/scripts/validate-adoption-proof.py @@ -1,5 +1,5 @@ #!/usr/bin/env python3 -"""Validate ARSAS onboarding, evidence, localization, issue intake and supply-chain contracts.""" +"""Validate ARSAS onboarding, learning, capability tutorials, evidence and supply-chain contracts.""" from __future__ import annotations @@ -16,6 +16,8 @@ "learning-center.html": "pusat-belajar-iec61850.html", "what-is-iec61850.html": "apa-itu-iec61850.html", "connect-ied-ip-arsas.html": "cara-hubungkan-ied-ip-arsas.html", + "mms-client.html": "mms-client-iec61850.html", + "smart-reporting.html": "smart-reporting-iec61850.html", "io-list-fat-evidence.html": "bukti-fat-iolist-iec61850.html", "faq.html": "faq-arsas.html", "compatibility.html": "bukti-kompatibilitas.html", @@ -84,6 +86,35 @@ def main() -> int: if "learning-center.html" not in text and "pusat-belajar-iec61850.html" not in text and name not in {"learning-center.html", "pusat-belajar-iec61850.html"}: errors.append(f"{name}: missing Learning Center continuation path") + capability_tutorials = { + "mms-client.html": ( + "30-second takeaway", "When to use the MMS Client", "Add IED", "Functional Constraint", + "Success criteria", "If it fails", "HowTo", "FAQPage", "learning-center.html", + ), + "mms-client-iec61850.html": ( + "Takeaway 30 detik", "Kapan memakai MMS Client", "Add IED", "Functional Constraint", + "Success criteria", "Bila gagal", "HowTo", "FAQPage", "pusat-belajar-iec61850.html", + ), + "smart-reporting.html": ( + "30-second takeaway", "DataSet", "BRCB", "URCB", "General Interrogation", + "Success criteria", "If Reporting is silent", "HowTo", "FAQPage", "learning-center.html", + ), + "smart-reporting-iec61850.html": ( + "Takeaway 30 detik", "DataSet", "BRCB", "URCB", "General Interrogation", + "Success criteria", "Bila Reporting silent", "HowTo", "FAQPage", "pusat-belajar-iec61850.html", + ), + } + for name, required_values in capability_tutorials.items(): + text = read(TEMPLATES / name, errors) + for value in required_values: + if value.lower() not in text.lower(): + errors.append(f"{name}: missing capability tutorial contract {value}") + if text.count('
') != 3: + errors.append(f"{name}: expected three visible capability FAQ items") + expected_step_class = 'class="reporting-step"' if name.startswith("smart-reporting") else 'class="step"' + if text.count(expected_step_class) != 6: + errors.append(f"{name}: expected six capability tutorial steps") + for name in ("io-list-fat-evidence.html", "bukti-fat-iolist-iec61850.html"): text = read(TEMPLATES / name, errors) lower = text.lower() @@ -216,7 +247,7 @@ def main() -> int: for error in errors: print(f"- {error}") return 1 - print("ARSAS adoption and field-proof validation passed: 62 pages, 21 localized pages, beginner learning, ARSAS tutorials, IO FAT evidence, onboarding, FAQ, field evidence, demo, issue intake and supply-chain contracts.") + print("ARSAS adoption and field-proof validation passed: 62 pages, 21 localized pages, beginner learning, bilingual MMS and Reporting tutorials, IO FAT evidence, onboarding, FAQ, field evidence, demo, issue intake and supply-chain contracts.") return 0 diff --git a/scripts/verify-adoption-deployment.py b/scripts/verify-adoption-deployment.py index f93ca80e6..42350b51e 100644 --- a/scripts/verify-adoption-deployment.py +++ b/scripts/verify-adoption-deployment.py @@ -1,5 +1,5 @@ #!/usr/bin/env python3 -"""Verify that public Pages exposes learning, adoption, evidence and IO FAT surfaces.""" +"""Verify that public Pages exposes learning, capability tutorials, evidence and IO FAT surfaces.""" from __future__ import annotations @@ -11,7 +11,7 @@ def fetch(url: str) -> tuple[int, str]: - request = Request(url, headers={"User-Agent": "ARSAS-Adoption-Attestation/1.1", "Cache-Control": "no-cache"}) + request = Request(url, headers={"User-Agent": "ARSAS-Adoption-Attestation/1.2", "Cache-Control": "no-cache"}) try: with urlopen(request, timeout=25) as response: return response.status, response.read().decode("utf-8", errors="replace") @@ -35,6 +35,10 @@ def main() -> int: "apa-itu-iec61850.html": ("Takeaway 30 detik", "Logical Node", "Reporting", "GOOSE", "FAQPage", "what-is-iec61850.html"), "connect-ied-ip-arsas.html": ("TCP port 102", "Add IED", "MMS association", "HowTo", "cara-hubungkan-ied-ip-arsas.html"), "cara-hubungkan-ied-ip-arsas.html": ("TCP port 102", "Add IED", "association MMS", "HowTo", "connect-ied-ip-arsas.html"), + "mms-client.html": ("30-second takeaway", "Add IED", "Functional Constraint", "Success criteria", "If it fails", "HowTo", "FAQPage", "mms-client-iec61850.html"), + "mms-client-iec61850.html": ("Takeaway 30 detik", "Add IED", "Functional Constraint", "Success criteria", "Bila gagal", "HowTo", "FAQPage", "mms-client.html"), + "smart-reporting.html": ("30-second takeaway", "DataSet", "BRCB", "URCB", "Success criteria", "If Reporting is silent", "HowTo", "FAQPage", "smart-reporting-iec61850.html"), + "smart-reporting-iec61850.html": ("Takeaway 30 detik", "DataSet", "BRCB", "URCB", "Success criteria", "Bila Reporting silent", "HowTo", "FAQPage", "smart-reporting.html"), "quick-start.html": ("quick-step-number", "data-responsive-media=\"webp\"", "panduan-mulai-arsas.html", "io-list-fat-evidence.html"), "io-list-fat-evidence.html": ("OFF → ON", "ON → OFF", "TestPointId", ".arsas", "Native PDF report", "bukti-fat-iolist-iec61850.html"), "bukti-fat-iolist-iec61850.html": ("OFF → ON", "ON → OFF", "TestPointId", ".arsas", "Report PDF native", "io-list-fat-evidence.html"), @@ -68,7 +72,7 @@ def main() -> int: for error in errors: print(f"- {error}") return 1 - print("Public ARSAS adoption attestation passed: Learning Center, beginner IEC 61850 guides, ARSAS tutorials, Quick Start, IO FAT evidence, FAQ, compatibility, demo, filters and responsive media are live.") + print("Public ARSAS adoption attestation passed: Learning Center, beginner IEC 61850 guides, bilingual MMS and Reporting tutorials, Quick Start, IO FAT evidence, FAQ, compatibility, demo, filters and responsive media are live.") return 0