Jungleworks Proposal

Proposal
For: ASAP507
Dated: May 14, 2018

SoCoMo Inc dba Click Labs 388 Market Street,Suite 1300,San Francisco CA 94111, USA +1 206-274-9145 1

TABLE OF CONTENTS

Section 1: Introduction & Background 3
Section 2: Project Description 5
2.1 Stakeholders 5
2.2 Technical Solution 5
Section 3: Workflow 6
Section 4: ASAP Ordering API 7
Section 5: Scope of Work 8
5.1 White Labeled Jungle Customer 8
5.2 Jungle Merchant Dashboard 10
5.3 Jungle Admin Dashboard (Order Management) 11
Section 6: Cost 16
4.1 Cost 16
4.2 Monthly Recurring Cost 16
Plan 1 16
Plan 2 16
4.3 Payment Terms 17
4.4 Timeline 17
Section 7: Proposal validity 18
Section 8: Jungleworks Credentials 18
8.1 Success Stories 18
8.2 Useful Links 20
Section 9: Agreement 21
Appendix A 22
Appendix B 23

SoCoMo Inc dba Click Labs 388 Market Street, Suite 1300 San Francisco, CA 94111, USA +1 206-274-9145

Section 1: Introduction & Background
About JungleWorks

JungleWorks is a power packed platform to help businesses on the move. We are
market leaders with 6+ years of investment in delivering mobility solutions to
entrepreneurs and enterprises looking to provide an omnichannel experience to their
customers. Our products have been designed to simplify technology for you while you
focus on expanding your business. During the course we have also created significant
IP code blocks, processes, etc that help us put together winning value propositions for
engagements in specific domains. We are an ISO 90012015 certified and ISO 20000 /
SEI CMM level 3 certified company.
To give a bird’s eye view of JungleWorks, we are organized as follows:



Section 2: Project Description

Client is looking to set up a marketplace by aggregating merchants from which
customers can order the products via the platform.
2.1 Stakeholders
The platform w
ill have following stakeholders :
Customers: Customers are the end users who can order products from the platform.
Merchants: Merchants are the store owners who will list their products based on the
availability.
Service owner: Service owner is the platform owner, owning and managing the entire
platform: users, services, content and other key operations.
2.2 Technical Solution
Our solution will include a SaaSbased native mobile application and a website for
the customers, a Jungle marketplace Dashboard for merchants. A Jungle
dashboard for ( order management ) for service owner on our base template to
manage all stakeholders and other key operations. Any other significant changes in the
admin panel on top of our base template would be charged additionally. The features of
the solution are listed below in the scope of work.
There will be API integration with the ASAP507’s backend using the APIs mentioned in
Section 4. For integration we will be using iFrames to open the ordering management
section on the existing applications and websites.

Section 3: Workflow
Customers: Customer will login the ASAP account. There will be an icon/button for
customer to access marketplace. Ability for the customer to search for stores, items.
Customer can browse product categories/items, add product/item to its cart and place a
delivery request, customer can request only one delivery per store at a time. Customer
can also add special notes/instructions while placing a request. Ability for the customer
to view its upcoming and ongoing order deliveries and can track the delivery. Customer
can view its completed orders, items ordered, quantity of items and total cost of
completed order including the delivery cost. Customer will also receive an order invoice
of completed order on its registered email id containing all the above mentioned details
of order.

Merchants/Store Owner: Store owner will add/edit categories and items. Store owner
will be able to add/edit prices and banner image for added items. It can also set “auto
accept” for all orders and can monitor the status ( received from ASAP Api) or any
delivery. Store owner will be able to go to ASAP system to monitor deliveries in real time
and contact support. It can set working/weekend hours, can mark the the item as
unavailable, can enable/disable item and can also accept/reject deliveries.

Service Owner/Admin: Service owner can add stores and items to those stores in
marketplace. It can also grant/revoke access to stores in marketplace, can set location
and working hours for a store.Service Owner can define the commission fee per store. It
can also create a delivery and send to ASAPSystem for each delivery received and
approved in ASAP/Ordering marketplace. Service Owner must send store name,
location, contact details, list/quantity of items and total cost to ASAP system to create
an order for delivery. Search radius determining which stores to be displayed to users
based on the delivery location will be set from service owner.

