CONTENTS

1. INTRODUCTION:..................................................................................................................................2
1.1 INTRODUCTION TO CISCO:................................................................................................................2
1.2 ERP IMPLEMENTATION PROJECT:.....................................................................................................2
1.3 STRATEGY OF THE PROJECT:.............................................................................................................2
2. PROJECT OVERVIEW:..........................................................................................................................3
2.1 IMPLEMENTATION PHASES:.............................................................................................................4
2.2 PROCUREMENT PROCESS:................................................................................................................4
3. THE REQUEST FOR PROPOSAL (RFP):..................................................................................................5
4. THE BIDDING PROCESS:......................................................................................................................6
5. TECHNICAL REQUIREMENTS:..............................................................................................................6
5.1 Implementation activities of the ERP solution:................................................................................7
5.2 Approach for Implementing the ERP solution:.................................................................................9
5.3 The ERP Solution Implementation Methodology:..........................................................................11
5.4 Technical Architecture Support:.....................................................................................................11
5.5 Auditing and Review:......................................................................................................................11
5.6 Support for System Stability:..........................................................................................................12
5.7 Technical Support:..........................................................................................................................13
5.8 Post Implementation Support:.......................................................................................................13
6. SELECTION CRITERIA:........................................................................................................................15
6.1 Proposal Evaluation........................................................................................................................15
6.2 RFP RESPONSE FORMAT.................................................................................................................16
6.3 SUBMITTAL FORMAT AND PROPOSAL TIME..................................................................................17
7. Principle Point of Contact:................................................................................................................19
8. Budget:..............................................................................................................................................19
1. INTRODUCTION:
1.1 INTRODUCTION TO CISCO:
Two enthusiastic computer engineers from Stanford University established Cisco Systems, Inc.
in 1984. The "router" was their first product. Market for Cisco products increased dramatically
after 1990 with increased digital use. By 1993, Cisco was a corporation with a volume of $500
million and in 1997 it was among the top rankings in earnings and Assets yields. In the same
year, Cisco joined Fortune 500 and achieved more than $100 billion in market capitalisation.
The first one to take initiative and lay the groundwork for a young company was Don Valentine,
partner of Sequoia Capital, and Vice Chairman of the board of Cisco. In 1988 he appointed John
Morgridge CEO, whose first task was to set up a systematic team. His management team
confronted the founders of Cisco systems and the founders left. After the initial public offering
of the company in 1990. In the end, CEO Morgridge was ready to enact a management
structure with exceedingly discipline in Cisco. He maintained a centralized functional
organization, which lasted about 10 years.
1.2 ERP IMPLEMENTATION PROJECT:
 In order to simplify and optimize its operations, CISCO has crafted a project to deploy an
integrated ERP (Enterprise Resource Planning) system
 The main consequence of this project is the availability of facilities, organizational
competence and accountability
 Delivery of services to involved entities
o Cross - platform services via portal, mobile equipment, etc.
o Consistent and reliable device-wide resources
o Comfort for the good of stakeholders
o Service and control flexibility for CISCO staff
 Operational Excellence
o System alignment – Finance, HR, Manufacturing, Order-entry etc.
o Resource utilization- financial capital and intellectual resources
o More fast time to respond, evaluate and report financial transactions
o Excellence in installations and equipment implementation, project preparation
and the utilization of internal skills
1.3 STRATEGY OF THE PROJECT:
The plan of the CISCO ERP implementation project has various aspects and the opportunities
provided by ERP solutions are devised.
 Standardization – method standardization, documents, terminology, frameworks for
Information sharing  
 Established strategies – Cisco has decided that an established ERP approach tackles the
above with a view to the size and criticality of its operations.
o ERP Solution offers an IT framework that incorporates all operations process
automation
 o Best Practices – ERP Approach can recognize be the best practices in the fields of
project management, financial asset management, Order-Entry, Material
maintenance, Manufacturing units.   
o Cross - platform service delivery – an ERP approach allows various computers
and operating systems to carry out purchases, allowing multi - platform
operational efficiency possible for stakeholders.
 Cisco plans to invest in software focused on ERPs:
o Achieving service consistency, productivity and greater monitoring of financial
transfers and mission activities;
o Establish consistent criteria for organizational efficiency, project management,
Capital utilization, HR and performance monitoring   
o Adopt worldwide best practises for diverse regions: sourcing, materiel
management, management of human capital, product management, customer
care, financial reporting, accounts and results reporting
 The project's projected results
o Using the ERP approach, Cisco needs various software components to be
implemented in a cohesive way to ensure that the data is not duplicated and
Cisco is able to create a solid base for decision support.
o Performance, transparency and rational decision-making would be driven by the
implementation of common practices of ERP solutions in key processes such as
financial and accounting, supervision, assessment, risk management, inventory
management, content management, human resources management as relevant
to the operations of Cisco.
o The ERP Approach is supposed to better implement common management
practices and procedures into all of its activities and eliminate non-value
addition/redundant processes in different departments of the firm in order to
make them effective, consistent and compliant.

2. PROJECT OVERVIEW:
The project is designed to be conducted on a fully integrated basis by a professional system
integrator with responsibility for all facets of this RFP project

 In order to align with the requirements of the Cisco, the device integrator has to
determine the requirements of the RFP and suggest established ERP solution from well-
known OEMs
 The purpose of function of the device integrator is to offer deployment services for the
ERP software recommended
 ERP solution software and hardware centered on the Cisco specifications and ERP
solution install / service
 Cisco will deliver the requisite hardware according to scale and SI proposal
 Cisco shall review and settle on options for hosting the ERP solution separately.
 The SI shall offer three years of organizational assistance for the Cisco ERP solution.
  In order to accomplish the gradual development and further enlargement of the ERP
system on its own, the SI will also be responsible for the institutionalization of the
processes and the dissemination of expertise under the CoE (Center of Excellence).
2.1 IMPLEMENTATION PHASES:
 Cisco will procure the ERP solution to the best of its requisite needs and deploy that in
two phases.
 Phase I of the implementation of the ERP will encompass:
o Finance Management

o HR, Payroll

o Manufacturing Units

o Order-Entry Management

 Phase II of the implementation will include:

o Project management

o Maintenance management

o Asset Maintenance Real-Time collaboration

o Integration module to integrate other applications

o Real-Time collaboration

2.2 PROCUREMENT PROCESS:

 Cisco plans to leverage the services rendered by Information Technology vendors
to implement and assist the ERP solution at Cisco.

 With an analysis of the market dynamics and industrial architecture, Cisco has
decided to procure the ERP solution and the ERP implementation services through
bidding process.
 Cisco believes the SI to offer an ERP solution based on the requirements of Cisco
articulated in this RFP and the in-depth knowledge & expertise the SI has on
several ERP solutions, present in the market.

 In addition to technological and economic ERP plans, the SI will give credible OEMs
a solution of ERP and request technical and commercial bids for Cisco 's planned
ERP solution.
 Each bidder can provide only one ERP solution and provide only implementing
 support for the ERP software.
 Cisco will have the option to negotiate and procure the ERP solution proposed by
the SI, directly from the OEM of the ERP solution.
 The implementation services for the proposed ERP solution will be contracted with
the successful bidder as per the RFP.
 The implementation services procured through this bidding process will be
applicable only for the first phase of the ERP.

3. THE REQUEST FOR PROPOSAL (RFP):

 This Request for Proposal (RFP) is given to provide an IT Services Company or System
Integrator with services to propose an ERP solution for three separate departments
(Order Entry, Finance and Manufacturing) and to provide services for Cisco to
introduce the proposed ERP solution.
 The following are included in this RFP

 Criteria for the eligibility of the System Integrator

 Technical requirements for ERP solution
 Scope of work
 Bidding terms
 Response formats to include details against the system integrator eligibility criteria
 Proposed assessment methodology for ERP solution technological and commercial
ideas as well as implementation services
 The RFP Annex includes all the formats that bidders are expected to use to prepare
their proposals / responses.
 Cisco circulates soft copies of RFP documents for the purpose of allowing bidders to
use any of the response formats. These programmed packages include editable
versions as well as non-editable versions. The non-editable version of the RFP
documents circulated by Cisco and held as a copy of the Cisco would be considered as
the authentic version in the event of any contradictions or disputes between the
contents of the RFP documents.
 A draught contract is given in Annexure, with the general terms and conditions to be
