Table of Contents

Executive Summary.....................................................................................................................................5
1. Introduction.........................................................................................................................................6
1.1 Management / Executive Summary.............................................................................................7
1.2 Document Audience....................................................................................................................7
1.3 Functional Scope of Work............................................................................................................8
.................................................................................................................................................................8
1.4 Business Objectives.....................................................................................................................9
2. CorporateStack Solution modules.....................................................................................................10
3. Telecom Egypt Organization Structure..............................................................................................11
3.1 Company Details........................................................................................................................11
3.1.1 Details....................................................................................................................................11
In the beginning, all the details related to the company are entered in this screen as follows:.........................11
3.2 Purchasing Department Organization Chart..............................................................................15
3.3 Project Data Master – Digital Import Tool.................................................................................15
4. Business Process & Solution Design...................................................................................................17
4.1 Solution Components................................................................................................................17
...............................................................................................................................................................17
4.2 Purchase Request......................................................................................................................18
4.2.1 Business Process Description.................................................................................................18
...............................................................................................................................................................18
4.2.2 PR - Business Process Description..........................................................................................19
4.2.3 Process Steps Details Requirements......................................................................................20
4.2.4 PR - Form Interface Requirements.............................................................................................34
After completing the previous settings, the data is prepared for transactions. Next, we will work on
the purchasing cycle..............................................................................................................................34
1- Purchase Request list:....................................................................................................................34
In this screen, all purchase quotations and their statuses will be displayed. You can search using
various filters such as product name, supplier, and warehouse , etc....................................................34
 Here are the statuses for a Purchase Request:..............................................................................34
1. Pending: The request has been submitted but not yet reviewed or acted upon...........................34
2. Approved: The request has been reviewed and approved for further action................................34
 3. Partially Ordered: The request has been partially fulfilled; some items have been ordered while
others are still pending..........................................................................................................................34
4. Fully Ordered: All items in the request have been ordered...........................................................34
5. Declined: The request has been reviewed and rejected................................................................34
6. Cancelled: The request has been cancelled and will not be processed.........................................34
7. All: Displays requests with any of the above statuses...................................................................34
Through the system, we can customize the terminology for purchase quotation statuses to align with
the company’s specific needs and terminology.....................................................................................34
2- Create Purchase Request:..............................................................................................................35
In the first step, we will create a Purchase Quotation, with all fields highlighted in different colors.
These fields will be worked on, and the color-coding is used to illustrate the overall process, which will
be explained in more detail later...........................................................................................................35
a. Main..............................................................................................................................................35
b. Items..............................................................................................................................................36
...............................................................................................................................................................36
1. Description: Provides a detailed explanation of the product or item being ordered, including its
features or specifications......................................................................................................................36
2. Select Product or Type Item Description: The option to choose a specific product or type of item
and provide a description for it.............................................................................................................36
3. Budget Item: The specific item or category within the budget that the purchase will impact......36
4. Unit: The unit of measurement for the item (e.g., pieces, kilograms, liters).................................36
5. Ordering Unit: The unit in which the product is ordered, which may differ from the unit used for
budgeting or inventory..........................................................................................................................36
6. Quantity: The amount of the product or item being ordered........................................................36
c. Documents :...................................................................................................................................37
Refers to the option to attach relevant files or documents related to the purchase, such as contracts,
invoices, or specifications......................................................................................................................37
...............................................................................................................................................................37
 Attach: The button or link used to upload or attach a file.............................................................37
4.2.5 Memo - Business Process Description...................................................................................39
4.2.6 Memo - Process Steps Details Requirements........................................................................40
2. Create Memo.................................................................................................................................41
2.1 Process Step.......................................................................................................................................42
2.3 information source from and nature...............................................................................................43
4.2.7 Letter of Internal........................................................................................................................44
4.2.8 Purchase order..........................................................................................................................45
4.2.9 Purchase Invoice........................................................................................................................51
Reporting...................................................................................................................................................53
1- Purchase Request Status...............................................................................................................53
Workflow...................................................................................................................................................56
3. Project Implementation Approach....................................................................................................59
a. Implementation Flow....................................................................................................................60
b. The Project Kick-off........................................................................................................................61
c. System Analysis.............................................................................................................................61
d. Customization Design....................................................................................................................63
e. Integration Design.........................................................................................................................64
f. Internal Quality Control (QC).........................................................................................................64
g. Training - Empowering Users for Success......................................................................................65
h. UAT................................................................................................................................................67
i. Go Live Preparation.......................................................................................................................68
j. Go Live – The Launch into Action...................................................................................................69
k. Post Go Live – The Launch into Action...........................................................................................70
4. The Project Requirements.................................................................................................................70
a. The Delivery...................................................................................................................................70
b. The Project Team...........................................................................................................................71
c. CorporateStack Direct / Indirect Facing.........................................................................................72
...............................................................................................................................................................72
d. The Project Documentation...........................................................................................................73
e. The Project Requirements.............................................................................................................74
f. Telecom Egypt Team Requirements..............................................................................................75
i. Resource Allocation.......................................................................................................................75
g. High-Level Project Plan..................................................................................................................76
5. The Annexes......................................................................................................................................76
a. Building an ERP System for Telecom Egypt's Procurement 2.........................................................76
b. High-Level Project Plan MS Excel Sheet.........................................................................................76

Figure 1: CorporateStack SCM.....................................................................................................................8

Figure 2: SCM Modules..............................................................................................................................10
Figure 7: PR Flow Chart.............................................................................................................................19
Figure 8: Memo Flow.................................................................................................................................39
Figure 9: Implementation Approach..........................................................................................................59
Figure 10: Integration Flow........................................................................................................................65
Figure 11: CS Team....................................................................................................................................71
Figure 12: High-Level Architecture............................................................................................................74
Executive Summary
This proposal outlines the plan for the implementation of an Enterprise Resource Planning (ERP) system
for the procurement department at Telecom Egypt. The primary objectives of this implementation are
to enhance operational efficiency, improve accuracy in procurement processes, streamline workflows,
and strengthen supplier relationship management. By integrating procurement with other business
functions, the ERP system aims to ensure compliance with regulatory requirements and facilitate
seamless operations across departments.

The ERP system is expected to deliver significant benefits, including increased transparency, reduced
operational costs, better data management, and improved decision-making capabilities. It will address
current challenges in procurement processes, such as manual data entry errors, inefficient workflows,
and difficulties in supplier management. By automating and optimizing procurement activities, the ERP
system will enable Telecom Egypt to achieve higher productivity and better resource utilization.

This project will be executed in several phases, starting with a detailed requirement analysis, followed
by system design, development, customization, testing, and quality assurance. The final stages will
involve deployment, user training, and change management to ensure a smooth transition and
successful adoption of the new system. A comprehensive risk management strategy and quality control
measures will be in place to mitigate potential risks and ensure project success.

The implementation timeline includes key milestones and deliverables, with a clear roadmap for
achieving project goals. Resource allocation is planned meticulously, with a dedicated project team
possessing the necessary skills and expertise. The financial plan provides a detailed budget breakdown,
covering software licensing, development, training, and infrastructure costs, along with a return on
investment (ROI) analysis to demonstrate the project's financial viability.

Stakeholder engagement and communication will be prioritized to ensure transparency and regular
updates throughout the project lifecycle. Potential risks will be assessed, and mitigation strategies will
be developed to address any challenges that may arise. Success metrics and key performance indicators
(KPIs) will be established to evaluate the project's impact and ensure continuous improvement.

In conclusion, the proposed ERP system for procurement at Telecom Egypt is a strategic initiative
designed to drive efficiency, improve accuracy, and enhance overall operational performance. We seek
your approval and support to proceed with this critical project, which promises substantial benefits and
a strong return on investment for Telecom Egypt
 1. Introduction
Telecom Egypt, a leading telecommunications company in Egypt, currently manages its procurement
processes through a paper-based system. This traditional approach includes obtaining offers, technical
and financial recommendations, negotiations with suppliers, and final approval of the purchase process.
This manual process is not only time-consuming but also prone to errors and lacks real-time visibility
into procurement activities.

