Bid Ref No.

GGL Mobile Application Development using SAP MCF-U

227009
Gujarat Gas Limited

SCOPE OF WORK & SPECIFICATIONS

Page 1 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

Table of Contents

Table of Contents ....................................................................................................... 2

Glossary ..................................................................................................................... 4
1 Executive Summary ............................................................................................ 5
1.1 Purpose of this document ............................................................................. 5
1.2 Project Background ....................................................................................... 5
1.3 Project Objective ........................................................................................... 5
2 Project Scope ...................................................................................................... 5
2.1 Project Management ..................................................................................... 6
2.2 Requirement analysis and scope documentation: ......................................... 6
2.3 Design and Development: ............................................................................. 6
2.4 Deployment & Release ................................................................................. 7
2.5 Testing: ......................................................................................................... 7
2.6 Training ......................................................................................................... 7
2.7 Support ......................................................................................................... 7
2.8 Annual Maintenance Contract (AMC)............................................................ 8
2.8.1 AMC Duration ......................................................................................... 8
2.8.2 Service Level Agreement (SLA) ............................................................. 8
3 Project Management Approach ........................................................................... 9
3.1 GGL PMM Process ..................................................................................... 10
3.1.1 Project organization, roles and responsibilities ..................................... 10
3.1.2 Project Management Approach ............................................................ 10
3.2 Change Management .................................................................................. 11
3.3 Implementation Resourcing ........................................................................ 11
3.3.1 Seller Responsibility Mandate .............................................................. 11
3.3.2 Security, Authorizations and Development Standards .......................... 11
3.3.3 Development Process........................................................................... 11
3.3.4 Project Governance .............................................................................. 12
3.3.5 GGL Escalation Matrix .......................................................................... 12
3.3.6 Knowledge Transfer of implementation ................................................ 12
4 Project Administration ....................................................................................... 12
4.1 Working hours ............................................................................................. 12
4.2 Project Venue.............................................................................................. 12
4.3 Stay arrangement of the Seller team ........................................................... 13

Page 2 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

4.4 Travel arrangements of the Seller team ...................................................... 13

5 Contract Terms and Conditions......................................................................... 13
5.1 Contract commencement date .................................................................... 13
5.2 Payments .................................................................................................... 14
5.3 Liquidity Damages....................................................................................... 14
5.3.1 Liquidated Damages for not adhering to Project Delivery ..................... 14
5.3.2 Liquidated Damages for not adhering to AMC SLA .............................. 14
5.4 Deployment of personnel ............................................................................ 15
5.5 Other Terms and Conditions ....................................................................... 15
6 RFP Response .................................................................................................. 15
6.1 Proposed Solution ....................................................................................... 15
6.2 Project Milestones ....................................................................................... 16
6.3 Project Cost Bill of Materials (BOM) ......................................................... 16
6.4 Project scope exclusion list ......................................................................... 16
6.5 Assumptions................................................................................................ 16
7 Annexure ........................................................................................................... 17

Page 3 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

Glossary

Term Meaning
GGL Gujarat Gas Limited

SAP Systems, Applications, Products

MCF-U Multi Channel Foundation for Utilities

GA Geographical Area

AMC Annual Maintenance Contract

PM Project Manager

SLA Service Level Agreement

BOM Bill of Material

Page 4 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

1 Executive Summary
1.1 Purpose of this document

The purpose of this document is to invite bid for designing and developing a mobile application and
a web based application using SAP MCF-U, to help GGL customers and other stakeholders to connect
and directly engage with the Company. The bidding organization is expected to sift through this
document thoroughly and consequently, revert with a Proposal. A conscious effort has been taken
to ensure that the GGL scope and the Seller scope are clearly outlined in this document.

1.2 Project Background

GGL is geographically expanding its network and new GAs are adding in GGL network so there is a
need to cater large number of customers (existing as well as prospective) across all geographic areas
through applications to utilize benefit of rapidly increasing smart phone users. GGL has automated
some of the features related to customers and other stakeholders through the company website but
same is not extended to mobile application and a customer specific web application. It is required to
develop a platform to provide facilities to the stakeholders including Customers, Vendors, Local
authorities, Employees etc. using mobile applications and web based application.

1.3 Project Objective

The objective of the project is to provide simple and user friendly solution to give better service to
all stakeholders and use technology to increase customer satisfaction, revenue and reduce Opex.

