The complete SafeSuite feature demonstrator and a live team-server demo: this repository is the server. Two ways in:
- Open from Team Server (File menu): URL
https://github.com/SafeTwice/SafeSuite-Showcase.gitinto an empty folder (private repo: save a GitHub token first under Team server settings -> Server credentials, hostgithub.com). - Clone manually to
C:\Demo\SafeSuite-Showcaseand openModel.ssproject.
Start with SHOWCASE.md - the guided tour of every feature. reset.cmd restores
the bench to pristine state at any time.
Governance (who may do what, and the proof of it) lives under Governance/: run
Governance\become.cmd elena-vidal to act as the safety manager (passphrase agripto), then open
Governance/Governance_Guide.strdoc — the Governance section of SHOWCASE.md summarises it.
The project is bound to SafeTwice's Jira site (project MYN): enable the experimental Jira integration, add your own API token, and try issue linking, two-way assignment, issue creation and the JQL import — the Jira integration section of SHOWCASE.md walks through it.
Rear PTO control system of the (fictional) Ager Dynamics T6100 tractor, developed end-to-end to EN ISO 25119:2023: HARA with AgPLr d, Category 3 dual-channel architecture, MTTFd/DC/CCF metrics computed from a real IEC/TR 62380 prediction, SRL 2 software, safety validation, assessment and release — all as native SafeSuite documents (.strdoc) plus native analysis artifacts (SafeFIT .sfit, SafeFMEA .sfmea, SafeTree .fta) and PDF deliverables.
Open Model.ssproject in SafeSuite and start with
0_Guide/Feature_Guide.strdoc — the standard documentation lives in the
structured documents, not in this file.
Generated by demos/agri-pto-generator in the SafeSuite repository; the
record layer (baselines, signatures, activity log) is built with the real
product code so every hash verifies.