The ERP system is expected to deliver significant benefits, including increased transparency, reduced
operational costs, better data management, and improved decision-making capabilities. It will address
current challenges in procurement processes, such as manual data entry errors, inefficient workflows,
and difficulties in supplier management. By automating and optimizing procurement activities, the ERP
system will enable Telecom Egypt to achieve higher productivity and better resource utilization.

This project will be executed in several phases, starting with a detailed requirement analysis, followed
by system design, development, customization, testing, and quality assurance. The final stages will
involve deployment, user training, and change management to ensure a smooth transition and
successful adoption of the new system. A comprehensive risk management strategy and quality control
measures will be in place to mitigate potential risks and ensure project success.

The implementation timeline includes key milestones and deliverables, with a clear roadmap for
achieving project goals. Resource allocation is planned meticulously, with a dedicated project team
possessing the necessary skills and expertise. The financial plan provides a detailed budget breakdown,
covering software licensing, development, training, and infrastructure costs, along with a return on
investment (ROI) analysis to demonstrate the project's financial viability.

Stakeholder engagement and communication will be prioritized to ensure transparency and regular
updates throughout the project lifecycle. Potential risks will be assessed, and mitigation strategies will
be developed to address any challenges that may arise. Success metrics and key performance indicators
(KPIs) will be established to evaluate the project's impact and ensure continuous improvement.

In conclusion, the proposed ERP system for procurement at Telecom Egypt is a strategic initiative
designed to drive efficiency, improve accuracy, and enhance overall operational performance. We seek
your approval and support to proceed with this critical project, which promises substantial benefits and
a strong return on investment for Telecom Egypt.
1.1 Management / Executive Summary
This Document will document how the business processes will be mapped in CorporateStack; we have
managed to design the processes as the standard available best practice scenarios.

1.2 Document Audience

This document is primarily aimed at customers and end-users who will interact directly with the
CorporateStack Supply Chain Management (SCM) Product. Specifically

1. The Customer - Telecom Egypt

a. Decision-makers and stakeholders within organizations looking to implement or
upgrade their supply chain management systems.
b. Individuals responsible for evaluating and selecting SCM software solutions that align
with their organization’s strategic goals and operational requirements.
c. Executives and managers seeking to understand how CorporateStack SCM can
improve efficiency, reduce costs, and enhance supply chain visibility and control.
2. The End User – The system users
a. Requesting Departments: Teams from various departments who will use the SCM
software to submit and track purchase requests, ensuring their procurement needs
are met efficiently.
b. Purchasing Department: The procurement staff responsible for reviewing,
processing, and approving purchase requests, managing supplier interactions, and
generating purchase orders.
c. Top Management: Executives and decision-makers who will use the SCM system for
high-level oversight, reviewing reports, and approving large purchases to ensure
strategic alignment with business objectives.
1.3 Functional Scope of Work
CorporateStack Supply Chain Management (SCM) Product

CorporateStack SCM
1.4 Business Objectives
The primary business objectives or benefits expected out of this project are listed below but not
limited to,

 Digitization of Procurement Processes: Transition from paper-based to digital

procurement processes to eliminate manual handling of documents and
streamline workflows.
 Improved Efficiency and Accuracy: Enhance efficiency by automating
procurement tasks such as purchase requisitions, purchase orders, supplier
management, and approvals. Improve accuracy by reducing manual data entry
and errors.
 Enhanced Reporting and Analytics: Implement robust reporting and analytics
capabilities to provide real-time insights into procurement performance, supplier
evaluation, and expenditure analysis.
 Streamlined Supplier Management: Centralize supplier information, track
supplier performance, and streamline the supplier selection process.
 Compliance and Audit Readiness: Ensure compliance with regulatory
requirements and internal policies. Maintain comprehensive audit trails for all
procurement activities.
 2. CorporateStack Solution modules
CorporateStack’s All-in-One SCM solution stands as a beacon of innovation, meticulously
crafted to empower WE Telecom Egypt in its pursuit of operational excellence and customer
satisfaction. Our comprehensive suite of modules covers essential aspects of WE Telecom
Egypt’s business operations, including sourcing commodities directly from growers and
producers through an extensive supplier network to ensure unmatched quality and consistency.

Our solution further enhances WE Telecom Egypt’s logistics capabilities with bespoke solutions
tailored to meet the unique needs of their clients. Each module within CorporateStack’s SCM
solution is designed for seamless integration and operational efficiency, aligning perfectly with
WE Telecom Egypt’s commitment to excellence in sourcing and logistics management.

By leveraging CorporateStack’s SCM solution, WE Telecom Egypt can optimize their

procurement processes, streamline operations, and achieve greater agility in responding to
market demands. We are dedicated to supporting WE Telecom Egypt in achieving their goals
and driving sustainable growth in their industry. purchase request

Figure 1: SCM Modules

 3. Telecom Egypt Organization Structure
This section will introduce the Organizational Structure Units, its purpose and major
characteristics of the business.

3.1 Company Details

3.1.1 Details
In the beginning, all the details related to the company are entered in this screen as follows:

1- The branch name, which carries the name of company .

2- Branch Alt Name : The alternative name for the company.

3- The branch code, which carries the company's code.

4- Branch Type: This field is used to input whether the company is a single entity or multiple
separate entities. It includes two options for selection.

5- Branch currency : The company's currency, which is used as the primary currency in all
transactions on the system, unless another currency is specified for a particular transaction.
6- VAT: which represents the tax rate imposed on the company.

7- TAX Registration No. (TRN): which represents the company's tax registration number.

8- Trade License Name: which represents the name of the company's trade license.

9- Trade License Number: which represents the company's license number.

10- Country, Governate, Region/City Street Building , Geo Location : the input fields for the
company's address details .

3.1.2 Sub-branch

From here, we can divide the company into multiple branches, and it will be possible to
add details for each branch externally.
 After saving and exiting, we can modify and add details such as the code, header, and footer for
each sub-branch, as shown in the images below.

 Active and Inactive refer to the number of active and inactive employees in the

company.

 From here, we can modify the details for each sub-branch individually, including the
code.
 From here, we can customize different headers and footers for each branch of the company.

3.1.3 Letterhead & Stamp

Here, we place the header, footer, and logo of the primary company.
  It is important to note that the header and footer are used in all printing related to
transactions in the system.

3.2 Purchasing Department Organization Chart

The purchasing organization, as the primary entity utilizing the system, is responsible for
creating and issuing purchase requests, generating memos, and ultimately issuing purchase
orders to the selected supplier in accordance with the established workflow and approval
cycle.
Procurement Team Structure Description
360 Users will use the system The organizational chart, including
department structure, reporting lines, and
titles, will be gathered by the
CorporateStack team during the
implementation phase.

3.3 Project Data Master – Digital Import Tool

Master data sheets for the organization, teams, Suppliers and other records will be stored
centrally in the database for cross-application use, helping to eliminate data redundancy. In
the SCM system, some master data sheets will be provided by the CorporateStack team,
collected from Telecom Egypt, and additional data will be created within the SCM during the
project implementation phase.
3.3.1 Master List sheets
 Employee Master Sheet
 List of Suppliers
 List of products
3.3.2 Front End – Digital Import Tool
In the import tool using Excel sheets, we can add all the data involved in
transactions, such as suppliers, products, and employees.
  The template is downloaded, filled out, and then uploaded on this screen. This is the
same process for other imports, and it is similar across most systems in the same way.

4. Business Process & Solution Design

4.1 Solution Components
The full-fledge solution covers all the required modules in one single platform. All modules are fully
integrated and can be extended in future for further development and enhancements.
 4.2 Purchase Request
4.2.1 Business Process Description
A purchase memo serves as a central repository to manage purchase requests received from various
departments within Telecom Egypt. It organizes activities related to request creation with well-defined
characteristics to guide the request through the system. This includes attaching and supplementing the
request with additional information required by the purchasing department's top management to
secure necessary approvals. Once approved, the memo proceeds through the contractual process,
ultimately leading to the issuance of a purchase order to the selected suppliers .

During gap analysis sessions between the CorporateStack and Telecom Egypt teams, we illustrated the
workflow for each section, categorized into target groups.

The scope of work includes significant customization of the purchase request forms and screens, with
detailed requirements gathered by both the CorporateStack and Telecom Egypt teams.

Additionally, the scope involves developing the purchase memo from scratch, as it is not typically part of
traditional purchasing modules. The design and required information for the memo have been carefully
collected, and the necessary fields and functionality are outlined below.