negotiated with the effective bidder. At the time of execution, minor improvements
can be made to this.
4. THE BIDDING PROCESS:
 The bidding process for the selection of the System Integrator (SI) to propose and
execute the proposed ERP solution at Cisco consists of the bidding and bid evaluation
phases that follow.
 SI prequalification: The SI prequalification plan will first be assessed for compliance
with the conditions stated in the RFP. The technical proposal will be evaluated and
scored in accordance with the procedures set out in this RFP for only those bidders
who qualify at this level.
 EVALUATION OF THE PROPOSED ERP SOLUTION: The technical proposal for the
proposed ERP solution will be carried out in compliance with the RFP requirements.
The assessment of the technical proposal for a bidder's implementation services can
only take place if the ERP solution proposed by the bidder qualifies the technical
evaluation criteria for the ERP solution as set out in the RFP.
 Evaluation of the implementation services for the proposed ERP: The technical
proposal for the implementation services for the proposed ERP solution will be carried
out in compliance with the terms and conditions of the RFP. The evaluation of the
commercial proposal for a bidder's implementation services will be carried out only if
the bidder qualifies for the professional evaluation of the implementation services as
set out in the RFP.
 Vendor selection on the basis of the combined technical and commercial scores: the
Integrator System (SI) will be selected by the technical and commercial scores defined
in the RFP to provide implementation services. In order to determine the successful
bidder, technical scores for implementation services and commercial bids for
implementation services will be used.
 The commercial proposal for the ERP solution will be used for the purpose of price
discovery and negotiating with the ERP solution OEM if necessary & direct
procurement from the OEM of the ERP solution.
 Finalization of the contract and reward for the ERP solution and facilities for
implementation

5. TECHNICAL REQUIREMENTS:
A systematic methodology for the introduction of the ERP Solution at Cisco must be introduced
by the System Integrator (SI) to ensure that the enterprise is able to meet the project goals and
fully harness the capabilities of the ERP solution and best practises. The implementation
approach should be targeted at streamlining deployment and supplying all project partners
with better outcomes. At the heart of the approach of the project is
 Implementation activities of the ERP solution
 Project plan and structure
  Implementation Approach and methodology
 Post implementation support

5.1 Implementation activities of the ERP solution:

The technique must be properly defined and the strategy planned. It must follow the best
standards for ERP delivery that are internationally agreed and should address the following
large phases or job elements:
 Preparing the Project
o This will concentrate on developing the project charter, interconnecting processes,
planning, the day-to-day action plan before the next immediate process is done,
familiarizing the SI team with Cisco activities and the Cisco team with SI's action
plan.
 Designing the Business Process
o The SI is expected to devise the company design or blue print, which will serve as
the key document for all future operations. The company plan or blue print that will
provide the summary of the processes / solution capabilities listed in the RFP would
cover the processes of the organizational units described in the RFP. This can be
achieved by activities such as system analysis, user workshop to identify processes-
to compromise on software features and design process implementations,
documenting operations / processes of CISCO, documenting processes of AS-IS &
TO-BE, review of AS-IS and TO-BE business processes. The blue print will be
implemented once approved by Cisco. The ERP solution provider can also be a part
of this approval. It is expected that the SI uses the standard template to deploy the
process. The critical outputs of this process:
 The master list of the processes
 Users of the scheme, operations, freedom of access
 The criteria for documentation, the report formats
 The description of interfaces, integration requirements, and the integration
scheme
 The demands and formats for data input
 The appropriate outputs / formats
 The criteria for teaching and change management
 Sizing the hardware
 The best practises and requires for improvements in procedures
 Customization specifications for meeting particular regulatory or operational
criteria
 The SI would also ensure the planning and preservation of the
comprehensive documents.
 Configuration
o Once the blue prints are approved, the system configurations will take place. It will
be a necessary step here to identify the processes that need to be configured. On
configuring the processes, it is expected that the SI carries out a trial run with the
 Cisco data so as to provide the demo to the Cisco team as well as check if any
modifications are required.

 Integration, Testing & Acceptance

o Integration:
 The system shall be developed, implemented and configured on the basis of
scalability, reliability, security, business continuity, maximum performance
of the entire solution and Cisco requirements.
 The architecture must be constructed in a way that makes it possible to