ASAP System: ASAP system will receive delivery requests coming from marketplace
system with all the details. ASAP system will be able to delivery id for orders and will be
able to see all the order details such as store name, location, contact details, requested
items with quantity and total cost. When a new store is added in marketplace, it will also
be reflected on ASAP system. ASAP system will send an estimated fare to ordering
system before every delivery creation. Status of every delivery will be sent to order
management system using API. ASAP system will able to inform store owner for
delivery acceptance/rejection. ASAP system will be able to distinguish which system is
managed by ASAP system and which stores have a store owner.

Section 4: ASAP Ordering API
● ASAP_Pricing_API: Will be used to share estimated fare (base+km
extra+service fee). Applies only for nonpartner stores that do not have a
flatrate.
● Delivery_Creation_API: Will be used to share pickup and delivery locations.
Share Item, its quantity, special instructions, price per item and total price of
goods.
● Delivery_Status_API: Will be used to shared status waiting for provider,
reached point A, waiting, picked up, reached point B, completed).
● DB_Update API: Will be used for general data update.
● New_Storefront_Created: When a new storefront is created in marketplace.
ASAP needs to open a corporate account for the newly created shop in Jungle
marketplace.
● Grant/Revoke_API: If a Store is revoked in marketplace dashboard, it should
also be revoked in ASAP Admin and viceversa.
● Business_APP_API: Are all incoming orders sent to dispatch? Or do we have to
wait for Store to Accept? Reject order?

Section 5: Scope of Work
Functional Requirements
5.1 White Labeled Jungle Customer
PLATFORM: iOS, ANDROID & WEB

A. Sign up & Login
1. Ability to Sign up & login by entering the registered email.
2. Ability to view and update profile name, number and change password after
login.
3. Ability to enter details in template field during signup as set by the admin.
4. Facebook: Ability to sign up via the Facebook account. A first name, last name,
will be fetched from the Facebook once the customer successfully signs up with
the Facebook.
5. Ability to login via Facebook once the signup is done.

B. Aggregation:
1. Ability to enter the location.
2. Ability to view a list of merchants in the location entered.
3. Ability to select the merchant from the list of merchants of that category.
4. Ability to view the menu/product listings for every merchant.
5. Ability to view the price for each product.
6. Ability to add to the cart.
7. Ability to add multiple items to the cart.
8. Ability to enter the address for the product delivery.

9. Ability to place an instant order or schedule the order for later date and time
(Customer will be displayed a notification message as time out if the time for
placing the order exceeds as per the time slot set by the service owner).
10. Ability to add notes/description if any in the free text field.
11. Ability to get the order invoice in the email once the order is placed.

C. Promo
1. The ability for the customer to apply promo code on (payment summary page).
Customer can apply the promo code while making the payment. Promo codes
will be based on either percentage or flat discount. The promo codes will be
created from the admin section.
2. Ability for the customer to share the referral code which will be unique to each
customer and avail percentage/flat discount upon use of referral code by other
customers.

D. Tracking: Ability to track the real time location and status of agents within the App.

E. Payments:
1. Ability to make payment upon placing the order by one of the added credit card
or debit card through integration with either Stripe or Braintree.
2. Ability to pay by cash at the time of delivery.

F. Ratings & Reviews:
1. Ability for the customers to provide rating and feedback to the merchants.

G. Notifications:
1. Ability to get notifications for:
A. Order Placed
B. Order Dispatched

C. Order Delivered
D. Order Rejected
E. Order Cancelled
F. Order Reminder

