Step-by-step
From IP address to one attributable value.
01Confirm the target and authority
Record the IED name, IP address, bay or function, expected vendor/model and the approved purpose of the connection. This prevents a successful connection to the wrong device from being treated as success.
Prepare the Windows network interface
Use an address in the approved subnet, or an approved routed path. Avoid changing plant network settings by trial and error. Keep the original adapter configuration so it can be restored.
Separate ping from IEC 61850 service
Ping can prove basic IP reachability, but MMS uses TCP port 102. A device may answer ping while the service is disabled, blocked by a firewall or unavailable to your client.
04Open ARSAS and choose General IEC 61850 Testing
Select Add IED, then enter a clear device name, the approved IP address and TCP port 102 unless the project explicitly uses another endpoint.
Connect and wait for live discovery
ARSAS establishes the MMS association and reads the server model. Do not judge success only from the TCP connection; confirm that Logical Devices, Logical Nodes, Data Objects and DataSets are actually discovered.
Read one point correctly
Choose a familiar indication or measurement. Check the IED identity, full IEC reference, current value, quality, device timestamp and acquisition source. Capture diagnostics before changing anything when one field is missing or unexpected.
+
+
Successful first connectionYou should be able to answer six questions.
Which IED answered? Which object was read? What was the value? Was its quality acceptable? When did the IED say it changed? How did ARSAS obtain the value—direct read, report or polling?
+
+
What the result means
Connection, discovery and trustworthy data are three different milestones.
Milestone 1TCP connection
The network path reached a service endpoint. It does not yet prove the intended IED model or permissions.
Milestone 2MMS association and discovery
The server accepted the association and exposed a navigable IEC 61850 model.
Milestone 3Trustworthy observation
A known point returned a plausible value with understandable quality, timestamp and identity.
Milestone 4Repeatable acquisition
Reporting or bounded polling delivers continued observations with visible source and diagnostics.
+
+
If it fails
Use the symptom to choose the next check.
No ping
Check cable, VLAN, subnet, route, duplicate IP and the approved network boundary.
Ping works, port 102 fails
Check MMS enablement, firewall, ACL, service endpoint and whether another interface is intended.
Port 102 works, association fails
Capture the exact diagnostic. Check server limits, authentication or access policy, edition behavior and concurrent client restrictions.
Discovery works, data looks wrong
Verify you selected the right object and Functional Constraint. Compare configured SCL intent with the live model and inspect quality.
+
+
Should I use ping as the only connection test?
No. Ping checks basic IP reachability. IEC 61850 MMS requires TCP port 102, a successful association and a usable server model.
Can I connect without an SCL file?
Yes when the IED permits live discovery. SCL remains valuable as configured intent and for integration comparison.
What is the safest first data point?
Choose a familiar read-only indication or measurement whose expected state can be independently confirmed. Avoid active controls during the first connection.
+
+
Next lessonMove from one value to continuous change delivery.
After discovery and a trustworthy read, learn how DataSets, BRCB and URCB let the IED send selected changes and how ARSAS keeps the acquisition source visible.
+ {{> download-cta}}
+
+ {{> footer}}
+
+
diff --git a/landing/templates/id.html b/landing/templates/id.html
index a89d03a..55e9d0b 100644
--- a/landing/templates/id.html
+++ b/landing/templates/id.html
@@ -3,8 +3,8 @@
-
Software IEC 61850 IO FAT, IP-to-SCL dan Pengujian Windows | ARSAS
-
+
Software IEC 61850 untuk Belajar, FAT dan Troubleshooting | ARSAS
+
@@ -20,36 +20,39 @@
-
-
+
+
-
+
-
-
+
+
{{> header}}
- Gratis dan open source · Windows · mainline {{ARSAS_VERSION}}Ubah IO List atau endpoint IED menjadi evidence IEC 61850 yang attributable.
Import SDI dan buktikan OFF → ON → OFF, atau hubungkan IED yang disetujui untuk complete MMS discovery dan SCL interoperable. Pertahankan identity, quality, timestamp, acquisition source dan project output tanpa membangun ulang evidence di banyak aplikasi.
Excel · PDF native · .arsasTanpa akun atau license keySource dan checksum publik
IO List → evidence OFF / ON / OFF
IP → MMS model → IID / ICD / CID
Gratis dan open source · Windows · belajar sebelum mengubah apa punHubungkan relay. Lihat semua sinyal. Buktikan apa yang berubah.
ARSAS membantu Anda memahami IEC 61850, menghubungkan IED yang disetujui, membaca live value, menyelesaikan masalah Reporting atau GOOSE, dan mengubah IO List menjadi evidence FAT yang dapat direview—tanpa berpindah-pindah aplikasi.
Bahasa sederhanaTanpa akun atau license keyExcel · PDF native · .arsas
Belajar → connect → verifikasi
IO List → evidence ON / OFF
FAT IO ListStrict import SDI, session satu IED dan ordered transition proof
Export evidenceCopy result Excel, PDF native dan project portable .arsas
IP-to-SCLComplete live discovery menjadi IID Edition 2 atau ICD Edition 1
Field engineeringReporting, GOOSE, file, control, diagnostik dan konteks multi-IED
Mulai dari kebutuhanAnda tidak harus memahami semua istilah IEC 61850 terlebih dahulu.
Pilih pertanyaan yang membawa Anda ke sini. Setiap jalur memberi takeaway, workflow praktis dan detail engineering di baliknya.
Saya pemulaApa itu IEC 61850?
Pahami IED, Logical Node, MMS, Reporting, GOOSE dan SCL menggunakan contoh gardu yang familiar.
Saya sudah punya softwareBagaimana cara memakai ARSAS?
Hubungkan IED berdasarkan IP, discovery live model dan baca satu point bersama quality serta timestamp.
Saya punya proyekBagaimana membuat evidence FAT?
Jalankan SDI hasil import secara berurutan, pertahankan evidence ON dan OFF, lalu export Excel, PDF atau project portable.
Saya punya masalahMengapa IEC 61850 tidak bekerja?
Mulai dari gejala: port 102, reporting diam, RCB occupied, sequence GOOSE, COMTRADE hilang atau SCL ditolak.
Batas rilisMainline saat ini mencakup IO List FAT; stable publik tetap 1.6.18.
Dokumentasi mengikuti development line 1.6.19. Review Catatan Rilis sebelum menganggap installer stable terbaru memiliki fitur current-main.
BelajarKonsep pemula dan tutorial software praktis
ConnectIP IED menjadi live MMS model dan trustworthy value
UjiFAT IO List, Reporting, GOOSE, SCL, file dan guarded control
SimpanIdentity, quality, timestamp, diagnostic dan evidence yang dapat diexport
Dua jalur awal terkontrolGunakan source of truth yang disetujui untuk task.
ARSAS memisahkan execution test plan repeatable dari exploratory engineering tanpa kehilangan hubungan evidence.
FAT / IO List TestingProject sudah memiliki digital-indication test plan yang disetujui.
- Validasi schema workbook dan
TestPointId - Bind point import ke satu IED live
- Wajibkan baseline OFF terpercaya
- Capture OFF → ON dan ON → OFF secara berurutan
- Export Excel, PDF native atau
.arsas
General IEC 61850 TestingTask mulai dari endpoint atau SCL dan membutuhkan analisis service lebih luas.
- Discovery complete live MMS model
- Periksa value, DataSet, RCB dan reporting
- Analisis GOOSE dan ambil fault record
- Generate IID, ICD atau bounded CID
- Gunakan guarded control hanya dengan authority
Dua workflow softwarePilih source of truth yang disetujui untuk task.
Gunakan IO List saat test plan sudah ditentukan. Gunakan endpoint IED atau SCL saat membutuhkan discovery dan diagnosis yang lebih luas.
FAT / IO List TestingUji digital indication yang disetujui dan simpan ordered evidence.
- Validasi workbook identity dan
TestPointId - Bind point ke satu live IED
- Wajibkan baseline OFF terpercaya
- Capture OFF → ON dan ON → OFF
- Export Excel, PDF native atau
.arsas
General IEC 61850 TestingExplore IED dan periksa service yang lebih luas.
- Discovery complete live MMS model
- Periksa value, quality, timestamp dan report
- Analisis GOOSE dan ambil fault record
- Bandingkan atau generate SCL
- Gunakan guarded control hanya dengan authority
Solusi proyekGunakan ARSAS sepanjang lifecycle proyek IEC 61850.
Dari evidence indication factory yang repeatable menuju FAT general, validasi site, commissioning terkontrol dan integrasi multi-vendor.
Factory planEvidence FAT IO List
Jalankan SDI hasil import dan bawa result yang dapat direview ke workstation lain.
Factory engineeringPengujian FAT General
Validasi model, report, GOOSE, control outcome, file access dan integration output.
SiteSAT dan Commissioning
Konfirmasi endpoint, reporting, station-bus behavior, fault record dan command completion.
IntegrasiMulti-Vendor IEC 61850
Generate atau normalize SCL bounded dan isolasi mismatch identity, DataSet, RCB serta GOOSE.
Belajar sambil bekerjaSetiap halaman fitur harus menjawab “apa ini, kapan digunakan, dan apa yang bisa gagal?”
Pusat Belajar menghubungkan konsep protokol dengan workflow ARSAS yang nyata, lalu mengarahkan langsung ke troubleshooting saat hasil yang diharapkan tidak muncul.
Evidence aplikasi nyataPeriksa produk Windows yang bekerja, bukan marketing mockup.
Screenshot publik saat ini menunjukkan session IED independen, unified values, GOOSE dan diagnostik. IO FAT didokumentasikan dari mainline dan masih menunggu screenshot publik yang disanitasi khusus.
Session multi-IED independen
Setiap device mempertahankan association, model dan diagnostic history sendiri.
Live value attributable
Identity, reference, value, quality, timestamp dan acquisition source tetap bersama.
Supervisi GOOSE
Periksa identity stream, sequence, retransmission dan ordered payload evidence.
Diagnostic yang dapat disalin
Pertahankan failure attributable sebelum mengubah IED, network atau project file.
Solusi proyekGunakan ARSAS sepanjang lifecycle proyek IEC 61850.
Bergerak dari belajar dan koneksi pertama menuju FAT repeatable, validasi site, commissioning dan integrasi multi-vendor.
Factory planEvidence FAT IO List
Jalankan SDI hasil import dan bawa result yang dapat direview ke workstation lain.
Factory engineeringPengujian FAT General
Validasi model, report, GOOSE, control outcome, file access dan integration output.
SiteSAT dan Commissioning
Konfirmasi endpoint, reporting, station-bus behavior, fault record dan command completion.
IntegrasiMulti-Vendor IEC 61850
Generate atau normalize SCL bounded dan isolasi mismatch identity, DataSet, RCB serta GOOSE.
Apakah ARSAS dapat memakai IO List untuk FAT?
Ya pada mainline saat ini untuk SDI hasil import. ARSAS memvalidasi workbook, bind point ke satu IED live, wajibkan evidence OFF → ON → OFF, lalu export Excel, PDF native atau project .arsas. Periksa scope stable release sebelum download.
Apakah ARSAS dapat generate SCL dari IP IED?
Ya. Setelah complete live discovery, ARSAS dapat generate IID Edition 2 atau ICD Edition 1 beserta companion evidence. RCB live terpilih juga dapat menjadi bounded CID Edition 1 atau Edition 2.
Apakah ARSAS mengklaim seluruh vendor kompatibel?
Tidak. Evidence kompatibilitas tetap service-specific dan setiap receiving system harus divalidasi.
Apakah ARSAS dapat melakukan active control?
Workflow Direct dan SBO guarded tersedia, tetapi operasi aktif membutuhkan procedure, plant authority dan independent safety check.
Evidence aplikasi nyataPeriksa produk Windows yang bekerja, bukan marketing mockup.
Screenshot publik menunjukkan session IED independen, live value, supervisi GOOSE dan diagnostic. Tutorial menjelaskan apa yang perlu diperhatikan pada setiap workspace.
Session multi-IED independen
Setiap device mempertahankan association, model dan diagnostic history sendiri.
Live value attributable
Identity, reference, value, quality, timestamp dan acquisition source tetap bersama.
Supervisi GOOSE
Periksa identity stream, sequence, retransmission dan ordered payload evidence.
Diagnostic yang dapat disalin
Pertahankan failure attributable sebelum mengubah IED, network atau project file.
Apakah saya bisa belajar IEC 61850 di sini tanpa menginstal ARSAS?
Bisa. Pusat Belajar menjelaskan mental model, service dan pola kegagalan umum dengan bahasa sederhana. Tutorial software kemudian menunjukkan bagaimana konsep tersebut muncul pada workstation nyata.
Apakah ARSAS dapat connect langsung ke alamat IP IED?
Bisa jika jalur network dan service MMS yang disetujui tersedia. ARSAS dapat membuat association, discovery live model dan membaca data yang didukung. Ping saja bukan bukti yang cukup.
Apakah ARSAS dapat memakai IO List untuk FAT?
Bisa pada mainline saat ini untuk SDI hasil import. ARSAS mewajibkan evidence OFF → ON → OFF secara berurutan dan dapat export Excel, PDF native atau project .arsas.
Apakah ARSAS menggantikan procedure testing yang disetujui?
Tidak. ARSAS mendukung pembelajaran dan evidence capture, tetapi plant authority, calibrated equipment, protection testing, independent witness dan formal acceptance tetap menjadi tanggung jawab terpisah.
Batas rilisDokumentasi dapat menjelaskan fitur current mainline sebelum installer stable memilikinya.
Periksa Catatan Rilis sebelum menganggap package publik terbaru berisi seluruh workflow yang ditampilkan website.
{{> footer}}
diff --git a/landing/templates/index.html b/landing/templates/index.html
index 7e0ce5c..e6df661 100644
--- a/landing/templates/index.html
+++ b/landing/templates/index.html
@@ -3,8 +3,8 @@
-
IEC 61850 IO FAT, IP-to-SCL and Testing Software for Windows | ARSAS
-
+
IEC 61850 Software for Learning, FAT and Troubleshooting | ARSAS
+
@@ -21,37 +21,39 @@
-
-
+
+
-
+
-
-
+
+
-
+
{{> header}}
- Free and open source · Windows · mainline {{ARSAS_VERSION}}Turn an approved IO List or IED endpoint into attributable IEC 61850 evidence.
Import SDI points and prove OFF → ON → OFF, or connect to an approved IED for complete MMS discovery and interoperable SCL. Keep identity, quality, timestamps, acquisition source and project output connected instead of rebuilding evidence across separate tools.
Excel · native PDF · .arsasNo account or license keyPublic source and checksums
IO List → OFF / ON / OFF evidence
IP → MMS model → IID / ICD / CID
Free and open source · Windows · learn before you change anythingConnect the relay. See every signal. Prove what changed.
ARSAS helps you understand IEC 61850, connect an approved IED, inspect live values, solve Reporting or GOOSE problems, and turn an IO List into reviewable FAT evidence—without jumping between unrelated tools.
Plain-language learningNo account or license keyExcel · native PDF · .arsas
Learn → connect → verify
IO List → ON / OFF evidence
IO List FATStrict SDI import, one-IED sessions and ordered transition proof
Evidence exportExcel result copy, native PDF and verified portable .arsas project
IP-to-SCLComplete live discovery to Edition 2 IID or Edition 1 ICD
Field engineeringReporting, GOOSE, files, control, diagnostics and multi-IED context
Start from your needYou do not need to know every IEC 61850 term first.
Choose the question that brought you here. Each path gives you a useful takeaway, a practical workflow and the engineering detail behind it.
I am newWhat is IEC 61850?
Understand IEDs, Logical Nodes, MMS, Reporting, GOOSE and SCL with familiar substation examples.
I have the softwareHow do I use ARSAS?
Connect an IED by IP, discover the live model and read one point together with quality and timestamp.
I have a projectHow do I produce FAT evidence?
Run imported SDI points in order, preserve ON and OFF evidence, and export Excel, PDF or a portable project.
I have a problemWhy is IEC 61850 not working?
Start from the symptom: port 102, silent reports, occupied RCB, GOOSE sequence, missing COMTRADE or rejected SCL.
Release boundaryCurrent mainline includes IO List FAT; stable public release remains 1.6.18.
The documentation tracks the 1.6.19 development line. Review Release Notes before assuming the latest stable installer contains a current-main feature.
LearnBeginner concepts and practical software tutorials
ConnectIED IP to complete live MMS model and trustworthy values
TestIO List FAT, Reporting, GOOSE, SCL, files and guarded control
PreserveIdentity, quality, timestamps, diagnostics and exportable evidence
Two controlled starting pathsUse the approved source of truth for the task.
ARSAS separates repeatable test-plan execution from exploratory engineering without losing the relationship between them.
FAT / IO List TestingThe project already has an approved digital-indication test plan.
- Validate workbook schema and
TestPointId - Bind imported points to one live IED
- Require a trustworthy OFF baseline
- Capture OFF → ON and ON → OFF in order
- Export Excel, native PDF or
.arsas
General IEC 61850 TestingThe task starts from an endpoint or SCL and needs broader analysis.
- Discover the complete live MMS model
- Inspect values, DataSets, RCBs and reporting
- Analyze GOOSE and retrieve fault records
- Generate IID, ICD or bounded CID
- Use guarded control only with authority
Two software workflowsChoose the approved source of truth for the task.
Use the IO List when the test plan is already defined. Use the IED endpoint or SCL when you need broader discovery and diagnosis.
FAT / IO List TestingTest approved digital indications and keep ordered evidence.
- Validate workbook identity and
TestPointId - Bind points to one live IED
- Require a trustworthy OFF baseline
- Capture OFF → ON and ON → OFF
- Export Excel, native PDF or
.arsas
General IEC 61850 TestingExplore the IED and investigate wider services.
- Discover the complete live MMS model
- Inspect values, quality, timestamps and reports
- Analyze GOOSE and retrieve fault records
- Compare or generate SCL
- Use guarded control only with authority
Project solutionsUse ARSAS across the IEC 61850 project lifecycle.
Move from repeatable factory indication evidence to broader FAT, site validation, controlled commissioning and multi-vendor integration.
Factory planIO List FAT Evidence
Execute imported SDI points and carry reviewable results to another workstation.
Factory engineeringGeneral FAT Testing
Validate models, reports, GOOSE, control outcomes, file access and integration output.
SiteSAT and Commissioning
Reconfirm endpoints, reporting, station-bus behavior, fault records and command completion.
IntegrationMulti-Vendor IEC 61850
Generate or normalize bounded SCL and isolate identity, DataSet, RCB and GOOSE mismatches.
Learn while you workEvery feature page should answer “what is it, when do I use it, and what can go wrong?”
The Learning Center connects protocol concepts to the actual ARSAS workflow, then links directly to troubleshooting when the expected result does not appear.
Real application evidenceInspect the working Windows product—not a marketing mockup.
Current screenshots show independent IED sessions, unified values, event correlation, GOOSE supervision and diagnostics. IO FAT is documented from the current mainline and awaits a dedicated sanitized public screenshot.
01Independent multi-IED sessions
Each device retains its own association, model, monitoring state and diagnostic history.
02Attributable live values
Device identity, reference, value, quality, timestamp and acquisition source remain together.
03GOOSE supervision
Inspect stream identity, sequence, retransmission and ordered payload evidence.
04Copyable diagnostics
Keep failures attributable before changing the IED, network or project file.
Project solutionsUse ARSAS across the IEC 61850 project lifecycle.
Move from learning and first connection to repeatable FAT, site validation, commissioning and multi-vendor integration.
Factory planIO List FAT Evidence
Execute imported SDI points and carry reviewable results to another workstation.
Factory engineeringGeneral FAT Testing
Validate models, reports, GOOSE, control outcomes, file access and integration output.
SiteSAT and Commissioning
Reconfirm endpoints, reporting, station-bus behavior, fault records and command completion.
IntegrationMulti-Vendor IEC 61850
Generate or normalize bounded SCL and isolate identity, DataSet, RCB and GOOSE mismatches.
Can ARSAS use an approved IO List for FAT?
Yes on the current mainline for imported SDI points. ARSAS validates the workbook, binds points to one live IED, requires OFF → ON → OFF evidence, and exports Excel, native PDF or a portable .arsas project. Check the stable release scope before download.
Can ARSAS generate SCL directly from an IED IP address?
Yes. After complete live discovery, ARSAS can generate an Edition 2 IID or Edition 1 ICD, plus companion evidence. A selected live RCB can also become a bounded Edition 1 or Edition 2 CID baseline.
Does ARSAS claim support for every IEC 61850 vendor?
No. Compatibility evidence remains service-specific and every receiving system must be validated.
Can ARSAS perform active control?
Guarded Direct and SBO workflows exist, but active operation requires an approved procedure, plant authority and independent safety checks.
Real application evidenceInspect the working Windows product—not a marketing mockup.
Current screenshots show independent IED sessions, live values, GOOSE supervision and diagnostics. The tutorials explain what to look for in each workspace.
01Independent multi-IED sessions
Each device retains its own association, model, monitoring state and diagnostic history.
02Attributable live values
Device identity, reference, value, quality, timestamp and acquisition source remain together.
03GOOSE supervision
Inspect stream identity, sequence, retransmission and ordered payload evidence.
04Copyable diagnostics
Keep failures attributable before changing the IED, network or project file.
Start with attributable evidenceChoose the approved IO List or endpoint and preserve what happened.
Download the stable Windows build for its documented scope, or review current-main documentation and release status before evaluating a newer workflow.
Can I learn IEC 61850 here without installing ARSAS?
Yes. The Learning Center explains the mental model, services and common failure patterns in plain language. The software tutorials then show how those concepts appear in a real workstation.
Can ARSAS connect directly to an IED IP address?
Yes when the approved network path and MMS service are available. ARSAS can establish an association, discover the live model and read supported data. Ping alone is not sufficient proof.
Can ARSAS use an approved IO List for FAT?
Yes on the current mainline for imported SDI points. ARSAS requires ordered OFF → ON → OFF evidence and can export Excel, native PDF or a portable .arsas project.
Does ARSAS replace an approved test procedure?
No. ARSAS supports learning and evidence capture, but plant authority, calibrated equipment, protection testing, independent witness and formal acceptance remain separate responsibilities.
Release boundaryDocumentation can describe current mainline features before the stable installer includes them.
Review Release Notes before assuming the latest published package contains every workflow shown on the website.
{{> footer}}
diff --git a/landing/templates/learning-center.html b/landing/templates/learning-center.html
new file mode 100644
index 0000000..4aed9e7
--- /dev/null
+++ b/landing/templates/learning-center.html
@@ -0,0 +1,51 @@
+
+
+
+
+
+
Learn IEC 61850 and ARSAS — Beginner to Field Engineer
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ {{> header}}
+
+ Plain language · practical steps · engineering depth when you need itLearn IEC 61850 by doing useful work.
You do not need to memorize every standard term before opening an IED. Start with the problem you want to solve, follow a safe ARSAS workflow, and learn the protocol concept behind each step.
+
+ BeginnerUnderstand the words and mental model without vendor jargon
PracticalFollow the same buttons and screens used in ARSAS
EngineeringKeep quality, timestamps, identity and failure boundaries visible
Field-readyTurn observations into repeatable FAT and troubleshooting evidence
Choose your starting pointWhat are you trying to achieve today?
Each path gives you a useful takeaway even when you do not install ARSAS yet.
New to the protocolI want to understand IEC 61850
Learn why IEC 61850 uses named objects instead of register numbers, how an IED model is organized, and where MMS, Reporting, GOOSE and SCL fit.
First software taskI want to connect an IED
Prepare the IP address, check TCP port 102, add the device, discover its live model and read one point with value, quality and timestamp.
Project executionI need FAT or commissioning evidence
Choose an approved IO List for repeatable indication testing, or start from the IED endpoint for broader reporting, GOOSE, file and control checks.
Something is not workingI need to troubleshoot
Start from the symptom—connection failed, reporting silent, RCB occupied, GOOSE sequence unclear, COMTRADE missing or SCL rejected.
30-second takeawayIEC 61850 is a shared language for substation functions and communication.
An IED exposes named functions and data—such as breaker position, current, voltage or protection status. Tools can discover these names, read their values, subscribe to changes and exchange configuration through SCL files.
ARSAS takeawayARSAS keeps the observation and its context together.
Do not look at a value alone. Keep the IED identity, object reference, quality, device timestamp, ARSAS capture time and acquisition source attached so another engineer can understand what happened.
+
+ Recommended learning path
Build confidence in small, useful steps.
01Understand the IEC 61850 mental model
Learn IED, Logical Device, Logical Node, Data Object, Data Attribute and Functional Constraint using familiar substation examples.
Connect one approved IED
Verify the network route and port 102, create the device in ARSAS and complete live discovery.
Read one point correctly
Check the value together with quality, timestamp, object reference and acquisition source.
Learn how changes arrive
Understand DataSets and Reporting before treating polling, BRCB or URCB as interchangeable.
Move to project evidence
Use IO List FAT, GOOSE analysis, file retrieval, SCL comparison or guarded control according to the approved procedure.
Learning principleSimple language does not mean weak engineering.
Every tutorial separates what you observed, what you inferred and what still needs independent verification. ARSAS guidance does not replace the IED manual, approved FAT procedure, switching authority or IEC 61850 conformance testing.
+ {{> footer}}
+
+
diff --git a/landing/templates/pusat-belajar-iec61850.html b/landing/templates/pusat-belajar-iec61850.html
new file mode 100644
index 0000000..da3a033
--- /dev/null
+++ b/landing/templates/pusat-belajar-iec61850.html
@@ -0,0 +1,51 @@
+
+
+
+
+
+
Belajar IEC 61850 dan ARSAS — Dari Pemula ke Engineer Lapangan
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ {{> header}}
+
+ Bahasa sederhana · langkah praktis · detail engineering saat dibutuhkanBelajar IEC 61850 dengan mengerjakan hal yang berguna.
Anda tidak perlu menghafal semua istilah standar sebelum membuka IED. Mulai dari masalah yang ingin diselesaikan, ikuti workflow ARSAS yang aman, lalu pahami konsep protokol di balik setiap langkah.
+
+ PemulaPahami istilah dan gambaran besar tanpa jargon vendor
PraktisIkuti nama tombol dan layar yang benar-benar ada di ARSAS
EngineeringJaga quality, timestamp, identity dan failure boundary tetap terlihat
Siap lapanganUbah observation menjadi evidence FAT dan troubleshooting yang repeatable
Pilih titik mulaiApa yang ingin Anda selesaikan hari ini?
Setiap jalur memberi takeaway yang bermanfaat meskipun Anda belum menginstal ARSAS.
Baru mengenal protokolSaya ingin memahami IEC 61850
Pelajari mengapa IEC 61850 memakai object name, bagaimana model IED disusun, serta posisi MMS, Reporting, GOOSE dan SCL.
Tugas software pertamaSaya ingin menghubungkan IED
Siapkan alamat IP, periksa TCP port 102, tambahkan device, discovery live model dan baca satu point lengkap dengan value, quality dan timestamp.
Eksekusi proyekSaya membutuhkan evidence FAT atau commissioning
Pilih IO List yang disetujui untuk indication testing repeatable, atau mulai dari endpoint IED untuk pemeriksaan reporting, GOOSE, file dan control yang lebih luas.
Ada masalahSaya perlu troubleshooting
Mulai dari gejala—koneksi gagal, reporting diam, RCB occupied, sequence GOOSE membingungkan, COMTRADE hilang atau SCL ditolak.
Takeaway 30 detikIEC 61850 adalah bahasa bersama untuk fungsi dan komunikasi gardu.
IED menampilkan fungsi dan data bernama—misalnya posisi breaker, arus, tegangan atau status proteksi. Software dapat menemukan nama tersebut, membaca nilainya, menerima perubahan dan bertukar konfigurasi melalui file SCL.
Takeaway ARSASARSAS menjaga observation dan konteksnya tetap bersama.
Jangan melihat value saja. Pertahankan identity IED, object reference, quality, timestamp device, waktu capture ARSAS dan acquisition source agar engineer lain memahami apa yang terjadi.
+
+ Jalur belajar yang disarankan
Bangun pemahaman melalui langkah kecil yang berguna.
01Pahami mental model IEC 61850
Kenali IED, Logical Device, Logical Node, Data Object, Data Attribute dan Functional Constraint menggunakan contoh gardu yang familiar.
Hubungkan satu IED yang disetujui
Periksa jalur network dan port 102, buat device di ARSAS lalu selesaikan live discovery.
Baca satu point dengan benar
Periksa value bersama quality, timestamp, object reference dan acquisition source.
Pahami bagaimana perubahan data datang
Pelajari DataSet dan Reporting sebelum menganggap polling, BRCB dan URCB sebagai hal yang sama.
Naik ke evidence proyek
Gunakan FAT IO List, analisis GOOSE, file retrieval, perbandingan SCL atau guarded control sesuai procedure yang disetujui.
Prinsip belajarBahasa sederhana tidak berarti engineering yang lemah.
Setiap tutorial memisahkan apa yang diamati, apa yang disimpulkan dan apa yang masih membutuhkan verifikasi independen. Panduan ARSAS tidak menggantikan manual IED, procedure FAT, switching authority atau pengujian conformance IEC 61850.
+ {{> footer}}
+
+
diff --git a/landing/templates/what-is-iec61850.html b/landing/templates/what-is-iec61850.html
new file mode 100644
index 0000000..3804745
--- /dev/null
+++ b/landing/templates/what-is-iec61850.html
@@ -0,0 +1,55 @@
+
+
+
+
+
+
What Is IEC 61850? A Practical Beginner Guide
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ {{> header}}
+
+ Beginner · 8 minute read · practical mental modelWhat is IEC 61850, in plain language?
IEC 61850 is a standardized way for substation devices to describe their functions, exchange data and share engineering information. Its biggest idea is not a cable or a packet—it is a common, meaningful model of the power-system function.
+
+ 30-second takeawayIEC 61850 gives substation data a shared name and meaning.
Instead of saying “read register 1024,” an IEC 61850 client can discover a named object that represents a real function—such as breaker position, phase current or protection pickup—and read its value together with quality and timestamp.
The mental modelThink of the IED as a structured library of functions.
The names may look unfamiliar at first, but the hierarchy is logical once each level has a job.
IEDThe physical or virtual device
A protection relay, bay controller, merging unit or other IEC 61850 server.
Logical Device
A grouping boundary inside the IED. One physical relay can contain several logical devices for protection, measurement or control.
Logical Node
A standardized functional block. For example, XCBR represents circuit-breaker information, while MMXU commonly represents measurements.
Data Object
A meaningful item inside the function, such as Pos for position or A for current.
Data Attribute
The actual value and supporting details, such as stVal, quality q and timestamp t.
ExampleA breaker position is more than ON or OFF.
An object such as XCBR.Pos can provide the state, quality and timestamp. This lets the engineer distinguish a valid fresh observation from an old, questionable or invalid value.
- Value: what state was reported?
- Quality: can the state be trusted?
- Timestamp: when did the IED say it changed?
- Identity: which IED and object produced it?
Why this mattersA value without context is weak evidence.
Two tools may display the same “1,” but only one may preserve the correct IED, object reference, quality, timestamp and acquisition path. IEC 61850 engineering is about that context as much as the value itself.
+
+ Main pieces of IEC 61850
Different services solve different communication problems.
Client/serverMMS
Used to associate with an IED, discover its model, read and write supported data, manage reports, transfer files and perform approved controls.
Change deliveryReporting
The IED sends selected changes through a DataSet and Report Control Block instead of waiting for the client to repeatedly poll every point.
Fast peer messagingGOOSE
Multicast messages distribute fast event states between devices, with sequence and retransmission behavior designed for dependable delivery.
Sample streamsSampled Values
High-rate streams carry sampled current and voltage values, commonly between merging units and protection or measurement functions.
Engineering filesSCL
XML-based Substation Configuration Language files describe devices, communication, DataSets, reports, GOOSE, Sampled Values and system intent.
OperationControl models
Direct and Select-Before-Operate define how approved commands are prepared, checked, executed and confirmed.
Common beginner mistakes
Keep these distinctions clear from the start.
IEC 61850 is not “Ethernet protection”
Ethernet is only part of the transport. The standard also defines data meaning, services, configuration and system engineering.
SCL is not automatically the live truth
SCL describes configured intent. The online IED model shows what the server currently exposes. A good workflow compares both.
Ping success is not MMS success
An IED can answer ping while TCP port 102, association, permissions or the application service still fails.
A good-looking value may still be invalid
Always read quality and timestamp before treating a displayed value as evidence.
Is IEC 61850 only a communication protocol?
No. It combines standardized data models, communication services, engineering configuration through SCL and broader system-design concepts.
Does every IEC 61850 device use exactly the same model?
No. The standard defines common classes and naming rules, but optional data, extensions and implementation details still vary. Discover and validate the actual IED.
What should I learn after this page?
Connect one approved IED, discover its live model, then read one point together with quality and timestamp. After that, learn DataSets and Reporting.
Next practical stepOpen one IED and connect the names to real data.
The next tutorial shows how to prepare the network, add an IED by IP address in ARSAS, complete discovery and verify your first live value.
+ {{> footer}}
+
+
diff --git a/scripts/apply-search-authority.py b/scripts/apply-search-authority.py
index 5b45ac6..74fdaad 100644
--- a/scripts/apply-search-authority.py
+++ b/scripts/apply-search-authority.py
@@ -15,6 +15,16 @@
DEFAULT_GRAPH = ROOT / "landing" / "search-authority.json"
GUIDE_ROLES = {"guide"}
DISCOVERY_ROLES = {"capability", "solution"}
+ALLOWED_ROLES = {"capability", "solution", "guide", "hub", "authority", "learning", "tutorial"}
+INDONESIAN_PAGES = {
+ "id.html", "unduh.html", "catatan-rilis.html", "panduan-mulai-arsas.html",
+ "pusat-belajar-iec61850.html", "apa-itu-iec61850.html", "cara-hubungkan-ied-ip-arsas.html",
+ "faq-arsas.html", "bukti-kompatibilitas.html", "demo-arsas.html", "panduan.html",
+ "mms-client-iec61850.html", "smart-reporting-iec61850.html", "analyzer-goose-iec61850.html",
+ "transfer-file-comtrade-iec61850.html", "workspace-scl-iec61850.html",
+ "bukti-fat-iolist-iec61850.html", "pengujian-fat-iec61850.html", "pengujian-sat-iec61850.html",
+ "commissioning-iec61850.html", "integrasi-multi-vendor-iec61850.html",
+}
def load_object(path: Path, label: str) -> dict[str, Any]:
@@ -88,7 +98,7 @@ def validate_graph(graph: dict[str, Any], entries: dict[str, dict[str, Any]]) ->
if cluster not in clusters:
raise SystemExit(f"Search authority node {path} uses unknown cluster {cluster}")
role = text(node.get("role"), f"nodes.{path}.role")
- if role not in {"capability", "solution", "guide", "hub", "authority"}:
+ if role not in ALLOWED_ROLES:
raise SystemExit(f"Search authority node {path} has invalid role {role}")
localized(node, "label", "en")
localized(node, "label", "id")
@@ -103,8 +113,8 @@ def validate_graph(graph: dict[str, Any], entries: dict[str, dict[str, Any]]) ->
for source, raw_targets in pages.items():
if source not in normalized_nodes:
raise SystemExit(f"Search authority source has no node metadata: {source}")
- if not isinstance(raw_targets, list) or not 2 <= len(raw_targets) <= 4:
- raise SystemExit(f"Search authority source {source} must have two to four related pages")
+ if not isinstance(raw_targets, list) or not 2 <= len(raw_targets) <= 5:
+ raise SystemExit(f"Search authority source {source} must have two to five related pages")
targets = [text(item, f"pages.{source}") for item in raw_targets]
if len(targets) != len(set(targets)):
raise SystemExit(f"Search authority source {source} contains duplicate targets")
@@ -150,22 +160,26 @@ def section(source: str, language: str, nodes: dict[str, dict[str, Any]], pages:
source_node = nodes[source]
cluster = str(source_node["cluster"])
is_id = language == "id"
- kicker = "Jalur evidence terkait" if is_id else "Related evidence paths"
- heading = "Lanjutkan ke gejala atau workflow yang paling dekat." if is_id else "Continue with the closest failure mode or workflow."
- intro = (
- "Link berikut dipilih dari cluster engineering yang sama agar diagnosis berpindah dari gejala ke evidence yang relevan."
- if is_id else
- "These links stay inside the same engineering evidence cluster, moving from the current workflow to the most relevant failure mode."
- )
+ if cluster == "learning":
+ kicker = "Jalur belajar terkait" if is_id else "Continue learning"
+ heading = "Lanjutkan dari konsep menuju langkah praktis." if is_id else "Move from the concept to the next practical step."
+ intro = (
+ "Materi berikut dipilih agar Anda dapat memperdalam konsep, mencoba workflow ARSAS, atau menuju troubleshooting yang relevan."
+ if is_id else
+ "These pages help you deepen the concept, try the matching ARSAS workflow, or move to the relevant troubleshooting path."
+ )
+ else:
+ kicker = "Jalur evidence terkait" if is_id else "Related evidence paths"
+ heading = "Lanjutkan ke gejala atau workflow yang paling dekat." if is_id else "Continue with the closest failure mode or workflow."
+ intro = (
+ "Link berikut dipilih dari cluster engineering yang sama agar diagnosis berpindah dari gejala ke evidence yang relevan."
+ if is_id else
+ "These links stay inside the same engineering evidence cluster, moving from the current workflow to the most relevant failure mode."
+ )
cards: list[str] = []
for target in pages[source]:
target_node = nodes[target]
- target_language = "id" if target.endswith(".html") and target in {
- "mms-client-iec61850.html", "smart-reporting-iec61850.html", "analyzer-goose-iec61850.html",
- "transfer-file-comtrade-iec61850.html", "workspace-scl-iec61850.html",
- "pengujian-fat-iec61850.html", "pengujian-sat-iec61850.html",
- "commissioning-iec61850.html", "integrasi-multi-vendor-iec61850.html",
- } else "en"
+ target_language = "id" if target in INDONESIAN_PAGES else "en"
label = localized(target_node, "label", language)
summary = localized(target_node, "summary", language)
role = str(target_node["role"])
@@ -173,12 +187,17 @@ def section(source: str, language: str, nodes: dict[str, dict[str, Any]], pages:
"guide": "Panduan troubleshooting" if is_id else "Troubleshooting guide",
"capability": "Capability produk" if is_id else "Product capability",
"solution": "Workflow solusi" if is_id else "Solution workflow",
- }.get(role, "Evidence path")
+ "learning": "Materi belajar" if is_id else "Learning article",
+ "tutorial": "Tutorial software" if is_id else "Software tutorial",
+ "hub": "Pusat belajar" if is_id else "Learning hub",
+ "authority": "Referensi engineering" if is_id else "Engineering reference",
+ }.get(role, "Jalur terkait" if is_id else "Related path")
attrs = target_attributes(language, target_language)
+ link_label = "Buka materi" if cluster == "learning" and is_id else "Open lesson" if cluster == "learning" else "Buka jalur evidence" if is_id else "Open evidence path"
cards.append(
f'
{escape(role_label)}'
f'{escape(label)}
{escape(summary)}
'
- f'{"Buka jalur evidence" if is_id else "Open evidence path"} →'
+ f'
{escape(link_label)} →'
)
return (
f'
ARSAS
-