@prefix adms: . @prefix dcat: . @prefix dcterms: . @prefix ns1: . @prefix pkdata: . @prefix pko: . @prefix pplan: . @prefix prov: . @prefix xsd: . a pko:Procedure ; dcterms:created "2026-07-06T12:30:25.103000+00:00"^^xsd:dateTime ; dcterms:creator ; dcterms:description """The Information Flow Methodology (IFM) is a structured modeling approach for analyzing decisionmaking in socio-technical systems. It focuses on how information is transformed and used across both human and automated components, and how this structure shapes outcomes, responsibilities, and potential risks."""^^xsd:string ; dcterms:identifier "32ad1c3b-1c70-4b33-aefd-891bf9927df8" ; dcterms:modified "2026-07-06T13:07:52.709000+00:00"^^xsd:dateTime ; dcterms:references [ a dcat:Resource ; dcterms:format ; dcterms:title "Information Flow Model (IFM) – Methodological Guide" ; dcat:accessURL ] ; dcterms:title "Information Flow Methodology v0.6"^^xsd:string ; adms:status pko:Draft ; dcat:keyword "AI Act"^^xsd:string, "AI Fairness"^^xsd:string, "Information Flow"^^xsd:string ; ns1:compliesWith ; pko:hasFirstStep ; pko:hasProcedureTarget [ dcterms:title "Decision making process"^^xsd:string ; dcterms:type "Information Flow Modeling"^^xsd:string ; prov:atLocation ""^^xsd:string ] ; pko:hasProcedureType ; pko:hasStep ; pko:isAdoptedBy pkdata:deployers-auditors-and-developers-of-ai-systems-public-sector-high-risk-ai ; pko:versionNumber "0.0.1"^^xsd:string . a pko:Action ; dcterms:title "Arrange sites and channels into a draft graph. Focus on clarity over precision."^^xsd:string . a pko:Action ; dcterms:title "Ask, how do you perform this step? What does it result in?"^^xsd:string . a pko:Action ; dcterms:title " Ask stakeholders to describe the process and the steps they take. Note down each step."^^xsd:string . a pko:Action ; dcterms:title "Channels represent transformations between sites—decisions, filtering steps, interviews, or automated evaluations"^^xsd:string . a pko:Action ; dcterms:title "Different sketches from different perspectives may coexist and be compared or merged later."^^xsd:string . a pko:Action ; dcterms:title "From the initial sites and channels, start looking at known intermediary steps. What transformations occur between the start and end points? Break these steps into sites and channels"^^xsd:string . a pko:Action ; dcterms:title "Name each site and channel descriptively to make the model understandable to stakeholders using the terms they use"^^xsd:string . a pko:Action ; dcterms:title "Sketches can be based on interviews, documentation, system behavior, or stakeholder narratives."^^xsd:string . a pko:Action ; dcterms:title "Start and End Points: Identify where the flow begins (e.g., data entry, initial request) and ends (e.g., decision, output, action)."^^xsd:string . a pko:Action ; dcterms:title " Use descriptive names for sites and channels which reflect how each element would be understood by stakeholders."^^xsd:string . a pko:Action ; dcterms:title "What decisions, evaluations, calculations and transformations are part of this process? These are Channels and connect Sites together."^^xsd:string . a pko:Action ; dcterms:title "What information is used throughout the process? This includes documents, forms and decisions. These represent Sites. If they are changed during the process each state represents it’s own Site"^^xsd:string . a pplan:Variable ; dcterms:title " "^^xsd:string . a pplan:Variable ; dcterms:title "Result of steps I: One or several scaffolds of the information flow model, showing the decision process loosely expressed as named sites and channels."^^xsd:string . a pplan:MultiStep ; dcterms:description """The first step is to create a sketched *scaffold* of the decision process you want to analyze. This sketch should capture the overall structure of how information flows — what enters the process, how it changes, and what final decision or outcome it leads to. The goal is not precision or formal correctness but to capture the overall structure in broad terms, facilitating stakeholder engagement and input as well as overview."""^^xsd:string ; dcterms:identifier "1"^^xsd:string ; dcterms:title "Step 1: Sketching the Information Flow"^^xsd:string ; pplan:hasOutputVar , ; ns1:compliesWith ; pko:hasFirstStep ; pko:hasStep , , , ; pko:minRepetitions 1 ; pko:stepNumber "1.0"^^xsd:float . a pplan:Step ; dcterms:description """• What decision or process is being modeled? Clearly state the boundaries and purpose. • Start and End Points: Identify where the flow begins (e.g., data entry, initial request) and ends (e.g., decision, output, action). • Example: We are modeling a recruitment process. It starts with a request from a client and ends when a set of candidate profiles is delivered back."""^^xsd:string ; dcterms:identifier "1.1"^^xsd:string ; dcterms:title "I. Define the Scope of the Decision Process"^^xsd:string ; pplan:hasInputVar ; pplan:hasOutputVar , ; ns1:compliesWith ; pko:nextStep ; pko:requiresAction ; pko:stepNumber "1.1"^^xsd:float . a pplan:Step ; dcterms:description """ • What information is used throughout the process? This includes documents, forms and decisions. These represent Sites. If they are changed during the process each state represents it’s own Site. • What decisions, evaluations, calculations and transformations are part of this process? These are Channels and connect Sites together. • Channels represent transformations between sites—decisions, filtering steps, interviews, or automated evaluations. • Use descriptive names for sites and channels which reflect how each element would be understood by stakeholders. • Example: “Initial candidates” and ”Final candidates” could be sites; “Recruiter filter based on Interview.” and ”DB search” could be channels."""^^xsd:string ; dcterms:identifier "1.2"^^xsd:string ; dcterms:title "II. Identify inital Sites and Channels"^^xsd:string ; pplan:hasInputVar , ; pplan:hasOutputVar ; ns1:compliesWith ; pko:nextStep ; pko:requiresAction , , , ; pko:stepNumber "1.2"^^xsd:float . a pplan:Step ; dcterms:description """ sites and channels, start looking at known intermediary steps. What transformations occur between the start and end points? Break these steps into sites and channels. • Ask stakeholders to describe the process and the steps they take. Note down each step. • Ask, how do you perform this step? What does it result in? * Name each site and channel descriptively to make the model understandable to stakeholders using the terms they use. """^^xsd:string ; dcterms:identifier "1.3"^^xsd:string ; dcterms:title "III. Map the Decision Process"^^xsd:string ; pplan:hasInputVar , ; pplan:hasOutputVar ; ns1:compliesWith ; pko:nextStep ; pko:requiresAction , , , ; pko:stepNumber "1.3"^^xsd:float . a pplan:Step ; dcterms:description """• Arrange sites and channels into a draft graph. Focus on clarity over precision. • Sketches can be based on interviews, documentation, system behavior, or stakeholder narratives. • Different sketches from different perspectives may coexist and be compared or merged later. • Example: The process might include “Initial candidates” → “Filtered Candidates” → “Interview Outcomes” → “Final Suggestions.”"""^^xsd:string ; dcterms:identifier "1.4"^^xsd:string ; dcterms:title "IV. Construct the Initial Graph"^^xsd:string ; pplan:hasInputVar , ; pplan:hasOutputVar ; ns1:compliesWith ; pko:requiresAction , , ; pko:stepNumber "1.4"^^xsd:float . a pplan:Variable ; dcterms:title "Modeled System"^^xsd:string, "Modeled system"^^xsd:string . a pplan:Variable ; dcterms:title "IFM"^^xsd:string .