What happens after the Business Analyst hands
you the design — ADW views, ODI pipelines, dataset governance, security, and
everything the agent needs to actually work in production.
This is Part 2 of a two-part series on OAC AI
Agent design. Part 1 — The Business Analyst's Guide — covers
discovery, dataset field design, knowledge document structure, and supplemental
instructions from the BA perspective. This blog picks up where the BA handoff
package ends and focuses on the IT Architect's implementation responsibilities.
If you
have read Part 1 of this series, you know that a Business Analyst's job is to
define what the OAC AI Agent needs — the questions it must
answer, the fields it requires, the policies it must reference, and the
vocabulary it must understand. A well-executed BA design produces a complete
handoff package: field specifications, derived metric formulas, knowledge
document drafts, vocabulary maps, and supplemental instructions ready to paste
into OAC.
Download complete Guide from our linkedIn Page
The IT
Architect's job is to make that design technically real — and to make it trustworthy
at scale. Not just for the first agent, but for every agent the
organisation will build after it. That requires a different mindset than
building a dashboard or a report. It requires thinking about data lineage,
pipeline governance, security boundaries, and the architectural foundation that
determines whether AI answers can be trusted at all.
This
blog covers the seven technical implementation decisions that separate a
production-grade OAC AI Agent from a demo that works once and breaks in real
life.
The
core risk to understand upfront: An OAC AI Agent
will give confident, fluent, well-formatted answers regardless of whether the
underlying data is correct, governed, or complete. The agent has no way to tell
the user "I am not sure about this number." It answers with the same
confidence whether the data is perfect or wrong. The IT Architect's job is to
ensure the data behind the agent is never the thing that fails.
