If you've been maintaining a separate SharePoint site, internal wiki, or portal just to communicate your organization's approved technology standards—this feature is for you.
The Problem We've All Been Working Around
For those of us managing technology standards in large organizations, the workflow has always been fragmented. Your Technology Reference Model (TRM) catalog lives in EA Workspace, but the people who actually need to know what's approved—developers, project managers, procurement teams—don't have access to it. Or they do, but they're not going to navigate into a specialized workspace just to check if they can use PostgreSQL.
So, what happens? Teams managing lifecycle governance, end up maintaining a parallel documentation effort. Maybe it's a SharePoint site. Maybe it's a Confluence wiki that's perpetually out of date. For federal agencies, this isn't optional—you're mandated by law to publish and maintain technology standards documentation.
Either way, you're doing double work: managing the authoritative catalog in EA Workspace, then manually replicating that information somewhere else for broader consumption.
What's New in Q1 2026
Starting with the Q1 2026 release, you can publish your TRM catalog directly to Knowledge Base—with business rules that enable automatic synchronization for most changes on the TRM catalogue.
Here's what that actually means in practice:
For EA Governance Teams: You will find a new option in the set up called- Publish Centre. Configure your Knowledge base with conditions over what TRM products you want to publish, with control over what data you wish to redact or show. You have complete control over what you want to show on the Knowledge base.
For your consumers: Developers, architects, and procurement teams get a searchable, browsable Knowledge Base with your approved technologies organized by category—no EA Workspace access required. They can search by product name, filter by category, and see exactly the technology lifecycles.
How it Actually Works
The publish wizard has three main configuration areas:
Scope: Define which TRM products to include using filter conditions. Want to publish only approved software products? Only items in specific categories? The filter builder supports any TRM product attribute and allows dot-walking to related fields. A live count shows you exactly how many products will be published based on your criteria.
Displayed content: Choose which fields appear in the published articles. Software and hardware products have separate field selections—you might want to show business justification and investment direction for software, but different attributes for hardware. Fields are pre-selected by default, but you control what's visible.
Catalog type: Internal catalogs require authentication. Public catalogs are accessible to anyone. You can create both with different configurations if you need tighter control over what's exposed externally.
The Auto-Sync Changes Everything
Here's the part that eliminates the double-work problem: you only set up to publish once.
After initial publication, any TRM product that's added, modified, or removed in your catalog automatically syncs to the Knowledge Base—as long as it meets your published scope criteria. Add a new approved database product? It shows up in the KB. Change a product's TRM phase from "Approved" to "Divest"? The article updates. Remove something from scope? The KB article retires.
Manual republishing is only required when you make big changes like updating existing TRM categories or TRM phases. The manual publishing is also a single button click carries over the scope and content conditions of the published catalogue.
Now Assist Makes it Conversational
Here's where it gets interesting for your consumers.
The published Knowledge Base integrates with Now Assist, so users don't have to browse or search in the traditional sense. They can just ask: "Which version of Oracle DB is approved?"
Now Assist pulls from the published TRM articles and returns a synthesized answer—complete with version details, approval dates, and constraints—along with a source link back to the full KB article.
For your developers and project teams, this changes the interaction model entirely. Instead of navigating category hierarchies or scanning article lists, they get direct answers to compliance questions in natural language. "Can I use PostgreSQL 15?" "What's the approved alternative to MongoDB?" "Is Red Hat Enterprise Linux still supported?"
The TRM data you're already maintaining becomes the grounding source for AI-assisted technology decisions—without any additional configuration on your part.
Who Should Care About This
If you've been maintaining parallel documentation of your technology standards—whether by choice or mandate—this consolidates that effort into your single source of truth.
If your developers and project teams have been asking "where do I find what's approved?"—now you can hand them a Knowledge Base link.
If you're a federal agency with compliance requirements around publishing technology standards—this gives you an automatically maintained, auditable catalog without the manual overhead.
