Vendor and Consignment Contract Management 1a-V5 0

CHAPTER 1
1.0 PROJECT CHARTER

1.1 PROJECT BACKGROUND
1.1.1Problem/Opportunity Description
Update
- Updating contracts for contracted company who has satisfactorily
done their services throughout the contract duration.

New Contract
- For companies who will become a partner of the company
throughout the business.

Editing
- After the discussion of what will be the contents of the contract,
the contracted firm can give their own terms that they want to be
added to the contract.

Cancellation/Termination of Contract
- It is for contracted companies when the company decided not to
renew their services for the company.
1.1.2 Benefits
Effective Merchandising Business
Contracts made between the supplier and the company itself
gives a vital role to an effective merchandising business. It gives just
rights for both buyer and seller. They share a common goal which is to
gain profits and to prevent bankruptcy.
Establishing good relationship between partners

Building a good relationship between the business partners by
instilling into them how to become responsible business persons. To

avoid misunderstanding, terms and conditions must be given. Its a
good foundation in this kind of situation.
Uncomplicated contract making
Contract has a standard format, whenever making contract,
additional will be after meeting of the two parties.
Vendor and Consignment Contract Management
Page
Organized list of the contracted firms

New, renewed vendor, consignor is separated based on their
categories.
Secured data records
The contract made is handled by selected users only. But in this
case, even if theres a trusted person to handle the contract, they will
still notify the admin and ask for their approval before they do actions
with regards to the contract.
1.1.3 Goals
To come-up with a system that can create an organize and secured
data of contracts.
Updating/renewing contracts organizing the list of the contracted
firms based on their category to make the contract making hassle-
free.
A system that can securely keep records of the contracts and avoid
falsification and over-manipulation of the contracts.
1.1.4 Stakeholders and Clients

Stakeholder
1. Merchandiser,
Description/Participation
Supplier They makes-up the whole contract
and the company itself.
will be no transactions to be done.

They are the one whos purchasing the
2. Customers/clients.
3. Project
Business
realistic. Without one of them, there
goods/products.
Manager, The developers of the system. Studies
Analyst, the needs of the company to come-up
Vendor and Consignment

Contract
Management
with a worthwhile one.
System Analyst,
Lead
Programmer
Document Specialist.
and
Page
Table 1: Stakeholders and Clients and their participation
1.2PROJECT SCOPE
1.2.1Objectives
1.2.1.1 Work Breakdown Structure (WBS)
Page
Figure 1: Vendor and Consignment Contract Management

Work Breakdown Structure
Explanation:
The proponents created the Work Breakdown Structure of Vendor
and Consignment Contract Management. The main functionalities of
Page
Vendor and Consignment Contract Management are can create contract

for new suppliers, make cancellation of contract for suppliers who havent
satisfied the needs of the company, update/renew contract for suppliers,
edit the contract if theres a sudden change to the product name and avoid
conflicts, can determine who is the manufacturer of an outright product of
the company and can add new product to the contract.
1.2.2 Deliverables
To come-up with a system that can create contract for new
suppliers.
- For companies who will become partners all throughout the
business process.
A system that can update/renew contract for suppliers.
- For the continuation of their services for the business.
A system that can determine who is the manufacturer of an outright
product of the company.
- By the help of categorization the contracts will be separated
according to company.
A system that can generate report.
- This is for the releasing of the contracts (a copy for the contract
partner).
- Also for Evaluation of weekly, monthly and annual reports.
A system that can organize the list of the contracts based on their
status.
- The contracts will be separated by the use of status: new, renew
and cancelled/terminated. It is necessary for Evaluation.
1.2.3 Out of Scope

The contract contains the product information, but the responsibility
of checking the products is done by the other team.

Products to be delivered per month are stated in the contract but the
monitoring of the delivery is a responsibility of the other team.
Page
1.3 PROJECT PLAN

1.3.1Approach and Methodology
In this project, the proponents conducted an interview to variety of
persons who has knowledge to this. Reading related books in the library,
surfing the net and looking or sites where we can get reliable informations
of what and how the contract is made. The proponents also interview a
person who is knowledgeable with regards to the business contract. The
proponents is determined to complete this project and to be able to get into
that the proponents done researches and collected supporting documents
which had been the basis all through-out the project making.
Phases
Work Production/Description
Page
System Planning
The proponents create project duration

or timeline which will be the foundation of the
whole project making. It includes all the actions
to
be
done
on
specified
dates.
Setting
deadlines for the accomplishment of each task.

Doing task one at a time is necessary to
come-up
with
good
result.
Project
budget/costing is also included so that there will

be allocated budget in case needed.
The proponents conduct a research to
look
for
contract
sample
for
suppliers/merchandisers. It will be the basis of

the group to make a contract. What will be the
content of that specific contract and how the
System Analysis
process of agreement takes place.

After searching for informations and data
needed, the proponents have their consultation
meeting to discuss, get the opinions of each
member
and
decide
whether
these
informations will be used in the system

development.
Discuss the searched information of
each member. Think what of that informations
is needed, what is not, and what tools to be use
for the system making.
Study what are the possible problems
that the system will encounter during execution.
Why these problems occur, whats the reason
System Design
behind this and how the proponents will solve it.

The principle goal of the proponents is to
establish a design approach that can easily
Page
understand by the user. Wherein the user can

easily search the different manufacturer to know
how long the contract will last. Also to view the
System
content of the contract.

The stage of putting altogether the
Implementation
overall system. To test its capabilities, and

check errors or program failure during the
whole process. This is done to observe what
will went wrong and if the system will produce
unexpected results, to monitor its behavior,
because as expected problems arises in
System Maintenance
unintended ways.
A System once implemented doesnt
mean it all ends-up there. Having a fastchanging world out there gives everyone the
insight that everything changes in just a snap.
So everybody must know how to get along with
the trends.
It needs a continuous attention and
evaluation to know its working capabilities as
well as to check the whole system performance.
The main goal is to recover errors,
update informations, monitor the performance
and enhance the system transactions/process.
To prevent the system from being obsolete, one
must compete with others to be not left behind.
Table 2: Approach and Methodology with description
Page
1.3.2Project Timeline
Page
I
D
1
2
3
4
5
6
7
8
Task Name
Start
Group meeting
(Planning)
06/24/14
06/24/2014
2 hours
06/28/201
4
06/28/2014
4 hours
07/01/201
4
07/01/2014
1 day
07/04/2014
1day
07/07/2014
1 day
07/09/2014
1 day
07/10/2014
1day
07/12/2014
1 day
07/14/2015
1day
07/18/2014
1 week
07/29/2014
1day
07/25/2014
1 week
07/26/2014
1day
07/31/2014
3 days
08/01/2014
1day
08/02/2014
1 day
08/08/2014
1 week
08/09/2014
08/15/2014
1 day
1 week
08/16/2014
1 day
09/05/2014
3 weeks
09/05/2014
1 day
09/12/2014
1 week
09/13/2014
1 day
Overall meeting
(4th yr BSIT)
Group meeting
with
other
groups
Group Meeting
(brain storming
about system)
Look/Search for
Adviser
Adviser
is
selected
Group Meeting
with head PMs
Meeting
with
Adviser
PM divided the
group work for
each member
Conduct
a
Research
07/04/201
4
07/07/201
4
07/09/201
4
07/10/201
4
07/12/201
4
07/14/201
4
07/15/201
10
4
07/19/201
11
Group Meeting
4
Conduct
a
07/21/201
12
Survey
4
07/26/201
13
Group Meeting
4
Conducted
a
07/28/201
14
Interview
4
08/01/201
15
Group Meeting
4
Group Meeting
08/02/201
16
with Adviser
4
08/04/201
17
Project Charter
4
08/09/201
18
Group Meeting
4
19
Chapter 2
08/11/2014
08/16/201
20
Group Meeting
4
08/18/201
21
Chapter 3
4
Group Meeting
09/05/201
22
with Adviser
4
09/08/201
23
Mock Defense
4
09/13/201
24
Group Meeting
4
Revision
of
Chapter 1 and
09/15/201
9
Finish
Duration
Page
Table 3: Project Timeline of the Proposed System