4.2.2 PR - Business Process Description

 The purchase request process initiates the procurement cycle, capturing the need for goods or
services from various departments within the organization. Key features of the purchase request
process include.

PR Flow Chart

4.2.3 Process Steps Details Requirements

 Before starting the purchasing cycle, we will create the products that will be worked on.

First, the category must be created because it is mandatory for creating a new product.

1- product category:
A. product category: Creating the product category is important not only because it helps in
organizing and categorizing products in a specific way, but also because it plays a key role in
accounting, as it is used for managing sales, purchases, and cost calculation.

- The name, code, and the accounts used are entered for the category.

B. We can create sub-categories from the main category to be part of the parent category.
Additionally, a key feature is that different accounts can be assigned to each sub-category
 individually. If no accounts are specified for a sub-category, it will inherit the accounts from
the main category.

 We can create an unlimited number of sub-categories and enter their names, codes, specific
accounts, and units of measure.

 From here, we can search for both categories and sub-categories.

2- Create Products :
A. Product list
 In the product list, we can view all the products available. From this screen, we can
search using various criteria such as product name, supplier, category, and brand.

A. From the export option, we can extract all the products available in the system in various
formats such as Excel, Word, and PDF.

B. From Sort , we can sort the products by name, date, or price.

B. New product:
When creating a new product, the product information is entered.

1- Main :

A. Product Name represents the name of the product.

B. Product No (SKU) specifies the product number.

C. Short Description provides a brief summary of the product.

D. Branch indicates the branch where this product will be located, which is set up in the company
settings.

E. Ordering Unit refers to the unit of measurement used for ordering the product. It
defines the standard quantity in which the product is purchased or ordered, such as
pieces, boxes, liters, or kilograms.
F. Dispensing Unit refers to the unit of measurement used when the product is dispensed or sold
to the customer. It might be different from the ordering unit and represents the quantity in
which the product is sold or given to the customer, such as per piece, per pack, or per bottle.
G. Production Unit is the unit of measurement used in the manufacturing or production process. It
represents how the product is measured or handled during production, which could be different
from the ordering or dispensing units. For example, it might be in kilograms, liters, or meters,
depending on the nature of the product and the production process.
H. Tax Type refers to the type of tax applicable to the product. It specifies the tax category or rate
that should be applied when the product is sold, such as VAT (Value Added Tax), sales tax, or
other relevant taxes.

I. Category is a required classification for the product. It helps in organizing products and
determining the accounts associated with the product.
J. Sub-Category is an optional classification under the main category that helps further organize
products. If specified, it allows for more detailed categorization and can have its own accounts
separate from the main category.
K. Brand refers to the manufacturer's or producer's name associated with the product. It
helps in identifying the product's origin and distinguishing it from other products in the
market.
L. Color and Size are attributes used to describe specific variations of a product.
a. Color specifies the color of the product.
b. Size indicates the dimensions or size options available for the product.
M. Lead time :It is measured in days and includes the time needed for processing,
production, and shipping.
2- Details:

A. Sell/Buy options define the availability and type of transactions allowed for the product:
Sell & Buy: The product is both available for sale and can be purchased.
Sell Only: The product is only available for sale and cannot be purchased.
Buy Only: The product can only be purchased and is not available for sale.
B. Item Type: allows you to specify the type of product:
Product: Refers to a standard product item.
Package: Refers to a product that is sold as a package or bundle of multiple items.

C. Supplier Price: The price at which the product is purchased from the supplier.

Supplier Price Lock: A feature that allows you to lock the supplier price to prevent
changes, ensuring stability in procurement costs.

D. Sale Price: The price at which the product is sold to customers.

Sale Price Lock: A feature that allows you to lock the sale price to prevent changes,
maintaining consistency in selling prices.
E. Min Price: The minimum price at which the product can be sold, often set to ensure
that the product is not sold below a certain cost or profit margin.
F. Product Weight refers to the weight of the product, typically used for shipping
calculations and inventory management.
G. Unit of Weight specifies the unit of measurement used for the product's weight, such as
kilograms, grams, pounds, or ounces. This helps in standardizing the weight
measurements for the product.
H. Product Details URL: A link to a webpage or online document that provides detailed
information about the product. This could include specifications, features, or additional
resources related to the product.
I. External Image URL: A link to an image of the product hosted externally, such as on a
website or cloud storage. This URL is used to display the product's image in the system
or application.
J. Full Description provides a detailed and comprehensive overview of the product. It
typically includes information about the product's features, benefits, specifications,
usage instructions, and any other relevant details that help customers understand the
product fully.
3- Inventory setting:
A. Inventory Type
B. Non-Stock: The product is not tracked in inventory; it is typically a service or a product
that does not require inventory management.
C. Maintain Stock: The product is tracked and managed in inventory. Inventory levels are
monitored to ensure that there is sufficient stock available to meet demand.
D. Min Stock: The minimum quantity of the product that should be maintained in
inventory to avoid stockouts. When the stock level falls below this threshold, it signals
the need for replenishment.
E. Max Stock: The maximum quantity of the product that should be kept in inventory to
prevent overstocking. This helps in managing storage space and reducing excess
inventory costs.
F. Expiry Date: that an expiry date be entered for the product, ensuring that products with
a shelf life are tracked and managed properly.
G. Batch Number: the entry of a batch number for the product, which is crucial for
tracking and managing inventory batches, especially for quality control and traceability.
H. Item Serialization: that each unit of the product have a unique serial number, which
helps in tracking individual items for inventory management, warranty purposes, or
product recalls.

 Mandatory means that the information or action is required to complete the process.
If a field or feature is marked as mandatory, it must be filled out or addressed before
proceeding.
K. Max Purchasing Tolerance Level: The maximum allowable deviation from the ordered
quantity when receiving products. It defines the upper limit of acceptable variance
between the ordered and received quantities.
L. Min Purchasing Tolerance Level: The minimum allowable deviation from the ordered
quantity when receiving products. It defines the lower limit of acceptable variance
between the ordered and received quantities.
M. Max Sales Tolerance Level: The maximum allowable deviation from the sold quantity
when shipping products. It defines the upper limit of acceptable variance between the
sold and shipped quantities.
N. Min Sales Tolerance Level: The minimum allowable deviation from the sold quantity
when shipping products. It defines the lower limit of acceptable variance between the
sold and shipped quantities.

4- Photos refers to images or photographs associated with the product. These visual
representations help provide a clearer understanding of the product’s appearance and
details, and can be used for product listings, marketing, and inventory management
C. Create supplier :

The supplier will be selected from the database of the Telecom Egypt Company.
However, the explanation provided is for clarity on how to perform this action within
the system.

1- Supplier list
In the supplier list, all existing suppliers are displayed. We can search using various
criteria such as name, branch, etc., and we can also generate reports related to
suppliers. We can export reports in various formats such as Excel, Word, and PDF.

From this screen, the Import feature can be used. This allows you to upload and
integrate supplier data into the system from an external file, such as an Excel sheet, for
bulk data entry and management.
2- New supplier
a. Main

1- Corporate and Individual in the context of suppliers:

Corporate: Refers to suppliers that are businesses or organizations. When defining a
corporate supplier in the system, you'll typically include details such as the company
name, registration number, contact information, and business address.
Individual: Refers to suppliers who are private individuals rather than businesses. For
individual suppliers, you would include personal details such as their name, contact
information, and personal address.
These distinctions help in managing and categorizing suppliers appropriately based on
their nature and type.

2- brief explanation of each term used for defining a supplier:

Name: The official name of the supplier .
Alternative Name: Any other name or trade name the supplier might be known by.
Branch: The specific branch or location of the supplier, if applicable.
Country: The country where the supplier is based.
City: The city where the supplier is located.
Address: The detailed address of the supplier, including street and building number.
Telephone: The contact phone number for the supplier.
Invalid Number: A field to indicate if the provided telephone number is incorrect or not
in use.
Website: The URL of the supplier's website, if available.
Email: The contact email address for the supplier.
 3- Type: refers to the category or classification of the supplier. It is set up according to the
company's specific settings and can vary based on the company's requirements. This
classification helps in organizing suppliers into different types or categories based on
their nature or business relationship.
4- Remarks is a field where additional notes or comments about the supplier can be
entered.

