The Role of Robotics & Automation in Data Centre Delivery  Data Centre Magazine

FORM Brands Studio has given London’s Air Ambulance Charity a new look. Rather than transporting patients to hospital, the charity’s doctors and paramedics treat seriously injured people at the scene from its two helicopters and eight cars. It is the only organisation performing this role in London. Established in 1989, it is called to a rising number of patients across the capital every year, helping more than 2,000 people in 2024. London’s Air Ambulance Charity (LAAC) needs £17m a year to operate, 96% which comes from donations. “But 60% of Londoners don’t know we’re a charity,” says LAAC’s director of fundraising and marketing, Jayne Clarke. FORM Brands Studio identity for London’s Air Ambulance Charity in OOH posters Its new organisational strategy is about raising awareness, enhancing fundraising efforts and strengthening its connection with London’s communities. “We’re trying to make sure the strategy is about hope and looking forward to the future,” Clarke says. To accompany this new strategy, the charity also decided to change up its visual identity. “Our previous branding was very corporate,” Clarke admits.FORM Brands Studio won the job after a pitch. Strategy director Beth Andlaw set up the east London agency in 2022 with creative director Alex Andlaw. Before that she had been in comms and PR, and had worked with LAAC on and off for about 20 years. FORM Brands Studio identity for London’s Air Ambulance Charity on stage FORM introduced a new wordmark, colour palette, typeface, icons, motion, creative copy, messaging, fundraising memorabilia and photography. However, the existing helicopter icon was retained. “It has a lot of love and legacy,” says Clarke. The agency’s brand idea, Propelling Promise, was inspired by the urgent, intense nature of the work carried out by LAAC’s clinical and operational crews. That was used to give structure to creative copy lines and the new tone of voice. Each lead line includes an element of “propelling” to imply urgency and momentum, and “promise” to imply warmth and hope. That resulted in lines including “Trauma doesn’t stop. Neither do we” and “Here for London. Today, tomorrow, always.” FORM brought in Peggy Nyamekye to work on the copywriting. Meanwhile, the visual identity, developed with designer Mayan Mistry, comprises a gradient design system, drawing on the rotational motion of helicopter blades. Borough names are repeated in radiating patterns and overlaid with the gradient. Red is still central to the charity’s identity, but FORM introduced the vivid orange worn by medics on-scene. “These colours blend in the gradient, creating a visual signature that speaks to urgency, action, optimism and hope,” says Alex Andlaw. https://d3faj0w6aqatyx.cloudfront.net/uploads/2025/06/LAA_OOH_TUBE_1920x1080.mp4 With the help of motion graphics designer Matt Fowler, the agency introduced movement to the branding, to reflect the aircraft’s blades in flight. The logo’s new wordmark is in Barlow, inspired by the existing big white lettering on the helicopter tail booms. Before, the charity’s name was written lower case in a thinner font. “Now it’s bigger, bolder and more impactful,” says Alex Andlaw. FORM also redesigned the icons to have more personality but still be functional. “The icons help the team talk about quite hard subjects,” he says, such as casualties, and the designs had to balance warmth and realism. “We did quite a few hearts, some look too detailed and some too basic,” he explains. The agency also created a series of collectible badges, inspired by the embroidered badges worn by the charity’s doctors and pilots.FORM Brands Studio identity for London’s Air Ambulance Charity in Instagram posts Meanwhile, photographer James Pearson-Howes was briefed to capture real people, places and moments from across London. The new branding had to resonate with very different types of donors, from the charity’s collection buckets to seven-figure corporate donations, says Clarke. “And the doctors wearing the brand have very strong opinions, as do the pilots. FORM took in all these views and managed to make all those people happy.” https://d3faj0w6aqatyx.cloudfront.net/uploads/2025/06/LAA_OOH_BILLBOARD_1920x1080.mp4 FORM Brands Studio identity for London’s Air Ambulance Charity FORM Brands Studio identity for London’s Air Ambulance Charity in OOH posters

Email authentication protocols like SPF, DKIM, and DMARC play a critical role in protecting domains from spoofing and phishing. However, when SEGs are introduced into the email path, the interaction with these protocols becomes more complex. Security gateways(SEGs) are a core part of many organizations’ email infrastructure. They act as intermediaries between the public internet and internal mail systems, inspecting, filtering, and routing messages. This blog examines how security gateways handle SPF, DKIM, and DMARC, with real-world examples from popular gateways such as Proofpoint, Mimecast, and Avanan. We’ll also cover best practices for maintaining authentication integrity and avoiding misconfigurations that can compromise email authentication or lead to false DMARC failures. Security gateways often sit at the boundary between your organization and the internet, managing both inbound and outbound email traffic. Their role affects how email authentication protocols behave. An inbound SEG examines emails coming into your organization. It checks SPF, DKIM, and DMARC to determine if the message is authentic and safe before passing it to your internal mail servers. An outbound SEG handles emails sent from your domain. It may modify headers, rewrite envelope addresses, or even apply DKIM signing. All of these can impact SPF,  DKIM, or DMARC validation on the recipient’s side. Understanding how SEGs influence these flows is crucial to maintaining proper authentication and avoiding unexpected DMARC failures. Inbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When an email comes into your organization, your security gateway is the first to inspect it. It checks whether the message is real, trustworthy, and properly authenticated. Let’s look at how different SEGs handle these checks. Avanan (by Check Point) SPF: Avanan verifies whether the sending server is authorized to send emails for the domain by checking the SPF record. DKIM: It verifies if the message was signed by the sending domain and if that signature is valid. DMARC: It uses the results of the SPF and DKIM check to evaluate DMARC. However, final enforcement usually depends on how DMARC is handled by Microsoft 365 or Gmail, as Avanan integrates directly with them. Avanan offers two methods of integration:1. API integration: Avanan connects via APIs, no change in MX, usually Monitor or Detect modes.2. Inline integration: Avanan is placed inline in the mail flow (MX records changed), actively blocking or remediating threats. Proofpoint Email Protection SPF: Proofpoint checks SPF to confirm the sender’s IP is authorized to send on behalf of the domain. You can set custom rules (e.g. treat “softfail” as “fail”). DKIM: It verifies DKIM signatures and shows clear pass/fail results in logs. DMARC: It fully evaluates DMARC by combining SPF and DKIM results with alignment checks. Administrators can configure how to handle messages that fail DMARC, such as rejecting, quarantining, or delivering them. Additionally, Proofpoint allows whitelisting specific senders you trust, even if their emails fail authentication checks. Integration Methods Inline Mode: In this traditional deployment, Proofpoint is positioned directly in the email flow by modifying MX records. Emails are routed through Proofpoint’s infrastructure, allowing it to inspect and filter messages before they reach the recipient’s inbox. This mode provides pre-delivery protection and is commonly used in on-premises or hybrid environments. API-Based (Integrated Cloud Email Security – ICES) Mode: Proofpoint offers API-based integration, particularly with cloud email platforms like Microsoft 365 and Google Workspace. In this mode, Proofpoint connects to the email platform via APIs, enabling it to monitor and remediate threats post-delivery without altering the email flow. This approach allows for rapid deployment and seamless integration with existing cloud email services. Mimecast SPF: Mimecast performs SPF checks to verify whether the sending server is authorized by the domain’s SPF record. Administrators can configure actions for SPF failures, including block, quarantine, permit, or tag with a warning. This gives flexibility in balancing security with business needs. DKIM: It validates DKIM signatures by checking that the message was correctly signed by the sending domain and that the content hasn’t been tampered with. If the signature fails, Mimecast can take actions based on your configured policies. DMARC: It fully evaluates DMARC by combining the results of SPF and DKIM with domain alignment checks. You can choose to honor the sending domain’s DMARC policy (none, quarantine, reject) or apply custom rules, for example, quarantining or tagging messages that fail DMARC regardless of the published policy. This allows more granular control for businesses that want to override external domain policies based on specific contexts. Integration Methods Inline Deployment: Mimecast is typically deployed as a cloud-based secure email gateway. Organizations update their domain’s MX records to point to Mimecast, so all inbound (and optionally outbound) emails pass through it first. This allows Mimecast to inspect, filter, and process emails before delivery, providing robust protection. API Integrations: Mimecast also offers API-based services through its Mimecast API platform, primarily for management, archival, continuity, and threat intelligence purposes. However, API-only email protection is not Mimecast’s core model. Instead, the APIs are used to enhance the inline deployment, not replace it. Barracuda Email Security Gateway SPF: Barracuda checks the sender’s IP against the domain’s published SPF record. If the check fails, you can configure the system to block, quarantine, tag, or allow the message, depending on your policy preferences. DKIM: It validates whether the incoming message includes a valid DKIM signature. The outcome is logged and used to inform further policy decisions or DMARC evaluations. DMARC: It combines SPF and DKIM results, checks for domain alignment, and applies the DMARC policy defined by the sender. Administrators can also choose to override the DMARC policy, allowing messages to pass or be treated differently based on organizational needs (e.g., trusted senders or internal exceptions). Integration Methods Inline mode (more common and straightforward): Barracuda Email Security Gateway is commonly deployed inline by updating your domain’s MX records to point to Barracuda’s cloud or on-premises gateway. This ensures that all inbound emails pass through Barracuda first for filtering and SPF, DKIM, and DMARC validation before being delivered to your mail servers. Deployment Behind the Corporate Firewall: Alternatively, Barracuda can be deployed in transparent or bridge mode without modifying MX records. In this setup, the gateway is placed inline at the network level, such as behind a firewall, and intercepts mail traffic transparently. This method is typically used in complex on-premises environments where changing DNS records is not feasible. Cisco Secure Email (formerly IronPort) Cisco Secure Email acts as an inline gateway for inbound email, usually requiring your domain’s MX records to point to the Cisco Email Security Appliance or cloud service. SPF: Cisco Secure Email verifies whether the sending server is authorized in the sender domain’s SPF record. Administrators can set detailed policies on how to handle SPF failures. DKIM: It validates the DKIM signature on incoming emails and logs whether the signature is valid or has failed. DMARC: It evaluates DMARC by combining SPF and DKIM results along with domain alignment checks. Admins can configure specific actions, such as quarantine, reject, or tag, based on different failure scenarios or trusted sender exceptions. Integration methods On-premises Email Security Appliance (ESA): You deploy Cisco’s hardware or virtual appliance inline, updating MX records to route mail through it for filtering. Cisco Cloud Email Security: Cisco offers a cloud-based email security service where MX records are pointed to Cisco’s cloud infrastructure, which filters and processes inbound mail. Cisco Secure Email also offers advanced, rule-based filtering capabilities and integrates with Cisco’s broader threat protection ecosystem, enabling comprehensive inbound email security. Outbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When your organization sends emails, security gateways can play an active role in processing and authenticating those messages. Depending on the configuration, a gateway might rewrite headers, re-sign messages, or route them through different IPs – all actions that can help or hurt the authentication process. Let’s look at how major SEGs handle outbound email flow. Avanan – Outbound Handling and Integration Methods Outbound Logic Avanan analyzes outbound emails primarily to detect data loss, malware, and policy violations. In API-based integration, emails are sent directly by the original mail server (e.g., Microsoft 365 or Google Workspace), so SPF and DKIM signatures remain intact. Avanan does not alter the message or reroute traffic, which helps maintain full DMARC alignment and domain reputation. Integration Methods 1. API Integration: Connects to Microsoft 365 or Google Workspace via API. No MX changes are needed. Emails are scanned after they are sent, with no modification to SPF, DKIM, or the delivery path.  How it works: Microsoft Graph API or Google Workspace APIs are used to monitor and intervene in outbound emails. Protection level: Despite no MX changes, it can offer inline-like protection, meaning it can block, quarantine, or encrypt emails before they are delivered externally. SPF/DKIM/DMARC impact: Preserves original headers and signatures since mail is sent directly from Microsoft/Google servers. 2. Inline Integration: Requires changing MX records to route email through Avanan. In this mode, Avanan can intercept and inspect outbound emails before delivery. Depending on the configuration, this may affect SPF or DKIM if not properly handled. How it works: Requires adding Avanan’s Protection level: Traditional inline security with full visibility and control, including encryption, DLP, policy enforcement, and advanced threat protection. SPF/DKIM/DMARC impact: SPF configuration is needed by adding Avanan’s include mechanism to the sending domain’s SPF record. The DKIM record of the original sending source is preserved. For configurations, you can refer to the steps in this blog. Proofpoint – Outbound Handling and Integration Methods Outbound Logic Proofpoint analyzes outbound emails to detect and prevent data loss (DLP), to identify advanced threats (malware, phishing, BEC) originating from compromised internal accounts, and to ensure compliance. Their API integration provides crucial visibility and powerful remediation capabilities, while their traditional gateway (MX record) deployment delivers true inline, pre-delivery blocking for outbound traffic. Integration methods 1. API Integration: No MX record changes are required for this deployment method. Integration is done with Microsoft 365 or Google Workspace. How it works: Through its API integration, Proofpoint gains deep visibility into outbound emails and provides layered security and response features, including: Detect and alert: Identifies sensitive content (Data Loss Prevention violations), malicious attachments, or suspicious links in outbound emails. Post-delivery remediation (TRAP): A key capability of the API model is Threat Response Auto-Pull (TRAP), which enables Proofpoint to automatically recall, quarantine, or delete emails after delivery. This is particularly useful for internally sent messages or those forwarded to other users. Enhanced visibility: Aggregates message metadata and logs into Proofpoint’s threat intelligence platform, giving security teams a centralized view of outbound risks and user behavior. Protection level: API-based integration provides strong post-delivery detection and response, as well as visibility into DLP incidents and suspicious behavior.  SPF/DKIM/DMARC impact: Proofpoint does not alter SPF, DKIM, or DMARC because emails are sent directly through Microsoft or Google servers. Since Proofpoint’s servers are not involved in the actual sending process, the original authentication headers remain intact. 2. Gateway Integration (MX Record/Smart Host): This method requires updating MX records or routing outbound mail through Proofpoint via a smart host. How it works: Proofpoint acts as an inline gateway, inspecting emails before delivery. Inbound mail is filtered via MX changes; outbound mail is relayed through Proofpoint’s servers. Threat and DLP filtering: Scans outbound messages for sensitive content, malware, and policy violations. Real-time enforcement: Blocks, encrypts, or quarantines emails before they’re delivered. Policy controls: Applies rules based on content, recipient, or behavior. Protection level: Provides strong, real-time protection for outbound traffic with pre-delivery enforcement, DLP, and encryption. SPF/DKIM/DMARC impact: Proofpoint becomes the sending server: SPF: You need to configure ProofPoint’s SPF. DKIM: Can sign messages; requires DKIM setup. DMARC: DMARC passes if SPF and DKIM are set up properly. Please refer to this article to configure SPF and DKIM for ProofPoint. Mimecast – Outbound Handling and Integration Methods Outbound Logic Mimecast inspects outbound emails to prevent data loss (DLP), detect internal threats such as malware and impersonation, and ensure regulatory compliance. It primarily functions as a Secure Email Gateway (SEG), meaning it sits directly in the outbound email flow. While Mimecast offers APIs, its core outbound protection is built around this inline gateway model. Integration Methods 1. Gateway Integration (MX Record change required) This is Mimecast’s primary method for outbound email protection. Organizations route their outbound traffic through Mimecast by configuring their email server (e.g., Microsoft 365, Google Workspace, etc.) to use Mimecast as a smart host. This enables Mimecast to inspect and enforce policies on all outgoing emails in real time. How it works: Updating outbound routing in your email system (smart host settings), or Using Mimecast SMTP relay to direct messages through their infrastructure. Mimecast then scans, filters, and applies policies before the email reaches the final recipient. Protection level: Advanced DLP: Identifies and prevents sensitive data leaks. Impersonation and Threat Protection: Blocks malware, phishing, and abuse from compromised internal accounts. Email Encryption and Secure Messaging: Applies encryption policies or routes messages via secure portals. Regulatory Compliance: Enforces outbound compliance rules based on content, recipient, or metadata. SPF/DKIM/DMARC impact: SPF: Your SPF record must include Mimecast’s SPF mechanism based on your region to avoid SPF failures. DKIM: A new DKIM record should be configured to make sure your emails are DKIM signed when routing through Mimecast. DMARC: With correct SPF and DKIM setup, Mimecast ensures DMARC alignment, maintaining your domain’s sending reputation. Please refer to the steps in this detailed article to set up SPF and DKIM for Mimecast. 2. API Integration (Complementary to Gateway) Mimecast’s APIs complement the main gateway by providing automation, reporting, and management tools rather than handling live outbound mail flow. They allow you to manage policies, export logs, search archived emails, and sync users. APIs enhance visibility and operational tasks but do not provide real-time filtering or blocking of outbound messages. Since APIs don’t process live mail, they have no direct effect on SPF, DKIM, or DMARC; those depend on your gateway (smart host) setup. Barracuda – Outbound Handling and Integration Methods Outbound Logic Barracuda analyzes outbound emails to prevent data loss (DLP), block malware, stop phishing/impersonation attempts from compromised internal accounts, and ensure compliance. Barracuda offers flexible deployment options, including both traditional gateway (MX record) and API-based integrations. While both contribute to outbound security, their roles are distinct. Integration Methods 1. Gateway Integration (MX Record / Smart Host) — Primary Inline Security How it works: All outbound emails pass through Barracuda’s security stack for real-time inspection, threat blocking, and policy enforcement before delivery. Protection level: Comprehensive DLP (blocking, encrypting, or quarantining sensitive content)  Outbound spam and virus filtering  Enforcement of compliance and content policies This approach offers a high level of control and immediate threat mitigation on outbound mail flow. SPF/DKIM/DMARC impact: SPF: Update SPF records to include Barracuda’s sending IPs or SPF include mechanism. DKIM: Currently, no explicit setup is needed; DKIM of the main sending source is preserved. Refer to this article for more comprehensive guidance on Barracuda SEG configuration. 2. API Integration (Complementary & Advanced Threat Focus) How it works: The API accesses cloud email environments to analyze historical and real-time data, learning normal communication patterns to detect anomalies in outbound emails. It also supports post-delivery remediation, enabling the removal of malicious emails from internal mailboxes after sending. Protection level: Advanced AI-driven detection and near real-time blocking of outbound threats, plus strong post-delivery cleanup capabilities. SPF/DKIM/DMARC impact: Since mail is sent directly by the original mail server (e.g., Microsoft 365), SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. Cisco Secure Email (formerly IronPort) – Outbound Handling and Integration Methods Outbound Logic Cisco Secure Email protects outbound email by preventing data loss (DLP), blocking spam and malware from internal accounts, stopping business email compromise (BEC) and impersonation attacks, and ensuring compliance. Cisco provides both traditional gateway appliances/cloud gateways and modern API-based solutions for layered outbound security. Integration Methods 1. Gateway Integration (MX Record / Smart Host) – Cisco Secure Email Gateway (ESA) How it works: Organizations update MX records to route mail through the Cisco Secure Email Gateway or configure their mail server (e.g., Microsoft 365, Exchange) to smart host outbound email via the gateway. All outbound mail is inspected and policies enforced before delivery. Protection level: Granular DLP (blocking, encrypting, quarantining sensitive content) Outbound spam and malware filtering to protect IP reputation Email encryption for sensitive outbound messages Comprehensive content and attachment policy enforcement SPF: Check this article for comprehensive guidance on Cisco SPF settings. DKIM: Refer to this article for detailed guidance on Cisco DKIM settings. 2. API Integration – Cisco Secure Email Threat Defense How it works: Integrates directly via API with Microsoft 365 (and potentially Google Workspace), continuously monitoring email metadata, content, and user behavior across inbound, outbound, and internal messages. Leverages Cisco’s threat intelligence and AI to detect anomalous outbound activity linked to BEC, account takeover, and phishing. Post-Delivery Remediation: Automates the removal or quarantine of malicious or policy-violating emails from mailboxes even after sending. Protection level: Advanced, AI-driven detection of sophisticated outbound threats with real-time monitoring and automated remediation. Complements gateway filtering by adding cloud-native visibility and swift post-send action. SPF/DKIM/DMARC impact: Since emails are sent directly by the original mail server, SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. If you have any questions or need assistance, feel free to reach out to EasyDMARC technical support.