H. Others:
1. Orders: Ability to view the total order requests placed with order id, order status,
order date & time and order amount, orders cancelled.
2. Profile: Ability to view and edit the profile information such as name, phone
number, change password and upload profile photo.
3. Notifications: Ability to view all the notifications against each order with
complete order details such as order id, order status, order time, store name,
delivery address and summary of the products ordered with their cost.
4. Inventory: Ability to view the out of stock items (based on the availability set by
the service owner).
5. Chat Support: Ability to chat with the service owner for any support required via
integration with HIPPO.
6. Cancellation: Ability for the customer to cancel the orders. Order cancelled by
the platform will also be notified at the order detail.

5.2 Jungle Merchant Dashboard
PLATFORM: WEB

A. Login
1. Ability to login to the dashboard using the credentials received via email from the
admin.

B. Aggregation

1. Ability to add/edit the catalogue for the items that they provide.
A. Ability to add categories/products for the catalogue.
2. Ability to import catalogue by uploading a CSV file.
3. Ability to set the price and description for each item/product.
4. Ability to upload images for each product (maximum 5 images can be uploaded).
5. Ability to enable/disable the inventory and set the quantity for each product in the
inventory which will be updated automatically based on the number of orders
placed.
6. Ability to enable/disable the customer to view out of stock items.
7. Ability to view incoming order requests with order id, customer id, payment method,
description, name, phone number, order time, order status, ratings etc.
8. Ability to logout from the dashboard.

C. Notifications
1. Ability to receive the notifications:
A. Order request received

D. Others
1. Ability to view the profile information and edit the fields such as name, description,
image, store logo and serving radius etc.
2. Ability to select from the timeslots from the ones set by the admin.
3. Ability to set/edit the additional information like minimum order amount etc.

5.3 Jungle Admin Dashboard (Order Management)
PLATFORM: WEB

A. Sign up & Login
1. Ability to Sign up & login by entering the email/password combination.

2. Ability to view company profile.
3. Ability to view notifications for all latest activities on the dashboard.

B. Catalogue
1. Ability to set the catalogue with categories, product details or add any addons and
set price for each addon, edit/delete addons.
2. Ability to set/edit the category name, description or cost.
3. Ability to enable/disable any category or product.
4. Ability to add/edit/delete any category or product.
5. Ability to upload multiple images of the catalogue.
6. Ability upload/import the CSV file for adding the catalogue.
7. Ability to set the view of the layout as banner view or grid view.
8. Ability to set/edit the quantity available in the inventory for each product which will
be updated automatically based on the number of orders placed.
9. Ability to enable/disable the inventory against each product.

C. Customers
1. Ability to view the list of the customers registered on the platform with customer
name, email and phone number etc.
2. Ability to edit the information based on above parameters except email id.
3. Ability to block/unblock the customers.
4. Ability to bulk upload the customers via CSV file.
5. Inventory: Ability to allow the customers to view the out of stock items based on the
availability set by the admin.

D. Orders

1. Ability to view the list of all the requests received on the platform with order id,
customer id who placed the order, payment method merchant name, description if
any, customer name, phone number, order time, order status and order rating if any.
2. Ability to view incoming order requests.

E. Merchants
1. Ability to add merchants on the platform.
2. Ability to view the list of all merchants added on the platform.
3. Ability to set a catalogue for each merchant.
4. Ability to view/edit the prices and description set by each merchant for each
category and product listed.
5. Ability to enable/disable any category/product from the list.
6. Ability to add/edit the catalogue for the items that any merchant provides.
7. Ability to upload images for the product (maximum 5 images can be uploaded).
8. Ability to enable/disable the inventory against each product.
9. Ability to set/edit the quantity in the inventory for each product which will be updated
automatically based on the number of orders placed.
10. Ability to view list of orders received to any merchant.
11. Ability to enable/disable the merchant.
12. Ability to view/edit merchant information with merchant name, phone number,
address, description and serving radius etc.
13. Ability to import the merchant catalogue via CSV file.
14. Ability to logout from the dashboard.

F. Notifications
1. Ability to enable/disable the the notifications like:
A. Order placed
B. New customer registered

C. Order reminder

G. Promo
1. Ability to create the promo codes/referral codes on the basis of percentage or flat
discount for referral and referee and edit the end date of the promo codes.
2. Ability to set/edit promo details promo id, promo code, promo type, value, maximum
discount, minimum order, start date & end date, description and status.
3. Ability to delete promo/referral code.

H. Manage profile
1. Ability to view and edit account information like name, phone number, business
name, address etc.

I. Others
1. Customers:
A. Ability to view the registered customers on the platform, with details such
as customer id, name, email, phone, address etc.
B. Ability to edit the above parameters.
C. Ability to block and unblock customers.
2. Merchants:
A. Ability to view all registered merchants on the platform, with details such
as merchant id, merchant name, email, phone, address.
B. Ability to add merchants.
C. Ability to edit the above parameters except merchant email id.
D. Ability to enable/disable the merchants.
3. Orders: Ability to view all the orders with order id, customer id, payment method,
merchant name, description, name, phone number address, time when order
placed.

4. Integrations: Ability to enable/disable the integration with delivery
management(Tookan) and HIPPO chat.
5. Ratings & Review:
1. Ability to view the ratings & review given the by the customers
2. Ability to enable/disable ratings & review feature.


6. Currency: Ability to select the currency from the list.
7. Ability to view the billing information of the customer like plan, billing date, amount
due, card details added by the customer etc.
8. Ability to set/edit taxes or delivery charges.
9. Ability to enable/disable the scheduling with delivery options as instant
request/scheduled request or both, set/edit slot interval, date range and hours,
(Customer will be displayed a notification message as time out if the time for placing
the order exceeds as per the time slot set).
10. Ability to add/edit the custom field signup template for customers, enable/disable the
template, add more templates etc.
11. Inventory:
A. Ability to enable the customers to view the out of stock items.
B. Ability to set/edit the quantity available in the inventory which will be
updated automatically based on the number of orders placed.
C. Ability to enable/disable the inventory against each product.
12. Promo & Referrals:
A. Ability to add, edit, delete the promo/referral code.
B. Ability to enable/disable the promo/referral code.
C. Ability to set/edit the validity of the promo/referral code.
13. Payments: Ability to view the total payments received from customers.

Non Functional Requirements
The scope of work with regards to our standard guidelines for non functional
requirements is mentioned below:

A. Application Technology Stack
1. Android: Android Studio 3.x + Java 8
2. iOS: Xcode 9.2 + Swift 4

3. Frontend: Angular 1.2
4. Backend: NodeJS 5.8 + MongoDB 3.0 + MySQL 5.6

B. Security
1. Application : Testing will be performed for following vulnerabilities
A. Login facility susceptible to bruteforce attacks
B. Sensitive information sent in unencrypted email
C. Account creation password never expires
D. Unnecessary/default content on server
E. Unnecessary data sent in API response
F. Inadequate data validation and/or sanitation
G. Insecure OTP validation process
H. API susceptible to automated attack
I. Enumeration of promotion codes
J. In Referral Code Don't use customer specific information
K. Administrators could not change their password
L. API auth key for every request
M. Rooted phone detection
N. Lack of Binary Protections
O. Security Decisions Via Untrusted Inputs
P. Poor Authorization and Authentication
Q. Unintended Data Leakage
R. Finding open ports and exploits on them
S. Cryptographic weakness in TLS/SSL implementation
T. Firewall must be on
U. OS level health check
V. Subnet for multi server systems
W. Software version(s) disclosed via HTTP headers/HTML content
2. Server Security Guidelines

A. Configuration Management
● Security HTTP Headers
● Sensitive Data on the Client Side
B. Authentication
● Brute Force Protection
C. Secure Transmission
● SSL Version, Algorithms, Key length
D. Ddos Protection
E. Additional Checks
● Disabling PhpMyAdmin link over the live environment
● Disable swagger link from Live environment
● Security patch updation script needs to be run manually after taking
AMI of the instance
3. Data :
A. Data at rest Based on requirement, we use volume encryption to secure
the data presented in the VG’s.
B. Data in transit We use SSL certificate implementation to protect client
information in transit.
C. Configuration All sensitive information like connection strings, shared
secrets, passwords etc.,we save in environment variable and bind the
access of individuals for the same.
C. Scalability
1. Application:
A. We configure alerts based scalability on few checks while
implementing/configuring the application, which are as below:
● Average 60% CPU usage and 60% memory usage.
● Auto scaling of instances if load average of CPU utilization spike upto
70% threshold.
● Minimum Count: 2

● Max Count: Based on traffic assumption
2. Database Size :
A. MySQL 40GB
B. MongoDb 150GB

D. Availability
1. Application/Database:
A. We configure the alerts checks of our application.
2. Monitoring:
A. We configure the alerts to monitor the application services.
3. Mobile r eception:
A. Where the user loses mobile connectivity, an Application themed error
page should be displayed to the user.

E. Monitoring and Reporting
1. Critical alerts:
A. We configure alert checks against few services/server level which sends
notification if threshold limit reaches, which are as below:
● Disk Space utilisation if > 50%
● CPU utilisation if > 80%
● Memory utilisation if > 80%
● Log’s deletion based on retention period
● Service down alerts
● Portal down alerts
● Instance health checks down alerts
B. Alerts need to be communicated via phone within 0 minutes of the failure.
C. Alerts need to be communicated via email & Text within 0 minutes of the
failure.
2. Warnings:

A. Operations staff needs alerting if the monitoring system raises warnings
against the production application, database and environment. A warning
is a systemgenerated recommendation based on predefined or outofbox
best practice analyzers and rules.
B. Warnings need to be communicated via email within 30 minutes of the
alert.

F. Backup & Restore policy will be shared separately after post go live, if
needed.
1. Backup: We are backing up our databases every 6 hours, archiving it and
uploading the dump to S3 Bucket. We are saving some latest copies of the
databases on the server itself in order to make our restore process faster in case
of any failure.
2. Restore : If we need to restore our database that is, at max 2 days older, we can
do it by using the dump files stored on EBS of EC2. If it is required to restore
dump older than 2 days, we need to fetch it from S3 bucket and restore operation
can be performed after that.

G. Display
1. Browser compatibility:
A. Chrome version 55 and above*
B. Firefox version 50 and above*
C. Internet Explorer 11
D. Safari version 9 and above*
*Available at the time of agreement
2. Responsive:
A. Web pages is responsive across multiple devices and screen sizes.
3. Tablet & iPad:

A. Apps is not compatible with tablets & iPad.
4. Mobile:
A. iOS: All the phones having 64 bit architecture and running on iOS 8 and
above*
B. Android: All the phones having required hardware, features and running
on OS version Jelly bean(API 16) and above*
*Available at the time of agreement
5. Email:
A. HTML /p
lain text
● All emails should be available in HTML and plain text versions and
served appropriately according to the user’s preference
B. Email rendering
● HTML and plain text emails should render according to the design in
the following email clients:
Apple Mail 9.0 Outlook 2013 Gmail (Android)

Gmail Windows Gmail iPhone 5s iOS 10
iPhone 6 Plus iOS 10

For more information on Native vs Hybrid debate here is a link to a detailed read .


Section 6: Cost
6.1 Cost

COMPONENTS COST
Jungle onetime setup cost
US$ 18,000
Jungle onetime server setup cost

6.2 Monthly Recurring Cost
Plan 1
Components Cost (USD)
Monthly Maintenance Fee
US$ 0.1 per task created/ US$1,000
(Activities Mentioned Under Appendix A) (whichever is higher) per month
Jungle Monthly Subscription US$ 0.1 per task created

Note:
1. The maintenance charges are US$ 1,000 for activities mentioned in Appendix A.
2. The Above Cost includes maintenance for 10,000 tasks.
Plan 2
Components Cost (USD)
Monthly Maintenance Fee
US$ 0.1 per task created/ US$ 500
(Activities Mentioned Under Appendix B) (whichever is higher) per month
Jungle Monthly Subscription US$ 0.1 per task created

Note:
1. The maintenance charges are US$ 500 for activities mentioned in Appendix B.
2. The Above Cost includes maintenance for 5,000 tasks

