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.
Bring one of your own scenarios and we will run the whole line against it.
One project workspace, one asset record, one controlled handover, end to end. Twenty minutes, no slide deck. You can use your own numbering convention and document types so you are watching your environment, not a demo dataset.
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. Open and API-led, which matters when this has to outlive the project that funded it.
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. Nobody adopts the whole lifecycle on day one.
When the register, the document, the revision and the asset stop agreeing, control becomes manual
ECH360 is designed for the point where shared drives, email, spreadsheets and disconnected repositories can no longer reliably answer which deliverable is due, which revision is current, who approved it, what was transmitted, or which asset the final record belongs to.
Project delivery pressure
MDR dates, contractor submissions, review cycles and transmittals need one governed status rather than separate trackers.
Handover risk
Approved as-built content must cross a controlled gate into authoritative master records with completeness, lineage and evidence intact.
Operations continuity
The asset can outlive many projects, so operations needs current master information linked to facility, system, equipment and tag context.
The plant outlives the project that built it. The record has to last as long as the plant.
One approved as-built, promoted into the master records with its revision history and its transmittal trail still attached, and read against the equipment tag by whoever is on shift twenty years from now.
Two conditions of the work, and the control that answers each one
Illustrative, not a client screenshot. Both will be familiar to anyone who has run document control on a live project. The caption under each one names what the information model does about it.
| Document | Register | Actual | Status |
|---|---|---|---|
| P-4471-PID-002 | Rev B | Rev C | out of step |
| P-4471-DS-118 | Rev A | not found | missing |
| P-4471-SPC-007 | Rev C | Rev C | in step |
| P-4471-VM-233 | not reg’d | Rev 1 | unregistered |
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.
└ Gas processing plant
└ Compression system
└ 3400-P-01B: PID-2200-0014, Rev C, approved · DS-3400-0071, Rev B, approved · ASB-2200-0007, Rev 1, as built
Down: validated documents accepted into master records, with revision history and transmittal trail attached. Up: operations and the next project draw the current record from the asset itself. (Illustrative, numbers and tag invented for this drawing.)
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.
Project delivery, authoritative records and asset context are related, but deliberately not the same thing
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.
Where work happens
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
What is authoritative
Master Records / Engineering Vault
The current authoritative approved engineering record.
- Approved / as-built documents
- Current controlled revision
- Project lineage retained
- Governed master use
- Controlled basis for future revision
What it is attached to
Asset / Equipment Context
Persistent engineering context that can outlive many projects.
- Facility / plant
- System
- Equipment
- Engineering tag
- Operations and maintenance access
Where this fits, and where it’s more than you need
Built for this
More than you need today
If your situation is in the right-hand column, say so on the call.
We will tell you what the shorter piece of work is instead, and there is no charge for finding that out.
Find out which column you are in before you spend a budget cycle on it.
Three kinds of organisation, and the eleven stakeholders who work the same record
Engineering document control has a wide buying committee, and the reason it is wide is that a document passes through most of it. Their needs converge on the same six things: fast search, simple workflows, secure collaboration, auditability, data integrity and compliance.
Owners and Operators
Capital projects and asset information. You fund the project and you inherit the record. Project work in progress and the master asset record stay separate, so what operations inherits is what engineering approved.
EPC and EPCM Teams
Engineering deliverables and contractor collaboration. You are graded on submission dates, review turnaround and a turnover package. MDR status is reported from the record instead of reassembled for the report.
Operations and Compliance
MOC, QHSE, SOPs and audit-ready records. You run the asset after handover. What is current, who approved it, and whether a change to the plant also changed its documents are all answerable from the record itself.
Five access principles the same record is held under
The stakeholder map, by group
Sets the standard, funds the work, and inherits the record at the end of it.
Executive sponsor and governance
Owns the mandate, the standard and the funding. Needs a defensible position on record completeness without reading the register personally.
Project manager, execution oversight
Needs progress and review status read off the record rather than reassembled for the weekly report.
Document controller
Runs the MDR and metadata, the documents and transmittals. Needs numbering validated at capture.
Engineer and lead engineer, reviewer
Needs the current revision and the whole comment history in one place.
Project manager, approver
Needs the approval evidence to outlast the project that produced it.
Procurement engineer and expeditor
Needs the outstanding list to be a live view of the register.
Submits into your standard, and is graded on how well it lands.
EPC engineer, submitter
Needs the submission requirement stated up front and a traceable response against every comment raised.
EPC document controller
Needs one place where the status is the status.
Contributes a small part of the record that handover cannot be signed without.
Vendor and supplier representative
Needs access scoped to the documents that concern them, and acknowledgement of what was received.
Reads the record for the whole life of the asset.
Operations and maintenance engineer
Needs to search against the tag, the equipment and the system, and find as-builts, manuals and modification history attached to the thing they belong to.
Keeps it supportable, integrated and upgradeable.
System administrator
One Alfresco-based architecture with a common security model, identity integration, API-led integration to ERP/EAM/CMMS, full audit history, and a documented upgrade path.
Bring your own project and we will map these eleven roles onto it in one session.
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 engineers, procurement and operational disciplines within 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.
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.
Asset Documentation
The record operations actually works from, organised by plant rather than by project. Enterprise asset workspaces aligned to field, facility, system, equipment or a hierarchy you define yourself. Engineering, vendor and as-built records with controlled renditions alongside native files, cross-linked back to the originating project and forward to later modifications.
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.
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.
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.
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.
Not sure which module has the deadline attached to it? That is the first question the session answers.
Under all six modules, the same seven things
Properties of the platform and the information model rather than features of one hub, which is why adopting a second module later does not mean configuring all of this again.
Information model
Configurable document classes, mandatory/optional metadata, controlled vocabularies, your own naming conventions. Legacy and new numbering can coexist.
Document control
Single/bulk upload, drag-and-drop registration, 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, results that respect permissions.
Engineering review
Online markup and annotation, concurrent/sequential review, controlled offline re-upload, consolidated comments, response tracking.
Security & governance
Role-, organization-, workspace- and project-scoped access, with document-level restrictions where required, plus audit history, controlled external collaboration, watermarking and retention controls.
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, collaboration, BI and reporting.
“Audit trail: no more ‘I didn’t get that document.’ File sharing and file opening is tracked by user. Transmittals are a matter of record and there’s no ‘delete’ function.”
Principal at a project management consultancy, describing document control on a $30M public-sector infrastructure project
Project deliverables
- Engineering drawings
- PFDs
- P&IDs
- Calculations
- Datasheets
- Specifications
Contractor and vendor records
- Vendor manuals
- Vendor certificates
- Technical queries
- Correspondence
- Meeting minutes
- Transmittals
Operations and compliance records
- As-built records
- Inspection & quality records
- Permits
- Risk assessments
- SOPs
- Work instructions
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 defence yards. Extreme drawing volume per hull or unit, class society and owner turnover packages, and a contractual delivery date that does not move.
Oil & Gas, LNG and Process Plant
Oil and natural gas, LNG, refining, chemicals and petrochemicals, power and utilities, water and wastewater. A permanent brownfield asset base and management of change as a standing legal obligation.
Industrial Manufacturing Capital Projects
Automotive, building materials, glass and packaging, heavy engineering, food processing, semiconductor and advanced manufacturing. Many concurrent plant and line projects, no two set up the same way.
The wider set the same modules cover
- Mining, metals & minerals
- Renewable energy
- Transportation infrastructure
- Civil & urban infrastructure
- Datacenters & digital infrastructure
- Buildings & real estate
- Pharmaceuticals & life sciences
- Defense & aerospace infrastructure
- Environmental & waste management
- Agriculture & food infrastructure
Same information model, same governance, different vocabulary. If your line is on this list, the honest first question is whether your document volumes and handover obligations justify a configured platform at all. The readiness review answers that before anyone writes a proposal.
Four layers, and it’s clear which two are ours
TechTiera’s engineering information model, experiences, workflows, dashboards and integration patterns sit on the Alfresco Content Services foundation.
Nothing in the stack is a black box, and every layer of it is something your IT team can read, support and upgrade.
Configuration first, and customisation only where a specific behaviour requires it.
Role-based project, asset, document control, contractor, MOC, QHSE and SOP experiences, with dashboards and task views. A document controller and a maintenance engineer do not get handed the same screen.
Workspace templates, numbering, metadata rules, MDR and SMDR, review workflows, transmittals, handover controls, notifications and reports. This is the layer that makes the difference between a platform and a solution.
Alfresco Content Services for the governed repository, metadata, versioning, audit and security. Alfresco Digital Workspace for the user experience. Process/workflow services and enterprise search & OCR.
Identity and access management, ERP, EAM, CMMS, project controls, email/collaboration, BI and e-signature. We integrate with these rather than asking you to retire them.
Named components in the stack
- Alfresco Content Services
- Alfresco Digital Workspace
- Hyland process & workflow services
- Enterprise search & OCR
- REST APIs & integration layer
Deployment: Customer-managed, private-cloud and cloud patterns can all be considered. Which ones apply depends on the Alfresco edition selected, your architecture standards, data-residency rules and commercial model. High availability, disaster recovery, backup, monitoring and security controls are sized and designed for the specific deployment rather than quoted from a template.
[NEEDS: verified list from the Alfresco practice team]: confirmed editions, hosting regions and supported topologies. Deployment topology and performance sizing are confirmed during discovery and written into scope, which is the only place either of them can honestly be stated.
The proof, stated the way we would want it stated to us
Third-party recognition of the Hyland partnership, the strongest independent evidence that exists for a solution this new. It is not a customer reference for this solution, and we are not going to present it as one.
An Alfresco practice that already exists
- Alfresco Content Services configuration, customization, Activiti workflow and BPM development, integration and records management.
- Managed services, health checks and performance work, 24x7x365, remote or onsite.
- Practice headcount and certification count: [NEEDS: verified number]
Engineering document control delivered in the industries this is built for
- Three oil and natural gas engagements: one platform modernization and two platform upgrades and implementations, one for an operator at major scale in APAC.
- Implementation and long-run support for the largest ship building company in APAC.
- Capital-project workspace provisioning automated for an industrial manufacturer.
- Named enterprise clients in industrial and manufacturing sectors include Hilti, Tenneco, Federal-Mogul and Ardagh Glass.
Engineering document control, delivered
An anonymized engineering EDMS case-study pattern showing the business challenge, solution design and expected project-to-asset outcomes that ECH360 is designed to support.
From Fragmented Engineering Content to a Governed Project-to-Asset Record
How a multi-site oil and gas operator modernized document control, collaboration and asset information management with ECH360.
“ECH360 replaced fragmented, folder- and email-driven document handling with a governed model connecting project work in progress, engineering decisions, approved master records and operational asset context.”
The Challenge, in one sentence
“Approved as-built records could be promoted into asset context with project lineage intact, supporting retrieval, maintenance decisions and future brownfield work.”
Results and Business Value: Operations-ready asset information
“ECH360 created a governed engineering information ecosystem connecting Project WIP → Approved Master Records → Asset Context → Operations, with security, metadata, version control, audit, retention and integration available as shared services.”
Lasting impact
Five phases, in this order, for a reason
Configuration-led, not a code project. Each phase produces something you can review before the next one starts, and you can stop after any of them.
Discover
Confirm lifecycle scope, personas, document classes, registers, numbering, workflows, volumes, integrations and compliance evidence.
Configure
Build the information model, workspace templates, roles, workflows, search, dashboards and integration rules, in your terminology.
Pilot
One real project, one real asset, one real handover scenario. This is where a solution stops being a demo.
Roll out
Roll out the configured solution by project or business unit, onboard users, train teams and turn on governance.
Operate
Application support, administration, release management, optimization and roadmap. The same team that configured it keeps running it.
Typical duration per phase: [NEEDS: verified number]. We would rather leave this blank than quote a timeline before seeing your document volumes and integration list.
When this is the wrong answer
Two of the four situations below come up often enough that saying so early saves everyone a quarter.
When the decision to be made is a process decision
Document control works when someone has the authority to reject a deliverable at the gate. Configuration puts the gate in the path, names the criteria and holds the evidence. No software supplies the decision to say no at that gate.
When the fix is configuration in what you already run
If you already run a capable EDMS and the open item is numbering, review routing or reporting, the cheapest correct answer is usually to fix the configuration you own. We will say that in the readiness review, and we do not send a proposal after saying it.
When you are mid-project and the change is the wrong one
Numbering conventions are painful to change mid-project and usually should not be. Review routing, transmittal control and handover preparation can be improved at almost any point.
What we will not tell you
We will not tell you that this makes you compliant with anything. Records and retention depend on controls you define and evidence you produce. What a configured platform can do is support those controls and hold the evidence.
ECH360 Project-to-Asset Solution Workshop
Bring one real project, MDR, handover or asset scenario. We will map it against the ECH360 project-to-asset model using your numbering, metadata, document-control and governance requirements.
Handover completeness read
The acceptance criteria your package will actually be measured against, and which categories are currently unmet.
The blocking versus noise split
Most outstanding-document lists mix contractual blockers with items nobody will ever ask for. We separate them.
Operations-inheritance risk list
What becomes someone’s problem after sign-off, and what each item costs to fix now versus later.
A staged closeout sequence
What to fix in the next 30 days, what to negotiate into the handover agreement, and what to accept as a documented exception.
- Scenario-led workshop
- No documents needed from you
- Deliverables yours to keep
- Architecture and governance focused
- Built on Hyland Alfresco
- Support model by engagement
- Global delivery capability
Handover coming up? Find out now what will be argued about later.
A completeness read, the blocking versus noise split, an operations risk list and a staged closeout sequence. Free, 60 minutes, yours to keep, no pitch.
Questions engineering and document control teams ask us first
What exactly is ECH360?
It’s a pre-built engineering document management system (EDMS) on Hyland Alfresco. Six modules, one information model, one security model, covering capital project documentation, asset documentation, transmittals, QHSE, SOPs, and management of change. Configured to your document classes, numbering and approval chain rather than coded from scratch.
This is a brand-new solution. What does that actually mean for us?
It means the six modules and the underlying engineering information model are newly packaged, but the platform underneath (Hyland Alfresco) and the team configuring it aren’t new to either Alfresco or engineering document control. What’s new is the pre-built configuration; what isn’t new is the delivery capability behind it.
Do we have to replace our existing EDMS to start?
No. Most teams start with one module (usually the one with a date attached, like transmittals or an approaching handover) running alongside what you already have. There’s no requirement to replace every existing repository or process on day one.
Which module do most teams start with?
Whichever one has a deadline attached. That’s usually Transmittals Management or Capital Projects Documentation ahead of a handover milestone. The other modules wait for the next project or the next audit. Nobody adopts the whole lifecycle at once, and we don’t recommend trying to.
Is this an Alfresco product or a TechTiera product?
Both, in the sense that matters. Alfresco Content Services and Digital Workspace are Hyland products underneath. The engineering information model, the six modules, the workflows and dashboards are TechTiera’s, built by our Alfresco practice, configured to your operating model, not bought off a shelf as a finished product.
What does the architecture look like, and where can it be deployed?
Four layers: your existing enterprise systems (ERP, EAM, CMMS, identity, etc.) at the base, the Hyland Alfresco content platform above that, TechTiera’s solution services above that, and the role-based experience layer on top. Deployment can be customer-managed, private cloud, or cloud, confirmed during discovery, not assumed up front.
What does engineering document control actually require, beyond storing the files?
Numbering and classification applied at the point of capture. A revision history that’s a record in its own right, not just a filename. Review and comment tracking with disposition codes. Transmittals that prove what was sent, to whom, when, and whether it was acknowledged. Validation gates before anything is promoted to master records. And retrieval by asset tag, not folder path, once it’s in operations.
We are mid-project. Is it too late to change anything?
Changing your numbering convention mid-project usually isn’t worth it. But review routing, transmittal control and handover preparation can be improved at almost any point in a project’s life. We’ll tell you which bucket your situation falls into in the readiness review, not after a proposal.
Our client mandates their EDMS for this project. Is this still useful?
Yes. Most EPC and vendor organizations run multiple clients’ mandated systems in parallel and still need their own internal control: MDR tracking, submission status, revision history and vendor coordination on their side of the fence. This can sit alongside a client-mandated system rather than replace it.
Do we have to share drawings or project documents for the readiness review?
No. The review runs on your description of the handover, the register, and the current state, not on your actual documents. Nothing is uploaded or reviewed as part of it.
Does this make us compliant with our industry standards?
No, and we won’t claim it does. Compliance depends on the controls you define and the evidence you produce. What a configured platform does is support those controls and hold the evidence reliably. Anything past that line is a statement about your process, not our product.
What does the readiness review cost, and what is the catch?
It’s free, 60 minutes, and there’s no requirement to engage us afterward. The four deliverables are yours to keep either way. The only “catch” is that we’ll tell you plainly if this isn’t the right fix for your situation.
Not ready to talk? Keep researching
What Does “As-Built” Actually Have to Mean at Handover?
Why Your Register and Your Drive Stop Agreeing
What Engineering Document Control Actually Requires
Management of Change Without Losing the As-Built
Alfresco Consulting Services and Support
ECH360 Project-to-Asset Solution Workshop
Bring one real project, MDR, handover or asset scenario. We will map it against the ECH360 project-to-asset model using your numbering, metadata, document-control and governance requirements.
A completeness read, the blocking versus noise split, an operations risk list and a staged closeout sequence. Free, 60 minutes, yours to keep, no pitch.
Prefer email? Write to info@techtiera.com with the project, the milestone and the date it lands on, and we will come back with a time.
If the form does not load on your network, email info@techtiera.com with the project, the milestone and the date it lands on.