2 Project Scope
The scope of this document is limited to the development of a mobile application and a web based
application for GGL stakeholders using SAP MCF-U.

These applications should have very user friendly interface. Mobile application should be easily
downloadable and it should be able to run on mobile phones with multiple platforms i.e. Android,
iOS and Windows.

SAP Multi Channel Foundation for Utilities (MCF-U) is to be used for fetching the SAP data in mobile
application and web based application.

Project scope includes the major components as shown below:

Project Management
Requirement analysis and scope documentation
Design and Development
Testing
Implementation
Go live

Page 5 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

Post go live support

2.1 Project Management

Based on the interactions between Buyer and the Seller, the Seller is expected to share a high-level
Project Plan.

The Seller is expected to assign a Project Manager (PM) to monitor and deliver all the activities of
the project. The PM would be the key point of contact between Buyer and the Seller.

The Seller will have to develop or configure the system at their premises. In case it is an Onsite
Activity, it is important to specify the duration of the activity as Buyer has to provide a work location
from where the individual will be able to carry out the activities.

Buyer Scope: Buyer will arrange the work location and access to relevant resources like users availability while
requirement gathering.

For Onsite activities, the Seller is expected to provide required infrastructure (laptop etc.) and
software to the team members for carrying out their work.

Note: Onsite activity refers to a task being carried out at Buyer premises, whereas Offsite activity
refers to an activity being carried out at the Sellers premises.

The Project Plan has to be a part of the Sellers proposal.

2.2 Requirement analysis and scope documentation:

Seller has to plan multiple workshops with business users and gather the business requirement with
maximum details. Seller will come up with detailed SRS. It will include complete business
requirement including hardware and software requirements if any.

Initial level requirements are detailed out in Annexure.

2.3 Design and Development:

Seller is expected to install SAP MCF Add-on on required systems and perform the configurations.
Seller should showcase 3 application designs each for web based and mobile based out of which GGL
would finalize one design.

Seller will use selected design and showcase design prototype for application features and need to
run through the process with business stakeholders. After receiving approval for design prototype
from buyers end, Seller will start the development which can be onsite or offsite. Seller has to
follow best industries practices while development and need to involve a person who has very good
design capabilities.

Page 6 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

2.4 Deployment & Release

The seller would be expected to carry out the deployment activities. This should be carried out as
per the process documented and as approved in the Deployment Plan.

Buyer Scope: Buyer will be reviewing and signing-off the Deployment Plan.

After a successful deployment, the seller would be required to release the new platform for use of
the end users. The release should be carried out using best industry practices and optimum care
should be taken to avoid users downtimes.

Buyer Scope: Buyer will approve downtime incase required.

2.5 Testing:

Seller has to perform end-to-end testing of the mobile application and web based application. Seller
has to do following activities in testing phase.

a. Test Environment Setup

b. 2 successful rounds of complete life-cycle testing including SIT, UAT.
c. Defect fixing, if any
d. Dry run
e. Testing sign-off

Testing should also include the performance testing with concurrent users using the
applications.

2.6 Training

The seller has to provide support to spread awareness to maximize utilization of these applications
by GGL customers and stakeholders. The seller needs to provide Training Manual which should
include all the steps and FAQs on how an end user can use all features. It should include images of
the user interface wherever applicable.

Buyer Scope: Buyer will review and approve the training manual.

2.7 Support

Offsite Support After the application goes live, seller will be responsible to resolve all the bugs and
minor changes required from business for 30 days.

After this 30-day period, the seller would enter into an Annual Maintenance Contract (AMC) for a
period of 1 year. The seller would be required to provide remote support for GGL mobile based and
web based applications. In case of critical issues, the seller might be required to provide Onsite

Page 7 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

support. The details of the AMC are specified in the Annual Maintenance Contract (AMC) section.
The seller has to specify the AMC costs separately in the proposal.

2.8 Annual Maintenance Contract (AMC)

The Seller will enter into an Annual Maintenance Contract agreement; Thirty (30) business days after
the project go live, as shown in the sequence map below. The exact date for this will be mutually
finalized between Buyer and the Seller, as this depends on the deliverable dates proposed in the
Sellers proposal. The AMC would be driven by the rules laid down in the Service Level Agreement
(SLA), as specified in the section below.

Project Kickoff Project Go Live 30 Days offsite Support AMC Starts

2.8.1 AMC Duration

