A structured and coordinated approach to AI systems deployment is essential to the effective integration of these systems into various parliamentary applications and workflows. These patterns of deployment reinforce good practices, helping to ensure that AI deployments are scalable, robust and maintainable. For further discussion of software deployment patterns, refer to the sub-guideline Systems development: Deployment patterns.
Parliament’s deployment strategy will depend on the degree of task automation. The various options are discussed below:
- Human-only: In this case, there is no automation. The task is carried out manually by users without AI support.
- AI assistance: The task is performed mainly by users, possibly with assistance and support from the AI system.
- Partial automation: The task is performed mainly by the AI system, which produces suggestions for users.
- Full automation: The task is performed entirely by the AI system, without human intervention.
Both AI assistance and partial automation are examples of “human-in-the-loop” deployments (for further discussion of this topic, refer to the sub-guideline Ethical principles: Human autonomy and oversight).
Deployment cases
The most common deployment cases and their characteristics are detailed below:
- New product or feature: In this case, a new AI-based product or feature is introduced.
- Partial task automation: In this case, a task was previously done manually and an AI algorithm is introduced to either automate this task or assist the user.
- Replacement of a previous AI system: In this case, a task was carried out via a previous implementation of an AI system, and another AI system is introduced to replace the previous one with a view to improving quality and/or execution time.
In the above deployment cases, parliament should consider the following two basic aspects:
- Gradually increase traffic with monitoring. It is advisable to avoid sending a lot of production traffic to an algorithm that is still learning and is not yet fully proven. It may be better to send it only a small amount of traffic, monitor it and then progressively ramp up the amount of traffic.
- Ensure there is a possibility to roll back. It is advisable to have a contingency plan in place to revert back to the previous, stable configuration in case the new algorithm does not work as expected.