“Is that concrete all around, or is it in my head?” asked Ian Hunter in “All the Young Dudes,” the song David Bowie wrote for Mott the Hoople in 1972. Concrete is all around us, and we haven’t quite wrapped our heads around it. It’s one of the indispensable materials of modernity; as we try to decarbonize the built environment, it’s part of the problem, and innovations in its composition may become part of the solution. Understanding its history more clearly, the Skyscraper Museum’s new exhibition in Manhattan implies, just might help us employ it better. Concrete is “the second most used substance in the world, after water,” the museum’s founder/director/curator Carol Willis told AN during a recent visit. For plasticity, versatility, and compressive strength, reinforced concrete is hard to beat, though its performance is more problematic when assessed by the metric of embodied and operational carbon, a consideration the exhibition acknowledges up front. In tall construction, concrete has become nearly hegemonic, yet its central role, contend Willis and co-curator Thomas Leslie, formerly of Foster + Partners and now a professor at the University of Illinois, Urbana-Champaign, is underrecognized by the public and by mainstream architectural history. The current exhibition aims to change that perception. The Skyscraper Museum in Lower Manhattan features an exhibition, The Modern Concrete Skyscraper, which examines the history of material choices in building tall towers. (Courtesy the Skyscraper Museum) The Modern Concrete Skyscraper examines the history of tall towers’ structural material choices, describing a transition from the early dominance of steel frames to the contemporary condition, in which most large buildings rely on concrete. This change did not happen instantly or for any single reason but through a combination of technical and economic factors, including innovations by various specialists, well-recognized and otherwise; the availability of high-quality limestone deposits near Chicago; and the differential development of materials industries in nations whose architecture grew prominent in recent decades. As supertalls reach ever higher—in the global race for official height rankings by the Council on Tall Buildings and Urban Habitat (CTBUH) and national, corporate, or professional bragging rights—concrete’s dominance may not be permanent in that sector, given the challenge of pumping the material beyond a certain height. (The 2,717-foot Burj Khalifa, formerly Burj Dubai, uses concrete up to 1,987 and steel above that point; Willis quotes SOM’s William Baker describing it as “the tallest steel building with a concrete foundation of 156 stories.”) For the moment, however, concrete is ahead of its chief competitors, steel and (on a smaller scale) timber. Regardless of possible promotional inferences, Willis said, “we did not work with the industry in any way for this exhibition.” “The invention of steel and the grid of steel and the skeleton frame is only the first chapter of the history of the skyscraper,” Willis explained. “The second chapter, and the one that we’re in now, is concrete. Surprisingly, no one had ever told that story of the skyscraper today with a continuous narrative.” The exhibition traces the use of concrete back to the ancient Roman combination of aggregate and pozzolana—the chemical formula for which was “largely lost with the fall of the Roman Empire,” though some Byzantine and medieval structures approximated it. From there, the show explores comparable materials’ revival in 18th-century England, the patenting of Portland cement by Leeds builder Joseph Aspdin in 1824, the proof-of-concept concrete house by François Coignet in 1856, and the pivotal development of rebar in the mid-19th century, with overdue attention to Ernest Ransome’s 1903 Ingalls Building in Cincinnati, then the world’s tallest concrete building at 15 stories and arguably the first concrete skyscraper. The exhibition includes a timeline that depicts concrete’s origins in Rome to its contemporary use in skyscraper construction. (Courtesy the Skyscraper Museum) Baker’s lectures, Willis reported, sometimes pose a deceptively simple question: “‘What is a skyscraper?’ In 1974, when the World Trade Center and Sears Tower are just finished, you would say it’s a very tall building that is built of steel, an office building in North America. But if you ask that same question today, the answer is: It’s a building that is mixed-use, constructed of concrete, and [located] in Asia or the Middle East.” The exhibition organizes the history of concrete towers by eras of engineering innovation, devoting special attention to the 19th- and early-20th-century “patent era” of Claude Allen Porter Turner (pioneer in flat-slab flooring and mushroom columns) and Henry Chandlee Turner (founder of Turner Construction), Ransome (who patented twisted-iron rebar), and François Hennebique (known for the re-inforced concrete system exemplified by Liverpool’s Royal Liver Building, the world’s tallest concrete office building when completed in 1911). In the postwar era, “concrete comes out onto the surface [as] both a structural material and aesthetic.” Brutalism, perhaps to some observers’ surprise, “does not figure very large in high-rise design,” Willis said, except for Paul Rudolph’s Tracey Towers in the Bronx. The exhibition, however, devotes considerable attention to the work of Pier Luigi Nervi, Bertrand Goldberg (particularly Marina City), and SOM’s Fazlur Khan, pioneer of the structural tube system in the 1960s and 1970s—followed by the postmodernist 1980s, when concrete could express either engineering values or ornamentation. The exhibition highlights a number of concrete towers, including Paul Rudolph’s Tracey Towers in the Bronx. (Courtesy the Skyscraper Museum) “In the ’90s, there were material advances in engineering analysis and computerization that helped to predict performance, and so buildings can get taller and taller,” Willis said. The current era, if one looks to CTBUH rankings, is dominated by the supertalls seen in Dubai, Shanghai, and Kuala Lumpur, after the Petronas Towers (1998) “took the title of world’s tallest building from North America for the first time and traumatized everybody about that.” The previous record holder, Chicago’s Sears (now Willis) Tower, comprised steel structural tubes on concrete caissons; with Petronas, headquarters of Malaysia’s national petroleum company of that name, a strong concrete industry was represented but a strong national steel industry was lacking, and as Willis frequently says, form follows finances. In any event, by the ’90s concrete was already becoming the standard material for supertalls, particularly on soft-soiled sites like Shanghai, where its water resistance and compressive strength are well suited to foundation construction. Its plasticity is also well suited to complex forms like the triangular Burj, Kuala Lumpur’s Merdeka 118, and (if eventually completed) the even taller Jeddah Tower, designed to “confuse the wind,” shed vortices, and manage wind forces. Posing the same question Louis Kahn asked about the intentions of a brick, Willis said, with concrete “the answer is: anything you want.” The exhibition is front-loaded with scholarly material, presenting eight succinct yet informative wall texts on the timeline of concrete construction. The explanatory material is accompanied by ample photographs as well as structural models on loan from SOM, Pelli Clarke & Partners, and other firms. Some materials are repurposed from the museum’s previous shows, particularly Supertall! (2011–12) and Sky High and the Logic of Luxury (2013–14). The models allow close examination of the Burj Khalifa, Petronas Towers, Jin Mao Tower, Merdeka 118, and others, including two unbuilt Chicago projects that would have exceeded 2,000 feet: the Miglin-Beitler Skyneedle (Cesar Pelli/Thornton Tomasetti) and 7 South Dearborn (SOM). The Burj, Willis noted, was all structure and no facade for a time: When its curtain-wall manufacturer, Schmidlin, went bankrupt in 2006, it “ended up going to 100 stories without having a stitch of glass on it,” temporarily becoming a “1:1 scale model of the structural system up to 100 stories.” Its prominence justifies its appearance here in two models, including one from RWDI’s wind-tunnel studies. Eero Saarinen’s only skyscraper, built for CBS in 1965 and also known as “Black Rock,” under construction in New York City. (Courtesy Eero Saarinen Collection, Manuscripts, and Archives, Yale University Library) The exhibition opened in March, with plans to stay up at least through October (Willis prefers to keep the date flexible), with accompanying lectures and panels to be announced on the museum’s website (skyscraper.org). Though the exhibition’s full textual and graphic content is available online, the physical models alone are worth a trip to the Battery Park City headquarters. Intriguing questions arise from the exhibition without easy answers, setting the table for lively discussion and debate. One is whether the patenting of innovations like Ransome bar and the Système Hennebique incentivized technological progress or hindered useful technology transfer. Willis speculated, “Did the fact that there were inventions and patents mean that competition was discouraged, that the competition was only in the realm of business, rather than advancing the material?” A critical question is whether research into the chemistry of concrete, including MIT’s 2023 report on the self-healing properties of Roman pozzolana and proliferating claims about “green concrete” using alternatives to Portland cement, can lead to new types of the material with improved durability and lower emissions footprints. This exhibition provides a firm foundation in concrete’s fascinating history, opening space for informed speculation about its future. Bill Millard is a regular contributor to AN.

Insights 4 Keys to AI-First Leadership: The New Imperative for Digital Transformation AI has become a defining force in reshaping industries and determining competitive advantage. To support AI-first strategies, leaders must progress through a deliberate journey: building foundational AI knowledge, cultivating an AI-first mindset, and honing AI-related skills, before confidently leading with AI. View the infographic Digital IntelligenceFuture of WorkTransformation Share this resource Share on LinkedIn Share on Facebook Share on X Share on WhatsApp Email this Page Connect with us Change isn’t easy, but we can help. Together we’ll create informed and inspired leaders ready to shape the future of your business. Contact us Latest Insights Strategic Alignment Harvard Business Publishing Unveils Harvard Business Impact as New Brand for Corporate Learning and Education Units Harvard Business Publishing announced the launch of Harvard Business Impact, a new brand identity for… Read more: Harvard Business Publishing Unveils Harvard Business Impact as New Brand for Corporate Learning and Education Units News Digital Intelligence Succeeding in the Digital Age: Why AI-First Leadership Is Essential While AI makes powerful operational efficiencies possible, it cannot yet replace the creativity, adaptability, and… Read more: Succeeding in the Digital Age: Why AI-First Leadership Is Essential Perspectives Digital Intelligence 4 Keys to AI-First Leadership: The New Imperative for Digital Transformation AI has become a defining force in reshaping industries and determining competitive advantage. To support… Read more: 4 Keys to AI-First Leadership: The New Imperative for Digital Transformation Infographic Talent Management Leadership Fitness Behavioral Assessment In our study, “Leadership Fitness: Developing the Capacity to See and Lead Differently Amid Complexity,”… Read more: Leadership Fitness Behavioral Assessment Job Aid The post 4 Keys to AI-First Leadership: The New Imperative for Digital Transformation appeared first on Harvard Business Impact.