Please note:
1. The client is being offered for 3 months subscription for Hippo inapp chat for free,
after which he will be charged as per standard costs. For pricing details, please visit
https://jungleworks.co/hippo/pricing/
2. The maintenance charges are for maintenance of whitelabeled applications hosted
on our servers including periodic updates.
3. The maintenance fee deduction will start as soon as we are done with the
deliverables whether Client golive or not.
4. White Labeling includes change in logo and color theme only.

6.3 Payment Terms

The payment schedule for one time cost with milestones are as follows:

MILESTONES AMOUNT
50% Payment to kickoff project US$ 9,000
50% Payment on work completion US$ 9,000

Please Note: Monthly recurring cost is payable separately.
6.4 Timeline
Timelines to deliver the solution is 6 weeks.

Section 7: Proposal validity

The proposal is valid maximum for 7 days from the date of submission.

Section 8: Jungleworks Credentials
8.1 Success Stories


8.2 Useful Links

1. Welcome to JungleWorks : An introduction to JungleWorks Business on the Move.
To learn more head to: https://jungleworks.co/
2. Blog : View articles on latest on demand startups, industry trends and case studies
3. OnDemand Business Modules : Get native mobile apps built to fit your business.
4. Enterprise : Give your Enterprise the OnDemand Edge.
5. Become a Partner : Explore the possibility of a partnership with JungleWorks to
power your business growth!


Section 9: Agreement

An authorized signature on this page indicates its acceptance and authorizes SoCoMo
Inc. dba Click Labs to provide services described herein in accordance with this Scope
of Work and Cost.

AGREED TO AGREED TO
ASAP507 SoCoMo Inc. dba Click Labs

By: By:

Authorized Signature Authorized Signature
Claudio Udler Samar Singla

Date: May 14, 2018 Date: May 14, 2018

Please note: The ownership and intellectual property rights of the Jungle product
shall remain with Jungle at all times. Upon expiry or early termination of this
Agreement, Jungle will remove the application from the relevant application
stores and will discontinue any and all use and access of/to the application.


Appendix A

Maintenance Activities Plan 1:

One time Setup Activities
DB performance tuning
Enabling slow running and high CPU utilization query module
Set maximum number of connections
Setting up the default idle connection timeout configuration
RDS Failover setup with Read Replications
Web server configuration tuning
Load balancing configuration (On Demand)
Auto Scaling implementation (On Demand)
Mongo cloud cluster implementation (On Demand)
Server health check notification
NewRelic implementation (API level)
Nagios alert implementation (Server level including Disk, CPU, RAM, Load utilization
etc.)
AMI creation
Operational Activities
RDS/MongoDB Backup (Managed) Daily
Transferring DB's backup to remote as agreed Weekly
Monitoring Open files and Apache Connections Included
Installation of Server level security patches and software patches monthly basis Included
Clearing RDS cache memory and temporary logs Daily
Log rotation and deletion Daily
Security patch updation Monthly
Periodic rebooting including PM2, Server and RDS Monthly
Regular server performance checks Monthly


Appendix B

Maintenance Activities Plan 2:

One time Setup Activities
DB performance tuning
Enabling slow running and high CPU utilization query module
Set maximum number of connections
Setting up the default idle connection timeout configuration
RDS Failover setup with Read Replications
Web server configuration tuning
Load balancing configuration (On Demand)
Auto Scaling implementation (On Demand)
Mongo cloud cluster implementation (On Demand)
Server health check notification
NewRelic implementation (API level)
Nagios alert implementation (Server level including Disk, CPU, RAM, Load utilization
etc.)
AMI creation
Operational Activities
Log rotation and deletion Daily
Periodic rebooting including PM2, Server and RDS Monthly
Server level alert Included
AMI creation Daily
Installation of Server level security patches and software patches monthly basis Included
Clearing RDS cache memory and temporary logs Daily


Jungleworks Proposal

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Jungleworks Proposal

Uploaded by

Copyright:

Available Formats

Apple Mail 9.0 Outlook 2013 Gmail (Android)

You might also like