b. Contact person
When selecting Corporate as the supplier type, this tab appears to allow us to
create entities or branches associated with this supplier. This helps in managing
and organizing different departments, locations, or business units that are part
of or related to the corporate supplier.

We fill in the supplier details as shown.

 c. Financial Details

a brief explanation of each term related to supplier information:

1.
TAX Option: Refers to the tax settings applicable to the supplier, such as VAT or other
2. VAT No: The VAT identification number assigned to the supplier for tax purposes.
3. Ledger Account: The accounting ledger account associated with transactions related
to the supplier.
4. Financial Account: The account used for financial transactions with the supplier,
which may include payments and receipts.
5. Tax Registration No: The number assigned to the supplier for tax registration
purposes, used for compliance with tax regulations.
6. Trade License No: The license number issued to the supplier to legally conduct
business.
7. Payment Terms: The terms agreed upon for payment to the supplier, such as net 30
days or other payment conditions.
8. Credit Limit: The maximum amount of credit that the supplier extends to the
company.
9. Credit Days: The number of days allowed for payment of invoices, based on the
credit terms agreed upon.
10. Reference No.: A unique reference number associated with the supplier, used for
tracking and identifying records.
11. Deactivation Date: The date when the supplier’s account or status is deactivated or
becomes inactive.

12. Churn Reason: The reason for the supplier’s deactivation or discontinuation of business
relationship, if applicable.
 d. Documents

explanation for each term:

 Document Type: The type of document associated with the supplier, such as a contract, invoice,
or certificate.

 Document No.: The unique identification number of the document, used for tracking and
referencing purposes.

 Remarks: Additional notes or comments related to the document or supplier, which may
provide context or additional information.

 Expiry Date: The date when the document or its validity expires, indicating when it needs to be
renewed or reviewed.

The Expiry Date should trigger a notification when it is approaching or has passed. This
helps ensure timely actions are taken, such as renewing documents or addressing any
issues related to expiration.
 4.2.4 PR - Form Interface Requirements

After completing the previous settings, the data is prepared for transactions.
Next, we will work on the purchasing cycle.

1- Purchase Request list:

In this screen, all purchase quotations and their statuses will be displayed. You can
search using various filters such as product name, supplier, and warehouse , etc

 Here are the statuses for a Purchase Request:

1. Pending: The request has been submitted but not yet reviewed or acted upon.
2. Approved: The request has been reviewed and approved for further action.
3. Partially Ordered: The request has been partially fulfilled; some items have been
ordered while others are still pending.
4. Fully Ordered: All items in the request have been ordered.
5. Declined: The request has been reviewed and rejected.
6. Cancelled: The request has been cancelled and will not be processed.
7. All: Displays requests with any of the above statuses.

Through the system, we can customize the terminology for purchase quotation
statuses to align with the company’s specific needs and terminology.
 2- Create Purchase Request:

In the first step, we will create a Purchase Quotation, with all fields highlighted in
different colors. These fields will be worked on, and the color-coding is used to
illustrate the overall process, which will be explained in more detail later.

a. Main

1- Branch: Refers to the specific branch or location where the purchase request is being
made or where the products will be used.
2- Department: The department within the organization that is initiating the purchase or
that will be responsible for the order.
3- Warehouse: The storage facility where the purchased goods will be delivered and
managed.
4- Expected Delivery Date: The date by which the ordered goods or services are expected
to be delivered.
5- Job: Refers to the specific task or project that the purchase is related to, indicating the
purpose or work for which the items are being ordered.
b. Items
1. Description: Provides a detailed explanation of the product or item
being ordered, including its features or specifications.
2. Select Product or Type Item Description: The option to choose a specific
product or type of item and provide a description for it.
3. Budget Item: The specific item or category within the budget that the
purchase will impact.
4. Unit: The unit of measurement for the item (e.g., pieces, kilograms,
liters).
5. Ordering Unit: The unit in which the product is ordered, which may
differ from the unit used for budgeting or inventory.
6. Quantity: The amount of the product or item being ordered.
 c. Documents :

Refers to the option to attach relevant files or documents related to the

purchase, such as contracts, invoices, or specifications.

 Attach: The button or link used to upload or attach a file.

‫‪Sr‬‬ ‫‪Type‬‬ ‫‪Dev Shape‬‬ ‫‪Description‬‬
‫‪.‬‬
‫‪1‬‬ ‫‪Enhancement‬‬ ‫‪Free text‬‬ ‫التوصيف الواضح للموضوع‬

‫‪2‬‬ ‫‪Enhancement‬‬ ‫‪Dropdown list‬‬ ‫اعضاء لجنة التوصية‬

‫‪with title‬‬ ‫والمسمي الوظيفي‬
‫‪3‬‬ ‫‪Enhancement‬‬ ‫‪Automatic by‬‬ ‫نائب الجهة الفنية المختص‬
‫‪.requesters‬‬ ‫والمسمي الوظيفي‬
‫‪4‬‬ ‫‪Enhancement‬‬ ‫‪Automatic by‬‬ ‫نائب الجهة الطالبة المختص‬
‫‪.requesters‬‬ ‫والمسمي الوظيفي‬
‫‪5‬‬ ‫‪Enhancement‬‬ ‫‪Automatic by‬‬ ‫الجهة المسئولة عن التنفيد‬
‫‪.requesters‬‬ ‫واالستالم واالفراج وشهادة‬
‫االستالم االبتدائي والنهائي‪.‬‬
‫‪6‬‬ ‫‪Customization Dropdown list‬‬ ‫طريقة الشراء‬

‫‪7‬‬ ‫‪Customization‬‬ ‫‪Dropdown list‬‬ ‫أسباب الشراء‬

‫‪8‬‬ ‫‪Customization‬‬ ‫‪Free text‬‬ ‫أساس حساب القيمة‬

‫التقديرية‬
‫‪9‬‬ ‫‪Customization‬‬ ‫‪Check box / Yes‬‬ ‫توافر االرتباط‬
‫‪or No‬‬
‫‪10‬‬ ‫‪Customization‬‬ ‫‪Free text‬‬ ‫توضيخ الغرض والعائد من‬
‫المنصرف‬
‫‪11‬‬ ‫‪Existing‬‬ ‫‪Calendar‬‬ ‫تاريخ بداية ونهاية التعاقد‬
‫الجديد‬
‫‪12‬‬ ‫‪Existing‬‬ ‫‪Free text‬‬ ‫تاريخ بداية ونهاية التعاقد‬
‫السابق‬
‫‪13‬‬ ‫‪Existing‬‬ ‫‪Free text‬‬ ‫الموقف المالي لتنفيذ‬
‫التعاقدات السابقة‬
‫‪14‬‬ ‫‪Customization‬‬ ‫‪Free text‬‬ ‫موقف الخدمة من نهاية‬
‫التعاقدات السابقة‬
‫‪15‬‬ ‫‪Customization‬‬ ‫‪Check box / Yes‬‬ ‫مطلوب عينات ام ال‬
‫‪or No‬‬
‫‪16‬‬ ‫‪Existing‬‬ ‫‪Dropdown list‬‬ ‫اسم المشروع باالرتباط‬
‫المالي‬
‫‪17‬‬ ‫‪Existing‬‬ ‫‪Attachments‬‬ ‫المرفقات‬
 4.2.5 Memo - Business Process Description
The Purchase Memo is a crucial step within Telecom Egypt’s procurement process. Once a Purchase
Request (PR) has been initiated and approved, the system converts it into a Purchase Memo, which acts
as the formal document for further evaluation. The memo provides detailed information for the
Evaluation Committee to assess and decide whether to proceed with a Purchase Order (PO).

Figure 2: Memo Flow

4.2.6 Memo - Process Steps Details Requirements
After creating the Purchase Request and it passes through all stages of the approval
cycle, the next step is to create the Purchase Memo. This memo formalizes the
purchase decision, marking the transition from request to execution.

1. Memo list

From the Purchase Request View screen, we will proceed to create the Purchase Memo. This
step allows us to document and formalize the purchase request for further processing.

