Lucas RosateQuality engineering · continuous improvement
Back to portfolio

CASE 04 / SISVE: audit and action management

SISVE: audits and actions across 16 industrial processes

I designed SISVE to connect audits, records, actions, due dates, evidence and assessment of effectiveness and recurrence across 16 industrial processes.

04.1 / Context

Disconnected audit and action stages

Execution needed to connect to action follow-up. Records, evidence, owners, deadlines and assessment of effectiveness and recurrence had to become one traceable workflow.

Investigating the problem

The critical point was the handoff between records, ownership and follow-up. Without that connection, auditing and corrective work appeared as separate stages even when digital records existed.

Implementation constraints

Audits, action execution and management analysis needed a shared, traceable history. Task completion had to remain distinct from assessment of effectiveness.

Fragmented cycleAudits, actions and management views appeared as disconnected stages.
Follow-upOwners and due dates needed a clear operational layer.
AssessmentEffectiveness and recurrence were assessed after the task was completed.

04.2 / Development

Power Platform and Qlik Sense in the audit cycle

Power Apps organised the interface; SharePoint held records and history; Power Automate supported notifications and integrations; Planner managed actions; and Qlik Sense provided an integrated operational view.

Audit: Power Apps — structured execution → Record: SharePoint — evidence and history → Deviation: Traceable corrective action starts → Task: Planner — owners and due dates → Actions: Power Automate — notifications and integration → Assessment: Effectiveness and recurrence after action → Integrated view: Qlik Sense — analysis across 16 processes01AuditPower Apps — structuredexecution02RecordSharePoint — evidence andhistory03DeviationTraceable corrective actionstarts04TaskPlanner — owners and due dates05ActionsPower Automate — notificationsand integration06AssessmentEffectiveness and recurrenceafter actionIntegrated view — Qlik Sense — analysis across 16 processes
  1. Audit

    Power Apps — structured execution

  2. Record

    SharePoint — evidence and history

  3. Deviation

    Traceable corrective action starts

  4. Task

    Planner — owners and due dates

  5. Actions

    Power Automate — notifications and integration

  6. Assessment

    Effectiveness and recurrence after action

  7. Integrated view

    Qlik Sense — analysis across 16 processes

↺ Effectiveness and recurrence history informs subsequent audit analysis.

Select a stage to explore its role in the flow.

← Scroll horizontally to explore the diagram →

Conceptual representation · no internal dataPower Apps · SharePoint · Power Automate · Planner · Qlik Sense

04.3 / Project decisions

Each component closed a specific stage of the cycle.

Clear responsibilities across applications preserved traceability.

Technical risk

A form alone does not create a follow-up system.

Separate interface and record

The application guided execution while the data structure retained history and traceability.

Technical risk

Actions lose continuity without explicit owners and deadlines.

Connect actions and ownership

Automations created and updated activities while keeping due dates and owners visible.

Technical risk

Closing a task does not establish that its cause has been eliminated.

Assess outcomes within the same cycle

Qlik Sense supported analysis of audits, nonconformities, actions and patterns by process.

From decision to implementation

  1. Record the finding

    Power Apps guided audit execution; SharePoint held records, evidence and history.

  2. Assign and follow up

    Power Automate supported notifications and integrations; Planner made activities, owners and deadlines visible.

  3. Assess in process context

    Qlik Sense brought together audits, nonconformities and actions to examine effectiveness, recurrence and patterns across the 16 processes.

16industrial processes in the system

04.4 / Evidence and outcomes

Traceability from audit to effectiveness assessment

SISVE structured the relationship between execution, ownership, deadlines, evidence and outcome assessment. The 16 processes describe system coverage, not a measured reduction in nonconformities.

  • standardised and traceable records;
  • clearer ownership and due dates;
  • audit execution connected to action follow-up;
  • operational and management views in one system.

Verification / interpreting the evidence

System coverage

The 16 processes describe SISVE coverage. The documented outcome is the connection between records, actions and assessment, not a percentage reduction in nonconformities.

Engineering criterion

The cycle closes through effectiveness and recurrence assessment. History informs subsequent audit analysis instead of treating every record as an isolated event.

Limits of the public evidence

Recurrence rates, closure times and internal datasets are not published. System coverage is not converted into unmeasured quantitative gains.

04.5 / Synthesis

Learning

Explicit responsibilities for the interface, records, automation and analysis preserved traceability between execution and outcome assessment.