Jul 2026· Universal Library of Engineering Technology· Vol 3, pp. 13-18· 0 citations· 12 references
TL;DR
This review examines the two approaches to embedded assistance through a seven-layer reference architecture that places each in a specific tier and clarifies why the boundary between them lies between the model and orchestration tiers.
Abstract
Customer relationship management platforms now embed artificial intelligence in two structurally different ways, and the choice between them shapes cost, governance, and the pace of organizational change. The first way places assistive models within the interfaces teams already use, so that scoring, summarization, and drafting occur at the point where work is performed. The second way introduces a separate orchestration tier in which semi-autonomous agents pursue goals across several systems while users remain in familiar screens. This review examines the two approaches through a seven-layer reference architecture that places each in a specific tier and clarifies why the boundary between them lies between the model and orchestration tiers. The analysis treats both as design options with measurable trade-offs across change management, expressiveness for multi-step work, architectural coupling, and the surface available for monitoring. Evidence from enterprise practice and the research literature suggests that embedded assistance is more successful during first-generation adoption in mature organizations because it leverages existing processes, whereas a dedicated agent tier yields stronger long-term outcomes for second-wave programs that target genuine cross-system automation. Supporting comparisons across data access, integration style, the trust model, and migration strategy show that the central decision sits inside a wider system of architectural commitments that the framework makes explicit for practicing architects.
Platform engineering has become, over the past several years, the default way large organizations manage the growing complexity of software delivery. That arrival has coincided with a second, less discussed obligation. Platform teams must now build platforms that host AI workloads, retrieval-augmented generation servic...
Sonu Kumar· International journal of com...· 0 citations
Hospitals are racing to embed Artificial Intelligence (AI), while coping with the surge in adaptation of the
technology in other industries, into the triage management, documentation, scheduling, and revenue-cycle workflows, yet
most deployments remain as fragmented pilots that stall at the edge of production, exposing...
Manideep Dhar, Ritwik Singh, Sharat Chandra Kumar Manikonda· International Journal of Inn...· 0 citations
AI agents increasingly enter practitioner workflows through delegated, multi-step tasks, such as data analysis, document review, coding, and summarization. Existing governance debates tend to emphasize provider-level technical governance, which steers general model behavior, and policy, which defines the boundaries of...
Nick Hagar, Nick Diakopoulos· AI and Ethics· 0 citations
Large language models (LLMs) have evolved from standalone generative systems into agentic AI systems capable of planning, reasoning, tool use, and multi-agent collaboration. Enterprises are increasingly adopting AI agents to automate and orchestrate complex workflows, from IT operations to employee productivity. While...
Min Du, Anbang Xu, Jasmine Jaksic et al.· Proceedings of the 32nd ACM...· 0 citations
It is argued that agentic AI governance is four problems, not one, each with a mature governing science, and a five-level maturity model with a non-compensatory bottleneck-weighted index and assessment instrument operationalizes CASE as a scientific rather than process maturity model, grounded in production enterprise...
Srinivas Telukunta, Georgios Nektarios Lilis, Lucio Baron· 0 citations
The ORBIT (Operations Responses and Business Intelligence Toolkit) project was initiated to assess agentic AI for the upcoming ESnet 7 initiative and to address persistent operational pain points in the Network Operations Center (NOC) workflow. ESnet operators experience slow retrieval from siloed data sources, inciden...
BinHao Dong, Sukhada Gholba, Brooklin Gore et al.· arXiv.org· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.