|
a. Identifying the data elements to be converted based on business requirements;
b. Providing formats in which the identified data elements must be collected to facilitate data conversion, clearly categorizing mandatory and optional elements;
c. Conversion of the extracted and cleansed data to the new system to create master files and opening balance data (where appropriate);
d. Verifying the accuracy of the data conversion process.
3.2.4 Customization Scope
No change will be made to the ERP code under any circumstances to ensure that future upgrades, enhancements and bug fixes are not impacted. A certification to this that it has been followed must be provided by the ERP Application vendor before the final acceptance of the solution by VPT. Incase any customization is warranted the bidder should provide the solution by ensuring no impact to the future upgrades, enhancements and bug fixes by taking necessary clearances from VPT. VPT expects successful bidder to deliver the ERP solution with minimal customization inside the ERP system to ensure easy upgrades in the future.
Reports
ERP delivers certain standard reports across modules. However, VPT anticipates that some custom reports would still need to be developed if the standard reports do not meet VPT’s specific requirements.
These reports would include those which would extract and present information already in the database in a specified format or could require some intelligence/ calculations built into it. Some reports would be required to facilitate execution of transactions.
Given the above, the bidder will be required to customize around fifty (50) critical and complex reports across all components of the ERP Solution. The specific number and distribution of reports to be customized amongst various modules will be finalized during the implementation stage, upto a maximum of 100 (including critical reports).
Development of custom reports must follow well-defined methodology. A brief description of the methodology employed when developing custom applications / reports should be included in the response to the Tender Document
Alerts / Notifications
VPT expects to have system generated alerts / notifications in various processes in the ERP solution. These alerts / notifications could be time based or event based. Some of such alerts / notifications that are expected to be provided in ERP Solution have been described in Annexure # 5
3.3. FUNCTIONAL SCOPE
Some of the key processes, which VPT expects the System Integrator to study, include (but are not limited to the following):
3.3.1. Finance
1. Maintain Chart of Accounts
2. Prepare Yearly Budgets
3. Manage Working Results
4. Monitor Administrative Budget
5. Handle Stores, Spares, Equipment and Consumables Payments
6. Handle Works Bills
7. Handle Miscellaneous Bills
8. Handle Payment to Railways
9. Process Insurance Claims
10. Manage Miscellaneous Payments
11. Payroll, Advances and Final Settlement
12. Provident Fund, Gratuity and Pension
13. Manage Cash and Bank
14. Handle Stores, Spares, Equipment and Consumables – Stock
Accounting
15. Inventory Valuation
16. Manage Costing
17. Manage Fixed Assets
18. Quarterly and Annual Closing and Consolidation
19. Preparation of Financial Statements
20. Techno Economical Project Cost Control Process – Expansion for capacity expansion of the Port.
21. Manage Internal Audit
22. Manage Excise Duty and Service Tax
23. Manage Sales Tax, VAT
24. Manage Income Tax and Wealth Tax
25 Preparation of draft balance sheet
3.3.2 HR Management
1. Manage Transfers
2. Manage Training programmes to the employees/stakeholders.
3. Handle Performance Appraisal system
4. Manage Promotions
5. Handle Industrial Relations
6. Manpower Planning
7. Manage Probation
8. Handle Joining
9. Internal recruitment
10. External Recruitment
11. General Administration
12. Discipline Management
13. Corporate Communications
14. Labor Management
15. Handling Compensation & Benefits
18. Medical care
19. Corporate social responsibility (CSR)
20. Daily Pass System/Gate Monitoring system
22. Competency management & Succession planning
3.3.4 Procurement & Inventory
1. Manage Vendors -Materials Management
2. Manage Vendors -Works Contracts
3. Raise Indent
4. Procure Spares, Consumables & other Materials
5. Procure Services -Works Contracts
6. Procure Services -Materials Management
8. Manage Stores –Receipt and Custody
9. Manage Stores- Execute Inventory Transactions
10. Manage Stores - Manage Discrepancy and Claims
11. Manage Stores- Stock Control and Planning
12. Manage Scrap Disposals through Tendering and Auctions
13. Manage Licenses
14. Manage Issues Post Award of Contract
15. Manage Medical Stores
16. Manage Inspection- Pre Dispatch Inspection
17. Manage Inspection- Receipt Inspection
18. Inventory analysis
19. Inventory control
3.3.5 Projects
1. Project planning
2. Procure Services -Project Contracts
2. Manage Project Procurement
3. Project Monitoring and control
4. Preparation of estimates for Civil/Mechanical/Electrical Engineering/Marine works with standard schedule of rates, reusable data for estimates.
5. Preparation of billing for running bills, part bills and final bills including recovery, adjustment of advances, release of Security Deposit and EMD etc.
3.3.6 Port Operations (the existing application software at the port is based on VB/COM+ based technology with Oracle 9i backend. The source code of the same shall be made available to the successful bidder)
1. Shipping operations management
2. Berth Planning
3. Cargo storage management
4. Railway operations management
5. Lease/ License management
6. Marine operations management
7. Interface with Railways (FOIS)
8. Port Community System/EDI interface
9. Billing for all the services
10. Tariff fixation
11. Portal for port users to obtain services
12. Interfacing with payment systems
13. Assignment of resources optimally
14. Resource Optimization for men, material, machinery & plant.
3.3.6A. The following are the different applications for Port operations which are presently in use:
VPOMS in VB/COM+ environment with Oracle DB.
PCS Application in VB/COM+ environment with Oracle DB.
Cargo stacking application in ASP.net environment with Oracle DB.
Active Server Pages for vessels in Port, vessels at Roads, vessels expected, vessels sailed and deposit balances.
All these Applications use the same Database.
3.3.7 Estate Management
1. Estate Master register
2. Status of each estate item
3. Lease/ lessee Management
4 GIS interfacing
8. Billing
6. Disputes/court cases
7 Receipts accounting
8. Pending receipts and age wise analysis
3.3.8 Maintenance Management
1. Equipment master maintenance
2. Work order generation
3. Preventive maintenance schedules and work orders
4. Work order planning and monitoring
5. Maintenance planning & scheduling for all the assets
6. Job costing
7. Root cause analysis
8. Maintenance costing
3.3.9. Integrating/ developing/ COTS applications
3.3.9.1 The port has the following applications which need to be integrated to the ERP software:
- Hospital Management system,
- e-procurement system of NIC,
- Biometric Access Control system,
- IP Security cameras and video analytics management software,
- AIS radar,
- RFID boom barrier system,
- GPS devices & tracking software and
- Weighbridges.
- Survey launch DGPS system
The data from these applications must be available on the BI module screens along with other data. They should form part of the MIS and BI reports. The bidder may give details of this integration. The actual formats will be discussed during detailing.
3.3.9.2. Development / Commercially Off The Shelf software
The software for Port Operations (including Railway Operations) should be either developed on ERP platform or supply Commercially Off The Shelf software and integrate with the ERP software. VPT is interested in having the ERP solution with minimal customization inside the ERP product. The data from these applications must be available on the BI module screens along with other data. They should form part of the MIS and BI reports. The bidder may give details of this integration. The actual formats will be discussed during detailing.
3.3.10. Business Intelligence
1. Berth wise profit/loss
2. Commodity wise profit/loss
3. Ship wise profit/loss
4. Activity wise income/expenditure
5. Operating ratio/surplus
6. Asset turnover
7. Return on capital employed
8. Critical spares consumption, lead time
9. Rate of loading of OHP
10. Loco wise no of trains/wagons hauled in empty/load condition
11. Wagon type wise stock lying in port yards in load/empty position
12. Time/cost overrun of projects with respect to project milestones
13. Status of fenders/bollards
14. Succession planning – employees due for retire and the post filling
15. Stevedore wise revenue earned/lost due to delays
16. Stack area turnover
17. Pollution control measures, expenditure, results analysis
18. Tug wise availability/utilization; income/expenditure analysis
19. Outstanding dues/liabilities analysis
20. PPP operator performance analysis
21. Incentive payment vis-à-vis value added work
22. Average line occupation
23. Derailments loco, location, cargo, wagon type, staff reason analysis
24. Contractor performance analysis
25. Equipment/facility wise revenue earned vis-à-vis energy consumption
26. Reason wise, cargo wise, stevedore wise pre-berthing detention analysis
27. Non-working time analysis
28. Record performance analysis
29. Any other customizable MIS reports using data from the above modules.
30. Economic value added for each activity to be linked to ROCE.
3.4. TECHNICAL SCOPE
The following features essentially, but not limited to, shall characterize the system:
3.4.1 User Interface:
The end user interfaces should be both web interface and Graphic User Interface (GUI) based. Wherever possible, data should be available for entry from a drop-down list. There should be field level validation of the data being entered. In case of an error in data type, the error message should be customized to VPT’s specification. It should be possible for the system administrator to restrict certain values for entry to specific users (e.g. account codes). It should also be possible for the users to retrieve data entered incorrectly and change the same subject to defined security procedure.
3.4.2 Single Point Data Entry avoiding Duplicate Data Entry:
It is imperative that the ERP solution eliminates instances of duplicate data entry. There should be a single set of data which once created should be available for use by all users, thereby eliminating the need for multiple data entry and ensuring data consistency across the system. This applies not only to the transaction level data but also to all master data, which may be shared across functions.
The system should support capture and storage of statutory documents like invoices, etc. as part of transaction for avoiding duplicate copies of such documents and access by all concerned from a single source.
3.4.3 Centralized / Common Master Data
The solution envisaged by VPT assumes a centralized master data repository to be shared by all the concerned based on their requirements.
These master data would include but not be limited to the following:
a. Chart of Account values
b. Item / Service Master
c. Vendor Master
d. Customer Master
e. Fixed Assets Category Master
f. Employee Master
g. Pensioner Master
h. Estate master
3.4.4 Data Access and Security
VPT believes that ensuring security of data in an ERP environment is critical.
Data security is essential at VPT from two angles;
To restrict access to / sharing of confidential data; and
To ensure that data is not changed or destroyed, either inadvertently or intentionally, by any user or an external party.
VPT expects that bidders will ensure following three aspects of data security and access:
Ensuring that only those with the relevant authority can access the ERP System;
Ensuring that those with access to the ERP System have access only to the data which is relevant to them; and
Access to the relevant data is further restricted to either inquiry or update depending on the responsibility.
The ERP Solution must also facilitate on-line monitoring of ERP modules access and usage.
3.4.5 Audit Trail
The Bidders must ensure that the ERP Solution proposed by them has extensive facility with respect to maintaining audit trail. Any addition, deletion or modification to an existing record, whether master or transaction, must bear the date and time stamp, the name of the log-in user who made the change and the terminal from which the change was made. It should also be possible to maintain details of the original record and subsequent changes to the same. Standard audit related reports should be available.
3.4.6 Data Archival
In order to meet statutory requirements, archiving and easy retrieval of data is important for VPT. The bidder must ensure that the proposed ERP Solution provides a user driven data archiving capability, with support for flexible archiving periods and select Tables. The system should also be able to restore previously archived data for on-line inquiry and reporting as and when required. The bidder will also provide a data archiving procedure based on best practices.
3.4.7 On Line Help Facility
The ERP Solution should have an online help capability for every form / process in the ERP Solution. This on-line help text / facility should be customizable to make it VPT processes specific. The Bidder must indicate how he proposes to make the online help specific to VPT.
3.4.8 Workflow Based Applications
VPT expects the proposed ERP Solution will support workflow-based functionalities. In other words, it expects the ERP Solution to be capable of replacing the current physical flow of documents across business team with the flow of electronic data. For instance, if purchase requisitions require approval based on the item or service being procured, then the workflow in the ERP Solution should forward the link of a purchase requisition electronically to a user/approver based on the criteria defined by VPT.
3.5. Deliverables:
The bidder will deliver the following at minimum. In case of consortium arrangement, the consortium member responsible for each deliverable must be clearly indicated. While submitting the bid, the consortium member responsible for each deliverable must sign against the deliverable listed in the table below. However, the consortium leader will be responsible for performance of the whole contract jointly and severally with the consortium partners. The acceptance criteria of the deliverables will be mutually agreed between VPT and Bidder at the commencement of the project/each stage.
SNO
|
Activity
|
Deliverable
|
Deliverable schedule
|
IMPLEMENTATION SERVICES
|
Project Initiation
|
1
|
The bidder will study the scope of work with respect to existing processes for which VPT has provided the As-Is process documentation, legacy applications, data availability, integration, customization etc. The bidder shall furnish his conclusions in form of a Report and a presentation to VPT
|
Project Initiation
Report & Presentation
|
Bidder to
suggest
suitable time
line for each
activity based
on the proposed ERP
Solution,
Project Plan
and their
Methodology
limiting to the
Overall time limit provided for project
Implementation.
|
2
|
The Project Plan and the high-level approach will be discussed with / presented to VPT which may suggest changes if necessary. Once the above has been discussed and changes, if any, incorporated, the bidder will prepare the Project Management Plan. This plan will :
i) Contain a project plan in MS
Project form
ii) Indicate the proposed approach towards key phases / activities of the project such as process engineering, legacy applications integration, data conversion, change management, training, documentation etc. The objective of this will be to provide a bird’s eye view of the proposed
approach of the bidder towards
execution of the project.
|
Project Management Plan containing the Project Plan
|
3
|
The bidder will carry out a detailed study to fine tune the specific requirements with respect to the hardware. This will be spelt out in the Hardware Requirement Report
|
Hardware Requirement
Report
|
4
|
The bidder will conduct a As-Is
Business Process & Information
Requirement study. The bidder will, subject to necessary confidentiality agreement, be provided with access to documents of As-Is studies conducted by VPT during pre-implementation study for their reference only.
|
As-Is Business
Process and Information Requirement Document.
|
5
|
Process and methodology adopted for Quality Assurance must be documented and periodic reports submitted to VPT
|
QA process document
|
Bidder to
suggest
suitable time
line for each
activity based
on the proposed ERP
Solution,
Project Plan
and their
Methodology
limiting to the
Overall time limit provided for project
Implementation.
|
Solution Development
|
6
|
Based on the agreed To-Be Processes, the bidder will prepare a prototype of the solution (including all customization, interfaces etc).
|
Solution Prototype with
Necessary documentation.
|
Bidder to
suggest
suitable time
line for each
activity based
on the
proposed ERP
Solution,
Project Plan
and their
Methodology
limiting to the
overall time limit
provided for
project
implementation.
|
7
|
The solution prototype should be made available for validation by VPT. VPT expects that the prototype validation will go through multiple iterations (often referred to as Conference Room Pilot sessions). The prototype validation must be conducted in a formal set up with proper CRP scripts prepared by the bidder and approved by VPT.
|
Solution Prototype
validation, CRP scripts and validation
clearance by VPT.
|
8
|
The feedback provided to the bidder after each round of validation / CRP must be documented and signed off by the VPT nominated users.
|
Solution Prototype
validation / CRP
feedback documented
|
9
|
Changes to the solution must be
presented to the users in next round of solution validation or CRP. This will be an iterative process till the solution prototype is signed off as acceptable by VPT.
|
Subsequent rounds of
Solution prototype
validation / CRP; Sign-off of the same
|
10
|
Process and methodology adopted for Quality Assurance must be documented and periodic reports submitted to VPT.
|
QA process
Document
|
Solution Validation
|
11
|
Once the solution prototype is signed off, the bidder will plan for the Unit Tests (UT), System Integration Tests (SIT), User Acceptance Tests (UAT),) and any other tests as may be necessary.
|
UT, SIT & UAT
Program
|
Bidder to
suggest
suitable time
line for each
activity based
on the
proposed ERP
Solution,
Project Plan
and their
Methodology
limiting to the
overall time limit
provided for
project
implementation.
|
12
|
The UT, SIT, UAT and other test scripts will be prepared by the bidder and validated by VPT.
|
Script for UT, SIT, UAT and other tests, if any
|
13
|
Once finalized, the bidder will assist VPT nominated user to conduct the UT, SIT, UAT and such other tests. User feedback from these tests will be documented by the bidder.
|
UT, SIT, UAT and other tests conducted and
Feedback documented
|
14
|
The data conversion test will also be conducted and signed off by the VPT Business team with assistance of the bidder in terms of format, completeness and correctness.
|
Data Conversion
Test feedback
|
15
|
Feedback of the UT, SIT, UAT data conversion and other tests will be presented to VPT in form of a report and a presentation to enable VPT decide on the readiness of the going live with solution.
|
UT, SIT, UAT
data conversion
and other tests
report & presentation
|
16
|
Submit the Access Control Matrix
Template to VPT, after the template is filled up by VPT, Configure the Access Control Matrix in the Application by bidder.
|
Access Control
Matrix Template and the Configured
Application print of the user access.
|
17
|
Based on the report and the feedback received from the users, VPT may recommend additional tests to be conducted in specific areas. Conduct of such additional tests and the bidder must document the results.
|
Additional tests
conducted in
specific areas
and test results
documented
|
18
|
The bidder should deploy performance-testing tools to proactively establish adherence to agreed performance levels with the representative data and the concurrent users.
|
Performance
test results
|
19
|
During the stabilization period post Go-Live, the performance will be observed on a continuous basis.
|
Stabilization
Acceptance Results
|
20
|
During the PG period the performance will be observed on continuous basis.
|
PG test results
|
Data Conversion
|
21
|
The bidder will provide data conversion strategy
|
Data Conversion
Strategy
|
Bidder to
suggest
suitable time
line for each
activity based
on the proposed ERP
Solution,
Project Plan and their
Methodology
limiting to the
overall time limit
provided for
project
implementation.
|
22
|
The bidder will provide the template in which each data element to be converted must be provided by VPT.
|
Template for data to be converted
|
23
|
The bidder must validate the data provided in terms of format.
|
Validate data provided in terms of format
|
24
|
The bidder will prepare the necessary data conversion scripts and document the same. He will also identify/provide necessary reports to facilitate verification of data converted.
|
Data conversion scripts & necessary documentation
|
25
|
The bidder will execute complete /
sample data conversion on test
instance for each data element and get sign off from users in terms of adequacy and correctness.
|
Data conversion test results for each data element
|
26
|
The bidder will execute data
conversion on production instance and obtain signoff from VPT
|
Data conversion executed on Production
Instance
|
27
|
The bidder will provide a scheme for archival of old data required to be maintained for statutory and other reporting purposes and retrieval of the same in the new ERP environment.
|
Archival and retrieval document
|
Assist in Change Managing
|
28
|
The bidder will give report /presentation to the VPT on anticipated change management related issues and propose solutions to overcome them.
|
Change Management
Approach Report /
Presentation
|
Bidder to
suggest
suitable time
line for each
activity based
on the
proposed ERP
Solution,
Project Plan
and their
Methodology
limiting to the
overall time limit
provided for
project
implementation
|
29
|
The bidder will provide guidelines in setting up an ERP Helpdesk including development of Service Level Agreements (SLA).
|
ERP Helpdesk
Guidelines
|
30
|
The bidder will conduct Change
Management programs on one-on-one individual basis or in groups and at different locations.
|
Tentative schedule and
approach document
|
31
|
The bidder will propose effectiveness measurement criteria on change management and its monitoring.
|
Effectiveness
measurement
document
|
Training
|
32
|
Identify training requirements for VPT Core / Technical team members and end-users.
|
Training Requirement
Report
|
Bidder to
suggest
suitable time
line for each
activity based
on the
proposed ERP
Solution,
Project Plan
and their
Methodology
limiting to the
overall time limit
provided for
project
implementation.
However, the
training to be
imparted by
Product Vendor
for Core team
need to be
planned before
the
implementation
activity begins.
|
33
|
A detailed Training Plan giving details of content, duration and training material to be provided to different categories of participants as identified by the VPT.
|
Training Plan for VPT Users
|
34
|
Specific training to VPT core team from Product Vendor on
a) Standard product functionalities
available in the chosen ERP by the ERP Product Vendor to achieve a level of knowledge of a Certified Product Consultant as per the standard curriculum.
b) Integrated Business Process in
standard ERP product by the
Product Vendor
|
Training plan for Solution Prototype
Validation
|
35
|
Specific training by the System Integrator to core team & business team to prepare them for testing and accepting fully configured solution prototype.
|
Training plan for Solution Prototype
Validation
|
36
|
Hands-on training to VPT core team members on ERP configurations, the processes and other applications.
|
ERP Training for VPT Core Team Members
|
37
|
Hands-on training to VPT technical team members on ERP and other applications, including training to VPT database administrators, System administrators including
backup & restoration, Development including reports and maintenance of package. .
|
ERP Training for VPT
Technical Team
Members
|
38
|
Training to Technical team on
Administration of servers, storage,
SAN and backup systems
|
Hardware training to VPT Technical Team
Members
|
39
|
A fully configured solution prototype for training VPT end-users.
|
Configured Solution
Prototype for Training
|
40
|
Hands-on training to VPT end-users (about 400 including Port operations) on ERP and other applications.
|
ERP Training for VPT end users.
|
41
|
Preparation of VPT ERP Solution
Training Manual and end user manuals keeping in mind the specific requirements of processes and users at VPT.
|
VPT ERP Solution
Training and end user
Manuals
|
42
|
Preparation of VPT ERP Systems
Management Manual keeping in mind the specific configuration of solution implemented at VPT.
|
VPT ERP Systems
Management Manual
|
VIII Custom Development
|
43
|
The bidder must deliver all custom development as has been described in his Bid / Proposal.
|
Custom development
|
Bidder to
Suggest suitable time
line for each
activity based
on the proposed ERP Solution,
Project Plan and their Methodology
limiting to the
overall time limit
provided for
project
implementation.
|
44
|
The bidder must provide relevant documentation about the business case for the custom development,
description of the code etc
|
Relevant
Documentation
|
IX Integration
|
45
|
The bidder must integrate the ERP Solution with certain retained legacy applications or new bolt-on applications. Some of the key applications are detailed in Annexure___ of the document. The detailed is only an indicative list and the complete list will depend on the final solution proposed by the bidder and accepted by VPT.
|
Integration
Document between ERP Solutions and
other legacy systems
|
Bidder to
Suggest suitable time line based on the proposed
ERP Solution,
Project Plan
and their
Methodology
|
X Executing Cut-Over from Legacy Applications to ERP Solution
|
46
|
The bidder will configure Production instance of the ERP Solution with assistance from the VPT core team.
|
Fully configured
Production Instance
|
Bidder to
Suggest suitable time line based on
the proposed
ERP Solution,
Project Plan and their Methodology
|
47
|
The bidder will present a cut-over strategy to VPT for their validation and approval.
|
Cut-over strategy
|
48
|
Executing the cut-over from the legacy applications to the ERP Solution in accordance with the approved cut-over strategy.
|
Executing cutover
|
49
|
In case the cut over does not
synchronize with the accounting period (such as beginning of the financial year
etc), the bidder will suggest and
provide the required strategy for building data for the prior period.
|
Strategy for prior period data buildup
|
XI Post Implementation Support
|
50
|
The bidder will provide post
implementation support for six months (minimum of two quarterly closings) after go-live.
|
Post go-live support for six months
|
Bidder to
suggest
suitable time
line based on
the proposed
ERP Solution
|
51
|
The bidder is expected to transfer knowledge and provide guidelines in setting up and managing an ERP Helpdesk by VPT, including the processes to be followed in logging request for assistance, assigning
requests to specific helpdesk
individual, recording resolution and tracking the overall time frame from logging a call to its resolution. The knowledge and guidelines will encompass all aspects of the help desk such as configuration, report writing, database administration, system administration etc.
|
Helpdesk guidelines
|
Bidder to
suggest
suitable time
line based on
the proposed
ERP Solution
At least one
month prior to
first go-live date
|
SUPPLY & INSTALLATION OF HARDWARE
|
52
|
The bidder shall perform study of hardware configurations requirements for Production, Quality Assurance/ Training and Development environments based on high availability “active-active” architecture.
|
System Configuration
document
|
Bidder to
suggest
suitable time
line based on
the proposed
ERP Solution,
Project Plan
and their
Methodology
|
53
|
Supply hardware and software
components including servers,
operating system, database, utilities, enterprise management system, backup hardware with license
documentation and media.
|
Supply of hardware, and related software.
|
Bidder to suggest
suitable time
line based on
the proposed
ERP Solution,
Project Plan and their Methodology
|
54
|
Services covering installation and commissioning, Performance Guarantee tests, training on systems & database administration and backup solution.
|
Installation and
Commissioning of hardware and network,
Training
|
Installation and
commissioning
of hardware
and Training
|
SUPPLY OF ERP APPLICATION, DATABASE, RELATED SOFTWARE &
TOOLS, USER LICENSES
|
55
|
ERP license supply
|
Delivery of licenses
|
Bidder to
|
56
|
The bidder will supply the ERP
Application, database, related software and tools, user licenses etc. that will be necessary. The number of expected ERP users and its distribution among different tracks is given in Annexure #4. Documentation related to the above must be supplied in both hard and softcopy. The bidder will be responsible for ensuring that the ERP Application, database, related software and tools, user licenses etc. are delivered in time and as per agreed terms and conditions.
|
ERP Application,
database, related software and tools, user licenses etc with relevant documentation
|
Bidder to suggest
suitable time line based on the proposed
ERP Solution and their
Methodology,
Project Plan
|
57
|
The number of expected ERP users and its distribution among different tracks is given in Annexure #5. Documentation related to the above must be supplied in both hard and soft copy. The bidder will be responsible for ensuring that the ERP Application, database, related software and tools, user licenses etc. are delivered in time and as per agreed terms and conditions.
|
ERP Application,
database, related software and tools, user licenses etc with relevant documentation
|
58
|
Documentation regarding Installation of the ERP Application, database, related software and tools, activation of user licenses etc which will be necessary for implementation of the ERP Project at VPT as per this Tender Document. Must be supplied in both hard and soft copy.
|
Installation of the ERP Application, database, related software and tools, activation of user licenses etc.
|
59
|
During the stabilization period, the performance will be observed on a continuous basis
|
Stabilization
Acceptance Results
|
60
|
During the PG period the performance will be observed on continuous basis
|
PG test results
|
ACTIVE-ACTIVE SOLUTION AND BACK-UP POLICY
|
61
|
The bidder will also provide an ”active-active” architecture and implementation including the backup plan keeping in mind the specific operational requirements.
|
Active-Active high availability & back up Plan
|
Bidder to suggest
suitable time
line based on
the proposed
ERP Solution and their Methodology,
Project Plan
|
62
|
The bidder will be responsible for providing load balanced active-active solution
|
Load balance testing sign off
|
63
|
The bidder will demonstrate the backup as mentioned in the plan
|
Backup sign off
| UPGRADE & PATCH APPLICATION POLICY |
64
|
The bidder will be responsible for providing a detailed upgrade policy for the upgrade (minor as well as major) of all applications being implemented as a part of this ERP implementation.
|
Application
Upgrade Policy
|
Bidder to suggest suitable time
line based on
the proposed
ERP Solution and their Methodology,
Project Plan
|
|
The bidder will also provide a patch application guideline based on the best practices in this regard
|
Patch application
guidelines
|
Share with your friends: | 