expand based on loosely coupled components.
 The framework should adhere to a Micro - service architecture-driven
application creation and integration methodology, a Service Oriented
Architecture (SOA) version, and the integration methodology should be
driven on REST / SOAP, etc. and Web - enabled services technologies.
 Customization should be enabled by the framework to satisfy the project
specifications. The same can be achieved in the form of add-ons and
routines / patches that can be plugged / unplugged from the base
programme package as the condition occurs where modification is desired.
 Testing:
o SI is expected to formulate procedures outlining Cisco-accepted measures to
perform the system testing.
o For checking the components, the SI can include regular feature test suites.
o The SI shall perform testing to confirm that the process satisfies the given
specifications as mentioned in the RFP and will conform to the procedures
defined.
 User Acceptance:
o Once the tests are conducted, the System Integrator will submit a report for
evaluation and to get a sign-off from Cisco.
o Establish a development strategy to facilitate the system and the integration
testing as well as that the User Acceptance Training (UAT) test cases are
planned.
o Integration checks shall be conducted to confirm that the cross-function
systems are compatible and that transaction data flows correctly through the
systems.
o Creating the acceptance testing protocols to confirm on the consistency with
necessary response period for process operations, technical quality after
implementation, and to remove any operating bugs.
Data Migration
 SI is responsible for the migration of data into the new system. Together with SI,
Cisco RFP for ERP Deployment at Cisco will collectively decide about what data will
be migrated and Cisco will be responsible for storing and ensuring the digitized data
 availability in compliance to that of the form provided by the integrator. During the
initial phases of the project, a comprehensive roadmap is expected for the data
migration activity.
 Critical tasks for data migration:
o Program development for uploading and downloading the data.
o Provision of frameworks/tools for data migration to Cisco
o Populating and migrating the whole system information feature to the ERP
framework
o Training the Cisco team
o Support with data accuracy and honesty management
o Integration checking using the populated master and transaction data of the
optimized device
o Assisting the Cisco Master Data Processing Unit
o Migrating the entire legacy systems and applications to ERP.
o Support with data accuracy and honesty management.
o Integration checking using the populated master and transaction data of the
optimized device.
o Assisting the Cisco Master Data Processing Unit.
 User and Technical training
o User training will ensure that all the stakeholders are well trained and "usage ready"
to execute their roles and responsibilities.
o "Usage Ready" means successfully installing all of the system and ready to be used
by all Cisco intended users to perform all expected transactions successfully as per
the RFP and according to the agreed standards and the SLA’s. Ready for use "shall
come into force only upon acceptance by Cisco."
o Following checks are expected to be done by the integrator to check if the ERP
device for "Usage Ready":
 Facilitate the development of a central support desk for inquiries
 Evaluate the system's stability, utilization and efficiency until it stabilizes.
 Ensure documenting the problems posed during implementation
 End-to-end setup / introduction, checking of volume and tension
 Turn to an area for development.

5.2 Approach for Implementing the ERP solution:

 SI would offer awareness of the best practices implemented for the introduction of
Cisco by other retail sector organizations. As process enhancement is part of the overall
development strategy, SI should suggest potential process enhancement locations that
are detailed in the schedule.
 SI is required at the time of designing business process and while introducing ERP so as
to document all operations in place at all Cisco locations. Where appropriate, with the
ERP approach, including documentation and formats, Cisco would like to follow the
best practices and common procedures available.
  The following list is known to be "Configuration" and not "Customization or Creation."
For the creation of these items, the SI shall not anticipate or suggest any extra charges.
These actions are supposed to be part of the standard attempt to incorporate an ERP
solution.
o Usage of the Customer / User Exits ERP system to fulfil clear service requirements /
expectations
o Description and allocation of User Defined rank for different objects
o Description of Assignment and Permission Controls
o Regular Workflows setup
o Seamless connectivity across all components and engines of the ERP solution or all
other planned third-party applications to satisfy Cisco’s specifications.
o Reports created using the Report Writer / Report painter in the various functional
areas
 Plan for customization/development – As part of the usual endeavor to incorporate the
ERP Solution, the SI can strategy for forthcoming changes.
o Incorporation of digital signature
o Integration for various forms of purchases online
o Biometric attendance system application
o Incorporation of Financial Operation
o Performances of documents in pdf format
o All the documentation that Cisco needs
 Documentation: The SI must ensure that all system configurations, modified programs,
