{"resourceId":"fsu-jaggaer-jai-procurement-assistant-20261001","versions":[{"version":"external-411fc252cdad6049f518eea6fc174fd66a309aec55fe192cfaa828e3b139cc57","resource":{"id":"fsu-jaggaer-jai-procurement-assistant-20261001","title":"Florida State University launches JAGGAER AI assistant in SpearMart procurement, telling users to verify answers before business decisions","organization":"Florida State University Procurement Services / JAGGAER","sector":"Public research university / procurement and contract management","geography":"United States (Florida)","publishedAt":"October 1, 2026","publicationDate":"2026-10-01","eventDate":"2026-10-01","sourceName":"FSU Procurement Services","sourceLabel":"Institutional (operator) service announcement","sourceUrl":"https://procurement.fsu.edu/article/jai-jaggaer-ai-launches-in-spearmart","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["knowledge-work","governance-procurement","developers-agents"],"finding":"FSU Procurement Services launched JAI (JAGGAER AI) in SpearMart effective Oct. 1, 2026. It is an embedded assistant that answers process questions, gives workflow guidance and helps users locate requisition and contract information, including requisitions awaiting the user's approval. Users are told to be specific and to verify information before relying on it for business decisions. Technical issues including JAI responses go to a SpearMart support address; policy questions go to Procurement.","sledRelevance":"A concrete example of vendor-embedded AI switched on inside a public university's eprocurement and contract system, with a verification caution and a support route for bad answers but no published controls or measures.","evidence":"Opened the FSU Procurement Services announcement dated Oct. 1, 2026.","architectureImplications":"Assistant is embedded in the JAGGAER eprocurement suite and reaches requisition, approval and contract-management data in the user's context.","governanceImplications":"Responsibility for accuracy is placed on users ('verify information'); there is no stated review of answer quality, data scope or approval-workflow safeguards.","securityPrivacyImplications":"Access to contract and requisition data should follow existing role permissions; the announcement does not say how permissions are enforced or what data the vendor model processes.","caveats":"Brief launch notice; no usage, accuracy or time-saving data; no description of data handling or permissions. Vendor feature, institution announcement.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: embedded procurement AI arrives with the platform, not a project. FSU switched on JAGGAER's assistant in its eprocurement and contract system with a simple warning to verify answers. Procurement and finance leaders elsewhere will see similar default features. A bounded readiness check on data scope, permissions and answer accuracy is credible; claims that the assistant speeds purchasing or reduces errors are not supported by this notice.","engineering":"Engineering framing: confirm the assistant respects existing roles. Fit is any campus on JAGGAER or similar suites enabling embedded assistants. Engineers should verify that answers about requisitions and contracts respect user permissions, identify what data reaches the vendor model, and confirm logging. Proof of value should test policy and workflow answers against the procurement manual and check that approval queues shown match the user's actual authority.","delivery":"Delivery framing: a launch notice is not a control. Delivery should define how wrong answers are reported and corrected, sample questions monthly against policy, and track whether users still route policy questions to Procurement. Owners are procurement services with the eprocurement system team. Risks include users acting on outdated or wrong policy answers, exposure of contract data beyond role, and unmeasured value."},"roleDetails":{"sales":{"customerProblem":"Procurement users struggle to navigate requisition and contract workflows, and vendors now embed AI assistants by default.","stakeholders":["Director of procurement services","Controller","Eprocurement system administrator","Information security"],"discoveryQuestions":["What data can the embedded assistant read?","How are wrong answers reported and corrected?","Are answers checked against current procurement policy?","What usage and accuracy will be measured?"],"valueHypothesis":"Interpretation: an embedded assistant may reduce routine help requests if answers are accurate and permission-aware; this is unmeasured.","potentialEngagement":"A bounded readiness and accuracy check of the embedded assistant covering permissions, data scope and a policy-answer test set.","unsupportedClaims":["No usage or accuracy data is reported.","No time savings are claimed or measured.","Data handling is not described."]},"engineering":{"fit":"Campuses on eprocurement suites that add embedded AI assistants.","architectureIntegration":"Assistant runs inside the procurement suite with access to requisitions, approvals and contract records under the user's session.","prerequisites":["Vendor documentation of data flows","Role-permission mapping","Current procurement policy content"],"constraints":["State public-records and procurement rules","Vendor-controlled model","Limited institution visibility into logs"],"security":"Verify permission enforcement on contract and approval data and obtain vendor terms on model data use and retention.","proofOfValue":["Test 50 policy and workflow questions against the procurement manual","Confirm users only see approvals within their authority","Review vendor logs for a sample of sessions"]},"delivery":{"work":"Set feedback, accuracy sampling and usage tracking for the embedded procurement assistant.","dependencies":["JAGGAER configuration and logs","Procurement policy owners","Support desk"],"ownership":"Procurement Services, with the eprocurement system team for technical issues.","skillsAdoption":"Users need guidance on effective questions and when to confirm with Procurement.","governanceCheckpoints":["Data-use review of vendor terms","Monthly answer-accuracy sample","Review before expanding to contract drafting"],"acceptanceCriteria":["Proposed: at least 90% of sampled policy answers correct","Proposed: zero instances of data shown beyond user role in testing","Proposed: usage and help-ticket trends reported after one term"],"risks":["Wrong policy answers acted on","Contract data exposure beyond role","Unmeasured value"]}},"retrievedAt":"2026-10-06T21:58:26-05:00","enrichedAt":"2026-10-06T21:58:26-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Could shift routine questions away from procurement staff; no staffing effects stated.","procurementImplications":"Embedded AI in existing platform contracts may arrive without separate procurement review; institutions should require data-use terms for such features.","operatingModelImplications":"Splits support between system technical support and procurement business questions, including a route for faulty AI responses.","sourceVerification":{"openedUrl":"https://procurement.fsu.edu/article/jai-jaggaer-ai-launches-in-spearmart","referenceExcerpt":"Verify information before relying on it for business decisions.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}