-
Notifications
You must be signed in to change notification settings - Fork 1
/
ERP SCOPE - ZTel.html
58 lines (52 loc) · 5.31 KB
/
ERP SCOPE - ZTel.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>ERP SCOPE - ZTel</title>
<link rel="stylesheet" href="https://stackedit.io/style.css" />
</head>
<body class="stackedit">
<div class="stackedit__left">
<div class="stackedit__toc">
<ul>
<li><a href="#enterprise-resource-portal-usability-scope">Enterprise Resource Portal Usability Scope</a>
<ul>
<li><a href="#overview">Overview</a></li>
<li><a href="#technical-overview">Technical Overview</a></li>
</ul>
</li>
</ul>
</div>
</div>
<div class="stackedit__right">
<div class="stackedit__html">
<h1 id="enterprise-resource-portal-usability-scope">Enterprise Resource Portal Usability Scope</h1>
<h2 id="overview">Overview</h2>
<p>Z-Telco has chosen the Odoo platform to serve as its Enterprise Resource Portal and Source Of Truth. The Odoo platform will serve as a basis for all company business process and be extended as needed by 3rd party applications.</p>
<p>The following functions have been identified as a core need for Odoo and will be detailed in the sections below:</p>
<h3 id="crm">CRM</h3>
<p>The Company needs to keep detailed information about prospective, current, and past customers. The CRM should be the central data source for the “Customer Object” and all related Data. The Customer Object should exist in a one to many relationship with objects created in the Sales Pipeline, Projects Pipeline, and After Sales module.</p>
<h3 id="sales-pipeline">Sales Pipeline</h3>
<p>The Sales Pipeline should be handled entirely within a single module, supporting the transition of a contact from a Lead to a Customer, along with supporting Sales Order Data. This includes the creation of Opportunities during prospecting; the preparation, submission, and confirmation of formal quotations; the creation, submission, and confirmation of binding sales orders; the creation, submission, and confirmation of binding contract documentation.</p>
<h3 id="after-sales">After Sales</h3>
<p>The After Sales module should provide for the servicing of the customers account once they have completed the Sales Pipeline. This includes the handling of support tickets created via phone, email, or 3rd party integration.</p>
<h3 id="invoicing">Invoicing</h3>
<p>As The Company has spent significant resources on the development of its Zoura platform, it is not ideal at this time to use the Invoicing module to interact directly with customers. It is however needed to form a link between the Sales Pipeline and Zoura, as well as to make data generated from within Zoura accessable to Platform Users</p>
<h3 id="projects-pipeline">Projects Pipeline</h3>
<p>On completion of the Sales Pipeline, dependent on product sold, A project and associated tasks must be created to allow our Implementation teams the ability to move the customer forward from a signed contract to receiving service. The Projects Pipeline offers us a large opportunity for the automation of our existing business processes as with additional LOBs coming online we will be seeing customers completing their onboarding via Self Service. The Projects Pipeline is to serve as a record of all operations performed for a customer between the completion of the Sales Pipeline until the activation of the customers service.</p>
<h3 id="inventory">Inventory</h3>
<p>The company maintains physical inventory in a self-managed warehouse, as well as has the ability to handle physical inventory via 3PL partners. All saleable items purchased by The Company should be tracked in this Inventory System.</p>
<h3 id="hr">HR</h3>
<p>The company wishes to gain more control over its HR documentation, timesheets, and training. To facilitate this The Company will be utilizing the TimeSheets, Employee, Expense, Time-Off, and E-Learning modules to form the basis of a new Employee Management System.</p>
<h2 id="technical-overview">Technical Overview</h2>
<h3 id="planned-deployment">Planned Deployment:</h3>
<p>The ERP and associated tools should be deployed as an interconnected collection of docker images (a “stack”) on the multi-datacenter Internal Services Docker Swarm Cluster. The Odoo interface is to be decoupled from its database and be independently scalable. The Odoo installation should operate in a <strong>stateless</strong> manner as multiple replicas of the interface may be accessing the database at any given time.</p>
<p>In addition to Odoo and its corresponding database a standalone version of our API Automation Platform (N8N) is to be deployed alongside to facilitate chronological applications and serve as the connector between Odoo and other services.</p>
<p>Additional 3rd Party tools which extend the functionality of Odoo will be included in this stack as well such as AppSmith, ToolJet, Grafana, Grist, etc.</p>
<h3 id="current-deployment">Current Deployment:</h3>
<p>Currently the Odoo Platform is deployed to production as a single VM. This <strong>IS NOT</strong> sustainable for production use and should be rectified at the earliest point. However we understand that there are chronological based events currently built into the Odoo system which prevent scaling to a multi-node cluster. These items will need to be addressed and migrated to the API Automation Platform individually before Containerization and Scaling can occur.</p>
</div>
</div>
</body>
</html>