We will create a dedicated screen to display all the Memos that will be generated.
This screen will allow easy tracking and management of all purchase memos in the
system.
2. Create Memo
This screen displays the Memo after it has been created by CorporateStack, and most
of the data will be taken from the Purchase Request. There will be a table below that
outlines where the information is sourced from and its nature. This helps in tracking
the origin of the data and ensures accuracy in the memo creation process.
2.1 Process Step

ID Process Step Description Solution Description Business Role

1 User Login The system, guided by predefined permissions, will identify
the login credentials and accordingly display the
functionalities accessible to the user based on those
credentials.
2 Purchase Request Status The user, based on their defined role in the system, will review Requester
navigation the status of all purchase requests (PRs) and complete the cycle
for approved PRs by issuing the corresponding memo.
23 Create the Purchase The user will initiate the purchase Memo by completing all the Requester buyer
Memo mandatory fields, which are clearly identified and listed below,
and then proceed with the first step of the approval cycle
3 Direct manager approval Based on the designed organizational chart that forms the Direct Manager
foundation of the SCM, the system will identify the employee
profile and their direct manager, enabling the system to send
notifications and collect the necessary approvals.
4 Direct Manager feedback Based on the type and nature of the request, the direct manager Direct Manager
will have the authority to approve it directly, send it back for
further clarification, or deny the Memo outright.
5 Action based activity Based on the feedback, the Memo will either be returned for
modifications and adjustments, or it will proceed to the next step
in the approval cycle.
6 Department Director / Based on the feedback, the request will either be sent back for Department Director
GM modifications and adjustments, or it will advance to the next stage & GM
in the approval process.
7 Once all required approvals are obtained, the memo will be Warehouse Staff
Audit Team forwarded to the audit team for validation. The audit team has the
authority to approve, return for revisions, or reject the memo.
Based on their decision, the memo will either proceed to the next
step or be finalized accordingly.
‫‪2.3 information source from and nature‬‬
‫‪.Sr‬‬ ‫‪Dev Shape‬‬ ‫‪Description‬‬
‫‪1‬‬ ‫‪Auto generation‬‬ ‫رقم المذكرة‬

‫‪2‬‬ ‫‪Calendar‬‬ ‫تاريخ‬

‫‪3‬‬ ‫‪Automatic from PR‬‬ ‫الموضوع‬

‫‪4‬‬ ‫‪Automatic from PR‬‬ ‫لجنة التوصية‬

‫‪5‬‬ ‫‪Automatic from PR‬‬ ‫نائب الجهة الفنية المختصة‬

‫‪6‬‬ ‫‪Automatic from PR‬‬ ‫نائب الجهة الطالبة المختصة‬

‫‪7‬‬ ‫‪Automatic from PR‬‬ ‫الجهة المسؤولة عن االستالم‬

‫‪8‬‬ ‫‪Automatic from PR‬‬ ‫طريقة الشراء‬

‫‪9‬‬ ‫‪Automatic from PR‬‬ ‫أسباب طريقة الشراء‬

‫‪10‬‬ ‫‪Dropdown list‬‬ ‫الشركة الموصي بها‬

‫‪11‬‬ ‫‪Dropdown list‬‬ ‫موقف اعتماد مسودة العقد‬

‫‪12‬‬ ‫‪Automatic from PR‬‬ ‫القيمة التقديرية‬

‫‪13‬‬ ‫‪Automatic from PR‬‬ ‫أساس حساب القيمة التقديرية‬

‫‪14‬‬ ‫‪Calendar‬‬ ‫صالحية العرض‬

‫‪15‬‬ ‫‪Free text‬‬ ‫قيمة التوصية‬

‫‪16‬‬ ‫‪Automatic from PR‬‬ ‫الغرض والعائد من المنصرف‬

‫‪17‬‬ ‫‪Automatic from PR‬‬ ‫التعاقدات السابقة لنفس االعمال‬

‫‪18‬‬ ‫‪Automatic from PR‬‬ ‫الموقف المالي لتنفيذ التعاقدات السابقة‬

‫‪19‬‬ ‫‪Automatic from PR‬‬ ‫سعر أخر شراء‬

‫‪20‬‬ ‫‪Free text‬‬ ‫شرح محتصر لما تم في إجراءات الشراء‬

‫‪21‬‬ ‫‪Dropdown list‬‬ ‫شروط التعاقد‬

‫‪22‬‬ ‫‪Automatic from PR‬‬ ‫توافر االرتباط‬

 23 Dropdown list ‫الشروط التجارية‬

24 Free text ‫التوصية‬

25 Free text ‫بند الالئحة‬

4.2.7 Letter of Internal

After the Purchase Memo is approved, the Letter of Internal will be created as follows. This letter serves
as the formal confirmation of the purchase decision, outlining the terms, conditions, and
responsibilities agreed upon for the procurement process.

4.2.8 Purchase order

1. Purchase order list
In the PO List, all purchase orders will be displayed along with their current statuses.
This allows easy tracking and management of each order as it progresses through
different stages.
 In the Purchase Order list, the orders will be categorized by their
statuses:

 Pending: Orders that are awaiting approval or further action.

 Approved: Orders that have been approved and are ready for processing.
 Issued Orders: Orders that have been issued to the supplier.
 Partial Delivery: Orders that have been partially delivered.
 Delivered: Orders that have been fully delivered.
 Declined: Orders that have been rejected.
 Cancelled: Orders that have been cancelled.
 Deleted: Orders that have been removed from the system.
 All: Displays all orders regardless of their status.

2. Create purchase order

 2.1 Main

a. Supplier: The vendor providing the goods or services.

b. Contact person: The point of contact at the supplier's side.
c. Subject: Brief title or description of the purchase.
d. Branch: The company location handling the order.
e. Sub-Branch: A smaller division or office within the branch.
f. Department: The department responsible for the purchase.
g. Currency: The currency used for the transaction.
h. Purchase Type: Whether the purchase is local or international.
i. Purchase order date: The date the purchase order was issued.
j. Quote Reference: The reference number of the supplier's quotation.
k. Assigned to: The person responsible for managing the PO.
l. Signatory: The person authorized to sign the PO.

2.2 Delivery Details

brief explanation of each term:

a. Ordered to Office: Indicates that the items are ordered to be delivered directly to the office.

b. Ordered to Warehouse: Indicates that the items are ordered to be delivered to the warehouse.

c. Ordered to Job: Indicates that the items are ordered for a specific job or project.

d. Delivery Date: The expected date on which the items will be delivered.

e. Shipping (Shipping Method): The method used to ship the items (e.g., air, sea, land).

f. Stock Value: Indicates whether VAT will be added to the item's price when creating the Goods
Receipt Note (GRN).

g. Delivery Address: The address where the items will be delivered.

h. Delivery Remarks: Any additional notes or instructions related to the delivery.

i. B/L No: Bill of Lading number, a document issued by the carrier acknowledging receipt of goods
for shipment.

j. Container No: Number assigned to the shipping container.

 k. Shipping Port: The port from which the items are shipped.

2.3 Items

brief explanation of each term:

 Type (Product, Service, Asset): Specifies whether the order is for a product, service, or asset.
 Description: A detailed explanation of the item or service being ordered.
 Budget Item: The category or account within the budget that the purchase will impact.
 Unit: The unit of measurement for the item (e.g., pieces, hours, units).
 Quantity: The amount of the item or service being ordered.
 Price: The cost per unit of the item or service.
 Discount: Any reduction in price applied to the item or service.
 VAT: Value Added Tax applied to the item or service.
 Sub Total: The total amount before any additional charges (such as VAT) or discounts are
applied.
 2.4 Payment terms

brief explanation of each term:

 Percentage: Indicates the percentage of the total amount that will be paid.
 Amount: The total sum to be paid or processed.
 Payment Method: The method used to make the payment (e.g., bank transfer, credit card,
cash).
 Due on (Days, Date): Specifies the due date for the payment, either by a certain number of days
or a specific date.
 Due In Days: The number of days remaining until the payment is due.
 Due In Date: The specific date by which the payment must be made.
 Description: Additional details or notes related to the payment terms.
 2.5 Terms & Conditions

 If there are written terms or Condition in the PO

2.6 Documents

brief explanation of each term:

 Document Type: The category or nature of the document (e.g., invoice, receipt, contract).

 Document No: The unique identifier or reference number for the document.

 Remarks: Additional comments or notes related to the document.

 Expiry Date: The date after which the document is no longer valid or applicable.

 Upload Document: The action to attach or upload the document to the system.

 Verified: Indicates whether the document has been reviewed and confirmed as accurate or
