How do multi-divisional corporations setup their technology infrastructure to allow each division to operate as a separate unit within the intra-corporate domain? Think like an apartment building where each unit is metered and/or share services like water, etc through their metered connection. I am at a lost on how to begin this structure using the IOT or cloud based infrastructure. Would we share one domain, Should we have subdomains per division? If so, I need direction on where to begin strategy development on this.
Most cloud based services allow you to create different service groups or other methods to group services together, many of them with different billing units. This way you can track what each division spends on a particular platform. I’ve used several different cloud platforms for my own business and my clients and almost all of them have the ability to track expenses based on named resources.
For example, if you’re hosting through Google Cloud Services, you can create different projects under the same account, and the billing details will be broken down for internal tracking. The projects will still be able to communicate with each other securely through the GCS infrastructure. Amazon Web Services has similar functionality as do the non managed platforms such as Linode and DigitalOcean.
Without knowing more on what your company is doing specifically, I can only generalize. If you’re looking for additional information or need help creating a structure, feel free to message me.
There is usually a chief technology officer (CTO) responsible for this. The CIO will then reflect this relevant information technology aspects of operations in the IT infrastructure. Their experience and expertise allows them to apply wide range of strategies depending on the specifics. Divisions usually share common governance, but common technology depends on a lot of factors. There are usually common systems for some aspects of the business (e.g., shared HR or legal services) while other aspects (costs and performance requirements lead to different mechanisms) are not common across divisions.
A single entity normally has a single top level domain (TLD), however, in many cases, such entities are formed by mergers and acquisitions, and as a result, branding my produce multiple TLDs, and divisions may be also have different TLDs for other branding reasons. Again, this is an executive team effort, or in some cases determined with the executive team working with division heads, depending on the particulars.
This is so incredibly easy to execute that I'm surprised it is a question, unless you're just trying to understand.
Just about any network engineer could build a structure for you that will behave in the way you describe.
All you need to do is describe what you want to happen, and why. It may be simple enough that it could be completed in a matter of hours. And if you're not ready to build it, the configuration could be diagrammed in even less time.