<Company Name>
Business Process Document
Business Process Document v2.0
Associated with the following:
<Project Name>
<Idea Doc ID>
VERSION <X.X>
Confidential Information
Month, Day, Year
<Title of Document>
Page 1 of 9
<Company Name>
Business Process Document
Table of Contents
1
2
3
4
5
Business Need ......................................................................................................................... 3
1.1 Background......................................................................................................................... 3
1.2 Business Objectives ........................................................................................................... 3
1.3 Business Risks ................................................................................................................... 3
1.4 Assumptions and Dependencies ........................................................................................ 3
1.5 Definitions ........................................................................................................................... 3
Starter Q&A .............................................................................................................................. 4
Business Requirements ........................................................................................................... 5
Process Flow ............................................................................................................................ 6
Impacts ..................................................................................................................................... 7
5.1 Call Center Impacts ............................................................................................................ 7
5.2................................................................................................................................................ 7
Appendix................................................................................................................................... 8
6.1 Related Artifacts ................................................................................................................. 8
6.2 Question and Issue Log/History ......................................................................................... 8
Change Management ............................................................................................................... 9
Month, Day, Year
<Title of Document>
Page 2 of 9
<Company Name>
Business Process Document
1 Business Need
< Overall business rationale which provide the foundation of the process defined herein >
1.1
BACKGROUND
< Provide a general description of the history or situation that led to the need for this business process; e.g.
need to make our search process industry-standard, new business model were pursuing, client is adjusting
its place in CE industry, because its about time someone documented our returns process, etc.
(1) What is the current problem (2) How would like to see it addressed >
1.2
BUSINESS OBJECTIVES
< Lists the specific business objectives of the process in a way that is quantitative and measurable. You may
draw from the work entered in the associated Idea Doc. In other words, what will define success once this
process is implemented; this may include budget & schedule objectives. >
1.3
BO-1:
BO-2:
BUSINESS RISKS
< Lists major business risks associated with the development of this solution, such as timing issues, losing
client business if not implemented, expenses being incurred from manual involvement. >
ID
Risk Description
Client opts not to
purchase subscription
~$1.5 million per
annum in revenue
loss
Regular client interaction,
responsiveness to client
needs
The core fee of a part is a
significantly small amount.
It costs
Partsearch more
to process the
core return.
If the core fee of a part is
equal to or less than the
threshold (currently set to
$10), the part will not be
considered core-eligible.
1.4
Risk
Probability
Risk
Impact
Risk
Consequences
Risk Mitigation
ASSUMPTIONS AND DEPENDENCIES
< List of any assumptions that were made when considering the business case. Also note any major
dependencies the process must rely on for success such as business relationships, integrations, third party
entities, etc >
1.5
AD-1:
AD-2:
DEFINITIONS
< Specify any terminology or industry-standard nomenclature this process will speak to. This will ensure
everyone is speaking the same language when defining the process and applications to follow.>
Month, Day, Year
<Title of Document>
Page 3 of 9
<Company Name>
Business Process Document
2 Starter Q&A
< Below are a list of questions most BAs will need to begin their analysis; please fill in the information for
each question with as much detail as you can provide. The more upfront information a BA has, the smoother
the remainder of the SDLC will be.>
1. Is there an existing process which is being replaced or enhanced? If so, what is it?
2. What would be the ideal process?
3. Who are the users/actors of this business process and what special permissions should
each user have?
4. Are there any prerequisites to this business process starting and/or completing?
Month, Day, Year
<Title of Document>
Page 4 of 9
<Company Name>
Business Process Document
3 Business Requirements
< The following section outlines the core business rules and requirements this process must follow. This
section should not be composed of how any applications should work, but how the process itself is to be
laid out. IT will in turn take these business requirements and turn them into product requirements the
application complies with>
ID
BR-1
Description
< Summary of business requirement>
Type
<Functional
or
Operational>
Reference
<Person or
Document req
originated
from>
BR-2
BR-3
BR-4
Month, Day, Year
<Title of Document>
Page 5 of 9
<Company Name>
Business Process Document
4 Process Flow
< Diagram depicting the lifecycle of the business process and all the people / groups (internal or external) that will be impacted; the ones below are swimlanes,
built using Visio. As long as the end-to-end process is captured, the format is your choice >
Place Order for core part
Airbil
Airbil
Customer ships part back
Customer ships part back
Fedex
Integration
SF
Core Portal
Customer
Returns Process
Can Customer Login?
Yes
Choose to print Airbil
Choose to print Airbil
Carrier
Fedex
Integration
SF
Generate Airbil
Receive package
Generate Airbil
Deliver Return
Receive package
Deliver Return
Company
Vendor
No
Fedex
Integration
Core Item has Shipped
Receive Return
Fedex
Flatfile
Core Item has Shipped
Receive Return
Fedex
Integration
SF
Receive delivery confirmation
Receive delivery confirmation
Partsearch Mails CR Airbil
Credits
Core Return is required?
Month, Day, Year
Send Servicer Core notification email.
Send Servicer Core notification email.
Record Tracking Number and update status
Record Tracking Number and update status
<Title of Document>
Receive In transit confirmation
Receive In transit confirmation
Page 6 of 9
<Company Name>
Business Process Document
5 Impacts
< This section outlines impacts this process will have within Partsearch as well as to external partners. If
there is no anticipated impact, please enter N/A>
5.1
INTERNAL IMPACTS
5.1.1
CSR FUNCTIONS
5.1.2
CORPORATE ACCOUNT TEAM
5.1.3
RETURNS / CREDITS
5.1.4
SOURCING / SHIPPING
5.1.5
RESO OPT
5.2
5.2.1
EXTERNAL PARTIES
CLIENTS
< Training concerns, Account setup, data integration (e.g. PSP contracts from BBY), etc>
5.2.2
CARRIERS
< e.g. FedEx, UPS, USPS, etc >
5.2.3
PAYMENT PROCESSORS
< e.g. CyberSource, PayPal, new processor? >
5.2.4
VENDORS
< Includes distributors, mfgs, OEMs >
Month, Day, Year
<Title of Document>
Page 7 of 9
<Company Name>
Business Process Document
6 Appendix
< Includes sections that are sited as references to other places in the document, as well as any other necessary information >
6.1
RELATED ARTIFACTS
< Any documents, pictures, email templates, etc which may additionally augment the analysis process >
6.2
Issue
#
1
2
3
4
QUESTION AND ISSUE LOG/HISTORY
Section
<hyperlink
to doc
section>
Month, Day, Year
Question
Status
Next Action
Due
<Open or
Closed>
<Title of Document>
Page 8 of 9
Owner
Answer / Notes
<Company Name>
Business Process Document
7 Change Management
<Denotes all changes to this document>
Change
Log #
CL1
CL2
BPD Ver.
1.0
1.1
Date
Revision Description
07/26/2007
08/24/2007
Initial version
Defined a process to handle different core
fees for the same item, item condition from
multiple vendors. Updated Risk #2, defined
BR-21, updated UC5 and UC6.
Month, Day, Year
<Title of Document>
Section
Modified
N/A
1.4
3
6.2
Bug # /
Author(s)
SMI #
Erwin Basa
CL3
Page 9 of 9