valid.
4.2.9 Purchase Invoice

1. Main

brief explanation of each term:

1. Voucher Date: The date the voucher or payment document is issued.

2. Narration: A brief description or explanation of the transaction.
3. Supplier: The vendor or company from whom the goods or services were purchased.
4. Purchase Order: The reference number or details of the purchase order associated with the
transaction.
5. GRN (Goods Received Note): A document confirming receipt of the goods.
6. Land Cost Invoices: Invoices related to land costs, if applicable.
7. Additional Tax: Any extra tax applied beyond the standard VAT or tax rate.
8. Currency: The currency used for the transaction.
9. Division: The division within the company handling the transaction.
10. Branch: The company location where the transaction is processed.
11. Sub-Branch: A smaller division or office within the branch.
12. Job: The specific project or job associated with the purchase.
13. Payment Terms: The conditions under which payment should be made (e.g., net 30 days).
14. Bill No.: The reference number of the bill.
15. Bill Date: The date on which the bill was issued.
16. Due Date: The date by which the payment is due.
 2. Line Items

brief explanation of each term:

1. Item Description: A detailed description of the item being purchased.

2. Unit: The measurement unit for the item (e.g., piece, kilogram, hour).

3. QTY: The quantity or number of units being ordered.

4. Price: The cost per unit of the item.

5. Discount: Any reduction in price applied to the item.

6. Total: The final amount for the item, calculated by multiplying the unit price by the quantity and
subtracting any discounts.

3. Documents
Reporting
1- Purchase Request Status

The report will categorize each purchase request (PR) status as defined in the module's
configuration and generate separate PRs based on those statuses.

2- Purchase Memo Status

The report will categorize each purchase memo status according to the
module's configuration and generate separate purchase memos based on
those statuses.
 3- Purchase Order Status
The report will categorize each purchase order (PO) status based on the
module's configuration and generate separate POs, including their delivery
status, according to the specified delivery conditions
This report will include the purchase order (PO) number, branch, date, and
other details.

4- Supplier Reports
The supplier report will include key details such as Account Number (Acc No.), Name, Country,
City, and Account Type. It will also specify the employee assigned to the account (Assigned To
Employee), the person it is delegated to (Delegated To), and the employee who originally created
the account (Created By Employee) along with the creation date (Created On). Additionally, the
report will capture the industry sector (Industry), any relevant flags (Flags), and the source of the
account (Source).
 The Purchasing Financial Report provides a detailed breakdown of all financial transactions
associated with purchasing activities, offering insights into spending patterns and financial
performance.

Report title Comments

Purchase Request Status The Purchase Request Status report provides a summary of the status of purchase
requests in the system. It helps users track various purchase requests and shows
whether the requests are under review, approved, canceled, or converted into
purchase orders.
Purchase Memo Status The Purchase Memo Status report provides an overview of the status of purchase memos in
the system. This report helps users track the progress and handling of purchase memos,
showing their current status and other relevant details.

Purchase Order Status The Purchase Order Status report provides a detailed overview of the current
status of purchase orders in the system. It helps users track the lifecycle of
purchase orders (POs), from creation to completion, and provides insights into
their progress.
Supplier Performance Report The Supplier Performance Report evaluates suppliers based on key metrics such as
order volume, on-time delivery, delivery accuracy, lead time, total purchase value, and
response time.

The Contract Approval Status The Contract Approval Status Report provides an overview of the current status of
Report contract approvals within the system. It helps users track the progress of contracts
through the approval process.
Regulatory Compliance Report This report highlights the published purchasing policies and tracks the acknowledgment
status for each policy across employees and departments. It provides a clear view of
which policies have been acknowledged by staff, helping ensure compliance and
awareness of purchasing procedures throughout the organization.
The Purchasing Financial Report The Purchasing Financial Report provides a detailed financial analysis of all purchasing
activities within an organization.
Workflow
Workflow setup
1. Purchase Request
 Purchase Request Process:

1. Select Purchasing Request: Begin by selecting the purchasing request.

2. Choose Branch and Department: From the workflow, select the relevant branch and
department.
3. Select Approval Sequence: Next, choose the sequence of approvals from the designated
employees. The sequence should follow a top-to-bottom order.
4. Save and Follow Workflow: Once saved, the purchase request will follow the predefined
workflow for the selected department. It will also appear in the workflow window as configured.
5. Editing: The request can be edited later if necessary.

2. Purchase Order
Purchase Order Process:

1. Select Purchase Order: Start by selecting the purchase order.

2. Choose Branch and Department: From the workflow, choose the appropriate branch and
department.
3. Select Approval Sequence: Select the sequence of approvals from the employees. The sequence
should flow from top to bottom.
4. Save and Follow Workflow: After saving, the purchase order will follow the configured workflow
for the selected department and will appear in the workflow window as set.
5. Editing: The purchase order can be edited later if necessary.

The requester has submitted their request and it is now in the approval phase.

 the first approver

The approver will get a notification and then will click it will take him to the purchase requests list

The approver has three options: to accept, decline, or edit

 3. Project Implementation Approach
In CorporateStack our approach to implementing the system is designed to ensure a seamless and
successful transition for your organization. Here is an outline of our implementation approach:
CorporateStack’s Software Implementation Methodology represents a carefully crafted framework of procedures
and best practices aimed at guaranteeing the seamless deployment of our solutions. At CorporateStack, we
acknowledge that each implementation scenario is unique. Hence, our methodology incorporates overarching
activities and processes while affording substantial flexibility at the task level. This approach empowers our
implementation team to tailor the process to the specific requirements of each project, ensuring a customized and
effective solution deployment.

Figure 3: Implementation Approach

a. Implementation Flow
The implementation of CorporateStack’s SCM solution involves several key stages meticulously designed
to ensure a smooth and effective deployment. These stages include detailed planning, comprehensive
configuration, seamless data migration, user-friendly customization, rigorous testing, and meticulous
training. Our methodology prioritizes collaboration with your team, allowing for flexibility and
customization at every step. This ensures that the implementation aligns precisely with the unique
needs and processes of your organization, fostering a successful and tailored solution.
 b. The Project Kick-off
This project event has been arranged in collaboration with our valued Customer to mark the official
commencement of the project.
During this meeting, we will introduce the members of the project team, elucidating their respective
roles and responsibilities. The session will also cover the project’s overarching objectives, the high-level
scope, and a detailed discussion of the project timelines. Teams involved during this stage are:

Team Involvement

c. System Analysis
The System Analysis stage starts the Execution phase of the project. During this stage, the hardware
readiness, current system (either the legacy application or manual process), existing workflow and
future workflows are reviewed and documented. System Analysis consists of:
 Current System Analysis and Workflow Review
 Interfaces Study and Discussion
 Configuration Data Collection

The Current System Analysis and Workflow Review (Future System Analysis) sessions are led by our
Solution Architect with participation of THE Customer’s Subject Matter Experts and Core- users. During
the Current System Analysis, THE Customer’s current practices, policies, and workflows (legacy system
or manual process) are discussed and documented.
The purpose of the Workflow Review (Future System Analysis) stage is to understand and incorporate
the requirements and needs of THE Customer, enhance, and map the As-Is workflows to our application
processes. The Future System Analysis sessions will be initiated by demonstrating the vanilla application
to THE Customer’s Subject Matter Experts/ Core-users. It should be noted that at this stage, the
application is not configured to THE Customer’s requirements. The purpose of this demonstration is to
make THE Customer’s Subject Matter Experts/ Core-users familiarize the application’s out-of-box
functionalities and capabilities, which would be helpful during the Future System Analysis discussions.
After concluding the future system analysis discussions, solution architect will produce future workflow
document, proposing the future workflows and the interface touch points with 3rd party solutions. The
future workflow document will be discussed and finalized with Customer’s subject matter experts, core-
users, and the solutions architects of the 3rd party solutions.

After finalizing the future workflow document, our interface architect will initiate interface discussions
with 3rd party solutions. For Customer implementation, the interface discussions will be in a separate
interface stream. During this stream, the workflows and interface touchpoints are discussed in detail
and will produce an interface model document.