The initial AMC would be for a period of one (1) year, immediately effective after the completion of
the 30-Days offsite Support period.

The 2nd and 3rd year AMC support would be subject to subsequent approvals by the Buyer through
an approval in the form of Purchase Orders. However, the Seller has to provide the cost of AMC for
both the second and the third year in the Bill of Materials section.

2.8.2 Service Level Agreement (SLA)

1. The AMC support would be classified into two types:

i) Onsite Support
ii) Remote Support
2. The Seller will need to furnish an Email ID where Buyer can mark/report all technical
queries/issues. This email id should be monitored regularly by the Sellers support team.
Additionally, the Seller would be required to provide one (1) support helpline mobile phone
number. This may also be a number of the support team engineer.
3. Vendor shall provide Day-to-day technical support including content updation, trouble shooting,
Patches & bug fixes etc. to GGL thorough telecommunication, email and onsite technical
personal visit.
4. The Seller shall ensure 99.5% up time of applications. However, Buyer will be responsible of
infrastructure availability. In case any downtime is required, the Seller will have to inform the
GGL stake holders and take prior approval.
5. When an issue/query is reported, the Seller would be required to consolidate the Ticket details
and send a confirmation of the reported issue via email. The Ticket should be
numbered/versioned and tracked by the Sellers support team. The Seller will have to send a
Monthly Ticket Report with the details and status of all the issues/queries reported by GGLs
users.

Page 8 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

6. The Onsite Support services shall be on-call basis. The Travel & Accommodation of the support
engineer will be reimbursed by GGL. However, the Seller will need to take a prior budgetary
approval for such cases.
7. It will be mutually decided by the Buyer PM and the Seller PM whether the support required
can be addressed onsite or remotely.
8. The Seller is required to assign a Project Manager who can be approached any time for urgent
matters related to applications. The Sellers Project Manager should be in regular touch with
Buyers Project Manager.
9. Support Timings: The Vendor should be able to provide a support time window from 09.30 AM
to 06.30 PM IST however in special circumstances, the Vendor required providing such services
on holidays also. Support should be available 24*7 for C1 and C2 categories of tickets.
10. Restoration Plan The Vendor is expected to be always ready with a restoration plan, in case
the system goes down. This Restoration plan document should be treated as a standard run-
book for bringing up the system.
11. In case of a hardware failure/OS failure/New environment creation, the GGL team will bring
back the hardware/OS, but the Vendor would be responsible for setting back the system with all
required software.
12. Vendor support would require for end user training including user manual.
13. Request for Remote Access of machine by Vendor shall be subject to GGL IT Security Policies.
Vendor shall arrange for online meeting space such as WebEx, live meeting.
14. The Vendor would be responsible for the overall smooth functioning of the applications at GGL
including minor modifications which are not more than 2 hours of effort each and yearly cap for
the same would be 72 hours.
15. Charges for additional work: Vendor shall provide man day rates for various types of resources
used for any change for application in case if any major additional out of scope work is
identified which requires to be delivered as part of the AMC.

The Seller would be responsible for the overall smooth functioning of GGL mobile based and web
based applications.

3 Project Management Approach

The Seller is expected to carry out the best practices of implementing GGL mobile based and web
based applications. It is expected that the Seller complies with the GGL PMM process for creating
the documentation required for the project implementation.
Before the start of the project, controls should be put in place to assure that process integrity is
maintained.
A clear Project Plan needs to be developed and strictly adhered to. Expectations from Buyer team
members should be clearly communicated and explained well in advance and reasonable time given
to respond to the queries.

Page 9 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

The Seller PM is expected to highlight and escalate in time, any schedule/deliverables concerns in
advance so as to avoid any schedule deviation.

3.1 GGL PMM Process

GGL has a well-defined Program Management Methodology for managing SAP projects. It clearly
defines the deliverables and activities to be completed at each stage of the project and also provides
the document templates to be created at each stage based on project complexities.

3.1.1 Project organization, roles and responsibilities

The most successful projects support a cohesive teaming environment across all disciplines and team
members. The project will depend on the knowledge and skills of the project sponsorship and
management team, the Seller and BUYER team.
# Role Responsibilities
1. Buyer Project Manager. Stake holder availability
Infrastructure availability.
Scope Management
Project Review
Risk Management
2. Seller Project Manager Resource availability
Scope Management
Project Management
Project Review
Risk Management
Awareness, Deployment, Support
3. Seller Consultant Current System Analysis and documentation
New features and requirement documentation
4. Seller Trainer Support for Awareness to GGL customers
5. Seller Developers Design, Development & Customization
Unit Testing, Fixes, Delivery, Support
6. Seller Test Engineers Testing (System, Integration)
7. Buyer Functional Reps UAT
8. Seller Support Engineer Provide support

3.1.2 Project Management Approach

The Seller is expected to provide a Project Manager (PM).

The Seller is also expected to understand all the GGL PMM best practice templates for all
documentation and suggest additions if any. The additions/changes will be reviewed by Buyer and
will be mutually discussed and finalized. This activity should be completed in week 1 of the project to
help speed up the project.
The Seller PM will escalate issues weekly, fortnightly, monthly as required to ensure the project does
not slip from the schedule. He-She will also give enough advance notice on BUYER deliverables and
work with Buyer team to facilitate completion of their deliverables.

Page 10 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

The Seller will conduct team and stakeholder workshops at different stages of the project to
communicate clearly the plan, expectations, and deliverables for the next phase of the project.

3.2 Change Management

In an event of a major change in the scope outlined in this document, or an new requirement where
in a major new module or feature needs to be added to the items in scope, that impacts the effort
and timelines of the project significantly (15%+), a Change Request would be raised by GGL, for
which GGL will approve and authorize the seller to carry out the additional line item.

The Change Request will need to be raised using the standard Change Request Template (CRT). The
work for the change request will proceed after proper approvals made on the CRT and signed by
authorized stake holders.

3.3 Implementation Resourcing

3.3.1 Seller Responsibility Mandate

Buyer expects the Seller to take responsibility for a number of key project deliverables as described
below:

Role Activity Time Required [Tentative] Required

Project Manager Project Management Complete project life cycle Onsite/offsite
including 30 days offsite support
Mobile and Web Mobile and Web based To be planned by Seller Onsite/offsite
based application application Design
Architecture
Development & Development, Testing, To be planned by Seller Onsite/Offsite
Testing Team Deployment.
Trainer Deliver Training To be planned by Seller

3.3.2 Security, Authorizations and Development Standards

The Seller has to document the role definition and security authorizations for both the applications.
The Seller needs to comply with exiting formalities after implementation.

3.3.3 Development Process

The Seller shall bring in its best development practices and align them with Buyers business
objectives. Development shall commence after a concrete study of the system and should be in line
with GGLs standard PMM processes. Additionally, the development should follow the best Software
Development Life Cycle processes followed in the industry.

The Seller is expected to include its proposed development process in the proposal.

Page 11 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

3.3.4 Project Governance

As part of the formal kickoff of the project, BUYER requires an agreed governance model and policy.

3.3.5 GGL Escalation Matrix

In case an issue cannot be resolved by Buyer or Seller, the next higher level in the organizational
hierarchy shall be notified on the basis of the following guidelines.

Level GGL Guideline

One Bindal Dave Same day
Two Tarun Sharma Expedited by Project Manager
Three B. C. Gheewala Expedited by Program Manager

3.3.6 Knowledge Transfer of implementation

To ensure long term success of the project it is imperative to build in-house skills that will enable
reduce dependency on external resources. This calls for significant knowledge transfer from Seller
team to Buyer team during the course of implementation. Seller is expected to play a very active and
keen role in imparting knowledge to Buyer team through various training programs mentioned in
the document and by imparting hands-on experience to end users at Buyer.

4 Project Administration
4.1 Working hours
GGL follows Monday to Saturday, 6 days a week at all its locations. 2nd and 4th Saturdays of the
month are holidays. During the course of implementation which is spread across project initiation to
post go live support it is proposed to keep the working hours for the team, generally from Monday
to Saturday, 10.30 AM to 06.30 PM, except at times of cutover, go-live etc. when project schedules
and downtime necessitates working on weekends, late hours etc. It is also expected that the Seller
team follows the GGL holiday calendar which will be circulated at the time of project initiation.

4.2 Project Venue

GGLs head offices are located in Ahmedabad and Gandhinagar as majority of the employees and
team members are from this place, hence the project site will be Ahmedabad and Gandhinagar
Offices. The Seller is expected to specify the number of team members onsite in advance, through
the proposal itself. This will help Buyer in planning and ensuring that infrastructure related
requirements is facilitated well in time.

Following infrastructure will be provided to the Seller team

