Skip to main content

Abstract

The following chapter describes the procedure for implementing RPA in detail. We focus on topics and special features that are relevant to the initial implementation of RPA within an organisation. However, many aspects also apply to subsequent implementations. All topics are covered, from setting up a suitable project structure, process selection and adaptation, RPA-development, testing and implementation of automated processes, to ensuring the long-term operation of the RPA. Helpful overviews are available in many places, which can also be used as checklists for practical application.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 59.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 79.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    The criteria are not always divided into technical and business criteria. Willcocks et al. (2017, p. 22), for example, do not further divide the criteria they listed - degree of process standardisation, rule-basedness, process maturity and transaction volumes.

  2. 2.

    Lacity and Willcocks (2016, p. 31) place a surface at the height of the grey diagonal line in Fig. 5.5 and call it an “automatable belt". The processes located in this area are suitable for automation, as they provide the mentioned savings of at least three FTE per year. However, the belt selected there excludes high-volume and complex processes such as P2. For this reason, an extended presentation of the approach is introduced here.

  3. 3.

    The term was created by Eric Ries (see Ries 2011).

  4. 4.

    The subdivision used here differs from the classic subdivision of test types in the field of software testing. However, based on the latter, the technical tests can also be regarded as integration tests, which results in the familiar sequence of developer/functional test, integration test and acceptance test (see Pilorget 2012).

  5. 5.

    This requires, however, that artefact components that have been successfully tested once are no longer fully tested in the next iteration, but only regressively.

  6. 6.

    See on the roles in process management, for example Fischermanns (2015).

  7. 7.

    For a more in-depth introduction to the field of testing/test management, see for example Pilorget (2012).

References

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Mario Smeets .

Rights and permissions

Reprints and permissions

Copyright information

© 2021 Springer Fachmedien Wiesbaden GmbH, part of Springer Nature

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Smeets, M., Erhard, R., Kaußler, T. (2021). The Implementation of RPA. In: Robotic Process Automation (RPA) in the Financial Sector. Springer, Wiesbaden. https://doi.org/10.1007/978-3-658-32974-7_5

Download citation

Publish with us

Policies and ethics