Phil Stevens

This is especially true of mid-size and smaller discrete manufacturers outside the technology sector.

• The barriers are not model quality: data sits in silos across aging operational technology (SCADA, PLC) and IT systems (MES, ERP, PLM); AI governance remains underdeveloped in areas including intellectual property ownership, bias, accountability and cybersecurity; and a talent gap demands reskilling and change management.
• The proposed path is holistic: modernize data infrastructure alongside AI projects, invest in workforce training, and establish governance and security frameworks early to avoid risks the organization does not fully understand.

Aerospace firms use generative design to produce lighter parts, while electronics manufacturers use synthetic data to improve automated optical inspection accuracy. Phil Stevens contrasts these concrete successes with a wider market that has yet to turn the same techniques into strategic transformation.

Read original

AMRs continuously produce material flow patterns, transport times, location histories, task completion rates, battery status and environmental conditions.

• Joined to MES, WMS and ERP, that data enables real-time visibility into material handling, rerouting around congestion, predictive maintenance, and evidence-based decisions on layout or inventory placement.
• They frame this as optimizing the whole internal logistics ecosystem, not just moving boxes, and note the practical requirements: legacy systems without modern APIs, proprietary data formats, middleware or custom development, and industrial-grade network coverage.

During the pandemic at Sportsman's Warehouse, access to up-to-the-minute supply chain data let the business make realistic delivery commitments to customers. Phil Stevens uses that episode to show what integrated operational data makes possible.

The two long-form posts place different bets. One treats generative AI as the headline technology that mostly has not scaled; the other argues that AMRs, though less discussed, are already changing factory floors—and that this is where the data groundwork pays off.

Read original

Both posts return to aging, fragmented systems—OT and IT silos on one side, legacy APIs and proprietary formats on the other—and the cost and complexity of bridging them. Without a solid data foundation and connectivity, AI starves; integration work must happen alongside the AI or robotics project, not after it.

Phil Stevens compares manufacturing integration with earlier work joining disparate systems across multiple business units, diverse functional areas and hundreds of Macy's locations, as well as the cross-business-unit integration needed for supply chain visibility.

Read original · Original 2

The responsibilities include a technology strategy aligned with business goals, IT and network readiness, cybersecurity for connected systems, vendor evaluation, change management and data governance.

• They favor a "start small, learn fast, scale smart" approach through pilots to de-risk later phases, particularly for mid-sized manufacturers.
• They also emphasize continuous learning, because AI raises the reskilling burden on existing engineers and operators.

In the AMR post, the CIO agenda includes developing a clear AMR strategy, preparing infrastructure, championing security, guiding vendor evaluation and establishing governance before scaling beyond pilot projects.

The recommendations stay consistent between the two essays, but the emphasis shifts: the GenAI piece stresses governance and workforce change, while the AMR piece stresses infrastructure and pilot sequencing.

Read original · Original 2

Event posts show the same interest in learning from peers and governance-level voices, combining conference attendance with leadership takeaways.

• At an NACD Atlanta Tech Officer Cohort breakfast, board members H.
• James Dallas, Kelly Barrett and Monique Picou offered advice on how a CIO can work effectively with a board; Phil Stevens described it as helpful.

Phil Stevens describes the Evanta 2024 Atlanta CIO Executive Summit as covering topics from stakeholder value to change management and AI. They also recount a two-day visit with Microsoft and CDW at the Microsoft EBC and Innovation Hub to see their vision of the future of work, including AI, cybersecurity and data.

Read original · Original 2 · Original 3

Start here to see how Phil Stevens connects technical challenges to business strategy and uses career examples to explain systemic issues.

Phil Stevens argues that many manufacturers, especially mid-size and smaller discrete manufacturers, use generative AI for isolated gains but lack a strategy for long-term competitiveness.

• They identify three systemic barriers: data silos and legacy systems (SCADA, PLC, MES, ERP); underdeveloped AI governance around intellectual property, bias, and cybersecurity; and a talent gap requiring reskilling and change management.
• They draw on their experience integrating disparate systems at Macy's and improving supply chain visibility at Sportsman's Warehouse and The Exchange.
• The post ends by asking readers about the biggest barrier and their past leadership experience.

