---
# System prepended metadata

title: Process Mapping Standards - RPA

---



# Best Practices for RPA Process Customization in Skore

## Introduction

To ensure the effectiveness and efficiency of our RPA (Robotic Process Automation) initiatives, it's critical to adhere to Skore's process standards. This document has been customized to conform to Skore's guidelines, ensuring that each process is purposeful, clear, and maintains a high standard before publishing.

## Skore Process Standards

### 1. Clearly Defined Process Purpose and Value

- **Process Purpose Field**: Every RPA process must have its purpose and value clearly defined in the Process Purpose field. This includes:
  - The goal of the process.
  - The primary customer or recipient of the process's outcomes.
  - The value that the process is expected to deliver to the customer.

### 2. Process Ownership

- **Assign a Process Owner**: Each process must be assigned an Owner who is responsible for:
  - Ongoing monitoring of the process.
  - Continuous improvement efforts.
  - Being the point of contact for any process-related queries.

### 3. What Boxes: Verb + Noun Descriptions

- **Action Descriptions**: What Boxes must describe activities with action-oriented labels using the Verb + Noun format. For example:
  - "Verify Account" instead of "Account Verification".
  - "Process Payment" instead of "Payment Processing".

### 4. Why Box: Defining Inputs and Outputs for What Boxes

- **Context through Inputs and Outputs**: Each What Box must have at least one input and one output to:
  - Indicate the start and end of an activity or input and output of an activity.
  - Describe handovers between different teams or systems.
  - Provide context for the process flow.

Example Structure:

`What Box: Categorize Email`
`Input: Email queued for categorization`
`Output: Categorized email with priority email`
`


### 5. Input and Output Descriptions

- **States or Tangibles**: Inputs and outputs should be described as states, items, or measurable entities, not actions. They should:
  - Reflect the prerequisites for starting a task (Input).
  - Indicate the deliverables or outcomes of completing a task (Output).
  - Never use a verb and noun format.



## Additional Best Practices

- **Documentation**: Ensure all process maps and RPA documentation are thorough and accessible for team reference.
- **Training**: Provide regular training sessions on Skore and RPA best practices to maintain high standards.
- **Review and Update**: Regularly review RPA processes to ensure they remain relevant and effective.

## Conclusion

By integrating Skore's process standards into our RPA customization, we establish a robust foundation for automation that is clear, monitored, and continually improved, driving value for the business and its customers.



------

------


# Best Practices for RPA SDLC with Skore

## Introduction

This document provides best practices for the customization and implementation of RPA solutions using the Skore platform. It aims to guide our team through the process of designing, deploying, and maintaining RPA workflows efficiently.

## 1. Understanding Business Requirements

- **Engage with Stakeholders**: Regularly consult with stakeholders to understand the business requirements and the expected outcomes of the RPA implementation.
- **Define Clear Objectives**: Establish clear, measurable objectives for what the RPA implementation is expected to achieve.

## 2. Process Selection and Mapping

- **Select Suitable Processes**: Identify and select processes that are high-volume, repetitive, and rule-based for RPA automation.
- **Comprehensive Process Mapping**: Utilize Skore's mapping tools to document every step of the selected processes.

## 3. RPA Design and Development

- **Modularity**: Design RPA bots that perform specific tasks which can be reused across different processes.
- **Scalability**: Ensure that the RPA solution is scalable to accommodate increased loads or process changes.
- **Error Handling**: Implement robust error handling and logging mechanisms within RPA workflows.
- **Data Privacy**: Design workflows with data privacy in mind, adhering to relevant data protection regulations.

## 4. Integration

- **API Usage**: Use APIs for integration with other systems where possible to reduce maintenance overhead.
- **System Compatibility**: Verify that the RPA bots are compatible with all systems they interact with.

## 5. Testing

- **Develop Test Plans**: Create detailed test plans covering all possible scenarios, including edge cases.
- **Continuous Testing**: Adopt a continuous testing approach to catch issues early in the development cycle.

## 6. Deployment

- **Staged Rollout**: Deploy RPA solutions in stages, starting with a pilot phase to gather feedback and make necessary adjustments.
- **Monitoring**: Set up monitoring








# Process Mapping Standards - RPA 

## Table of Contents

1. [Process](#Process)
2. [Componets](#Componets)


## Process 
 
*    **Purpose**: Process shold have valide explanation of its purpose. The purpose should agree with the process owner. 
*    **Value:** 
*    **Name:** Reference number_short description as in the other RPA documents. 
 

---

## Component 
*    **What Box:** Its an activity box in a process. They are actions so should always be stated as a Verb + Noun. The action is being done to something. Try to limit the what box numbers of 6. to acheive this you may need to group sub activities and that can be maximum number of 10. 

*    **Why Box:** It represents the inputs and outputs. Describe the main input and the output to the process. Adher the naming convention for the 	I/O.  Each activity should have at least one I/O. Input and outputs are states or tangible/ measurable things we can check whether they exist to know when it's time to move to the next step in the process. 
*    **Attachements:** Describe what it does and all the menaingful details of the process. Background of activities outputs and inputs may be nesessary to help and read and understanding the map process. This amount of detail should be added in the attachement so that the diagram will be clean and readable. 

------
	
*    **Sub Activity:** The sub activities are represented by a square and arrow inside it on the main activity page. The activities, inputs and outputs follow the agreed standards mentioned about. 
Explain the activity and number activities that we can use. 
Explain the naming convention for the activities. 


----