Sitting facility (open work station area, not closed rooms)

Page 12 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

Note: The Seller PM will need to specify the number of work-station locations required in
the proposal. This will help GGL in better planning, coordination and thereby ensure a timely
delivery through a team effort.
Computing facility (desktops/laptops as required)
Note: For the laptops, the Seller has to specify in the proposal, the number, desired
configuration and required duration.
Printing facility
Presentation and meeting room facility in case required
Tea, coffee facility etc.

4.3 Stay arrangement of the Seller team

The Seller team is required to make their stay arrangements. They are advised to touch base with
the GGL Admin team to identify the hotels.

This cost should be factored in the fixed price of the project.

Buyer Scope: Buyer PM will assist the Seller PM to coordinate with GGL Admin team, to streamline these
arrangements.

4.4 Travel arrangements of the Seller team

The Seller team is required to arrange their travel arrangements including Airport Transfers and
to/from office to accommodation. Ahmedabad has major links to the cities such as Mumbai,
Ahmedabad, Delhi, and Bangalore through trains.

This cost should be factored in the fixed price of the project.

5 Contract Terms and Conditions

5.1 Contract commencement date
The Contract commencement date will be considered from the date when Seller has mobilized the
team to start the project work; it can start with the kick off meeting of the project team. The Seller
should start the engagement within 15 days of the receipt of the PO.

The Sellers team members will sign a Non Disclosure Agreement (NDA) for ensuring that GGLs
Intellectual Property is safe and secure.

All the deliverables of this project would be the property of GGL.

Page 13 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

The recommended flow will be in the following sequence, after receipt of the proposal:
1) Seller Finalization
2) Release of Purchase Order (PO)
3) Project Kick-Off (Should happen within 15 business days of receipt of the PO)

5.2 Payments
Payments will be as per GGL C&P Terms & Conditions.

5.3 Liquidity Damages

5.3.1 Liquidated Damages for not adhering to Project Delivery

In case if the work is not completed within the time frame as per the approved project plan, Buyer
can deduct liquidity damages (LD) at the rate of 1% per month of the total contract amount, limited
to a maximum of 10% of the total contract value.

LD will be charged in case the delay is due to force majeure. LD will be charged only when the delay
is attributable to the Seller.

In case any deliverables is considered a failure due to significant number of defects. LD will be
charged at 1% per instance, limited to a maximum of 10% of the total contract value.

5.3.2 Liquidated Damages for not adhering to AMC SLA

The SLA between Service Provider and GGL will be enforceable only during the Post Go-Live Phase
and the following penalty shall be applicable:
Response Time & Resolution Time Metrics

Criticality Title Response Time Service Provider Proposed Resolution Time

C1 Critical 1 Hour 4 Hours

C2 Major 2 Hours 8 hours

C3 Medium 4 Hours 16 Hours

Response Time is defined as the time taken to communicate back to the request initiator
the first cut assessment of the problem and expected resolution time.
Resolution Time is defined as the actual time taken to rectify and resolve the problem.

Criticality Definitions

1. Scenarios that lead to complete shutdown of the applications as C1 (Critical) issues.

Page 14 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

2. Scenarios that cause failure of application functionalities which affects many end
users are classified as C2 (Major); Defects that lead to inaccuracies are also
considered as failure of operations.
3. Scenarios that cause failure of application functionalities which affects few end users
are classified as C3. Defects that lead to inaccuracies are also considered as failure of
operations.
In case if the work is not completed within the time frame as per the approved project
plan, Buyer can deduct liquidity damages (LD) at the rate of 1% per month of the total
contract amount, limited to a maximum of 10% of the total contract value.

5.4 Deployment of personnel

The Seller should ensure that the personnel deployed are specialists who have the requisite
knowledge and abilities to perform their task with high standard, safe in all respect.

If Buyer at any point in time becomes dissatisfied for any reason with the performance of any of the
Seller personnel, if Buyer so requires, the Seller would cease to engage such person in carrying out
the services and will provide a suitable substitute at no additional cost to the company.

In case the Seller is not able to provide a competent resource as per Buyer expectations, BUYER will
be free to secure the resources from other Sellers and deduct the expenses from the contract price.

5.5 Other Terms and Conditions