1.3.3 Success Criteria
Having this Vendor and Consignment Contract Management System
can be a great help for both partners. It will ease the contract making
whenever the company makes agreements. This will make the contract
management less complicated because of its capabilities of securing the
data records of contracts. Making organized list of each contract by setting
status for it. These will make handling contracts much easy yet secured.
1.3.4 Issues and Policy Implications
This Vendor and Consignment Contract Management System could
really affect the flow of business matters between both sides in a good way.
Both consignor and consignee will both benefit by the said scheme. This
will be easy for them to have a contract relying on this system. It also
lessens the paper works in creating the contract.
1.3.5 Risk Management Plan

Risk Factor
Probability
Impact
Risk
Management
Page
(H-M-L)
(H-M-L)
Members Risk
Action
Making
sure
that
everyone will attend the

meeting so no one will
M
be
left
behind
with
regards to the project

Development
updates.
Setting alternatives for
Risks
future problems to be
M
encountered during the

overall project making.
Financial Risk
Implementing funds so
that there will be a
H
source of income for

future and emergency
purposes.
Setting
dates
Availability Risk
for
activities to be done in
M
advance to be able to
manage the availability
of the group.
Gather
informations
Company Risk
through
internet. And
read related books to

broaden more the said
H
informations gathered.
Also
talk
to
knowledgeable
people
to be able to fill the
Hardware
Capability Risk
informations needed.
Finding alternatives of
how
to
gather
Page
necessary informations.
Table 4: Risk Management of the Proposed Project

1.3.6 Service Transition
The role of the contract is to secure and prove the agreement
between two who has the same goal. So, if ever theres a
sudden change to be done with the agreement, the two parties
have to meet first and discuss it.

If ever the consignor cant supply the products needed to his
consignee, the consignee must have other options of suppliers to
be able to fill the insufficiency of products.

The agreement happens between the two parties. The basic
holder is the consignor but the one who has the great power in
them is the consignee/vendor but they have to coordinate,
communicate, and cooperate with each other to make better
services.
The vendor/consignee coordinate with the consignor for the
products and the consignor coordinate with the consignee for the
products sake.
1.3.7 Option Analysis

During the discussion of the agreement to be done. The two parties
will tackle their specific concerns throughout the partnership. What will
be the standards and quality assurance of the products? Its a must to
know it, to be able to have a good growing business. In the process,
cost will be reduced. Cost will be reduced in the form that the making of
Page
the contract is computerized, so the printing of documents every now

and then will be lessened.
1.4 Technical Features
The proponents decided to use Net beans as the front-end and MSSql for
the database. The software can give product and manufacturers information
by the use of search engine. The system can update the contract and can
preview the whole content of the contract. The system has a very simple
interface and is not complicated to use and reduces paperwork by keeping
efficient electronic records.
1.5 Project Organization and Staffing
Role
Project Manager
Responsibilities
Serves as the head that has the responsibility
of leading the team.
Business Analyst
Distributing the task to every team member.
Providing techniques to make a satisfying
project.
Analyzing the business rules as well as the
problems to be encountered.
Maintain control over important business

concerns.
System Analyst
Making key business decisions.

Making effective solutions to the business
concerns.
Lead Programmer
Constructing plans of the project making.
Evaluating the needs of the customers.

Designing the program features.
Coding of the program.
Maintaining technical aspects.
Security of informations.
Page
Document Specialist
Adviser
Assurance of the data accuracy.

Providing written and printed reports.
In-charge in filing datas.
Analyzing changes in files and records.
Organizing data records.

Guide throughout the project making.
Reviews the documents.
Explains some of the things to be done in the

project.
Project
Shares knowledge towards the project.
Provides techniques to ease the project
Evaluation
development.
Teaches and explains the procedure of the
Committee (PEC)
project making.
Evaluator
of
the
on-going
project
development.
Checks the updates of the works done.
Guide for the project study preparation.
Provides opportunity to every group to create

an original work.
Table 5: Project Organization and Staffing

1.6 Project Budget
Budget Item
Description
Budgeted Cost
One-time cost
Project Manager
System Analyst
Project Head that will lead