For brands planning a campaign

For a manufacturing technology vendor targeting CIOs, this post offers a ready-made agenda for a thought-leadership webinar or outreach: bring data modernization, governance, and workforce readiness together. It also shows Phil Stevens can frame a problem and invite discussion, making them a credible host or panelist.

Start here for Phil Stevens's practical approach to deriving value from robotics beyond automation and their focus on integrating with enterprise systems.

Phil Stevens explains that autonomous mobile robots (AMRs) are more than task automation: they’re also rich data sources, providing information on material flow, transport times, task completion, and battery status.

• They argue that integrating this data with existing systems like MES, WMS, and ERP can unlock real-time visibility and optimize logistics, though legacy systems and network infrastructure pose challenges.
• They cite their experience at Sportsman's Warehouse during the pandemic, where up-to-date supply chain data enabled realistic delivery commitments.
• They suggest CIOs champion a holistic AMR strategy with pilot projects.

For brands planning a campaign

This piece is directly relevant to a smart factory data integration vendor.

• It outlines the value of connecting AMR data to MES, WMS, and ERP, along with the challenges to address.
• It could support a webinar or whitepaper on data-driven manufacturing, with Phil Stevens as a speaker on both the promise and practical hurdles.

Start here to see the peer networks and learning forums they value, which can inform outreach timing and context.

Phil Stevens reflects on attending the Evanta 2024 Atlanta CIO Executive Summit, where topics ranged from stakeholder value to change management and AI.

• They note reconnecting with former colleagues and making new ones.
• The post shows engagement with the CIO community and a broad interest in leadership topics.

For brands planning a campaign

This post shows which topics Phil Stevens follows and could inform outreach. A vendor might propose a follow-up conversation or invite them to a similar event, referencing shared interests in change management and AI.

Start here to understand their emphasis on governance and strategic alignment, relevant to vendors selling to the executive level.

Phil Stevens thanks board members H.

• James Dallas, Kelly Barrett, and Monique Picou for sharing insights at an NACD Atlanta Tech Officer Cohort Breakfast.
• They say that, as a CIO, they find board members’ advice on how to work with them helpful.
• The post highlights their focus on governance and executive-level communication.

For brands planning a campaign

This post signals interest in board-level perspectives and governance. A campaign targeting CIOs could use it to position a solution around board reporting and risk management, or invite Phil Stevens to discuss CIO-board collaboration.

Start here to see their openness to vendor briefings and focus on AI, cybersecurity, and data.

Phil Stevens describes spending a couple of days with Microsoft and CDW at the Microsoft EBC and Innovation Hub, where they saw the companies’ vision of the future of work, including AI, cybersecurity, and data. The post shows they engage directly with major technology vendors and keep up with emerging trends.

For brands planning a campaign

This post shows Phil Stevens is receptive to vendor-led innovation briefings. A manufacturing technology vendor could propose a similar deep-dive session aligned with their interests in AI, cybersecurity, and data.

They identify systemic barriers: data silos across aging OT systems like SCADA and PLC and IT systems like MES, ERP and PLM; underdeveloped AI governance covering intellectual property, bias, accountability and cybersecurity; and a talent gap that requires reskilling and change management.

• They cite aerospace generative design for lighter parts and electronics manufacturers using synthetic data to improve automated optical inspection as examples that work.
• The recommended path is holistic: modernize data infrastructure alongside AI projects, invest in workforce training and establish governance early.

Uses concrete industry examples and prior retail supply-chain experience to explain systemic IT/OT barriers.

The focus is on mid-size and smaller discrete manufacturers outside the technology space, not only large enterprises.

For brands planning a campaign

A manufacturing technology vendor targeting CIOs can use Stevens' framing to open a conversation about adoption barriers rather than product features. A thought-leadership webinar or article on escaping pilot purgatory through data readiness, governance and workforce planning fits the priorities they state.

Examples: Source 1

They generate data on material flow, transport times, location histories, task completion, battery status and environmental conditions.

