--- title: "Common Service Data Model Alignment: Where Most CMDBs Fall Short" description: Common Service Data Model alignment depends on links between records. Where CMDBs fall short, the checks that expose it, and what to fix first. image: https://www.apexconfiguration.com/hubfs/AI-Generated%20Media/Images/Two%20Colleagues%20Sketching%20Strategy%20on%20Glass%20Wall.png --- [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [tel:+442080588135](tel:+442080588135)[mailto:contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [CMDB](https://www.apexconfiguration.com/blog/tag/cmdb)[ServiceNow](https://www.apexconfiguration.com/blog/tag/servicenow) [CSDM](https://www.apexconfiguration.com/blog/tag/csdm)[Data Model Design](https://www.apexconfiguration.com/blog/tag/data-model-design) # Common Service Data Model Alignment: Where Most CMDBs Fall Short [![Warren O'Neill](https://www.apexconfiguration.com/hs-fs/hubfs/warren-oneill.webp?width=40&height=40&name=warren-oneill.webp)](https://www.apexconfiguration.com/blog/author/warren-oneill) by [Warren O'Neill](https://www.apexconfiguration.com/blog/author/warren-oneill) 7 min read Oct 26, 2026, 9:00:02 AM Last updated on 26 Oct 2026, 09:00:02 Common Service Data Model alignment means more than having the right tables populated. It means each record type is used for the purpose the model defines, and linked to the records either side of it, so that incident, change and service mapping can rely on an unbroken chain from the business service down to the server. Most configuration management databases (CMDBs) we assess have the tables. Where they fall short is the links between them, the separation of environments and the foundation data everything else refers to. ## Key Takeaways - Common Service Data Model alignment means each record type is used for the purpose the model defines and linked to the records either side of it. Populated tables alone don't deliver it. - Most CMDBs have the tables. The shortfalls are in the links between them, the separation of environments and the foundation data that everything else refers to. - A business application is a portfolio record, so it shouldn't be selected on incidents, problems or changes. When it is, impact analysis has nothing beneath it to follow. - An application service represents one deployment in one environment. Relating a development service to infrastructure that also hosts production breaks change risk assessment. - Business service offerings need related application services, and technology management service offerings need an active support group. Without those relationships the model is decorative. - Weight each gap by the processes it affects, then fix foundation data and the crawl stage first. This article sets out what the model actually asks of your CMDB, the shortfalls we find most often at each stage, the checks that expose them, and how to run a gap analysis that prioritises what matters to your processes instead of chasing completeness for its own sake. ## What the Common Service Data Model asks of your CMDB ServiceNow's Common Service Data Model defines where each kind of service, application and infrastructure record belongs, and how they relate. Version 5 organises the model into domains covering foundation data, ideation and strategy, design and planning, build and integration, service delivery and service consumption. ServiceNow doesn't recommend implementing it all at once. Its white paper describes a staged approach: foundation, then crawl, walk, run and fly. Crawl centres on business applications, application services, discovered applications and servers. Walk adds technology management services and their offerings. Run adds business services and business service offerings. Version 5 also introduced two changes that matter for alignment work. The application service table was relabelled as service instance, with new sibling classes for data, connection, network, facility and operational process instances. And life cycle stage and life cycle stage status replace the older status fields as the standard way of recording where a record is in its life. The new service instance classes have no user interface for creating them yet, and ServiceNow says there's no expectation to use them unless local requirements need them. Don't let them distract you from fixing the application services you already have. ## Foundation data: the stage most estates skip The foundation stage covers reference data: companies, business units, departments, locations, groups, users, product models and contracts. It looks like housekeeping. It's what every report, assignment rule and certification campaign depends on. The shortfalls we see most: - Company records that mix legal entities with departments, so vendor and manufacturer reporting can't be trusted - Location hierarchies that stop at site level when the estate needs building, floor or data centre - Support groups that no longer exist still referenced on configuration items (CIs) - Product models created ad hoc by each integration, so the same hardware model appears several times Measure each one directly. Count CIs referencing inactive groups. Count product models that share a manufacturer and model number. List locations with no parent. These are cheap reports that tell you whether the higher stages have anything solid to stand on. ## Crawl-stage mistakes that break incident and change The crawl stage is where most alignment problems start, because it's where the application records live and where most implementations stop. **Business applications used as operational CIs.** The model is explicit that a business application is a portfolio record, not an operational CI, and shouldn't be selected on incidents, problems or changes. When it is, impact analysis has nothing beneath it to follow. Report on incidents and changes in the last quarter that reference the business application class. **The application table filled by hand.** The application class is meant to hold software discovered running on a host. When it's used as a manual application inventory, it duplicates the business application list and misleads anyone who assumes it came from discovery. Report on application CIs with no discovery source. **Application services without environment separation.** An application service represents one deployment of an application: production, test or development, in a given location. Mixing environments under one service, or relating a development service to production infrastructure, breaks change risk assessment in a way nobody sees until it's too late. On an estate of around seven million CIs, the development environment of a business application had been mapped to infrastructure that also hosted production. A change against the development environment was raised at low priority, because development changes were considered low risk. When the infrastructure was shut down, production went down with it. It wasn't the first time. The client's own customer invoked a get-out clause in their contract and left. We rebuilt the mapping using custom pattern extensions, having first confirmed which hardware actually provided each environment, then ran top-down, pattern-based mapping. The check is straightforward. For every application service marked as non-production, list any related infrastructure CI that is also related to a production application service. Each result needs an explanation or a correction. ## Walk and run: services without relationships At the walk and run stages, the common shortfall isn't missing records. It's records that exist without the relationships that give them a purpose. Technology management service offerings should carry the support groups that resolve incidents and approve changes for the platforms beneath them. When offerings exist but assignment still runs from a spreadsheet of group names, the model is decorative. Business service offerings should relate to the application services that deliver them. A business service catalogue with no relationships downward gives the service desk a nice picklist and gives change impact analysis nothing. Two checks cover most of it. Count business service offerings with no related application service. Count technology management service offerings whose support group is empty or inactive. Both numbers should trend towards zero, and both are easy to put in front of a service owner. ## Life cycle values: two status models in one CMDB Many estates now carry both the older operational and install status fields and the newer life cycle stage and status fields, populated by different sources and processes. Reports then disagree about whether a CI is live, depending on which field they filter on. Decide which model your processes will use, map the old values to the new, and make sure discovery, integrations and retirement processes all write to the same fields. Test the mapping in a sub-production instance first. Until the decision is made, add the status field used to every CMDB report definition, so readers know which truth they're looking at. ## Running a Common Service Data Model gap analysis A gap analysis is only useful if it tells you what to fix first. We score it against the processes that depend on the model. 1. List the checks for each stage, including the ones above. 2. Weight each check by the processes it affects. A gap that breaks change impact analysis outweighs one that only affects a portfolio report. 3. Run the checks and record results as key performance indicators (KPIs) with a current value and a target. 4. Sort the gaps by weighted impact and group them into a phased plan, foundation first. The result is a short list of fixes that make incident, change and service mapping more reliable, in an order you can defend. It also stops the programme drifting towards the fly stage while crawl-stage errors are still taking production down. For how these measures sit alongside completeness and correctness, see our article on [the 3 Cs of a CMDB](https://www.apexconfiguration.com/blog/the-3-cs-of-a-cmdb-completeness-correctness-and-compliance-in-practice), and for how the data model affects wider outcomes, [why your CMDB data model matters](https://www.apexconfiguration.com/blog/cmdb-data-model-security-ai-performance). ## How Apex helps Our data quality assessment measures your CMDB against weighted critical success factors, KPIs and metrics, and we build the Common Service Data Model checks into it. You get a scored gap analysis weighted by process impact, showing where alignment is failing and why. It's scoped at the initial consultation against your estate and requirements. If you want a faster read first, our two-week CMDB health baseline scores which CIs and relationships are trustworthy and which are guesses. The output is a report you can take to your change advisory board. You can [book a CMDB diagnostic call](https://www.apexconfiguration.com/cmdb-diagnostic-call) to talk through your alignment, or [book a meeting](https://www.apexconfiguration.com/book-a-meeting) with one of our consultants. ## Frequently asked questions ### What does Common Service Data Model alignment mean in practice? Each record type is used for the purpose the model defines and related correctly to the records around it. In practice that means operational CIs on incidents and changes, application services separated by environment, and service offerings linked to what delivers them. ### Do we need to adopt version 5 straight away? Most of what version 5 asks for builds on earlier versions. The service instance siblings are optional unless you have a local need for them. The life cycle stage and status fields deserve a decision soon, because mixed status models cause reporting errors today. ### Can business applications be used on incidents and changes? The model says no. A business application is a portfolio record. Incidents and changes should reference the application service for the affected deployment, or the infrastructure CI, so impact analysis can follow relationships. ### Where should a gap analysis start? With foundation data and the crawl stage. Those gaps affect incident and change directly, and later stages depend on them. Weight each gap by the processes it breaks, then fix in that order. *Written by Warren O'Neill, Apex Configuration Group.* Book a free call to discuss how Apex can help you on your journey to a better CMDB   [![\CMDB Diagnostic Call\](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/147949153/interactive-378363509978.png)](https://www.apexconfiguration.com/hs/cta/wi/redirect?encryptedPayload=AVxigLIyu1qT7kQAdA%2B8WtNqzcTTqWCk%2BDtB5UCZoyP9MSybdgla4WV0J1OcnGHDWjL5bGXbtF4os%2Fy5PedgiGPSc928e0%2B995o%2BriTEaMKTqw0WVbwAUPu2ilqQ%2F2Kq7nEvrv%2BgqJ1YpOcYxCqJ7X82ZX%2BTjPdrjiSIbWkqPzgB%2FkAQfMQTMW5bx9J1L0C91zJYtLQ%2BDnqYmpP%2BBnZA7gTbgzZD5235yjRwCAU8xoZxZuQ%3D&webInteractiveContentId=378363509978&portalId=147949153) - Recent - Topics - Archive Recent ### Recent Topics ### Topics - [ServiceNow (46)](https://www.apexconfiguration.com/blog/tag/servicenow) - [CMDB (32)](https://www.apexconfiguration.com/blog/tag/cmdb) - [CMDB Data Quality (13)](https://www.apexconfiguration.com/blog/tag/cmdb-data-quality) - [Case Studies (8)](https://www.apexconfiguration.com/blog/tag/case-studies) - [ServiceNow Discovery (8)](https://www.apexconfiguration.com/blog/tag/servicenow-discovery) - [Service Mapping (7)](https://www.apexconfiguration.com/blog/tag/service-mapping) - [Change Management (6)](https://www.apexconfiguration.com/blog/tag/change-management) - [Vulnerability Management (6)](https://www.apexconfiguration.com/blog/tag/vulnerability-management) - [Duplicate CIs (5)](https://www.apexconfiguration.com/blog/tag/duplicate-cis) - [IT Governance (5)](https://www.apexconfiguration.com/blog/tag/it-governance) - [CI Ownership (4)](https://www.apexconfiguration.com/blog/tag/ci-ownership) - [Compliance & Audit (4)](https://www.apexconfiguration.com/blog/tag/compliance-audit) - [Enterprise Risk Management (4)](https://www.apexconfiguration.com/blog/tag/enterprise-risk-management) - [Incident Management (4)](https://www.apexconfiguration.com/blog/tag/incident-management) - [Service Graph Connectors (4)](https://www.apexconfiguration.com/blog/tag/service-graph-connectors) - [Agentic AI (3)](https://www.apexconfiguration.com/blog/tag/agentic-ai) - [Configuration Management (3)](https://www.apexconfiguration.com/blog/tag/configuration-management) - [Cyber Security (3)](https://www.apexconfiguration.com/blog/tag/cyber-security) - [Data Model Design (3)](https://www.apexconfiguration.com/blog/tag/data-model-design) - [IRE (3)](https://www.apexconfiguration.com/blog/tag/ire) - [ITOM (3)](https://www.apexconfiguration.com/blog/tag/itom) - [Manufacturing (3)](https://www.apexconfiguration.com/blog/tag/manufacturing) - [Problem Management (3)](https://www.apexconfiguration.com/blog/tag/problem-management) - [Broadcast & Media (2)](https://www.apexconfiguration.com/blog/tag/broadcast-media) - [CI Reconciliation (2)](https://www.apexconfiguration.com/blog/tag/ci-reconciliation) - [CMDB Remediation (2)](https://www.apexconfiguration.com/blog/tag/cmdb-remediation) - [Dependency Views (2)](https://www.apexconfiguration.com/blog/tag/dependency-views) - [IT Asset Management (2)](https://www.apexconfiguration.com/blog/tag/it-asset-management) - [IT Cost Optimisation (2)](https://www.apexconfiguration.com/blog/tag/it-cost-optimisation) - [Managed Services (2)](https://www.apexconfiguration.com/blog/tag/managed-services) - [ServiceNow Advisory (2)](https://www.apexconfiguration.com/blog/tag/servicenow-advisory) - [CSDM (1)](https://www.apexconfiguration.com/blog/tag/csdm) - [Operational Efficiency (1)](https://www.apexconfiguration.com/blog/tag/operational-efficiency) See all Archive ### Archive - [October 2026 (19)](https://www.apexconfiguration.com/blog/archive/2026/10) - [September 2026 (16)](https://www.apexconfiguration.com/blog/archive/2026/09) - [August 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/08) - [July 2026 (4)](https://www.apexconfiguration.com/blog/archive/2026/07) - [June 2026 (3)](https://www.apexconfiguration.com/blog/archive/2026/06) - [May 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/05) See all ### Subscribe by email Share this [Share on X](https://x.com/intent/post?url=https://www.apexconfiguration.com/blog/common-service-data-model-alignment-where-most-cmdbs-fall-short&text=Common+Service+Data+Model+Alignment%3A+Where+Most+CMDBs+Fall+Short) [Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https://www.apexconfiguration.com/blog/common-service-data-model-alignment-where-most-cmdbs-fall-short&t=Common+Service+Data+Model+Alignment%3A+Where+Most+CMDBs+Fall+Short) [Share on LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https://www.apexconfiguration.com/blog/common-service-data-model-alignment-where-most-cmdbs-fall-short&t=Common+Service+Data+Model+Alignment%3A+Where+Most+CMDBs+Fall+Short) Previous story [← EOL Radar: A Weekly End-Of-Support Report For ServiceNow Estates](https://www.apexconfiguration.com/blog/eol-radar-end-of-support-queries) ![Warren O'Neill](https://www.apexconfiguration.com/hs-fs/hubfs/warren-oneill.webp?width=64&height=64&name=warren-oneill.webp) By [Warren O'Neill](https://www.apexconfiguration.com/blog/author/warren-oneill) Co-owner and Technology Director at Apex Configuration Group, based in Bath, UK. Warren specialises in ServiceNow CMDB and CSDM, ITOM Discovery, Service Mapping and pattern development, with a focus… [Full profile & credentials →](https://www.apexconfiguration.com/blog/author/warren-oneill) ### Get Email Notifications [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png)](https://www.apexconfiguration.com/) ServiceNow CMDB specialists delivering enterprise-grade implementation, remediation, and managed services. Address: 20 Wenlock Road, London, England, N1 7GU VAT Number: 505 0347 31 Company Number: 15871442 Email: [contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [Follow Apex Configuration Group on LinkedIn](https://www.linkedin.com/company/apex-configuration-group) Services - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - [Health Dashboard & Reporting](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) Company - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - [About](https://www.apexconfiguration.com/about-apex) - [Blog](https://www.apexconfiguration.com/blog) Resources - [Contact Us](https://www.apexconfiguration.com/contact-us) - [CMDB Diagnostic Call](https://www.apexconfiguration.com/cmdb-diagnostic-call) - [Book A Meeting](https://www.apexconfiguration.com/book-a-meeting) © 2026 Apex Configuration Group. All rights reserved. ServiceNow is a trademark of ServiceNow, Inc. We are not affiliated with or endorsed by ServiceNow. - [Terms](https://www.apexconfiguration.com/terms) - [Cookies](https://www.apexconfiguration.com/cookie-policy) - [Privacy](https://www.apexconfiguration.com/privacy-policy) ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#organization", "@type" : [ "Organization", "ProfessionalService" ], "address" : { "@type" : "PostalAddress", "addressCountry" : "GB", "addressLocality" : "London", "addressRegion" : "England", "postalCode" : "N1 7GU", "streetAddress" : "20 Wenlock Road" }, "alternateName" : "Apex Configuration Group", "areaServed" : "GB", "contactPoint" : { "@type" : "ContactPoint", "areaServed" : "GB", "availableLanguage" : "en", "contactType" : "customer service", "telephone" : "+44 20 8058 8135" }, "identifier" : { "@type" : "PropertyValue", "propertyID" : "UK Companies House company number", "value" : "15871442" }, "image" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/Configuration-data.webp", "legalName" : "Apex Configuration Group Ltd", "logo" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png", "name" : "Apex Configuration Group Ltd", "sameAs" : [ "https://www.linkedin.com/company/apex-configuration-group", "https://find-and-update.company-information.service.gov.uk/company/15871442", "https://www.crunchbase.com/organization/apex-configuration-group-ltd" ], "telephone" : "+44 20 8058 8135", "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#website", "@type" : "WebSite", "inLanguage" : "en-GB", "name" : "Apex Configuration Group", "publisher" : { "@id" : "https://www.apexconfiguration.com/#organization" }, "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@type" : "WebPage", "description" : "Common Service Data Model alignment depends on links between records. Where CMDBs fall short, the checks that expose it, and what to fix first.", "inLanguage" : "en-GB", "name" : "Common Service Data Model Alignment: Where Most CMDBs Fall Short", "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" }, "url" : "https://www.apexconfiguration.com/blog/common-service-data-model-alignment-where-most-cmdbs-fall-short" } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/", "name" : "Home", "position" : 1 }, { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/blog/common-service-data-model-alignment-where-most-cmdbs-fall-short", "name" : "Common Service Data Model Alignment: Where Most CMDBs Fall Short", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Warren O'Neill", "sameAs" : [ "https://www.linkedin.com/in/warren-oneill/" ], "url" : "https://www.apexconfiguration.com/blog/author/warren-oneill" }, "dateModified" : "2026-10-26T09:00:02+0000", "datePublished" : "2026-10-26T09:00:02+0000", "headline" : "Common Service Data Model Alignment: Where Most CMDBs Fall Short", "image" : [ "https://147949153.fs1.hubspotusercontent-eu1.net/hubfs/147949153/AI-Generated%20Media/Images/Two%20Colleagues%20Sketching%20Strategy%20on%20Glass%20Wall.png" ], "mainEntityOfPage" : { "@id" : "https://www.apexconfiguration.com/blog/common-service-data-model-alignment-where-most-cmdbs-fall-short", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" } } ```