the project making.
Analyzing
the
process.
System
350,000.00
250,000.00
Page
Programmer
Network Analyst
Cable
PC
Total one-time cost
On-going cost
Broadband
Computer rent
Total on-going cost
Program making.
Network Connection.
System use.
Internet Access
Internet Access
100,000.00
30,000.00
10,000.00
20,000.00
760,000.00
50
10
60
Table 6: Project Budget
CHAPTER 2
2.0 Related Literatures
2.1 Foreign Literature
2.1.1 Global Sourcing Development at IKEA
This study explores the dynamic process of global sourcing
development through a case study of the Swedish home furnishing giant
IKEA and its supply network concerning the PAX wardrobe system. The
paper provides a synthesis of the existing global sourcing literature by
dividing this growing body of research into three major themes:
globalization processes and stages, motives/drivers, and organizational
design and management. Moreover, the paper integrates the global
sourcing literature with the established literature on the internationalization
process of firms. Comparing the existing research on global sourcing and
internationalization, we propose two research questions focused on: (1) the
Page
ways in which the IKEA global sourcing and supply chain development
process resembles a linear stages process, and (2) the principal drivers of
the development of global sourcing within IKEA. Relating the findings of the
global sourcing process in the case of IKEA, the paper suggests that the
process does not fit the linear and incremental stage processes as
suggested in the majority of global sourcing literature, but rather fits the
interaction and network process model as suggested in the network school
of internationalization.
(Source: http://www.ikea.com/)
2.1.2 The Contract Companies
The Contract Companies was established back in 1983 as a
national outbound business-to-business call center which provides a
marketing campaign/service to physicians and business owners across the
United States. We currently employee close to 100 sales executives who
have the capacity to reach out and communicate to 400 plus clients and
potential advertisers per representative per day. We have the ability to
cover an enormous amount of area every single week. Our success over
the years can be attributed to our sales staff which directly communicates a
brief, but extremely effective presentation with the specific physician and/or
decision-maker in a 6- to 7-minute time frame. Over the years, we have
spent close to 5 million dollars acquiring and maintaining our existing
database of 12 million plus potential customers. It contains every physician
by specialty, and every business owner in the country. We currently receive
quarterly updates to ensure the accuracy of our client list. With our
proprietary software, we have the capacity to be as broad or as specific as
necessary. We have two state-of-the-art facilities with built-in redundancy
into our hardware and VOIP phone system to ensure zero downtime is ever
experienced. The Community Focus Online division of The Contract
Companies evolved as a spinoff of the Business Review division. After 24
years of working with more than 1,500 newspapers across the country, we
have transitioned to the Internet by partnering with major chambers of
commerce as well as prominent local Web sites nationally to bring an
Page
incessant marketing campaign for our doctors and business owners.

Contract Medical, our fourth division, was created to assist doctors in
saving money on various items purchased for their individual practice as
well as help create and implement additional revenue opportunities. We are
a very experienced marketing company equipped with a professional sales
team capable of handling any and all direct sales campaigns. Our
Publisher Relations department is available to business owners and
marketing teams to discuss the benefits of the Community Focus Online to
market your goods and services. The Fundraising division of The Contract
Companies is a direct sales operation that presently carries ongoing
campaigns to raise funds for five different Charities and Non-Profit
Organizations. This is accomplished via direct donation campaigns and
advertising sales.In order to operate more efficiently and stay competitive,
our state-of-the-art in-house graphic arts department provides high-quality
designs and camera-ready art for all of our ongoing projects.
2.1.3 Contract Management for International EPC Projects
We have been allotted seven weeks to work on this project, and
during this period we are going to review their project, while trying to
develop qualitative and quantitative methods to assess and control the
project risk. We will be making regular visits to the company to conduct
research. With the information gathered, we will begin to formulate means
of measuring risk. By the end of our project, we aim to have completed a
review of their project along with methods that help measure and control
the projects risks. In order to accomplish our goal, we interviewed company
personnel and analyzed the data that was gathered. The company
personnel that we interviewed were top managers who were directly
involved with the Saudi Arabia project, we were not able to interview the
labor force because they were unable to be contacted. In order to fully
optimize contract risk management, we also researched the four
international delivery systems, which consist of contract management
processes and systems, risks involving contracts, and performance
evaluation methods.
Page
With the completion of this project we were able to analyze the

contracts life cycle along with determining the main elements of risk that
should be taken into account during each specific phase. The individual
risks were analyzed in greater detail to provide a more comprehensive
evaluation. After the life cycle was analyzed we proceeded to analyze the
SCCSs legal department. Seeing as how the Saudi polyolefin project was
their first international project, they had no experience and little knowledge
of international contracts and laws. This led them to hire other consulting
firms to handle this work for them. Through our analysis of their legal
department, we decided on two recommendations that we determined to
be plausible. The first recommendation consists of recruiting or training law
personnel who specialize in international regulations and laws. Once the
law personnel are acquired the next recommendation we opted to have
was to create a legal department focused on international projects. Lastly,
a performance evaluation was established based on the Fuzzy-AHP
(Analytical Hierarchy Process), which helped combine various criteria to
help evaluate individual workers performance. This method allows the
combination of qualitative and quantitative methods to help analyze the
workers performance.
2.1.4 Contract Management on Microsoft SharePoint Server 2007
Nowadays, most organizations have already recognized the
importance of managing information and knowledge as they realize that
this is their big opportunity for accelerating business process, improve
employees, working efficiency and cost saving etc. The management of
knowledge includes acquiring or creating knowledge, transforming it into a
reusable form, retaining it, and finding and reusing it. Large organizations
have difficulties in finding and reusing knowledge. Sometimes, even
determining if the knowledge exists within the organization can be difficult.
Digital technology seems to be an obvious way to improve enterprise
knowledge management. Information that is represented digitally and
placed on an intranet can be accessed by anyone in the organization any
time. Enterprise document management is often viewed as a component of
Page
enterprise content management and related to digital asset management,

document
imaging,
workflow
and
record
management.
Document
management is the process of handling documents in such a way that

information can be created, shared, organized and stored efficiently and
appropriately. (Source: http://www.contentmanager.eu.com/)
2.2 Local Literature

2.2.1 Orienge Contract Management
The project was aimed at automating contract approval processes.
To be reviewed and approved by CEO, a contract (its printed copy) had
to go first through 8 to 12 departments, located in three different city
districts, and collect the required signatures on its read and understood
page. So, on average, the approval process lasted for about 45 days per
one contract. The same went for invoices and deeds approval. With about
5,000 new contracts per year, the existing procedure caused multiple
harmful effects such as negative business image, inability to locate the
required contractual document, document losses, different fines and
penalties, a significant increase in the total cost of ownership for the
process, etc.
To overcome the existing problems, a good Enterprise Content
Management system was needed. Having analyzed and compared four
different ECM systems the company chose the solution with the richest
functionality for a better price. Another important factor taken into account
was the agility of the system, as the company planned to retain the core
logic of the existing business processes.
Page
The project included creating electronic contracts archive, regulating

contracts registration, as well as automating approval and other contractrelated processes. The professional implementation strategy was applied,
so the ECM system was configured according to specific customers
requirements and implemented by the integrators employees.
To simplify the solution configuration, different process roles were
created, which allowed system administrators to easily appoint employees
for various approval actions. According to the companys business
processes, four standard routes for approving various contractual
documents were configured. From that moment users did not have to know
the exact person to approve the contract: all they had to do was to select
the required standard route and leave the rest to the ECM system. The
responsibility matrix, elaborated to comply with the companys internal
regulations, ensured correct approvers selection.
As one of the companys requirements was having detailed and
structured information on contracts, 37 databooks and dictionaries of
diverse complexity were developed in addition to the existing ones.
Electronic contract card was equipped with multiple attributes, which
substantially simplified the processes of preparing orders and approval
forms, gathering statistics, searching for contracts and controlling their
processing. A variety of new reports allowed users to collect and analyze all
sorts of information on contracts from different databooks. The approval
forms with information on contract conditions, approvers, time of approval
and digital signing were now generated automatically.
In cooperation with SAP specialists, the ECM system was integrated
with SAP R/3 and SAP HR solutions, which enabled data interchange
between the systems.Prior to the pilot operation stage, corporate contracts
archive had been created; and the process of contracts creation,
registration and approval had been launched.Contract automation has
been a success. All departments involved in the process now work in the
Enterprise Content Management system, approving contracts and the
related documents electronically. Printed copies are no longer sent from
Page
one office to another. Risks of document loss have been eliminated. The
approval process has been accelerated by 37% and more: 28 days
approval (compared to the initial 45 days) is now an absolute maximum.
Transparent workflow and enhanced supervision possibilities ensure timely
contract commitments fulfillment; thus guaranteeing against fines and
penalties, and improving the business image of the company. The ultimate
total cost of ownership for the contract approval process has dropped.
(Source: http://www.orienge.com/contracts-case1)
2.2.2 Enzine Inc.

Contract Management encompasses all the activities that an enterprise
or an individual engages in, while entering into a business transaction with
one or more trading partners and fulfilling all the obligations of the terms
and conditions agreed upon on the contract.Almost all the transactions that
occur in the business world are governed by a contract is some shape or
form. Some of the common examples of contracts we deal with in our dayto-day life are employment letters, sales invoices, purchase orders, utility
contracts.Contract management is the process of managing of all aspects
and phases of any and all contractual agreements including the creation of
certified, professional contracts that meet legal directives, supply
categorization and systematization in contracts, etc.Contract Management
is the total arrangement of transactions of an individual or a venture.
Contract management covers the most basic operation to the most major
decision occurring between two or more identities in the business. Even the
simplest individuals who are just leading an average living engages in a
contract management in the form of the receipts of every purchase they
make, the tickets they use in transportations, the warranty of the
appliances or gadgets they have bought.
Page
A contract management system facilitates coordination, reporting, and

monitoring of multiple business processes and partners throughout the
supply chain. The strength of contract management tools lies in
automation: streamlining the management of each contract through its
entire lifecycle, including the stages of planning, negotiation, storage,
maintenance, and analysis.
Contract Management is the creation and maintenance of trading
partner relationships in a structured format. Today's complex trading
relationships involve multiple business processes and business partners
throughout the supply chain. Inherent in these relationships are complex
language and terms governing many factors such as price, shipment,
payment, quality, volume breaks, rebate policies, discounts, and so forth.
Managing all of this, especially if you have thousands of relationships and
contracts that change on a frequent basis, requires a serious commitment
of time, and resources.
Ismael
D.
Tabije
is
the
Publisher-Editor
of
www.BestManagementArticles.com
[http://www.BestManagementArticles.com], a unique niche-topic article
directory that features exclusively business and management topics. For a
large dose of contract-management tips, ideas and strategies, see
contract-management.bestmanagementarticles.com.
http://ezinearticles.com/?Contract-Management&id=367734
2.2.3 Razon-led Bloomberry Resorts Corp
MANILA, Philippines - Razon-led Bloomberry Resorts Corp., the owner
of the $1.2-billion Solaire Resort and Casino, has sacked its casino
manager and a key executive for breach of contract.
Page
The management shakeup came just six months since the opening of
the casino complex, whose revenues have yet to catch up with high
operating expenses.
Bloomberry and its operating subsidiaries Sureste Properties Inc. and
Bloomberry Resorts and Hotels Inc. said they have terminated the
management service agreement (MSA) with Global Gaming Philippines
LLC (GGAM) because of material breach of the MSA by GGAM.
GGAM has not spent any material time in attending to the
management of Solaire and has failed to perform its obligations and
deliveries under the MSA, Bloomberry said in a disclosure.Bloomberry
said it is eyeing an experienced casino hotel executive to replace Solaire
chief operating officer Michael French, the official representative of
GGAM.Following the shakeup, Bloomberry said Solaire will be operated by
several members of the existing management team that are very
capable.For its part, GGAM said it did not violate the agreement with
Bloomberry.Bloom berrys assertions regarding GGAMs performance of
its obligations under the MSA have no factual or legal validity, the casino
manager said in a statement.Bloomberry has materially breached that
agreement and GGAM is pursuing its rights under that contract in
arbitration in Singapore, it added.GGAM is led by three principals who
each have decades of integrated tourism resort and gaming industry
experience, a substantial portion of which were in senior management
positions with Las Vegas Sands in the US and Macau. Late last year,
GGAM exercised its option to acquire 921.18 million Bloomberry shares at
a sharp discount. The purchase of an 8.7-percent stake, which allowed
GGAM to become the second-biggest shareholder of Solaire, aligned the
interest of GGAM with those of the owners of Solaire.The $750-million
Phase 1 of Solaire, which offers 500-rooms, 18,500 square meters of
gaming space and 15 luxurious dining options, started commercial
operations on Mar. 16.
Page
http://www.philstar.com/business/2013/09/14/1207211/bloomberrysacks-solaire-manager-contract-breach
2.2.4 San Miguel Corp.
MANILA, Philippines - Diversified conglomerate San Miguel Corp.
remains interested in operating and maintaining the 218-megawatt Angat
hydropower plant in Bulacan despite thorny issues that continue to delay
the turnover of the facility to its foreign partner, K-Water Resources Corp. of
Korea, its top official said.The Power Sector Assets and Liabilities
Management Corp. (PSALM), the government corporation tasked to
privatize state-owned power assets, said there are still issues being
addressed before the deals final closing. There are pending issues
preventing closing, PSALM president and chief executive officer
Emmanuel Ledesma, Jr. said yesterday. He declined to elaborate on the
issues but said PSALM is targeting to close the sale by Sept. 1.
He also explained that the lower purchase price of the facility is due to
the capacity testing of the plants main Units 2 and 4 as provided under the
sale agreement. Business (ArticleMRec), pagematch: 1, sectionmatch: 1 KWaters bid lowered to $439 million from the original $440.88 million in
2010, data from PSALM showed. PSALM sold the plant to K-Water which
is working on securing a $500-million bridge loan from the Korean Exim
Bank for the takeover.
PSALM issued the certificate of effectivity (COE) to K-Water in
September last year and had targeted to close the sale within 270 days
from the issuance of the COE. It conducted a bidding for the facility in
2010. K-Water topped the bidding but was unable to take over the plant
due to thorny issues including court hurdles raised by non-government
organizations (NGO) on the foreign takeover of a power asset.
Page
The Supreme Court last year upheld the privatization of the power plant
but K-Water had negotiated with the government for a lower price tab on
the facility, saying it wanted the same level of benefits expected in its 2010
bid. The privatization of Angat, once completed, would be the first
successful power asset sale under the Aquino administration, as mandated
under the Electric Power Industry Reform Act of 2001. K-Water is optimistic
that its investment in Angat is only the beginning of future projects in
hydropower.
http://www.philstar.com/business/2014/08/30/1363196/san-miguel-stillkeen-angat-contract
2.2.5 Renewable Energy

In an effort to promote and encourage the utilization of renewable
energy resources and to accelerate the exploration and development of
renewable energy (RE) resources, the Congress of the Philippines passed
Renewable Energy act of 2008 (Republic Act No. 9513) on 16 December
2008.
To further promote the development of RE projects/systems (i.e., those
which convert RE resources into useful energy forms like electrical,
mechanical etc.), the law provides for substantial incentives to interested
entities. Under the same law, the Renewable Energy sector has been
declared a priority investment sector that will regularly form part of the
Philippines Investment priority Plan (IPP) so that all entities duly accredited
by the DOR under R.A. 9513 will be entitled to special incentives
Page
2.3 SYNTHESIS and MATRIX
System
Global
Sourcin
g
Develop
ment at
IKEA
Contrac
t
Manage
ment for
Internati
onal
EPC
Projects
The
contract
compan
ies
Contrac
t
Manage
ment on
Microso
ft Server
2007
Orienge
Contrac
t
Manage
ment
Enzine,
Inc.
Can
create
contrac
t for
new
supplie
rs.
Make
cancellation
/
termination
of
contracts.
Renew/
update
contracts
for
suppliers.
Edit
the
contract.
Determine
who the
manufactu
rer of an
outright
and
consigned
product is.
Can add
new
product
to the
contract.
Mobile
applicat
ions.
Razon-
Page
led
Bloomb
erry
Resorts
Corp.
San
Miguel
Corp.
Renewa
ble
Energy
Puregol
d
Table 7: Comparative Matrix

Synthesis:
The special feature that the proponents will add is the android application.
It will be specially designed for this project. Unlike anybody else, because Vendor
and Consignment Contracts are confidential files held only by specified persons,
the android application to be made will be for the convenience of the handlers of
the contract (managers). Our generation as of now is very fast, the demands and
needs of the people also changes, so the proponents will make this application to
be able to cope-up. Contracts are mostly saved to the computer, so if ever
needed, the manager has to open the computer first to be able to view the
contract. But now, the proponents decided to take this contract wherever with the
manager by just using android phones. Every literature gathered has its own
capabilities. The other has and the other did not. So the proponents decided to
get all of the features stated and put it all together to make such difference.
Page
3.0 CHAPTER 3 - EIS PROJECT MANAGEMENT AND DEVELOPMENT

3.1 RISK MITIGATION, MONITORING AND MANAGEMENT PLAN
3.1.1 INTRODUCTION
3.1.1.1 Scope and intent of RMMM activities
The goal of the risk mitigation, monitoring and management plan is
to identify as many potential risks as possible. To help determine what
the potential risks are, the project will then be analyzed to determine
any specific project risks. When all risks have been identified, they will
then be evaluated to determine their probability of occurrence, and how
intense it will be affected if they do occur. Plans will then be made to
avoid each risk, to track each risk to determine if it is more or less likely
to occur, and to plan for those risks if ever they occur. It is the
organizations responsibility to perform risk mitigation, monitoring, and
management in order to produce a quality product. The quicker the
risks can be identified and avoided, the smaller the chances of having
to face that particular risks consequence. The fewer consequences
suffered as a result of good RMMM plan, the better the product, and the
smoother the development process.
3.1.1.2 Risk management organizational role
Each member of the group will undertake risk management. The
development team will consistently be monitoring their progress and
Page
project status to identify present and future risks as quickly and

accurately as possible. With this, the members who are not directly
involved with the implementation of the product will also need to keep
their eyes open for any possible risks that the development team did not
spot. The responsibility of risk management falls on each member of
the organization.
3.1.2 FUNCTIONAL DATA DESCRIPTION
3.1.2.1 Risk Table
Category
Members Risk
Risks
Lack
Development
knowledge.
Not
always
Risks
Financial Risk
resources is there
Lack
of
financial
Availability Risk
support.
Members
Company Risk
always present.
Not
always
of
members
the
are
company
not
Probability
Impact
25%
10%
20%
10%
20%
15%
the
gives
necessary information.
Capability
of
the
Hardware
Capability Risk
computer hardware.
Table 8: Risk Table

Table Risks Table (sorted)
Impact Values
Description
Catastrophic
Critical
Page
Marginal
Negligible
3.1.2.3
Description of Risk m
3.1.2.4
Probability and Impact for Risk
3.1.3 Risk Mitigation, Monitoring and Management

This section in detail describes Risk Mitigation, Monitoring and
Management for each of the possible risks. It will talk about ways to
avoid, monitor and to have ways to manage the risks.
3.1.3.1 Risk Mitigation
In this section several different software development risks
will be identified, a plan will be created to avoid these risks. We
will think of the way to keep the software development process
from encountering these risks. It is important to have mitigation
plan to avoid risks once and for all. Goal is to attack the risks
even before it comes into existence. The plan will help in
identifying the possible risks and to monitor them.
3.1.3.2 Members Risk
This risks concern in the knowledge of each member to help
the proponent to develop a system is involved. Proponent will
make sure that each member was know the phases while
developing a proposed system and learn the programming
language to avoid failure that may cause big problem in
implementation of the system.
Page
3.1.3.3 Development Risk

The proponent must provide all necessary equipment for
developing a system to avoid this risks the proponent will make
sure that the budget is included to provide a high quality of the
system and to achieve the objective of the proponent.
3.1.3.4 Financial Risk
If the proponent has no budget to develop a system it can cause
failure. Money is very important to develop a system because every
action has money involved unfortunately the proponent has only 5
members that can cause financial shortage.
3.1.3.5 Availability Risk
In this risk the proponents time and availability is concerned
because each member has a different activity that can cause absent in
a meeting or grouping it is also concern in the knowledge of each
member to develop a proposed system.
3.1.3.6 Company Risk
If the company doesnt participate to help the proponent to
develop a proposed system the proponents fail to know what the
problem with the present system. Clients also need to mention
all operation in contract management.
3.1.3.7 Hardware Capability Risk
This risk will focus on the computer to be use to develop a proposed
system if that computer is not updated there are probability to hardware
failure.
Page
3.1.4Risk Monitoring
In this section the proponent will identify the conditions to monitor to
determine whether risk m is becoming more or less likely.
For monitoring phase during the development of the
proposed system the proponent will keep eye on each other to
know if some member is having difficulties in performing the
assign tasks in desire time of the proponent.
For monitoring phase during the development of the
proposed system the proponent will keep an eye on equipment
being used and their effectiveness. The proponent also looks for
availability of the equipment to be use.
3.1.4.3 Financial Shortage
To monitor this risks the proponent will keep communication each
other to be ready and to know the needs while developing a proposed
system and that has money involved.
3.1.4.4 Availability of the Proponents
To monitor this risk the proponent will keep track the all activities of
each member to know if the member was following the plan of the
proponent to avoid rushing of assign activities of each member.
Page

To monitor this risks the proponent will keep communication
to the company to help the proponent to know the needs of
system.
3.1.4.6 Hardware Capability

To monitor this risks the proponent must search a good computer or
laptop to be use for developing a proposed system and know the
capability that can handle the Java programming language and MS
SQL in database.
3.1.5 Risk Management
In this section the proponent will identify several different software
development risks and will try to create a plan to manage these risks if they
do occur.
To manage this risks the proponent need to help each other.
If one of the members is lack of ability to use a Netbeans other
member will take some time to teach him or her to understand
the whole process of proposed system.
If the proponent fails to provide necessary equipment for
developing a system the proponent will reschedule the phases of
software to provide more information on different equipment to
be use.
Page
3.1.5.3 Financial Shortage

The proponent must have a fund or budget while developing a
proposed system. The proponent must collect every week at least 10
pesos to each member to provide efficient money and provide the
needs of the project.
3.1.5.4 Availability of the Proponents
The proponent will keep contact each other to know the schedule of
each member or the proponent will do a project timeline that can help to
manage the schedule while doing a proposed system and avoid
rushing.
If the company cant communicate with the proponent because of a
heavy schedule one of the member will pass a questionnaire to the staff
of the company to answer all needs of a company to be develop by the
proponent.
3.1.5.6 Hardware Capability Risk
After monitoring for all features of Java Programming and MS SQL
the proponent will provide a laptop that can handle and support the all
features of Java Programming and MS SQL to failure while developing
a proposed system.
Page
3.2 SOFTWARE CONFIGURATION MANAGEMENT PLAN

3.2.1INTRODUCTION
During the time of the software development the proponents will be
making changes to the original plans. Software Configuration Management
Plan is developed so that the proponents can identify the change, control
the change, make sure the plan is implemented correctly and make sure
that change will be reported to persons concerned.
3.2.1.1 SCOPE AND INTENT OF SCM ACTIVITIES
The main purpose of the SCM is to make, report and track changes
made to the original software development plan. It is done throughout
the whole project development process to help the proponents keep
track of the changes. The SCM procedures will guide the proponents on
how to make the changes relatively easy whenever needed so. With
this, the proponents have to take so much time to report those changes
that they think is necessary to others.
SCM activities are developed to:
Identify change.
Control change.
Ensure that change is being properly implemented.
Also have a way to document the change.
3.2.1.2 SCM ORGANIZATIONAL ROLE

Having a small software development team, each member will be
given the task to work with the software configuration management. It is
necessary to jot down the changes to eliminate confusions towards the
proponents with regards to the software changes. If one of the member
Page
reports changes, all the other remaining members has now the job to
authorize the given changes, this is to ensure that the changes are
properly implemented. Eliminating confusions is the primary goal of
SCM.
Once the clients discussed about it and decided to go on with the
change, then and only then the changes will be implemented. The said
changes will be noted in a specific section together with the original
plan so that the proponents will have a hold of why those specific
changes were done. it is made for the users convenience, the
proponents will report and document all the changes so that the client
will have access to it after the software is packed and delivered.
3.2.2 SCM TASKS
In this section, the proponents will detail all important SCM tasks and
will assign responsibilities for each. The members will be given each task
for the software development. One of the proponents will keep in touch with
any of the clients side to inform all the changes that will happen. All of
those changes that will affect the user of the software will be discussed
with the entire team together with the clients team during meetings.
3.2.2.1 IDENTIFICATION
In this section, the proponents will describe how the software
configuration items will be identified for the SCMP.
3.2.2.1.1 Description
Identify the change
- If during the software development phase, a team member
suggests a change to the software, then the proponents have to
discuss whether the said change is necessary.

Approve change
The proponents want to make things organize and avoid conflict
within the system development as well as between the team
members. So the proponents have to set rules that will give just
rights to all team members. By these, no member will think of
Page
changing or implementing change without the approval of the

other members. The whole team must be one in the decisionmaking to avoid technical problems.
Ensure that the change is properly implemented

Mistake at times will never be prevented. So all the team
member is responsible to look over the change its co-member
makes, to finalize the change before implementing it.

Document the change
Change has to be documented every time the suggested change
from a team member was finalized.
3.2.2.1.2 Works products and documentation

Identify change.
Control change.
Ensure that change is properly implemented.
Document the change.
3.2.3 CONFIGURATION CONTROL
3.2.3.1 Description
The change will be controlled by using the teas awareness of what
procedure to undergo and the tools to be used. Under are the steps
provided to be able to control the change:
Report/Request change.
Evaluation of the request by the developer.
Finalization of the said change.
Approval of the change.
Implementation of the change.
Document the change.
3.2.4 VERSION CONTROL
3.2.4.1 Description
3.2.4.2 Increasing Version Number
When a change request is filed, a change report will be created.
After the change was finalized, it will be documented.
<major update>.<minor update><bug fix>
Page
3.2.4.3 Work Products and Documentation

3.2.5 CONFIGURATION STATUS ACCOUNTING (CSA)
3.2.5.1 Description
3.2.5.2 Work Products and Documentation
Help-desk.
Change request report.
email
3.2.6 SOFTWARE QUALITY ASSURANCE OVERVIEW
SCOPE AND INTENT OF SQA ACTIVITIES
REVIEWS AND AUDITS
3.2.6.1 Generic Review Guidelines
Management Responsibility
Quality System
Contract Review
Design Control
3.2.6.2 Conduction a Review
There will be two kinds of review to do, its with the client and the
other is with the teammates.
Consulting the changes to the client is a must because they
will be the one affected. Keeping records of the changes before and
after it is done.
3.2.6.3 Roles and Responsibilities
As stated in 1.2, SQA Organizational Role, the task of each member
seems confusing.
Project Manager/Head developer: Alfred Perido
Programmer: Alvin Jan Trinidad
System Analyst/Software designs: RonnelCaramoan
Architectural Plan: Larissa Alcantara
Document Specialist: Carmela Padua
3.2.7 FORMAL TECHNICAL REVIEWS
Here are the FTR that the proponents will conduct during the software
process:
Page
Walkthroughs
Inspections
After each form (interface) designed, the proponents will do a test by
doing an inspection to the interface. This will be done to all the interfaces.
3.2.7.1 Description of review Walkthroughs
Description and focus of Review
This review is mainly focus on the design integrations. The
proponents will ask some of the other member to do the walkthroughs
with the help of the encoder.
3.2.7.2 Description of review Inspection
Description and Review Inspection
This review mainly focuses on the correctness of the design. The
members will do such tests on this to evaluate its appropriateness.
3.2.7.3 System Specification Review
The system specification change usually happens during every
proponents meeting. But as of now, the proponents are settled on the
system design made. Even the proponents have expended the project
into a higher level; the basic mapping of the project is still there.
3.2.7.4 Software Project Plan Review
The main purpose of Software Project Plan is to look over the whole
Project Development. For further explanation, please see the document
titled Software Project Plan.
3.2.7.5 RMMM Review
RMMM, Risk Mitigation, Monitoring and Management Plan is use to
analyze the risks to be encounter and how to handle those risks. For
further explanation, please see the document titled RMMM.
3.2.7.6 Requirements Review
Software Requirements explains the data requirements and
specifications. For further explanation, please see the document titled
Requirement Plan.
Page
3.2.7.7 Data Design Review

Data design talks about the flow of the whole process from one
interface or form to another. For further explanation of the Architectural
Design, please see the document titled Architectural Design.
3.2.7.8 Architectural Design Review
The Architectural Design review is all about the whole project
design, layout, system flow and the transitions from one form to
another. For further explanation, please see the document titled
Architectural Design.
3.2.7.9 Interface
The interface will be coming from the request of the client, previous
version will be the teams basis. The proponents now has 9 interfaces,
additional will be added later on. They are all Net Beans front-end.
3.2.7.10 Component Design Review
Aside from the 9 interfaces, the proponents are also doing an
Android application designed for specific persons only.
3.2.7.11 Code Review
3.2.7.12 Test Specification Review
3.2.7.13 Change Control Reviews and Audits
3.2.8SQA AUDITS
The team members will have a report of their performance for the past
week. Problems and questions with regards with each members
performance will be noted.

Any changes that will affect the project will be consulted first to other
team members for approval before it will be implemented. These
changes are minor which needs little changes on the codes only.
Page
3.2.9PROBLEM REPORTING AND CORRECTIVE ACTION/FOLLOW-UP

3.2.9.1 Reporting Mechanisms
3.2.9.2 Responsibilities
Each member is given a task to do something. But the members still
works hand in hand. The Project Manager of the team acts as the
leader for he has a great motivating skill to manage his team members
all throughout the project making. But with regards to the decisions he
will make, he still rely on the opinions and suggestion of his team
members.
3.2.9.3 Data Collection and Valuation
3.3 SOFTWARE QUALITY ASSURANCE

3.3.1 Introduction
This section gives a broad overview of the Vendor and Consignment
Contract Management. SQA will focus on the different issues in Contract
Management and the process specific activities that enable a software
project.
SQA plan provides a road map for instituting system quality assurance.
Develop by the proponents, the serves as a template for SQA activities that
are instituted for each software project.
Page
3.3.1.1 Scope and Intent of SQA Activities

3.3.1.2 SQA Organizational Role
The proponents have a relatively 5 members.
Fig. 2: SQA Organizational Role
Project Manager: Alfred Perido

Business Analyst: LaressaAlcantara
System Analyst: RonnelCaramoan
Lead Programmer: Alvin Jan Trinidad
The
proponents
have
advantages
and
disadvantages.
The
Proponent is always willing to help each other to finish the assign task
to meet the deadline immediately. Communication is very important to
know if the member was doing a right way. The Proponent has 3 times
a week meeting to update the assign task. The disadvantage of the
Proponent is between each member. Example, the Project Manager will
give a task to System Analyst to do a system design and give it before
the deadline but the System Analyst cant do that in time so the Project
Manager will assign another member to help to do assign task to meet
the deadline and prevent rushing of document.
Page
3.3.2 SQA Tasks

Here are the tasks we have for the SQA:
Analyzing of a system and process

Close contact with the client
User friendly design
3.3.2.1 Task Overview
Task that describe above will cover the product quality control, Detail
Design that easilyunderstand to user , minimize errors, Problem
Tracking and Data flow.
3.3.2.2 Standard, Practices Conventions (SPC)
Analyzing of a System and Process
The proponents have to analyze the functionality and process of the
proposed system if that is included in the scope to change it
immediately before the presentation of the system.
Close contact with the client

Communication with client is very important to know the process and
flow of Vendor and Consignment Contract Management. The Proponent
will contact client to discuss the problems, options Proponent have
come up with, with their experience on the field, and they provide
solutions for the Proponent.
User Friendly Design
After analyzing the flow of proposed system, System Analyst will
start to design the system and the standard is to understand easily by
the user. The System Analyst must provide a button that can represent
the function. The Interface of the system must understandable and can
be use by different user even the user is lack of knowledge about the
system.
3.3.2.3SQA Resources
No external SQA resources are defined for this project.
Page
3.3.3 Review and Audits

3.3.3.1 Generic Review Guidelines
Management Responsibility
Quality System
Contract Review
Design Control
Conduction a Review
There will be two kinds of review to do, its with the client and the
other is with the teammates.
Consulting the changes to the client is a must because they will be
the one affected. Keeping records of the changes before and after it is
done.
Roles and Responsibilities
As stated in 1.2, SQA Organizational Role, the task of each member
seems confusing.
3.3.4 FORMAL TECHNICAL REVIEWS
Here are the FTR that the proponents will conduct during the software
process:
- Walkthroughs
- Inspections
After each form (interface) designed, the proponents will do a test by
doing an inspection to the interface. This will be done to all the interfaces.
3.3.4.1 Description of review Walkthroughs
Description and focus of Review
This review is mainly focus on the design integrations. The
proponents will ask some of the other member to do the walkthroughs
with the help of the encoder.
Page
3.3.4.2 Description of review Inspection

Description and Review Inspection
This review mainly focuses on the correctness of the design. The
members will do such tests on this to evaluate its appropriateness.
3.3.4.3System Specification Review
The system specification change usually happens during every
proponents meeting. But as of now, the proponents are settled on the
system design made. Even the proponents have expended the project
into a higher level; the basic mapping of the project is still there.
Software Project Plan Review
The main purpose of Software Project Plan is to look over the whole
Project Development. For further explanation, please see the document
titled Software Project Plan.
RMMM Review
RMMM, Risk Mitigation, Monitoring and Management Plan is use to
analyze the risks to be encounter and how to handle those risks. For
further explanation, please see the document titled RMMM.
Requirements Review
Software Requirements explains the data requirements and
specifications. For further explanation, please see the document titled
Requirement Plan.
Data Design Review
Data design talks about the flow of the whole process from one
interface or form to another. For further explanation of the Architectural
Design, please see the document titled Architectural Design.
3.3.4.7 Architectural Design Review
The Architectural Design review is all about the whole project
design, layout, system flow and the transitions from one form to
another. For further explanation, please see the document titled
Architectural Design.
Page
Interface
The interface will be coming from the request of the client, previous
version will be the teams basis. The proponents now has 9 interfaces,
additional will be added later on. They are all Net Beans front-end.
3.3.4.9Component Design Review
Aside from the 9 interfaces, the proponents are also doing an
Android application designed for specific persons only.
Code Review
Test Specification Review
Change Control Reviews and Audits
3.3.5 PROBLEM REPORTING AND CORRECTIVE ACTION/FOLLOW-UP
3.3.5.1 Reporting Mechanisms
3.3.5.2 Responsibilities
Each member is given a task to do something. But the members still
works hand in hand. The Project Manager of the team acts as the
leader for he has a great motivating skill to manage his team members
all throughout the project making. But with regards to the decisions he
will make, he still rely on the opinions and suggestion of his team
members.
3.3.5.3 Data Collection and Valuadation
3.3.5.4 Statistical SQA
Statistical quality assurance reflects a growing trend throughout
industry to become more quantitative about quality. For software, and
disseminated. Statistical quality assurance implies the following steps:
Information about software defects is collected and categorized.
An attempt is made to trace each defect to its underlying cause.
Once the vital few causes have been identified, move to correct the
problems that have caused the defects.
Page
Although hundreds of different errors can be covered, even for a

small scale project like this, all can be tracked to one (or more) of
the following causes:
Incomplete or erroneous specification(IES)

Misinterpretation of client communication(MCC)
Intentional deviation from specification(IDS)
Violations of programming standards(VPS)
Error in data representation(EDR)
Inconsistent module interface(IMI)
Error in design logic(EDL)
Incomplete or erroneous(IET)
Inaccurate or incomplete documentation(IID)
Error in programming language translation of design(PLT)
Ambiguous or inconsistent human-computer interface(MIS)
Miscellaneous(MIS)
3.3.6 Software Process Improvement Activities

Determines for software Quality and Organizational Effectiveness
Product
Customer
Characteristics
Business Conditions
Proce
ss
People
Technology
Environm
ent
Developmen
Fig. 3: Software process Improvement
Activities
3.3.6.1 Goal and Object of SPI

Here are some of the goals of SPI
All errors are defects are categorized by origin.

The number of errors are defects in each category are counted and
ordered in descending order.

Plans are developed to modify the process with the intent of
eliminating the class of
errors and defects that is most costly.
Page
The graph below illustrated the error that we expected for the
project. They categorized in six fields. (PS2)
3.3.6.2 SPI Tasks and responsibilities
Since the proponent has only five members, the responsibilities of
each member will do doing SPI.
3.3.7 Software Configuration Management Overview
While developing software the proponent will be making changes to the
original plan. Software Configuration Management Plan is developed to
identify the changes, to make sure that the plan of the proponents was
implemented correctly and also to know the changes of each member and
client. For more information please go to the document titled Software
Configuration Management Plan.
3.3.8 SQA Tools, Techniques, Methods
The proponent describes a lot of tools, techniques, methods for SQA.
Using analyzing of a system and process, close contact with a client, User
friendly design
3.4 SOFTWARE DESIGN SPECIFICATIONS

3.4.1 Introduction
The proponents system can view, can print can edit the contract but it has
a limit when it comes to editing. System has two users one is admin that can
handle all important information and can edit contract letter. And the other user
is staff that can only view some information.
Page
3.4.1.1 Goals and Objectives

To come-up with a system that can handle amendments to the contract.
Like updating (renewal) and cancelling of the contract. A system that can
securely keep records of the contracts and avoid falsification and overmanipulation of the contracts.
To come-up with a system that can create contract for new suppliers.
To make cancellation of contract for suppliers who havent satisfied the
needs of the company.
A system that can update/renew contract for suppliers.
A system that can edit the contract if theres a sudden change to the
product name and avoid conflicts.
A system that can determine who is the manufacturer of an outright
product of the company.
A system that can add new product to the contract.
3.4.1.2 System Statement of Scope
3.4.1.2.1 General Requirements
A way in which DEQ could add new facilities to the database
A way in which DEQ could generate electronic checklists.
A search on all electronic checklists.
A way in which they could generate letters to be sent out to facilities
based on inspection results.

A way in which all letters and checklists could be stored
electronically.
A way to search for existing facilities
A way to print blank checklists and staff reports.
A way in which they could view data which was entered into the
database prior to our software.

DEQ wanted a product that would allow them to easily add new
checklists and letters or change existing checklists and letters.

Interface Enhancements
Staff members of WMD have requested a lot of interface
enhancements that will increase the usability of the product and
letters.
Database Administrative Interface
There is current no documented interface for WMD staff
members to maintain the checklist and letters templates. Should no
Page
such interface existed, Cyber Rovers will have to implement one

from scratch.
3.4.1.3 System Context
Eventually, multiple users will be using the product simultaneously.
Therefore, concurrent connection will be an issue for implementation. In
additions, this is a pilot product that hopefully, If successful, can be
used in other locations as well. This leads to issues about future
support for a larger user base.
3.4.1.4 Major Constraints
Time
We only have about two months to finish the whole
documentation, software creation and enhancements. We have a lot
of ideas but cannot implement due to time constraint. One of the
major ones is to move the application to be completely browserbased.
Funding
To develop and implement the Palm Pilot integration, we will
need funding to buy at least one Palm Pilot. We will request the
funding from University of Michigan Dearborn should we decided
to pursue this function.
Data Design
3.4.2.1 Database Description
Entities
Each record in the entity represents a (n).
TITLE
Staff title
STAFF
Staff member
Page
ACCESS
Facility
MODULE
Module
FACILITY TYPE
Facility Type
EPA_CODE
EPA Code
INSPECTION
Inspection
INSPECTION_DETAIL
Inspection Checklist Item
INSPECTION_CHECKLIST
Inspection Checklist
3.4.3 Architectural and Component-Level Design

3.4.3.1 Program Structure
3.4.3.1.1 Overall
Menu Items
The following shows the architecture of the main menu:
File
Switch User
Exit
Facility
Inspection
Create/Modify
File Results
Get Approval
Print letters
View schedule
Approval
Reports
Print Staff Report
Print Blank Checklist
Page
Efficiency Report
.(more TBD)
Maintenance
Checklists
Letters
Users
Options
Help
Contents
About
3.4.3.1.2 Create Inspection

3.4.3.1.3 During Inspection
3.4.3.1.4 Post-Inspection
3.4.3.1.5 Approval
3.4.3.2 Description for Components
3.4.3.2.1 Switch User
Major Form(s)
:frmLogin
Major Action(s)
:Login
3.4.3.2.2 Facility
Major Forms(s)
:frmFacility,frmFacilityBrowse,
andfrmFacilitySearch
Major Action(s): Browse, Search, Save, Delete and View

Browse
Object
To browse all facilities, user can click on the bomb button next to
the txtFacilityID field.
frmFacilitySearch will appear. User can highlight a facility in the
result grid, the click cmdOkay. All the information on frmFacility will
be filled in.
Save
Page
Object Name: cmdSave

To Save button should be disabled unless the txtFacilityID field is
filled in, and any there have been changes made to any field on the
frmFacility. When the save button is clicked, new record will be
generated if the Facility ID does not exist in the system,
otherwise,current record will be updated.
Delete
Object Name: cmdDelete
The Delete button should be disable unless no historical data
have been found for the facility. The Delete and View button should
never be enabled at the same time.
View
Object Name: cmdView
The View button should be disabled unless historical data have
been found for the facility. The Delete and View button should never
be enabled at the same time
3.4.3.2.3 Create/Modify Inspection Step 1
Major
Form(s)
:frmInspection,frmInspectionBrowse,InspectionSearch,
frmFacilityBrowse, and frmFacilitySearch
Major Action(s): Create Inspection, Modify Inspection (Inspection
Browse, Inspection Search), Next Step and Add/Edit/Delete Date
Create Inspection
To create an inspection, user needs to enter a new Inspection ID
in the txtInspectionID field. To use an automatic number, click on the
blank paper button, an automatic number will be generated and filled
in the txtInspectionID field.
Page
Modify Inspection
To modify an inspection, user needs to enter an existing
Inspection ID in the txtInspectionID field. To browse all open
inspections, user can click on the bomb button next to the
txtInspectionID field. frmInspectionBrowse will appear. User can
highlight an inspection in the grid, then click cmdOkay. All the
information on frmInspection will be filled in.
Add Onsite Visit Date
Users need to click on the calendar icon, pick a date. txtTime can
be left blank. User can then click cmdDateAdd to add the date to the
grid.
Edit/Delete Onsite Visit Date
If a user highlights a row in the date grid, he or she can edit the
contents in the txtDate (using the calendar control) and txtTime field.
Then he or she can click on cmdDateEdit to update the record. The
User can also click cmdDateDelete to remove the highlighted row.
Next Step
frmPickChecklist will appear. See Create/Modify Inspection
Step 2 for more info.
3.4.3.2.4 Create/Modify Inspection Step 2
Major Form(s)
:frmPickChecklist
Major Action(s): Pick Checklist(s), Finish
3.4.3.2.5 File Results Step 1
Major Form(s)
:frmFilresults1,
frmInspectionBrowse,and
frmInspectionSearchMajor Action(s): Browse/Search Inspections,

Next Step
Page
3.4.3.2.6 File Results Step 2

Major Form(s)
:frmFileResults2
Major Action(s) : Add/Edit/Remove comments and status for

each inspection item, Preview Letter, Spell Check (2).
Add Comments
To add comment for an inspection item in the checklist, user
needs to highlight an item in 1 stRegulations, enter comments in the
txtComments and select status in cboStatus. Then he or she needs
to click cmdAdd. The item will be added to 1stInspected.
Remove Comments
To remove comments for an added inspection item. User needs
to highlight an item in 1 stInspected then cmdEdit to apply the
changes.
Spell Checker
User
can
click
on
cmdSpellCheck1
(for
add)
and
cmdSpellCheck2 (for edit) to check the spellings in the respective

comment box.
Preview Letter
When cmdPreview is clicked, the application will generate a
letter in the right portion of the screen. Which letter to use will
depend on the letter chosen in cboLetters.
3.4.3.2.7 Approval
Major Form(s)
:frmApproval,frmLetterDisplay
Major Action(s) : View, Approve, and Deny

3.4.3.2.8 Checklist Maintenance
Major Form(s)
:frmMaintainChecklists
Page
Major Functions: New, Browse/View, Save, View, Delete,Close.

New
When cmdNewChecklist is clicked, frmMaintainChecklists will be
cleared and the internal checklist ID, intChecklistID will be set to
null as well.
Browse
When cmdBrowseChecklist is clicked, frmBrowseChecklists will
appear. After the user made a selection in frmBrowseChecklist
component description), txtChecklistID will be filled in by the value
returned
by
frmBrowseChecklist.frmMaintainChecklist
will
be
refreshed with all the details of that checklist. The bottom data grid
will be filled in with items from the checklist.
Remove
When the user click on cmdDeleteChecklist, a warning message
will appear to confirm the users action. If the user confirms the
action,
the
appropriate
checklist
header
record
in
CHKLIST_HEADER will be removed. Records in CHKLIST_ITEM

that are related to that header will also be removed. Afterwards,
1stChecklists will be refreshed.
Close
When cmdCloseChecklist is clicked, if changes were made to
any field within the form, a warning message will appear to confirm
users action. If the user confirms, the form will be closed and no
actions will be performed on the database. If the user does not
confirm, user will simply be returned to the form.
Save
Page
When the user clicks on save, if intChecklistID already exists in

the database, the header record in CHKLIST_HEADER with CH_ID
equals to intChecklistID will be updated. Also all records in
CHKLIST_ITEM with CI_CH_ID equals to intChecklistID will be
updated as well. If intChecklistID does not exist, a header record will
be recorded in CHKLIST_HEADER. Appropriate number of records
will also be created in CHKLIST_ITEM.
3.4.3.2.9 Letter Maintenance
Major Form(s)
:frmMaintainletters
Major Functions: New, Browse/View, Save, View, Delete, Close.
New
When cmdNewLetter is clicked, frmMaintainLetters will be
cleared and the internal letter ID, intLetterID will be set to null as
well.
Browse
When cmdBrowseLetters is clicked, frmBrowseLetters will
appear. After the user made a selection in frmBrowseLetters (see
details in the frmBrowseLetters component description), txtletterID
will be filled in by the value returned by frmBrowseLetters.
frmMaintanLetters will be refreshed with all the details of that letter.
The bottom data grid will be filled in with items from the letter.
Remove
When the user click on cmdDeleteLetter, a warning message will
appear to confirm the users action. If the user confirms the action,
the appropriate letter header record in LETTER_HEADER will be
removed. Records in LETTER_ITEM that are related to that header
will also be removed. Afterwards, 1stLetters will be refreshed.
Close
Page
When cmdCloseLetter is clicked, if changes were made to any

field within the form, a warning message will appear to confirm
users action. If the user confirms, the form will be closed and no
actions will be performed on the database. If the user does not
confirm, user will simply be returned to the form.
Save
When the user clicks on save, of intLetterID already exists in the
database, the header record in LETTER_HEADER with LTR_ID
equals to intLetterID will be updated. Also, all records in
LETTER_ITEM with LTRI_LTR_ID equals to intLetterID will be
updated as well. If intChecklistID does not exists, a header record
will be recorded in LETTER_HEADER. Appropriate number of
records will also be created in LETTER_ITEM.
3.4.4 User Interface Design
There will be about 30 interfaces in the program. We cant design on
the exact number of it yet. Because the clients still have to think over on
several interfaces, to see rather they can be combined some of the forms
or put some them in separated forms.
3.4.4.1 Description of the User Interface
Below are some of the forms in the program. After fire up the
program, the login screen will appear. If the users enter the right user
name with the matching password, it will immediately take them to the
main interface (mdiDEQ).
3.4.4.1.1Screen Image
- Login Screen
- Main Interface
- Generate Check List
- Facility Information
- Search Pages
- Approval Queue
Page
3.4.4.1.2 Objects and Action

1.
Login Screen
User Name
User name can be ranged from 6 to 20 letters (numbers), as the
industry standard. No Special characters, space. And mostly likely
the user will use their DEQ user name for this system as well.
Password
Password can be ranged from 6 to 20 letters (numbers), as the
industry standard. No Special Characters, space.
OK
If the users enter the right user name with the matching
password, it will immediately take them to the main interface.
Cancel
If the user wishes to exit the program, hit the Cancel button.
2.
Main Interface
Menu Items The following show the architecture of the main menu:
File
Switch user
Exit
Facility
Inspection
Create/Modify
File Results
Get Approval
Page
Print Letters
View Schedule
Page
Reports
Print Staff Report
Print Blank Checklists
Efficiency Report
(more TBD)
Maintenance
Checklist
Letters
Users
Options
Help
Contents
About
Switch User
Major Form(s) :frmLogin
Major Action(s) :Login
Facility
MajorForm(s): frmFacility,frmFacilityBrowse,
andFacilitySearch
Major Action(s)
:Browse, Search, Save, Delete
and View
Browse
Object Name: cmdBrowse
To browse all facilities, user can click on the bomb button next
to the txtFacilityID field. frmFaciltyBrowse will appear. User can
highlight a facility in the grid, then click cmdOkay. All the
information on frmFacility will be filled in.
Search
Object Name: cmdSearch
To search for facility, user can be click on the multi-page
document button next to the txtFacilityID field. frmFacilitySearch
will appear. User can highlight a facility in the result grid, the click
cmdOkay. All the information on frmFacility will be filled in.
Save
Object Name: cmdSave
The save button should be disabled unless the txtFacilityID
field is filled in, and any there have been changes made to any
field on the frmFacility. When the save button is clicked, new
Page
record will be generated if the Facility ID does not exist in the

system, otherwise, current record will be updated.
Deleted
Object Name: cmdDelete
The delete button should be disabled unless no historical
data have been found for the facility. The delete and view button
should never be enabled at the same time.
View
Object Name: cmdView
The delete button should be disabled unless historical data
have been found for the facility. The delete and view button
should never be enabled at the same time.
Create/Modify Inspection-Step 1
MajorForm(s)
:frmInspection,
frmInspectionBrowse,
frmInspectionSearch,
frmFacilityBrowse,and
frmFacilitySearch
Major Action(s) :Create Inspection, Modify

inspection(Inspection Browse,
Inspection Search), Next Step
And Add/Edit/Delete Date.
Create Inspection
To create an inspection, user need to enter a new Inspection
ID in the txtInspectionID field. To use an automatic number, click
on the blank paper button, an automatic number will be
generated and filled in the txtInspectionID field.
Modify Inspections
To modify an inspection, user needs
to
enter
an
exitinginspectionID in the txtInspectionID field. To browse all

open inspection, user can click on the bomb button next to the
txtInspectionID field. frmInspection Browse will appear. User can
Page
highlight an inspection in the grid,then click cmdOkay. All the
information on frmInspection will be filled in.

Add OnSite Visit Date
Edit/Delete Onsite Visit Date
Next Step
Create/Modify Inspection- Step 2
File Result- Step 1
File Result- Step 2
Add Comments
Remove Comments
To remove comments for an added inspections
Edit Comments
To edit comments for an added inspection item. User needs
to highlight an item in 1stInspected. The comment for that item
will be shown to the right. The user can then update the
comments and click cmdEdit to apply the changes.

Spell Check
User can click on cmdSpellCheck1(for
Add)
and
cmdSpellCheck2(for Edit) to check the spellings in the respective

comments box.
Preview letter
When cmdPreview is clicked, the application will generate a
letter in the right portionof the screen. Which letter to use will
depend on the letter chosen in cboletters
Approval
Major Form(s)
:frmApproval,frmLetterDisplay
Major Action(s) :View, Approve, and Deny
Page

Vendor and Consignment Contract Management 1a-V5 0

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Vendor and Consignment Contract Management 1a-V5 0

Încărcat de

Drepturi de autor:

Formate disponibile

CHAPTER 1

1.0 PROJECT CHARTER

done their services throughout the contract duration.

throughout the business.

added to the contract.

Establishing good relationship between partners

instilling into them how to become responsible business persons. To

Organized list of the contracted firms

1.1.4 Stakeholders and Clients

and the company itself.

will be no transactions to be done.

realistic. Without one of them, there

Vendor and Consignment

Table 1: Stakeholders and Clients and their participation

Vendor and Consignment Contract Management

Figure 1: Vendor and Consignment Contract Management

Vendor and Consignment Contract Management are can create contract

1.2.3 Out of Scope

of checking the products is done by the other team.

Vendor and Consignment Contract Management

1.3 PROJECT PLAN

Vendor and Consignment Contract Management

The proponents create project duration

deadlines for the accomplishment of each task.

budget/costing is also included so that there will

suppliers/merchandisers. It will be the basis of

process of agreement takes place.

informations will be used in the system

behind this and how the proponents will solve it.

Vendor and Consignment Contract Management

understand by the user. Wherein the user can

content of the contract.

overall system. To test its capabilities, and

Table 2: Approach and Methodology with description

Vendor and Consignment Contract Management

Vendor and Consignment Contract Management

Table 3: Project Timeline of the Proposed System

1.3.5 Risk Management Plan

Vendor and Consignment Contract Management

everyone will attend the

regards to the project

encountered during the

source of income for

read related books to

to be able to fill the

Vendor and Consignment Contract Management

Table 4: Risk Management of the Proposed Project

have to meet first and discuss it.

be able to fill the insufficiency of products.

1.3.7 Option Analysis

Vendor and Consignment Contract Management

the contract is computerized, so the printing of documents every now

Distributing the task to every team member.

Providing techniques to make a satisfying

Maintain control over important business

Making key business decisions.

Constructing plans of the project making.

Evaluating the needs of the customers.

Coding of the program.

Maintaining technical aspects.

Vendor and Consignment Contract Management

Assurance of the data accuracy.