Sales Order Application for Cable Manufacturing Industry

Client

Sales Order Web Application

Date: June 04, 2020

Version 1.1

By signing / Approval of this proposal you are agreeing that the information contained in this document is confidential and will not be shared with any third parties without inexpensivecoders permission.

Table of Contents

Objective
Background
Scope
Development Team
Development Strategies
LOGIN Page
ADMIN Login
Menu
Customer Login
Executive Login
Agent Login
Entry
Solution Implementation
Client Responsibilities
Project Deliverables
Timeframe for Expected Deliverables
Structure of the project team
Contact person from client’s side
Incident Change and Release Management
12.1 Incident Management
12.2 Change Management
12.3 Release Management
Deployment, testing, documentation and training for the newly integrated systems
Quality Assurance and Quality Control
The payment schedule
Terms & Conditions

Introduction

Dear Client

We welcome the opportunity to build a cutting-edge online Sales Order Web application Software that will have the required functionalities using the high-level Requirements gathered from you.

inexpensivecoders is a Custom software development and Mobile application development company focused on empowering organisations by deploying the best of breed, cost-effective software solutions that would add immense value to their business processes. From Desktop to mobile including Android, iPhone applications, iPad applications, PHP, HTML5, .Net, PERL, CFML, Python applications) inexpensivecoders delivers apps and websites on every platform.

inexpensivecoders also offers full white label solutions, mobile applications, mobile websites, complete brand customization, applications for small businesses and more.

To know more about the organisation and the envisaged project, please contact Hari, at hari@inexpensivecoders.com or +91 99521 99321

We look forward to working with you.

1. Objective

This document provides an overview of Client’s Online Sales Order software requirement.

2. Background

Client is a well-known established product development company that has various customers across the globe. Due to the growth of technology and expansion of their business, Client feels that online sales order web application will help their customers for onetime procurement and delivery

3. Scope

Client’s online sales Order software requirement is the primary focus of this document. As the enterprise Sales order application, this system should capture and distribute a wide variety of Customer, Products, Sales data and should effectively manage, analyse and report everything that is possible in sales using this application. The requirement is not limited to but will ensure that it meets the below given criteria.

The developed Sales order System will be owned and managed by Client and it should suite to the organization's business model, organizational structure and cost structure.
Should be installed at the Client Server.
Must fully interface and be capable to export/import related financial and personnel data to/from the organization's custom software respectively.
The system should be able to produce various reports on all aspects
Single Sign-On
Tool to do bulk user updates
Data integrity, archiving and storage

4. Development Team

The development team (inexpensivecoders) will work closely with Client to develop the sales order application

inexpensivecoders is a full-service Custom software and Application development company that provides cost cutting solutions for any business.

5. Development Strategies

inexpensivecoders will develop the application in PHP with mysql as backend and Apache server and Linux platform and is divided into the functional components. The components are tightly integrated. Data entered into any component flows throughout the system to those processes that use the data.

Sample Screens

LOGIN Page

With the logged in UserName, UserType should be catered and redirect to the respective Dashboard page.

ADMIN Login

DashBoard

Orders Received – Customerwise
Orders Received – Unitwise
Orders Received – Productwise

Order Entry
- Master
  - Customer will be the logged in customer
  - Sales Order No – Auto increment
  - Sales Order Date – Input
  - Purchase Order No – Input
  - Purchase Order Date – Input
  - Destination - Input
  - CustomerDeliveryDate - Input
  - SpecialInstructions - Input
  - Executive – Dropdown (for the logged in customer)
  - AgentCode – Dropdown (for the logged in customer)
- Get Product Details (Multiple Entries)
  - Product (Drop down – search text like ClientCRM – Customername)
  - (Search in ItemCode, Item Description)
  - GeneralDescription - Input
  - SpecialMarkings - Input
  - Quantity – Input

Executive Login

DashBoard
Orders Booked Customerwise / Productwise
Orders Pending Customerwise / Productwise
Orders Invoiced Customerwise / Productwise
Payment pending Customerwise / Productwise
Entry
Order Entry
Master
Customer – Input dropdown (for the logged in executive)
Sales Order No – Auto increment
Sales Order Date – Input
Purchase Order No – Input
Purchase Order Date – Input
Destination - Input
CustomerDeliveryDate - Input
SpecialInstructions - Input
Executive – Logged in Executive
AgentCode – Dropdown (for the selected in customer)
Get Product Details (Multiple Entries)
Product (Drop down – search text like ClientCRM – Customername)
(Search in ItemCode, Item Description)
GeneralDescription - Input
SpecialMarkings - Input
Quantity – Input

Agent Login

DashBoard
Orders Booked Customerwise / Productwise
Orders Pending Customerwise / Productwise
Orders Invoiced Customerwise / Productwise
Payment pending Customerwise / Productwise

Entry

Order Entry
Master
Customer – Input dropdown ( for the logged in Agent)
Sales Order No – Auto increment
Sales Order Date – Input
Purchase Order No – Input
Purchase Order Date – Input
Destination - Input
CustomerDeliveryDate - Input
SpecialInstructions - Input
Executive – Dropdown (for the selected in customer)
AgentCode – Logged in Agent
Get Product Details (Multiple Entries)
Product (Drop down – search text like ClientCRM – Customername)
(Search in ItemCode, Item Description)
GeneralDescription - Input
SpecialMarkings - Input
Quantity – Input

Reports

