Contents
EPO requirements
Prerequisites
Technical requirements
Functional requirements
Appendix A: List of EPO modules
Appendix B: Permission in EPO

EPO requirements

Prerequisites

Server access

• App server (to install API)
• Recommended specs: minimally 2 cores, and minimally 4GB ram, better 8GB, ideal 16GB,
• With Windows (server) (new enough to install .Net core) (2016 and newer)

1. IIS manager (https://www.howtogeek.com/112455/how-to-install-iis-8-on-windows-8/).
2. IIS server to be remotely accessible (RDP, Any Desk or Screen Connect)
3. SQL Server
4. SQL management studio (can also be on the SQL machine directly - in which case we need access to the SQL machine)

The sa user password

1. Firewall: open port 80 / 443, we will use port 443 (HTTPS) but we need port 80 to request the SSL certificate.

The application requires SSL for all its communication between the client and the API.
There are two approaches here, the client handles the SSL certificate itself, or we facilitate the SSL certificate. The last case, we do this using Let's Encrypt, and use auto-renewal. For this, we need a port 80 on the forwarded IP to go to the App server.

• Port forward on 443 to the app server
• IF, we need to provision SSL, then we need the port forward of port 80 as well.
• if you provision SSL, we'd need the domain name

Hairpin NAT configuration (aka NAT loopback)

• Setup hairpin NAT on the firewall / router

1. Site must be available over https (the domain name should be resolved)
   • If there is no domain name, then Asamco would assign a domain name otherwise it should be provided by the client

Technical requirements

1. STMP server for email notification
   1. We would require username, password, SSL port and SMTP domain
   2. If the client does not have STMP server, it should be coordinated with Asamco
2. Location in the server for storing the uploaded files from EPO
   1. If the location is not specified by the client, then default location on IIS server would be selected

Functional requirements

1. List of available modules in EPO
   1. PO, SO, RTS, Requisition, RFQ, etc (for list of available modules in EPO please check Appendix A: List of EPO modules).
2. List of users who are going to use the system
   1. For all the users in the list an email address should be provided
   2. The permission of the users should be specified in the list (for list of permission please check Appendix B: Permission in EPO)

3. List of the workflows (if the client is using workflows) and which step of the workflow the user is standing with their approval limit for example: Workflow name: finance WF

   Workflow steps	Approval users/group	Approval limit
   First step	Accountant group	1000

   
   

   Appendix A: List of EPO modules

   Purchase:
4. Purchase orders
5. Return to supplier
6. Expense claim
7. Supplier request
8. Payment batch

Sales:

1. Sales order
2. Credit note
3. Debit batch

Advance procurement:

1. RFQ (Request for quotation)
2. Requisition

Appendix B: Permission in EPO

There are default groups that are create in Sage when EPO is deployed,
Members of each group would have certain permissions and if they are added or removed from those groups those permission would be given or taken, the list of groups and their permissions is as follows:

Note: if you want customized permissions then you need to inform Asamco and a new group would be created with the specific permissions