For asset-intensive organizations modernizing or replacing engineering document management
One controlled engineering record, for the life of the asset.
ECH360 by TechTiera is a project-to-asset engineering information management solution powered by Hyland Alfresco. It connects MDR-driven project delivery, engineering WIP, EPC and vendor collaboration, review and approval, authoritative master records, asset and equipment context, operations and future brownfield change.
ECH360 = TechTiera engineering solution layer · Hyland Alfresco = enterprise content platform foundation
01Project Workspace + MDR
02Master Records / Engineering Vault
03Asset / Equipment Context
04Operations
What is ECH360?
Project-to-asset engineering information management on Hyland Alfresco
ECH360 combines a pre-built engineering information model, modular business capabilities and controlled workflows on the Hyland Alfresco platform. It is configured to your document classes, numbering, metadata, approval chain, organizational model and asset structure. Configuration first, with customization only where specific behavior requires it.
In practitioner terms: the register, the documents, the review, the transmittal and the as-built all live in one place, and that place knows which revision is current, who approved it, when it was sent, to whom, and what it’s attached to.
From the first FEED deliverable to a modification made twenty years into operations.
What TechTiera brings
Project and asset workspace templates, the engineering information model, MDR and SMDR registers, review and transmittal workflows, handover controls, dashboards and integration patterns. Configured to your operating model, not coded from a blank page.
What Alfresco brings underneath
The content repository, versioning, permissions, full-text and metadata search, process integration, governance options, open APIs, and a deployment model your IT team can support and upgrade.
Where teams start
With the module that has a date attached, usually register control, transmittals, or an approaching handover milestone. The other five wait for the next project or the next audit.
The lifecycle
The MDR controls project deliverables while authoritative master records remain separate from asset context
The project workspace provides the business context and the MDR acts as the planned and controlled deliverable register. Documents are created and revised in WIP, reviewed, approved and issued through controlled transmittals. Accepted as-built information becomes the current authoritative master record, which is then linked to persistent facility, system, equipment and tag context for operations and future modification projects.
Project Workspace + MDR
Establish project context, team, metadata and planned engineering deliverables.
Engineering WIP
Create, receive and revise documents and drawings against controlled deliverables.
Review & Approval
Capture technical review, markups, comments, responses, decisions and approvals.
Revision & Transmittal
Control revisions and formal exchanges with revision-aware issue history.
Approved / As-Built
Validate completeness, acceptance evidence and final handover readiness.
Master Records / Vault
Create the current authoritative approved engineering record with project lineage.
Asset Context & Operations
Link current masters to facility, system, equipment and tags for operations and future change.
ECH360 operating model
Project delivery, authoritative records and asset context are related, but deliberately not the same thing
ECH360 separates temporary project work from the long-lived engineering record. The MDR remains inside the project as the planned deliverable control layer; accepted as-built information is promoted to Master Records / Engineering Vault; asset and equipment workspaces provide the persistent operational context for those authoritative records.
Project Workspaces
Project business context for people, content, data and tasks.
- Project metadata and team
- MDR / SMDR planned deliverables
- Engineering WIP and revisions
- Review / approval and markups
- Transmittals and close-out
Master Records / Engineering Vault
The current authoritative approved engineering record.
- Approved / as-built documents
- Current controlled revision
- Project lineage retained
- Read-only / governed master use
- Controlled basis for future revision
Asset / Equipment Context
Persistent engineering context that can outlive many projects.
- Facility / plant
- System
- Equipment
- Engineering tag
- Operations and maintenance access
Project Workspace + MDR → Engineering WIP → Review / Approval → Approved / As-Built → Master Records / Engineering Vault → Asset / Equipment Context → Operations → Future Modification Project
Shared foundation: Engineering Information Model · Workflow · Search · Security · Governance · Audit · Retention · Integration
Six modular capabilities
Adopt together or phase them around your business priorities
All six capabilities share the same engineering information model, security, search and governance foundation. They can be deployed together or phased around project, handover, compliance and operational priorities.
Capital Projects Documentation
The project record, from a governed template rather than from somebody’s old folder. Template-based project workspaces with discipline hierarchies. A master document register (MDR and SMDR) with deliverable planning and forecast submission dates. Document and drawing registration, configurable numbering, metadata validation at the point of capture, controlled review and approval, markups and comment-response sheets, deadline notifications, project dashboards and a closeout process that has to be satisfied rather than declared.
Used daily by document control and project controls on a live project. Read weekly by the engineering manager and the project manager.
Asset Documentation
The persistent operational context for authoritative engineering information, organised by plant rather than by project. Master Records / Engineering Vault retains the current approved engineering record; asset workspaces organise access through field, facility, system, equipment and tag context, linked back to the originating project and forward to later modifications.
Used by maintenance and reliability engineers, asset and plant information managers, and the next project team that needs to know what is actually installed.
Transmittals Management
Who sent what, to whom, on which date, at which revision. Incoming, outgoing and internal transmittals with configurable numbering and cover sheets. Package validation before issue, recipient and distribution controls, acknowledgements, revision-aware document lists, and a complete transmission history held as a record in its own right.
Owned by document control. Relied on by anyone who has had to prove a document was issued, and by commercial teams when a claim is being argued.
QHSE Hub
Governed compliance content, with an owner and a review date on every item. Policies, plans, permits, inspections, risk assessments, incident records and corrective actions. Each item carries ownership, a review cycle, approval history and permissions that match who is actually allowed to see it.
Used by QHSE managers and HSE document controllers. Read by site supervisors, and by whoever sits opposite the auditor.
SOP Hub
Controlled procedures, and supersession that actually supersedes. Controlled authoring, review, approval, publication and periodic review of procedures and work instructions, with supersession control so a retired version stops being findable as if it were current.
Used by operations supervisors and training and competence teams. Owned by the technical authority for each procedure.
Management of Change
Change on a live asset, with the document updates inside the change rather than after it. Configurable initiation, technical assessment, impact review, approval and closure workflows, with closeout blocked until affected documents are actually updated.
Run jointly by operations, engineering and QHSE. Owned in practice by the MOC coordinator, and audited by whoever answers to the regulator.
See ECH360 against your own engineering scenario.
Under all six modules, the same eight things
Properties of the platform and information model rather than features of one module.
Adopting a second module later doesn’t mean configuring all of this again.
Information model
Configurable document classes, mandatory/optional metadata, controlled vocabularies, your own naming conventions.
Document control
Single/bulk upload, check-in/check-out, version and revision history as two separate ideas, status control.
Search & discovery
Full-text and metadata search, faceted filters, saved views, OCR-enabled discovery where configured.
Engineering review
Online markup and annotation, concurrent/sequential review, consolidated comments, response tracking.
Security & governance
Role-, organization-, workspace- and project-scoped access, with document-level restrictions where required, plus audit history and controlled external collaboration.
Reporting
MDR progress, overdue submissions, review aging, transmittal status, handover completeness, configurable KPIs.
Integration
API-led patterns for ERP, EAM, CMMS, project controls, identity services and BI/reporting.
Enterprise-to-project governance
Organization onboarding is centrally governed; project access is locally administered
ECH360 separates enterprise administration, business-unit control and project-level access so internal teams, EPC organizations and vendors can collaborate without weakening accountability or project boundaries.
Enterprise Workspace
Super Administrator
- Platform and global configuration
- Business Unit administration
- Enterprise security, audit and integration oversight
Business Unit
Business Administrator
- Business Unit configuration and standards
- Projects and templates
- External organization administration
- EPC and Vendor/Supplier onboarding
Project Workspace
Project Administrator / Project DCM
- Project members and roles
- Project-specific permissions
- Workflow and document-control administration
- EPC and vendor access within approved scope
EPC Organization
Business-unit administration approves the EPC organization. The Project Administrator assigns approved EPC users to the project. EPC DCM coordinates EPC engineers, procurement and operational disciplines within the authorized scope.
Vendor / Supplier Organization
Vendor organizations and identities are governed centrally, while project administrators assign scope-specific access for submissions, comment responses, transmittals and deliverable collaboration.
Governance principles: Least privilege · Segregation of duties · Project-scope enforcement · Controlled external collaboration · Lifecycle access review · Full audit and traceability
Architecture and deployment
Four layers, and it’s clear which two are ours
Nothing in the stack is a black box. Every layer is something your IT team can read, support and upgrade. Configuration first, customization only where a specific behavior requires it.
Role-based project, asset, document control, contractor, QHSE and SOP experiences, with dashboards and task views.
Workspace templates, numbering, metadata rules, MDR/SMDR, review workflows, transmittals, handover controls, notifications and reports.
Content Services (repository, metadata, versioning, audit, security), Digital Workspace, process/workflow services and enterprise search, with OCR where configured.
Identity and access management, ERP, EAM, CMMS, project controls, email/collaboration, BI, e-signature (integrated with, not replaced).
Deployment: customer-managed, private-cloud and cloud patterns can all be considered, depending on the Alfresco edition, your architecture standards, data-residency rules and commercial model, confirmed during discovery, not assumed up front.
Who it’s for
Three kinds of organization, one shared record
Owners & Operators
Capital projects and asset information. You fund the project and inherit the record. Project WIP and the master asset record stay separate, so what operations inherits is what engineering approved.
EPC & EPCM Teams
Engineering deliverables and contractor collaboration. Graded on submission dates and review turnaround; MDR status is reported from the record instead of reassembled for a report.
Operations & Compliance
MOC, QHSE, SOPs and audit-ready records. What’s current, who approved it, and whether a change to the plant also changed its documents, all answerable from the record itself.
Where this fits, and where it’s more than you need
Built for this
More than you need today
See ECH360 against your own engineering scenario.
Industries
Built for engineering-intensive, asset-heavy industries
ECH360 is designed for capital-intensive, drawing-heavy environments where engineering information must remain controlled from project delivery through long-term operations.
We lead with the sectors where TechTiera has the strongest engineering document-control relevance.
Marine, Offshore & Heavy Fabrication
Shipyards, offshore fabricators, FPSO and topsides, rig builders, naval and defense yards. Extreme drawing volume per hull or unit and a contractual delivery date that doesn’t move.
Oil & Gas, LNG and Process Plant
Oil and natural gas, LNG, refining, chemicals, power and utilities, water and wastewater. A permanent brownfield asset base and MOC as a standing legal obligation.
Industrial Manufacturing Capital Projects
Automotive, building materials, glass and packaging, heavy engineering, semiconductor and advanced manufacturing. Many concurrent plant and line projects, no two set up the same way.
Also serves:
Renewable energy
Transportation infrastructure
Civil & urban infrastructure
Datacenters & digital infrastructure
Buildings & real estate
Pharmaceuticals & life sciences
Defense & aerospace
Environmental & waste management
Agriculture & food infrastructure
Proof
Recognized by Hyland. Delivered in the industries this is built for.
Third-party recognition of the Hyland partnership, not a customer reference for this specific solution.
What we’re not going to claim: ECH360 is positioned as TechTiera’s engineering solution layer on Hyland Alfresco. Product-specific customer references and quantitative outcomes should be used only where separately approved and evidenced. Evaluate the solution through a working session against your own project, MDR, handover or asset scenario.
See ECH360 against your own engineering scenario
Bring one real project, MDR, handover or asset scenario. We will map it against the ECH360 project-to-asset model using your numbering, metadata and document-control requirements.
Or book by email: info@techtiera.com