• When that data is integrated with MES, WMS and ERP, they say it can support real-time visibility, dynamic route adjustments, predictive maintenance and better facility layout decisions.
• They also note integration complexity with legacy systems that lack modern APIs or use proprietary formats, plus the need for middleware and industrial-grade network coverage.
• They recommend a CIO-led AMR strategy aligned with business goals and a "start small, learn fast, scale smart" pilot approach.

Links AMR telemetry to MES/WMS/ERP integration and CIO-level strategy.

The post is written for CIOs and manufacturing leaders, with less detail on operator-level workflows.

For brands planning a campaign

A vendor selling AMRs, industrial data platforms or system integration can evaluate Stevens for content that connects robotics to enterprise data outcomes rather than hardware alone. Their CIO framing suits a webinar on integrating AMR data with existing manufacturing systems.

Examples: Source 1

In the GenAI post, siloed data is a core reason manufacturers stall.

• In the AMR post, it appears as legacy APIs, proprietary formats, middleware requirements and network infrastructure.
• They connect this to earlier retail supply-chain work at Sportsman's Warehouse and The Exchange, and mention integrating disparate systems across business units and hundreds of Macy's locations as a comparable challenge.

Uses prior retail supply-chain integration experience as an analogy for manufacturing IT/OT challenges.

For brands planning a campaign

Vendors with data integration, middleware, industrial networking or MES/ERP connectors can assess Stevens as a CIO voice who speaks about the unglamorous prerequisites of AI and robotics. Outreach can invite them to discuss a specific integration pattern or reference architecture.

Examples: Source 1 · Source 2

In the GenAI post, they emphasize change management, reskilling and continuous learning. These items show an interest in the leadership and governance side of technology adoption, not only tools.

Mixes event observations with leadership lessons from technology adoption.

The event recap posts are brief and do not detail the sessions beyond broad themes.

For brands planning a campaign

For brands that sell to CIOs or run executive programs, Stevens can be evaluated for content on the CIO-board relationship and organizational change. A roundtable, executive dinner or co-authored piece on change management for AI adoption may fit better than a product demo.

Examples: Source 1 · Source 2 · Source 3

This shows a pattern of engaging with major technology vendors and channel partners on enterprise priorities.

Brief event recap. Ask for a product evaluation if that is central to the campaign.

For brands planning a campaign

A manufacturing technology vendor could assess Stevens for event-based or partner-led content. Because the posts are a brief event recap, ask them for a specific angle before assuming depth on Microsoft or CDW offerings.

Examples: Source 1

The longer posts pose a question, explain barriers, draw examples from aerospace, electronics or retail, recommend a holistic path and invite readers to respond.

• They use hashtags around GenAI, manufacturing, AI, robotics, data analytics and Industry 4.0.
• The recaps focus on relationships and takeaways from industry gatherings.

Pairs analytical explainers with event recaps and questions for readers.

The available material is short-form LinkedIn posts; no articles or videos are present.

For brands planning a campaign

A brand can evaluate format fit: Stevens can carry a nuanced argument in a LinkedIn post or discussion prompt. Propose a format they have demonstrated, and ask for samples before extending the campaign to a new format.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

The posts present it as a former employer.

View example

View example

View example

The post describes a briefing visit, not a sponsorship, client, or reseller relationship.

View example

The post describes no commercial arrangement.

View example

View example

View example

Anthony Cacciatore's posts focus on Canadian manufacturing and defence investment, robotics, and device-level cybersecurity, overlapping with Phil Stevens's interest in secure, integrated factory systems.

Anthony Cacciatore focuses on Canadian industrial policy, defence manufacturing capability, and robot cybersecurity standards such as IEC 62443-4-2. Phil Stevens takes a CIO strategy view, concentrating on data integration, enterprise systems, and adoption barriers such as governance and workforce readiness.

Read original · Original 2

David Katzman's posts cover cloud-native CAD, PLM, AI in design workflows, and manufacturer connectivity, themes adjacent to Phil Stevens's focus on integrated manufacturing data.

David Katzman writes from a product and platform leadership position in CAD/PLM software, highlighting releases such as Onshape and Arena capabilities, AI Advisor, and cloud-native product development workflows. Phil Stevens writes from the CIO adoption side, focusing on factory-floor data integration, AMR telemetry, generative AI barriers, and governance.

Read original · Original 2