other operations, steps followed in implementation, the complete source code for the
modified software created, are prepared in full documentation. The business process
guide, end-user manual and instruction guide will be prepared by the SI.
 Solution Documentation - With comparison to Cisco, the System Integrator can have
comprehensive final device documents. The SI must provide Cisco with the final user
manual which shall contain all the specifics of all the menus and services offered by the
system.
 Using the tool for project management: The tool can be used by the SI for documenting
project's whole operations, even but not limited to:
o The versions of business design documentations
o The MOM
o System documentation
o Lists of Issues, Resolutions
o Training Requirements

5.3 The ERP Solution Implementation Methodology:

 There will be numerous operating components and tasks in the approach to be applied
by the SI to incorporate the ERP solution. Both these tasks and job components should
concentrate coherently on achieving the following main outcomes.
o Deployed solution consistency.
o Customer satisfaction throughout deployment and during operation.
 o Efficient execution of the result in terms of completeness and timely achievement.
 Implementation Essential Activities: While numerous methods and resources available,
following shall be implemented by the integrator:
o Conducting workshops with all the stakeholders involved, discuss improvements,
establish consensus on the nature of processes, sign deliverables, etc. As needed by
the context, these need to be arranged at various times and in different locations
over the period of the projects.
o Consultation of stakeholders, other than meetings, with those stakeholders defined
by Cisco for essential feedback, analysis, recommendations, explanation of
processes, etc.
o Procedure documentation-recording the innovations, conversations, deliverables,
using common methods and accessible native resources for the ERP solution.
o Job standards / practices for reporting, layout, checking, transfer of data, etc.
o Training the multiple holders of stakes on an ongoing basis.

5.4 Technical Architecture Support:

 The SI will verify the current technology architecture of Cisco and propose a viable
approach to satisfy the market needs of Cisco when applying the ERP framework.
 During the deployment of ERP at Cisco, the SI will also manage the archiving strategy,
access and security aspects.
 The SI may propose the architecture design including all the system specifications,
taking into account the regional distribution and difficulty of deployment, the
connectivity networks at Cisco, and the specifications for data archival & preservation.
 The SI may then propose the design of the overall IT architecture taking into account
the regional distribution and difficulty of deployment, the connectivity networks
required in the country & at Cisco, and the specifications for data preservation and
archives.
 Integrator must confirm that scalability, catastrophe recovery, testing and development
environments are also provided for under the suggested architecture.
 The SI will assist in the provision of comprehensive hardware sizing requirements to be
procured by Cisco. The Integrator must also verify the design to move forward with.

5.5 Auditing and Review:

 Input from user and review:
o The integrators shall create appropriate frameworks during various phases of the
project to obtain input from multiple users of the ERP Solution.
o Such users / stakeholders will be identified by CISCO for providing input.
o The SI is expected to implement the expertise of related projects previously carried
out by it. While these experts are not expected to be on hand full time for the
project, all key deliverables are expected to be reviewed by these experts. Similarly,
for this initiative, the SI shall deploy all QA measures according to globally accepted
 quality requirements.

 Third party audit

o Cisco may select third party experts, taking into account the complexity of
Cisco's operations.
o The integrator is required to provide the organization assigned by Cisco with
complete cooperation for this reason, to do its job professionally.
o Mechanism for accepting input / audit results: There are three forms of reviews
from the third-party consultants employed by Cisco, the users / stakeholders
and the SI's own consultants for the deliverables. On these feedback / audit
results, the following is expected from the SI.
 Both of the suggestions will be shared with Cisco and integrated into the
project based on Cisco’s advice.
 Although, by default, the feedback / audit results for any rework correct the
inadequacy of the consistency of the work generated in the first place, Cisco
will not consider any demands for improvement reports for these reworks.
 SI would develop adequate mechanisms to track the risks over time,
potentially due to the commitment involved to rework poor quality
deliverables.
 At the beginning and at the beginning of each stage, SI must indicate how it
plans to make recommendations and processes to incorporate the
recommendations into the project schedule and deliverables.
 SI will disclose to Cisco how the input has been integrated into the
