Project Proposal

Supplier Price Quotation Capture System

1
 Table of Contents

Section Section Details Page No

A General Information 3
B Project Description 3
- Business Problem 3
- Project Business Objectives 4
- Core Business Activity Impacted 4
- Constraints 4
C Estimated Project Development Time Line 5
D Financial Estimate 6
- Cost Benefit Analysis Summary 6
- Estimate of software/Hardware Execution 7
Expenditures
- Estimate of Operations Expenditures 8
E Project Risk 9
F References 10

2
A. General Information

Supplier Price Quotation Capture

Project Project Working Title: SPQCS
Title: System

Project Management: PRIME TECHNOLOGIES MALAYSIA SDN BHD.

Prepared by: Mohan Kumar Date Prepared: 29th Jan 2011

Points of Contact
List the principal individuals who may be contacted for information regarding the project.

Position Title/Name/Organization Phone E-mail

Project Sponsor

Program Manager (if

applicable)
Project Manager (or
designee)

Customer (User)
Representative(s)

Other

B. Project Description
Explain the business reason(s) for doing this project.

Due to the competency in the market, products market price fluctuation in a short span of time will lead to an
inconsistency in sales for that product which in turn will affect the product’s profit margin values. In order to
increase and optimize sales, there is a need to have an effective system which will optimize supplier source, planning
and ordering action in an inventory control system.

1. Business Problem
The Business Problem is a question, issue, or situation, pertaining to the business, which needs to be answered or
resolved. Often, the Business Problem is reflected as a critical business issue or initiative in the organizations
Strategic Plan.

State in specific terms the problem or issue this project will resolve

The proposal is to develop SPQCS, as a web-based system with Microsoft .NET platform and MSSQL database.
SPQCS will have the following functionalities:

3
 1. Capture of price from time to time
2. Preparation of supplier quotation
3. Approval & Disapproval of Supplier quotation based on buyer
4. Reports
5. Personalized Reports based on Roles
6. User Management
7. User Profile Management
8. User Activity Log

2. Project Business Objectives

Define the specific Business Objectives of the project that relate to the strategic initiatives or issues identified in the Organizations
Strategic Plan for Technology . Every Business Objective must relate to at least one strategic initiative or critical issue.
Objectives should be explicit and measurable.

1. Systematically monitor selected supplier price movement & effective review of trading list price & margin.
Thus, optimizing supplier sourcing, planning & ordering action.
2. Pro-actively direct sales team to maximize buyers orders during limited grace period before impending
price hike. In so doing, sustaining trading margin volumes due to hedging against rising inventory
investment cost.
3. Streamline negotiation process and reduce paper work by optimizing computer usage for efficient price
information search, analytical reporting and improving work efficiency.
4. Enable systematic uploading of voluminous item price updates to current Purchasing System. Eliminating
manual purchase price entry with effective date.

Dateline 2010 – Initiative or Organizations Project Business Objectives

Critical Issue

3. Core Business Activity Impacted

Core Business Activities are cross-functional processes that produce the organization’s primary products and
services, or support the production of the products or services. List the Core Business Activities impacted by the
project and identify the impact.

Core Business Activity Impact on Core Business Activity

4
4. Constraints
Constraints are items that by their nature restrict choice. Identify Constraints that will influence the selection of a
solution to resolve the Business Problem. Constraints can include but are not limited to: time, funding, personnel,
facilities, and management limitations.

Example constraints
• Requirements are very high level
• There is a need for detailed requirement study to seek clarifications on the specifications required.
• There is a need for High level Technical Solution Design Document to estimate the timeline and effort.
• It needs be to be noted that the author of this proposal has based the estimations on his personal experience
and understanding of the specified broad objectives.

C. Estimated Project Development Timeline (Major Milestones)

Identify major Project Milestones for planning, execution, and closeout.

Referring to current Requirement document

Event Estimated Mandays Estimated Total Mandays

System study and Analysis

- Information gathering 1
- Process flow analysis 1 5
- RDBMS analysis 1
- User access and data security 1
- End user reports 1
Design

- Technical Design Document- High Level 2

2 7
- Ms SQL database design
- Web Page Design and Layout 3

Development

- Ms SQL database develop and testing 5

10 40
- Data Access layer development
- Coding on Functional processes 25

Unit Test 2

- Test Cases 1

5
 - Code coverage 0.5
- Code Analysis 0.5
Testing 5 5
Hardware / Software Installation 1 1
Integration with existing System 3 3
UAT 2 2
Project close out 1 1
Total estimated Man days 66

