Turn MMS Client and Smart Reporting into bilingual practical tutorials - #118
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7ee0cc5938
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| <section class="section section-tight"><div class="container comparison-grid"><article class="comparison-panel highlight"><span class="kicker">Before you start</span><h2>Collect the target facts.</h2><ul><li>Approved IED name, bay or function</li><li>IP address, subnet and approved route</li><li>Expected TCP port 102 availability</li><li>Expected vendor or model identity</li><li>Permission to connect from this workstation</li></ul></article><article class="comparison-panel"><span class="kicker">Safety boundary</span><h2>Keep the first session read-only.</h2><p>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.</p></article></div></section> | ||
|
|
||
| <section class="section" id="tutorial"><div class="container"><div class="section-head center"><span class="kicker">Step-by-step in ARSAS</span><h2>From approved IP address to one attributable value.</h2><p>Do not skip identity and quality checks merely because the association succeeds.</p></div><div class="step-list"><article class="step"><span class="step-number">01</span><div><h3>Confirm the target and network path</h3><p>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.</p><div class="section-actions"><a class="btn" href="port-102-connection-failed.html">Diagnose port 102</a></div></div></article><article class="step"><span class="step-number">02</span><div><h3>Select Add IED</h3><p>Open <strong>General IEC 61850 Testing</strong>, choose <strong>Add IED</strong>, enter a clear device name, the approved IP address and port 102 unless the project specifies another endpoint.</p></div></article><article class="step"><span class="step-number">03</span><div><h3>Complete the MMS association</h3><p>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.</p></div></article><article class="step"><span class="step-number">04</span><div><h3>Inspect identity and live-model discovery</h3><p>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.</p></div></article><article class="step"><span class="step-number">05</span><div><h3>Find the intended object and Functional Constraint</h3><p>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.</p></div></article><article class="step"><span class="step-number">06</span><div><h3>Verify the first trustworthy value</h3><p>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.</p></div></article></div></div></section> |
There was a problem hiding this comment.
When a user follows step 6 in the MMS live-value workspace, the tutorial requires an “ARSAS capture time,” but the relevant grids expose only Signal/IEC Telegram, Value, Quality, IED Timestamp, and Acquisition (MainWindow.xaml:435-442 and 757-765); no capture-time field is visible. Consequently, users cannot complete the evidence checklist as written in either language, so either limit the step to displayed fields or expose the capture timestamp in this workflow.
Useful? React with 👍 / 👎.
| <meta name="viewport" content="width=device-width, initial-scale=1" /> | ||
| <title>IEC 61850 Smart Reporting — BRCB, URCB and Fallback | ARSAS</title> | ||
| <meta name="description" content="Learn how ARSAS validates IEC 61850 BRCB and URCB coverage, handles occupied RCBs and empty DataSets, recovers exact gaps and preserves bounded polling fallback." /> | ||
| <title>How IEC 61850 Reporting Works — BRCB, URCB and DataSets | ARSAS</title> |
There was a problem hiding this comment.
These pages are substantially rewritten in the July 29 commit, but their registry entries remain dated July 27 for MMS and July 20 for Smart Reporting (landing/site.json:71-74). Because write_sitemap copies those values verbatim (scripts/build-product-site.py:360), the deployed sitemap falsely tells crawlers that all four tutorials predate this update; refresh the four lastmod values alongside the template changes.
Useful? React with 👍 / 👎.
1 participant
Purpose
Continue the ARSAS Learning Center transformation by converting two high-intent capability pages from feature descriptions into practical, search-friendly tutorials.
MMS Client tutorial — English and Indonesian
Rewrites:
mms-client.htmlmms-client-iec61850.htmlThe new flow separates network reachability, TCP port 102, MMS association, live-model discovery and trustworthy data. It requires identity, object reference, Functional Constraint, value, quality, timestamp and acquisition source before an observation is treated as useful evidence.
Smart Reporting tutorial — English and Indonesian
Rewrites:
smart-reporting.htmlsmart-reporting-iec61850.htmlThe tutorial explains DataSet versus RCB, BRCB versus URCB, General Interrogation, integrity and trigger behavior, exact coverage, configured-report-first behavior, conditional recovery and visible polling fallback.
Search and learning structure
Each page now includes:
TechArticle,HowTo,FAQPageandBreadcrumbListstructured dataEngineering honesty
The tutorials do not claim that association proves interoperability, that GI proves spontaneous Reporting, that BRCB always provides continuity, or that polling is always failure. Configuration writes and active stimuli remain conditional on IED capability, approved procedure and authority.
Automated contracts
Adoption and public-deployment validators now enforce the bilingual pairs, required tutorial sections, six ordered steps, visible FAQs, structured data and Learning Center continuation paths.
Automated validation at head
7ee0cc5938a5918e2e35844c188aace93350e457Deploy product website run 159 — success
Validate adoption and field proof run 50 — success
Build search growth queue run 59 — success
Build ARSAS run 776 — success
Additional gates — success