Confidential Document

MVP Release Scope

1 Copyright Information
 Confidential Document

Table of Contents

1. ABOUT THE GUIDE....................................................................................................................3

1.1 Document Organization................................................................................................................................... 3

1.2 Document Conventions................................................................................................................................... 3

1.3 Disclaimer....................................................................................................................................................... 4

1.4 Intended Audience.......................................................................................................................................... 4

2. VISION............................................................................................................................................4

3. MVP SCOPE..................................................................................................................................4

3.1 Sales............................................................................................................................................................... 5

3.2 CRM................................................................................................................................................................ 6
3.2.1 Master Screens.......................................................................................................................................................6
3.2.2 Other CRM Screens.................................................................................................................................................6

3.3 Air................................................................................................................................................................... 7

3.4 BI Reports....................................................................................................................................................... 9

3.5 NFR................................................................................................................................................................. 9

3.6 In-App Help Training...................................................................................................................................... 10

4. APPENDIX...................................................................................................................................10

4.1 Notifications & Alerts.................................................................................................................................... 10

4.1.1 Things to Consider for the Optimal Solution........................................................................................................11

2 Copyright Information
 Confidential Document

1. About the Guide

The MVP Release Scope Guide describes the various functionalities of the XXXXXXXXXXXXXXXX

This chapter contains the following sections:

 Document Organization

 Document Conventions

 Disclaimer

 Intended Audience

1.1 Document Organization

The MVP Release Scope Guide is divided into chapters. Each chapter starts with a brief introduction of the
tasks covered. Each chapter is further divided into topics XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.

1.2 Document Conventions

The following table lists the common typographical conventions used in this guide:

Formatting Style Standards

This typeface indicates the page names, fields, buttons, and figure or
Bold
page references.

This list indicates an unordered series of items or options, rather than

Bulleted List
a sequence of processes, events, or steps.

This list indicates a chronological sequence of processes, events, or

Numbered List
steps.

3 Copyright Information
 Confidential Document

1.3 Disclaimer
The system and product names described in this document are not always accompanied by their Vendors or

Owners trademark symbols (™ and ®).

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.

1.4 Intended Audience

This guide is intended for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.

2. Vision
Newage (add Trademark) has a vision and commitment to enable Freight Management and Logistics through
the Digital First Approach and provide a modern Logistics Solution with Omni Channel capability and superior

user experience. It is launched under the flagship name of <<<<<>>>>>>>.

The product will go with the MVP launch and then followed by the quarterly releases.

The following are the development strategies:

 Approach the MVP targeting the small and medium sized customers for both the new and existing

customers.

 Evolve the strategy for large customers based on the learnings from the small and medium sized

implementation.

3. MVP Scope
The MVP Scope section describes the modules or capabilities of MVP.

The following are the modules or capabilities of MVP:

 Sales
 CRM
 Air
 BI Reports
 NFR
 In-App Help Training

4 Copyright Information
 Confidential Document

3.1 Sales
This section describes about the following sales table:

Functionality System Generated User Trigger Mobile

Alert/Notification Generated Names (Refer Enablement
Alert / Appendix
Notification 3.1)

Call Entry Yes Yes Yes

Call Follow-Up No No Yes

Monitor

Enquiry Log Yes Yes Yes

Quotation Yes Yes

Spot Quote Yes Yes

Organizer No No

Maintaining Yes Yes Rate request

Sales Enquiries approval

(Multi-Service

in Single
Enquiry)

Internal Contract
Client Tariff Yes Yes
Approval
(Sell Contract)
External

Contract
Approval

3.2 CRM
The CRM section describes Master Screens and Other CRM Screens.

3.2.1 Master Screens

The following are the common upload for the master screens:

5 Copyright Information
 Confidential Document

 Customer Master
 Agent Master
 Employee Master
 Charge Master
 Year Master
 CFS Master
 Agent Port Master
 Service Master
 Container Master
 Storage Master
 Vehicle Master
 Reason Master
 Document Type Master
 Competitor Master
 Sailing Schedule
 Designation Master
 Department Master
 Branch Master
 Company Master
 User Master

3.2.2 Other CRM Screens

This section describes about the following other CRM screens table:

System User Trigger Names (Refer Mobile

Generated Generated Appendix 3.1) Enablement
Functionality
Alert/ Alert/
Notification Notification

1) Booking Confirmation
Yes Yes
2) Cargo Readiness Follow-
Up
3) Pick-up Follow-Up
4) Pick-Up Confirmation
Shipment 5) Cargo Acceptance at
(Ocean) Warehouse Confirmation
6) Document Follow-Up
7) SI Follow-Up FCL
8) Draft BL

Customer Yes Yes DSR Auto-Trigger

Specific DSR
Automation

Denied Party -

Validation and

6 Copyright Information
 Confidential Document

