{"id":1131,"date":"2026-03-24T06:37:53","date_gmt":"2026-03-24T06:37:53","guid":{"rendered":"https:\/\/www.srinsoft.engineering\/blogs\/?p=1131"},"modified":"2026-04-02T09:38:31","modified_gmt":"2026-04-02T09:38:31","slug":"5-common-coordination-issues-solved-by-structural-bim-models","status":"publish","type":"post","link":"https:\/\/www.srinsoft.engineering\/blogs\/5-common-coordination-issues-solved-by-structural-bim-models\/","title":{"rendered":"5 Common Coordination Issues Solved by Structural BIM Models"},"content":{"rendered":"\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/Blog-new_Common-Coordination-Issues-32-1-1024x538.jpg\" alt=\"Structural BIM Models\" class=\"wp-image-1132\" srcset=\"https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/Blog-new_Common-Coordination-Issues-32-1-1024x538.jpg 1024w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/Blog-new_Common-Coordination-Issues-32-1-300x158.jpg 300w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/Blog-new_Common-Coordination-Issues-32-1-768x403.jpg 768w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/Blog-new_Common-Coordination-Issues-32-1.jpg 1200w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p><strong><em>Ballast does the work.&nbsp;Steel gets the credit.&nbsp;<\/em><\/strong>&nbsp;<\/p>\n\n\n\n<p><em>In rail tracks, ballast&nbsp;is what&nbsp;distributes load, maintains alignment, and absorbs stress long before visible failure occurs.<\/em>&nbsp;<\/p>\n\n\n\n<p><em>And in complex&nbsp;construction&nbsp;projects, coordination&nbsp;plays the same role.&nbsp;<\/em>&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Structural BIM&nbsp;Coordination&nbsp;&#8211;&nbsp;The Cost of Inaction&nbsp;<\/h2>\n\n\n\n<p>When structural BIM is not treated as the coordination backbone, expect:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Re-coordination cycles after \u201capproved\u201d milestones&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>RFIs driven by&nbsp;confusion about the&nbsp;positions, not&nbsp;desTign&nbsp;complexity&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Fabrication packages built on misaligned datums&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Temporary works designed on incorrect structural assumptions&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Procurement delays from spec-model discrepancies&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Program recovery attempts that trigger structural rechecks&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Erosion of contractor confidence in the&nbsp;<a href=\"https:\/\/www.srinsoft.engineering\/blogs\/bim-coordination-services\/\" target=\"_blank\" rel=\"noopener\" title=\"\">federated model<\/a>&nbsp;<\/li>\n<\/ul>\n\n\n\n<p><a href=\"https:\/\/www.srinsoft.engineering\/bim-service\/\" target=\"_blank\" rel=\"noopener\" title=\"\">Structural BIM models<\/a>\u00a0reinforce coordination before execution begins. Here are five failures they prevent.\u00a0These\u00a0are workflow failures.\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Issue #1:&nbsp;BIM&nbsp;Clash Detection Against Immature Models&nbsp;<\/h2>\n\n\n\n<p>Structural BIM Modeling:&nbsp;Most problems with <a href=\"https:\/\/www.srinsoft.engineering\/blogs\/bim-clash-detection\/\" title=\"\">clash detection<\/a> come from running it against the wrong models, at the wrong LOD, at the wrong time, and calling that&nbsp;BIM&nbsp;coordination.&nbsp;<\/p>\n\n\n\n<p>Most persistent clashes trace back to three things:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Late model submissions compress review cycles, leaving little time to resolve clashes before sign-off and pushing unresolved issues to site.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>LOD mismatches where structural reaches LOD 300\u2013350 while MEP&nbsp;remains&nbsp;at LOD 200 or early 300, producing clash reports that look clean but fail once services are fully developed.&nbsp;&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>And parallel workflows where disciplines develop in isolation and converge only at coordination meetings, by which point changes are&nbsp;expensive&nbsp;and nobody wants to own them.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Structural models often become the earliest stable reference and can set the coordination baseline.&nbsp;<\/p>\n\n\n\n<p>That means defining LOD expectations per coordination&nbsp;milestone, and&nbsp;treating the structural model as the anchor of the federated model.&nbsp;<br>&nbsp;<br><strong><em>Example:<\/em><\/strong>&nbsp;A hospital project runs clash detection at 60% CD&nbsp;stage.&nbsp;&nbsp;Reports come back clean. Three weeks&nbsp;later&nbsp;MEP&nbsp;updates&nbsp;their model with fully coordinated ductwork \u2014 now 340 clashes in the plant room alone.&nbsp;&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Issue #2:&nbsp;Uncontrolled Datums in Federated Models<\/h2>\n\n\n\n<p>Things&nbsp;accumulates&nbsp;quietly, one discipline referencing finished floor levels, another working to structural slab, a third importing coordinates from a survey point that was never formally&nbsp;established&nbsp;as the shared project reference.&nbsp;<\/p>\n\n\n\n<p>A 50mm datum discrepancy in early design becomes a 50mm discrepancy in every updated model that references it. By the time it&nbsp;surfaces,&nbsp;&nbsp;usually&nbsp;during&nbsp;fabrication&nbsp;alignment,&nbsp;&nbsp;it&#8217;s&nbsp;embedded in hundreds of elements across multiple disciplines.&nbsp;Unpicking it&nbsp;is&nbsp;a coordination crisis.&nbsp;<\/p>\n\n\n\n<p>A coordination protocol led by survey control and structural reference geometry prevents this, because the project&nbsp;establishes&nbsp;a single shared coordinate system and level structure early in the model setup.&nbsp;Shared coordinates, agreed levels, a single survey point formally adopted across all disciplines from project start. When structural owns that baseline and enforces it at federated model setup, the problem&nbsp;doesn&#8217;t&nbsp;compound \u2014 it&nbsp;doesn&#8217;t&nbsp;start.&nbsp;<br>&nbsp;<br><strong><em>Example:<\/em><\/strong>&nbsp;Structural models&nbsp;to&nbsp;structural&nbsp;slab. Architecture models to finished floor levels. The offset between them is never formally documented or shared in the coordination model.&nbsp;Eight months in, the facade contractor imports both models to start panel sizing \u2014 and every floor is 40mm out across the entire building envelope.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"286\" src=\"https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bimstructuralservices-1024x286.jpg\" alt=\"\" class=\"wp-image-1145\" srcset=\"https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bimstructuralservices-1024x286.jpg 1024w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bimstructuralservices-300x84.jpg 300w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bimstructuralservices-768x214.jpg 768w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bimstructuralservices.jpg 1200w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Issue #3:&nbsp;Hidden Construction Sequencing Assumptions&nbsp;<\/h2>\n\n\n\n<p>Structural engineers constantly make sequencing decisions, such as&nbsp;determining&nbsp;concrete pour sequences based on movement joints.&nbsp;Propping assumptions that&nbsp;determine&nbsp;how&nbsp;loads&nbsp;transfer between slabs during construction and how long temporary&nbsp;supports&nbsp;must remain in place.&nbsp;Steel erection&nbsp;logic that&nbsp;determines&nbsp;which connections can be made&nbsp;permanent&nbsp;and when.&nbsp;&nbsp;<\/p>\n\n\n\n<p>The result is a 4D program built against geometry with no awareness of the constraints behind it. The contractor sequences based on what looks logical spatially, not what the structural design&nbsp;actually requires.&nbsp;Temporary works may be designed without full visibility into the propping and staging assumptions used in the structural design.&nbsp;A pour sequence is changed to suit the schedule, and no one flags that the new order alters the&nbsp;deflection&nbsp;assumptions used in the design calculations.&nbsp;<\/p>\n\n\n\n<p>The sequencing logic lives in calculation packages, engineer&#8217;s notes, and meetings that the contractor&nbsp;wasn&#8217;t&nbsp;in. Bridging that gap means working with the structural engineer to surface those assumptions explicitly \u2014 model phasing that reflects pour sequences, element naming that communicates construction stage, 4D links that are built around structural logic rather than just program logic.&nbsp;<\/p>\n\n\n\n<p><strong><em>Example:<\/em><\/strong>&nbsp;A contractor reorders the pour sequence on a post-tensioned deck to recover two weeks of program. The structural engineer had assumed a specific sequence to manage long-term deflection. Nobody told the contractor.&nbsp;The slab begins behaving outside the deflection assumptions used in the&nbsp;design&nbsp;and a remediation assessment eats the two weeks back and then some.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Issue #4:&nbsp;Change Without a Model of Record&nbsp;<\/h2>\n\n\n\n<p>Late design changes are inevitable. Without a clear model of record driving updates, this is what happens.&nbsp;&nbsp;Architect issues a revised floor plate. Structural updates the model. MEP&nbsp;doesn&#8217;t&nbsp;receive the notification, or&nbsp;receives&nbsp;it too late, or receives it but&nbsp;hasn&#8217;t&nbsp;federated the latest structural model yet. The coordination model being reviewed in the next clash session is already out of date. Nobody knows whose model is current. The RFI log starts growing.&nbsp;<\/p>\n\n\n\n<p>Structural&nbsp;is the natural anchor for change control because structural changes have the broadest downstream impact. A column shift affects architecture, MEP routing, facade, and foundations simultaneously. When structural BIM is treated as the coordination backbone,&nbsp;change notifications flow from it. Other disciplines update against it. The federated model has a clear hierarchy.&nbsp;<\/p>\n\n\n\n<p><strong><em>Example:<\/em><\/strong>&nbsp;Architect shifts a core wall 300mm in response to a tenant requirement. Structural updates the model. MEP coordinates against the&nbsp;previous&nbsp;version for another three weeks before anyone notices. Eighteen RFIs and a re-coordination session&nbsp;follow.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Issue #5.&nbsp;Specification Data That Never Reaches the Model<\/h2>\n\n\n\n<p>The model shows one thing. The specification says another.&nbsp;<\/p>\n\n\n\n<p>It shows up in predictable places. Steel grades that were updated in the spec after a value engineering exercise but never reflected in the model. Fire ratings on structural elements that conflict with what the passive fire protection package is designed around. Connection details that exist in the calculation package but have no model representation \u2014 so fabricators are working from geometry that&nbsp;doesn&#8217;t&nbsp;communicate the full design intent.&nbsp;<\/p>\n\n\n\n<p>Making the structural model a genuine&nbsp;single source&nbsp;of truth requires two things most projects&nbsp;skip. First, a formal link between specification updates and model update obligations \u2014 when the spec changes, the model changes.&nbsp;Second, model attributes that&nbsp;actually carry&nbsp;specification data.&nbsp;Material grades, fire ratings, surface treatments embedded in element properties.&nbsp;<\/p>\n\n\n\n<p><strong><em>Example:<\/em><\/strong>&nbsp;Steel fabricator prices the job from the model. S275 throughout. Value engineering six months prior had upgraded connections to S355 in the spec. The discrepancy surfaces during procurement. Reorder, delay, cost delta \u2014 all of it avoidable.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bim-drafting-services-1024x538.jpg\" alt=\"\" class=\"wp-image-1147\" srcset=\"https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bim-drafting-services-1024x538.jpg 1024w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bim-drafting-services-300x158.jpg 300w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bim-drafting-services-768x403.jpg 768w, https:\/\/www.srinsoft.engineering\/blogs\/wp-content\/uploads\/2026\/03\/bim-drafting-services.jpg 1200w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Coordination Is a Structural Problem&nbsp;<\/h2>\n\n\n\n<p><a href=\"https:\/\/www.srinsoft.engineering\/automation-service\/\" target=\"_blank\" rel=\"noopener\" title=\"\">Coordination<\/a>&nbsp;failures&nbsp;follow predictable patterns \u2014 late models, misaligned datums, assumptions that never leave the engineer&#8217;s calculations, changes that propagate without an anchor. The BIM manager&#8217;s job&nbsp;is&nbsp;to build&nbsp;the&nbsp;workflow that makes late-stage surprises structurally impossible.&nbsp;<\/p>\n\n\n\n<p>A mature structural BIM model&nbsp;doesn&#8217;t&nbsp;just reduce RFIs. It changes who controls the project during execution.&nbsp;<\/p>\n\n\n\n<p>If&nbsp;you&#8217;re&nbsp;working on a complex project and the structural&nbsp;BIM&nbsp;model&nbsp;isn&#8217;t&nbsp;doing that work yet,&nbsp;that&#8217;s&nbsp;the gap worth closing.&nbsp;<\/p>\n\n\n\n<p>The best practice in any discipline is to continuously link the structural model with other models like ID, landscape, and architecture. Regularly reloading and coordinating models prevents many future clashes.&nbsp;<\/p>\n\n\n\n<p>SRINSOFT Engineering&nbsp;delivers&nbsp;high-end&nbsp;structural&nbsp;<a href=\"https:\/\/www.srinsoft.engineering\/design-service\/\" target=\"_blank\" rel=\"noopener\" title=\"\">3D&nbsp;BIM modeling services<\/a>&nbsp;and&nbsp;deliver&nbsp;models&nbsp;built for coordination, not just compliance. Explore how we structure models to&nbsp;eliminate&nbsp;late-stage coordination risk.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FAQs<\/h3>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong>1. Why are clashes still happening even after running\u00a0Navisworks\u00a0weekly?<\/strong><\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Clashes occur when the structural model is not actively coordinated with other disciplines like interior design, landscape, and architecture.&nbsp;<br>Expecting a 100% clash-free model at the&nbsp;initial&nbsp;stage is unrealistic. Early-stage models are still evolving, with incomplete data and inconsistent levels of detail. The goal is to&nbsp;identify&nbsp;critical issues early and reduce coordination noise as the model matures.&nbsp;<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong><strong>2. How do\u00a0I\u00a0enforce consistent levels and shared coordinates across\u00a0ll\u00a0disciplines?<\/strong>\u00a0<\/strong><\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Issue a formal coordination baseline early. Lock shared coordinates, levels, and survey points before federating. Reject models that&nbsp;don\u2019t&nbsp;comply.<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong><strong><strong>3. How can\u00a0structural\u00a0sequencing assumptions be reflected in the model?<\/strong>\u00a0<\/strong><\/strong><\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Use phasing, construction-stage parameters, and 4D links. Embed pour sequence and propping logic visibly instead of leaving it in calculation notes.&nbsp;<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong><strong><strong><strong>4. Who should own change control in a federated\u00a0BIM\u00a0environment?<\/strong>\u00a0<\/strong><\/strong><\/strong><\/h3><div class=\"aioseo-faq-block-answer\">\n<p>The discipline with the widest downstream impact.&nbsp;Typically&nbsp;structural. Establish a model of record and require updates to reference it.&nbsp;<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong><strong><strong><strong><strong>5. How do\u00a0I\u00a0prevent spec and model mismatches before procurement?<\/strong><\/strong><\/strong><\/strong><\/strong><\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Link specification revisions to mandatory model updates. Embed material grades and fire ratings as element parameters, not external documents.&nbsp;<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq tl-dr-box has-background\" style=\"background-color:#ffe4e8;padding-top:15px;padding-right:15px;padding-bottom:15px;padding-left:15px\"><h3 class=\"aioseo-faq-block-question\"><strong>TL;DR<\/strong><\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Most persistent coordination failures follow predictable structural patterns. They are not random clashes. They stem from LOD drift, uncontrolled datums, hidden sequencing logic, unmanaged change, and spec-model gaps.&nbsp;<\/p>\n<\/div><\/div>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ballast does the work.&nbsp;Steel gets the credit.&nbsp;&nbsp; In rail tracks, ballast&nbsp;is what&nbsp;distributes load, maintains alignment, and absorbs stress long before [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":1132,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"","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":"","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":""},"categories":[3],"tags":[],"class_list":["post-1131","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bim"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/posts\/1131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/comments?post=1131"}],"version-history":[{"count":8,"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/posts\/1131\/revisions"}],"predecessor-version":[{"id":1177,"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/posts\/1131\/revisions\/1177"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/media\/1132"}],"wp:attachment":[{"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/media?parent=1131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/categories?post=1131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.srinsoft.engineering\/blogs\/wp-json\/wp\/v2\/tags?post=1131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}