SharePoint Enterprise Intranets for Multi-Site Manufacturers
Summary
We build enterprise intranets for manufacturing groups operating across many sites and countries. Work of this kind covers information architecture and governance, controlled document management, provisioned project workspaces, approval workflows, identity consolidation where organizations merge, migration from legacy content platforms, and multilingual rollout. The result is a working surface for procedures, projects and people, not a news page bolted onto a document store.
The Challenge
In a multi-site manufacturing group an intranet carries controlled documents, project collaboration, health and safety and quality procedures, engineering change communication, supplier documentation and human resources processes. Users range from office staff with full desktops to plant personnel on shared terminals and mobile devices. That mix drives concrete requirements: predictable navigation regardless of entry point, search that returns the current revision of a procedure, not a draft, and permissions that follow organizational reality rather than folder habits.
Structural decisions are made early and are expensive to reverse, and the recurring failures are structural too: permission sprawl through unique per-item breaks becomes unmanageable at scale, folders used as the taxonomy make search impossible to tune, indiscriminate migration carries obsolete content into the new estate, and heavy customization blocks future upgrades. Ownership matters too, because a site with no accountable owner turns into unmaintained content that erodes trust.
The Solution
Information architecture and governance
Content is separated into site collections or hub-connected sites by purpose and lifecycle: communication sites for news, team sites for departments, and provisioned project workspaces. Content types and site columns define document classes such as work instruction, drawing, audit report or supplier certificate, published centrally from a content type hub so every site inherits the same metadata contract. Managed metadata term sets carry plant, product line, region and language. Search is tuned by mapping crawled properties to managed properties and building refiners and result types on that metadata, which is what makes a large estate navigable. Governance covers site request and approval, ownership, retention labels, and when a workspace is archived rather than left to decay.
Workspaces, templates and workflows
Consistency comes from provisioning, not documentation. We define site templates that create the workspace, libraries, content types, views, navigation, default permissions and initial task structure in one operation, driven by a provisioning engine and scripted deployment rather than manual configuration. Predefined workflows cover the recurring approval patterns:
- Document review and controlled release
- Engineering change requests
- Capital expenditure approvals
- Onboarding of a project team
Roles are attached to the template so every new workspace inherits the same responsibility model, and cross-site reporting is possible because the schema is identical everywhere.
Identity, migration and multilingual reality
Where two organizations are being brought together, identity is the hardest technical constraint. Separate directories mean duplicate accounts, conflicting principal names, mismatched group models and two sets of profile attributes, so consolidation involves directory synchronization, profile mapping, group rationalization and a decision about how audiences are computed. Migration requires metadata mapping rather than file copying: source fields become managed metadata, permissions are translated into the new model, versions and dates preserved where required, and content checked with hash-based verification. Multilingual estates need a defined language strategy for interface, navigation and content, with fallbacks agreed rather than accidental.
Build and rollout
We start with a content and process inventory, then design the taxonomy and permission model against it before building anything. Customization is layered so upgrades remain possible: extensions and front-end web parts rather than changes to the platform core, deployed through source control and automated pipelines. Branding, terminology and familiar navigation patterns are carried forward where they do not conflict with the new structure, because continuity lowers the learning curve. Rollout is staged by site and region, with pilot groups, measurement of search success, and support content in the languages in use.
What This Delivers
Staff at every site read the same authoritative procedure in the same place, and search returns the released revision, not a draft. New projects open with their libraries, roles and approvals already in place, so collaboration starts immediately. Permissions reflect the organization rather than folder habits, which makes access reviews defensible. Because customization sits in supported extension points, the estate can be upgraded rather than frozen.
Technologies and Tools
SharePoint, using communication sites, hub-connected team sites, content type hub publishing, the managed metadata term store, search schema and refiners, and retention labels. Around it: a site provisioning engine, scripted deployment, front-end web parts and extensions, directory synchronization for identity consolidation, migration tooling with checksum verification, and source-controlled build and release pipelines.