deliverables of the project and delete a sign from Cisco’s appointed
authority.

5.6 Support for System Stability:

 The SI will have three months of system stabilisation services following the completion
or "full implementation" of the ERP solution.
 The SI will take up the following during this stage:
 After completion or "complete deployment" of the ERP solution, the SI will have three
months of system stabilisation facilities.
 During this step, the SI will accept the following:
o Tasks associated with error correction (if any) in the personalization of the
device
o Maintaining the applied back-ups of the computer
o Coordination with ERP Solution OEM for issues applicable to some ERP solution
dependent on it. RFP for supply and implementation of ERP at CISCO.
o Hand holding of customers
5.7 Technical Support:
 Ensuring ERP Solution OEM resources for system stability, performance tuning,
enhancements, etc. The technological support for the ERP solution is intended to
guarantee OEM support.
 Formulation of all Basic Technologies, System Maintenance, Data Base Management,
Software, Files, Network Protection & Security policies and procedures, backup, etc.
 Prepare the device landscape and procedures for the smooth execution of the ERP
required. This also takes into account the variable pilots and the rollouts.
 The SI will support the CISCO team in carrying out all authorization-related operations
before the ERP system stabilizes (activity party, licenses, accounts, etc.).
 Assist CISCO with the maintenance of legacy data interfaces, print spools, batch
employment, setup of printers, etc.
 Prepare a comprehensive Manual for System Management, Data Management Manual,
Operating Manual, and User Manual to be used by CISCO employees to manage the
development environment allowed by ERP. This often covers how the different
parameters in a live device are monitored / tuned.
 For all the operating areas, finalize the archival policies. The required modifications
must be completed and tested.
 Prepare the appropriate disaster recovery system.
 24*7 assistance for practical and technological sector troubleshooting.

5.8 Post Implementation Support:

 SI shall preserve details on entitlement to updates, changes, refreshes, replacements
and repair of the ERP solution.
 If it is appropriate to install / reinstall / de-install the Operating System or external
versions of the Operating System, the same can be achieved as part of the ATS.
 SI can make the required modifications / interface updates to incorporate various
iterations of the ERP solution.
 Updates / Upgrades / New Versions / New Launches of the applications and OS are
given and introduced by the SI from time to time as needed. If and when issued by ERP
Solution OEM, the SI can ensure improvements, modifications & patches of the ERP
Solution and instruments to Cisco.
 Patches for the systems will be provided by the integrator for all the applications
 The services for license management will be given by the SI.
 Support services post the implementation will commence once the consumer
acceptance services have been completed i.e. after three months.
 Support services are expected from the SI for a year after the "Full Implementation"
announcement.
 In time buckets of six months each, Cisco can choose to expand the post-
implementation support services by two more years.

Project Deliverables
 It is assumed that only when the deliverables of that stage are approved can the project
pass from one stage to the next. The following table summarizes the key deliverables in
the process to be commenced:

 For the sake of comprehensiveness, SI is urged to recommend any additional

deliverables during executing to boost the quality of the process.
 On each of the mile stones, it is expected that the integrator includes specifics of the
corresponding deliverables as well as distribution of priced goods on such mile stones.
The foundation for payments for the matching valued goods would be the mile stone to
deliverables & supply listing.
 Acceptance requirements for deliverables
o For each stage, the approval conditions are the presentation and approval of all
deliverables specified for that stage. The formal recognition by CISCO of the
deliverables of the process signifies the completion of the process and the clearance
 for the start of the next phase and the invoice for payment by CISCO, provided that
the payment is included in the milestone.
o Approval requirements shall be defined for each deliverable prior to the start of
each step-in accordance with the process outlined in the following paragraphs.
o SI should have models of deliverables proposed. SI will consult with the CISCO
Project Manager at the outset of each stage to discuss the relevant prototypes,
customized to meet the project requirements, and settle on the nature, style, and
quality of each of the key deliverables for that level.
o For each deliverable, the decisions produced during this meeting will be recorded in
a Deliverable Summary Document (DRD).
o Only after the deliverables of a given project milestone are approved by the
appropriate authority can the CISCO team go ahead and shift from one project
milestone to the other project milestone. Therefore, at the outset of the project,
the process for application, analysis, revision and approval will be set up. The SI is
expected to submit as part of the proposal the specifics of this protocol.