During the configuration data collection stream, which runs in parallel to the interface stream, our
solution architect will review and discuss with Customer subject matter experts/ core- users and solution
architects of other 3rd party solutions on the configuration data that needs be collected for our
application. After these discussions, CorporateStack submits the finalized data collection templates (dct)
for data collection, and Customer provides the data requested, per the project schedule.
Team Involvement
 d. Customization Design
The primary objective of this stage is to conclude the customization design and the interface model.
Our solution architect will compile and submit the customization design document to Customer,
outlining forthcoming workflows, streamlined as-is workflows, interface touchpoints, application
functionalities, business rules, “stop, start & continue” processes, and design determinations for
The application.

Throughout the customization design review sessions, our solution architect will present the
customization design document to Customer’s subject matter experts (smes) and core users. The
outcome of these sessions will be the finalization and approval of the customization design document.
 e. Integration Design
The interface model document, generated initially during the system analysis - interface stream, delves
into the specifics of interface touchpoints and trigger events, format, and specifications of interface
messages, design choices, and other technical elements of the interfaces.
Our integration architect will conduct a comprehensive review of the interface model document
alongside the integration architects of third-party solutions. This collaborative effort will result in the
finalization and approval of the interface model document.
Working closely with the solution and integration architects, our business analysts and implementation
consultants will revise and enhance the product-ready test scripts for system validation. These scripts
will encompass various test scenarios based on the functional design and interface model document.

f. Internal Quality Control (QC)

Focuses on configuring the platform with the mandatory functionality and managing personalization to
align This stage is dedicated to the meticulous testing and validation of the CorporateStack solution and
interface components, which is essential before the application proceeds to User Acceptance Testing.
Our Implementation Team, in collaboration with Quality Control (QC), undertakes a series of
comprehensive testing processes to ensure the high quality of the Application Build.
Key Testing Phases:
 Unit Testing: This phase verifies that the configuration data from Customer aligns seamlessly
with the application’s requirements. It is conducted in parallel with the Build and Configuration
activities and is diligently performed by our QA team, with support from Business Analysts and
Implementation Consultants.
 System (Functional) Testing: Following the application’s configuration, this phase involves
standalone functional testing to validate that the application functions as intended. Our QC
team, supported by the Solution Architect, conducts this testing in parallel with Build and
Configuration activities.
  Interface Testing: This critical testing phase is carried out with 3rd Party applications after the
Interface Build and Configuration, as well as Unit and System Testing, are completed. It adheres
to the Interface Model document, covering all aspects of the interfaces. This collaborative
testing effort comprises our QA team, Business Analysts, Implementation Consultants, and the
3rd Party Application team. Representatives from the required 3rd Party systems must be
available. The Integration Architect leads the testing and assists in creating test cases and
scenarios.
 Solution Validation: This comprehensive testing phase occurs after the successful completion of
the previous testing phases and consists of two parts:
.1 End-to-end testing to verify the integrated application’s functionalities and the
interface touch-points with 3rd Party applications.
.2 A demo of the application to Customer upon completing part (1).
This rigorous Internal QC process ensures the quality, functionality, and performance of the
CorporateStack solution, providing a solid foundation for the subsequent User Acceptance
Testing phase.

Figure 4: Integration Flow

g. Training - Empowering Users for Success

In this pivotal phase, CorporateStack is dedicated to preparing and empowering users to efficiently
utilize the solution in alignment with their functional roles and responsibilities. Administrative training is
also a key component. Our training methodology follows the “Train-the-Trainers” approach, fostering
self-sufficiency and continuous learning.

 Train-the-Trainer Approach: CorporateStack adopts the “Train-the-Trainer” method,

which complements Customer’s Continuous Learning strategy and programs. Customer
typically identifies Trainers from the Subject Matter Experts (SMEs) and Core-User
groups, evaluating them based on their training capabilities and participation in project
implementations. These Trainers are crucial in cascading knowledge to end-users,
usually during Go Live Preparations or when new users join the organization.
 Training Focus: The training extends to all identified Subject Matter Experts and Core-
User groups, who serve as Champions and Trainers responsible for equipping End-Users.
It is typically conducted after the successful User Acceptance Testing (UAT) phase.
 Training Delivery:
.1 Application Functionality
.2 Application Administration
 Training Agenda and Schedules: CorporateStack provides Training Agendas and
Schedules in advance to the Customer to facilitate planning and session arrangements.
 Collaborative Training Planning: As part of Training Planning, our Trainers work closely
with the CorporateStack Project Manager, Solution Architect, and the Customer’s
project team to ensure that all training requirements are met. Expectations are
thoroughly discussed and understood to plan for a successful training experience.
 Application Functionality Training: The primary objective of this training is to ensure
that trainees have a comprehensive understanding of the application’s functional
aspects, its interactions with other 3rd Party applications, and role-based functionalities.
The training is based on the Design Document, and trainees receive hands-on
opportunities during the sessions. Each trainee is provided with a set of role-based tasks
to be completed in the application, ensuring that theoretical knowledge can be
effectively translated into practical proficiency. Trainees are assessed through a
classroom-based exam to evaluate their application competency. Additionally, Training
Evaluation Forms are distributed to determine the training sessions, topics, and the
training environment. Training Manuals are provided during the sessions.
 Application Administration Training: This training is tailored for individuals identified by
Customer as Application Administrators. The training equips trainees with a
comprehensive understanding of the configuration and administration aspects of the
application. Each trainee is given a set of configuration/administrator-based tasks to be
completed in the application’s configuration area, ensuring they are confident and
knowledgeable about the concepts. Like Application Functionality Training, a classroom-
based exam evaluates trainees’ competency. Training Evaluation Forms are also
distributed to assess the training sessions, topics, and the training environment. Training
Manuals are provided during the sessions.
 h. UAT
knowledgeable about the concepts. Like Application Functionality Training, a classroom-based exam
evaluates trainees’ competency. Training Evaluation Forms are also distributed to assess the training
sessions, topics, and the training environment. Training Manuals are provided during the sessions.
During this stage, the core users and subject matter experts of the organization conduct end-to-end
testing of the solutions, covering both functional and technical aspects (including security testing). If
defects are identified, they will be prioritized and scheduled for correction. CorporateStack will submit
test scripts to the organization as a guideline for testing. If needed, the organization can create
additional test scripts and test scenarios.

The UAT process will involve several key steps:

 Planning: Our project manager will hold meetings with the Telecom Egypt project team, solution
architects, integration architects, and third-party applications to confirm UAT dates, ensure
readiness of UAT test data and domains, verify third-party solution readiness, and review the
development and coverage of test scripts and other details.

 Test Script Readiness: CorporateStack will develop and submit the test scripts to Telecom Egypt.
If needed, Telecom Egypt can create additional test scripts.

 Selecting the UAT Team: Identification and confirmation of Telecom Egypt's UAT team and
third-party solutions' UAT team. The UAT team should be familiar with the application and
should have attended the Train-the-Trainer sessions.

 Execution of UAT: Telecom Egypt's team will execute the UAT based on the UAT scripts, with
assistance from our business analysts and implementation consultants. During UAT execution,
each test case will be marked as Pass or Fail, and failed test cases will have a priority indicator
set by the tester.

 Issue Correction: Each day, business analysts and implementation consultants will conduct UAT
review meetings with the Telecom Egypt project team to review UAT results and reconfirm
priority indicators. Corrective actions will be taken for Priority 1 and 2 issues. Priority 3 and 4
issues will be reviewed with the solution architect to create a correction schedule, which will be
discussed with the Telecom Egypt project team. Failed test cases will be re-run after corrections
are made.

 Application Acceptance: In the final stage of UAT, Telecom Egypt will provide application
acceptance sign-off based on the acceptance criteria documented in the project plan.
 i. Go Live Preparation
In this pivotal phase, we meticulously prepare for a seamless transition to live project operations.
Regular Go Live Preparation meetings are conducted to verify that all essential preparations are in place
for a successful launch. This stage is marked by infrastructure and application readiness reviews, and
Customer’s Subject Matter Experts and core users are instrumental in providing End-User training. Key
aspects of this stage include:

1. Production Hardware and Environment Readiness Assessment: This step involves a thorough
assessment to ensure the production hardware and environment are fully prepared to support
the project’s live operation.
2. Train the Trainers Training Confirmation: We confirm that the “Train the Trainers” training
across all functional areas has been completed. This is crucial to ensure that the trainers
instructing end-users are fully equipped with the necessary knowledge and skills.
3. Resolution of High Severity Software Issues: High-severity software issues, as defined by the
Test Plan, are addressed and updated in the production environment. This is a critical step to
ensure the system is free from any significant defects that could impact the Go Live phase.
4. System Cut-Over Plan Publication: The System Cut-Over plan is published, outlining agreed-
upon Data Migration timings and providing a clear understanding of the process for manually
migrating legacy data to the live environment. This ensures a smooth transition from the testing
environment to the production environment.
5. Go-Live Support Roster Publication: A comprehensive Go-Live support roster is published,
designating roles and responsibilities for the team members supporting the project’s launch.
This includes individuals responsible for various aspects of the Go Live phase.
6. Go-Live Issue Escalation Procedure Publication: The Go-Live Issue escalation procedure is
available, providing a clear and documented process for addressing and escalating any
unforeseen issues during the Go-Live phase.
 j. Go Live – The Launch into Action
The Go Live phase marks the solutions transition into live operation. During this crucial stage,
CorporateStack will deploy business analysts and implementation Consultants to provide essential
support and guidance to end-users.
Key activities encompass:
1. Define the Go-Live Date and Time: The Go-Live date and time are precisely defined and
communicated to all users to ensure a coordinated transition.
2. Review and Update Support Strategy: A thorough review of the support strategy is conducted,
and the communication process during Post Go-Live Stabilization support is updated to align
with the evolving needs of the project.
3. Distribute Support Resources: The necessary support resources are distributed to the
designated teams to provide immediate assistance and address emerging issues.
4. Manage Support Calls and Issues: Efficient management of support calls, logs, and issue
tracking is vital. This ensures a systematic approach to resolving user queries and addressing
operational challenges.
5. Daily System Round: A daily system round is conducted to monitor users’ activities and gather
feedback. This process helps in identifying and addressing any concerns or challenges faced by
users.
6. Monitor Printing and Message/Interface Operations: Continuously monitoring the correct
operation for printing forms, reports, labels, and barcodes is essential to maintain smooth
operations. Additionally, the monitoring of messages, interfaces, and error logs is crucial to
ensure data integrity and system functionality.
7. Install Fixes Based on Feedback received during the support process is analyzed, and, if
necessary, fixes and updates are deployed to enhance system performance and user experience.
8. Go-Live Issues Log Tracking: An issues log is diligently maintained and updated daily to ensure
timely resolution and closure. CorporateStack recommends providing on-site stabilization
support two months following the Go-Live date, utilizing the Centralized Command Center
method located within Customer’s premises. Additionally, we offer ongoing annual
maintenance and support based on the standard support model, with the option to include on-
 site support as needed. This comprehensive approach ensures a successful and smooth
transition to live operations and continued support for the project.

k. Post Go Live – The Launch into Action

CorporateStack offers a dedicated post-go-live support period of one month. This support is provided during a
single shift for 8 hours a day, five days a week.
Following the conclusion of the post-go-live support phase, our commitment to support seamless transitions to the
ongoing L2 and L3 support, which follows the standard maintenance contract mode. This ensures your facility
receives the necessary assistance and maintenance to sustain and optimize the solutions implemented. Our
ongoing support is designed to meet the evolving needs and challenges of your operations, providing a reliable
foundation for Customer facility’s success.

4. The Project Requirements

a. The Delivery
The CS team will strategically divide the project into Three distinct tracks to ensure a streamlined and
efficient implementation process.
The on-boarding track: Focuses on configuring the platform with the mandatory functionality and
managing personalization to align with Customer’s specific requirements. This involves personalizing the
system to meet the organization’s unique needs, ensuring seamless optimized functionality. The CS
team will handle the on-boarding process meticulously, ensuring that all necessary modules are
appropriately configured and personalized to enhance user experience and maximize system
capabilities.
The customization track: Addresses any requirements that necessitate new developments features that
may require. This track will operate in an agile manner, allowing for flexibility and iterative
enhancements throughout the project. The CS team will closely collaborate with stakeholders to identify
and prioritize customization needs and then proceed with agile development cycles to deliver tailored
solutions. This approach ensures that new developments are implemented efficiently and effectively,
aligning with Customer’s evolving business objectives.

Third-Party Integration Track: The integration track focuses on API design and testing for seamless
integration with external systems and services. Our team will work with Customer team and relevant
third-party vendors to identify the necessary integrations. We will design and develop robust APIs that
facilitate data exchange between the CS CRM system and these external systems. Rigorous testing and
validation will be conducted to ensure the smooth flow of data and a seamless user experience.
By kicking off all three tracks in parallel, we aim to expedite the project delivery process while
maintaining high quality and attention to detail. This approach allows us to progress across multiple
areas concurrently, avoiding potential bottlenecks and ensuring efficient use of resources. Regular
communication and collaboration between our teams will ensure that all tracks progress smoothly and
remain aligned with the overall project goals.
Throughout the implementation process, we will provide regular status updates, conduct milestone
reviews, and engage in ongoing communication with your organization to ensure transparency and
address any questions or concerns that may arise. Our experienced project manager will oversee the
entire implementation, ensuring each track remains on schedule and meets your expectations.
We are committed to delivering a successful project outcome and providing a state-of-the-art CRM
system and career portal that aligns with your organization’s needs, enhances Customer’s operational
processes, and supports your talent acquisition efforts.

b. The Project Team

Figure 5: CS Team
c. CorporateStack Direct / Indirect Facing
d. The Project Documentation
 e. The Project Requirements
1. Hardware
 Intel Quad-core or higher
 32GB RAM or higher
 1 TB SSD or higher
2. Software
 Windows Server 2016 or higher
 IIS version 8 or higher
 MS SQL Database version 2014 or higher
 Net Framework version 4.8 or higher

Figure 6: High-Level Architecture

 f. Telecom Egypt Team Requirements
CorporateStack and Customer teams both aim at delivering the best possible service to complete the
project at the maximum success level. This requires proper cooperation and coordination between the
teams involved to achieve the required results and ensure an on-time and on budget project delivery.

Customer must appoint a project manager who will build the adequate team around CorporateStack
team. In case of the unavailability of the required resources, CorporateStack project manager will report
the potential impacts to Customer project manager (project delay, project resources allocation,
commercial impacts).

Customer commits to provide the necessary hardware and software in addition to the network
capabilities to achieve the highest possible service performance. It’s mandatory to provide
CorporateStack team with all the required information for the integration with the third-party systems.

As per Telecom Egypt Document the team allocation for the project is as follow

i. Resource Allocation
1. Project Manager (1)
o Responsibilities:
 Oversee the entire project
 Coordinate between Telecom Egypt and the service provider
 Ensure project timelines and budgets are met
 Communicate with stakeholders
 Manage risk and issue resolution

2. Business Analyst (2)

o Responsibilities:
 Gather and document business requirements
 Conduct process mapping and gap analysis
 Liaise between business users and the service provider
 Validate system design against business needs

3. Procurement Lead (1)

o Responsibilities:
 Provide expertise on procurement processes
 Ensure system functionalities meet procurement needs
 Validate configurations and customizations
 Support UAT and system validation

4. Data Migration Specialist (1)

o Responsibilities:
 Plan and coordinate data migration activities with the service provider
 Ensure data accuracy and integrity
 Validate data post-migration
  Resolve data-related issues

5. Training Coordinator (2)

o Responsibilities:
 Develop and implement training plans
 Organize training sessions and workshops
 Create training materials (manuals, guides, videos)
 Provide ongoing user support during and after training

6. Change Management Lead (2)

o Responsibilities:
 Develop and implement change management strategies
 Conduct change readiness assessments
 Engage stakeholders and manage communication
 Address user concerns and resistance

7. Subject Matter Experts (2)

o Responsibilities:
 Provide expertise on procurement processes
 Validate system functionalities against business requirements
 Support UAT and system validation
 Assist in training and change management activities

Total Team Members: 11

g. High-Level Project Plan

The initial project plan is attached to this document.

5. The Annexes
a. Building an ERP System for Telecom Egypt's
Procurement 2
b. High-Level Project Plan MS Excel Sheet