D. Financial Estimate
Provide an economic justification for the project based upon the Cost Benefit Analysis and the expected return on
investment. Identify the estimated funding resources required to complete the project and then identify the funding
requirements to operate or maintain the product(s) or service(s) developed from the project.

1. Cost Benefit Analysis Summary

Answer the following questions in the space provided. Attach detailed explanations and analysis as appendices which should
include identification, evaluation, and comparison of alternatives to the proposed solution.

a. Summarize the results of the Cost Benefit Analysis. Explain why the expected monetary and non-monetary benefits validate the
expenditure of resources for this project. Attach the Cost Benefit Analysis as Appendix A.

6
b. Summarize the results of the Return on Investment Analysis. If the project does not have a positive expected return on
investment, explain why this project proposal is being submitted. Attach the detailed Return on Investment Analysis as Appendix B.

7
2. Estimate of software/Hardware Execution Expenditures and Funding
Provide an Estimate of the Expenditures and Funding required for execution and close out of the project.

Estimated Expenditures ($000)

FY 2011 Total Comments
Internal Staff Labor
2000.0
Services 1 x 2000 0 Server Maintenance & Monitoring
1500.0
Software Tools 1x 1500 0 Optional Firewall software
6000.0 Dell Power edge T410
Hardware 1 X 6000 0 with SQL server standard licence
Materials and Supplies
Facilities
Telecommunications 1 x 618 618.00 Streamyx Internet with fixed IP address
Training
Contingency (Risk)
9500.0 Additional 618 per month for tmnet ipaddress
Total 0
This estimate is accurate to: 50% [ ] 60% [ ] 70% [ ] 80% [ X ] 90% [ ]
Explanation:

Anticipated (proposed) Funding Source ($000)

FY 200_ Total Comments

Equipment Trust Fund N/A N/A N/A

Technology Fee N/A N/A N/A

College Funds N/A N/A N/A

General Funds N/A N/A N/A

Federal Funds N/A N/A N/A
(Grants)

Other N/A N/A N/A

Total N/A N/A N/A

This estimate is accurate to: 50% [ ] 60% [ ] 70% [ ] 80% [ ] 90% [ ]
Explanation:

N/A

8
3. Estimate of Operations Expenditures and Funding
Provide an Estimate of the Expenditures and Funding for Operations and Maintenance of the asset(s) delivered upon
project completion.

Estimated Expenditures ($000)

FY 2011 Total Comments
Internal Staff Labor 2 x 66 x 500 66000.00 2 resources estimated cost
Services
Software Tools 2 X 1000 2000.00 Software licences
Hardware 2 X 2000 4000.00 laptops
Materials and Supplies
Facilities
Telecommunications
Training
Contingency (Risk) 1 X 5000 5000.00
77000.00 The price does not include the
maintenance of the project after
the project closed out.

After completion of the project

if source code to be handover,
then the cost will differ
accordingly.

Charges can be as much as

50% of the Development cost.

Total
50% 60% 70% 80% [X] 90%
This estimate is accurate to:
[ ] [ ] [ ] [ ]
Explanation:

Anticipated (proposed) Funding Source ($000)

FY 200_ Total Comments

Equipment Trust Fund N/A N/A N/A

Technology Fee N/A N/A N/A

College Funds N/A N/A N/A

General Funds N/A N/A N/A

9
 Federal Funds (Grants) N/A N/A N/A

Other N/A N/A N/A

Total N/A N/A N/A

This estimate is accurate to: 50% [ ] 60% [ ] 70% [ ] 80% [ ] 90% [ ]
Explanation:

N/A

E. Project Risk

Risk Item Risk Level Risk Score

External Dependencies Risk High (11–15)

Medium (6-10)
How dependent is the project on other 5
projects or work efforts? Low (1-5)

None (0)
Management Risk High (11–15)

Medium (6-10)
What level of risk does the organization’s 5
project management capability represent? Low (1-5)

None (0)
Mission Critical Risk High (11–15)

Medium (6-10)
How critical is the project success to the 2
success of the organization? Low (1-5)

None (0)
Failure Risk High (11–15)

Medium (6-10)
What is the risk of failure? 5
Low (1-5)

None (0)
Complexity Risk High (11–15)

Medium (6-10)
How complex is project? 4
Low (1-5)

None (0)

10
 Preliminary Risk Assessment High (73–100)

Medium (36-72)
What is the overall risk of the project? Total Risk Score:
Low (1-35) 21

None (0)

F. References

The First cut Requirement Document

11