6. Principle Point of Contact:

The following are some of the important rules with respect to the communication between the
bidder and CISCO:

 This RFP does not commit Cisco to enter into an agreement or similar undertaking with
the bidder or any other organization and Cisco shall have the right to reject or accept
any proposal or offer.
 All the communication between CISCO and the bidder will be done through the
representatives appointed by CISCO.
 No oral communication will be termed as an official communication.
 Only those communication done through authorized personals will be considered as
official communication.

The authorized representatives of CISCO are:

1. Mr. Robin - Business Integration Specialist
 Phone no - 020-257931000
 Email Add - robin@cisco.com
 Address - 170 West Tasman Dr. San Jose, CA 95134 USA
2. Randy Pond - Director of manufacturing & Co-leader of the project
 Phone no - 020-257930111
 Email Add - randypond@cisco.com
 Address - 170 West Tasman Dr. San Jose, CA 95134 USA
7. Budget:
The implementation cost of services, support cost for ERP solution, the training cost, data
migration, etc. will be paid by CISCO on the basis of completion of a milestone of the project
and only after the deliverables are accepted.
The overall cost of the project will be paid in 4 stages. The following is the amount paid on the
basis of the project as per the completion of the project:

 At the Project Preparation phase, 15% of the cost will be paid

 35% of the cost will be paid after the completion of Blueprint phase
 25% project cost will be paid after completion of the project
 The final 25% service cost of the project will be paid after successful deployment and
adoption of the ERP system.

The following is the cost of the service paid on the basis of the task performed:

Task Cost
Development $80000
Deployment $10000
Training $20000
Maintenance $10000
All the costs are non-negotiable.

8. SELECTION CRITERIA:
The evaluator committee would consider the completeness of the proposal, how well the
offeror fulfilled the response criteria, the responsiveness of the offeror to requests, the amount
and type of exemptions (if any) made to the terms and conditions by the offeror, the overall
cost of ownership, and how well the proposed solution of the offeror satisfies the
requirements.
8.1 Proposal Evaluation
In order to decide the proponents are eligible for consideration, the evaluator may review all
proposals. Proposers are expected to comply with the general qualifications set out in the RFP.
If the proposer does not meet the eligibility requirements, their bids will be refused and will not
be considered for further consideration.
On the QCBS (Quality cum Cost Based Selection) framework, the supplier will be assessed.
Initially, proposals will be checked to verify that the submission conforms to the requirements
specified. The committee will not assess any responses that deviate substantially from the basic
purpose and/or fail to fulfil the necessary criteria.
Proposals submitted will be evaluated based on the below mentioned criterias:

 The content of the plan and its consistency

 Integration and compatibility with current hardware and applications
 Ability to meet criteria according to the RFP requirement.
 Well-thought-out schedule and the desired go-live date roadmap.
 Proven technological capacity to design, install and promote the device proposed.
 Price and price expected
 Perceived risk level
 Corporations and financial stability
 References
8.2 RFP RESPONSE FORMAT
Your RFP response should be according to the format defined in the table below. Your response should
include each section in the order presented. Failure to address all items will impact the evaluation and
may classify the response as non‐responsive and preclude it from further consideration. Do not provide
references to other sections, documents or websites for the information required, it should be
specifically included in the RFP response.

Section Title Contents

Section 1 Cover Page Provider Logo, Name of the firm and the City in which the provider
is based.
Section 2 Offerors Provide an overview of the qualifications and experience of your
Qualifications firm including the following:
and Experience a) Provide an overview description of the Offeror’s
qualification related to the requirements defined in this
RFP.
b) Provide the number of years the firm has provided the
products and services outlined in the RFP.
c) Provide the name of the Principal or Project Manager who
will have direct and continued responsibility for the
project. This person will be the contact person on all
matters dealing with the project and will handle the day‐
to‐day activities through completion.
d) Provide a resume for all staff/employees assigned to the
proposed implementation team including a list of the tasks
for which they will be responsible.
e) Identify services that will be outsourced to a sub‐
contractor. The Offeror will be responsible for verifying the
experience and qualifications for any outsourced work to
sub‐contractors.

