{"id":36873,"date":"2025-07-10T09:20:18","date_gmt":"2025-07-10T08:20:18","guid":{"rendered":"https:\/\/www.dataiq.global\/?post_type=article&p=36873"},"modified":"2025-07-10T09:20:18","modified_gmt":"2025-07-10T08:20:18","slug":"data-sharing-aerospace-and-defence","status":"publish","type":"article","link":"https:\/\/www.dataiq.global\/devstage\/articles\/data-sharing-aerospace-and-defence\/","title":{"rendered":"Successfully Enabling Data Sharing in the Aerospace and Defence Sector"},"content":{"rendered":"

Peer questions<\/span>\u00a0<\/span><\/h3>\n
    \n
  • What makes internal versus external data sharing uniquely difficult in aerospace and defence?<\/span>\u00a0<\/span><\/li>\n
  • How can organisations mitigate the tension between data sovereignty and the need to collaborate?<\/span>\u00a0<\/span><\/li>\n
  • What cultural and behavioural blockers persist, even where legal and technical solutions exist?<\/span>\u00a0<\/span><\/li>\n
  • What models exist for trusted, decentralised data sharing across supply chains?<\/span>\u00a0<\/span><\/li>\n
  • Can industry-level collaboration accelerate standardisation and interoperability?<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

    \u00a0<\/span><\/p>\n

    Making internal data sharing the default<\/span>\u00a0<\/span><\/h3>\n

    One aerospace firm applies a policy called \u201copen by consent\u201d: internal data is presumed shareable unless explicitly restricted. Open by consent works on the notion that data is presumed shareable, but only with explicit and informed consent from the data subject (unless there are legal or ethical reasons to override this).\u00a0<\/span>\u00a0<\/span><\/p>\n

    This flips the burden of justification and prevents siloed hoarding. \u201cFor internal data, you need to justify why you cannot share it,\u201d said a senior data governance expert. The leader found that this approach maintained compliance and documentation of everything while avoiding sharing blockages. That shift accelerated uptake, especially when backed by executive sponsorship.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Culture, not compliance, is the main blocker<\/span>\u00a0<\/span><\/h3>\n

    While legal constraints like the International Traffic in Arms Regulations (ITAR) \u2013 a US government legislation controlling trade in defence articles \u2013 and export control are real and must be adhered to, many leaders agreed the bigger challenge is behavioural and cultural. \u201cThe safe answer is always \u2018no\u2019,\u201d said one attendee. Reluctance to make a change or evolve a system is often rooted in habit or fear, not regulation. Even when data can be shared, users default to legacy platforms or avoid perceived risks.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Bridge the knowledge gap to change behaviour<\/span>\u00a0<\/span><\/h3>\n

    Unlike sectors where commercial motives impede data sharing, defence organisations face a different cultural issue: people want to do the right thing, but they are not sure how. \u201cI think the quandary is trying to do the right thing, but not really knowing what the right thing is,\u201d said one participant. To combat this, data and AI leaders need to secure investment in education and clarity around classification and consent to convert agreement into action.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Jurisdictions cause sharing complexities, even internally<\/span>\u00a0<\/span><\/h3>\n

    Even intra-group sharing can become complex when organisations span jurisdictions. A CTO described how inside the UK, sharing is seen as relatively smooth. But when sharing involves crossing borders, data and AI leaders are effectively sharing externally, even within their own company. This complicates policy and language alignment. There must be a high level understand of different national regulations from numerous departments and leaders in a multinational corporation which requires further investment and time considerations.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Ensure semantic clarity for correct shared data use<\/span>\u00a0<\/span><\/h3>\n

    Some data producers resist sharing due to fear of misinterpretation. \u201cSometimes you cannot understand my data, and I would prefer you don’t have it, because you will make bad decisions because you don’t understand it,\u201d said one contributor. Semantic clarity and access become critical to avoid incorrect usage and blame.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Symmetry is essential for successful cross-functional sharing<\/span>\u00a0<\/span><\/h3>\n

    Structured data often flows from design to engineering to support, but value is realised much later. \u201cContributing data where you see the benefit is one thing, but sharing data for the benefit of others in the organisation is something else. When input, process, and output in an organisation are asymmetric, it is far more difficult to achieve alignment around sharing,\u201d observed one attendee. The asymmetry of effort and reward needs strategic resolution.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Decentralisation can cause governance problems<\/span>\u00a0<\/span><\/h3>\n

    Pooling sensitive data centrally is not feasible in the defence sector and comes with serious concerns regarding governance and ownership. One participant explained their pivot towards a decentralised model: \u201cWe federated services in the middle that will help organise data, including trust frameworks and managing data sharing agreements covering the data provider and the data consumer\u2019s access and usage policies. But data being decentralised and having one architecture to pull all the data causes a governance issue: who is the one governing and honing the architecture in the middle?\u201d<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Standardisation is the sector\u2019s Achilles\u2019 heel<\/span>\u00a0<\/span><\/h3>\n

    While all attendees agreed on the need for digital continuity and structured data exchange, the industry lacks common semantics and technical standards. \u201cA key challenge is that our sector is not good with standardisation. We like things made by ourselves and consistently over engineering stuff, making it difficult to align on one simple way to achieve success as an industry,\u201d one attendee remarked.<\/span>\u00a0<\/span><\/p>\n

    Without alignment, scalable collaboration is impossible. It is essential that data and AI leaders in the defence industry come together regularly to discuss and develop digital structured data exchanges.\u00a0<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Cultural change to improve data sharing<\/span>\u00a0<\/span><\/h3>\n

    Attendees discussed how technologies enabling column and row-based permissions exist, but uptake is patchy. As one data and AI leader put it, \u201cWhen someone says, \u2018can I access that data? Can I share it? Can I put a copy in the lake house?\u2019 The safe option is to say no, and that’s the barrier we’ve got to try and get over. If you’re allowed to access it in source, you should be able to access it from the lake house. But the culture says \u2018well, let me keep hold of it\u2019.\u201d The industry is in a situation where capability is ahead of maturity and a cultural shift \u2013 which notoriously takes time \u2013 is required to rectify this bottleneck.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Look to other sectors for models and pitfalls<\/span>\u00a0<\/span><\/h3>\n

    The group welcomed the idea of learning from open banking\u2019s trust frameworks and market architectures. \u201cThere’s nothing like that in our industry. It is more linear in supply chain terms, and the controls on data sharing,\u201d said one participant. Crucially, any model must scale from bilateral agreements to decentralised ecosystems without compromising control.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    What data and AI leaders should do<\/span><\/b>\u00a0<\/span><\/h3>\n
      \n
    • Formalise share by default policies backed by executive enforcement.<\/span>\u00a0<\/span><\/li>\n
    • Train teams and leaders on semantic understandings in addition to legal compliance.<\/span>\u00a0<\/span><\/li>\n
    • Create cross-functional data usage maps to surface asymmetries and bottlenecks.<\/span>\u00a0<\/span><\/li>\n
    • Co-develop a decentralised data sharing architecture with partners.<\/span>\u00a0<\/span><\/li>\n
    • Define lightweight trust frameworks and enforceable access controls.<\/span>\u00a0<\/span><\/li>\n
    • Engage industry peers in standards-setting, especially for structured data.<\/span>\u00a0<\/span><\/li>\n
    • Pilot internal marketplaces for low-risk data to build confidence.<\/span>\u00a0<\/span><\/li>\n
    • Audit and streamline existing bilateral agreements to reduce redundancy.<\/span>\u00a0<\/span><\/li>\n
    • Avoid over-reliance on central platforms and focus on interoperable, federated services.<\/span>\u00a0<\/span><\/li>\n
    • Explore follow-up sessions with other sector pioneers to understand scalable governance models.<\/span>\u00a0<\/span><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

      Aerospace and defence data and AI leaders examine the challenges surrounding security and regulation of sharing data both within and between organisations.<\/p>\n","protected":false},"author":19,"featured_media":36874,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","_searchwp_excluded":"","footnotes":""},"categories":[129,398],"tags":[1400,1264,384,171,1129,1074,1401],"pillar":[198],"class_list":["post-36873","article","type-article","status-publish","format-standard","has-post-thumbnail","hentry","category-editorial","category-public","tag-aerospace","tag-ai-governance","tag-compliance-and-regulation","tag-data-governance","tag-defence","tag-security","tag-sharing","pillar-governance"],"acf":[],"publishpress_future_action":{"enabled":false,"date":"2026-05-20 22:44:54","action":"change-status","newStatus":"draft","terms":[],"taxonomy":"category","extraData":[]},"publishpress_future_workflow_manual_trigger":{"enabledWorkflows":[]},"_links":{"self":[{"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/article\/36873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/types\/article"}],"author":[{"embeddable":true,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/comments?post=36873"}],"version-history":[{"count":2,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/article\/36873\/revisions"}],"predecessor-version":[{"id":36876,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/article\/36873\/revisions\/36876"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/media\/36874"}],"wp:attachment":[{"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/media?parent=36873"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/categories?post=36873"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/tags?post=36873"},{"taxonomy":"pillar","embeddable":true,"href":"https:\/\/www.dataiq.global\/devstage\/wp-json\/wp\/v2\/pillar?post=36873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}