Skip to content

Instantly share code, notes, and snippets.

@punchouty
Last active September 30, 2021 19:49
Show Gist options
  • Save punchouty/8abb78c696bd4bbfe8858025f4944e3e to your computer and use it in GitHub Desktop.
Save punchouty/8abb78c696bd4bbfe8858025f4944e3e to your computer and use it in GitHub Desktop.

Questions

How will you manage deployment?

Earlier assumptions was that client already has UiPath infrastructure and resources to support new processes. Existing team can manage additional deployment.

If that is not a case there will be additional effort to do everything from ground up.

  1. Two new environment need to setup on aws/azure/google cloud - 4 weeks (stage and prod) (assume all licences are in place)
  2. Release, deployment and testing process setup with focus on devops (CI/CD pipeline) - 2 weeks

CI/CD Pipeline

Azure Devops Example

Plan for maintenance, support?

It will be driven by SLA. Following are the possibilities.

  1. If customer can manage 48 hours of downtime, 20 hours per month of resource time will be enough for maintenance and support of 4 processes.
  2. If issue need to be resolved with in 12-48 hours, 40 hours per month of time will be needed for support.
  3. If SLA are of order of less than 8 hours we need to assign a regular resource with 160 hours of monthly commitment.

Training/Documentation

The bots executions are simple. We will create basic usage documentation with in above deployment budget.

How will the bots handle changes to layout of websites/apps.

If there are no fundamental changes in layout, changes will be covered as part of maintenance and support. If changes are big we need to add additional 24-72 hours depending upon changes (Case 1 ad 2 above).

Important Notes

We have taken a lot of assumptions for scope and requirements. It is better to setup call with end client to understand exact requirements.

Otherwise, to handle this ambiguity, assign a resource for 8 weeks. He/She will take care of all above tasks. And depending upon selected SLA above, use same resource for maintenance and support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment