no (Norwegian)

SESG Fall 2026: Demonstrating regulatory compliance with a requirements management system

SESG Fall 2026

At the Systems Engineering Study Group (SESG) meeting at USN Krona, industry experts demonstrated how requirements management systems support regulatory compliance.

Talks

TechnipFMC (Kirsten Helle and Helge Smedsrud): Requirements management systems. For safety-critical systems, external standards such as IEC 61511, API Std 17O and NORSOK S-001 are loaded into a requirements database (Polareon) and broken down to system and subsystem level, giving a traceable chain from planning through specification and verification to user manual. Their engineering and reliability programme follows ISO 20815 and is compliant with IEC 61511:2016.

Kongsberg Maritime (Morten Løvdok): “What is testing … really?” For software-intensive systems, requirements alone are not enough to ensure quality. Testing should start early in development, and its purpose is to find errors.

Workshop findings

Q1: Continuous compliance and learning. Does experience from testing and operations flow back into the requirements? All groups found that the feedback loop is rarely closed. Feedback depends heavily on individuals and is often not formalised. Information flows within departments but not across the organisation, and lost information is not taken seriously. Several groups stressed the difference between compliance and learning: a requirements system documents compliance, but it does not by itself make the organisation improve. Larger organisations tend to “do it the way we used to”, which raises the question of how long a company that doesn’t learn will last.

Company size and criticality matter. Growing companies need more formal ways of working, and the same people often work very differently on safety-critical and non-critical systems. Feedback tends to arrive late in projects, and fixed bugs can reappear in the next update. Verification is often squeezed for resources, so testers should be treated as stakeholders. Requirements are often “cast in stone”, although test results should be able to change them. Costs are committed early but spent late, and improvements need a budget and a return on investment.

Q2: AI in the compliance chain. Who signs, and who is accountable? The groups agreed that a human must still sign and be accountable, both for decisions and for keeping knowledge in the organisation. A key concern is that we do not know how AI reasons.

The workshop nevertheless ended on an optimistic note, with concrete opportunities for AI to help close the loop:

  • AI can detect inconsistencies in requirements.
  • AI can analyse operational data over long periods to improve specifications.
  • One model could verify another.
  • Prompt engineering may develop into prompt architecting.

Takeaways

The main challenge is organisational rather than technical: closing the loop from testing and operations back to requirements. Responsibility stays with people, but AI can become a powerful tool for continuous compliance and learning.

Thanks to Satya Kokkula for arranging the day, and to the speakers and all participants.