Formations aux usages et à la bureautique Microsoft

The contract duration is 48 months. The start date of the contract will be counted from either the date of notification of the public contract, the date of notification of the service order, or the execution start date specified in the contract if it is later than the notification date.

Key milestones and phases mentioned include:

• A launch meeting (Réunion de lancement) to be held once after notification for finalizing the PAQ, defining interlocutors, reporting, communication, and the start calendar.
• A national steering committee (COPIL national) which will meet quarterly during the first year and then semi-annually, unless otherwise required.
• Exceptional meetings (Réunion exceptionnelle) can be requested by the CAIH in cases of major incidents, transverse difficulties, regulatory changes, or significant changes to the offer.
• Local governance is structured according to the service type: short services include launch and closure, intermediate missions involve follow-up points, milestones, and action plans, while complex or critical projects entail COSUI, COPIL, financial reporting, and formal acceptance.
• Execution or delivery times for services are established by individual purchase orders, as per the CCAP stipulations.

The core scope of work for this tender involves accompanying adherents in defining and implementing their infrastructure and platform trajectories, encompassing Azure, Bleu, trusted cloud offers, and hybrid architectures. This includes consulting, architecture, preparation, migration, security, stabilization, and transfer services to ensure project success. The work also entails comparing scenarios across on-site, public, trusted, and hybrid clouds; designing technical foundations; securing migrations; organizing reversibility; and managing consumption, licenses, service levels, backup, and continuity.

The statement of work highlights several key deliverables:

• Architecture and Design Documentation: This includes general and detailed architecture files, regulatory and security qualification files, shared responsibility and RACI matrices, standards, policies, governance rules, landing zone design/evolution files, scripts, templates, and infrastructure as code elements.
• Migration and Implementation Plans: Deliverables cover migration plans, breakdown into waves, migration files, test plans, acceptance reports, cutover plans, and rollback plans.
• Operational and Support Documentation: This includes production and stabilization reports, exploitation files, administration procedures, supervision, backup, and restoration procedures.
• Continuity and Financial Management: Plans for continuity or recovery, FinOps dashboards, budgetary models, optimization reports, remediation plans, and reversibility plans are expected.
• Knowledge Transfer: Skills transfer files, mission reports, and elements enabling takeover by the adherent or a designated provider are crucial.
• Quality Assurance: A Quality Assurance Plan (PAQ) outlining governance and service commitments is required.
• Formalized Requirements: The process includes the reception, control, qualification, and enrichment of the Statement of Needs (FEB), with an anonymized example or model of a qualified FEB and a corresponding quote as deliverables.

It is explicitly stated that the offer does not integrate daily administration, continuous supervision, recurring support, or operational/security maintenance as a managed service.