Roadmap, Requirements and Architecture Document for Data Analytics Platform

Project Description

We are transforming three thousand full-service gas stations for sensor-based data collection to enable real-time personalization and customer analytics.  We are looking for an expert to put together an architecture, and a detailed requirements document with budget to implement a data platform and analytics that will serve 3,000 gas stations with 50 customers per hour per station. You must have experience preparing detail budgets and requirements for a large project that involves building a data platform and customer analytics. Experience with open source data platforms like CDAP is a plus.

User Experience

Each salesman would have a mobile or web app on an Android Tablet to be informed of useful customer data and provide additional information.The customer would have downloaded a driver’s mobile app and register himself or herself with a payment method and his or her vehicle’s plate number.

1. The customer arrives to the station and is identified when he stops at the pump by reading his car’s plates. In a second step, he is also soft-authenticated by verifying if his mobile device’s MAC address is connected to the station’s Wi-Fi antenna at the moment.

2. The salesperson’s tablet would provide customer insights that would allow for a better experience and opportunities for upselling. It would also show whether the customer has automatic payment activated, provided complete invoicing information, and is eligible for a coupon or any other loyalty offer.

3. Then, the gas recharge process runs as usual, creating an entry with the details of the process, such as product, amount, location, timestamp, user data, etc. This data is obtained by mixing user data and station’s software data in a local server.

4. When the recharging process ends, the payment process may follow one of the following scenarios:

• Auto-Payment: Users who has Gulf’s prepaid e-card do not have to do anything when auto-payment is activated, when plate’s have been read correctly or when the customer's mobile device has been detected at the station.
• On-App Payment: Users with Gulf mobile app can opt to pay with his registered payment methods: (1) Gulf prepaid e-card; (2) Visa Card-On-File (with an extra convenience fee); (3) PayPal (with an extra convenience fee); (4) Other third parties’ e-cards (to be defined).
• Traditional Payment: Users with or without Gulf’s app can also opt for traditional payment with cash, paper coupons, debit card or credit card. In these scenarios, the salesman should inform on his app.

5. The sales person would get a notification when the payment is approved and the final payment data is sent to the clod server and the invoicing process begins by sending required info to facturador.com service.

6. Later, the customer would be required to grade the experience to get his loyalty points and a notification when his invoice’s ready.

Business Requirements

It is crucial to design a disruptive, flexible and scalable platform with high availability that fulfills the following business requirements:

1. Non-sensible data integration: All customer interactions, both purchasing, visiting or interaction with any of our engagement and loyalty proposals, would be cloud-stored, centralized and available for further analysis. External data sources may also be added.

2. Sensible customer data: User private information, such as vehicle’s plate, MAC addresses, hashed passwords or biometrics and other should be safely stored and available only by certain services.

3. Centralized cloud app: It will centralize and process authentications, queries, transactions, fuel volumetric data, automatic invoicing and the payment platform.

4. Local service station app and buffer database: A local server would be running a local app to ensure the service 24/7 regardless of internet’s signal intermittence. This app would interact with the following services:

• Mobile salesman app
• Service Station’s control software
• Point-of-Sale
• Centralized Cloud app
• Centralized Cloud Database
• Identification and authentication platforms

5. Driver’s mobile app: A wallet app with notification capabilities will work as the main customer interface. There, the customer will register and create his prepaid account, link more payment methods, fill his invoicing data and interact with Gulf’s gamification scheme and loyalty program.

6. Salesmen tablet app: This app will show useful customer insights and his availability for auto-payment, invoicing and other; sales people may also add additional customer preferences. This app should manage two different profiles: admin and user.

7. Servicing platform: Customers may have access to a FAQ site with an online chat service integrated to manage questions and complains.

8. Data analytics: All non-sensible data is subjected to be aggregated and analyzed for commercial intelligence purposes. Also, some reports to energy and fiscal authorities will be processed and generated from the whole aggregated data.

9. Loyalty points platform: Users will be rewarded with Gulf’s Power Points for visiting us (check-in), purchases based on the payment method, social network’s interactions and referrals. Those point would be used to acquire coupons (for Gulf or our allies) or branded merchandising on an e-platform.

10. Gamification platform: In a second engagement platform, the customer will earn Experience Points (ExP), and badges to advance through levels.

11. Campaign manager: It’s a web app for Gulf to upload certain geo-based campaigns:

• Earn extra points
• New and last minute coupons
• New branded merchandising
• Any other push, SMS or email notification

We have additional details for each of the eleven point above that we will share with the Experfy expert who is hired for the project.

We would like to begin the project ASAP and complete it within two weeks if possible. Please tell about your background and approach; what makes you qualified to work on a roadmap and requirements document for this project; your availability to work and what kind of support you require from our stakeholders.

If you have put together a requirements document for a different project in the past, even if it a completely unrelated project, it would be helpful for us to see it.  It would help us determine how detailed your plans are and if you have experience with budgeting.