[{"data":1,"prerenderedAt":8969},["ShallowReactive",2],{"header-shared":3,"footer-shared":42,"header-locale-en":185,"footer-locale-en":219,"industries-shared":304,"industries-locale-en":334,"navigation-shared":604,"navigation-locale-en":745,"mobile-header-shared":900,"mobile-header-locale-en":914,"resource-detail-en-blog-individuelle-netzwerkueberwachung-mit-dem-solarwinds-sdk":930,"resource-detail-related-en":1425,"resource-type-page-en-blogs":8924},{"id":4,"cta":5,"extension":7,"languages":8,"logo":15,"meta":18,"navigation":19,"stem":40,"__hash__":41},"headerShared\u002Fglobals\u002Flayout\u002Fheader.shared.yml",{"to":6},"\u002Fcontact","yml",[9,12],{"code":10,"flag":11},"de","🇩🇪",{"code":13,"flag":14},"en","🇬🇧",{"src":16,"alt":17},"\u002Fmedia\u002Flogos\u002Fheureka-logo-508x112.svg","heureka e-Business",{},[20,24,28,31,34,37],{"key":21,"to":22,"hasMegaMenu":23},"home","\u002F",false,{"key":25,"to":26,"hasMegaMenu":27,"megaMenuId":25},"solutions","\u002Fsolutions",true,{"key":29,"to":30,"hasMegaMenu":27,"megaMenuId":29},"industries","\u002Findustries",{"key":32,"to":33,"hasMegaMenu":27,"megaMenuId":32},"services","\u002Fservices",{"key":35,"to":36,"hasMegaMenu":27,"megaMenuId":35},"resources","\u002Fresources",{"key":38,"to":39,"hasMegaMenu":27,"megaMenuId":38},"company","\u002Fcompany\u002Fabout","globals\u002Flayout\u002Fheader.shared","wJh6vN1Q3lS2dWxCxFlnlRZ500wvOrmsYoIUVTtREY4",{"id":43,"company":44,"extension":7,"legal":54,"meta":74,"sections":75,"social":166,"stem":183,"__hash__":184},"footerShared\u002Fglobals\u002Flayout\u002Ffooter.shared.yml",{"name":45,"address":46,"phone":50,"phoneHref":51,"email":52,"emailHref":53},"heureka e-Business GmbH",{"street":47,"postalCode":48,"city":49},"Eichwiesenring 4F","70567","Stuttgart","+49 (0)7152 - 93 93 10","tel:+4971529393-10","heureka@heureka.com","mailto:heureka@heureka.com",{"links":55},[56,59,62,65,68,71],{"key":57,"to":58},"imprint","\u002Flegal\u002Fimprint",{"key":60,"to":61},"privacy","\u002Flegal\u002Fprivacy-policy",{"key":63,"to":64},"terms","\u002Flegal\u002Fterms-of-service",{"key":66,"to":67},"cookies","\u002Flegal\u002Fcookie-policy",{"key":69,"to":70},"subprocessors","\u002Flegal\u002Fsubprocessors",{"key":72,"to":73},"security-policy","\u002Flegal\u002Fsecurity-policy",{},{"solutions":76,"services":102,"company":128,"resources":146},{"links":77},[78,81,84,87,90,93,96,99],{"key":79,"to":80},"media-streaming","\u002Fsolutions\u002Fmedia-streaming",{"key":82,"to":83},"observability","\u002Fsolutions\u002Fobservability",{"key":85,"to":86},"managed-file-transfer","\u002Fsolutions\u002Fmanaged-file-transfer",{"key":88,"to":89},"it-security","\u002Fsolutions\u002Fit-security",{"key":91,"to":92},"it-operations","\u002Fsolutions\u002Fit-operations",{"key":94,"to":95},"it-service-management","\u002Fsolutions\u002Fit-service-management",{"key":97,"to":98},"data-modeling","\u002Fsolutions\u002Fdata-modeling",{"key":100,"to":101},"data-governance","\u002Fsolutions\u002Fdata-governance",{"links":103},[104,107,110,113,116,119,122,125],{"key":105,"to":106},"conception","\u002Fservices\u002Fconception",{"key":108,"to":109},"installations","\u002Fservices\u002Finstallations",{"key":111,"to":112},"integration-automation","\u002Fservices\u002Fintegration-automation",{"key":114,"to":115},"migrations","\u002Fservices\u002Fmigrations",{"key":117,"to":118},"data-model-migration","\u002Fservices\u002Fdata-model-migration",{"key":120,"to":121},"consulting","\u002Fservices\u002Fconsulting",{"key":123,"to":124},"trainings","\u002Fservices\u002Ftrainings",{"key":126,"to":127},"support","\u002Fservices\u002Fsupport",{"links":129},[130,133,135,138,141,144],{"key":131,"to":132},"products","\u002Fsolutions\u002Fproducts",{"key":134,"to":39},"about",{"key":136,"to":137},"partners","\u002Fcompany\u002Fpartners",{"key":139,"to":140},"careers","\u002Fcompany\u002Fcareers",{"key":142,"to":143},"security","\u002Fcompany\u002Fsecurity",{"key":145,"to":6},"contact",{"links":147},[148,151,154,157,160,163],{"key":149,"to":150},"blog","\u002Fresources#blog",{"key":152,"to":153},"webinars","\u002Fresources#webinars",{"key":155,"to":156},"case-studies","\u002Fresources#case-studies",{"key":158,"to":159},"faq","\u002Fresources#faq",{"key":161,"to":162},"newsletter","\u002Fnewsletter",{"key":164,"to":165},"inside-portal","https:\u002F\u002Finside.heureka.com",[167,171,175,179],{"label":168,"href":169,"icon":170},"LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fheureka-e-business-gmbh\u002Fposts\u002F?feedView=all","linkedin",{"label":172,"href":173,"icon":174},"XING","https:\u002F\u002Fwww.xing.com\u002Fpages\u002Fheurekae-businessgmbh","xing",{"label":176,"href":177,"icon":178},"X","https:\u002F\u002Fx.com\u002Fheurekagotdg","x-social",{"label":180,"href":181,"icon":182},"Facebook","https:\u002F\u002Fde-de.facebook.com\u002Fheureka.eBusiness\u002F","facebook","globals\u002Flayout\u002Ffooter.shared","BGWF_LzcFA5LnTMWSNU0Qt8KvCTO9zz6s1M_R6gQoCo",{"id":186,"accessibility":187,"cta":194,"extension":7,"languages":196,"meta":202,"navigation":203,"stem":217,"__hash__":218},"headerLocaleEn\u002Flocales\u002Fenglish\u002Fglobals\u002Fheader.locale.yml",{"logoAriaLabel":188,"languageSelectLabel":189,"selectLanguageLabel":190,"openMenuLabel":191,"closeMenuLabel":192,"mainNavigationLabel":193},"heureka e-Business home","Language selection","Select language","Open menu","Close menu","Main navigation",{"label":195},"Talk to Experts",{"labels":197},[198,200],{"key":10,"value":199},"German",{"key":13,"value":201},"English",{},{"labels":204},[205,207,209,211,213,215],{"key":21,"value":206},"Home",{"key":25,"value":208},"Solutions",{"key":29,"value":210},"Industries",{"key":32,"value":212},"Services",{"key":35,"value":214},"Resources",{"key":38,"value":216},"Company","locales\u002Fenglish\u002Fglobals\u002Fheader.locale","elWkdc_qly6uHu8b1_0eWkPEQq5BIBmxw-JW2Bw6vZ0",{"id":220,"contactTitle":221,"copyright":222,"extension":7,"legal":223,"meta":237,"sections":238,"stem":302,"__hash__":303},"footerLocaleEn\u002Flocales\u002Fenglish\u002Fglobals\u002Ffooter.locale.yml","Contact","All rights reserved.",{"labels":224},[225,227,229,231,233,235],{"key":57,"value":226},"Imprint",{"key":60,"value":228},"Privacy",{"key":63,"value":230},"Terms & Conditions",{"key":66,"value":232},"Cookies",{"key":69,"value":234},"Subprocessors",{"key":72,"value":236},"Security Policy",{},{"solutions":239,"services":257,"company":275,"resources":288},{"title":208,"labels":240},[241,243,245,247,249,251,253,255],{"key":79,"value":242},"Media Streaming",{"key":82,"value":244},"Observability & Monitoring",{"key":85,"value":246},"Managed File Transfer",{"key":88,"value":248},"IT Security",{"key":91,"value":250},"IT Operations",{"key":94,"value":252},"IT Service Management",{"key":97,"value":254},"Data Modeling",{"key":100,"value":256},"Data Governance",{"title":212,"labels":258},[259,261,263,265,267,269,271,273],{"key":105,"value":260},"Conception & Workshops",{"key":108,"value":262},"Installations & Setup",{"key":111,"value":264},"Integration & Automation",{"key":114,"value":266},"Migrations",{"key":117,"value":268},"Data Model Migration",{"key":120,"value":270},"Consulting",{"key":123,"value":272},"heureka Academy",{"key":126,"value":274},"Support Packages",{"title":216,"labels":276},[277,279,281,283,285,287],{"key":131,"value":278},"Products",{"key":134,"value":280},"About heureka",{"key":136,"value":282},"Partners",{"key":139,"value":284},"Careers",{"key":142,"value":286},"Security & Compliance",{"key":145,"value":221},{"title":214,"labels":289},[290,292,294,296,298,300],{"key":149,"value":291},"Blog",{"key":152,"value":293},"Webinars",{"key":155,"value":295},"Success Stories",{"key":158,"value":297},"FAQ",{"key":161,"value":299},"Newsletter",{"key":164,"value":301},"Inside Portal","locales\u002Fenglish\u002Fglobals\u002Ffooter.locale","OL7vdEHDDImTtXxjHZfOycrydjcR-moQDcaupH0bG8o",{"id":305,"extension":7,"items":306,"meta":331,"stem":332,"__hash__":333},"industriesShared\u002Fglobals\u002Findustries\u002Findustries.shared.yml",[307,311,315,319,323,327],{"slug":308,"icon":309,"solutions":310},"insurance","i-heroicons:shield-check",[85,82,100],{"slug":312,"icon":313,"solutions":314},"it-providers","i-heroicons:server-stack",[82,91,88],{"slug":316,"icon":317,"solutions":318},"manufacturing","i-heroicons:building-office-2",[82,85,88],{"slug":320,"icon":321,"solutions":322},"finance","i-heroicons:banknotes",[85,82,100],{"slug":324,"icon":325,"solutions":326},"public-sector","i-heroicons:building-library",[82,85,91],{"slug":328,"icon":329,"solutions":330},"energy","i-heroicons:bolt",[82,88,91],{},"globals\u002Findustries\u002Findustries.shared","IUf76cv9H2EtDVg4YiaWy4tCQwA1M_tM_-Q_GJcvSZM",{"id":335,"extension":7,"items":336,"meta":601,"stem":602,"__hash__":603},"industriesLocaleEn\u002Flocales\u002Fenglish\u002Fglobals\u002Findustries\u002Findustries.locale.yml",[337,381,425,469,513,557],{"slug":308,"title":338,"description":339,"story":340,"challenges":367,"outcomes":372,"projects":377},"Insurance","Secure data handling, compliance automation, and operational reliability for insurance providers navigating digital transformation.",{"headline":341,"subheadline":342,"scenario":343,"journey":346,"approach":357},"Digital transformation without risking compliance","Insurance providers face unique challenges: legacy systems that can't be easily replaced, strict regulatory requirements, and the constant pressure to modernize.",{"title":344,"story":345},"A familiar situation","Your claims processing system runs on infrastructure that's been in place for years. It works - most of the time. But when it doesn't, nobody knows exactly why. Meanwhile, regulators are asking questions about data handling that your team struggles to answer with confidence. DORA deadlines are approaching, and the gap between where you are and where you need to be feels overwhelming.",{"before":347,"after":352},[348,349,350,351],"Siloed systems with no unified view of operations","Compliance evidence gathered manually before each audit","File transfers between partners using outdated protocols","Incidents discovered by users, not monitoring systems",[353,354,355,356],"Connected visibility across all critical systems","Continuous compliance monitoring with audit-ready reports","Secure, automated file exchange with full audit trails","Proactive detection before business impact",[358,361,364],{"title":359,"description":360},"Understand your landscape","We start by mapping your current systems, data flows, and compliance requirements - no assumptions, no shortcuts.",{"title":362,"description":363},"Design for your reality","Solutions that work with your existing investments, not rip-and-replace approaches that disrupt operations.",{"title":365,"description":366},"Build knowledge, not dependency","Your team learns alongside ours. When we're done, you own the capability.",[368,369,370,371],"Legacy system modernization","Regulatory compliance (DORA, GDPR)","Secure data exchange with partners","Claims processing efficiency",[373,374,375,376],"Compliant data architectures","Automated file transfer workflows","Reduced operational risk","Accelerated digital transformation",[378,379,380],"MFT platform migration","Observability rollout for core systems","Data governance framework implementation",{"slug":312,"title":382,"description":383,"story":384,"challenges":411,"outcomes":416,"projects":421},"IT Providers","Scalable monitoring, automation, and security solutions that help IT service providers deliver more value to their customers.",{"headline":385,"subheadline":386,"scenario":387,"journey":390,"approach":401},"Scale your services without scaling your problems","Managing IT for multiple clients means multiplied complexity. Every new customer adds monitoring overhead, security considerations, and SLA pressure.",{"title":388,"story":389},"The scaling challenge","You've grown from a handful of clients to dozens. Each one has different systems, different expectations, different definitions of \"urgent.\" Your team is stretched thin, jumping between dashboards and trying to maintain visibility across environments that have nothing in common. Client satisfaction depends on catching problems before they do - but with this many moving parts, something always slips through.",{"before":391,"after":396},[392,393,394,395],"Separate monitoring tools for each client environment","SLA reporting compiled manually each month","Security posture varies wildly between clients","Scaling means hiring, not optimizing",[397,398,399,400],"Unified multi-tenant visibility in a single pane of glass","Automated SLA tracking and client-ready reports","Consistent security baseline across all clients","Growth through efficiency, not just headcount",[402,405,408],{"title":403,"description":404},"Consolidate without compromise","Multi-tenant architectures that give you unified visibility while keeping client data properly isolated.",{"title":406,"description":407},"Automate the routine","Free your team from repetitive tasks so they can focus on what actually requires human judgment.",{"title":409,"description":410},"Build repeatable practices","Standardized approaches that work across clients, so onboarding new customers doesn't mean starting from scratch.",[412,413,414,415],"Multi-tenant monitoring complexity","Client SLA management","Security posture across client environments","Scaling operations efficiently",[417,418,419,420],"Unified multi-tenant monitoring","Automated SLA reporting","Consistent security baseline","Operational efficiency at scale",[422,423,424],"Multi-tenant monitoring platform","Automated patch management rollout","Security assessment program",{"slug":316,"title":426,"description":427,"story":428,"challenges":455,"outcomes":460,"projects":465},"Manufacturing","OT\u002FIT convergence monitoring, secure supply chain data exchange, and operational technology visibility for modern manufacturers.",{"headline":429,"subheadline":430,"scenario":431,"journey":434,"approach":445},"When IT meets OT, visibility becomes critical","Modern manufacturing blurs the line between information technology and operational technology. Monitoring both requires understanding both.",{"title":432,"story":433},"The convergence reality","Your production floor is increasingly connected. PLCs talk to enterprise systems, supply chain data flows in real time, and every minute of unplanned downtime costs more than anyone wants to calculate. But your IT monitoring wasn't built for industrial protocols, and your OT team doesn't trust IT tools near their systems. The gap between these worlds is where problems hide.",{"before":435,"after":440},[436,437,438,439],"IT and OT monitoring in separate silos","Supply chain visibility limited to batch reports","Production issues discovered after the fact","Industrial systems treated as \"not IT's problem\"",[441,442,443,444],"Unified view across IT infrastructure and industrial systems","Real-time supply chain data exchange with partners","Early warning systems for production anomalies","Holistic security that includes OT environments",[446,449,452],{"title":447,"description":448},"Bridge the IT\u002FOT divide","We speak both languages. Solutions that respect OT requirements while delivering IT-grade visibility.",{"title":450,"description":451},"Protect what matters","Industrial systems require specialized security approaches. We understand the constraints and work within them.",{"title":453,"description":454},"Minimize disruption","Production environments can't tolerate experiments. Every change is planned, tested, and executed with operational continuity in mind.",[456,457,458,459],"OT\u002FIT convergence gaps","Supply chain data visibility","Production downtime costs","Cybersecurity for industrial systems",[461,462,463,464],"Unified OT\u002FIT monitoring","Secure supply chain data exchange","Reduced unplanned downtime","Industrial cybersecurity baseline",[466,467,468],"OT monitoring implementation","Supply chain MFT deployment","Vulnerability assessment for industrial systems",{"slug":320,"title":470,"description":471,"story":472,"challenges":499,"outcomes":504,"projects":509},"Finance","Regulatory-compliant infrastructure monitoring, secure file transfers, and data governance for banks and financial services.",{"headline":473,"subheadline":474,"scenario":475,"journey":478,"approach":489},"Regulatory confidence through operational excellence","Financial services operate under constant regulatory scrutiny. Compliance isn't a checkbox - it's a continuous capability that requires real-time visibility.",{"title":476,"story":477},"The compliance pressure","DORA requirements are clear on paper but complex in practice. Regulators want proof of operational resilience - not just policies, but evidence that your systems can detect, respond to, and recover from incidents. Your current monitoring gives you pieces of the picture, but stitching them together for an audit is a manual scramble every time.",{"before":479,"after":484},[480,481,482,483],"Compliance evidence assembled manually for each audit","File transfers with partners lack complete audit trails","Data lineage documented in spreadsheets","Incident response depends on tribal knowledge",[485,486,487,488],"Continuous compliance monitoring with automated evidence","Every file transfer logged, encrypted, and auditable","Complete data lineage from source to consumption","Documented, tested incident response procedures",[490,493,496],{"title":491,"description":492},"Build compliance into operations","Not a separate workstream, but an integral part of how your systems work every day.",{"title":494,"description":495},"Automate evidence collection","Auditors shouldn't trigger fire drills. The evidence should already be there, continuously collected and organized.",{"title":497,"description":498},"Prepare for examinations","We help you understand what regulators will look for and ensure you can demonstrate capability, not just intent.",[500,501,502,503],"DORA\u002FBaFin compliance","Secure interbank file transfers","Real-time system monitoring requirements","Data lineage and quality",[505,506,507,508],"Regulatory-compliant monitoring","Auditable file transfer workflows","Real-time operational dashboards","Complete data lineage",[510,511,512],"DORA compliance monitoring","Interbank MFT modernization","Enterprise data governance rollout",{"slug":324,"title":514,"description":515,"story":516,"challenges":543,"outcomes":548,"projects":553},"Public Sector","Secure, sovereign, and compliant IT operations for government agencies and public institutions.",{"headline":517,"subheadline":518,"scenario":519,"journey":522,"approach":533},"Modernization with sovereignty and security","Government IT must balance modernization pressure with data sovereignty requirements and security constraints that commercial organizations don't face.",{"title":520,"story":521},"The modernization mandate","Citizens expect digital services. Leadership expects cost efficiency. Security requirements expect perfection. And all of this on infrastructure that may have been designed before \"cloud\" was a computing term. You need to modernize, but you can't compromise on data sovereignty or citizen data protection. The path forward isn't obvious.",{"before":523,"after":528},[524,525,526,527],"Legacy systems with limited visibility","Data sovereignty concerns blocking cloud adoption","Citizen data protection handled inconsistently","Budget constraints limiting improvement options",[529,530,531,532],"Modern monitoring respecting sovereignty requirements","Secure, sovereign-compliant infrastructure choices","Consistent data protection across all citizen touchpoints","Cost-optimized operations through automation",[534,537,540],{"title":535,"description":536},"Sovereignty-first architecture","Solutions designed from the start to meet data residency and sovereignty requirements - not retrofitted afterwards.",{"title":538,"description":539},"Work within constraints","Budget limitations are real. We help you prioritize investments that deliver the most value within available resources.",{"title":541,"description":542},"Long-term partnership","Public sector projects often span multiple budget cycles. We plan for sustainability, not just implementation.",[544,545,546,547],"Data sovereignty requirements","Legacy infrastructure modernization","Citizen data protection","Budget constraints",[549,550,551,552],"Sovereign-compliant infrastructure","Modernized monitoring and operations","Enhanced citizen data protection","Cost-optimized operations",[554,555,556],"Sovereign monitoring deployment","Secure file transfer for citizen data","IT operations automation",{"slug":328,"title":558,"description":559,"story":560,"challenges":587,"outcomes":592,"projects":597},"Energy","Critical infrastructure monitoring, SCADA security, and operational resilience for energy providers and utilities.",{"headline":561,"subheadline":562,"scenario":563,"journey":566,"approach":577},"Critical infrastructure requires critical visibility","Energy infrastructure is inherently critical. Monitoring it requires understanding both the technology and the consequences of getting it wrong.",{"title":564,"story":565},"The criticality reality","When your systems fail, it's not just a business problem - it's a public safety issue. NIS2 requirements formalize what you already know: you need complete visibility into your infrastructure, the ability to detect threats early, and proven response capabilities. Your current monitoring handles the IT side, but SCADA systems and distributed assets are a different challenge entirely.",{"before":567,"after":572},[568,569,570,571],"Traditional IT monitoring blind to OT systems","SCADA and ICS systems monitored separately","NIS2 compliance gaps identified but not addressed","Distributed assets with inconsistent visibility",[573,574,575,576],"Unified visibility across IT and OT environments","SCADA-aware monitoring that respects operational constraints","Demonstrated NIS2 compliance capabilities","Centralized management of distributed infrastructure",[578,581,584],{"title":579,"description":580},"Understand the stakes","Critical infrastructure monitoring isn't about dashboards - it's about protecting essential services. We approach every project with that context.",{"title":582,"description":583},"Specialized expertise","SCADA and ICS environments have unique requirements. Our team includes people who've worked in these environments, not just around them.",{"title":585,"description":586},"Compliance as capability","NIS2 isn't just paperwork. We help you build the actual capabilities that the regulations require.",[588,589,590,591],"Critical infrastructure protection","SCADA\u002FICS monitoring","Regulatory compliance (NIS2)","Distributed asset management",[593,594,595,596],"Critical infrastructure visibility","SCADA-aware monitoring","NIS2 compliance readiness","Centralized asset management",[598,599,600],"SCADA monitoring integration","Energy grid observability","NIS2 compliance assessment",{},"locales\u002Fenglish\u002Fglobals\u002Findustries\u002Findustries.locale","6hhO1-13_rlPW0PdSO6hTOCK9hZNk2zZOI9Q2AZhLio",{"id":605,"company":606,"extension":7,"industries":617,"meta":628,"resources":629,"services":655,"solutions":679,"stem":743,"__hash__":744},"navigationShared\u002Fglobals\u002Flayout\u002Fnavigation.shared.yml",{"items":607,"cta":614,"location":615},[608,609,611,613],{"key":134,"to":39,"icon":317},{"key":136,"to":137,"icon":610},"i-heroicons:squares-2x2",{"key":139,"to":140,"icon":612},"i-heroicons:briefcase",{"key":142,"to":143,"icon":309},{"to":39},{"city":49,"country":616},"Germany",{"stats":618,"cta":627},[619,622,624],{"key":620,"value":621},"customers","1.000+",{"key":29,"value":623},"40+",{"key":625,"value":626},"years","30+",{"to":30},{},{"learn":630,"proof":639,"support":651,"cta":654},[631,633,635,637],{"key":149,"to":150,"icon":632},"i-heroicons:newspaper",{"key":152,"to":153,"icon":634},"i-heroicons:video-camera",{"key":161,"to":162,"icon":636},"i-heroicons:envelope",{"key":164,"to":165,"icon":638},"i-heroicons:lock-closed",[640,643,647],{"key":641,"to":156,"icon":642},"success-stories","i-heroicons:trophy",{"key":644,"to":645,"icon":646},"whitepapers","\u002Fresources#whitepapers","i-heroicons:document-text",{"key":648,"to":649,"icon":650},"events","\u002Fresources\u002Fevents","i-heroicons:calendar-days",[652],{"key":158,"to":159,"icon":653},"i-heroicons:question-mark-circle",{"to":156},{"professional":656,"enablement":669,"cta":678},[657,659,661,663,665,667],{"key":105,"to":106,"icon":658},"i-heroicons:light-bulb",{"key":108,"to":109,"icon":660},"i-heroicons:arrow-down-tray",{"key":111,"to":112,"icon":662},"i-heroicons:code-bracket-square",{"key":114,"to":115,"icon":664},"i-heroicons:arrow-right",{"key":117,"to":118,"icon":666},"i-heroicons:arrow-path-rounded-square",{"key":120,"to":121,"icon":668},"i-heroicons:user-group",[670,672,676],{"key":123,"to":124,"icon":671},"i-heroicons:academic-cap",{"key":673,"to":674,"icon":675},"documentation","\u002Fservices\u002Fdocumentation","i-heroicons:book-open",{"key":126,"to":127,"icon":677},"i-heroicons:lifebuoy",{"to":127},{"byNeed":680,"popular":703,"byNeedCallToAction":739,"popularCallToAction":741},[681,684,686,688,691,694,697,700],{"key":82,"to":83,"icon":682,"subKey":683},"i-heroicons:eye","observability-sub",{"key":85,"to":86,"icon":309,"subKey":685},"managed-file-transfer-sub",{"key":88,"to":89,"icon":638,"subKey":687},"it-security-sub",{"key":91,"to":92,"icon":689,"subKey":690},"i-heroicons:cog-6-tooth","it-operations-sub",{"key":94,"to":95,"icon":692,"subKey":693},"i-heroicons:wrench-screwdriver","it-service-management-sub",{"key":97,"to":98,"icon":695,"subKey":696},"i-heroicons:circle-stack","data-modeling-sub",{"key":100,"to":101,"icon":698,"subKey":699},"i-heroicons:chart-bar","data-governance-sub",{"key":79,"to":80,"icon":701,"subKey":702},"i-heroicons:play-circle","media-streaming-sub",[704,708,712,717,722,727,731,735],{"key":705,"to":706,"icon":682,"subKey":707},"solarwinds-observability","\u002Fsolutions\u002Fproducts\u002Fsolarwinds-observability-self-hosted","solarwinds-observability-sub",{"key":709,"to":710,"icon":695,"subKey":711},"solarwinds-dpa","\u002Fsolutions\u002Fproducts\u002Fsolarwinds-database-performance-analyzer","solarwinds-dpa-sub",{"key":713,"to":714,"icon":715,"subKey":716},"solarwinds-arm","\u002Fsolutions\u002Fproducts\u002Fsolarwinds-access-rights-manager","i-heroicons:key","solarwinds-arm-sub",{"key":718,"to":719,"icon":720,"subKey":721},"progress-moveit","\u002Fsolutions\u002Fproducts\u002Fprogress-moveit-transfer","i-heroicons:arrows-right-left","progress-moveit-sub",{"key":723,"to":724,"icon":725,"subKey":726},"tenable-one","\u002Fsolutions\u002Fproducts\u002Ftenable-one","i-heroicons:shield-exclamation","tenable-one-sub",{"key":728,"to":729,"icon":313,"subKey":730},"n-able-n-central","\u002Fsolutions\u002Fproducts\u002Fn-able-n-central","n-able-n-central-sub",{"key":732,"to":733,"icon":610,"subKey":734},"erwin-data-modeler","\u002Fsolutions\u002Fproducts\u002Fquest-erwin-data-modeler","erwin-data-modeler-sub",{"key":736,"to":737,"icon":658,"subKey":738},"erwin-data-intelligence","\u002Fsolutions\u002Fproducts\u002Fquest-erwin-data-intelligence-suite","erwin-data-intelligence-sub",{"to":26,"icon":740},"i-heroicons:sparkles",{"to":132,"icon":742},"i-heroicons:cube","globals\u002Flayout\u002Fnavigation.shared","b0FdNSJH695HMltiuk4-9cZlnCEB78L6R8Dn85ET40I",{"id":746,"company":747,"extension":7,"industries":760,"meta":774,"resources":775,"services":800,"solutions":822,"stem":898,"__hash__":899},"navigationLocaleEn\u002Flocales\u002Fenglish\u002Fglobals\u002Fnavigation.locale.yml",{"section":748,"cta":755},{"title":216,"labels":749},[750,751,752,753],{"key":134,"value":280},{"key":136,"value":282},{"key":139,"value":284},{"key":142,"value":754},"Security",{"headline":756,"description":757,"buttonLabel":758,"highlights":759},"Enterprise IT, done right.","Based in Stuttgart, serving enterprises across the DACH region with 30+ years of experience.","Learn About Us",[],{"section":761,"stats":763,"cta":770},{"title":762},"Industries we serve",{"labels":764},[765,767,768],{"key":620,"value":766},"Customers",{"key":29,"value":210},{"key":625,"value":769},"Years",{"headline":771,"buttonLabel":772,"highlights":773},"","View All Industries",[],{},{"learn":776,"proof":783,"support":791,"cta":795},{"title":777,"labels":778},"Knowledge",[779,780,781,782],{"key":149,"value":291},{"key":152,"value":293},{"key":161,"value":299},{"key":164,"value":301},{"title":784,"labels":785},"Proof",[786,787,789],{"key":641,"value":295},{"key":644,"value":788},"Whitepapers",{"key":648,"value":790},"Events",{"title":792,"labels":793},"Support",[794],{"key":158,"value":297},{"headline":796,"description":797,"buttonLabel":798,"highlights":799},"Success stories & insights","Read how enterprises like yours solved real challenges. Preview our case studies and whitepapers.","Browse Case Studies",[],{"professional":801,"enablement":810,"cta":817},{"title":802,"labels":803},"Professional Services",[804,805,806,807,808,809],{"key":105,"value":260},{"key":108,"value":262},{"key":111,"value":264},{"key":114,"value":266},{"key":117,"value":268},{"key":120,"value":270},{"title":811,"labels":812},"Enablement & Ongoing",[813,814,816],{"key":123,"value":272},{"key":673,"value":815},"Documentation",{"key":126,"value":274},{"headline":818,"description":819,"buttonLabel":820,"highlights":821},"Support that takes ownership.","From basic support to fully managed operations, we offer tiered packages that scale with your needs.","Compare Support Options",[],{"byNeed":823,"popular":856},{"cta":824,"title":827,"description":828,"labels":829},{"buttonLabel":825,"description":826},"View All Solutions","Browse the full catalog","By business need","Find your fit",[830,832,834,836,837,839,840,842,843,845,846,848,849,851,853,855],{"key":82,"value":831},"Prevent Downtime Proactively",{"key":683,"value":833},"Observability",{"key":85,"value":835},"Protect Critical File Exchange",{"key":685,"value":246},{"key":88,"value":838},"Minimize IT Security Risks",{"key":687,"value":248},{"key":91,"value":841},"Automate IT Operations",{"key":690,"value":250},{"key":94,"value":844},"Structure IT Services",{"key":693,"value":252},{"key":97,"value":847},"Build Future-Ready Data Architecture",{"key":696,"value":254},{"key":100,"value":850},"Govern Enterprise Data",{"key":699,"value":852},"Data & Governance",{"key":79,"value":854},"Deliver Reliable Streaming at Scale",{"key":702,"value":242},{"cta":857,"title":860,"description":861,"labels":862},{"buttonLabel":858,"description":859},"All Products","Explore our portfolio","Popular solutions","Top picks",[863,865,867,869,871,873,875,877,879,882,884,886,888,890,892,894,896],{"key":705,"value":864},"SolarWinds Observability Self-hosted",{"key":709,"value":866},"SolarWinds Database Performance Analyzer",{"key":713,"value":868},"SolarWinds Access Rights Manager",{"key":718,"value":870},"Progress MOVEit Transfer",{"key":723,"value":872},"Tenable One",{"key":728,"value":874},"N-able N-central",{"key":732,"value":876},"erwin Data Modeler",{"key":736,"value":878},"erwin Data Intelligence",{"key":880,"value":881},"logzilla","LogZilla AI Platform",{"key":707,"value":883},"Full-stack monitoring",{"key":711,"value":885},"Database insights",{"key":716,"value":887},"Access governance",{"key":721,"value":889},"Secure file transfer",{"key":726,"value":891},"Exposure management",{"key":730,"value":893},"RMM platform",{"key":734,"value":895},"Data architecture",{"key":738,"value":897},"Data governance","locales\u002Fenglish\u002Fglobals\u002Fnavigation.locale","SfzkW7rKoujXkpsTjkAlFPt8riIZ8rlWu_6eeopTkXU",{"id":4,"cta":901,"extension":7,"languages":902,"logo":905,"meta":906,"navigation":907,"stem":40,"__hash__":41},{"to":6},[903,904],{"code":10,"flag":11},{"code":13,"flag":14},{"src":16,"alt":17},{},[908,909,910,911,912,913],{"key":21,"to":22,"hasMegaMenu":23},{"key":25,"to":26,"hasMegaMenu":27,"megaMenuId":25},{"key":29,"to":30,"hasMegaMenu":27,"megaMenuId":29},{"key":32,"to":33,"hasMegaMenu":27,"megaMenuId":32},{"key":35,"to":36,"hasMegaMenu":27,"megaMenuId":35},{"key":38,"to":39,"hasMegaMenu":27,"megaMenuId":38},{"id":186,"accessibility":915,"cta":916,"extension":7,"languages":917,"meta":921,"navigation":922,"stem":217,"__hash__":218},{"logoAriaLabel":188,"languageSelectLabel":189,"selectLanguageLabel":190,"openMenuLabel":191,"closeMenuLabel":192,"mainNavigationLabel":193},{"label":195},{"labels":918},[919,920],{"key":10,"value":199},{"key":13,"value":201},{},{"labels":923},[924,925,926,927,928,929],{"key":21,"value":206},{"key":25,"value":208},{"key":29,"value":210},{"key":32,"value":212},{"key":35,"value":214},{"key":38,"value":216},{"resource":931,"categoryValue":1424},{"id":932,"title":933,"assessmentSlug":934,"associatedSolution":934,"authors":935,"body":937,"category":934,"ctaLabel":934,"date":1410,"dateModified":934,"deliveryFormat":934,"description":1411,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":1413,"navigation":27,"newsletterTopic":934,"path":1414,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":1417,"slug":1421,"stem":1422,"teaser":934,"type":934,"__hash__":1423},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Findividuelle-netzwerkueberwachung-mit-dem-solarwinds-sdk.md","Custom Network Monitoring with the SolarWinds SDK",null,[936],"Kai Bosch",{"type":938,"value":939,"toc":1405},"minimark",[940,952,957,965,973,1093,1102,1105,1108,1115,1118,1121,1130,1134,1137,1140,1202,1205,1213,1220,1256,1263,1266,1340,1346,1349,1377,1381,1401],[941,942,943,944,951],"p",{},"The Software Development Kit for SolarWinds Orion is a collection of tools for extending the monitoring platform. It primarily supports custom solutions in PowerShell and Python, but it can also be used independently through SOAP and REST. The ",[945,946,950],"a",{"href":947,"rel":948},"https:\u002F\u002Fgithub.com\u002Fsolarwinds\u002FOrionSDK\u002F",[949],"nofollow","Orion SDK is available on GitHub",".",[953,954,956],"h2",{"id":955},"simple-data-manipulation-with-swis","Simple Data Manipulation with SWIS",[941,958,959,960,951],{},"The SolarWinds Information Service (SWIS) is a central interface for querying and modifying Orion data. It provides the SolarWinds Query Language (SWQL), a SQL-like query language. The underlying ",[945,961,964],{"href":962,"rel":963},"https:\u002F\u002Fsolarwinds.github.io\u002FOrionSDK\u002Fschema\u002Findex.html",[949],"SWIS data schema is documented online",[941,966,967,968,972],{},"The following PowerShell example finds applications containing a component monitor named ",[969,970,971],"code",{},"get mountpoints",". It then identifies the associated nodes and displays their names and IDs:",[974,975,979],"pre",{"className":976,"code":977,"language":978,"meta":771,"style":771},"language-powershell shiki shiki-themes material-theme-palenight github-light","Add-PSSnapin SwisSnapin;\n\n$swis = Connect-Swis;\n\n# Name of the application monitor\n$ComponentName = \"get mountpoints\";\n\n# Get application IDs for applications containing the component monitor\n[string]$sAppIDs = Get-SwisData $swis \"SELECT ApplicationID FROM Orion.APM.Component WHERE Name = @name\" @{name = $ComponentName};\n$aAppIDs = $sAppIDs.Split(\" \");\n\nWrite-Output \"Found $($aAppIDs.Length) Application(s) with Component\";\n\nForEach ($sAppID in $aAppIDs) {\n    # Get its node ID and name\n    $nodeID = Get-SwisData $swis \"SELECT NodeID FROM Orion.APM.Application WHERE ApplicationID = @AppID\" @{AppID = $sAppID};\n    $NodeName = Get-SwisData $swis \"SELECT NodeName FROM Orion.Nodes WHERE NodeID = @node;\" @{node = $nodeID};\n    Write-Output \"Node ID: $($nodeID) Name: $($NodeName)\";\n}\n","powershell",[969,980,981,989,995,1001,1006,1012,1018,1023,1029,1035,1041,1046,1052,1057,1063,1069,1075,1081,1087],{"__ignoreMap":771},[982,983,986],"span",{"class":984,"line":985},"line",1,[982,987,988],{},"Add-PSSnapin SwisSnapin;\n",[982,990,992],{"class":984,"line":991},2,[982,993,994],{"emptyLinePlaceholder":27},"\n",[982,996,998],{"class":984,"line":997},3,[982,999,1000],{},"$swis = Connect-Swis;\n",[982,1002,1004],{"class":984,"line":1003},4,[982,1005,994],{"emptyLinePlaceholder":27},[982,1007,1009],{"class":984,"line":1008},5,[982,1010,1011],{},"# Name of the application monitor\n",[982,1013,1015],{"class":984,"line":1014},6,[982,1016,1017],{},"$ComponentName = \"get mountpoints\";\n",[982,1019,1021],{"class":984,"line":1020},7,[982,1022,994],{"emptyLinePlaceholder":27},[982,1024,1026],{"class":984,"line":1025},8,[982,1027,1028],{},"# Get application IDs for applications containing the component monitor\n",[982,1030,1032],{"class":984,"line":1031},9,[982,1033,1034],{},"[string]$sAppIDs = Get-SwisData $swis \"SELECT ApplicationID FROM Orion.APM.Component WHERE Name = @name\" @{name = $ComponentName};\n",[982,1036,1038],{"class":984,"line":1037},10,[982,1039,1040],{},"$aAppIDs = $sAppIDs.Split(\" \");\n",[982,1042,1044],{"class":984,"line":1043},11,[982,1045,994],{"emptyLinePlaceholder":27},[982,1047,1049],{"class":984,"line":1048},12,[982,1050,1051],{},"Write-Output \"Found $($aAppIDs.Length) Application(s) with Component\";\n",[982,1053,1055],{"class":984,"line":1054},13,[982,1056,994],{"emptyLinePlaceholder":27},[982,1058,1060],{"class":984,"line":1059},14,[982,1061,1062],{},"ForEach ($sAppID in $aAppIDs) {\n",[982,1064,1066],{"class":984,"line":1065},15,[982,1067,1068],{},"    # Get its node ID and name\n",[982,1070,1072],{"class":984,"line":1071},16,[982,1073,1074],{},"    $nodeID = Get-SwisData $swis \"SELECT NodeID FROM Orion.APM.Application WHERE ApplicationID = @AppID\" @{AppID = $sAppID};\n",[982,1076,1078],{"class":984,"line":1077},17,[982,1079,1080],{},"    $NodeName = Get-SwisData $swis \"SELECT NodeName FROM Orion.Nodes WHERE NodeID = @node;\" @{node = $nodeID};\n",[982,1082,1084],{"class":984,"line":1083},18,[982,1085,1086],{},"    Write-Output \"Node ID: $($nodeID) Name: $($NodeName)\";\n",[982,1088,1090],{"class":984,"line":1089},19,[982,1091,1092],{},"}\n",[941,1094,1095,1096,1101],{},"The PowerShell snap-in must be installed before the script runs. The Orion SDK's ",[945,1097,1100],{"href":1098,"rel":1099},"https:\u002F\u002Fgithub.com\u002Fsolarwinds\u002FOrionSDK\u002Fwiki\u002FPowerShell",[949],"PowerShell documentation"," explains the setup.",[941,1103,1104],{},"SWIS uses SolarWinds credentials and honors the permissions of the relevant user. The interface also isolates clients from direct database-schema changes, helping provide a consistent data model for integrations.",[941,1106,1107],{},"The SDK installation includes SWQL Studio for building queries.",[941,1109,1110],{},[1111,1112],"img",{"alt":1113,"src":1114},"SWQL Studio showing the schema and a query against Orion data","\u002Fmedia\u002Fresources\u002Fblog\u002Fswql-studio.png",[941,1116,1117],{},"In addition to read-only SWQL queries, SWIS exposes functions for CRUD operations. They can be called through the PowerShell snap-in, Python client, SOAP, or REST, although they are not implemented for every Orion data type.",[941,1119,1120],{},"SWIS functions use a SWIS URI to select an object:",[974,1122,1124],{"className":976,"code":1123,"language":978,"meta":771,"style":771},"$swisUri = 'swis:\u002F\u002Flocalhost\u002FOrion\u002FOrion.Nodes\u002FNodeID=$nodeID\u002FVolumes\u002FVolumeID=$volumeId';\n",[969,1125,1126],{"__ignoreMap":771},[982,1127,1128],{"class":984,"line":985},[982,1129,1123],{},[953,1131,1133],{"id":1132},"automating-solarwinds-management-with-swis-verbs","Automating SolarWinds Management with SWIS Verbs",[941,1135,1136],{},"SWIS verbs execute common Orion actions directly from scripts. The following example temporarily removes a node from monitoring.",[941,1138,1139],{},"First, SWQL is used to find the node ID:",[974,1141,1145],{"className":1142,"code":1143,"language":1144,"meta":771,"style":771},"language-sql shiki shiki-themes material-theme-palenight github-light","SELECT NodeID, Caption, Status, StatusDescription\nFROM Orion.Nodes\nWHERE Caption LIKE '%Test%';\n","sql",[969,1146,1147,1163,1177],{"__ignoreMap":771},[982,1148,1149,1153,1157,1160],{"class":984,"line":985},[982,1150,1152],{"class":1151},"s0tkd","SELECT",[982,1154,1156],{"class":1155},"sSBVg"," NodeID, Caption, ",[982,1158,1159],{"class":1151},"Status",[982,1161,1162],{"class":1155},", StatusDescription\n",[982,1164,1165,1168,1172,1174],{"class":984,"line":991},[982,1166,1167],{"class":1151},"FROM",[982,1169,1171],{"class":1170},"svmGq"," Orion",[982,1173,951],{"class":1155},[982,1175,1176],{"class":1170},"Nodes\n",[982,1178,1179,1182,1185,1188,1192,1196,1199],{"class":984,"line":997},[982,1180,1181],{"class":1151},"WHERE",[982,1183,1184],{"class":1155}," Caption ",[982,1186,1187],{"class":1151},"LIKE",[982,1189,1191],{"class":1190},"sBjgV"," '",[982,1193,1195],{"class":1194},"sYJ8Q","%Test%",[982,1197,1198],{"class":1190},"'",[982,1200,1201],{"class":1155},";\n",[941,1203,1204],{},"Example result:",[974,1206,1211],{"className":1207,"code":1209,"language":1210,"meta":771},[1208],"language-text","NodeID  Caption     Status  StatusDescription\n78      Testserver  1       Node status is Up.\n","text",[969,1212,1209],{"__ignoreMap":771},[941,1214,1215,1216,1219],{},"The ID is then supplied to ",[969,1217,1218],{},"Invoke-SwisVerb",". The dates from the historical example are intentionally retained:",[974,1221,1223],{"className":976,"code":1222,"language":978,"meta":771,"style":771},"Add-PSSnapin SwisSnapin;\n\n$swis = Connect-Swis;\n[datetime]$timestampNow = \"01.09.2017\";\n[datetime]$timestampLater = \"12.09.2017\";\n\nInvoke-SwisVerb $swis Orion.Nodes Unmanage @(\"N:78\", $timestampNow, $timestampLater, \"false\");\n",[969,1224,1225,1229,1233,1237,1242,1247,1251],{"__ignoreMap":771},[982,1226,1227],{"class":984,"line":985},[982,1228,988],{},[982,1230,1231],{"class":984,"line":991},[982,1232,994],{"emptyLinePlaceholder":27},[982,1234,1235],{"class":984,"line":997},[982,1236,1000],{},[982,1238,1239],{"class":984,"line":1003},[982,1240,1241],{},"[datetime]$timestampNow = \"01.09.2017\";\n",[982,1243,1244],{"class":984,"line":1008},[982,1245,1246],{},"[datetime]$timestampLater = \"12.09.2017\";\n",[982,1248,1249],{"class":984,"line":1014},[982,1250,994],{"emptyLinePlaceholder":27},[982,1252,1253],{"class":984,"line":1020},[982,1254,1255],{},"Invoke-SwisVerb $swis Orion.Nodes Unmanage @(\"N:78\", $timestampNow, $timestampLater, \"false\");\n",[941,1257,1258,1259,1262],{},"The node is removed from monitoring at the first timestamp and added again at the second. Running the query again reports status ",[969,1260,1261],{},"9",", “Unmanaged.”",[941,1264,1265],{},"The arguments accepted by a verb can be queried from metadata in SWQL Studio:",[974,1267,1269],{"className":1142,"code":1268,"language":1144,"meta":771,"style":771},"SELECT EntityName, VerbName, Position, Name, Type, IsOptional\nFROM Metadata.VerbArgument\nWHERE VerbName = 'Unmanage'\n  AND EntityName = 'Orion.Nodes';\n",[969,1270,1271,1290,1302,1321],{"__ignoreMap":771},[982,1272,1273,1275,1278,1281,1284,1287],{"class":984,"line":985},[982,1274,1152],{"class":1151},[982,1276,1277],{"class":1155}," EntityName, VerbName, Position, ",[982,1279,1280],{"class":1151},"Name",[982,1282,1283],{"class":1155},", ",[982,1285,1286],{"class":1151},"Type",[982,1288,1289],{"class":1155},", IsOptional\n",[982,1291,1292,1294,1297,1299],{"class":984,"line":991},[982,1293,1167],{"class":1151},[982,1295,1296],{"class":1170}," Metadata",[982,1298,951],{"class":1155},[982,1300,1301],{"class":1170},"VerbArgument\n",[982,1303,1304,1306,1309,1313,1315,1318],{"class":984,"line":997},[982,1305,1181],{"class":1151},[982,1307,1308],{"class":1155}," VerbName ",[982,1310,1312],{"class":1311},"s8ScI","=",[982,1314,1191],{"class":1190},[982,1316,1317],{"class":1194},"Unmanage",[982,1319,1320],{"class":1190},"'\n",[982,1322,1323,1326,1329,1331,1333,1336,1338],{"class":984,"line":1003},[982,1324,1325],{"class":1151},"  AND",[982,1327,1328],{"class":1155}," EntityName ",[982,1330,1312],{"class":1311},[982,1332,1191],{"class":1190},[982,1334,1335],{"class":1194},"Orion.Nodes",[982,1337,1198],{"class":1190},[982,1339,1201],{"class":1155},[941,1341,1342],{},[1111,1343],{"alt":1344,"src":1345},"Arguments of the Unmanage SWIS verb in SWQL Studio","\u002Fmedia\u002Fresources\u002Fblog\u002Fswis-verb-properties.png",[941,1347,1348],{},"Another SWQL query lists the verbs supported by a particular installation:",[974,1350,1352],{"className":1142,"code":1351,"language":1144,"meta":771,"style":771},"SELECT Name, EntityName\nFROM Metadata.Verb;\n",[969,1353,1354,1364],{"__ignoreMap":771},[982,1355,1356,1358,1361],{"class":984,"line":985},[982,1357,1152],{"class":1151},[982,1359,1360],{"class":1151}," Name",[982,1362,1363],{"class":1155},", EntityName\n",[982,1365,1366,1368,1370,1372,1375],{"class":984,"line":991},[982,1367,1167],{"class":1151},[982,1369,1296],{"class":1170},[982,1371,951],{"class":1155},[982,1373,1374],{"class":1170},"Verb",[982,1376,1201],{"class":1155},[953,1378,1380],{"id":1379},"documentation-and-community","Documentation and Community",[941,1382,1383,1384,1389,1390,1394,1395,1400],{},"The ",[945,1385,1388],{"href":1386,"rel":1387},"https:\u002F\u002Fgithub.com\u002Fsolarwinds\u002FOrionSDK\u002Fwiki",[949],"Orion SDK wiki"," is the main starting point for productive use of the tools. The ",[945,1391,1393],{"href":962,"rel":1392},[949],"SWIS schema"," and ",[945,1396,1399],{"href":1397,"rel":1398},"https:\u002F\u002Fthwack.solarwinds.com\u002F",[949],"THWACK community"," provide additional reference material and support.",[1402,1403,1404],"style",{},"html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html pre.shiki code .s0tkd, html code.shiki .s0tkd{--shiki-dark:#F78C6C;--shiki-light:#D73A49}html pre.shiki code .sSBVg, html code.shiki .sSBVg{--shiki-dark:#BABED8;--shiki-light:#24292E}html pre.shiki code .svmGq, html code.shiki .svmGq{--shiki-dark:#BABED8;--shiki-light:#005CC5}html pre.shiki code .sBjgV, html code.shiki .sBjgV{--shiki-dark:#89DDFF;--shiki-light:#032F62}html pre.shiki code .sYJ8Q, html code.shiki .sYJ8Q{--shiki-dark:#C3E88D;--shiki-light:#032F62}html pre.shiki code .s8ScI, html code.shiki .s8ScI{--shiki-dark:#89DDFF;--shiki-light:#D73A49}",{"title":771,"searchDepth":991,"depth":991,"links":1406},[1407,1408,1409],{"id":955,"depth":991,"text":956},{"id":1132,"depth":991,"text":1133},{"id":1379,"depth":991,"text":1380},"2017-09-01","Query, extend, and automate SolarWinds Orion with SWIS, SWQL, PowerShell, and SWIS verbs.","md",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Findividuelle-netzwerkueberwachung-mit-dem-solarwinds-sdk","3 min read","BlogPosting",{"title":1418,"description":1419,"imageKey":35,"changeFrequency":1420},"Network Monitoring with the SolarWinds SDK","Practical examples using the SolarWinds Orion SDK, SWIS, SWQL, PowerShell, CRUD operations, and SWIS verbs for monitoring automation.","yearly","individuelle-netzwerkueberwachung-mit-dem-solarwinds-sdk","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Findividuelle-netzwerkueberwachung-mit-dem-solarwinds-sdk","YqyQE0ZaU_lgI-y71zBHQ3tojjFgKoqnuoXII-YmDMg","blogs",[1426,1462,1484,1548,1641,1728,1762,1957,2098,2241,2398,2455,2554,2666,2996,3116,3289,3791,3906,4555,5022,5600,6173,6784,7300,7814,8328],{"id":1427,"title":1428,"assessmentSlug":1429,"associatedSolution":100,"authors":934,"body":1430,"category":1440,"ctaLabel":1441,"date":1442,"dateModified":1442,"deliveryFormat":934,"description":1443,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":27,"format":1440,"gated":23,"healthCheckSlug":934,"keyTakeaways":1444,"meta":1449,"navigation":27,"newsletterTopic":1452,"path":1453,"publicType":1454,"published":27,"readTime":1455,"resourceType":1456,"schemaType":1457,"seo":1458,"slug":1429,"stem":1459,"teaser":1460,"type":1440,"__hash__":1461},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fassessments\u002Fdata-governance-maturity-assessment.md","Data Governance Maturity Assessment","data-governance-maturity-assessment",{"type":938,"value":1431,"toc":1438},[1432,1435],[1433,1434,1428],"h1",{"id":1429},[941,1436,1437],{},"Start with the questionnaire. Your first score, category results, and immediate observations are shown before any contact details are requested. Detailed recommendations can then be requested and are also sent by email.",{"title":771,"searchDepth":991,"depth":991,"links":1439},[],"assessment","Start assessment","2026-08-19","Answer twelve focused questions and receive an immediate maturity score across ownership, metadata, data quality, lifecycle, processes, and adoption.",[1445,1446,1447,1448],"Immediate overall score","Category-level results","Immediate observations before the lead form","Detailed recommendations after optional lead submission",{"tags":1450},[100,1440,1451],"maturity","dataManagementEnterpriseArchitecture","\u002Flocales\u002Fenglish\u002Fresources\u002Fassessments\u002Fdata-governance-maturity-assessment","assessments","5 min","Assessment","TechArticle",{"title":1428,"description":1443},"locales\u002Fenglish\u002Fresources\u002Fassessments\u002Fdata-governance-maturity-assessment",[1443],"8F9hX2UThd-waa9_mkSFyktsbWGlM9TZ1T1oc8Jxld8",{"id":1463,"title":1464,"assessmentSlug":1465,"associatedSolution":79,"authors":934,"body":1466,"category":1440,"ctaLabel":1441,"date":1442,"dateModified":1442,"deliveryFormat":934,"description":1474,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":27,"format":1440,"gated":23,"healthCheckSlug":934,"keyTakeaways":1475,"meta":1476,"navigation":27,"newsletterTopic":1478,"path":1479,"publicType":1454,"published":27,"readTime":1455,"resourceType":1456,"schemaType":1457,"seo":1480,"slug":1465,"stem":1481,"teaser":1482,"type":1440,"__hash__":1483},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fassessments\u002Fstreaming-platform-readiness-assessment.md","Streaming Platform Readiness Assessment","streaming-platform-readiness-assessment",{"type":938,"value":1467,"toc":1472},[1468,1470],[1433,1469,1464],{"id":1465},[941,1471,1437],{},{"title":771,"searchDepth":991,"depth":991,"links":1473},[],"Assess architecture, capacity, resilience, access protection, delivery quality, monitoring, ownership, and lifecycle readiness.",[1445,1446,1447,1448],{"tags":1477},[79,1440,1451],"companyPortfolio","\u002Flocales\u002Fenglish\u002Fresources\u002Fassessments\u002Fstreaming-platform-readiness-assessment",{"title":1464,"description":1474},"locales\u002Fenglish\u002Fresources\u002Fassessments\u002Fstreaming-platform-readiness-assessment",[1474],"LvgZtgxHPe_MYXlA_wSQaZKGAwcCWfH6F4iDTBDtm5s",{"id":1485,"title":1486,"assessmentSlug":934,"associatedSolution":934,"authors":1487,"body":1489,"category":934,"ctaLabel":934,"date":1537,"dateModified":934,"deliveryFormat":934,"description":1538,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":1539,"navigation":27,"newsletterTopic":934,"path":1540,"publicType":149,"published":27,"readTime":1541,"resourceType":934,"schemaType":1416,"seo":1542,"slug":1545,"stem":1546,"teaser":934,"type":934,"__hash__":1547},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fapi-management-whitepaper.md","API Management: An Overview and Use Cases for Decision-Makers",[1488],"Andreas Koppenhoefer",{"type":938,"value":1490,"toc":1534},[1491,1494,1497,1503,1507,1526,1529],[941,1492,1493],{},"Digital transformation is both a challenge and an opportunity for many organizations. Data and services need to become available to customers, partners, and new business models without sacrificing traceability or security. API management provides a controlled framework for doing so.",[941,1495,1496],{},"The whitepaper explains what API management means and where it is used. It introduces the components of a mature API management solution and how they work together. It also outlines potential benefits and several use cases that help decision-makers assess the value for their own organization.",[941,1498,1499],{},[1111,1500],{"alt":1501,"src":1502},"Modern architecture model with API management between services and applications","\u002Fmedia\u002Fresources\u002Fblog\u002Fapi-management-architecture.jpg",[953,1504,1506],{"id":1505},"what-the-whitepaper-covers","What the Whitepaper Covers",[1508,1509,1510,1514,1517,1520,1523],"ul",{},[1511,1512,1513],"li",{},"the meaning and responsibilities of API management",[1511,1515,1516],{},"core components and how they work",[1511,1518,1519],{},"secure access for customers and partners",[1511,1521,1522],{},"using and monetizing existing data and services",[1511,1524,1525],{},"use cases from different industries and business areas",[941,1527,1528],{},"The historical form used to email the download link is not available on this website. Contact heureka if you would like to ask whether the whitepaper is still available.",[941,1530,1531],{},[945,1532,1533],{"href":6},"Contact heureka about the API management whitepaper",{"title":771,"searchDepth":991,"depth":991,"links":1535},[1536],{"id":1505,"depth":991,"text":1506},"2018-04-24","A concise introduction to the purpose, components, benefits, and use cases of API management solutions.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fapi-management-whitepaper","1 min read",{"title":1543,"description":1544,"imageKey":35,"changeFrequency":1420},"API Management for Decision-Makers","This whitepaper provides a concise overview of the purpose, components, benefits, and use cases of modern API management solutions.","api-management-whitepaper","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fapi-management-whitepaper","zgpaEyCF_rrJqOnMSJ8GneKIKElgVplrzfOAxHljG90",{"id":1549,"title":1550,"assessmentSlug":934,"associatedSolution":934,"authors":1551,"body":1553,"category":934,"ctaLabel":934,"date":1632,"dateModified":934,"deliveryFormat":934,"description":1633,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":1634,"navigation":27,"newsletterTopic":934,"path":1635,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":1636,"slug":100,"stem":1639,"teaser":934,"type":934,"__hash__":1640},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance.md","Data Governance: The Foundation for Better Decisions",[1552],"Kim Lust",{"type":938,"value":1554,"toc":1625},[1555,1558,1561,1564,1568,1571,1574,1578,1581,1584,1588,1591,1594,1598,1601,1604,1608,1611,1622],[941,1556,1557],{},"Data and the information derived from it are essential resources of the digital age. Their value, however, does not result from volume alone. Quality, reliability, and controlled handling throughout the lifecycle are what matter. Data governance establishes the rules, responsibilities, and tools required for that control.",[941,1559,1560],{},"The philosopher Francis Bacon coined the phrase “knowledge is power.” The digital age makes it particularly clear that knowledge depends on reliable data. Data is useful only when it meets certain conditions: it must be captured correctly, maintained, and ultimately archived or deleted when it no longer provides value.",[941,1562,1563],{},"As the amount of data used by an organization grows, so does the importance of an effective data governance strategy.",[953,1565,1567],{"id":1566},"_1-master-data-management","1. Master Data Management",[941,1569,1570],{},"Master data describes central real-world objects such as people, organizations, or products. A person record may contain a name, street, city, postal code, email address, and other attributes. The more complete and purposeful the description, the more options the organization has for acting on it.",[941,1572,1573],{},"A sales team can contact a person only through channels for which reliable information is available. If objects are defined inadequately in the master data model, their records serve the intended purpose only partially or, in the worst case, become unusable.",[953,1575,1577],{"id":1576},"_2-data-quality","2. Data Quality",[941,1579,1580],{},"A sound definition is not enough. The required attributes must actually contain complete and correct values. The time of collection—the point of entry—is especially important. Effective policies and validation controls ensure that data is captured at the required level of quality from the outset.",[941,1582,1583],{},"Complete and correct records save time and prevent mistakes. Gaps in a price list force sales staff to carry out additional research. Incorrect prices can lead to difficult customer conversations or direct financial losses.",[953,1585,1587],{"id":1586},"_3-data-maintenance-and-lifecycle","3. Data Maintenance and Lifecycle",[941,1589,1590],{},"Data has a finite useful life. How long it remains valuable and how much benefit the organization gains from it depend on ongoing maintenance. Correctness must be preserved beyond the original point of entry.",[941,1592,1593],{},"Archiving and deletion are equally important. Once data reaches the end of its lifecycle, unusable records should not remain in the system indefinitely. Consistently removing data waste supports database performance over the long term and reduces maintenance and operating costs.",[953,1595,1597],{"id":1596},"_4-privacy-and-protection","4. Privacy and Protection",[941,1599,1600],{},"Data governance concerns not only quality but also protection. Inadequate security and privacy measures can result in penalties, reputational damage, and lasting loss of trust among customers and business partners.",[941,1602,1603],{},"Clear ownership, controlled access, and traceable processes protect data from unauthorized use. Data governance therefore safeguards both the business value of data and the trust of the people it describes.",[953,1605,1607],{"id":1606},"conclusion","Conclusion",[941,1609,1610],{},"Every organization ultimately needs a concept for managing its data. The primary benefits are clear:",[1508,1612,1613,1616,1619],{},[1511,1614,1615],{},"High-quality data supports efficient, flexible use and saves employee time.",[1511,1617,1618],{},"Reliable data is essential for fast, goal-oriented decisions.",[1511,1620,1621],{},"Strong data protection shields the organization from harm and builds trust.",[941,1623,1624],{},"The earlier an effective data-management strategy is established, the lower the later remediation effort and associated costs. The 26-page whitepaper offered by the original article is currently unavailable at its historical destination.",{"title":771,"searchDepth":991,"depth":991,"links":1626},[1627,1628,1629,1630,1631],{"id":1566,"depth":991,"text":1567},{"id":1576,"depth":991,"text":1577},{"id":1586,"depth":991,"text":1587},{"id":1596,"depth":991,"text":1597},{"id":1606,"depth":991,"text":1607},"2017-11-09","Why master data management, data quality, lifecycle management, and privacy form the foundation of effective data governance.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance",{"title":1637,"description":1638,"imageKey":35,"changeFrequency":1420},"Data Governance as a Basis for Better Decisions","Four building blocks of effective data governance: master data management, data quality, data lifecycle, and privacy in the enterprise.","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance","bILoyX-mrpTTX8B40Kd4ohqhshpaZgmnh9d4EqwjWo8",{"id":1642,"title":1643,"assessmentSlug":934,"associatedSolution":934,"authors":1644,"body":1646,"category":934,"ctaLabel":934,"date":1718,"dateModified":934,"deliveryFormat":934,"description":1719,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":1720,"navigation":27,"newsletterTopic":934,"path":1721,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":1722,"slug":1725,"stem":1726,"teaser":934,"type":934,"__hash__":1727},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance-als-schluessel-zur-implementierung-von-gdpr.md","Data Governance as the Key to Implementing GDPR",[1645],"Katarina Kramaric",{"type":938,"value":1647,"toc":1712},[1648,1651,1655,1658,1661,1664,1668,1671,1674,1678,1681,1684,1687,1691,1694,1709],[941,1649,1650],{},"Internal and external pressures have sharply increased interest in formal methods for managing enterprise data. Consistent implementation, by contrast, has progressed comparatively slowly. A study conducted by erwin, Inc. in 2017 examined the challenges of introducing enterprise-wide data governance and the state of the market at the time.",[953,1652,1654],{"id":1653},"online-survey-on-data-governance","Online Survey on Data Governance",[941,1656,1657],{},"Data governance is the systematic management of an organization's complete data estate with respect to quality, security, and traceability. In addition to supporting regulatory compliance, it can increase transparency and improve decision-making.",[941,1659,1660],{},"Working with UBM, erwin conducted an online survey of leading North American organizations in November 2017. Participants included CIOs, CTOs, IT professionals, and consultants from more than 20 industries. The survey found very strong cross-industry interest in data governance, while only some organizations had already implemented an initiative. The principal challenges included insufficient organizational support, inadequate budgets, and a lack of understanding of suitable implementation approaches.",[941,1662,1663],{},"For 98 percent of respondents, data governance was exceptionally important to their organization. At the same time, 46 percent reported having no formal governance strategy. The gap showed that the relevance of the topic was understood, but implementation was far from straightforward.",[953,1665,1667],{"id":1666},"drivers-of-data-governance-initiatives","Drivers of Data Governance Initiatives",[941,1669,1670],{},"The strongest driver was compliance, especially the European Union's General Data Protection Regulation (GDPR). Sixty percent of participants cited it as the primary reason for their interest in data governance. Forty-nine percent expected higher customer satisfaction, and 45 percent considered better decision-making an important motivation.",[941,1672,1673],{},"The study also examined obstacles. Four in ten respondents said that they understood the importance of appropriate measures but lacked sufficient funding to implement them. Limited knowledge of how to introduce and operate an enterprise-wide governance strategy was another important factor.",[953,1675,1677],{"id":1676},"connecting-data-governance-and-gdpr","Connecting Data Governance and GDPR",[941,1679,1680],{},"New regulation increases the pressure to act. Organizations that conduct business involving people in the European Union must account for the applicable privacy requirements. These include the ability to provide information about collected personal data, delete data promptly in response to a valid request, and document its processing path.",[941,1682,1683],{},"Those obligations can be met reliably only when data management is treated as a strategic objective and coordinated across the departments involved. A data governance initiative combines ownership, processes, and technical controls in a traceable framework.",[941,1685,1686],{},"The study findings at the time showed that many international organizations still lacked a functioning solution for comprehensive data management despite recognizing its importance. In addition to limited funding, a lack of understanding of the appropriate approach was a major reason.",[953,1688,1690],{"id":1689},"recommendations","Recommendations",[941,1692,1693],{},"Four fundamental recommendations follow from the challenges identified:",[1695,1696,1697,1700,1703,1706],"ol",{},[1511,1698,1699],{},"Define data governance as a strategic corporate objective and secure full management support.",[1511,1701,1702],{},"Assign responsibilities and prepare a budget and timeline that account for everyone involved.",[1511,1704,1705],{},"Treat GDPR and its national implementations as binding constraints.",[1511,1707,1708],{},"Communicate the risks and benefits of data retention, along with expectations and responsibilities, transparently throughout the organization.",[941,1710,1711],{},"The original article linked to the complete “2018 State of Data Governance Report.” That historical download no longer resolves unambiguously to the study, so it has not been presented as a current link here.",{"title":771,"searchDepth":991,"depth":991,"links":1713},[1714,1715,1716,1717],{"id":1653,"depth":991,"text":1654},{"id":1666,"depth":991,"text":1667},{"id":1676,"depth":991,"text":1677},{"id":1689,"depth":991,"text":1690},"2018-08-20","Findings from a 2017 erwin study on the importance, drivers, and obstacles of enterprise data governance initiatives.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance-als-schluessel-zur-implementierung-von-gdpr",{"title":1723,"description":1724,"imageKey":35,"changeFrequency":1420},"Data Governance as the Key to GDPR","A study examines the importance, drivers, and barriers of data governance and offers recommendations for enterprise-wide implementation.","data-governance-als-schluessel-zur-implementierung-von-gdpr","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance-als-schluessel-zur-implementierung-von-gdpr","or4ORbqqOPSZxIpWW-AtpSP3saBoVZ21qQmZFALA0kk",{"id":1729,"title":1730,"assessmentSlug":934,"associatedSolution":934,"authors":1731,"body":1733,"category":934,"ctaLabel":934,"date":1752,"dateModified":934,"deliveryFormat":934,"description":1753,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":1754,"navigation":27,"newsletterTopic":934,"path":1755,"publicType":149,"published":27,"readTime":1541,"resourceType":934,"schemaType":1416,"seo":1756,"slug":1759,"stem":1760,"teaser":934,"type":934,"__hash__":1761},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance-verstehen.md","Understanding Data Governance: An Introductory Guide",[1732],"Larissa Albrecht",{"type":938,"value":1734,"toc":1750},[1735,1738,1741,1744,1747],[941,1736,1737],{},"Data management has changed fundamentally over the past several decades. There is now broad agreement that data drives business and society. Within an organization, however, views often differ sharply on who governs that data and what data governance actually includes.",[941,1739,1740],{},"A shared understanding is the basis of every data governance initiative. As the number of data sources and the volume of data increase, organizations need to manage rights, duties, and responsibilities deliberately.",[941,1742,1743],{},"Data governance is not solely a technology matter. People must take responsibility for their organization's data and information assets. Introducing a software product is not enough. Ineffective organizational structures need to be reviewed, new roles and accountabilities defined, and data treated as a corporate asset.",[941,1745,1746],{},"There is no universally accepted definition. The original guide was therefore designed to provide a holistic overview of the topic and its building blocks, establishing a common point of departure.",[941,1748,1749],{},"The historical download was provided through an external form-based landing page. That destination is currently unavailable, and no public PDF download could be verified.",{"title":771,"searchDepth":991,"depth":991,"links":1751},[],"2020-05-27","A concise introduction to data governance, its organizational building blocks, and responsibility for data as a business asset.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance-verstehen",{"title":1757,"description":1758,"imageKey":35,"changeFrequency":1420},"Understanding Data Governance – A Guide","The guide establishes a shared understanding of data governance, roles, responsibilities, and the value of enterprise data.","data-governance-verstehen","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-governance-verstehen","0vCVMp0VpbZwM0Dy0s3iuMOf-QXOQ7qRwV70JCli_Hw",{"id":1763,"title":1764,"assessmentSlug":934,"associatedSolution":934,"authors":1765,"body":1767,"category":934,"ctaLabel":934,"date":1947,"dateModified":934,"deliveryFormat":934,"description":1948,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":1949,"navigation":27,"newsletterTopic":934,"path":1950,"publicType":149,"published":27,"readTime":1951,"resourceType":934,"schemaType":1416,"seo":1952,"slug":1954,"stem":1955,"teaser":934,"type":934,"__hash__":1956},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-warehouse-automatisierung-mit-erwin.md","Data Warehouse Automation with erwin",[1766],"Stefan Kausch",{"type":938,"value":1768,"toc":1939},[1769,1772,1776,1779,1800,1803,1817,1821,1824,1827,1831,1834,1860,1866,1872,1875,1879,1882,1905,1909,1912,1915,1929,1933,1936],[941,1770,1771],{},"Data warehouse projects have traditionally struggled with long implementation times. This increases the chance that business requirements will change while the project is still under way, putting schedule and budget goals at risk. A highly systematic model such as Data Vault offers substantial potential for automation.",[953,1773,1775],{"id":1774},"benefits-of-the-data-vault-methodology","Benefits of the Data Vault Methodology",[941,1777,1778],{},"Dan Linstedt developed Data Vault to shorten implementation times and make data warehouses easier to adapt to change. Its central design principle separates business keys, contextual information, and relationships into dedicated table types:",[1508,1780,1781,1788,1794],{},[1511,1782,1783,1787],{},[1784,1785,1786],"strong",{},"Hubs"," contain stable business keys.",[1511,1789,1790,1793],{},[1784,1791,1792],{},"Satellites"," hold descriptive and historized context.",[1511,1795,1796,1799],{},[1784,1797,1798],{},"Links"," represent relationships between business keys.",[941,1801,1802],{},"This separation offers several advantages:",[1508,1804,1805,1808,1811,1814],{},[1511,1806,1807],{},"Models are easy to extend and therefore support an agile approach.",[1511,1809,1810],{},"The resulting structures scale well.",[1511,1812,1813],{},"Load processes can be parallelized extensively because there are few synchronization points.",[1511,1815,1816],{},"Changes and history are easy to audit.",[953,1818,1820],{"id":1819},"the-trade-off","The Trade-Off",[941,1822,1823],{},"By separating information types and adding load metadata, Data Vault creates a very large number of tables and columns. Modeling effort increases even though much of the work consists of straightforward, mechanical steps.",[941,1825,1826],{},"That systematic structure is also what makes generation practical. When derivation rules can be described unambiguously, large parts of the modeling process can be automated and projects accelerated substantially.",[953,1828,1830],{"id":1829},"automation-potential-across-dwh-layers","Automation Potential Across DWH Layers",[941,1832,1833],{},"A typical data warehouse architecture includes the following layers:",[1508,1835,1836,1842,1848,1854],{},[1511,1837,1838,1841],{},[1784,1839,1840],{},"Source systems:"," operational platforms such as ERP or CRM solutions.",[1511,1843,1844,1847],{},[1784,1845,1846],{},"Staging area:"," receives data from operational systems. Its structure largely mirrors the source and is augmented with technical load information.",[1511,1849,1850,1853],{},[1784,1851,1852],{},"Core warehouse:"," integrates data from multiple systems. Under Data Vault it is divided into a raw vault and business vault. Business rules reside in the business vault, while the raw vault uses the simplest possible transformations.",[1511,1855,1856,1859],{},[1784,1857,1858],{},"Data marts:"," follow reporting requirements and are often modeled as star schemas.",[941,1861,1862],{},[1111,1863],{"alt":1864,"src":1865},"Layers of a data warehouse architecture from source systems to data marts","\u002Fmedia\u002Fresources\u002Fblog\u002Fdata-vault-architecture.png",[941,1867,1868],{},[1869,1870,1871],"em",{},"The staging area and raw vault can be derived from their preceding layers using clear rules.",[941,1873,1874],{},"The staging area and raw vault are particularly suitable for automation because their structures can be generated from the preceding model through well-defined rules.",[953,1876,1878],{"id":1877},"standard-modeler-or-specialized-automation-tool","Standard Modeler or Specialized Automation Tool?",[941,1880,1881],{},"Specialized data warehouse automation products address this potential directly. A standard modeling tool such as erwin Data Modeler offers a different set of strengths:",[1508,1883,1884,1887,1890,1893,1896,1899,1902],{},[1511,1885,1886],{},"Existing source-system models can be reused.",[1511,1888,1889],{},"Mature features support model comparison and standardization.",[1511,1891,1892],{},"A broad range of databases is supported.",[1511,1894,1895],{},"Interfaces allow models to be imported from other tools.",[1511,1897,1898],{},"Source systems or other warehouses are often already modeled in the same product.",[1511,1900,1901],{},"The model portfolio can represent the wider enterprise architecture, not only the data warehouse.",[1511,1903,1904],{},"Existing semantic information can be integrated through business glossaries.",[953,1906,1908],{"id":1907},"modgen-for-erwin-data-modeler","MODGEN for erwin Data Modeler",[941,1910,1911],{},"The MODGEN add-in was developed to provide model-based generation within erwin. It integrates into the erwin interface and uses a workflow closely aligned with Complete Compare.",[941,1913,1914],{},"MODGEN provides capabilities including:",[1508,1916,1917,1920,1923,1926],{},[1511,1918,1919],{},"generating staging and raw-vault models from the preceding layer,",[1511,1921,1922],{},"controlling generation through metadata stored in user-defined properties (UDPs),",[1511,1924,1925],{},"permanently or interactively excluding individual objects,",[1511,1927,1928],{},"and applying templates for standardized metadata columns.",[953,1930,1932],{"id":1931},"round-trips-mappings-and-lineage","Round Trips, Mappings, and Lineage",[941,1934,1935],{},"An iterative modeling process needs to be repeatable. MODGEN therefore compares the source and target model during every generation run. It displays differences and lets users select which changes to apply. The process remains round-trip capable as models are extended repeatedly.",[941,1937,1938],{},"Generation covers not only tables and columns as horizontal model structure. For every target column, it also documents the relationship to its source column as a data source. This provides a basis for producing source-to-target mappings. When source and target models are integrated into the Web Portal, the same information becomes available for impact and lineage analysis.",{"title":771,"searchDepth":991,"depth":991,"links":1940},[1941,1942,1943,1944,1945,1946],{"id":1774,"depth":991,"text":1775},{"id":1819,"depth":991,"text":1820},{"id":1829,"depth":991,"text":1830},{"id":1877,"depth":991,"text":1878},{"id":1907,"depth":991,"text":1908},{"id":1931,"depth":991,"text":1932},"2017-01-19","How Data Vault, erwin Data Modeler, and MODGEN automate the modeling of staging areas and raw vaults.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-warehouse-automatisierung-mit-erwin","4 min read",{"title":1764,"description":1953,"imageKey":35,"changeFrequency":1420},"Automate Data Vault models with erwin and MODGEN using metadata, round trips, source-to-target mappings, impact analysis, and lineage.","data-warehouse-automatisierung-mit-erwin","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdata-warehouse-automatisierung-mit-erwin","S0envYlOO6wnqyY6OyhfXy6PfwljVGnyDB7bnvqWpSE",{"id":1958,"title":1959,"assessmentSlug":934,"associatedSolution":934,"authors":1960,"body":1962,"category":934,"ctaLabel":934,"date":2089,"dateModified":934,"deliveryFormat":934,"description":2090,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":2091,"navigation":27,"newsletterTopic":934,"path":2092,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":2093,"slug":2095,"stem":2096,"teaser":934,"type":934,"__hash__":2097},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdie-eu-dsgvo-und-ihre-auswirkungen.md","The EU GDPR and Its Impact",[1961],"Michael Wycisk",{"type":938,"value":1963,"toc":2081},[1964,1968,1971,1974,1977,1981,1984,1987,1991,1994,2011,2014,2018,2021,2025,2028,2054,2058,2061,2064,2078],[953,1965,1967],{"id":1966},"introduction","Introduction",[941,1969,1970],{},"The EU General Data Protection Regulation has applied since 25 May 2018. Its purpose is to harmonize privacy law across Europe. It covers organizations and establishments in the European Union that process personal data.",[941,1972,1973],{},"Under certain conditions, it also applies to organizations outside the EU when processing relates to offering goods or services to people in the Union or monitoring their behavior.",[941,1975,1976],{},"Organizations therefore need to understand the requirements for lawful processing, the obligations the regulation creates, and the potential consequences of non-compliance.",[953,1978,1980],{"id":1979},"supervisory-authorities","Supervisory Authorities",[941,1982,1983],{},"Supervisory authorities monitor and enforce application of the regulation. They handle questions and complaints from data subjects, raise awareness of controllers' obligations, and investigate whether requirements are being observed.",[941,1985,1986],{},"Their powers range from warnings to instructions intended to protect data-subject rights. Depending on the infringement, penalties can reach EUR 20 million or four percent of worldwide annual turnover in the preceding financial year.",[953,1988,1990],{"id":1989},"data-protection-principles","Data Protection Principles",[941,1992,1993],{},"The regulation is built around central principles for processing personal data. Data must be:",[1508,1995,1996,1999,2002,2005,2008],{},[1511,1997,1998],{},"processed lawfully, fairly, and transparently for the data subject,",[1511,2000,2001],{},"collected for specified, explicit, and legitimate purposes,",[1511,2003,2004],{},"limited to what is necessary for those purposes,",[1511,2006,2007],{},"accurate and kept up to date,",[1511,2009,2010],{},"and stored only for as long as the processing purpose requires.",[941,2012,2013],{},"Security and protection against unauthorized or unlawful processing, accidental loss, destruction, or damage are equally important. Appropriate technical and organizational measures should safeguard these objectives. Controllers must be able to demonstrate compliance with the principles.",[953,2015,2017],{"id":2016},"lawfulness","Lawfulness",[941,2019,2020],{},"Processing may be based on the data subject's consent. Other possible legal bases include performance of a contract, compliance with a legal obligation, a task carried out in the public interest, and legitimate interests pursued by a controller or third party. The appropriate basis depends on the specific processing activity.",[953,2022,2024],{"id":2023},"data-subject-rights","Data-Subject Rights",[941,2026,2027],{},"Data subjects have rights concerning their personal data, including:",[1508,2029,2030,2033,2036,2039,2042,2045,2048,2051],{},[1511,2031,2032],{},"the right of access",[1511,2034,2035],{},"the right to rectification",[1511,2037,2038],{},"the right to erasure",[1511,2040,2041],{},"the right to restrict processing",[1511,2043,2044],{},"the right to data portability",[1511,2046,2047],{},"the right to object",[1511,2049,2050],{},"the right not to be subject solely to an automated individual decision",[1511,2052,2053],{},"the right to withdraw consent",[953,2055,2057],{"id":2056},"security-of-processing","Security of Processing",[941,2059,2060],{},"Controllers must implement appropriate technical and organizational measures after considering the nature, scope, circumstances, and purpose of the processing. The measures should be proportionate to the activities and risks, while accounting for implementation costs and the state of the art.",[941,2062,2063],{},"The measures described include:",[1508,2065,2066,2069,2072,2075],{},[1511,2067,2068],{},"pseudonymization and encryption of personal data,",[1511,2070,2071],{},"the ability to ensure the ongoing confidentiality, integrity, availability, and resilience of systems and services,",[1511,2073,2074],{},"the ability to restore availability and access following a physical or technical incident,",[1511,2076,2077],{},"and a process for regularly testing, assessing, and evaluating the effectiveness of the measures.",[941,2079,2080],{},"This article reflects the information available at the time of publication and does not constitute legal advice.",{"title":771,"searchDepth":991,"depth":991,"links":2082},[2083,2084,2085,2086,2087,2088],{"id":1966,"depth":991,"text":1967},{"id":1979,"depth":991,"text":1980},{"id":1989,"depth":991,"text":1990},{"id":2016,"depth":991,"text":2017},{"id":2023,"depth":991,"text":2024},{"id":2056,"depth":991,"text":2057},"2018-04-30","A historical overview of the EU GDPR's scope, principles, data-subject rights, and security requirements.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdie-eu-dsgvo-und-ihre-auswirkungen",{"title":1959,"description":2094,"imageKey":35,"changeFrequency":1420},"An overview of supervisory authorities, privacy principles, lawfulness, data-subject rights, and security under the EU GDPR.","die-eu-dsgvo-und-ihre-auswirkungen","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdie-eu-dsgvo-und-ihre-auswirkungen","ygxclcXRCeGXHwD1pxIx7FG34YovAXrwKdGCn3YPQZM",{"id":2099,"title":2100,"assessmentSlug":934,"associatedSolution":934,"authors":2101,"body":2103,"category":934,"ctaLabel":934,"date":2231,"dateModified":934,"deliveryFormat":934,"description":2232,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":2233,"navigation":27,"newsletterTopic":934,"path":2234,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":2235,"slug":2238,"stem":2239,"teaser":934,"type":934,"__hash__":2240},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdynamisches-daten-management-system-erwin-data-modeler.md","A Dynamic Data Management System with erwin Data Modeler",[2102],"Michael Diederich",{"type":938,"value":2104,"toc":2224},[2105,2108,2111,2114,2125,2129,2132,2136,2139,2143,2146,2149,2155,2160,2164,2167,2170,2174,2177,2180,2221],[941,2106,2107],{},"erwin Data Modeler can model entities and columns and generate SQL changes through forward engineering. That still leaves one question unanswered: How should end users create, find, and update data in the new tables?",[941,2109,2110],{},"heureka developed a dynamic data management system for this purpose: an administration interface for maintaining data. A dedicated application imports the erwin model, enriches it with metadata, and automatically generates a graphical interface.",[941,2112,2113],{},"Model-based generation offers three principal advantages:",[1508,2115,2116,2119,2122],{},[1511,2117,2118],{},"Applications can be provided very quickly.",[1511,2120,2121],{},"Data maintenance follows a consistent interaction model.",[1511,2123,2124],{},"The repeatable generation process reduces application-specific testing effort.",[953,2126,2128],{"id":2127},"_1-export-from-erwin","1. Export from erwin",[941,2130,2131],{},"The process starts with the physical data model. It is exported as an XML file containing the complete structural information. Tables and columns can be augmented through user-defined properties (UDPs). This metadata controls features such as which elements are visible in search. Fundamental presentation properties can be assigned through domains.",[953,2133,2135],{"id":2134},"_2-xml-import","2. XML Import",[941,2137,2138],{},"The application imports the XML file and presents every detected change in a structured list. New entities, modified values, column lengths, and other relevant differences become visible. Users can review the changes and cancel the import if necessary.",[953,2140,2142],{"id":2141},"_3-maintaining-additional-information","3. Maintaining Additional Information",[941,2144,2145],{},"After import, metadata can be adapted to the needs of end users. Entities with many-to-many relationships can, for example, be made accessible from more than one location. Individual columns can display supplementary information.",[941,2147,2148],{},"Additional project-level settings are available. These include user management, connection to an LDAP server for centralized authentication, logging of subsequent data changes, and multilingual labels.",[941,2150,2151],{},[1111,2152],{"alt":2153,"src":2154},"Maintaining data in an administration interface generated from an erwin model","\u002Fmedia\u002Fresources\u002Fblog\u002Fgenerated-data-administration.png",[941,2156,2157],{},[1869,2158,2159],{},"The generated administration interface combines model metadata with a consistent data-maintenance experience.",[953,2161,2163],{"id":2162},"_4-json-export","4. JSON Export",[941,2165,2166],{},"A JSON file is generated for each entity and for the project itself. All generated files can be downloaded as a compact ZIP archive and included in the corresponding project. The JSON documents contain the presentation information and are supplemented with individual permissions from the database.",[941,2168,2169],{},"This configuration controls the pages used to edit data. There is no longer a need to program every administration page manually.",[953,2171,2173],{"id":2172},"_5-generated-administration-interface","5. Generated Administration Interface",[941,2175,2176],{},"On first use, the application loads the relevant project JSON and updates its settings. From this point onward, each administration interface is individual: not only the appearance but also the business logic can be adapted to the project.",[941,2178,2179],{},"Potential capabilities include:",[1508,2181,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,2212,2215,2218],{},[1511,2183,2184],{},"granular permissions for tenants, functions, saving, and deletion,",[1511,2186,2187],{},"logging,",[1511,2189,2190],{},"scheduling of recurring tasks,",[1511,2192,2193],{},"dynamic documentation for tables and columns,",[1511,2195,2196],{},"configurable column combinations in overview screens,",[1511,2198,2199],{},"multiple displays and sorting rules for many-to-many relationships,",[1511,2201,2202],{},"search and replace across multiple records,",[1511,2204,2205],{},"tenant controls,",[1511,2207,2208],{},"required-field and content validation,",[1511,2210,2211],{},"maintenance of multilingual text,",[1511,2213,2214],{},"a WYSIWYG HTML editor,",[1511,2216,2217],{},"custom layouts,",[1511,2219,2220],{},"and extensions through project-specific templates and scripts.",[941,2222,2223],{},"This approach quickly creates a modular interface with little manual programming. It can be adapted to business requirements while retaining a consistent interaction model.",{"title":771,"searchDepth":991,"depth":991,"links":2225},[2226,2227,2228,2229,2230],{"id":2127,"depth":991,"text":2128},{"id":2134,"depth":991,"text":2135},{"id":2141,"depth":991,"text":2142},{"id":2162,"depth":991,"text":2163},{"id":2172,"depth":991,"text":2173},"2019-04-16","Generate a modular data administration interface automatically from an erwin data model.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdynamisches-daten-management-system-erwin-data-modeler",{"title":2236,"description":2237,"imageKey":35,"changeFrequency":1420},"Dynamic Data Management with erwin","Import an erwin model as XML, enrich it with metadata, and provide end users with a modular generated administration interface.","dynamisches-daten-management-system-erwin-data-modeler","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fdynamisches-daten-management-system-erwin-data-modeler","xk7BEnfsyr9IFaqYgjlJeoGhSnSU7eKzdrl9fEHDt0E",{"id":2242,"title":2243,"assessmentSlug":934,"associatedSolution":934,"authors":2244,"body":2245,"category":934,"ctaLabel":934,"date":2388,"dateModified":934,"deliveryFormat":934,"description":2389,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":2390,"navigation":27,"newsletterTopic":934,"path":2391,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":2392,"slug":2395,"stem":2396,"teaser":934,"type":934,"__hash__":2397},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Ferstellung-von-komplexen-technischen-dokumentationen-aus-datenbanken.md","Creating Complex Technical Documentation from Databases",[2102],{"type":938,"value":2246,"toc":2380},[2247,2250,2253,2257,2260,2280,2284,2287,2293,2298,2302,2305,2325,2331,2336,2340,2343,2346,2350,2353,2357,2360,2377],[941,2248,2249],{},"Technical documentation, specifications, and extensive price lists often need to present large volumes of data in a controlled layout. If such documents are maintained entirely by hand in Adobe InDesign, the effort grows with every product variation. Quality control and consistency also become increasingly difficult.",[941,2251,2252],{},"Vehicle price lists are one example. Models, engines, equipment packages, technical specifications, and country-specific prices create a large number of combinations. The data already exists in databases, while the publication is required as a designed PDF or an editable InDesign file.",[953,2254,2256],{"id":2255},"requirements-for-an-automated-solution","Requirements for an Automated Solution",[941,2258,2259],{},"An appropriate architecture should:",[1508,2261,2262,2265,2268,2271,2274,2277],{},[1511,2263,2264],{},"take structured data directly from a database,",[1511,2266,2267],{},"comply with mandatory layout and brand rules,",[1511,2269,2270],{},"generate large documents reproducibly,",[1511,2272,2273],{},"provide both PDF and InDesign files,",[1511,2275,2276],{},"separate changes to data from changes to design,",[1511,2278,2279],{},"and support final editorial refinement.",[953,2281,2283],{"id":2282},"adobe-indesign-server-as-the-publishing-engine","Adobe InDesign Server as the Publishing Engine",[941,2285,2286],{},"Adobe InDesign Server exposes InDesign capabilities through automated server processes. Templates define the layouts, while scripts insert the required data and assemble the document. The result can be exported directly as a PDF or delivered as an InDesign file for further editing.",[941,2288,2289],{},[1111,2290],{"alt":2291,"src":2292},"Database-driven document generation with Adobe InDesign Server","\u002Fmedia\u002Fresources\u002Fblog\u002Fdocumentation-indesign-server.png",[941,2294,2295],{},[1869,2296,2297],{},"Database content is placed in an InDesign template and exported as a PDF.",[953,2299,2301],{"id":2300},"solution-architecture","Solution Architecture",[941,2303,2304],{},"In the implementation described here, design, data management, and publishing worked together:",[1695,2306,2307,2310,2313,2316,2319,2322],{},[1511,2308,2309],{},"A graphic designer creates the InDesign template with placeholders and mandatory layout rules.",[1511,2311,2312],{},"JavaScript files control InDesign and are first tested locally.",[1511,2314,2315],{},"Once tested, the template and scripts are deployed to InDesign Server.",[1511,2317,2318],{},"A web application built with Lucee manages the data and accepts publication requests.",[1511,2320,2321],{},"Users select the content and output format.",[1511,2323,2324],{},"Lucee passes the data to InDesign Server, which generates a PDF or InDesign file.",[941,2326,2327],{},[1111,2328],{"alt":2329,"src":2330},"Workflow from a database and Lucee through InDesign Server to PDF or InDesign output","\u002Fmedia\u002Fresources\u002Fblog\u002Fdocumentation-workflow.png",[941,2332,2333],{},[1869,2334,2335],{},"The web application orchestrates data, templates, scripts, and output as one process.",[953,2337,2339],{"id":2338},"separating-data-from-layout","Separating Data from Layout",[941,2341,2342],{},"The database remains the reliable source for product and pricing information. InDesign is responsible for design, typography, and page composition. This separation reduces duplicate maintenance and allows data to be updated independently of the layout.",[941,2344,2345],{},"Responsibilities remain clear as well: subject-matter users maintain content, designers develop the template, and the server generates reproducible documents. Template changes can be applied to the next edition without setting the entire data set manually again.",[953,2347,2349],{"id":2348},"review-and-refinement","Review and Refinement",[941,2351,2352],{},"Automatically generated PDFs can first be provided for subject-matter review. If corrections are required, the source data or template is updated and the document is generated again. For individual design refinements, the InDesign file is also available for a designer to finish manually.",[953,2354,2356],{"id":2355},"benefits-and-further-applications","Benefits and Further Applications",[941,2358,2359],{},"Automation improves consistency and repeatability, reduces manual typesetting, and accelerates updates. It is not limited to vehicle price lists. The same principle can be used for:",[1508,2361,2362,2365,2368,2371,2374],{},[1511,2363,2364],{},"financial and annual reports,",[1511,2366,2367],{},"product catalogs,",[1511,2369,2370],{},"personalized documents,",[1511,2372,2373],{},"technical manuals,",[1511,2375,2376],{},"and publications configured online.",[941,2378,2379],{},"Wherever structured data needs to become a sophisticated, brand-compliant document, this solution combines database logic with professional publishing.",{"title":771,"searchDepth":991,"depth":991,"links":2381},[2382,2383,2384,2385,2386,2387],{"id":2255,"depth":991,"text":2256},{"id":2282,"depth":991,"text":2283},{"id":2300,"depth":991,"text":2301},{"id":2338,"depth":991,"text":2339},{"id":2348,"depth":991,"text":2349},{"id":2355,"depth":991,"text":2356},"2017-12-06","Automate technical documentation from databases with Adobe InDesign Server, Lucee, and reusable templates.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Ferstellung-von-komplexen-technischen-dokumentationen-aus-datenbanken",{"title":2393,"description":2394,"imageKey":35,"changeFrequency":1420},"Creating Technical Documentation from Databases","Learn how databases, templates, and Adobe InDesign Server generate complex, consistent PDF and InDesign documents automatically.","erstellung-von-komplexen-technischen-dokumentationen-aus-datenbanken","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Ferstellung-von-komplexen-technischen-dokumentationen-aus-datenbanken","a3Tppxm_0pXXFksGS8LwCQOkwflI1uVqlMhQvHa_JZk",{"id":2399,"title":2400,"assessmentSlug":934,"associatedSolution":934,"authors":2401,"body":2402,"category":934,"ctaLabel":934,"date":2445,"dateModified":934,"deliveryFormat":934,"description":2446,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":2447,"navigation":27,"newsletterTopic":934,"path":2448,"publicType":149,"published":27,"readTime":1541,"resourceType":934,"schemaType":1416,"seo":2449,"slug":2452,"stem":2453,"teaser":934,"type":934,"__hash__":2454},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fgdpr-dsgvo-leitfaden.md","Mastering GDPR: A Guide to Efficient Management",[1552],{"type":938,"value":2403,"toc":2441},[2404,2407,2410,2414,2417,2421,2424,2438],[941,2405,2406],{},"The General Data Protection Regulation (GDPR) has applied across the European Union since 25 May 2018. For many responsible professionals, the question consequently shifted from “What needs to be done?” to “How can it be managed efficiently?”",[941,2408,2409],{},"The original guide consisted of two parts.",[953,2411,2413],{"id":2412},"part-1-core-gdpr-principles","Part 1: Core GDPR Principles",[941,2415,2416],{},"The first part explained the fundamental requirements for collecting and storing personal data. These included data quality as well as integrity and confidentiality. Its purpose was to establish a shared understanding of the principles before tools and processes were selected.",[953,2418,2420],{"id":2419},"part-2-the-gdpr-operating-framework","Part 2: The GDPR Operating Framework",[941,2422,2423],{},"The second part translated those principles into an operating framework. Using erwin data governance software for demonstration, it considered tasks including:",[1508,2425,2426,2429,2432,2435],{},[1511,2427,2428],{},"discovering, collecting, and classifying data,",[1511,2430,2431],{},"assigning responsibilities to data stewards and process owners,",[1511,2433,2434],{},"organizing processing and evidence workflows,",[1511,2436,2437],{},"supporting reporting and auditing.",[941,2439,2440],{},"The historical download led to a form-based route. That route currently returns a server error, and no public PDF download could be verified.",{"title":771,"searchDepth":991,"depth":991,"links":2442},[2443,2444],{"id":2412,"depth":991,"text":2413},{"id":2419,"depth":991,"text":2420},"2018-09-17","A two-part guide to the core GDPR principles and an operating framework for practical data management.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fgdpr-dsgvo-leitfaden",{"title":2450,"description":2451,"imageKey":35,"changeFrequency":1420},"Mastering GDPR – An Efficient Management Guide","The guide connects core GDPR principles with an operating framework for classification, ownership, reporting, and auditing.","gdpr-dsgvo-leitfaden","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fgdpr-dsgvo-leitfaden","05SCyrANtdDWOp63ccnNP392RKFMos5u5EDvORXOLFI",{"id":2456,"title":2457,"assessmentSlug":934,"associatedSolution":934,"authors":2458,"body":2459,"category":934,"ctaLabel":934,"date":2544,"dateModified":934,"deliveryFormat":934,"description":2545,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":2546,"navigation":27,"newsletterTopic":934,"path":2547,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":2548,"slug":2551,"stem":2552,"teaser":934,"type":934,"__hash__":2553},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fgdpr-und-data-governance.md","GDPR and Data Governance",[1645],{"type":938,"value":2460,"toc":2536},[2461,2464,2468,2471,2474,2478,2481,2485,2488,2491,2508,2511,2515,2518,2521,2525,2528,2531,2533],[941,2462,2463],{},"The 2018 debate involving Facebook, Aleksandr Kogan, and Cambridge Analytica showed the consequences of opaque handling of personal data. People provide information to organizations in exchange for services or personalized offers. Trust and transparency about what happens to that information are essential to this relationship.",[953,2465,2467],{"id":2466},"gdpr-as-a-new-framework","GDPR as a New Framework",[941,2469,2470],{},"The European Union's General Data Protection Regulation has applied since 25 May 2018. It strengthened data-subject rights, expanded the obligations of organizations that process data, and under certain conditions also applies to companies outside the EU. Serious infringements can result in significant penalties.",[941,2472,2473],{},"The regulation made clear that privacy is not a responsibility of the legal department alone. Business processes, IT systems, and ownership need to be considered together.",[953,2475,2477],{"id":2476},"data-incidents-and-loss-of-trust","Data Incidents and Loss of Trust",[941,2479,2480],{},"Well before GDPR took effect, public data incidents had demonstrated that inadequate protection has more than legal consequences. Reputational damage and lost trust can burden an organization for years. Technical safeguards are therefore necessary, but they are insufficient without clear rules and responsibilities.",[953,2482,2484],{"id":2483},"data-governance-as-an-approach","Data Governance as an Approach",[941,2486,2487],{},"Data governance defines who may access which data, the rules under which it is processed, and how decisions remain traceable. Roles and permissions should follow the principle of least privilege. People receive only the access they genuinely require for their work.",[941,2489,2490],{},"Technical and organizational measures include:",[1508,2492,2493,2496,2499,2502,2505],{},[1511,2494,2495],{},"encryption and secure transmission,",[1511,2497,2498],{},"ongoing confidentiality, integrity, and availability of systems,",[1511,2500,2501],{},"controlled recovery procedures,",[1511,2503,2504],{},"regular reviews of the effectiveness of safeguards,",[1511,2506,2507],{},"documented responsibilities and approvals.",[941,2509,2510],{},"Appropriate measures depend on the organization, its data, and its risks. Data governance therefore does not provide a rigid universal model. It creates a framework in which rules, roles, and controls can be tailored to the specific organization.",[953,2512,2514],{"id":2513},"governing-the-data-lifecycle","Governing the Data Lifecycle",[941,2516,2517],{},"Personal data moves through several phases: collection, use, disclosure, archiving, and deletion. The purpose, legal basis, responsibility, and permitted access must be known for every phase. Only then can an organization answer access requests, perform deletions, and demonstrate processing activities.",[941,2519,2520],{},"A data steward can take business responsibility for defined data domains. Process owners specify workflows, while technical teams implement controls and interfaces. The interaction between those roles is what matters.",[953,2522,2524],{"id":2523},"processes-not-isolated-measures","Processes, Not Isolated Measures",[941,2526,2527],{},"GDPR compliance does not result from a one-time cleanup or the installation of a tool. Policies must be translated into operating processes, accountability must be established permanently, and controls must be reviewed regularly.",[941,2529,2530],{},"Data governance software can make metadata, responsibilities, and data flows visible. It supports implementation but does not replace business decisions or an active governance organization.",[953,2532,1607],{"id":1606},[941,2534,2535],{},"GDPR requires transparency and control over personal data. Data governance provides the organizational and technical foundation: clear roles, defined processes, controlled access, and a traceable data lifecycle. The better these elements work together, the more reliably privacy obligations can be met in day-to-day operations.",{"title":771,"searchDepth":991,"depth":991,"links":2537},[2538,2539,2540,2541,2542,2543],{"id":2466,"depth":991,"text":2467},{"id":2476,"depth":991,"text":2477},{"id":2483,"depth":991,"text":2484},{"id":2513,"depth":991,"text":2514},{"id":2523,"depth":991,"text":2524},{"id":1606,"depth":991,"text":1607},"2018-05-02","Why organizational and technical data governance provides an essential foundation for implementing GDPR.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fgdpr-und-data-governance",{"title":2549,"description":2550,"imageKey":35,"changeFrequency":1420},"GDPR and Data Governance in the Enterprise","Roles, processes, access controls, and data lifecycles connect data governance with the practical requirements of GDPR.","gdpr-und-data-governance","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fgdpr-und-data-governance","oxGQSpdhrpHxywEj9aoEQGsE8TnhOk9BxYEhFs7ZbtI",{"id":2555,"title":2556,"assessmentSlug":934,"associatedSolution":934,"authors":2557,"body":2559,"category":934,"ctaLabel":934,"date":2655,"dateModified":934,"deliveryFormat":934,"description":2656,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":2657,"navigation":27,"newsletterTopic":934,"path":2658,"publicType":149,"published":27,"readTime":2659,"resourceType":934,"schemaType":1416,"seo":2660,"slug":2663,"stem":2664,"teaser":934,"type":934,"__hash__":2665},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Findividuelle-inhalte-fuer-ihre-marketing-automation.md","Custom Content for Your Marketing Automation",[2558],"Dirk Wöhr",{"type":938,"value":2560,"toc":2646},[2561,2564,2568,2571,2574,2580,2585,2589,2592,2596,2601,2604,2610,2615,2619,2622,2625,2631,2636,2640,2643],[941,2562,2563],{},"Email platforms such as Inxmail, Mailchimp, GetResponse, Episerver, and Salesforce Marketing Cloud can automate personalized messages. Complex relationships and content, however, often reside in external systems. This is where the heureka Custom Content Framework (CCF) comes in.",[953,2565,2567],{"id":2566},"dynamic-content-with-xml-and-xslt","Dynamic Content with XML and XSLT",[941,2569,2570],{},"The CCF receives structured data in XML format and transforms it into the required output using XSLT. The result can be HTML, plain text, or another XML structure. Content preparation therefore remains independent of the target system and can be used for newsletters, landing pages, PDFs, or other delivery channels.",[941,2572,2573],{},"Parameters can be supplied with each request. Content is generated when it is needed and can be tailored to the recipient, language, product, or campaign.",[941,2575,2576],{},[1111,2577],{"alt":2578,"src":2579},"Data flow for dynamic content between a source system, the CCF, and an email platform","\u002Fmedia\u002Fresources\u002Fblog\u002Fdynamic-content-workflow.jpg",[941,2581,2582],{},[1869,2583,2584],{},"Dynamic content is generated from source data and delivered to the email platform.",[953,2586,2588],{"id":2587},"intelligent-caching","Intelligent Caching",[941,2590,2591],{},"Dynamic generation does not need to compromise performance. An intelligent cache retains previously calculated results and invalidates them whenever the source data changes. Frequently requested content is delivered quickly while updates continue to propagate reliably.",[953,2593,2595],{"id":2594},"specialized-output-formats","Specialized Output Formats",[2597,2598,2600],"h3",{"id":2599},"pdf-documents-as-email-attachments","PDF Documents as Email Attachments",[941,2602,2603],{},"In one customer project, personalized comparisons of technical devices were generated as PDFs. Technical data was passed to the CCF, transformed into HTML with XSLT, and then rendered in the required layout by a PDF library. The completed document could be sent as a personalized attachment through Inxmail.",[941,2605,2606],{},[1111,2607],{"alt":2608,"src":2609},"Example of a personalized PDF document generated as an Inxmail attachment","\u002Fmedia\u002Fresources\u002Fblog\u002Finxmail-pdf-attachment.jpg",[941,2611,2612],{},[1869,2613,2614],{},"The PDF is assembled from structured data and sent as an individual attachment.",[2597,2616,2618],{"id":2617},"dynamic-images","Dynamic Images",[941,2620,2621],{},"HTML in email is more constrained than HTML on a regular website. Some personalized presentations are therefore better rendered as images. The CCF can turn HTML into JPEG or PNG files through a WebKit-based rendering process. It can output an entire page, a region, or an individual element.",[941,2623,2624],{},"This makes it possible to generate energy labels, personal information, reviews, or language-specific graphics from XML data. The resulting image paths are then embedded in the mailing like any other dynamic content.",[941,2626,2627],{},[1111,2628],{"alt":2629,"src":2630},"Example of a dynamically generated newsletter graphic","\u002Fmedia\u002Fresources\u002Fblog\u002Fdynamic-newsletter-image.jpg",[941,2632,2633],{},[1869,2634,2635],{},"A newsletter graphic generated from HTML and external data.",[953,2637,2639],{"id":2638},"ccf-for-marketing-automation","CCF for Marketing Automation",[941,2641,2642],{},"The Custom Content Framework adds flexible, scalable, and robust content preparation to marketing-automation platforms. Through its REST API, campaigns can access data and presentations that the email platform itself cannot model or render.",[941,2644,2645],{},"Personalization is therefore not limited to text. Complex documents and graphics can also be generated automatically, reproducibly, and for the individual recipient.",{"title":771,"searchDepth":991,"depth":991,"links":2647},[2648,2649,2650,2654],{"id":2566,"depth":991,"text":2567},{"id":2587,"depth":991,"text":2588},{"id":2594,"depth":991,"text":2595,"children":2651},[2652,2653],{"id":2599,"depth":997,"text":2600},{"id":2617,"depth":997,"text":2618},{"id":2638,"depth":991,"text":2639},"2018-08-14","Generate dynamic content, PDFs, and images for automated email campaigns with the heureka Custom Content Framework.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Findividuelle-inhalte-fuer-ihre-marketing-automation","2 min read",{"title":2661,"description":2662,"imageKey":35,"changeFrequency":1420},"Custom Content for Marketing Automation","Learn how the Custom Content Framework creates dynamic content, PDFs, and images for personalized automated email campaigns.","individuelle-inhalte-fuer-ihre-marketing-automation","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Findividuelle-inhalte-fuer-ihre-marketing-automation","gjdYJbDbJujRgW64hArhg9fz56bbMGY4h3DJnbKS9RM",{"id":932,"title":933,"assessmentSlug":934,"associatedSolution":934,"authors":2667,"body":2668,"category":934,"ctaLabel":934,"date":1410,"dateModified":934,"deliveryFormat":934,"description":1411,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":2994,"navigation":27,"newsletterTopic":934,"path":1414,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":2995,"slug":1421,"stem":1422,"teaser":934,"type":934,"__hash__":1423},[936],{"type":938,"value":2669,"toc":2989},[2670,2675,2677,2682,2686,2766,2771,2773,2775,2779,2781,2783,2791,2793,2795,2797,2837,2839,2844,2848,2880,2884,2886,2944,2948,2950,2974,2976,2987],[941,2671,943,2672,951],{},[945,2673,950],{"href":947,"rel":2674},[949],[953,2676,956],{"id":955},[941,2678,959,2679,951],{},[945,2680,964],{"href":962,"rel":2681},[949],[941,2683,967,2684,972],{},[969,2685,971],{},[974,2687,2688],{"className":976,"code":977,"language":978,"meta":771,"style":771},[969,2689,2690,2694,2698,2702,2706,2710,2714,2718,2722,2726,2730,2734,2738,2742,2746,2750,2754,2758,2762],{"__ignoreMap":771},[982,2691,2692],{"class":984,"line":985},[982,2693,988],{},[982,2695,2696],{"class":984,"line":991},[982,2697,994],{"emptyLinePlaceholder":27},[982,2699,2700],{"class":984,"line":997},[982,2701,1000],{},[982,2703,2704],{"class":984,"line":1003},[982,2705,994],{"emptyLinePlaceholder":27},[982,2707,2708],{"class":984,"line":1008},[982,2709,1011],{},[982,2711,2712],{"class":984,"line":1014},[982,2713,1017],{},[982,2715,2716],{"class":984,"line":1020},[982,2717,994],{"emptyLinePlaceholder":27},[982,2719,2720],{"class":984,"line":1025},[982,2721,1028],{},[982,2723,2724],{"class":984,"line":1031},[982,2725,1034],{},[982,2727,2728],{"class":984,"line":1037},[982,2729,1040],{},[982,2731,2732],{"class":984,"line":1043},[982,2733,994],{"emptyLinePlaceholder":27},[982,2735,2736],{"class":984,"line":1048},[982,2737,1051],{},[982,2739,2740],{"class":984,"line":1054},[982,2741,994],{"emptyLinePlaceholder":27},[982,2743,2744],{"class":984,"line":1059},[982,2745,1062],{},[982,2747,2748],{"class":984,"line":1065},[982,2749,1068],{},[982,2751,2752],{"class":984,"line":1071},[982,2753,1074],{},[982,2755,2756],{"class":984,"line":1077},[982,2757,1080],{},[982,2759,2760],{"class":984,"line":1083},[982,2761,1086],{},[982,2763,2764],{"class":984,"line":1089},[982,2765,1092],{},[941,2767,1095,2768,1101],{},[945,2769,1100],{"href":1098,"rel":2770},[949],[941,2772,1104],{},[941,2774,1107],{},[941,2776,2777],{},[1111,2778],{"alt":1113,"src":1114},[941,2780,1117],{},[941,2782,1120],{},[974,2784,2785],{"className":976,"code":1123,"language":978,"meta":771,"style":771},[969,2786,2787],{"__ignoreMap":771},[982,2788,2789],{"class":984,"line":985},[982,2790,1123],{},[953,2792,1133],{"id":1132},[941,2794,1136],{},[941,2796,1139],{},[974,2798,2799],{"className":1142,"code":1143,"language":1144,"meta":771,"style":771},[969,2800,2801,2811,2821],{"__ignoreMap":771},[982,2802,2803,2805,2807,2809],{"class":984,"line":985},[982,2804,1152],{"class":1151},[982,2806,1156],{"class":1155},[982,2808,1159],{"class":1151},[982,2810,1162],{"class":1155},[982,2812,2813,2815,2817,2819],{"class":984,"line":991},[982,2814,1167],{"class":1151},[982,2816,1171],{"class":1170},[982,2818,951],{"class":1155},[982,2820,1176],{"class":1170},[982,2822,2823,2825,2827,2829,2831,2833,2835],{"class":984,"line":997},[982,2824,1181],{"class":1151},[982,2826,1184],{"class":1155},[982,2828,1187],{"class":1151},[982,2830,1191],{"class":1190},[982,2832,1195],{"class":1194},[982,2834,1198],{"class":1190},[982,2836,1201],{"class":1155},[941,2838,1204],{},[974,2840,2842],{"className":2841,"code":1209,"language":1210,"meta":771},[1208],[969,2843,1209],{"__ignoreMap":771},[941,2845,1215,2846,1219],{},[969,2847,1218],{},[974,2849,2850],{"className":976,"code":1222,"language":978,"meta":771,"style":771},[969,2851,2852,2856,2860,2864,2868,2872,2876],{"__ignoreMap":771},[982,2853,2854],{"class":984,"line":985},[982,2855,988],{},[982,2857,2858],{"class":984,"line":991},[982,2859,994],{"emptyLinePlaceholder":27},[982,2861,2862],{"class":984,"line":997},[982,2863,1000],{},[982,2865,2866],{"class":984,"line":1003},[982,2867,1241],{},[982,2869,2870],{"class":984,"line":1008},[982,2871,1246],{},[982,2873,2874],{"class":984,"line":1014},[982,2875,994],{"emptyLinePlaceholder":27},[982,2877,2878],{"class":984,"line":1020},[982,2879,1255],{},[941,2881,1258,2882,1262],{},[969,2883,1261],{},[941,2885,1265],{},[974,2887,2888],{"className":1142,"code":1268,"language":1144,"meta":771,"style":771},[969,2889,2890,2904,2914,2928],{"__ignoreMap":771},[982,2891,2892,2894,2896,2898,2900,2902],{"class":984,"line":985},[982,2893,1152],{"class":1151},[982,2895,1277],{"class":1155},[982,2897,1280],{"class":1151},[982,2899,1283],{"class":1155},[982,2901,1286],{"class":1151},[982,2903,1289],{"class":1155},[982,2905,2906,2908,2910,2912],{"class":984,"line":991},[982,2907,1167],{"class":1151},[982,2909,1296],{"class":1170},[982,2911,951],{"class":1155},[982,2913,1301],{"class":1170},[982,2915,2916,2918,2920,2922,2924,2926],{"class":984,"line":997},[982,2917,1181],{"class":1151},[982,2919,1308],{"class":1155},[982,2921,1312],{"class":1311},[982,2923,1191],{"class":1190},[982,2925,1317],{"class":1194},[982,2927,1320],{"class":1190},[982,2929,2930,2932,2934,2936,2938,2940,2942],{"class":984,"line":1003},[982,2931,1325],{"class":1151},[982,2933,1328],{"class":1155},[982,2935,1312],{"class":1311},[982,2937,1191],{"class":1190},[982,2939,1335],{"class":1194},[982,2941,1198],{"class":1190},[982,2943,1201],{"class":1155},[941,2945,2946],{},[1111,2947],{"alt":1344,"src":1345},[941,2949,1348],{},[974,2951,2952],{"className":1142,"code":1351,"language":1144,"meta":771,"style":771},[969,2953,2954,2962],{"__ignoreMap":771},[982,2955,2956,2958,2960],{"class":984,"line":985},[982,2957,1152],{"class":1151},[982,2959,1360],{"class":1151},[982,2961,1363],{"class":1155},[982,2963,2964,2966,2968,2970,2972],{"class":984,"line":991},[982,2965,1167],{"class":1151},[982,2967,1296],{"class":1170},[982,2969,951],{"class":1155},[982,2971,1374],{"class":1170},[982,2973,1201],{"class":1155},[953,2975,1380],{"id":1379},[941,2977,1383,2978,1389,2981,1394,2984,1400],{},[945,2979,1388],{"href":1386,"rel":2980},[949],[945,2982,1393],{"href":962,"rel":2983},[949],[945,2985,1399],{"href":1397,"rel":2986},[949],[1402,2988,1404],{},{"title":771,"searchDepth":991,"depth":991,"links":2990},[2991,2992,2993],{"id":955,"depth":991,"text":956},{"id":1132,"depth":991,"text":1133},{"id":1379,"depth":991,"text":1380},{},{"title":1418,"description":1419,"imageKey":35,"changeFrequency":1420},{"id":2997,"title":2998,"assessmentSlug":934,"associatedSolution":934,"authors":2999,"body":3000,"category":934,"ctaLabel":934,"date":2655,"dateModified":934,"deliveryFormat":934,"description":3107,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":3108,"navigation":27,"newsletterTopic":934,"path":3109,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":3110,"slug":3113,"stem":3114,"teaser":934,"type":934,"__hash__":3115},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Finxmail-nutzen-durch-integrationen-optimieren.md","Maximizing the Value of Inxmail Through Integrations",[2558],{"type":938,"value":3001,"toc":3092},[3002,3005,3009,3012,3016,3019,3022,3026,3029,3032,3036,3039,3043,3046,3050,3053,3057,3060,3063,3067,3070,3073,3077,3080,3084,3087,3089],[941,3003,3004],{},"Inxmail provides several interfaces, including SOAP, REST, Java, and .NET APIs. These interfaces connect the email marketing platform to CRM solutions, data warehouses, and external automation. The greatest value comes from defining clearly which system is responsible for each category of data.",[953,3006,3008],{"id":3007},"crm-integration","CRM Integration",[941,3010,3011],{},"CRM and email platforms can be connected in two fundamental ways.",[2597,3013,3015],{"id":3014},"real-time-data-transfer","Real-Time Data Transfer",[941,3017,3018],{},"In a real-time integration, registrations, unsubscriptions, and changes are transferred immediately between the systems. Users see current information, and automated processes can react without delay.",[941,3020,3021],{},"The implementation is more demanding, however. Legal requirements need to be represented, concurrent changes must be resolved, and failures must be logged completely. The participating systems also become more dependent on each other's availability.",[2597,3023,3025],{"id":3024},"asynchronous-data-management","Asynchronous Data Management",[941,3027,3028],{},"In an asynchronous integration, the CRM remains the system of record. Relevant recipient data is synchronized with Inxmail at regular intervals. This pattern is technically simpler and creates greater separation between the systems.",[941,3030,3031],{},"Before every mailing, however, the organization must ensure that unsubscriptions have already been synchronized. Triggered mailings should also be initiated by the system of record so that the business state remains unambiguous.",[953,3033,3035],{"id":3034},"selecting-recipients","Selecting Recipients",[941,3037,3038],{},"There are also different approaches to recipient selection.",[2597,3040,3042],{"id":3041},"direct-recipient-lists","Direct Recipient Lists",[941,3044,3045],{},"The system of record prepares a complete recipient list for each campaign and transfers it to Inxmail before delivery. This suits ad hoc campaigns and reduces the amount of selection data stored permanently. The list must, however, be rebuilt and maintained for every campaign.",[2597,3047,3049],{"id":3048},"dynamic-lists-and-target-groups-in-inxmail","Dynamic Lists and Target Groups in Inxmail",[941,3051,3052],{},"Alternatively, the attributes required for selection are synchronized with Inxmail. Filters defined in the platform assign recipients automatically to dynamic lists or target groups. This is efficient for recurring campaigns, but every relevant attribute needs to remain current.",[953,3054,3056],{"id":3055},"synchronization-with-the-heureka-integration-service","Synchronization with the heureka Integration Service",[941,3058,3059],{},"The heureka Integration Service (hIS) can manage data exchange, reporting, and conflict handling. The concept is not limited to Inxmail; other email services such as Salesforce Marketing Cloud can be connected as well.",[941,3061,3062],{},"In addition to master data, the integration can transfer metadata such as registrations, unsubscriptions, bounces, clicks, and opens. Responses from email marketing therefore become available in the CRM or analytical systems.",[953,3064,3066],{"id":3065},"double-opt-in-and-preference-centers","Double Opt-In and Preference Centers",[941,3068,3069],{},"A double-opt-in workflow frequently spans both systems. The CRM knows the contact and the relevant business context, while Inxmail manages the confirmation message and distribution list. The integration must transfer the status completely and traceably between both sides.",[941,3071,3072],{},"An integrated preference center can combine additional preferences from the CRM with subscriptions held in Inxmail. Each data field should again have exactly one designated system of record.",[953,3074,3076],{"id":3075},"extended-reporting","Extended Reporting",[941,3078,3079],{},"Opens, clicks, bounces, and campaign results become more valuable when they are combined with sales, customer, or product data. Transferring them to a data warehouse enables analysis beyond individual mailings and establishes a shared basis for marketing and sales.",[953,3081,3083],{"id":3082},"external-automation","External Automation",[941,3085,3086],{},"External systems can use the Inxmail interfaces to create and trigger mailings and add individual attachments. Triggers may originate in a CRM, online shop, or line-of-business application. The delivery platform handles sending and tracking while the source system retains the business logic.",[953,3088,1607],{"id":1606},[941,3090,3091],{},"Inxmail integrations range from simple list imports to bidirectional real-time architectures. A robust solution begins not with the API but with data ownership: Which information is authoritative, which events must be processed immediately, and which evidence must be retained? Once those questions are answered, the appropriate integration pattern can be selected.",{"title":771,"searchDepth":991,"depth":991,"links":3093},[3094,3098,3102,3103,3104,3105,3106],{"id":3007,"depth":991,"text":3008,"children":3095},[3096,3097],{"id":3014,"depth":997,"text":3015},{"id":3024,"depth":997,"text":3025},{"id":3034,"depth":991,"text":3035,"children":3099},[3100,3101],{"id":3041,"depth":997,"text":3042},{"id":3048,"depth":997,"text":3049},{"id":3055,"depth":991,"text":3056},{"id":3065,"depth":991,"text":3066},{"id":3075,"depth":991,"text":3076},{"id":3082,"depth":991,"text":3083},{"id":1606,"depth":991,"text":1607},"Integration patterns for CRM data, recipient lists, double opt-in, reporting, and automated mailings with Inxmail.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Finxmail-nutzen-durch-integrationen-optimieren",{"title":3111,"description":3112,"imageKey":35,"changeFrequency":1420},"Maximizing Inxmail Through Integrations","A practical overview of CRM synchronization, recipient lists, double opt-in, reporting, and externally automated mailings with Inxmail.","inxmail-nutzen-durch-integrationen-optimieren","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Finxmail-nutzen-durch-integrationen-optimieren","nQ7EWtNO3IhunBJnyVyOBlJENIvylf4UMVmC-yuJrCI",{"id":3117,"title":3118,"assessmentSlug":934,"associatedSolution":934,"authors":3119,"body":3121,"category":934,"ctaLabel":934,"date":3280,"dateModified":934,"deliveryFormat":934,"description":3281,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":3282,"navigation":27,"newsletterTopic":934,"path":3283,"publicType":149,"published":27,"readTime":2659,"resourceType":934,"schemaType":1416,"seo":3284,"slug":3286,"stem":3287,"teaser":934,"type":934,"__hash__":3288},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fmodgen-und-die-erwin-scapi.md","MODGEN and the erwin Script Client API",[3120],"Kevin Petri",{"type":938,"value":3122,"toc":3274},[3123,3126,3129,3133,3140,3147,3151,3154,3160,3165,3169,3178,3209,3219,3223,3226,3229,3255,3261,3266],[941,3124,3125],{},"heureka developed the MODGEN add-in for erwin to automate transformations in data warehouses. The version described at the time could generate a Data Vault model from a staging model. The erwin Script Client API (SCAPI) was indispensable to its development.",[941,3127,3128],{},"SCAPI is an extensive interface. It allows applications to create, open, and modify objects within a model, including tables, columns, and user-defined properties (UDPs).",[953,3130,3132],{"id":3131},"access-levels","Access Levels",[941,3134,3135,3136,3139],{},"The API distinguishes several access levels. At the standard ",[1784,3137,3138],{},"SCD_SL_M0"," level, applications can create, read, and write tables and columns. Simple properties can also be created and modified there.",[941,3141,3142,3143,3146],{},"Access to metadata and the ability to modify or delete UDPs require a session with elevated privileges at the ",[1784,3144,3145],{},"SCD_SL_M1"," level.",[953,3148,3150],{"id":3149},"persistence-units-and-property-bags","Persistence Units and Property Bags",[941,3152,3153],{},"Alongside persistence units, SCAPI provides property bags. They represent the properties of an object. In addition to a name and value, they contain useful flags. These indicate, for example, whether a value is null or scalar and whether a property is read-only.",[941,3155,3156],{},[1111,3157],{"alt":3158,"src":3159},"Class and interface model of the erwin Script Client API","\u002Fmedia\u002Fresources\u002Fblog\u002Fscapi-model.gif",[941,3161,3162],{},[1869,3163,3164],{},"The SCAPI model connects persistence units, ModelObjects, collections, and properties.",[953,3166,3168],{"id":3167},"modelobject-and-modelobjects","ModelObject and ModelObjects",[941,3170,3171,3172,3175,3176,3146],{},"The most frequently used class is ",[969,3173,3174],{},"ModelObject",". Tables and columns are examples of this class and can be accessed through the standard ",[969,3177,3138],{},[941,3179,3180,3183,3184,3186,3187,3190,3191,3194,3195,1283,3198,1283,3201,3204,3205,3208],{},[969,3181,3182],{},"ModelObjects",", in the plural, is a collection of ",[969,3185,3174],{}," instances. It contains an enumerator that supports iteration. The ",[969,3188,3189],{},"NewEnum"," property references the ",[969,3192,3193],{},"IEnumVARIANT"," interface, whose ",[969,3196,3197],{},"Next()",[969,3199,3200],{},"Skip()",[969,3202,3203],{},"Reset()",", and ",[969,3206,3207],{},"Clone()"," methods control the iteration sequence.",[941,3210,3211,3212,3214,3215,3218],{},"A ",[969,3213,3174],{}," also has a ",[969,3216,3217],{},"Properties"," property. The collection can be iterated in full or used to address one specific property.",[953,3220,3222],{"id":3221},"changes-and-transactions","Changes and Transactions",[941,3224,3225],{},"Changes to ModelObjects can be applied directly to the model. A transaction is opened before the objects are retrieved and committed after the required changes. Committing writes every change to the affected objects back to the corresponding erwin model.",[941,3227,3228],{},"Each object is classified by four identifiers:",[1508,3230,3231,3237,3243,3249],{},[1511,3232,3233,3236],{},[969,3234,3235],{},"SC_OBJID"," identifies the specific object.",[1511,3238,3239,3242],{},[969,3240,3241],{},"SC_CLSID"," assigns the object to a class.",[1511,3244,3245,3248],{},[969,3246,3247],{},"SC_MODELTYPEID"," represents the model type.",[1511,3250,3251,3254],{},[969,3252,3253],{},"SC_CREATORID"," identifies the creator.",[941,3256,3257],{},[1111,3258],{"alt":3259,"src":3260},"SCAPI code example that modifies one property on every table","\u002Fmedia\u002Fresources\u002Fblog\u002Fscapi-code-example.png",[941,3262,3263],{},[1869,3264,3265],{},"Example of iterating over tables and changing a property.",[941,3267,1383,3268,3273],{},[945,3269,3272],{"href":3270,"rel":3271},"https:\u002F\u002Fbookshelf.quest.com\u002Fbookshelf\u002F9.8.00\u002FBookshelf_Files\u002FPDF\u002Ferwin_API_Ref.pdf",[949],"erwin API Reference for version 9.8"," provides detailed information and further code examples.",{"title":771,"searchDepth":991,"depth":991,"links":3275},[3276,3277,3278,3279],{"id":3131,"depth":991,"text":3132},{"id":3149,"depth":991,"text":3150},{"id":3167,"depth":991,"text":3168},{"id":3221,"depth":991,"text":3222},"2019-01-29","An overview of the erwin Script Client API and its use in automating data warehouse models with MODGEN.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fmodgen-und-die-erwin-scapi",{"title":3118,"description":3285,"imageKey":35,"changeFrequency":1420},"Core erwin SCAPI concepts: access levels, ModelObjects, property bags, transactions, and object identifiers used by MODGEN.","modgen-und-die-erwin-scapi","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fmodgen-und-die-erwin-scapi","K64lBaPcVS1YoAOFa3kqdYWHJwOvK0ykfn52qRX_JME",{"id":3290,"title":3291,"assessmentSlug":934,"associatedSolution":934,"authors":934,"body":3292,"category":934,"ctaLabel":934,"date":3780,"dateModified":3781,"deliveryFormat":934,"description":3782,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":3783,"navigation":27,"newsletterTopic":934,"path":3784,"publicType":149,"published":27,"readTime":3785,"resourceType":934,"schemaType":1416,"seo":3786,"slug":3788,"stem":3789,"teaser":934,"type":934,"__hash__":3790},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fobservability-runbooks-for-enterprise-teams.md","Practical Observability Runbooks for Enterprise IT Teams",{"type":938,"value":3293,"toc":3765},[3294,3297,3300,3304,3307,3310,3333,3336,3340,3343,3346,3350,3353,3464,3467,3471,3474,3477,3521,3524,3528,3531,3551,3554,3558,3561,3564,3584,3587,3591,3594,3597,3629,3632,3636,3639,3642,3646,3649,3678,3681,3685,3688,3705,3708,3712,3715,3738,3741,3745,3748,3751,3753,3756],[941,3295,3296],{},"Observability is most useful when technical signals lead to explainable decisions. Metrics, logs, traces, events, and dashboards provide visibility. During an incident, an operations team also needs a shared response path: what is actually affected, which signals matter, what changed, which dependency should be checked, and who is allowed to perform a recovery action?",[941,3298,3299],{},"That is the role of an observability runbook. It is not a collection of screenshots and it is not complete documentation for the monitoring platform. A good runbook describes the shortest dependable path from a symptom to a qualified hypothesis, a controlled action, and verification that the service has recovered.",[953,3301,3303],{"id":3302},"runbooks-should-support-decisions","Runbooks should support decisions",[941,3305,3306],{},"Runbooks often become too large because they try to explain every possible failure scenario. For incident response, a more useful perspective is to start with the decisions responders need to make in the first minutes and the information required to make them.",[941,3308,3309],{},"An operational runbook should answer at least these questions:",[1508,3311,3312,3315,3318,3321,3324,3327,3330],{},[1511,3313,3314],{},"Which service or business process is affected?",[1511,3316,3317],{},"Which team owns the service operationally?",[1511,3319,3320],{},"What level of impact requires escalation?",[1511,3322,3323],{},"Which telemetry provides the primary starting point?",[1511,3325,3326],{},"Which dependencies and recent changes need to be checked?",[1511,3328,3329],{},"Which actions are permitted and which approvals are required?",[1511,3331,3332],{},"How do responders verify that the service is actually stable again?",[941,3334,3335],{},"The goal is not maximum documentation. It is a repeatable decision path.",[953,3337,3339],{"id":3338},"establish-service-context-and-ownership-first","Establish service context and ownership first",[941,3341,3342],{},"Before a runbook points to dashboards or queries, it should explain what the monitored service does. That includes its business function, owning team, relevant dependencies, and escalation path. In larger environments, the application, platform, database, network, and monitoring stack may belong to different teams. Those boundaries should be visible in the runbook.",[941,3344,3345],{},"The runbook should also define how to assess customer or business impact. A technical fault is not automatically a critical incident, while a modest technical deviation may matter if it affects an important process. Responders therefore need a clear way to evaluate impact before setting priority and escalation.",[953,3347,3349],{"id":3348},"a-practical-minimum-structure","A practical minimum structure",[941,3351,3352],{},"A consistent structure makes it easier for teams to navigate runbooks even when they do not know the service well.",[3354,3355,3356,3372],"table",{},[3357,3358,3359],"thead",{},[3360,3361,3362,3366,3369],"tr",{},[3363,3364,3365],"th",{},"Runbook element",[3363,3367,3368],{},"Content",[3363,3370,3371],{},"Purpose",[3373,3374,3375,3387,3398,3409,3420,3431,3442,3453],"tbody",{},[3360,3376,3377,3381,3384],{},[3378,3379,3380],"td",{},"Service context",[3378,3382,3383],{},"Service, business function, owner, criticality",[3378,3385,3386],{},"Places the signal in context",[3360,3388,3389,3392,3395],{},[3378,3390,3391],{},"Trigger & impact",[3378,3393,3394],{},"Alert, symptom, affected users or processes",[3378,3396,3397],{},"Separates signal from actual impact",[3360,3399,3400,3403,3406],{},[3378,3401,3402],{},"Primary telemetry",[3378,3404,3405],{},"Relevant dashboards, metrics, logs, traces",[3378,3407,3408],{},"Provides a defined starting point",[3360,3410,3411,3414,3417],{},[3378,3412,3413],{},"Dependencies",[3378,3415,3416],{},"Upstream, downstream, and platform dependencies",[3378,3418,3419],{},"Prevents isolated diagnosis",[3360,3421,3422,3425,3428],{},[3378,3423,3424],{},"Change context",[3378,3426,3427],{},"Deployments, configuration, infrastructure, scheduled jobs",[3378,3429,3430],{},"Makes timing correlations reviewable",[3360,3432,3433,3436,3439],{},[3378,3434,3435],{},"Escalation",[3378,3437,3438],{},"Ownership, contact path, handoff criteria",[3378,3440,3441],{},"Avoids ambiguous responsibility",[3360,3443,3444,3447,3450],{},[3378,3445,3446],{},"Recovery",[3378,3448,3449],{},"Approved actions, risks, approvals, rollback",[3378,3451,3452],{},"Keeps interventions controlled",[3360,3454,3455,3458,3461],{},[3378,3456,3457],{},"Verification",[3378,3459,3460],{},"Expected signals after the action",[3378,3462,3463],{},"Prevents premature closure",[941,3465,3466],{},"The tools and links can differ by service. The structure should remain as consistent as possible.",[953,3468,3470],{"id":3469},"build-investigation-paths-from-symptoms","Build investigation paths from symptoms",[941,3472,3473],{},"A runbook should not assume that the cause is already known. It should start from the observable symptom and reduce uncertainty step by step.",[941,3475,3476],{},"A useful investigation path can look like this:",[1695,3478,3479,3485,3491,3497,3503,3509,3515],{},[1511,3480,3481,3484],{},[1784,3482,3483],{},"Confirm impact."," Determine whether the signal is actually affecting a service, user, or business process.",[1511,3486,3487,3490],{},[1784,3488,3489],{},"Set the time window."," Compare the start of the symptom with a normal reference period.",[1511,3492,3493,3496],{},[1784,3494,3495],{},"Check the primary signal."," Open the defined dashboard or service view instead of exploring several tools without a clear priority.",[1511,3498,3499,3502],{},[1784,3500,3501],{},"Correlate telemetry."," Compare metrics, logs, and traces for the same time window and service context.",[1511,3504,3505,3508],{},[1784,3506,3507],{},"Check dependencies."," Review relevant databases, interfaces, network paths, platform services, or external dependencies.",[1511,3510,3511,3514],{},[1784,3512,3513],{},"Compare recent changes."," Check deployments, configuration changes, infrastructure changes, and scheduled jobs around the start of the symptom.",[1511,3516,3517,3520],{},[1784,3518,3519],{},"Record the hypothesis."," Capture which observation justifies the next action.",[941,3522,3523],{},"This reduces the risk of jumping directly to a familiar cause or comparing unrelated data from different time windows.",[953,3525,3527],{"id":3526},"alerts-need-context-not-just-thresholds","Alerts need context, not just thresholds",[941,3529,3530],{},"An alert is an entry point into an investigation. A runbook should therefore contain more than the alert name. Useful context includes:",[1508,3532,3533,3536,3539,3542,3545,3548],{},[1511,3534,3535],{},"the behavior the alert is intended to detect;",[1511,3537,3538],{},"the service impact that may correspond to it;",[1511,3540,3541],{},"the first dashboard or view to open;",[1511,3543,3544],{},"the dimensions or filters needed for investigation;",[1511,3546,3547],{},"known non-critical patterns;",[1511,3549,3550],{},"the criteria for escalation versus continued observation.",[941,3552,3553],{},"For a latency alert, for example, it is not enough to state that a value is elevated. The runbook should clarify whether responders first examine end-to-end latency, specific endpoints, dependencies, or resource pressure. That turns a signal into a repeatable investigation path.",[953,3555,3557],{"id":3556},"treat-recent-changes-as-a-separate-investigation-step","Treat recent changes as a separate investigation step",[941,3559,3560],{},"Deployments and configuration changes should be considered in the same time context as telemetry. A runbook should state where changes are visible and which types of changes matter for the service.",[941,3562,3563],{},"Examples can include:",[1508,3565,3566,3569,3572,3575,3578,3581],{},[1511,3567,3568],{},"application and platform deployments;",[1511,3570,3571],{},"configuration and feature-flag changes;",[1511,3573,3574],{},"network, firewall, or routing changes;",[1511,3576,3577],{},"certificate and identity changes;",[1511,3579,3580],{},"database or schema changes;",[1511,3582,3583],{},"scheduled batch and maintenance processes.",[941,3585,3586],{},"The objective is not to treat every change as the cause. The objective is to compare changes systematically with the start and progression of the symptom.",[953,3588,3590],{"id":3589},"document-recovery-with-clear-guardrails","Document recovery with clear guardrails",[941,3592,3593],{},"The most sensitive part of a runbook is often recovery rather than diagnosis. Restarting a service, rolling back a release, switching a feature flag, or draining a queue changes system state. Every recovery action therefore needs explicit conditions.",[941,3595,3596],{},"For each action, document:",[1508,3598,3599,3605,3611,3617,3623],{},[1511,3600,3601,3604],{},[1784,3602,3603],{},"Prerequisite:"," Which observation must be present?",[1511,3606,3607,3610],{},[1784,3608,3609],{},"Impact:"," Which components, users, or data may be affected?",[1511,3612,3613,3616],{},[1784,3614,3615],{},"Authorization:"," Who may execute or approve the action?",[1511,3618,3619,3622],{},[1784,3620,3621],{},"Rollback:"," How is the action reversed if it does not help?",[1511,3624,3625,3628],{},[1784,3626,3627],{},"Verification:"," Which signals must return to an expected state afterward?",[941,3630,3631],{},"A runbook should not present a risky action as a universal default. If an action is safe only under specific conditions, those conditions belong directly next to the step.",[953,3633,3635],{"id":3634},"make-escalation-and-handoff-explicit","Make escalation and handoff explicit",[941,3637,3638],{},"Complex incidents often move between teams as the investigation develops. A runbook should therefore include not only contact information but also handoff criteria.",[941,3640,3641],{},"Examples include a confirmed database dependency, a network issue outside the current team's responsibility, or a recovery action that requires additional approval. A useful handoff includes the current impact, telemetry already reviewed, relevant time window, actions already taken, and the current hypothesis. The next team should not have to restart the investigation from zero.",[953,3643,3645],{"id":3644},"example-a-high-latency-runbook","Example: a high-latency runbook",[941,3647,3648],{},"A compact response path for elevated service latency could be structured as follows:",[1695,3650,3651,3654,3657,3660,3663,3666,3669,3672,3675],{},[1511,3652,3653],{},"Confirm customer or process impact using the defined service view.",[1511,3655,3656],{},"Identify when latency increased and compare it with error rate, throughput, and resource behavior.",[1511,3658,3659],{},"Narrow the issue to affected endpoints or transactions.",[1511,3661,3662],{},"Review traces and logs for the same time window and request context.",[1511,3664,3665],{},"Check dependencies such as databases, APIs, or platform services for correlated symptoms.",[1511,3667,3668],{},"Compare deployments and configuration changes around the start of the issue.",[1511,3670,3671],{},"Execute recovery only if the documented prerequisites are met.",[1511,3673,3674],{},"After recovery, verify not only the original alert but also service impact and relevant dependencies.",[1511,3676,3677],{},"Capture new findings for the alert, dashboard, or runbook.",[941,3679,3680],{},"The technical implementation will vary with the stack. The response path remains understandable because it focuses on decisions and evidence rather than tool navigation.",[953,3682,3684],{"id":3683},"maintain-runbooks-as-part-of-the-operating-model","Maintain runbooks as part of the operating model",[941,3686,3687],{},"A runbook becomes stale when the service, telemetry, or ownership changes. Maintenance should therefore be tied to real operational events. Useful review triggers include:",[1508,3689,3690,3693,3696,3699,3702],{},[1511,3691,3692],{},"an incident exposed a missing or incorrect step;",[1511,3694,3695],{},"an alert or dashboard changed;",[1511,3697,3698],{},"a dependency was added or replaced;",[1511,3700,3701],{},"a deployment or recovery process changed;",[1511,3703,3704],{},"ownership or escalation paths changed.",[941,3706,3707],{},"Regular review of the most important services is also useful. It does not require rewriting every paragraph. Links, ownership, prerequisites, and recovery steps deserve particular attention because outdated information in those areas can slow responders immediately.",[953,3709,3711],{"id":3710},"how-to-recognize-a-useful-runbook","How to recognize a useful runbook",[941,3713,3714],{},"A runbook is operationally useful when a knowledgeable team member can act without having to guess undocumented assumptions. Practical quality criteria include:",[1508,3716,3717,3720,3723,3726,3729,3732,3735],{},[1511,3718,3719],{},"The starting point is unambiguous.",[1511,3721,3722],{},"Service impact and technical signal are evaluated separately.",[1511,3724,3725],{},"Each investigation step leads to an expected observation or next decision.",[1511,3727,3728],{},"Dependencies and recent changes are part of the workflow.",[1511,3730,3731],{},"Recovery actions include prerequisites and verification.",[1511,3733,3734],{},"Escalation criteria are concrete.",[1511,3736,3737],{},"The document can be updated directly from incident findings.",[941,3739,3740],{},"If a runbook is only a list of links, the decision path is missing. If it tries to explain every theoretical failure mode, it becomes too slow during an incident. The useful middle ground is a concise, verifiable workflow with enough context for safe decisions.",[953,3742,3744],{"id":3743},"introduce-runbooks-incrementally","Introduce runbooks incrementally",[941,3746,3747],{},"A practical starting point is to focus on services where outages matter or where several teams regularly need to collaborate. Existing incidents are useful source material: which questions were repeatedly asked, which dashboards were actually useful, where was ownership unclear, and which recovery action worked under which conditions?",[941,3749,3750],{},"Those answers produce a runbook grounded in real operations. Additional services can then follow the same structure. This creates a shared runbook practice without requiring a complete documentation program upfront.",[953,3752,1607],{"id":1606},[941,3754,3755],{},"Observability runbooks connect telemetry with operational responsibility. Their value is not the amount of information they contain, but their ability to help teams make faster, explainable, and controlled decisions under pressure.",[941,3757,3758,3759,3761,3762,951],{},"If you want to connect your monitoring and observability environment more closely with incident processes, service context, and dependable operational workflows, see ",[945,3760,244],{"href":83},". For a concrete review of your current setup, ",[945,3763,3764],{"href":6},"contact heureka",{"title":771,"searchDepth":991,"depth":991,"links":3766},[3767,3768,3769,3770,3771,3772,3773,3774,3775,3776,3777,3778,3779],{"id":3302,"depth":991,"text":3303},{"id":3338,"depth":991,"text":3339},{"id":3348,"depth":991,"text":3349},{"id":3469,"depth":991,"text":3470},{"id":3526,"depth":991,"text":3527},{"id":3556,"depth":991,"text":3557},{"id":3589,"depth":991,"text":3590},{"id":3634,"depth":991,"text":3635},{"id":3644,"depth":991,"text":3645},{"id":3683,"depth":991,"text":3684},{"id":3710,"depth":991,"text":3711},{"id":3743,"depth":991,"text":3744},{"id":1606,"depth":991,"text":1607},"2026-06-07","2026-09-04","How enterprise IT teams can structure observability runbooks that connect service context, telemetry, change data, escalation, and safe recovery into a dependable incident workflow.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fobservability-runbooks-for-enterprise-teams","8 min read",{"title":3291,"description":3787,"imageKey":35,"changeFrequency":1420},"A practical guide to observability runbooks with clear ownership, investigation paths, recovery guardrails, and continuous maintenance.","observability-runbooks-for-enterprise-teams","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fobservability-runbooks-for-enterprise-teams","U9S8uWnRe_ekQ3195gQf2xeMswxAPlR7K7lADIsZ894",{"id":3792,"title":3793,"assessmentSlug":934,"associatedSolution":934,"authors":3794,"body":3796,"category":934,"ctaLabel":934,"date":3897,"dateModified":934,"deliveryFormat":934,"description":3898,"downloadFileName":934,"downloadLabel":934,"downloadUrl":934,"excerpt":771,"exclusive":23,"exclusiveLabel":934,"extension":1412,"featured":23,"format":934,"gated":23,"healthCheckSlug":934,"keyTakeaways":934,"meta":3899,"navigation":27,"newsletterTopic":934,"path":3900,"publicType":149,"published":27,"readTime":1415,"resourceType":934,"schemaType":1416,"seo":3901,"slug":3903,"stem":3904,"teaser":934,"type":934,"__hash__":3905},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fwebentwicklung-mit-coldfusion-und-reactjs.md","Web Development with ColdFusion and ReactJS",[3795],"Jonathan Holz",{"type":938,"value":3797,"toc":3889},[3798,3801,3805,3808,3814,3819,3822,3826,3829,3832,3838,3843,3847,3850,3853,3857,3860,3866,3871,3874,3878,3881,3884,3886],[941,3799,3800],{},"Web development changes continuously. New devices, higher usability expectations, and growing applications demand a clear structure. One approach is to decouple the frontend from the backend. ReactJS manages the user interface, while ColdFusion exposes data and business logic through a REST API.",[953,3802,3804],{"id":3803},"rest-apis-as-the-connection","REST APIs as the Connection",[941,3806,3807],{},"A REST API exposes resources through clearly defined HTTP endpoints. Client and server typically exchange JSON documents. The interface remains stateless: every request contains the information required to process it.",[941,3809,3810],{},[1111,3811],{"alt":3812,"src":3813},"Communication between a client, REST API, and database","\u002Fmedia\u002Fresources\u002Fblog\u002Fcoldfusion-rest-api.png",[941,3815,3816],{},[1869,3817,3818],{},"The client communicates with a REST API over HTTP using JSON.",[941,3820,3821],{},"This separation has a practical benefit. The backend can serve mobile apps or other systems in addition to the web interface. The frontend, in turn, does not need to know how data is stored internally.",[953,3823,3825],{"id":3824},"coldfusion-in-the-backend","ColdFusion in the Backend",[941,3827,3828],{},"ColdFusion can implement the business logic and REST endpoints. In the architecture described here, the CFWheels framework organizes the application into models and controllers. Models represent data and rules; controllers process HTTP requests and return the appropriate responses.",[941,3830,3831],{},"Additional services encapsulate business functions that do not belong directly in a controller. Database access can be handled through an ORM. The result is a backend with separated responsibilities and functions available through a consistent API.",[941,3833,3834],{},[1111,3835],{"alt":3836,"src":3837},"ColdFusion backend with controllers, services, ORM, and database","\u002Fmedia\u002Fresources\u002Fblog\u002Fcoldfusion-backend.png",[941,3839,3840],{},[1869,3841,3842],{},"Controllers coordinate services and data access and return JSON to the client.",[953,3844,3846],{"id":3845},"reactjs-in-the-frontend","ReactJS in the Frontend",[941,3848,3849],{},"ReactJS builds the user interface from reusable components. A component combines presentation and behavior for a clearly bounded part of the application. State changes cause React to render the affected areas again.",[941,3851,3852],{},"The frontend calls REST endpoints asynchronously and processes the JSON data returned. It can be developed and deployed independently of the ColdFusion code as long as the API contract remains stable.",[953,3854,3856],{"id":3855},"authentication-without-a-server-side-session","Authentication Without a Server-Side Session",[941,3858,3859],{},"With a stateless API, authentication is not managed through a conventional server-side session. After a successful login, the server can instead issue a JSON Web Token (JWT). The token contains a header, payload, and cryptographic signature.",[941,3861,3862],{},[1111,3863],{"alt":3864,"src":3865},"Structure of a JSON Web Token with header, payload, and signature","\u002Fmedia\u002Fresources\u002Fblog\u002Fcoldfusion-jwt.png",[941,3867,3868],{},[1869,3869,3870],{},"The token carries the information required for subsequent requests.",[941,3872,3873],{},"The client submits the token with later requests. The server verifies its signature and validity before carrying out the requested action. The frontend can retain the token locally; the actual implementation must make deliberate decisions about storage, expiration, renewal, and protection against attacks.",[953,3875,3877],{"id":3876},"performance-and-evolution","Performance and Evolution",[941,3879,3880],{},"The decoupled architecture makes it possible to load data asynchronously and update only the parts of the interface that changed. Frontend and backend can be developed, tested, and deployed as separate packages.",[941,3882,3883],{},"The separation also creates a clear boundary: the REST API is a contract that must be maintained and versioned. Error handling, authentication, and authorization are as much a part of that contract as the structure of the JSON responses.",[953,3885,1607],{"id":1606},[941,3887,3888],{},"ColdFusion and ReactJS complement one another in this architecture. ColdFusion provides data and business logic, ReactJS delivers a component-based interface, and REST with JSON connects the two sides. Decoupling improves reuse and supports parallel development, but it requires a carefully defined and secured API.",{"title":771,"searchDepth":991,"depth":991,"links":3890},[3891,3892,3893,3894,3895,3896],{"id":3803,"depth":991,"text":3804},{"id":3824,"depth":991,"text":3825},{"id":3845,"depth":991,"text":3846},{"id":3855,"depth":991,"text":3856},{"id":3876,"depth":991,"text":3877},{"id":1606,"depth":991,"text":1607},"2020-06-03","Decouple frontend and backend with ReactJS, ColdFusion, REST, and JSON to build modular web applications.",{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Fwebentwicklung-mit-coldfusion-und-reactjs",{"title":3793,"description":3902,"imageKey":35,"changeFrequency":1420},"An architecture for decoupled web applications using ReactJS, a ColdFusion backend, REST APIs, JSON, and JWT authentication.","webentwicklung-mit-coldfusion-und-reactjs","locales\u002Fenglish\u002Fresources\u002Fblogs\u002Fwebentwicklung-mit-coldfusion-und-reactjs","-TgLXwdIoNHzt6YHQpL2-F2NBvWP-ziYnI9OfFPDpgw",{"id":3907,"title":3908,"assessmentSlug":1429,"associatedSolution":100,"authors":934,"body":3909,"category":4531,"ctaLabel":4532,"date":1442,"dateModified":1442,"deliveryFormat":4533,"description":4534,"downloadFileName":4535,"downloadLabel":4536,"downloadUrl":4537,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":27,"format":4531,"gated":27,"healthCheckSlug":934,"keyTakeaways":4539,"meta":4544,"navigation":27,"newsletterTopic":1452,"path":4547,"publicType":4548,"published":27,"readTime":4549,"resourceType":4550,"schemaType":1457,"seo":4551,"slug":3913,"stem":4552,"teaser":4553,"type":4531,"__hash__":4554},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fdata-governance-maturity-checklist.md","Data Governance Maturity Checklist",{"type":938,"value":3910,"toc":4519},[3911,3914,3917,3923,3927,3980,3984,3987,4018,4023,4034,4038,4041,4068,4072,4080,4084,4087,4120,4124,4135,4139,4142,4175,4179,4190,4194,4197,4230,4234,4242,4246,4249,4282,4286,4294,4298,4301,4334,4338,4346,4350,4353,4386,4390,4398,4402,4405],[1433,3912,3908],{"id":3913},"data-governance-maturity-checklist",[941,3915,3916],{},"Use this checklist in a working session with business domain owners, data stewards, platform teams, information security, compliance, and enterprise architecture. For each control, record the current status, accountable owner, evidence, and next review date.",[3918,3919,3920],"blockquote",{},[941,3921,3922],{},"Rate each item as established, partially established, planned, missing, or unclear. Treat “established” as requiring repeatable evidence—not only an agreed intention.",[953,3924,3926],{"id":3925},"assessment-scale","Assessment scale",[3354,3928,3929,3938],{},[3357,3930,3931],{},[3360,3932,3933,3935],{},[3363,3934,1159],{},[3363,3936,3937],{},"Meaning",[3373,3939,3940,3948,3956,3964,3972],{},[3360,3941,3942,3945],{},[3378,3943,3944],{},"Established",[3378,3946,3947],{},"Implemented, owned, repeatable, and evidenced",[3360,3949,3950,3953],{},[3378,3951,3952],{},"Partially established",[3378,3954,3955],{},"Works only for part of the scope or depends on manual effort",[3360,3957,3958,3961],{},[3378,3959,3960],{},"Planned",[3378,3962,3963],{},"Approved work exists but the control is not operational",[3360,3965,3966,3969],{},[3378,3967,3968],{},"Missing",[3378,3970,3971],{},"No reliable control or owner exists",[3360,3973,3974,3977],{},[3378,3975,3976],{},"Unclear",[3378,3978,3979],{},"Evidence or responsibility could not be confirmed",[953,3981,3983],{"id":3982},"_1-ownership-and-decision-rights","1. Ownership and decision rights",[941,3985,3986],{},"Confirm that business accountability is explicit for critical data domains and decisions.",[1508,3988,3991,4000,4006,4012],{"className":3989},[3990],"contains-task-list",[1511,3992,3995,3999],{"className":3993},[3994],"task-list-item",[3996,3997],"input",{"disabled":27,"type":3998},"checkbox"," Critical data domains are defined and have formally assigned Data Owners.",[1511,4001,4003,4005],{"className":4002},[3994],[3996,4004],{"disabled":27,"type":3998}," Data Owners have documented decision rights for definitions, quality thresholds, access, and lifecycle rules.",[1511,4007,4009,4011],{"className":4008},[3994],[3996,4010],{"disabled":27,"type":3998}," Ownership remains valid across organisational changes and is reviewed on a fixed cadence.",[1511,4013,4015,4017],{"className":4014},[3994],[3996,4016],{"disabled":27,"type":3998}," Escalation paths exist for conflicts between business domains, technology teams, security, and compliance.",[941,4019,4020],{},[1784,4021,4022],{},"Evidence to collect",[1508,4024,4025,4028,4031],{},[1511,4026,4027],{},"Domain map and ownership register",[1511,4029,4030],{},"RACI or decision-rights matrix",[1511,4032,4033],{},"Minutes from ownership reviews",[953,4035,4037],{"id":4036},"_2-data-stewardship-and-governance-roles","2. Data stewardship and governance roles",[941,4039,4040],{},"Check whether day-to-day governance work has named roles, capacity, and operating routines.",[1508,4042,4044,4050,4056,4062],{"className":4043},[3990],[1511,4045,4047,4049],{"className":4046},[3994],[3996,4048],{"disabled":27,"type":3998}," Data Stewards are assigned for priority domains and their responsibilities are documented.",[1511,4051,4053,4055],{"className":4052},[3994],[3996,4054],{"disabled":27,"type":3998}," Stewards have sufficient capacity and access to subject-matter experts and technical teams.",[1511,4057,4059,4061],{"className":4058},[3994],[3996,4060],{"disabled":27,"type":3998}," A governance council or equivalent forum has a defined mandate, membership, and decision cadence.",[1511,4063,4065,4067],{"className":4064},[3994],[3996,4066],{"disabled":27,"type":3998}," Role handovers, deputies, and onboarding material reduce dependence on individual people.",[941,4069,4070],{},[1784,4071,4022],{},[1508,4073,4074,4077],{},[1511,4075,4076],{},"Role descriptions and capacity allocation",[1511,4078,4079],{},"Governance meeting calendar and decision log",[953,4081,4083],{"id":4082},"_3-business-glossary-metadata-and-catalog-coverage","3. Business glossary, metadata, and catalog coverage",[941,4085,4086],{},"Determine whether business meaning and technical context can be found and maintained.",[1508,4088,4090,4096,4102,4108,4114],{"className":4089},[3990],[1511,4091,4093,4095],{"className":4092},[3994],[3996,4094],{"disabled":27,"type":3998}," Priority business terms have approved definitions, owners, synonyms, and usage guidance.",[1511,4097,4099,4101],{"className":4098},[3994],[3996,4100],{"disabled":27,"type":3998}," Critical datasets, reports, interfaces, and data products are registered in a catalog or equivalent inventory.",[1511,4103,4105,4107],{"className":4104},[3994],[3996,4106],{"disabled":27,"type":3998}," Technical metadata ingestion is automated for priority platforms and monitored for failures.",[1511,4109,4111,4113],{"className":4110},[3994],[3996,4112],{"disabled":27,"type":3998}," Lineage is available at the level needed for impact analysis, incident investigation, and regulatory evidence.",[1511,4115,4117,4119],{"className":4116},[3994],[3996,4118],{"disabled":27,"type":3998}," Metadata quality, freshness, and ownership are measured instead of relying on one-off documentation projects.",[941,4121,4122],{},[1784,4123,4022],{},[1508,4125,4126,4129,4132],{},[1511,4127,4128],{},"Glossary approval workflow",[1511,4130,4131],{},"Catalog coverage report",[1511,4133,4134],{},"Metadata ingestion monitoring",[953,4136,4138],{"id":4137},"_4-data-quality-controls-and-issue-management","4. Data quality controls and issue management",[941,4140,4141],{},"Verify that quality expectations are measurable and quality incidents are owned through resolution.",[1508,4143,4145,4151,4157,4163,4169],{"className":4144},[3990],[1511,4146,4148,4150],{"className":4147},[3994],[3996,4149],{"disabled":27,"type":3998}," Critical data elements are identified and linked to business processes, reports, or regulatory obligations.",[1511,4152,4154,4156],{"className":4153},[3994],[3996,4155],{"disabled":27,"type":3998}," Quality rules define dimensions, thresholds, measurement frequency, and business impact.",[1511,4158,4160,4162],{"className":4159},[3994],[3996,4161],{"disabled":27,"type":3998}," Quality results are visible to Data Owners and operational teams in a consistent scorecard.",[1511,4164,4166,4168],{"className":4165},[3994],[3996,4167],{"disabled":27,"type":3998}," Issues have severity, owner, root cause, remediation date, and escalation criteria.",[1511,4170,4172,4174],{"className":4171},[3994],[3996,4173],{"disabled":27,"type":3998}," Recurring defects trigger preventive changes to source processes, interfaces, or controls.",[941,4176,4177],{},[1784,4178,4022],{},[1508,4180,4181,4184,4187],{},[1511,4182,4183],{},"Critical data element register",[1511,4185,4186],{},"Quality rule catalogue and scorecards",[1511,4188,4189],{},"Issue backlog with root-cause fields",[953,4191,4193],{"id":4192},"_5-classification-access-and-responsibility","5. Classification, access, and responsibility",[941,4195,4196],{},"Check that sensitive data is classified and access decisions have accountable owners.",[1508,4198,4200,4206,4212,4218,4224],{"className":4199},[3990],[1511,4201,4203,4205],{"className":4202},[3994],[3996,4204],{"disabled":27,"type":3998}," Classification levels and handling rules are defined and usable by business and technology teams.",[1511,4207,4209,4211],{"className":4208},[3994],[3996,4210],{"disabled":27,"type":3998}," Data classifications are recorded in systems or metadata repositories and reviewed when data usage changes.",[1511,4213,4215,4217],{"className":4214},[3994],[3996,4216],{"disabled":27,"type":3998}," Access requests require business approval appropriate to the data classification and purpose.",[1511,4219,4221,4223],{"className":4220},[3994],[3996,4222],{"disabled":27,"type":3998}," Privileged and sensitive access is recertified periodically, including service accounts and data extracts.",[1511,4225,4227,4229],{"className":4226},[3994],[3996,4228],{"disabled":27,"type":3998}," Access exceptions are time-bound, documented, and visible to Data Owners and security.",[941,4231,4232],{},[1784,4233,4022],{},[1508,4235,4236,4239],{},[1511,4237,4238],{},"Classification standard and handling matrix",[1511,4240,4241],{},"Access approval and recertification records",[953,4243,4245],{"id":4244},"_6-lifecycle-retention-and-deletion","6. Lifecycle, retention, and deletion",[941,4247,4248],{},"Confirm that lifecycle obligations are connected to real datasets and operational execution.",[1508,4250,4252,4258,4264,4270,4276],{"className":4251},[3990],[1511,4253,4255,4257],{"className":4254},[3994],[3996,4256],{"disabled":27,"type":3998}," Retention schedules map legal and business requirements to concrete data categories and systems.",[1511,4259,4261,4263],{"className":4260},[3994],[3996,4262],{"disabled":27,"type":3998}," Archive, deletion, and anonymisation controls have defined owners and technical implementation patterns.",[1511,4265,4267,4269],{"className":4266},[3994],[3996,4268],{"disabled":27,"type":3998}," Legal holds and exceptions prevent premature deletion and are traceable.",[1511,4271,4273,4275],{"className":4272},[3994],[3996,4274],{"disabled":27,"type":3998}," Deletion jobs are monitored, failures are remediated, and completion evidence is retained.",[1511,4277,4279,4281],{"className":4278},[3994],[3996,4280],{"disabled":27,"type":3998}," New systems and data products cannot go live without lifecycle and decommissioning decisions.",[941,4283,4284],{},[1784,4285,4022],{},[1508,4287,4288,4291],{},[1511,4289,4290],{},"Retention schedule linked to systems",[1511,4292,4293],{},"Deletion run reports and exception register",[953,4295,4297],{"id":4296},"_7-policies-auditability-and-governance-kpis","7. Policies, auditability, and governance KPIs",[941,4299,4300],{},"Assess whether governance can demonstrate effectiveness and improve based on evidence.",[1508,4302,4304,4310,4316,4322,4328],{"className":4303},[3990],[1511,4305,4307,4309],{"className":4306},[3994],[3996,4308],{"disabled":27,"type":3998}," Governance policies are versioned, approved, communicated, and linked to operational controls.",[1511,4311,4313,4315],{"className":4312},[3994],[3996,4314],{"disabled":27,"type":3998}," Exceptions include rationale, risk acceptance, approver, expiry date, and compensating controls.",[1511,4317,4319,4321],{"className":4318},[3994],[3996,4320],{"disabled":27,"type":3998}," Audit evidence can be produced without reconstructing decisions from email and individual knowledge.",[1511,4323,4325,4327],{"className":4324},[3994],[3996,4326],{"disabled":27,"type":3998}," KPIs cover adoption, metadata coverage, quality, issue ageing, policy compliance, and business outcomes.",[1511,4329,4331,4333],{"className":4330},[3994],[3996,4332],{"disabled":27,"type":3998}," Governance metrics lead to decisions and funded improvement actions rather than passive reporting.",[941,4335,4336],{},[1784,4337,4022],{},[1508,4339,4340,4343],{},[1511,4341,4342],{},"Policy register and exception log",[1511,4344,4345],{},"Governance KPI dashboard and decision minutes",[953,4347,4349],{"id":4348},"_8-tooling-and-stakeholder-adoption","8. Tooling and stakeholder adoption",[941,4351,4352],{},"Ensure tools support the operating model and stakeholders know how to use governance processes.",[1508,4354,4356,4362,4368,4374,4380],{"className":4355},[3990],[1511,4357,4359,4361],{"className":4358},[3994],[3996,4360],{"disabled":27,"type":3998}," Tooling requirements are derived from governance use cases and workflows, not vendor feature lists.",[1511,4363,4365,4367],{"className":4364},[3994],[3996,4366],{"disabled":27,"type":3998}," Catalog, quality, lineage, identity, ticketing, and reporting tools exchange the context required by users.",[1511,4369,4371,4373],{"className":4370},[3994],[3996,4372],{"disabled":27,"type":3998}," Business users can find definitions, owners, quality status, and access guidance without specialist support.",[1511,4375,4377,4379],{"className":4376},[3994],[3996,4378],{"disabled":27,"type":3998}," Training and communications are tailored to Data Owners, Stewards, engineers, analysts, and executives.",[1511,4381,4383,4385],{"className":4382},[3994],[3996,4384],{"disabled":27,"type":3998}," Adoption is measured through usage, workflow completion, response times, and stakeholder feedback.",[941,4387,4388],{},[1784,4389,4022],{},[1508,4391,4392,4395],{},[1511,4393,4394],{},"Use-case and integration architecture",[1511,4396,4397],{},"Role-based training plan and adoption metrics",[953,4399,4401],{"id":4400},"build-the-90-day-improvement-backlog","Build the 90-day improvement backlog",[941,4403,4404],{},"For every item rated missing, unclear, or partially established, record business impact, risk, accountable owner, dependency, target date, required evidence, and the first executable action. Prioritise controls that reduce multiple risks or unblock other controls.",[3354,4406,4407,4432],{},[3357,4408,4409],{},[3360,4410,4411,4414,4417,4420,4423,4426,4429],{},[3363,4412,4413],{},"Priority",[3363,4415,4416],{},"Gap",[3363,4418,4419],{},"Business impact \u002F risk",[3363,4421,4422],{},"Owner",[3363,4424,4425],{},"First action",[3363,4427,4428],{},"Target date",[3363,4430,4431],{},"Evidence",[3373,4433,4434,4451,4468,4485,4502],{},[3360,4435,4436,4439,4441,4443,4445,4447,4449],{},[3378,4437,4438],{},"1",[3378,4440],{},[3378,4442],{},[3378,4444],{},[3378,4446],{},[3378,4448],{},[3378,4450],{},[3360,4452,4453,4456,4458,4460,4462,4464,4466],{},[3378,4454,4455],{},"2",[3378,4457],{},[3378,4459],{},[3378,4461],{},[3378,4463],{},[3378,4465],{},[3378,4467],{},[3360,4469,4470,4473,4475,4477,4479,4481,4483],{},[3378,4471,4472],{},"3",[3378,4474],{},[3378,4476],{},[3378,4478],{},[3378,4480],{},[3378,4482],{},[3378,4484],{},[3360,4486,4487,4490,4492,4494,4496,4498,4500],{},[3378,4488,4489],{},"4",[3378,4491],{},[3378,4493],{},[3378,4495],{},[3378,4497],{},[3378,4499],{},[3378,4501],{},[3360,4503,4504,4507,4509,4511,4513,4515,4517],{},[3378,4505,4506],{},"5",[3378,4508],{},[3378,4510],{},[3378,4512],{},[3378,4514],{},[3378,4516],{},[3378,4518],{},{"title":771,"searchDepth":991,"depth":991,"links":4520},[4521,4522,4523,4524,4525,4526,4527,4528,4529,4530],{"id":3925,"depth":991,"text":3926},{"id":3982,"depth":991,"text":3983},{"id":4036,"depth":991,"text":4037},{"id":4082,"depth":991,"text":4083},{"id":4137,"depth":991,"text":4138},{"id":4192,"depth":991,"text":4193},{"id":4244,"depth":991,"text":4245},{"id":4296,"depth":991,"text":4297},{"id":4348,"depth":991,"text":4349},{"id":4400,"depth":991,"text":4401},"checklist","Get the checklist","Interactive HTML checklist","Verify whether ownership, metadata, data-quality controls, lifecycle rules, access responsibilities, and governance KPIs are defined before expanding governance tooling.","data-governance-maturity-checklist.html","Download checklist","\u002Fdownloads\u002Fen\u002Fdata-governance-maturity-checklist.html","Exclusive",[4540,4541,4542,4543],"A control inventory across ownership, stewardship, metadata, quality, lifecycle, access, policy, and adoption.","Evidence prompts that distinguish documented governance from informal practice.","A practical prioritisation method for a 90-day improvement backlog.","Inputs for governance KPIs, audit preparation, and tooling decisions.",{"tags":4545},[100,4546,4531],"readiness","\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fdata-governance-maturity-checklist","checklists","12 min read","Checklist",{"title":3908,"description":4534},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fdata-governance-maturity-checklist",[3916,3922],"HoG--M-Ztul9Ngz2j2sR3-cBq_YVzVPuea7TiZeuYdA",{"id":4556,"title":4557,"assessmentSlug":934,"associatedSolution":97,"authors":934,"body":4558,"category":4531,"ctaLabel":4532,"date":1442,"dateModified":1442,"deliveryFormat":4533,"description":5007,"downloadFileName":5008,"downloadLabel":4536,"downloadUrl":5009,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":23,"format":4531,"gated":27,"healthCheckSlug":934,"keyTakeaways":5010,"meta":5015,"navigation":27,"newsletterTopic":1452,"path":5017,"publicType":4548,"published":27,"readTime":3785,"resourceType":4550,"schemaType":1457,"seo":5018,"slug":4562,"stem":5019,"teaser":5020,"type":4531,"__hash__":5021},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fdata-modeling-standards-starter-checklist.md","Data Modeling Standards Starter Checklist",{"type":938,"value":4559,"toc":4997},[4560,4563,4566,4571,4573,4615,4619,4622,4649,4653,4661,4665,4668,4695,4699,4707,4711,4714,4741,4745,4753,4757,4760,4787,4791,4799,4803,4806,4833,4837,4845,4849,4852,4879,4883,4891,4893,4895],[1433,4561,4557],{"id":4562},"data-modeling-standards-starter-checklist",[941,4564,4565],{},"Use the checklist to establish a minimum viable modeling standard that teams can apply consistently. It is suitable for new governance programmes, tool migrations, or consolidation of independently maintained models.",[3918,4567,4568],{},[941,4569,4570],{},"Decide which rules are mandatory, recommended, or domain-specific, then identify the repository and review workflow that make them enforceable.",[953,4572,3926],{"id":3925},[3354,4574,4575,4583],{},[3357,4576,4577],{},[3360,4578,4579,4581],{},[3363,4580,1159],{},[3363,4582,3937],{},[3373,4584,4585,4591,4597,4603,4609],{},[3360,4586,4587,4589],{},[3378,4588,3944],{},[3378,4590,3947],{},[3360,4592,4593,4595],{},[3378,4594,3952],{},[3378,4596,3955],{},[3360,4598,4599,4601],{},[3378,4600,3960],{},[3378,4602,3963],{},[3360,4604,4605,4607],{},[3378,4606,3968],{},[3378,4608,3971],{},[3360,4610,4611,4613],{},[3378,4612,3976],{},[3378,4614,3979],{},[953,4616,4618],{"id":4617},"_1-scope-and-model-layers","1. Scope and model layers",[941,4620,4621],{},"Clarify what each model type is expected to communicate.",[1508,4623,4625,4631,4637,4643],{"className":4624},[3990],[1511,4626,4628,4630],{"className":4627},[3994],[3996,4629],{"disabled":27,"type":3998}," Conceptual, logical, and physical model purposes and audiences are defined.",[1511,4632,4634,4636],{"className":4633},[3994],[3996,4635],{"disabled":27,"type":3998}," Domain, system, integration, analytics, and data-product boundaries are explicit.",[1511,4638,4640,4642],{"className":4639},[3994],[3996,4641],{"disabled":27,"type":3998}," Required detail and abstraction levels are defined for each lifecycle stage.",[1511,4644,4646,4648],{"className":4645},[3994],[3996,4647],{"disabled":27,"type":3998}," Source-of-truth repositories and model ownership are assigned.",[941,4650,4651],{},[1784,4652,4022],{},[1508,4654,4655,4658],{},[1511,4656,4657],{},"Model taxonomy",[1511,4659,4660],{},"Repository and ownership map",[953,4662,4664],{"id":4663},"_2-naming-and-definitions","2. Naming and definitions",[941,4666,4667],{},"Make model elements consistent and understandable across teams.",[1508,4669,4671,4677,4683,4689],{"className":4670},[3990],[1511,4672,4674,4676],{"className":4673},[3994],[3996,4675],{"disabled":27,"type":3998}," Entity, attribute, relationship, table, column, key, and constraint naming conventions are documented.",[1511,4678,4680,4682],{"className":4679},[3994],[3996,4681],{"disabled":27,"type":3998}," Business terms and technical names are connected without forcing one vocabulary into every layer.",[1511,4684,4686,4688],{"className":4685},[3994],[3996,4687],{"disabled":27,"type":3998}," Abbreviations, reserved words, language, casing, singular\u002Fplural, and length rules are defined.",[1511,4690,4692,4694],{"className":4691},[3994],[3996,4693],{"disabled":27,"type":3998}," Every important model element has a meaningful definition and accountable owner.",[941,4696,4697],{},[1784,4698,4022],{},[1508,4700,4701,4704],{},[1511,4702,4703],{},"Naming standard",[1511,4705,4706],{},"Glossary linkage rules",[953,4708,4710],{"id":4709},"_3-notation-keys-and-relationships","3. Notation, keys, and relationships",[941,4712,4713],{},"Standardise structural decisions and their representation.",[1508,4715,4717,4723,4729,4735],{"className":4716},[3990],[1511,4718,4720,4722],{"className":4719},[3994],[3996,4721],{"disabled":27,"type":3998}," Notation, cardinality, optionality, identifying relationships, and subtype conventions are chosen.",[1511,4724,4726,4728],{"className":4725},[3994],[3996,4727],{"disabled":27,"type":3998}," Natural, surrogate, business, primary, and foreign key guidance is documented.",[1511,4730,4732,4734],{"className":4731},[3994],[3996,4733],{"disabled":27,"type":3998}," Reference data, master data, history, slowly changing dimensions, and temporal validity patterns are defined where relevant.",[1511,4736,4738,4740],{"className":4737},[3994],[3996,4739],{"disabled":27,"type":3998}," Normalization and denormalization decisions require stated purpose and trade-offs.",[941,4742,4743],{},[1784,4744,4022],{},[1508,4746,4747,4750],{},[1511,4748,4749],{},"Notation guide",[1511,4751,4752],{},"Approved modeling patterns",[953,4754,4756],{"id":4755},"_4-metadata-lineage-and-quality","4. Metadata, lineage, and quality",[941,4758,4759],{},"Attach the context required for implementation, governance, and impact analysis.",[1508,4761,4763,4769,4775,4781],{"className":4762},[3990],[1511,4764,4766,4768],{"className":4765},[3994],[3996,4767],{"disabled":27,"type":3998}," Models capture business owner, technical owner, domain, source, sensitivity, lifecycle, and quality expectations.",[1511,4770,4772,4774],{"className":4771},[3994],[3996,4773],{"disabled":27,"type":3998}," Lineage links model elements to sources, transformations, interfaces, reports, and consuming products.",[1511,4776,4778,4780],{"className":4777},[3994],[3996,4779],{"disabled":27,"type":3998}," Critical data elements and quality rules are referenced consistently.",[1511,4782,4784,4786],{"className":4783},[3994],[3996,4785],{"disabled":27,"type":3998}," Metadata completeness and stale models are measurable.",[941,4788,4789],{},[1784,4790,4022],{},[1508,4792,4793,4796],{},[1511,4794,4795],{},"Required metadata profile",[1511,4797,4798],{},"Lineage integration design",[953,4800,4802],{"id":4801},"_5-review-approval-and-versioning","5. Review, approval, and versioning",[941,4804,4805],{},"Create traceable controls without blocking delivery.",[1508,4807,4809,4815,4821,4827],{"className":4808},[3990],[1511,4810,4812,4814],{"className":4811},[3994],[3996,4813],{"disabled":27,"type":3998}," Review criteria cover semantics, structure, security, privacy, quality, performance, integration, and standards compliance.",[1511,4816,4818,4820],{"className":4817},[3994],[3996,4819],{"disabled":27,"type":3998}," Reviewers and approval authority are defined by model type and impact.",[1511,4822,4824,4826],{"className":4823},[3994],[3996,4825],{"disabled":27,"type":3998}," Versions, branches, baselines, change descriptions, and release tags follow a documented workflow.",[1511,4828,4830,4832],{"className":4829},[3994],[3996,4831],{"disabled":27,"type":3998}," Exceptions have rationale, owner, approval, expiry, and remediation decision.",[941,4834,4835],{},[1784,4836,4022],{},[1508,4838,4839,4842],{},[1511,4840,4841],{},"Review checklist",[1511,4843,4844],{},"Version and exception workflow",[953,4846,4848],{"id":4847},"_6-engineering-handover-and-reuse","6. Engineering handover and reuse",[941,4850,4851],{},"Ensure approved models remain usable through implementation and change.",[1508,4853,4855,4861,4867,4873],{"className":4854},[3990],[1511,4856,4858,4860],{"className":4857},[3994],[3996,4859],{"disabled":27,"type":3998}," Handover packages include approved model, definitions, constraints, mappings, quality rules, security requirements, and open decisions.",[1511,4862,4864,4866],{"className":4863},[3994],[3996,4865],{"disabled":27,"type":3998}," Generated DDL or code is reviewed and reconciled with deployed structures.",[1511,4868,4870,4872],{"className":4869},[3994],[3996,4871],{"disabled":27,"type":3998}," Reusable patterns and shared models have owners, compatibility rules, and change notification.",[1511,4874,4876,4878],{"className":4875},[3994],[3996,4877],{"disabled":27,"type":3998}," Model drift between repository and production is detected and resolved.",[941,4880,4881],{},[1784,4882,4022],{},[1508,4884,4885,4888],{},[1511,4886,4887],{},"Handover template",[1511,4889,4890],{},"Model drift report",[953,4892,4401],{"id":4400},[941,4894,4404],{},[3354,4896,4897,4915],{},[3357,4898,4899],{},[3360,4900,4901,4903,4905,4907,4909,4911,4913],{},[3363,4902,4413],{},[3363,4904,4416],{},[3363,4906,4419],{},[3363,4908,4422],{},[3363,4910,4425],{},[3363,4912,4428],{},[3363,4914,4431],{},[3373,4916,4917,4933,4949,4965,4981],{},[3360,4918,4919,4921,4923,4925,4927,4929,4931],{},[3378,4920,4438],{},[3378,4922],{},[3378,4924],{},[3378,4926],{},[3378,4928],{},[3378,4930],{},[3378,4932],{},[3360,4934,4935,4937,4939,4941,4943,4945,4947],{},[3378,4936,4455],{},[3378,4938],{},[3378,4940],{},[3378,4942],{},[3378,4944],{},[3378,4946],{},[3378,4948],{},[3360,4950,4951,4953,4955,4957,4959,4961,4963],{},[3378,4952,4472],{},[3378,4954],{},[3378,4956],{},[3378,4958],{},[3378,4960],{},[3378,4962],{},[3378,4964],{},[3360,4966,4967,4969,4971,4973,4975,4977,4979],{},[3378,4968,4489],{},[3378,4970],{},[3378,4972],{},[3378,4974],{},[3378,4976],{},[3378,4978],{},[3378,4980],{},[3360,4982,4983,4985,4987,4989,4991,4993,4995],{},[3378,4984,4506],{},[3378,4986],{},[3378,4988],{},[3378,4990],{},[3378,4992],{},[3378,4994],{},[3378,4996],{},{"title":771,"searchDepth":991,"depth":991,"links":4998},[4999,5000,5001,5002,5003,5004,5005,5006],{"id":3925,"depth":991,"text":3926},{"id":4617,"depth":991,"text":4618},{"id":4663,"depth":991,"text":4664},{"id":4709,"depth":991,"text":4710},{"id":4755,"depth":991,"text":4756},{"id":4801,"depth":991,"text":4802},{"id":4847,"depth":991,"text":4848},{"id":4400,"depth":991,"text":4401},"Define naming, model layers, notation, review, versioning, metadata, lineage, reuse, and engineering handover before models diverge across teams.","data-modeling-standards-starter-checklist.html","\u002Fdownloads\u002Fen\u002Fdata-modeling-standards-starter-checklist.html",[5011,5012,5013,5014],"A starter standard for conceptual, logical, and physical models.","Naming, notation, metadata, and lineage decisions.","Review, approval, versioning, and exception controls.","Clear handover expectations for engineering and analytics teams.",{"tags":5016},[97,4546,4531],"\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fdata-modeling-standards-starter-checklist",{"title":4557,"description":5007},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fdata-modeling-standards-starter-checklist",[4565,4570],"x-wa072hjm_GNVz02xRQeN2pdZY7KLmGDMr-oBiPbAA",{"id":5023,"title":5024,"assessmentSlug":934,"associatedSolution":82,"authors":934,"body":5025,"category":4531,"ctaLabel":5580,"date":1442,"dateModified":1442,"deliveryFormat":4533,"description":5581,"downloadFileName":5582,"downloadLabel":5583,"downloadUrl":5584,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":27,"format":5585,"gated":27,"healthCheckSlug":5029,"keyTakeaways":5586,"meta":5591,"navigation":27,"newsletterTopic":5593,"path":5594,"publicType":4548,"published":27,"readTime":4549,"resourceType":5595,"schemaType":1457,"seo":5596,"slug":5029,"stem":5597,"teaser":5598,"type":5585,"__hash__":5599},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fenterprise-observability-health-check.md","Enterprise Observability Health Check",{"type":938,"value":5026,"toc":5568},[5027,5030,5033,5038,5040,5082,5086,5089,5116,5120,5128,5132,5135,5162,5166,5174,5178,5181,5214,5218,5226,5230,5233,5266,5270,5278,5282,5285,5312,5316,5324,5328,5331,5358,5362,5370,5374,5377,5404,5408,5416,5420,5423,5450,5454,5462,5464,5466],[1433,5028,5024],{"id":5029},"enterprise-observability-health-check",[941,5031,5032],{},"Run the health check with service owners, operations, platform engineering, application teams, database teams, security, and incident management. The goal is to identify blind spots and operating weaknesses—not to count monitoring tools.",[3918,5034,5035],{},[941,5036,5037],{},"Rate each item using observable evidence from the last three months. Where teams disagree, record the disagreement as a gap and assign an owner to resolve it.",[953,5039,3926],{"id":3925},[3354,5041,5042,5050],{},[3357,5043,5044],{},[3360,5045,5046,5048],{},[3363,5047,1159],{},[3363,5049,3937],{},[3373,5051,5052,5058,5064,5070,5076],{},[3360,5053,5054,5056],{},[3378,5055,3944],{},[3378,5057,3947],{},[3360,5059,5060,5062],{},[3378,5061,3952],{},[3378,5063,3955],{},[3360,5065,5066,5068],{},[3378,5067,3960],{},[3378,5069,3963],{},[3360,5071,5072,5074],{},[3378,5073,3968],{},[3378,5075,3971],{},[3360,5077,5078,5080],{},[3378,5079,3976],{},[3378,5081,3979],{},[953,5083,5085],{"id":5084},"_1-infrastructure-visibility","1. Infrastructure visibility",[941,5087,5088],{},"Confirm consistent coverage of compute, network, storage, cloud, containers, and platform services.",[1508,5090,5092,5098,5104,5110],{"className":5091},[3990],[1511,5093,5095,5097],{"className":5094},[3994],[3996,5096],{"disabled":27,"type":3998}," Critical on-premises, cloud, virtual, container, and managed-service infrastructure is inventoried and monitored.",[1511,5099,5101,5103],{"className":5100},[3994],[3996,5102],{"disabled":27,"type":3998}," Availability, saturation, errors, and capacity signals are collected at an actionable resolution.",[1511,5105,5107,5109],{"className":5106},[3994],[3996,5108],{"disabled":27,"type":3998}," Monitoring detects collection failures and stale targets instead of treating missing telemetry as healthy.",[1511,5111,5113,5115],{"className":5112},[3994],[3996,5114],{"disabled":27,"type":3998}," Infrastructure ownership and support contacts are attached to monitored assets.",[941,5117,5118],{},[1784,5119,4022],{},[1508,5121,5122,5125],{},[1511,5123,5124],{},"Coverage report by environment and criticality",[1511,5126,5127],{},"Collector health dashboard",[953,5129,5131],{"id":5130},"_2-application-and-database-visibility","2. Application and database visibility",[941,5133,5134],{},"Check whether teams can connect user symptoms to application and database behavior.",[1508,5136,5138,5144,5150,5156],{"className":5137},[3990],[1511,5139,5141,5143],{"className":5140},[3994],[3996,5142],{"disabled":27,"type":3998}," Critical applications expose health, latency, throughput, error, and dependency signals.",[1511,5145,5147,5149],{"className":5146},[3994],[3996,5148],{"disabled":27,"type":3998}," Database monitoring covers availability, waits, locks, slow queries, resource pressure, replication, and backup health.",[1511,5151,5153,5155],{"className":5152},[3994],[3996,5154],{"disabled":27,"type":3998}," Deployment and configuration changes are visible alongside performance data.",[1511,5157,5159,5161],{"className":5158},[3994],[3996,5160],{"disabled":27,"type":3998}," Synthetic or real-user checks cover critical customer and employee journeys.",[941,5163,5164],{},[1784,5165,4022],{},[1508,5167,5168,5171],{},[1511,5169,5170],{},"Service-level dashboard",[1511,5172,5173],{},"Database diagnostic coverage matrix",[953,5175,5177],{"id":5176},"_3-logs-metrics-and-traces","3. Logs, metrics, and traces",[941,5179,5180],{},"Assess telemetry completeness, consistency, retention, and correlation.",[1508,5182,5184,5190,5196,5202,5208],{"className":5183},[3990],[1511,5185,5187,5189],{"className":5186},[3994],[3996,5188],{"disabled":27,"type":3998}," Logs from critical services, platforms, security controls, and dependencies are centrally searchable.",[1511,5191,5193,5195],{"className":5192},[3994],[3996,5194],{"disabled":27,"type":3998}," Metrics use documented names, labels, units, and cardinality controls.",[1511,5197,5199,5201],{"className":5198},[3994],[3996,5200],{"disabled":27,"type":3998}," Distributed traces cover priority transaction paths and propagate context across service boundaries.",[1511,5203,5205,5207],{"className":5204},[3994],[3996,5206],{"disabled":27,"type":3998}," Correlation identifiers connect logs, metrics, traces, deployments, and incidents where practical.",[1511,5209,5211,5213],{"className":5210},[3994],[3996,5212],{"disabled":27,"type":3998}," Retention and sampling balance troubleshooting, compliance, performance, and cost requirements.",[941,5215,5216],{},[1784,5217,4022],{},[1508,5219,5220,5223],{},[1511,5221,5222],{},"Telemetry standards",[1511,5224,5225],{},"Retention and sampling decisions",[953,5227,5229],{"id":5228},"_4-alert-quality-and-alert-fatigue","4. Alert quality and alert fatigue",[941,5231,5232],{},"Determine whether alerts drive timely action without overwhelming responders.",[1508,5234,5236,5242,5248,5254,5260],{"className":5235},[3990],[1511,5237,5239,5241],{"className":5238},[3994],[3996,5240],{"disabled":27,"type":3998}," Every paging alert has a clear condition, owner, severity, response expectation, and runbook.",[1511,5243,5245,5247],{"className":5244},[3994],[3996,5246],{"disabled":27,"type":3998}," Alerts reflect service or user impact where possible rather than only low-level thresholds.",[1511,5249,5251,5253],{"className":5250},[3994],[3996,5252],{"disabled":27,"type":3998}," Duplicate, flapping, stale, and unactionable alerts are measured and removed on a regular cadence.",[1511,5255,5257,5259],{"className":5256},[3994],[3996,5258],{"disabled":27,"type":3998}," Routing, schedules, escalation, and fallback contacts are tested before incidents occur.",[1511,5261,5263,5265],{"className":5262},[3994],[3996,5264],{"disabled":27,"type":3998}," Alert load, acknowledgement time, and after-hours noise are reported by service and team.",[941,5267,5268],{},[1784,5269,4022],{},[1508,5271,5272,5275],{},[1511,5273,5274],{},"Alert inventory and hygiene report",[1511,5276,5277],{},"On-call load metrics",[953,5279,5281],{"id":5280},"_5-ownership-and-service-dependencies","5. Ownership and service dependencies",[941,5283,5284],{},"Check whether responders know who owns a service and what depends on it.",[1508,5286,5288,5294,5300,5306],{"className":5287},[3990],[1511,5289,5291,5293],{"className":5290},[3994],[3996,5292],{"disabled":27,"type":3998}," Each critical service has a named business owner, technical owner, and operational support group.",[1511,5295,5297,5299],{"className":5296},[3994],[3996,5298],{"disabled":27,"type":3998}," Service dependencies include upstream, downstream, external, network, database, and identity components.",[1511,5301,5303,5305],{"className":5302},[3994],[3996,5304],{"disabled":27,"type":3998}," Dependency maps are updated from reliable sources and validated during incidents or changes.",[1511,5307,5309,5311],{"className":5308},[3994],[3996,5310],{"disabled":27,"type":3998}," Business criticality, support hours, recovery objectives, and maintenance windows are available to responders.",[941,5313,5314],{},[1784,5315,4022],{},[1508,5317,5318,5321],{},[1511,5319,5320],{},"Service catalog and ownership register",[1511,5322,5323],{},"Dependency map with freshness indicator",[953,5325,5327],{"id":5326},"_6-incident-response-and-runbooks","6. Incident response and runbooks",[941,5329,5330],{},"Verify that monitoring information supports repeatable diagnosis, communication, and recovery.",[1508,5332,5334,5340,5346,5352],{"className":5333},[3990],[1511,5335,5337,5339],{"className":5336},[3994],[3996,5338],{"disabled":27,"type":3998}," Major-incident roles, communication channels, severity criteria, and escalation rules are documented and exercised.",[1511,5341,5343,5345],{"className":5342},[3994],[3996,5344],{"disabled":27,"type":3998}," Runbooks cover diagnosis, safe mitigation, validation, rollback, and escalation for common failure modes.",[1511,5347,5349,5351],{"className":5348},[3994],[3996,5350],{"disabled":27,"type":3998}," Responders can access dashboards, logs, traces, changes, and dependency context without changing tools repeatedly.",[1511,5353,5355,5357],{"className":5354},[3994],[3996,5356],{"disabled":27,"type":3998}," Post-incident actions update alerts, dashboards, runbooks, automation, and service design.",[941,5359,5360],{},[1784,5361,4022],{},[1508,5363,5364,5367],{},[1511,5365,5366],{},"Incident procedure and exercise records",[1511,5368,5369],{},"Runbook ownership and review dates",[953,5371,5373],{"id":5372},"_7-monitoring-gaps-and-capacity-planning","7. Monitoring gaps and capacity planning",[941,5375,5376],{},"Make blind spots and future resource constraints visible before they become incidents.",[1508,5378,5380,5386,5392,5398],{"className":5379},[3990],[1511,5381,5383,5385],{"className":5382},[3994],[3996,5384],{"disabled":27,"type":3998}," Coverage gaps are recorded by service, signal type, risk, owner, and target date.",[1511,5387,5389,5391],{"className":5388},[3994],[3996,5390],{"disabled":27,"type":3998}," New services and major changes include observability acceptance criteria before production approval.",[1511,5393,5395,5397],{"className":5394},[3994],[3996,5396],{"disabled":27,"type":3998}," Capacity forecasts consider growth, seasonality, batch windows, failover, and planned business events.",[1511,5399,5401,5403],{"className":5400},[3994],[3996,5402],{"disabled":27,"type":3998}," Resource saturation and cost trends trigger planned action before hard limits are reached.",[941,5405,5406],{},[1784,5407,4022],{},[1508,5409,5410,5413],{},[1511,5411,5412],{},"Risk-ranked monitoring gap register",[1511,5414,5415],{},"Capacity forecast and action plan",[953,5417,5419],{"id":5418},"_8-reporting-and-operational-governance","8. Reporting and operational governance",[941,5421,5422],{},"Ensure observability performance is measured and platform decisions have accountable governance.",[1508,5424,5426,5432,5438,5444],{"className":5425},[3990],[1511,5427,5429,5431],{"className":5428},[3994],[3996,5430],{"disabled":27,"type":3998}," Reports distinguish service outcomes, monitoring coverage, platform health, incident performance, and telemetry cost.",[1511,5433,5435,5437],{"className":5434},[3994],[3996,5436],{"disabled":27,"type":3998}," Service-level indicators and objectives are agreed with business stakeholders for priority services.",[1511,5439,5441,5443],{"className":5440},[3994],[3996,5442],{"disabled":27,"type":3998}," Telemetry standards, platform guardrails, exceptions, and ownership are documented.",[1511,5445,5447,5449],{"className":5446},[3994],[3996,5448],{"disabled":27,"type":3998}," Observability improvements are prioritised against risk and operational outcomes, not tool adoption alone.",[941,5451,5452],{},[1784,5453,4022],{},[1508,5455,5456,5459],{},[1511,5457,5458],{},"Operational scorecard",[1511,5460,5461],{},"Platform decision and exception log",[953,5463,4401],{"id":4400},[941,5465,4404],{},[3354,5467,5468,5486],{},[3357,5469,5470],{},[3360,5471,5472,5474,5476,5478,5480,5482,5484],{},[3363,5473,4413],{},[3363,5475,4416],{},[3363,5477,4419],{},[3363,5479,4422],{},[3363,5481,4425],{},[3363,5483,4428],{},[3363,5485,4431],{},[3373,5487,5488,5504,5520,5536,5552],{},[3360,5489,5490,5492,5494,5496,5498,5500,5502],{},[3378,5491,4438],{},[3378,5493],{},[3378,5495],{},[3378,5497],{},[3378,5499],{},[3378,5501],{},[3378,5503],{},[3360,5505,5506,5508,5510,5512,5514,5516,5518],{},[3378,5507,4455],{},[3378,5509],{},[3378,5511],{},[3378,5513],{},[3378,5515],{},[3378,5517],{},[3378,5519],{},[3360,5521,5522,5524,5526,5528,5530,5532,5534],{},[3378,5523,4472],{},[3378,5525],{},[3378,5527],{},[3378,5529],{},[3378,5531],{},[3378,5533],{},[3378,5535],{},[3360,5537,5538,5540,5542,5544,5546,5548,5550],{},[3378,5539,4489],{},[3378,5541],{},[3378,5543],{},[3378,5545],{},[3378,5547],{},[3378,5549],{},[3378,5551],{},[3360,5553,5554,5556,5558,5560,5562,5564,5566],{},[3378,5555,4506],{},[3378,5557],{},[3378,5559],{},[3378,5561],{},[3378,5563],{},[3378,5565],{},[3378,5567],{},{"title":771,"searchDepth":991,"depth":991,"links":5569},[5570,5571,5572,5573,5574,5575,5576,5577,5578,5579],{"id":3925,"depth":991,"text":3926},{"id":5084,"depth":991,"text":5085},{"id":5130,"depth":991,"text":5131},{"id":5176,"depth":991,"text":5177},{"id":5228,"depth":991,"text":5229},{"id":5280,"depth":991,"text":5281},{"id":5326,"depth":991,"text":5327},{"id":5372,"depth":991,"text":5373},{"id":5418,"depth":991,"text":5419},{"id":4400,"depth":991,"text":4401},"Get the health check","Evaluate infrastructure, application, database, log, metric, trace, alerting, ownership, incident-response, dependency, capacity, and reporting coverage.","enterprise-observability-health-check.html","Download health check","\u002Fdownloads\u002Fen\u002Fenterprise-observability-health-check.html","health-check",[5587,5588,5589,5590],"A coverage review spanning infrastructure, applications, databases, logs, metrics, and traces.","Checks for alert quality, fatigue, routing, ownership, and incident response.","Evidence prompts for service dependencies, runbooks, capacity planning, and reporting.","A prioritised monitoring-gap backlog for the next 90 days.",{"tags":5592},[82,4546,5585],"observabilityMonitoring","\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fenterprise-observability-health-check","Health Check",{"title":5024,"description":5581},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fenterprise-observability-health-check",[5032,5037],"LAW1Qx4oMDvXETsbA3K80aSgjEgDZrLfDRUKb2pQtgQ",{"id":5601,"title":5602,"assessmentSlug":934,"associatedSolution":94,"authors":934,"body":5603,"category":4531,"ctaLabel":4532,"date":6156,"dateModified":6156,"deliveryFormat":4533,"description":6157,"downloadFileName":6158,"downloadLabel":4536,"downloadUrl":6159,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":23,"format":4531,"gated":27,"healthCheckSlug":934,"keyTakeaways":6160,"meta":6165,"navigation":27,"newsletterTopic":1478,"path":6168,"publicType":4548,"published":27,"readTime":4549,"resourceType":4550,"schemaType":1457,"seo":6169,"slug":5607,"stem":6170,"teaser":6171,"type":4531,"__hash__":6172},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fitsm-readiness-checklist.md","ITSM Readiness Checklist",{"type":938,"value":5604,"toc":6144},[5605,5608,5611,5616,5618,5662,5666,5669,5696,5700,5708,5712,5715,5742,5746,5754,5758,5761,5794,5798,5806,5810,5813,5840,5844,5852,5856,5859,5886,5890,5898,5902,5905,5932,5936,5944,5948,5951,5978,5982,5990,5994,5997,6024,6028,6036,6038,6041],[1433,5606,5602],{"id":5607},"itsm-readiness-checklist",[941,5609,5610],{},"Use the checklist to evaluate IT service management through clear ownership, repeatable practices, and defensible evidence rather than tool availability alone.",[3918,5612,5613],{},[941,5614,5615],{},"Score each item against the process people actually follow. A configured feature is not yet an established control or service practice.",[953,5617,3926],{"id":3925},[3354,5619,5620,5628],{},[3357,5621,5622],{},[3360,5623,5624,5626],{},[3363,5625,1159],{},[3363,5627,3937],{},[3373,5629,5630,5636,5642,5649,5656],{},[3360,5631,5632,5634],{},[3378,5633,3944],{},[3378,5635,3947],{},[3360,5637,5638,5640],{},[3378,5639,3952],{},[3378,5641,3955],{},[3360,5643,5644,5646],{},[3378,5645,3960],{},[3378,5647,5648],{},"Approved work exists but the practice is not operational",[3360,5650,5651,5653],{},[3378,5652,3968],{},[3378,5654,5655],{},"No reliable practice or owner exists",[3360,5657,5658,5660],{},[3378,5659,3976],{},[3378,5661,3979],{},[953,5663,5665],{"id":5664},"_1-service-scope-and-ownership","1. Service scope and ownership",[941,5667,5668],{},"Define what the service organization supports and who is accountable for decisions.",[1508,5670,5672,5678,5684,5690],{"className":5671},[3990],[1511,5673,5675,5677],{"className":5674},[3994],[3996,5676],{"disabled":27,"type":3998}," Business-facing IT services, user groups, service hours, dependencies, and support boundaries are documented.",[1511,5679,5681,5683],{"className":5680},[3994],[3996,5682],{"disabled":27,"type":3998}," Every service has a business owner, service owner, support group, and escalation path.",[1511,5685,5687,5689],{"className":5686},[3994],[3996,5688],{"disabled":27,"type":3998}," Roles for the service desk, specialist teams, suppliers, and change authority are explicit.",[1511,5691,5693,5695],{"className":5692},[3994],[3996,5694],{"disabled":27,"type":3998}," Policies and workflows have named owners and scheduled review dates.",[941,5697,5698],{},[1784,5699,4022],{},[1508,5701,5702,5705],{},[1511,5703,5704],{},"Service portfolio and ownership matrix",[1511,5706,5707],{},"RACI and review calendar",[953,5709,5711],{"id":5710},"_2-demand-intake-and-service-catalogue","2. Demand, intake, and service catalogue",[941,5713,5714],{},"Create predictable access to support and fulfilment without losing context between channels.",[1508,5716,5718,5724,5730,5736],{"className":5717},[3990],[1511,5719,5721,5723],{"className":5720},[3994],[3996,5722],{"disabled":27,"type":3998}," Approved portal, email, phone, and chat channels feed a single authoritative system of record.",[1511,5725,5727,5729],{"className":5726},[3994],[3996,5728],{"disabled":27,"type":3998}," Categories and forms capture the minimum information needed to route, prioritise, and fulfil work.",[1511,5731,5733,5735],{"className":5732},[3994],[3996,5734],{"disabled":27,"type":3998}," The service catalogue uses language users understand and states eligibility, approvals, fulfilment steps, and expected timeframes.",[1511,5737,5739,5741],{"className":5738},[3994],[3996,5740],{"disabled":27,"type":3998}," Routing and assignment rules have exception queues, ageing controls, and named queue owners.",[941,5743,5744],{},[1784,5745,4022],{},[1508,5747,5748,5751],{},[1511,5749,5750],{},"Channel and intake map",[1511,5752,5753],{},"Service catalogue and routing rules",[953,5755,5757],{"id":5756},"_3-incident-request-problem-and-change-practices","3. Incident, request, problem, and change practices",[941,5759,5760],{},"Keep the core practices distinct while preserving a useful flow of context between them.",[1508,5762,5764,5770,5776,5782,5788],{"className":5763},[3990],[1511,5765,5767,5769],{"className":5766},[3994],[3996,5768],{"disabled":27,"type":3998}," Incidents, service requests, problems, and changes use distinct definitions, workflows, and closure criteria.",[1511,5771,5773,5775],{"className":5772},[3994],[3996,5774],{"disabled":27,"type":3998}," Incident priority combines impact and urgency, with a tested major-incident process and communication model.",[1511,5777,5779,5781],{"className":5778},[3994],[3996,5780],{"disabled":27,"type":3998}," Common requests use repeatable fulfilment workflows with clear approvals, tasks, and completion evidence.",[1511,5783,5785,5787],{"className":5784},[3994],[3996,5786],{"disabled":27,"type":3998}," Recurring or high-impact incidents trigger problem investigation, known-error documentation, and tracked corrective action.",[1511,5789,5791,5793],{"className":5790},[3994],[3996,5792],{"disabled":27,"type":3998}," Standard, normal, and emergency changes have proportionate risk checks, approvals, testing, scheduling, and rollback criteria.",[941,5795,5796],{},[1784,5797,4022],{},[1508,5799,5800,5803],{},[1511,5801,5802],{},"Process definitions and workflow diagrams",[1511,5804,5805],{},"Major-incident and change records",[953,5807,5809],{"id":5808},"_4-service-levels-prioritisation-and-escalation","4. Service levels, prioritisation, and escalation",[941,5811,5812],{},"Make commitments measurable and ensure breaches trigger action rather than retrospective reporting.",[1508,5814,5816,5822,5828,5834],{"className":5815},[3990],[1511,5817,5819,5821],{"className":5818},[3994],[3996,5820],{"disabled":27,"type":3998}," Response and resolution targets reflect service criticality, support hours, request type, and agreed dependencies.",[1511,5823,5825,5827],{"className":5824},[3994],[3996,5826],{"disabled":27,"type":3998}," Priority rules, pause conditions, reassignment, and target calculations are consistently implemented and understood.",[1511,5829,5831,5833],{"className":5830},[3994],[3996,5832],{"disabled":27,"type":3998}," Warning thresholds and functional or hierarchical escalations activate before commitments are missed.",[1511,5835,5837,5839],{"className":5836},[3994],[3996,5838],{"disabled":27,"type":3998}," Supplier and internal team commitments support the end-to-end service levels communicated to users.",[941,5841,5842],{},[1784,5843,4022],{},[1508,5845,5846,5849],{},[1511,5847,5848],{},"Service-level model and priority matrix",[1511,5850,5851],{},"Escalation rules and breach review",[953,5853,5855],{"id":5854},"_5-knowledge-and-self-service","5. Knowledge and self-service",[941,5857,5858],{},"Turn resolved work into reusable guidance while keeping content accurate and easy to find.",[1508,5860,5862,5868,5874,5880],{"className":5861},[3990],[1511,5863,5865,5867],{"className":5864},[3994],[3996,5866],{"disabled":27,"type":3998}," Agents can create or propose knowledge from resolved incidents, requests, problems, and changes.",[1511,5869,5871,5873],{"className":5870},[3994],[3996,5872],{"disabled":27,"type":3998}," Knowledge articles have an owner, audience, approval state, review date, and retirement rule.",[1511,5875,5877,5879],{"className":5876},[3994],[3996,5878],{"disabled":27,"type":3998}," Search terms, portal navigation, and request forms help users reach the right article or service without knowing internal team structures.",[1511,5881,5883,5885],{"className":5882},[3994],[3996,5884],{"disabled":27,"type":3998}," Usefulness, search success, feedback, and assisted resolution are measured without rewarding ticket avoidance alone.",[941,5887,5888],{},[1784,5889,4022],{},[1508,5891,5892,5895],{},[1511,5893,5894],{},"Knowledge lifecycle and content sample",[1511,5896,5897],{},"Search, feedback, and self-service metrics",[953,5899,5901],{"id":5900},"_6-automation-integrations-and-data-quality","6. Automation, integrations, and data quality",[941,5903,5904],{},"Automate repeatable work with visible failure handling and accountable configuration changes.",[1508,5906,5908,5914,5920,5926],{"className":5907},[3990],[1511,5909,5911,5913],{"className":5910},[3994],[3996,5912],{"disabled":27,"type":3998}," Routing, approvals, notifications, escalations, and repeatable fulfilment steps are automated where rules are stable.",[1511,5915,5917,5919],{"className":5916},[3994],[3996,5918],{"disabled":27,"type":3998}," Identity, monitoring, asset, collaboration, and business-system integrations have owners, data contracts, and failure alerts.",[1511,5921,5923,5925],{"className":5922},[3994],[3996,5924],{"disabled":27,"type":3998}," Integration accounts and automation permissions follow least privilege, with credentials stored and rotated appropriately.",[1511,5927,5929,5931],{"className":5928},[3994],[3996,5930],{"disabled":27,"type":3998}," Workflow and integration changes are tested, documented, recoverable, and reviewed after failed runs.",[941,5933,5934],{},[1784,5935,4022],{},[1508,5937,5938,5941],{},[1511,5939,5940],{},"Automation and integration inventory",[1511,5942,5943],{},"Failure dashboard and change records",[953,5945,5947],{"id":5946},"_7-asset-and-configuration-context","7. Asset and configuration context",[941,5949,5950],{},"Give service teams enough trusted technical context to assess impact and resolve work efficiently.",[1508,5952,5954,5960,5966,5972],{"className":5953},[3990],[1511,5955,5957,5959],{"className":5956},[3994],[3996,5958],{"disabled":27,"type":3998}," Relevant users, devices, software, services, and configuration items can be linked to incidents, requests, problems, and changes.",[1511,5961,5963,5965],{"className":5962},[3994],[3996,5964],{"disabled":27,"type":3998}," Asset and configuration data has source systems, owners, reconciliation rules, freshness targets, and quality checks.",[1511,5967,5969,5971],{"className":5968},[3994],[3996,5970],{"disabled":27,"type":3998}," Relationships are maintained to the level needed for impact assessment, troubleshooting, compliance, and change planning.",[1511,5973,5975,5977],{"className":5974},[3994],[3996,5976],{"disabled":27,"type":3998}," Lifecycle, warranty, contract, ownership, and support status are visible where they affect service decisions.",[941,5979,5980],{},[1784,5981,4022],{},[1508,5983,5984,5987],{},[1511,5985,5986],{},"Asset and configuration data model",[1511,5988,5989],{},"Data-quality and reconciliation report",[953,5991,5993],{"id":5992},"_8-reporting-and-continual-improvement","8. Reporting and continual improvement",[941,5995,5996],{},"Use balanced evidence to improve user outcomes, team flow, service reliability, and control quality.",[1508,5998,6000,6006,6012,6018],{"className":5999},[3990],[1511,6001,6003,6005],{"className":6002},[3994],[3996,6004],{"disabled":27,"type":3998}," Reporting balances volume, backlog, ageing, service levels, reopen rates, first-contact resolution, quality, and user experience.",[1511,6007,6009,6011],{"className":6008},[3994],[3996,6010],{"disabled":27,"type":3998}," Dashboards distinguish demand, performance, and risk by service, channel, category, priority, team, and user group.",[1511,6013,6015,6017],{"className":6014},[3994],[3996,6016],{"disabled":27,"type":3998}," Reviews examine recurring demand, failure causes, breached commitments, automation errors, feedback, and knowledge gaps.",[1511,6019,6021,6023],{"className":6020},[3994],[3996,6022],{"disabled":27,"type":3998}," Improvement actions have an owner, priority, target date, expected outcome, and evidence of completion.",[941,6025,6026],{},[1784,6027,4022],{},[1508,6029,6030,6033],{},[1511,6031,6032],{},"Operational dashboard and review pack",[1511,6034,6035],{},"Prioritised continual-improvement register",[953,6037,4401],{"id":4400},[941,6039,6040],{},"For every item rated missing, unclear, or partially established, record the impact, risk, accountable owner, dependencies, first executable action, target date, and required evidence. Prioritise actions that close multiple gaps or enable further improvements.",[3354,6042,6043,6062],{},[3357,6044,6045],{},[3360,6046,6047,6049,6051,6054,6056,6058,6060],{},[3363,6048,4413],{},[3363,6050,4416],{},[3363,6052,6053],{},"Impact \u002F risk",[3363,6055,4422],{},[3363,6057,4425],{},[3363,6059,4428],{},[3363,6061,4431],{},[3373,6063,6064,6080,6096,6112,6128],{},[3360,6065,6066,6068,6070,6072,6074,6076,6078],{},[3378,6067,4438],{},[3378,6069],{},[3378,6071],{},[3378,6073],{},[3378,6075],{},[3378,6077],{},[3378,6079],{},[3360,6081,6082,6084,6086,6088,6090,6092,6094],{},[3378,6083,4455],{},[3378,6085],{},[3378,6087],{},[3378,6089],{},[3378,6091],{},[3378,6093],{},[3378,6095],{},[3360,6097,6098,6100,6102,6104,6106,6108,6110],{},[3378,6099,4472],{},[3378,6101],{},[3378,6103],{},[3378,6105],{},[3378,6107],{},[3378,6109],{},[3378,6111],{},[3360,6113,6114,6116,6118,6120,6122,6124,6126],{},[3378,6115,4489],{},[3378,6117],{},[3378,6119],{},[3378,6121],{},[3378,6123],{},[3378,6125],{},[3378,6127],{},[3360,6129,6130,6132,6134,6136,6138,6140,6142],{},[3378,6131,4506],{},[3378,6133],{},[3378,6135],{},[3378,6137],{},[3378,6139],{},[3378,6141],{},[3378,6143],{},{"title":771,"searchDepth":991,"depth":991,"links":6145},[6146,6147,6148,6149,6150,6151,6152,6153,6154,6155],{"id":3925,"depth":991,"text":3926},{"id":5664,"depth":991,"text":5665},{"id":5710,"depth":991,"text":5711},{"id":5756,"depth":991,"text":5757},{"id":5808,"depth":991,"text":5809},{"id":5854,"depth":991,"text":5855},{"id":5900,"depth":991,"text":5901},{"id":5946,"depth":991,"text":5947},{"id":5992,"depth":991,"text":5993},{"id":4400,"depth":991,"text":4401},"2026-08-29","Assess service scope, ownership, intake, core processes, service levels, knowledge, automation, asset context, and continual improvement.","itsm-readiness-checklist.html","\u002Fdownloads\u002Fen\u002Fitsm-readiness-checklist.html",[6161,6162,6163,6164],"Checks for service scope, ownership, intake channels, and the service catalogue.","Controls for incidents, requests, problems, changes, service levels, and escalation.","Review of knowledge, self-service, automation, integrations, and asset context.","A prioritised 90-day backlog with owners, target dates, and evidence.",{"tags":6166},[94,6167,4546,4531],"service-desk","\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fitsm-readiness-checklist",{"title":5602,"description":6157},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fitsm-readiness-checklist",[5610,5615],"lA5tjo70zkzv_AvTPr-n1Q3ROT8u-3qk8fBDeOCCdeY",{"id":6174,"title":6175,"assessmentSlug":934,"associatedSolution":85,"authors":934,"body":6176,"category":4531,"ctaLabel":4532,"date":1442,"dateModified":1442,"deliveryFormat":4533,"description":6767,"downloadFileName":6768,"downloadLabel":4536,"downloadUrl":6769,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":27,"format":4531,"gated":27,"healthCheckSlug":934,"keyTakeaways":6770,"meta":6775,"navigation":27,"newsletterTopic":6777,"path":6778,"publicType":4548,"published":27,"readTime":6779,"resourceType":4550,"schemaType":1457,"seo":6780,"slug":6180,"stem":6781,"teaser":6782,"type":4531,"__hash__":6783},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fmft-security-migration-readiness-checklist.md","MFT Security & Migration Readiness Checklist",{"type":938,"value":6177,"toc":6755},[6178,6181,6184,6189,6191,6233,6237,6240,6273,6277,6285,6289,6292,6325,6329,6337,6341,6344,6377,6381,6389,6393,6396,6429,6433,6441,6445,6448,6481,6485,6493,6497,6500,6533,6537,6545,6549,6552,6585,6589,6597,6601,6604,6637,6641,6649,6651,6653],[1433,6179,6175],{"id":6180},"mft-security-migration-readiness-checklist",[941,6182,6183],{},"Use the checklist before defining migration waves or selecting a cutover date. Include transfer owners, application teams, network and security teams, compliance, service management, and the people who support partner connections.",[3918,6185,6186],{},[941,6187,6188],{},"A transfer is not migration-ready until its owner, dependencies, security material, test criteria, failure behavior, rollback path, and operational handover are documented.",[953,6190,3926],{"id":3925},[3354,6192,6193,6201],{},[3357,6194,6195],{},[3360,6196,6197,6199],{},[3363,6198,1159],{},[3363,6200,3937],{},[3373,6202,6203,6209,6215,6221,6227],{},[3360,6204,6205,6207],{},[3378,6206,3944],{},[3378,6208,3947],{},[3360,6210,6211,6213],{},[3378,6212,3952],{},[3378,6214,3955],{},[3360,6216,6217,6219],{},[3378,6218,3960],{},[3378,6220,3963],{},[3360,6222,6223,6225],{},[3378,6224,3968],{},[3378,6226,3971],{},[3360,6228,6229,6231],{},[3378,6230,3976],{},[3378,6232,3979],{},[953,6234,6236],{"id":6235},"_1-transfer-inventory-and-ownership","1. Transfer inventory and ownership",[941,6238,6239],{},"Establish a complete and accountable inventory before moving any production flow.",[1508,6241,6243,6249,6255,6261,6267],{"className":6242},[3990],[1511,6244,6246,6248],{"className":6245},[3994],[3996,6247],{"disabled":27,"type":3998}," FTP, SFTP, FTPS, AS2, API, mailbox, and file-system transfers are inventoried across production and non-production.",[1511,6250,6252,6254],{"className":6251},[3994],[3996,6253],{"disabled":27,"type":3998}," Each transfer has a business owner, technical owner, support group, and escalation contact.",[1511,6256,6258,6260],{"className":6257},[3994],[3996,6259],{"disabled":27,"type":3998}," Schedules, triggers, source and target systems, filenames, formats, volumes, and service windows are recorded.",[1511,6262,6264,6266],{"className":6263},[3994],[3996,6265],{"disabled":27,"type":3998}," Undocumented transfers, shared accounts, manual steps, and unsupported scripts are explicitly flagged.",[1511,6268,6270,6272],{"className":6269},[3994],[3996,6271],{"disabled":27,"type":3998}," Inactive and duplicate transfers are validated before being excluded from migration scope.",[941,6274,6275],{},[1784,6276,4022],{},[1508,6278,6279,6282],{},[1511,6280,6281],{},"Transfer inventory export",[1511,6283,6284],{},"Ownership and support matrix",[953,6286,6288],{"id":6287},"_2-partner-and-application-dependencies","2. Partner and application dependencies",[941,6290,6291],{},"Identify external constraints that can block testing or cutover.",[1508,6293,6295,6301,6307,6313,6319],{"className":6294},[3990],[1511,6296,6298,6300],{"className":6297},[3994],[3996,6299],{"disabled":27,"type":3998}," Every external partner has technical contacts, business contacts, support hours, and escalation paths.",[1511,6302,6304,6306],{"className":6303},[3994],[3996,6305],{"disabled":27,"type":3998}," IP allowlists, DNS names, proxy rules, firewalls, ports, and network routes are captured.",[1511,6308,6310,6312],{"className":6309},[3994],[3996,6311],{"disabled":27,"type":3998}," Upstream and downstream application dependencies include batch order, acknowledgements, and reconciliation logic.",[1511,6314,6316,6318],{"className":6315},[3994],[3996,6317],{"disabled":27,"type":3998}," Peak periods, blackout windows, regulatory deadlines, and partner change freezes are known.",[1511,6320,6322,6324],{"className":6321},[3994],[3996,6323],{"disabled":27,"type":3998}," Partner lead times for certificates, endpoint changes, and testing are reflected in the plan.",[941,6326,6327],{},[1784,6328,4022],{},[1508,6330,6331,6334],{},[1511,6332,6333],{},"Partner dependency register",[1511,6335,6336],{},"Network and endpoint matrix",[953,6338,6340],{"id":6339},"_3-authentication-keys-and-certificates","3. Authentication, keys, and certificates",[941,6342,6343],{},"Ensure identity material can be migrated without insecure shortcuts or unexpected expiry.",[1508,6345,6347,6353,6359,6365,6371],{"className":6346},[3990],[1511,6348,6350,6352],{"className":6349},[3994],[3996,6351],{"disabled":27,"type":3998}," Authentication methods are documented per transfer, including passwords, SSH keys, certificates, tokens, and mutual TLS.",[1511,6354,6356,6358],{"className":6355},[3994],[3996,6357],{"disabled":27,"type":3998}," Private keys and credentials are stored in approved secret-management or key-management systems.",[1511,6360,6362,6364],{"className":6361},[3994],[3996,6363],{"disabled":27,"type":3998}," Key and certificate ownership, expiry, rotation, revocation, and emergency replacement are defined.",[1511,6366,6368,6370],{"className":6367},[3994],[3996,6369],{"disabled":27,"type":3998}," Host-key validation and partner key fingerprints are verified rather than bypassed.",[1511,6372,6374,6376],{"className":6373},[3994],[3996,6375],{"disabled":27,"type":3998}," Shared accounts and long-lived credentials have a documented remediation plan.",[941,6378,6379],{},[1784,6380,4022],{},[1508,6382,6383,6386],{},[1511,6384,6385],{},"Credential and certificate register",[1511,6387,6388],{},"Rotation and expiry calendar",[953,6390,6392],{"id":6391},"_4-encryption-audit-logging-retention-and-compliance","4. Encryption, audit logging, retention, and compliance",[941,6394,6395],{},"Verify that security and evidence obligations survive the migration.",[1508,6397,6399,6405,6411,6417,6423],{"className":6398},[3990],[1511,6400,6402,6404],{"className":6401},[3994],[3996,6403],{"disabled":27,"type":3998}," Approved protocols, cipher suites, key lengths, and encryption-at-rest requirements are documented.",[1511,6406,6408,6410],{"className":6407},[3994],[3996,6409],{"disabled":27,"type":3998}," Audit logs record authentication, transfer start and result, file identity, user or service account, and administrative changes.",[1511,6412,6414,6416],{"className":6413},[3994],[3996,6415],{"disabled":27,"type":3998}," Log integrity, time synchronisation, access, export, and retention meet investigation requirements.",[1511,6418,6420,6422],{"className":6419},[3994],[3996,6421],{"disabled":27,"type":3998}," File retention, deletion, quarantine, and archive rules align with contracts, GDPR, and legal obligations.",[1511,6424,6426,6428],{"className":6425},[3994],[3996,6427],{"disabled":27,"type":3998}," Personal and sensitive data flows have a documented purpose, recipient, legal basis, and minimisation review.",[941,6430,6431],{},[1784,6432,4022],{},[1508,6434,6435,6438],{},[1511,6436,6437],{},"Security baseline and protocol matrix",[1511,6439,6440],{},"Audit and retention requirements",[953,6442,6444],{"id":6443},"_5-automation-and-failed-transfer-handling","5. Automation and failed-transfer handling",[941,6446,6447],{},"Confirm predictable behavior for normal processing and failure scenarios.",[1508,6449,6451,6457,6463,6469,6475],{"className":6450},[3990],[1511,6452,6454,6456],{"className":6453},[3994],[3996,6455],{"disabled":27,"type":3998}," Scheduling, event triggers, dependencies, retries, and concurrency limits are documented.",[1511,6458,6460,6462],{"className":6459},[3994],[3996,6461],{"disabled":27,"type":3998}," Duplicate prevention, idempotency, partial-file handling, checksum validation, and acknowledgement logic are defined.",[1511,6464,6466,6468],{"className":6465},[3994],[3996,6467],{"disabled":27,"type":3998}," Failed transfers generate actionable alerts with owner, business impact, retry state, and next action.",[1511,6470,6472,6474],{"className":6471},[3994],[3996,6473],{"disabled":27,"type":3998}," Quarantine, replay, manual intervention, and data-correction procedures are tested.",[1511,6476,6478,6480],{"className":6477},[3994],[3996,6479],{"disabled":27,"type":3998}," Automation service accounts follow least privilege and changes are version-controlled and reviewed.",[941,6482,6483],{},[1784,6484,4022],{},[1508,6486,6487,6490],{},[1511,6488,6489],{},"Job dependency and retry design",[1511,6491,6492],{},"Failure runbooks and test results",[953,6494,6496],{"id":6495},"_6-monitoring-and-operational-readiness","6. Monitoring and operational readiness",[941,6498,6499],{},"Ensure support teams can detect, diagnose, and resolve transfer problems after cutover.",[1508,6501,6503,6509,6515,6521,6527],{"className":6502},[3990],[1511,6504,6506,6508],{"className":6505},[3994],[3996,6507],{"disabled":27,"type":3998}," Dashboards show expected, successful, delayed, failed, retried, and missing transfers by criticality.",[1511,6510,6512,6514],{"className":6511},[3994],[3996,6513],{"disabled":27,"type":3998}," Monitoring covers platform health, queues, storage, certificates, network dependencies, and scheduler status.",[1511,6516,6518,6520],{"className":6517},[3994],[3996,6519],{"disabled":27,"type":3998}," Support teams have searchable audit context and can distinguish partner, network, authentication, application, and platform failures.",[1511,6522,6524,6526],{"className":6523},[3994],[3996,6525],{"disabled":27,"type":3998}," Service levels, on-call coverage, escalation, maintenance, and capacity thresholds are agreed.",[1511,6528,6530,6532],{"className":6529},[3994],[3996,6531],{"disabled":27,"type":3998}," Operational reports cover reliability, failure ageing, partner impact, security exceptions, and capacity trends.",[941,6534,6535],{},[1784,6536,4022],{},[1508,6538,6539,6542],{},[1511,6540,6541],{},"Operations dashboard and alert catalogue",[1511,6543,6544],{},"Support model and service levels",[953,6546,6548],{"id":6547},"_7-migration-sequencing-testing-and-reconciliation","7. Migration sequencing, testing, and reconciliation",[941,6550,6551],{},"Create risk-based waves with objective acceptance criteria.",[1508,6553,6555,6561,6567,6573,6579],{"className":6554},[3990],[1511,6556,6558,6560],{"className":6557},[3994],[3996,6559],{"disabled":27,"type":3998}," Transfers are grouped into waves based on business criticality, dependencies, partner readiness, complexity, and reversibility.",[1511,6562,6564,6566],{"className":6563},[3994],[3996,6565],{"disabled":27,"type":3998}," Test cases cover positive flow, invalid credentials, expired keys, network interruption, duplicate files, partial files, retries, and peak volume.",[1511,6568,6570,6572],{"className":6569},[3994],[3996,6571],{"disabled":27,"type":3998}," Partner tests have named participants, data, dates, acceptance criteria, and evidence retention.",[1511,6574,6576,6578],{"className":6575},[3994],[3996,6577],{"disabled":27,"type":3998}," Parallel operation and reconciliation compare file counts, hashes, business records, acknowledgements, and timing.",[1511,6580,6582,6584],{"className":6581},[3994],[3996,6583],{"disabled":27,"type":3998}," Go\u002Fno-go decisions use measurable thresholds and require sign-off from business and technical owners.",[941,6586,6587],{},[1784,6588,4022],{},[1508,6590,6591,6594],{},[1511,6592,6593],{},"Wave plan and dependency graph",[1511,6595,6596],{},"Test catalogue and signed evidence",[953,6598,6600],{"id":6599},"_8-rollback-and-operational-handover","8. Rollback and operational handover",[941,6602,6603],{},"Protect production continuity and make post-cutover ownership explicit.",[1508,6605,6607,6613,6619,6625,6631],{"className":6606},[3990],[1511,6608,6610,6612],{"className":6609},[3994],[3996,6611],{"disabled":27,"type":3998}," Rollback restores endpoints, credentials, routing, schedules, data state, and partner communication within an agreed window.",[1511,6614,6616,6618],{"className":6615},[3994],[3996,6617],{"disabled":27,"type":3998}," Rollback decision thresholds, authority, command channel, and latest safe decision time are documented.",[1511,6620,6622,6624],{"className":6621},[3994],[3996,6623],{"disabled":27,"type":3998}," Hypercare has staffing, monitoring, issue triage, partner communication, and exit criteria.",[1511,6626,6628,6630],{"className":6627},[3994],[3996,6629],{"disabled":27,"type":3998}," Runbooks, architecture, inventories, credentials ownership, support queues, and known issues are handed over and accepted.",[1511,6632,6634,6636],{"className":6633},[3994],[3996,6635],{"disabled":27,"type":3998}," Legacy endpoints, accounts, certificates, jobs, and data are decommissioned only after reconciliation and retention approval.",[941,6638,6639],{},[1784,6640,4022],{},[1508,6642,6643,6646],{},[1511,6644,6645],{},"Rollback plan and rehearsal result",[1511,6647,6648],{},"Signed operational acceptance",[953,6650,4401],{"id":4400},[941,6652,4404],{},[3354,6654,6655,6673],{},[3357,6656,6657],{},[3360,6658,6659,6661,6663,6665,6667,6669,6671],{},[3363,6660,4413],{},[3363,6662,4416],{},[3363,6664,4419],{},[3363,6666,4422],{},[3363,6668,4425],{},[3363,6670,4428],{},[3363,6672,4431],{},[3373,6674,6675,6691,6707,6723,6739],{},[3360,6676,6677,6679,6681,6683,6685,6687,6689],{},[3378,6678,4438],{},[3378,6680],{},[3378,6682],{},[3378,6684],{},[3378,6686],{},[3378,6688],{},[3378,6690],{},[3360,6692,6693,6695,6697,6699,6701,6703,6705],{},[3378,6694,4455],{},[3378,6696],{},[3378,6698],{},[3378,6700],{},[3378,6702],{},[3378,6704],{},[3378,6706],{},[3360,6708,6709,6711,6713,6715,6717,6719,6721],{},[3378,6710,4472],{},[3378,6712],{},[3378,6714],{},[3378,6716],{},[3378,6718],{},[3378,6720],{},[3378,6722],{},[3360,6724,6725,6727,6729,6731,6733,6735,6737],{},[3378,6726,4489],{},[3378,6728],{},[3378,6730],{},[3378,6732],{},[3378,6734],{},[3378,6736],{},[3378,6738],{},[3360,6740,6741,6743,6745,6747,6749,6751,6753],{},[3378,6742,4506],{},[3378,6744],{},[3378,6746],{},[3378,6748],{},[3378,6750],{},[3378,6752],{},[3378,6754],{},{"title":771,"searchDepth":991,"depth":991,"links":6756},[6757,6758,6759,6760,6761,6762,6763,6764,6765,6766],{"id":3925,"depth":991,"text":3926},{"id":6235,"depth":991,"text":6236},{"id":6287,"depth":991,"text":6288},{"id":6339,"depth":991,"text":6340},{"id":6391,"depth":991,"text":6392},{"id":6443,"depth":991,"text":6444},{"id":6495,"depth":991,"text":6496},{"id":6547,"depth":991,"text":6548},{"id":6599,"depth":991,"text":6600},{"id":4400,"depth":991,"text":4401},"Prepare enterprise file-transfer environments for migration without losing partner connectivity, encryption, auditability, failure handling, or operational control.","mft-security-migration-readiness-checklist.html","\u002Fdownloads\u002Fen\u002Fmft-security-migration-readiness-checklist.html",[6771,6772,6773,6774],"An inventory model for FTP, SFTP, FTPS, AS2, API, and scheduled transfer dependencies.","Security checks for identities, keys, certificates, encryption, logging, retention, and GDPR.","Migration-wave, partner-test, cutover, reconciliation, and rollback controls.","Operational handover criteria covering monitoring, failed transfers, automation, and support.",{"tags":6776},[85,4546,4531],"secureFileTransferEdi","\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fmft-security-migration-readiness-checklist","14 min read",{"title":6175,"description":6767},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fmft-security-migration-readiness-checklist",[6183,6188],"zdwLvVSFDXTjvT2beoIiqvfk3dnphuSZPUre55WjUmo",{"id":6785,"title":6786,"assessmentSlug":934,"associatedSolution":91,"authors":934,"body":6787,"category":4531,"ctaLabel":4532,"date":1442,"dateModified":1442,"deliveryFormat":4533,"description":7283,"downloadFileName":7284,"downloadLabel":4536,"downloadUrl":7285,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":23,"format":4531,"gated":27,"healthCheckSlug":934,"keyTakeaways":7286,"meta":7291,"navigation":27,"newsletterTopic":7293,"path":7294,"publicType":4548,"published":27,"readTime":7295,"resourceType":4550,"schemaType":1457,"seo":7296,"slug":6791,"stem":7297,"teaser":7298,"type":4531,"__hash__":7299},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fpatch-management-automation-maturity-checklist.md","Patch Management & Automation Maturity Checklist",{"type":938,"value":6788,"toc":7272},[6789,6792,6795,6800,6802,6844,6848,6851,6878,6882,6890,6894,6897,6924,6928,6936,6940,6943,6970,6974,6982,6986,6989,7016,7020,7028,7032,7035,7062,7066,7074,7078,7081,7108,7112,7120,7124,7127,7154,7158,7166,7168,7170],[1433,6790,6786],{"id":6791},"patch-management-automation-maturity-checklist",[941,6793,6794],{},"Use the checklist to review whether patching is a controlled operating process across endpoints, servers, cloud workloads, network devices, applications, and dependencies.",[3918,6796,6797],{},[941,6798,6799],{},"Score maturity by platform and criticality. A strong average must not hide unsupported or unpatched critical systems.",[953,6801,3926],{"id":3925},[3354,6803,6804,6812],{},[3357,6805,6806],{},[3360,6807,6808,6810],{},[3363,6809,1159],{},[3363,6811,3937],{},[3373,6813,6814,6820,6826,6832,6838],{},[3360,6815,6816,6818],{},[3378,6817,3944],{},[3378,6819,3947],{},[3360,6821,6822,6824],{},[3378,6823,3952],{},[3378,6825,3955],{},[3360,6827,6828,6830],{},[3378,6829,3960],{},[3378,6831,3963],{},[3360,6833,6834,6836],{},[3378,6835,3968],{},[3378,6837,3971],{},[3360,6839,6840,6842],{},[3378,6841,3976],{},[3378,6843,3979],{},[953,6845,6847],{"id":6846},"_1-inventory-and-ownership","1. Inventory and ownership",[941,6849,6850],{},"Know which assets are in scope and who owns remediation.",[1508,6852,6854,6860,6866,6872],{"className":6853},[3990],[1511,6855,6857,6859],{"className":6856},[3994],[3996,6858],{"disabled":27,"type":3998}," Supported endpoints, servers, virtual machines, cloud workloads, containers, network devices, databases, middleware, and applications are inventoried.",[1511,6861,6863,6865],{"className":6862},[3994],[3996,6864],{"disabled":27,"type":3998}," Asset criticality, environment, owner, maintenance window, support status, and patch method are recorded.",[1511,6867,6869,6871],{"className":6868},[3994],[3996,6870],{"disabled":27,"type":3998}," Unknown, stale, duplicate, and unmanaged assets are identified and assigned.",[1511,6873,6875,6877],{"className":6874},[3994],[3996,6876],{"disabled":27,"type":3998}," Application and service owners understand dependency and outage implications.",[941,6879,6880],{},[1784,6881,4022],{},[1508,6883,6884,6887],{},[1511,6885,6886],{},"Patch coverage inventory",[1511,6888,6889],{},"Ownership matrix",[953,6891,6893],{"id":6892},"_2-risk-based-prioritisation","2. Risk-based prioritisation",[941,6895,6896],{},"Prioritise beyond vendor severity alone.",[1508,6898,6900,6906,6912,6918],{"className":6899},[3990],[1511,6901,6903,6905],{"className":6902},[3994],[3996,6904],{"disabled":27,"type":3998}," Prioritisation combines severity, exploitability, active exploitation, exposure, asset criticality, and compensating controls.",[1511,6907,6909,6911],{"className":6908},[3994],[3996,6910],{"disabled":27,"type":3998}," Emergency patch criteria, authority, communication, testing, and accelerated windows are defined.",[1511,6913,6915,6917],{"className":6914},[3994],[3996,6916],{"disabled":27,"type":3998}," Remediation targets vary by risk and include unsupported software and end-of-life platforms.",[1511,6919,6921,6923],{"className":6920},[3994],[3996,6922],{"disabled":27,"type":3998}," Deferred patches have approved risk acceptance, expiry, and compensating actions.",[941,6925,6926],{},[1784,6927,4022],{},[1508,6929,6930,6933],{},[1511,6931,6932],{},"Risk-scoring method",[1511,6934,6935],{},"Emergency patch procedure",[953,6937,6939],{"id":6938},"_3-testing-and-release-readiness","3. Testing and release readiness",[941,6941,6942],{},"Reduce avoidable disruption without creating indefinite delay.",[1508,6944,6946,6952,6958,6964],{"className":6945},[3990],[1511,6947,6949,6951],{"className":6948},[3994],[3996,6950],{"disabled":27,"type":3998}," Representative test rings cover critical hardware, operating systems, middleware, applications, and integrations.",[1511,6953,6955,6957],{"className":6954},[3994],[3996,6956],{"disabled":27,"type":3998}," Acceptance criteria include service health, performance, security controls, backup, monitoring, and business transactions.",[1511,6959,6961,6963],{"className":6960},[3994],[3996,6962],{"disabled":27,"type":3998}," Known issues, prerequisites, reboots, downtime, and application-owner approvals are recorded.",[1511,6965,6967,6969],{"className":6966},[3994],[3996,6968],{"disabled":27,"type":3998}," Test results and release decisions are retained for traceability.",[941,6971,6972],{},[1784,6973,4022],{},[1508,6975,6976,6979],{},[1511,6977,6978],{},"Test-ring design",[1511,6980,6981],{},"Release evidence",[953,6983,6985],{"id":6984},"_4-automated-deployment-and-orchestration","4. Automated deployment and orchestration",[941,6987,6988],{},"Evaluate repeatability, safety, and dependency awareness.",[1508,6990,6992,6998,7004,7010],{"className":6991},[3990],[1511,6993,6995,6997],{"className":6994},[3994],[3996,6996],{"disabled":27,"type":3998}," Deployment tooling covers required platforms and reports unreachable or unsupported assets.",[1511,6999,7001,7003],{"className":7000},[3994],[3996,7002],{"disabled":27,"type":3998}," Rings, maintenance windows, throttling, prerequisites, reboots, and service sequencing are automated where appropriate.",[1511,7005,7007,7009],{"className":7006},[3994],[3996,7008],{"disabled":27,"type":3998}," Automation credentials use least privilege and changes to jobs or policies are reviewed and versioned.",[1511,7011,7013,7015],{"className":7012},[3994],[3996,7014],{"disabled":27,"type":3998}," Failed deployments create actionable work with error context, owner, retry state, and business impact.",[941,7017,7018],{},[1784,7019,4022],{},[1508,7021,7022,7025],{},[1511,7023,7024],{},"Automation workflow design",[1511,7026,7027],{},"Failure and retry dashboard",[953,7029,7031],{"id":7030},"_5-exceptions-and-rollback","5. Exceptions and rollback",[941,7033,7034],{},"Keep deviations controlled and recovery executable.",[1508,7036,7038,7044,7050,7056],{"className":7037},[3990],[1511,7039,7041,7043],{"className":7040},[3994],[3996,7042],{"disabled":27,"type":3998}," Exceptions include affected assets, reason, risk, owner, approver, expiry, and compensating controls.",[1511,7045,7047,7049],{"className":7046},[3994],[3996,7048],{"disabled":27,"type":3998}," Rollback or recovery steps are defined for operating system, application, firmware, and configuration changes.",[1511,7051,7053,7055],{"className":7052},[3994],[3996,7054],{"disabled":27,"type":3998}," Backups, snapshots, package caches, and break-glass access are validated before high-risk deployment.",[1511,7057,7059,7061],{"className":7058},[3994],[3996,7060],{"disabled":27,"type":3998}," Rollback criteria and decision authority are known during the maintenance window.",[941,7063,7064],{},[1784,7065,4022],{},[1508,7067,7068,7071],{},[1511,7069,7070],{},"Exception register",[1511,7072,7073],{},"Rollback test evidence",[953,7075,7077],{"id":7076},"_6-verification-and-reporting","6. Verification and reporting",[941,7079,7080],{},"Prove successful installation and expose residual risk.",[1508,7082,7084,7090,7096,7102],{"className":7083},[3990],[1511,7085,7087,7089],{"className":7086},[3994],[3996,7088],{"disabled":27,"type":3998}," Post-deployment verification checks version, service health, business transactions, security agents, and monitoring.",[1511,7091,7093,7095],{"className":7092},[3994],[3996,7094],{"disabled":27,"type":3998}," Compliance reports distinguish missing, failed, pending reboot, excluded, unsupported, and false-positive states.",[1511,7097,7099,7101],{"className":7098},[3994],[3996,7100],{"disabled":27,"type":3998}," Metrics cover risk-weighted compliance, time to remediate, failure rate, exception ageing, automation coverage, and repeat incidents.",[1511,7103,7105,7107],{"className":7104},[3994],[3996,7106],{"disabled":27,"type":3998}," Reports are reconciled with asset and vulnerability data before management decisions.",[941,7109,7110],{},[1784,7111,4022],{},[1508,7113,7114,7117],{},[1511,7115,7116],{},"Post-deployment verification report",[1511,7118,7119],{},"Risk-weighted patch scorecard",[953,7121,7123],{"id":7122},"_7-operating-model-and-continual-improvement","7. Operating model and continual improvement",[941,7125,7126],{},"Make patching a governed service rather than a monthly task.",[1508,7128,7130,7136,7142,7148],{"className":7129},[3990],[1511,7131,7133,7135],{"className":7132},[3994],[3996,7134],{"disabled":27,"type":3998}," Roles across security, operations, application teams, service owners, change management, and vendors are explicit.",[1511,7137,7139,7141],{"className":7138},[3994],[3996,7140],{"disabled":27,"type":3998}," A regular governance forum reviews risk, exceptions, failures, unsupported systems, and improvement work.",[1511,7143,7145,7147],{"className":7144},[3994],[3996,7146],{"disabled":27,"type":3998}," Lessons from failed patches and incidents update tests, automation, maintenance windows, and runbooks.",[1511,7149,7151,7153],{"className":7150},[3994],[3996,7152],{"disabled":27,"type":3998}," Capacity and licensing of patch tooling are monitored as the estate changes.",[941,7155,7156],{},[1784,7157,4022],{},[1508,7159,7160,7163],{},[1511,7161,7162],{},"Patch governance charter",[1511,7164,7165],{},"Improvement backlog",[953,7167,4401],{"id":4400},[941,7169,4404],{},[3354,7171,7172,7190],{},[3357,7173,7174],{},[3360,7175,7176,7178,7180,7182,7184,7186,7188],{},[3363,7177,4413],{},[3363,7179,4416],{},[3363,7181,4419],{},[3363,7183,4422],{},[3363,7185,4425],{},[3363,7187,4428],{},[3363,7189,4431],{},[3373,7191,7192,7208,7224,7240,7256],{},[3360,7193,7194,7196,7198,7200,7202,7204,7206],{},[3378,7195,4438],{},[3378,7197],{},[3378,7199],{},[3378,7201],{},[3378,7203],{},[3378,7205],{},[3378,7207],{},[3360,7209,7210,7212,7214,7216,7218,7220,7222],{},[3378,7211,4455],{},[3378,7213],{},[3378,7215],{},[3378,7217],{},[3378,7219],{},[3378,7221],{},[3378,7223],{},[3360,7225,7226,7228,7230,7232,7234,7236,7238],{},[3378,7227,4472],{},[3378,7229],{},[3378,7231],{},[3378,7233],{},[3378,7235],{},[3378,7237],{},[3378,7239],{},[3360,7241,7242,7244,7246,7248,7250,7252,7254],{},[3378,7243,4489],{},[3378,7245],{},[3378,7247],{},[3378,7249],{},[3378,7251],{},[3378,7253],{},[3378,7255],{},[3360,7257,7258,7260,7262,7264,7266,7268,7270],{},[3378,7259,4506],{},[3378,7261],{},[3378,7263],{},[3378,7265],{},[3378,7267],{},[3378,7269],{},[3378,7271],{},{"title":771,"searchDepth":991,"depth":991,"links":7273},[7274,7275,7276,7277,7278,7279,7280,7281,7282],{"id":3925,"depth":991,"text":3926},{"id":6846,"depth":991,"text":6847},{"id":6892,"depth":991,"text":6893},{"id":6938,"depth":991,"text":6939},{"id":6984,"depth":991,"text":6985},{"id":7030,"depth":991,"text":7031},{"id":7076,"depth":991,"text":7077},{"id":7122,"depth":991,"text":7123},{"id":4400,"depth":991,"text":4401},"Assess asset coverage, risk-based prioritisation, testing, deployment automation, exceptions, rollback, reporting, and operational ownership.","patch-management-automation-maturity-checklist.html","\u002Fdownloads\u002Fen\u002Fpatch-management-automation-maturity-checklist.html",[7287,7288,7289,7290],"Coverage and ownership checks across the enterprise estate.","Risk-based patch prioritisation and service-level criteria.","Testing, deployment, rollback, and exception controls.","Metrics for compliance, ageing, failure, and automation quality.",{"tags":7292},[91,4546,4531],"endpointPatchManagement","\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fpatch-management-automation-maturity-checklist","9 min read",{"title":6786,"description":7283},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fpatch-management-automation-maturity-checklist",[6794,6799],"t45wEa4y1uA6qXmOj8Whzc5DcEvpznxjfP0ODgIEv4w",{"id":7301,"title":7302,"assessmentSlug":934,"associatedSolution":88,"authors":934,"body":7303,"category":4531,"ctaLabel":4532,"date":1442,"dateModified":1442,"deliveryFormat":4533,"description":7798,"downloadFileName":7799,"downloadLabel":4536,"downloadUrl":7800,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":23,"format":4531,"gated":27,"healthCheckSlug":934,"keyTakeaways":7801,"meta":7806,"navigation":27,"newsletterTopic":7808,"path":7809,"publicType":4548,"published":27,"readTime":7295,"resourceType":4550,"schemaType":1457,"seo":7810,"slug":7307,"stem":7811,"teaser":7812,"type":4531,"__hash__":7813},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fsecurity-posture-readiness-checklist.md","Security Posture Readiness Checklist",{"type":938,"value":7304,"toc":7787},[7305,7308,7311,7316,7318,7360,7364,7367,7394,7398,7406,7410,7413,7440,7444,7452,7456,7459,7486,7490,7497,7501,7504,7531,7535,7543,7547,7550,7577,7581,7589,7593,7596,7623,7627,7635,7639,7642,7669,7673,7681,7683,7685],[1433,7306,7302],{"id":7307},"security-posture-readiness-checklist",[941,7309,7310],{},"Use the checklist to establish a defensible baseline across technology, process, ownership, and evidence. It is suitable for planning a security assessment, tooling consolidation, or control-improvement backlog.",[3918,7312,7313],{},[941,7314,7315],{},"Prioritise gaps by exploitability, business impact, exposure, control dependency, and evidence quality.",[953,7317,3926],{"id":3925},[3354,7319,7320,7328],{},[3357,7321,7322],{},[3360,7323,7324,7326],{},[3363,7325,1159],{},[3363,7327,3937],{},[3373,7329,7330,7336,7342,7348,7354],{},[3360,7331,7332,7334],{},[3378,7333,3944],{},[3378,7335,3947],{},[3360,7337,7338,7340],{},[3378,7339,3952],{},[3378,7341,3955],{},[3360,7343,7344,7346],{},[3378,7345,3960],{},[3378,7347,3963],{},[3360,7349,7350,7352],{},[3378,7351,3968],{},[3378,7353,3971],{},[3360,7355,7356,7358],{},[3378,7357,3976],{},[3378,7359,3979],{},[953,7361,7363],{"id":7362},"_1-asset-and-exposure-coverage","1. Asset and exposure coverage",[941,7365,7366],{},"Establish what must be protected and where it is exposed.",[1508,7368,7370,7376,7382,7388],{"className":7369},[3990],[1511,7371,7373,7375],{"className":7372},[3994],[3996,7374],{"disabled":27,"type":3998}," Hardware, software, cloud, SaaS, identities, data stores, APIs, and internet-facing services are inventoried.",[1511,7377,7379,7381],{"className":7378},[3994],[3996,7380],{"disabled":27,"type":3998}," Business criticality, owner, environment, support status, and data classification are recorded.",[1511,7383,7385,7387],{"className":7384},[3994],[3996,7386],{"disabled":27,"type":3998}," Unknown, unmanaged, obsolete, and shadow assets are detected and triaged.",[1511,7389,7391,7393],{"className":7390},[3994],[3996,7392],{"disabled":27,"type":3998}," External attack-surface changes are monitored and assigned for remediation.",[941,7395,7396],{},[1784,7397,4022],{},[1508,7399,7400,7403],{},[1511,7401,7402],{},"Asset coverage report",[1511,7404,7405],{},"External exposure register",[953,7407,7409],{"id":7408},"_2-identity-and-privileged-access","2. Identity and privileged access",[941,7411,7412],{},"Review authentication, lifecycle, privilege, and service-account controls.",[1508,7414,7416,7422,7428,7434],{"className":7415},[3990],[1511,7417,7419,7421],{"className":7418},[3994],[3996,7420],{"disabled":27,"type":3998}," Joiner, mover, and leaver processes cover employees, contractors, partners, and service identities.",[1511,7423,7425,7427],{"className":7424},[3994],[3996,7426],{"disabled":27,"type":3998}," MFA is enforced based on risk, especially for privileged, remote, and sensitive access.",[1511,7429,7431,7433],{"className":7430},[3994],[3996,7432],{"disabled":27,"type":3998}," Privileged access is separated, time-bound where possible, logged, and periodically recertified.",[1511,7435,7437,7439],{"className":7436},[3994],[3996,7438],{"disabled":27,"type":3998}," Service-account ownership, secrets, permissions, rotation, and usage are reviewed.",[941,7441,7442],{},[1784,7443,4022],{},[1508,7445,7446,7449],{},[1511,7447,7448],{},"Access review evidence",[1511,7450,7451],{},"Privileged account inventory",[953,7453,7455],{"id":7454},"_3-vulnerability-and-configuration-management","3. Vulnerability and configuration management",[941,7457,7458],{},"Confirm coverage, prioritisation, remediation, and exception handling.",[1508,7460,7462,7468,7474,7480],{"className":7461},[3990],[1511,7463,7465,7467],{"className":7464},[3994],[3996,7466],{"disabled":27,"type":3998}," Authenticated scanning or equivalent coverage includes servers, endpoints, network devices, containers, cloud, applications, and dependencies.",[1511,7469,7471,7473],{"className":7470},[3994],[3996,7472],{"disabled":27,"type":3998}," Prioritisation combines exploitability, exposure, asset criticality, active exploitation, and compensating controls.",[1511,7475,7477,7479],{"className":7476},[3994],[3996,7478],{"disabled":27,"type":3998}," Remediation targets, owners, verification, and escalation are defined by risk.",[1511,7481,7483,7485],{"className":7482},[3994],[3996,7484],{"disabled":27,"type":3998}," Configuration baselines and exceptions are versioned, monitored, and time-bound.",[941,7487,7488],{},[1784,7489,4022],{},[1508,7491,7492,7495],{},[1511,7493,7494],{},"Coverage and ageing dashboard",[1511,7496,7070],{},[953,7498,7500],{"id":7499},"_4-logging-detection-and-response","4. Logging, detection, and response",[941,7502,7503],{},"Check whether security-relevant activity can be detected and investigated.",[1508,7505,7507,7513,7519,7525],{"className":7506},[3990],[1511,7508,7510,7512],{"className":7509},[3994],[3996,7511],{"disabled":27,"type":3998}," Critical identity, endpoint, network, cloud, application, database, and administrative logs are collected.",[1511,7514,7516,7518],{"className":7515},[3994],[3996,7517],{"disabled":27,"type":3998}," Detection rules have owners, severity, response playbooks, test evidence, and review dates.",[1511,7520,7522,7524],{"className":7521},[3994],[3996,7523],{"disabled":27,"type":3998}," Log retention, integrity, access, time synchronisation, and search performance support investigations.",[1511,7526,7528,7530],{"className":7527},[3994],[3996,7529],{"disabled":27,"type":3998}," Incident roles, communication, containment, evidence handling, recovery, and lessons learned are exercised.",[941,7532,7533],{},[1784,7534,4022],{},[1508,7536,7537,7540],{},[1511,7538,7539],{},"Logging coverage matrix",[1511,7541,7542],{},"Detection test and exercise records",[953,7544,7546],{"id":7545},"_5-data-backup-and-resilience-controls","5. Data, backup, and resilience controls",[941,7548,7549],{},"Review protection of sensitive data and recovery from destructive events.",[1508,7551,7553,7559,7565,7571],{"className":7552},[3990],[1511,7554,7556,7558],{"className":7555},[3994],[3996,7557],{"disabled":27,"type":3998}," Sensitive data locations, flows, access, encryption, retention, and exports are known.",[1511,7560,7562,7564],{"className":7561},[3994],[3996,7563],{"disabled":27,"type":3998}," Backups are isolated appropriately, monitored, protected from unauthorised deletion, and tested for restoration.",[1511,7566,7568,7570],{"className":7567},[3994],[3996,7569],{"disabled":27,"type":3998}," Recovery objectives and dependencies are documented for critical services.",[1511,7572,7574,7576],{"className":7573},[3994],[3996,7575],{"disabled":27,"type":3998}," Security controls remain available or have defined alternatives during disaster recovery.",[941,7578,7579],{},[1784,7580,4022],{},[1508,7582,7583,7586],{},[1511,7584,7585],{},"Data-flow and backup architecture",[1511,7587,7588],{},"Restore test evidence",[953,7590,7592],{"id":7591},"_6-third-party-and-change-risk","6. Third-party and change risk",[941,7594,7595],{},"Include suppliers, integrations, and technical change in the security baseline.",[1508,7597,7599,7605,7611,7617],{"className":7598},[3990],[1511,7600,7602,7604],{"className":7601},[3994],[3996,7603],{"disabled":27,"type":3998}," Critical suppliers and services have owners, security requirements, data-access records, and exit plans.",[1511,7606,7608,7610],{"className":7607},[3994],[3996,7609],{"disabled":27,"type":3998}," Supplier findings, exceptions, incidents, and contract obligations are tracked to closure.",[1511,7612,7614,7616],{"className":7613},[3994],[3996,7615],{"disabled":27,"type":3998}," Changes include security impact, testing, rollback, logging, and post-deployment validation.",[1511,7618,7620,7622],{"className":7619},[3994],[3996,7621],{"disabled":27,"type":3998}," New technologies and integrations have threat-model or architecture-review criteria proportional to risk.",[941,7624,7625],{},[1784,7626,4022],{},[1508,7628,7629,7632],{},[1511,7630,7631],{},"Supplier risk register",[1511,7633,7634],{},"Security change criteria",[953,7636,7638],{"id":7637},"_7-governance-metrics-and-evidence","7. Governance, metrics, and evidence",[941,7640,7641],{},"Ensure the security programme is owned, measurable, and auditable.",[1508,7643,7645,7651,7657,7663],{"className":7644},[3990],[1511,7646,7648,7650],{"className":7647},[3994],[3996,7649],{"disabled":27,"type":3998}," Security policies, standards, control owners, exceptions, and review dates are documented.",[1511,7652,7654,7656],{"className":7653},[3994],[3996,7655],{"disabled":27,"type":3998}," Metrics cover exposure, control coverage, remediation ageing, identity risk, detection performance, incidents, and resilience.",[1511,7658,7660,7662],{"className":7659},[3994],[3996,7661],{"disabled":27,"type":3998}," Executive reporting explains business risk and decisions, not only technical activity.",[1511,7664,7666,7668],{"className":7665},[3994],[3996,7667],{"disabled":27,"type":3998}," Evidence can be reproduced consistently for audits and customer assurance requests.",[941,7670,7671],{},[1784,7672,4022],{},[1508,7674,7675,7678],{},[1511,7676,7677],{},"Control and evidence register",[1511,7679,7680],{},"Security scorecard and decision log",[953,7682,4401],{"id":4400},[941,7684,4404],{},[3354,7686,7687,7705],{},[3357,7688,7689],{},[3360,7690,7691,7693,7695,7697,7699,7701,7703],{},[3363,7692,4413],{},[3363,7694,4416],{},[3363,7696,4419],{},[3363,7698,4422],{},[3363,7700,4425],{},[3363,7702,4428],{},[3363,7704,4431],{},[3373,7706,7707,7723,7739,7755,7771],{},[3360,7708,7709,7711,7713,7715,7717,7719,7721],{},[3378,7710,4438],{},[3378,7712],{},[3378,7714],{},[3378,7716],{},[3378,7718],{},[3378,7720],{},[3378,7722],{},[3360,7724,7725,7727,7729,7731,7733,7735,7737],{},[3378,7726,4455],{},[3378,7728],{},[3378,7730],{},[3378,7732],{},[3378,7734],{},[3378,7736],{},[3378,7738],{},[3360,7740,7741,7743,7745,7747,7749,7751,7753],{},[3378,7742,4472],{},[3378,7744],{},[3378,7746],{},[3378,7748],{},[3378,7750],{},[3378,7752],{},[3378,7754],{},[3360,7756,7757,7759,7761,7763,7765,7767,7769],{},[3378,7758,4489],{},[3378,7760],{},[3378,7762],{},[3378,7764],{},[3378,7766],{},[3378,7768],{},[3378,7770],{},[3360,7772,7773,7775,7777,7779,7781,7783,7785],{},[3378,7774,4506],{},[3378,7776],{},[3378,7778],{},[3378,7780],{},[3378,7782],{},[3378,7784],{},[3378,7786],{},{"title":771,"searchDepth":991,"depth":991,"links":7788},[7789,7790,7791,7792,7793,7794,7795,7796,7797],{"id":3925,"depth":991,"text":3926},{"id":7362,"depth":991,"text":7363},{"id":7408,"depth":991,"text":7409},{"id":7454,"depth":991,"text":7455},{"id":7499,"depth":991,"text":7500},{"id":7545,"depth":991,"text":7546},{"id":7591,"depth":991,"text":7592},{"id":7637,"depth":991,"text":7638},{"id":4400,"depth":991,"text":4401},"Review asset coverage, identity controls, vulnerability management, logging, incident readiness, third-party risk, and evidence before a security improvement programme.","security-posture-readiness-checklist.html","\u002Fdownloads\u002Fen\u002Fsecurity-posture-readiness-checklist.html",[7802,7803,7804,7805],"A baseline covering assets, identity, vulnerabilities, logging, response, suppliers, and evidence.","Clear ownership and evidence prompts for each control family.","Risk-based prioritisation inputs for a remediation backlog.","A practical starting point for security architecture and tooling reviews.",{"tags":7807},[88,4546,4531],"cybersecurityAccessManagement","\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fsecurity-posture-readiness-checklist",{"title":7302,"description":7798},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fsecurity-posture-readiness-checklist",[7310,7315],"Tit2iltCIU_jFZnWUx9mlJqfFw9AOkpo6LgpsINeoOo",{"id":7815,"title":7816,"assessmentSlug":1465,"associatedSolution":79,"authors":934,"body":7817,"category":4531,"ctaLabel":4532,"date":1442,"dateModified":1442,"deliveryFormat":4533,"description":8313,"downloadFileName":8314,"downloadLabel":4536,"downloadUrl":8315,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":23,"format":4531,"gated":27,"healthCheckSlug":934,"keyTakeaways":8316,"meta":8321,"navigation":27,"newsletterTopic":1478,"path":8323,"publicType":4548,"published":27,"readTime":7295,"resourceType":4550,"schemaType":1457,"seo":8324,"slug":7821,"stem":8325,"teaser":8326,"type":4531,"__hash__":8327},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fstreaming-platform-readiness-checklist.md","Streaming Platform Readiness Checklist",{"type":938,"value":7818,"toc":8302},[7819,7822,7825,7830,7832,7874,7878,7881,7908,7912,7920,7924,7927,7954,7958,7966,7970,7973,8000,8004,8012,8016,8019,8046,8050,8058,8062,8065,8092,8096,8104,8108,8111,8138,8142,8150,8154,8157,8184,8188,8196,8198,8200],[1433,7820,7816],{"id":7821},"streaming-platform-readiness-checklist",[941,7823,7824],{},"Use the checklist for enterprise live and on-demand platforms, internal communications, training, customer portals, and event streaming. Validate assumptions with real workload and quality evidence.",[3918,7826,7827],{},[941,7828,7829],{},"Score normal operation, peak events, degraded dependencies, and recovery scenarios separately.",[953,7831,3926],{"id":3925},[3354,7833,7834,7842],{},[3357,7835,7836],{},[3360,7837,7838,7840],{},[3363,7839,1159],{},[3363,7841,3937],{},[3373,7843,7844,7850,7856,7862,7868],{},[3360,7845,7846,7848],{},[3378,7847,3944],{},[3378,7849,3947],{},[3360,7851,7852,7854],{},[3378,7853,3952],{},[3378,7855,3955],{},[3360,7857,7858,7860],{},[3378,7859,3960],{},[3378,7861,3963],{},[3360,7863,7864,7866],{},[3378,7865,3968],{},[3378,7867,3971],{},[3360,7869,7870,7872],{},[3378,7871,3976],{},[3378,7873,3979],{},[953,7875,7877],{"id":7876},"_1-workload-and-service-objectives","1. Workload and service objectives",[941,7879,7880],{},"Define demand, audiences, journeys, and measurable success.",[1508,7882,7884,7890,7896,7902],{"className":7883},[3990],[1511,7885,7887,7889],{"className":7886},[3994],[3996,7888],{"disabled":27,"type":3998}," Live, on-demand, linear, internal, external, authenticated, and public use cases are documented.",[1511,7891,7893,7895],{"className":7892},[3994],[3996,7894],{"disabled":27,"type":3998}," Concurrent users, geographic distribution, event peaks, video profiles, storage, and retention are measured or forecast.",[1511,7897,7899,7901],{"className":7898},[3994],[3996,7900],{"disabled":27,"type":3998}," Availability, start time, buffering, failure, recovery, and support objectives are agreed.",[1511,7903,7905,7907],{"className":7904},[3994],[3996,7906],{"disabled":27,"type":3998}," Business-critical events and blackout constraints are identified.",[941,7909,7910],{},[1784,7911,4022],{},[1508,7913,7914,7917],{},[1511,7915,7916],{},"Workload profile",[1511,7918,7919],{},"Service-level objectives",[953,7921,7923],{"id":7922},"_2-architecture-capacity-and-resilience","2. Architecture, capacity, and resilience",[941,7925,7926],{},"Review end-to-end design and failure tolerance.",[1508,7928,7930,7936,7942,7948],{"className":7929},[3990],[1511,7931,7933,7935],{"className":7932},[3994],[3996,7934],{"disabled":27,"type":3998}," Ingest, encoding, packaging, origin, storage, CDN, player, identity, analytics, and integration components are mapped.",[1511,7937,7939,7941],{"className":7938},[3994],[3996,7940],{"disabled":27,"type":3998}," Capacity models include peak concurrency, bitrate ladders, redundancy, failover, and headroom.",[1511,7943,7945,7947],{"className":7944},[3994],[3996,7946],{"disabled":27,"type":3998}," Critical dependencies have timeouts, retries, degradation, failover, and recovery behavior.",[1511,7949,7951,7953],{"className":7950},[3994],[3996,7952],{"disabled":27,"type":3998}," Load, failover, and recovery tests reflect realistic event conditions.",[941,7955,7956],{},[1784,7957,4022],{},[1508,7959,7960,7963],{},[1511,7961,7962],{},"End-to-end architecture",[1511,7964,7965],{},"Capacity and resilience test results",[953,7967,7969],{"id":7968},"_3-identity-access-and-content-protection","3. Identity, access, and content protection",[941,7971,7972],{},"Protect access, entitlements, administration, and media assets.",[1508,7974,7976,7982,7988,7994],{"className":7975},[3990],[1511,7977,7979,7981],{"className":7978},[3994],[3996,7980],{"disabled":27,"type":3998}," Authentication, SSO, MFA, session, entitlement, and revocation behavior are defined.",[1511,7983,7985,7987],{"className":7984},[3994],[3996,7986],{"disabled":27,"type":3998}," Administrative roles use least privilege, separation of duties, and audit logging.",[1511,7989,7991,7993],{"className":7990},[3994],[3996,7992],{"disabled":27,"type":3998}," Signed URLs, tokens, DRM, geo restrictions, watermarking, or equivalent controls match content risk.",[1511,7995,7997,7999],{"className":7996},[3994],[3996,7998],{"disabled":27,"type":3998}," Keys, certificates, secrets, and content-protection policies have owners and rotation procedures.",[941,8001,8002],{},[1784,8003,4022],{},[1508,8005,8006,8009],{},[1511,8007,8008],{},"Access and entitlement design",[1511,8010,8011],{},"Content-protection control matrix",[953,8013,8015],{"id":8014},"_4-privacy-retention-and-compliance","4. Privacy, retention, and compliance",[941,8017,8018],{},"Review personal data, analytics, recordings, and content rights.",[1508,8020,8022,8028,8034,8040],{"className":8021},[3990],[1511,8023,8025,8027],{"className":8024},[3994],[3996,8026],{"disabled":27,"type":3998}," Viewer, device, analytics, chat, registration, and support data have documented purposes and retention.",[1511,8029,8031,8033],{"className":8030},[3994],[3996,8032],{"disabled":27,"type":3998}," Consent, privacy notices, access requests, deletion, and regional transfer requirements are implemented.",[1511,8035,8037,8039],{"className":8036},[3994],[3996,8038],{"disabled":27,"type":3998}," Recording, distribution, accessibility, licensing, and content-rights decisions are documented.",[1511,8041,8043,8045],{"className":8042},[3994],[3996,8044],{"disabled":27,"type":3998}," Logs and analytics minimise unnecessary personal data while preserving operational evidence.",[941,8047,8048],{},[1784,8049,4022],{},[1508,8051,8052,8055],{},[1511,8053,8054],{},"Data-flow and retention register",[1511,8056,8057],{},"Content-rights checklist",[953,8059,8061],{"id":8060},"_5-device-and-delivery-quality","5. Device and delivery quality",[941,8063,8064],{},"Validate playback across target environments and network conditions.",[1508,8066,8068,8074,8080,8086],{"className":8067},[3990],[1511,8069,8071,8073],{"className":8070},[3994],[3996,8072],{"disabled":27,"type":3998}," Supported browsers, operating systems, mobile devices, managed endpoints, TVs, and accessibility technologies are defined.",[1511,8075,8077,8079],{"className":8076},[3994],[3996,8078],{"disabled":27,"type":3998}," Codec, container, protocol, subtitle, caption, audio, and adaptive-bitrate profiles are tested.",[1511,8081,8083,8085],{"className":8082},[3994],[3996,8084],{"disabled":27,"type":3998}," Startup time, buffering, playback failures, latency, and quality switches are measured by device, location, and network.",[1511,8087,8089,8091],{"className":8088},[3994],[3996,8090],{"disabled":27,"type":3998}," CDN routing, caching, purge, origin shielding, and failover are validated.",[941,8093,8094],{},[1784,8095,4022],{},[1508,8097,8098,8101],{},[1511,8099,8100],{},"Device coverage matrix",[1511,8102,8103],{},"Quality-of-experience test report",[953,8105,8107],{"id":8106},"_6-monitoring-and-incident-operations","6. Monitoring and incident operations",[941,8109,8110],{},"Ensure teams can detect and resolve issues during critical delivery windows.",[1508,8112,8114,8120,8126,8132],{"className":8113},[3990],[1511,8115,8117,8119],{"className":8116},[3994],[3996,8118],{"disabled":27,"type":3998}," Monitoring covers ingest, encoders, packaging, origin, storage, CDN, player, authentication, APIs, and third-party dependencies.",[1511,8121,8123,8125],{"className":8122},[3994],[3996,8124],{"disabled":27,"type":3998}," Synthetic probes and real-user telemetry detect regional and device-specific failures.",[1511,8127,8129,8131],{"className":8128},[3994],[3996,8130],{"disabled":27,"type":3998}," Alerts identify service impact, owner, affected audience, likely layer, and runbook.",[1511,8133,8135,8137],{"className":8134},[3994],[3996,8136],{"disabled":27,"type":3998}," Event command, incident communication, escalation, vendor support, and recovery procedures are rehearsed.",[941,8139,8140],{},[1784,8141,4022],{},[1508,8143,8144,8147],{},[1511,8145,8146],{},"Operational dashboard",[1511,8148,8149],{},"Event and incident runbooks",[953,8151,8153],{"id":8152},"_7-ownership-lifecycle-and-cost","7. Ownership, lifecycle, and cost",[941,8155,8156],{},"Make platform accountability and sustainable operation explicit.",[1508,8158,8160,8166,8172,8178],{"className":8159},[3990],[1511,8161,8163,8165],{"className":8162},[3994],[3996,8164],{"disabled":27,"type":3998}," Business, product, platform, security, operations, content, and vendor responsibilities are assigned.",[1511,8167,8169,8171],{"className":8168},[3994],[3996,8170],{"disabled":27,"type":3998}," Release, configuration, certificate, player, codec, device, and vendor lifecycle processes are documented.",[1511,8173,8175,8177],{"className":8174},[3994],[3996,8176],{"disabled":27,"type":3998}," Cost reporting covers encoding, storage, egress, CDN, licenses, support, and peak-event capacity.",[1511,8179,8181,8183],{"className":8180},[3994],[3996,8182],{"disabled":27,"type":3998}," Unit costs and quality outcomes inform architecture, retention, and delivery decisions.",[941,8185,8186],{},[1784,8187,4022],{},[1508,8189,8190,8193],{},[1511,8191,8192],{},"Operating model",[1511,8194,8195],{},"Lifecycle and cost scorecard",[953,8197,4401],{"id":4400},[941,8199,4404],{},[3354,8201,8202,8220],{},[3357,8203,8204],{},[3360,8205,8206,8208,8210,8212,8214,8216,8218],{},[3363,8207,4413],{},[3363,8209,4416],{},[3363,8211,4419],{},[3363,8213,4422],{},[3363,8215,4425],{},[3363,8217,4428],{},[3363,8219,4431],{},[3373,8221,8222,8238,8254,8270,8286],{},[3360,8223,8224,8226,8228,8230,8232,8234,8236],{},[3378,8225,4438],{},[3378,8227],{},[3378,8229],{},[3378,8231],{},[3378,8233],{},[3378,8235],{},[3378,8237],{},[3360,8239,8240,8242,8244,8246,8248,8250,8252],{},[3378,8241,4455],{},[3378,8243],{},[3378,8245],{},[3378,8247],{},[3378,8249],{},[3378,8251],{},[3378,8253],{},[3360,8255,8256,8258,8260,8262,8264,8266,8268],{},[3378,8257,4472],{},[3378,8259],{},[3378,8261],{},[3378,8263],{},[3378,8265],{},[3378,8267],{},[3378,8269],{},[3360,8271,8272,8274,8276,8278,8280,8282,8284],{},[3378,8273,4489],{},[3378,8275],{},[3378,8277],{},[3378,8279],{},[3378,8281],{},[3378,8283],{},[3378,8285],{},[3360,8287,8288,8290,8292,8294,8296,8298,8300],{},[3378,8289,4506],{},[3378,8291],{},[3378,8293],{},[3378,8295],{},[3378,8297],{},[3378,8299],{},[3378,8301],{},{"title":771,"searchDepth":991,"depth":991,"links":8303},[8304,8305,8306,8307,8308,8309,8310,8311,8312],{"id":3925,"depth":991,"text":3926},{"id":7876,"depth":991,"text":7877},{"id":7922,"depth":991,"text":7923},{"id":7968,"depth":991,"text":7969},{"id":8014,"depth":991,"text":8015},{"id":8060,"depth":991,"text":8061},{"id":8106,"depth":991,"text":8107},{"id":8152,"depth":991,"text":8153},{"id":4400,"depth":991,"text":4401},"Review workload, architecture, capacity, resilience, access protection, content security, device coverage, delivery quality, monitoring, ownership, and cost before scaling or migrating a streaming platform.","streaming-platform-readiness-checklist.html","\u002Fdownloads\u002Fen\u002Fstreaming-platform-readiness-checklist.html",[8317,8318,8319,8320],"Architecture and capacity checks for live and on-demand workloads.","Security, identity, entitlement, and content-protection controls.","Device, playback, CDN, and quality-of-experience readiness.","Operational monitoring, incident, ownership, lifecycle, and cost criteria.",{"tags":8322},[79,4546,4531],"\u002Flocales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fstreaming-platform-readiness-checklist",{"title":7816,"description":8313},"locales\u002Fenglish\u002Fresources\u002Fchecklists\u002Fstreaming-platform-readiness-checklist",[7824,7829],"D6EcFrNYAJgkd1dIDSk1bWlIg_VILuwrlIUuttDGAk8",{"id":8329,"title":8330,"assessmentSlug":934,"associatedSolution":97,"authors":8331,"body":8332,"category":8894,"ctaLabel":8895,"date":8896,"dateModified":8896,"deliveryFormat":8897,"description":8898,"downloadFileName":8899,"downloadLabel":8900,"downloadUrl":8901,"excerpt":771,"exclusive":27,"exclusiveLabel":4538,"extension":1412,"featured":27,"format":8894,"gated":27,"healthCheckSlug":934,"keyTakeaways":8902,"meta":8907,"navigation":27,"newsletterTopic":1452,"path":8912,"publicType":644,"published":27,"readTime":8913,"resourceType":8914,"schemaType":1457,"seo":8915,"slug":8918,"stem":8919,"teaser":8920,"type":8894,"__hash__":8923},"resourceEntries_en\u002Flocales\u002Fenglish\u002Fresources\u002Fwhitepapers\u002Fai-starts-with-data-modelling-model-first.md","AI Starts with Data Modelling: Why 'Model First' Matters More Than Ever",[45],{"type":938,"value":8333,"toc":8856},[8334,8337,8340,8346,8350,8353,8356,8388,8391,8395,8398,8421,8424,8427,8431,8441,8444,8483,8486,8490,8494,8497,8500,8504,8507,8510,8514,8517,8520,8524,8527,8530,8534,8537,8540,8544,8548,8551,8555,8558,8562,8565,8569,8572,8576,8579,8583,8586,8636,8640,8643,8713,8716,8720,8724,8727,8731,8734,8738,8741,8745,8748,8752,8755,8759,8762,8765,8769,8773,8776,8780,8783,8787,8790,8794,8797,8801,8804,8808,8811,8843,8846,8848,8851],[1433,8335,8330],{"id":8336},"ai-starts-with-data-modelling-why-model-first-matters-more-than-ever",[941,8338,8339],{},"Everyone wants AI outcomes, but many organisations are building on fragmented, poorly understood data foundations. Before AI can deliver dependable value, the organisation needs confidence in the structure, meaning, quality, ownership, and permitted use of the data on which models and agents depend.",[941,8341,3211,8342,8345],{},[1784,8343,8344],{},"model-first"," approach addresses that problem before it becomes hidden inside transformation code, prompts, embeddings, feature pipelines, or application-specific workarounds. It is not a return to slow, document-heavy architecture. It is a disciplined decision sequence: define the business decision, identify the concepts and relationships involved, establish authoritative meaning and ownership, map the relevant sources, and then implement the smallest viable technical model with measurable controls.",[953,8347,8349],{"id":8348},"executive-summary","Executive summary",[941,8351,8352],{},"AI increases the cost of ambiguity. A dashboard may expose an inconsistent metric to one team. An AI assistant can reproduce the same inconsistency at scale, in natural language, across many decisions. A poorly documented join may affect one report; the same join embedded in retrieval or feature engineering can shape thousands of automated responses or predictions.",[941,8354,8355],{},"Model first creates a shared contract between business, data, architecture, engineering, governance, security, and AI teams. That contract should answer six questions before implementation becomes difficult to change:",[1695,8357,8358,8363,8368,8373,8378,8383],{},[1511,8359,8360],{},[1784,8361,8362],{},"Which business concepts and decisions are in scope?",[1511,8364,8365],{},[1784,8366,8367],{},"How are those concepts related, identified, and versioned?",[1511,8369,8370],{},[1784,8371,8372],{},"Which source data is authoritative for each attribute and event?",[1511,8374,8375],{},[1784,8376,8377],{},"Who owns definitions, quality thresholds, access decisions, and lifecycle rules?",[1511,8379,8380],{},[1784,8381,8382],{},"How do changes propagate through data products, analytics, and AI applications?",[1511,8384,8385],{},[1784,8386,8387],{},"What evidence demonstrates that the data remains trustworthy in operation?",[941,8389,8390],{},"The outcome is not a diagram for its own sake. The outcome is a controlled foundation for reuse, traceability, automation, and change.",[953,8392,8394],{"id":8393},"_1-ai-readiness-is-a-data-structure-problem-before-it-is-a-model-selection-problem","1. AI readiness is a data-structure problem before it is a model-selection problem",[941,8396,8397],{},"Many AI initiatives begin with a tool choice: a foundation model, vector database, orchestration framework, feature store, or managed AI service. Those choices matter, but they do not resolve basic questions such as:",[1508,8399,8400,8403,8406,8409,8412,8415,8418],{},[1511,8401,8402],{},"whether “customer”, “account”, “contract”, and “party” refer to the same or different entities;",[1511,8404,8405],{},"which identifier survives mergers, migrations, or source-system replacement;",[1511,8407,8408],{},"whether revenue is booked, billed, recognised, forecast, or collected revenue;",[1511,8410,8411],{},"whether a document is current, superseded, confidential, or legally restricted;",[1511,8413,8414],{},"whether a timestamp represents occurrence, ingestion, processing, or correction;",[1511,8416,8417],{},"what happens when two sources conflict and which one is authoritative;",[1511,8419,8420],{},"whether an AI application is permitted to combine particular attributes for a specific purpose.",[941,8422,8423],{},"Without explicit answers, teams infer structure from whatever data is easiest to access. Data scientists create feature definitions independently. Retrieval teams chunk documents without authoritative metadata. Application teams encode business rules in prompts. Governance is applied after the pilot rather than shaping the design before the assumptions become dependencies.",[941,8425,8426],{},"Model first reverses that sequence. It makes the essential data decisions visible while they are still economical to change.",[953,8428,8430],{"id":8429},"_2-what-model-first-means-in-a-modern-architecture","2. What “model first” means in a modern architecture",[941,8432,8433,8434,8437,8438,951],{},"Model first does ",[1784,8435,8436],{},"not"," mean designing a complete enterprise data model before delivering anything. A practical model-first approach is ",[1784,8439,8440],{},"use-case bounded, iterative, and executable",[941,8442,8443],{},"For each priority AI use case, create only the modelling depth needed to support a dependable decision:",[1508,8445,8446,8453,8459,8465,8471,8477],{},[1511,8447,8448,8449,8452],{},"a ",[1784,8450,8451],{},"conceptual model"," to align business language and scope;",[1511,8454,8448,8455,8458],{},[1784,8456,8457],{},"logical model"," to define entities, relationships, rules, cardinality, identity, and lifecycle independently of technology;",[1511,8460,8448,8461,8464],{},[1784,8462,8463],{},"physical or data-product model"," to implement storage, APIs, events, analytical tables, graph structures, or document metadata;",[1511,8466,8448,8467,8470],{},[1784,8468,8469],{},"semantic model"," to define measures, dimensions, hierarchies, and business calculations;",[1511,8472,8448,8473,8476],{},[1784,8474,8475],{},"retrieval model"," to define document boundaries, metadata, permissions, provenance, freshness, and ranking signals;",[1511,8478,8448,8479,8482],{},[1784,8480,8481],{},"governance model"," to connect ownership, policy, classification, quality, access, retention, and evidence.",[941,8484,8485],{},"These are different views of the same business reality. Their value comes from traceable relationships between them rather than isolated modelling artefacts.",[953,8487,8489],{"id":8488},"_3-five-foundations-of-ai-ready-data","3. Five foundations of AI-ready data",[2597,8491,8493],{"id":8492},"_31-stable-business-semantics","3.1 Stable business semantics",[941,8495,8496],{},"AI systems need more than labels. They need definitions with scope, examples, exclusions, ownership, and change history. A useful business term explains what the concept means, which process creates it, which identifier represents it, which calculations depend on it, who approves changes, and where the definition is implemented.",[941,8498,8499],{},"This becomes critical with natural-language interfaces. If a user asks an assistant for “active customers”, the organisation must know whether that means customers with a current contract, a recent transaction, a login in the last 90 days, or another approved definition.",[2597,8501,8503],{"id":8502},"_32-explicit-relationships-and-constraints","3.2 Explicit relationships and constraints",[941,8505,8506],{},"Many AI errors originate in relationships. A flat export can hide that one party has multiple roles, one contract covers several services, or one asset moves between organisational units over time. Logical models make these constraints explicit before they are reduced to joins or prompt instructions.",[941,8508,8509],{},"Key decisions include cardinality, mandatory and optional participation, temporal validity, hierarchy, reference-data ownership, identity resolution, event ordering, and late-arriving corrections.",[2597,8511,8513],{"id":8512},"_33-traceable-source-to-use-mappings","3.3 Traceable source-to-use mappings",[941,8515,8516],{},"An AI output should be traceable to authoritative sources and transformation decisions. Technical lineage alone is insufficient. The organisation needs a mapping that connects business concepts, source attributes, transformation and quality rules, semantic or feature definitions, retrieval metadata, AI applications, accountable owners, and approval evidence.",[941,8518,8519],{},"That mapping makes impact analysis possible. When a source field, definition, policy, or model changes, teams can identify which reports, features, prompts, agents, and downstream decisions require review.",[2597,8521,8523],{"id":8522},"_34-measurable-quality-and-fitness-for-purpose","3.4 Measurable quality and fitness for purpose",[941,8525,8526],{},"“High-quality data” is too vague to operate. Quality rules must attach to specific concepts, relationships, and uses. A critical attribute may require completeness and validity; an event stream may require timeliness and ordering; a retrieval corpus may require freshness, classification, permissions, and document-version controls.",[941,8528,8529],{},"Each threshold should define how it is calculated, where it is enforced, who owns remediation, how exceptions are handled, what happens when the threshold is breached, and whether the data remains fit for the AI use case.",[2597,8531,8533],{"id":8532},"_35-governed-change","3.5 Governed change",[941,8535,8536],{},"AI-ready data is not a one-time state. Sources, policies, products, models, prompts, and use cases change continuously. The model therefore needs versioning, review, compatibility rules, migration planning, deprecation, and evidence of approved change.",[941,8538,8539],{},"A model change should trigger the relevant downstream checks: semantic calculations, embeddings, feature pipelines, access policies, quality rules, and user-facing definitions.",[953,8541,8543],{"id":8542},"_4-where-ai-initiatives-fail-without-a-model-first-foundation","4. Where AI initiatives fail without a model-first foundation",[2597,8545,8547],{"id":8546},"rag-without-authoritative-metadata","RAG without authoritative metadata",[941,8549,8550],{},"Retrieval can return technically relevant but obsolete, restricted, or contextually wrong documents. Chunking alone cannot distinguish an approved policy from a draft or a current instruction from a superseded version. A retrieval model needs document type, owner, effective date, version, classification, jurisdiction, product, process, and access metadata.",[2597,8552,8554],{"id":8553},"features-with-the-same-name-but-different-meaning","Features with the same name but different meaning",[941,8556,8557],{},"Two teams may both create “customer risk score” or “days since last activity” using different sources and time windows. The results cannot be compared, reused, or governed reliably. Logical and semantic modelling make grain, temporal behaviour, calculation, and ownership explicit.",[2597,8559,8561],{"id":8560},"agents-automating-an-unclear-process","Agents automating an unclear process",[941,8563,8564],{},"An agent cannot compensate for undefined decision rights. If a process has no authoritative status model, escalation rule, or exception path, automation reproduces ambiguity faster. Process and state models are part of the data foundation.",[2597,8566,8568],{"id":8567},"knowledge-graphs-with-inconsistent-identity","Knowledge graphs with inconsistent identity",[941,8570,8571],{},"Graphs expose valuable relationships only when identity, role, relationship type, temporal validity, and provenance are controlled. Otherwise the graph connects records that look similar without proving they represent the same real-world entity.",[2597,8573,8575],{"id":8574},"governance-added-after-the-pilot","Governance added after the pilot",[941,8577,8578],{},"Pilots often use broad access, curated data, and experts who understand hidden assumptions. Production introduces scale, sensitive data, changing sources, support obligations, and users who do not share that context. Governance added afterwards becomes remediation rather than enablement.",[953,8580,8582],{"id":8581},"_5-a-model-first-delivery-sequence","5. A model-first delivery sequence",[941,8584,8585],{},"A practical sequence keeps modelling close to implementation:",[1695,8587,8588,8594,8600,8606,8612,8618,8624,8630],{},[1511,8589,8590,8593],{},[1784,8591,8592],{},"Start with the decision, not the dataset."," Define the user outcome, decision owner, acceptable uncertainty, response time, and consequence of a wrong answer.",[1511,8595,8596,8599],{},[1784,8597,8598],{},"Identify the minimum concept set."," Model only the entities, events, documents, measures, and relationships required by the use case.",[1511,8601,8602,8605],{},[1784,8603,8604],{},"Agree definitions and ownership."," Assign accountable owners for critical terms, rules, quality thresholds, access, and lifecycle.",[1511,8607,8608,8611],{},[1784,8609,8610],{},"Build the logical model."," Define keys, cardinality, state, temporal behaviour, reference data, constraints, and business rules independently of the target platform.",[1511,8613,8614,8617],{},[1784,8615,8616],{},"Map sources and evidence."," Connect critical concepts to source attributes, transformation logic, quality rules, lineage, and approval evidence.",[1511,8619,8620,8623],{},[1784,8621,8622],{},"Design the implementation model."," Choose the necessary tables, events, APIs, data products, graph structures, features, document metadata, embeddings, or semantic measures while preserving traceability.",[1511,8625,8626,8629],{},[1784,8627,8628],{},"Implement controls with the pipeline."," Validation, observability, access enforcement, retention, change detection, and exception handling belong in delivery.",[1511,8631,8632,8635],{},[1784,8633,8634],{},"Test business meaning as well as technical correctness."," Validate representative scenarios, edge cases, time periods, jurisdictions, and access contexts with business subject-matter experts.",[953,8637,8639],{"id":8638},"_6-governance-that-accelerates-delivery","6. Governance that accelerates delivery",[941,8641,8642],{},"Model-first governance should focus on decisions and evidence, not meetings and documents.",[3354,8644,8645,8655],{},[3357,8646,8647],{},[3360,8648,8649,8652],{},[3363,8650,8651],{},"Role",[3363,8653,8654],{},"Core accountability",[3373,8656,8657,8665,8673,8681,8689,8697,8705],{},[3360,8658,8659,8662],{},[3378,8660,8661],{},"Business owner",[3378,8663,8664],{},"Meaning, scope, acceptable use, business outcome",[3360,8666,8667,8670],{},[3378,8668,8669],{},"Data owner",[3378,8671,8672],{},"Authoritative sources, quality thresholds, access, lifecycle",[3360,8674,8675,8678],{},[3378,8676,8677],{},"Data steward",[3378,8679,8680],{},"Definitions, mappings, issues, evidence, day-to-day maintenance",[3360,8682,8683,8686],{},[3378,8684,8685],{},"Data modeller \u002F architect",[3378,8687,8688],{},"Conceptual, logical, semantic, and implementation traceability",[3360,8690,8691,8694],{},[3378,8692,8693],{},"Data \u002F platform engineer",[3378,8695,8696],{},"Structures, transformations, controls, observability",[3360,8698,8699,8702],{},[3378,8700,8701],{},"AI product owner",[3378,8703,8704],{},"Use case, evaluation criteria, operational risk, user feedback",[3360,8706,8707,8710],{},[3378,8708,8709],{},"Security \u002F privacy",[3378,8711,8712],{},"Classification, permitted use, access, retention, control evidence",[941,8714,8715],{},"The level of governance should be proportional to risk. A low-risk internal assistant may need an approved corpus and clear ownership. A customer-facing or regulated decision may require formal validation, versioned evidence, purpose-based access, human review, and ongoing monitoring.",[953,8717,8719],{"id":8718},"_7-applying-model-first-across-the-modern-data-stack","7. Applying model first across the modern data stack",[2597,8721,8723],{"id":8722},"warehouses-and-lakehouses","Warehouses and lakehouses",[941,8725,8726],{},"Define grain, keys, relationships, history, and rules before implementing dimensional models, data vault structures, wide tables, or curated lakehouse layers.",[2597,8728,8730],{"id":8729},"data-products-and-apis","Data products and APIs",[941,8732,8733],{},"Treat the model as a contract: meaning, schema, quality, ownership, service level, compatibility, and permitted use. Consumers should not need to reverse-engineer producer assumptions.",[2597,8735,8737],{"id":8736},"knowledge-graphs","Knowledge graphs",[941,8739,8740],{},"Define entity types, relationship semantics, identity, provenance, and temporal validity before ingestion. The graph should implement known semantics rather than inventing them dynamically.",[2597,8742,8744],{"id":8743},"vector-stores-and-retrieval-pipelines","Vector stores and retrieval pipelines",[941,8746,8747],{},"Define document classes, chunking boundaries, metadata, permissions, versioning, provenance, and lifecycle. Retrieval evaluation can then be tied to approved sources and contexts.",[2597,8749,8751],{"id":8750},"feature-stores-and-ml-pipelines","Feature stores and ML pipelines",[941,8753,8754],{},"Define feature meaning, grain, event time, calculation window, leakage constraints, and ownership. Reuse becomes possible because a feature is a governed contract rather than a code fragment.",[953,8756,8758],{"id":8757},"_8-the-economic-case-reduce-rework-before-scaling-consumption","8. The economic case: reduce rework before scaling consumption",[941,8760,8761],{},"Weak modelling costs appear later as repeated interpretation and reconciliation. Typical cost drivers are duplicate transformations, inconsistent KPIs, manual investigation of unexplained AI answers, repeated privacy review because lineage is unclear, failed reuse because data lacks contracts, migrations delayed by undocumented dependencies, and retraining or corpus rebuilding after unplanned source changes.",[941,8763,8764],{},"Model first moves critical decisions to a point where they are cheaper to change and easier to reuse. That is why modelling remains economically relevant even when infrastructure and AI services are increasingly automated.",[953,8766,8768],{"id":8767},"_9-a-practical-90-day-implementation-path","9. A practical 90-day implementation path",[2597,8770,8772],{"id":8771},"days-115-frame-the-use-case","Days 1–15 — frame the use case",[941,8774,8775],{},"Deliver: one prioritised AI use case, decision owner, success and risk criteria, minimum concept and source scope, regulatory constraints, and a list of unresolved assumptions.",[2597,8777,8779],{"id":8778},"days-1635-establish-semantic-and-logical-foundations","Days 16–35 — establish semantic and logical foundations",[941,8781,8782],{},"Deliver: conceptual model, approved glossary entries, logical model with keys and relationships, named business and data owners, source-to-concept mappings, and initial quality\u002Faccess rules.",[2597,8784,8786],{"id":8785},"days-3660-implement-the-usable-data-contract","Days 36–60 — implement the usable data contract",[941,8788,8789],{},"Deliver: physical\u002Fsemantic\u002Fretrieval\u002Ffeature model, versioned schemas, automated validation and observability, source-to-AI lineage, and an exception\u002Fremediation workflow.",[2597,8791,8793],{"id":8792},"days-6175-evaluate-meaning-risk-and-operability","Days 61–75 — evaluate meaning, risk, and operability",[941,8795,8796],{},"Deliver: representative evaluation set, tests for definitions and permissions, operational dashboards, incident and rollback procedures, and documented residual risks.",[2597,8798,8800],{"id":8799},"days-7690-scale-deliberately","Days 76–90 — scale deliberately",[941,8802,8803],{},"Deliver: evidence-based production approval, reusable model and data-product assets, backlog for adjacent concepts and sources, adoption\u002Fquality metrics, and a review cadence for model, source, and policy changes.",[953,8805,8807],{"id":8806},"_10-model-first-readiness-questions","10. Model-first readiness questions",[941,8809,8810],{},"Before expanding an AI pilot, ask:",[1508,8812,8813,8816,8819,8822,8825,8828,8831,8834,8837,8840],{},[1511,8814,8815],{},"Are critical business concepts defined with owners, scope, examples, and exclusions?",[1511,8817,8818],{},"Are entity identity, relationships, grain, and temporal behaviour explicit?",[1511,8820,8821],{},"Can important outputs be traced to authoritative sources and transformation rules?",[1511,8823,8824],{},"Are quality thresholds tied to operational consequences and the AI use case?",[1511,8826,8827],{},"Are document versions, permissions, classifications, and effective dates available to retrieval?",[1511,8829,8830],{},"Are semantic measures and features defined once and reused consistently?",[1511,8832,8833],{},"Is there a governed process for model, schema, source, and policy changes?",[1511,8835,8836],{},"Can teams identify which AI applications are affected by a data-model change?",[1511,8838,8839],{},"Are uncertainty, exceptions, and human escalation represented in the process and data model?",[1511,8841,8842],{},"Is operational evidence available for access, quality, lineage, freshness, and incident handling?",[941,8844,8845],{},"If several answers are unclear, scaling the AI layer will scale uncertainty rather than value.",[953,8847,1607],{"id":1606},[941,8849,8850],{},"AI does not remove the need for data modelling. It makes the consequences of weak modelling more visible, faster, and more expensive. Organisations that move sustainably are not those that skip structure, meaning, and governance. They make the necessary decisions early, keep scope proportionate, connect models directly to implementation, and reuse the resulting contracts across analytics, automation, and AI.",[941,8852,8853],{},[1784,8854,8855],{},"Model first is not a documentation phase. It is a delivery discipline for trusted, explainable, changeable, and economically scalable AI systems.",{"title":771,"searchDepth":991,"depth":991,"links":8857},[8858,8859,8860,8861,8868,8875,8876,8877,8884,8885,8892,8893],{"id":8348,"depth":991,"text":8349},{"id":8393,"depth":991,"text":8394},{"id":8429,"depth":991,"text":8430},{"id":8488,"depth":991,"text":8489,"children":8862},[8863,8864,8865,8866,8867],{"id":8492,"depth":997,"text":8493},{"id":8502,"depth":997,"text":8503},{"id":8512,"depth":997,"text":8513},{"id":8522,"depth":997,"text":8523},{"id":8532,"depth":997,"text":8533},{"id":8542,"depth":991,"text":8543,"children":8869},[8870,8871,8872,8873,8874],{"id":8546,"depth":997,"text":8547},{"id":8553,"depth":997,"text":8554},{"id":8560,"depth":997,"text":8561},{"id":8567,"depth":997,"text":8568},{"id":8574,"depth":997,"text":8575},{"id":8581,"depth":991,"text":8582},{"id":8638,"depth":991,"text":8639},{"id":8718,"depth":991,"text":8719,"children":8878},[8879,8880,8881,8882,8883],{"id":8722,"depth":997,"text":8723},{"id":8729,"depth":997,"text":8730},{"id":8736,"depth":997,"text":8737},{"id":8743,"depth":997,"text":8744},{"id":8750,"depth":997,"text":8751},{"id":8757,"depth":991,"text":8758},{"id":8767,"depth":991,"text":8768,"children":8886},[8887,8888,8889,8890,8891],{"id":8771,"depth":997,"text":8772},{"id":8778,"depth":997,"text":8779},{"id":8785,"depth":997,"text":8786},{"id":8792,"depth":997,"text":8793},{"id":8799,"depth":997,"text":8800},{"id":8806,"depth":991,"text":8807},{"id":1606,"depth":991,"text":1607},"whitepaper","Get the whitepaper","2026-08-24","Print-ready HTML whitepaper","Build trusted, AI-ready data by making structure, meaning, ownership, quality, lineage, and change explicit before scaling models, agents, and automation.","ai-starts-with-data-modelling-model-first.html","Download whitepaper","\u002Fdownloads\u002Fen\u002Fai-starts-with-data-modelling-model-first.html",[8903,8904,8905,8906],"A practical definition of model first for modern data, analytics, and AI programmes.","The connection between conceptual, logical, physical, semantic, retrieval, and governance models.","Concrete controls for trusted AI-ready data, including ownership, lineage, quality, access, and change management.","A 90-day implementation path with clear outputs, accountable roles, and evidence.",{"tags":8908},[97,8909,100,8910,8911],"artificial-intelligence","enterprise-architecture","ai-readiness","\u002Flocales\u002Fenglish\u002Fresources\u002Fwhitepapers\u002Fai-starts-with-data-modelling-model-first","16 min read","Whitepaper",{"title":8916,"description":8917},"AI Starts with Data Modelling: Why Model First Matters","A practical model-first approach for trusted, governed, scalable AI-ready data foundations.","ai-starts-with-data-modelling-model-first","locales\u002Fenglish\u002Fresources\u002Fwhitepapers\u002Fai-starts-with-data-modelling-model-first",[8921,8922],"Everyone wants AI outcomes, but many organisations are building on fragmented, poorly understood data foundations. The result is avoidable rework, inconsistent answers, weak controls, and pilots that cannot be operated with confidence.","A model-first approach does not mean months of abstract design before delivery. It means making the minimum necessary decisions about business meaning, structure, ownership, lineage, quality, and change before those decisions are buried inside pipelines, prompts, vector stores, or application code.","Ccn20fk9fLQdBjaUNy34otqt8saRogWJHnb4N_JY3xs",{"id":8925,"title":8926,"body":8927,"dateModified":934,"datePublished":934,"description":771,"extension":1412,"lastUpdated":934,"meta":8964,"navigation":27,"path":8965,"seo":8966,"stem":8967,"__hash__":8968},"resourceTypePages_en\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs\u002Findex.md","Blog Detail",{"type":938,"value":8928,"toc":8962},[8929,8942,8945],[8930,8931,8932,8938],"blog-head",{},[8933,8934,8935],"template",{"v-slot:back-label":771},[941,8936,8937],{},"Back to Resources",[8933,8939,8940],{"v-slot:label":771},[941,8941,291],{},[8943,8944],"blog-body",{},[8946,8947,8948,8953,8958],"bottom-conversion-panel",{},[8933,8949,8950],{"v-slot:title":771},[941,8951,8952],{},"Ready to move forward?",[8933,8954,8955],{"v-slot:description":771},[941,8956,8957],{},"Talk to our experts about your specific challenges. We provide honest assessments and actionable recommendations.",[8933,8959,8960],{"v-slot:primaryLabel":771},[941,8961,195],{},{"title":771,"searchDepth":991,"depth":991,"links":8963},[],{},"\u002Flocales\u002Fenglish\u002Fresources\u002Fblogs",{"title":8926,"description":771},"locales\u002Fenglish\u002Fresources\u002Fblogs\u002Findex","H9wOwVWDq1mVkUChMdJAA9_xaq0lKod0X6bcq0vTIAE",1788552590585]