Section 3 Key System Submit the Key Functional and Technical Requirements provided
Requirements against each item and have a specific qualitative comment about
how the software supports the requirement as defined.
Section 4 Pricing Submit the pricing summary provided as in this RFP. This document
 should tie to the Total Cost. Pricing must be complete and list any
available discounts. Pricing information supplied with the response
must be valid for at least 150 days. All one‐time and recurring costs
must be fully provided. Provide estimates of total hours and hourly
rates associated to each line item. Estimates for implementation
services should include, but not be limited to, the following:
a) Implementation of the software  
b) System configuration
c) Training
d) Data conversion
e) Interfaces or integration 
f) Travel  
g) Post Go‐Live Support
Section 5 Implementation An overview of Offeror’s implementation methodology:
a) MS Project Plan: including phases, tasks and timeline.
b) Implement using phases or all modules at one time.
c) Process Improvement: approach to process improvement
through implementation.
d) Change Management: tools and methodology.
e) Environments available (production, test, training, etc.) 
f) Testing: configuration, technical, user acceptance, etc.
g) Training: approach, resources available, documentation
provided.
h) Integration: approach, tools, experience.
i) Post Go‐Live Implementation Support.
Section 6 Support Overview of the support services offered and recommended for
the products proposed in this RFP, including:
a) System Administration: performance monitoring, tuning,
loading of patches and version releases.  
b) Disaster Planning and Recovery: for on‐premises and/or
hosted options proposed.
c) User Groups and conferences, community forums,
knowledge base, etc.
d) End User Support: number of staff offering user support,
hours of service, average and guaranteed response time,
ticketing system used, escalation process, user forums,
etc.  
e) Software Upgrades: timing, support provided,
documentation. 
f) Documentation: description and examples of user,
administrator, and technical system reference documents
and help materials, e.g. procedures, definitions,
configuration, API's, etc.
Section 7 Training ‐ Post Training resources provided for technical and user training post go‐
Go‐Live live; approach to delivery, training materials provided, available
online tutorials, etc.  
8.3 SUBMITTAL FORMAT AND PROPOSAL TIME
The Format includes a detailed document, with the Cover page containing the Provider Logo,
Name and the City in which the provider is based. The document details include details about
the offerors qualifications and experience, key system requirements, Pricing Summary, how the
solution is catering to the budget, technical requirements and what special the provider is
offering.
The document should also contain details regarding similar projects that have been undertaken
by the company and how have they tackled with the given problem. The Offeror shall submit a
proposal which demonstrates and provides evidence that the Offeror has the capabilities, professional
expertise, and experience to perform the services described herein

All Proposals shall be in a sealed envelope and clearly marked in the lower left corner: “ERP
SOFTWARE AND IMPLEMENTATION SERVICES.” Proposals sent by Mail or other carrier that
requires the use of a proprietary mailing envelope shall be in a sealed envelope inside the
proprietary mailing envelope. The return address area of the sealed proposal envelope shall
contain the legal company name, name of company contacts, complete mailing address, and
email address of the Offeror
The proposals shall be delivered to:
Address
Email Add - robin@cisco.com
170 West Tasman Dr. San Jose, CA 95134 USA
Phone no - 020-257931000

The submissions should be done on the Email ID cto@cisco.com. The proposals hard copy for
the same should also be received to the Cisco Main Office at San Jose by 5:00 p.m. IST on
November 19, 2020. Proposals received after 5:00 p.m. IST on November 19, 2020 will not be
considered. The Offeror has the sole responsibility to have the proposal received by the Bedford
County Fiscal Management Department at the above address and by the above stated time and date

From the issue date of the RFP until contract award is made, respondents are not permitted to
communicate with any employee or agent about the subject or contents of the RFP except as
outlined in the RFP. Violation of this provision may result in rejection of the respondent’s
submission. No information provided verbally or by any other personnel will be considered. All
respondents shall use the RFP and its exhibits and amendments as the sole basis for proposal at
this time.
Proposals should be prepared simply, providing a straightforward, concise delineation of the
capabilities necessary to satisfy the requirements of the RFP. Technical literature and elaborate
promotional materials should not be submitted at this time. CISCO will select the finalist by
compiling the proposal and cost evaluation, scripted demonstration results, site visits and
references. The top ranked Offeror that the County feels would make the best solution provider
will be selected.