Joshua Joseph's posts on autonomous systems, fleet scale, industrial engineering, and Toyota Production System lessons connect with Phil Stevens's AMR and manufacturing modernization themes.

Joshua Joseph frames the topic through industrial engineering education, autonomous fleet design, and human decision-making, drawing on historical production examples and conference observations. Phil Stevens takes a CIO perspective, focusing on enterprise integration, legacy system modernization, and governance in manufacturing technology.

Read original · Original 2

The two posts reviewed argue that cybersecurity now belongs on the robot-selection list next to payload, reach, accuracy and cycle time; they name IEC 62443-4-2 and Security Level 2 as purchasing criteria and tell buyers to ask the manufacturer, the integrator and to ask for the certificate.

• That is the right voice for a vendor selling automation hardware, robot controllers or device-level OT security, and for buyers who need cybersecurity certification in the procurement conversation.
• The second post speaks to a national-industrial audience, framing increased Canadian defence spending as a manufacturing modernization opportunity and arguing that the measure of the investment is what Canada builds, not only what it purchases.
• A campaign aimed at Canadian plants can use that framing, which Phil Stevens' posts do not supply.

The tradeoff is altitude.

• Cacciatore's posts focus on equipment and component-level security, with automation engineers and procurement decision-makers in view.
• They do not address CIO-level data architecture, MES, WMS or ERP integration, or the governance, talent and change-management problems Phil Stevens writes about.
• A webinar on making factory data usable across enterprise systems would require the host to move from component certification to an integration story they have not published.
• Cacciatore is the narrower, more technical alternative to a CIO-facing host; ask for audience data before assuming they have standing with CIOs.

Examples: Source 1 · Source 2

The posts cover cloud-native CAD and PLM: Onshape and Arena releases, a feature-script tool that turns natural language into custom CAD functionality, a Gartner Magic Quadrant placement for PLM in discrete manufacturing, Arena GovCloud for regulated industries, integrations that bring PCB designs and Windchill data into cloud workflows, and an annual review naming an NVIDIA robotics design-to-simulation link.

• A vendor selling engineering data management, design collaboration, simulation or product-data governance would be speaking to a subject Katzman already publishes on, and a connected-product-data webinar fits his posts more closely than a factory integration one.
• His Arena Connect post is the clearest match: it is about connecting the systems manufacturers rely on, automating workflows and keeping information moving across the product lifecycle.

The tradeoff is independence and subject matter.

• Katzman's posts are product and release announcements written from inside a CAD and PLM business, so they carry a vendor's perspective rather than a practitioner's view of buyer problems.
• They do not discuss OT/IT data silos, SCADA or PLC connectivity, robotics, or AMR deployment—the core of a campaign about operational integration.
• For a webinar on that topic, Katzman would bring adjacent expertise in keeping engineering data synchronized across tools, not an operational-integration narrative.
• Ask for audience data before claiming the profile reaches manufacturing IT buyers.

Examples: Source 1 · Source 2

The posts describe a season of speaking at Automate, Robotics Summit & Expo, MODEX and IISE, and report the questions heard there: how to run fleets with different models and failure modes, whether software or hardware owns the factory of the future, and what happens when one node breaks inside a larger autonomous network.

• Joseph states the shift directly, arguing that the autonomous factory is where people stop doing what a machine can do reliably and start doing judgment, adaptation and accountability.
• The second post reaches back to Taiichi Ohno and just-in-time manufacturing to argue that industrial engineering is about finding waste, not buying bigger equipment.
• Both are useful when a campaign wants a keynote or panel voice with demonstrated event presence, or an angle on workforce and human judgment as AMRs, cobots and humanoids arrive together.

The tradeoff is specificity.

• Joseph's posts treat the autonomous factory as a design problem; they do not name the enterprise systems, integration patterns, middleware or governance questions a campaign about enterprise integration raises.
• They offer no MES, WMS or ERP detail, and do not discuss AI governance, IP ownership or accountability structures.
• Where Phil Stevens lists barriers that map directly onto a vendor agenda, Joseph offers framing and open questions.
• Joseph reports speaking engagements, but they are not documented in these posts; confirm the appearances before using them in a pitch.

Examples: Source 1 · Source 2