{"resourceId":"la-county-isd-servicenow-itsm-work-order-e2-275","versions":[{"version":"external-30eafcc53f555f3645cfb7ef7ec286c7a686e9cf8da99f7587da372d1fa0f271","resource":{"id":"la-county-isd-servicenow-itsm-work-order-e2-275","title":"Board Notification of Intent to Execute Work Order E2-275 for ServiceNow ITSM Implementation","organization":"County of Los Angeles Internal Services Department","sector":"County government IT","geography":"Los Angeles County, California, U.S.","publishedAt":"2026-10-14","publicationDate":"2026-10-14","eventDate":"2026-10-14","sourceName":"County of Los Angeles Board of Supervisors","sourceLabel":"County procurement notice (PDF)","sourceUrl":"https://file.lacounty.gov/SDSInter/bos/bc/1219380_ISD-NoticeofIntenttoExecuteWOE2-275-ESMAServiceNowImplementation-October2026.pdf","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["governance-procurement","operating-model","infrastructure"],"finding":"LA County ISD notified its Board of intent to award a $1,990,000 work order to Accenture LLC to implement ServiceNow ITSM, ITOM (CSDM, CMDB, Discovery), Security Incident Response, Field Service Management, Employee Center and Performance Analytics, replacing a legacy ITSM platform that sunsets in December 2026. Six proposals were received; four met minimum requirements and were scored by an evaluation committee. Funding is pending Information Technology Investment Board approval. The notice does not mention AI.","sledRelevance":"Direct county-government procurement showing ServiceNow platform consolidation under a hard legacy-sunset deadline; establishes the data foundation (CMDB, knowledge, workflows) later AI features would depend on.","evidence":"Primary government document with scope, cost, selection process and timeline; no outcome data.","architectureImplications":"Scope includes CSDM/CMDB, Discovery, SSO and integrations with County systems, which are prerequisites for AI-driven ITSM.","governanceImplications":"Executive steering committee, requirements finalization dates, user stories with acceptance criteria and UAT are contractually required.","securityPrivacyImplications":"Includes Security Incident Response and role/permission design; specifics not described.","caveats":"Procurement notice, not an evaluation of results; evidence class reflects a government publication documenting a competitive evaluation; AI is not in scope; funding not yet approved; two weeks of post-go-live support is short for a platform of this breadth (interpretation).","streamIds":["servicenow","local-government"],"roles":{"sales":"Sales framing: legacy sunset deadlines drive ServiceNow consolidation in large counties, and AI is not yet in scope here. The opportunity is positioning AI readiness as a later phase built on the CMDB, knowledge and workflow foundation being implemented now. Respect that an implementation partner was competitively selected; any engagement should complement, not compete with, the awarded work.","engineering":"Engineering framing: the scope establishes CSDM, CMDB and Discovery, which determine the data quality later AI features depend on. Pre-sales should note that integration architecture and security roles are defined during planning. Recommend data-quality checkpoints for CMDB and knowledge content so future Now Assist or agent use cases are feasible. Limited AI applicability: the work order contains no AI scope, so AI proposals belong in a later phase.","delivery":"Delivery framing: the work order mandates a phased methodology, steering committee and UAT, with only two weeks of hypercare. With a December 2026 legacy sunset, schedule risk is significant. Delivery teams should plan cutover contingencies, knowledge migration and post-go-live support beyond the contracted window if the county requires it. Funding for this portion is still pending ITIB approval, which is an explicit dependency for start dates."},"roleDetails":{"sales":{"customerProblem":"A county must replace an end-of-life ITSM platform and consolidate fragmented service delivery.","stakeholders":["ISD Director","County CIO/ITIB","Board of Supervisors","Implementation partner"],"discoveryQuestions":["What AI capabilities are planned after the initial ITSM phase?","How will CMDB and knowledge quality be measured?"],"valueHypothesis":"A clean data foundation now could lower the cost of later AI use cases.","potentialEngagement":"A post-implementation AI readiness assessment once ITSM is live.","unsupportedClaims":["Any AI outcomes","Cost savings from consolidation","Funding certainty"]},"engineering":{"fit":"Platform foundation; AI not yet scoped.","architectureIntegration":"ITSM, ITOM, SIR and FSM with SSO and County system integrations.","prerequisites":["ITIB funding approval","Requirements finalization","Integration architecture"],"constraints":["December 2026 legacy sunset","Fixed scope with backlog management"],"security":"Security roles and permissions defined during solution design.","proofOfValue":["CMDB completeness and accuracy metrics after Discovery","Knowledge article coverage for top request types"]},"delivery":{"work":"Phased ServiceNow implementation with UAT, cutover and two-week hypercare.","dependencies":["Funding approval","County system owners","Legacy data migration"],"ownership":"LA County ISD.","skillsAdoption":"Staff adoption of Employee Center and Service Operations Workspace.","governanceCheckpoints":["Steering committee cadence","UAT sign-off","Closeout lessons learned"],"acceptanceCriteria":["Proposed: critical and high defects remediated before cutover, per the work order"],"risks":["Sunset deadline compression","Funding delay","Short hypercare"]}},"retrievedAt":"2026-10-29T22:28:03-05:00","enrichedAt":"2026-10-29T22:33:17-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Employee Center portal adoption; accessibility not addressed.","procurementImplications":"Shows use of a master agreement with competitive mini-solicitation and board notification above $500,000.","operatingModelImplications":"Moves ISD toward a single enterprise service platform with standardized processes.","sourceVerification":{"openedUrl":"https://file.lacounty.gov/SDSInter/bos/bc/1219380_ISD-NoticeofIntenttoExecuteWOE2-275-ESMAServiceNowImplementation-October2026.pdf","referenceExcerpt":"The current legacy ITSM platform will be sunset in December 2026 as the product has reached the end of its lifecycle","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}