rygg
Find your starting point
Product compliance and customer requirements

One answer per requirement, valid for the part, the site and the date it is asked for

Product regulation in the EU is changing in several places at once, and customers send questionnaires with their own requirements. Teams answer the same questions again and again from different sources. rygg connects requirement, product, test and evidence, with the regulatory status and validity of each.

Find your starting pointDemo graph: Product compliance
Situation

Requirements come from regulation, standards and customer-specific requirements, in different formats and versions.

Evidence exists, but its scope is unclear: which part, which site, which version of the requirement, valid until when.

Customer questionnaires are answered by hand, by several people, and the answers do not always match.

Questions rygg answers
  • Which parts and products are affected by this change in a requirement?
  • Which evidence covers this requirement for this site and this period?
  • What did we answer to this question last time, and is it still valid?
  • Which obligations are adopted, which are drafts, and since when do they apply?
  • Which decision on a substitution was taken, with which options and test results?
Applications in this use case

Product compliance and customer requirements: 4 applications

context engineering with rygg
Impact of a changed requirement

From a changed requirement or substance to the affected materials, parts, programs and customers.

Agent context
Agent task
Runs the reverse search and lists affected objects with path
Reads
Requirements with status, bill-of-material links, customers
Suggests
Impact list with paths
Approved by
Product compliance
Metric: Affected parts found, checked against manual review
Customer questionnaires

Each customer question is mapped to a canonical requirement and answered from valid evidence.

Agent context
Agent task
Drafts answers from canonical requirements
Reads
Canonical requirements, evidence with validity, earlier answers
Suggests
Answer drafts with source and validity
Approved by
Key account and compliance
Metric: Time per questionnaire; consistent answers
Validity of evidence

Certificates, test reports and supplier declarations with scope and expiry date, so nothing is used after it has expired.

Agent context
Agent task
Flags expiring evidence and drafts requests to suppliers
Reads
Evidence with scope and expiry date
Suggests
Expiry list, request drafts
Approved by
Purchasing and compliance
Metric: Expired evidence still in use
Substitution decisions

When a material or component has to be replaced: options, tests, costs and the reasons for the choice.

Agent context
Agent task
Assembles options with test results and open questions
Reads
Options, test results, affected requirements
Suggests
Decision template with sources
Approved by
Engineering board
Metric: Substitutions with a complete record
What rygg provides
  • Obligation as a node, separated from its legal basis, with a versioned regulatory status
  • Evidence with scope and validity: part, site, period, version of the requirement
  • Answer drafts for questionnaires with sources, approved by the responsible role
  • Reverse search: from a changed requirement to affected parts, programs and customers
Who works with it
  • Head of product compliance, regulatory affairs
  • Quality and product safety
  • Sales and key account management
  • Purchasing for supplier declarations
Metrics we agree on
  • Time per customer questionnaire, measured before and after
  • Share of answers with a valid source
  • Evidence that has expired and is marked as such
  • Affected parts found per change, checked against manual review
What rygg is not here

Not a compliance suite, material database or legal advice. rygg shows missing evidence, not violations.

How it starts

An evidence project for one product family and two sets of requirements, with the current effort for customer requests measured. Then a pilot with a questionnaire agent.

Find your starting point
Usually starts withEvidence Project

Research and design to HCRD standards. Results are documented so they can become part of a graph.

 Demo graphProduct compliance

Requirements, parts, tests and evidence with validity, customer questionnaires and the reverse search from a changed requirement.