{ "ces_concepts_varient_d_une_organisation_a_l_autre_et_la_plupart_": "— these concepts vary from one organisation to another and most warehouses don't document them. Without explicit context, the agent returns answers that are technically correct but operationally wrong.", "et_trouvent_les_passages_conceptuellement_similaires": "— and find conceptually similar passages.", "interesse": "— Interested? —", "une_recette_exclusive": "— An Exclusive Recipe —", "target_record": "; target: Record", "l_ia_peut_en_extraire_sentiment_produits_mentionnes_problemes_id": "? AI can extract sentiment, mentioned products and identified issues from it.", "cree_la_structure_de_satellite_standard_pour_cette_source_a_part": "“Create the standard satellite structure for this source using our template.”", "d_ou_vient_ce_chiffre_devient_une_requete_pas_une_enquete": "“Where does this number come from?” becomes a query, not an investigation.", "quels_concepts_metier_sont_lies_au_domaine_client": "“Which business concepts are connected to the customer domain?”", "loads_public_locales": "(); /** Loads /public/locales/", "l_agent_ajoute_un_case_statement_et_regenere": "→ the agent adds a CASE statement and regenerates.", "agents_focalises_la_plupart_des_plateformes_agent_permettent_de_": "**Focused agents.** Most agent platforms allow you to filter which tools an agent can access from the MCP server. You can create a simple agent with 2-3 tools for a specific task, or a comprehensive agent with access to the entire catalog.", "assurance_qualite_ne_supposez_pas_que_les_sorties_ia_sont_parfai": "**Quality Assurance.** Do not assume that AI outputs are perfect. Apply business rules, statistically monitor accuracy and confidence, and implement human review on a sample basis for critical cases. beVault's Verify module simplifies this work with integrated validation rules.", "auditabilite_chaque_sortie_ia_est_stockee_avec_son_contexte_comp": "**Auditability** — Every AI output is stored with its complete context: timestamp, model version, prompt, confidence score.", "burden_de_configuration_chaque_endpoint_api_doit_etre_mappe_a_un": "**Configuration burden.** Each API endpoint must be mapped to a tool. And with new agent frameworks constantly emerging, switching platforms means rebuilding the entire configuration.", "cas_1_l_ia_accelere_l_implementation_data_vault_des_agents_ia_ex": "**Case 1 — AI accelerates Data Vault implementation.** AI agents use the beVault API to create hubs, links, satellites and mappings from a natural-language description. What used to take an hour now takes two minutes.", "cas_2_les_sorties_ia_deviennent_une_source_data_vault_sentiment_": "**Case 2 — AI outputs become a Data Vault source.** Sentiment, extracted entities, detected anomalies — these insights are stored, versioned and governed like any other source data. A virtuous cycle where AI both consumes and feeds the warehouse.", "cas_3_bevault_comme_fondation_ia_donnees_centralisees_qualite_ve": "**Case 3 — beVault as an AI foundation.** Centralized data, continuously verified quality, rich business metadata, automated documentation — everything AI agents need for sound reasoning.", "comment_ca_marche_des_agents_ia_qui_raisonnent_sur_des_objectifs": "**How it works:** AI agents that reason about goals, select the appropriate tools from a set of available APIs, and iterate towards solutions through conversation.", "comment_ca_marche_un_serveur_mcp_model_context_protocol_agit_com": "**How it works:** an MCP Server (Model Context Protocol) acts as an intelligent gateway between agents and your APIs. It encapsulates complex orchestration logic and exposes high-level tools in business language. Any MCP-compatible agent platform can connect without specific configuration.", "comment_ca_marche_une_state_machine_lineaire_recuperer_des_donne": "**How it works:** a linear state machine — retrieve data, call the AI API with a structured prompt, receive a formatted response, update beVault via API. No human interaction, just sequential orchestration.", "comment_ca_marche_en_pratique": "**How it works in practice:**", "complexite_encapsulee_toute_l_orchestration_vit_dans_le_serveur_": "**Encapsulated complexity**: all orchestration lives in the MCP server. The agent speaks pure business language.", "consolidation_un_seul_modele_oriente_metier_bevault_integre_chaq": "**Consolidation — a single business-oriented model.** beVault integrates every source system into a unified Data Vault 2.0 model. Agents no longer query 50 connectors — they query a single point with a consistent structure. New source? Add it once, and every agent benefits.", "contexte_metier_absent_une_table_c_est_juste_des_noms_et_des_nom": "**Missing business context.** A table is just names and numbers — unless metadata explains what they mean. \\", "contexte_riche_via_les_metadonnees_chaque_hub_lien_et_satellite_": "**Rich context via metadata.** Each hub, link and satellite is documented with business definitions, usage rules and semantic relationships. When an agent queries \\", "deploiement_on_premise_possible_pour_les_organisations_avec_des_": "**On-premise deployment** possible for organizations with data sovereignty requirements: beVault on-prem, Qdrant or pgvector, Ollama for the LLM, n8n for agent logic. No data leaves your infrastructure.", "donnees_dispersees_entre_des_dizaines_de_systemes_les_agents_ia_": "**Data dispersed across dozens of systems.** AI agents perform best with three to five clearly defined tools. Companies present them with dozens of connectors to heterogeneous systems. Result: slow logic, unpredictable behavior, infernal maintenance.", "envoyer_le_sql_a_anthropic_claude_avec_un_prompt_structure": "**Send** the SQL to Anthropic Claude with a structured prompt", "etape_1_etablir_la_fondation_identifiez_vos_actifs_non_structure": "**Step 1 — Establish the foundation.** Identify your unstructured assets that AI could enrich. Customer emails linked to a hub \\", "etape_2_creer_la_couche_de_consommation_ia_via_le_module_distrib": "**Step 2 — Create the AI consumption layer.** Via the beVault Distribute module, create an Information Mart designed for AI consumption. This mart contains everything the model needs: business keys, file references, contextual metadata. Name columns clearly — AI performs better with well-named fields.", "etape_3_concevoir_vos_prompts_pour_une_sortie_structuree_c_est_l": "**Step 3 — Design your prompts for structured output.** This is the key success factor that most implementations miss. AI models are conversational by default. You need machine-readable JSON. Here's a real example used at dFakto for destination extraction:", "etape_4_orchestrer_avec_states_l_orchestrateur_bevault_gere_l_in": "**Step 4 — Orchestrate with States.** The beVault orchestrator manages the integration between your Data Vault and the AI provider: querying the mart, building the API call, execution, and storing the result in staging. States centralises the orchestration logic in a configuration-driven approach — no custom scripts to maintain.", "etape_5_modeliser_la_sortie_ia_comme_source_dans_le_module_sourc": "**Step 5 — Model the AI output as a source.** In beVault's Source module, add your AI provider as a source. Use a two-table approach:", "etape_6_fermer_la_boucle_dans_le_module_distribute_creez_des_inf": "**Step 6 — Close the loop.** In the Distribute module, create Information Marts that combine traditional structured data with AI insights. A customer analytics mart can now include CRM data, sentiment scores from support interactions, topics extracted from emails, and segment predictions.", "gain_de_temps_30_60_min_manuellement_2_3_min_avec_l_ia_90": "**Time saving**: 30-60 min manually → 2-3 min with AI (−90%)", "gouvernance_amelioree_lineage_complet_format_coherent_aucune_doc": "**Enhanced governance**: full lineage, consistent format, no missed documentation", "gouvernance_les_sorties_ia_passent_par_les_memes_controles_quali": "**Governance** — AI outputs go through the same quality controls, access rights and business rules as any other data.", "l_architecture_un_agent_avec_un_seul_outil_d_acces_aux_metadonne": "**The architecture.** An agent with a single tool for accessing Data Vault model metadata, and a system prompt containing SQL templates with placeholders.", "l_avantage_dynamique_quand_vous_ajoutez_un_nouvel_outil_au_serve": "**The dynamic advantage.** When you add a new tool to the MCP server, all connected agents access it immediately. No reconfiguration, no updating of tool definitions.", "l_opportunite_un_script_avec_50_colonnes_peut_prendre_une_heure_": "**The opportunity:** a script with 50 columns can take an hour to document manually. With AI automation, this drops to 2-3 minutes — a 90%+ reduction while improving consistency.", "l_orchestration_avec_states_automatise_l_ensemble_extraction_des": "**Orchestration with States** automates the whole process: source extraction, loading into the vault, Verify checks, and feeding the vector store and marts. AI always works with fresh, validated data.", "le_defi_les_utilisateurs_metier_connaissent_les_insights_dont_il": "**The challenge.** Business users know the insights they need but lack SQL skills. Engineers spend hours on repetitive SQL following predictable patterns. Both scenarios benefit from AI assistance that understands the context.", "lineage_et_conformite_rgpd_ai_act_si_vous_ne_pouvez_pas_tracer_q": "**Lineage and compliance**: GDPR, AI Act — if you cannot trace which data influenced which decision, an audit can shut the system down.", "maintenance_centralisee_quand_l_api_bevault_change_vous_mettez_a": "**Centralised maintenance**: when the beVault API changes, you update the MCP server once. All connected agents benefit immediately.", "maintenance_centralisee_une_mise_a_jour_beneficie_a_tous_les_age": "**Centralized maintenance**: one update benefits all connected agents", "maitriser_les_couts_api_testez_d_abord_sur_10_50_enregistrements": "**Master API costs.** Test first on 10-50 records with cheaper models (Claude Haiku, GPT-3.5 Turbo). Evaluate quality. Upgrade only if accuracy is insufficient. Process non-urgent data in batches during off-peak hours.", "meilleure_collaboration_les_utilisateurs_metier_comprennent_les_": "**Improved collaboration**: business users understand data products without reading SQL", "mettre_a_jour_les_metadonnees_de_colonnes_via_l_api_bevault": "**Update** column metadata via the beVault API", "moins_d_erreurs_pas_de_fautes_de_frappe_dans_les_noms_de_colonne": "**Fewer errors**: no typos in column names or entity references", "moins_de_tokens_des_outils_de_haut_niveau_clairs_reduisent_la_co": "**Fewer tokens**: clear, high-level tools reduce LLM consumption. In our early tests, the MCP server cut token usage by 90% for the same requests.", "moins_de_tokens_des_outils_simples_et_clairs_reduisent_la_consom": "**Fewer tokens**: simple, clear tools reduce LLM consumption (−90% in our first tests)", "parser_la_reponse_json_contenant_les_metadonnees": "**Parse** the JSON response containing the metadata", "portabilite_technologique_pointez_n_importe_quelle_plateforme_ag": "**Technological portability**: point any agent platform (n8n, Claude Desktop, LangChain) at the same MCP Server endpoint. No need to rebuild tools.", "portabilite_changez_de_plateforme_agent_sans_reconstruire_les_in": "**Portability**: change agent platforms without rebuilding integrations", "pour_les_donnees_qualitatives_descriptions_retours_clients_conte": "**For qualitative data** (descriptions, customer feedback, text content): loaded into a vector store (Chroma, Pinecone, pgvector, Qdrant). Agents perform semantic search — \\", "pour_les_donnees_quantitatives_kpis_chiffres_de_vente_metriques_": "**For quantitative data** (KPIs, sales figures, performance metrics): exposed via dedicated Information Marts. The agent calls the mart and receives structured and precise results.", "prise_de_decision_apres_chaque_action_il_evalue_le_resultat_et_d": "**Decision-making**: after each action, it evaluates the result and decides on the next step", "proliferation_des_outils_les_agents_fonctionnent_mieux_avec_peu_": "**Tool proliferation.** Agents work best with few, clear tools. Too many available APIs → orchestration errors, increased token usage, less predictable behaviour.", "qualite_continue_le_module_verify_chaque_chargement_passe_par_de": "**Continuous quality — the Verify module.** Every load goes through completeness, consistency and anomaly checks. Decision-makers trust AI outputs because they rest on data that has passed these validations, with lineage for every rule applied.", "qualite_incertaine_l_ia_accepte_la_donnee_telle_quelle_des_valeu": "**Uncertain quality.** AI accepts data as it comes. Missing values, inconsistent formats, duplicates — these flaws don't show up in the interface, but they resurface in the recommendations. Decision-makers' trust collapses quickly.", "qualite_insuffisante_un_modele_entraine_sur_des_donnees_incomple": "**Insufficient quality**: a model trained on incomplete or inconsistent data inherits those flaws. Trust collapses at the first errors.", "quand_l_utiliser_taches_repetitives_bien_definies_equipe_qui_deb": "**When to use it:** well-defined repetitive tasks, a team new to AI, quick results without complex infrastructure.", "quand_l_utiliser_vous_avez_besoin_de_dialogue_iteratif_les_gains": "**When to use it:** you need iterative dialogue, the productivity gains justify the complexity, your team has the technical capacity.", "quand_l_utiliser_vous_planifiez_plusieurs_agents_la_maintenabili": "**When to use it:** you are planning multiple agents, long-term maintainability is a priority, platform independence is strategically important.", "recuperer_le_sql_du_script_depuis_bevault": "**Retrieve** the SQL from the script from beVault", "resolution_iterative_il_raffine_son_approche_jusqu_a_atteindre_l": "**Iterative resolution**: it refines its approach until the goal is reached", "retraitement_conservez_les_references_aux_fichiers_originaux_pou": "**Reprocessing** — Keep references to original files to re-process them with improved models at any time.", "sources_fragmentees_des_dizaines_de_systemes_avec_leurs_propres_": "**Fragmented sources**: dozens of systems each with their own keys and conventions. The reconciliation effort often outweighs the value produced.", "table_staging_brute_stocke_le_json_complet_tel_que_recu_avec_req": "**Raw staging table**: stores the full JSON as received, with request_id, timestamp, model version, prompt version, reference to the input, raw JSON, API latency and API cost.", "usage_d_outils_l_agent_selectionne_parmi_plusieurs_apis_disponib": "**Tool usage**: the agent selects among several available APIs depending on the situation", "versioning_persistez_les_resultats_de_versions_successives_de_mo": "**Versioning** — Persist the results of successive model versions side-by-side to measure which performs better on identical data.", "versionner_les_prompts_comme_du_code_toute_modification_change_l": "**Version your prompts like code.** Any change alters the extraction logic. Store each version as metadata in your Data Vault.", "vue_de_staging_parse_le_json_et_le_pivote_en_format_relationnel_": "**Staging view**: parses the JSON and pivots it into a relational format ready for Data Vault modeling.", "2026_dfakto_bevault": "© 2026 dFakto — beVault", "integrations_et_deploiement": "← Integrations and deployment", "toutes_les_plateformes": "← All Platforms", "1_an": "< 1 year", "1_7_etp": "−1.7 FTE", "2_1_etp": "−2.1 FTE", "90_de_temps_de_reporting": "−90% reporting time", "equipe_dfakto_projets_regules": "✅ dFakto team, regulated projects", "maintenabilite_portabilite_couts_reduits_experience_agent_simpli": "✅ Maintainability, portability, reduced costs, simplified agent experience.", "oui_a_l_execution_du_chargement": "✅ Yes, when the load runs", "oui_avec_lignage": "✅ Yes, with lineage", "oui_avec_lignage_complet": "✅ Yes, with full lineage", "oui_avec_quarantaine_et_score": "✅ Yes, with quarantine and score", "oui_aws_step_functions": "✅ Yes, AWS Step Functions", "oui_certifie": "✅ Yes, certified", "oui_dans_la_plateforme": "✅ Yes, within the platform", "oui_produit_complet": "✅ Yes, complete product", "oui_serverless_aws_step_functions": "✅ Yes, serverless AWS Step Functions", "rapide_a_implementer_logique_simple_retour_sur_investissement_im": "✅ Fast to implement, simple logic, immediate ROI.", "resolution_interactive_pas_de_barriere_technique_pour_les_utilis": "✅ Interactive resolution, no technical barrier for business users, massive productivity gains.", "configuration_complexe_lock_in_plateforme_utilisation_de_tokens_": "❌ Complex configuration, platform lock-in, higher token usage.", "investissement_initial_en_developpement_expertise_technique_requ": "❌ Initial development investment, technical expertise required.", "pas_d_adaptabilite_gestion_d_erreurs_limitee_usage_unique": "❌ No adaptability, limited error handling, single use.", "m_name_m_role": "${m.name} — ${m.role}", "0_group_columns": "0 || group.columns) &&", "0_5_a_1_etp_dedie": "0.5 to 1 dedicated FTE", "1_cout_actuel_par_source_integree": "1. Current cost per integrated source", "10_minutes_chiffres_et_suite": "10 minutes — figures and next steps", "10_minutes_votre_contexte": "10 minutes — your context", "100_bruxelloise": "100% Brussels-based", "11_mars_2026": "March 11, 2026", "11_rapports": "11 reports", "12_000_planificateurs": "12,000+ planners", "12_000_planificateurs_d_evenements_interrogent_en_langage_nature": "12,000+ event planners query certified destination data in natural language, built on beVault.", "12_000_planificateurs_pcma_accedent_a_des_donnees_dont_la_fiabil": "12,000+ PCMA planners access data with mechanical, not editorial, reliability. Each update passes the same validation.", "12_systemes_consolides_les_equipes_terrain_pilotent_sur_des_donn": "12 consolidated systems. Field teams drive decisions with reliable real-time data.", "12_systemes_independants_consolides_en_un_entrepot_unique_les_eq": "12 independent systems consolidated into a single warehouse. Field teams work with reliable real-time data.", "12_systemes_une_ville": "12 systems. One city.", "14_jours_4_heures": "14 days → 4 hours", "15_janvier_2026": "January 15, 2026", "18_juin_2026": "June 18, 2026", "2_consultants": "2 consultants", "2_volume_annuel_de_demandes": "2. Annual volume of requests", "22_avril_2026": "April 22, 2026", "25_minutes_la_plateforme_en_situation": "25 minutes — the platform in action", "27_novembre_2025": "November 27, 2025", "28_mai_2026_42_min": "May 28, 2026 · 42 min", "29_septembre_2026": "September 29, 2026", "3_8_etp": "3.8 FTE", "3_8_etp_recuperes": "3.8 FTE recovered", "3_8_m": "3.8 M", "3_8_m_calculs_executes_chaque_nuit": "3.8 M calculations executed nightly", "3_8_millions_de_calculs_par_nuit_pour_unifier_ventes_staffing_et": "3.8 million calculations nightly to unify sales, staffing, and finance across 7 countries.", "3_8_millions_de_calculs_par_nuit": "3.8 million calculations nightly.", "3_cout_de_maintenance_evite": "3. Maintenance cost avoided", "36_avenue_hoche": "36 avenue Hoche", "4_comparaison_au_cout_de_la_plateforme": "4. Comparison to platform cost", "45_minutes_en_visioconference_pour_comprendre_le_perimetre_et_l_": "45 minutes on a video call to understand the scope and approach. The most requested format.", "45_minutes_pour_voir": "45 minutes to see", "4h": "4h", "5_fevrier_2026": "February 5, 2026", "5_jours_de_production_mensuelle_quelques_heures_2_consultants_df": "Five days of monthly production → a few hours. Two dFakto consultants, no parallel infrastructure, no extra licence.", "7_pays": "7 countries", "70_a_85_des_projets_ia_meurent_entre_le_proof_of_concept_et_la_p": "70 to 85% of AI projects die between proof-of-concept and production. Technology, skills and expectations get the blame. The real cause: data infrastructure.", "8_systemes": "8 systems", "9_octobre_2025": "October 9, 2025", "a_deux_plus_vite": "together, faster.", "a_dire_clairement": "To state clearly", "a_ecrire_par_vos_equipes": "To be written by your teams", "a_maintenir_manuellement": "To maintain manually", "a_propos": "About", "a_propos_de_bevault_dfakto": "About beVault & dFakto", "a_retenir": "Key takeaway", "a_savoir": "Good to know", "a_titre_indicatif": "For information only", "a_verifier_selon_la_version_et_le_patron_mis_en_uvre": "To be confirmed depending on the version and pattern implemented", "a_votre_rythme": "At your own pace.", "a_votre_trajectoire_data": "that fits your data journey", "acceder": "Access", "acceder_a_l_e_learning": "Access the e-learning", "acceder_a_la_documentation": "Access documentation", "acceder_au_livre_blanc": "Access the white paper", "acceder_au_portail": "Access the portal", "accelerez_vos_projets_data": "Accelerate your data projects", "acces_a_la_plateforme_adapte_au_perimetre_retenu": "Platform access adapted to the selected scope", "acces_gouverne": "Governed access", "acces_reserve_aux_partenaires_actifs_enregistrement_des_opportun": "Access reserved for active partners: opportunity registration, deal tracking and sales resources.", "accompagnement": "Support", "accompagnement_commercial": "Sales support", "accompagnement_lors_des_evolutions_structurantes_nouveaux_domain": "Support during structural changes: new domains, shifts in business definitions, reworking a scope.", "accompagnement_par_des_praticiens": "Support by practitioners", "accompagnez_des_environnements_complexes_et_des_programmes_data_": "Support complex environments, deployment requirements and larger data programmes.", "accueil": "Home", "actualites": "News", "adaptee_a_votre_secteur_et_a_votre_plateforme_cible": "Adapted to your sector and target platform", "administration_publique": "Public administration", "administrations_agences_et_operateurs_publics": "Administrations, agencies and public operators", "administrations_agences_et_operateurs_publics_structurer_des_don": "Administrations, agencies and public operators: structure data spread across legacy systems, retain control of the infrastructure, and produce figures that can be reconstructed as of their date.", "agents_ia_interactifs": "Interactive AI agents", "agents_ia_interactifs_pour_le_data_vault_l_approche_api_directe": "Interactive AI agents for the Data Vault: the direct API approach", "agents_ia_pour_le_data_vault": "AI agents for Data Vault", "agents_ia_pour_le_data_vault_trois_architectures_trois_niveaux_d": "AI agents for Data Vault: three architectures, three maturity levels", "agoria": "Agoria", "ai_native_ne_signifie_pas_ajouter_un_chatbot": "AI-Native does not mean \"adding a chatbot\"", "aide_au_diagnostic_et_a_la_resolution_lorsque_vos_equipes_rencon": "Diagnostic and troubleshooting support when your teams encounter a situation they haven't seen before.", "ajout_de_nouvelles_sources_sans_refonte_du_modele_existant": "Adding new sources without redesigning the existing model.", "ajouter_d_autres_sources_et_domaines_faire_evoluer_le_modele_et_": "Add other sources and domains, evolve the model and open up new analytical and AI use cases, without rebuilding what already exists.", "ajouter_des_ingenieurs_n_accelere_pas": "Adding engineers does not speed things up", "ajoutez_de_nouveaux_systemes_sources_concepts_et_attributs_sans_": "Add new source systems, concepts and attributes without redesigning everything that already exists. The model evolves as the organization evolves.", "ajoutez_de_nouvelles_sources_de_nouveaux_concepts_et_attributs_s": "Add new sources, concepts and attributes without re-engineering the existing foundation.", "aller_plus_loin": "Go further", "amazon_redshift": "Amazon Redshift", "amazon_redshift_microsoft_sql_server_et_postgresql_sont_supporte": "Amazon Redshift, Microsoft SQL Server and PostgreSQL are supported today. Databricks and Microsoft Fabric are coming with the next release.", "ameliorer_en_continu": "Continuously improve", "amnesty_international": "Amnesty International", "analyse_d_impact": "Impact analysis", "analyse_d_impact_automatique_avant_chaque_evolution": "Automatic impact analysis before every change", "analyse_de_sentiment_depuis_du_texte_ou_de_l_audio": "Sentiment analysis from text or audio", "api_agents_ia": "API & AI Agents", "api_agents_ia_2": "API & AI Agents", "api_bevault_mcp_server_agents_et_controle_humain": "beVault API, MCP Server, agents and human oversight", "api_complete_serveur_mcp": "Full API & MCP Server", "api_complete_et_serveur_mcp_pour_piloter_la_plateforme": "Full API and MCP server to drive the platform", "api_et_agents_ia": "API and AI agents", "api_rest_complete_et_serveur_mcp": "Full REST API & MCP Server", "api_rest_complete_et_serveur_mcp_vos_scripts_vos_ci_et_vos_assis": "Full REST API & MCP Server: Your scripts, CI, and AI assistants drive the platform without workarounds.", "api_serveur_mcp_et_agents_ia": "API, MCP server and AI agents", "applications_anciennes_fichiers_plats_bases_sans_schema_document": "Legacy applications, flat files, databases without documented schemas: sources are loaded as they are and historized from the very first load, with no prior rewriting.", "applications_internes": "Internal applications.", "appliquer_les_regles_de_survivance_validees": "Apply the validated survivorship rules", "appliquer_vos_regles_de_modelisation_ou_votre_modele": "Apply your modeling rules or template.", "apportez_deux_rapports_qui_ne_tombent_pas_d_accord_nous_regardon": "Bring us two reports that disagree. We'll look at where the discrepancy comes from.", "approfondissez": "Dive deeper.", "approvisionnement_et_achats_partagent_les_memes_identifiants_met": "Supply chain and procurement share the same business identifiers as the rest of the chain.", "apres_la_mise_en_production_support_evolution_du_modele_et_integ": "After go-live: support, model evolution and integration of new sources, according to the scope agreed with you.", "apres_la_production": "After go-live", "apres_publication_en_batch": "Post-publication, in batch", "architectes_et_ingenieurs_data_qui_apportent_la_methode_la_conna": "Data architects and engineers who bring methodology, platform expertise and experience from environments comparable to yours.", "architecture": "Architecture", "architecture_bevault_utilisateurs_metavault_states_et_workers_so": "beVault architecture: users, metaVault, States and Workers, data sources, client infrastructure with target databases, and outputs", "architecture_cible": "Target architecture", "architecture_cible_et_choix_de_deploiement": "Target architecture and deployment choices", "architecture_cible_modele_decrit_dans_metavault_sources_integree": "Target architecture, model described in metaVault, integrated sources, quality controls, orchestration workflows, documented outputs and operational documentation.", "architecture_de_la_plateforme": "Platform Architecture", "architecture_on_premises_cloud_ou_hybride": "On-premises, cloud or hybrid architecture", "architecture_technique": "Technical Architecture", "argumentaires_elements_de_comparaison_et_accompagnement_sur_les_": "Sales arguments, comparison materials and support for early sales cycles, including in public procurement.", "arrive_bientot": "Coming soon", "article_suivant": "Next article", "articles": "Articles", "articles_produits": "Articles & products", "articles_techniques_strategie_data_et_retours_d_experience": "Technical articles, data strategy and feedback from experience.", "articulation_avec_les_traitements_aws_existants": "Integration with existing AWS processes", "assister_les_taches_de_modelisation_repetitives": "Assist with repetitive modeling tasks.", "assurance": "Insurance", "atelier_d_architecture": "Architecture workshop", "au_c_ur_de_bevault": "at the heart of beVault.", "au_lieu_d_exposer_la_complexite_brute_des_apis_a_l_agent_le_serv": "Instead of exposing the raw complexity of APIs to the agent, the MCP Server handles the technical details internally. It translates between how humans naturally phrase their requests and what APIs technically require.", "au_lieu_de_reconstruire_les_memes_structures_a_la_main_votre_equ": "Instead of rebuilding the same structures by hand, your team can create reusable processes that produce consistent results every time.", "au_niveau_de_la_tache_sans_rejeu_global": "At the task level, without global re-run", "au_dela_de_l_interface": "beyond the interface.", "au_dela_du_code": "Beyond the code", "aucun_bevault_s_appuie_sur_votre_plateforme": "None: beVault runs on your platform", "aucun_meme_metamodele": "None: same metamodel", "aucun_attribut_descriptif_aucune_relation_c_est_ce_depouillement": "No descriptive attribute, no relationship. This stripped-down nature is precisely what makes the hub the stable anchor point of the whole model: as long as the business identifies its customers the same way, the hub doesn't move, whatever changes occur in the source systems.", "aucun_chiffre_publie_sans_accord_du_client_concerne": "No figures published without the consent of the client concerned", "aucun_cout_de_licence_plateforme": "No platform license costs", "aucun_de_ces_postes_n_apparait_dans_une_comparaison_de_licences_": "None of these costs appear in a license comparison. All of them appear in your operations.", "aucun_engagement_a_l_issue_de_l_echange": "No commitment after the conversation", "aucun_proprietaire": "No owner", "aucune_inclus_dans_bevault": "None — included in beVault", "aucune_capacite_n_est_reservee_a_un_mode_de_deploiement_le_choix": "No capability is reserved for a specific deployment mode. The choice is an architecture decision, not a licensing tier — and it remains reversible: models and metadata are portable.", "aucune_dependance_a_un_service_proprietaire_vous_gardez_la_main": "No dependency on a proprietary service — you remain in control", "aucune_duplication_de_plateforme_les_agents_consomment_les_memes": "No platform duplication: agents consume the same definitions and the same marts as reporting tools. A business rule is changed once.", "aucune_licence_ni_integration_supplementaire": "No additional licenses or integrations", "aucune_zone_grise_de_gouvernance_non_plus_les_droits_la_tracabil": "No governance gray area either: rights, traceability, and history remain owned by the foundation, not delegated to the conversational layer.", "audit_independant_du_code_reellement_genere": "Independent audit of actually generated code", "auditabilite": "Auditability", "auditabilite_native": "Auditability by design", "augmenter_l_equipe_augmente_aussi_le_nombre_de_conventions_concu": "Growing the team also increases the number of competing conventions, code reviews and sync points. On non-standardized repetitive work, the marginal output of an additional engineer quickly becomes low.", "author": "author", "automatique_optimisee_par_moteur": "Automatic, optimized by engine", "automatique_optimisee_par_plateforme_cible": "Automatic, optimized by target platform", "automatisation": "Automation", "automatisation_data_vault": "Data Vault Automation", "automatisation_historique_d_entrepot_contre_plateforme_data_vaul": "Long-standing warehouse automation versus a certified, orchestrated Data Vault platform.", "automatisation_orientee_developpement_d_objets_d_entrepot": "Automation focused on warehouse object development", "automatisation_par_scripts_et_metadonnees": "Automation via scripts and metadata", "automatisation_reproductible": "Reproducible Automation", "automatiser_l_extraction_de_metadonnees": "Automate metadata extraction", "automatiser_l_extraction_de_metadonnees_avec_l_ia_fini_les_parse": "Automating metadata extraction with AI: no more SQL parsers", "automatiser_les_taches_de_modelisation_repetitives": "Automate repetitive modeling tasks", "automatisez_bevault": "Automate beVault", "automatisez_le_travail_repetitif_de_modelisation_et_de_generatio": "Automate repetitive modelling and generation work so your teams can deliver new data domains faster.", "autonomie": "Autonomy", "autres_secteurs": "Other sectors", "avant_de_parler_de_fonctionnalites_une_equipe_d_architecture_veu": "Before talking features, an architecture team wants to know what is installed, where it runs, what crosses the network, and what stays under its control. That's a question of architecture, not licensing.", "avant_de_reserver": "Before booking", "avant_projet_nous_relevons_trois_valeurs_avec_vous_le_delai_moye": "Before the project, we measure three values with you: the average time to integrate a source, the time spent on recurring reporting and the number of data incidents per quarter. These same values are revisited six and twelve months after go-live. No figure is published without the client's agreement.", "avantages_architecturaux": "Architectural benefits", "avantages_cles": "Key benefits:", "avec_bevault_le_sens_de_vos_donnees_est_capture_avec_le_modele_n": "With beVault, the meaning of your data is captured alongside the model. Business names, descriptions, relationships and source context help AI agents interpret your data correctly instead of working with isolated tables and ambiguous field names.", "avec_des_donnees_datees": "with dated data.", "avec_des_langages_de_programmation_courants_comme_python_ruby_ja": "Using common programming languages like Python, Ruby, Java or .NET, you can develop Workers tailored to your unique data processing needs.", "avec_l_api_et_les_agents_ia": "with APIs and AI agents.", "avec_l_api_vous_pouvez": "You can use the API to:", "avec_l_asl_states_construit_des_machines_a_etats_capables_de_ger": "Using ASL, States builds state machines that handle conditional branching, parallel execution and iterative processing.", "avec_moins_de_code_de_chargement_ecrit_a_la_main_des_modeles_coh": "With less hand-written loading code, consistent models and reusable information marts, each new use case becomes easier to deliver. The foundation grows with your organization instead of being replaced every time a source, business definition or AI tool changes.", "aws_step_functions": "AWS Step Functions", "aws_step_functions_est_pris_en_charge_comme_orchestrateur_extern": "AWS Step Functions is supported as an external orchestrator: it triggers and supervises processing without being a target database.", "aws_step_functions_est_pris_en_charge_comme_orchestrateur_extern_2": "AWS Step Functions is supported as an external orchestrator. It is not a target database: it triggers and supervises processing.", "aws_step_functions_est_pris_en_charge_comme_orchestrateur_extern_3": "AWS Step Functions is supported as an external orchestrator. It is not a target database.", "aws_step_functions_est_un_orchestrateur_externe_il_pilote_deja_d": "AWS Step Functions is an external orchestrator: it already drives extractions, function calls or notifications. beVault has its own orchestration for the platform's data loads, and works alongside what exists rather than replacing it.", "aws_step_functions_et_bevault": "AWS Step Functions and beVault", "aws_step_functions_orchestre_les_chargements_a_partir_du_graphe_": "AWS Step Functions orchestrates loads based on the dependency graph. No external orchestrator to maintain.", "aws_step_functions_docker": "AWS Step Functions, Docker", "badge_data_vault_alliance_vendor_tool_certification": "Data Vault Alliance Vendor Tool Certification badge", "banques_assureurs_et_administrations_ne_peuvent_pas_confier_leur": "Banks, insurers and administrations cannot entrust their data to a shared service. beVault deploys wherever your constraints require: on-premises, in the cloud, in PaaS or in hybrid mode — with the same product in all cases.", "banques_gestion_d_actifs_back_office": "Banking, asset management, back office", "bases_de_donnees_cibles": "Target databases", "beaucoup_d_applications_restent_allumees_des_annees_apres_leur_r": "Many applications stay switched on for years after being replaced, because no one dares lose what they contain. The question isn't technical: it's about continuity and proof. As long as the organization can't demonstrate that the history has been carried over and is consistent, it won't switch anything off.", "beaucoup_d_organisations_progresseront_naturellement_a_travers_c": "Many organizations will naturally progress through these stages as their AI maturity grows.", "befast_becollaborative_beefficient": "beFast · beCollaborative · beEfficient", "besoin_d_interaction_gains_justifient_la_complexite": "Interaction is needed, and the gains justify the complexity", "besoins_d_api_ou_d_integration_configures": "Configured API or integration needs", "bevault": "beVault", "bevault_accueil": "beVault — Home", "bevault_l_execution": "beVault — the execution", "bevault_la_confiance": "beVault — trust", "bevault_le_modele": "beVault — the model", "bevault_plateforme_de_donnees_prete_pour_l_ia": "beVault — AI-ready data platform", "bevault_natif": "beVault (native)", "bevault_orchestration_integree": "beVault (integrated orchestration)", "bevault_a_sa_propre_biere": "beVault has its own beer.", "bevault_aide_t_il_a_decoupler_les_usages_analytiques_d_oracle": "Does beVault help decouple analytics uses from Oracle?", "bevault_applique_ces_regles_a_la_generation_et_embarque_nativeme": "beVault enforces these rules at generation time and natively embeds quality checks on volumes, freshness, and version consistency. Silent duplication becomes an alert, not a chance discovery during an audit.", "bevault_applique_la_meme_approche_pilotee_par_le_modele_a_chaque": "beVault applies the same model-driven approach to every data project. Define the business meaning once, connect and historize your sources, verify the data, publish trusted outputs and orchestrate the flow. Each step builds on the same model and metadata, so your teams can deliver new use cases without starting over.", "bevault_applique_les_regles_dv_2_1_en_continu_et_refuse_les_mode": "beVault enforces DV 2.1 rules continuously and rejects non-compliant models. With dbt, compliance depends on the team's discipline and the macros chosen.", "bevault_automatise_votre_fondation_data_vault_modelisation_gener": "beVault automates your Data Vault foundation: modelling, code generation, data quality and orchestration, within an environment you control.", "bevault_avec_snowflake_databricks": "beVault with Snowflake & Databricks", "bevault_cloud": "beVault Cloud", "bevault_conserve_les_deux_valeurs_et_leurs_dates_ainsi_que_les_e": "beVault keeps both values and their dates, along with the successive states of assets and scopes.", "bevault_conserve_les_flux_et_les_referentiels_avec_leurs_dates_c": "beVault retains flows and reference data with their dates, making each period analyzable in its own context.", "bevault_couvre_modelisation_generation_orchestration_qualite_mdm": "beVault covers modeling, generation, orchestration, quality, MDM, and marts in one product. With a generator alone, you have to assemble and maintain the rest of the chain.", "bevault_devient_ainsi_une_partie_de_votre_architecture_de_donnee": "This allows beVault to become part of your broader data architecture rather than another disconnected application.", "bevault_en_production_ia_evenementiel": "beVault in production — AI & Event-driven", "bevault_est_certifie_sur_data_vault_2_1_la_revision_la_plus_rece": "beVault is certified on Data Vault 2.1, the latest revision of the standard, with an independent audit of the actual generated code.", "bevault_est_concu_pour_integrer_des_environnements_de_donnees_he": "beVault is designed to integrate heterogeneous data environments: connection to sources, legacy ERPs and applications, multi-source, mappings, ingestion, historization and connection to target platforms.", "bevault_est_developpe_par_dfakto_qui_livre_aussi_des_projets_dat": "beVault is developed by dFakto, which also delivers data projects in regulated environments. The product evolves based on real-world constraints encountered.", "bevault_est_le_seul_outil_certifie_dans_le_cadre_du_vendor_tool_": "beVault is the only tool certified under the Data Vault Alliance Vendor Tool Certification Program (VTCP). The certification is an independent review of how the tool applies the Data Vault standard in the structures and loading code it generates.", "bevault_est_ne_d_une_conviction_simple_les_projets_data_vault_so": "beVault was born from a simple conviction: Data Vault projects are too long, too costly and too dependent on scarce experts. We built the tool we wished we had on our own projects.", "bevault_est_un_produit_dfakto_une_equipe_de_data_engineers_basee": "beVault is a dFakto product — a team of data engineers based in Brussels, specialized in Data Vault for over a decade.", "bevault_est_une_plateforme_de_donnees_pas_un_produit_de_conformi": "beVault is a data platform, not a regulatory compliance product. It does not issue any certification and does not guarantee the compliance of a report: it makes your data production traceable and documented, which you still need to present in an audit.", "bevault_est_volontairement_resserre_trois_composants_des_respons": "beVault is deliberately kept lean: three components, separated responsibilities, and an explicit boundary with your application landscape. Everything else — your sources, your infrastructure, your target databases and your reporting tools — remains your domain.", "bevault_est_il_adapte_aux_pme": "Is beVault suitable for SMEs?", "bevault_et_dbt_peuvent_ils_cohabiter": "Can beVault and dbt coexist?", "bevault_evolue_vite": "beVault evolves quickly.", "bevault_face_aux_approches_les_plus_souvent_evaluees": "beVault against the approaches most commonly evaluated", "bevault_fonctionne_sur_la_base_d_une_proposition_adaptee_les_con": "beVault uses a quote-based model. The final conditions are defined according to the organisation's size, project scope, deployment environment, number of domains and level of services required.", "bevault_fonctionne_t_il_avec_des_extensions_postgresql": "Does beVault work with PostgreSQL extensions?", "bevault_fonctionne_t_il_avec_ssis_ou_azure_data_factory": "Does beVault work with SSIS or Azure Data Factory?", "bevault_genere_du_code_natif": "beVault generates native code.", "bevault_helps_organisations_structure_control_and_evolve_their_d": "beVault helps organisations structure, control and evolve their data while keeping control of their environment.", "bevault_historise_chaque_chargement_conserve_la_donnee_source_te": "beVault tracks every load, keeps the source data exactly as it arrived, and preserves the link between that source and the published indicator.", "bevault_learn": "beVault Learn", "bevault_n_a_pas_besoin_de_fonctionner_comme_une_plateforme_isole": "beVault does not need to operate as an isolated platform. Use the API to connect it to the tools your organization already uses.", "bevault_n_est_ni_un_modele_d_ia_ni_un_remplacement_de_vos_outils": "beVault is neither an AI model nor a replacement for your AI tools. It is the upstream data layer: it prepares, historizes, documents and exposes governed data that your models, agents and applications consume.", "bevault_n_est_pas_un_outil_de_bi": "beVault is not a BI tool", "bevault_n_est_pas_une_plateforme_mdm_native_ni_une_suite_mdm_com": "beVault is not a native MDM platform, nor a full MDM suite, nor an automatic golden-record engine, nor a replacement for your existing MDM tools. beVault provides a governed, historized foundation for consistency of reference data across systems.", "bevault_n_est_pas_une_solution_juridique_ou_de_conformite_la_pla": "beVault is not a legal or compliance solution. The platform provides technical controls, historization, lineage and audit trails; assessing compliance with a regulatory framework is the responsibility of your organization and its advisors.", "bevault_ne_fournit_pas_de_modele_d_ia_et_ne_produit_pas_automati": "beVault does not provide an AI model and does not automatically produce AI results. It prepares the material your AI use cases need: structured, controlled, historised and documented data.", "bevault_ne_remplace_pas_ces_bases_de_gestion_il_les_lit_conserve": "beVault does not replace these operational databases. It reads them, keeps every state received with its date, and reconciles business keys across branches.", "bevault_ne_remplace_pas_les_applications_metier_en_place_il_cons": "beVault does not replace the business applications already in place. It forms the historized layer that reads them, retains them, and makes them explainable, without requiring you to migrate the existing setup first.", "bevault_ne_remplace_pas_power_bi_tableau_looker_ou_vos_clients_s": "beVault does not replace Power BI, Tableau, Looker or your SQL clients. It feeds these tools with governed datasets, in the supported configurations validated with you.", "bevault_ne_remplace_pas_snowflake_ni_databricks": "beVault does not replace Snowflake or Databricks:", "bevault_ne_remplace_pas_une_equipe_data_il_lui_rend_du_temps_et_": "beVault does not replace a data team: it gives them back time and makes their work transferable.", "bevault_ne_remplace_pas_votre_outil_de_bi_il_fournit_a_cet_outil": "beVault does not replace your BI tool: it supplies that tool with governed, documented data. Your existing reports reconnect progressively, without a disruptive switchover.", "bevault_ne_remplace_pas_votre_stack_il_produit_du_code_natif_pou": "beVault does not replace your stack: it generates native code for the target database you've already chosen, and runs wherever you decide.", "bevault_ne_s_adresse_pas_qu_au_secteur_public": "beVault is not only for the public sector", "bevault_necessite_t_il_une_migration_vers_une_autre_plateforme": "Does beVault require migration to another platform?", "bevault_offre_a_vos_equipes_une_interface_graphique_pour_concevo": "beVault gives your teams a graphical interface for designing, documenting and managing Data Vault environments. But you are not limited to the interface. Use the beVault API to connect the platform to your applications, scripts and workflows. Use the beVault MCP Server to connect beVault to any AI agents.", "bevault_offre_un_socle_gouverne_pour_les_donnees_de_reference_et": "beVault provides a governed foundation for reference data and multi-source consistency: identity matching across systems, shared business keys, historization, traceability to the source, and consistent views of information. This foundation works alongside your existing reference-data processes; it does not automatically replace an MDM tool already in place.", "bevault_on_premises": "beVault On-Premises", "bevault_orchestre_ses_propres_chargements_si_ssis_ou_adf_gerent_": "beVault orchestrates its own loads. If SSIS or ADF handle other flows, the two coexist.", "bevault_ou_datavault_builder": "beVault or Datavault Builder:", "bevault_ou_dbt": "beVault or dbt:", "bevault_ou_vaultspeed": "beVault or VaultSpeed:", "bevault_ou_wherescape": "beVault or WhereScape:", "bevault_part_du_metamodele_data_vault_hubs_links_et_satellites_s": "beVault starts from the Data Vault metamodel: hubs, links and satellites are first-class objects, not a design pattern applied to a general-purpose warehouse tool.", "bevault_permet_de_controler_la_qualite_de_donnees_historisees_pr": "beVault allows you to control the quality of historized data from multiple systems. Anomalies are reported in actionable lists so that data stewards can correct the data in the source systems. The data can then be extracted and tested again as part of a continuous quality improvement process.", "bevault_peut_consommer_vos_referentiels_existants_comme_source_d": "beVault can consume your existing reference data as a source of truth when it's relevant for your organization.", "bevault_peut_etre_installe_on_premises_dans_le_cloud_en_paas_ou_": "beVault can be installed on-premises, in the cloud, in PaaS or in hybrid mode. It's the same product in all cases: what changes is the location of the components and who operates the infrastructure.", "bevault_regroupe_ces_sources_dans_une_base_historisee_reconcilie": "beVault brings these sources together into a historized database, reconciles product and point-of-sale reference data by business keys, and then feeds the operational dashboards.", "bevault_remplace_t_il_dbt": "Does beVault replace dbt?", "bevault_remplace_t_il_les_notebooks_databricks": "Does beVault replace Databricks notebooks?", "bevault_reunit_la_construction_du_modele_l_integration_des_sourc": "beVault brings together model design, source integration, quality control, data distribution and workflow orchestration — in your environment, under your rules.", "bevault_s_adapte_a_la_facon_dont_vos_equipes_travaillent": "beVault adapts to the way your teams work.", "bevault_s_appuie_sur_aws_step_functions_en_serverless_pas_de_clu": "beVault runs on AWS Step Functions in serverless mode: no Airflow cluster to operate, update or monitor. The dependency graph is derived from the model.", "bevault_s_appuie_sur_le_data_vault_comme_fondation_puis_automati": "beVault builds on the Data Vault as its foundation, then automates what costs the most: producing and maintaining loading code, controlling quality, orchestrating workflows and publishing ready-to-use data — in the environment you have chosen.", "bevault_s_installe_dans_votre_perimetre_y_compris_entierement_on": "beVault is installed within your perimeter, including fully on-premises, which remains decisive for public-sector and regulated organizations.", "bevault_s_installe_dans_votre_propre_environnement_cloud_les_tra": "beVault installs in your own cloud environment. Processes execute within the perimeter you define, and your security team maintains control over access.", "bevault_s_integre_t_il_avec_dataform_ou_dbt_sur_gcp": "Does beVault integrate with Dataform or dbt on GCP?", "bevault_s_y_insere": "beVault fits right in.", "bevault_se_connecte_a_ces_systemes_tels_qu_ils_sont_y_compris_au": "beVault connects to these systems as they are, including legacy environments, without requiring prior migration, and makes the mappings explicit and durable.", "bevault_se_deploie_dans_l_environnement_que_vous_avez_retenu_ave": "beVault deploys in the environment you have chosen, with your access rules and operational constraints. You decide where the data lives and who operates the infrastructure — including in regulated and sovereign contexts.", "bevault_se_deploie_la_ou_votre_organisation_peut_l_exploiter_on_": "beVault is deployed where your organisation can exploit it: on-premises, in your cloud, in PaaS or in hybrid mode. You maintain control of the infrastructure and access, and deployment relies on Docker.", "bevault_se_deploie_le_plus_souvent_avec_un_partenaire_cabinet_de": "beVault is most often deployed with a partner: a consulting firm, integrator or specialized vendor. The product handles the industrial side — modeling, generation, orchestration, quality — while your consultants focus on business value.", "bevault_structure_et_documente_les_donnees_qui_alimentent_vos_et": "beVault structures and documents the data that feeds your reports; it does not automatically guarantee their regulatory compliance, which remains your organization's responsibility.", "bevault_transforme_le_data_vault_en_un_modele_visuel_et_partage_": "beVault turns Data Vault into a shared, visual model of your business. It generates the structures, loading processes, documentation and lineage from that model. It is the only tool certified by the Data Vault Alliance.", "bevault_vs_datavault_builder": "beVault vs Datavault Builder", "bevault_vs_dbt": "beVault vs dbt", "bevault_vs_vaultspeed": "beVault vs VaultSpeed", "bevault_vs_wherescape": "beVault vs WhereScape", "bevault_powered_by_dfakto": "beVault, powered by dFakto", "bi_reporting": "BI & Reporting", "bi_reporting_2": "BI & Reporting", "bigquery_est_serverless_rapide_et_scalable_mais_sans_discipline_": "BigQuery is serverless, fast, and scalable. But without modeling discipline, the platform fills with work tables, stacked views, and costly queries, driving up Google Cloud bills without improving data reliability. beVault generates native BigQuery SQL that leverages the platform's native mechanisms — partitioning, clustering, incremental ingestion.", "bigquery_et_bevault": "BigQuery and beVault", "bigquery_sans_modele": "BigQuery without a model,", "blog": "Blog", "bnp_paribas": "BNP Paribas", "bonne_maitrise_sql_macros_jinja_et_ingenierie_logicielle": "Strong command of SQL, Jinja macros and software engineering", "bonnes_pratiques": "Best practices", "book_a_demo": "book a demo", "brancher_un_modele_sur_une_base_de_donnees_ne_suffit_pas_ce_qui_": "Connecting a model to a database isn't enough. What's almost always missing is what surrounds the data: its history, its business meaning, its metadata, its quality controls and its traceability. Without that, every new initiative starts over from raw, fragmented data.", "brassee_a_bruxelles_par_des_artisans_passionnes": "Brewed in Brussels by passionate artisans.", "bronze_silver_gold_flou": "Bronze/Silver/Gold flow", "bruxelles": "Brussels", "build_the_data_foundation": "Build the data foundation", "business_cases": "Business cases", "c_est_ce_qui_rend_la_modernisation_difficile_refaire_a_cote_sans": "This is what makes modernization difficult. Rebuilding alongside without linking to the existing system produces a second warehouse to reconcile. Redoing everything at once ties up teams for months, with no visible output. The sustainable path is the third one: build a new foundation that coexists with the old, and move usage over domain by domain.", "c_est_ce_qui_rend_le_modele_auditable_par_construction_chaque_en": "This is what makes the model auditable by design: every record carries its source and its load timestamp, history is never overwritten, and reconstructing a past state is a query, not a project.", "c_est_du_compute_perdu": "that's wasted compute.", "c_est_frequent_et_c_est_utile_l_ecart_est_analyse_jusqu_a_sa_cau": "That's common, and it's useful: the discrepancy is traced to its cause. It often reveals an undocumented implicit rule or an old error that had gone unnoticed.", "c_est_la_que_l_automatisation_prend_tout_son_sens_bevault_genere": "This is where automation makes all the difference: beVault generates the structures and loads from the model, applies the same controls everywhere, and eliminates drift between pipelines written by different developers.", "c_est_la_que_sont_decrits_les_workflows_d_extraction_et_d_export": "This is where extraction and export workflows are described: which data is retrieved, in what order, under what conditions, and to which destinations.", "c_est_meme_la_trajectoire_que_nous_recommandons_un_domaine_prior": "This is the very trajectory we recommend. A priority domain allows for the setup of the model, controls and initial marts before expanding.", "c_est_plus_qu_une_opportunite_manquee_c_est_un_gap_architectural": "This is more than a missed opportunity: it's an architectural gap. AI outputs are data. Like any enterprise data, they need durable storage, lineage, versioning and governance.", "c_est_precisement_la_part_que_bevault_automatise_a_partir_du_mod": "This is precisely the part that beVault automates: from the model, the platform generates the structures, loads, quality controls and orchestration. Teams keep the modeling decisions and give up manual code production.", "cadrage": "Scoping", "cadrage_commun": "Joint scoping", "cadrage_des_objectifs_et_du_perimetre": "Scoping of objectives and scope", "cadrage_et_architecture_cible": "Scoping and target architecture", "cadrage_technique": "Technical scoping", "cadrage_etat_des_lieux_architecture_cible": "Scoping, current-state review, target architecture", "cadrer_le_deploiement": "Scope the deployment", "cadrer_mon_projet": "Frame my project", "cadrer_mon_projet_aws": "Scope my AWS project", "cadrer_mon_projet_bigquery": "Frame my BigQuery project", "cadrer_mon_projet_databricks": "Frame my Databricks project", "cadrer_mon_projet_db2": "Frame my DB2 project", "cadrer_mon_projet_oracle": "Frame my Oracle project", "cadrer_mon_projet_postgresql": "Frame my PostgreSQL project", "cadrer_mon_projet_redshift": "Frame my Redshift project", "cadrer_mon_projet_snowflake": "Frame my Snowflake project", "cadrer_mon_projet_sql_server": "Frame my SQL Server project", "cadrer_votre_fondation_ia": "Frame your AI foundation", "caisse_et_e_commerce_alimentent_la_meme_base_chacun_a_son_rythme": "POS and e-commerce feed the same database, each at its own pace, through incremental loads.", "caisse_e_commerce_approvisionnement_fidelite_rh_chaque_systeme_p": "POS, e-commerce, supply chain, loyalty, HR: each system produces its own figures, with its own definition of product, store and business day.", "calc_49_65_25px": "", "calcul": "Calculation", "calculs_executes_chaque_nuit": "calculations executed nightly", "candidater": "Apply", "candidature": "Application", "candidature_et_qualification": "Application and qualification", "capacites_bevault_pertinentes_dans_ce_contexte": "Relevant beVault capabilities in this context", "cartographie_des_sources_critiques": "Critical source mapping", "cartographie_des_sources_des_rapports_et_de_leurs_consommateurs_": "Mapping of sources, reports, and their consumers. We select a high-value domain.", "cartographie_et_priorisation": "Mapping and prioritization", "cartographier_et_prioriser": "Map and prioritize", "cartographier_les_sources_et_les_besoins_modeliser_le_sens_metie": "Map the sources and needs, model business meaning in metaVault, generate the structures and load data in a historised way.", "cas_clients": "Customer cases", "cas_d_usage": "Use Cases", "cas_d_usage_amazon_redshift": "Use case — Amazon Redshift", "cas_d_usage_bi_reporting": "Use case — BI & Reporting", "cas_d_usage_databricks_arrive_bientot": "Use case — Databricks (coming soon)", "cas_d_usage_fondation_ia": "Use case — AI Foundation", "cas_d_usage_google_bigquery_arrive_bientot": "Use case — Google BigQuery (coming soon)", "cas_d_usage_ibm_db2": "Use case — IBM DB2", "cas_d_usage_mdm_integration": "Use case — MDM & Integration", "cas_d_usage_microsoft_sql_server": "Use case — Microsoft SQL Server", "cas_d_usage_migration_erp_legacy": "Use case — ERP & Legacy Migration", "cas_d_usage_modernisation": "Use case — Modernisation", "cas_d_usage_oracle": "Use case — Oracle", "cas_d_usage_plateformes": "Use case — Platforms", "cas_d_usage_postgresql": "Use case — PostgreSQL", "cas_d_usage_qualite_gouvernance": "Use case — Quality & Governance", "cas_d_usage_snowflake": "Use case — Snowflake", "cas_d_usage_agent_de_creation_d_information_marts": "Use case: Information Mart creation agent", "cas_d_usage_courants": "Common use cases:", "catalogue_de_la_plateforme_alimente_separement": "Platform catalog, populated separately", "catalogues_de_donnees_et_glossaires_metier": "Data catalogs and business glossaries.", "categorisation_de_documents_par_type_ou_urgence": "Document categorization by type or urgency", "ce_defaut_vient_presque_toujours_d_une_regle_implementee_a_la_ma": "This flaw almost always comes from a rule implemented by hand, differently in each pipeline. When normalization and hash calculation are generated from the model, they're identical everywhere — including on sources added two years later.", "ce_n_est_generalement_pas_un_budget_visible_c_est_du_temps_d_equ": "It is generally not a visible budget: it is team time spent redoing, verifying and defending figures, instead of exploiting them.", "ce_n_est_ni_la_technologie_ni_les_equipes_c_est_la_part_de_trava": "It's neither the technology nor the teams. It's the share of repetitive work that no one budgets for — and that consumes 60 to 80% of the project.", "ce_n_est_pas_le_meme_metier": "it isn't the same job.", "ce_n_est_presque_jamais_un_probleme_d_outil_c_est_un_probleme_de": "It's almost never a tooling problem: it's a problem of position in the chain.", "ce_pattern_connecte_deux_apis_via_une_state_machine_lineaire": "This pattern connects two APIs via a linear state machine:", "ce_qu_aws_step_functions_orchestre_deja": "What AWS Step Functions already orchestrates", "ce_qu_un_cas_d_usage_ia_reclame_vraiment": "What an AI use case really requires", "ce_qu_un_modele_de_donnees_fait_reellement": "What a data model actually does", "ce_que_bevault_apporte": "What beVault provides", "ce_que_bevault_apporte_a_destinaitor": "What beVault brings to Destinaitor", "ce_que_bevault_historise_et_reconcilie": "What beVault historizes and reconciles", "ce_que_bevault_n_est_pas": "What beVault isn't", "ce_que_bevault_orchestre": "What beVault orchestrates", "ce_que_bevault_permet_de_tenir": "What beVault makes possible", "ce_que_bevault_verrouille_pour_vous": "What beVault locks in for you", "ce_que_ca_change": "What changes", "ce_que_ca_change_chez_vous": "what changes for you.", "ce_que_ca_change_en_pratique": "What changes in practice", "ce_que_ca_delivre": "What it delivers", "ce_que_ce_projet_demontre": "What this project demonstrates", "ce_que_cela_change": "What this changes", "ce_que_cela_change_en_exploitation": "What this changes in operations", "ce_que_cela_coute": "What it costs", "ce_que_cela_signifie_pour_nos_clients": "What this means for our customers", "ce_que_cette_page_ne_dit_pas": "What this page does not say", "ce_que_chacun_apporte": "What each brings", "ce_que_change_l_automatisation": "What automation changes", "ce_que_constatent_les_equipes_qui_migrent": "What migrating teams observe", "ce_que_couvre_l_integration": "What the integration covers", "ce_que_demandent_les_equipes_de_production": "What production teams ask for", "ce_que_fait_bevault": "What beVault does", "ce_que_fait_bevault_en_une_page": "What beVault does, on one page", "ce_que_l_historisation_permet": "What historization enables", "ce_que_la_certification_couvre_et_ce_qu_elle_ne_couvre_pas": "What certification covers — and what it doesn't", "ce_que_la_conteneurisation_change_concretement": "What containerization changes in practice", "ce_que_la_mission_couvre": "What the engagement covers", "ce_que_la_plateforme_apporte_a_ses_utilisateurs": "What the platform brings to its users", "ce_que_la_stack_externalisee_ajoute_reellement": "What an Outsourced Stack Truly Adds", "ce_que_le_data_vault_2_0_change": "What Data Vault 2.0 Changes", "ce_que_le_partenariat_apporte": "What Partnership Brings", "ce_que_le_programme_couvre": "What the program covers", "ce_que_les_environnements_oracle_accumulent": "What Oracle Environments Accumulate", "ce_que_les_equipes_demandent": "What teams ask", "ce_que_les_equipes_nous_demandent": "What Teams Ask Us For", "ce_que_les_partenaires_demandent": "What partners ask", "ce_que_les_pme_nous_demandent_le_plus_souvent": "What SMEs ask us most often", "ce_que_mesurent_nos_clients": "What Our Clients Measure", "ce_que_nos_clients_constatent": "What Our Clients Observe", "ce_que_nos_clients_ont_mesure": "What Our Clients Have Measured", "ce_que_nous_construisons": "What we build", "ce_que_votre_rssi_verifiera": "What Your CISO Will Verify", "ce_que_vous_evitez_grace_a_un_outil_certifie": "What You Avoid with a Certified Tool", "ce_que_vous_n_achetez_pas_separement_vous_n_avez_pas_a_l_integre": "What you don't buy separately, you don't have to integrate or maintain.", "ce_que_vous_obtenez": "What you get", "ce_que_vous_pilotez_au_quotidien": "What you manage day to day", "ce_qui_a_change": "What Has Changed", "ce_qui_a_ete_mesure": "What Was Measured", "ce_qui_a_ete_sous_estime_c_est_l_invisible_le_code_de_chargement": "What was underestimated is the invisible part: loading code, controls, historical backfill, rejection handling, documentation, rework after source changes. This part doesn't show up in a functional spec, but it accounts for most of the real effort.", "ce_qui_change": "What changes", "ce_qui_change_d_une_plateforme_a_l_autre_c_est_le_nombre_d_outil": "What changes from one platform to another is the number of tools you need to assemble to cover this journey — and the integration work that this assembly then imposes, year after year.", "ce_qui_compose_bevault": "What beVault is made of,", "ce_qui_devient_difficile_sans_historique": "What becomes difficult without history", "ce_qui_differencie_vraiment_les_deux": "what really sets the two apart.", "ce_qui_doit_etre_traite_en_premier_ce_qui_peut_attendre_et_ce_qu": "What must be addressed first, what can wait, and what isn't relevant at this stage — with a reasoned recommendation, including when the right decision is to change nothing.", "ce_qui_est_connecte_et_historise": "What is connected and historized", "ce_qui_est_en_jeu": "What's at stake", "ce_qui_est_reconcilie_et_historise": "What is reconciled and historized", "ce_qui_est_verifie": "What Is Verified", "ce_qui_prenait_une_heure_manuellement_est_fait_en_deux_minutes": "What took an hour manually is done in two minutes.", "ce_qui_rend_un_systeme_agent": "What Makes a System 'Agent-Based'", "ce_qui_reste_a_votre_charge_avec_un_simple_generateur": "What Remains Your Responsibility with a Simple Generator", "ce_qui_reste_chez_vous": "What stays with you", "ce_qui_se_passe_entre_une_source_et_un_chiffre": "What happens between a source and a figure", "ce_qui_se_perd_quand_l_historique_est_ecrase": "What's lost when history gets overwritten", "ce_qui_se_voit_en_production_pas_en_demonstration": "What You See in Production, Not in Demos", "ce_ralentissement_n_est_presque_jamais_un_probleme_d_outil_ou_de": "This slowdown is almost never a tooling or skills problem. It is the direct consequence of the lack of a model: every new integration has to work around implicit choices made six months earlier, which no one documented and no one dares to break.", "ce_sujet_parait_technique_mais_c_est_souvent_lui_qui_debloque_ou": "This topic looks technical, but it's often the one that unlocks — or blocks — IT department sign-off.", "cela_change_t_il_la_base_de_donnees_cible": "Does this change the target database?", "cela_depend_il_de_la_base_cible_utilisee": "Does it depend on the target database used?", "certaines_organisations_avancent_seules_apres_une_phase_de_cadra": "Some organisations progress alone after a scoping phase, others prefer continuous support. dFakto services are optional and scale to actual needs.", "certaines_taches_sont_parfaites_pour_l_automatisation_ia_fastidi": "Some tasks are perfect for AI automation: tedious to do manually, based on pattern recognition rather than business judgment, and producing structured outputs.", "certification": "Certification", "certification_data_vault_2_1": "Data Vault 2.1 Certification", "certification_data_vault_2_1_en_vigueur": "Active Data Vault 2.1 Certification", "certification_dv_2_1": "DV 2.1 Certification", "certification_dv_2_1_delivree_apres_audit_du_code_genere": "DV 2.1 Certification Issued After Generated Code Audit", "certification_iso_iec_27001_2022_de_dfakto_consulter_les_informa": "dFakto ISO/IEC 27001:2022 certification — view official information", "certifie_par_la_data_vault_alliance": "Certified by the Data Vault Alliance", "ces_cas_decrivent_des_contextes_differents_avec_un_point_commun_": "These cases describe different contexts, with one thing in common: a foundation built step by step rather than in a single project. They are not presented as SME references.", "ces_conditions_peuvent_concerner_la_plateforme_les_services_d_ac": "These conditions may cover the platform, the support services and the way you get started. They are discussed case by case, based on your actual context.", "ces_criteres_sont_presentes_a_titre_informatif_ils_ne_conditionn": "These criteria are provided for information only. They do not condition the use of beVault and constitute neither legal nor tax advice.", "ces_limitations_pointent_vers_une_approche_plus_sophistiquee_les": "These limitations point to a more sophisticated approach: MCP servers.", "ces_metadonnees_sont_precieuses_pour_la_gouvernance_la_visualisa": "This metadata is valuable for governance, lineage visualization, self-service analytics, and team collaboration.", "ces_pages_ne_figurent_pas_dans_la_navigation_principale_elles_s_": "These pages don't appear in the main navigation: they are intended for teams already engaged in a comparison.", "ces_resultats_sont_reels_voyez_si_le_votre_est_reproductible": "These results are real. See if yours is reproducible.", "ces_taches_partagent_un_pattern_commun_envoyer_une_entree_a_un_m": "These tasks share a common pattern: send an input to an AI model, receive a structured output, use the result. No complex decision-making. No iterative refinement. Just simple orchestration.", "ces_trois_cas_ne_sont_pas_des_strategies_separees_ils_se_renforc": "These three cases aren't separate strategies. They reinforce each other: AI accelerates construction, outputs enrich the data, and the foundation guarantees reliability.", "ces_vues_se_consomment_avec_vos_outils_habituels_power_bi_tablea": "These views are consumed with your usual tools — Power BI, Tableau, Looker or any SQL client — and by your applications via the API. The MCP Server also lets agents interact with the platform.", "cette_approche_excelle_quand_les_taches_sont_bien_definies_et_le": "This approach excels when tasks are well-defined and scripts are stable. It shows its limits for interactive refinement based on business context, or for highly ambiguous column names without domain knowledge.", "cette_approche_modulaire_simplifie_la_gestion_et_favorise_la_reu": "This modular approach simplifies management and promotes reusability, saving time and resources in the long run.", "cette_biere_n_existe_nulle_part_ailleurs_la_recette_a_ete_develo": "This beer exists nowhere else. The recipe was developed in close collaboration between beVault teams and Witloof brewers — a unique blend, brewed in limited edition.", "cette_etape_a_ete_franchie_en_etroite_collaboration_avec_probo_d": "This milestone was achieved in close partnership with Probo, whose platform and team guided us through the ISO 27001 journey and helped make the process significantly smoother from start to finish.", "cette_logique_deverrouille_quatre_capacites_que_la_plupart_des_d": "This logic unlocks four capabilities that most AI deployments ignore:", "cette_page_decrit_l_architecture_technique_de_la_plateforme_les_": "This page describes the platform's technical architecture: the beVault components and their role, the people who use them, and the boundary with what belongs to you — data sources, infrastructure, target databases, outputs and deployment context.", "cette_page_n_existe_pas_ou_a_ete_deplacee_utilisez_le_menu_ci_de": "This page does not exist or has been moved. Use the menu above to continue exploring beVault.", "cette_reussite_reflete_le_travail_mene_pour_integrer_la_securite": "This achievement reflects the work we've done to build security into how we operate. First, across our people, processes, and technology. And continuously, to manage information security risks in a structured and transparent way.", "ceux_qui_font_bevault": "The People Behind beVault", "chacune_de_ces_sources_arrive_avec_sa_frequence_sa_qualite_et_so": "Each of these sources comes with its own frequency, quality and level of documentation. The challenge isn't connecting one: it's integrating them all into a common model, and keeping that setup understandable two years later.", "chaque_attribut_de_la_vue_consolidee_reste_rattache_au_systeme_d": "Each attribute of the consolidated view remains linked to the system it comes from, making it possible to justify a value rather than defend it.", "chaque_chiffre_doit_rester_explicable": "Every figure must remain explainable", "chaque_colonne_d_une_table_source_est_rattachee_explicitement_au": "Each column of a source table is explicitly linked to the model's objects: the mapping stays readable and documented.", "chaque_controle_porte_une_description_un_niveau_un_type_une_crit": "Each control carries a description, a level, a type, a severity and the expected action in case of a discrepancy.", "chaque_domaine_de_donnees_a_un_responsable_identifie_destinatair": "Each data domain has an identified owner, who is the recipient of the exceptions concerning it. Without a name, no rule gets handled.", "chaque_enregistrement_est_historise_avec_sa_date_de_chargement_e": "Every record is historized with its load date and quality score. The state of the data at any past date can be reconstructed.", "chaque_enregistrement_garde_sa_source_et_son_horodatage_de_charg": "Every record retains its source and its load timestamp. Raw data is not transformed before being stored.", "chaque_equipe_a_construit_sa_logique_de_calcul_dans_son_propre_t": "Each team built its own calculation logic in its own dashboard. None of them is wrong on its own; it's just that no one can say which one is authoritative, or why the results differ.", "chaque_equipe_ajoute_son_schema_de_travail_deux_ans_plus_tard_pe": "Each team adds its work schema. Two years later, no one knows which view is authoritative or which tables can be deleted.", "chaque_equipe_construit_sa_propre_agregation_les_chiffres_diverg": "Each team builds its own aggregation. Figures diverge between notebooks, and reconciliations take days.", "chaque_equipe_cree_ses_propres_tables_de_travail_les_couts_de_st": "Each team creates its own work tables. Storage and query costs increase with no visibility into what is useful.", "chaque_equipe_cree_son_propre_schema_de_travail_deux_ans_plus_ta": "Each team creates its own work schema. Two years later, no one knows what can be deleted.", "chaque_etape_demande_du_cadrage_des_arbitrages_metier_et_du_temp": "Each stage requires scoping, business trade-offs and team time. beVault reduces repetitive work, it does not eliminate design work.", "chaque_execution_reste_observable_ce_qui_a_tourne_ce_qui_a_echou": "Every run remains observable: what ran, what failed, and what needs to be relaunched.", "chaque_fiche_destination_est_stockee_avec_son_historique_complet": "Every destination record is stored with its full history. Every change is visible — who made it, when, and from which source.", "chaque_hub_link_et_satellite_devient_un_modele_a_ecrire_dans_dbt": "Every hub, link and satellite becomes a model to write in dbt. beVault generates them from the metamodel: the code follows the model, not the other way around.", "chaque_indicateur_de_delai_de_stock_ou_de_performance_reste_ratt": "Every lead-time, inventory or performance metric stays linked to the data that produced it.", "chaque_initiative_ia_recommence_a_zero": "Every AI initiative starts from scratch", "chaque_maillon_a_son_propre_referentiel_articles": "Each link in the chain has its own product reference system", "chaque_modification_se_valide_en_production_les_regressions_se_d": "Each modification is validated in production. Regressions are discovered in reports, not before.", "chaque_module_de_bevault_peut_etre_presente_separement_mais_ils_": "Each beVault module can be presented on its own, but they share the same metamodel, the same security and the same lineage. That's what avoids gluing together a modeler, a generator, an orchestrator and a quality tool bought separately.", "chaque_organisation_part_d_un_perimetre_d_un_environnement_et_d_": "Every organisation starts from a different scope, environment and level of support. Choose a starting point and discuss the conditions that fit your project.", "chaque_page_compare_des_perimetres_pas_des_slogans": "Each page compares scopes, not slogans", "chaque_page_decrit_les_enjeux_data_du_secteur_les_cas_d_usage_le": "Each page describes the sector's data challenges, the most common use cases and, where a reference has been validated, the corresponding case study.", "chaque_page_detaille_le_contexte_de_depart_la_demarche_que_nous_": "Each page details the initial context, our recommended approach, and observed results.", "chaque_plateforme_a_ses_mecanismes_de_performance_propres_bevaul": "Each platform has its own performance mechanisms. beVault knows them and generates code that exploits them — distribution keys for Redshift, micro-partitions for Snowflake, native SQL for SQL Server or PostgreSQL. The result is readable, commented and exportable code. You are not dependent on a black box.", "chaque_source_suit_la_meme_trajectoire_c_est_cette_repetabilite_": "Every source follows the same path. This repeatability is what makes integration scalable instead of a project every time.", "chaque_systeme_a_raison_dans_son_perimetre_le_probleme_apparait_": "Each system is right within its own scope. The problem appears when you want to count, compare or consolidate: identities don't match up, and manual reconciliation starts over every time.", "chaque_version_du_modele_est_enregistree_avec_son_auteur_sa_date": "Every version of the model is recorded with its author, date and scope. You compare two versions before deciding.", "chargement_incremental": "Incremental loading", "chargement_incremental_avec_detection_des_changements_fini_les_r": "Incremental loading with change detection. No more full reloads wasting slots.", "chargement_incremental_avec_detection_des_changements_fini_les_r_2": "Incremental loading with change detection. No more full reloads wasting compute.", "chargements_data_vault_sur_redshift": "Data Vault loads on Redshift", "chargements_incrementaux_pas_de_rechargement_complet": "Incremental loads, no full reloads", "chargements_regles_et_evolutions_de_modele_sont_traces_le_lignag": "Loads, rules and model changes are tracked. Lineage and documentation are generated from the model itself, not maintained separately in a spreadsheet.", "chez_vous": "On your side", "chiffrement_en_transit_et_au_repos_separation_stricte_des_enviro": "Encryption in transit and at rest, strict environment separation, vault-managed secrets, and key rotation.", "chiffrement_et_cloisonnement": "Encryption & isolation", "chiffrer_mon_cas": "Encrypt my case", "choisir_l_indicateur_litigieux": "Choose the disputed indicator", "choisir_l_objet_et_ses_sources": "Choose the object and its sources", "choisir_un_premier_sujet": "Choose a first subject", "choisir_une_destination_pour_un_congres_international_suppose_de": "Choosing a destination for an international conference involves crossing dozens of criteria: hotel capacity, air accessibility, seasonality, costs, sustainability, regulatory context. This information exists but is dispersed, heterogeneous, and often outdated.", "choisir_votre_architecture": "Choose your architecture", "choisir_votre_path": "Choose your path", "choisissez_le_format_qui_vous_convient": "Choose the format that suits you", "choix_de_la_langue": "Language selection", "choix_de_la_plateforme_cible_du_mode_de_deploiement_et_du_decoup": "Choice of target platform, deployment mode and domain breakdown, with the roadmap to get there.", "cibles": "Targets", "cinq_etapes_un_domaine_a_la_fois": "Five steps, one domain at a time", "cinq_modules_un_seul_metamodele": "Five modules, one single metamodel,", "circuit_d_exception_avec_responsable_et_suivi": "Exception workflow with an owner and follow-up", "cle_metier": "Business Key", "cles_composites_et_perimetre_de_collision": "Composite keys and collision perimeter", "cles_de_hachage_horodatages_de_chargement_tracabilite_de_la_sour": "Hash keys, load timestamps, source traceability and full historization: the ability to reconstruct the exact state of the data at any past date is verified.", "cles_metier": "Business keys", "cles_metier_dans_le_data_vault_construire_pour_que_ca_dure": "Business keys in the Data Vault: building to last", "cles_metier_relations_et_definitions_partagees_donnent_aux_agent": "Business keys, relationships, and shared definitions provide agents with actionable context: they handle concepts, not cryptic column names.", "client_actif": "active client\\", "client_actif_2": "Active Client\\", "clients": "Clients", "clients_contrats_evenements_les_entites_sont_modelisees_et_docum": "Customers, contracts, events: entities are modeled and documented in metaVault, giving teams and tools alike a stable vocabulary.", "clients_produits_et_intermediaires_reconcilies_entre_branches_pa": "Customers, products and intermediaries reconciled across business lines using Business Keys, without imposing a single reference system upstream of source systems.", "cloisonnement": "Segregation", "cloud_dans_votre_compte": "Cloud, in your account", "co_creee_unique_artisanale": "Co-created. Unique. Crafted.", "co_delivery_des_premiers_projets_avec_nos_architectes": "Co-delivery of the first projects with our architects", "co_delivery_sur_les_premiers_projets": "Co-delivery on the first projects", "code_de_chargement_genere_et_optimise_pour_snowflake": "Loading code generated and optimized for Snowflake", "code_exportable_et_versionnable_dans_git": "Exportable and versionable code in Git", "code_lisible_commente_exportable_vous_gardez_la_main": "Readable, commented, exportable code — you retain control", "code_natif_optimise_pour_chaque_moteur": "Native code optimized for each engine", "code_natif_optimise_pour_chaque_plateforme_cible": "Native code optimized for each target platform", "codes_libelles_et_hierarchies_changent_les_correspondances_sont_": "Codes, labels and hierarchies change: mappings are preserved, so analyses stay comparable over time.", "c_ur_bancaire_outils_de_marche_fichiers_de_contreparties_applica": "Core banking, trading tools, counterparty files, management applications: each system holds part of the final figure, with its own identifiers and its own schedule.", "c_ur_du_produit": "Core of the product", "coherence_modele_execution": "Model ↔ Execution consistency", "combien_d_environnements_peut_on_gerer": "How many environments can be managed?", "combien_d_equipements_etaient_reellement_en_service_ce_trimestre": "How many assets were actually in service that quarter?", "combien_de_domaines_en_parallele": "How many domains in parallel?", "combien_de_temps_pour_un_premier_resultat": "How long until the first results?", "commandes_receptions_et_conditions_historisees_avec_leurs_dates_": "Orders, receipts and terms historized with their successive effective dates.", "commandez_nos_bieres": "Order our beers", "commencer_avec_un_perimetre_clair_puis_avancer_par_etapes": "Start with a clear scope, then progress in stages", "commencer_gratuitement": "Start for free", "commencer_par_l_indicateur_qui_pose_probleme": "Start with the metric that causes trouble", "commencez_avec_bevault": "Start with beVault", "commencez_avec_un_perimetre_cible_et_decouvrez_comment_bevault_p": "Start with a focused scope and explore how beVault could fit your data journey.", "commencez_avec_une_fondation_de_donnees_ciblee_sur_un_premier_do": "Start with a focused data foundation for a first domain or use case.", "comment_bevault_resout_les_trois": "How beVault solves the three", "comment_ca_fonctionne": "How it works", "comment_ces_informations_sont_publiees": "How this information is published", "comment_connecter_odoo_a_un_data_vault_et_produire_des_dashboard": "How to connect Odoo to a Data Vault and produce native dashboards without an intermediate layer. By Loïc Gamain and Julien Masson.", "comment_demontrer_la_conformite_lors_d_un_audit": "How do you demonstrate compliance during an audit?", "comment_demontrer_que_la_reprise_est_coherente": "How do you demonstrate that the migration is consistent?", "comment_est_decidee_la_frontiere_entre_les_deux": "How is the boundary between the two decided?", "comment_gerer_des_regles_metier_contradictoires_entre_services": "How do you handle conflicting business rules between departments?", "comment_gerer_la_coexistence_avec_les_rapports_existants": "How to manage coexistence with existing reports?", "comment_gerer_une_suppression_ciblee_avec_un_entrepot_historise": "How do you handle a targeted deletion with a historized warehouse?", "comment_l_articulation_se_met_en_place": "How the articulation comes together", "comment_l_intelligence_artificielle_et_le_data_vault_se_renforce": "How Artificial Intelligence and Data Vault mutually reinforce each other — from strategic foundation to AI agents in production. A complete series for data teams.", "comment_le_detecter_en_dix_minutes": "How to detect it in ten minutes", "comment_le_metamodele_data_vault_expose_une_semantique_metier_qu": "How the Data Vault metamodel exposes business semantics that LLMs can use directly through the API or MCP.", "comment_le_modele_guide_les_mappings": "How the model guides the mappings", "comment_le_perimetre_d_integration_est_il_defini": "How is the integration scope defined?", "comment_les_composants_s_articulent_ce_qui_est_genere_ce_qui_res": "How the components fit together, what is generated, what remains custom-developed, and why.", "comment_les_marts_sont_rafraichis": "How the Information Marts are refreshed", "comment_nous_mesurons": "How we measure", "comment_on_demarre": "How we get started", "comment_preparer_des_donnees_pour_l_ia": "How to prepare data for AI?", "comment_preparer_votre_organisation_a_l_ia_des_aujourd_hui": "How to prepare your organisation for AI today", "comment_retracer_un_indicateur_jusqu_a_ses_sources": "How do you trace a metric back to its sources?", "comment_se_comparent_les_couts": "How do costs compare?", "comment_se_construit_le_retour_sur_investissement": "How the return on investment builds up", "comment_se_deroule_la_mission": "How the engagement unfolds", "comment_se_passe_l_echange": "How the conversation unfolds", "comment_se_passent_les_mises_a_jour": "How are updates handled?", "comment_sont_enregistrees_les_opportunites": "How are opportunities recorded?", "comment_verifier_chez_vous_en_une_heure": "How to verify at your place in one hour", "comment_verifier_qu_un_outil_est_certifie": "How do you check that a tool is certified?", "communaute_editeurs_multiples": "Community + multiple publishers", "comparaison": "Comparison", "comparatif": "Comparative", "comparatifs_disponibles": "Available comparisons", "comparer_avec_un_architecte": "Compare with an architect", "comparer_dans_le_temps": "Compare over time", "comparer_des_periodes": "Compare periods", "comparer_sans_caricaturer": "Comparing without oversimplifying:", "comparez_a_perimetre_egal_en_incluant_l_integration_et_le_run_c_": "Compare on equal terms, including integration and run — that's where the gap widens.", "comparez_sur_ce_que_vous_devrez_exploiter_pendant_cinq_ans_pas_s": "Compare based on what you'll have to operate for the next five years, not just the build phase.", "comparez_sur_vos_propres_donnees": "Compare on your own data", "comparez_sur_votre_propre_grille": "Compare on your own grid", "compatible_avec_aws_step_functions": "Compatible with AWS Step Functions", "compatible_sql_server_on_premise_et_azure_sql_managed_instance": "Compatible with SQL Server on-premise and Azure SQL Managed Instance", "competence_requise": "Skills required", "competences_rares": "Rare skills", "completez_par_une_mesure_de_frequence_le_nombre_moyen_de_version": "Complement this with a frequency measure: the average number of versions per key per month. When this value tracks the pipeline's run frequency rather than the actual business rhythm, the diagnosis is confirmed.", "completude_unicite_format_plages_de_valeurs_integrite_referentie": "Completeness, uniqueness, format, value ranges, referential integrity, inter-source consistency, specific business rules: rules are declared once and applied at each load.", "composants": "Components", "comprendre_mcp_model_context_protocol": "Understand MCP (Model Context Protocol)", "comprendre_comparer_et_verifier_avant_de_contacter_l_equipe": "Understand, compare and verify before contacting the team.", "concevez_hubs_links_et_satellites_dans_une_interface_visuelle_le": "Design hubs, links, and satellites in a visual interface. The model becomes the single source of truth: SQL code, loads, and documentation are automatically derived.", "concevoir_le_prompt_parfait_pour_bevault": "Design the perfect prompt for beVault", "concretement_pour_les_equipes_data": "Specifically, for data teams", "concu_pour_passer_a_l_echelle": "Built to scale", "conditions": "Terms", "config_awaited": "config: Awaited", "conformite_des_structures": "Structure compliance", "conformite_et_controle": "Compliance and Control", "conformite_gouvernance_et_master_data": "Compliance, governance and master data", "confrontez_bevault_a_l_outil_que_vous_evaluez": "Compare beVault with the tool you are evaluating", "confrontez_votre_architecture_actuelle_a_un_regard_exterieur": "Put your current architecture to the test with an outside perspective.", "confrontons_cette_architecture_a_la_votre": "Let's compare this architecture with yours.", "connaissance_du_standard": "Knowledge of the standard", "connaissance_metier_et_modelisation": "Business knowledge and modeling", "connecter_bevault_a_votre_ecosysteme_existant": "Connect beVault to your existing ecosystem", "connecter_bevault_aux_agents_ia_avec_mcp": "Connect beVault to AI agents with MCP", "connecter_et_historiser_les_sources": "Connect and track history from sources", "connecter_vos_agents_a_la_plateforme": "Connect your agents to the platform", "connecteurs_synchronisation_maintenance": "Connectors, synchronization, maintenance", "connectez_bevault_a_un_agent_ia_et_permettez_lui_de_consulter_ou": "Connect beVault to an AI agent and allow it to consult or create objects in your data model within the permissions and controls you define.", "connectez_vos_sources_mappez_les_donnees_et_historisez_les_chang": "Connect your sources, map the data and historise changes over time.", "connexion": "Connection", "connexion_aux_agents_ia": "Connecting to AI agents", "connexion_des_sources_mappings_ingestion_et_historisation_domain": "Connecting sources, mappings, ingestion and historization, domain by domain rather than in a single batch.", "conserver_historique_et_lignage": "Preserve history and lineage", "conserver_l_historique_et_le_sens_metier_pendant_un_changement_d": "Preserve history and business meaning during a system change.", "conserver_l_origine": "Preserving the origin", "conserver_la_tracabilite": "Preserve traceability", "conserver_le_contexte_et_l_historique_des_sources": "Preserve source context and history", "conserver_les_etats_successifs_des_actifs": "Preserve the successive states of assets", "consolider_le_socle": "Consolidate the foundation", "consolides_sans_perte_de_donnees": "consolidated without data loss", "construire_avec_vos_equipes": "Build with your teams,", "construire_ensuite": "Build next.", "construire_la_fondation": "Build the foundation", "construire_le_raw_vault_du_domaine": "Build the domain's Raw Vault", "construire_une_fondation_maitrisee": "Build a controlled foundation", "construire_alimenter_controler_distribuer_et_orchestrer_vos_donn": "Build, load, control, distribute and orchestrate your data.", "construisez_des_bases_solides_pour_votre_plateforme_ia": "Build solid foundations for your AI platform.", "construisez_la_fondation": "Build the foundation", "construite_sur_bevault_par_dfakto": "Built on beVault by dFakto.", "consulter_le_certificat_iso_27001_de_dfakto": "View dFakto's ISO 27001 certificate →", "contact": "Contact", "contact_us": "contact us", "contact_us_2": "Contact us", "contact_dfakto_com": "contact@dfakto.com", "contactez_nous": "Contact us", "contactez_nous_2": "Contact us", "contactez_nous_pour_discuter_de_votre_architecture_nous_evaluero": "Contact us to discuss your architecture — we will assess the covered scope.", "contactez_nous_pour_discuter_de_votre_configuration_unity_catalo": "Contact us to discuss your Unity Catalog setup and the integration scope.", "contactez_nous_pour_evaluer_la_compatibilite_avec_vos_extensions": "Contact us to assess compatibility with your specific extensions.", "contactez_nous_pour_verifier_la_compatibilite_avec_votre_version": "Contact us to verify compatibility with your specific version and configuration.", "contactez_nous_pour_verifier_la_compatibilite_avec_votre_version_2": "Contact us to verify compatibility with your specific version.", "contexte_de_deploiement": "Deployment context", "contexte_metier": "Business context", "continuite_operationnelle_non_negociable": "Operational continuity is non-negotiable", "contrainte_frequente": "Common constraint", "contraintes_et_controles_a_implementer": "Constraints and controls to implement", "contraintes_repetees_sur_le_format_de_sortie": "Repeated constraints on output format", "contrairement_a_l_approche_api_directe_qui_necessite_de_configur": "Unlike the direct API approach, which requires configuring each tool individually in every agent platform, the MCP Server provides a dynamic list of tools that agents can discover and use automatically.", "contrats_sinistres_et_reporting": "Contracts, claims and reporting", "controle_de_l_auditabilite_et_de_la_tracabilite_de_source": "Audit and source traceability review", "controle_de_l_infrastructure_on_premises": "On-premises infrastructure control", "controler_et_produire": "Control and deliver", "controler_la_qualite_de_vos_donnees": "Control your data quality", "controler_pendant_pas_apres": "Control during, not after", "controler_mesurer_et_corriger_la_donnee_au_moment_ou_elle_entre_": "Control, measure and correct data as it enters the platform.", "controles_de_qualite_appliques_avant_exposition_pas_apres_signal": "Quality checks applied pre-exposure, not post-reporting.", "controles_et_non_conformites_relies_aux_lots_et_aux_articles_con": "Controls and non-conformities linked to the batches and items concerned, with their timestamps.", "controles_qualite": "Data quality controls", "corriger_dans_la_source": "Fix in the source", "corriger_sans_perdre_l_auditabilite": "Fixing data without losing auditability", "cote_dfakto_cadrage_architecture_implementation_formation_transf": "On the dFakto side: scoping, architecture, implementation, training, skills transfer, support and evolution. These services are optional and sized according to what your teams want to handle in-house.", "cote_plateforme_moins_de_travail_repetitif_des_regles_et_des_met": "On the platform side: less repetitive work, centralised rules and metadata, a more readable model, easier evolution of sources and usable documentation derived from the model.", "couche_de_restitution_documentee_avec_lignage_complet_et_indicat": "Documented restitution layer with full lineage and quality indicators, directly exposed to Looker Studio or any BI tool.", "couche_semantique_commune_a_l_interface_et_aux_agents_ia": "A semantic layer shared by the interface and the AI agents.", "cout_d_execution_non_maitrise": "Uncontrolled runtime cost", "cout_d_integration": "Integration cost", "cout_de_licence_croissant": "Increasing license cost", "couts_caches": "Hidden costs", "creation_dynamique_de_workflows": "Dynamic workflow creation", "creer_des_produits_de_donnees_documentes": "Create documented data products", "creer_et_mettre_a_jour_des_entites_dans_bevault": "Create and update entities in beVault.", "creer_les_entites_necessaires_dans_bevault": "Create the required entities in beVault.", "creer_ou_mettre_a_jour_des_objets_dans_bevault": "Create or update objects in beVault.", "critere_de_decision": "Decision criterion", "criteres_de_decision": "Decision criteria", "cycle_de_vie": "lifecycle\\", "d_amendes_correctement_emises_grace_a_une_meilleure_donnee": "of fines correctly issued thanks to better data", "d_ou_viennent_ces_metadonnees": "Where this metadata comes from", "d_une_armee_d_ingenieurs": "of an army of engineers.", "dans_bevault_la_definition_des_cles_metier_est_portee_par_le_mod": "In beVault, business key definitions are driven by the model and applied during generation: normalization, hashing, and scope management are consistent across all loads, by design.", "dans_bevault_la_documentation_des_information_marts_est_essentie": "In beVault, documenting Information Marts is essential but time-consuming. You write SQL in the \\", "dans_cinq_systemes_differents": "across five different systems.", "dans_l_energie_une_valeur_n_est_jamais_definitive_elle_est_relev": "In energy, a value is never final: it's read, estimated, then corrected. A useful data foundation keeps these versions instead of overwriting them.", "dans_l_environnement_qui_correspond_a_votre_organisation": "In the environment that fits your organisation", "dans_la_banque_et_l_assurance_il_faut_pouvoir_justifier_un_chiff": "In banking and insurance, you must be able to justify a figure published three years ago. Certified historization makes that request trivial instead of a project.", "dans_la_finance_la_difficulte_n_est_pas_de_produire_un_rapport_c": "In finance, the difficulty isn't producing a report, it's being able to explain how it was produced: from which source, with which rule, on which date.", "dans_la_plateforme": "In the platform", "dans_la_plupart_des_organisations_la_donnee_existe_deja_elle_est": "In most organizations, the data already exists. It's simply spread across systems that don't talk to each other, transformed differently by each team, and rarely kept over time.", "dans_metavault_vos_architectes_decrivent_ce_que_l_organisation_m": "In metaVault, your architects describe what the organization actually works with: business keys, relationships, contexts, definitions. This model isn't a supporting document — it's the single source of truth the platform builds on.", "dans_un_data_vault_l_entite_metier_existe_une_seule_fois_chaque_": "In a Data Vault, the business entity exists only once. Each system attaches its own reference to it without losing its own: reconciliation is additive, it doesn't replace.", "dans_un_deploiement_conteneurise_les_composants_de_bevault_s_exe": "In a containerized deployment, beVault's components run in the environment defined with your teams. Data never leaves that environment.", "dans_un_historique_coherent": "into a consistent history.", "dans_votre_infrastructure": "in your infrastructure.", "data_catalog": "Data Catalog", "data_catalog_metadonnees_origine_des_donnees": "Data Catalog, metadata, data lineage", "data_products_information_marts": "Data products & Information Marts", "data_products_information_marts_2": "Data Products & Information Marts", "data_quality_mdm": "Data Quality & MDM", "data_quality_et_mdm_dans_la_plateforme": "Data Quality and MDM in the platform", "data_quality_integree_au_chargement": "Data Quality integrated during loading", "data_quality_native": "Native Data Quality", "data_quality_native_a_l_execution": "Native data quality at run time", "data_quality_native_appliquee_au_chargement_et_non_a_posteriori": "Native Data Quality, applied during loading, not post-hoc", "data_strategy_architecture": "Data Strategy & Architecture", "data_vault_2_0": "Data Vault 2.0.", "data_vault_2_0_as_the_semantic_layer_for_ai": "Data Vault 2.0 as the semantic layer for AI", "data_vault_automation": "Data Vault Automation", "data_vault_comme_fondation": "Data Vault as the foundation", "data_vault_dans_l_ecosysteme_google_cloud": "Data Vault in the Google Cloud ecosystem", "data_vault_genere_et_orchestre_sur_snowflake": "Data Vault generated and orchestrated on Snowflake", "data_vault_sur_db2_y_compris_mainframe": "Data Vault on Db2, including mainframe", "data_vault_sur_postgresql_souverain": "Data Vault on sovereign PostgreSQL", "data_vault_qualite_des_donnees_ia_et_retours_terrain_par_les_equ": "Data Vault, data quality, AI, and field feedback — by the dFakto teams.", "databricks": "Databricks", "databricks_est_il_deja_supporte": "Is Databricks already supported?", "databricks_et_bevault": "Databricks and beVault", "databricks_excelle_dans_le_traitement_massif_le_machine_learning": "Databricks excels at large-scale processing, machine learning and exploration. But a lakehouse without a reference model produces data no one can rely on. beVault generates Data Vault structures on Delta Lake and exposes historized, traceable, quality-scored data — exactly what your AI models and reports demand.", "databricks_traite_vos_donnees": "Databricks processes your data.", "db2_et_bevault": "DB2 and beVault", "db2_n_est_pas_un_probleme_a_resoudre_c_est_une_source_a_exploite": "Db2 isn't a problem to solve. It's a source to be properly leveraged.", "dbt_a_rendu_les_transformations_sql_versionnables_testables_et_l": "dbt made SQL transformations versionable, testable and readable — that's a real step forward, and many teams use it very well. But dbt doesn't know what a hub, a link or a satellite is: you have to write and maintain those patterns yourself. beVault starts from the Data Vault model itself and derives the code, load order, quality controls and marts from it.", "dbt_execute_un_graphe_de_modeles_le_declenchement_les_reprises_e": "dbt runs a graph of models; triggering, retries, and monitoring still need to be built. beVault orchestrates loading natively.", "de_cinq_jours_a_quelques_heures_par_mois_sans_infrastructure_par": "From five days to a few hours per month. Without parallel infrastructure, without additional licenses.", "de_cinq_jours_a_quelques_heures": "From five days to a few hours.", "de_fiabilite_des_donnees_mesuree_et_certifiee": "data reliability, measured and certified", "de_l_entrepot_a_l_ia_sans_detour": "From the warehouse to AI, without detours", "de_l_installation_a_l_exploitation": "From installation to day-to-day operation", "de_la_connexion_a_la_donnee_historisee": "From connection to historized data", "de_la_fondation_aux_produits_de_donnees": "From foundation to data products", "de_la_modification_au_passage_en_production": "From change to production", "de_la_repetition_manuelle_a_l_automatisation_reutilisable": "From manual repetition to reusable automation", "de_la_source_au_chiffre_publie": "From source to published figure", "de_latence_contre_14_jours": "latency (vs. 14 days)", "de_latence_donnees_contre_14_jours_auparavant": "data latency (vs. 14 days previously)", "de_nombreuses_equipes_data_creent_regulierement_des_objets_et_de": "Many data teams repeatedly create similar objects and structures. With the beVault API, these operations can be automated.", "de_temps_de_production_des_rapports_mensuels": "monthly report production time", "decider_d_abord": "Decide first.", "declarations_reevaluations_et_reglements_historises_avec_le_cont": "Declarations, revaluations, and settlements historized, with the contractual context that applied at the time.", "declarees_dans_le_processus_de_chargement_et_mesurees_en_continu": "Declared in the loading process and measured continuously, rather than discovered after the fact in reports.", "declarer": "Declare", "declarer_le_mart": "Declare the mart", "declarer_les_regles_attendues_et_rendre_les_ecarts_visibles_et_a": "Declare the expected rules and make deviations visible and actionable.", "declarer_les_regles_de_qualite_mesurer_les_ecarts_rendre_les_ano": "Declare quality rules, measure deviations, make anomalies visible and actionable, then produce the first Information Marts.", "declenchement": "Triggering", "declenchements_et_dependances_explicites": "Explicit triggers and dependencies", "declencher_l_etape_suivante_de_votre_workflow_de_livraison": "Trigger the next step in your delivery workflow.", "decommission_progressive": "Progressive decommission", "decommissionner_et_enchainer": "Decommission and chain", "decomposer_le_delai_reel_d_une_demande_metier": "Breaking down the real turnaround time of a business request", "decouplage_progressif": "Progressive decoupling", "decouvrez_l_equipe_en_video_dans_le_cadre_du_programme_welcome_t": "Discover the team on video — as part of the Welcome to the Jungle program.", "decouvrez_la_plateforme_en_action": "See the platform in action", "decouvrir_comment_bevault_alimente_les_produits_ia": "Discover how beVault powers AI products →", "decouvrir_la_brasserie_witloof": "Discover Witloof Brewery", "decouvrir_la_plateforme": "Discover the platform", "decouvrir_le_deploiement_la_souverainete": "Discover Deployment & Sovereignty", "decouvrir_le_programme_partenaires": "Explore the Partner Program", "decouvrir_les_services_data": "Discover our data services", "decrire_le_modele_une_seule_fois": "Describe the model only once", "decrire_ma_situation": "Describe my situation", "decrivez_nous_un_flux_de_terrain_et_un_indicateur_que_vous_devez": "Tell us about a field data flow and a metric you need to justify. We'll start from there.", "decrivez_nous_vos_sources_votre_equipe_et_vos_echeances_nous_vou": "Describe your sources, your team and your deadlines to us. We will tell you honestly where to start — and if beVault is the right tool for you.", "decrivez_nous_votre_cas": "Describe your use case", "decrivez_nous_votre_contexte_en_quelques_lignes_nous_vous_dirons": "Describe your context in a few lines. We'll tell you honestly if beVault is the right tool for you — and if not, why.", "defendable_devant_un_controle": "defensible under scrutiny.", "definir_et_mettre_en_uvre_des_mesures_de_securite_appropriees": "Defining and implementing appropriate security controls.", "definir_l_indicateur": "Defining the indicator", "definissez_le_modele_une_fois_puis_utilisez_le_pour_generer_les_": "Define the model once, then use it to generate database structures, loading processes, documentation and lineage. Your teams focus on business meaning and design decisions instead of maintaining repetitive implementation code.", "definissons_le_bon_point_de_depart_pour_votre_organisation": "Let's define the right starting point for your organisation.", "definition_de_la_limite_entre_les_deux_ce_que_bevault_pilote_de_": "Defining the boundary between the two: what beVault manages end to end, and what remains in your existing chain.", "definition_de_role_claire": "Clear role definition", "definition_du_schema": "Schema definition", "definitions": "Definitions", "definitions_proprietaires_et_structures_sont_decrits_dans_metava": "Definitions, owners and structures are described in metaVault and can be retrieved via the API and the Data Catalog.", "demander_la_mise_en_relation": "Request connection", "demander_mon_acces": "Request access", "demander_notre_dossier_de_certification": "Request our certification file", "demander_un_devis": "Get a quote", "demander_une_demo_comparative": "Request a comparative demo", "demander_une_proposition": "Get a quote", "demander_une_reference": "Request a reference", "demandez_le_certificat_dv_2_1_et_sa_date_pas_la_mention_sur_le_s": "Ask for the DV 2.1 certificate and its date, not just the mention on the site.", "demarche": "Approach", "demarrage_offert": "Free onboarding", "demarrage_plus_rapide_du_projet": "Faster project start", "demarrer": "Get started", "demarrer_l_essai_gratuit": "start the free trial", "demo": "Demo", "demo_le_serveur_mcp_bevault_implemente_un_modele_data_vault_avec": "Demo: the beVault MCP Server implements a Data Vault model with an AI agent", "demo_comparative": "Comparative demo", "demo_decouverte": "Discovery demo", "demo_interactive_a_partir_d_un_projet_bevault_vide_l_agent_propo": "Interactive demo: starting from an empty beVault project, the agent proposes a data model for the user to review and validate before it is executed.", "demonstration_conduite_par_un_praticien_pas_par_un_commercial": "Demonstration led by a practitioner, not a salesperson", "depend_de_la_conception_du_dag": "Depends on DAG design", "dependances_parallelisme_reprises_sur_erreur_et_supervision_exec": "Dependencies, parallelism, error recovery, and supervision executed natively on AWS Step Functions, without operating a cluster.", "deplacer_les_consommateurs_progressivement": "Move consumers over gradually", "deplacer_les_usages_puis_enchainer": "Move usage over, then move ahead", "deploiement": "Deployment", "deploiement_docker": "Deployment — Docker", "deploiement_saas_uniquement_ou_on_premises_possible": "Deployment: SaaS only or on-premises possible?", "deploiement_souverainete": "Deployment & Sovereignty", "deploiement_cloud_vpc_dedie_ou_on_premises": "Cloud, dedicated VPC, or on-premises deployment", "deploiement_conjoint": "Joint deployment", "deploiement_dans_l_environnement_cible_procedures_d_exploitation": "Deployment into the target environment, operating procedures and recovery conditions.", "deploiement_dans_l_environnement_du_client": "Deployment within the customer environment", "deploiement_domaine_par_domaine_sans_arret_de_production": "Domain by domain deployment, without production downtime", "deploiement_et_souverainete": "Deployment and sovereignty", "deploiement_heberge": "Hosted deployment", "deploiement_on_premise_cloud_ou_hybride_selon_votre_choix": "On-premises, cloud, or hybrid deployment as per your choice", "deploiement_on_premises": "On-premises deployment", "deploiement_on_premises_vpc_dedie": "On-premises / dedicated VPC deployment", "deploiement_on_premises_reellement_disponible": "On-premises deployment actually available", "deploiement_on_premises_cloud_ou_hybride": "On-premises, cloud, or hybrid deployment", "deploiement_on_premises_cloud_ou_hybride_selon_vos_contraintes": "On-premises, cloud, or hybrid deployment, based on your constraints", "deploiement_on_premises_cloud_ou_hybride_en_europe": "On-premises, cloud, or hybrid deployment, in Europe", "deploiement_on_premises_cloud_paas_ou_hybride_vos_donnees_resten": "On-premises, cloud, PaaS or hybrid deployment — your data stays in your environment", "deploiement_progressif_les_systemes_de_production_ne_sont_pas_to": "Progressive deployment — production systems are not affected", "deploiement_progressif_domaine_par_domaine_sans_arret_de_product": "Progressive domain by domain deployment, without production downtime", "deploiement_saas_vpc_dedie_ou_on_premises_complet_avec_le_meme_p": "SaaS deployment, dedicated VPC or full on-premises, with the same product. A deal-breaker criterion for many European public-sector and financial organizations.", "deploiements_non_destructifs": "Non-destructive deployments", "deploiements_non_destructifs_l_historique_est_preserve": "Non-destructive deployments: history is preserved", "deployer_bevault_c_est_installer_les_composants_de_la_plateforme": "Deploying beVault means installing the platform components — metaVault, States and Workers — in the environment you have chosen, with Docker as the deployment technology.", "deployer_en_production": "Deploy to production", "deployer_les_structures_generees_c_est_appliquer_dans_votre_base": "Deploying generated structures means applying the objects and code produced by the platform to your target database. The two operations are independent: the beVault installation mode does not determine the location of your target database.", "deposez_votre_candidature_partenaire": "Submit your partner application", "depots_git_et_plateformes_ci_cd": "Git repositories and CI/CD platforms.", "deroule": "Process", "des_besoins_analytiques_et_ia": "Analytics and AI needs", "des_centaines_de_procedures_stockees_ecrites_par_des_equipes_suc": "Hundreds of stored procedures written by successive teams. No one knows what can be touched without risk.", "des_chiffres": "Figures", "des_chiffres_publics": "Public figures", "des_chiffres_que_nos_clients": "Numbers our clients", "des_conditions_adaptees_a_votre_organisation": "Conditions adapted to your organisation", "des_conditions_adaptees_aux_pme": "Conditions adapted to SMEs", "des_controles_de_qualite_appliques_en_amont_avant_exposition_aux": "Quality controls applied upstream, before exposure to agents.", "des_controles_declares_pas_improvises": "Declared controls, not improvised ones", "des_decennies_de_vues_triggers_et_procedures_stockees_dont_perso": "Decades of views, triggers, and stored procedures where no one knows all the dependencies. Each modification is a risk.", "des_definitions_metier_qui_evoluent": "Business definitions that evolve", "des_distributions_inadaptees_et_des_rechargements_complets_font_": "Inadequate distributions and full reloads drive up the AWS bill without warning.", "des_donnees_critiques_une_infrastructure_eprouvee": "Critical data, proven infrastructure", "des_donnees_provenant_de_plusieurs_systemes": "Data coming from multiple systems", "des_donnees_que_le_metier_peut_utiliser": "Data the business can actually use", "des_enjeux_tres_differents": "very different challenges.", "des_environnements_heterogenes_un_meme_chemin": "Heterogeneous environments, a single path", "des_evaluations_de_securite_fournisseurs_et_des_revues_d_achat_f": "Easier vendor security assessments and procurement reviews.", "des_indicateurs_alignes_sur_des_definitions_partagees_et_reconst": "Indicators aligned with shared definitions and reconstructable over time.", "des_insights_ia_aux_actifs_data": "From AI insights to data assets", "des_insights_ia_aux_actifs_data_integrer_les_sorties_ia_dans_vot": "From AI insights to data assets: integrate AI outputs into your Data Vault", "des_marts_construits_sur_des_definitions_partagees_et_reconcilie": "Marts built on shared definitions and reconciled with the sources.", "des_marts_et_une_gouvernance_lisibles": "Readable marts and governance", "des_marts_fiables_pour_vos_tableaux_de_bord": "Reliable marts for your dashboards", "des_obligations_legales_reglementaires_et_contractuelles": "Legal, regulatory, and contractual obligations.", "des_partenaires_conseil_data_et_technologiques_presents_en_belgi": "Consulting, data, and technology partners present in Belgium, France, and beyond.", "des_personnes_et_des_processus_organisationnels": "People and organizational processes.", "des_petits_comme_des_grands_modeles_de_donnees_avec_un_traitemen": "Support small and large data models, with parallel processing across independent data flows.", "des_premiers_domaines_livres_puis_l_autonomie": "First domains delivered, then autonomy", "des_produits_de_donnees_documentes_des_indicateurs_coherents_d_u": "Documented data products, metrics that are consistent from one team to another, calculations you can trace back to their origin, preserved source context, and a clean foundation for analytics and AI use cases.", "des_rechargements_complets_faute_d_historisation_des_jointures_r": "Full reloads due to lack of historization, redundant joins and oversized warehouses drive up credit consumption.", "des_regles_de_qualite_ne_valent_que_confrontees_a_vos_donnees_re": "Quality rules only mean something once tested against your actual data.", "des_requetes_non_optimisees_sur_des_tables_non_partitionnees_fon": "Unoptimized queries on unpartitioned tables drive up slot consumption without warning.", "des_satellites_qui_grossissent_sans_raison_des_historiques_fauss": "Satellites growing for no reason, distorted history, drifting storage costs. Anatomy of a bug that never throws an error.", "des_sources_qui_changent": "Changing sources", "des_technologies_et_des_infrastructures": "Technology and infrastructure.", "des_trajectoires_documentees": "Documented journeys", "des_types_flottants_ou_des_dates_avec_fuseau_qui_se_serialisent_": "Float types or time-zoned dates that serialize differently depending on the engine.", "des_vues_metier_gouvernees_dimensions_faits_points_d_observation": "Governed business views — dimensions, facts, point-in-time snapshots — fed by the Raw Vault and ready for Power BI, Tableau or Looker.", "des_workers_sur_mesure": "Custom Workers", "des_workflows_de_donnees_flexibles": "Flexible data workflows,", "description": "description", "description_du_modele_metier_dans_metavault_entites_cles_metier_": "Description of the business model in metaVault: entities, business keys, relationships and shared naming conventions.", "designer_des_responsables_reels": "Assign real owners", "destinaitor": "DestinAItor", "destinaitor_aide_les_planificateurs_d_evenements_a_choisir_une_d": "Destinaitor helps event planners choose a destination in seconds rather than hours. The platform compares capacity, costs, sustainability and market context in a single prompt — with certified data. beVault is the invisible foundation: every destination record is versioned, every change is traceable, every piece of data exposed to AI is auditable.", "destinaitor_est_un_produit_destine_au_marche_pas_un_tableau_de_b": "DestinAItor is a market-facing product, not an internal dashboard. It shows what an industrialized data foundation makes possible: building end-user-facing AI applications without reinventing the data layer for every use case.", "destinaitor_developpe_par_dfakto_avec_pcma_repond_a_cette_questi": "DestinAItor, developed by dFakto with PCMA, answers this question in natural language — relying on consolidated, historized, traceable data rather than approximate generative search.", "detecter_les_anomalies_avant_qu_elles_ne_se_propagent": "Detect anomalies before they propagate", "detecter_les_erreurs_les_corriger_a_la_source_ameliorer_durablem": "Detect errors. Fix them at the source. Sustainably improve quality.", "detectez_les_anomalies_rendez_les_actionnables_et_permettez_aux_": "Detect anomalies, make them actionable and allow managers to correct the data at its source.", "detection_de_patterns_sur_de_larges_corpus_textuels": "Pattern detection on large text corpora", "detection_et_classification_d_objets_dans_des_images": "Object detection and classification in images", "detection_trop_tardive": "Detection too late", "deux_a_quatre_semaines_sur_un_domaine_reel_avec_criteres_de_succ": "Two to four weeks on a real domain, with success criteria defined together in advance.", "deux_architectures_a_perimetre_identique": "Two architectures, identical scope", "deux_certifications": "Two certifications.", "deux_couches_deux_responsabilites": "Two layers, two responsibilities", "deux_deploiements_distincts": "Two distinct deployments", "deux_generations_d_automatisation": "two generations of automation.", "deux_orchestrations_des_responsabilites_claires": "Two orchestrations, clear responsibilities", "deux_outils_data_vault_deux_perimetres_qualite_orchestration_et_": "Two Data Vault tools, two scopes: quality, and orchestration and deployment.", "deux_perimetres_differents": "Two different scopes.", "deux_portails_deux_usages": "Two portals, two uses", "deux_portes_d_entree": "Two entry points", "deux_reunions_deux_chiffres_de_ventes_aucun_moyen_de_trancher": "Two meetings, two different sales figures, no way to settle it", "deux_semaines_rendues_a_la_finance": "Two weeks back to finance", "dev_recette_et_production_partagent_le_meme_modele_de_reference_": "Dev, staging, and production share the same reference model but have distinct parameters and targets.", "developpee_specialement_pour_bevault_impossible_a_trouver_ailleu": "Developed exclusively for beVault, impossible to find elsewhere.", "developpement_recette_et_production_reposent_sur_la_meme_base_ce": "Development, staging, and production run on the same foundation, reducing discrepancies between environments.", "devenir_partenaire": "Become a partner", "dfakto": "dFakto", "dfakto_tout_le_reste_reste_en_interne": "dFakto — everything else stays internal", "dfakto_construit_des_plateformes_de_donnees_pour_des_organisatio": "dFakto has been building data platforms for public and private organizations for years. beVault grew out of that practice. Our services follow the same principle: we work with your teams, not in their place, and we leave once they're self-sufficient.", "dfakto_est_certifie_data_vault_2_0_bevault_la_plateforme_issue_d": "dFakto is Data Vault 2.0 certified. beVault, the platform born from this practice, is deployed at financial institutions, public organizations and fast-growing companies.", "dfakto_est_certifiee_iso_iec_27001_2022_dans_le_perimetre_certif": "", "dfakto_est_une_societe_de_conseil_et_d_edition_de_logiciels_spec": "dFakto is a consulting and software company specialized in data engineering, Data Vault 2.0 and ERP. Founded in Brussels, it helps public and private organizations build reliable, lasting data foundations.", "dfakto_et_dust_s_associent_pour_deployer_l_ia_en_entreprise_sur_": "dFakto and Dust team up to deploy enterprise AI on reliable data", "dfakto_et_pcma_lancent_destinaitor_la_plateforme_ia_pour_l_evene": "dFakto and PCMA launch DestinAItor, the AI platform for the events industry", "dfakto_obtient_la_certification_iso_et_renforce_son_engagement_e": "", "dfakto_obtient_la_certification_iso_u2060iec_u00a027001_et_renfo": "", "dfakto_l_equipe_qui_a_construit_bevault": "dFakto, the team that built beVault", "diagnostic_eclate": "Fragmented diagnostics", "dialog": "dialog", "discuter_de_vos_besoins": "Discuss your requirements", "discuter_de_votre_architecture": "Discuss your architecture", "discuter_de_votre_deploiement": "Discuss your deployment", "discuter_de_votre_fondation_ia": "Discuss your AI foundation", "discuter_de_votre_referentiel": "Discuss your reference data", "discuter_de_votre_reporting": "Discuss your reporting", "discuter_de_votre_trajectoire_data": "Discuss your data trajectory", "discutons_de_vos_sources_reelles_pas_d_une_liste_de_connecteurs": "Let's talk about your actual sources, not a list of connectors.", "disponible_y_compris_sans_connexion_sortante": "Available, even without an outbound connection", "disponibles_dans_la_base_cible_en_sql_standard_pour_power_bi_tab": "Available in the target database, in standard SQL, for Power BI, Tableau, Looker, SQL clients, and applications.", "distribution": "Distribution", "distribution_keys_et_sort_keys_calcules_a_partir_du_modele_metie": "Distribution keys and sort keys calculated from the business model", "distribution_keys_sort_keys_compression_encoding_le_code_exploit": "Distribution keys, sort keys, compression encoding — the code leverages native mechanisms instead of ignoring them.", "docker": "Docker", "docker_est_une_technologie_de_conteneurisation_et_de_deploiement": "Docker is a containerization and deployment technology, not a data platform. In a containerized deployment, beVault's components run in the environment defined with your teams: same deployment tools, same security rules, same operations as the rest of your application landscape.", "docker_et_bevault": "Docker and beVault", "docker_sert_de_technologie_de_deploiement_des_composants_sur_sit": "Docker is used as the deployment technology for components, on-premises, in the cloud, or hybrid, within the perimeter you control.", "docker_sert_de_technologie_de_deploiement_des_composants_sur_sit_2": "Docker is used as the deployment technology for components, on-premises, in the cloud, in PaaS, or hybrid, within the perimeter you control.", "documentation": "Documentation", "documentation_bevault": "beVault Documentation", "documentation_d_exploitation_et_documentation_du_modele_alimente": "Operational documentation and model documentation, populated from the beVault platform's metadata.", "documentation_et_lignage": "Documentation and lineage", "documentation_generee_depuis_les_fichiers_du_projet": "Documentation generated from the project files", "documentation_technique_complete_tutoriels_pas_a_pas_et_parcours": "Complete technical documentation, step-by-step tutorials, and structured training paths — all accessible online, no installation required.", "documenter_l_indicateur": "Documenting the indicator", "documenter_les_transformations": "Document the transformations", "documenter_une_chaine_de_traitement_quand_ses_auteurs_ont_quitte": "Documenting a processing pipeline once its authors have left.", "doit_on_abandonner_nos_rapports_power_bi_existants": "Do we have to abandon our existing Power BI reports?", "domaine_par_domaine_les_anciens_scripts_sont_remplaces_la_veloci": "Domain by domain, old scripts are replaced. Velocity increases with each iteration.", "donnee_de_reference": "Reference data", "donnees_concernees": "Data concerned", "donnees_de_destination_consolidees_et_historisees_avec_tracabili": "Consolidated and historicized destination data, with source traceability.", "donnees_historiques_precieuses": "Valuable historical data", "donnees_sans_modele_la_maison_sans_plan_d_architecte": "Data without a model: a house with no architect's blueprint", "donnees_versionnees": "Versioned data", "donner_a_vos_modeles_et_a_vos_agents_des_donnees_avec_du_context": "Give your models and agents data with context and history.", "donner_plus_de_capacite_a_vos_equipes": "Giving more capacity to your teams", "donner_une_structure_data_vault_au_lakehouse": "Bring Data Vault structure to the lakehouse", "donnez_a_l_ia_la_couche_semantique_dont_elle_a_besoin": "Give AI the semantic layer it needs", "donnez_aux_equipes_metier_et_techniques_un_cadre_commun_pour_def": "Give business and technical teams a shared way to define the model, discuss the data and make decisions together.", "download_our_paper_about_bevault_ai": "Download our paper about beVault & AI", "du_besoin_metier_au_produit_de_donnees": "From business need to data product", "du_champ_source_jusqu_au_mart": "From source field to mart", "du_sql_genere_pour_redshift": "SQL generated for Redshift", "du_sql_genere_pour_snowflake": "SQL generated for Snowflake", "dust_apporte_la_couche_agents_construction_d_assistants_metier_c": "Dust brings the agent layer: building business assistants, connecting to workplace tools, distributing them at scale across the enterprise. dFakto brings, with beVault, the governed data foundation these agents rely on.", "dv_2_1_est_la_revision_la_plus_recente_du_standard_avec_des_exig": "DV 2.1 is the most recent revision of the standard, with stronger requirements on auditability and advanced structures. Certification is issued by an independent third party after auditing the generated code.", "ecosysteme": "Ecosystem", "ecrire_a_l_equipe": "Email the team", "ecrire_a_l_equipe_2": "Email the team", "ecrire_les_patrons_ou_les_tenir_pour_acquis": "Write the patterns, or take them for granted", "ecriture_du_code_de_chargement": "Writing Load Code", "ecriture_et_derive_des_dag": "DAG Writing and Derivation", "editeur_praticien": "Practitioner Editor", "edition_limitee": "Limited Edition", "effet_indirect": "Indirect effect", "effort_de_maintenance_annuel": "Annual maintenance effort", "eight_advisory": "Eight Advisory", "elements_concrets": "Concrete elements", "elle_s_applique": "It applies.", "elles_meritent_une_architecture_a_la_hauteur": "They deserve an architecture that lives up to them.", "email": "Email", "en_bleu_les_composants_bevault_en_orange_les_composants_externes": "In blue, the beVault components. In orange, the external components that remain in your environment.", "en_construisant_d_abord_une_fondation_historisee_controlee_et_do": "By first building a historised, controlled and documented foundation, then exposing Information Marts intended for specific uses. beVault does not provide an AI model.", "en_deplacant_la_logique_metier_hors_de_la_base_transactionnelle_": "By moving business logic out of the transactional database, yes — mechanically. It's not our core promise, but it's an observed effect.", "en_droit_de_l_union_europeenne_une_pme_compte_moins_de_250_perso": "In European Union law, an SME has fewer than 250 people and respects the ceiling of 50 million euros in turnover or 43 million euros in total balance sheet. Partner or linked companies may also need to be taken into account in the calculation.", "en_general_un_seul_au_depart_puis_plusieurs_quand_l_equipe_maitr": "Usually just one to start, then several once the team masters the approach. The pace depends more on the availability of business stakeholders than on technology.", "en_parler": "Talk about it", "en_savoir_plus": "Learn more", "en_savoir_plus_sur_dfakto": "Learn more about dFakto", "en_savoir_plus_sur_la_certification_dfakto": "Learn more about dFakto’s certification →", "en_savoir_plus_sur_notre_approche_ia": "Learn more about our AI approach →", "en_service_manage_nous_les_appliquons_pour_vous_dans_votre_envir": "In managed service mode, we apply them for you. In your environment, they are delivered as a validated release, deployable according to your change schedule.", "enablement_technique_et_commercial_pour_vos_equipes": "Technical and sales enablement for your teams", "energie_utilities": "Energy & utilities", "enfin_reconcilies": "finally reconciled.", "enjeux": "Challenges", "enregistrement_des_opportunites_dans_le_portail_partenaire": "Registration of opportunities in the partner portal", "enterprise": "Enterprise", "entite_certifiee_deployments_factory_sa_operant_sous_le_nom_dfak": "Certified entity: Deployments Factory SA, trading as ‘dFakto’.", "entrainer_sur_des_donnees_dont_on_ignore_la_qualite_c_est_indust": "Training on data of unknown quality industrializes bias. The beVault quality score travels with every dataset served.", "entreprise": "Enterprise", "environnement": "Environment", "environnement_cible": "Target environment", "environnement_cible_ressources_acces_aux_systemes_sources_et_a_l": "Target environment, resources, access to source systems and the target database, applicable security rules.", "environnements": "Environments", "environnements_dev_recette_et_production_separes": "Separate dev, staging and production environments", "environnements_reproductibles": "Reproducible environments", "environnements_reproductibles_et_cloisonnes": "Reproducible and isolated environments", "environnements_separes": "Separate environments", "envoyez_votre_cahier_des_charges_nous_repondons_critere_par_crit": "Send us your specifications: we respond criterion by criterion, without embellishing points where we are not the best choice.", "envoyez_votre_grille_de_criteres_nous_repondons_point_par_point_": "Send us your criteria grid: we respond point by point, including where another choice would be more relevant.", "envoyez_nous_vos_contraintes_de_souverainete_nous_preparons_un_s": "Send us your sovereignty constraints: we'll prepare a suitable deployment blueprint.", "eon_collective": "Eon Collective", "equipements_remplaces_points_de_livraison_modifies_perimetres_re": "Replaced equipment, modified delivery points, redrawn boundaries: every state remains queryable at its date.", "equipements_zones_et_points_d_intervention_evoluent_sur_le_terra": "Equipment, zones and intervention points change in the field; their successive states are preserved.", "equipes_data_cloud_first": "Cloud-first data teams", "equipes_et_environnements_plus_larges": "Larger teams and environments", "erp_applications_metier_fichiers_echanges_par_mail_bases_histori": "ERPs, business applications, files exchanged by email, legacy databases whose schema nobody remembers: integration is almost always the most costly step of a data project. beVault structures this step so it is repeatable, documented and owned by your teams.", "erp_mes_gestion_d_entrepot_transport_achats_qualite_un_meme_arti": "ERP, MES, warehouse management, transport, purchasing, quality: the same item often carries several codes, and the same day doesn't start at the same time.", "est_ce_compatible_avec_notre_orchestrateur_de_conteneurs": "Is it compatible with our container orchestrator?", "est_ce_compatible_avec_unity_catalog": "Is it compatible with Unity Catalog?", "est_ce_lie_au_remplacement_de_l_erp_lui_meme": "Is this tied to replacing the ERP itself?", "estimation_de_delai_sur_votre_premier_domaine_elements_de_cout_t": "Timeline estimate for your first domain, total cost elements and, if relevant, an introduction to a reference in your sector.", "et_bien_plus_encore_toute_action_realisable_dans_l_interface_peu": "And much more: every action you can perform in the interface can be reproduced with the API.", "et_ce_qui_reste_chez_vous": "and what stays with you.", "et_les_autres_plateformes": "What about other platforms?", "et_pour_la_reversibilite": "What about reversibility?", "et_si_nous_changeons_de_plateforme_cible": "What if we change target platform?", "et_si_nous_utilisons_deja_un_orchestrateur": "What if we already use an orchestrator?", "et_tout_autre_outil_capable_d_echanger_avec_une_api": "And any other tool that can communicate through an API.", "et_toute_autre_tache_que_vous_confiez_a_votre_agent_dans_la_limi": "And any other task you give your agent, within the access you grant it.", "etablir_une_gouvernance_des_politiques_et_des_responsabilites_cl": "Establishing clear governance, policies, and responsibilities.", "etape_suivante": "Next step", "etapes_suivantes": "Next Steps", "etat_actuel": "Current State", "etat_des_lieux": "Current-state assessment", "etat_des_lieux_de_l_existant_et_des_priorites": "Assessment of the current setup and priorities", "etendez_la_plateforme_a_plusieurs_domaines_sources_et_equipes": "Extend the platform across multiple domains, sources and teams.", "etendre_progressivement": "Extend step by step", "etendre_sans_reconstruire": "Extend without rebuilding", "evaluer_mon_retour_sur_investissement": "Assess my return on investment", "evolution_du_modele": "Model evolution", "evolution_produit": "Product evolution", "exceptions_routees_vers_un_responsable_identifie": "Exceptions routed to an identified owner", "execution": "Execution", "execution_dans_l_environnement_defini_avec_vos_equipes": "Runs in the environment defined with your teams", "execution_du_graphe_ordonnancement_externe_a_prevoir": "Graph execution; external scheduling required", "execution_native_et_supervisee_ou_airflow_a_installer_securiser_": "Native and supervised execution, or Airflow to install, secure, and maintain?", "exemple_envoyer_un_script_sql_a_claude_avec_un_prompt_demandant_": "Example: send a SQL script to Claude with a prompt requesting structured metadata. Receive JSON. Parse and insert into the beVault metadata catalog.", "exemple_de_parsing": "Parsing example:", "exemples": "Examples:", "exigences_d_infrastructure_et_de_souverainete": "Infrastructure and sovereignty requirements", "exigences_de_deploiement_specifiques": "Specific deployment requirements", "exigences_reglementaires_elevees": "High regulatory requirements", "existe_t_il_une_facon_gratuite_de_demarrer": "Is there a free way to get started?", "exki": "EXKi", "exki_2": "Exki", "exki_gere_des_restaurants_dans_7_pays_en_propre_et_en_franchise_": "Exki manages restaurants in 7 countries, both owned and franchised, each with its own POS and back-office tools. Financial closings took two weeks. Decisions on menus, HR costs, and procurement came too late. beVault unified 8 source systems in a few weeks — without losing a single historical record.", "expliquer_un_ecart_entre_deux_versions_d_un_meme_etat": "Explain a discrepancy between two versions of the same state.", "exploitation": "Operations", "exploitation_par_vos_equipes_avec_vos_outils": "Run by your teams, with your tools", "explorer_les_fonctionnalites": "Explore features", "explorer_les_metadonnees_les_entites_les_relations_et_le_lignage": "Explore metadata, entities, relationships and lineage.", "explorer_vos_actifs_et_leur_lignage": "Explore your assets and their lineage", "exposer_proprement": "Cleanly expose", "exposer_une_vue_gouvernee": "Expose a governed view", "exposition_gouvernee": "Governed exposure", "exposition_via_api_et_serveur_mcp_pour_vos_agents_ia": "Exposure via API and MCP server for your AI agents", "extensibilite": "Extensibility", "extension_du_support_de_plateformes_cibles": "Extending target platform support", "extraction_d_entites_depuis_des_documents_noms_dates_montants": "Entity extraction from documents (names, dates, amounts)", "extraire_a_nouveau": "Extract again", "facturation_a_l_usage_du_calcul": "Billing based on compute usage", "facture_de_calcul_incontrolee": "Uncontrolled compute costs", "facture_de_compute_non_maitrisee": "Uncontrolled compute costs", "facture_imprevisible": "Unpredictable costs", "faire_evoluer_l_architecture_progressivement_sans_interrompre_le": "Evolve the architecture progressively, without disrupting existing reports.", "faire_evoluer_l_entrepot": "Evolving the warehouse", "faire_evoluer_l_existant_sans_tout_reecrire": "Evolve what exists without rewriting everything", "faites_travailler_les_equipes_metier_et_data_ensemble": "Bring business and data teams together", "faites_valider_le_mode_de_deploiement_par_vos_equipes_it": "Have your IT teams validate the deployment mode.", "faut_il_arreter_les_developpements_en_cours": "Do we need to stop ongoing developments?", "faut_il_deja_maitriser_data_vault_2_0": "Do we need to already master Data Vault 2.0?", "faut_il_disposer_d_une_grande_equipe_data": "Is a large data team necessary?", "faut_il_documenter_manuellement_chaque_colonne": "Do we need to manually document every column?", "faut_il_migrer_hors_d_oracle_pour_utiliser_bevault": "Do you have to migrate off Oracle to use beVault?", "faut_il_migrer_vers_azure": "Should we migrate to Azure?", "faut_il_preparer_des_donnees": "Do you need to prepare data?", "faut_il_rejeter_les_donnees_non_conformes": "Should non-compliant data be rejected?", "faut_il_remplacer_nos_step_functions_existantes": "Do we need to replace our existing Step Functions?", "faut_il_repartir_de_zero": "Should we start from scratch?", "faut_il_repartir_de_zero_sur_bigquery": "Should we start from scratch on BigQuery?", "faut_il_repartir_de_zero_sur_snowflake": "Should we start from scratch on Snowflake?", "faut_il_tout_integrer_d_un_coup": "Do you need to integrate everything at once?", "faut_il_tout_reconstruire_pour_passer_a_bevault": "Do we need to rebuild everything to switch to beVault?", "faut_il_tout_reprendre": "Do we need to start over?", "faut_il_un_catalogue_de_donnees_en_complement": "Do we need a data catalog in addition?", "faut_il_un_depot_git_externe": "Do we need an external Git repository?", "faut_il_un_orchestrateur_externe_pour_bevault": "Do we need an external orchestrator for beVault?", "fermer": "Close", "fermer_l_annonce": "Close the announcement", "fiabilite_mesuree": "Measured reliability", "fil_d_ariane": "Breadcrumbs", "finance_recupere_ses_deux_semaines_de_cloture_l_equipe_travaille": "Finance gets its two weeks of closing back. The team works on P&L analysis, not on reconciling Excel files.", "finesse_du_lignage": "Granular lineage", "follow_us": "Follow US", "fonctionnalites": "Features", "fondamentaux_du_modele_sujets_techniques_avances_strategie_data_": "Model fundamentals, advanced technical topics, data strategy, and product news.", "fondation_de_donnees_prete_pour_l_ia": "AI-ready Data Foundation", "fondation_de_modelisation_et_de_metadonnees": "Data modelling and metadata foundation", "fondation_ia": "AI foundation", "formation": "Training", "formation_et_transfert_de_competences": "Training & Knowledge Transfer", "formation_produit_et_certification_interne_de_vos_consultants": "Product training and internal certification of your consultants", "formation_technique": "Technical training", "formation_transfert_de_competences_et_documentation": "Training, knowledge transfer and documentation", "formation_transfert_de_competences_et_support": "Training, knowledge transfer and support", "formats": "Formats", "formulaires_de_candidature_disponibles_en_francais_et_en_anglais": "Application forms available in French and English", "formulation_exacte": "Exact wording", "fournisseurs": "Suppliers", "fournisseurs_achats": "Suppliers & procurement", "framework_de_qualite_des_donnees": "Data quality framework", "framework_de_transformation_contre_automatisation_data_vault_de_": "Transformation framework versus end-to-end Data Vault automation.", "framework_integre_au_chargement": "Framework built into the load", "framework_integre_au_chargement_regles_versionnees": "Framework built into the load, versioned rules", "framework_integre_regles_versionnees_exceptions_gerees": "Built-in framework, versioned rules, managed exceptions", "framework_qualite_elargi": "Expanded quality framework", "france_2030": "France 2030", "franchise_et_succursales_unifies": "unified franchise and branches", "frontiere": "Boundary", "gains_immediats_equipe_debutante": "Immediate gains, beginner team", "garantie_par_construction": "Guaranteed by design", "garder_la_main": "Stay in control", "gardez_vos_donnees_la_ou_votre_organisation_en_a_besoin": "Keep your data where your organization needs it.", "generalement_adressee_par_un_outil_tiers": "Usually addressed by a third-party tool", "generateur_de_code_contre_plateforme_complete_ce_qui_reste_a_con": "Code generator versus complete platform: what's left to build after generation.", "generateur_de_code_vs_plateforme_complete": "Code generator vs. complete platform", "generation_automatique_du_code": "Automatic code generation", "generation_de_code_data_vault": "Data Vault code generation", "generation_du_code_de_chargement": "Load code generation", "generation_du_code_t_sql": "T-SQL code generation", "generation_du_sql_db2_natif": "Native DB2 SQL generation", "generation_du_sql_oracle_natif": "Native Oracle SQL generation", "generer_du_code_ne_suffit_pas_a_faire_tourner_un_entrepot": "Generating code isn't enough to run a warehouse", "generer_du_code_ne_suffit_pas": "Generating code isn't enough.", "generer_et_rafraichir": "Generate and refresh", "generer_et_tester": "Generate and test", "generes_depuis_le_metamodele": "Generated from the metamodel", "generes_depuis_le_metamodele_a_jour_par_construction": "Generated from the metamodel, up to date by design", "gestion_des_branches": "Branch management", "gestion_des_cas_limites_ctes_requetes_imbriquees_transformations": "Edge case management (CTEs, nested queries, complex transformations)", "git_store": "Git Store", "glossaire": "Glossary", "go_home": "Go home", "golden_record": "Golden record", "google_bigquery": "Google BigQuery", "google_bigquery_est_il_deja_supporte": "Is Google BigQuery already supported?", "gouvernance_et_evolution": "Governance and evolution", "gouvernance_operationnelle": "Operational governance", "gouvernance_partielle": "Partial governance", "gouverner_aussi_les_sorties": "Govern outputs too", "grace_a_la_reduction_des_reclamations_traitees_manuellement": "through the reduction of manually processed claims", "grandir_sans_reconstruire_la_fondation": "Grow without rebuilding the foundation", "graphe_de_dependances_deduit_du_modele": "Dependency graph inferred from the model", "grille_de_lecture": "Reading grid", "group": "group", "guides_utilisateur_reference_api_notes_de_version_et_guides_par_": "User guides, API reference, release notes, and module-specific guides. Updated with every release.", "guides_utilisateurs_api_et_support_technique_bevault": "User guides, API, and beVault technical support.", "hash_diff_empreinte_du_contenu_utilisee_pour_ne_charger_que_les_": "Hash diff: content fingerprint, used to load only true changes.", "hash_key_identifiant_technique_deterministe_derive_de_la_cle_met": "Hash key: deterministic technical identifier derived from the business key.", "hash_keys_determinisme_et_hygiene": "Hash keys: determinism and hygiene", "historique_absent": "Missing history", "historique_ecrase": "Overwritten history", "historique_integral_sans_ecrasement_des_etats_passes": "Complete history, without overwriting past states", "historique_perdu": "Lost history", "historisation": "Historization", "historisation_complete_et_piste_d_audit_par_nature": "Full historisation and an audit trail by design", "historisation_des_donnees_critiques_sans_impact_sur_les_systemes": "Historization of critical data without impacting source systems", "historisation_et_marts_sur_oracle": "Historization and marts on Oracle", "historisation_et_qualite": "Historization and quality", "historisation_native_chaque_etat_de_la_donnee_est_conserve_et_da": "Native historization: every data state is preserved and datable", "historisation_native_sans_dependance_aux_mecanismes_temporels_ma": "Native historization, without reliance on homegrown temporal mechanisms", "historisation_native_sans_rechargements_complets": "Native historization, without full reloads", "historisation_native_sans_rechargements_complets_qui_consomment_": "Native historization, without full reloads that consume slots", "historisation_native_sans_tables_de_travail_improvisees": "Native historization, without improvised staging tables", "historisation_sans_ecrasement_des_donnees_existantes": "Historization without overwriting existing data", "historisation_sans_impact_source": "Historization without source impact", "historiser_controler_et_documenter_avant_d_ouvrir_des_usages_ia": "Historise, control and document before opening up AI use cases.", "hors_perimetre": "Out of scope", "hors_perimetre_produit": "Out of product scope", "hubs_liens_satellites_la_mecanique_du_data_vault_expliquee": "Hubs, links, satellites: Data Vault mechanics explained", "hubs_links_et_satellites_conformes_au_standard_dv_2_1_avec_le_co": "Hubs, links and satellites compliant with the DV 2.1 standard, with the load code generated for the target engine.", "hubs_links_et_satellites_doivent_respecter_la_separation_stricte": "Hubs, links, and satellites must respect the strict separation between business key, relationship, and context. Any deviation — a descriptive attribute in a hub, for example — is disqualifying.", "hybride": "Hybrid", "ia_data_vault_la_combinaison_qui_change_tout": "AI & Data Vault: the game-changing combination", "ia_evenementiel": "AI & Event-driven data", "ia_evenementiel_produit_dfakto": "AI & Event-driven data (dFakto product)", "ia_et_data_vault_3_synergies_pour_des_equipes_data_modernes": "AI and Data Vault: 3 synergies for modern data teams", "ia_modernisation_migration_bi_mdm_gouvernance": "AI, modernization, migration, BI, MDM, governance", "iam_gere_les_acces_mais_ne_dit_rien_sur_la_qualite_des_donnees_n": "IAM manages access but says nothing about data quality or which table is authoritative for which indicator.", "ibm_db2": "IBM DB2", "ibm_db2_2": "IBM Db2", "ibm_db2_heberge_souvent_les_donnees_les_plus_critiques_et_les_pl": "IBM Db2 often hosts an organization's most critical and long-standing data: banking transactions, management data, operational history. beVault generates SQL tailored to Db2 and lets you build a Data Vault 2.0 architecture directly on your existing infrastructure, without disrupting production systems or forcing a move to the cloud.", "idealement_l_architecte_data_et_le_responsable_metier_du_domaine": "Ideally the data architect and the business owner of the domain concerned. Cost and timeline questions are best handled with both present.", "identification_des_tables_a_forte_valeur_analytique_nous_commenc": "Identify tables with high analytical value. We start with the domain most requested by the business.", "identification_des_tables_db2_a_forte_valeur_analytique_nous_com": "Identifying the Db2 tables with the highest analytical value. We start with the domain that unlocks the most use cases.", "identifie_t_elle_le_meme_objet_reel_dans_tous_les_systemes_qui_l": "Does it identify the same real-world object across all systems that handle it? If not, a composite key or a correspondence reference is needed.", "identifier": "Identify", "identifier_et_evaluer_les_risques_lies_a_la_securite_de_l_inform": "Identifying and assessing information security risks.", "identifier_et_reconcilier_les_cles_metier": "Identify and reconcile business keys", "identifier_les_domaines_et_les_sources_qui_comptent": "Identify the domains and sources that matter", "identifiez_la_part_passee_a_ecrire_ou_corriger_du_code_de_charge": "Identify the share of time spent writing or fixing loading code and orchestration dependencies.", "identite_et_habilitations": "Identity and authorizations", "il_faut_aussi_une_equipe": "You also need a team.", "il_faut_le_faire_tourner": "It has to be run.", "il_historise_le_contexte_descriptif_sans_ecraser_le_passe": "It historicizes the descriptive context without overwriting the past.", "il_isole_les_relations_qui_sont_la_partie_la_plus_volatile_du_re": "It isolates relationships, which are the most volatile part of reality.", "il_leur_donne_une_structure": "it gives them a structure.", "il_lui_manque_une_architecture": "What it lacks is an architecture.", "il_permet_d_ajouter_une_source_sans_renegocier_l_existant": "It allows a new source to be added without renegotiating what already exists.", "il_rend_explicite_l_identification_metier_des_objets_les_cles_me": "It makes the business identification of objects explicit (business keys).", "il_y_a_des_contextes_ou_dbt_est_le_bon_choix": "There are contexts where dbt is the right choice", "illustration_creation_dynamique_de_workflows_dans_bevault": "Illustration: dynamic workflow creation in beVault", "illustration_deploiement_de_la_plateforme_dans_l_environnement_d": "Illustration: the platform deployed in the customer's environment", "illustration_equipes_client_et_equipes_dfakto_travaillant_ensemb": "Illustration: client teams and dFakto teams working together", "illustration_extension_des_workflows_par_des_workers_personnalis": "Illustration: extending workflows with custom Workers", "illustration_mise_en_production_progressive_et_montee_en_autonom": "Illustration: gradual rollout to production and growing team autonomy", "illustration_states_coordonne_les_workers_qui_executent_les_tach": "Illustration: States coordinates the Workers that execute tasks", "illustration_une_equipe_reduite_qui_construit_une_fondation_de_d": "Illustration: a small team building a common data foundation", "illustration_workflows_decoupes_en_machines_a_etats_plus_petites": "Illustration: workflows split into smaller state machines", "illustration_du_parcours_bevault_de_la_modelisation_a_l_orchestr": "Illustration of the beVault journey, from modeling to orchestration", "ils_deploient_bevault_avec_nous": "They deploy beVault with us", "ils_echouent_sur_les_donnees": "They fail because of the data.", "ils_ont_reconstruit": "They rebuilt", "implementation": "Implementation", "implementation_support": "Implementation & support", "implementation_et_mise_en_production": "Implementation and production rollout", "implementation_technique_6_etapes": "Technical implementation: 6 steps", "implementation_formation_support": "Implementation, Training & Support", "impossible_d_arreter_les_systemes_pour_restructurer_la_migration": "Stopping the systems to restructure isn't an option. Migration happens in parallel, domain by domain.", "incluez_toujours_les_metadonnees_ia_comme_attributs_satellites_v": "Always include AI metadata as satellite attributes: model version, confidence scores, prompt version, processing timestamp.", "inclus": "Included", "inclus_dans_la_plateforme": "Included in the platform", "incluse_calculee_depuis_le_graphe_de_dependances": "Included, calculated from the dependency graph", "incluse_dependances_deduites_du_modele": "Included, dependencies inferred from the model", "industrialiser_les_cas_d_usage": "Industrialising use cases", "industrie_supply_chain": "Industry & supply chain", "industries": "Industries", "industries_assurance": "Industries — Insurance", "industries_energie_utilities": "Industries — Energy & utilities", "industries_industrie_supply_chain": "Industries — Industry & supply chain", "industries_mobilite_services_urbains": "Industries — Mobility & urban services", "industries_retail_biens_de_consommation": "Industries — Retail & consumer goods", "industries_secteur_public": "Industries — Public sector", "industries_services_financiers": "Industries — Financial services", "information_mart": "Information Mart", "information_marts": "Information Marts", "information_marts_2": "Information Marts", "information_marts_et_documentation": "Information Marts and documentation", "information_marts_et_mise_en_production": "Information Marts and production rollout", "information_marts_gouvernes": "Governed Information Marts", "information_marts_gouvernes_2": "Governed Information Marts", "information_marts_pour_la_bi_et_l_analytique": "Information Marts for BI and analytics", "infrastructure_les_points_de_decision": "Infrastructure: the decision points", "ingestion": "Ingestion", "insights": "insights.", "installation_sur_votre_propre_infrastructure_pour_les_environnem": "Installation on your own infrastructure, for regulated or disconnected environments. Components and data remain within your network perimeter.", "instruction_de_format_explicite": "Explicit format instruction", "integration": "Integration", "integration_connectivite": "Integration & connectivity", "integration_services": "Integration & Services", "integration_aux_contraintes_techniques_de_l_organisation": "Integration with the organisation's technical constraints", "integration_aws_partielle": "Partial AWS integration", "integration_des_sources": "Source integration", "integration_des_sources_et_mappings": "Source integration and mappings", "integration_des_systemes_qui_apparaissent_apres_la_mise_en_produ": "Integration of systems that appear after go-live, or inclusion of those that had been excluded from the initial scope.", "integration_des_workers": "Worker integration", "integration_et_connectivite": "Integration and connectivity", "integration_et_connectivite_des_donnees": "Data Integration & Connectivity", "integration_naturelle_dans_l_ecosysteme_google_cloud": "Natural integration into the Google Cloud ecosystem", "integration_par_api": "API integration", "integration_sso_saml_roles_granulaires_par_projet_et_par_domaine": "SSO/SAML integration, granular roles by project and domain, and the least-privilege principle applied down to API keys.", "integration_gouvernance_et_trajectoire_d_evolution": "Integration, governance and evolution roadmap", "integrations_et_deploiement_2": "Integrations & deployment", "integrer_bevault_dans_vos_processus_ci_cd_et_de_deploiement": "Integrate beVault into CI/CD and deployment processes.", "integrer_et_conserver_l_historique_applicatif": "Integrate and retain application history", "integrer_et_historiser_les_sources_qui_comptent": "Integrate and historize the sources that matter", "integrer_les_sources_concernees": "Integrate the relevant sources", "integrite_et_historisation": "Integrity and historization", "interaction_raffinement_iteratif": "Interaction, iterative refinement", "interface_bevault": "beVault interface", "interface_bevault_colonnes_d_une_table_source_reliees_aux_hubs_l": "beVault interface: source table columns linked to the model's hubs, links and satellites", "interface_bevault_couche_de_distribution_des_information_marts": "beVault interface: distribution layer for Information Marts", "interface_bevault_editeur_de_graphe_avec_hubs_liens_et_satellite": "beVault interface: graph editor with hubs, links and satellites", "interface_bevault_editeur_de_graphe_et_modele_de_donnees": "beVault interface: graph editor and data model", "interface_bevault_liste_des_controles_de_qualite_avec_niveau_typ": "beVault interface: list of quality checks with level, type and criticality", "interface_bevault_mapping_des_colonnes_d_une_table_source_vers_l": "beVault interface: mapping the columns of a source table to the objects of the model", "interface_graphique": "Graphical interface", "interface_visuelle_et_metamodele_natif_certifie_dv_2_1": "Visual interface and native metamodel certified DV 2.1", "interface_visuelle_metamodele_certifie_dv_2_1": "Visual interface, DV 2.1-certified metamodel", "interrogez_vos_data_scientists_les_memes_quatre_manques_revienne": "Ask your data scientists: the same four shortcomings arise in every delayed project.", "interruption_lors_des_migrations_pos": "interruption during POS migrations", "inventaire_de_ce_qui_est_deja_orchestre_cote_aws_et_de_ce_qui_re": "Inventory of what is already orchestrated on the AWS side and what will fall under the data platform.", "inventaire_des_sources_des_rapports_et_de_leurs_consommateurs_on": "Inventory of sources, reports and their consumers. We start with a domain of real value and manageable complexity, never the hardest one.", "inventaire_des_sources_des_rapports_et_de_leurs_consommateurs_on_2": "Inventory of sources, reports and their consumers. We identify the domains with the highest business value and manageable complexity.", "inventaire_et_priorisation": "Inventory and Prioritization", "iso_iec_27001_2022": "ISO/⁠IEC 27001:⁠2022", "itbm": "ITBM", "jan_de_nul": "Jan De Nul", "jeux_d_entrainement_non_reproductibles": "Non-reproducible training sets", "jeux_d_entrainement_reproductibles_versionnes_et_documentes_un_m": "Reproducible, versioned and documented training sets: a model can be retrained identically six months later.", "join_our_partner_ecosystem": "Join our partner ecosystem", "journal_complet_des_acces_des_modifications_de_modele_et_des_exe": "Full log of accesses, model changes, and executions. Every published figure can be reconstructed to its date.", "l_acces_reste_gouverne_ce_que_les_agents_peuvent_interroger_depe": "Access remains governed: what agents can query depends on the access rights and data products exposed, not on direct, open access to the warehouse.", "l_agence_de_parking_de_bruxelles_gerait_capteurs_horodateurs_pai": "Brussels' parking agency managed sensors, meters, payments, fines and finance in independent systems. Producing a consolidated report required considerable manual work. The city's growth made the situation untenable. beVault consolidated all sources into a single warehouse, with built-in quality controls and real-time dashboards.", "l_agent_interroge_les_metadonnees_identifie_les_tables_correspon": "The agent: queries the metadata → identifies the matching tables → fills in the placeholders → generates the complete SQL → presents it for validation.", "l_ancien_systeme_continue_de_tourner_pendant_que_le_nouveau_se_c": "The legacy system keeps running while the new one is being built.", "l_anomalie_est_constatee_apres_publication_le_metier_a_deja_vu_l": "The anomaly is found after publication. The business has already seen the wrong figure, and trust is lost faster than it's rebuilt.", "l_api_bevault": "The beVault API", "l_api_bevault_permet_a_vos_applications_et_outils_d_automatisati": "The beVault API allows your applications and automation tools to interact with beVault without requiring users to perform every operation manually through the graphical interface.", "l_api_donne_un_acces_programmatique_aux_actions_disponibles_dans": "The API provides programmatic access to the actions available in the beVault interface. This means that operations performed by a user can also be integrated into scripts, applications, workflows and enterprise platforms.", "l_api_permet_d_interagir_avec_la_plateforme_et_ses_metadonnees_c": "The API allows interaction with the platform and its metadata. It is not the channel through which Information Marts are made available.", "l_api_rest_complete_et_le_serveur_mcp_rendent_la_plateforme_pilo": "The full REST API and the MCP Server make the platform controllable by your scripts, your CI pipelines and your agents. Source integration and the metadata catalog complete the picture.", "l_approche_orchestration_simple": "The approach: simple orchestration", "l_approche_bevault_traiter_les_sorties_ia_comme_n_importe_quelle": "The beVault approach: treat AI outputs like any other source", "l_approche_bevault_en_5_etapes_source_build_verify_distribute_or": "The beVault approach in 5 steps: Source → Build → Verify → Distribute → Orchestrate", "l_approche_data_vault_2_0_est_elle_adaptee_a_db2": "Is the Data Vault 2.0 approach suited to DB2?", "l_approche_de_deploiement_depend_de_votre_environnement_techniqu": "The available deployment approach depends on your technical environment and requirements. Discuss your context with the team to identify the appropriate option.", "l_approche_saine_consiste_a_corriger_d_abord_la_regle_de_calcul_": "The sound approach is to first fix the hash-calculation rule and normalization, start clean for subsequent loads, then treat existing history as a documented remediation operation, keeping a record of what was consolidated.", "l_architecture_cible_posee_avant_le_code": "The target architecture, set before the code", "l_architecture_du_serveur_mcp_bevault": "The beVault MCP server architecture", "l_article_precedent_montrait_comment_l_orchestration_simple_auto": "Our previous article showed how simple orchestration automates repetitive tasks. But what happens when you need iterative dialogue? That's where agent architectures excel.", "l_article_precedent_montrait_comment_les_agents_avec_api_directe": "The previous article showed how agents with direct API access deliver massive productivity gains. It also revealed their architectural constraints: tool proliferation, configuration overhead, platform lock-in. These constraints limit long-term scalability, portability and maintainability.", "l_assurance_que_la_securite_est_integree_a_nos_operations_quotid": "Assurance that security is embedded into our daily operations.", "l_automatisation_data_vault_en_detail": "Data Vault automation in detail", "l_avantage_strategique": "The strategic advantage", "l_avenir_de_l_implementation_data_vault_n_est_pas_de_remplacer_l": "The future of Data Vault implementation isn't about replacing data engineers — it's about amplifying their capabilities and making data modeling accessible to more people across the organization.", "l_ecosysteme_bevault_et_les_trois_portes_d_entree": "The beVault ecosystem and its three entry points", "l_ecriture_manuelle_des_pipelines_chaque_table_source_produit_du": "Manual pipeline writing: each source table produces repetitive code, written and tested by hand, with variations from one developer to another.", "l_eligibilite_n_est_pas_automatique_elle_depend_de_votre_situati": "Eligibility is not automatic: it depends on your situation and the scope considered. We discuss it with you before any proposal.", "l_empecher_par_construction": "Preventing it by design", "l_emplacement_des_composants_n_est_pas_un_detail": "Where components run is not a detail", "l_enjeu": "The challenge", "l_enregistrement_retenu_comme_faisant_foi_pour_une_entite_constr": "The record chosen as authoritative for an entity, built by reconciling multiple sources according to explicit rules.", "l_ensemble_des_controles_verifiant_que_les_donnees_sont_complete": "The set of controls verifying that data is complete, consistent and compliant with business rules, with explicit handling of exceptions.", "l_equipe": "The team", "l_equipe_data_assemble_les_structures_de_restitution_et_les_regl": "The data team assembles the consumption structures and associated business rules in beVault, documented in the same place as the model.", "l_equipe_derriere_bevault": "The team behind beVault", "l_equipe_dfakto": "The dFakto team", "l_equipe_dfakto_aux_cotes_de_la_votre_du_cadrage_a_la_production": "The dFakto team alongside yours, from scoping to production.", "l_etat_exact_d_un_contrat_au_moment_d_un_sinistre": "The exact state of a contract at the time of a claim.", "l_evolution_est_decrite_dans_metavault_les_controles_de_conformi": "The change is described in metaVault; DV 2.1 compliance checks apply immediately.", "l_evolution_se_traite_dans_le_modele_et_dans_les_definitions_de_": "Changes are handled in the model and in the relevant mart definitions, along with the associated documentation. The scale of the work depends on the nature of the change.", "l_existant_n_est_pas_qu_une_dette": "The existing setup isn't just debt", "l_historique_est_intact": "History stays intact", "l_historique_existant_peut_il_etre_repris": "Can the existing history be carried over?", "l_historisation_rend_le_chiffre_d_hier_reproductible_on_peut_res": "Historization makes yesterday's figure reproducible: you can restore the state of the data as of the relevant date, rather than recalculating from today's state. Lineage lets you trace a published metric back to the source fields that fed it.", "l_ia_ne_cite_que_des_donnees_dont_l_origine_est_tracable_pas_d_h": "AI only cites data whose origin is traceable. No hallucination on capacity or cost figures.", "l_identifiant_metier_retenu_numero_d_entreprise_identifiant_nati": "The chosen Business Key — company number, national identifier, combination of fields — is a decision documented in the model, not an implicit convention.", "l_identifiant_qu_utilise_l_organisation_pour_designer_un_objet_d": "The identifier an organization uses to designate a real-world object: a customer number, a contract reference, an employee ID. It's used to match records coming from different systems.", "l_inconvenient_est_connu_ecrit_a_la_main_un_data_vault_demande_b": "The drawback is well known: hand-written, a Data Vault requires a lot of repetitive code and a discipline few teams sustain over time. beVault handles this mechanical part and leaves your teams the part that has value — business meaning.", "l_information_de_qualite_est_reliee_a_la_donnee_concernee_et_a_s": "Quality information is linked to the data concerned and its origin, so that the reliability of an indicator is visible when it is read.", "l_interface_l_api_et_le_serveur_mcp_ne_sont_pas_des_produits_dis": "The interface, API and MCP Server are not separate products. They are complementary ways to interact with the same beVault platform.", "l_objection_classique_est_legitime_le_data_vault_genere_beaucoup": "The classic objection is legitimate: the Data Vault generates many objects and a lot of repetitive code. Written by hand, this code accounts for most of the project's effort — and most of its defects.", "l_operateur_du_stationnement_bruxellois_sur_une_fondation_data_v": "The Brussels parking operator, on a governed Data Vault foundation for its operations.", "l_operateur_public_du_stationnement_bruxellois_a_structure_ses_d": "The public parking operator in Brussels structured its operational and control data on a governed Data Vault foundation.", "l_operation_qui_recupere_les_donnees_d_un_systeme_source_pour_le": "The operation that pulls data from a source system into the platform, either in full or incrementally.", "l_opportunite_documenter_vos_information_marts_avec_l_ia": "The opportunity: documenting your Information Marts with AI", "l_orchestrateur_integre_execute_les_traitements_gere_les_dependa": "The integrated orchestrator executes processing, manages dependencies, and provides visibility into what happened. The output: documented datasets usable by your BI tools, business users, and AI agents.", "l_orchestrateur_integre_execute_les_traitements_gere_les_dependa_2": "The integrated orchestrator executes processes, manages dependencies, and provides visibility into every execution.", "l_orchestrateur_ne_l_est_pas": "The orchestrator is not.", "l_orchestration_est_la_voyez_ce_qu_elle_rend_possible_pour_l_ia": "Orchestration is built in. See what it makes possible for AI.", "l_orchestration_integree": "Integrated orchestration", "l_orchestration_reconstruite_a_part_dependances_reprises_sur_inc": "Orchestration rebuilt separately: dependencies, incident recovery, scheduling — a project within the project, often handed to an external tool to administer.", "l_orchestration_suit_les_dependances_du_modele_ordre_d_execution": "Orchestration follows the model's dependencies: execution order, parallelism, error retries and supervision. AWS Step Functions is supported as an external orchestrator when you already use one.", "l_ordre_des_chargements_les_reprises_sur_erreur_et_le_parallelis": "Load order, error recovery, and parallelism are all derived from the model's dependency graph.", "l_outil_externe_voit_une_table_pas_un_satellite_alimente_par_tro": "The external tool sees a table, not a satellite fed by three sources. It's impossible to pinpoint the real origin of the defect.", "la_3nf_a_l_inverse_integre_proprement_mais_absorbe_mal_les_chang": "3NF, by contrast, integrates cleanly but absorbs source structure changes poorly: a new column or a new relationship requires touching existing tables, and therefore retesting everything that depends on them.", "la_boucle_qualite": "The quality loop", "la_brasserie_witloof_est_une_brasserie_artisanale_independante_b": "Brasserie Witloof is an independent craft brewery based in Brussels. Passionate about quality beers and creative collaborations, it shares the same values with beVault: excellence, attention to detail, and local roots.", "la_business_key_est_la_decision_la_plus_structurante_de_votre_mo": "The business key is the most critical decision in your model. Well-chosen, it survives migrations; poorly chosen, it condemns you to rebuild.", "la_capacite_d_une_organisation_a_reprendre_ou_deplacer_sa_platef": "An organization's ability to take back or move its platform without depending indefinitely on a vendor.", "la_certification_couvre_la_conception_le_developpement_la_fourni": "The certification covers the design, development, delivery and support of software solution services for data automation, AI-ready data governance and strategic execution.", "la_certification_dv_2_1_atteste_de_la_conformite_du_code_data_va": "DV 2.1 certification attests to the compliance of the generated Data Vault code. It says nothing about data quality, orchestration or deployment model. Yet that's exactly where the real cost of your platform plays out in year two.", "la_certification_dv_2_1_c_est_verifiable": "DV 2.1 certification is verifiable.", "la_certification_en_pratique": "Certification in Practice", "la_certification_est_elle_permanente": "Is the certification permanent?", "la_certification_ne_juge_pas_l_ergonomie_ni_le_marketing_elle_ex": "Certification doesn't judge usability or marketing: it examines what the tool produces and whether that result respects the standard's invariants.", "la_cle_metier_comme_point_de_convergence": "The business key as a convergence point", "la_cle_retenue_est_arbitree_avec_le_metier_puis_les_correspondan": "The chosen key is agreed with the business, then the correspondences between systems are established and materialized in the model.", "la_coherence_des_indicateurs_la_capacite_a_expliquer_un_chiffre_": "The consistency of metrics, the ability to explain a figure in a meeting, and the quality of context provided for future analytics and AI use cases.", "la_combinaison_repond_a_la_seule_question_qui_compte_pour_un_cdo": "The combination answers the one question that matters to a CDO: how to deploy AI without degrading the reliability of information circulated internally.", "la_comparaison_est_faite_confrontez_la_a_votre_contexte": "The comparison has been made. Put it to the test against your context.", "la_comparaison_est_posee_verifiez_la_sur_votre_modele": "The comparison is laid out. Check it against your model.", "la_comparaison_utile_porte_sur_le_cout_total_licence_mais_aussi_": "The comparison that matters is total cost: license, but also orchestrator, quality tool and operating time. We produce this calculation based on your actual assumptions.", "la_compatibilite_depend_de_votre_environnement_de_conteneurs_et_": "Compatibility depends on your container environment and its operational constraints. It's assessed during technical scoping to define the right deployment mode.", "la_confusion_vient_du_mot_plateforme_employe_des_deux_cotes_pour": "The confusion comes from the word \"platform\", used on both sides to mean different things.", "la_consolidation_des_sources_se_fait_par_domaine_les_systemes_co": "Sources are consolidated domain by domain: the relevant systems are connected, historized and qualified, without touching existing pipelines. Existing reports continue to be produced by the legacy environment until their equivalents have been reviewed and accepted.", "la_continuite_des_rapports_la_reconciliation_entre_ancien_et_nou": "Report continuity, reconciliation between old and new, historical data recovery, parallel operation and controlled cutover are properties of the approach described here. They are verified domain by domain, on your scope — they are not promised universally.", "la_contrainte": "The constraint", "la_coordination_des_traitements_dans_quel_ordre_sous_quelles_con": "The coordination of processes: in what order, under what conditions, with what dependencies, and what to do when one of them fails.", "la_correction_retroactive_est_la_regle_pas_l_exception": "Retroactive correction is the rule, not the exception", "la_correspondance_entre_les_champs_d_une_source_et_les_elements_": "The correspondence between a source's fields and the model's elements. In beVault, it's described, versioned metadata, not code scattered across the codebase.", "la_couche_de_restitution_est_generee_et_documentee_avec_lignage_": "The reporting layer is generated and documented, with full lineage from the source field to the report.", "la_couche_exposee_est_mise_a_disposition_des_roles_et_des_outils": "The exposed layer is made available to the relevant roles and tools, according to configured permissions.", "la_data_quality_native": "Native Data Quality", "la_data_vault_alliance_certifie_independamment_dossier_et_code_a": "The Data Vault Alliance independently certifies, based on documentation and code, that tools genuinely comply with the DV 2.1 standard. beVault has earned it — and here we explain exactly what that covers.", "la_data_vault_alliance_publie_la_liste_des_outils_certifies_vous": "The Data Vault Alliance publishes the list of certified tools. You can check any vendor's status directly — without relying on what the vendor claims itself.", "la_definition_retenue_est_implementee_une_seule_fois_documentee_": "The chosen definition is implemented once, documented and exposed to your existing BI tools in supported configurations.", "la_demarche": "The approach", "la_difference_cle_l_orchestration_simple_suit_un_chemin_predeter": "The key difference: simple orchestration follows a predetermined path. Agent systems chart their own route toward a goal.", "la_difference_de_fond": "The Fundamental Difference", "la_difficulte_ne_vient_pas_de_l_extraction_des_donnees_mais_de_t": "The difficulty isn't extracting the data, but everything around it: knowing what must be kept and for how long, ensuring existing reports keep working during the migration, and being able to explain a discrepancy between old and new. Without these three elements, the decision to decommission gets postponed indefinitely.", "la_direction_est_prise_nous_construisons_avec_vos_equipes_formon": "The direction is set: we build with your teams, train them, document, deploy to production and support future changes.", "la_documentation_derivee_a_la_main_elle_est_obsolete_le_jour_de_": "Manually derived documentation: it's obsolete the day it's delivered, making each evolution slower than the last.", "la_documentation_des_donnees_echoue_presque_toujours_pour_la_mem": "Data documentation almost always fails for the same reason: it is written alongside the system, then abandoned. In beVault, the model description is also what produces the processes: lineage is generated automatically for the elements built in the platform, while descriptions and additional metadata depend on the information provided by your teams.", "la_donnee_n_est_pas_exposee_brute_aux_consommateurs_elle_est_pub": "Data isn't exposed raw to consumers. It's published as documented data products, built once and reused across multiple use cases.", "la_duplication_silencieuse_ne_fait_echouer_aucun_chargement_le_p": "Silent duplication doesn't fail any load. The pipeline shows green, dashboards render, nobody is alerted. It's just that a satellite meant to record three changes a year records three hundred instead.", "la_finance_annonce_un_chiffre_d_affaires_le_commerce_en_annonce_": "Finance reports one revenue figure, sales reports another, and the meeting turns into a data investigation. The problem is rarely the visualization tool: it comes from diverging definitions, rules recreated in every report, and missing history.", "la_fondation_data_vault_open_source": "The Data Vault open source foundation", "la_fondation_data_vault": "The Data Vault foundation.", "la_fondation_ia": "The AI Foundation", "la_frontiere": "The boundary", "la_garantie_applicable_avant_un_avenant": "The coverage applicable before an amendment.", "la_generation_represente_une_part_importante_de_l_effort_initial": "Generation accounts for a large share of the initial effort, but a small share of the cost over five years. The rest — orchestration, quality, operations, governance — still needs to be built if the tool doesn't cover it.", "la_gestion_des_referentiels_en_pratique": "Reference data management in practice", "la_gouvernance_ne_se_declare_pas": "Governance can't just be declared.", "la_meilleure_facon_de_juger_reste_de_voir_la_plateforme_sur_vos_": "The best way to judge is still to see the platform on your own data.", "la_meme_approche_peut_etre_adaptee_a_des_projets_cibles_pour_les": "The same approach can be adapted to focused projects for SMEs, growing organisations and larger international data programmes.", "la_meme_architecture_s_applique_a_tout_secteur_ou_la_fiabilite_d": "The same architecture applies to any sector where answer reliability drives adoption — healthcare, finance, the public sector, industry.", "la_meme_donnee_pour_tous": "The same data for all", "la_meme_entite_decrite_differemment_partout": "The same entity, described differently everywhere", "la_methode": "The method", "la_methode_est_certifiee_voyez_maintenant_comment_la_qualite_est": "The method is certified. Now see how quality is integrated.", "la_mise_en_uvre_avance_par_domaines_avec_un_transfert_de_compete": "Implementation proceeds by domain, with a transfer of skills to your teams.", "la_mise_en_uvre_depend_des_acces_disponibles_du_perimetre_du_pro": "Implementation depends on available access, project scope, and target architecture. Scoping is done source by source with your teams.", "la_necessite_de_garder_le_controle_de_l_environnement": "The need to maintain control over the environment", "la_norme_definit_les_exigences_pour_etablir_mettre_en_uvre_maint": "The standard defines requirements for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). This system is designed to help organizations systematically manage information security risks, taking into account:", "la_ou_une_regle_a_ete_definie_et_acceptee_elle_produit_une_valeu": "Where a rule has been defined and accepted, it produces an explainable reference value. Ambiguous cases go to human arbitration, with the context needed to decide.", "la_plateforme": "The Platform", "la_plateforme_cible_est_connue_voyez_ce_que_bevault_y_deploie": "The target platform is known. See what beVault deploys there.", "la_plateforme_cible_et_l_orchestration_sont_deux_sujets_distinct": "The target platform and orchestration are two separate topics. Supported platforms are listed on the dedicated page.", "la_plateforme_d_un_cote_les_structures_generees_de_l_autre": "The platform on one side, generated structures on the other", "la_plateforme_de_donnees_prete_pour_l_ia_deployee_dans_votre_env": "The AI-ready data platform, deployed in your environment.", "la_plateforme_rend_elle_mon_organisation_conforme": "Does the platform make my organization compliant?", "la_plateforme_s_accompagne_d_un_chemin_vers_la_production": "The platform comes with a path to production.", "la_plateforme_s_installe_chez_vous": "The platform runs in your environment", "la_plupart_de_nos_echanges_commencent_par_un_probleme_precis_cho": "Most of our conversations start with a specific problem. Choose the one that looks most like yours.", "la_plupart_des_comparatifs_opposent_des_listes_de_fonctionnalite": "Most comparisons pit feature lists against each other. We prefer to start from the questions actually raised in selection committees: who orchestrates loads, where data quality lives, which infrastructure the product runs on, and what remains to be built once the code is generated.", "la_plupart_des_initiatives_d_intelligence_artificielle_butent_su": "Most AI initiatives run into the same reality: non-historized data that nobody can trace or trust. No model, however powerful, compensates for the lack of a foundation. A Data Vault provides exactly what's missing — full history, traceability and business semantics.", "la_plupart_des_organisations_achetent_un_outil_de_qualite_des_do": "Most organizations buy a data quality tool, plug it in downstream of the warehouse, and discover anomalies the next day in a report nobody acts on. beVault reverses the logic: rules live inside the platform, run during loading, and make reliability visible the moment the figure is produced.", "la_plupart_des_organisations_qui_ont_sql_server_ont_aussi_des_an": "Most organizations running SQL Server also have years of accumulated scripts, stacked views and working tables whose origin no one remembers. beVault generates native T-SQL optimized for on-premises SQL Server or Azure SQL, and lets you build a Data Vault 2.0 architecture on top of your existing infrastructure — without forcing a move to the cloud.", "la_plupart_des_organisations_traitent_les_resultats_de_leurs_sys": "Most organizations treat the results of their AI systems as disposable data. A customer email produces a sentiment score, a call is classified, a contract is annotated — and the output disappears into a log file or a temporary table. Never traced, never audited, never reused.", "la_plupart_des_outils_data_vault_cloud_first_s_arretent_a_la_gen": "Most cloud-first Data Vault tools stop at code generation: data quality, scheduling and error recovery remain your responsibility, in Airflow, Matillion or dbt. beVault covers the full chain, with DV 2.1 certification as an independent guarantee.", "la_plupart_des_plateformes_de_donnees_couteuses_le_sont_devenues": "Most expensive data platforms became expensive for lack of a decision made at the right time. This engagement is about framing objectives, taking an honest look at what exists, and settling on a target architecture your teams can defend internally.", "la_plupart_des_pme_et_organisations_publiques_restent_bloquees_d": "Most SMEs and public organizations remain stuck in the Excel era — not for lack of ambition, but for lack of access. This white paper explains how beVault closes that gap: enterprise-grade data infrastructure, without the budgets or teams that usually come with it.", "la_premiere_question_d_un_architecte": "An architect's first question", "la_prochaine_vague_d_automatisation_en_data_warehousing_n_est_pa": "The next wave of data warehousing automation isn't new code-generation tools. It's AI agents that leverage those tools to go even faster. We compare three patterns, from simplest to most advanced.", "la_progression_est_la_meme_a_chaque_domaine_ce_qui_change_c_est_": "The progression is the same for every domain. What changes is the difficulty: we start with a scope that has real value and manageable complexity.", "la_provision_telle_qu_elle_avait_ete_estimee_a_l_arrete_preceden": "The provision as it was estimated at the previous closing.", "la_puissance_de_l_orchestration_de_workflows": "Unleashing the power of workflow orchestration", "la_qualite_au_chargement": "Quality on Load", "la_qualite_des_donnees": "Data quality", "la_qualite_n_est_pas_un_etat_atteint_une_fois_c_est_une_boucle_q": "Quality is not a one-time state: it is a repeating loop that progresses data over time.", "la_qualite_traitee_en_fin_de_chaine_les_controles_arrivent_apres": "Quality treated at the end of the chain: controls arrive after production, when discrepancies are already arbitrated in meetings.", "la_qualite_elle_se_decouvre_trop_tard_dans_le_rapport_final_plut": "Quality, for its part, is discovered too late — in the final report rather than at the start of the chain. Knowledge of the processing stays in the heads of a few people and is rarely documented. And the first AI projects run into that same base: data that is neither historised, nor controlled, nor documented.", "la_question_n_est_pas_de_choisir_un_orchestrateur_mais_de_savoir": "The question isn't choosing an orchestrator, but knowing who triggers what and where to look when something fails.", "la_question_revient_a_chaque_comite_de_choix_nous_avons_deja_sno": "The question comes up in every selection committee: “we already have Snowflake, why add beVault?” Because those platforms provide storage and compute, not a model. They run the SQL you give them — someone still has to write it, evolve it, schedule it, and check its results. That's exactly beVault's scope.", "la_question_utile_n_est_pas_combien_d_ingenieurs_faut_il_mais_qu": "The useful question isn't “how many engineers do we need?” but “how much of what our engineers produce could be generated deterministically?”. On a Data Vault platform, the answer is: most of it.", "la_reduction_de_cout_vient_de_l_automatisation_du_code_vous_choi": "The cost reduction comes from code automation. You choose where to deploy.", "la_regle_de_calcul_est_ecrite_une_fois_au_bon_endroit_et_version": "The calculation rule is written once, in the right place, and versioned.", "la_regle_de_separation": "The Separation Rule", "la_regle_pratique_integrer_la_portee_dans_la_cle_metier_des_que_": "The practical rule: integrate the scope into the business key as soon as two sources can produce the same value for two different objects. The cost is zero during modeling; it is considerable after production deployment.", "la_reponse_data_vault_2_0_avec_bevault": "The Answer: Data Vault 2.0 with beVault", "la_reponse_data_vault_est_un_same_as_link_chaque_source_conserve": "The Data Vault answer is a same-as link: each source keeps its key in the hub, and the matching link carries the reconciliation decision. That decision remains revisable without destroying history, and you can always demonstrate on what basis two records were treated as the same customer.", "la_rupture_arrive_quand_on_ajoute_l_ia_au_lieu_de_stocker_seulem": "The shift happens when AI is added. Instead of storing only metadata, AI extracts structured, actionable insights from the content itself. Scanned contracts become structured databases. Call transcripts become sentiment datasets.", "la_separation_entre_modelisation_definition_des_workflows_et_exe": "The separation between modeling, workflow definition and execution lets the model evolve without rewriting the processes.", "la_serie_est_complete_passez_a_l_etape_d_apres": "The series is complete. Proceed to the next step.", "la_situation": "The situation", "la_source_corrigee_est_extraite_de_nouveau_sans_ecraser_l_histor": "The corrected source is extracted again, without overwriting the history of what was received.", "la_source_est_declaree_et_connectee_depuis_votre_infrastructure_": "The source is declared and connected from your infrastructure. Access remains managed by your teams, according to your security rules.", "la_structure_elle_reste_a_faire": "The structure, however, still has to be built.", "la_suite_implementation_formation_support": "What comes next: implementation, training & support", "la_tentation_est_d_ecraser_les_variantes_pour_produire_une_fiche": "The temptation is to flatten variants to produce a single record. That's precisely what makes the result questionable: as soon as a selection rule changes, nothing is verifiable anymore, and source systems no longer recognize themselves in the consolidated version.", "la_tentation_est_de_purger_les_doublons_a_posteriori_c_est_risqu": "The temptation is to purge duplicates after the fact. That's risky: in a Raw Vault, history is authoritative, and any deletion must be traceable and justified.", "la_valeur_pratique": "The practical value", "la_verification_qu_un_chiffre_produit_par_la_plateforme_correspo": "The check that a figure produced by the platform matches the one in the source system, with an explanation of any discrepancies found.", "la_version_est_promue_telle_quelle_ce_qui_est_valide_en_recette_": "The version is promoted as-is: what is validated in staging is exactly what goes to production.", "la_vue_de_reference_est_publiee_pour_les_applications_et_les_rap": "The reference view is published for applications and reports, together with the Data Lineage of every attribute back to its source system.", "le_benefice_concret": "The concrete benefit", "le_benefice_se_mesure_au_moment_ou_il_compte_lors_du_remplacemen": "The benefit shows up exactly when it matters: when a source system is replaced, the warehouse absorbs the new source without replaying history or renegotiating identifiers.", "le_benefice_se_voit_sur_la_duree_pas_sur_la_demo": "The benefit shows over time, not in a demo", "le_business_vault_construit_par_dessus_porte_les_regles_metier_a": "The Business Vault, built on top, carries the business rules: calculated aggregates, views, bridge tables, master data repositories. It can be rebuilt at will without ever touching the Raw Vault.", "le_cadrage_sert_a_situer_chaque_brique_et_chaque_responsabilite_": "Scoping serves to position each building block and each responsibility before construction begins.", "le_cas_des_cles_multi_sources": "The case of multi-source keys", "le_catalogue_est_le_point_d_entree_des_equipes_qui_doivent_trava": "The catalog is the entry point for teams who need to work with data they didn't build themselves: find an entity, a table or a column, and immediately see which business domain it belongs to and where it's used.", "le_catalogue_remplace_t_il_une_demarche_de_gouvernance": "Does the catalog replace a governance program?", "le_chemin_d_une_source": "The journey of a source", "le_chemin_d_une_valeur_de_la_source_jusqu_a_la_sortie_consommee_": "The path of a value, from source to consumed output, remains traceable — a practical precondition for any explanation.", "le_chemin_entre_les_sources_et_la_donnee_exposee_reste_consultab": "The path between sources and the exposed data remains available for review in the platform, within the scope covered by lineage.", "le_chemin_parcouru_par_une_donnee_de_son_systeme_d_origine_jusqu": "The path a piece of data takes, from its source system to the consumed output, including the transformations applied along the way.", "le_chiffre_arrive_vite_l_explication_beaucoup_moins": "The number comes fast. The explanation, far less so.", "le_chiffre_obtenu_est_votre_cout_d_opportunite_annuel_et_la_base": "The resulting figure is your annual opportunity cost — and the basis for a business case you can defend internally.", "le_cloud_n_est_pas_une_obligation_mais_sans_architecture_la_migr": "The cloud isn't mandatory. But without architecture, migration won't solve the underlying problems.", "le_code_de_chargement_est_regenere_et_execute_sur_l_environnemen": "The load code is regenerated and run on the development environment, with Verify rules active.", "le_code_est_genere_voyez_comment_l_orchestration_suit_automatiqu": "The code is generated. See how orchestration follows automatically.", "le_code_est_il_generique_ou_natif": "Is the generated code generic or native?", "le_code_genere_doit_etre_deterministe_et_coherent_le_meme_modele": "The generated code must be deterministic and coherent: the same model always produces the same result, an essential condition for industrialization without surprises.", "le_code_genere_est_il_lisible": "Is the generated code readable?", "le_code_genere_est_il_portable_vers_une_autre_plateforme": "Is the generated code portable to another platform?", "le_code_genere_m_appartient_il": "Do I own the generated code?", "le_code_genere_par_bevault_est_il_exportable": "Is the code generated by beVault exportable?", "le_code_genere_reste_t_il_exportable": "Does the generated code remain exportable?", "le_code_genere_s_applique_a_la_base_cible_que_vous_avez_retenue_": "The generated code applies to the target database you have selected: Snowflake, Amazon Redshift, Microsoft SQL Server, or PostgreSQL. Databricks, Microsoft Fabric, and Google BigQuery are coming soon.", "le_code_produit_exploite_les_specificites_de_la_plateforme_clust": "The generated code leverages the platform's specifics — clustering, micro-partitions, set-based operations — instead of generic SQL loosely translated.", "le_code_les_chargements_et_la_documentation_derivent_du_metamode": "Code, loads and documentation are derived from the metamodel", "le_comite_de_direction_discute_de_la_decision_plus_de_la_provena": "The executive committee discusses the decision, not the origin of the figure.", "le_comparatif_critere_par_critere": "The comparison, criterion by criterion", "le_composant_s_insere_dans_vos_regles_de_reseau_d_acces_et_de_jo": "The component fits within your network, access and logging rules, like any other application.", "le_contenu_reel_de_l_audit": "What the audit actually covers", "le_contexte_db2": "The DB2 context", "le_contexte_et_l_historique_integres_au_socle": "Context and history built into the foundation", "le_cout_d_une_plateforme_data_vault_ne_se_lit_pas_sur_la_facture": "The cost of a Data Vault platform isn't found on the license invoice: it's found in the number of tools your team has to integrate, secure and maintain all year round.", "le_crm_en_a_fait_deux_fiches_l_erp_en_a_une_troisieme_avec_une_r": "The CRM turned it into two records, the ERP has a third with an abbreviated company name, and the billing system still uses the old account number. Until these identities are reconciled, no cross-functional metric is reliable — and as long as source context is lost along the way, no one trusts the result.", "le_cycle_de_livraison": "The delivery cycle", "le_cycle_de_vie_est_long_les_systemes_ne_le_sont_pas": "The life cycle is long, systems aren't", "le_data_vault_alliance_sur_la_base_du_standard_data_vault_2_1_de": "The Data Vault Alliance, based on the Data Vault 2.1 standard defined by Dan Linstedt.", "le_data_vault_apporte_la_structure_bevault_automatise_le_travail": "Data Vault provides the structure. beVault automates the work.", "le_data_vault_est_puissant_mais_sa_mise_en_uvre_traditionnelle_e": "Data Vault is powerful, but implementing it traditionally requires specialised knowledge and a significant amount of repetitive code. beVault makes the methodology accessible through a shared, visual model of your business concepts, relationships and attributes. Business and technical teams can work from the same description, while beVault generates the structures, loading processes and documentation needed to put the model into operation.", "le_data_vault_fournit_les_patterns_coherents_le_contexte_metier_": "The Data Vault provides the consistent patterns, business context, traceability, and continuous quality that AI needs. beVault automates the construction of this foundation.", "le_data_vault_historise": "The Data Vault historizes.", "le_data_vault_les_structure": "The Data Vault structures them.", "le_data_vault_n_ecrase_rien_chaque_etat_est_conserve_date_et_rat": "The Data Vault overwrites nothing: every state is kept, dated and linked to its source. That's what makes a dataset reproducible a year later.", "le_data_vault_rend_explicites_les_concepts_metier_et_leurs_relat": "Data Vault makes business concepts and their relationships explicit. Your teams work from a model that is understandable to both business and technical stakeholders.", "le_data_vault_separe_ce_qui_est_stable_l_identification_metier_d": "The Data Vault separates what is stable (business identification) from what moves (relationships) and what changes constantly (attributes). This separation has a very concrete consequence: adding a source or an attribute is done by adding objects, not by modifying existing ones.", "le_data_vault_separe_la_donnee_brute_des_regles_d_interpretation": "The Data Vault separates raw data from interpretation rules. Each department can have its own mart, built on a shared, historized base of facts.", "le_data_vault_sans_le_travail_repetitif": "Data Vault, without the repetitive work.", "le_decalage_n_est_pas_une_erreur_d_estimation": "The gap isn't an estimation error", "le_defi_donnees_non_structurees_et_insights_ia": "The challenge: unstructured data and AI insights", "le_delai_de_livraison": "the delivery time.", "le_deploiement_est_applique_selon_votre_calendrier_de_changement": "The deployment is applied according to your change calendar, with no full reload of the history.", "le_document_existe_il_a_ete_valide_et_personne_ne_peut_dire_s_il": "The document exists, it's been validated, and no one can say whether it's being followed. The rules live in a repository separate from the processes; the processes, meanwhile, keep loading whatever they're given.", "le_domaine_legacy_n_est_arrete_que_lorsque_la_nouvelle_chaine_de": "The legacy domain is only decommissioned once the new data pipeline is reliable. The team then moves on to the next domain, with the approach already proven.", "le_fait_de_conserver_les_etats_successifs_d_une_donnee_au_lieu_d": "Keeping the successive states of a piece of data instead of overwriting the previous value. It allows a past situation to be reconstructed and a discrepancy to be explained.", "le_fait_de_maitriser_ou_les_donnees_sont_stockees_et_traitees_et": "Control over where data is stored and processed, and who can access it — a strong requirement in the public sector and regulated industries.", "le_flux_est_sources_bevault_base_vectorielle_agent_ia": "The flow is: Sources → beVault → Vector database ← AI Agent.", "le_fosse_data_entre_grandes_entreprises_et_pme": "The data gap between large enterprises and SMEs", "le_gain_n_est_pas_seulement_de_temps_il_est_de_defendabilite_une": "The gain isn't just time: it's defensibility. A destination recommendation can be backed up in front of a committee with sourced, dated figures.", "le_generateur_de_code_est_gratuit": "The code generator is free.", "le_git_store_est_integre_a_la_plateforme_il_peut_etre_connecte_a": "The Git Store is built into the platform. It can be connected to your existing CI/CD pipeline if you want promotions to be triggered from your pipelines.", "le_git_store_et_les_promotions_d_environnement_remplacent_les_pr": "The Git Store and environment promotions replace manual deployment procedures and their windows of risk.", "le_hub_la_liste_des_identifiants_metier": "The hub: the list of business identifiers", "le_lakehouse_sans_structure_ce_qu_on_retrouve": "The lakehouse without structure: what you end up with", "le_lignage_couvre_t_il_ce_qui_se_passe_hors_de_bevault": "Does lineage cover what happens outside beVault?", "le_lignage_et_la_documentation_de_la_plateforme_permettent_de_su": "The platform's lineage and documentation let you trace the path between sources and the exposed data, within the covered scope.", "le_lignage_porte_sur_les_traitements_pilotes_par_la_plateforme_c": "Lineage covers the processes driven by the platform. What is transformed downstream, in a BI tool for example, falls under that tool.", "le_lignage_l_historisation_et_les_regles_documentees_permettent_": "Data Lineage, history tracking and documented rules make it possible to reconstruct how a metric was produced at a given date. Compliance with a specific regulatory framework then depends on your own scope.", "le_link_la_relation_et_rien_d_autre": "The link: the relationship, and nothing else", "le_mapping_etant_une_metadonnee_la_modification_est_faite_au_niv": "Since mapping is metadata, changes are made at the description level and then propagated to the processes, rather than scattered across code.", "le_mart_est_produit_puis_rafraichi_par_l_orchestration_integree_": "The mart is produced and then refreshed by the built-in orchestration, at the pace defined for that use case.", "le_meme_client_existe_souvent_sous_trois_identifiants_dans_trois": "The same customer often exists under three different identifiers in three systems. The temptation is to pick the “master system” and ignore the rest. That's a bet on the organization, not on the data — and organizations change.", "le_meme_client": "The same client,", "le_meme_produit_dans_votre_environnement": "The same product, in your environment", "le_metier_formule_la_question_a_laquelle_il_veut_repondre_et_la_": "The business defines the question it wants answered and the expected level of detail. The concepts already exist in the Data Vault: nothing to re-ingest.", "le_metier_la_reconnait_il_sans_traduction_si_l_on_doit_passer_pa": "Does the business recognize it without translation? If a lookup table is needed to explain it, it is not a business key.", "le_mode_de_deploiement_suit_vos_contraintes_d_infrastructure_san": "The deployment mode follows your infrastructure constraints, without changing the product your teams use.", "le_model_context_protocol_ou_mcp_fournit_une_facon_standard_pour": "The Model Context Protocol, or MCP, provides a standard way for AI applications to connect to external tools and data sources.", "le_modele_data_vault_est_independant_de_la_plateforme_si_une_mig": "The Data Vault model is platform-independent. If a migration is decided, the model follows without rewriting.", "le_modele_data_vault_est_reconstruit_dans_metavault_les_regles_m": "The Data Vault model is rebuilt in metaVault; existing business rules serve as the reference for the marts. The repetitive load code no longer needs to be maintained.", "le_modele_en_etoile_reste_excellent_pour_ce_pour_quoi_il_a_ete_c": "The star schema remains excellent for what it was designed for: analytical reporting. It becomes costly as soon as it is also asked to serve as the historized integration layer. Any change in granularity or dimension requires reprocessing, often destructively.", "le_modele_est_portable_le_sql_sera_regenere_pour_la_nouvelle_pla": "The model is portable. The SQL will be regenerated for the new target platform — beVault does it automatically.", "le_modele_est_pose_voyez_ce_qu_il_donne_sur_vos_propres_donnees": "The model is in place. See what it looks like on your own data.", "le_modele_est_un_artefact_de_code_pas_un_reglage_d_interface": "The model is a code artifact, not a UI setting", "le_modele_metier_avant_le_code": "The business model before the code", "le_modele_reste_identique_la_generation_est_refaite_pour_la_nouv": "The model stays the same: generation is redone for the new target, without redoing the modeling.", "le_moment_de_bascule_arrive_presque_toujours_au_meme_endroit_un_": "The tipping point almost always occurs in the same place: a figure is challenged in a meeting, no one knows how to reconstruct how it was produced, and the only person who knows the chain is on leave.", "le_nombre_d_environnements_n_est_pas_limite_par_le_produit_il_de": "The number of environments is not limited by the product: it depends on your organization and your target infrastructure.", "le_parallelisme_est_calcule_a_partir_du_graphe_de_dependances_le": "Parallelism is calculated from the dependency graph: warehouses run only for the necessary time, no longer.", "le_parcours": "The journey", "le_parcours_d_un_nouveau_partenaire": "A new partner's journey", "le_parcours_d_un_projet": "The path of a project", "le_perimetre_de_deploiement_n_est_pas_negociable": "The deployment perimeter is non-negotiable", "le_perimetre_est_adapte_a_votre_contexte_mais_ces_sujets_sont_sy": "The scope is adapted to your context, but these topics are systematically addressed.", "le_perimetre_est_clair_comparez_sur_un_cas_reel": "The scope is clear. Compare it on a real case.", "le_perimetre_exact_des_connexions_depend_de_votre_environnement_": "The exact scope of connections depends on your environment. It is defined source by source with our teams before implementation, rather than promised in advance.", "le_perimetre_s_etend": "The scope expands", "le_perimetre_s_etend_progressivement_risk_treasury_et_analytique": "The scope is expanding progressively: risk, treasury and customer analytics are being deployed on the same foundation.", "le_pl_sql_genere_est_il_lisible": "Is the generated PL/SQL readable?", "le_plan_d_execution_est_deduit_du_modele_et_execute_en_serverles": "The execution plan is derived from the model and run serverless on AWS Step Functions: no orchestration infrastructure to maintain.", "le_point_commun": "The common thread", "le_point_de_blocage_des_projets_ia_en_entreprise": "The blocking point for AI projects in enterprises", "le_point_de_depart": "The starting point", "le_point_de_jonction": "The junction point", "le_point_de_vue": "The perspective", "le_premier_deploiement_client_est_mene_conjointement_avec_transf": "The first customer deployment is carried out jointly, with a gradual handover to your teams.", "le_principe": "The principle", "le_principe_data_vault": "The Data Vault principle", "le_principe_est_simple_un_insight_produit_par_l_ia_est_un_evenem": "The principle is simple: an insight produced by AI is a business event. Treat it with the same rigor as your ERP or CRM data.", "le_probleme": "The problem", "le_probleme_de_duplication_silencieuse_dans_les_satellites_data_": "The silent duplication problem in Data Vault satellites", "le_probleme_du_retail_n_est_pas_le_volume_de_donnees_c_est_leur_": "Retail's problem isn't the volume of data, it's its movement: assortments that change every season, stores that open and close, revised product hierarchies, sources that don't talk to each other.", "le_probleme_n_est_pas_l_acces_a_la_donnee_la_plupart_des_organis": "The problem isn't data access: most organizations can technically read their systems. What's missing is a foundation where history is preserved, business concepts are named, quality is measured, and the origin of every value can be explained. Without this foundation, a model's results remain hard to defend before a committee.", "le_probleme_n_est_pas_seulement_technique_les_definitions_devien": "The problem isn't just technical: definitions become hard to trace, reporting logic becomes hard to maintain, and AI use cases end up without context or documentation on the data they consume.", "le_probleme_n_est_presque_jamais_l_outil_de_restitution": "The problem is almost never the reporting tool", "le_probleme_c_est_de_les_reunir": "The problem is bringing them together.", "le_programme_est_clair_deposez_votre_candidature": "The program is clear. Submit your application.", "le_programme_partenaire_bevault_n_est_pas_un_annuaire_de_logos_i": "The beVault Partner Program isn't a directory of logos. It structures how your consultants build expertise, how the first projects are supported, and how opportunities are registered and tracked.", "le_programme_vous_interesse_envoyez_votre_candidature": "Interested in the program? Send us your application.", "le_rattachement_d_un_client_repris_a_son_portefeuille_d_origine": "Linking a transferred customer back to their original portfolio.", "le_raw_vault_conserve_la_donnee_telle_qu_elle_est_arrivee_meme_m": "The Raw Vault keeps the data exactly as it arrived, even if it's wrong. That's what lets you, two years later, reconstruct what the source system stated at the time — and prove the correction happened downstream, in a documented, versioned rule.", "le_raw_vault_est_genere_avec_le_sql_adapte_aux_specificites_db2_": "The Raw Vault is generated with SQL tailored to Db2's specifics — with no extra abstraction layer.", "le_raw_vault_est_genere_avec_les_structures_data_vault_2_0_corre": "The Raw Vault is generated with correct Data Vault 2.0 structures — hubs, links, satellites — in native SQL Server T-SQL.", "le_raw_vault_est_genere_avec_pl_sql_adapte_aux_specificites_orac": "The Raw Vault is generated with PL/SQL adapted to Oracle specifics. No generic layer, no degraded performance.", "le_raw_vault_est_modelise_dans_bevault_et_le_sql_postgresql_est_": "The Raw Vault is modeled in beVault and PostgreSQL SQL is automatically generated — hubs, links, satellites with correct DV 2.1 structures.", "le_raw_vault_ne_doit_jamais_alterer_la_donnee_recue_les_regles_m": "The Raw Vault must never alter the data it receives. Business rules belong to the interpretation layers, which guarantees that an external audit can trace back to the source.", "le_raw_vault_recoit_les_donnees_telles_que_la_source_les_delivre": "The Raw Vault receives data exactly as delivered by the source, with no business transformation. This is what makes auditing possible: you can always demonstrate what the source system sent, and when.", "le_referentiel_qui_fait_autorite_pour_une_donnee_donnee_en_son_a": "The reference that has authority over a given piece of data. Without it, every team produces its own figures and no one can arbitrate.", "le_reste_de_la_plateforme_reste_accessible_depuis_le_menu_ces_tr": "The rest of the platform remains accessible from the menu: these three pages are the ones that directly address public-sector constraints.", "le_satellite_tout_le_contexte_historise": "The satellite: all context, historized", "le_second_symptome_est_plus_discret_sans_historisation_un_rappor": "The second symptom is more subtle: without historization, a report rerun the following month no longer gives the same result, and it becomes impossible to say which one was correct. The third is lineage — when no one knows which source a column comes from, the debate over the figure becomes a matter of opinion.", "le_secteur_public_reste_notre_terrain_principal": "The public sector remains our core focus", "le_serveur_mcp_bevault_est_disponible_aujourd_hui_il_permet_a_vo": "The beVault MCP Server is available today. It lets your agents query the metamodel, trigger loads, and read lineage — with the same access controls as the rest of your organization.", "le_serveur_mcp_bevault_permet_aux_agents_ia_compatibles_mcp_d_in": "The beVault MCP Server allows MCP-compatible AI agents to interact with your data model within the permissions and controls you define.", "le_serveur_mcp_permet_certaines_interactions_configurees_avec_la": "The MCP Server allows certain configured interactions with the platform, within the defined scope.", "le_seul_indicateur_que_votre_direction_retiendra": "The only metric your management will remember:", "le_siege_et_le_responsable_de_magasin_regardent_le_meme_chiffre_": "Head office and the store manager look at the same sales figure, calculated once, comparable from one season to the next despite changes in assortment and network.", "le_socle_construit_avec_bevault_agrege_les_sources_publiques_et_": "The foundation built with beVault aggregates public and partner sources, applies quality controls upstream of restitution, and exposes a stable semantic layer to the platform's AI components.", "le_sql_genere_est_standard_si_vous_changez_d_infrastructure_le_m": "The generated SQL is standard. If you change infrastructure, the model follows without a rewrite.", "le_succes_de_cette_automatisation_depend_entierement_du_prompt_e": "The success of this automation depends entirely on prompt engineering. Your prompt must guide Claude to produce JSON that directly maps to the beVault column structure.", "le_suivi": "Follow-up", "le_symptome_une_plateforme_qui_ralentit_au_lieu_d_accelerer": "The symptom: a platform that slows down instead of speeding up", "le_systeme_de_management_de_la_securite_de_l_information_de_dfak": "", "le_systeme_de_management_de_la_securite_de_l_information_de_dfak_2": "", "le_t_sql_genere_est_il_lisible": "Is the generated T-SQL readable?", "le_tableau_ci_dessous_compare_le_perimetre_fonctionnel_typique_d": "The table below compares the typical functional scope of a certified generator with that of an integrated platform.", "le_temps_est_reaffecte": "Time is reallocated", "le_terrain_bouge_plus_vite_que_les_referentiels": "The field moves faster than reference systems", "le_trajet_est_toujours_le_meme_decrire_le_sens_metier_integrer_l": "The path is always the same: describe business meaning, integrate sources, control quality during loading, orchestrate processing, publish consumable views, then run it all in your target environment.", "le_transfert_n_est_pas_une_session_de_fin_de_projet_il_commence_": "Knowledge transfer isn't an end-of-project session: it starts as soon as the first domains are delivered, working side by side with your teams.", "le_vocabulaire_des_projets_data": "The vocabulary of data projects,", "le_vrai_frein_n_est_pas_le_modele_c_est_son_cout_de_mise_en_uvre": "The real obstacle is not the model, it's the cost of implementing it", "le_vrai_gain_n_est_pas_le_cout_c_est_la_reprise_de_credibilite": "The real gain isn't cost, it's regaining credibility", "le_vrai_perimetre": "The real scope", "les_agents_ia_ont_besoin_de_plus_qu_un_acces_aux_donnees_ils_doi": "AI agents need more than access to data. They need to understand what your business concepts mean, how they relate to each other and which information can be trusted.", "les_agents_terrain_et_la_direction_travaillent_sur_la_meme_donne": "Field agents and management work on the same data. Pricing policy decisions rely on verifiable figures, not estimates.", "les_analyses_techniques_peuvent_remonter_dans_le_temps_sans_reco": "Technical analyses can look back in time without manual reconstruction. Management reports and prudential reports start from the same historized data, with the link preserved back to the source.", "les_anomalies_sont_detectees_dans_les_resultats_des_modeles_pas_": "Anomalies are detected in model results, not at the source. The cost of correction is maximal.", "les_anomalies_sont_remontees_dans_des_listes_exploitables_qualif": "Anomalies are reported in actionable lists, qualified and assigned to the relevant owner.", "les_audits_oracle_sont_imprevisibles_reduire_l_empreinte_fonctio": "Oracle audits are unpredictable. Reducing the functional footprint in the database mechanically reduces exposure.", "les_causes_habituelles": "Common causes", "les_champs_de_la_source_sont_rattaches_aux_entites_et_attributs_": "Source fields are linked to the entities and attributes described in metaVault. The mapping is metadata: readable, reviewed and versioned.", "les_champs_sources_sont_rattaches_aux_concepts_et_attributs_meti": "Source fields are mapped to the business concepts and attributes defined in beVault. Because the mapping is stored as metadata, it can be reviewed, versioned and propagated to the generated processes instead of being scattered across undocumented code.", "les_changements_sont_conserves_dans_le_temps_plutot_qu_ecrases_v": "Changes are kept over time rather than overwritten. You can reconstruct the state of a piece of data at a given date and explain a discrepancy.", "les_chargements_de_donnees_de_la_plateforme_ordre_dependances_en": "The platform's data loads: order, dependencies between jobs, execution conditions and lifecycle.", "les_chargements_s_executent_selon_le_graphe_de_dependances_du_mo": "Loads run according to the model's dependency graph: error recovery, parallelism and monitoring included. AWS Step Functions is supported as an external orchestrator.", "les_chargements_sont_orchestres_par_bevault_a_partir_du_graphe_d": "Loads are orchestrated by beVault from the dependency graph. No external scheduler to maintain in your GCP environment.", "les_chargements_sont_orchestres_par_bevault_a_partir_du_graphe_d_2": "Loads are orchestrated by beVault from the dependency graph. No external scheduler required.", "les_chartes_de_gouvernance_decrivent_un_ideal_que_rien_dans_la_c": "Governance charters describe an ideal that nothing in the technical chain makes mandatory. Governance becomes effective the day the rules run on the data process — at every load, without depending on everyone's goodwill.", "les_chiffres_du_jour_le_matin": "Today's figures, in the morning", "les_cinq_composants_critiques": "The five critical components:", "les_codes_divergents_des_differents_systemes_sont_rattaches_a_un": "Divergent codes from different systems are linked to a single Business Key, without rewriting the source reference systems.", "les_comparaisons_entre_periodes_tiennent_compte_des_changements_": "Period-to-period comparisons account for changes in scope and subsequent corrections.", "les_composants_bevault_et_votre_environnement": "beVault components and your environment", "les_composants_d_execution_ils_executent_les_workflows_definis_d": "The execution components. They run the workflows defined in States, apply the generated code and perform the loads into the target database.", "les_composants_s_installent_dans_l_environnement_que_vous_avez_c": "Components are installed in the environment you choose — on-premises, cloud, PaaS or hybrid — with Docker as the deployment technology.", "les_consequences_se_voient_ailleurs_volumes_qui_explosent_requet": "The consequences show up elsewhere: volumes explode, history queries slow down, and above all metrics like “number of address changes” or “time between status changes” become wrong without anyone knowing why.", "les_consolidations_manuelles_diminuent_parce_que_la_logique_n_es": "Manual consolidations decrease because the logic is no longer redone in every report. And when a discrepancy appears, it can be traced back to its source instead of remaining an open question.", "les_controles_de_qualite_s_appliquent_aux_donnees_historisees_et": "Quality controls apply to historical data and report anomalies in actionable lists.", "les_controles_qualite_sont_integres_au_chargement_coherence_et_f": "Quality controls are built into the loading process: consistency and freshness are checked continuously. Errors are caught before they reach reports.", "les_controles_s_executent_sur_des_donnees_historisees_et_multi_s": "Controls run on historized and multi-system data, at the source, domain, or load level.", "les_controles_sont_dans_la_plateforme_voyez_ce_que_ca_libere_cot": "Controls are within the platform. See what that frees up in terms of deadlines.", "les_correspondances_entre_identifiants_de_systemes_differents_so": "Correspondences between identifiers from different systems are materialized through dedicated structures (same-as links), which are revisable and historized.", "les_couches_de_restitution_sont_decrites_dans_la_plateforme_au_m": "Reporting layers are described in the platform, in the same place as the model that feeds them.", "les_couches_se_multiplient_les_regles_de_promotion_ne_sont_pas_d": "Layers keep multiplying, promotion rules go undocumented, and no one knows which Silver table is authoritative for which use case.", "les_criteres_qui_decident": "the criteria that decide.", "les_criteres_sont_verifiables_en_demonstration": "The criteria can be verified in a demo", "les_criteres_point_par_point": "The criteria, point by point", "les_data_stewards_corrigent_les_donnees_dans_les_systemes_source": "Data stewards correct data in the source systems where the error was introduced.", "les_decisions_a_eclairer_les_cas_d_usage_a_servir_les_obligation": "The decisions to inform, the use cases to serve, regulatory obligations, deadlines and budget constraints.", "les_decisions_a_prendre_avant_de_lancer_un_projet_data_gouvernan": "Decisions to make before launching a data project — governance, ownership, initial scope.", "les_decisions_qui_suivent_le_choix_des_modules": "The decisions that follow choosing the modules", "les_dependances_de_chargement_sont_deduites_du_modele_et_execute": "Load dependencies are derived from the model and executed natively. There's no external scheduler to install, secure and maintain.", "les_dependances_de_chargement_sont_reecrites_a_la_main_a_chaque_": "Loading dependencies are rewritten manually. With each model evolution, they must be updated — and an oversight leads to an inconsistent silent load.", "les_deploiements_les_plus_rapides_partent_d_un_perimetre_metier_": "The fastest deployments start from a business scope that's already modeled and a question whose answer is currently costly to produce manually. Value shows up in weeks, not quarters.", "les_derniers_domaines_sont_construits_par_vos_equipes_avec_notre": "The final domains are built by your teams, with our support, until they become self-sufficient.", "les_descriptions_saisies_lors_de_la_modelisation_alimentent_la_d": "Descriptions entered during modeling feed the documentation. It follows the model instead of drifting into a separate document, and goes all the way down to the column: definition, original source and role in the output consumed by BI or by an agent.", "les_deux_approches_sont_possibles_selon_la_volumetrie_la_frequen": "Both approaches are possible depending on data volume, access frequency and the target environment. The choice is made when the mart is declared.", "les_deux_produits_proposent_une_modelisation_visuelle_du_data_va": "Both products offer visual Data Vault modeling and automate loading code generation. Demos often look similar. Differences appear later: in the depth of quality governance, how loads are orchestrated in production, and the deployment options truly available to you.", "les_deux_produits_reduisent_le_travail_manuel_la_question_est_de": "Both products reduce manual work. The question is what remains to be assembled around them once the first warehouse is delivered.", "les_deux_se_combinent_souvent_le_nouveau_systeme_porte_les_proce": "The two are often combined: the new system carries the processes, the platform carries the history. These are two distinct efforts that are best not confused.", "les_donnees_citoyennes_ou_administratives_ne_peuvent_pas_toujour": "Citizen or administrative data cannot always go through a shared service. beVault deploys on-premises, in your cloud or hybrid, with no loss of functionality.", "les_donnees_de_fidelite_sont_rattachees_aux_ventes_sans_imposer_": "Loyalty data is linked to sales without imposing a single reference system on operational systems.", "les_donnees_et_les_structures_produites_restent_dans_l_environne": "The data and the structures produced stay within the environment defined with you. Deployment, operations and evolution conditions are scoped from the start.", "les_donnees_existent_ce_qui_manque_c_est_un_endroit_ou_elles_son": "The data exists. What's missing is a place where it's kept in its original state, dated, and linked to the rules that transform it. Without this, an audit or a parliamentary question turns into a multi-week internal investigation.", "les_donnees_finissent_reparties_dans_plusieurs_outils_erp_crm_fa": "Data ends up spread across several tools — ERP, CRM, invoicing, business files — and indicators are rebuilt by hand at every deadline. A customer, a contract or an order is not counted the same way from one team to the next, and operational systems overwrite past states: reconstructing a situation at a given date becomes difficult.", "les_donnees_historisees_conservent_le_contexte_des_sources_et_le": "Historized data preserves source context and changes over time, making information traceable and auditable.", "les_donnees_industrielles_ne_manquent_pas_elles_sont_enfermees_d": "Industrial data isn't lacking. It's locked away in systems that share neither the same keys, nor the same clocks, nor the same lifespan.", "les_donnees_passent_d_excel_a_un_data_vault_les_definitions_sont": "Data moves from Excel to a Data Vault. Definitions are shared between departments — a single version of the truth.", "les_donnees_preparees_sont_mises_a_disposition_des_outils_de_res": "Prepared data is made available to the reporting tools and consuming systems in your environment.", "les_donnees_reprises_restent_interrogeables_par_les_sorties_cons": "Migrated data remains queryable through outputs built for that purpose, without restarting the original application. Lineage and documentation explain where a piece of information comes from and how it was transformed.", "les_donnees_sensibles_peuvent_etre_isolees_dans_des_structures_d": "Sensitive data can be isolated in dedicated structures, making targeted deletion possible without breaking the consistency of the business history. The exact scope is defined with your teams.", "les_donnees_sont_conservees_telles_qu_elles_ont_ete_recues_sans_": "Data is kept as received, without overwriting history. Each load keeps track of its origin and date, allowing the raw model to be reused for new needs and a source to be reconstructed as it was at a given time. You thus have a reliable basis for analysis, auditing, and compliance.", "les_donnees_sont_extraites_et_historisees_de_facon_incrementale_": "Data is extracted and historized incrementally. Production systems continue to run normally.", "les_donnees_sont_historisees_au_lieu_d_etre_ecrasees_sans_trace_": "Data is historized instead of silently overwritten. Source context and changes are preserved, making it easier to explain where information came from and how it changed over time.", "les_donnees_sont_sur_aws_mais_l_orchestration_tourne_sur_un_sche": "The data sits on AWS but orchestration runs on an external scheduler. No one guarantees consistency.", "les_elements_cles_definition_de_role_claire_instruction_de_forma": "Key elements: clear role definition, explicit format instruction, schema definition, few-shot examples including edge cases, repeated constraints on output format.", "les_elements_de_preuve_historique_des_regles_journaux_de_chargem": "Evidence — rule history, load logs, lineage — is produced by the platform and available whenever a review requires it.", "les_elements_listes_sont_indicatifs_et_precises_lors_de_la_quali": "Listed items are indicative and refined during project qualification.", "les_enregistrements_en_ecart_ne_sont_pas_silencieusement_ecartes": "Records with discrepancies aren't silently discarded: they're flagged as exceptions and routed to the owner of the relevant domain, with the context needed to decide. Data Vault historization preserves the original state, and lineage allows tracing back from an output to the fields that fed it.", "les_entites_et_relations_sont_nommees_avec_les_concepts_de_l_org": "Entities and relationships are named using the organization's own concepts, and documented in the metamodel rather than guessed from column names.", "les_entreprises_gerent_des_volumes_considerables_de_donnees_non_": "Companies manage considerable volumes of unstructured data — PDFs, images, audio recordings, text documents. The Data Vault traditionally stores their metadata and references in the object store.", "les_environnements_db2_sont_souvent_soumis_aux_controles_les_plu": "DB2 environments are often subject to the strictest controls. Traceability must be mechanical, not documentary.", "les_environnements_de_donnees_changent_sans_cesse_les_sources_so": "Data environments change constantly. Sources are replaced, business definitions evolve and new use cases appear over time. Data Vault provides a structured way to integrate and historize this changing information without losing its origin or rebuilding the entire foundation each time.", "les_environnements_sont_cadres_voyez_ou_la_plateforme_peut_tourn": "Environments are well defined. See where the platform can run.", "les_equipes_data_mesurent_l_impact_d_un_changement_avant_de_le_f": "Data teams measure the impact of a change before making it, business teams check a definition without opening a ticket, and control functions handle audit requests based on the same metadata. Vocabulary becomes shared because it exists in only one place.", "les_equipes_data_pour_comprendre_l_impact_d_un_changement_les_me": "Data teams to understand the impact of a change, business teams to check a definition, and control functions to handle an audit request.", "les_equipes_dfakto_interviennent_aux_cotes_des_votres_cadrage_et": "dFakto teams work alongside yours: scoping and assessment, architecture, implementation, training and knowledge transfer, then ongoing support and evolution.", "les_equipes_dfakto_interviennent_aux_cotes_des_votres_du_cadrage": "dFakto teams work alongside yours, from scoping through to knowledge transfer.", "les_equipes_qui_livrent": "the teams that deliver.", "les_equipes_risque_finance_et_direction_generale_travaillent_sur": "Risk, finance and executive management teams work on the same historized facts. Any remaining discrepancies are definitional, visible and can be arbitrated, rather than unexplained source discrepancies.", "les_equipes_techniques_definissent_les_controles_techniques_les_": "Technical teams define technical controls, business teams contribute functional rules, according to the governance model actually in place in your organization.", "les_equipes_travaillent_sur_l_analyse_pas_sur_la_reconciliation_": "Teams work on analysis, not reconciliation. The time freed up is redirected to business value.", "les_etats_d_exploitation_et_les_etats_transmis_partent_des_memes": "Operational reports and submitted reports start from the same dated facts, and any gap between two publications can be explained.", "les_etats_successifs_des_donnees_sont_conserves_et_horodates_une": "Successive states of the data are kept and timestamped. A retrospective analysis relies on the actual state as of the relevant date, not on today's state.", "les_etats_successifs_et_le_chemin_des_donnees_restent_disponible": "The successive states and the data's path remain available, making it possible to reconstruct a past situation and explain a published figure.", "les_etats_successifs_sont_conserves_et_dates_donc_une_analyse_pe": "Successive states are kept and dated, so an analysis can be reconstructed as at its date. Declared rules are evaluated at each load, so quality remains measurable. Entities carry the organisation's own names and are documented in the metamodel, so business context is not lost.", "les_etats_successifs_sont_conserves_plutot_qu_ecrases_les_charge": "Successive states are preserved rather than overwritten: later loads add, they don't replace.", "les_exigences_de_la_charte_deviennent_des_regles_declarees_appli": "The charter's requirements become declared rules, enforced at every load rather than checked during an annual review.", "les_fonctionnalites_sont_claires_voyez_ce_qu_elles_donnent_sur_v": "The features are clear. See what they deliver for your case.", "les_fonctions_de_securite_de_snowflake_sont_excellentes_mais_ell": "Snowflake's security functions are excellent, but they say nothing about the meaning of data or its quality.", "les_formulaires_existent_ils_en_anglais": "Are the forms available in English?", "les_hash_keys_rendent_les_chargements_parallelisables_et_indepen": "Hash keys make loads parallelizable and independent of lookups. They only add value if the normalization applied before hashing is strictly identical everywhere: case, spacing, separators, null values.", "les_indicateurs_sont_documentes_et_rattaches_a_leur_source_ce_qu": "Indicators are documented and linked to their source, making it possible to explain a published figure rather than recalculate it on demand. Deployment can stay within your perimeter when your organization's framework requires it.", "les_indicateurs_sont_recalcules_depuis_le_data_vault_et_compares": "The metrics are recalculated from the Data Vault and compared figure by figure with the old system before any cutover.", "les_indicateurs_sont_recalcules_depuis_le_vault_et_compares_a_ce": "Metrics are recalculated from the vault and compared against those from the old system. Discrepancies are explained and settled with the business before any cutover.", "les_indicateurs_sont_recalcules_depuis_le_vault_et_compares_a_ce_2": "Metrics are recalculated from the vault and compared against those from the legacy environment. Discrepancies are made visible and explained, never hidden.", "les_information_marts_sont_produits_dans_la_base_cible_documente": "Information Marts are produced in the target database, documented and ready to be consumed.", "les_information_marts_sont_produits_dans_la_base_de_donnees_cibl": "Information Marts are produced in the target database. They can be consumed by applications, BI tools, and AI agents within the scope configured for these consumers.", "les_informations_qui_decrivent_les_donnees_structure_origine_def": "The information that describes the data: structure, origin, definition, applied rules. This is what makes it possible to generate the processing and produce the documentation.", "les_jeux_de_donnees_mis_a_disposition": "The datasets made available", "les_licences_continuent_les_competences_s_en_vont_et_quelques_fo": "Licenses keep running, expertise leaves, and a few times a year an audit or a dispute forces someone to dig up information from a system that no one uses day-to-day anymore.", "les_limites_de_cette_approche": "The limits of this approach", "les_livrables": "The deliverables", "les_managers_voient_les_chiffres_du_jour_le_matin_pas_deux_semai": "Managers see the day's figures in the morning — not two weeks later. Menu and staffing decisions can be adjusted in real time.", "les_marts_alimentent_les_outils_de_bi_les_applications_et_dans_l": "The marts feed BI tools, applications and, within the approved scope, agents via beVault's API and MCP Server.", "les_marts_exposent_des_indicateurs_dont_la_definition_et_le_lign": "Marts expose indicators whose definition and lineage are derived from the model, not described in a separate document.", "les_marts_peuvent_ils_servir_des_applications_et_des_agents_ia_p": "Can marts serve applications and AI agents, not just BI?", "les_marts_rendent_la_donnee_utilisable": "Marts make data usable.", "les_marts_sont_construits_avec_lignage_complet_indicateurs_de_qu": "Marts are built with full lineage, quality indicators, and traceability for regulatory audits.", "les_marts_sont_generes_avec_lignage_complet_vos_data_scientists_": "Marts are generated with full lineage. Your data scientists access versioned and documented datasets.", "les_marts_sont_ils_materialises_ou_virtuels": "Are marts materialized or virtual?", "les_memes_controles_finissent_reecrits_dans_l_etl_dans_l_outil_q": "The same checks end up rewritten in the ETL, in the quality tool and in the reports — with three different results.", "les_memes_controles_sont_rejoues_pour_verifier_que_la_correction": "The same controls are replayed to verify that the correction produced the expected effect.", "les_memes_donnees_fiables_peuvent_alimenter_agents_ia_bases_vect": "The same trusted data can feed AI agents, vector databases, BI dashboards, information marts and business applications. If you change your AI agent, LLM or vector database, your underlying business model and data foundation remain reusable.", "les_memes_donnees_servent_au_pilotage_quotidien_de_l_exploitatio": "The same data supports day-to-day operational steering and the reports requested by the supervisory authority.", "les_memes_fondations": "The same foundations,", "les_mesures_conservees_dans_le_temps_montrent_une_tendance_la_qu": "Measures kept over time show a trend: quality is managed as an indicator, not an incident.", "les_modules": "The modules", "les_modules_ne_s_echangent_pas_des_fichiers_ils_lisent_et_ecrive": "Modules don't exchange files: they read and write the same metamodel. A change made in modeling is immediately known to orchestration, documentation and lineage.", "les_niveaux_du_programme_l_enablement_technique_et_commercial_et": "The program's tiers, technical and commercial enablement, and how projects are run jointly.", "les_niveaux_et_mouvements_sont_conserves_a_leur_date_ce_qui_rend": "Levels and movements are kept at their original date, making breaks analyzable after the fact.", "les_nouvelles_couches_de_consommation_sont_publiees_sous_forme_d": "New consumption layers are published as documented Information Marts, fed from the vault and refreshed by the built-in orchestration. Every rebuilt indicator can be compared figure by figure with its original version.", "les_organisations_investissent_des_budgets_considerables_en_ia_p": "Organizations are investing considerable budgets in AI. Yet most initiatives never make it to production. The culprit isn't the model — it's the data underneath.", "les_organisations_ne_manquent_pas_de_cas_d_usage_ia_elles_butent": "Organizations aren't short of AI use cases. They stumble on a prior question: what data is the agent answering from, and who guarantees that data?", "les_organisations_publiques_travaillent_avec_des_applications_me": "Public organizations work with legacy business applications, file exports, and databases whose documentation was lost along with the teams that built them.", "les_organisations_qui_repondent_aux_criteres_europeens_de_la_pme": "Organisations that meet the European SME criteria can benefit from conditions adapted to their size, their scope and their deployment journey.", "les_organisations_qui_repondent_aux_criteres_europeens_de_la_pme_2": "Organisations that meet the European SME criteria may benefit from conditions adapted to their size, scope and deployment journey. These conditions may cover the platform, implementation services and the way the project starts.", "les_organisations_qui_repondent_aux_criteres_europeens_de_la_pme_3": "Organisations that meet the European SME criteria may be eligible for conditions adapted to their size, scope and deployment journey. Eligibility is discussed during the qualification process.", "les_patterns_de_chargement_d_un_hub_d_un_link_ou_d_un_satellite_": "The loading patterns for a hub, a link or a satellite are identical regardless of the business domain. What varies is the mapping; what repeats is the code — 90% of the time.", "les_plateformes_cibles_disponibles_ou_a_venir": "Target platforms, available or coming soon", "les_plateformes_supportees_une_par_une": "Supported platforms, one by one", "les_pme_beneficient_elles_de_conditions_specifiques": "Do SMEs have specific conditions?", "les_pme_doivent_souvent_structurer_leurs_donnees_avec_des_source": "SMEs often need to structure their data with multiple sources, small teams and rapidly evolving needs. beVault helps build a reliable foundation, improve Data Quality and prepare for analytical and AI use cases without losing control of the environment.", "les_points_ou_l_autre_outil_est_pertinent_sont_indiques": "The points where the other tool is relevant are indicated", "les_points_sensibles": "The sensitive points", "les_premiers_mois_d_un_projet_data_sont_trompeusement_rapides_de": "The first months of a data project are deceptively fast. Two or three sources, a few tables, a dashboard: everyone is happy. The problem appears with the next source, then with historical data reload, then with the first change to a source system. What used to take a week now takes six.", "les_problemes_de_qualite_se_revelent_le_plus_souvent_en_aval_un_": "Quality issues most often surface downstream: a report is published, an indicator circulates, and the discrepancy only appears afterward. By then, the decision has already been made on the wrong figure.", "les_procedures_stockees_existantes_sont_elles_migrees": "Are existing stored procedures migrated?", "les_quatre_ecarts_structurants": "The four structural differences", "les_quatre_ecueils_d_un_bigquery_sans_structure": "The four pitfalls of an unstructured BigQuery", "les_quatre_ecueils_d_un_redshift_sans_modele": "The four pitfalls of a Redshift without a model", "les_quatre_ecueils_d_un_snowflake_sans_modele": "The four pitfalls of a Snowflake without a model", "les_quatre_exigences": "The Four Requirements", "les_quatre_foyers_de_derive": "The Four Drift Hotbeds", "les_quatre_questions_a_poser_a_chaque_editeur_certifie": "The Four Questions to Ask Every Certified Vendor", "les_quatre_signaux_d_un_sql_server_a_bout_de_souffle": "Four signs that a SQL Server is running out of steam", "les_questions_auxquelles_il_faut_pouvoir_repondre": "The questions you need to be able to answer", "les_rapports_pointent_directement_sur_les_tables_transactionnell": "Reports point directly to transactional tables. The slightest schema change breaks analytical production.", "les_rapports_pointent_vers_les_nouveaux_marts_une_fois_la_reconc": "Reports point to the new marts once reconciliation is accepted, the old pipeline stays available as a fallback for the agreed time, and the team moves on to the next domain.", "les_rapports_sont_reconstruits_depuis_le_data_vault_les_tables_o": "Reports are rebuilt from the Data Vault. Source Oracle tables remain intact — dependency is mechanically reduced.", "les_regles_appliquees_sont_versionnees_avec_le_modele_et_leur_li": "Applied rules are versioned with the model, and their lineage is derived from it.", "les_regles_de_qualite_declarees_s_appliquent_a_chaque_chargement": "Declared quality rules apply to every load: a partial load no longer produces a plausible but incorrect figure without anyone noticing.", "les_regles_de_qualite_sont_declarees_dans_le_processus_de_charge": "Quality rules are declared in the loading process and measured continuously, source by source, with exception management.", "les_regles_de_qualite_sont_versionnees_avec_le_modele_et_evaluee": "Quality rules are versioned with the model and evaluated during loading, instead of being checked afterward by a separate tool.", "les_regles_de_qualite_vivent_dans_la_plateforme_et_s_appliquent_": "Quality rules live in the platform and apply at load time. Discrepancies are tracked, versioned and attributable to a source, rather than discovered a month later in a dashboard.", "les_regles_declarees_sont_appliquees_et_mesurees_a_chaque_charge": "Declared rules are applied and measured at every load, and exceptions are visible rather than silent.", "les_regles_metier_et_techniques_evoluent_avec_le_modele_on_sait_": "Business and technical rules evolve with the model. You know exactly which version applied on the date of a calculation.", "les_regles_metier_sont_declarees_dans_la_plateforme_et_deviennen": "Business rules are declared in the platform and become technical controls applied at every load: completeness, format, cross-source consistency, expected cardinalities. Their results are measured, kept, and comparable over time.", "les_regles_s_executent_pendant_le_chargement_avec_quarantaine_et": "Rules run during loading, with quarantine and a score per dataset — rather than a check after the fact in a separate tool.", "les_resultats_dependent_de_votre_point_de_depart_nombre_de_sourc": "Results depend on your starting point: number of sources, state of the existing model, team maturity. This is exactly what we look at together during a demo tailored to your context.", "les_roles_sont_clairs_voyez_le_code_genere_sur_votre_moteur": "Roles are clear. See the code generated on your engine.", "les_satellites_accrochent_le_descriptif_a_un_hub_ou_a_un_link_no": "Satellites attach descriptive data to a hub or a link: name, address, status, amounts, business dates. Each change creates a new timestamped row instead of overwriting the previous one.", "les_series_issues_de_systemes_de_comptage_differents_sont_rattac": "Series from different metering systems are linked to the same delivery points.", "les_sites_industriels_vivent_avec_des_contraintes_reseau_et_des_": "Industrial sites operate under network constraints and in sensitive environments. Deployment can remain on-premises, within your own infrastructure.", "les_sorties_prennent_la_forme_d_information_marts_definis_pour_u": "Outputs take the form of Information Marts defined for a specific use, rather than raw access to the warehouse. What an agent can query depends on the products exposed, the permissions and the configuration chosen — so AI use cases open up progressively, as the foundation consolidates.", "les_sources_concernees_sont_integrees_et_historisees_telles_quel": "The relevant sources are integrated and historized as-is, without immediately disrupting existing reporting, which keeps running on the old pipeline.", "les_sources_critiques_sont_integrees_dans_un_data_vault_historis": "Critical sources are integrated into a Data Vault, historized, and qualified. This is the only truly structural step.", "les_sources_du_domaine_entrent_dans_le_raw_vault_historisees_et_": "The domain's sources enter the Raw Vault, historized and subjected to the declared quality rules. The existing environment isn't altered.", "les_sources_restent_vos_systemes_applications_metier_et_fichiers": "The sources remain your systems: business applications and files present in your application landscape. Workers read the data there, drop it into staging, then apply the loads to the target database you've chosen.", "les_sources_sont_chargees_avec_detection_des_changements_pas_de_": "Sources are loaded with change detection. No full reloads, no temporary work tables.", "les_sources_sont_chargees_en_incremental_avec_detection_des_chan": "Sources are loaded incrementally, with change detection. No more full reloads that consume credits for nothing.", "les_sources_sont_chargees_et_historisees_dans_le_data_vault_sans": "Sources are loaded and historized in the Data Vault with no business transformation. Definitions — revenue, active customer, margin — are implemented in the Information Marts, where they are documented and tracked over time. Legitimate variants become explicit views, not unexplained discrepancies.", "les_sources_sont_integrees_telles_quelles_dans_un_raw_vault_hist": "Sources are integrated as-is into a historized Raw Vault. Nothing is transformed at load time, so nothing is lost — business rules are applied later, in the Information Marts, where they remain readable and editable.", "les_specialistes_db2_sont_precieux_bevault_automatise_le_code_de": "DB2 specialists are valuable. beVault automates loading code so their skills can focus on business value.", "les_structures_data_vault_sont_generees_directement_sur_delta_la": "Data Vault structures are generated directly on Delta Lake. The Bronze layer remains intact as a raw source of truth.", "les_structures_generees_et_les_chargements_s_appliquent_a_la_bas": "Generated structures and loads apply to the target database you've chosen. beVault doesn't impose a platform on you: it produces code adapted to the one you already run.", "les_systemes_contributeurs_sont_charges_tels_quels_historises_et": "Source systems are loaded as-is, historized and subjected to controls. No business rule is applied at this stage.", "les_systemes_db2_accumulent_souvent_des_decennies_de_donnees_tra": "Db2 systems often accumulate decades of transactional data. That depth is an asset — provided you can leverage it.", "les_systemes_de_gestion_font_leur_travail_ils_gerent_l_etat_cour": "Operational systems do their job — they manage the current state. What they don't do is preserve the succession of states: an amendment replaces the previous version, a provision is revalued, a product reference is renamed.", "les_systemes_herites_restent_en_production": "Legacy systems remain in production", "les_systemes_qui_portent_vos_processus_gestion_finance_rh_produc": "The systems that run your processes — operations, finance, HR, production — were never designed to be read together. Alongside them are old relational databases still in production, flat files dropped regularly, and a few APIs exposed by the most recent applications.", "les_systemes_retenus_pour_le_cas_d_usage_sont_charges_dans_le_ra": "The systems selected for the use case are loaded into the Raw Vault, as-is, with their origin and load date.", "les_systemes_sources_sont_connectes_et_mappes_sur_le_modele_puis": "Source systems are connected and mapped to the model, then loaded while preserving the history of what was received.", "les_tables_sont_mises_a_jour_en_place_reconstituer_l_etat_des_do": "Tables are updated in place. Reconstructing the state of the data six months ago has become a project in its own right.", "les_tarifs_sont_ils_publics": "Is pricing public?", "les_termes_qui_reviennent": "The recurring terms", "les_tests_dbt_verifient_des_hypotheses_techniques_bevault_ajoute": "dbt tests verify technical assumptions. beVault adds per-source scoring, exception management and master data reconciliation.", "les_trois_niveaux_correspondent_a_des_perimetres_et_des_contexte": "The three levels represent different scopes and project contexts. The right option depends on your sources, domains, teams, deployment environment and support needs.", "les_trois_pages_qui_comptent_ici": "The three pages that matter here", "les_trois_problemes_qui_tuent_les_initiatives_ia": "The Three Problems Killing AI Initiatives", "les_trois_questions_a_poser_avant_de_figer_une_cle": "The Three Questions to Ask Before Freezing a Key", "les_usages_qui_justifient_l_investissement_reporting_conformite_": "The use cases that justify the investment: reporting, compliance, AI readiness, replacing an end-of-life system.", "les_utilisateurs_travaillent_dans_metavault_et_states_les_worker": "Users work in metaVault and States; Workers execute processing, read sources, and load your infrastructure's target database, which then feeds your outputs.", "les_valeurs_d_origine_restent_conservees_et_datees_une_correspon": "Original values remain kept and dated. A mapping revised later doesn't erase what was observed before.", "les_valeurs_de_chaque_systeme_restent_stockees_telles_quelles_da": "Values from each system remain stored as-is, dated and linked to their origin. Nothing is overwritten in favor of a single version.", "les_workflows_complexes_peuvent_etre_decoupes_en_machines_a_etat": "Complex workflows can be broken down into smaller, more manageable state machines.", "les_workflows_d_extraction_recuperent_les_donnees_selon_la_frequ": "Extraction workflows retrieve data at the chosen frequency, fully or by delta, with execution tracking.", "leur_rapport_a_la_donnee": "the way they work with data.", "liberez_les_sans_tout_reconstruire": "Free it up without rebuilding everything.", "licence_additionnelle_requise": "Additional License Required", "licence_et_mise_en_uvre_comparees_aux_economies_annuelles_le_cro": "License and implementation compared to annual savings. The crossover generally occurs between the fourth and eighth month.", "lignage_documentation": "Lineage & Documentation", "lignage_du_champ_source_jusqu_au_jeu_d_entrainement": "Lineage from the source field through to the training set", "lignage_du_champ_source_jusqu_au_mart_sans_rupture": "Lineage from the source field all the way to the mart, with no gaps", "lignage_et_documentation": "Lineage and documentation", "lignage_et_documentation_derives_du_modele_mis_a_jour_avec_lui": "Lineage and documentation derived from the model, updated along with it.", "lignage_garanti": "Guaranteed Lineage", "lignage_verifiable_du_champ_source_au_jeu_d_entrainement": "Verifiable lineage from source field to training dataset", "limitee_aux_tables_observees": "Limited to Observed Tables", "lire": "Read", "lire_l_article": "Read the article →", "lire_le_blog": "Read the blog", "lire_le_business_case": "Read the business case →", "lire_le_cas": "Read the case study", "lire_le_cas_complet": "Read the full case study", "lire_le_comparatif": "Read the comparison", "lire_les_articles": "Read the articles", "lire_les_metadonnees_d_un_systeme_source": "Read metadata from a source system.", "livrer_du_data_vault_2_0": "Delivering Data Vault 2.0", "livrer_du_data_vault_2_0_a_deux_integrateurs_conseils_et_editeur": "Delivering Data Vault 2.0 together: integrators, consultancies and software vendors.", "livres_aux_equipes_ops_et_finance": "delivered to ops and finance teams", "load_date_et_record_source_tracabilite_native_de_chaque_enregist": "Load date and record source: native traceability of each record.", "logique_metier_enfouie_dans_la_base": "Business Logic Buried in the Database", "logo_logo_name": "Logo ${logo.name}", "logo_name": "Logo ${name}", "logo_p_name": "Logo ${p.name}", "logo_partner_name": "Logo ${partner.name}", "logo_de_la_brasserie_witloof_brasserie_artisanale_bruxelloise": "Witloof Brewery Logo, artisan brewery in Brussels", "logos_precedents": "Previous logos", "logos_suivants": "Next logos", "loic": "Loïc", "lors_du_cadrage_avec_vos_equipes_d_exploitation_c_est_une_decisi": "During scoping, with your operations teams. It's as much an organizational decision as a technical one.", "magasins_et_points_de_vente": "Stores and points of sale", "maintenance_d_infrastructure": "Infrastructure maintenance", "maintenir_airflow_correctement_demande_un_profil_plateforme_ce_p": "Maintaining Airflow correctly requires a platform profile. This profile is expensive, hard to recruit, and their departure creates an immediate operational risk.", "maintenir_le_contexte_historique": "Maintaining historical context", "maitrise_des_couts_de_calcul": "Compute cost control", "management_de_la_donnee_batir_un_socle_solide": "Data Management: Building a Solid Foundation", "managing_director_dfakto": "Managing Director, dFakto", "mapping": "Mapping", "marts_et_gouvernance_lisibles": "Readable marts and governance", "marts_gouvernes": "Governed marts", "marts_gouvernes_exposes_directement_a_looker_studio_power_bi_ou_": "Governed marts exposed directly to Looker Studio, Power BI or Tableau", "marts_gouvernes_exposes_directement_a_power_bi_ou_tableau": "Governed marts exposed directly to Power BI or Tableau", "marts_gouvernes_exposes_directement_a_quicksight_power_bi_ou_tab": "Governed marts exposed directly to Quicksight, Power BI or Tableau", "marts_api_et_serveur_mcp_donnent_aux_equipes_data_science_et_aux": "Marts, APIs and the MCP Server give data science teams and agents governed access, with the same permissions as the rest of the organization.", "master_data_management": "Master Data Management", "maximilien": "Maximilien", "mdm_golden_records": "MDM / golden records", "mdm_integration": "MDM & integration", "mdm_integration_des_donnees": "MDM & Data Integration", "mdm_et_reconciliation": "MDM and reconciliation", "mdm_et_reconciliation_master_data": "MDM and master data reconciliation", "melanger_ces_trois_rythmes_dans_une_meme_table_c_est_accepter_qu": "Mixing these three paces in a single table means letting the most volatile one impose its rate of rework on the most stable one. The Data Vault separates them into three distinct object types.", "meme_contexte_meme_ambition_parlons_en": "Same context? Same ambition? Let's talk.", "mes_et_erp_alimentent_la_meme_base_de_faits_ce_qui_evite_d_arbit": "The MES and the ERP feed the same fact base, avoiding the need to arbitrate between two partial truths.", "mesurer": "Measure", "mesurer_la_qualite_et_les_exceptions": "Measure quality and exceptions", "mesures_avant_apres_sur_des_projets_en_production": "Before/after measurements on projects in production", "metadonnees": "Metadata", "metamodele_data_vault_natif_contre_macros_a_ecrire_et_maintenir": "Native Data Vault metamodel versus macros to write and maintain", "metamodele_data_vault_natif_certifie_dv_2_1": "Native Data Vault metamodel, DV 2.1 certified", "metamodele_versionne_dans_le_git_store": "Metamodel versioned in the Git Store", "metavault": "metaVault", "metavault_l_environnement_de_modelisation": "metaVault — the modelling environment", "metavault_modelisation_et_automatisation_data_vault": "metaVault — Data Vault modeling and automation", "metavault_states_et_workers_sont_des_composants_bevault_les_sour": "metaVault, States and Workers are beVault components. Sources, infrastructure, target databases and reporting tools remain external components that you continue to control.", "metavault_states_workers_environnements": "metaVault, States, Workers, environments", "methode": "Method", "methode_de_calcul_transparente_et_contestable": "Transparent and challengeable calculation method", "mettre_a_jour_le_catalogue_de_donnees_et_la_documentation_techni": "Update the data catalog and technical documentation.", "mettre_en_regard_deux_trimestres_en_tenant_compte_des_changement": "Compare two quarters while accounting for scope changes that occurred between them.", "microsoft_sql_server": "Microsoft SQL Server", "migration_modernisation": "Migration & modernization", "migration_cloud_sous_pression": "Cloud migration under pressure", "migration_d_entrepot": "Warehouse migration", "migration_d_un_entrepot_legacy_sans_arret_de_service": "Migrating a legacy warehouse without downtime", "migration_erp_legacy": "ERP & Legacy Migration", "migration_et_sortie_d_applications_historiques": "Migration and retirement of legacy applications", "migration_impossible_a_planifier": "Impossible to plan migration", "migrer_vers_redshift_resout_un_probleme_d_infrastructure_sans_di": "Migrating to Redshift solves an infrastructure problem. Without modelling discipline, the platform fills up with working schemas, stacked views and unoptimised queries, and the AWS bill rises while data reliability does not improve. beVault brings the structure: a Data Vault 2.0 architecture adapted to your environment, code generated with the right distribution settings, and beVault orchestration integrated into your AWS environment.", "migrer_vers_snowflake_resout_des_problemes_d_infrastructure_pas_": "Migrating to Snowflake solves infrastructure problems, not modelling problems. Without discipline, the platform quickly fills up with intermediate tables, stacked views and processes whose bill rises while confidence in the figures does not improve. beVault brings the structure: a Data Vault 2.0 architecture adapted to your environment, generated code optimised for Snowflake and orchestration that does not waste your credits.", "mise_en_uvre": "Implementation", "mise_en_uvre_transfert_de_competences_evolution": "Implementation, knowledge transfer, evolution", "mise_en_place_des_conteneurs_dans_votre_environnement_avec_vos_o": "Deployment of containers in your environment, using your usual deployment tools.", "mise_en_place_du_point_de_jonction_et_des_conditions_de_demarrag": "Setting up the junction point and the start conditions, with clear responsibility on each side.", "mise_en_production": "Go-live", "mise_en_production_exploitation_documentation_et_transfert_de_co": "Go-live, operations, documentation and knowledge transfer to your teams, followed by ongoing support.", "mise_en_service_initiale": "Initial go-live", "mobilite_services_urbains": "Mobility & urban services", "model_context_protocol_mcp_est_un_protocole_standardise_qui_defi": "Model Context Protocol (MCP) is a standardized protocol that defines how AI agents interact with external systems. In our context, it works as an API gateway that simplifies orchestration logic and provides business-language parameters.", "modele_comme_source_de_verite": "Model as source of truth", "modele_de_donnees_plateforme_cible_mode_de_deploiement_integrati": "Data model, target platform, deployment mode, integration into the application landscape, governance and a phased evolution path. The target architecture describes a realistic trajectory; it doesn't assume everything must be replaced immediately.", "modeles_versionnes_dans_le_git_store_et_promotions_dev_recette_p": "Models versioned in the Git Store and audited dev → test → production promotions, without rebuilding the warehouse for every change.", "modelisation": "Modeling", "modelisation_metavault": "Modeling & metaVault", "modelisation_d_un_objet_metier_proche_du_votre_generation_du_cod": "Modeling of a business object close to yours, code generation, historized loading, a quality rule in action and publishing of a mart.", "modelisation_data_vault": "Data Vault modeling", "modelisation_des_donnees_et_mise_en_place_des_metadonnees": "Data modelling and metadata setup", "modelisation_et_generation": "Modeling and generation", "modelisation_et_marts_sur_bigquery": "Modeling and marts on BigQuery", "modelisation_metavault_2": "metaVault modeling", "modelisation_metier_generation_de_code_et_de_structures": "Business modeling, code and structure generation", "modelisation_sur_delta_lake": "Modeling on Delta Lake", "modelisation_visuelle": "Visual modeling", "modelisation_visuelle_du_metamodele": "Visual metamodel modeling", "modelisation_integration_des_sources_controles_qualite_orchestra": "Modeling, source integration, quality controls, orchestration and Information Marts, delivered domain by domain.", "modelisation_integration_qualite_et_orchestration": "Modeling, integration, quality and orchestration", "modelisation_orchestration_et_qualite_au_dessus_du_calcul": "Modeling, orchestration and quality on top of the compute engine", "modeliser_en_dev": "Model in dev", "modelisez_le_metier_bevault_construit_le_reste": "Model the business. beVault builds the rest.", "modelisez_le_sens_metier_et_construisez_une_fondation_data_vault": "Model the business meaning and build a Data Vault foundation from metadata.", "modelisez_votre_metier_pas_vos_systemes_sources": "Model your business, not your source systems.", "modernisation_d_entrepot": "Warehouse modernisation", "modernisation_de_l_entrepot_de_donnees": "Data Warehouse Modernization", "moderniser_sans_migration_cloud_forcee": "Modernize without forced cloud migration", "modernisez_votre_entrepot": "Modernize your warehouse", "modes_de_deploiement": "Deployment modes", "modularite": "Modularity", "moins_de_10_salaries_et_jusqu_a_2_m": "Fewer than 10 employees and up to €2m.", "moins_de_250_salaries_avec_un_chiffre_d_affaires_jusqu_a_50_m_ou": "Fewer than 250 employees, with turnover up to €50m or a balance sheet up to €43m.", "moins_de_50_salaries_et_jusqu_a_10_m": "Fewer than 50 employees and up to €10m.", "moins_de_code_de_chargement_ecrit_a_la_main_aucun_cluster_d_orch": "Less hand-written loading code, no orchestration cluster to maintain, more consistent models and simpler maintenance as sources are added.", "moins_de_code_de_chargement_ecrit_a_la_main_des_modeles_plus_hom": "Less hand-written loading code, more consistent models, immediate impact analysis and new use cases delivered faster. The scale of the gain depends on the number of sources and the state of the existing model.", "moins_de_code_ecrit_a_la_main_des_modeles_data_vault_plus_homoge": "Less hand-written code, more consistent Data Vault models, end-to-end readable traceability and new use cases delivered faster.", "moment_du_controle": "Control moment", "montrez_nous_un_chiffre_difficile_a_expliquer_nous_regardons_ens": "Show us a figure that's hard to explain. We'll look together at what would need to be retained to answer for it.", "mouvements_d_entrepot_expeditions_et_transport_rattaches_aux_mem": "Warehouse movements, shipments and transport linked to the same business objects.", "multi_sources_data_qualite_bevault_l_entrepot_de_donnees_avec_re": "Multi-source, data quality, beVault — the data warehouse with reporting integrated into the Odoo ERP", "n_importe_qui_peut_ecrire_data_vault_2_0": "Anyone can write \"Data Vault 2.0\".", "natif_les_mecanismes_de_performance_propres_a_chaque_moteur_micr": "Native. The performance mechanisms specific to each engine — micro-partitions, distribution, table formats — are leveraged by the generated code.", "navigation_principale": "Main navigation", "ne_corrige_rien": "fixes nothing.", "ne_dit_rien_a_un_agent_ia_sans_signification_explicite_le_modele": "says nothing to an AI agent. Without explicit meaning, the model confuses real patterns with noise.", "ne_jamais_rejeter_toujours_qualifier": "Never reject, always qualify", "ne_ratez_aucune_nouveaute": "Don't miss any news", "ni_concurrent_ni_substitut_ce_que_bevault_apporte_au_dessus_de_v": "Neither a competitor nor a substitute: what beVault brings on top of your target platform.", "niveaux": "Levels", "niveaux_enablement_technique_et_commercial_co_delivery": "Tiers, technical and commercial enablement, co-delivery", "nombre_de_jours_homme_moyen_pour_integrer_une_nouvelle_source_mu": "Average man-days to integrate a new source, multiplied by your fully loaded daily cost. Most of our clients start at 15 to 25 days per source.", "nombre_de_sources_et_d_evolutions_livrees_par_an_c_est_souvent_c": "Number of sources and changes delivered per year. It's often this number, more than the unit cost, that reveals the scale of the gain.", "nommer_les_concepts_metier": "Name the business concepts", "non_nous_reconstruisons_la_couche_de_chargement_proprement_pluto": "No — we cleanly rebuild the loading layer rather than migrating problematic code.", "non_elle_porte_sur_une_version_du_produit_et_doit_etre_maintenue": "No: it applies to a specific product version and must be maintained. That's also why we guarantee compliance with every major release.", "non_couvert": "Not covered", "non_pour_une_demo_decouverte_pour_un_atelier_ou_un_poc_un_extrai": "Not for a discovery demo. For a workshop or a POC, an anonymized extract from two or three sources is enough to make the exercise concrete.", "non_et_c_est_la_premiere_decision_a_prendre_le_perimetre_est_arr": "No, and that's the first decision to make. Scope is set according to retention obligations and actual usage, not out of caution.", "non_mais_il_faut_des_interlocuteurs_metier_disponibles_pour_defi": "No, but available business contacts are needed to define the meaning of the data, and at least one technical profile on the client side. dFakto can supplement this arrangement for as long as necessary.", "non_bevault_construit_le_data_vault_directement_sur_db2_si_une_m": "No. beVault builds the Data Vault directly on DB2. If a migration is decided down the line, the model will be reusable on the target platform.", "non_bevault_fonctionne_sur_sql_server_on_premise_si_vous_migrez_": "No. beVault runs on SQL Server on-premise. If you migrate to Azure SQL eventually, the same model follows without change.", "non_bevault_genere_du_sql_oracle_natif_la_migration_eventuelle_p": "No. beVault generates native Oracle SQL. The eventual migration can be done at your pace — the model will follow you.", "non_bevault_genere_et_orchestre_le_code_qui_s_execute_sur_votre_": "No. beVault generates and orchestrates the code that runs on your platform. Your data stays within your perimeter.", "non_bevault_orchestre_les_chargements_de_donnees_qui_relevent_de": "No. beVault orchestrates the data loads that belong to the platform. Existing AWS jobs can stay in place; integration depends on the boundary defined between the two scopes.", "non_bevault_prend_en_charge_la_couche_de_structuration_et_de_gou": "No. beVault handles the structuring and governance layer. Your data scientists keep Databricks for exploration and ML.", "non_elle_fournit_les_controles_les_traces_et_l_historique_sur_le": "No. It provides the controls, the audit trails and the history that a compliance approach can rely on. Regulatory assessment remains your organization's responsibility.", "non_il_en_supprime_la_partie_la_plus_ingrate_collecter_et_tenir_": "No. It removes the most thankless part — collecting and maintaining the information — but the rules, responsibilities and trade-offs still need to be defined with your teams.", "non_l_orchestration_des_chargements_peut_etre_assuree_par_bevaul": "No. Load orchestration can be handled by beVault. An external orchestrator comes into play when the organization needs to coordinate beVault with other jobs, functions or applications already present in its environment.", "non_l_orchestration_serverless_s_appuie_sur_aws_dans_le_mode_heb": "No. Serverless orchestration relies on AWS in hosted mode, but a fully on-premises deployment is available for sovereign contexts.", "non_la_fondation_se_construit_a_cote_de_l_existant_domaine_par_d": "No. The foundation is built alongside the existing setup, domain by domain, which allows delivery on the old environment to continue during the transition.", "non_la_formation_couvre_les_fondamentaux_du_standard_et_la_manie": "No. The training covers the fundamentals of the standard and how beVault applies them. Experience in data integration is nonetheless useful.", "non_le_mode_d_execution_de_la_plateforme_et_la_base_cible_sont_d": "No. The platform's execution mode and the target database are two separate choices.", "non_les_projets_avancent_domaine_par_domaine_ce_qui_permet_de_li": "No. Projects move forward domain by domain, which delivers value before the entire application landscape has been integrated.", "non_les_projets_demarrent_le_plus_souvent_par_un_domaine_en_para": "No. Projects most often start with a single domain, running alongside the existing setup, then expand the scope once loads and marts are validated.", "non_nous_structurons_domaine_par_domaine_en_parallele_de_l_exist": "No. We structure domain by domain, alongside the existing setup, with reconciliation before cutover.", "non_nous_structurons_domaine_par_domaine_en_parallele_de_l_exist_2": "No. We structure domain by domain, in parallel with the existing system, reconciling figures before cutover.", "non_vous_rebranchez_progressivement_vos_rapports_sur_les_marts_g": "No. You gradually reconnect your reports to the governed marts; the presentation layer remains yours.", "nos_architectes_interviennent_avec_vos_equipes_sur_les_premiers_": "Our architects work alongside your teams on the first projects, then step back gradually.", "nos_bureaux": "Our offices", "nos_clients_mesurent_une_livraison_environ_7_fois_plus_rapide_su": "Our clients measure delivery roughly 7 times faster on new sources, with a return on investment reached in six months on average. This isn't an individual productivity gain: it's the elimination of an entire category of work.", "nos_clients_n_achetent_pas_du_data_vault_ils_arrivent_avec_un_en": "Our clients don't buy “Data Vault”: they come to us with a warehouse running out of steam, reporting that no longer convinces, a stalled AI project, or a regulatory requirement to meet. Here's how beVault addresses each of these situations, with the results we see in the field.", "nos_clients_ne_lancent_pas_un_projet_ia_ils_rendent_leur_socle_e": "Our clients don't launch an “AI project”: they make their foundation usable, and use cases then become achievable one after another.", "nos_clients_sont_majoritairement_europeens_mais_nous_accompagnon": "Our clients are mostly European, but we also support international deployments, notably for NGOs.", "nos_donnees_sortent_elles_de_notre_plateforme": "Does our data leave our platform?", "nos_equipes_cadrent_ce_perimetre_avec_vous_puis_outillent_la_mis": "Our teams scope this together with you, then build the tooling to make data available to agents via the beVault API.", "nos_equipes_sont_a_bruxelles_et_a_paris": "Our teams are in Brussels and Paris.", "nos_experts_partagent_leurs_retours_terrain_sur_data_vault_la_qu": "Our experts share what they see in the field on Data Vault, data quality and AI. Recorded sessions, available at any time.", "notre_approche": "Our approach", "notre_culture": "Our culture", "notre_difference_pese_lorsque_vous_cherchez_a_reduire_le_nombre_": "Our difference matters when you're looking to reduce the number of components to maintain, when data quality and identity reconciliation are at the heart of the problem, or when you need to present independent proof of standard compliance to an auditor. In these situations, an integrated and certified platform changes the nature of the internal conversation.", "notre_objectif_de_fin_de_mission_est_simple_que_vos_equipes_puis": "Our end goal is simple: your teams should be able to add a source, evolve the model and diagnose a process with far more autonomy, without systematically depending on us. The whole process is organized to get there.", "notre_partenaire": "Our partner", "notre_proposition_prend_tout_son_sens_dans_le_cas_inverse_equipe": "Our proposition makes perfect sense in the opposite case: lean data team, desire to reduce the number of tools to maintain, strong auditability requirements or sovereignty constraints. In this context, an integrated platform costs significantly less to operate than an assembled chain, and above all, it remains maintainable when people change.", "nous_avons_volontairement_reduit_notre_offre_de_services_a_deux_": "We deliberately narrowed our services to two clear sets rather than a catalogue of offerings.", "nous_construisons_le_data_vault_en_parallele_de_l_existant_avec_": "We build the Data Vault in parallel with the existing system, reconciling figures domain by domain before any cutover.", "nous_contacter": "Contact us", "nous_documentons_des_contextes_reels_ce_qui_posait_probleme_ce_q": "We document real-world contexts: what the problem was, what was put in place, and how the platform is used today. We'd rather you come to the demo with your toughest questions already prepared.", "nous_exploitons_la_plateforme_pour_vous_mises_a_jour_supervision": "We operate the platform for you: updates, monitoring, backups, and support. Ideal for getting started quickly and staying focused on business value.", "nous_identifions_vos_marches_vos_secteurs_et_les_competences_dat": "We identify your markets, your sectors and the data skills already present in your teams.", "nous_intervenons_sur_toute_la_trajectoire_en_combinant_l_experti": "We work across the entire trajectory, combining dFakto's team expertise with the beVault platform's capabilities: modeling, source integration, quality controls, load orchestration, Information Marts and go-live.", "nous_les_retrouvons_dans_presque_toutes_les_plateformes_que_nous": "We find them in almost all the platforms we take over.", "nous_n_affichons_une_reference_que_lorsque_son_contenu_a_ete_val": "We only display a reference once its content has been validated by the client. Sectors without a published reference show none.", "nous_ne_pretendons_pas_qu_airflow_soit_un_mauvais_choix_si_vous_": "We do not claim that Airflow is a bad choice. If you already orchestrate hundreds of heterogeneous processes outside the data scope, and a platform team exists, sharing it makes sense. In that case, beVault fits in: our loads can be triggered and monitored from your enterprise orchestrator. What we dispute is building that infrastructure solely to run a Data Vault.", "nous_ne_pretendons_pas_que_le_choix_est_toujours_le_meme": "We don't claim the choice is always the same", "nous_ne_publions_pas_de_gains_theoriques_calcules_sur_un_tableur": "We do not publish theoretical gains calculated on a spreadsheet. The figures below come from real projects, measured before and after the implementation of beVault, with the measurement method explained for each.", "nous_ne_publions_pas_de_grille_tarifaire_car_les_conditions_depe": "We do not publish a price list because the right conditions depend on the project scope, deployment environment, number of domains, teams and level of support. Contact us to discuss the right starting point.", "nous_organisons_volontiers_un_echange_direct_avec_le_client_dont": "We gladly arrange a direct exchange with the client whose context is closest to yours.", "nous_preferons_une_methode_que_vous_pouvez_contester_ligne_a_lig": "We prefer a method you can challenge line by line rather than a number handed down as fact.", "nous_prenons_volontairement_l_hypothese_la_plus_favorable_a_la_s": "We deliberately assume the most favorable case for the outsourced stack: excellent tools, well mastered.", "nous_preparons_les_dossiers_de_securite_de_nos_clients_depuis_pl": "We have been preparing our clients' security files for over ten years, at dFakto, for demanding financial and public institutions.", "nous_vous_proposons_une_demonstration_sur_un_jeu_de_donnees_issu": "We offer a demonstration on a dataset from your environment: the comparison becomes factual in one hour.", "nouvelles_sources": "New sources", "nuance": "Nuance", "object_contain_p_4_sm_p_8": "object-contain p-4 sm:p-8", "objectifs_et_cas_d_usage": "Objectives and use cases", "objectifs_perimetre_contraintes_reglementaires_et_etat_des_lieux": "Objectives, scope, regulatory constraints and an assessment of the current setup. The output of this step is a decision, not a document.", "on_brasse_aussi_notre_propre_biere_bevault_a_co_cree_une_recette": "We also brew our own beer. beVault co-created an exclusive recipe with Brasserie Witloof, a Brussels craft brewery. Limited edition, 100% local.", "on_peut_empiler_des_donnees_comme_on_empile_des_briques_sans_pla": "You can stack data the way you stack bricks. Without a blueprint, the structure holds for a few months — then every new source cracks the whole thing.", "on_separe_generalement_les_satellites_par_source_et_par_frequenc": "Satellites are generally separated by source and by rate of change. One satellite for civil status data that changes once a year, another for statuses that change daily: volumes stay under control and loads remain independent.", "on_premises": "On-premises", "on_premises_complet_pour_les_contextes_souverains": "Full on-premises for sovereign contexts", "on_premises_cloud_de_l_administration_ou_hybride_dans_votre_peri": "On-premises, government cloud, or hybrid — within your area of responsibility.", "on_premises_cloud_ou_hybride_docker_permet_d_adapter_l_execution": "On-premises, cloud or hybrid: Docker lets you adapt the platform's execution to your infrastructure environment.", "on_premises_cloud_paas_ou_hybride": "On-premises, cloud, PaaS, or hybrid", "on_premises_cloud_paas_hybride_docker": "On-premises, cloud, PaaS, hybrid, Docker", "on_premises_dans_votre_cloud_en_paas_ou_en_mode_hybride_avec_doc": "On-premises, in your cloud, in PaaS or in hybrid mode, with Docker as the deployment technology. You keep control of the infrastructure and access.", "open_source_ne_veut_pas_dire_sans_structure": "Open source doesn't mean unstructured", "oracle": "Oracle", "oracle_et_bevault": "Oracle and beVault", "oracle_heberge_souvent_les_donnees_les_plus_strategiques_de_l_or": "Oracle often hosts an organization's most strategic data. Rushing a migration to another platform is neither realistic nor necessary. beVault generates SQL tailored to Oracle and lets you build a Data Vault 2.0 architecture on top of your existing infrastructure — gradually reducing proprietary lock-in without disrupting production.", "orchestrateur_externe": "External orchestrator", "orchestrateur_externe_avec_lequel_bevault_s_articule": "External orchestrator beVault works alongside", "orchestrateur_integre_dependances_suivi_des_traitements": "Built-in orchestrator, dependencies, process monitoring", "orchestration": "Orchestration", "orchestration_aws_step_functions": "Orchestration — AWS Step Functions", "orchestration_incluse_ou_cluster_a_operer": "Orchestration: included or cluster to operate?", "orchestration_calculee_a_partir_du_graphe_de_dependances_du_mode": "Orchestration calculated from the model's dependency graph", "orchestration_des_chargements": "Load orchestration", "orchestration_des_chargements_de_donnees_pilotee_par_bevault": "Data load orchestration driven by beVault", "orchestration_des_workflows": "Workflow Orchestration", "orchestration_incluse_aucune_dependance_a_airflow_ou_matillion": "Orchestration included: no dependency on Airflow or Matillion", "orchestration_incluse_sans_orchestrateur_tiers_a_operer": "Orchestration included, with no third-party orchestrator to operate", "orchestration_incluse_sans_planificateur_supplementaire": "Orchestration included, with no additional scheduler", "orchestration_integree": "Integrated orchestration", "orchestration_integree_serverless": "Integrated serverless orchestration", "orchestration_integree_vs_orchestrateur_a_operer": "Integrated orchestration vs. orchestrator to operate", "orchestration_native": "Native orchestration", "orchestration_native_sans_airflow": "Native orchestration, no Airflow", "orchestration_serverless_sans_cluster_a_operer": "Serverless orchestration, no cluster to operate", "orchestration_via_aws_step_functions_sans_orchestrateur_externe": "Orchestration via AWS Step Functions — no external orchestrator", "orchestrer_les_flux_de_donnees_de_la_source_a_l_usage": "Orchestrate data flows from source to use", "orchestrer_les_traitements": "Orchestrate the processes", "ordonnancement_calcule_pour_limiter_le_temps_de_warehouse": "Scheduling calculated to limit warehouse time", "ordonnancement_outille_souvent_complete_par_un_orchestrateur": "Tool-based scheduling, often supplemented by an orchestrator", "ordonnanceur_natif_ou_orchestrateur_tiers_a_configurer": "Native scheduler or third-party orchestrator to configure", "ordre_de_chargement_deduit_du_modele_pas_d_un_graphe_de_fichiers": "Load order derived from the model, not from a file graph", "ordres_lots_et_declarations_issus_de_l_erp_et_du_mes_conserves_d": "Orders, batches and declarations from the ERP and the MES, kept in their original state.", "organisations_qui_travaillent_avec_dfakto": "Organizations working with dFakto", "ou": "Or:", "ou_aller_ensuite": "Where to go next", "ou_bevault_peut_il_etre_deploye": "Where can beVault be deployed?", "ou_le_temps_se_perd": "Where time is lost", "ou_s_execute_la_plateforme": "Where the platform runs", "ou_s_executent_les_composants_qui_opere_l_infrastructure_et_quel": "Where components run, who operates the infrastructure, and which regulatory constraints apply.", "ou_vous_documentez_chaque_colonne_de_sortie_et_son_lineage": "where you document each output column and its lineage.", "oui_licence_tierce_requise": "Yes — third-party license required", "oui_sql_lisible_commente_et_exportable_sur_toutes_les_plateforme": "Yes: readable, commented and exportable SQL, across all supported target platforms.", "oui_c_est_du_sql_standard_lisible_et_commente_exportable_a_tout_": "Yes, it's standard, readable, commented SQL, exportable at any time. No dependency on a proprietary engine at runtime.", "oui_des_lors_qu_il_y_a_plusieurs_sources_a_reconcilier_et_un_bes": "Yes, as soon as there are multiple sources to reconcile and a need for reliable reporting. The initial scope can remain limited; it is the method, not the size, that determines the result.", "oui_l_une_apres_l_autre_les_entites_metier_communes_sont_rapproc": "Yes, one after the other. Common business entities are matched by their business keys, which avoids rebuilding a silo for each application.", "oui_bevault_orchestre_les_chargements_avec_aws_step_functions_a_": "Yes. beVault orchestrates loads with AWS Step Functions based on the dependency graph, with no external orchestrator to maintain.", "oui_bevault_peut_travailler_avec_vos_processus_de_referentiel_ou": "Yes. beVault can work with your existing reference-data processes or MDM tool when it's relevant; it doesn't automatically replace them.", "oui_bevault_se_branche_sur_vos_sources_et_alimente_vos_outils_de": "Yes. beVault connects to your sources and feeds your existing BI tools; it replaces neither your ERP, nor your CRM, nor your reporting tool.", "oui_bevault_se_connecte_a_postgresql_qu_il_soit_on_premise_ou_ma": "Yes. beVault connects to PostgreSQL whether it's on-premises or cloud-managed.", "oui_c_est_du_code_standard_commente_versionnable_dans_git_et_exp": "Yes. It's standard, commented code, versionable in Git and exportable.", "oui_c_est_du_sql_bigquery_standard_lisible_commente_et_exportabl": "Yes. It's standard BigQuery SQL, readable, commented and exportable.", "oui_c_est_du_sql_redshift_standard_lisible_commente_et_exportabl": "Yes. It's standard Redshift SQL, readable, commented and exportable.", "oui_c_est_du_sql_snowflake_standard_lisible_commente_et_exportab": "Yes. It's standard Snowflake SQL, readable, commented and exportable at any time.", "oui_c_est_du_t_sql_standard_commente_versionnable_dans_git_et_ex": "Yes. It's standard T-SQL, commented, versionable in Git and exportable at any time.", "oui_des_equipes_conservent_dbt_pour_des_transformations_analytiq": "Yes. Some teams keep dbt for analytical transformations downstream of the Information Marts produced by beVault.", "oui_la_modelisation_et_le_code_genere_sont_adaptes_au_perimetre_": "Yes. The modeling and generated code are adapted to the chosen Db2 scope. Compatibility details are defined based on your version and configuration.", "oui_la_page_devenir_partenaire_affiche_le_formulaire_corresponda": "Yes. The “Become a partner” page displays the form matching the site's active language, in both French and English.", "oui_la_version_precedente_du_modele_reste_disponible_dans_le_git": "Yes. The previous version of the model remains available in the Git Store and can be re-promoted; historized data is not destroyed by a version rollback.", "oui_le_sql_produit_est_commente_et_exportable_vous_n_etes_pas_en": "Yes. The SQL produced is commented and exportable. You're not locked into a black box.", "oui_les_information_marts_sont_produits_dans_la_base_cible_et_pe": "Yes. Information Marts are produced in the target database and can be consumed by applications, BI tools and AI agents within the scope configured for these consumers.", "oui_les_marts_sont_exposes_directement_aux_outils_bi_via_les_con": "Yes. Data marts are directly exposed to BI tools via standard connectors.", "oui_les_modeles_et_les_metadonnees_sont_portables_une_migration_": "Yes. Models and metadata are portable: migrating from the managed service to your own environment, or vice versa, does not put your Data Vault at risk.", "oui_nos_architectes_analysent_votre_modele_existant_et_definisse": "Yes. Our architects analyze your existing model and define a migration plan before any commitment. Historical data is preserved during migration.", "oui_nous_donnons_un_ordre_de_grandeur_des_le_premier_echange_en_": "Yes. We provide an order of magnitude from the first exchange, depending on the number of sources and the deployment method.", "oui_une_organisation_peut_commencer_avec_un_premier_domaine_ou_c": "Yes. Organisations can start with a first domain or use case and extend the platform progressively as their needs grow.", "outiller_le_developpement_ou_industrialiser_le_modele": "Equip development, or industrialize the model", "outils_de_gouvernance_des_donnees": "Data governance tools.", "outils_de_workflow_et_d_orchestration": "Workflow and orchestration tools.", "outils_existants": "Existing tools", "ouverture_aux_agents_ia": "Openness to AI agents", "ouvertures_fermetures_changements_de_format_ou_de_rattachement_r": "Openings, closures, format changes or regional reassignments are dated rather than overwritten.", "ouvrir_le_menu": "Open menu", "paas": "PaaS", "page_introuvable": "Page not found", "par_des_controles_de_comptage_et_de_coherence_entre_le_systeme_s": "Through count and consistency checks between the source system and the platform, documented and repeatable. That evidence is what enables the decommissioning decision.", "par_exemple_un_agent_ia_pourrait_repondre_a": "For example, an AI agent could answer:", "par_exemple_vous_pouvez_definir_un_modele_pour_un_concept_metier": "For example, you can define a template for a recurring business concept and use it to create the corresponding entities in beVault automatically. This helps standardize implementation, reduce manual effort and accelerate the delivery of new business cases.", "par_industrie": "By industry", "par_ou_commencent_nos_clients": "Where our clients start", "par_ou_commencer": "Where to start", "par_ou_commencer_2": "Where to start?", "par_ou_continuer": "Where to go from here", "par_ou_une_pme_peut_commencer": "Where an SME can start", "par_projet": "By project", "par_un_domaine_avec_un_responsable_designe_et_quelques_regles_qu": "With one domain, a designated owner and a few rules that truly matter. Governance that delivers results on a limited scope then scales up far more easily.", "parce_que_le_modele_est_stocke_sous_forme_de_metadonnees_la_plat": "Because the model is stored as metadata, the platform derives the structures, loading code, documentation and lineage from it. A change to the model propagates, instead of triggering a manual rework campaign across dozens of scripts.", "parce_que_les_controles_portent_sur_des_donnees_historisees_et_r": "Because controls focus on historical data gathered from multiple systems, anomalies are proactively detected and linked to a specific source, rather than a general suspicion about the warehouse.", "parce_que_les_meilleures_decisions_se_prennent_parfois_autour_d_": "Because the best decisions are sometimes made over a beer. beVault collaborated with Brasserie Witloof, a Brussels craft brewery, to create an exclusive recipe — brewed in small batches, with as much care as our code.", "parcours_de_formation_structures_pour_prendre_en_main_la_platefo": "Structured training paths to master the platform, from Data Vault modeling to first deployments.", "paris": "Paris", "parking_brussels": "parking.brussels", "parler_a_un_architecte": "talk to an architect", "parler_a_un_architecte_2": "Talk to an architect", "parler_a_un_expert": "Talk to an expert", "parler_a_un_expert_2": "Talk to an expert", "parler_a_une_equipe_data": "Talk to a data team", "parler_de_vos_conditions_pme": "Discuss your SME conditions", "parler_de_vos_enjeux_data": "Talk about your data challenges", "parler_de_votre_architecture": "Discuss your architecture", "parler_de_votre_contexte_d_orchestration": "Discuss your orchestration context", "parler_de_votre_contexte_de_migration": "Discuss your migration context", "parler_de_votre_environnement_de_deploiement": "Discuss your deployment environment", "parler_de_votre_environnement_de_donnees_assurance": "Discuss your insurance data environment", "parler_de_votre_environnement_de_donnees_d_exploitation": "Discuss your operational data environment", "parler_de_votre_environnement_de_donnees_energie": "Discuss your energy data environment", "parler_de_votre_environnement_de_donnees_publiques": "Discuss your public data environment", "parler_de_votre_environnement_de_donnees_regule": "Discuss your regulated data environment", "parler_de_votre_modele_data_vault": "Discuss your Data Vault model", "parler_de_votre_paysage_de_donnees_industrielles": "Discuss your industrial data landscape", "parler_de_votre_projet": "Talk about your project", "parler_de_votre_situation": "Discuss your situation", "parlez_a_un_architecte_de_votre_contexte_avant_de_parler_d_outil": "Talk to an architect about your context before talking about tools.", "parlons_de_la_fondation_de_donnees_dont_vos_cas_d_usage_ia_ont_b": "Let's talk about the data foundation your AI use cases need.", "parlons_de_vos_donnees_de_reference_et_des_systemes_a_reconcilie": "Let's talk about your master data and the systems to reconcile.", "parlons_de_vos_systemes_existants_de_vos_contraintes_de_deploiem": "Let's talk about your existing systems, your deployment constraints, and what you need to be able to prove.", "parlons_de_votre_architecture_actuelle_et_de_ce_qui_peut_evoluer": "Let's talk about your current architecture and what could evolve first.", "parlons_de_votre_environnement_de_reporting_et_de_l_indicateur_q": "Let's talk about your reporting environment and the metric that's causing trouble.", "parlons_de_votre_projet_et_de_l_equipe_qui_devra_le_porter": "Let's talk about your project and the team that will carry it forward.", "partenaires": "Partners", "partenaires_programme": "Partners — Program", "partez_de_votre_situation_pas_d_une_technologie": "Start from your situation, not from a technology.", "partitionnement_par_date_de_chargement_clustering_par_cle_metier": "Partitioning by load date, clustering by business key, optimized MERGE operations — the code leverages native mechanisms.", "pas_de_cluster_ni_de_scheduler_a_operer": "No clusters or schedulers to operate", "pas_de_dette_d_architecture_invisible": "No invisible architectural debt", "pas_de_presentation_generique_de_trente_diapositives_vous_nous_d": "No generic thirty-slide presentations. You describe a source and a reporting need; we show the complete journey within the platform—modeling, historized loading, quality control, orchestration, and mart publication. You judge on facts.", "pas_de_source_de_verite": "No single source of truth", "pas_du_sql_generique_traduit": "Not generic SQL translated after the fact.", "pas_encore_snowflake_amazon_redshift_microsoft_sql_server_et_pos": "Not yet. Snowflake, Amazon Redshift, Microsoft SQL Server, and PostgreSQL are supported today; Databricks is coming soon. Contact us to discuss your timeline.", "pas_encore_snowflake_amazon_redshift_microsoft_sql_server_et_pos_2": "Not yet. Snowflake, Amazon Redshift, Microsoft SQL Server and PostgreSQL are supported today; Google BigQuery is coming soon. Contact us to discuss your schedule.", "pas_la_structure": "Not the structure.", "pas_necessairement_bevault_documente_les_definitions_les_respons": "Not necessarily: beVault documents definitions, owners and lineage. If you already have an enterprise catalog, it can be fed from the API.", "pas_necessairement_mais_vous_devez_alors_auditer_vous_meme_le_co": "Not necessarily, but you will then need to audit the generated code yourself. At a minimum, request a complete sample of loading code before deciding.", "pas_necessairement_le_raw_vault_conserve_la_donnee_telle_qu_elle": "Not necessarily. The Raw Vault keeps the data as it arrived: rules identify and flag issues without silently destroying the original history, and exceptions remain visible and tracked.", "passage_en_production": "Go-live", "passons_en_revue_vos_exigences_de_gouvernance_et_ce_qui_peut_etr": "Let's review your governance requirements and what can be tooled.", "patrons_a_implementer_via_des_macros_et_des_paquets_communautair": "Patterns to implement via macros and community packages", "pattern_1_orchestration_simple_api_anthropic_api_bevault": "Pattern 1 — Simple orchestration: Anthropic API + beVault API", "pattern_2_agents_interactifs_avec_api_directe": "Pattern 2 — Interactive agents with direct API", "pattern_3_agents_avec_serveurs_mcp": "Pattern 3 — Agents with MCP servers", "pcma": "PCMA", "pendant_ce_temps_le_referentiel_physique_change_une_zone_est_red": "Meanwhile, the physical reference data changes: a zone is redrawn, a rate is revised, equipment is replaced. If these changes overwrite the previous state, a year-over-year comparison no longer makes sense, and a reported figure can no longer be justified.", "pendant_le_chargement_data_vault": "During Data Vault loading", "pendant_que_vos_concurrents_luttent_avec_des_integrations_fragil": "While your competitors struggle with fragile integrations and dubious quality, you deploy agents with confidence. Projects succeed because the data layer is right. They scale because the architecture was designed for the enterprise from the start.", "performances_solides": "Robust performance", "perimetre": "Scope", "perimetre_couvert": "Scope covered", "perimetre_de_deploiement_defini_lors_de_la_qualification": "Deployment scope defined during qualification", "personne_ne_consomme_des_hubs_et_des_satellites_les_utilisateurs": "Nobody consumes hubs and satellites: users want a customer dimension, quarterly revenue, or a risk view at a given date. beVault builds these consumption layers on top of the Data Vault, as documented, usable data products.", "personne_au_comite_de_direction_ne_demandera_si_votre_satellite_": "No one on the executive committee will ask whether your satellite is correctly historized. They'll ask why a new source takes six weeks. Data Vault automation acts precisely there: it removes the repetitive work of generating and maintaining code, and makes delivery time predictable.", "perte_du_lignage": "Loss of lineage", "peut_on_aborder_les_tarifs": "Can we discuss pricing?", "peut_on_changer_de_mode_de_deploiement_plus_tard": "Can we change deployment modes later?", "peut_on_choisir_entre_un_deploiement_on_premises_cloud_ou_hybrid": "Can I choose between on-premises, cloud and hybrid deployment?", "peut_on_commencer_avec_un_perimetre_cible": "Can I start with a focused scope?", "peut_on_commencer_avec_un_seul_domaine_ou_cas_d_usage": "Can we start with a single domain or use case?", "peut_on_conserver_les_systemes_existants": "Can we keep our existing systems?", "peut_on_deployer_sur_un_cloud_manage_rds_cloudsql": "Can we deploy on a managed cloud (RDS, CloudSQL)?", "peut_on_exposer_les_donnees_vers_power_bi_ou_tableau": "Can we expose data to Power BI or Tableau?", "peut_on_garder_notre_outil_mdm_existant": "Can we keep our existing MDM tool?", "peut_on_migrer_un_projet_vaultspeed_vers_bevault": "Can we migrate a VaultSpeed project to beVault?", "peut_on_reprendre_un_modele_datavault_builder_existant": "Can we reuse an existing Datavault Builder model?", "peut_on_revenir_en_arriere_apres_une_promotion": "Can we roll back after a promotion?", "peut_on_traiter_plusieurs_applications": "Can we handle multiple applications?", "peuvent_defendre_en_interne": "can defend internally.", "photo_biere_bevault_a_venir": "beVault beer photo — coming soon", "piloter_l_exploitation_urbaine": "Steering urban operations", "planificateurs_d_evenements_sur_donnees_certifiees": "event planners working on certified data", "plateforme_de_donnees_prete_pour_l_ia": "AI-ready data platform", "plateforme_ia_de_destination_events_construite_par_dfakto_sur_be": "AI destination platform for events built by dFakto on beVault. Every piece of data exposed to AI is certified, versioned and auditable.", "plateforme_tout_en_un": "All-in-one platform", "plateforme_tout_en_un_ou_assemblage_de_licences": "All-in-one platform or license assembly", "plateformes": "Platforms", "plateformes_de_donnees": "Data platforms", "plateformes_et_bases_cibles": "Target platforms and databases", "plateformes_supportees": "Supported platforms", "plus_de_12_000_professionnels_de_l_evenementiel_accedent_a_une_b": "More than 12,000 event industry professionals now access a consistent, comparative database, where the work used to rely on spreadsheets and calls to tourist offices.", "plus_de_contenu_moins_de_slides": "More content, fewer slides.", "plusieurs_agents_planifies_couts_long_terme_importants": "Multiple planned agents, significant long-term costs", "plusieurs_agents_maintenabilite_long_terme": "Multiple agents, long-term maintainability", "plusieurs_domaines_et_sources": "Multiple domains and sources", "plusieurs_semaines_d_installation_et_de_cadrage": "Several weeks of installation and scoping", "plusieurs_systemes_alimentent_souvent_les_memes_entites_metier_l": "Multiple systems often feed the same business entities. Business Keys make it possible to reconcile them without losing the origin of each record — and the retained history is useful well beyond analytics: it de-risks migrations and application decommissioning.", "point_de_depart": "Starting point", "point_essentiel_un_link_est_toujours_n_n_par_construction_si_le_": "Key point: a link is always many-to-many by design. If the business decides tomorrow that a contract can have two holders, no table needs to be modified — cardinality was never fixed in the structure.", "points_de_depart": "Starting points", "politique_de_confidentialite": "Privacy Policy", "portabilite": "Portability", "portabilite_preservee": "Portability preserved", "portabilite_totale": "Full portability", "portail_partenaire": "Partner Portal", "poser_une_question": "Ask a question", "posez_les_a_toute_votre_short_list_y_compris_a_nous_une_reponse_": "Ask them of your entire shortlist, including us. An evasive answer on any of these points will cost you in operations.", "possible_selon_l_edition_et_l_architecture_retenue": "Possible depending on the edition and architecture chosen", "postgresql": "PostgreSQL", "postgresql_est_la_plateforme_de_reference_pour_les_organisations": "PostgreSQL is the platform of choice for organizations that refuse vendor lock-in. beVault generates native PostgreSQL SQL and builds a Data Vault on infrastructure you fully control—on-premise, cloud, or hybrid. The generated code is standard SQL: readable, versionable, portable.", "postgresql_et_bevault": "PostgreSQL and beVault", "postgresql_offre_toute_la_puissance_necessaire_pour_un_data_vaul": "PostgreSQL offers all the power needed for an industrial-grade Data Vault. What's missing is automation.", "postgresql_supporte_des_volumes_importants_avec_les_bons_index_e": "PostgreSQL handles large volumes with the right indexes and partitioning. beVault generates these structures automatically.", "pour_atteindre_ces_resultats_en_production": "to achieve these results in production", "pour_beaucoup_d_organisations_la_question_n_est_pas_ce_que_fait_": "For many organizations, the question isn't what the platform does but where it runs, who holds the access, and what leaves the network. That answer shapes the project timeline far more than the features do.", "pour_decider_le_matin": "To decide in the morning.", "pour_l_organisation_time_to_implementation_de_quelques_heures_a_": "For the organization: time-to-implementation drops from hours to minutes, engineering capacity is freed for strategic work, and quality is maintained because the agent applies best practices consistently.", "pour_le_prompt_complet_pret_pour_la_production_voir_la_documenta": "For the full, production-ready prompt, see the beVault documentation: https://support.bevault.io/en/bevault-documentation/current-version/how-tos/how-to-update-the-metadata-of-your-im-scripts-with-ai", "pour_les_organisations": "for organizations", "pour_les_organisations_qui_souhaitent_executer_bevault_dans_leur": "For organisations that need to run beVault within their own infrastructure and control their deployment environment.", "pour_les_organisations_soumises_a_des_exigences_de_souverainete_": "For organizations subject to data sovereignty requirements, on-premise PostgreSQL remains the simplest answer.", "pour_les_pme": "For SMEs", "pour_les_utilisateurs_techniques_developpement_accelere_role_qui": "For technical users: faster development, a shift from executor to reviewer, and better accuracy through consistent metadata encoding.", "pour_nos_clients_cela_signifie": "For our customers, this means:", "pour_un_regulateur_comme_pour_un_audit_interne_il_faut_pouvoir_e": "Whether for a regulator or an internal audit, you need to be able to explain what data a model was trained on. Full lineage makes this answer immediate.", "pourquoi_c_est_pertinent_pour_vous": "Why this matters to you", "pourquoi_ca_compte": "Why it matters", "pourquoi_cela_vous_protege": "Why this protects you", "pourquoi_cette_mecanique_s_automatise_si_bien": "Why these mechanics automate so well", "pourquoi_l_ancien_systeme_reste_allume": "Why the old system stays switched on", "pourquoi_le_chiffre_publie_il_y_a_un_an_differe_du_chiffre_recal": "Why does the figure published a year ago differ from the figure recalculated today?", "pourquoi_le_data_vault": "Why use Data Vault?", "pourquoi_les_approches_traditionnelles_echouent": "Why traditional approaches fail", "pourquoi_les_modeles_traditionnels_s_essoufflent": "Why traditional models run out of steam", "pourquoi_les_projets_ia_echouent": "Why AI projects fail", "pourquoi_les_projets_ia_echouent_et_comment_construire_une_fonda": "Why AI projects fail—and how to build a lasting foundation", "pourquoi_les_projets_qualite_s_essoufflent": "Why data quality projects run out of steam", "pourquoi_postgresql_pour_le_data_vault": "Why PostgreSQL for Data Vault", "pourquoi_un_data_vault_bien_construit_est_la_fondation_la_plus_s": "Why a well-built Data Vault is the most solid foundation for deploying reliable AI agents.", "pourquoi_un_socle_data_vault_sous_une_plateforme_ia": "Why a Data Vault foundation under an AI platform", "pourquoi_vos_projets_data_prennent_toujours_plus_longtemps_que_p": "Why your data projects always take longer than expected", "precision": "Accuracy", "premier_domaine_ou_perimetre_cible": "First domain or focused scope", "premier_projet_accompagne": "Guided first project", "premiers_information_marts": "First Information Marts", "prendre_bevault_en_main": "get to grips with beVault.", "prenez_contact": "Contact us", "prenez_contact_avec_notre_equipe_pour_discuter_de_vos_projets_da": "Get in touch with our team to discuss your data projects.", "prenez_les_trois_dernieres_sources_integrees_et_comptez_les_jour": "Take the last three integrated sources and count the man-days actually consumed, excluding business rules.", "prenons_un_flux_reel_entre_votre_erp_et_votre_mes_et_regardons_c": "Let's take a real flow between your ERP and your MES, and look at what would need to be kept to track it end to end.", "prenons_une_branche_et_un_cas_de_sinistre_reel_nous_regardons_ce": "Let's take a line of business and a real claim case: we look at what would need to be kept to reconstruct it.", "prenons_une_serie_de_comptage_et_une_correction_recente_nous_reg": "Take a counting series and a recent correction: we look at what your current foundation retains of it.", "preparer_des_donnees_exploitables_par_vos_agents": "Prepare data your agents can act on", "preparer_des_donnees_utilisables_par_l_ia": "Prepare data usable by AI", "preparez_une_fois_reutilisez_partout": "Prepare once. Reuse everywhere.", "preserver_l_historique_et_le_contexte_des_sources": "Preserve source history and context", "prete_pour_l_ia": "ready for AI,", "preuves": "Evidence", "prevu_dans_une_prochaine_version": "Planned for a future version", "priorite": "Priority", "priorites": "Priorities", "priorites_recommandations": "Priorities & recommendations", "procedures_de_suivi_et_de_reprise_pour_que_les_equipes_sachent_o": "Monitoring and recovery procedures, so teams know where to look when a job fails overnight.", "production_et_logistique": "Production and logistics", "production_logistique_referentiels_articles": "Production, logistics, item master data", "produisez_des_information_marts_documentes_pour_vos_usages_bi_an": "Produce documented Information Marts for your BI, analytical and AI use cases.", "produit_fonctionnalites": "Product — Features", "produit_versioning_environnements": "Product — Versioning & environments", "produit_certifie_par_un_organisme_independant": "Product certified by an independent body", "produite_en_petites_quantites_pour_garder_le_caractere_artisanal": "Produced in small quantities to maintain artisanal character.", "produits": "Products", "produits_dans_votre_base_cible": "Produced in your target database", "produits_de_donnees_information_marts": "Data Products & Information Marts", "profondeur_historique": "Historical depth", "programme_partenaire": "Partner Program", "programme_partenaires": "Partner Program", "proliferation_des_couches": "Layer proliferation", "proliferation_des_datasets": "Dataset proliferation", "proliferation_des_schemas": "Schema proliferation", "promise": "Promise", "promotions_auditees_reversibles_et_tracables": "Audited, reversible and traceable promotions", "promouvoir_en_recette": "Promote to staging", "proof_of_concept": "Proof of Concept", "proprietaires_de_donnees_seuils_d_alerte_et_decisions_prises_res": "Data owners, alert thresholds and decisions taken stay attached to the model rather than to a separate document.", "publier_aux_consommateurs_autorises": "Publish to authorized consumers", "publier_des_information_marts_documentes": "Publish documented Information Marts", "publier_un_mart_gouverne": "Publish a Governed Mart", "puis_leur_laisser_la_main": "then hand over to them.", "puis_je_utiliser_aws_step_functions_pour_orchestrer_mon_data_vau": "Can I use AWS Step Functions to orchestrate my Data Vault?", "qu_il_vienne_du_crm_de_l_erp_ou_du_facturier_un_client_doit_pouv": "Whether it comes from the CRM, the ERP or the billing system, a customer must be recognized as the same entity, without the original record disappearing. That's the role of Business Keys and historization in the model.", "qualite": "Quality", "qualite_gouvernance": "Quality & Governance", "qualite_gouvernance_2": "Quality & Governance", "qualite_gouvernance_des_donnees": "Data Quality & Governance", "qualite_des_donnees": "Data Quality", "qualite_des_donnees_native_ou_licence_tierce": "Data Quality: Native or Third-Party License?", "qualite_des_donnees_gouvernance": "Data Quality & Governance", "qualite_des_donnees_mdm": "Data Quality & MDM", "qualite_des_donnees_et_mdm": "Data Quality and MDM", "qualite_des_donnees_et_referentiels_integres": "Data Quality and integrated master data", "qualite_des_donnees_instrumentee_au_dela_des_tests_de_schema": "Data Quality instrumented beyond schema tests", "qualite_des_donnees_integree_au_chargement": "Data Quality built into loading", "qualite_et_mdm": "Quality and MDM", "qualite_et_mdm_les_points_sensibles": "Quality & MDM: Sensitive Points", "qualite_et_mdm_integres": "Integrated Quality & MDM", "qualite_et_orchestration": "Quality and orchestration", "qualite_integree_ou_outil_separe": "Integrated Quality or Separate Tool", "qualite_invisible": "Invisible Quality", "qualite_mesuree": "Measured Quality", "qualite_mesuree_et_attachee_a_chaque_enregistrement": "Quality Measured and Attached to Each Record", "qualite_native_vs_outil_tiers_a_connecter": "Native Quality vs. Third-Party Tool to Connect", "quand_chaque_equipe_refait_ses_propres_calculs": "When every team redoes its own calculations", "quand_datavault_builder_peut_convenir": "When Datavault Builder Can Be a Good Fit", "quand_dbt_suffit": "When dbt is enough", "quand_il_est_disponible_et_exploitable_oui_il_est_charge_dans_le": "When it's available and usable, yes: it's loaded into the vault as a full-fledged source. What was overwritten in the old system obviously can't be reconstructed.", "quand_la_hierarchie_produits_est_reorganisee_les_comparaisons_an": "When the product hierarchy is reorganized, year-over-year comparisons break. When a store changes format, network history becomes unreadable. Teams' time goes into manual reconciliation before the first business comment is even made.", "quand_la_stack_externalisee_reste_pertinente": "When the Outsourced Stack Remains Relevant", "quand_les_donnees_grandissent_plus_vite_que_l_organisation": "When data grows faster than the organisation", "quand_les_structures_les_chargements_les_controles_de_qualite_et": "When structures, loads, quality controls and orchestration are generated from the model, adding a source is no longer a project but an iteration. Teams spend their time on business rules — the only part that can't be automated.", "quand_un_chargement_echoue_a_3_h_du_matin_l_equipe_cherche_entre": "When a load fails at 3am, the team has to search across the modeling tool, the orchestrator and the target platform. Three interfaces, three logs, three support channels.", "quand_un_ecart_apparait_en_cloture_la_question_posee_n_est_pas_q": "When a discrepancy appears at closing, the question isn't “which figure is correct” but “why do these two differ.” Without a history of loads or rule versioning, that answer has to be rebuilt by hand, under deadline pressure.", "quand_un_projet_d_entrepot_annonce_a_neuf_mois_en_prend_dix_huit": "When a warehouse project announced at nine months takes eighteen, the instinct is to blame the initial estimate. In most cases, the estimate was accurate on the visible scope: business rules, indicators, reports.", "quand_vaultspeed_peut_etre_le_meilleur_choix": "When VaultSpeed Can Be the Best Choice", "quand_vous_comparez_des_plateformes_data_vault_la_ligne_orchestr": "When you compare Data Vault platforms, the “orchestration” line is often missing from the quote — because it's assumed to be covered by Airflow, dbt or an in-house scheduler. Yet that line very much exists in your budget: it's called half or a full FTE, every year, to maintain a piece of infrastructure that produces no business value.", "quand_wherescape_reste_pertinent": "When WhereScape remains relevant", "quatre_capacites_qui_se_completent_portees_par_des_choix_humains": "Four capabilities that complement each other, driven by human choices that the platform makes explicit and reusable.", "quatre_contextes_une_meme_exigence_de_preuve": "Four Contexts, One Same Proof Requirement", "quatre_problemes_reviennent_systematiquement": "Four Problems Systematically Recur:", "quatre_projets_reels_des_resultats_mesures_avant_et_apres_aucun_": "Four Real Projects. Measured Results Before and After. No Theoretical Figures.", "quatre_projets_quatre_contextes_differents_les_memes_exigences_d": "Four Projects, Four Different Contexts — The Same Rigor Requirements.", "quatre_sessions_a_revoir": "Four Sessions to Review", "quatre_usages_concrets": "Four concrete use cases", "quatre_volets_du_premier_echange_a_la_mise_en_production": "Four stages, from the first conversation to going live", "que_comprend_une_proposition": "What does a quote include?", "que_devient_le_code_deja_ecrit": "What happens to the code already written?", "que_se_passe_t_il_quand_le_modele_source_evolue": "What happens when the source model changes?", "que_se_passe_t_il_si_les_chiffres_different": "What happens if the figures differ?", "que_se_passe_t_il_si_une_source_change_de_structure": "What happens if a source changes structure?", "que_tout_le_monde_peut_expliquer": "that everyone can explain.", "que_vos_equipes_gardent_en_main": "that your teams keep control of.", "que_vous_decouvriez_le_programme_ou_que_vous_soyez_deja_partenai": "Whether you're discovering the program or are already an active partner, everything starts from these three pages.", "quel_accompagnement_dfakto_est_disponible": "What dFakto support is available?", "quel_tarif_s_appliquait_a_cette_zone_en_mars_dernier": "Which rate applied to this zone last March?", "quelle_difference_entre_certification_dv_2_0_et_dv_2_1": "What is the Difference Between DV 2.0 and DV 2.1 Certification?", "quelle_est_la_difference_entre_bevault_et_un_outil_de_reporting": "What is the difference between beVault and a reporting tool?", "quelle_est_la_difference_entre_les_trois_niveaux": "What is the difference between the three levels?", "quelle_source_fait_foi_pour_l_adresse_pour_la_raison_sociale_ces": "Which source is authoritative for the address, for the company name: these rules are explicitly declared and applied, within the scope agreed with you.", "quelle_version_de_postgresql_est_supportee": "Which PostgreSQL Version is Supported?", "quelles_bases_cibles_sont_concernees": "Which target databases are affected?", "quelles_plateformes_cibles_sont_supportees": "Which Target Platforms are Supported?", "quelles_versions_d_oracle_sont_supportees": "Which Oracle versions are supported?", "quelles_versions_de_db2_sont_supportees": "Which DB2 Versions are Supported?", "quelques_jours": "A Few Days", "questions_frequentes": "Frequently Asked Questions", "questions_frequentes_sur_l_offre": "Pricing FAQ", "qui_a_promu_quoi_quand_et_vers_quel_environnement_la_piste_d_aud": "Who promoted what, when and to which environment: the audit trail supports compliance reviews.", "qui_decide_des_definitions_comment_le_modele_evolue_et_comment_d": "Who decides on definitions, how the model evolves and how new sources are integrated after the engagement.", "qui_definit_les_regles": "Who defines the rules?", "qui_delivre_la_certification": "Who Delivers the Certification?", "qui_devrait_participer": "Who Should Attend?", "qui_est_considere_comme_une_pme": "Who is considered an SME?", "qui_fait_quoi": "Who does what", "qui_fait_quoi_concretement": "Who does what, concretely", "qui_gere_les_acces_aux_sources": "Who manages access to the sources?", "qui_grandit_avec_votre_entreprise": "that grows with your business.", "qui_opere_l_infrastructure": "Who operates the infrastructure?", "qui_sommes_nous": "Who we are", "qui_tiennent_en_audit": "that hold up in an audit.", "qui_utilise_le_catalogue_au_quotidien": "Who uses the catalog day to day?", "qui_veulent_garder_le_controle": "that want to stay in control.", "quitter_un_entrepot_legacy": "Leaving a Legacy Warehouse", "raffinement": "Refinement: *\\", "rapport_a_exploiter_manuellement": "Report for manual exploitation", "rapportez_ce_volume_au_nombre_de_sources_encore_a_integrer_sur_v": "Relate this volume to the number of sources yet to be integrated on your roadmap.", "rapports_et_utilisateurs_basculent_une_fois_les_nouveaux_resulta": "Reports and users switch over once the new results are reviewed and accepted by the business. The old pipeline remains available for the agreed period.", "rapports_unifies_pour_7_pays_franchise_et_succursales_architectu": "Unified reports for 7 countries, franchises, and branches. Migration-proof architecture: a new POS connects without rewriting reports.", "rapprochement_multi_source": "Multi-source reconciliation", "rattacher_chaque_source_au_modele_metier": "Map every source to the business model", "raw_vault_et_business_vault": "Raw Vault and Business Vault", "raw_vault_historise_sur_bigquery": "Raw Vault historized on BigQuery", "recette_exclusive": "Exclusive recipe", "reconciliation": "Reconciliation", "reconcilier_des_referentiels_disperses_entre_plusieurs_outils": "Reconcile reference data scattered across several tools.", "reconcilier_et_mesurer": "Reconcile and measure", "reconcilier_les_donnees_de_terrain": "Reconcile field data", "reconcilier_les_identites_entre_crm_erp_et_facturier_et_produire": "Reconcile identities across CRM, ERP, and billing systems, and produce golden records whose definitions are finally accepted by the business.", "reconcilier_les_series_de_consommation": "Reconcile consumption series", "reconcilier_les_sorties_nouvelles_et_existantes": "Reconcile new and existing outputs", "reconstituer_un_indicateur_tel_qu_il_etait_publie_a_sa_date": "Reconstruct a metric exactly as it was published on its date.", "reconstituer_une_chaine_production_expedition": "Reconstruct a production-to-shipping chain", "reconstituer_une_date": "Reconstruct a date", "reconstruction_des_marts": "Mart reconstruction", "reconstruire_les_marts_et_reconcilier": "Rebuild marts and reconcile", "recuperation_de_donnees_via_api_lorsque_le_systeme_source_en_exp": "Data retrieval via API when the source system exposes one, and exposure of prepared data through the beVault API.", "recuperer_et_conserver_l_historique_applicatif_au_lieu_de_le_per": "Recover and preserve application history instead of losing it during migration.", "recuperes_sur_les_taches_manuelles_de_reconciliation": "recovered from manual reconciliation tasks", "redonner_confiance_dans_les_chiffres_une_source_de_verite_unique": "Restore trust in data: a single source of truth, shared definitions, and an auditable history.", "redshift_et_bevault": "Redshift and beVault", "redshift_serverless_est_il_supporte": "Is Redshift Serverless supported?", "redshift_tourne": "Redshift is running.", "reduction_progressive_de_la_dependance_aux_fonctionnalites_propr": "Progressive reduction of reliance on proprietary features", "reduire_la_dependance_oracle_sans_tout_reconstruire": "Reduce Oracle dependency without rebuilding everything", "reduisez_le_travail_data_repetitif": "Reduce repetitive data work", "reference_validee": "Validated reference", "references_clients_affichees_uniquement_lorsqu_elles_sont_valide": "Customer references shown only when validated", "references_disponibles_sur_demande": "References available upon request", "referentiels": "Master data", "referentiels_administratifs_dossiers_et_actes_donnees_budgetaire": "Administrative reference data, files and records, budget and operational data, exports from business applications.", "regles_de_qualite": "Quality rules", "regles_de_qualite_a_l_execution_quarantaine_scoring_et_reconcili": "Runtime Data Quality rules, quarantine, scoring and identity reconciliation are part of the product — no extra tool to acquire and connect.", "regles_de_qualite_versionnees_scoring_par_source_gestion_des_exc": "Versioned quality rules, source-based scoring, exception management, and master data reconciliation — integrated into loading, not branched separately.", "regles_de_qualite_versionnees_scoring_par_source_reconciliation_": "Versioned quality rules, per-source scoring, master data reconciliation, lineage and living documentation.", "regles_de_survivance": "Survivorship rules", "regles_documentees_historisation_et_lignage_de_quoi_reconstituer": "Documented rules, historization and lineage: enough to reconstruct how a metric was produced, and from which data.", "regles_dupliquees": "Duplicated rules", "regles_embarquees_dans_la_plateforme_ou_outil_tiers_a_acheter_et": "Rules embedded in the platform, or a third-party tool to buy and integrate?", "regles_executees_a_chaque_chargement_pas_en_batch_separe": "Rules executed with each load, not in a separate batch", "regles_metier_controles_de_completude_et_de_coherence_reconcilia": "Business rules, completeness and consistency checks, reconciliation with source systems.", "regles_metier_controles_reconciliation_referentiels": "Business rules, controls, reconciliation, master data", "regles_versionnees_scoring_par_source_et_gestion_des_exceptions_": "Versioned rules, source-based scoring, and exception handling integrated into the load process — not a dashboard tacked on afterwards.", "regles_controles_et_auditabilite": "Rules, controls and auditability", "regroupez_la_modelisation_la_qualite_l_orchestration_et_la_docum": "Consolidate modelling, quality, orchestration and documentation capabilities in one platform instead of maintaining disconnected tools and processes.", "rejoignez_notre_ecosysteme_de_partenaire": "Join our partner ecosystem", "rejoindre_l_ecosysteme_bevault_candidature_qualification_et_prem": "Join the beVault ecosystem: application, qualification and first projects supported by our architects.", "releves_controles_et_interventions_issus_de_systemes_distincts_p": "Readings, checks and interventions from separate systems share the same Business Keys once modeled.", "relier_systemes_industriels_et_systemes_de_gestion": "Connect industrial systems and management systems", "remonter_d_une_expedition_a_l_ordre_de_fabrication_et_aux_compos": "Trace back from a shipment to the manufacturing order and the received components, in the state the reference data was in on that date.", "rendre_ces_produits_consommables": "Make these products consumable", "rendre_la_fiabilite_visible": "Make reliability visible", "rendre_la_gouvernance_operationnelle": "Make governance operational", "rendre_la_modelisation_data_vault_accessible_a_toute_votre_equip": "Make Data Vault modelling accessible to your whole team", "rendre_les_indicateurs_explicables": "Make metrics explainable", "rendre_vos_donnees_reellement_exploitables_par_des_modeles_et_de": "Make your data truly exploitable by models and agents: history, lineage, quality, semantics.", "renseignez_votre_email_pour_recevoir_le_document_nous_vous_enver": "Enter your email to receive the document. We will also send you updates if the content evolves.", "repartition_des_roles": "Division of roles", "repartition_entre_vos_serveurs_et_un_environnement_cloud_selon_l": "Distribution between your servers and a cloud environment, depending on component sensitivity and operational constraints.", "repere": "Benchmark", "replays_de_nos_sessions_en_direct_sur_le_data_vault_et_la_qualit": "Replays of our live sessions on Data Vault and data quality.", "repondre_a_des_questions_sur_votre_modele_de_donnees": "Answer questions about your data model.", "repondre_aux_exigences_reglementaires_bcbs_239_rgpd_solvency_ave": "Meet regulatory requirements — BCBS 239, GDPR, Solvency — with end-to-end traceability, without endless documentation projects.", "repondre_sans_reconstituer": "Answer without rebuilding", "reponses_chiffrees_sur_les_delais_et_le_cout_total": "Quantified answers on deadlines and total cost", "reporting_dependant_de_la_base_source": "Reporting dependent on the source database", "reporting_fiable_et_auditable_pour_la_direction": "Reliable and auditable reporting for management", "reprendre_une_base_existante_sans_repartir_de_zero": "Build on an existing base without starting from scratch.", "reprise_sur_incident": "Incident recovery", "republique_francaise": "French Republic", "request_access": "request access", "requete_utilisateur": "User query: *\\", "reseaux_de_points_de_vente_produits_ventes": "Point-of-sale networks, products, sales", "reseaux_consommation_actifs_techniques": "Networks, consumption, technical assets", "reseaux_consommations_et_actifs": "Networks, consumption and assets", "reserver_la_demo_comparative": "Book a comparative demo", "reserver_un_creneau": "Book a slot", "reserver_une_demo": "book a demo", "reserver_une_demo_2": "Book a demo", "reserver_une_demo_bevault": "Book a beVault demo", "resoudre": "Solve", "ressources": "Resources", "ressources_comparatifs": "Resources — Comparisons", "ressources_2": "Resources &", "ressources_insights": "Resources & insights.", "ressources_en_ligne": "Online resources", "reste_t_elle_valable_si_le_systeme_source_est_remplace_demain_si": "Is it still valid if the source system is replaced tomorrow? If not, it's technical.", "restituer": "Deliver", "restitution_ce_qu_on_nous_demande": "Consumption: what we're asked", "resultat_chaque_nouveau_besoin_un_tableau_de_bord_un_indicateur_": "The result: every new need — a dashboard, an executive metric, a first AI project — starts over with the same integration work, and ends with numbers nobody can really defend.", "resultat_des_controles_et_date_du_dernier_chargement_accompagnen": "Control results and the date of the last load accompany the figure: users know what they're relying on before commenting on it.", "resultats": "Results", "resultats_clients": "Customer results", "resultats_des_controles_par_domaine_volume_d_exceptions_et_delai": "Control results by domain, exception volumes and processing time: governance is managed with metrics, like any other activity.", "retail_biens_de_consommation": "Retail & consumer goods", "retail_restauration_7_pays": "Retail & catering, 7 countries", "retail_7_pays": "Retail, 7 countries", "retour_a_l_accueil": "Back to home", "retour_a_la_serie": "Back to series", "retrouver_l_etat_du_reseau_des_zones_et_des_tarifs_applicables_a": "Retrieve the state of the network, the zones and the rates applicable at a given period, with no manual reconstruction.", "retrouver_la_regle_appliquee_avant_une_reforme_une_fois_la_table": "Retrieving the rule that applied before a reform, once the source table has been overwritten.", "retrouver_comprendre_expliquer": "Retrieve, understand, explain", "reversibilite": "Reversibility", "revoir_vos_exigences_de_gouvernance": "Review your governance requirements", "roles": "Roles", "roles_deroule_de_projet_et_livrables": "Roles, project timeline and deliverables", "rue_saint_hubert_17": "Rue Saint Hubert 17", "s_inscrire_aux_release_notes": "Subscribe to release notes", "sa_structure_modulaire_convient_aux_petits_comme_aux_grands_mode": "The modular structure works for small and large data models and supports parallel processing across independent data flows where the target architecture allows it.", "saas_mutualise_impose_ou_vpc_dedie_et_on_premises_reellement_sup": "Forced shared SaaS, or truly supported dedicated VPC and on-premises?", "sans_ce_contrat_chaque_developpeur_en_reinvente_une_version_loca": "Without this contract, every developer reinvents their own local version. Three pipelines, three definitions of revenue — and a management committee that spends more time arbitrating discrepancies than making decisions.", "sans_changer_les_equipes": "Without changing the teams.", "sans_couche_de_restitution_gouvernee_la_logique_de_calcul_se_rec": "Without a governed reporting layer, calculation logic gets rebuilt in every BI tool. Two reports then show two different figures, and no one knows which one is authoritative.", "sans_dependance_proprietaire": "No proprietary lock-in.", "sans_eteindre_la_lumiere": "without turning off the lights.", "sans_historisation_les_donnees_sont_ecrasees_a_chaque_chargement": "Without historization, data is overwritten with every load. Reconstructing the state of the data three months ago becomes impossible.", "sans_historisation_un_rapport_rejoue_le_mois_suivant_donne_un_re": "Without historization, a report re-run the following month yields a different result — impossible to know which was correct.", "sans_jargon_inutile": "without needless jargon.", "sans_le_reconstruire": "without rebuilding it.", "sans_repartir_de_zero": "without starting from scratch.", "savoir_ce_qu_une_modification_casse_en_aval_prend_des_jours_d_in": "Knowing what a change breaks downstream takes days of manual investigation. Built-in lineage answers in seconds.", "savoir_ce_qui_s_est_passe_ne_suffit_pas_il_faut_savoir_dans_quel": "Knowing what happened isn't enough. You need to know what state the network was in that day: which zones, which rates, which equipment was in service.", "scale_free": "Scale Free", "scheduler_workers_base_de_metadonnees_montees_de_version_securit": "Scheduler, workers, metadata database, upgrades, security: a self-managed orchestrator is a product in its own right that someone has to operate.", "schema_bevault_des_systemes_sources_vers_bevault_puis_vers_les_s": "beVault diagram: from source systems to beVault, then to AI systems and users", "schema_d_architecture": "Architecture diagram", "schema_d_architecture_de_donnees_des_sources_jusqu_aux_usages": "Data architecture diagram, from sources to uses", "score_de_qualite_rattache_au_lignage_complet": "Quality score linked to full lineage", "scores_classifications_resultats_produits_par_un_modele_peuvent_": "Scores, classifications and results produced by a model can be fed back into the vault like any other source: historized, dated, and traced to their origin. You then know exactly which result was produced, when, and from which data — making a review possible.", "scripts_d_insertion_gestion_des_cles_de_hachage_detection_des_ch": "Insert scripts, hash key management, change detection, recovery: several days per source, redone with every change. beVault generates it.", "scripts_sans_proprietaire": "Scripts without owner", "se_pilote_dans_la_duree": "is managed over time.", "secteur_prioritaire": "Priority sector", "secteur_public": "Public sector", "secteur_public_finance_assurance_retail_mobilite": "Public sector, finance, insurance, retail, mobility…", "securite_conformite": "Security & compliance", "securite_de_l_information_et_gouvernance": "Information security and governance", "see_a_demo": "Book a demo", "see_a_demo_first": "see a demo first", "see_if_it_applies_to_your_context": "see if it applies to your context", "see_the_platform_in_action": "see the platform in action", "see_what_it_looks_like_for_your_use_case": "see what it looks like for your use case", "selon_leurs_acces_les_agents_peuvent": "Depending on their access, agents can:", "semantique_metier_explicite_exploitable_par_les_agents": "Explicit business semantics, usable by agents", "senior_data_analyst_dfakto": "Senior Data Analyst, dFakto", "sens_metier": "Business meaning", "separation_des_environnements_de_travail_et_de_production_aligne": "Separation of working and production environments, aligned with your existing practices.", "serie_7_articles": "Series · 7 articles", "serie_ia_article_1_7": "AI Series · Article 1/7", "serie_ia_article_2_7": "AI Series · Article 2/7", "serie_ia_article_3_7": "AI Series · Article 3/7", "serie_ia_article_4_7": "AI Series · Article 4/7", "serie_ia_article_5_7": "AI Series · Article 5/7", "serie_ia_article_6_7": "AI Series · Article 6/7", "serie_ia_article_7_7": "AI Series · Article 7/7", "series_de_comptage_referentiels_d_actifs_points_de_livraison_int": "Counting series, asset registries, delivery points, field interventions: data keeps coming in continuously, and a significant share of it is revised afterward.", "serveur_mcp": "MCP Server", "serveurs_mcp": "MCP Servers", "serveurs_mcp_l_architecture_portable_pour_vos_agents_data_vault": "MCP Servers: the portable architecture for your Data Vault agents", "services_adaptes_et_qualification_du_projet": "Tailored services and qualification", "services_data": "Data Services", "services_data_dfakto": "dFakto Data Services", "services_financiers": "Financial services", "sessions_produit_acces_a_un_environnement_de_travail_et_document": "Product sessions, access to a working environment and documentation so your consultants become self-sufficient on metaVault, States and Verify.", "shortcut_icon": "shortcut icon", "si_la_valeur_corrigee_efface_la_valeur_publiee_l_ecart_entre_deu": "If a corrected value overwrites the published value, the gap between two reported states becomes impossible to explain. If replacing a piece of equipment erases the old one, analyzing a past period loses its context.", "si_une_regle_de_survivance_change_dans_six_mois_elle_est_modifie": "If a survivorship rule changes in six months, it is updated and the outputs are regenerated: the original data is still there, intact and timestamped. This is what allows a decision to be revised without rebuilding the reference model.", "si_vos_equipes_utilisent_deja_l_outil_depuis_des_annees_que_vos_": "If your teams have already used the tool for years, your design patterns are stable and the warehouse isn't strictly Data Vault, changing foundations has no immediate benefit. The topic becomes relevant when maintaining the pipeline — orchestration, quality, governance — weighs more than the build itself.", "si_votre_besoin_se_limite_a_des_transformations_analytiques_au_d": "If your need is limited to analytical transformations on top of an already clean foundation, without a requirement for full historization or point-in-time audit, dbt gets the job done with a small team. beVault becomes relevant when historization, traceability and compliance with the Data Vault standard become requirements, not good intentions.", "si_votre_organisation_dispose_deja_d_une_plateforme_d_orchestrat": "If your organization already has a robust orchestration platform and a team operating it daily, if your quality governance is already tooled elsewhere and suits you, and if you are only looking to accelerate Data Vault code generation, then a specialized generator will meet your needs.", "si_votre_perimetre_se_limite_a_modeliser_et_charger_un_data_vaul": "If your scope is limited to modeling and loading a Data Vault, if data quality is already handled by a team and tools that satisfy you, and if daily operations are handled by a dedicated infrastructure team, Datavault Builder will fulfill its function.", "si_vous_construisez_un_produit_ia_un_portail_donnees_ou_une_appl": "If you're building an AI product, a data portal or an analytics application, beVault is the foundation that makes your data citable, auditable and retrainable. AI agents are only as reliable as the data they rely on.", "situation": "Location", "six_familles_de_donnees": "Six data families", "six_situations": "Six situations.", "six_usages_concrets": "Six concrete use cases", "size_3_5_transition_transform_duration_200": "size-3.5 transition-transform duration-200", "size_7_transition_colors_duration_500": "size-7 transition-colors duration-500", "snowflake": "Snowflake", "snowflake_databricks": "Snowflake / Databricks", "snowflake_et_bevault": "Snowflake and beVault", "snowflake_vous_donne_la_puissance": "Snowflake gives you the power.", "snowflake_amazon_redshift_microsoft_sql_server_et_postgresql_son": "Snowflake, Amazon Redshift, Microsoft SQL Server and PostgreSQL are supported today. Databricks, Microsoft Fabric and Google BigQuery are coming soon.", "snowflake_amazon_redshift_microsoft_sql_server_et_postgresql_son_2": "Snowflake, Amazon Redshift, Microsoft SQL Server and PostgreSQL are supported today. Databricks, Microsoft Fabric and Google BigQuery are coming soon.", "snowflake_amazon_redshift_microsoft_sql_server_et_postgresql_son_3": "Snowflake, Amazon Redshift, Microsoft SQL Server, and PostgreSQL are supported today. Databricks, Microsoft Fabric, and Google BigQuery are coming soon. The status indicated on each card specifies what is available.", "snowflake_amazon_redshift_microsoft_sql_server_et_postgresql_par": "Snowflake, Amazon Redshift, Microsoft SQL Server and PostgreSQL. Tell us about your target stack to learn the extension timeline.", "snowflake_amazon_redshift_microsoft_sql_server_postgresql_et_ibm": "Snowflake, Amazon Redshift, Microsoft SQL Server, PostgreSQL and IBM db2, with code generation optimized by target.", "snowflake_bigquery_redshift_databricks_sql_server": "Snowflake, BigQuery, Amazon Redshift, Databricks, SQL Server…", "socle_de_donnees_exploitable_par_l_ia": "A data foundation AI can work with", "solutions": "Solutions", "solutions_industries": "Solutions — Industries", "solutions_pour_les_pme": "Solutions — For SMEs", "something_went_wrong_on_our_end_you_can_try_refreshing_or_head_b": "Something went wrong on our end. You can try refreshing or head back home.", "sommes_nous_dependants_d_aws": "Are we dependent on AWS?", "sortie_possible_le_code_genere_vous_appartient": "Possible outcome: the generated code belongs to you", "sorties_documentees_et_consommables_par_vos_outils_de_bi_vos_uti": "Documented outputs consumable by your BI tools, your users and authorized agents in your environment.", "sorties_documentees_pour_la_bi_le_reporting_et_l_ia": "Documented outputs for BI, reporting and AI", "sorties_et_consommation": "Outputs and consumption", "sortir_d_un_entrepot_legacy_ou_d_un_empilement_de_scripts_sans_i": "Moving off a legacy warehouse or a stack of scripts without interrupting existing reports, by switching over domain by domain.", "source_de_verite": "Source of truth", "sources_multiples_equipe_data_reduite_besoins_qui_evoluent_vite_": "Multiple sources, small data team, rapidly evolving needs: a dedicated page describes how to start with a controlled scope and expand later.", "sources_entrepots_et_traitements_existants_points_de_rupture_dep": "Existing sources, warehouses and processes, breaking points, dependencies on individuals, technical debt and blind spots.", "sources_erp_historisation_plateformes_cibles": "Sources, ERP, historization, target platforms", "sources_plateforme_cible_taille_de_l_equipe_contraintes_reglemen": "Sources, target platform, team size, regulatory constraints and main blocking point. This step determines everything else.", "souscription_sinistres_reporting_prudentiel": "Underwriting, claims, prudential reporting", "souscriptions_avenants_et_resiliations_conserves_comme_une_suite": "Policy inceptions, endorsements and cancellations kept as a sequence of dated states, viewable at any past date.", "souverainete": "Sovereignty", "souverainete_des_donnees": "Data sovereignty", "souverainete_des_donnees_marches_publics_contraintes_d_audit_et_": "Data sovereignty, public procurement, audit constraints and legacy environments: this is the context in which beVault was built and hardened.", "soyons_honnetes": "Let's be honest", "sql_adapte_a_oracle_pl_sql_et_structures_data_vault_2_0_correcte": "SQL adapted to Oracle — correct PL/SQL and Data Vault 2.0 structures", "sql_bigquery_natif_partitionnement_et_clustering_generes_automat": "Native SQL BigQuery — automatic partitioning and clustering generated", "sql_db2_natif_genere_adapte_aux_specificites_de_la_plateforme": "Native DB2 SQL generated — adapted to platform specifics", "sql_et_macros_ecrits_et_maintenus_par_l_equipe": "SQL and macros written and maintained by the team", "sql_optimise_pour_bigquery": "SQL optimized for BigQuery", "sql_postgresql_natif_genere_postgresql_version_15_ou_superieure": "Native PostgreSQL SQL generated — PostgreSQL version 15 or higher", "sql_server": "SQL Server", "sql_server_et_bevault": "SQL Server and beVault", "standard": "Standard", "standard_certifie": "Certified standard", "starter": "Starter", "states": "States", "states_la_definition_des_workflows": "States — the workflow definition layer", "states_est_fourni_avec_un_ensemble_de_workers_generiques_et_perm": "States comes with a set of generic Workers, and also supports custom Worker creation.", "states_est_l_orchestrateur_interne_de_bevault_il_pilote_vos_flux": "States is the internal orchestrator of beVault. It manages your data pipelines, from initial extraction to final delivery into your business intelligence tools.", "states_s_appuie_sur_l_amazon_states_language_asl_un_langage_base": "States leverages the Amazon States Language (ASL), a JSON-based language designed for creating workflows called state machines. From simple linear workflows to complex branching scenarios, States provides the flexibility and control you need.", "states_s_integre_a_de_petits_services_web_appeles_workers_ces_co": "States integrates with small web services called Workers. These specialised components execute specific tasks such as making HTTP calls or querying databases.", "states_l_orchestrateur_de_bevault_s_appuie_sur_l_amazon_states_l": "States, beVault's orchestrator, is built on the Amazon States Language, the state machine language of AWS Step Functions. Your workflows fit naturally into your AWS environment.", "stationnement_transport_services_aux_citoyens": "Parking, transport, citizen services", "stockage_et_calcul": "Storage and compute", "stockage_moteur_de_calcul_securite_d_acces_aux_donnees_elasticit": "Storage, compute engine, data access security, elasticity. This is where your tables live and your queries run.", "stocks": "Inventory", "stocks_logistique": "Inventory & logistics", "strategie_architecture": "Strategy & architecture", "strategie_architecture_data": "Data Strategy & Architecture", "strategie_data": "Data strategy", "strategie_et_architecture_implementation_formation_et_transfert_": "Strategy and architecture, implementation, training and skills transfer, long-term support, model evolution and integration of new sources: each strand can be used on its own, whenever it becomes useful.", "strategie_et_architecture_implementation_formation_transfert_de_": "Strategy and architecture, implementation, training, skills transfer, support and evolution of the model. These services are optional and scaled as needed.", "structure_essentielle": "Essential structure:", "structurer_et_maitriser_les_couts_de_warehouse": "Structure and control warehouse costs", "structurer_les_donnees_critiques_mainframe": "Structure critical mainframe data", "structurer_vos_donnees_par_etapes_sans_construire_une_architectu": "Structure your data in stages, without building a disproportionate architecture.", "structurer_votre_plateforme_snowflake_avec_un_data_vault_et_mait": "Structure your Snowflake platform with a Data Vault and master the compute bill from the first year.", "structures_data_vault_generees_sur_delta_lake": "Data Vault structures generated on Delta Lake", "success_stories": "Success stories", "success_story_administration_publique": "Success story — Public administration", "success_story_retail_restauration": "Success story — Retail & food service", "success_story_services_financiers": "Success story — Financial services", "suite_a_la_simplification_des_annulations_de_redevances": "following the simplification of royalty cancellations", "suivi_des_executions_et_diagnostic_des_echecs": "Execution monitoring and failure diagnostics", "suivre_la_complexite": "Scale as complexity grows", "suivre_les_changements": "Track changes", "suivre_les_corrections": "Track corrections", "suivre_les_referentiels_physiques": "Track physical registries", "sujets_traites": "Topics covered", "summary_large_image": "summary_large_image", "supervision_sauvegardes_et_procedures_de_reprise_assurees_par_vo": "Monitoring, backups and recovery procedures handled by your teams, documented at go-live.", "support": "Support", "support_evolution": "Support & evolution", "support_a_l_exploitation": "Operational support", "support_et_conditions_definis_selon_le_projet": "Support and conditions defined according to the project", "support_et_evolution_dans_la_duree": "Ongoing support and evolution", "support_partenaire_dedie": "Dedicated partner support", "support_technique_dedie_pendant_les_phases_de_deploiement": "Dedicated technical support during deployment phases", "support_evolution_du_modele_et_nouvelles_sources": "Support, model evolution and new sources", "sur_chaque_satellite_comparez_le_nombre_de_lignes_au_nombre_de_c": "On each satellite, compare the row count to the number of distinct (key, content hash) pairs. A large gap signals rows that add no new information.", "sur_la_couche_data_vault_et_les_marts_bevault_prend_en_charge_la": "On the Data Vault layer and the marts, beVault handles generation and orchestration. If dbt or Dataform manage other GCP flows, the two coexist.", "sur_la_couche_data_vault_et_les_marts_oui_la_generation_de_code_": "On the Data Vault layer and the marts, yes: code generation and orchestration are native. If dbt is used elsewhere in your organization, the two coexist without difficulty.", "sur_laquelle_vos_projets_ia_peuvent_s_appuyer": "that your AI projects can rely on.", "sur_un_domaine_cadre_nos_clients_obtiennent_un_premier_chargemen": "Within a defined scope, our clients get a first historical load and an exploitable mart in a few weeks.", "sur_un_projet_manuel_le_temps_passe_a_modeliser_et_a_comprendre_": "On a manual project, time spent modeling and understanding the business is the minority. Most of it goes into writing and maintaining code.", "sur_une_base_historisee_et_reconciliee": "on a historized, reconciled foundation.", "sur_une_chaine_de_faits_continue": "on a continuous chain of facts.", "surveiller_revoir_et_ameliorer_en_continu_notre_posture_de_secur": "Continuously monitoring, reviewing, and improving our security posture.", "synchroniser_les_metadonnees_et_la_documentation_avec_votre_cata": "Synchronize metadata and documentation with your data catalog.", "system_prompt_utilise": "System prompt used:", "t_sql_natif_genere_pas_de_couche_d_abstraction_supplementaire": "Native T-SQL generated — no additional abstraction layer", "tableau_de_bord_qualite_des_donnees_scores_par_concept_et_par_so": "Data quality dashboard: scores by concept and source, issues by criticality and scores by owner", "tableaux_de_bord_pour_equipes_terrain_et_direction": "dashboards for field teams and management", "taches_repetitives_specifiques_equipe_debutante": "Specific repetitive tasks, novice team", "taille_d_organisation": "Organisation size", "talk_to_an_architect": "talk to an architect", "talk_to_an_expert": "talk to an expert", "tant_que_ces_correspondances_vivent_dans_des_fichiers_de_rapproc": "As long as these mappings live in reconciliation files, it's impossible to trace a batch end to end, and a simple operational question — where did this component come from, when did it leave — becomes an investigation.", "target_language_value_function_buildindex_fr_record": "target-language value. */ function buildIndex(fr: Record", "tarification_gestion_des_sinistres_et_reporting_s_appuient_sur_l": "Pricing, claims management and reporting all rely on the same base of dated facts.", "tarifs": "Pricing", "technologie_de_conteneurisation_et_de_deploiement": "Containerization and deployment technology", "technologie_de_deploiement": "Deployment technology", "telecharger": "Download", "telecharger_le_livre_blanc": "Download the white paper", "telecharger_notre_livre_blanc": "Download our white paper", "telechargez_notre_livre_blanc_sur_bevault_et_l_ia_pour_les_pme_e": "Download our white paper on beVault and AI for SMEs and public organizations.", "temps_consacre_aux_incidents_de_chargement_aux_corrections_de_co": "Time spent on load incidents, code fixes and orchestrator maintenance — costs the platform absorbs.", "temps_reel": "Real-time", "tester_a_nouveau": "Test again", "testez_les_deux_sur_le_meme_cas": "Test both on the same use case", "tests_et_recette": "Testing and UAT", "tests_impossibles": "Tests impossible", "tests_unitaires_et_de_schema": "Unit and schema tests", "the_synergies_of_ai_data_vault": "The synergies of AI & Data Vault", "this_page_didn_t_load": "This page didn't load", "time_travel_n_est_pas_une_strategie_d_historisation_sa_fenetre_e": "Time Travel isn't a historization strategy: its window is short and its retention cost is high. Business history needs to be modeled.", "tirer_parti_de_l_ecosysteme_aws_nativement": "Leverage the AWS ecosystem natively", "tous_les_articles": "All articles", "tous_les_business_cases": "All business cases", "tous_les_cas_d_usage": "All use cases", "tout_ce_qu_il_faut_pour": "Everything it takes for", "tout_ce_que_vous_decrivez_dans_metavault_est_stocke_sous_forme_d": "Everything you describe in metaVault is stored as versioned metadata. A change can be reviewed, compared and promoted like any software change.", "tout_voir": "See all", "toute_la_mecanique_du_data_vault_tient_dans_une_idee_les_trois_c": "The entire mechanics of the Data Vault rest on one idea: the three components of a piece of business data don't change at the same pace. A customer's identifier rarely changes. Their relationships with contracts, branches or orders change regularly. Their descriptive attributes change constantly.", "toutes_les_capacites_du_niveau_standard": "All Standard capabilities", "toutes_les_capacites_du_niveau_starter": "All Starter capabilities", "toutes_les_sources_alimentent_un_entrepot_unique_chaque_evenemen": "All sources feed a single warehouse. Each parking event is historized with its context — zone, parking meter, payment channel, status.", "tracabilite": "Traceability", "tracabilite_d_audit": "Audit traceability", "tracer_un_evenement_operationnel": "Trace an operational event", "traduire_les_politiques_en_controles": "Translate policies into controls", "traitement_des_anomalies": "Anomaly management", "trajectoire": "Trajectory", "transactions_releves_de_capteurs_controles_interventions_les_flu": "Transactions, sensor readings, checks, interventions: data flows arrive continuously, produced by different systems and sometimes by different providers.", "transfert_de_competences": "Knowledge transfer", "travaillez_vous_hors_d_europe": "Do you work outside Europe?", "tres_peu_d_editeurs_du_marche_sont_certifies": "Very few vendors on the market are certified", "trois_basculements_concrets": "Three concrete shifts", "trois_cas_d_usage": "Three use cases", "trois_composants_bevault_utilises_par_vos_equipes": "Three beVault components, used by your teams", "trois_consequences_reviennent_systematiquement_les_anomalies_ne_": "Three consequences come up systematically: anomalies are only discovered by the end user, no one can reconstruct the state of the data at a past date, and no one specifically owns responsibility for a domain.", "trois_contraintes_propres_aux_organisations_publiques": "Three constraints specific to public-sector organizations", "trois_entrees": "Three entry points", "trois_facons_d_interagir": "Three ways to interact", "trois_niveaux_de_perimetre_sans_grille_tarifaire_publique": "Three scope levels, no public price list.", "trois_objets_une_regle_d_or_separer_les_cles_les_relations_et_le": "Three objects, one golden rule: separate keys, relationships and context. The clear guide to Data Vault 2.0 mechanics.", "trois_pages_a_lire_si_ce_cadre_est_le_votre": "Three pages to read if this situation applies to you", "trois_pages_pour_aller_plus_loin": "Three pages to go further", "trois_points_de_depart": "Three starting points", "trois_rapports_trois_reponses": "Three reports, three answers", "try_again": "Try again", "twitter_card": "twitter:card", "twitter_description": "twitter:description", "twitter_title": "twitter:title", "typeof_v_boolean_v": "typeof v === \"boolean\" ? ( v ? (", "un_accompagnement_adapte_a_votre_environnement_data_au_perimetre": "Support adapted to your data environment, implementation scope and level of autonomy.", "un_accompagnement_adapte_a_votre_trajectoire": "Support tailored to your trajectory", "un_alignement_avec_les_attentes_de_securite_des_entreprises_des_": "Alignment with enterprise, regulatory, and contractual security expectations.", "un_analyste_metier_decrit_ses_besoins_en_langage_naturel_l_agent": "A business analyst describes their needs in natural language → the agent generates production-ready SQL", "un_assistant_branche_sur_des_extractions_non_gouvernees_produit_": "An assistant connected to ungoverned extracts produces plausible but indefensible answers. In an executive committee, a figure nobody can source is worth less than no figure at all.", "un_assistant_qui_recommande_une_destination_doit_pouvoir_justifi": "An assistant that recommends a destination must be able to justify its answer: which source, which date, which definition. That's exactly what a Data Vault model provides natively — every record carries its origin and timestamp.", "un_audit_lance_en_reunion_se_resout_en_secondes_l_etat_des_donne": "An audit request raised in a meeting is resolved in seconds: the state of the data at any past date can be reconstructed.", "un_audit_reglementaire_soutenable": "A sustainable regulatory audit", "un_canal_de_support_partenaire_pour_les_questions_de_deploiement": "A dedicated partner support channel for questions on deployment, modeling and performance.", "un_chiffre_de_ventes_discutable_sur_le_fond_plus_jamais_sur_sa_p": "A sales figure may still be questioned on substance, but never again on where it came from.", "un_chiffre_publie_reste_reconstituable_avec_sa_source_sa_date_et": "A published figure remains traceable, with its source, its date and the rule that produced it.", "un_chiffre_qu_on_peut_defendre": "A figure you can defend", "un_chiffre_qu_on_peut_expliquer_vaut_mieux_qu_un_chiffre_simplem": "A figure you can explain is worth more than a figure that's simply available.", "un_chiffre_que_l_on_peut_expliquer": "A figure you can explain", "un_client_reste_le_meme_client": "A customer stays the same customer", "un_code_genere_de_maniere_deterministe_se_teste_une_fois_pour_to": "Deterministically generated code is tested once and for all. Copy-paste regressions disappear.", "un_contrat_vit_dix_ans_un_sinistre_se_regle_sur_plusieurs_exerci": "A policy lives for ten years, a claim settles over several fiscal years, and the systems handling them change in the meantime. The challenge isn't centralizing everything: it's preserving the state of each object at every point in time.", "un_data_vault_mal_implemente_ne_se_voit_pas_la_premiere_annee_il": "A poorly implemented Data Vault doesn't show in the first year. It's paid for in the third, when recovering the history becomes impossible.", "un_data_vault_sur_dbt_fonctionne_la_question_est_de_savoir_qui_e": "A Data Vault on dbt works. The question is who writes, tests and maintains the hundreds of repetitive models it requires.", "un_data_vault_sur_oracle_sans_rupture": "A Data Vault on Oracle, seamlessly", "un_declenchement_explicite_entre_les_deux_arrete_lors_du_cadrage": "An explicit trigger between the two, defined during scoping according to the chosen direction and your operating practices.", "un_defaut_qui_ne_casse_rien_et_c_est_bien_le_probleme": "A flaw that breaks nothing — and that's exactly the problem", "un_delai_de_livraison_previsible_et_defendable_en_interne": "A delivery timeline that's predictable and defensible internally", "un_domaine_ou_un_cas_d_usage_prioritaire_celui_ou_la_donnee_est_": "A priority domain or use case: the one where data is most disputed, or the one blocking a decision or a concrete use.", "un_entrepot_de_donnees_vit_nouvelles_sources_nouvelles_regles_no": "A data warehouse lives: new sources, new rules, new marts. The risk isn't modeling, it's deploying a change to production without knowing what it breaks. beVault versions the metamodel and replays promotions in a controlled way, environment by environment.", "un_entrepot_qui_a_dix_ans_porte_de_la_dette_technique_scripts_em": "A ten-year-old warehouse carries technical debt: stacked scripts, outdated documentation, poorly understood dependencies. It also carries the organization's memory and the calculation rules no one wants to lose.", "un_entrepot_techniquement_irreprochable_ne_sert_a_rien_si_le_met": "A technically flawless warehouse is useless if the business distrusts the numbers. beVault allows you to declare controls on historized and multi-system data, report anomalies in actionable lists, and improve quality through corrections made in source systems.", "un_entrepot_unique": "A single warehouse", "un_hash_diff_calcule_sur_un_ensemble_de_colonnes_incluant_un_hor": "A hash diff calculated on a set of columns including a technical timestamp, a batch number or a counter: each execution produces a different fingerprint.", "un_historique_a_preserver": "A history to preserve", "un_historique_consultable_une_reponse_tracable_et_un_systeme_de_": "A searchable history, a traceable answer, and one less system to maintain.", "un_historique_continu_de_la_chaine_conserve_meme_quand_les_syste": "A continuous history of the chain, preserved even when the systems carrying it change.", "un_hub_ne_contient_qu_une_chose_la_liste_unique_des_cles_metier_": "A hub contains only one thing: the unique list of business keys for a concept — a customer number, a contract identifier, a product code. It also carries the source of origin and the date of first appearance.", "un_ingenieur_decrit_un_modele_l_agent_cree_tous_les_hubs_liens_s": "An engineer describes a model → the agent creates all hubs, links, satellites, and mappings in 2 minutes (instead of an hour)", "un_interlocuteur_unique": "A single point of contact", "un_jeu_de_donnees_destine_a_un_usage_precis_reporting_applicatio": "A dataset intended for a specific use — reporting, application, training — is exposed with its definition, scope and lineage.", "un_langage_metier_partage": "Shared business language", "un_lignage_genere_a_partir_de_ce_que": "A Data Lineage generated from what", "un_link_materialise_l_association_entre_deux_hubs_ou_plus_ce_cli": "A link materializes the association between two or more hubs: this customer holds this contract, this order concerns this product delivered to this address. It only stores the keys involved and load metadata.", "un_message_avec_votre_contexte_suffit_nous_revenons_vers_vous_so": "A message with your context is enough: we get back to you within one business day with a time slot and the name of the contact.", "un_modele_conforme_et_du_sql_standard_signifient_que_vous_pouvez": "A compliant model and standard SQL mean you can switch tools. That's precisely the guarantee non-certified vendors can't offer.", "un_modele_maitre_relie_tous_les_systemes_legacy_pos_nouveaux_ter": "A master model connects all systems — legacy POS, new cloud terminals, staffing. When Exki changes POS in one country, data follows without rewriting reports.", "un_modele_maitre_tous_les_systemes": "One master model, all systems", "un_modele_metier_partage": "A shared business model", "un_modele_ml_entraine_aujourd_hui_ne_peut_pas_etre_recree_a_l_id": "An ML model trained today can't be recreated identically six months from now. Regulatory compliance becomes a problem.", "un_modele_n_est_pas_un_schema_decoratif_valide_en_comite_c_est_u": "A model is not a decorative diagram validated in committee. It is a contract: it states what a customer is, what identifies them in a stable way, how a contract is linked to that customer, and where the descriptive attributes that change over time land.", "un_modele_oriente_metier_rend_les_concepts_et_leurs_relations_co": "A business-oriented model makes concepts and relationships understandable to both business and technical teams.", "un_modele_predictif_a_besoin_de_l_etat_des_donnees_au_moment_de_": "A predictive model needs the state of the data at the moment of a past decision, not its current state. The Data Vault historizes every change by design.", "un_numero_de_facture_n_est_unique_qu_a_l_interieur_d_une_entite_": "An invoice number is only unique within a legal entity; a product code is only unique within a catalog. Omitting scope produces silent collisions that surface months later as incorrect aggregates.", "un_objet_metier_a_la_fois": "One business object at a time", "un_ordre_de_colonnes_non_fige_dans_la_concatenation_avant_hachag": "Column order not fixed in the concatenation before hashing.", "un_outil_de_reporting_affiche_des_donnees_bevault_construit_hist": "A reporting tool displays data; beVault builds, historises, controls and documents the foundation on which this data rests, then feeds it into defined outputs.", "un_outil_non_certifie_est_il_forcement_mauvais": "Is an uncertified tool necessarily bad?", "un_outil_non_conforme_produit_un_entrepot_qui_ressemble_a_un_dat": "A non-compliant tool produces a warehouse that resembles a Data Vault without having its properties. Reconstruction, when it occurs, costs several person-years.", "un_parallelisme_mal_regle_multiplie_la_facture_cloud_bevault_cal": "Poorly tuned parallelism multiplies your cloud bill. beVault computes the optimal scheduling from the model, with no manual tuning.", "un_parcours_reproductible_du_modele_metier_aux_donnees_exploitab": "One repeatable path from business model to usable data", "un_partenariat_qui_relie_les_agents_ia_de_dust_au_socle_de_donne": "A partnership connecting Dust's AI agents to beVault's governed data foundation: traceable answers, not hallucinations.", "un_paysage_applicatif_pas_une_source_unique": "An application landscape, not a single source", "un_premier_cas_d_usage_est_cadre_une_equipe_extrait_des_donnees_": "A first use case is scoped. A team extracts data from three systems, cleans it on its own, produces a usable dataset — then moves to the next one, and starts over. None of that work is reusable.", "un_premier_domaine_se_livre_vite_dans_les_deux_cas_l_ecart_appar": "A first domain ships quickly either way. The gap appears at the tenth domain, when the number of objects to maintain exceeds what a team can track by hand: that's where using the model as the source of truth changes the project's economics.", "un_programme_construit_pour": "A program built for", "un_projet_data_ne_depend_pas_uniquement_des_choix_techniques_il_": "A data project doesn't depend only on technical choices. It moves forward when it's clear who decides, who builds, and who takes over afterward.", "un_rapport_d_anomalies_sans_circuit_de_traitement_ne_produit_auc": "An anomaly report with no resolution workflow produces no correction. Quality stays a metric, never an action.", "un_raw_vault_structure_et_historise": "A structured and historized Raw Vault", "un_rechargement_complet_de_la_source_traite_comme_un_delta_sans_": "A full reload of the source treated as a delta, without comparison to the last known state.", "un_referentiel_de_contrepartie_qui_change_un_instrument_reclasse": "A counterparty reference that changes, an instrument reclassified, a retroactive correction: successive states coexist instead of overwriting each other.", "un_retard_une_non_conformite_ou_une_rupture_peut_etre_replace_da": "A delay, a non-conformity or a stock-out can be put back into context: which stocks, which suppliers, which production configuration.", "un_score_de_qualite_accompagne_chaque_donnee_exposee_aux_planifi": "A quality score accompanies every piece of data exposed to planners. Incomplete or outdated data is flagged before it reaches the user.", "un_sequencement_par_domaine_pour_livrer_quelque_chose_d_utile_av": "A domain-by-domain sequencing, to deliver something useful before the program ends.", "un_seul_objet_souvent_le_client_ou_le_fournisseur_et_trois_a_cin": "A single object — often the customer or the supplier — and three to five contributing systems. The actual duplicate rate is measured before any decision is made.", "un_seul_tableau_de_bord": "A single dashboard.", "un_seul_celui_qui_declenche_les_debats_en_reunion_ses_definition": "One only, the one that sparks debate in meetings. Its competing definitions and their respective sources are documented side by side.", "un_socle_data_vault_historise_avec_tracabilite_a_la_source_de_ch": "A historical Data Vault foundation, with source traceability for every value.", "un_socle_que_l_on_peut_defendre": "A foundation you can defend", "un_systeme_agentique_va_au_dela_de_l_execution_de_workflows_pred": "An agentic system goes beyond executing predefined workflows — it makes decisions based on context and adjusts its approach dynamically. Three capabilities define it:", "un_terme_manque_ou_reste_flou_posez_la_question_a_nos_equipes": "Missing a term or still unclear? Ask our teams.", "une_administration_doit_pouvoir_expliquer_un_chiffre_publie_il_y": "A public administration must be able to explain a figure published two years ago: where it comes from, which rule produced it, and what state the data was in that day. That's where most decision-support platforms stop.", "une_administration_une_banque_un_reseau_de_points_de_vente_et_un": "A public administration, a bank, a retail network and a mobility operator don't pursue the same goals — but they face the same obstacle: scattered, non-historized data that's hard to defend under audit. beVault provides a common Data Vault 2.0 foundation, tailored by industry.", "une_analyse_d_une_periode_passee_s_appuie_sur_le_reseau_tel_qu_i": "An analysis of a past period relies on the network as it was configured at that time.", "une_approche_de_la_securite_structuree_et_continue": "A structured, ongoing approach to security", "une_approche_de_modelisation_qui_separe_les_identifiants_les_lie": "A modeling approach that separates identifiers, the links between them, and descriptive attributes. It's designed to absorb new sources without reworking the existing model.", "une_approche_fondee_sur_les_risques_pour_identifier_et_gerer_les": "A risk-based approach to identifying and managing information security threats.", "une_approche_pas_une_garantie": "An approach, not a guarantee", "une_architecture_data_vault_2_0_sur_ibm_db2": "A Data Vault 2.0 architecture on IBM Db2", "une_architecture_data_vault_2_0_sur_postgresql": "A Data Vault 2.0 architecture on PostgreSQL", "une_architecture_data_vault_2_0_sur_votre_sql_server": "A Data Vault 2.0 architecture on your SQL Server", "une_automatisation_typique_peut": "A typical automation could:", "une_bascule_complete_vers_une_autre_plateforme_prend_des_annees_": "A complete switch to another platform takes years. A gradual domain-by-domain approach is the only realistic path.", "une_base_documentee_pour_vos_controles_et_audits": "A documented foundation for your controls and audits", "une_bonne_partie_des_malentendus_dans_un_projet_de_donnees_vient": "Much of the misunderstanding in a data project comes from words used differently by technical teams and business teams. Here are the definitions we use, written to be understood without prior training.", "une_cle_metier_est_l_identifiant_qu_un_utilisateur_metier_pronon": "A business key is the identifier a business user says out loud: a contract number, a staff number, an IBAN, an item code. It exists independently of the system that stores it.", "une_cle_metier_n_est_pas_une_cle_technique": "A business key is not a technical key", "une_cle_technique_un_identifiant_auto_incremente_un_guid_applica": "A technical key — an auto-incrementing ID, an application GUID, a replication key — belongs to the system. It disappears the day the system is replaced. Building hubs on technical keys is like anchoring your warehouse to an ERP you'll change in five years.", "une_competence_transferable": "Transferable skill", "une_conception_modulaire": "Modular design", "une_confiance_accrue_dans_la_maniere_dont_nous_protegeons_les_in": "Increased confidence in how we protect sensitive and confidential information.", "une_couche_de_restitution_documentee_remplace_la_foret_de_vues_a": "A documented restitution layer replaces the view jungle, with full lineage and quality indicators.", "une_couche_semantique_explicite_les_definitions_metier_sont_part": "An explicit semantic layer: business definitions are shared between humans and agents.", "une_demi_journee_avec_vos_architectes_pour_cadrer_la_trajectoire": "Half a day with your architects to frame the target trajectory and integration points.", "une_demonstration_d_une_heure_sur_un_cas_issu_de_votre_environne": "A one-hour demo on a case from your own environment is worth more than any comparison chart — including ours.", "une_donnee_partagee_par_plusieurs_processus_clients_produits_org": "Data shared across multiple processes — customers, products, organizations — whose definition must be consistent for figures to reconcile.", "une_enseigne_de_restauration_qui_a_unifie_ses_donnees_de_ventes_": "A restaurant chain that unified its sales data and reference data to run its network.", "une_equipe_data_qui_livre_en_jours_change_de_statut_dans_l_organ": "A data team that delivers in days changes its status within the organization: it stops being a bottleneck and becomes a partner people bring ideas to. Our clients see the number of requests increase after rollout — not because demand exploded, but because the business started asking again.", "une_equipe_doit_comprendre_une_nouvelle_source_l_agent_explore_l": "A team needs to understand a new source → the agent explores its structure and suggests a model design", "une_equipe_reduite_peut_tenir_une_plateforme_de_donnees_a_condit": "A small team can maintain a data platform, provided they do not rewrite the same thing for each source.", "une_etape_construite_au_quotidien": "A milestone built into everyday work", "une_etape_majeure_pour_proteger_l_information_et_meriter_la_conf": "A major milestone in protecting information and earning the trust of our customers and partners.", "une_evolution_de_structure_n_efface_pas_l_historique_charge_le_d": "A structural change doesn't erase loaded history: the Data Vault extends, it doesn't fully reload.", "une_execution_en_conteneurs": "Container-based execution,", "une_exposition_par_api_pensee_pour_les_scripts_la_ci_cd_et_les_a": "API exposure, designed for scripts, CI/CD, and AI agents.", "une_fois_la_chaine_validee_l_ancien_systeme_peut_etre_arrete_ave": "Once the chain is validated, the old system can be decommissioned, along with the operational burden and risk exposure that came with it. The scope migrated is an explicit choice, set according to retention obligations and actual usage.", "une_fois_les_fonctionnalites_comprises_deux_sujets_determinent_l": "Once the features are understood, two questions shape implementation: where the platform runs, and how it's exposed to your applications.", "une_fondation_data_vault_sur_votre_lakehouse": "A Data Vault foundation on your lakehouse", "une_fondation_de_donnees": "A data foundation", "une_fondation_de_donnees_citable_par_l_ia": "A data foundation AI can cite", "une_fondation_de_donnees_doit_encaisser_des_sources_qui_changent": "A data foundation has to absorb sources that change, business definitions that get refined, and questions not yet asked. That's what Data Vault solves: every load is historized, every business key is identified, nothing is overwritten.", "une_fondation_de_donnees_ne_cree_de_la_valeur_que_si_les_personn": "A data foundation only creates value when people and systems can use it. beVault publishes governed information marts and documented business views for reporting, applications, APIs and AI agents. The same model can support both precise analytical queries and richer AI experiences.", "une_fondation_de_donnees_qui_grandit_avec_votre_entreprise": "A data foundation that grows with your business", "une_fondation_qui_absorbe_l_existant": "A foundation that absorbs what already exists", "une_lecture_factuelle_de_l_existant_y_compris_des_solutions_de_c": "A factual reading of the current setup, including the workarounds teams have put in place to keep things running.", "une_meme_fondation": "One and the same foundation.", "une_migration_n_est_jamais_sans_friction_les_ecarts_entre_ancien": "A migration is never friction-free. Gaps between old and new emerge, implicit rules have to be rediscovered, business trade-offs are needed. The approach described here makes that friction visible and manageable — not pretend it doesn't exist.", "une_modernisation_domaine_par_domaine": "A domain-by-domain modernization", "une_modernisation_ne_devrait_pas_exiger_d_abandonner_l_environne": "Modernization shouldn't require abandoning the existing environment or launching a full warehouse project from scratch. The existing architecture holds value: proven rules, known definitions, history. The goal is to evolve it through controlled steps, not replace it wholesale.", "une_normalisation_divergente_entre_deux_pipelines_produit_deux_h": "Divergent normalization between two pipelines produces two different hashes for the same business key — hence two hub lines for the same client. This is exactly the type of rule that should be centralized rather than documented.", "une_normalisation_instable_des_valeurs_nulles_des_espaces_de_fin": "Unstable normalization of null values, trailing spaces, or case between two executions or two pipelines.", "une_nouvelle_source_integree_en_jours_plutot_qu_en_semaines": "A new source integrated in days rather than weeks", "une_offre_adaptee": "Pricing", "une_option_de_demarrage_gratuit_peut_etre_proposee_aux_organisat": "A free starting option may be available for organisations that want to explore beVault with a focused scope. Access conditions and available capabilities depend on the current offer.", "une_option_de_deploiement_hebergee_pour_les_organisations_qui_so": "A hosted deployment option for organisations looking for a managed way to get started with beVault.", "une_orchestration_bevault_integree_a_votre_environnement_aws": "A beVault orchestration integrated into your AWS environment", "une_orchestration_econome": "Cost-effective orchestration", "une_organisation_du_secteur_financier_qui_a_industrialise_la_pro": "A financial-sector organization that industrialized the production of its management data on beVault.", "une_partie_de_la_documentation_provient_des_metadonnees_de_model": "Some of the documentation comes from modeling metadata. Business definitions, however, remain a human decision: the platform collects and distributes them, it doesn't invent them.", "une_plateforme_de_donnees": "A data platform", "une_plateforme_de_donnees_vit_de_nouvelles_sources_arrivent_des_": "A data platform is alive: new sources arrive, definitions change, teams turn over.", "une_plateforme_ia_de_destination_events_construite_sur_bevault_p": "An AI platform for destination events built on beVault by dFakto.", "une_plateforme_ia_de_destination_events": "An AI platform for destination events.", "une_plateforme_ne_suffit_pas": "A platform isn't enough.", "une_plateforme_pour_structurer_controler_et_faire_evoluer_vos_do": "A platform to structure, control and evolve your data", "une_plateforme_reellement_prete_pour_l_ia_expose_son_metamodele_": "A truly AI-ready platform exposes its metamodel, lineage and quality indicators to automated systems, under access control. It's this openness — API, scoped keys, MCP Server — that makes agents useful and governable. Everything else is just a conversational interface bolted onto data nobody can explain.", "une_plateforme_pas_une_collection": "A platform, not a collection", "une_plateforme_trois_facons_d_interagir": "One platform. Three ways to interact.", "une_plateforme_trois_facons_de_travailler_par_l_interface_par_le": "One platform. Three ways to work: through the interface, through code and through AI.", "une_pme_accumule_rarement_ses_problemes_de_donnees_d_un_coup_ils": "An SME rarely accumulates its data problems all at once. They appear as tools are added, dashboards are built in a hurry, and definitions slowly diverge from one team to another.", "une_pme_n_a_pas_besoin_de_couvrir_tout_son_systeme_d_information": "An SME does not need to cover its entire information system from the start. A well-chosen domain is enough to establish the method and then expand it.", "une_pme_peut_commencer_par_un_besoin_concret_reporting_qualite_i": "An SME can start from a concrete need — reporting, quality, integration or AI readiness — then gradually extend its data foundation. These use cases are not reserved for SMEs: they are possible entry points.", "une_politique_ecrite_ne_controle_rien": "A written policy controls nothing", "une_proposition_peut_couvrir_le_perimetre_de_la_plateforme_l_env": "A quote may cover the platform scope, deployment environment, implementation requirements and services needed for the project.", "une_qualite_difficile_a_controler": "Quality that is difficult to control", "une_qualite_mesuree_apres_coup": "Quality measured after the fact", "une_question_un_projet": "A question? A project?", "une_question_simple_une_reponse_difficile": "A simple question, a difficult answer", "une_recette_exclusive_co_creee_avec_la_brasserie_witloof_a_bruxe": "An exclusive recipe, co-created with Brasserie Witloof in Brussels.", "une_regle_qui_n_est_pas_executable_reste_une_intention": "A rule that isn't executable remains just an intention.", "une_reponse_a_d_ou_vient_ce_chiffre_qui_se_lit_dans_la_plateform": "An answer to “where does this figure come from” that's read directly in the platform, not reconstructed after the fact.", "une_seule_chaine_de_support_en_cas_d_incident": "A single support chain in case of an incident", "une_seule_plateforme_a_maitriser_moins_de_transferts_de_contexte": "Only one platform to master: fewer context switches between tools, stable delivery times over time.", "une_seule_plateforme_de_la_source_jusqu_a_l_usage": "One platform, from source to use.", "une_seule_version_du_chiffre": "A single version of the truth", "une_societe_de_services_financiers_produisait_ses_rapports_de_ge": "A financial services company was producing its management reports in five days a month. Figures diverged from one department to another. Two dFakto Data Vault consultants built a beVault warehouse on top of existing systems — without parallel infrastructure, without additional licenses.", "une_sortie_construite_pour_un_usage_precis_un_tableau_de_bord_un": "An output built for a specific use: a dashboard, a regulatory filing, an application. It's produced from the central model and documented.", "une_sortie_d_ia_reste_une_donnee_elle_merite_le_meme_traitement_": "An AI output is still data: it deserves the same treatment as any other.", "une_sortie_possible": "A possible exit", "une_trajectoire_bigquery_maitrisee": "A controlled BigQuery trajectory", "une_trajectoire_redshift_maitrisee": "A controlled Redshift trajectory", "une_trajectoire_snowflake_maitrisee": "A controlled Snowflake trajectory", "une_valeur_revisee_s_ajoute_a_la_precedente_au_lieu_de_l_ecraser": "A revised value is added alongside the previous one instead of overwriting it, with a timestamp for the revision.", "une_vue_de_reference_est_une_interpretation_jamais_une_destructi": "A reference view is an interpretation, never a destruction.", "unifier_et_historiser_les_donnees_de_reference": "Unify and historize reference data", "unifiez_les_donnees_de_toutes_vos_sources": "Unify data from every source", "usages_ia": "AI use cases", "utiliser_bevault_par_programmation": "Use beVault programmatically", "utilisez_l_api_pour_automatiser_les_operations_connecter_bevault": "Use the API to automate operations, connect beVault to other enterprise tools and integrate the platform into your existing workflows.", "utilisez_l_interface_bevault_pour_modeliser_les_concepts_metier_": "Use the beVault interface to model business concepts, map source systems, create Data Vault objects, configure data quality rules and manage Information Marts.", "vault_industrialise_sur_le_lakehouse": "Industrialized Vault on the lakehouse", "vault_sur_sql_server_on_premises_ou_azure": "Vault on SQL Server, on-premises or Azure", "vaultspeed_est_un_generateur_de_code_data_vault_reconnu_et_si_vo": "VaultSpeed is a well-known Data Vault code generator, and if your need stops at generation, it's a good tool. The real question is different: what do you do with the code once it's generated? Who orchestrates it, who checks the quality of the loaded data, and on what infrastructure does all this run? That's exactly where the two approaches diverge.", "ventes": "Sales", "ventes_produits_et_points_de_vente": "Sales, products and points of sale", "verification_des_structures_cles_de_hachage_et_historisation": "Verification of structures, hash keys, and historization", "verifier_votre_eligibilite": "Check your eligibility", "vers_vos_plateformes_de_donnees": "To your data platforms", "versioning_et_environnements": "Versioning and environments", "versionner_les_regles": "Version the rules", "via_l_api_et_le_serveur_mcp_les_agents_peuvent_interagir_avec_le": "Via the API and the MCP Server, agents can interact with the exposed metadata and data according to configured permissions and controls.", "via_l_api_et_le_serveur_mcp_vos_agents_peuvent_interroger_le_met": "Via the API and the MCP Server, your agents can query the metamodel, trigger loads and read lineage — with the same access controls as the rest of the organization.", "via_le_portail_partenaire_qui_centralise_les_deals_enregistres_e": "Via the partner portal, which centralizes registered deals and their tracking.", "vie_non_vie_sante_courtage_portefeuilles_repris_lors_d_une_acqui": "Life, non-life, health, brokerage, portfolios acquired through a merger: each branch holds a share of the truth about the same customer, with its own product codes and its own notion of effective date.", "viewport": "viewport", "vitesse_de_livraison": "Delivery speed", "voir_bevault_dans_votre_contexte": "See beVault in your context", "voir_bevault_dans_votre_contexte_retail": "See beVault in your retail context", "voir_ce_que_ca_donne_sur_votre_cas": "See what it looks like for your use case", "voir_ce_que_ca_donne_sur_votre_cas_2": "See what it looks like for your use case", "voir_comment_bevault_construit_cette_fondation": "See how beVault builds this foundation", "voir_comment_bevault_gere_vos_cles_metier": "See how beVault manages your business keys →", "voir_comment_bevault_modelise_vos_donnees": "See how beVault models your data →", "voir_comment_bevault_traite_la_complexite_des_donnees": "See how beVault handles data complexity", "voir_l_api_les_agents": "View the API & agents", "voir_l_api_bevault": "See the beVault API", "voir_l_architecture_de_la_plateforme": "See the platform architecture", "voir_l_orchestration": "View the orchestration", "voir_la_documentation": "See the documentation", "voir_la_liste_des_outils_certifies": "See the list of certified tools →", "voir_la_modelisation_metavault": "See the metaVault modeling", "voir_la_page_pour_les_pme": "See the page For SMEs", "voir_la_plateforme": "See the platform", "voir_la_plateforme_en_action": "See the platform in action", "voir_la_plateforme_en_action_2": "See the platform in action", "voir_la_qualite_des_donnees": "See data quality", "voir_la_serie_complete": "See the complete series", "voir_le_cas_d_usage": "See the use case", "voir_le_deploiement": "See the deployment", "voir_le_module_data_quality": "See the Data Quality module", "voir_le_module_data_quality_2": "See the Data Quality module →", "voir_le_module_de_modelisation": "See the modeling module →", "voir_le_module_orchestration": "See the Orchestration module", "voir_le_secteur_public": "See the public sector", "voir_les_business_cases": "See the business cases", "voir_les_cas_d_usage": "See the use cases", "voir_les_fonctionnalites": "See all features", "voir_les_information_marts": "See the Information Marts", "voir_les_offres": "See pricing", "voir_les_plateformes": "See the platforms", "voir_les_replays": "See the replays", "voir_les_resultats_chiffres": "See the quantified results", "voir_les_success_stories": "See success stories", "voir_si_ca_s_applique_a_votre_contexte": "See whether this applies to your context", "voir_si_ca_s_applique_a_votre_contexte_2": "See whether this applies to your context", "voir_une_demo": "See a demo", "voir_une_demo_2": "Book a demo", "voir_une_demo_d_abord": "watch a demo first", "volume_de_code_a_maintenir": "Volume of code to maintain", "vos_agents_ia_valent_vos_donnees": "Your AI agents are only as good as your data", "vos_architectes_decrivent_les_objets_metier_leurs_cles_metier_et": "Your architects describe business objects, their business keys, and their relationships. This description drives everything else.", "vos_consultants_suivent_les_sessions_produit_et_travaillent_sur_": "Your consultants attend product sessions and work in a dedicated environment.", "vos_donnees_db2_ont_de_la_valeur": "Your DB2 data has value.", "vos_donnees_ne_devraient_pas_redevenir_un_projet_a_chaque_fois_q": "Your data shouldn't turn into a project every time you want to use it.", "vos_donnees_oracle_ont_de_la_valeur": "Your Oracle data has value.", "vos_donnees_sont_deja_quelque_part": "Your data is already somewhere.", "vos_donnees_sont_pretes_pour_l_ia_voyez_ce_que_ca_change_en_45_m": "Your data is ready for AI. See what that changes in 45 minutes.", "vos_enchainements_aws_existants_extractions_applicatives_appels_": "Your existing AWS workflows: application extracts, function calls, technical processing and notifications.", "vos_equipes": "Your teams", "vos_equipes_apprennent_le_standard_pas_les_particularites_d_un_e": "Your teams learn the standard, not a vendor's quirks. New hires and contractors get up to speed faster.", "vos_equipes_decrivent_les_objets_metier_leurs_relations_et_leurs": "Your teams describe the business objects, their relationships and their rules. beVault uses that description to generate the structures and the code, connect the source systems and load the data while preserving its history.", "vos_equipes_et_les_notres_sur_le_meme_terrain": "Your teams and ours, on the same ground", "vos_equipes_sont_formees_sur_la_plateforme_bevault_et_sur_la_met": "Your teams are trained on the beVault platform and on the dFakto method, using your own model as the basis rather than a generic example.", "vos_equipes_y_decrivent_le_modele_entites_metier_cles_metier_rel": "Your teams describe the model there: business entities, business keys, relationships, and attributes. The metadata entered here drives the generation of structures and loading code.", "vos_equipes_bevault_s_execute_dans_votre_infrastructure_et_utili": "Your teams. beVault runs in your infrastructure and uses the access you grant, with your security and traceability rules.", "vos_equipes_les_composants_s_executent_dans_l_environnement_defi": "Your teams. The components run in the environment defined with you, which is precisely the point for organizations with sovereignty requirements.", "vos_experts_metier_et_vos_equipes_it_restent_proprietaires_des_d": "Your business experts and IT teams remain owners of the definitions, priorities and trade-offs. They are the ones who will run the platform afterward.", "vos_projets_ia_n_echouent_pas_sur_le_modele": "Your AI projects don't fail because of the model.", "vos_regles": "your rules.", "vos_workflows_de_donnees_s_adaptent_ainsi_a_votre_logique_metier": "Your data workflows adapt to your business logic and data structure.", "votre_agent_ia_n_a_pas_besoin_de_se_connecter_separement_a_chaqu": "Your AI agent does not need to connect separately to every operational system. beVault absorbs the differences between sources and presents the data through a unified structure, making it easier to integrate new systems without rebuilding the entire AI architecture.", "votre_chaine_aws_existe_deja": "Your AWS chain already exists.", "votre_contexte_est_particulier": "Is your context specific?", "votre_enjeu_votre_secteur_votre_plateforme_cible": "Your challenge, your industry, your target platform.", "votre_equipe": "Your team", "votre_organisation_n_a_pas_besoin": "Your organisation does not need", "votre_perimetre": "Your scope", "votre_plateforme_cible_reste_la_votre_aucune_donnee_n_est_deplac": "Your target platform stays yours: no data is moved", "votre_plateforme_votre_perimetre": "Your platform, your scope,", "votre_secteur_est_identifie_voyez_l_enjeu_que_vous_voulez_traite": "Your sector is identified. See which challenge you want to tackle first.", "votre_situation_n_est_pas_dans_la_liste": "Don't see your situation on the list?", "votre_situation_ressemble_a_l_une_d_elles": "Does your situation look like one of these?", "votre_sql_server_est_deja_la": "Your SQL Server is already there.", "vous_aider_a_creer_des_information_marts_a_partir_de_votre_model": "Help you build Information Marts from your existing model.", "vous_avez_la_theorie_voyez_la_en_pratique": "You have the theory. See it in practice.", "vous_avez_le_livre_blanc_l_etape_suivante_c_est_45_minutes_sur_v": "You have the white paper. The next step is 45 minutes on your data.", "vous_construisez_dans_bevault": "you build in beVault.", "vous_decidez_de_l_emplacement_des_composants_la_frontiere_avec_v": "You decide where components are located; the boundary with your environment stays clear.", "vous_decidez_ou_vivent_les_composants_qui_ouvre_les_acces_et_ce_": "You decide where components live, who opens access, and what leaves your network.", "vous_devez_decider_avant_de_construire_objectifs_etat_des_lieux_": "You need to decide before building: objectives, current state, priorities, target architecture, deployment choices and governance.", "vous_etes_une_pme": "Are you an SME?", "vous_etes_une_pme_avec_une_equipe_data_reduite": "You are an SME with a small data team", "vous_evaluez_plusieurs_solutions_nous_repondons_directement_a_vo": "Evaluating multiple solutions? We'll directly address your criteria grid, no detours.", "vous_gardez_ainsi_un_controle_precis_sur_chaque_etape_de_votre_f": "This gives you precise control over each step of your data pipeline.", "vous_integrez_un_erp_ou_des_systemes_legacy": "You're integrating an ERP or legacy systems", "vous_modernisez_un_entrepot_existant": "You're modernizing an existing warehouse", "vous_preparez_une_fondation_de_donnees_pour_l_ia": "You're building a data foundation for AI", "vous_remplissez_le_formulaire_partenaire_en_francais_ou_en_angla": "You fill in the partner form, in French or English. We get back to you for an initial qualification call.", "vous_souhaitez_recevoir_nos_bieres_bevault_pour_un_evenement_un_": "Interested in receiving our beVault beers for an event, a client, or simply for your team? Contact us.", "vous_travaillez_la_qualite_et_la_gouvernance": "You're working on quality and governance", "vous_voulez_tester_bevault_sur_vos_donnees_avant_de_vous_engager": "Want to try beVault on your own data before committing?", "vous_voulez_une_bi_et_un_reporting_fiables": "You want reliable BI and reporting", "voyez_bevault_dans_votre_contexte": "See beVault in your context.", "voyez_ce_que_l_api_et_le_serveur_mcp_debloquent_sur_vos_donnees": "See what the API and MCP Server unlock on your data.", "voyez_comment_bevault_peut_s_integrer_a_votre_trajectoire_data": "See how beVault can integrate into your data trajectory.", "voyez_comment_d_autres_organisations_abordent_leurs_enjeux_de_do": "See how other organizations approach their data challenges.", "voyez_comment_vos_workflows_s_executeraient": "See how your workflows would run.", "voyez_le_catalogue_et_le_lignage_sur_un_modele_reel": "See the catalog and lineage on a real model.", "voyez_un_mart_construit_sur_un_modele_proche_du_votre": "See a mart built on a model close to yours.", "voyons_comment_bevault_s_insere_dans_votre_chaine_aws": "Let's see how beVault fits into your AWS pipeline.", "voyons_comment_une_migration_se_deroulerait_dans_votre_environne": "Let's see how a migration would play out in your environment.", "vue_d_ensemble": "Overview", "vue_d_ensemble_des_fonctionnalites": "Features overview", "webinaires": "Webinars", "website": "website", "wherescape_est_l_un_des_pionniers_de_l_automatisation_d_entrepot": "WhereScape is one of the pioneers of data warehouse automation, with a solid installed base and a tooled approach to development. beVault starts from a different point: the Data Vault model as the single source of truth, with orchestration, quality and marts included in the same product, and a deployment designed for European sovereignty constraints.", "white_paper": "White paper", "white_papers": "White papers", "width_device_width_initial_scale_1": "width=device-width, initial-scale=1", "wisedigi": "WiseDigi", "witloof_brasserie_artisanale_bruxelloise": "Witloof, artisanal brewery in Brussels", "workers": "Workers", "workers_l_execution": "Workers — execution", "workflows_dependances_entre_traitements_conditions_d_execution_e": "Workflows, dependencies between processes, execution conditions and tracking of the load lifecycle.", "your_ai_can_trust": "your AI can trust.", "zero_integration_a_maintenir": "zero integrations to maintain.", "zero_regression_liee_a_du_code_de_chargement_ecrit_a_la_main": "Zero regression linked to hand-written loading code", "manual_iso27001_article_0": "dFakto achieves ISO/⁠IEC 27001 Certification, Strengthening Its Commitment to Information Security", "manual_iso27001_article_1": "We're proud to announce that dFakto (Deployments Factory) is now ISO/⁠IEC 27001 certified, marking a major milestone in our ongoing commitment to protecting information and earning the trust of our customers and partners.", "manual_iso27001_article_2": "ISO/⁠IEC 27001 certification provides independent validation that dFakto has implemented and operates a robust Information Security Management System (ISMS) aligned with international best practices.", "manual_iso27001_article_3": "ISO/⁠IEC 27001 is not a one-time effort. It represents a continuous commitment to maintaining, monitoring, and improving our information security practices over time.", "manual_iso27001_article_4": "What is ISO/⁠IEC 27001, exactly?", "manual_iso27001_article_5": "ISO/⁠IEC 27001 is the leading international standard for information security management, published by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC).", "manual_iso27001_article_6": "As part of the certification process, an independent, accredited certification body audited our ISMS and verified that it meets the requirements of ISO/⁠IEC 27001 within the defined scope of certification.", "manual_iso27001_article_7": "Achieving ISO/⁠IEC 27001 certification required us to formalize and strengthen how we approach information security, including:", "manual_iso27001_article_8": "dFakto achieves ISO/⁠IEC 27001 certification | beVault", "manual_iso27001_article_9": "dFakto (Deployments Factory) is ISO/⁠IEC 27001 certified: independent validation of its Information Security Management System.", "manual_drink_photo_alt": "Can of beVault IPA beer, brewed in Brussels", "meta_0_pourquoi_vos_projets_data_prennent_toujours_plus_l": "Why your data projects always take longer than expected | beVault", "meta_1_les_vraies_causes_des_d_passements_de_d_lai_dans_l": "The real causes behind data warehouse project delays, and how Data Vault automation helps bring delivery back to a sprint-level timeframe.", "meta_2_pourquoi_les_projets_ia_chouent_et_comment_constru": "Why AI projects fail — and how to build a solid foundation | beVault", "meta_3_transformer_des_donn_es_fragment_es_et_de_qualit_v": "Turn fragmented, variable-quality data into a governed platform where AI can finally deliver value.", "meta_4_des_insights_ia_aux_actifs_data_int_grer_les_sorti": "AI Insights to Data Assets: Integrating AI Output into Your Data Vault | beVault", "meta_5_transformer_les_scores_de_sentiment_tags_d_entit_s": "Transform sentiment scores, entity tags, and anomaly signals into governed Data Vault satellites.", "meta_6_serveurs_mcp_l_architecture_portable_pour_vos_agen": "MCP Servers: A Portable Architecture for Your Data Vault Agents | beVault", "meta_7_comment_r_soudre_la_prolif_ration_d_outils_le_burd": "How to solve tool sprawl, configuration burden, and platform lock-in with an MCP server.", "meta_8_agents_ia_interactifs_pour_le_data_vault_l_approch": "Interactive AI Agents for Data Vault: The Direct API Approach | beVault", "meta_9_de_l_automation_l_interaction_quand_les_exigences_": "From automation to interaction: when requirements emerge through dialogue, agent architectures take over.", "meta_10_automatiser_l_extraction_de_m_tadonn_es_avec_l_ia_": "Automating Metadata Extraction with AI: No More SQL Parsers | beVault", "meta_11_la_puissance_de_l_orchestration_ia_simple_sans_inf": "Discover the power of simple AI orchestration to document your Information Marts, with no complex infrastructure required.", "meta_12_cl_s_m_tier_dans_le_data_vault_construire_pour_que": "Business Keys in Data Vault: Building to Last | beVault", "meta_13_comment_choisir_des_business_keys_stables_dans_un_": "How to choose stable business keys in a Data Vault 2.0 model, avoid technical keys, and absorb source system changes.", "meta_14_agents_ia_pour_le_data_vault_trois_architectures_t": "AI Agents for Data Vault: Architectures and Maturity Levels | beVault", "meta_15_de_l_orchestration_simple_aux_serveurs_mcp_quel_pa": "From simple orchestration to MCP servers: which AI agent pattern should you choose for your Data Vault team?", "meta_16_ia_et_data_vault_3_synergies_pour_des_quipes_data_": "AI and Data Vault: Synergies for Modern Data Teams | beVault", "meta_17_combiner_la_rigueur_du_data_vault_2_0_et_la_vitess": "Combine the rigour of Data Vault 2.0 with the speed of AI to deliver reliable insights faster, with concrete use cases.", "meta_18_dfakto_obtient_la_certification_iso_bevault": "dFakto Achieves ${ISO} Certification | beVault", "meta_19_dfakto_deployments_factory_est_certifi_e_iso_une_v": "dFakto (Deployments Factory) is ${ISO} certified: an independent validation of its information security management system.", "meta_20_le_probl_me_de_duplication_silencieuse_dans_les_sa": "The Silent Duplication Problem in Data Vault Satellites | beVault", "meta_21_pourquoi_vos_satellites_data_vault_stockent_des_ch": "Why your Data Vault satellites store changes that aren't real, how to detect it, and how to prevent it by design.", "meta_22_dfakto_et_pcma_lancent_destinaitor_la_plateforme_i": "dFakto and PCMA Launch DestinAItor, the AI Platform for the Events Industry | beVault", "meta_23_destinaitor_donne_plus_de_12_000_planificateurs_d_": "DestinAItor gives event planners access to certified destination data on a Data Vault foundation built with beVault.", "meta_24_dfakto_et_dust_s_associent_pour_d_ployer_l_ia_en_e": "dFakto and Dust Partner to Deploy Enterprise AI on Reliable Data | beVault", "meta_25_un_partenariat_qui_connecte_les_agents_ia_de_dust_": "A partnership connecting Dust's AI agents to a governed data foundation built with beVault, for sourced, dated, and auditable answers.", "meta_26__propos_l_quipe_derri_re_bevault_bevault": "About Us — The Team Behind beVault | beVault", "meta_27_bevault_est_un_produit_dfakto_une_quipe_de_data_en": "beVault is a dFakto product from a Brussels-based team of data engineers with deep expertise in Data Vault.", "meta_28_bevault_avec_snowflake_databricks_la_couche_data_v": "beVault with Snowflake & Databricks — The Data Vault Layer on Top", "meta_29_snowflake_et_databricks_stockent_et_calculent_beva": "Snowflake and Databricks store and compute. beVault models, generates, orchestrates, and manages quality on top. See how the two layers share the workload.", "meta_30_bevault_vs_datavault_builder_quel_choix_pour_votre": "beVault vs Datavault Builder: Which to Choose for Your Data Vault?", "meta_31_comparatif_d_taill_entre_bevault_et_datavault_buil": "A detailed comparison of beVault and Datavault Builder: DV 2.1 certification, orchestration, data quality, MDM, and sovereign deployment.", "meta_32_bevault_vs_dbt_automatisation_data_vault_ou_framew": "beVault vs dbt: Data Vault Automation or Transformation Framework", "meta_33_dbt_structure_vos_transformations_sql_bevault_auto": "dbt structures your SQL transformations. beVault provides end-to-end Data Vault automation: modelling, generation, orchestration, quality, and marts. A detailed comparison.", "meta_34_bevault_vs_vaultspeed_comparatif_honn_te_pour_votr": "beVault vs VaultSpeed: An Honest Comparison for Your Data Vault Choice", "meta_35_certification_dv_2_1_orchestration_int_gr_e_qualit": "DV 2.1 certification, integrated orchestration, native data quality, sovereign deployment: compare beVault and VaultSpeed on the criteria that really matter.", "meta_36_bevault_vs_wherescape_comparatif_automatisation_da": "beVault vs WhereScape: Data Vault Automation Comparison", "meta_37_wherescape_automatise_la_construction_d_entrep_ts_": "WhereScape has long automated warehouse construction. Compare its scope with beVault's: DV 2.1 certification, integrated orchestration, native quality, deployment.", "meta_38_blog_ressources_insights_data_vault_2_0_bevault": "Blog — Data Vault 2.0 Resources & Insights | beVault", "meta_39_data_vault_qualit_des_donn_es_ia_et_retours_terrai": "Data Vault, data quality, AI, and field reports: analysis and lessons learned from the dFakto team on data platform automation.", "meta_40_demander_une_d_mo_bevault_45_minutes_sur_vos_cas_r": "Request a beVault Demo — Based on Your Real-World Use Cases", "meta_41_une_d_monstration_bevault_adapt_e_votre_contexte_m": "A beVault demonstration tailored to your context: modelling, historised loading, quality, and orchestration, based on a use case from your environment.", "meta_42_contactez_nous_parlons_de_vos_projets_data_bevault": "Contact Us — Let's Discuss Your Data Projects | beVault", "meta_43_prenez_contact_avec_l_quipe_bevault_formulaire_bur": "Get in touch with the beVault team: use our contact form or find our Brussels and Paris office details, phone number, and email address.", "meta_44_strat_gie_architecture_data_services_dfakto": "Data Strategy & Architecture | dFakto Services", "meta_45_cadrage_des_objectifs_tat_des_lieux_priorit_s_reco": "Defining objectives, current state analysis, priorities, recommendations, target architecture, deployment choices, integration, and governance: decide before you build.", "meta_46_impl_mentation_formation_support_services_dfakto": "Implementation, Training & Support | dFakto Services", "meta_47_mise_en_uvre_de_bevault_avec_vos_quipes_mod_lisati": "beVault implementation with your teams: modelling, integration, quality, orchestration, Information Marts, go-live, training, documentation, support and model evolution.", "meta_48_services_data_dfakto_accompagnement_bevault": "dFakto Data Services — beVault Support | beVault", "meta_49_cadrage_architecture_impl_mentation_formation_et_s": "Scoping, architecture, implementation, training and support: how dFakto teams work with yours, from the first workshop to go-live.", "meta_50_la_bi_re_bevault_dition_limit_e_avec_brasserie_wit": "The beVault Beer — limited edition with Brasserie Witloof | beVault", "meta_51_bevault_a_co_cr_une_recette_de_bi_re_exclusive_ave": "beVault co-created an exclusive beer recipe with Brasserie Witloof in Brussels. A limited edition, 100% craft and local brew.", "meta_52_automatiser_bevault_avec_l_api_et_les_agents_ia_be": "Automate beVault with the API and AI agents | beVault", "meta_53_connectez_bevault_vos_applications_scripts_et_work": "Connect beVault to your applications, scripts and workflows with the API, and to your AI agents with the beVault MCP server.", "meta_54_fonctionnalit_s_bevault_mod_liser_orchestrer_v_rif": "beVault Features — Model, Orchestrate, Verify, Distribute | beVault", "meta_55_metavault_orchestration_qualit_des_donn_es_informa": "metaVault, orchestration, data quality, information marts and versioning: how beVault's modules connect around a single meta-model.", "meta_56_int_gration_connectivit_des_donn_es_bevault": "Data Integration & Connectivity | beVault", "meta_57_connexion_aux_syst_mes_sources_erp_et_applications": "Source system, ERP and legacy app connections, mapping, ingestion, historisation, APIs and target platform connections: how beVault feeds your data platform.", "meta_58_data_products_information_marts_bevault": "Governed Data Products & Information Marts | beVault", "meta_59_transformez_votre_data_vault_en_produits_de_donn_e": "Turn your Data Vault into documented data products: governed marts for BI, reporting, applications and AI use cases.", "meta_60_data_quality_mdm_bevault": "Data Quality Management & MDM | beVault", "meta_61_contr_les_d_clar_s_sur_des_donn_es_historis_es_et_": "Declarative checks on historised, multi-system data, anomalies raised in actionable lists, source correction and continuous quality improvement with beVault.", "meta_62_automatisation_data_vault_bevault": "Data Vault Automation | beVault", "meta_63_bevault_transforme_le_data_vault_en_un_mod_le_visu": "beVault turns Data Vault into a visual business model, generating structures, loads, docs and lineage. The only tool certified by the Data Vault Alliance.", "meta_64_d_ploiement_souverainet_cloud_on_premises_ou_hybri": "Deployment & Sovereignty — Cloud, On-Premises or Hybrid | beVault", "meta_65_d_ployez_bevault_en_service_manag_dans_votre_propr": "Deploy beVault as a managed service, in your own cloud or on your servers, using Docker: full sovereignty, security and control over component location.", "meta_66_la_plateforme_bevault_du_mod_le_m_tier_aux_donn_es": "The beVault Platform — From Business Model to Actionable Data | beVault", "meta_67_data_vault_comme_fondation_mod_lisation_pilot_e_pa": "Data Vault foundation, metadata-driven modelling, integration, quality, orchestration and information marts: how the beVault platform works and deploys in your environment.", "meta_68_data_catalog_lignage_documentation_bevault": "Data Catalogue, Lineage & Documentation | beVault", "meta_69_le_data_catalog_de_bevault_rassemble_les_m_tadonn_": "The beVault Data Catalogue gathers all platform metadata: asset search, automatic column documentation, data origin and visibility over transformations.", "meta_70_architecture_de_la_plateforme_bevault": "The beVault Platform Architecture | beVault", "meta_71_les_composants_bevault_metavault_states_et_workers": "beVault components—metaVault, States and Workers—and the boundary with your environment: sources, infrastructure, target databases and reporting tools.", "meta_72_versioning_environnements_git_store_et_promotions_": "Versioning & Environments — Git Store and Audited Promotions | beVault", "meta_73_mod_les_versionn_s_dans_le_git_store_environnement": "Versioned models in the Git Store, dev/test/prod environments, audited promotions and non-destructive deployments with beVault.", "meta_74_states_l_orchestrateur_de_workflows_de_bevault": "States: beVault's Data Workflow Orchestrator | beVault", "meta_75_states_l_orchestrateur_interne_de_bevault_pilote_v": "States, beVault's internal orchestrator, drives your data workflows from extraction to BI tools, using the Amazon States Language and extensible Workers.", "meta_76_politique_de_confidentialit_bevault_par_dfakto": "Privacy Policy | beVault by dFakto", "meta_77_comment_dfakto_sa_deployments_factory_collecte_uti": "How dFakto SA – Deployments Factory collects, uses and protects personal data on the beVault website.", "meta_78_bevault_la_plateforme_de_donn_es_pr_te_pour_l_ia": "beVault — The AI-Ready Data Platform", "meta_79_bevault_est_une_plateforme_de_donn_es_pr_te_pour_l": "beVault is an AI-ready data platform for organisations that want to keep control of their data: build, feed, control, distribute and orchestrate, in your own environment.", "meta_80_partenaires_bevault_int_grateurs_conseils_et_diteu": "beVault Partners — Integrators, Consultants & ISVs | beVault", "meta_81_rejoignez_l_cosyst_me_bevault_programme_partenaire": "Join the beVault ecosystem: partner programme, enablement, Data Vault 2.0 co-delivery and access to the partner portal.", "meta_82_programme_partenaire_bevault_enablement_et_co_deli": "beVault Partner Programme — Enablement and Co-delivery | beVault", "meta_83_le_programme_partenaire_bevault_enablement_techniq": "The beVault partner programme: technical and sales enablement, co-delivery of initial projects, opportunity registration and dedicated support.", "meta_84_tarifs_bevault_une_offre_adapt_e_votre_trajectoire": "beVault Pricing — An offer for your data journey | beVault", "meta_85_starter_standard_enterprise_trois_niveaux_de_p_rim": "Starter, Standard, Enterprise: three tiers to get started with beVault. No public price list—request a proposal tailored to your project.", "meta_86_privacy_policy_bevault_by_dfakto": "Privacy Policy | beVault by dFakto", "meta_87_how_dfakto_sa_deployments_factory_collects_uses_an": "How dFakto SA – Deployments Factory collects, uses and protects personal data on the beVault website.", "meta_88_destinaitor_une_plateforme_ia_construite_sur_bevau": "Destinaitor: An AI platform built on beVault | beVault", "meta_89_12_000_planificateurs_d_v_nements_acc_dent_des_don": "12,000+ event planners access versioned, traceable and measured data. beVault is the invisible foundation of Destinaitor.", "meta_90_exki_de_14_jours_4_heures_de_latence_donn_es_avec_": "Exki: From 14-day to 4-hour data latency with beVault | beVault", "meta_91_8_syst_mes_sources_consolid_s_3_8_millions_de_calc": "8 consolidated source systems, 3.8 million calculations per night, and 11 reports delivered to ops and finance teams in 7 countries.", "meta_92_success_stories_clients_bevault_quatre_projets_r_e": "beVault Customer Success: Four Real-World Projects", "meta_93_itbm_exki_parking_brussels_destinaitor_quatre_proj": "ITBM, Exki, parking.brussels, Destinaitor: four Data Vault 2.0 projects automated with beVault, with measured before-and-after results.", "meta_94_itbm_90_de_temps_de_reporting_avec_bevault": "ITBM: 90% Less Reporting Time with beVault", "meta_95_comment_une_soci_t_de_services_financiers_est_pass": "How a financial services firm went from five days to just hours for monthly reporting, while achieving 95% data reliability.", "meta_96_parking_brussels_3_8_etp_r_cup_r_s_avec_bevault": "parking.brussels: 3.8 FTEs Reclaimed with beVault", "meta_97_12_syst_mes_consolid_s_en_un_entrep_t_unique_contr": "12 systems consolidated into a single warehouse, with integrated quality controls and real-time dashboards for field teams and management.", "meta_98_r_sultats_clients_les_chiffres_mesur_s_avec_bevaul": "Customer Results: Measured Outcomes with beVault", "meta_99_itbm_exki_parking_brussels_destinaitor_les_r_sulta": "ITBM, Exki, parking.brussels, Destinaitor: measured before/after results of implementing beVault, with the calculation method explained.", "meta_100_comparatifs_alternatives_data_vault_bevault": "Data Vault Comparisons & Alternatives | beVault", "meta_101_bevault_face_vaultspeed_wherescape_datavault_build": "beVault vs. VaultSpeed, WhereScape, Datavault Builder, and dbt, and its role with Snowflake or Databricks: the criteria that really matter.", "meta_102_documentation_et_e_learning_bevault_ressources": "beVault Documentation & E-learning | Resources", "meta_103_documentation_technique_bevault_r_f_rence_api_note": "beVault technical documentation, API reference, release notes, and beVault Learn training paths—accessible online with no installation required.", "meta_104_glossaire_des_donn_es_bevault": "Data Glossary — beVault", "meta_105_les_termes_utilis_s_dans_les_projets_de_plateforme": "Terms used in data platform projects, explained simply: business key, historisation, lineage, Information Mart, orchestration, metadata, golden record.", "meta_106_ressources_insights_data_vault_bevault": "Data Vault Resources & Insights | beVault", "meta_107_blog_white_paper_webinaires_et_documentation_bevau": "beVault blog, white papers, webinars, and documentation: Data Vault, data quality, AI, and field insights from the dFakto teams.", "meta_108_webinaires_data_vault_qualit_des_donn_es_et_ia_bev": "Data Vault, Data Quality & AI Webinars | beVault", "meta_109_sessions_enregistr_es_par_les_experts_bevault_data": "Recorded sessions by beVault experts on Data Vault 2.0, data quality, ERP reporting, and AI foundations. Available to watch at any time.", "meta_110_livre_blanc_infrastructure_de_donn_es_sans_arm_e_d": "White Paper: Data Infrastructure Without an Engineer Army | beVault", "meta_111_t_l_chargez_le_livre_blanc_bevault_comment_les_pme": "Download the beVault white paper: how SMEs and public sector organisations access an enterprise-grade data platform and prepare for AI.", "meta_112_bevault_pour_les_pme_une_fondation_de_donn_es_qui_": "beVault for SMEs — A Data Foundation That Grows With You", "meta_113_sources_multiples_quipe_data_r_duite_besoins_qui_v": "Multiple sources, a small data team, evolving needs: how beVault helps SMEs structure their data, manage its quality, and prepare for analytics and AI.", "meta_114_data_vault_pour_l_nergie_les_utilities_bevault": "Data Vault for Energy & Utilities | beVault", "meta_115_s_ries_de_comptage_actifs_et_interventions_conserv": "Metering series, assets, and interventions: maintain successive states and corrections in a consistent history for both operations and reporting.", "meta_116_data_vault_pour_les_services_financiers_bevault": "Data Vault for Financial Services | beVault", "meta_117_banques_gestion_d_actifs_et_back_office_historisat": "Banking, asset management, and back-office: historisation, reconciliation, measured quality, and indicator documentation with the beVault platform.", "meta_118_industries_data_vault_2_0_par_secteur_bevault": "Industries — Data Vault 2.0 by Sector | beVault", "meta_119_secteur_public_services_financiers_assurance_retai": "Public sector, financial services, insurance, retail, mobility, manufacturing, and energy: how beVault structures data for each industry.", "meta_120_data_vault_pour_l_assurance_bevault": "Data Vault for Insurance | beVault", "meta_121_contrats_sinistres_et_reporting_une_base_historis_": "Policies, claims, and reporting: a historised and reconciled database across business lines, without replacing existing management systems.", "meta_122_data_vault_pour_l_industrie_la_supply_chain_bevaul": "Data Vault for Manufacturing & Supply Chain | beVault", "meta_123_erp_mes_logistique_et_achats_connecter_et_historis": "ERP, MES, logistics, and procurement: connect and historise items, production, stock, and logistics events in a continuous chain of facts.", "meta_124_data_vault_pour_la_mobilit_les_services_urbains_be": "Data Vault for Mobility & Urban Services | beVault", "meta_125_stationnement_transport_et_services_aux_citoyens_h": "Parking, transport, and citizen services: historise operational flows and field reference data to enable management and reporting.", "meta_126_data_vault_pour_le_secteur_public_bevault": "Data Vault for the Public Sector | beVault", "meta_127_administrations_agences_et_op_rateurs_publics_stru": "Government bodies, agencies, and public operators: structure historised, documented data deployed within your own perimeter with beVault.", "meta_128_data_vault_pour_le_retail_les_biens_de_consommatio": "Data Vault for Retail & Consumer Goods | beVault", "meta_129_ventes_produits_stocks_et_points_de_vente_r_concil": "Sales, products, stock, and points of sale, reconciled and historised on a common basis for consistent management between HQ and the field.", "meta_130_data_vault_sur_amazon_redshift_structure_et_co_ts_": "Data Vault on Amazon Redshift: Controlled Structure & Costs | beVault", "meta_131_construire_une_architecture_data_vault_2_0_sur_ama": "Build a Data Vault 2.0 architecture on Amazon Redshift with beVault: distribution keys, sort keys, and beVault orchestration in your AWS environment.", "meta_132_bevault_aws_step_functions_orchestration_sur_aws": "beVault & AWS Step Functions: Orchestration on AWS", "meta_133_faire_cohabiter_l_orchestration_int_gr_e_de_bevaul": "Combine beVault's integrated orchestration with AWS Step Functions: triggers, dependencies, execution tracking, and integration with your AWS stack.", "meta_134_data_vault_sur_google_bigquery_structure_et_slots_": "Data Vault on Google BigQuery: Controlled Structure & Slots | beVault", "meta_135_construire_une_architecture_data_vault_2_0_sur_big": "Build a Data Vault 2.0 architecture on BigQuery with beVault: partitioning, clustering, incremental loading, and governed data marts.", "meta_136_data_vault_sur_databricks_structurer_le_lakehouse_": "Data Vault on Databricks: Structuring the Lakehouse | beVault", "meta_137_construire_une_fondation_data_vault_sur_delta_lake": "Build a Data Vault foundation on Delta Lake with beVault: historisation, complete lineage, and API/CDP exposure for your AI agents.", "meta_138_bevault_en_conteneurs_docker_d_ploiement_ma_tris_": "beVault in Docker Containers: Controlled Deployment", "meta_139_ex_cuter_bevault_en_conteneurs_dans_votre_infrastr": "Run beVault in containers on your infrastructure: reproducible environments, isolation, managed by your IT teams, on-premises, cloud or hybrid.", "meta_140_data_vault_sur_ibm_db2_structurer_les_donn_es_crit": "Data Vault on IBM DB2: Structure Critical Data | beVault", "meta_141_construire_une_architecture_data_vault_2_0_sur_ibm": "Build a Data Vault 2.0 architecture on IBM DB2 with beVault: generated native DB2 SQL, history tracking with no source impact, and regulatory traceability.", "meta_142_data_vault_par_plateforme_code_natif_g_n_r_bevault": "Data Vault by Platform: Generated Native Code | beVault", "meta_143_snowflake_amazon_redshift_microsoft_sql_server_et_": "Currently supports Snowflake, Redshift, SQL Server & PostgreSQL; Databricks, Fabric & BigQuery coming soon. beVault generates native code for the target platform.", "meta_144_data_vault_sur_oracle_r_duire_la_d_pendance_sans_t": "Data Vault on Oracle: Reduce Lock-in Without a Rebuild | beVault", "meta_145_construire_une_architecture_data_vault_2_0_sur_ora": "Build a Data Vault 2.0 architecture on Oracle with beVault: generated native Oracle SQL, non-destructive history, and progressive decoupling.", "meta_146_data_vault_sur_postgresql_la_fondation_open_source": "Data Vault on PostgreSQL: The Open Source Foundation | beVault", "meta_147_construire_une_architecture_data_vault_2_0_sur_pos": "Build a Data Vault 2.0 architecture on PostgreSQL with beVault: generated native SQL, on-premise, cloud or hybrid deployment, and no vendor lock-in.", "meta_148_data_vault_sur_snowflake_structurer_et_ma_triser_l": "Data Vault on Snowflake: Structure Data & Control Costs | beVault", "meta_149_construire_une_architecture_data_vault_2_0_sur_sno": "Build a Data Vault 2.0 architecture on Snowflake with beVault: optimised code, native orchestration and controlled credit consumption.", "meta_150_data_vault_sur_microsoft_sql_server_t_sql_natif_g_": "Data Vault on SQL Server: Generated Native T-SQL | beVault", "meta_151_construire_une_architecture_data_vault_2_0_sur_sql": "Build a Data Vault 2.0 architecture on SQL Server on-premise or Azure SQL with beVault: generated native T-SQL, without a forced cloud migration.", "meta_152_fondation_de_donn_es_pr_te_pour_l_ia_bevault": "AI-Ready Data Foundation | beVault", "meta_153_historique_contexte_m_tier_m_tadonn_es_qualit_et_l": "History, business context, metadata, quality and lineage: build a governed, reusable data foundation that your AI initiatives can rely on.", "meta_154_bi_reporting_des_chiffres_que_tout_le_monde_peut_e": "BI & Reporting: Numbers Everyone Can Explain | beVault", "meta_155_d_finitions_m_tier_partag_es_information_marts_gou": "Shared business definitions, governed Information Marts, history and lineage: make reporting more reliable without changing your visualisation tool.", "meta_156_qualit_gouvernance_la_gouvernance_ne_se_d_cr_te_pa": "Quality & Governance: Governance Can't Be Decreed | beVault", "meta_157_traduire_les_r_gles_en_contr_les_ex_cut_s_chaque_c": "Translate rules into controls executed on every load, measure quality, handle exceptions and preserve history and lineage.", "meta_158_moderniser_votre_entrep_t_de_donn_es_sans_repartir": "Modernise Your Data Warehouse Without Starting Over | beVault", "meta_159_faire_voluer_un_entrep_t_existant_domaine_par_doma": "Evolve an existing warehouse domain by domain: source consolidation, history preservation, coexistence with the current system and new consumption layers.", "meta_160_migration_erp_legacy_quitter_un_entrep_t_sans_tein": "ERP & Legacy Migration: Don't Turn Off the Lights | beVault", "meta_161_continuit_pr_servation_de_l_historique_et_r_ductio": "Continuity, history preservation and risk reduction: a controlled, domain-by-domain migration, with reconciliation between the old and new systems.", "meta_162_cas_d_usage_bevault_votre_stack_votre_enjeu": "beVault Use Cases — Your Stack, Your Challenge", "meta_163_migration_d_entrep_t_bi_reporting_fondation_ia_qua": "Warehouse migration, BI & reporting, AI foundation, quality & governance, MDM, Snowflake: discover how beVault addresses your specific situation.", "meta_164_mdm_int_gration_de_donn_es_un_client_cinq_syst_mes": "MDM & Data Integration: One Customer, Five Systems | beVault", "meta_165_r_concilier_les_identit_s_et_les_donn_es_de_r_f_re": "Reconcile identities and master data from CRM, ERP and billing systems without losing source context, on a historised and governed data foundation.", "meta_166_hubs_liens_satellites_la_m_canique_du_data_vault_e": "Hubs, Links, Satellites: Data Vault Mechanics Explained | beVault", "meta_167_comprendre_les_trois_objets_du_data_vault_2_0_hubs": "Understand the three core objects of Data Vault 2.0—hubs, links, and satellites—and the separation rule that makes the model scalable and auditable.", "meta_168_donn_es_sans_mod_le_la_maison_sans_plan_d_architec": "Data Without a Model: A House Without a Blueprint | beVault", "meta_169_pourquoi_la_mod_lisation_des_donn_es_conditionne_l": "Why data modelling determines a platform's lifespan, and what Data Vault 2.0 offers over traditional models.", "meta_170_fondation_ia_pr_parer_vos_donn_es_pour_l_intellige": "AI Foundation: Get Your Data Ready for AI | beVault", "meta_171_historisation_lignage_qualit_et_s_mantique_pourquo": "History, lineage, quality and semantics: why a Data Vault is the true foundation that your AI projects need.", "meta_172_plateformes_data_vault_comparer_le_p_rim_tre_r_el": "Data Vault Platforms — Comparing The True Scope", "meta_173_toutes_les_certifications_dv_2_1_ne_couvrent_pas_l": "Not all Data Vault 2.1 certifications cover the same scope. Compare Data Quality, orchestration, and on-premises deployment capabilities before you choose.", "meta_174_orchestration_int_gr_e_vs_externalis_e_le_co_t_r_e": "Integrated vs External Orchestration: The True Cost | beVault", "meta_175_airflow_dbt_scheduler_maison_ce_que_l_orchestratio": "Airflow, dbt, in-house schedulers: what external data workflow orchestration truly costs a data team, and the difference native orchestration makes.", "meta_176__quipes_data_cloud_first_pourquoi_bevault_va_plus_": "For Cloud-First Data Teams: Why beVault Goes Further", "meta_177_certification_dv_2_1_data_quality_native_et_orches": "DV 2.1 certification, native Data Quality, and integrated orchestration: what cloud-first tools leave you to handle, versus what beVault covers natively.", "meta_178_certification_dv_2_1_la_seule_garantie_ind_pendant": "Data Vault 2.1 Certification: The Only Independent Guarantee", "meta_179_bevault_est_certifi_data_vault_2_1_comprendre_ce_q": "beVault is Data Vault 2.1 certified. Understand what this independent audit truly validates and why it protects your architecture.", "meta_180_vitesse_de_livraison_livrer_plus_vite_un_nouveau_c": "Delivery Speed: Deliver New Use Cases Faster | beVault", "meta_181_ce_que_l_automatisation_data_vault_change_sur_le_d": "How Data Vault automation shortens the time between a business request and the final numbers—and how to assess the ROI in your own context.", "meta_182_data_quality_native_dans_la_plateforme_pas_c_t_bev": "Native Data Quality: Inside the Platform, Not Beside It | beVault", "meta_183_pourquoi_une_qualit_des_donn_es_int_gr_e_au_charge": "Why data quality integrated into the Data Vault load process transforms business trust—and what a separate quality tool really costs." }