Reporting: Reports will be available, according to role, across functional areas and provide data that relates to business tasks, and can be filtered so that users can view only their own data.

Import / Export

Data Transfer: Transfer of data inside / outside the system

Settings

Application Settings: Customizing the application based on requirement needs

Security

Security is role-based. Roles (tasks that the user performs) determine the environments, transactions, and infotypes (screens) that a user can access and/or update. Roles can be either centralized or decentralized.

6. Solution Implementation

We are estimating the following major tasks in the implementation phase:

Getting familiar with development environment

During this phase, we plan to familiarize ourselves with the development methodologies and the various calculations required for the payroll process, documents to be used, database design etc.

Coding

This phase consists of coding the entire payroll module using the open source technologies. We suggest using PHP, MYSQL, Apache and Linux environment.

User Acceptance Testing

The application will be available in staging environment for three working days for entire testing.

Bug Fixing

The bugs discovered during UAT will be fixed and the application will be retested again to ensure that the reported bugs are addressed.

Delivery

The final product will be available for delivery.

Possible Extensions

This application can also be possibly extended in many ways based on the future requirement.

7. Client Responsibilities

Client will provide inexpensivecoders with complete requirement details for the application. Assuming that the above is the finalized requirement and if clarification raises during development it is the responsibility of both the parties to discuss and freeze to change or modify on technology constraints.

8. Project Deliverables

This project encompasses the following major deliverables:

Assessment and Inception Report
Development/redesign of module, Payroll module and Reporting module
Data integration and migration of and Payroll into EMIS database
Testing and Deployment
Documentation and training of the newly integrated systems

9. Timeframe for Expected Deliverables

The project is expected to be completed over a period of 4 Weeks starting from project kick off date. The indicative timelines for these activities, in number of weeks, is as shown in the table below. It is very important that project is completed within the proposed time in order to meet the deadline.

Activity	W1	W2	W3	W4
Database Design	●
Iterative development of the System	●	●
Data Importing	●
Documentation and Training	●
System pilot			●
Deployment and acceptance testing				●
System Go Live and Maintenance		●

10. Structure of the project team

The project requires a team of Four (4) key staff persons with professional

#	Expert Title	QTY.	Qualification	Relevant Experience(Years)	Expected Time of Engagement
1.	Project Manager	1	Bachelor in business administration, management or MIS (Master’s degree preferred)	At least 7 years’ experience in project management and information technology.	1 month
2.	Software Developer	2	Bachelor in Computer Science/IT	At least 5 years’ experience in software/database development and programming	4 month
3.	Tester	1	Bachelor any other relevant field	At least 1 years experiences in testing	2 weeks

11. Contact person from client’s side

The client would designate one of its technical consultant for the contact. This person would be responsible to interact with the inexpensivecoders consultant for administrative and technical matters on day to day basis; comment / approve the deliverables submitted by the consultant within the stipulated time etc.

12. Incident, Change, and Release Management

A lot of pieces must fit together seamlessly within a computer system (and to other systems) to guarantee success and long-term value. This includes incident management, change management and release management.

12.1 Incident Management

During development, the team will track all incidents affecting the development. Incidents may be events that do or have the potential to interrupt or reduce service, or requests for help in processing a transaction or clarifying system functionality. Incidents may be reported to the client or other stakeholders who interact with the development team.

An electronic tracking system similar to email, slack or skype may be used to manage incidents to completion. Incidents are prioritized for resolution, and may be transitioned to Change/Release Management process if they involve a change to the automated payroll development.

12.2 Change Management

System changes can affect multiple users, disrupt services, affect stored data, or involve hardware or software. To reduce risk, all change requests (CRs) are reviewed, prioritized, and tracked to completion. All change processes and workflows will be identified and severity levels will be assigned.

12.3 Release Management

Release Management (RM) is the process of planning, creating, testing, and implementing software releases. Developed automated payroll system will be frequently updated to ensure that it meets the technical and business requirements.

13. Deployment, testing, documentation and training for the newly integrated systems

Upon successful development and integration of the required application, the contractor shall propose a deployment plan, which includes the rolling out of the new modules and data migration of the production data. It also includes black box testing by EMIS department, proper documentation (technical and functional) and training of related departments on how to use and extend the system.

14. Quality Assurance and Quality Control

In order to ensure quality of the work, the consultant will ensure to submit the following reports:

Inception report
Work progress report before each payment
Final system report

15. The payment schedule

The payments to the contractor will be made into the following instalments:

Installment Number	Project Phase	Payment amount (%)
1	Advance	30%
2	50% Development completion	25%
3	100% Completion of development	20%
3	System testing by technical team and end users, installation in staging Environment.	15%
4	Submission and Acceptance of final Report on all deliverables	10%

16. Terms & Conditions

The proposal shall remain valid for acceptance for a period of 30 days from the date of submission
inexpensivecoders shall start the project within 7 days of receiving the confirmed order
The required information for project completion on time shall be provided by Client
The project shall be developed and executed on an offshore model.
All costs associated with any on-site visit required during implementation will be on Client
Master Data in pre-defined and agreed format shall be made available as per requirement
Additional work required beyond the scope will be charged additionally

Force Majeure and Time Delays: inexpensivecoders shall not be liable for any non-performance of this assignment provided such non-performance is occasioned by fire, flood, power failure / UPS breakdown, riots, lockouts, civil disobedience, act of God like floods, cyclone etc. and equipment failure/breakdown. (Unless arising out of improper / erroneous handling of equipment / software by our personnel).