Professional Documents
Culture Documents
FOR THE
GreatVines
Cazacliu Cristian,
Roșca Doinița,
Florea Cristina,
Kalinovski Bogdan
Introduction
GreatVines is an all-in-one Sales Execution Platform for beverage suppliers, distributors, and
promotional agencies. Powered by Salesforce, our suite of mobile tools help you manage 3-
tier account relationships, plan appropriate sales activities, create smarter goals for growth,
and monitor trade spend and marketing programs. GreatVines offers the flexibility to adapt
your sales strategy for rapidly changing market conditions, and supplies analytics to precisely
measure the results you need to quickly collaborate with your channel partners.
1.4. Scope
This document describes the approach and various processed to be considered for the Project.
For any mobile , desktop or web application there are three relevant and actual deployment
option that affect the process for requesting information :
Private Any private servers used by Andavi Solution may be operated by arbitrary
servers business ,groups or individuals with no direct link to the main company.
GreatVines is an online platform and the interaction between customers and the platform happens
based on an account. Most of their customers are other companies, and GreatVines provide them a list
of services.
To create a customer account on this platform is requested to introduce your first name, last name, a
working email, a phone number and company name
To identify the proper user account, the specific server therefore must be named as well
(generally in form of the URL).
2.3. Data retention information
GreatVines is a Nielsen Connected Partner. As part of the Connected Partner program, the
TDLinx account universe can be embedded into the GreatVines platform and leveraged with
great results by users of the GreatVines tool. TDLinx provides suppliers, wholesalers and
marketers with universal coverage and unique codes for every store in retail trade channels
and for every outlet in on-premise trade.
For alcohol beverage companies, the TDLinx data provides insight into over 770,000
stores/outlets and more than 9,800 accounts. It is updated daily and delivered automatically to
GreatVines at regular intervals.
Role Authority
Project Manager Coordinate activity of the team
Approve every modification in project and documents
Ensure free communication between each member of team
Assigned experts to be involved directly in Project phases.
3.3.2. Reporting
Progress report will be communicated by Business analyst through email once in 2 working day.
4. Quality Assurance
Quality assurance provided via mandatory peer review of project management procedures and
reports, combined with configuration management processes.
The Project Manager and Business Analyst, who controls documents lifecycle and QA
procedures fulfillment, supports configuration items list.
5. Risk Management
Each member of team can identify a risk. He or she will report this risk though email and
should communicate it to the Project Manager.
Project Manager with the risk initiator and other team members qualify the risk, define parts
of project it can fluent and people who may be involved. Risk owner should be defined at this
step. After the qualification, the risk should be included into the risk log.
5.1.2. Risk evaluation
The Project Manager with experts define project parameters risk can fluent to (scope,
duration, and budget).
Risk Impact. The potential impact of the risk if it did become a project issue. Valid
options include the following: High, Medium, Low. These are defined as follows:
High: Risk that has the potential to greatly impact project cost, project schedule
or performance.
Medium: Risk that has the potential to slightly impact project cost, project
schedule or performance.
Low: Risk that has relatively little impact on cost, schedule or performance.
Probability of occurrence:
High: more than 80%.
Medium: Between 20% and 80%.
Low: Less than 20%.
For each major risk, one of the following approaches will be selected to address it:
For each major risk that is to be mitigated or that is accepted, a course of action will be
outlined for the event that the risk does materialize in order to minimize its impact.
5.2. Risk Monitoring, Controlling, and Reporting
All the Project members are responsible to track, monitor and report throughout the project
lifecycle the risks.
Project Manager is responsible to keep up-to-date Risk Log. A summary of the Risk Log must
be included into the Project Progress Report.
All project change requests will be analyzed for their possible impact to the project risks.
GreatVines Mobile (our original mobile solution) is developed with a hybrid HTML5
framework where our field sales mobile app introduces our first pure Javascript Progressive
Web App (PWA) on the latest standards.
Both mobile solutions utilize the same credentials as our standard browser environment, are
available in offline mode, and GreatVines Mobile can also be installed by end users from the
device app stores.
The GreatVines Data Integration platform can load data from third-party data providers, such
as Nielsen and VIP, into GreatVines to provide a complete picture of customers and sales
across the 3-tier supply chain. This data includes retailers, national account chains, wholesaler
inventory and depletions, and Sales to Retailers (STR/RAD).
All core GreatVines application functionality and data management, other than reporting and
analytics, is developed on and powered by the Salesforce Lightning Platform. The GreatVines
Mobile application (version 1) was built upon the Salesforce Mobile SDK, and has been
recognized as a leading partner app for innovation. GreatVines has been a featured partner on
the AppExchange Retail category since 2010, as well as a participant in the annual
Dreamforce conference in San Francisco
7. Training Plan
A software solution can only show all its benefits if used properly. An efficient capacity
building can avoid problems during and after the implementation process.
The Trainer responsibility is to ensure the relevant IT administrators and users of the
Beneficiary’s institution are enabled to autonomously operate and maintain the systems after
the end of the project and the final users understand how to use it properly.
One of the main Project objective is to ensure that management of the Beneficiary agencies
and their key users of the System are sufficiently experienced to be capable of assuming the
full responsibility for the System operation and other support, maintenance and enhancement
tasks, in order to guarantee the long-term sustainability of the supplied solution.
The Supplier’s Project Manager will take all the necessary measures in order to ensure that
the experience for duly operate the supplied System.
To achieve the proposed objective, the Supplier, in collaboration with the Purchaser, will
perform the following actions:
The Purchaser’s Project Manager and EGA Representative are responsible to name the
appropriate team members to participate at:
- Technical meetings
- Project Management meetings
The Purchaser’s Project Manager is responsible to coordinate the process with the Supplier’s
Project Manager, the communication will be realized according to Project Organization and
Management Plan.
When putting into the operation the System, all the related documentation will be delivered to
the Beneficiary and provided knowledge data base transfer (to see the Training Plan and
Turnover and coordination plan).
During the Warranty Period, Andavi Solution. is responsible to ensure System availability and
reduce the risk of distrusted operations due to incident occurrence. Therefore, all the incidents
may be reported by the Beneficiary’s responsible person via support channel: hot line and/or
service desk.
No later than 3 weeks before starting the Warranty period, the Supplier will configure the
Project within the Service Desk and open the account to appointed by Project Manager
responsible persons, assign a Hot line number.
If during the incident analysis and solution identification, the Supplier needs more
information, the Beneficiary must provide the support operator with the request information
or ensure operator remote access to the incident location. If the Beneficiary has not provided
the information or access during 3 working days, the ticket is considered resolved and closed.
The Supplier is responsible for incident analysis, solution identification and categorization,
with the primary goal being a quick-as-possible restoration of System being on service.
Support of the System is based on a Service Desk with two levels. Incident processing starts
at first level, 2nd level is getting involved as necessary.
First-Line Support (a support operator) opens an incident ticket and attempts to collect as
much information and diagnostics about the incident as possible, sets the incident priority
(according to policy) and even resolves the issue on the spot, if possible, using Support
Knowledge Base.
If First-Line Support is not able to resolve the incident right away, it will escalate the incident
to Second-Line Support.
When the ticket is assigned to the 2nd level support line, the support operator must provide the
following information:
- Incident description
- A possible cause of the incident
- Expected results and Actual results
- Any print screens and System logs if applicable
The Beneficiary must confirm the solution and close the ticket in 3 working days, after
solution delivery. If no response if received form the Beneficiary, the ticket will be considered
resolved and will be automatically closed. If the Beneficiary will not confirm the solution of a
closed ticket, a new ticket on the problem will be submitted.
During the warranty period, the Beneficiary may address change request to the System. The
change request must be addressed via Project official communication channel.
The changes in business functionalities will be provided upon request, the effort of
implementing change request will not exceed 50-man days per annum.
9.3. Quality assurance and control
Periodically the Parties arrange a meeting where they analyze support operations and issues.
As a result of this analysis following tasks will be initiated:
The developed Software will be transferred in the Purchaser’s property; thus the source codes
will be submitted during the implementation of the Project.