{"id":14635,"date":"2026-04-13T19:00:18","date_gmt":"2026-04-13T17:00:18","guid":{"rendered":"https:\/\/tricise.com\/docu\/automic\/services\/consulting-packages\/automic-system-health-check\/full-guide\/"},"modified":"2026-04-14T18:23:35","modified_gmt":"2026-04-14T16:23:35","slug":"guide-complet","status":"publish","type":"docs","link":"https:\/\/tricise.com\/fr\/docu\/automic\/services\/consulting-packages\/automic-system-health-check\/full-guide\/","title":{"rendered":"Guide complet"},"content":{"rendered":"\n<style>\n.tcs-hover-benefit { transition: border-color 0.15s ease, transform 0.15s ease; }\n.tcs-hover-benefit:hover { border-color: #A32D2D !important; transform: translateY(-2px); }\n.tcs-hover-btn-primary { transition: background-color 0.15s ease, transform 0.15s ease; }\n.tcs-hover-btn-primary:hover { background-color: #A3192A !important; transform: translateY(-1px); }\n.tcs-hover-btn-secondary { transition: background-color 0.15s ease, transform 0.15s ease; }\n.tcs-hover-btn-secondary:hover { background-color: #FCEBEB !important; transform: translateY(-1px); }\n.tcs-hover-btn-ghost { transition: background-color 0.15s ease, border-color 0.15s ease, transform 0.15s ease; }\n.tcs-hover-btn-ghost:hover { background-color: rgba(255,255,255,0.08) !important; border-color: #9B9A95 !important; transform: translateY(-1px); }\n.tcs-hover-inc { transition: background-color 0.15s ease; }\n.tcs-hover-inc .tcs-hover-arrow { display: inline-block; transition: color 0.15s ease, transform 0.15s ease; }\n.tcs-hover-inc:hover { background-color: #EFEDE5 !important; }\n.tcs-hover-inc:hover .tcs-hover-arrow { color: #501313 !important; transform: translateX(2px); }\n.tcs-toc a { color: #A32D2D; text-decoration: none; transition: color 0.15s ease; }\n.tcs-toc a:hover { color: #501313; text-decoration: underline; }\n.tcs-inline-code { font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; font-size: 12px; background: #F0EEE6; color: #501313; padding: 2px 6px; border-radius: 4px; }\n.tcs-callout { background: #FCEBEB; border-left: 4px solid #A32D2D; padding: 14px 18px; border-radius: 0 8px 8px 0; margin: 16px 0; font-size: 13px; color: #501313; line-height: 1.65; }\n.tcs-callout strong { color: #2C2C2A; }\n.tcs-phase { padding: 18px 22px; background: #F7F6F2; border-radius: 10px; margin-bottom: 12px; border-left: 4px solid #A32D2D; }\n.tcs-phase-num { display: inline-block; font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; font-size: 11px; font-weight: 600; color: #A32D2D; margin-bottom: 6px; letter-spacing: 0.6px; }\n.tcs-phase-title { font-size: 15px; font-weight: 500; color: #2C2C2A; margin-bottom: 8px; }\n.tcs-phase-body { font-size: 13px; color: #555550; line-height: 1.7; }\n.tcs-phase-body p { margin: 6px 0; }\n.tcs-phase-body ul { margin: 8px 0; padding-left: 20px; }\n.tcs-phase-body li { margin: 3px 0; }\n.tcs-faq-item { background: #FAFAF8; border: 1px solid #EFEDE5; border-radius: 8px; margin-bottom: 10px; transition: border-color 0.15s ease; }\n.tcs-faq-item[open] { border-color: #A32D2D; background: #FFFFFF; }\n.tcs-faq-item summary { cursor: pointer; padding: 16px 20px; font-size: 14px; font-weight: 500; color: #2C2C2A; list-style: none; display: flex; align-items: center; justify-content: space-between; gap: 16px; outline: none; }\n.tcs-faq-item summary::-webkit-details-marker { display: none; }\n.tcs-faq-item summary::after { content: '+'; font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; font-size: 20px; font-weight: 400; color: #A32D2D; flex-shrink: 0; transition: transform 0.2s ease; line-height: 1; }\n.tcs-faq-item[open] summary::after { content: '\u2212'; }\n.tcs-faq-item summary:hover { color: #A32D2D; }\n.tcs-faq-body { padding: 0 20px 18px 20px; font-size: 13px; color: #555550; line-height: 1.7; }\n.tcs-faq-body p { margin: 0 0 10px 0; }\n.tcs-faq-body p:last-child { margin-bottom: 0; }\n.tcs-section h2 { font-size: 26px; font-weight: 500; margin: 0 0 14px 0; color: #2C2C2A; letter-spacing: -0.3px; }\n.tcs-section h3 { font-size: 18px; font-weight: 500; margin: 24px 0 10px 0; color: #2C2C2A; }\n.tcs-section h4 { font-size: 15px; font-weight: 500; margin: 18px 0 8px 0; color: #2C2C2A; }\n.tcs-section p { font-size: 14px; line-height: 1.7; color: #333333; margin: 0 0 12px 0; }\n.tcs-section ul { font-size: 13px; line-height: 1.75; color: #333333; padding-left: 22px; margin: 8px 0 14px 0; }\n.tcs-section ul li { margin-bottom: 4px; }\n.tcs-eyebrow { font-size: 10px; font-weight: 600; color: #A32D2D; text-transform: uppercase; letter-spacing: 0.7px; margin: 0 0 8px 0; }\n.tcs-section-divider { border: none; border-top: 1px solid #EFEDE5; margin: 44px 0 36px 0; }\n.tcs-evaluation { padding: 14px 18px; background: #FAFAF8; border: 1px solid #EFEDE5; border-radius: 8px; margin-bottom: 10px; transition: border-color 0.15s ease; }\n.tcs-evaluation:hover { border-color: #A32D2D; }\n.tcs-evaluation-title { font-size: 14px; font-weight: 500; color: #2C2C2A; margin-bottom: 6px; }\n.tcs-evaluation-body { font-size: 12px; line-height: 1.65; color: #6B6A66; }\n.tcs-evaluation-body strong { color: #501313; font-weight: 500; }\n<\/style>\n\n<div style=\"font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,'Helvetica Neue',Arial,sans-serif; color:#333333; max-width:920px; margin:0 auto; padding:24px 0; line-height:1.6;\">\n\n  <!-- ============================================================\n       HERO\n       ============================================================ -->\n  <div style=\"position:relative; background:#FAFAF8; border:1.5px solid #2C2C2A; border-radius:16px; padding:40px 44px; margin-bottom:36px; overflow:hidden; min-height:280px;\">\n\n    <svg style=\"position:absolute; top:0; right:0; height:100%; width:48%; pointer-events:none;\" viewBox=\"0 0 400 280\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" preserveAspectRatio=\"xMaxYMid meet\">\n      <g>\n        <rect x=\"56\" y=\"20\" width=\"8\" height=\"8\" transform=\"rotate(45, 60, 24)\" fill=\"#F5D1D1\" opacity=\"0.5\"\/>\n        <rect x=\"92\" y=\"36\" width=\"10\" height=\"10\" transform=\"rotate(45, 97, 41)\" fill=\"#E8A8A8\" opacity=\"0.7\"\/>\n        <rect x=\"140\" y=\"18\" width=\"7\" height=\"7\" transform=\"rotate(45, 143.5, 21.5)\" fill=\"#F5D1D1\" opacity=\"0.6\"\/>\n        <rect x=\"184\" y=\"40\" width=\"12\" height=\"12\" transform=\"rotate(45, 190, 46)\" fill=\"#F09595\" opacity=\"0.8\"\/>\n        <rect x=\"232\" y=\"24\" width=\"9\" height=\"9\" transform=\"rotate(45, 236.5, 28.5)\" fill=\"#E8A8A8\"\/>\n        <rect x=\"280\" y=\"38\" width=\"11\" height=\"11\" transform=\"rotate(45, 285.5, 43.5)\" fill=\"#CF2031\" opacity=\"0.6\"\/>\n        <rect x=\"324\" y=\"20\" width=\"8\" height=\"8\" transform=\"rotate(45, 328, 24)\" fill=\"#F09595\"\/>\n        <rect x=\"360\" y=\"46\" width=\"10\" height=\"10\" transform=\"rotate(45, 365, 51)\" fill=\"#CF2031\" opacity=\"0.8\"\/>\n        <rect x=\"72\" y=\"72\" width=\"11\" height=\"11\" transform=\"rotate(45, 77.5, 77.5)\" fill=\"#E8A8A8\" opacity=\"0.6\"\/>\n        <rect x=\"116\" y=\"88\" width=\"9\" height=\"9\" transform=\"rotate(45, 120.5, 92.5)\" fill=\"#F09595\" opacity=\"0.8\"\/>\n        <rect x=\"164\" y=\"70\" width=\"13\" height=\"13\" transform=\"rotate(45, 170.5, 76.5)\" fill=\"#CF2031\" opacity=\"0.75\"\/>\n        <rect x=\"212\" y=\"92\" width=\"8\" height=\"8\" transform=\"rotate(45, 216, 96)\" fill=\"#A3192A\" opacity=\"0.7\"\/>\n        <rect x=\"256\" y=\"76\" width=\"11\" height=\"11\" transform=\"rotate(45, 261.5, 81.5)\" fill=\"#CF2031\"\/>\n        <rect x=\"304\" y=\"90\" width=\"9\" height=\"9\" transform=\"rotate(45, 308.5, 94.5)\" fill=\"#F09595\" opacity=\"0.9\"\/>\n        <rect x=\"348\" y=\"72\" width=\"12\" height=\"12\" transform=\"rotate(45, 354, 78)\" fill=\"#CF2031\" opacity=\"0.85\"\/>\n        <rect x=\"52\" y=\"128\" width=\"8\" height=\"8\" transform=\"rotate(45, 56, 132)\" fill=\"#F5D1D1\" opacity=\"0.55\"\/>\n        <rect x=\"100\" y=\"116\" width=\"10\" height=\"10\" transform=\"rotate(45, 105, 121)\" fill=\"#E8A8A8\" opacity=\"0.7\"\/>\n        <rect x=\"148\" y=\"134\" width=\"11\" height=\"11\" transform=\"rotate(45, 153.5, 139.5)\" fill=\"#F09595\"\/>\n        <rect x=\"196\" y=\"122\" width=\"9\" height=\"9\" transform=\"rotate(45, 200.5, 126.5)\" fill=\"#CF2031\" opacity=\"0.65\"\/>\n        <rect x=\"244\" y=\"138\" width=\"13\" height=\"13\" transform=\"rotate(45, 250.5, 144.5)\" fill=\"#A3192A\" opacity=\"0.8\"\/>\n        <rect x=\"292\" y=\"120\" width=\"10\" height=\"10\" transform=\"rotate(45, 297, 125)\" fill=\"#CF2031\"\/>\n        <rect x=\"340\" y=\"136\" width=\"8\" height=\"8\" transform=\"rotate(45, 344, 140)\" fill=\"#CF2031\" opacity=\"0.75\"\/>\n        <rect x=\"80\" y=\"172\" width=\"12\" height=\"12\" transform=\"rotate(45, 86, 178)\" fill=\"#E8A8A8\" opacity=\"0.8\"\/>\n        <rect x=\"128\" y=\"186\" width=\"8\" height=\"8\" transform=\"rotate(45, 132, 190)\" fill=\"#F5D1D1\"\/>\n        <rect x=\"176\" y=\"170\" width=\"10\" height=\"10\" transform=\"rotate(45, 181, 175)\" fill=\"#F09595\" opacity=\"0.75\"\/>\n        <rect x=\"220\" y=\"188\" width=\"11\" height=\"11\" transform=\"rotate(45, 225.5, 193.5)\" fill=\"#CF2031\" opacity=\"0.7\"\/>\n        <rect x=\"268\" y=\"172\" width=\"9\" height=\"9\" transform=\"rotate(45, 272.5, 176.5)\" fill=\"#E8A8A8\"\/>\n        <rect x=\"316\" y=\"186\" width=\"12\" height=\"12\" transform=\"rotate(45, 322, 192)\" fill=\"#CF2031\" opacity=\"0.85\"\/>\n        <rect x=\"64\" y=\"222\" width=\"8\" height=\"8\" transform=\"rotate(45, 68, 226)\" fill=\"#F5D1D1\" opacity=\"0.5\"\/>\n        <rect x=\"112\" y=\"236\" width=\"10\" height=\"10\" transform=\"rotate(45, 117, 241)\" fill=\"#E8A8A8\" opacity=\"0.6\"\/>\n        <rect x=\"156\" y=\"220\" width=\"9\" height=\"9\" transform=\"rotate(45, 160.5, 224.5)\" fill=\"#F09595\" opacity=\"0.7\"\/>\n        <rect x=\"204\" y=\"238\" width=\"11\" height=\"11\" transform=\"rotate(45, 209.5, 243.5)\" fill=\"#CF2031\" opacity=\"0.6\"\/>\n        <rect x=\"248\" y=\"224\" width=\"8\" height=\"8\" transform=\"rotate(45, 252, 228)\" fill=\"#F5D1D1\"\/>\n        <rect x=\"296\" y=\"240\" width=\"10\" height=\"10\" transform=\"rotate(45, 301, 245)\" fill=\"#E8A8A8\" opacity=\"0.8\"\/>\n        <rect x=\"344\" y=\"222\" width=\"9\" height=\"9\" transform=\"rotate(45, 348.5, 226.5)\" fill=\"#F09595\" opacity=\"0.85\"\/>\n      <\/g>\n    <\/svg>\n\n    <div style=\"position:absolute; bottom:28px; right:32px; background:#FFFFFF; border:1.5px solid #2C2C2A; border-radius:12px; padding:16px 20px; transform:rotate(-2deg); box-shadow:0 6px 20px rgba(44,44,42,0.15); z-index:3;\">\n      <div style=\"font-size:9px; font-weight:600; color:#2C2C2A; text-transform:uppercase; letter-spacing:1px; margin-bottom:4px; font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;\">Fixed price<\/div>\n      <div style=\"font-size:28px; font-weight:600; color:#CF2031; line-height:1; letter-spacing:-0.5px;\">8.000 \u20ac<\/div>\n      <div style=\"font-size:10px; color:#6B6A66; margin-top:4px;\">per Automic system \u00b7 excl. VAT<\/div>\n    <\/div>\n\n    <div style=\"position:relative; max-width:58%; z-index:2;\">\n      <div style=\"font-size:10px; font-weight:600; color:#CF2031; text-transform:uppercase; letter-spacing:1.5px; margin-bottom:14px; font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace; display:flex; align-items:center; gap:10px;\">\n        <span style=\"display:inline-block; width:24px; height:1px; background:#CF2031;\"><\/span>\n        Full Guide \u00b7 Consulting Package\n      <\/div>\n      <h1 style=\"font-size:36px; font-weight:500; line-height:1.15; margin:0 0 14px 0; max-width:620px; color:#2C2C2A; letter-spacing:-0.5px;\">\n        Automic System Health Check \u2014 <em style=\"font-style:italic; color:#CF2031; font-weight:500;\">stability &amp; performance<\/em>\n      <\/h1>\n      <p style=\"font-size:15px; color:#6B6A66; margin:0 0 24px 0; max-width:580px; line-height:1.65;\">\n        Full Guide for the Automic System Health Check consulting package \u2014 the 5-day expert review Tricise delivers to audit and optimise one Automic system.\n      <\/p>\n      <div>\n        <a href=\"#method\" class=\"tcs-hover-btn-primary\" style=\"display:inline-block; font-size:13px; font-weight:500; padding:12px 22px; border-radius:8px; text-decoration:none; background:#CF2031; color:#FFFFFF; margin-right:10px;\">Jump to method<\/a>\n        <a href=\"#evaluations\" class=\"tcs-hover-btn-secondary\" style=\"display:inline-block; font-size:13px; font-weight:500; padding:12px 22px; border-radius:8px; text-decoration:none; background:#FFFFFF; color:#CF2031; border:1px solid #2C2C2A;\">What we check<\/a>\n      <\/div>\n    <\/div>\n\n  <\/div>\n\n  <!-- ============================================================\n       QUICK FACTS\n       ============================================================ -->\n  <div style=\"display:grid; grid-template-columns:repeat(auto-fit, minmax(180px, 1fr)); gap:12px; margin-bottom:36px;\">\n    <div style=\"background:#F7F6F2; border-radius:8px; padding:14px 16px;\">\n      <div style=\"font-size:10px; color:#6B6A66; margin-bottom:4px; text-transform:uppercase; letter-spacing:0.4px;\">Price<\/div>\n      <div style=\"font-size:13px; font-weight:500; color:#2C2C2A;\">8.000 \u20ac <span style=\"font-size:11px; color:#6B6A66; font-weight:400;\">excl. VAT<\/span><\/div>\n    <\/div>\n    <div style=\"background:#F7F6F2; border-radius:8px; padding:14px 16px;\">\n      <div style=\"font-size:10px; color:#6B6A66; margin-bottom:4px; text-transform:uppercase; letter-spacing:0.4px;\">Duration<\/div>\n      <div style=\"font-size:13px; font-weight:500; color:#2C2C2A;\">5 days<\/div>\n    <\/div>\n    <div style=\"background:#F7F6F2; border-radius:8px; padding:14px 16px;\">\n      <div style=\"font-size:10px; color:#6B6A66; margin-bottom:4px; text-transform:uppercase; letter-spacing:0.4px;\">Delivery<\/div>\n      <div style=\"font-size:13px; font-weight:500; color:#2C2C2A;\">Remote \/ on-site<\/div>\n    <\/div>\n    <div style=\"background:#F7F6F2; border-radius:8px; padding:14px 16px;\">\n      <div style=\"font-size:10px; color:#6B6A66; margin-bottom:4px; text-transform:uppercase; letter-spacing:0.4px;\">Scope<\/div>\n      <div style=\"font-size:13px; font-weight:500; color:#2C2C2A;\">1\u00d7 Automic system<\/div>\n    <\/div>\n  <\/div>\n\n  <!-- ============================================================\n       TABLE OF CONTENTS\n       ============================================================ -->\n  <div class=\"tcs-toc\" style=\"background:#FAFAF8; border:1px solid #EFEDE5; border-radius:12px; padding:24px 28px; margin-bottom:36px;\">\n    <div class=\"tcs-eyebrow\">Contents<\/div>\n    <ol style=\"margin:8px 0 0 0; padding-left:22px; font-size:13px; line-height:2; color:#2C2C2A;\">\n      <li><a href=\"#why\">Why a Health Check matters<\/a><\/li>\n      <li><a href=\"#method\">The 5-day method<\/a><\/li>\n      <li><a href=\"#evaluations\">What we analyse<\/a><\/li>\n      <li><a href=\"#deliverables\">Deliverables<\/a><\/li>\n      <li><a href=\"#scope\">Technical scope &amp; customer involvement<\/a><\/li>\n      <li><a href=\"#faq\">FAQ<\/a><\/li>\n    <\/ol>\n  <\/div>\n\n  <!-- ============================================================\n       1 \u00b7 WHY A HEALTH CHECK MATTERS\n       ============================================================ -->\n  <div id=\"why\" class=\"tcs-section\" style=\"margin-bottom:36px;\">\n    <div class=\"tcs-eyebrow\">1 \u00b7 Why a Health Check matters<\/div>\n    <h2>Why a structured Health Check<\/h2>\n    <p>Most enterprise <a href=\"https:\/\/www.broadcom.com\/products\/software\/automation\/automic-automation\" target=\"_blank\" rel=\"noopener\" style=\"color:#A32D2D; text-decoration:underline;\">Broadcom Automic Automation<\/a> landscapes follow the same story: a stable initial install, years of quiet operation, gradual extension, and a growing assumption that &#8220;it just runs&#8221;. Schedules grew, agents multiplied, new applications were connected, versions were upgraded \u2014 and the underlying platform kept up, but nobody has taken a structured look at whether it is still sized, configured and tuned the way the current workload requires.<\/p>\n\n    <p>The Automic System Health Check is Tricise&#8217;s answer to exactly that situation. It is a 5-day, expert-led, fixed-price review of one Automic system, designed to identify weaknesses, uncover optimisation potential, and produce a structured, documented roadmap for remediation. The engagement is delivered remotely or on-site by Broadcom-certified Tricise experts and uses our own SQL-based analysis tooling to measure how the platform is actually behaving \u2014 not just how it was set up years ago.<\/p>\n\n    <p>The guiding principle behind the Health Check is simple: <strong>never change a running system \u2014 but never assume a running system is still optimal either<\/strong>. Historically grown Automic environments often carry settings that have been obsolete for several versions (for example the legacy <span class=\"tcs-inline-code\">FT_VERSION<\/span> parameter in <span class=\"tcs-inline-code\">UC_HOSTCHAR_*<\/span> system variables), over-provisioned resources from a different era of workload, or under-tuned components that are quietly approaching their limits. The Health Check surfaces all of that in one structured engagement so your team can prioritise what matters, without having to first run the discovery themselves.<\/p>\n\n    <p>A clear picture of the current platform health is also the foundation for informed planning across several fronts \u2014 sizing decisions, upgrade projects, agent consolidation, performance tuning, and operational budgeting. None of these conversations are productive without numbers and documented findings. The Automic System Health Check is how you get them.<\/p>\n  <\/div>\n\n  <hr class=\"tcs-section-divider\">\n\n  <!-- ============================================================\n       2 \u00b7 THE METHOD\n       ============================================================ -->\n  <div id=\"method\" class=\"tcs-section\" style=\"margin-bottom:36px;\">\n    <div class=\"tcs-eyebrow\">2 \u00b7 Method<\/div>\n    <h2>The 5-day method<\/h2>\n    <p>The Automic System Health Check is delivered as a single, fixed-scope engagement of five consecutive working days. The five days are not a rigid day-by-day agenda \u2014 they are a budget of expert time that is allocated across four clear stages: preparation, data collection, analysis, and joint walkthrough. The exact distribution depends on the landscape, the access situation, and how quickly your team can answer questions along the way.<\/p>\n\n    <div class=\"tcs-phase\">\n      <div class=\"tcs-phase-num\">STAGE 1 \u2014 PREPARATION &amp; ACCESS<\/div>\n      <div class=\"tcs-phase-title\">Scoping and environment access<\/div>\n      <div class=\"tcs-phase-body\">\n        <p>Before the engagement begins, Tricise and your team align on which Automic system is in scope, who the customer-side contacts are, and which access (Automic user, database read access, log file access) the consultant will need. The SQL scripts that Tricise uses for the data collection phase are introduced and reviewed with your team, so you see exactly what they do before they touch your environment. This stage is deliberately light on effort on the customer side \u2014 typically one short scoping call and one access provisioning session.<\/p>\n      <\/div>\n    <\/div>\n\n    <div class=\"tcs-phase\">\n      <div class=\"tcs-phase-num\">STAGE 2 \u2014 DATA COLLECTION<\/div>\n      <div class=\"tcs-phase-title\">Run the analysis tooling against the live system<\/div>\n      <div class=\"tcs-phase-body\">\n        <p>With access in place, the Tricise consultant runs the analysis scripts against the Automic repository, collects log files from the Automation Engine and the AWI, captures configuration files and system variables, and extracts the historical runtime data needed for the performance evaluations. All data collection is read-only \u2014 nothing in the Automic system is modified during this stage. The collection is lightweight from a system-load perspective and comparable to a reporting query.<\/p>\n        <p>Depending on the size of the landscape, the data collection takes between half a day and a full day of consultant time.<\/p>\n      <\/div>\n    <\/div>\n\n    <div class=\"tcs-phase\">\n      <div class=\"tcs-phase-num\">STAGE 3 \u2014 ANALYSIS<\/div>\n      <div class=\"tcs-phase-title\">Expert review across all eight evaluation areas<\/div>\n      <div class=\"tcs-phase-body\">\n        <p>This is the heart of the engagement. The Tricise consultant works through the collected data and applies the evaluation catalogue described in the next section: system architecture and hardware, database and processes, system settings and incompatibilities, Automic system configuration, AE performance, performance towards the database, Webinterface configuration, and sizing. Each area produces findings, each finding is documented, and every finding is linked to a concrete recommendation with an effort and impact rating.<\/p>\n        <p>The analysis stage uses the largest share of the 5-day budget \u2014 typically two to three days \u2014 because this is where experience and pattern recognition turn raw data into useful conclusions.<\/p>\n      <\/div>\n    <\/div>\n\n    <div class=\"tcs-phase\">\n      <div class=\"tcs-phase-num\">STAGE 4 \u2014 WALKTHROUGH &amp; REPORT<\/div>\n      <div class=\"tcs-phase-title\">Joint result session and written report<\/div>\n      <div class=\"tcs-phase-body\">\n        <p>The engagement ends with a joint walkthrough session in which the Tricise consultant presents the findings, the recommendations and the graphical evaluations to your team. The session is interactive: your team asks questions, challenges findings where useful, adds context the consultant could not see from outside, and confirms priorities. The outputs of this session feed into the final written report \u2014 a comprehensive document that your team can work from on its own in the weeks and months following the engagement.<\/p>\n        <p>The walkthrough is deliberately scheduled towards the end of the 5 days so there is no gap between &#8220;analysis done&#8221; and &#8220;findings handed over&#8221; \u2014 you leave the engagement with the understanding, not just the document.<\/p>\n      <\/div>\n    <\/div>\n\n    <div class=\"tcs-callout\">\n      <strong>What 5 days buys you.<\/strong> Five consecutive days of Broadcom-certified expert time, fully focused on one Automic system, with no parallel work and no competing priorities. The fixed-price model means you know exactly what the engagement costs up-front and exactly what you receive; scope creep is not a concern because the evaluation catalogue is standardised.\n    <\/div>\n  <\/div>\n\n  <hr class=\"tcs-section-divider\">\n\n  <!-- ============================================================\n       3 \u00b7 WHAT WE ANALYSE\n       ============================================================ -->\n  <div id=\"evaluations\" class=\"tcs-section\" style=\"margin-bottom:36px;\">\n    <div class=\"tcs-eyebrow\">3 \u00b7 Evaluation catalogue<\/div>\n    <h2>What we analyse<\/h2>\n    <p>The Automic System Health Check evaluation catalogue is the result of many years of Tricise consulting experience and covers <strong>more than 30 structured diagnostic checks<\/strong> grouped into eight main areas. The categories below describe the types of evaluation performed during the engagement \u2014 each one surfaces a different class of issue, and together they give a complete picture of the platform&#8217;s health. The exact metrics, thresholds and queries are part of Tricise&#8217;s consulting method and are applied by the consultant during the engagement; what you see here is what the findings look like, not how they are computed.<\/p>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">System architecture &amp; hardware<\/div>\n      <div class=\"tcs-evaluation-body\">Analysis of the current system architecture and verification that it still matches the requirements and the actual size of the Automic landscape. Many environments were sized years ago for a different workload profile and have quietly drifted \u2014 some are under-provisioned and starting to creak, others are significantly over-provisioned and wasting infrastructure. <strong>What it reveals:<\/strong> whether your architecture has outgrown its original design, whether sizing is still balanced against the current load, and whether it is ready for the next 2\u20133 years of growth.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">Database &amp; processes<\/div>\n      <div class=\"tcs-evaluation-body\">Review of the database configuration, key Automation Engine processes, and their interconnections for efficiency and stability. Even though Automic is &#8220;only a user&#8221; of the database, the repository has its own parameters and best practices depending on the backend in use. <strong>What it reveals:<\/strong> database parameters that need tuning, process interconnections that introduce latency or contention, and configuration patterns that limit throughput during peak hours.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">System settings &amp; incompatibilities<\/div>\n      <div class=\"tcs-evaluation-body\">Review of all Automic configuration files and system variables (<span class=\"tcs-inline-code\">UC_*<\/span>) and identification of obsolete, deprecated or incompatible settings that have survived multiple version upgrades. Historically grown systems often carry parameters from versions below 12.x that are no longer used \u2014 for example <span class=\"tcs-inline-code\">FT_VERSION<\/span> in <span class=\"tcs-inline-code\">UC_HOSTCHAR_*<\/span>. <strong>What it reveals:<\/strong> legacy settings that can safely be cleaned up, incompatible components that could cause problems during the next upgrade, and configuration drift relative to current Broadcom recommendations.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">Automic system configuration<\/div>\n      <div class=\"tcs-evaluation-body\">Deep review and optimisation of the Automation Engine (AE) system configuration \u2014 the <span class=\"tcs-inline-code\">ucsrv.ini<\/span>, server parameters, system-wide settings and routing rules that shape how the platform behaves. This is where many &#8220;we always did it that way&#8221; decisions hide, often with real impact on throughput, stability and behaviour under load. <strong>What it reveals:<\/strong> configuration parameters that should be adjusted for the current workload, settings that disagree with current Broadcom best practice, and opportunities for stability improvements.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">AE performance &amp; work processes<\/div>\n      <div class=\"tcs-evaluation-body\">Performance analysis of the Automation Engine based on current and historical runtime data, including sizing of the work processes (WPs) and the ratio between the number of started work processes and actual system utilisation. More processes is not always better \u2014 an over-provisioned WP count wastes resources, while an under-provisioned one causes queueing under peak load. Server routines such as <span class=\"tcs-inline-code\">UCGENX_R\/GENX<\/span> are reviewed in the log files for patterns that may indicate objects using an elevated number of script lines, which can hint at performance issues. <strong>What it reveals:<\/strong> the optimal work-process count for the current workload, patterns in server routine execution that point to performance hotspots, and resource waste from over-provisioning.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">Performance toward the database<\/div>\n      <div class=\"tcs-evaluation-body\">Analysis of database performance and its interaction with the AE to identify bottlenecks and optimisation potential. The Automation Engine continuously interacts with the repository through many different types of queries, and some of them \u2014 for example <span class=\"tcs-inline-code\">SLUC<\/span>, a <em>select for update<\/em> statement used for transaction handling \u2014 should always run fast. When they don&#8217;t, that is a signal. <strong>What it reveals:<\/strong> which database calls are slow, whether slow calls correlate with specific time windows, and whether the slowness correlates with elevated server routines. This includes review of the AE REORG \u2014 frequency, runtime, table sizes, index structure \u2014 because REORG configuration directly shapes long-term database performance.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">Object activations &amp; load distribution<\/div>\n      <div class=\"tcs-evaluation-body\">Analysis of process activations over different time horizons \u2014 monthly, weekly, daily, hourly \u2014 to identify peak-load periods and uneven load distribution. Most landscapes have sharp peaks at predictable times (the 06:00 morning batch, the end-of-month closing, the Monday reporting wave) and these peaks drive both stability and sizing decisions. <strong>What it reveals:<\/strong> workload shape, smoothing and consolidation opportunities, the real peak your sizing needs to accommodate, and load hotspots that deserve a closer look.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">Object analysis (variables, calendars, jobs, agents)<\/div>\n      <div class=\"tcs-evaluation-body\">Structural review of the Automic object layer. Are there variables with hundreds of thousands of entries \u2014 or calendars with thousands of entries \u2014 that slow down loading and operations? Are there jobs that abort repeatedly? Do the connected agents match the current Automation Engine version, and are they fully compatible? <strong>What it reveals:<\/strong> oversized objects that need cleanup, unstable jobs that indicate deeper process issues, and agent version mismatches that will become a problem at the next upgrade.<\/div>\n    <\/div>\n\n    <div class=\"tcs-evaluation\">\n      <div class=\"tcs-evaluation-title\">AWI (Webinterface) analysis<\/div>\n      <div class=\"tcs-evaluation-body\">Review of the Automic Web Interface regardless of whether Tomcat or Jetty is used as the launcher. The consultant checks the <span class=\"tcs-inline-code\">configuration.properties<\/span> file for useful parameters, inspects Tomcat and Jetty log files for anomalies, verifies that sufficient resources are available for AWI operation, and evaluates the overall AWI architecture for optimisation potential. <strong>What it reveals:<\/strong> Webinterface parameters that improve usability and stability, resource sizing issues that affect user experience, and architectural improvements for better scalability.<\/div>\n    <\/div>\n\n    <div class=\"tcs-callout\">\n      <strong>More than 30 structured diagnostic checks.<\/strong> The eight areas above are the main families of evaluation; inside each one, the consultant applies multiple specific checks depending on the database backend, Automic version and landscape size. A typical Health Check engagement produces between 20 and 60 concrete findings, each linked to the area it came from and each with its own recommendation and priority.\n    <\/div>\n  <\/div>\n\n  <hr class=\"tcs-section-divider\">\n\n  <!-- ============================================================\n       4 \u00b7 DELIVERABLES\n       ============================================================ -->\n  <div id=\"deliverables\" class=\"tcs-section\" style=\"margin-bottom:36px;\">\n    <div class=\"tcs-eyebrow\">4 \u00b7 Deliverables<\/div>\n    <h2>What you receive<\/h2>\n    <p>At the end of the 5-day Automic System Health Check, you leave the engagement with a complete set of written and visual outputs that your team can work from on its own, without further Tricise involvement. Everything listed below is part of the fixed price \u2014 the Automic System Health Check has no hidden extras and no per-hour billing inside the agreed scope.<\/p>\n\n    <h3>Detailed analysis report<\/h3>\n    <p>A comprehensive written document containing all findings from the engagement, organised by evaluation area and with each finding described, quantified, and put into context. The top section is a structured executive summary readable by operations management; the body carries the technical detail operations and platform engineers need to act. The document is walked through jointly with the Tricise expert at the end of the engagement so everyone on your team understands what was found, why it matters, and what the next steps look like.<\/p>\n\n    <h3>Practical recommendations &amp; action plan<\/h3>\n    <p>Every finding comes with a concrete recommendation: what to change, how much effort it represents, and what the expected impact on stability, performance or resource utilisation is. Recommendations are grouped into immediate quick wins, medium-term improvements, and longer-term architectural changes, so your team has a clear top-down list rather than a flat bag of suggestions.<\/p>\n\n    <h3>Critical-adjustment highlights<\/h3>\n    <p>A dedicated section highlighting adjustments that are critical for avoiding incidents, failed upgrades or stability regressions \u2014 the things that need attention first. This section exists because not every finding is equal: some are nice-to-have, and some are &#8220;fix this before the next maintenance window&#8221;.<\/p>\n\n    <h3>Graphical evaluations<\/h3>\n    <p>Visualisations of system load, object activations and database access patterns that make the findings tangible \u2014 the shape of the weekly peak, the distribution of database calls by duration, the top tables by row count, the top load drivers and most frequently triggered objects. Graphical output turns numbers into arguments your team can use internally when advocating for the prioritised changes.<\/p>\n\n    <h3>Joint walkthrough session<\/h3>\n    <p>The final walkthrough with the Tricise consultant is itself a deliverable. It is where your team sees the findings first-hand, clarifies context, asks questions and turns the written report into shared understanding. The session happens within the 5-day engagement, not as a separate follow-up, so nothing gets lost between analysis and handover.<\/p>\n\n    <h3>Roadmap for future-proofing<\/h3>\n    <p>A concise roadmap that pulls the recommendations together into a sequence: what to do first, what to do next, and what to plan for in the context of upcoming upgrades, scaling decisions or architectural changes. This is the deliverable that makes the Health Check useful months and years after the engagement itself.<\/p>\n  <\/div>\n\n  <hr class=\"tcs-section-divider\">\n\n  <!-- ============================================================\n       5 \u00b7 TECHNICAL SCOPE & CUSTOMER INVOLVEMENT\n       ============================================================ -->\n  <div id=\"scope\" class=\"tcs-section\" style=\"margin-bottom:36px;\">\n    <div class=\"tcs-eyebrow\">5 \u00b7 Technical scope<\/div>\n    <h2>Technical scope &amp; what we need from you<\/h2>\n    <p>The Automic System Health Check is deliberately light on customer prerequisites. We do not ask your team to prepare data, run scripts, or assemble reports in advance. What we need is access to the system, availability during the walkthrough, and the contextual knowledge that only your operations team has. The total customer-side effort across the 5-day engagement is typically around half a day to one day \u2014 the rest is Tricise doing the work.<\/p>\n\n    <h3>What is in scope<\/h3>\n    <ul>\n      <li><strong>One Automic system<\/strong> \u2014 a single Automic Automation Engine system, which may include multiple clients if they share the same repository<\/li>\n      <li><strong>5 days of consultant effort<\/strong> \u2014 preparation, data collection, analysis, report, walkthrough<\/li>\n      <li><strong>All eight evaluation areas<\/strong> \u2014 architecture, database, system settings, configuration, AE performance, database performance, activations, objects and AWI<\/li>\n      <li><strong>More than 30 structured diagnostic checks<\/strong> \u2014 applied from the Tricise catalogue<\/li>\n      <li><strong>Report, recommendations, graphical evaluations and walkthrough<\/strong> \u2014 the complete deliverable set<\/li>\n    <\/ul>\n\n    <h3>What your team needs to provide<\/h3>\n    <ul>\n      <li><strong>Full access to the Automic system<\/strong> \u2014 an Automic user account with sufficient rights to inspect configuration, objects and system variables<\/li>\n      <li><strong>Read access to the Automic repository<\/strong> \u2014 for running the Tricise analysis scripts against PostgreSQL, Oracle or SQL Server, depending on your backend<\/li>\n      <li><strong>Access to relevant log files<\/strong> \u2014 Automation Engine logs, AWI logs (Tomcat or Jetty), and any recent incident logs that might be useful context<\/li>\n      <li><strong>Participants for the walkthrough<\/strong> \u2014 typically one or two Automic administrators and, where applicable, a database administrator<\/li>\n      <li><strong>A short scoping call<\/strong> before the engagement starts, to confirm access, contacts and timeline<\/li>\n    <\/ul>\n\n    <h3>Delivery mode<\/h3>\n    <p>The Automic System Health Check is delivered remotely by default, which keeps costs predictable, enables fast scheduling, and works well for most customers. On-site delivery is available on request; travel expenses are then charged in addition to the fixed price, at actual cost. The analysis itself is identical in either delivery mode \u2014 remote delivery uses secure access and video conferencing for the walkthrough, and customers who have worked with Tricise remotely consistently report that the format works well for this type of engagement.<\/p>\n\n    <h3>Out of scope<\/h3>\n    <ul>\n      <li>Implementation of the recommendations \u2014 the Health Check delivers the analysis and the plan; the implementation is typically handled by your own team or as a separate Tricise consulting engagement<\/li>\n      <li>Upgrade execution \u2014 an upgrade project is a separate engagement, though the Health Check is often a valuable input to it<\/li>\n      <li>Analysis of systems other than the one contracted in this engagement<\/li>\n      <li>Ongoing monitoring or managed services \u2014 see Tricise Application Managed Services (AMS) for that<\/li>\n    <\/ul>\n  <\/div>\n\n  <hr class=\"tcs-section-divider\">\n\n  <!-- ============================================================\n       6 \u00b7 FAQ\n       ============================================================ -->\n  <div id=\"faq\" class=\"tcs-section\" style=\"margin-bottom:36px;\">\n    <div class=\"tcs-eyebrow\">6 \u00b7 FAQ<\/div>\n    <h2>Frequently asked questions<\/h2>\n    <p>Click any question to expand the answer.<\/p>\n\n    <details class=\"tcs-faq-item\">\n      <summary>What is the Automic System Health Check and what does it do?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>The Automic System Health Check is a fixed-price consulting package by Tricise that performs a structured, 5-day review of one Automic Automation Engine system. Broadcom-certified Tricise experts audit eight areas of the platform \u2014 system architecture, database, system settings, Automic configuration, AE performance, database performance, object activations, structural object layer, and the Webinterface (AWI) \u2014 applying more than 30 structured diagnostic checks from the Tricise evaluation catalogue. The engagement ends with a detailed report, prioritised recommendations, graphical evaluations, and a joint walkthrough session with your team, so you leave with both the document and the shared understanding needed to act on it.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>How much does the Automic System Health Check cost?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>The Automic System Health Check is offered at a fixed price of <strong>8.000 \u20ac (excl. VAT) per Automic system<\/strong>. The fixed price covers the complete 5-day engagement: preparation, data collection, analysis across all eight evaluation areas, the written report, the prioritised recommendations, the graphical evaluations, and the joint walkthrough session. If the engagement is delivered on-site at your request, travel expenses are charged in addition at actual cost. There are no hidden extras and no per-hour billing inside the agreed scope.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>How long does the Automic System Health Check take?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>The Automic System Health Check is a <strong>5-day engagement<\/strong>, usually delivered as five consecutive working days. The five days are a budget of Tricise expert time that covers preparation, data collection, analysis, report writing, and the final walkthrough \u2014 not a rigid day-by-day agenda. Depending on the landscape and the access situation, the distribution can vary slightly, but the total effort and the fixed price are constant. The effort on the customer side is very light by comparison \u2014 typically around half a day to one day in total, including the scoping call and the final walkthrough session.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>Which Automic versions and database backends are supported?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>The Automic System Health Check supports current Automic Automation Engine versions running on any of the three common repository databases: <strong>PostgreSQL, Oracle and Microsoft SQL Server<\/strong>. Tricise maintains analysis scripts and evaluation checks adapted to each backend and to the Automation Engine version in use. If your landscape uses a very old Automic version \u2014 something well below the current support window \u2014 let us know during scoping; we will tell you directly whether the standard engagement still fits or whether adjustments are needed.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>What do I need to prepare before the Health Check starts?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>The preparation on your side for an Automic System Health Check is intentionally minimal. You need to provide an Automic user account with enough rights to inspect configuration, objects and system variables; read access to the Automic repository database for the Tricise analysis scripts; and access to the relevant log files (Automation Engine, AWI, incident logs). You also nominate one or two Automic administrators \u2014 plus a database administrator where applicable \u2014 who join the short scoping call at the start and the walkthrough session at the end. No data pre-processing, no internal spreadsheets, no advance reports \u2014 the engagement is designed so that your team&#8217;s total involvement stays under one day.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>Is the data collection intrusive? Does it affect production?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>No. The data collection during the Automic System Health Check is entirely <strong>read-only<\/strong> \u2014 the Tricise analysis scripts query the Automic repository and the log files but never modify them. There is no code deployed into the Automation Engine, no agents installed, no changes to workflows or objects, no risk to running jobs. The scripts are reviewed jointly with your team before execution, so you see exactly what they do before they touch your environment. The load impact on the database is comparable to a reporting query.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>How does this differ from the Automic Process Analysis &amp; Optimisation package?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>The two packages complement each other. The <strong>Automic System Health Check<\/strong> is an architecture and configuration review \u2014 it asks &#8220;is the platform healthy?&#8221; and looks at how the Automation Engine is set up, sized and tuned (database parameters, work processes, server routines, REORG, AWI configuration, object layer hygiene, agent compatibility). The <strong>Automic Process Analysis &amp; Optimisation<\/strong> package is a workload review \u2014 it asks &#8220;are we running it efficiently?&#8221; and looks at what the system is actually executing, in what volume, at what frequency, and with what efficiency. Customers often book both, in either order, depending on which question is more pressing. A Health Check is typically the right starting point if stability, upgrades or sizing are the driving concern; Process Analysis fits better when the driver is workload efficiency or execution-based licensing.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>Will you tell me exactly what to change, or just what&#8217;s wrong?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>Every finding in the Automic System Health Check report comes with a concrete recommendation \u2014 what to change, how much effort it represents, and what the expected impact is. For configuration and parameter findings, the recommendation is typically at the level of &#8220;change this setting to that value because of X&#8221;. For architectural and sizing findings, the recommendation is at the pattern level, because the actual decision depends on business context only your team has. Either way, the report gives you actionable next steps, not just observations.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>Can you also implement the recommendations?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>Implementation is deliberately <strong>not part<\/strong> of the fixed-price Automic System Health Check \u2014 the package is scoped as an analysis and recommendation engagement. That said, Tricise can of course implement the recommendations as a follow-up project, scoped and priced separately based on what the Health Check produced. Many customers take the report first, work through the quick wins internally, and then engage Tricise for the medium-term and architectural items. Others hand everything back to us immediately. Both models work.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>Do we keep the SQL scripts after the engagement?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>The SQL analysis scripts and evaluation tooling are Tricise&#8217;s consulting method and remain with Tricise \u2014 they are the instrument we use to perform the Health Check, not a product deliverable. What you receive and keep is the complete analysis report, all findings, recommendations, graphical evaluations, and the action roadmap. If you want an ongoing, self-service monitoring capability rather than a point-in-time expert review, that is a different conversation \u2014 typically either the Automation CLI Action Pack, the Application Managed Services (AMS), or a periodically repeated Health Check engagement.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>How often should we run a System Health Check?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>There is no single right answer, but a useful rule of thumb is <strong>every 12 to 24 months<\/strong>, or whenever a significant event is coming up \u2014 a major Automic upgrade, a migration, a platform consolidation, a new workload onboarding, or a sharp growth in load. Between engagements, the recommendations from the previous Health Check should have been worked through, which means the next run starts from a cleaner baseline and produces more targeted findings. Customers who run a Health Check every 18 months and work through the top findings between runs typically see measurable long-term improvements in stability and performance.<\/p>\n      <\/div>\n    <\/details>\n\n    <details class=\"tcs-faq-item\">\n      <summary>Is the Health Check useful before an Automic upgrade?<\/summary>\n      <div class=\"tcs-faq-body\">\n        <p>Yes \u2014 this is one of the most common reasons customers book the Automic System Health Check. The evaluation catalogue includes obsolete parameters, legacy system variables, incompatible components and agent version mismatches, all of which are exactly the things that cause friction during an upgrade. A Health Check run 1\u20133 months before a planned upgrade gives you a clean list of what to fix up front so the actual upgrade window is much less exciting. Many Tricise customers pair the Health Check with an upcoming upgrade project for exactly this reason.<\/p>\n      <\/div>\n    <\/details>\n  <\/div>\n\n  <!-- ============================================================\n       FOOTER CTA\n       ============================================================ -->\n  <div style=\"background:#2C2C2A; border-radius:12px; padding:28px 32px; margin-top:24px;\">\n    <div style=\"margin-bottom:14px;\">\n      <div style=\"font-size:17px; font-weight:500; color:#FFFFFF; margin:0 0 4px 0;\">\n        Ready to <em style=\"font-style:italic; color:#F09595; font-weight:500;\">stabilise &amp; future-proof your Automic system?<\/em>\n      <\/div>\n      <div style=\"font-size:13px; color:#B4B2A9;\">Book directly in the shop or talk to our experts about scope &amp; scheduling.<\/div>\n    <\/div>\n    <div>\n      <a href=\"https:\/\/tricise.com\/shop\/automic-system-healthcheck\/\" class=\"tcs-hover-btn-primary\" style=\"display:inline-block; font-size:13px; font-weight:500; padding:10px 20px; border-radius:8px; text-decoration:none; background:#A32D2D; color:#FFFFFF; margin-right:10px;\">Buy now \u00b7 8.000 \u20ac excl. VAT<\/a>\n      <a href=\"https:\/\/tricise.com\/contact\/consultation\/\" class=\"tcs-hover-btn-ghost\" style=\"display:inline-block; font-size:13px; font-weight:500; padding:10px 20px; border-radius:8px; text-decoration:none; background:transparent; color:#FFFFFF; border:1px solid #5F5E5A;\">Talk to expert<\/a>\n    <\/div>\n  <\/div>\n\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Fixed price 8.000 \u20ac per Automic system \u00b7 excl. VAT Full Guide \u00b7 Consulting Package Automic System Health Check \u2014 [&hellip;]<\/p>\n","protected":false},"author":59,"featured_media":0,"parent":14575,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"doc_badge":[],"class_list":["post-14635","docs","type-docs","status-publish","hentry"],"acf":[],"meta_box":[],"author_avatar":"https:\/\/secure.gravatar.com\/avatar\/f90ddc4bef2e4782ae1e7c9da72b6fd7660039c95037dc1af7edfb48356d41b4?s=96&d=mm&r=g","author_name":"Martin Winkler","_links":{"self":[{"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/docs\/14635","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/users\/59"}],"replies":[{"embeddable":true,"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/comments?post=14635"}],"version-history":[{"count":2,"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/docs\/14635\/revisions"}],"predecessor-version":[{"id":14942,"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/docs\/14635\/revisions\/14942"}],"up":[{"embeddable":true,"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/docs\/14575"}],"wp:attachment":[{"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/media?parent=14635"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=14635"},{"taxonomy":"doc_badge","embeddable":true,"href":"https:\/\/tricise.com\/fr\/wp-json\/wp\/v2\/doc_badge?post=14635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}