{"resourceId":"maryland-doit-technical-acquisition-team-ai-partners-public-good-20261105","versions":[{"version":"external-775af38f633f6667917b772542aab94f6455728cecfe32bf2b985908a417e60d","resource":{"id":"maryland-doit-technical-acquisition-team-ai-partners-public-good-20261105","title":"Maryland DoIT launches a technical acquisition team and plans AI-assisted procurement intake under the Responsible AI Policy","organization":"Maryland Department of Information Technology (DoIT)","sector":"State government","geography":"Maryland, United States","publishedAt":"2026-11-05","publicationDate":"2026-11-05","eventDate":"2026-11-05","sourceName":"Maryland Department of Information Technology","sourceLabel":"DoIT press release","sourceUrl":"https://doit.maryland.gov/About-DoIT/Press/pages/DoIT-Unveils-Modernized-Strategic-IT-Acquisition-Strategy-and-the-State-Technical-Acquisition-Team-.aspx","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["governance-procurement","operating-model","developers-agents"],"finding":"On 5 November 2026 Maryland DoIT announced the state's first technical acquisition team and a strategic IT acquisition framework tied to the Procurement Reform Act of 2025. Agencies are to bring technology problems through a centralized \"single front door\" rather than naming a product first, so DoIT can test whether existing statewide systems already solve the need. FY2026 discovery found more than 1,700 technology requests representing over half a billion dollars in estimated demand, and only about 3% of IT buy-type and procurement-vehicle combinations have a purpose-built template, with some RFPs stretching to 118 pages. Nine DoIT review functions (including AI) are aligning standing compliance requirements. DoIT plans to partner with Partners for Public Good to use AI to streamline acquisition, subject to Maryland's Responsible AI Policy. The new process is in end-to-end user testing with seven agencies while DoIT recruits product managers, UX researchers, designers and engineers alongside procurement staff. No measured time or cost savings from the AI component are reported yet.","sledRelevance":"Direct U.S. state shared-services procurement reform with an explicit AI workstream under a Responsible AI Policy. Transferable to other states redesigning IT intake before GenAI platform buys; keep citizen 311/digital-service bots in Citizen Engagement unless the buy is enterprise acquisition tooling.","evidence":"DoIT press release dated 11/5/2026 states the technical acquisition team, single-front-door intake, FY2026 discovery figures (>1,700 requests; >$500M estimated demand; ~3% templated combinations; RFPs up to 118 pages), partnership plan with Partners for Public Good for AI in acquisition under the Responsible AI Policy, and seven-agency end-to-end user testing. StateScoop same-day reporting quotes CIO Katie Savage on problem-first discovery and corroborates the AI partnership and testing.","architectureImplications":"Centralized intake and discovery before buy; reuse of existing state stack preferred over one-off products; fit-for-purpose solicitation templates; any acquisition AI must sit inside statewide Responsible AI controls.","governanceImplications":"DoIT leads technical discovery and standards while DGS retains statutory procurement authority; standing multi-function compliance requirements (cyber, privacy, accessibility, data, AI, licensing, legal) are meant to cut agency paperwork.","securityPrivacyImplications":"AI acquisition tooling must adhere to the state's Responsible AI Policy; the press release does not detail data flows, logging or model-training opt-outs for the planned AI aids.","caveats":"AI for procurement is planned, not deployed with results. Discovery demand figures are estimates. Template and RFP-length statistics describe process pain, not proven savings from the new team. Recruiting is ongoing.","streamIds":["state-government"],"roles":{"sales":"Ask whether the state's IT intake still starts from a named product rather than a problem statement, and whether GenAI platform RFPs are proceeding without a discovery team that can reject duplicate buys. Position acquisition-process redesign and Responsible AI-compliant assistive tooling as prerequisites to multi-vendor frontier-model contracts. Offer a short assessment of intake volume, template coverage and where AI could draft or check solicitations without replacing statutory approvers. Do not claim Maryland has already cut cycle time or spend.","engineering":"Map a single-front-door intake service that routes agency problem statements into discovery, existing-contract reuse checks and new-buy paths. Integrate standing cyber, privacy, accessibility, data-governance and AI-policy gates as reusable requirement packs inside solicitation templates. If building AI aids for RFP drafting or requirement matching, keep them inside the state's approved identity, logging and Responsible AI controls, and design for human procurement/DGS sign-off. Prefer reuse of statewide platforms before net-new SKUs.","delivery":"Staff a joint team of procurement officers, product managers, UX researchers, designers and engineers; run problem-framing workshops with pilot agencies; publish shorter capability-focused templates; instrument cycle time from intake to award and reuse rate of existing systems. Gate any AI acquisition feature on Responsible AI Policy review and a documented human-approval step. Expand beyond the seven test agencies only after intake SLAs and override rates are measured."},"roleDetails":{"sales":{"customerProblem":"Agencies arrive with product-named IT requests, producing long RFPs, duplicate buys and weak validation of need versus existing state systems.","stakeholders":["State CIO / DoIT","Department of General Services procurement","Agency IT and program owners","State finance / budget"],"discoveryQuestions":["How many IT requests enter intake each year and what share name a product first?","What fraction of buy-type and vehicle combinations already have a template?","Who can stop a buy when an existing statewide system fits?"],"valueHypothesis":"Problem-first discovery plus tighter templates may cut duplicate spend and RFP length; AI aids are secondary and policy-bound.","potentialEngagement":"Intake diagnostic across a sample of recent buys, with a reuse-or-buy decision framework and Responsible AI checklist for any acquisition assistants.","unsupportedClaims":["Measured savings from Maryland's new team","Deployed AI procurement tool performance","Halved RFP length already achieved"]},"engineering":{"fit":"Workflow and knowledge tooling around intake, discovery and solicitation assembly, with optional AI drafting under policy controls.","architectureIntegration":"Central intake service; agency CRM/ticket handoff; links to existing statewide catalogs/contracts; template engine with embedded compliance packs.","prerequisites":["Authoritative inventory of statewide platforms and contracts","Agreed standing requirements from cyber/privacy/AI reviewers","Identity and audit logging for any AI assistant"],"constraints":["DGS retains statutory procurement authority","Responsible AI Policy constraints on AI aids","Legacy multi-document RFP practices"],"security":"Keep acquisition data in approved tenants; no uncontrolled model training on solicitation content; human approval before release.","proofOfValue":["Intake-to-award cycle time vs baseline","Share of requests resolved via existing stack","Template adoption and page-count reduction on new solicitations"]},"delivery":{"work":"Stand up the technical acquisition team, finish seven-agency testing, publish templates and optional AI aids with policy gates.","dependencies":["DGS partnership","Agency pilot participation","Recruiting for product/UX/engineering roles"],"ownership":"DoIT Technology Acquisitions with DGS OSP for procurement actions.","skillsAdoption":"Train agency requesters to file problem statements; train acquisition staff on discovery methods and AI-policy review.","governanceCheckpoints":["Responsible AI Policy review before any AI feature goes live","DGS approval path unchanged for awards","Expansion beyond pilot agencies gated on metrics"],"acceptanceCriteria":["Proposed: documented problem statement on every intake","Proposed: measured reuse rate and cycle-time baseline published"],"risks":["Agencies treat intake as new red tape and bypass it","AI drafting introduces inaccurate requirements","Recruiting delays leave process design without operators"]}},"retrievedAt":"2026-11-06T07:23:51.604396-06:00","enrichedAt":"2026-11-05T22:35:30-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Team mix explicitly includes UX researchers and designers so accessibility and usability inform buys; workforce impact of AI aids is not yet measured.","procurementImplications":"Shifts agency behavior from product-named RFPs to problem intake; shortens templates; embeds AI and other compliance gates; AI may later assist drafting under policy.","operatingModelImplications":"DoIT discovery plus DGS statutory procurement; product-management practices move into acquisition, not only digital-service teams.","sourceVerification":{"openedUrl":"https://doit.maryland.gov/About-DoIT/Press/pages/DoIT-Unveils-Modernized-Strategic-IT-Acquisition-Strategy-and-the-State-Technical-Acquisition-Team-.aspx","referenceExcerpt":"DoIT also plans to partner with Partners for Public Good to introduce the use of AI to further streamline the acquisition process.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}