For many businesses, information technology once meant a relatively predictable collection of systems:<\/p>\n
Computers. Servers. Email. Business applications. Networks. Printers.<\/p>\n
For manufacturers, engineering firms, mobility companies, and other technology-intensive organizations, that definition is becoming increasingly incomplete.<\/p>\n
Today’s environment can include:<\/p>\n
IT + Cloud + Engineering Data + Connected Devices + OT\/Edge Systems + AI + External Partners<\/strong><\/p>\n That convergence is changing both the technology environment and the leadership required to manage it.<\/p>\n Michigan’s continued investment in mobility and advanced technology provides a useful example of where this is heading.<\/p>\n On September 11, 2026, Michigan announced $1.5 million in funding through the Michigan Mobility Funding Platform<\/a> for 10 projects intended to help companies test, validate, and commercialize emerging technologies in real-world environments.<\/p>\n The projects span technologies including autonomous systems, hydrogen production and fueling, electric vehicle charging, infrastructure inspection, traffic optimization, accessible transportation, robotics, and fleet-management technology.<\/p>\n Among the projects are Spot robots conducting mapping and inspection work in Detroit, traffic-signal optimization in Oakland and Macomb counties, underwater robotics inspecting municipal infrastructure, autonomous-vehicle safety monitoring, hydrogen technologies, and EV charging infrastructure.<\/p>\n At first glance, this might appear primarily relevant to automotive, mobility, engineering, or economic-development organizations.<\/p>\n But there is a broader technology story underneath it.<\/p>\n Every time physical products, infrastructure, sensors, equipment, vehicles, robotics, cloud platforms, and data become more connected, the traditional boundary between information technology and operational technology becomes less distinct<\/strong>.<\/p>\n And that creates an important question for Michigan businesses:<\/p>\n Who is responsible for making all of this technology work together securely, reliably, and strategically?<\/strong><\/p>\n Consider a growing manufacturer.<\/p>\n Its business environment might include:<\/p>\n Which of those are IT?<\/p>\n Which are operational technology?<\/p>\n Which belong to engineering?<\/p>\n Which belong to cybersecurity?<\/p>\n Which belong to operations?<\/p>\n The technical answer matters.<\/p>\n But from a business leadership perspective, something else matters even more:<\/p>\n They are increasingly interconnected.<\/strong><\/p>\n A problem in one environment can affect another.<\/p>\n An identity compromise can become an operational problem.<\/p>\n A poorly secured vendor connection can become a cybersecurity problem.<\/p>\n A network outage can become a production problem.<\/p>\n A cloud configuration can become a data-governance problem.<\/p>\n An unmanaged connected device can become an entry point into the broader environment.<\/p>\n And an AI application can create new connections among systems and information that previously operated independently.<\/p>\n This is why technology management increasingly needs to look across the entire business rather than treating each system as an isolated technical asset.<\/p>\n Operational technology, or OT<\/strong>, refers broadly to programmable systems and devices that interact with the physical environment.<\/p>\n The National Institute of Standards and Technology’s Guide to Operational Technology Security<\/a> includes examples such as industrial control systems, building automation, transportation systems, physical-access systems, and environmental monitoring systems.<\/p>\n For decades, many operational environments were relatively isolated from traditional corporate IT.<\/p>\n That separation is changing.<\/p>\n Modern businesses want operational information available for:<\/p>\n Those capabilities require connectivity.<\/p>\n Connectivity creates opportunity.<\/p>\n It also creates dependencies and risk.<\/p>\n NIST has highlighted this changing relationship between IT and OT in manufacturing<\/a><\/strong>, noting that increased connectivity requires manufacturers to think carefully about cybersecurity where these environments meet.<\/p>\n That doesn’t mean every small manufacturer suddenly needs an industrial cybersecurity department.<\/p>\n It means leadership needs a better understanding of what is connected, why it is connected, who manages it, and what happens if it fails.<\/strong><\/p>\n Traditional business cybersecurity often focuses heavily on confidentiality.<\/p>\n Protect customer records.<\/p>\n Protect employee information.<\/p>\n Protect email.<\/p>\n Protect intellectual property.<\/p>\n Those remain important.<\/p>\n But operational environments can change the priority.<\/p>\n For a production system, availability and integrity<\/strong> may be equally or even more consequential.<\/p>\n A ransomware event that encrypts office documents is damaging.<\/p>\n A cybersecurity event that interrupts production can directly affect:<\/p>\n This is why applying traditional office-IT security practices blindly to operational environments can be problematic.<\/p>\n OT systems may have unique uptime, performance, reliability, safety, lifecycle, and vendor-support requirements.<\/p>\n The objective isn’t simply to install more security software.<\/p>\n It is to understand the environment and manage risk appropriately.<\/p>\n This brings us back to a fundamental principle of technology management:<\/p>\n You cannot effectively manage what you don’t understand.<\/strong><\/p>\n For manufacturers and engineering-oriented organizations, a meaningful technology assessment increasingly needs to look beyond laptops and servers.<\/p>\n Leadership should understand:<\/p>\n Endpoints, identity, Microsoft 365 or Google Workspace, email, servers, networks, cloud platforms, business applications, backup, and support.<\/p>\n Engineering workstations, CAD\/CAM applications, intellectual property, product data, simulation environments, source code, and specialized applications.<\/p>\n Production equipment, industrial control systems, sensors, robotics, connected machinery, building systems, and other technologies interacting with physical operations.<\/p>\n How IT, OT, cloud platforms, remote users, vendors, facilities, and external partners communicate.<\/p>\n Where engineering, production, customer, operational, and business information resides and how it moves between systems.<\/p>\n Identity, permissions, segmentation, endpoint protection, monitoring, remote access, vulnerability management, incident response, and recovery.<\/p>\n Which systems are critical, how long the business can operate without them, and what happens when technology becomes unavailable.<\/p>\n Only after understanding those layers can leadership make informed decisions about architecture, cybersecurity, modernization, and automation.<\/p>\n One important concept in converged environments is segmentation<\/strong>.<\/p>\n Not every device or system should communicate freely with every other system.<\/p>\n NIST has specifically examined security segmentation for smaller manufacturers<\/a><\/strong>.<\/p>\n The principle is straightforward:<\/p>\n Group assets based on their function, criticality, communication requirements, and cybersecurity needs\u2014and control communication between those groups.<\/p>\n A manufacturing organization might separate:<\/p>\n The exact architecture will depend on the business.<\/p>\n But the broader principle matters:<\/p>\n Connectivity should be intentional.<\/strong><\/p>\n A production machine should not automatically trust every laptop simply because both happen to be connected to the company’s network.<\/p>\n Likewise, a vendor should not necessarily receive broad network access simply because remote maintenance is required.<\/p>\n As IT and OT converge, network architecture becomes part of business-risk management.<\/p>\n Modern manufacturing and mobility ecosystems rarely operate in isolation.<\/p>\n A business may depend on:<\/p>\n Each relationship can introduce another technical connection.<\/p>\n That creates a governance question:<\/p>\n Who owns the whole environment?<\/strong><\/p>\n A machine vendor may understand the machine.<\/p>\n A cloud provider understands its platform.<\/p>\n An MSP understands the corporate IT environment.<\/p>\n An automation company understands the workflow.<\/p>\n An engineering team understands the product.<\/p>\n A cybersecurity provider understands security controls.<\/p>\n But leadership still needs someone looking horizontally across those domains.<\/p>\n Otherwise, organizations can accumulate capable vendors without developing a coherent technology strategy.<\/p>\n Large enterprises can maintain specialized teams for:<\/p>\n A 30-, 50-, or 100-person manufacturer usually cannot.<\/p>\n But the complexity doesn’t disappear simply because the organization is smaller.<\/p>\n This creates a growing gap.<\/p>\n An organization can become too technologically complex for reactive IT support while remaining too small to justify a complete internal technology leadership organization.<\/strong><\/p>\n That is where a combined Managed IT<\/a> + Fractional CIO<\/a><\/strong> model becomes particularly relevant.<\/p>\n Managed IT provides the operational foundation:<\/p>\n Fractional CIO leadership addresses the larger questions:<\/p>\n The value isn’t simply having another IT provider.<\/p>\n It is creating technology ownership across an increasingly interconnected business environment.<\/strong><\/p>\n This evolution maps naturally into our Build.<\/strong> Protect. Accelerate.<\/strong> Business Technology Framework.<\/p>\n The first objective is visibility.<\/p>\n Identify:<\/p>\n Then establish reliable technology operations, documentation, standards, and ownership.<\/p>\n For manufacturing environments, Build increasingly means understanding both traditional IT and the systems IT depends on or connects with.<\/p>\n Once the environment is understood, organizations can better determine how it should be protected.<\/p>\n That may involve:<\/p>\nMichigan’s Mobility Investments Point to a Bigger Technology Shift<\/h2>\n
The Traditional Definition of IT Is Becoming Too Narrow<\/h2>\n
\n
IT\/OT Convergence Is Already Happening<\/h2>\n
\n
Connected Technology Changes Cybersecurity<\/h2>\n
\n
Start With Visibility<\/h2>\n
Business IT<\/h3>\n
Engineering Technology<\/h3>\n
Operational Technology<\/h3>\n
Connectivity<\/h3>\n
Data<\/h3>\n
Cybersecurity<\/h3>\n
Business Continuity<\/h3>\n
Segmentation Becomes Increasingly Important<\/h2>\n
\n
External Partners Add Another Layer<\/h2>\n
\n
This Is Where the CIO Role Changes<\/h2>\n
\n
\n
\n
Build. Protect. Accelerate. in a Converged Environment<\/h2>\n
BUILD \u2014 Understand and Stabilize the Environment<\/h3>\n
\n
PROTECT \u2014 Secure the Connections<\/a><\/h3>\n