System User Trigger Names (Refer Mobile

Generated Generated Appendix 3.1) Enablement
Functionality
Alert/ Alert/
Notification Notification

Approval
( External

Integration)

1) Booking Confirmation
Yes Yes
2) Cargo Readiness Follow-
Up
3) Pick up Follow up
4) Pick-Up Confirmation
Shipment (Air) 5) Cargo Acceptance at
Warehouse Confirmation
6) Document Follow-Up
7) Draft HAWB

Yes Yes 1) Internal Contract Approval

Client Tariff Yes
2) External Contract Approval
(Sell Contract)

3.3 Air
This section describes about the following Air table:

Functionality System User Trigger Names (Refer Mobile

Generated Generated Appendix 3.1) Enable
Alert/Noti Alert / ment
fication Notificatio
n

Air Master Yes Yes 1) Loading Confirmation

Generation
2) Onboard Confirmation

3) Vessel or Flight Update

4) HAWB Confirmation

5) Pre Alert Confirmation

7 Copyright Information
 Confidential Document

Functionality System User Trigger Names (Refer Mobile

Generated Generated Appendix 3.1) Enable
Alert/Noti Alert / ment
fication Notificatio
n

6) Arrival Confirmation

7) Delivery Order Follow-Up

8) Delivery Order Confirmation

9) Transit Update

10) Shut Out Update.

Shipment Linking Yes Yes Linked and Unlinked Shipment

or Unlinking Auto Trigger

Job Creation Yes Yes Same as Master

CFS/Warehouse Yes Yes 1) Status Wise Auto Trigger

Receive

CFS/Warehouse Yes Yes Pending Items in CFS Auto

Delivery Trigger

Airline Pre- Yes Yes Carrier/Carrier Agent

Booking Communication Trigger

Credit Limit Yes Yes Credit Approval Mail Yes

Override option
in Air

Agent Branch No No

Mapping

(Auto Master

Generation)

8 Copyright Information
 Confidential Document

3.4 BI Reports
The BI Reports are attempted to be reused from eFS. This section describes the following BI Reports:

#NO: Requested Reports and Description Theme

1 Salesman Wise Shipment Count, Volume, Billing, and GP Sales

2 Sales Enquiry to Booking Sales

3 Weekly Booking Report - to Monitor the Booking and Get Sales

Converted into Job

4 Enquiry Not Quoted - Week, Segment, Enquiry No, Sales Sales

Coordinator, Salesman, Customer, Enquiry Date, and Number
of Enquiries

3.5 NFR
This section describes about the following NFR table:

NFR Description Comments

Customer Status
The Communication to Customer via Alerts/Notifications
Update
etc. should be Configurable
RBAC Handling
Role Based Access Control will be Enabled, and Users will
be Authorized to Perform Activities According to Their
Roles Configured by the Administrator

Error Handling The User Interface should Provide User-Friendly Error

Message in case of System Exceptions
Provision of Multi-Language Support will be Provided
Framework for MVP will be
Localization Started with
English Only

9 Copyright Information
 Confidential Document

3.6 In-App Help Training

The In-App Help focuses on providing a framework containing screen specific information maintained in JSON
format. This is configurable for the screen and it is managed via the user-specific information. That identifies a
new logged user who needs specific training related to usage of a screen. It will not get displayed
subsequently, if the user has already used the help, i.e. a common configuration as a plugin.

The target two screens on the section level and it is extendable to all the screens:

 Call Entry
 Shipment

4. Appendix

4.1 Notifications & Alerts

The communication needs to be carved out as a separate module as configurable. For communication module,
the capacity utilization visibility needs to be provided to the client. This will help to quote the client for the
extended services.

The communication should be based on system trigger or manual trigger.

In the case of system trigger, this will be activity based or scheduler based. The scheduler based will be periodic
(configured). The triggers will be identified through the event/report names.

The medium of communication are listed below:

 Email
 SMS
 WhatsApp (Business version)
 Mobile App (In-house)

The initiation of communication will be triggered through Push Notification (Online).

The Master screen is used to create the event triggers and configure the same. This form will be useful for the
Implementation team to configure during the implementation to list the available options to the customer and
configure. It will reduce the dependency on the Development team for customization during the project
implementation.

4.1.1 Things to Consider for the Optimal Solution

1. An optimal solution is required to fine tune the email delivery process and to save the database space.

2. The solution needs to be arrived for the notifications with feedback. External users (customers/vendors/

agents) with or without access to the applications need to be able to access the related data.

10 Copyright Information
 Confidential Document

3. A separate mobile app needs be built for internal (employees) and external users (customer/agents
/respective dashboard/related actions need be flown based on the user persona).

4. For WhatsApp integration, business version to be used.

5. High priority events need to be identified for offline/emergency alerts for internal users.

11 Copyright Information