Tierce maintenance applicative de la plateforme mes demarches en nouvelle-aquitaine (portail de gestion des subventions regionales et europeennes) et de ses composants

The contract timeline is as follows:

The framework agreement is concluded for a total duration of 48 months. The execution of services begins from the date of notification of the contract.

Key milestones and phases include:

• A launch meeting must be planned within a maximum of 30 working days from the notification of the framework agreement.
• The incoming transition phase will be planned by mutual agreement during this launch meeting.
• For services provided under purchase orders, the execution or delivery deadlines are specified in each purchase order and commence from the date of their notification.
• Purchase orders can be issued up to the last day of the framework agreement's validity, and their execution may extend beyond this period.
• Upon receiving a request for service costing, the company must provide a detailed financial proposal within 5 working days.

The core scope of work for this tender is the provision of Third-Party Application Maintenance (TMA) services for the MDNA (Mes Démarches en Nouvelle-Aquitaine) application, operated by the Nouvelle-Aquitaine Region.

The Statement of Work is structured as a composite framework agreement, comprising two main parts:

1. Ordinary Market Part (for fixed-price services at market launch):

• Launch meeting at the start of the framework agreement.
• Incoming transition services.
• Annual corrective maintenance and support services.

2. Framework Agreement with Purchase Orders Part (for services ordered as needed):

• TMA piloting services.
• Complementary services for evolutionary, adaptative, or preventive maintenance, including studies, parameterization, developments, functional support, and change management.
• Training services, both on-site at the Region and via video-conference.
• Outgoing reversibility services.

Core Deliverables include:

• Technical design document describing the solution architecture.
• Proposed architecture, compliance plan (if applicable), and proposed planning.
• A secure delivery space with usage documentation.
• Documentation of the version numbering method and a delivery slip model.
• Initial versions of installation and exploitation documents, packages, and scripts required for solution installation.
• Deployment plan.
• Maintenance scripts (for backup/restore, data replication, anonymization).
• Technical installation and exploitation procedures, and an update file.
• Reversibility plan and reports.
• All updated market deliverables, a knowledge base, a corrective maintenance base, and documentation of all norms, rules, and standards used by the contractor.
• Consolidated code documentation.