For all deliverables from Buyer, the Seller will give at least 2 weeks time or more after the
issues are clear on both sides.
All the configuration and development done for this project will remain the Intellectual
Property of BUYER. The Seller will not use the same for any other implementation without
the written approval from the Buyer management.
The Seller will work and support the transition to the new Seller, in case of termination of
contract.
In case of unavailability of any resources for more than a week, the Seller will provide
alternate resource having the same experience.

6 RFP Response
Seller is expected to provide the following details in their technical response to the eTender:

6.1 Proposed Solution

The Seller needs to elaborate in detail the solution that they are proposing for achieving the
requirements in this RFP. This should include the high level architecture, the functionalities and

Page 15 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

features of different modules of the applications. The Seller may also include pictorial diagrams of
the proposed solution. The technical specifications should also include the software and hardware
details of the proposed solution.

6.2 Project Milestones

The Seller will list down the proposed project milestones based on the requirements communicated
through this document. The Seller will be required to list down the payment milestone in line with
the key deliverables of the project. They should also list down the criteria to validate the milestone
completion.

6.3 Project Cost Bill of Materials (BOM)

The Seller shall submit the Priced Bid online on nProcure portal. No hard copy shall be submitted.

6.4 Project scope exclusion list

Seller needs to list down in detail the activities, if any will be excluded from the list price contract for
the project as part of the response to the RFP. This list should be very detailed to avoid any
misunderstandings in the future.

This list will be discussed and finalized as part of the SOW technical discussion. All other activities in
exception to the list will be considered as part of the scope of the project.

6.5 Assumptions
The Seller is recommended to specify all the assumptions they have, in order to bring in more clarity
into the overall scope of the engagement.

Page 16 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

7 Annexure

High Level Requirements for mobile based and web based applications are described below:

New User ID/Login Process:

Every GGL Customer should be allowed to create an online account on mobile application and
web based application.
Every GGL Customer to have individual Login via his/her Individual Customer ID (Contract
Account).
Customer should be allowed to use same Login ID in both the applications.
Customer Registration for these applications to be authenticated/secured by OTP via SMS/E-
mail mechanism.
Landing page has to be common for all app users.

Application Features:

Sr. Category/Menu Detailed Description

1 Landing Dashboard Dashboard Menu with various information

- User registration
- Log In Authentication
2 User Registration Process
- Forgot Password
- Change Password

Home page for customer

- Menu
3 My Account - Latest updates
- Dashboard Displaying consumption / bill / payment details
etc.

- View & update

personal information
address information
4 Manage Customer Details
contact information
communication preferences
preferred language etc.

Page 17 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

- View meter reading history

5 Manage Meter Reading - Submit meter reading

Data - View upcoming meter reading dates etc.

- View account summary

- View consumption history
- View bills and bill details
View Bill Outstanding &
6 - Inquire about a certain bill
Consumption
- View current consumption, if available
- View forecasted consumption, if available
- Download consumption data etc.

- Manage bank account details

- Manage credit card details
- View & update payment/refund account details
7 Manage Payments
- Make one-time payment
- View payment history
- Cancel scheduled payment

- New Connection enquiry form

Request -Online
8 Customer new - Document uploading
connection enquiry
- New Connection enquiry Status

9 Complaint/Request
Alerts Landing page and
10
My account home page
In line with SAP ECC Customer Complaints process using Notifications
Alerts on top regarding some new scheme launching or other
information

- Generalized Notification Current Happenings (Tariff Revision etc)

11 Push Notifications - Personalized Notification Payment Reminders
- Group Notification Planned Outage in specific area

12 Emergency Numbers Emergency Contact Numbers

13 Dial before dig Dial before dig Numbers

Page 18 of 19
 Bid Ref No.
GGL Mobile Application Development using SAP MCF-U
227009
Gujarat Gas Limited

- Safety & Energy Conservation Tips

14 Info Guide - Seasonal Tips - Monsoon Tips
- Link to SOP & SOC, public notices, orders - Gujarat Gas Website

Display Google Map with Balloon tip of nearest center with timings
GGL Office Locations with Contact Numbers
Collection Centres
Bill Payment Centres
15 Locate Us
Drop Box Centres
CNG Stations
CNG Kit Suppliers
Cylinder Testing Centres etc.

- PNG Bill Calculator based on units

16 PNG Calculator
- Comparison of Commercial LPG Vs PNG

- CNG Bill Calculator

17 CNG Calculator
- Comparison of CNG Vs other fuels

18 Tell a Friend Forward the link to download the app

19 Feedback Submit App review / feedbacks

Page 19 of 19