<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Concept Systems</title>
  <link>https://conceptsystems.co.uk/</link>
  <description>Clear thinking on systems integration and infrastructure</description>
  <language>en</language>
  <lastBuildDate>Fri, 13 Nov 2026 19:41:32 GMT</lastBuildDate>
  <atom:link href="https://conceptsystems.co.uk/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Manifest and Mismatch: The Integration Contract Behind UK Carrier APIs</title>
    <link>https://conceptsystems.co.uk/manifest-and-mismatch-uk-carrier-api-integration-contract/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/manifest-and-mismatch-uk-carrier-api-integration-contract/</guid>
    <description>Carrier APIs are often scoped as a label-printing feature, yet the real contract spans manifests, asynchronous events, exception taxonomies and returns. This article argues for treating UK parcel integration as a reconciliation system with an explicit event model, ownership and a peak-ready test plan.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Fri, 13 Nov 2026 14:27:25 GMT</pubDate>
  </item>
  <item>
    <title>Service Levels for the Space Between Systems: Making Backpressure Explicit</title>
    <link>https://conceptsystems.co.uk/service-levels-for-the-space-between-systems/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/service-levels-for-the-space-between-systems/</guid>
    <description>Integration failure often starts not with a broken link but with a producer that quietly outpaces its consumer. This article argues that queue depth, retry budgets and consumer lag belong in the service contract, not only on an operations dashboard.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Fri, 13 Nov 2026 10:17:44 GMT</pubDate>
  </item>
  <item>
    <title>Trust With an Expiry Date: Governing TLS Renewal Across the Integration Estate</title>
    <link>https://conceptsystems.co.uk/trust-with-an-expiry-date-governing-tls-renewal-integration-estate/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/trust-with-an-expiry-date-governing-tls-renewal-integration-estate/</guid>
    <description>TLS certificates are often treated as housekeeping until an endpoint stops trusting another. A governed renewal discipline treats them as integration controls: owned, inventoried, scheduled around UK bank holidays and change freezes, evidenced by automation, and proven through failure testing.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Fri, 13 Nov 2026 00:11:42 GMT</pubDate>
  </item>
  <item>
    <title>Borrowed Authority: Governing the External Lists Your Integrations Treat as Truth</title>
    <link>https://conceptsystems.co.uk/borrowed-authority-governing-external-reference-data/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/borrowed-authority-governing-external-reference-data/</guid>
    <description>Postcodes, VAT rates, company numbers and currency codes are often handled as fixed lookups, yet their authority sits outside the organisation. This article sets out a practical way to treat externally maintained reference data as governed integration dependencies, with clear ownership, change signals and failure behaviour that protects transactions.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Thu, 12 Nov 2026 21:09:57 GMT</pubDate>
  </item>
  <item>
    <title>The Ledger That Outlasts the Team: Integration Handover Under TUPE</title>
    <link>https://conceptsystems.co.uk/ledger-outlasts-team-integration-handover-tupe/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/ledger-outlasts-team-integration-handover-tupe/</guid>
    <description>TUPE transfers are usually managed as an HR and legal programme, but the interfaces remain and the operational knowledge often leaves with the outgoing team. A minimum handover ledger can turn the transfer into a controlled integration event rather than an unplanned knowledge loss.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Thu, 12 Nov 2026 12:42:39 GMT</pubDate>
  </item>
  <item>
    <title>The Browser Is Part of the Estate: Governing Vendor Scripts as Integration Dependencies</title>
    <link>https://conceptsystems.co.uk/browser-part-of-estate-governing-vendor-scripts/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/browser-part-of-estate-governing-vendor-scripts/</guid>
    <description>Integration audits often stop at APIs and file transfers, leaving embedded vendor scripts outside the governance frame. Yet payment widgets, chat tools, analytics tags and consent code form a broad dependency surface that can read page content, call endpoints and fail without warning. This article sets out a practical control model for inventorying those scripts, mapping their reach, testing their behaviour and assigning clear ownership.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Wed, 11 Nov 2026 21:27:57 GMT</pubDate>
  </item>
  <item>
    <title>Dial Tone as a Dependency: Auditing the Interfaces the PSTN Withdrawal Will Expose</title>
    <link>https://conceptsystems.co.uk/dial-tone-as-a-dependency-pstn-withdrawal-audit/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/dial-tone-as-a-dependency-pstn-withdrawal-audit/</guid>
    <description>The PSTN withdrawal is often framed as a telecoms procurement task. For many UK organisations it is an integration migration: a set of undocumented analogue interfaces that carry alarms, telemetry and escalation behaviour. This article sets out an evidence-led audit that finds those dependencies before the dial tone disappears.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Wed, 11 Nov 2026 14:25:24 GMT</pubDate>
  </item>
  <item>
    <title>Who Opened the Outbound Door? Egress Logs as Integration Evidence</title>
    <link>https://conceptsystems.co.uk/who-opened-the-outbound-door-egress-logs-integration-evidence/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/who-opened-the-outbound-door-egress-logs-integration-evidence/</guid>
    <description>Integration designs rarely document outbound connectivity, yet an unlisted firewall rule can decide whether a release succeeds. This article argues that egress permissions deserve the same contract discipline as APIs, and sets out how UK organisations can use firewall and proxy logs to expose hidden SaaS, payment and data-transfer dependencies before they stall delivery.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Tue, 10 Nov 2026 08:29:33 GMT</pubDate>
  </item>
  <item>
    <title>What the Estate Already Knows: Assembling an Integration Bill of Materials Without a Questionnaire</title>
    <link>https://conceptsystems.co.uk/integration-bill-of-materials-evidence-led-catalogue/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/integration-bill-of-materials-evidence-led-catalogue/</guid>
    <description>Software supply-chain rules have made a bill of materials for libraries and containers routine, yet few UK organisations can list the interfaces their business actually depends on. This article sets out a pragmatic, evidence-led route to an integration bill of materials — built from gateway configurations, certificates, contracts and spend data rather than from memory — and explains what it is worth during audits, supplier transitions and incident response.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Tue, 10 Nov 2026 00:40:01 GMT</pubDate>
  </item>
  <item>
    <title>The Quarter-Turn: Making MTD Income Tax Behave Like an Integration Contract</title>
    <link>https://conceptsystems.co.uk/quarter-turn-mtd-income-tax-integration-contract/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/quarter-turn-mtd-income-tax-integration-contract/</guid>
    <description>Making Tax Digital for Income Tax has now been through enough quarterly cycles for finance teams to see where the real fragility sits. The lesson of 2026 is that MTD is not a compliance add-on but a recurring integration dependency, and it needs the same contracts, error handling and evidence trails as any other live system interface.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Mon, 09 Nov 2026 12:53:04 GMT</pubDate>
  </item>
  <item>
    <title>The Endpoint Behind the Answer: Governing External AI as a Live Integration Dependency</title>
    <link>https://conceptsystems.co.uk/external-ai-live-integration-dependency/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/external-ai-live-integration-dependency/</guid>
    <description>External model access has moved from experimentation to production dependency for many UK organisations. This article sets out the controls that make an AI endpoint governable: pinned versions, cost and rate-limit guardrails, fallback paths, data protection evidence and observability that survives the provider changing the service underneath you.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Sun, 08 Nov 2026 12:31:10 GMT</pubDate>
  </item>
  <item>
    <title>Switching Off the Middle: A Controlled Retirement Sequence for Legacy Integration Platforms</title>
    <link>https://conceptsystems.co.uk/legacy-integration-platform-retirement-sequence/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/legacy-integration-platform-retirement-sequence/</guid>
    <description>Decommissioning an ageing ESB or middleware layer is an architecture discipline in its own right. This article sets out a practical retirement sequence for UK organisations: discover live traffic, freeze new dependencies, run parallel periods with exit criteria, prove the negative and leave an audit trail that survives the server.</description>
    <author>Concept Systems</author>
    <category>Cloud Architecture</category>
    <pubDate>Sun, 08 Nov 2026 12:31:10 GMT</pubDate>
  </item>
  <item>
    <title>Metering the Middleware: An Energy Account for Integration Workloads</title>
    <link>https://conceptsystems.co.uk/metering-middleware-energy-account-integration-workloads/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/metering-middleware-energy-account-integration-workloads/</guid>
    <description>Energy is becoming a board-level concern, but integration estates are rarely metered at the interface level. A lightweight carbon ledger can make batch windows, retry storms and always-on connectors visible to finance and sustainability teams without pretending to be a full life-cycle assessment.</description>
    <author>Concept Systems</author>
    <category>Cloud Architecture</category>
    <pubDate>Sun, 08 Nov 2026 08:30:42 GMT</pubDate>
  </item>
  <item>
    <title>Before the Signature: Making API Capability a Procurement Test</title>
    <link>https://conceptsystems.co.uk/before-signature-api-capability-procurement-test/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/before-signature-api-capability-procurement-test/</guid>
    <description>SaaS contracts are still too often signed before anyone has tested the API that will carry the organisation&#039;s data. Integration capability belongs in procurement, with answers written into the contract rather than discovered during onboarding.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Sun, 08 Nov 2026 08:30:42 GMT</pubDate>
  </item>
  <item>
    <title>Address Reconciliation Without a Master Data Programme: Making the UPRN Work</title>
    <link>https://conceptsystems.co.uk/address-reconciliation-uprn-without-master-data-programme/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/address-reconciliation-uprn-without-master-data-programme/</guid>
    <description>UK organisations often treat address matching as a precursor to a master data programme. A narrower pattern — a governed crosswalk, deterministic matching and controlled fuzzy fallback — can deliver most of the value without the programme.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Sun, 08 Nov 2026 04:32:46 GMT</pubDate>
  </item>
  <item>
    <title>The Calendar Is a Dependency: Integration Operations for the UK Year</title>
    <link>https://conceptsystems.co.uk/calendar-dependency-integration-operations-uk-year/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/calendar-dependency-integration-operations-uk-year/</guid>
    <description>Integration incidents cluster around dates that are entirely predictable. A calendar-aware operating model — with freeze tiers, regional holiday logic and rehearsed year-end runbooks — is a more useful control than a generic change policy.</description>
    <author>Concept Systems</author>
    <category>Cloud Architecture</category>
    <pubDate>Sun, 08 Nov 2026 04:32:46 GMT</pubDate>
  </item>
  <item>
    <title>Auditable by Design: What the New UK Data Regime Asks of Your Interfaces</title>
    <link>https://conceptsystems.co.uk/auditable-by-design-uk-data-regime-interfaces/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/auditable-by-design-uk-data-regime-interfaces/</guid>
    <description>The Data (Use and Access) Act is often framed as a legal and regulatory change, but its practical obligations concentrate at system boundaries. This opinion piece argues that audit trails, purpose-bound APIs and revocable access are integration architecture decisions, not compliance paperwork.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Sun, 08 Nov 2026 00:32:48 GMT</pubDate>
  </item>
  <item>
    <title>The 2am Test: Matching Data Movement to the Team That Must Run It</title>
    <link>https://conceptsystems.co.uk/2am-test-data-movement-patterns-operations/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/2am-test-data-movement-patterns-operations/</guid>
    <description>Batch, change data capture and event streams each carry a different operational bill. This practical guide gives UK teams a decision framework based on latency, volume, failure tolerance and in-house capability, with the 2am debug test as the final gate.</description>
    <author>Concept Systems</author>
    <category>Cloud Architecture</category>
    <pubDate>Sun, 08 Nov 2026 00:32:48 GMT</pubDate>
  </item>
  <item>
    <title>Exit Is an Architecture, Not a Clause: Making Cloud Portability an Integration Discipline</title>
    <link>https://conceptsystems.co.uk/exit-architecture-not-clause-cloud-portability/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/exit-architecture-not-clause-cloud-portability/</guid>
    <description>UK buyers now have more contractual leverage over cloud switching than at any point in the last decade. The remaining obstacle is architectural: identities, event schemas and data pipelines that only make sense inside one provider. Portability has to be designed into the integration layer, not negotiated into the contract.</description>
    <author>Concept Systems</author>
    <category>Cloud Architecture</category>
    <pubDate>Sat, 07 Nov 2026 20:33:17 GMT</pubDate>
  </item>
  <item>
    <title>The Interfaces Nobody Owns: Auditing Integration Debt Before It Becomes an Incident</title>
    <link>https://conceptsystems.co.uk/interfaces-nobody-owns-auditing-integration-debt/</link>
    <guid isPermaLink="true">https://conceptsystems.co.uk/interfaces-nobody-owns-auditing-integration-debt/</guid>
    <description>Most UK organisations can account for every software licence but not for the thousands of interfaces holding their systems together. Treating those links as tracked, depreciating assets — and auditing them on a four-week cycle — turns an invisible liability into a fundable remediation plan.</description>
    <author>Concept Systems</author>
    <category>Integration Strategy</category>
    <pubDate>Sat, 07 Nov 2026 20:33:17 GMT</pubDate>
  </item>
</channel>
</rss>