Anthropic says that it has released a new set of AI models tailored for U.S. national security customers. The new models, a custom set of “Claude Gov” models, were “built based on direct feedback from our government customers to add

The enterprise cloud narrative is undergoing a fundamental shift. After years of public cloud evangelism, IT leaders are orchestrating what Broadcom’s latest research aptly terms a “cloud reset”—a strategic recalibration that p

Army Boosts Lethality, Navy Innovates in NATO Push  Mirage News

Outsourcing definition Outsourcing is defined as a business practice in which services or job functions are hired out to a third-party on a contract or ongoing basis. In IT, an outsourcing initiative with a technology provid

CIOs and business leaders know they’re sitting on a goldmine of business data. And while traditional tools such as business intelligence platforms and statistical analysis software can effectively surface insights from the collated data resources, doing so quickly, in real-time and at scale remains an unsolved challenge.Enterprise AI, when deployed responsibly and at scale, can turn these bottlenecks into opportunities. Acting quickly on data, even ‘live’ (during a customer interaction, for example), is one of the technology’s abilities, as is scalability: AI can process large amounts of information from disparate sources almost as easily as it can summarize a one-page spreadsheet.But deploying an AI solution in the modern enterprise isn’t simple. It takes structure, trust and the right talent. Along with the practical implementation challenges, using AI brings its own challenges, such as data governance, the need to impose guardrails on AI responses and training data, and persistent staffing issues.We met with Rani Radhakrishnan, PwC Principal, Technology Managed Services – AI, Data Analytics and Insights, to talk candidly about what’s working — and what’s holding back CIOs in their AI journey. We spoke ahead of her speaking engagement at TechEx AI & Big Data Expo North America, June 4 and 5, at the Santa Clara Convention Center.Rani is especially attuned to some of the governance, data privacy and sovereignty issues that face enterprises, having spent many years in her career working with numerous clients in the health sector — an area where issues like privacy, data oversight and above all data accuracy are make-or-break aspects of technology deployments.“It’s not enough to just have a prompt engineer or a Python developer. … You still need the human in the loop to curate the right training data sets, review and address any bias in the outputs.” —Rani Radhakrishnan, PwCFrom support to strategy: shifting expectations for AIRani said that there’s a growing enthusiasm from PwC’s clients for AI-powered managed services that can provide both business insights in every sector, and for the technology to be used more proactively, in so-called agentic roles where agents can independently act on data and user input; where autonomous AI agents can take action based on interactions with humans, access to data resources and automation.For example, PwC’s agent OS is a modular AI platform that connects systems and scales intelligent agents into workflows, many times faster than traditional computing methods. It’s an example of how PwC responds to the demand for AI from its clients, many of whom see the potential of this new technology, but lack the in-house expertise and staff to act on their needs.Depending on the sector of the organization, the interest in AI can come from many different places in the business. Proactive monitoring of physical or digital systems; predictive maintenance in manufacturing or engineering; or cost efficiencies won by automation in complex, customer-facing environments, are just a few examples.But regardless of where AI can bring value, most companies don’t yet have in-house the range of skills and people necessary for effective AI deployment — or at least, deployments that achieve ROI and don’t come with significant risk.“It’s not enough to just have a prompt engineer or a Python developer,” Rani said. “You’ve got to put all of these together in a very structured manner, and you still need the human in the loop to curate the right training data sets, review and address any bias in the outputs.”Cleaning house: the data challenge behind AIRani says that effective AI implementations need a mix of technical skills — data engineering, data science, prompt engineering — in combination with an organization’s domain expertise. Internal domain expertise can define the right outcomes, and technical staff can cover the responsible AI practices, like data collation and governance, and confirm that AI systems work responsibly and within company guidelines.“In order to get the most value out of AI, an organization has to get the underlying data right,” she said. “I don’t know of a single company that says its data is in great shape … you’ve got to get it into the right structure and normalize it properly so you can query, analyze, and annotate it and identify emerging trends.”Part of the work enterprises have to put in for effective AI use is the observation for and correction of bias — in both output of AI systems and in the analysis of potential bias inherent in training and operational data.It’s important that as part of the underlying architecture of AI systems, teams apply stringent data sanitization, normalization, and data annotation processes. The latter requires “a lot of human effort,” Rani said, and the skilled personnel required are among the new breed of data professionals that are beginning to emerge.If data and personnel challenges can be overcome, then the feedback loop makes the possible outcomes from generative AI really valuable, Rani said. “Now you have an opportunity with AI prompts to go back and refine the answer that you get. And that’s what makes it so unique and so valuable because now you’re training the model to answer the questions the way you want them answered.”For CIOs, the shift isn’t just about tech enablement. It’s about integrating AI into enterprise architecture, aligning with business strategy, and managing the governance risks that come with scale. CIOs are becoming AI stewards — architecting not just systems, but trust and transformation.ConclusionIt’s only been a few years since AI emerged from its roots in academic computer science research, so it’s understandable that today’s enterprise organizations are, to a certain extent, feeling their way towards realizing AI’s potential.But a new playbook is emerging — one that helps CIOs access the value held in their data reserves, in business strategy, operational improvement, customer-facing experiences and a dozen more areas of the business.As a company that’s steeped in experience with clients large and small from all over the world, PwC is one of the leading choices that decision-makers turn to, to begin or rationalize and direct their existing AI journeys.Explore how PwC is helping CIOs embed AI into core operations, and see Rani’s latest insights at the June TechEx AI & Big Data Expo North America.(Image source: “Network Rack” by one individual is licensed under CC BY-SA 2.0.)