5.1 - Annex 1 - IoT Platform

ANNEX 1: TECHNICAL REQUIREMENTS
1
I. Technical requirements for Connectivity Management Platform (CMP)
I.1 Reference architecture for CMP (Connectivity Management Platform)
Interconnection between CMP and Viettel’s existing network
2
I.2 Detailed technical requirements for Connectivity Management Platform (CMP)
ID Function Description Evaluated criteria
I Connectivity Options
Pass: The platform support connectivity via WiFi, Cellular-2G/3G/4G
The platform must enable the following types of
and LPWA (NB-IoT).
1 Connectivity Options network connectivity includes at least WiFi,
Not pass: The platform does not support one of these types of network
Cellular-2G/3G/4G and LPWA (NB-IoT)
connectivity: WiFi, Cellular-2G/3G/4G and LPWA (NB-IoT)
Pass: The platform support connectivity via LTE-M.
Accepted: Vendor has the roadmap to support LTE-M network
connectivity free of charge within 06 months since the effective date of
the contract and will be tested before the FAC (Final Acceptance
The platform must support the LTE-M network Certificate).
2 Connectivity Options
connectivity Not pass: Do not meet any of these requirements:
- The platform support connectivity via LTE-M.
- Vendor has the roadmap to support LTE-M network connectivity free of
charge within 06 months since the effective date of the contract and will
be tested before the FAC.
Order Provisioning
II
Management
Pass: The platform support order placing, processing and provisioning.
The platform must support order placing,
1 Order Provisioning Not pass: The platform does not support one of functions of order
processing and provisioning
placing, processing and provisioning.
2 Order Provisioning The typical time (within the platform) between Pass: The statistics or performance counters from the Platform show that
placing the order and the asset being connected the typical time (within the platform) between placing the order and the
should be less than 5s asset being connected should be less than 5s for at least 99% of times. In
case the platform does not support to show by counters or statistics, the
test will be carried out by manual test for at least 100 times.
Not pass: The typical time (within the platform) between placing the
order and the asset being connected is more than 5s for more than 1% of
3
times.
Pass: The platform support integration with Viettel’s Order/ Management
systems.
Accepted: The vendor has the roadmap to support integration with
Viettel’s Order/ Management systems free of charge within 06 months
The platform must support integration with the since the effective date of the contract and will be tested before the FAC.
3 Order Provisioning current Viettel’s Order/Management systems Not pass: Does not meet any of these requirements:
(Viettel BSS) - The platform support integration with Viettel’s Order/ Management
systems.
- The vendor has the roadmap to support integration with Viettel’s Order/
Management systems free of charge within 06 months since the effective
date of the contract and will be tested before the FAC.
Pass: The platform support to manage the connected estate via a portal.
The platform must support to manage the
4 Order Management Not pass: The platform does not support to manage the connected estate
connected estate via a portal
via a portal.
Pass: The platform allows access via a web browser without any
The platform must support to access via a web
hardware restriction.
5 Order Management browser (http, https) without any hardware
Not pass: The platform does not support to be accessed via a web
restriction (desktop, laptop, tablet, mobile device)
browser or support but with hardware restriction.
Pass: The platform support to change existing subscriptions, activate SIM
The platform must support to change existing
/deactivate SIM via API or Web portal.
6 Order Management subscriptions, activate SIM /deactive SIM via API
Not pass: The platform does not support to change existing subscriptions,
or Web portal
activate SIM /deactive SIM via API, Web portal.
Subscription
III
Management
1 Subscription The platform must support to manage Pass: The platform support to manage subscriptions, to add connections,
Management subscriptions, to add connections, and to change and to change data plans.
data plans Not pass: The platform does not support one of functions of managing
4
subscriptions, adding connections, and changing data plans.
Pass: The platform support to manage up to 180.000 subscribers on the
The platform must support to manage up to same instance.
2 Scalability
180.000 subscribers on the same instance Not pass: The platform does not support to manage up to 180.000
subscribers on the same instance.
Pass: The platform support OTA subscription provisioning including
OTA eSIM provisioning (eSIM Profile Download, Enable, Change,
Delete).
Accepted: The platform has the roadmap to support OTA subscription
provisioning including OTA eSIM provisioning (eSIM Profile Download,
Enable, Change, and Delete) free of charge within 06 months since the
The platform must support OTA subscription effective date of the contract and will be tested before the FAC.
Provisioning and
3 provisioning including OTA eSIM provisioning Not pass: Does not meet any of these requirements:
Activation
(eSIM Profile Download, Enable, Change, Delete) - The platform support OTA subscription provisioning including OTA
eSIM provisioning (eSIM Profile Download, Enable, Change, and
Delete).
- The platform has the roadmap to support OTA subscription provisioning
including OTA eSIM provisioning (eSIM Profile Download, Enable,
Change, and Delete) free of charge within 06 months since the effective
Pass: The platform support also eSIM, multi IMSI SIM profile.
Provisioning and The platform must support also eSIM, multi IMSI
4 Not pass: The platform does not support also eSIM, multi IMSI SIM
Activation SIM profile
profile.
Pass: The platform support Subscription Activate, Deactivate, Pause and
Provisioning and The platform must support Subscription Activate, Terminate.
5
Activation Deactivate, Pause and Terminate Not pass: The platform does not support Subscription Activate,
Deactivate, Pause and Terminate.
6 Provisioning and The platform must support to use “Automation Pass: The platform support to use “Automation Rule” to change SIM
5
status through predefined conditions.
Rule” to change SIM status through predefined
Activation Not pass: The platform does not support to use “Automation Rule” to
conditions
change SIM status through predefined conditions.
Pass: The platform support SIM order management in bulk with
Provisioning and The platform must support SIM order appropriate price plan.
7
Activation management in bulk with appropriate price plan Not pass: The platform does not support SIM order management in bulk
with appropriate price plan.
Pass: The platform support to change SIM status via WebGUI/ API
Provisioning and The platform must support to change SIM status individually or collectively.
8
Activation via WebGUI/ API individually or collectively Not pass: The platform does not support to change SIM status via
WebGUI/ API individually or collectively.
Pass: The platform support changing Physical SIM card on Device.
Provisioning and The platform must support changing Physical SIM
9 Not pass: The platform does not support changing Physical SIM card on
Activation card on Device
Device.
Pass: The platform support to enable automatic SIM activation only
The platform must enable automatic SIM
Provisioning and when the device is powered on for the first time.
10 activation only when the device is powered on for
Activation Not pass: The platform does not support to enable automatic SIM
the first time
activation only when the device is powered on for the first time.
Pass: The platform support a non-billable state for the SIM while device
Provisioning and The platform must support a non-billable state for is in distribution channel.
11
Activation the SIM while device is in distribution channel Not pass: The platform does not support a non-billable state for the SIM
while device is in distribution channel.
Pass: The platform support to enable post-testing stage activation:
The platform must support to enable post-testing Testing stage should not be the start of the monthly service and should
Provisioning and stage activation: Testing stage should not be the not be considered Activated.
12
Activation start of the monthly service and should not be Not pass: The platform does not support to enable post-testing stage
considered Activated. activation: Testing stage should not be the start of the monthly service
and should not be considered Activated.
6
Pass: The platform support to enable instant state changes to the SIM,
The platform must support to enable instant state including moving from Activated to Deactivated individually or in bulk.
Provisioning and
13 changes to the SIM, including moving from Not pass: The platform does not support to enable instant state changes
Activation
Activated to Deactivated individually or in bulk. to the SIM, including moving from Activated to Deactivated individually
or in bulk.
Pass: The platform support different transition states per Customer
Provisioning and The platform must support different transition account.
14
Activation states per Customer account Not pass: The platform does not support different transition states per
Customer account.
Pass: The platform support to provide measures to detect removal of SIM
The platform must provide measures to detect from one device to another and take preventive measures to prevent fraud
Provisioning and removal of SIM from one device to another and and abuse.
15
Activation take preventive measures to prevent fraud and Not pass: The platform does not support to provide measures to detect
abuse. removal of SIM from one device to another and take preventive measures
to prevent fraud and abuse.
Pass: The platform support different provisioning rules and transition
The platform must support different provisioning
Provisioning and states per roam zone within a single Customer account.
16 rules and transition states per roam zone within a
Activation Not pass: The platform does not support different provisioning rules and
single Customer account
transition states per roam zone within a single Customer account.
The platform must support to change MNO Pass: The platform support to change MNO service provider of eSIM (at
service provider of eSIM at least between Viettel least between Viettel and their subsidiaries).
Provisioning and
17 and their subsidiaries (in Vietnam, Laos, Not pass: The platform does not support to change MNO service
Activation
Cambodia, Myanmar, Timor Leste, Haiti, Peru, provider of eSIM between Viettel and their subsidiaries.
Tanzania, Burundi, Cameroon, Mozambique)
Pass: The platform support to manage SIMs that have been transferred to
The platform must enable the ability to manage
Provisioning and other operators' networks from a single point of access.
18 SIMs that have been transferred to other operators'
Activation Not pass: The platform does not support to manage SIMs that have been
networks from a single point of access.
transferred to other operators' networks from a single point of access.
7
Subscriptions The platform must support Pausing/ Resuming Pass: The platform support Pausing/ Resuming service.
19
Management service Not pass: The platform does not support Pausing/ Resuming service.
Pass: The platform support buying additional service for data, SMS,
Subscriptions The platform must support buying additional voice.
20
Management service for data, SMS, voice Not pass: The platform does not support buying additional service for
data, SMS, voice.
Pass: The platform support Subscriber Payment individually or
Subscriptions The platform must support Subscriber Payment collectively.
21
Management individually or collectively (in bulk) Not pass: The platform does not support Subscriber Payment individually
or collectively.
Pass: The platform support remote eSIM profile transfers from one
The platform must support remote eSIM profile operator to another to support Customer's multi-region deployment
Multi-Operator transfers from one operator to another to support requirements.
22
Management Customer's multi-region deployment Not pass: The platform does not support remote eSIM profile transfers
requirements. from one operator to another to support Customer's multi-region
deployment requirements.
IV Rating Management
Pass: The platform support multiple tariff options includes at least
The platform must support multiple tariff options
prepaid, postpaid, and pooled plans.
1 Tariffs includes at least prepaid, postpaid, and pooled
Not pass: The platform does not support multiple tariff options includes
plans.
at least prepaid, postpaid, and pooled plans.
Pass: The platform support to change price plan.
2 Rate Plan Management The platform must support to change price plan
Not pass: The platform does not support to change price plan.
Pass: The platform support multiple rate plans.
3 Rate Plan Management The platform must support multiple rate plans
Not pass: The platform does not support multiple rate plans.
4 Rate Plan Management The platform must support selecting of rate plans Pass: The platform support selecting of rate plans via web interface.
via web interface Not pass: The platform does not support selecting of rate plans via web
8
interface.
Pass: The platform support post-paid, pooled plans.
5 Rate Plan Management The platform must support post-paid, pooled plans
Not pass: The platform does not support post-paid, pooled plans.
Pass: The platform support pre-paid, pooled plans.
6 Rate Plan Management The platform must support pre-paid, pooled plans
Not pass: The platform does not support pre-paid, pooled plans.
Pass: The platform support per-term plans (at least xMBs or xMonths,
The platform must support per-term plans (at least whichever comes first).
7 Rate Plan Management
xMBs or xMonths, whichever comes first) Not pass: The platform does not support per-term plans (at least xMBs or
xMonths, whichever comes first).
The platform must support volume-based pre-paid Pass: The platform support volume-based pre-paid plans.
plans Not pass: The platform does not support volume-based pre-paid plans.
The platform must support time-based pre-paid Pass: The platform support time-based pre-paid plans.
plans Not pass: The platform does not support time-based pre-paid plans.
Pass: The platform support roam zones.
Accepted: The platform must have roadmap to support roam zones free
of charge within 06 months since the effective date of the contract and
will be tested before the FAC.
10 Rate Plan Management The platform must support roam zones Not pass: Does not meet any of these requirements:
- The platform support roam zones.
- The platform must have roadmap to support roam zones free of charge
within 06 months since the effective date of the contract and will be
tested before the FAC.
11 Rate Plan Management The platform must support discount tiers by total Pass: The platform support discount tiers by total account payment or
account payment or subscribers subscribers.
Accepted: The platform must have roadmap to support discount tiers by
total account payment or subscribers free of charge within 06 months
since the effective date of the contract and will be tested before the FAC.
9
Not pass: Does not meet any of these requirements:
- The platform support discount tiers by total account payment or
subscribers.
- The platform must have roadmap to support discount tiers by total
account payment or subscribers free of charge within 06 months since the
effective date of the contract and will be tested before the FAC.
The platform must support discount tiers by rate Pass: The platform support discount tiers by rate plan.
plan Not pass: The platform does not support discount tiers by rate plan.
Pass: The platform support discount tiers by roam zone.
Accepted: The platform must have roadmap to support discount tiers by
roam zone free of charge within 06 months since the effective date of the
contract and will be tested before the FAC.
The platform must support discount tiers by roam
13 Rate Plan Management Not pass: Does not meet any of these requirements:
zone
- The platform support discount tiers by roam zone.
- The platform must have roadmap to support discount tiers by roam zone
free of charge within 06 months since the effective date of the contract
and will be tested before the FAC.
Pass: The platform support APN-based rating.
Accepted: The platform must have roadmap to support APN-based rating
14 Rate Plan Management The platform must support APN-based rating Not pass: Does not meet any of these requirements:
- The platform support APN-based rating.
- The platform must have roadmap to support APN-based rating free of
The platform must support peak and off-peak Pass: The platform support peak and off-peak rating.
rating Not pass: The platform does not support peak and off-peak rating.
10
Pass: The platform support different overage rates by roam zone.
Accepted: The platform must have roadmap to support different overage
rates by roam zone free of charge within 06 months since the effective
The platform must support different overage rates
16 Rate Plan Management Not pass: Does not meet any of these requirements:
by roam zone
- The platform support different overage rates by roam zone.
- The platform must have roadmap to support different overage rates by
roam zone free of charge within 06 months since the effective date of the
Pass: The platform support different overage rates by peak and off peak.
The platform must support different overage rates
17 Rate Plan Management Not pass: The platform does not support different overage rates by peak
by peak and off peak
and off peak.
Pass: The platform support proration of service fees based on activation.
The platform must support proration of service
18 Rate Plan Management Not pass: The platform does not support proration of service fees based
fees based on activation
on activation.
Pass: The platform support different session rounding per rate plan.
The platform must support different session
19 Rate Plan Management Not pass: The platform does not support different session rounding per
rounding per rate plan
rate plan.
Pass: The platform support different session rounding per roam zone.
The platform must support different session
20 Rate Plan Management Not pass: The platform does not support different session rounding per
rounding per roam zone
roam zone.
Pass: The platform support rating calculations based on commercial
The platform must support rating calculations
terms and not on activation status of SIM.
21 Rate Plan Management based on commercial terms and not on activation
Not pass: The platform does not support rating calculations based on
status of SIM
commercial terms and not on activation status of SIM.
Pass: The platform support IMEI based rating.
22 Rate Plan Management The platform must support IMEI based rating
Not pass: The platform does not support IMEI based rating.
11
Pass: The platform support rating based on URL, group of URL's, IP
The platform must support rating based on URL,
address and IP address range based rating.
23 Rate Plan Management group of URL's, IP address and IP address range
Not pass: The platform does not support rating based on URL, group of
based rating
URL's, IP address and IP address range based rating.
Pass: The platform support time-of-day, day-of-week based rating.
The platform must support time-of-day, day-of-
24 Rate Plan Management Not pass: The platform does not support time-of-day, day-of-week based
week based rating
rating.
Pass: The platform support location (MCC-MNC, RAC, TAC) based
The platform must support location (MCC-MNC, rating.
RAC, TAC) based rating Not pass: The platform does not support location (MCC-MNC, RAC,
TAC) based rating.
Pass: The platform support access technology type (2G, 3G, LTE) based
The platform must support access technology type rating.
(2G, 3G, LTE) based rating Not pass: The platform does not support access technology type (2G, 3G,
LTE) based rating.
Usage/Cost
V
Management
Pass: The platform support both manual and automatic usage monitoring
The platform must support both manual and options.
1 Usage Monitoring
automatic usage monitoring options Not pass: The platform does not support both manual and automatic
usage monitoring options.
Pass: The platform support to display all invoice details online.
The platform must support to display all invoice
2 Usage Management Not pass: The platform does not support to display all invoice details
details online.
online.
Pass: The platform support to generate invoice which include by type of
The platform must support to generate invoice
connectivity service and all applicable charges.
3 Usage Management which include by type of connectivity service and
Not pass: The platform does not support to generate invoice which
all applicable charges
include by type of connectivity service and all applicable charges.
12
Pass: The platform support invoice searching by SIM, Rate Plan, and
The platform must support invoice searching by
Sub-Customer or Customer-division.
4 Usage Management SIM, Rate Plan, and Sub-Customer or Customer-
Not pass: The platform does not support invoice searching by SIM, Rate
division.
Plan, and Sub-Customer or Customer-division.
Pass: The platform support to provide invoice and billing details
The platform must support to provide invoice and available at a summary level and broken out at an individual SIM level.
5 Usage Management billing details available at a summary level and Not pass: The platform does not support to provide invoice and billing
broken out at an individual SIM level. details available at a summary level and broken out at an individual SIM
level.
Pass: The platform support to export invoice data to Excel (.csv) format,
The platform must support to export invoice data
via API, or over a data warehouse feed.
6 Usage Management to Excel (.csv) format, via API, or over a data
Not pass: The platform does not support to export invoice data to Excel
warehouse feed.
(.csv) format, via API, or over a data warehouse feed.
Pass: The platform support to displays all rate plans available.
The platform must support to displays all rate
7 Usage Management Not pass: The platform does not support to displays all rate plans
plans available
available.
Pass: The platform support to enables rate plan changes by SIM, Sub-
The platform must enable rate plan changes by
Customer or block of SIMs via the web, bulk upload or API.
8 Usage Management SIM, Sub-Customer or block of SIMs via the web,
Not pass: The platform does not support to enables rate plan changes by
bulk upload or API
SIM, Sub-Customer or block of SIMs via the web, bulk upload or API.
Pass: The platform support automatic disablement of SIM usage when
The platform must support automatic disablement
SIM reaches its pre-configured overage limit for the billing cycle.
of SIM usage when SIM reaches its pre-
Platform must support override of this disablement.
9 Usage Management configured overage limit for the billing cycle.
Not pass: The platform does not support automatic disablement of SIM
Platform must support override of this
usage when SIM reaches its pre-configured overage limit for the billing
disablement
cycle. Platform does not support override of this disablement.
The platform must support automatically notify Pass: The platform support automatically notify selected users when a
10 Usage Management
selected users when a SIM or block of SIMs is SIM or block of SIMs is about to exceed its expected usage in a 24hour or
13
30-day period.
about to exceed its expected usage in a 24hour or Not pass: The platform does not support automatically notify selected
30-day period users when a SIM or block of SIMs is about to exceed its expected usage
in a 24hour or 30-day period.
Pass: The platform support to display total data, SMS and voice
The platform must support to display total data,
consumed by the a SIM at any point within a billing cycle.
11 Usage Management SMS and voice consumed by a SIM at any point
Not pass: The platform does not support to display total data, SMS and
within a billing cycle (monthly).
voice consumed by the a SIM at any point within a billing cycle.
Pass: The platform support to enable automatic transition to another rate
The platform must support to enable automatic
plan at the end of a pre-paid subscription plan.
12 Usage Management transition to another rate plan at the end of a pre-
Not pass: The platform does not support to enable automatic transition to
paid subscription plan
another rate plan at the end of a pre-paid subscription plan.
Pass: The platform support automatic change of rate plan assignment
The platform must supports automatic change of
based on network registration and roam zone usage.
13 Usage Management rate plan assignment based on network
Not pass: The platform does not support automatic change of rate plan
registration and roam zone usage
assignment based on network registration and roam zone usage.
Pass: The platform support automatically notify selected users when a
The platform must support automatically notify pool of SIMs reaches a certain % of its data or SMS allotment. Threshold
selected users when a pool of SIMs reaches a to initiate a notification must be configurable.
14 Usage Management
certain % of its data or SMS allotment. Threshold Not pass: The platform does not support automatically notify selected
to initiate a notification must be configurable. users when a pool of SIMs reaches a certain % of its data or SMS
allotment. Threshold to initiate a notification must be configurable.
Pass: The platform support billing and usage management based on type
The platform must support billing and usage
of service as defined by URL(s), IP Address, device type (IMEI), access
management based on type of service as defined
type (2G, 3G, 4G), time of day/day of week and location.
15 Usage Management by URL(s), IP Address, device type (IMEI),
Not pass: The platform does not support billing and usage management
access type (2G, 3G, 4G), time of day/day of
based on type of service as defined by URL(s), IP Address, device type
week and location
(IMEI), access type (2G, 3G, 4G), time of day/day of week and location.
14
Pass: The platform support to provide Dashboard to compare stream
level usage over two time periods (weekly or monthly).
Accepted: The platform must have roadmap to support to provide
Dashboard to compare stream level usage over monthly period free of
The platform must provide Dashboard to compare be tested before the FAC.
16 Usage Management stream level usage over two time periods (weekly Not pass: Does not meet any of these requirements:
or monthly) - The platform support to provide Dashboard to compare stream level
usage over two time periods (weekly or monthly).
- The platform must have roadmap to support to provide Dashboard to
compare stream level usage over monthly period free of charge within 06
months since the effective date of the contract and will be tested before
the FAC.
Pass: The platform support to display airtime billing, total amount of
The platform must support to display airtime
charge at the time of requesting report.
17 Usage Management billing, total amount of charge at the time of
Not pass: The platform does not support to display airtime billing, total
requesting report
amount of charge at the time of requesting report.
Pass: The platform support to display used amount/ the rest/ total paid
The platform must support to display used amount of data.
18 Usage Management
amount/ the rest/ total paid amount of data Not pass: The platform does not support to display used amount/ the rest/
total paid amount of data.
Pass: The platform support to display used amount/ the rest/ total paid
The platform must support to display used amount of SMS.
19 Usage Management
amount/ the rest/ total paid amount of SMS Not pass: The platform does not support to display used amount/ the rest/
total paid amount of SMS.
20 Usage Management The platform must support to display used Pass: The platform support to display used amount/ the rest/ total paid
amount/ the rest/ total paid amount of voice amount of voice.
Not pass: The platform does not support to display used amount/ the rest/
15
total paid amount of voice.
For sharing data plans among a number of Pass: The platform support to show the Total used amount/ the rest/ the
subscription, the platform must support to show: paid amount and the Effective time of different block of data.
21 Usage Management
- Total used amount/ the rest/ the paid amount Not pass: The platform does not support to show the Total used amount/
- Effective time of different block of data the rest/ the paid amount and the Effective time of different block of data.
Pass: The platform support to manage billing, invoicing and cost
The platform must support to manage billing, management across multiple operators' networks in a multi-operator
invoicing and cost management across multiple network/region deployment scenario.
22 Usage Management
operators' networks in a multi-operator Not pass: The platform does not support to manage billing, invoicing and
network/region deployment scenario cost management across multiple operators' networks in a multi-operator
network/region deployment scenario.
VI Billing Management
Pass: The platform support collect billing data via CDR or other file
The platform must support to collect billing data formats.
1 Billing options /flexibility
via CDR or other file formats Not pass: The platform does not support collect billing data via CDR or
other file formats.
The platform must support to manage rating and Pass: The platform support to manage rating and charging.
2 Billing options /flexibility
charging Not pass: The platform does not support to manage rating and charging.
Pass: The platform support to present invoice and bill to the customer.
The platform support to present invoice and bill to
3 Billing options /flexibility Not pass: The platform does not support to present invoice and bill to the
the customer
customer.
The platform must support to integrate with Pass: The platform support to integrate with Viettel billing system or
Viettel billing system (via secure FTP for the provide independent airtime billing system within CMP.
4 Billing integration exchange of CDR, invoices and reports) or Not pass: The platform does not support to integrate with Viettel billing
provide independent airtime billing system within system or provide independent airtime billing system within CMP.
CMP
5 Billing management The platform must support to present detailed Pass: The platform support to present detailed invoices for all subscribed
invoices for all subscribed services, by type of
16
services, by type of service and device.
service and device Not pass: The platform does not support to present detailed invoices for
all subscribed services, by type of service and device.
Pass: The platform support to display all the invoice information in the
The platform must support to display all the web interface.
6 Billing management
invoice information in the web interface Not pass: The platform does not support to display all the invoice
information in the web interface.
Pass: The platform support split-billing based on multiple rating for
multiple service types.
Accepted: The platform must have roadmap to support split-billing based
on multiple rating for multiple service types free of charge within 06
The platform must support split-billing based on the FAC.
7 Billing management
multiple rating for multiple service types Not pass: Does not meet any of these requirements:
- The platform support split-billing based on multiple rating for multiple
service types.
- The platform must have roadmap to support split-billing based on
multiple rating for multiple service types free of charge within 06 months
Pass: The platform support APN based split billing.
Accepted: The platform must have roadmap to support APN based split
billing free of charge within 06 months since the effective date of the
The platform must support APN based split
8 Billing management Not pass: Does not meet any of these requirements:
billing
- The platform support APN based split billing.
- The platform must have roadmap to support APN based split billing free
of charge within 06 months since the effective date of the contract and
17
Pass: The platform support split-billing on Classified Data Streams.
Accepted: The platform must have roadmap to support split-billing on
Classified Data Streams free of charge within 06 months since the
The platform must support split-billing on
9 Billing management Not pass: Does not meet any of these requirements:
Classified Data Streams
- The platform support split-billing on Classified Data Streams.
- The platform must have roadmap to support split-billing on Classified
Data Streams free of charge within 06 months since the effective date of
the contract and will be tested before the FAC.
Troubleshooting and
Fault management
VII
procedures, Help Desk
and SLA criteria
Pass: The platform support reporting procedure for loss of one or more
Troubleshooting /Fault The platform must have the reporting procedure connections.
1
Finding for loss of one or more connections Not pass: The platform does not support reporting procedure for loss of
one or more connections.
Pass: The platform support the rectification of faults and notification
The platform must support the rectification of
Troubleshooting/Fault processes relating to loss of connection or loss of services.
2 faults and notification processes relating to loss of
Finding Not pass: The platform does not support the rectification of faults and
connection or loss of services
notification processes relating to loss of connection or loss of services.
Pass: The platform support to figure out the last time of checked
Troubleshooting/Fault The platform must support to figure out the last connection.
3
Finding time of checked connection Not pass: The platform does not support to figure out the last time of
checked connection.
4 Troubleshooting/Fault The platform must support to figure out the last Pass: The platform support to figure out the last location and display on
Finding location and display on the map the map.
Not pass: The platform does not support to figure out the last location
18
and display on the map.
Pass: The platform support to make call or send SMS to test the
Troubleshooting/Fault The platform must support to make call or send connection.
5
Finding SMS to test the connection Not pass: The platform does not support to make call or send SMS to test
the connection.
Pass: The platform support mechanism to measure and report the key
SLA/QoS metrics.
Accepted: The platform must have roadmap to support mechanism to
measure and report the key SLA/QoS metrics free of charge within 06
Service Level The platform must provide the mechanism to the FAC.
6
Agreements (SLAs) measure and report the key SLA/QoS metrics Not pass: Does not meet any of these requirements:
- The platform support mechanism to measure and report the key
SLA/QoS metrics.
- The platform must have roadmap to support mechanism to measure and
report the key SLA/QoS metrics free of charge within 06 months since
the effective date of the contract and will be tested before the FAC.
Pass: The platform support integration of Helpdesk capabilities for the
customer.
Accepted: The platform must have roadmap to support integration of
Helpdesk capabilities for the customer free of charge within 06 months
The platform must provide or support integration
7 Help Desk Not pass: Does not meet any of these requirements:
of Helpdesk capabilities for the customer
- The platform support integration of Helpdesk capabilities for the
customer.
- The platform must have roadmap to support integration of Helpdesk
capabilities for the customer free of charge within 06 months since the
19
Pass: The platform support integration of Helpdesk capabilities for the
The platform must support the integration with
customer.
8 Help Desk Viettel Customer Care System with the hotline for
Not pass: The platform does not support integration of Helpdesk
helpdesk support
capabilities for the customer.
Pass: The platform support the integration with Viettel Trouble Ticket
The platform must support the integration with System for technical issues.
9 Network Monitoring
Viettel Trouble Ticket System for technical issues Not pass: The platform does not support the integration with Viettel
Trouble Ticket System for technical issues.
Pass: The platform support monitoring and reporting on abusive devices,
The platform must support monitoring and defined by specified number of authorization attempts within a given
reporting on abusive devices, defined by specified period.
10 Network Monitoring
number of authorization attempts within a given Not pass: The platform does not support monitoring and reporting on
period abusive devices, defined by specified number of authorization attempts
within a given period.
Pass: The platform support the ability to provide a pass through link to
Operators Support platform.
Accepted: The platform must have roadmap to support the ability to
provide a pass through link to Operators Support platform free of charge
The platform must support the ability to provide a
11 Network Monitoring Not pass: Does not meet any of these requirements:
pass through link to Operators Support platform
- The platform support the ability to provide a pass through link to
Operators Support platform.
- The platform must have roadmap to support the ability to provide a pass
through link to Operators Support platform free of charge within 06
the FAC.
VIII Diagnostic
20
Pass: The platform support network activity diagnostics to resolve
The platform must provide network activity technical issues regarding communications (at least for NB-IoT devices).
1 Diagnostic diagnostics to resolve technical issues regarding Not pass: The platform does not support network activity diagnostics to
communications (at least for NB-IoT devices) resolve technical issues regarding communications (at least for NB-IoT
devices).
Pass: The platform support to display real-time session status, including
The platform must support to display real-time IP address, operator, session start time (at least for NB-IoT devices).
2 Diagnostic session status, including IP address, operator, Not pass: The platform does not support to display real-time session
session start time (at least for NB-IoT devices) status, including IP address, operator, session start time (at least for NB-
IoT devices).
Pass: The platform support to evaluate the SIM’s ability to attach to the
The platform must support to evaluate the SIM’s wireless network by checking its current status on the HLR as well as the
ability to attach to the wireless network by HLR logs (at least for NB-IoT devices).
3 Diagnostic
checking its current status on the HLR as well as Not pass: The platform does not support to evaluate the SIM’s ability to
the HLR logs (at least for NB-IoT devices) attach to the wireless network by checking its current status on the HLR
as well as the HLR logs (at least for NB-IoT devices).
Pass: The platform support to send SMS to specified device to determine
The platform must support to send SMS to
whether or not it is reachable over the operator network.
4 Diagnostic specified device to determine whether or not it is
Not pass: The platform does not support to send SMS to specified device
reachable over the operator network
to determine whether or not it is reachable over the operator network.
5 Diagnostic The platform must support to ping specified Pass: The platform support to ping specified device to determine whether
device to determine whether or not it is reachable or not it is reachable over the operator network.
over the operator network Accepted: The platform does have the ability to tell if the subscriber is
online or offline or the platform must have roadmap to support the ability
to ping specified device to determine whether or not it is reachable over
the operator network free of charge within 06 months since the effective
Not pass: The platform does not support to ping specified device to
determine whether or not it is reachable over the operator network and
21
does have the ability to tell if the subscriber is online or offline.
IX Alarm management
The platform must support alarm setting for Pass: The platform support alarm setting for thresholds (over used, lost
threshold: connection, wrong device).
- Dramatically used daily, weekly, monthly over Not pass: The platform does not support alarm setting for thresholds
limitation (over used, lost connection, wrong device).
1 Alarm management - Rarely used daily, weekly, monthly under
limitation
- Lost connection.
- Wrong mapping between IMSI & IMEI in pool
of device
The platform must support to configure the Pass: The platform support to configure the moment of rising alert when
moment of rising alert: event occurs and alarm occurs.
2 Alarm management - Immediately when event occurs Not pass: The platform does not support to configure the moment of
- After an amount of time after occurring rising alert when event occurs and alarm occurs.
- Duration of effectiveness of alarm
The platform must support method of generating Pass: The platform support method of generating alarm via SMS, Email
alarm via: or call.
- SMS Not pass: The platform does not support method of generating alarm via
3 Alarm management
- Email SMS, Email or call.
- Direct call
All SMS/ Call/ Email are sent from the system
The platform must support the general Pass: The platform support the general configuration of Enable/Disable
configuration: alarm or Modifying the content of the message.
4 Alarm management
- Enable/ Disable alarm Not pass: The platform does not support the general configuration of
- Modify the content of the message Enable/Disable alarm or Modifying the content of the message.
X Location based services
1 Location based services The platform must support to locate the position Pass: The platform support to locate the position of devices.
22
Accepted: The platform must have roadmap to support to locate the
position of devices free of charge within 06 months since the effective
of devices.
- The platform support to locate the position of devices.
- : The platform must have roadmap to support to locate the position of
devices free of charge within 06 months since the effective date of the
Pass: The platform support using different colors for displaying different
The platform must support using different colors status.
2 Location based services
for displaying different status Not pass: The platform does not support using different colors for
displaying different status.
Pass: The platform support the quick search for subscription &
The platform must support the quick search for connectivity on the map.
3 Location based services
subscription & connectivity on the map Not pass: The platform does not support the quick search for subscription
& connectivity on the map.
XI Security
Pass: The platform support capabilities to ensure security of connection
by users role-based access control and IP access control.
Accepted: The platform must have roadmap to support IP access control
The platform must provide capabilities to ensure based on IP address or range free of charge within 06 months since the
security of connection by providing capabilities to effective date of the contract and will be tested before the FAC.
1 Security of connection different users based on profiles and IP access Not pass: Does not meet any of these requirements:
management to limit access only from predefined - The platform support capabilities to ensure security of connection by
IP address or range. user’s role-based access control and IP access control.
- The platform must have roadmap to support IP access control based on
IP address or range free of charge within 06 months since the effective
23
Pass: The platform support capabilities to ensure the security of
The platform must provide capabilities to ensure
Security of data transmission including HTTPS or SSL.
2 the security of transmission including HTTPS or
transmission Not pass: The platform does not support capabilities to ensure the
SSL
security of transmission including HTTPS or SSL.
Pass: The platform support to provide connection via public/ private
The platform must support to provide connection
APN and dynamic/ static IP address.
3 Security via public/ private APN and dynamic/ static IP
Not pass: The platform does not support to provide connection via
address
public/ private APN and dynamic/ static IP address.
Pass: The platform support IP-address filtering features via APN.
The platform must support IP-address filtering
4 Security Not pass: The platform does not support IP-address filtering features via
features via APN
APN.
Pass: The platform support password protected authentication to allow
The platform must support password protected access to the network.
5 Authentication
authentication to allow access to the network Not pass: The platform does not support password protected
authentication to allow access to the network.
Pass: The platform must not display passwords, either via email or an
The platform must not display passwords, either
web-based password reminder function.
6 Password control via email or a web-based password reminder
Not pass: The platform display passwords, either via email or an web-
function.
based password reminder function.
7 Fraud management The platform must prohibit the use of a SIM Pass: The platform support to send notification when fraudulent activity
outside of its unintended device. Platform must is outside of its unintended device.
send notification when fraudulent activity is Accepted: The platform must have roadmap to support to send
attempted notification when fraudulent activity is outside of its unintended device
- The platform support to send notification when fraudulent activity is
outside of its unintended device.
24
- The platform must have roadmap to support to send notification when
fraudulent activity is outside of its unintended device free of charge
Pass: The platform support for IMEI whitelisting.
8 Filtering The platform must support for IMEI whitelisting
Not pass: The platform does not support for IMEI whitelisting.
Pass: The platform support for SMS whitelisting.
9 Filtering The platform must support for SMS whitelisting
Not pass: The platform does not support for SMS whitelisting.
Pass: The platform support for Voice whitelisting.
10 Filtering The platform must support for Voice whitelisting
Not pass: The platform does not support for Voice whitelisting.
Pass: The platform support to track actions performed by users in the
The platform must support to track actions system, including time stamp for actions like changing a rate plan or what
performed by users in the system, including time events triggered automation rules.
11 Track events
stamp for actions like changing a rate plan or what Not pass: The platform does not support to track actions performed by
events triggered automation rules users in the system, including time stamp for actions like changing a rate
plan or what events triggered automation rules.
IP Addressing
Mechanisms and Access
XII Point Name - APN
(private and public)
provisioning
Pass: The platform support both static and dynamic IP addressing.
IP Addressing The platform must support both static and
1 Not pass: The platform does not support both static and dynamic IP
Mechanisms dynamic IP addressing
addressing.
Access Point Name - Pass: The platform support both public and private APN provisioning.
The platform must support both public and private
2 APN (private and public) Not pass: The platform does not support both public and private APN
APN provisioning
provisioning provisioning.
25
Application Program
XIII interfaces (APIs)/
Developer Tools
Pass: The platform support to provide API libraries for all major
The platform must provide API libraries for all functions including Order provisioning, Subscription Management,
Application Program major functions including Order provisioning, Rating Management, Usage Management
1
Interfaces (APIs) Subscription Management, Rating Management, Not pass: The platform does not support to provide API libraries for all
Usage Management major functions including Order provisioning, Subscription Management,
Rating Management, Usage Management.
Pass: The platform support to provide API for integrating with other
enterprise system including CRM, Application Enablement Platform for
below actions:
The platform must provide API for integrating - Get connection status of SIM, operation status of subscription
with other enterprise system including Customer - Get history of usage
Relation Management (CRM), Application - Get history of billing
Enablement Platform (AEP) for below actions - Get location-based info
Application Program - Get connection status of SIM, operation status of - Get alert info
2
Interfaces (APIs) subscription Not pass: The platform does not support to provide API for integrating
- Get history of usage with other enterprise system including CRM, Application Enablement
- Get history of billing Platform for below actions:
- Get location-based info - Get connection status of SIM, operation status of subscription
- Get alert info - Get history of usage
- Get history of billing
- Get location-based info
- Get alert info
Pass: The platform support APIs to support the provisioning of devices
Application Program The platform must provide APIs to support the and services.
3
Interfaces (APIs) provisioning of devices and services. Not pass: The platform does not support APIs for the provisioning of
devices and services.
26
XIV Administration
Pass: The platform support administrative capabilities including Service
Desk and Data Centre Management.
Accepted: The platform must have roadmap to support administrative
capabilities including Service Desk and Data Centre Management free of
The platform must support administrative be tested before the FAC.
1 Administration capabilities including Service Desk and Data Not pass: Does not meet any of these requirements:
Centre Management. - The platform support administrative capabilities including Service Desk
and Data Centre Management.
- The platform must have roadmap to support administrative capabilities
including Service Desk and Data Centre Management free of charge
The platform must support to Add/ Modify/ Pass: The platform support to Add/ Modify/ Delete user.
2 Administration
Delete user Not pass: The platform does not support to Add/ Modify/ Delete user.
Pass: The platform support to Add/ Modify/ Delete the hierarchy of
The platform must support to Add/ Modify/
organization with at least 3 layer of users.
3 Administration Delete the hierarchy of organization with at least 3
Not pass: The platform does not support to Add/ Modify/ Delete the
layer of users
hierarchy of organization with at least 3 layer of users.
The platform must support to grant permission to Pass: The platform support to grant permission.
4 Administration
access the Platform Not pass: The platform does not support to grant permission.
Pass: The platform support customer admin to manage and authorize
The platform must support customer admin to
their accounts in the organization by themselves.
5 Administration manage and authorize their accounts in the
Not pass: The platform does not support customer admin to manage and
organization by themselves
authorize their accounts in the organization by themselves.
The platform must support role-based Pass: The platform support role-based administration.
6 Role-based Access
administration Not pass: The platform does not support role-based administration.
27
Pass: The platform support specialized role, allowing access only for
customer support personnel, with no financial information.
Accepted: The platform must have roadmap to support specialized role,
allowing access only for customer support personnel, with no financial
information free of charge within 06 months since the effective date of
The platform must support specialized role, the contract and will be tested before the FAC.
7 Role-based Access allowing access only for customer support Not pass: Does not meet any of these requirements:
personnel, with no financial information - The platform support specialized role, allowing access only for
customer support personnel, with no financial information.
- The platform must have roadmap to support specialized role, allowing
access only for customer support personnel, with no financial information
Pass: The platform support specialized role, allowing access only for
financial personnel.
Accepted: The platform must have roadmap to support specialized role,
allowing access only for financial personnel free of charge within 06
The platform must support specialized role, the FAC.
8 Role-based Access
allowing access only for financial personnel Not pass: Does not meet any of these requirements:
- The platform support specialized role, allowing access only for financial
personnel.
- The platform must have roadmap to support specialized role, allowing
access only for financial personnel free of charge within 06 months since
the effective date of the contract and will be tested before the FAC.
Pass: The platform support sub-management roles, limiting information
Platform must support sub-management roles,
and activity to subset of SIMs allocated.
9 Role-based Access limiting information and activity to subset of
Not pass: The platform does not support sub-management roles, limiting
SIMs allocated
information and activity to subset of SIMs allocated.
28
Pass: The platform support features to allow a resale model whereby
Platform must support features to allow a resale Customer can support multiple Sub-Customers in a management and
model whereby Customer can support multiple billing capacity.
10 Role-based Access
Sub-Customers in a management and billing Not pass: The platform does not support features to allow a resale model
capacity. whereby Customer can support multiple Sub-Customers in a management
and billing capacity.
Dashboard, Reporting
XV and Inventory
Management
The platform must provide dashboard for Pass: The platform support to provide dashboard for controlling
controlling connectivity status, including ratio connectivity status, including ratio chart for connection type (SIM status,
chart for connection type: Subscription Control status).
1 Dashboard
- SIM control status: connected/ disconnected Not pass: The platform does not support to provide dashboard for
- Subscription control status: Active/ Deactivate/ controlling connectivity status, including ratio chart for connection type
Pause/ Terminate (SIM status, Subscription Control status).
Pass: The platform support to provide dashboard for total daily amount
The platform must provide dashboard for total usage for: data, SMS, voice.
2 Dashboard
daily amount usage for: data, SMS, voice Not pass: The platform does not support to provide dashboard for total
daily amount usage for: data, SMS, voice.
Pass: The platform support to provide dashboard for total monthly,
The platform must provide dashboard for total
cumulative usage/ total paid amount for: data, SMS voice.
3 Dashboard monthly, cumulative usage/ total paid amount for:
Not pass: The platform does not support to provide dashboard for total
data, SMS voice
monthly, cumulative usage/ total paid amount for: data, SMS voice.
Pass: The platform support provide the history of usage, status for
The platform must provide the history of usage, subscription.
4 Dashboard
status for subscription Not pass: The platform does not support to provide the history of usage,
status for subscription.
5 Dashboard The platform must support for searching a Pass: The platform support for searching a subscription for all
29
information.
subscription for all information Not pass: The platform does not support for searching a subscription for
all information.
Pass: The platform support to provide the table of IMSI SIM & IMEI
The platform must support to provide the table of Device mapping.
6 Dashboard
IMSI SIM & IMEI Device mapping Not pass: The platform does not support to provide the table of IMSI
SIM & IMEI Device mapping.
Pass: The platform support the mapping of subscription & device
The platform must support the mapping of identification. Customer can manage the mapping between subscription &
subscription & device identification. Customer device by IMEI themselves.
7 Dashboard
can manage the mapping between subscription & Not pass: The platform does not support the mapping of subscription &
device by IMEI themselves device identification. Customer can manage the mapping between
subscription & device by IMEI themselves.
Pass: The platform support to provide Dashboard & Chart of alarm by
The platform must support to provide Dashboard daily, weekly, monthly. Ratio chart by alarm status (New/ Fixed).
8 Dashboard & Chart of alarm by daily, weekly, monthly. Ratio Not pass: The platform does not support to provide Dashboard & Chart
chart by alarm status (New/ Fixed) of alarm by daily, weekly, monthly. Ratio chart by alarm status (New/
Fixed).
Pass: The platform support to provide Dashboard & Chart of using data
The platform must support to provide Dashboard plans.
9 Dashboard
& Chart of using data plans Not pass: The platform does not support to provide Dashboard & Chart
of using data plans.
Pass: The platform support to provide Dashboard & Chart of history for
The platform must support to provide Dashboard
usage, connectivity, airtime rating and billing.
10 Dashboard & Chart of history for usage, connectivity, airtime
Not pass: The platform does not support to provide Dashboard & Chart
rating and billing
of history for usage, connectivity, airtime rating and billing.
11 Reporting The platform must support to provides data, voice Pass: The platform support to provides data, voice and SMS usage by
and SMS usage by SIM, Sub-Customer and Rate SIM, Sub-Customer and Rate Plan.
30
Not pass: The platform does not support to provides data, voice and SMS
Plan
usage by SIM, Sub-Customer and Rate Plan.
Pass: The platform support to provide details of every PDP context
The platform must support to provide details of activation, including start time, duration and data volume as a minimum.
12 Reporting every PDP context activation, including start time, Not pass: The platform does not support to provide details of every PDP
duration and data volume as a minimum. context activation, including start time, duration and data volume as a
minimum.
Pass: The platform support to provides reporting on the number of active
The platform must support to provides reporting and inactive SIMs.
13 Reporting
on the number of active vs. inactive SIMs Not pass: The platform does not support to provides reporting on the
number of active and inactive SIMs.
Pass: The platform support to provide time-based session information for
The platform must support to provide time-based analytical purposes.
14 Reporting
session information for analytical purposes Not pass: The platform does not support to provide time-based session
information for analytical purposes.
Pass: The platform support to store an audit trail of every action taken in
The platform must support to store an audit trail the platform, including action, affected SIM and user ID of the person
of every action taken in the platform, including who made the change.
15 Reporting
action, affected SIM and user ID of the person Not pass: The platform does not support to store an audit trail of every
who made the change action taken in the platform, including action, affected SIM and user ID
of the person who made the change.
Pass: The platform support to provide easily searchable dashboard of all
The platform must support to provide easily
SIMs, organized by ICCID and MSISDN.
16 Inventory Management searchable dashboard of all SIMs, organized by
Not pass: The platform does not support to provide easily searchable
ICCID and MSISDN
dashboard of all SIMs, organized by ICCID and MSISDN.
XVI Automation
The platform must support rules-based business Pass: The platform support rules-based business process automation with
1 Automation
process automation with intuitive, easy and non- intuitive, easy and non-programmatic way to create automation rules
31
beyond notification.
programmatic way to create automation rules Not pass: The platform does not support rules-based business process
beyond notification automation with intuitive, easy and non-programmatic way to create
automation rules beyond notification.
Pass: The platform support automated SIM provisioning: SIM Rate Plan
The platform must support automated SIM Changes, SIM State Changes, and SIM custom field changes.
2 Automation provisioning: SIM Rate Plan Changes, SIM State Not pass: The platform does not support automated SIM provisioning:
Changes, and SIM custom field changes. SIM Rate Plan Changes, SIM State Changes, and SIM custom field
changes.
The platform must support automated Pass: The platform support automated preventative security diagnostics:
preventative security diagnostics: Notification Notification when a SIM has a credential
3 Automation when a SIM has a credential mismatch and when Not pass: The platform does not support automated preventative security
the IMEI in the package is different from the diagnostics: Notification when a SIM has a credential.
previous IMEI for a SIM
The platform must support the automated Pass: The platform support the automated subscription management
subscription management, including: including SIM data limit, SIM expiration and SIM plan completion.
+ SIM data limit, triggered when a prepaid plan Not pass: The platform does not support the automated subscription
comes close to using its included usage management including SIM data limit, SIM expiration and SIM plan
4 Automation + SIM expiration, triggered when a SIM on a completion.
prepaid plan comes close to its expiration date
+ SIM plan completion, triggered when a SIM's
prepaid plan term ends due to either term
expiration or data consumption
Pass: The platform support standard automated business rules that are
The platform must support standard automated
triggered when any SIM start/end a session or have abnormal actions.
business rules that are triggered when:
+ any SIM starts a session Not pass: The platform does not support standard automated business
5 Automation rules that are triggered when any SIM start/end a session or have
+ any SIM ends a session
+ a SIM has more connections than expected in abnormal actions.
the current billing cycle
32
+ a SIM has more/fewer connections than
expected in the trailing 24 hours
+ per SIM when the SIM has not been connected
for [Offline_Hours] hours
+ a SIM registers to the network in a selected zone
in the trailing 24 hours
+ a SIM's cycle to date data usage is above the
specified threshold
+ a SIM's cycle to date data usage is above the
specified threshold in a zone
+ per account/zone when data usage for the zone
is over the limit for the pooled plans
+ per SIM when usage is over limit in the trailing
24 hours
+ per account per zone when SMS usage for the
zone is over the limit for the pooled plans
+ a SIM's cycle to date voice usage is above the
specified threshold
+ a SIM's cycle to date voice usage is above the
specified threshold in a zone
+ a SIM's daily voice usage is above the specified
threshold
Pass: The platform support the ability to automatically notify the
The platform must support the ability to
assigned business owner of excessive usage for that account.
6 Automation automatically notify the assigned business owner
Not pass: The platform does not support the ability to automatically
of excessive usage for that account
notify the assigned business owner of excessive usage for that account.
7 Automation The platform must support the ability to Pass: The platform support the ability to automatically notify the
automatically notify the assigned business owner assigned business owner of numerous logins within the platform.
of numerous logins within the platform Not pass: The platform does not support the ability to automatically
notify the assigned business owner of numerous logins within the
33
platform.
The platform must support the ability to assigned business owner when the account is nearing a prescribed usage
automatically notify the assigned business owner threshold.
8 Automation
when the account is nearing a prescribed usage Not pass: The platform does not support the ability to automatically
threshold notify the assigned business owner when the account is nearing a
prescribed usage threshold.
assigned business owner of SIM activations.
9 Automation automatically notify the assigned business owner
of SIM activations
notify the assigned business owner of SIM activations.
Pass: The platform support the ability to take action against defined
The platform must support the ability to take business rules and triggers. Should support the ability to specify multiple
action against defined business rules and triggers. follow-up actions, allowing you to make temporary changes to the device
Should support the ability to specify multiple behavior in response to business conditions.
10 Automation
follow-up actions, allowing you to make Not pass: The platform does not support the ability to take action against
temporary changes to the device behavior in defined business rules and triggers. Should support the ability to specify
response to business conditions multiple follow-up actions, allowing you to make temporary changes to
the device behavior in response to business conditions.
Pass: The platform support the ability to send an email message to one or
The platform must support the ability to send an more email addresses or to the end user associated with the device, based
email message to one or more email addresses or on a business rule.
11 Automation
to the end user associated with the device, based Not pass: The platform does not support the ability to send an email
on a business rule message to one or more email addresses or to the end user associated with
the device, based on a business rule.
12 Automation The platform must support the ability to send an Pass: The platform support the ability to send an SMS directly to your
SMS directly to your device when triggered by a device when triggered by a certain event. Some devices are programmed
certain event. Some devices are programmed to to “wake up” when they receive an SMS or to send diagnostic
“wake up” when they receive an SMS or to send information back to a server when they receive an SMS. Depending on
34
how your device is programmed, the SMS action can help you interact
directly with your devices in the field.
diagnostic information back to a server when they Not pass: The platform does not support the ability to send an SMS
receive an SMS. Depending on how your device directly to your device when triggered by a certain event. Some devices
is programmed, the SMS action can help you are programmed to “wake up” when they receive an SMS or to send
interact directly with your devices in the field diagnostic information back to a server when they receive an SMS.
Depending on how your device is programmed, the SMS action can help
you interact directly with your devices in the field.
Pass: The platform support the ability to push an API message. Platform
The platform must support the ability to push an should be able to send a programmatic message to a URL you specify
API message. Platform should be able to send a when a rule is triggered.
13 Automation
programmatic message to a URL you specify Not pass: The platform does not support the ability to push an API
when a rule is triggered. message. Platform should be able to send a programmatic message to a
URL you specify when a rule is triggered.
Pass: The platform support the ability to automatically change a device’s
SIM state when a rule is triggered.
14 Automation automatically change a device’s SIM state when a
rule is triggered
change a device’s SIM state when a rule is triggered.
Pass: The platform support the ability to automatically change a device’s
The platform must support the ability to rate plan when a rule is triggered. For example, if a device uses more data
automatically change a device’s rate plan when a than expected, platform should be able to switch it from a standard rate
rule is triggered. For example, if a device uses plan to a premium rate plan.
15 Automation
more data than expected, platform should be able Not pass: The platform does not support the ability to automatically
to switch it from a standard rate plan to a change a device’s rate plan when a rule is triggered. For example, if a
premium rate plan device uses more data than expected, platform should be able to switch it
from a standard rate plan to a premium rate plan.
16 Automation The platform must support the ability to limit or Pass: The platform support the ability to limit or filter the devices that are
filter the devices that are subject to the rule, so subject to the rule, so that an automation rule only applies to a subset of
that an automation rule only applies to a subset of devices.
35
Not pass: The platform does not support the ability to limit or filter the
devices devices that are subject to the rule, so that an automation rule only applies
to a subset of devices.
Pass: The platform support automation based on the following special
rules:
+ Session Start, Session
+ CDR Streaming
The platform must support automation based on + Push raw CDR to destination URL
the following special rules: + SMS-MO Received
+ Session Start, Session End Notify when a device + Monitor SMS Usage for fraud or abuse
begins or closes connection to the wireless + Get Notified when device sends SMS to a specific short code
network + OTA Swap: for over-the-air SIM swaps, especially with Global SIM
+ CDR Streaming feature
+ Push raw CDR to destination URL + OTA MSISDN: sync device MSISDN
17 Automation
+ SMS-MO Received Not pass: The platform does not support automation based on the
+ Monitor SMS Usage for fraud or abuse following special rules:
+ Get Notified when device sends SMS to a + Session Start, Session
specific short code + CDR Streaming
+ OTA Swap: for over-the-air SIM swaps, + Push raw CDR to destination URL
especially with Global SIM feature + SMS-MO Received
+ OTA MSISDN: sync device MSISDN + Monitor SMS Usage for fraud or abuse
+ Get Notified when device sends SMS to a specific short code
+ OTA Swap: for over-the-air SIM swaps, especially with Global SIM
feature
+ OTA MSISDN: sync device MSISDN
General Requirements
XVII
for Platform
Platform Integration All data and control found within the Platform Pass: The platform support access by a web-based interface.
1
Capability must be accessible by a web-based interface Not pass: The platform does not support access by a web-based interface.
36
Pass: The platform support to customize Web-based UI to allow users to
Web-based UI should be customizable to allow choose the appropriate view relevant to their operational needs.
Platform Integration
2 users to choose the appropriate view relevant to Not pass: The platform does not support to customize Web-based UI to
Capability
their operational needs. allow users to choose the appropriate view relevant to their operational
needs.
Pass: The platform support to access all data and control via API.
Platform Integration All data and control found within the Platform
3 Not pass: The platform does not support to access all data and control via
Capability must be accessible via API
API.
Platform Integration Pass: The platform support Pull and Push APIs.
4 The platform must support Pull and Push APIs
Capability Not pass: The platform does not support Pull and Push APIs.
Pass: The platform support sandbox environment for API testing outside
Platform Integration The platform must support sandbox environment of production.
5
Capability for API testing outside of production Not pass: The platform does not support sandbox environment for API
testing outside of production.
Platform Integration Pass: The platform support to provide REST APIs.
6 The platform must support to provide REST APIs
Capability Not pass: The platform does not support to provide REST APIs.
Pass: The platform support to provide XML APIs and SOAP APIs.
Accepted: The platform must have roadmap to support to provide XML
APIs and SOAP APIs free of charge within 06 months since the effective
Platform Integration The platform must support to provide XML APIs
7 Not pass: Does not meet any of these requirements:
Capability and SOAP APIs
- The platform support to provide XML APIs and SOAP APIs.
- The platform must have roadmap to support to provide XML APIs and
SOAP APIs free of charge within 06 months since the effective date of
The platform must support the capability of Pass: The platform support the capability of integration with all Viettel
8 Global expansion support integration with all Viettel connections all over connections all over the globe, Viettel subsidiaries in 11 countries
the globe, Viettel subsidiaries in 11 countries (Vietnam, Laos, Cambodia, Myanmar, Timor Leste, Haiti, Peru,
37
Tanzania, Burundi, Cameroon, Mozambique).
(Vietnam, Laos, Cambodia, Myanmar, Timor Not pass: The platform does not support the capability of integration with
Leste, Haiti, Peru, Tanzania, Burundi, Cameroon, all Viettel connections all over the globe, Viettel subsidiaries in 11
Mozambique) countries (Vietnam, Laos, Cambodia, Myanmar, Timor Leste, Haiti, Peru,
Tanzania, Burundi, Cameroon, Mozambique).
Pass: Platform support at least English and Buyer can add new language
Platform must support Multilingual (at least (Vietnamese) into the system.
9 Multilingual Vietnamese and English) and have method to add Not pass: Do not meet one of these requirements:
new language into system. - Platform support multilingual (Vietnamese and English).
- User can add new language into the system.
Pass: The platform support fully delivered as a hosted service or on
The platform must support fully delivered as a
Delivery and Product premise, Private Cloud or hybrid cloud.
10 hosted service or on premise, Private Cloud or
Release Cycle Not pass: The platform does not support fully delivered as a hosted
hybrid cloud
service or on premise, Private Cloud or hybrid cloud.
Pass: The platform must not have any single point of failure and ensure
The platform must not have any single point of
IoT services will not be interrupted by a single failure for 99.999% of
Delivery and Product failure and ensure IoT services will not be
11 time.
Release Cycle interrupted by a single failure for 99.999% of
Not pass: The platform have any single point of failure that result in IoT
time.
services interrupted
Pass: The platform has the life span of the included hardware equipment
Delivery and Product The life span of the hardware equipment of the at least 4 years.
12
Release Cycle platform is at least 4 years Not pass: The platform has the life span of the equipment less than 4
years.
Pass: The platform has the minimum warranty time for the whole system
Delivery and Product The minimum warranty time for the whole system (hardware and software) ≥ 01 year.
13
Release Cycle (software and hardware) ≥ 01 year Not pass: The platform has the minimum warranty time for the whole
system (hardware and software) < 01 year.
14 Pass: The platform has the support minimum time the vendor commit to
Delivery and Product The minimum time the vendor commit to provide
38
technical support service (after warranty time) ≥ provide technical support service (after warranty time) ≥ 03 year.
Release Cycle
03 year Not pass: The platform does not support.
Pass: The platform support connectivity analytic including Descriptive,
Diagnostic, Predictive and Prescriptive Analytics based on the conditions
of networks.
Accepted: The platform must have roadmap to support connectivity
including Descriptive and Diagnostic analytic provided based on the
conditions of networks free of charge within 06 months since the
The platform must support connectivity analytic
15 Connectivity Analytics Not pass: Does not meet any of these requirements:
provided based on the conditions of networks
- The platform support connectivity analytic including Descriptive,
Diagnostic, Predictive and Prescriptive Analytics based on the conditions
of networks.
- The platform must have roadmap to support connectivity including
Descriptive and Diagnostic analytic provided based on the conditions of
networks free of charge within 06 months since the effective date of the
Pass: The platform support the ability to route to cloud storage services
The platform must support the ability to route to
16 Cloud supporting Not pass: The platform does not support the ability to route to cloud
cloud storage services
storage services
Pass: The platform support Application protection at the level of N+1
(for the whole system) to ensure that even when one node down, the
Application protection at the level of N+1 (for the
application still running on other nodes.
17 Backup whole system) to ensure that even when one node
Not pass: The platform does not support Application protection at the
down, the application still running on other nodes.
level of N+1 (for the whole system) to ensure that even when one node
down, the application still running on other nodes.
18 Backup Server protection at the level of N+1 (for the Pass: The platform support Server protection at the level of N+1 (for the
whole system) to ensure that even when one node whole system) to ensure that even when one node down, the platform still
down, the platform still can run normally on other can run normally on other nodes.
39
Not pass: The platform does not support Server protection at the level of
nodes. N+1 (for the whole system) to ensure that even when one node down, the
platform still can run normally on other nodes.
Pass: The platform has the original data and backup data is stored in
The original data and backup data is stored in
separated storage to ensure that data is always availability even when 01
separated storage (Storage protection at the level
19 Backup storage system got errors..
of N+1) to ensure that data is always availability
Not pass: The platform has the original data and backup data is stored in
even when 01 storage system got errors.
same storage.
Pass: The platform has the availability of hardware and software for the
The availability of hardware and software for the whole system ≥ 99.99%.
20 Availability
whole system ≥ 99.99% Not pass: The platform has the availability of hardware and software for
the whole system < 99.99%.
Response time ≤ 100 ms for at least 99% of Pass: The platform has Response time ≤ 100 ms for at least 99% of
messages (only considering the time the messages messages.
21 Response time
is routing within the platform, not include the time Not pass: The platform has Response time ≤ 100 ms for at least 99% of
messages are routing via radio access network) messages.
Pass: The platform support to install many tenants of platform as needed
Viettel can install many tenants of platform as (the minimum is 22 tenants).
22 License model
needed (the minimum is 22 tenants). Not pass: The platform does not support install many tenants of platform
as needed (the minimum is 22 tenants).
Pass: The platform should support On Premises and Private Cloud
The Platform should support On Premises and deployment by installed in Viettel data center, or Viettel's Customer
23 Deployment model Private Cloud deployment by installed in Viettel Premises.
data center, or Viettel's Customer Premises. Not pass: The platform does not support the On Premises or Private
Cloud deployment.
Pass: The platform support to be managed by Viettel only.
24 Operation model The Platform should be operated by Viettel.
Not pass: The platform does not support to be managed by Viettel only.
25 Brand name The Platform should be used under Viettel Brand Pass: The platform support to be branded by Viettel name.
40
name. Not pass: The platform does not support to be branded by Viettel name.
The Platform must have the hardware ready to Pass: The platform support the software license as pay as you go model.
support at least 180.000 subscribers with the The initial capacity of the platform for the signed contract must support at
following requirements: least 180,000 subscribers for CMP.
26 Capacity - Updates their usage information at least once Not pass: The platform does not support the software license as pay as
per 15 minutes. you go model. The initial capacity of the platform for the signed contract
- Support at least 2500 concurrent network must support at least 180,000 subscribers for CMP
connections per second.
The system must support the integration with AEP Pass: The CMP vendor provide all necessary APIs, tools, software, and
- Application Enablement Platform that Viettel technical support for the successful integration of CMP to 3 rd party AEP
27 AEP Integration has plan to deploy that may include but not by other vendors
limited to AEP by Thingworx, Nokia IMPACT, Not Pass: The CMP vendor does not support Viettel for the successful
Yodiwo, ZTE, IBM, Ayala integration with AEP provided by other vendor.
In case the vendor of CMP or AEP have update or
upgrade, the existing CMP vendor must support to Pass: The CMP vendor provide all necessary APIs, tools, software, and
cooperate for the future integration with the new technical support for the successful integration of CMP to new version of
Future proof of AEP
28 version of AEP. Viettel has the right to choose the AEP by other vendors
interworking
standards, methods that both CMP and AEP Not Pass: The CMP vendor does not support Viettel for the successful
vendor must follow for the successful integration integration with new version of AEP provided by other vendor.
of CMP and AEP
Pass: The system can automatically increase the capacity of the system
when the load increase.
Accepted: The Platform has the roadmap to support automatically
Platform can automatically increase the capacity increasing the capacity of the system when the load increases free of
29 Auto scaling charge within 06 months since the effective date of the contract and will
of the system when the load increases.
- The system can automatically increase the capacity of the system when
the load increase.
41
- The Platform has the roadmap to support automatically increasing the
capacity of the system when the load increases free of charge within 06
the FAC.
Pass: User is able to update and turn off some nodes in the system
Platform must have the ability to update or turn
without affecting overall system.
30 Hot maintenance off some nodes in the system without affecting the
Not pass: User is not able to update and turn off some nodes in the
overall system.
system without affecting overall system.
Every node in the system has load balancing Pass: Platform on Cloud support load balancing feature in every node.
31 Load balancing feature so that the load can be share to many other Not pass: Platform on Cloud does not support load balancing feature in
nodes. every node.
Pass:
- Every errors, user actions, system actions should be logged
Platform must have the ability to log every errors,
- User can access and read all the log visually.
32 Logging user actions, system actions for trouble shooting
Not pass: Does not meet one of these requirement:
purpose later.
Pass: User is able to view/read the information (load, status, errors) of all
Platform must have interface to view all the server
server in the system via platform's GUI and has tool to troubleshoot errors
in the system with information such as load,
33 Server monitoring Not pass: User is not able to view/read the information (load, status,
status, errors and has tools to troubleshoot when
errors) of all server in the system via platform's GUI or does not has tool
errors happen.
to troubleshoot errors
Pass: User is able view/read load and status of each node in the system
Platform must have interface to view load and via platform's GUI
34 Node monitoring
status of all nodes in the system. Not pass: User is not able view/read load and status of each node in the
system via platform's GUI
35 Notification Platform must support mail and SMS notification Pass:
when abnormal events in the system happen. - Platform support mail and SMS notification
User can easily define abnormal events and - User is able to define abnormal events and configure who can receive
42
notifications.
Not pass: Does not meet one of these requirements:
configure who can receive notification. - Platform support mail and SMS notification
- User is able to define abnormal events and configure who can receive
notifications.
Pass: System load of servers and other network devices of the system
when running with the maximum number of subscibers (180,000
-System load of servers and other network devices subscribers) must meet the following criteria:
of the system when running with the maximum +Server: CPU ≤ 75%, RAM ≤ 90%.
number of subscibers (180,000 subscribers) must +Device for storing data: IOPS ≤ 80%, hard disk space usage ≤80%
meet the following criteria: +Network device: Number of ports used and device throughput ≤80%.
+Server: CPU ≤ 75%, RAM ≤ 90%. In case equipment is deployed active-active redundancy model, even if
+Device for storing data: IOPS ≤ 80%, hard disk one of the equipment is faulty and stop operation, the remaining
space usage ≤80% equipment must meet the system load parameters as above.
36 System load
+Network device: Number of ports used and Not pass: System load of servers and other network devices of the system
device throughput ≤80%. when running with the maximum number of subscibers (180,000
In case equipment is deployed active-active subscribers) does not meet the following criteria:
redundancy model, even if one of the equipment +Server: CPU ≤ 75%, RAM ≤ 90%.
is faulty and stop operation, the remaining +Device for storing data: IOPS ≤ 80%, hard disk space usage ≤80%
equipment must meet the system load parameters +Network device: Number of ports used and device throughput ≤80%.
as above. In case equipment is deployed active-active redundancy model, even if
one of the equipment is faulty and stop operation, the remaining
equipment does not meet the system load parameters as above.
43
II. Technical requirements for Application Enablement Platform (AEP)
II.1 Reference architecture for Application Enablement Platform (AEP)
Interconnection between AEP and Viettel’s existing network
44
II.2 Detailed technical requirements for Application Enablement Platform (AEP)
Device
1
Management
Device's
1.1 information
management
Pass: User is able to manage (read, update) the general information of the
Platform must provide a GUI (web portals,
device (name, producer, ID) via platform’s GUI (web portals or mobile apps)
mobile apps) or APIs to manage the general
General information or APIs.
1.1.1 information of the device including but not
management Not pass: User is not able to manage (view, update) the general information
limited to name, producer, ID
of the device (name, producer, ID) via platform’s GUI (web portals, mobile
apps) or APIs.
Platform must have the ability to manage device Pass: User is able to manage (create, read, update, delete) the device template
templates (all the device's specifications such as and create new device based on the device template via platform’s GUI and
Device template the general information of the device, device's APIs.
1.1.2
management attributes and device's commands). Not pass: User is not able to manage (create, read, update, delete) the device
New device can be created based on the pre- template or create new device based on the device template via platform's
defined device template. GUI or APIs.
Platform must have the ability to group devices Pass: User is able to group devices into collections and assigned to different
into collections by different criteria. account for each collections via platform's GUI or APIs
Device collection
1.1.3 These collections can be organized into data Not pass: Platform does not support one of these requirements:
management
structure such as tree, list and also can be - Group devices into collection
assigned with their own users. - Assign collection to account
Platform must show the location of devices on Pass: The platform can show the location of devices on the map and have a
Device location
1.1.4 the map, support at least Google Map. method to add new map or change map. The platform support google map.
management
Platform also have to provide a method to add Accepted: The platform can show the location of devices on the map and
45
have a method to add new map or change map. And have roadmap to support
google map with free of charge within 06 months since the effective date of
ID Function Description the contract and will be testedEvaluated
before the criteria
FAC.
new map or change the map if necessary.
Not pass: Platform does not support one of these requirements:
- Show location of devices on the map
- Have the method to add new map or change map
Platform must have the ability to manage the
Pass: User is able to view and directly/remotely update the version and
Device version and information of version and firmware of the
firmware of devices via platform's GUI or APIs
1.1.5 firmware device.
Not pass: User is not able to view and directly/remotely update the version
management Platform also can change and update the
and firmware of devices via GUI and APIs
firmware directly and remotely when needed.
Device's data
1.2
management
Pass: User is able to view, retrieve, the real-time data via platform’s UI or
Platform must have the ability to store the real
Real time data APIs.
1.2.1 time data of the device, allow access the data in
management Not pass: User is not able to view, retrieve the real-time data via platform’s
real-time via User Interface (UI) or APIs.
UI and APIs.
Pass: User is able to view, retrieve the historical data via platform’s GUI or
Platform must have the ability to store historical
Historical data APIs.
1.2.2 data of the device in storage for at least 01
management Not pass: User is not able to view, retrievethe historical data via platform’s
months, allow access the data via UI and APIs.
GUI and APIs.
Device' status
1.3
Management
1.3.1 Device connectivity Platform must have the ability to monitor the Pass: User is able to view the connectivity status of the devices such as
status Management connectivity status of the devices such as online, online, offline via platform’s GUI or APIs
offline. Accepted: Can integrate to other Connectivity Management Platform (CMP)
to provide the function or have roadmap to support monitoring the
connectivity status of the devices such as online, offline free of charge within
06 months since the effective date of the contract and will be tested before the
46
FAC.
ID Function Description Evaluated
-User is able to view the connectivity criteria
status of the devices such as online,
offline via platform’s GUI or APIs
- Can integrate to other Connectivity Management Platform (CMP) to provide
the function or have roadmap to support monitoring the connectivity status of
the devices such as online, offline free of charge within 06 months since the
Pass: User is able to read/view the status of device (error, operation, status,
Platform must have the ability to monitor the
Device status battery level) via platform’s GUI or APIs.
1.3.2 status of the device including but not limited to:
management Not pass: User is not able to read/view the status of device (error, operation,
error, operation status, battery level
status, battery level) via platform’s GUI or APIs.
Device Controlling
1.4
and updating
Pass: User is able to control the device's attributes via platform's GUI and
Platform must support user to use commands to APIs (CLI)
1.4.1 Device Controlling
control devices via UI and APIs Not pass: User is not able to control the device's attributes via platform's GUI
and APIs (CLI)
Pass: User is able to view/read and update the device's configuration via
Device
Platform must support user to view and update platform GUI and APIs (CLI).
1.4.2 configuration
the device's configurations via UI and APIs. Not Pass: User is not able to view/read and update the device's configuration
updating
via platform GUI and APIs (CLI).
1.5 Device integration
1.5.1 Security Platform must have security mechanism to Pass: User is able to grant authority for accessing the system to devices or set
guarantee that only authorized devices can up rules/policies to make a barrier to unauthorized devices via platform's GUI
connect to the system and can kick abnormal or APIs. User is also able to kick devices out of the system via platform's GUI
devices out of the system. or APIs.
- Can grant authority for accessing the system to devices or set up
47
rules/policies to make a barrier to unauthorized devices via platform's GUI or
APIs.
- Can kick devices out of the system via platform's GUI or APIs
Platform must have a method to add new Pass: User is able to program the Adapter, Software Gateway or similar
Adapter, Software Gateway or similar technology or use scripting languages to integrate new protocols or standard
technology in order to integrate new protocols, into the system via platform's GUIs or CLI.
1.5.2 Protocol integration
standards into the system. It should be done by Not pass: User is not able to program the Adapter or Software Gateway or
programming the adapter or by using a scripting similar technology or use scripting languages to integrate new protocols or
language. standard into the system via platform's GUIs or CLI.
Pass: The platform support HTTP, MQTT. Supplier/bidder must provide a
method to check this requirement. For example, with MQTT, platform must
either connect to a MQTT supported device or show the MQTT exchanged
Standards Platform must support at least standards: HTTP,
1.5.3 message
conformance MQTT
Not pass: The platform does not support one of these standards:
- HTTP
- MQTT
Application
2
Enablement
Automated
2.1
scenario
Pass: User is able to create scenarios based on time event and trigger tasks
Platform allows user to create scenarios based on
(send SMS or integrate to outside sms gateway, send mail, control the device
time so that at a predefined time, the system does
and send command to outside system) via platform's GUI or APIs.
2.1.1 Time trigger some tasks including but not limited to: sending
Not Pass: User is not able to create scenarios based on time event and trigger
SMS, sending mail, controlling the device, send
tasks (send SMS, send mail, control the device and send command to outside
command to the outside system.
system) via platform's GUI and APIs.
2.1.2 Location trigger Platform allows user to create scenarios based on Pass: User is able to create scenarios based on device's location and trigger
location so that when a device enters or exits an tasks (send SMS, send mail, control the device and send command to outside
area (predefined on the map), the system does system) via platform's GUI or APIs.
48
Accepted: Can integrate to open source rule engine that provide the location
trigger function or have the roadmap to support location trigger feature free of
charge within 6 months after signing date and will be tested before the FAC.
some tasks including but not limited to: sending
- User is able to create scenarios based on device's location and trigger tasks
ID Function SMS, sending mail,Description
controlling the device, send Evaluated criteria
(send SMS, send mail, control the device and send command to outside
command to the outside system.
system) via platform's GUI or APIs.
- Can integrate to open source rule engine that provide the location trigger
function or have the roadmap to support location trigger function free of
charge within 6 months after signing date and will be tested before the FAC.
Platform allows user to create automation
scenarios, on which system or devices react
Pass: User is able to create automation scenarios based on pre-defined
when one or more devices meet some criteria.
threshold and trigger task (send SMS, send email, control the device, send
For instance, when a device's attribute exceed the
command to outside system) via platform's GUI or APIs.
2.1.3 Automation scenario predefined threshold, system automatically does
Not pass: User is not able to create automation scenarios based on pre-
some tasks including but not limited to: sending
defined threshold and trigger task (send SMS, send email, control the device,
SMS, sending email, controlling the device and
send command to outside system) via platform's GUI or APIs.
other devices and sending command to outside
system.
Platform allows user to create complicated
Pass: User is able to create complicated business process flow based on pre-
business process flows in order to handle the
defined threshold or event in order to control other device or interact with
business flow from the device through many
Business process outside system via platform's GUI or APIs.
2.1.4 user's predefined steps. The output of the data in
flow management Not pass: User is not able to create complicated business process flow based
each step decides which actions will be taken by
on pre-defined threshold or event in order to control other device or interact
the system such as controlling other devices,
with outside system via platform's GUI or APIs.
interact with outside system.
2.2 Dashboard
2.2.1 Flexible dashboard User can create flexible dashboard without Pass: User is able to:
coding: - Set up the input data for dashboard (device's data, data from other system)
- Inputs of dashboard including but not limited - Organize chart in dashboard
49
- Drag-drop the chart into flexible layout
to: device's data, data from other system. Not pass: User is not able to do one of these requirements:
- Can organize charts into group. - Set up the input data for dashboard (device's data, data from other system)
- Can drag-drop the charts into flexible layout. - Organize chart in dashboard
- Drag-drop the chart into flexible layout
Pass: User is able to set the location of devices in real map or insert the user-
ID Function Description defined map and set the location of devices
Evaluated in this map. User is also able to
criteria
create dashboard reflect these maps.
Accepted: The platform must have the roadmap to support dashboard that
reflects real map free of charge within 06 months since the effective date of
Dashboard reflect User can create dashboard reflect the locations of
2.2.2 Not pass: Does not meet any of these requirements:
real map the devices in real map or in user-defined map.
- User is able to set the location of devices in real map or insert the user-
defined map and set the location of devices in this map. User is also able to
create dashboard reflect these maps.
- The platform must have the roadmap to support dashboard that reflects real
map free of charge within 06 months since the effective date of the contract
Application
2.3
Enablement
Pass: User is able to create, read, update, delete virtual devices and use them
in order to develop apps or test device's features via platform's GUI or APIs.
Device Simulation Platform must have tools to simulate the devices
2.3.1 Not pass: User is not able to create, read, update, delete virtual devices and
tools for developing application without real devices.
use them in order to develop apps or test device's features via platform's GUI
or APIs.
2.4 API management
2.4.1 Developer API Platform must have APIs for application to Pass: Supplier/bidder provide the list of APIs:
connect, use and gather information. The APIS - Device management APIs
are including but not limited to: - Event management APIs
- Device management APIs - User management APIs
50
Supplier/bidder also provide method to test all these APIs
Not pass: Supplier/bidder cannot provide one of these list of APIs:
ID Function Description - Device management APIs Evaluated criteria
- Event management APIs
- Scenario management APIs
- User management APIs
Or supplier/bidder cannot provide method to test all these APIs
Pass: User is able to view/read and update the detail specification of each
Platform must have detailed specifications for
API in the system.
2.4.2 API Specification each API on the system, and those specifications
Not pass: User is not able to view/read and update the detail specification of
can be easily modified.
each API in the system.
Platform must allow users to integrate their own Pass: User is able to integrate his/her own APIs into the system.
2.4.3 User's APIs
APIs into the system. Not pass: User is not able to integrate his/her own APIs into the system.
Pass: User is able to view/read the usage of APIs (number of API call, API's
average processing time, result of API call and successful rate).
Accepted: Provide a method to calculate the API usage from data or have a
roadmap to support monitoring the APIs usage (number of API call, result of
API call and successful rate) free of charge within 06 months since the
User can view/read the usage of the APIs
including but not limited to: number of API call,
2.4.4 API usage Not pass: Does not meet any of these requirements:
result of API call (success or fail), and successful
- User is able to view/read the usage of APIs (number of API call, result of
rate.
API call and successful rate).
- Provide a method to calculate the API usage from data or have a roadmap to
support monitoring the APIs usage (number of API call, result of API call and
successful rate) free of charge within 06 months since the effective date of the
Pass: System's admin is able to create user and grant authority to access
Platform must provide security mechanism to
specific API or group of APIs.
2.4.5 Security ensure that only authorized user can access to the
Not pass: System's admin is not able to create user and grant authority to
corresponding APIs.
access specific API or group of APIs.
51
Pass:
- The platform support RESTful
2.4.6 Protocol Platform must support at least RESTful protocol. - Supplier/bidder provide method to prove this requirement
Not pass: The platform does not support RESTful or supplier/bidder is not
able to provide a method to prove this requirement.
3 Analytic Platform
3.1 Storage
Pass: User is able to store data in big data storage and can access, fetch and
Platform must have the ability to store data in big
query the data via tools or APIs provided by supplier/bidder.
3.1.1 Big data storage data storage and must provide tools or APIs to
Not pass: User is not able to store data in big data storage and can access,
access and query the data.
fetch and query the data via tools or APIs provided by supplier/bidder.
Pass: User is able to store time series data and can access, fetch, search and
Platform must have the ability to store time
query the data via tools or APIs provided by supplier/bidder.
3.1.2 Time series database series data and must provide tools or APIs to
Not pass: User is not able to store time series data and can access, fetch,
quickly access, query and search the data.
search and query the data via tools or APIs provided by supplier/bidder.
Pass: User is able to view/read real time data and can access and manipulate
Platform must have the ability to manage real
the data via tools or APIs provided by supplier/bidder.
3.1.3 Real time data time data streaming and provide tools or APIs to
Not pass: User is not able to store time series data and can access, fetch,
access, query and manipulate the data.
search and query the data via tools or APIs provided by supplier/bidder.
3.2 Processing
3.2.1 Statistics Platform must have the ability to analyze the Pass:
system's data using statistical methods and - Supplier/bidder provide a list of supported statistical methods and
provide a dashboard/chart system to visually corresponding detail information.
view the analytic results. - Platform have a dashboard/chart system to visually show the analytic
results.
Not pass:
- Supplier/bidder does not provide a list of supported statistical methods and
corresponding detail information.
- Or platform does not have a dashboard/chart system to visually show the
52
analytic results.
Pass: User is able to search for specific pattern in data and get notifications
Platform must provide a method to search for
about the abnormal events happen in the system.
3.2.2 Data analytic specific pattern in data and notify users about
ID Function Not pass: User is not able to search a specific pattern in data and get
abnormal events. Description Evaluated criteria
notifications about the abnormal events happen in the system.
Pass: User is able to build his/her own data analytical features via built-in
Platform must provide tools for user to build the tools provided by supplier/bidder.
3.2.3 Customized analytic
data analytical features by themselves. Not Pass: User is not able to build his/her own data analytical features via
built-in tools provided by supplier/bidder.
Pass: User is able to build statistical model based on historical data to predict
the trend of data and future event.
Accepted: Supplier/bidder guarantees to provide this function without any
Platform must allow user to build statically additional charge within 6 months after signing date.
3.2.4 Predictive model based on historical data and then predict Not pass: Does not meet any of these requirements:
the trend of data and future event. - User is able to build statistical model based on historical data to predict the
trend of data and future event.
- Supplier/bidder guarantees to provide this function without any additional
charge within 6 months after signing date.
Pass: User is able to search for a specific pattern in real time data and get
Platform must provide a method to search for the
notifications about the abnormal events happen in the system.
3.2.5 Real time processing specific pattern in flow of real time data and
Not pass: User is not able to search for a specific pattern in real time data and
notify users about abnormal events.
get notifications about the abnormal events happen in the system.
3.2.6 Search engine Platform must provide search engine to quickly Pass: User is able to search in big data using platform's built-in search engine
search in big data.
Accepted: Can integrate to open source search engine or have a roadmap to
support built-in search engine free of charge within 06 months since the
- User is able to search in big data using platform's built-in search engine.
- Can integrate to open source search engine or have a roadmap to support
53
built-in search engine free of charge within 06 months since the effective date
of the contract and will be tested before the FAC.
Pass: User is able to define rules to process data based on platform's built-in
Platform must provide rule engine to process the
rule engine.
3.2.7 Rule engine data flow so that the user can define rules to
Not pass: User is not able to define rules to process data based on platform's
process the data.
built-in rule engine.
3.3 Integration
Platform must have the ability to send data to the
Pass: User is able to send data directly in real time or indirectly via storage
outside Big data Platform to process externally.
3rd Big data from the platform to outside Big data Platform.
3.3.1 It should be done by sending directly in real time
Platform integration Not pass: User is not able to send data directly in real time or indirectly via
from the Platform or sending indirectly via
storage from the platform to outside Big data Platform.
storage.
Pass: User is able to input data from various sources (devices, external
Data Source Platform must allow user to input the data from system) to the platform.
3.3.2
Integration various sources: devices, external system. Not pass: User is not able to input data from various sources (devices,
external system) to the platform.
Pass: User is able to input data from various type of datasets (Excel file, csv,
database file)
Accepted: Support at least 1 of 3 types (Excel, csv, database file) or have a
roadmap to support input data from various type of datasets (Excel file, csv,
database file) free of charge within 06 months since the effective date of the
Platform must allow user to input the data from contract and will be tested before the FAC.
Data Source
3.3.3 various type of datasets including but not limited Not pass: Do not meet one of these requirements:
Integration
to: Excel file, csv, database file - User is able to input data from various type of datasets (Excel file, csv,
database file)
- Support at least 1 of 3 types (Excel, csv, database file) or have a roadmap to
support input data from various type of datasets (Excel file, csv, database file)
free of charge within 06 months since the effective date of the contract and
54
4 Additional Services
4.1 Map
Platform must provide a ready-to-use map and Pass: Platform have a built-in map or supplier/bidder provide a way to
provide a way to integrate other maps to the integrate other maps to the platform (Viettel map, Google map).
4.1.1 Map
system including but not limited to Viettel map, Not pass: Platform does not have a built-in map or supplier/bidder provide a
Google map. way to integrate other maps to the platform (Viettel map, Google map).
4.2 Communication
Pass: User is able to send SMS via the platform or provide a way to integrate
Platform must have method to send SMS in
4.2.1 SMS to outside sms gateway
Vietnam
Not pass: User is not able to send SMS via the platform.
Pass: User is able to send email via the platform.
4.2.2 Mail Platform must have method to send email
Not pass: User is not able to send email via the platform.
Platform on the
5
Edge
Device
5.1
Management
Pass: User is able to view/read, update, and delete the information of devices
Platform has the ability to manage information of connecting to gateway.
5.1.1 Device management
devices connecting to gateway. Not pass: User is not able to view/read, update, and delete the information of
devices connecting to gateway.
Pass: Platform support all these connectivity standards:
- WiFi
- Bluetooth
Platform must support popular connectivity
Connectivity - ZigBee
5.1.2 standard including but not limited to: WiFi,
Standard Not pass: Platform does not support one of these connectivity standards:
Bluetooth, and ZigBee.
- WiFi
- Bluetooth
- ZigBee
55
5.2 Cloud Integration
Platform must have the ability to connect to Pass: Platform can connect to Cloud and receive command from Cloud using
ID CloudFunction
integration Cloud and receiveDescription
commands from Cloud using MQTT standard. Evaluated criteria
5.2.1
standard international message standard including but not Not pass: Platform cannot connect to Cloud or receive command from Cloud
limited to MQTT. using MQTT standard.
Pass: User can program adapter or use simple script language to connect the
gateway to different IoT Cloud.
Accepted: Provide a method to help Viettel connect the Platform to different
IoT Cloud environments or have a roadmap to support connecting to different
IoT Cloud enviroments free of charge within 06 months since the effective
Platform must have the ability to connect to
Multiple Cloud IoT different IoT Cloud environments. This should
5.2.2 Not pass: Does not meet any of these requirements:
Platform Supporting be done by programming the adapter or using
- User can program adapter or use simple script language to connect the
simple script language.
gateway to different IoT Cloud.
- Provide a method to help Viettel connect the Platform to different IoT Cloud
environments or have a roadmap to support connecting to different IoT Cloud
environments free of charge within 06 months since the effective date of the
5.3 Data processing
Pass: Platform on the Edge can temporarily store data from devices while
Platform must have the ability temporarily store
Temporarily data there is no connection to the server.
5.3.1 data from devices while there is no connection to
storage Not pass: Platform on the Edge cannot temporarily store data from devices
the server.
while there is no connection to the server.
Pass: User is able to make schedule and control the devices based on this
Platform must have schedule feature for use to schedule.
5.3.2 Scheduler
control the connected device Not pass: User is not able to make schedule and control the devices based on
this schedule.
5.3.3 Rule engine Platform must provide a way to process simple Pass: User is able to create simple rules based on device's status, time and
rules based on at least device's status, time in process them via Platform on the Edge.
56
Not pass: User is not able to create simple rules based on device's status, time
order to control the device
ID Function Description or process them via Platform on the Edgecriteria
Evaluated
5.4 Modifiability
Pass: Supplier/bidder provide a method and support Viettel to add one new
connectivity standard to the gateway.
Accepted: The platform has the roadmap to support adding new connectivity
standard to the gateway free of charge within 06 months since the effective
Adding new date of the contract and will be tested before the FAC.
Platform must have a method to add new
5.4.1 connectivity Not pass: Does not meet any of these requirements:
standard - Supplier/bidder provide a method and support Viettel to add one new
- The platform has the roadmap to support adding new connectivity standard
to the gateway free of charge within 06 months since the effective date of the
5.5 Management
Pass: User is able to remotely update the software and firmware of the IoT
User can remotely update the software and gateway.
5.5.1 Remote update
firmware of the IoT gateway. Not pass: User is not able to remotely update the software and firmware of
the IoT gateway.
Pass: Administrator can monitor all the information (status, events,
User can monitor all the IoT gateway connecting
configuration information) of all the gateway that are connected to the IoT
to IoT Platform from an administrator interface.
Platform.
5.5.2 Monitoring Administrator should visually see all the
Not pass: Administrator cannot monitor all the information (status, events,
information, status, events, and configurations of
configuration information) of all the gateway that are connected to the IoT
the IoT gateway.
Platform.
Pass: User is able to remotely configure the IoT gateway.
5.5.3 Remotely configure User can remotely configure the IoT gateway.
Not pass: User is not able to remotely configure the IoT gateway.
5.5.4 Logging Platform must the ability to log every error, Pass: Administrator is able to view/read all the log of error, event, and action
event, action for administrator to remotely remotely.
57
Not pass: Administrator is not able to view/read all the log of error, event,
troubleshoot.
and action remotely.
Pass: Platform can run on all these OS:
- Window
- Linux
- Android
Accepted: Platform can run on Window and Linux or has the roadmap to
ID Function Description support all three kinds of OS:Evaluated criteria
Window, Linux, Android free of charge within
Platform must run on popular OS including but
5.5.5 OS support 06 months since the effective date of the contract and will be tested before the
not limited to: Window , Linux and Android
FAC.
- Platform can run on all these OS: Window, Linux, Android
- Platform can run on Window and Linux or has the roadmap to support all
three kinds of OS: Window, Linux, Android free of charge within 06 months
since the effective date of the contract and will be tested before the FAC..
Developer
6
environment
6.1 Developer Portal
Pass: Different users are able to develop separated IoT apps on the same
Different companies can develop separated IoT environment.
6.1.1 Multi-tenant
Applications on the same environment. Not pass: Different users are not able to develop separated IoT apps on the
same environment.
6.1.2 Company Platform must have the ability to create Pass: Can create multiple company's administrator account and this account
management administrator account for each company. This can manage the resources, developers/users, applications belong to this
account can manage the resources, applications, company.
developers of the company. Accepted: Has a roadmap to support this feature free of charge within 06
months since the effective date of the contract and will be tested before the
FAC.
Not pass: Cannot create multiple company's administrator account and this
account can manage the resources, users/developers, application belong to
58
this company.
Pass: Provide a Developer Portal in which, company's administrator is able to
Platform must have the ability to manage the
create different accounts for different developers and assigned roles,
ID Function developers in one company. The Developer
Description
Developer resources to these accounts. Evaluated criteria
6.1.3 Portal should be able to create different accounts
management Not pass: Does not provide a Developer Portal in which, company's
for different developers and each account has it
administrator is able to create different accounts for different developers and
owned assigned roles, resources.
assigned roles, resources and to these accounts.
Platform must have Developer Portal in which Pass: Provide a Developer Portal in which company's administrator is able to
Application user can manage the list of applications belong to manage the list of application belong to his company.
6.1.4
management one company, and can assign developers for each Not pass: Does not provide a Developer Portal in which, company's
application. administrator is able to manage the list of application belong to his company.
Pass: Provide a method/tools to assign data for each company, developer,
application. Each company, developer, application can only access to
assigned data.
Platform must have permission management
Permission Not pass: Does not meet one of these requirements:
6.1.5 mechanism so that company, developer,
management - Provide a method/tools to assign data for each company, developer,
application can only access to assigned data.
application.
- Each company, developer, application can
only access to assigned data.
Pass: User have two different environments to develop apps: development
Platform must have the ability to separate the environment and production environment and can migrate data between two
development environment and production environments.
Release
6.1.6 environment, and have method to migrate the Not pass: Does not meet one of these requirements:
management
data between development environment and - User have two different environments to develop apps: development
production environment. environment and production environment.
- Can migrate data between two environments.
6.2 Developer SDK
6.2.1 Developer SDK Platform must have Software Development Kit Pass:
(SDK) for developers to developed software on - User is able to develop software on devices using the platform's built-in
59
SDK (library, software agent)
- Supplier/bidder provide all the detail information of the SDK (library,
software agent)
devices. The SDK can have many form such as Not pass: Does not meet one of these requirements:
library, software agent. - User is able to develop software on devices using the platform's built-in
SDK (library, software agent)
- Supplier/bidder provide all the criteria of the SDK (library,
detail information
software agent)
Pass: Software developed using platform's built-in SDK (library, software
Platform's SDK must have the ability to run on
Compatible with agent) can run on Arduino and Rasberry Pi.
6.2.2 popular hardware kit including but not limited to
devices Not pass: Software developed using platform's built-in SDK (library,
Arduino, Rasberry Pi.
software agent) cannot run on Arduino and Rasberry Pi.
6.3 Billing
Pass:
- Platform can store billing information (number of requests, number of
devices).
- User can fetch the billing information for further use
Accepted: The platform has the roadmap to support storing the billing
information such as number of requests, number of devices for billing
purpose free of charge within 06 months since the effective date of the
Platform must have the ability to store the billing
6.3.1 Billing information information such as number of requests, number
of devices for billing purpose.
- Platform can store billing information (number of requests, number of
devices).
- User can fetch the billing information for further use.
- The platform has the roadmap to support storing the billing information such
as number of requests, number of devices for billing purpose free of charge
within 06 months since the effective date of the contract and will be tested
before the FAC.
Non Functional
60
requirement
1 Architecture
Pass: Platform can deploy into different deployment architectures:
- On-premise
- Public cloud
Platform must have the ability to deploy into
Deployment - Private cloud
1.1 flexible deployment architectures including on
Architecture Not pass: Platform cannot deploy into one of these deployment architectures:
premise, public cloud and private cloud.
- On-premise
- Public cloud
- Private cloud
Pass: Platform can deploy and run on VMWare and OpenStack or Kubernetes
Platform must support at least VMWare and
IaaS infrastructure or vendor’s own IaaS Platform
1.2 OpenStack or Kubernetes or vendor’s own IaaS
support Not pass: Platform cannot deploy and run on VMWare or OpenStack or
Platform
Kubernetes or vendor’s own IaaS Platform
2 Modifiability
White label interface allow user easily modify to Pass: User can embed Viettel brand image into the Platform
2.1 White label interface
embed Viettel brand image into the platform. Not pass: User cannot embed Viettel brand image into the Platform
2.2 Scripting User can use built-in script language to modify Pass: User can use built-in script language to modify data flows from outside
data flows from outside system to the platform system to the platform
Accepted: Have a method to modify data flows from outside system to the
platform using external script or has a roadmap to support modifying data
flows form outside system to the platform using built-in script free of charge
within 06 months since the effective date of the contract and will be tested
before the FAC.
-User can use scripting to modify data flows from outside system to the
platform
- Have a method to modify data flows from outside system to the platform
using external script or has a roadmap to support modifying data flows form
61
outside system to the platform using built-in script free of charge within 06
FAC.
ID Function Pass: User is able to fetch data (real-timecriteria

data and stored data) from system
Platform must haveDescription
APIs or other methods to get Evaluated
to external system using APIs or other method provided by supplier/bidder.
data (both real time data and stored data) from
2.3 Data access Not pass: User is not able to fetch data (real-time data and stored data) from
system to external system for further processing
system to external system using APIs or other method provided by
such as data analytic.
supplier/bidder.
Pass:
- Platform support multilingual (English)
Platform must support Multilingual (Vietnamese
2.4 Multilingual and English) and have method to add new
Not pass: Do not meet one of these requirements:
language into system.
- Platform support multilingual (English)
3 Integration
Platform must have the ability to integrate many Pass: User can program the adapter or using script language to integrate
kinds of devices by adding adapter to convert the device into the system.
3.1 Device Integration
data from the device, adapter should be added by Not pass: User cannot program the adapter or using script language to
programming or scripting language. integrate device into the system.
Platform must integrate with the CMP
(Connectivity Management Platform) that Viettel
Pass: User is able to get information of connectivity status, billing
paln to deploy using the APIs that is provied by
information, subscription information and send SMS to SIM using platform's
CMP side. APIs including but not limited to:
GUI.
- Get connectivity status
3.2 CMP Integration Not Pass: User is not able to get information of connectivity status, billing
- Get billing information
information, subscription information and send SMS to SIM using platform's
- Get subscription information.
GUI.
- Send SMS to the SIM.
Platform must provide a GUI for user to view
these information and send SMS to SIM.
62
Supplier/bidder must maintaince the integration
between the Platform and the CMP within the
technical support time (at least 3 years). In case
there is an intergration problem in the future that
Pass: Supplier/bidder commit about the requirement.
CMP Integration two sides (AEP and CMP) can not handle
3.3 Not Pass: Supplier/bidder does not commit about the requirement.
future commitment (Example: new CMP version with new standards
and APIs and AEP side can not integrate), Viettel
will provide the integration rules and two sides
have to follow these rules until succesful
integration.
Pass: The system can integrate Video management system or streaming
ID Function Description server and allow user to view Evaluated criteria
video on the dashboard.
Accepted: The Platform has a roadmap to support integrating Video
management system or streaming server and allow user to view video on the
dashboard free of charge within 06 months since the effective date of the
VMS integration Platform must have the ability to integrate Video contract and will be tested before the FAC.
3.4 (Video management management system or streaming server and Not pass: Does not meet any of these requirements:
System) allow user to view video on the dashboard. - The system can integrate Video management system or streaming server and
allow user to view video on the dashboard.
- The Platform has a roadmap to support integrating Video management
system or streaming server and allow user to view video on the dashboard
free of charge within 06 months since the effective date of the contract and
3.5 Other system Platform must have the ability to integrate with Pass: The system can integrate with integration framework which support
Integration integration frameworks which support REST API REST API and MQTT.
and MQTT Accepted: The system can integrate to integration framework which support
REST API or MQTT or has the roadmap to support integrating with
integration frameworks free of charge within 06 months since the effective
Not pass: Do not meet any of these requirements:
- The system can integrate with integration framework which support REST
63
API and MQTT.
- The system can integrate to integration framework which support REST API
or MQTT or has the roadmap to support integrating with integration
frameworks free of charge within criteria
06 months since the effective date of the
4 Operability
Pass: Administrator is able to deploy the topology of the system, add or
Administrator can deploy the topology of the
remove node easily via the built-in interface.
4.1 Auto deployment system, add or remove node easily via the
Not pass: Administrator is not able to deploy the topology of the system, add
platform's built-in interface.
or remove node easily via the built-in interface.
Pass: The system can automatically increase the capacity of the system when
the load increase.
Accepted: The Platform has the roadmap to support automatically increasing
the capacity of the system when the load increases free of charge within 06
FAC.
Platform can automatically increase the capacity
4.2 Auto scaling Not pass: Does not meet any of these requirements:
of the system when the load increases.
- The system can automatically increase the capacity of the system when the
load increase.
- The Platform has the roadmap to support automatically increasing the
capacity of the system when the load increases free of charge within 06
FAC.
Pass: User is able to update and turn off some nodes in the system without
Platform must have the ability to update or turn
affecting overall system.
4.3 Hot maintenance off some nodes in the system without affecting
Not pass: User is not able to update and turn off some nodes in the system
the overall system.
without affecting overall system.
5 Availability
5.1 Load balancing Every node in the system has load balancing Pass: Platform on Cloud support load balancing feature in every node.
64
feature so that the load can be share to many Not pass: Platform on Cloud does not support load balancing feature in
other nodes. every node.
ID Function Every node in the system has back up

Description Pass: Platform on Cloud support back upcriteria
Evaluated mechanism (active standby, active
mechanism (active standby or active active), so active) on every nodes in the system.
5.2 Back up
that if one node goes down, the system still runs Not pass: Platform on Cloud does not support back up mechanism (active
smoothly. standby, active active) on every nodes in the system.
6 Capacity
Pass: Platform on Cloud support scale out to increase the capacity of each
Every node in the system can increase the node
6.1 Scale out
capacity such as storage by adding more servers. Not pass: Platform on Cloud does not support scale out to increase the
capacity of each node
Pass: Platform on Cloud support scale out to increase the device numbers in
Can add more devices by scaling out the system each node
6.2 Device capacity
(adding more servers). Not pass: Platform on Cloud does not support scale out to increase the device
numbers in each node
7 Monitoring
Pass: Administrator is able to monitor all the nodes (web server, database
Administrator can visually monitor overall of the
server, proxy) in the system, configurations of nodes and relationship among
system including all the nodes (including but not
Topology nodes via platform's GUI
7.1 limited to web server, database, and proxy),
monitoring Not pass: Administrator is not able to monitor all the nodes (web server,
configurations of the nodes and relationship
database server, proxy) in the system, configurations of nodes and
between nodes.
relationship among nodes via platform's GUI.
Pass:
Platform must have the ability to log every
7.2 Logging errors, user actions, system actions for trouble
Not pass: Does not meet one of these requirement:
shooting purpose later.
7.3 Server monitoring Platform must have interface to view all the Pass: User is able to view/read the information (load, status, errors) of all
65
server in the system via platform's GUI and has tool to troubleshoot errors
server in the system with information such as
Not pass: User is not able to view/read the information (load, status, errors)
load, status, errors and has tools to troubleshoot
of all server in the system via platform's GUI or does not has tool to
when errors happen.
troubleshoot errors
Pass: User is able view/read load and status of each node in the system via
Platform must have interface to view load and platform's GUI
7.4 Node monitoring
status of all nodes in the system. Not pass: User is not able view/read load and status of each node in the
system via platform's GUI
Pass:
- Platform support mail and SMS notification
Platform must support mail and SMS notification - User is able to define abnormal events and configure who can receive
when abnormal events in the system happen. notifications.
7.5 Notification
User can easily define abnormal events and Not pass: Does not meet one of these requirements:
configure who can receive notification. - Platform support mail and SMS notification
- User is able to define abnormal events and configure who can receive
notifications.
8 Security
Pass: Meets these requirements:
- Platform has security mechanism to protect the connection between device
and Cloud, device and gateway, gateway.
Platform must have security mechanism to
- Supplier/bidder provide all the detail information about the security
protect the connection between device and
Connectivity mechanism
8.1 Cloud, device and gateway, gateway and Cloud,
security Not pass: Does not meet one of these requirements:
make sure that the data is consistent, cannot be
- Platform has security mechanism to protect the connection between device
modified or eavesdrop by unauthorized person.
and Cloud, device and gateway, gateway.
mechanism
8.2 Cloud security Platform must have security mechanism to Pass: Meets these requirements:
protect the data on Cloud - Platform has security mechanism to protect data on Cloud.
66
mechanism.
Not Pass: Does not meet one of these requirements:
- Platform has security mechanism to protect data on Cloud.
mechanism
- Platform has security mechanism criteria
to protect the data on IoT gateway.
Platform must have security mechanism to mechanism.
8.3 Edge security
protect the data on IoT gateway. Not Pass: Does not meet one of these requirements:
- Platform has security mechanism to protect the data on IoT gateway.
mechanism.
9 Performance
- The system can handle the throughput of message coming from the devices
The system can handle the throughput of to the cloud at least 2500 messages per second
message coming from the devices to the cloud at - The system can increase the throughput by adding more server.
9.1 Throughput
least 2500 messages per second, and can increase Not pass: Does not meet one of these requirements:
the throughput by adding more server. - The system can handle the throughput of message coming from the devices
to the cloud at least 2500 messages per second
- The system can increase the throughput by adding more server.
9.2 System load -System load of servers and other network Pass: System load of servers and other network devices of the system when
devices of the system when running with running with throughput 2500 messages per second (messages coming from
throughput 2500 messages per second (messages the devices to the cloud) must meet the following criteria:
coming from the devices to the cloud) must meet +Server: CPU ≤ 75%, RAM ≤ 90%.
the following criteria: +Device for storing data: IOPS ≤ 80%, hard disk space usage ≤80%
+Server: CPU ≤ 75%, RAM ≤ 90%. +Network device: Number of ports used and device throughput ≤80%.
+Device for storing data: IOPS ≤ 80%, hard disk In case equipment is deployed active-active redundancy model, even if one of
space usage ≤80% the equipment is faulty and stop operation, the remaining equipment must
67
meet the system load parameters as above.
Not pass: System load of servers and other network devices of the system
+Network device: Number of ports used and
when running with throughput 2500 messages per second (messages coming
device throughput ≤80%.
from the devices to the cloud) does not meet the following criteria:
In case equipment is deployed active-active
+Server: CPU ≤ 75%, RAM ≤ 90%.
redundancy model, even if one of the equipment
+Device for storing data: IOPS ≤ 80%, hard disk space usage ≤80%
ID Function is faulty and stop operation, the remaining
Description +Network device: Number ofEvaluated
ports used criteria
and device throughput ≤80%.
equipment must meet the system load parameters
In case equipment is deployed active-active redundancy model, even if one of
as above.
the equipment is faulty and stop operation, the remaining equipment does not
meet the system load parameters as above.
General
10
requirement
Pass: Viettel is able to expanse the platform supporting to install at least 22
Viettel can expanse the platform supporting to instances of platform at different data centers including Viettel's data centers
install at least 22 instances of platform at or data center of Viettel's customer.
10.1 License model
different data centers including Viettel’s data Not pass: Viettel is not able to expanse the platform supporting to install at
centers or data center of Viettel's customer. least 22 instances of platform at different data centers including Viettel's data
centers or data center of Viettel's customer.
Pass: The platform is operated by Viettel
10.2 Operation model Platform must be operated by Viettel.
Not pass: The platform is operated by supplier/bidder
Pass: The platform is used under Viettel brand name
10.3 Brand name Platform must be used under Viettel Brand name.
Not pass: The platform is not used under Viettel brand name
Pass: Platform support NB-IoT, eMTC, LoRa Connectivity standards
Not pass: Platform does not support one of these Connectivity standards:
Connectivity Platform must support NB-IoT, eMTC, LoRa
10.4 - NB-IoT
Standard Connectivity standards
- eMTC
- LoRa
68
III. Minimum hardware requirement (apply for both CMP’s hardware and AEP’s hardware)
ID Function Description Evaluation criteria
General
I
requirement
Pass: Hardware warranty duration ≥ 03 years.
1 Hardware warranty ≥ 3 years
Not pass: Hardware warranty duration < 03 years.
Include full accessories to deploy in the Pass: Include full accessories to deploy in the Viettel’s data center.
2 Accessories
Viettel’s data center Not pass: Not include full accessories to deploy in the Viettel’s data center.
Pass: All hardware and software can successfully run IPv4-related operations and/or
All hardware and software support IPv6-related operations
3 Support Ipv6
concurrent Ipv4 and Ipv6 Not pass: Any hardware or software does not support IPv4-related operations or
IPv6-related operations
All applications, databases, storage, Pass: All applications, databases, storage, networking, power supply can be deployed
networking, power supply have to be in HA model (active – active or active – standby)
4 HA
deployed in HA model (active – active or Not pass: Any of applications or databases or storage or networking or power supply
active – standby) failed to be deployed in HA model (active – active or active – standby)
II Physical server
Number of CPU sockets per server ≥ 02 Pass: The number of CPU Intel Scalable or newer version ≥ 2
1 CPU
CPU Intel Scalable or newer version Not pass: The number of CPU Intel Scalable or newer version < 2
Memory type: DDR4 Pass: RAM type is DDR4
Not Pass: RAM type is not DDR4
Memory bus ≥ 2666 MT/s Pass: Memory bus speed ≥ 2666 MT/s.
2 RAM Not pass: Memory bus speed < 2666 MT/s.
Memory protection: ECC/Advanced Pass: Memory protection mechanism using ECC/Advanced ECC
ECC Not pass: Memory protection mechanism does not support ECC/ Advanced ECC
3 Card NIC Speed per port ≥ 10Gbps Pass: Speed per port ≥ 10Gbps
69
Not pass: Speed per port < 10Gbps
Number of ports ≥ 2 Pass: Number of ports ≥ 2 ports
Not pass: Number of ports < 2 ports
Number of cards ≥ 2 Pass: Number of cards ≥ 2 cards
Not pass: Number of cards < 2 cards
Number of cards ≥ 2 Pass: Number of cards ≥ 2 cards
Not pass: Number of cards < 2 cards
4 Card HBA (if any) Port speed ≥ 16 Gbps, Fibre Channel, Pass: Speed per port ≥ 16Gbps and support Fibre Channel, Auto-sensing
Auto-sensing Not pass: Speed per port < 16Gbps or not support Fibre Channel or Auto-sensing
Pass: RAID controller support RAID (0, 1, 5)
5 RAID controller RAID (0, 1, 5): supported
Not pass: RAID controller does not support RAID (0, 1, 5)
Support the below operating system (OS) Pass: Support the installation of all below operating system (OS) or equivalent:
or equivalent: + Windows server 2012/2016
Operating System + Windows server 2012/2016 + RedHat Enterprise Linux ≥ 6.9
6
(OS) + RedHat Enterprise Linux ≥ 6.9 + VMWare vSphere ≥ 6.0
+ VMWare vSphere ≥ 6.0 + KVM (Kernel Base Virtual Machine)
+ KVM (Kernel Base Virtual Machine) Not pass: Does not support the installation of any above OSs.
Supporting remote managing hardware Pass: Support to remote manage hardware via Web/console interface
via Web/console interface Not pass: Does not support to remote manage hardware via Web/console interface
Supporting remote installation and Pass: Support remote installation and configuration.
configuration Not pass: Does not support remote installation and configuration.
7 Administration
Supporting troubleshoot via logs, and Pass: Supporting troubleshoot via logs, and capture logs.
capture logs Not pass: Does not support troubleshoot via logs, and capture logs.
Pass: Supporting SNMP protocol (v2c, v3)
Supporting SNMP protocol (v2c, v3)
Not pass: Does not support SNMP protocol (v2c, v3)
8 Firmware Using the latest version by manufacturer Pass: The firmware using the latest version by manufacturer
70
Not pass: The firmware is updated with the latest version by manufacturer
Switching
III
Equipment
Pass: The switch support Rack 19” (inch).
1 Rack mount Support Rack 19” (inch)
Not pass: The switch does not support Rack 19” (inch).
Number of interfaces for management Pass: The number of interfaces for management includes at least 01 x serial (console)
Management includes at least ≥1 x serial (console) RJ- RJ-45, 01 x management (Gigabit LAN) RJ-45 and 01 x USB.
2
interfaces 45, 1 x management (Gigabit LAN) RJ- Not pass: The number of interfaces for management does not include at least 01 x
45 and 1 x USB serial (console) RJ-45, 01 x management (Gigabit LAN) RJ-45 and 01 x USB.
Jumbo Frame Pass: Support MTU size ≥ 9000 bytes.
3 Support MTU size ≥ 9000 bytes
Support Not pass: The maximum MTU size < 9000 bytes.
Pass: The switch support Layer 2, Layer 3 operation.
4 Operating mode Support Layer 2, Layer 3 operation
Not pass: The switch does not support Layer 2, Layer 3 operation.
Pass: The number of supporting VLAN ≥ 2000.
Number of supporting VLAN ≥ 2000
Not pass: The number of supporting VLAN < 2000.
Pass: Support Spanning Tree Protocol.
Support loop-free protocol
Not pass: Does not support Spanning Tree Protocol.
5 L2 function Pass: Support LACP, Cross stack ether-channel or equivalent.
Support LACP, Cross stack ether-
Not pass: Does not support one of protocols include LACP, Cross stack ether-
channel or equivalent
channel.
Pass: Support Port mirroring
Support Port mirroring
Not pass: Does not support Port mirroring
6 L3 function (apply Support RIP V2, OSPF, Static route Pass: Support RIP V2, OSPF, Static route.
for core switch (if Not pass: Does not support any of RIP V2, OSPF, Static route.
71
any), distribute
switch (if any), not Pass: Support VRRP or equivalent.
Support VRRP or equivalent
for management Not pass: Does not support VRRP or any equivalent protocol.
switch (if any))
Pass: Support Access control list (ACL) based on Layer 2, 3, 4 information
Support Access control list (ACL) Not pass: Does not support Access control list (ACL) based on Layer 2, 3, 4
information
7 Security Pass: Support Storm control or equivalent protocol.
Support Storm control
Not pass: Does not support Storm control or any equivalent protocol.
Support Control plane protection or Pass: Support Control plane protection or equivalent.
equivalent Not pass: Does not support Control plane protection or any equivalent protocol.
Pass: Support CLI.
Support CLI
Not pass: Does not support CLI.
Management Pass: Support Telnet, SSH, console.
8 Support telnet, SSH, console
protocols Not pass: Does not support Telnet, SSH, console.
Pass: Support SNMP v2c, v3, NTP
Support SNMP v2c, v3, NTP
Not pass: Does not support one of these protocol: SNMP v2c, v3, NTP
Support 02 power supply using power Pass: Support 02 power supply using power cable based on standard C13/C14,
cable based on standard C13/C14, include 2 for spare parts
include 2 for spare parts Not pass: The number of power supply and power cable less than 02.
Pass: Support Voltage range from 200-240VAC/50-60Hz
Voltage: 200-240VAC/50-60Hz
9 Power supply Not pass: Does not support Voltage range from 200-240VAC/50-60Hz
Pass: The equipment support standby mode for power supply: N+N (N ≥ 1),
swappable
Standby N+1 (N ≥ 1)
Not pass: The equipment does not support standby mode for power supply: N+N (N
≥ 1) or not swappable
IV Storage
72
Pass: The switch support Rack 19” (inch).
1 Storage Form Standard Rack 19 "(inch)
Not pass: The switch does not support Rack 19” (inch).
These components must be hot-
swappable and hot-pluggable, the actions
Pass: All the components (Disk drive, Cooling system, Power module, Storage
of hot-plugging and hot-swapping must
controller) are hot-swappable and hot-pluggable without the interruption of the
not interrupt the read/write operations
read/write operations between the hosts and the volumes in the storage, and must not
Hot-swappable and between the hosts and the volumes in the
degrade the storage performance.
2 hot-pluggable storage, and must not degrade the storage
Not pass: Any of the components (Disk drive, Cooling system, Power module,
capabilities performance:
Storage controller) are not hot-swappable and hot-pluggable without the interruption
- Disk drive (all types)
of the read/write operations between the hosts and the volumes in the storage, and
- Cooling system
must not degrade the storage performance.
- Power supply system
- Storage controller
The upgrading firmware process of the Pass: The upgrading firmware process of the storage must not interrupt read/write
Online firmware storage must not interrupt read/write operations between the hosts and the volumes in the storage
3
upgrade operation operations between the hosts and the Not pass: The upgrading firmware process of the storage interrupt read/write
volumes in the storage operations between the hosts and the volumes in the storage
Management Number of management interfaces Pass: The number of management interfaces (100/1000Base-T) ≥ 02 port.
4
interfaces (100/1000Base-T) ≥ 02 port Not pass: The number of management interfaces (100/1000Base-T) < 02 port.
Management Pass: Support management via Web-based GUI, CLI.
5 Web-based GUI, CLI
Interface Not pass: Does not support management via Web-based GUI, CLI.
Battery-backed cache to disk de-stage or Pass: Support Battery-backed cache to disk de-stage or equivalent.
6 Cache redundancy
equivalent. Not pass: Does not support Battery-backed cache to disk de-stage or equivalent.
Support mix all Support for hard drives plug types, Pass: Support for hard drives plug types, different capacity.
7
kinds of hard disk different capacity Not pass: Does not support for hard drives plug types, different capacity.
8 The ability to Allow upgrades to expand capacity by Pass: Support upgrading expand capacity by adding more drives or expand tray when
upgrade hardware adding more drives or expand tray when the equipment is running.
73
when the device is Not pass: Does not allow upgrades to expand capacity by adding more drives or
the device is running
active expand tray when the device is running.
Support 02 power supply using power Pass: Support 02 power supply using power cable based on standard C13/C14,
cable based on standard C13/C14, include 2 for spare parts
include 2 for spare parts Not pass: The number of power supply and power cable less than 02.
Pass: The equipment support standby mode for power supply: N+N (N ≥ 1),
Power supply
9 Supports N + N redundancy and hot- swappable
module
swappable Not pass: The equipment does not support standby mode for power supply: N+N (N
≥ 1) or not swappable
Operating input voltage: 200-240VAC / Pass: Support Voltage range from 200-240VAC/50-60Hz
50-60Hz. Not pass: Does not support Voltage range from 200-240VAC/50-60Hz
IV.1 Controller
Pass: The number of Controller ≥ 2
Quantity ≥ 2
Not pass: The number of Controller < 2
1 All Controller operation in Mesh-Active Pass: All Controller operation in Mesh-Active or Active-Active architecture which
Controller
or Active-Active architecture which allows each LUN in System to be active on every controller in the system.
allows each LUN in System to be active Not pass: Controllers does not support any operation of Mesh-Active or Active-
on every controller in the system Active architecture
Pass: RAID controller support RAID (1/5/6/10)
2 Support RAIDs 1/5/6/10 or equivalent
Not pass: RAID controller does not support RAID (1/5/6/10)
IV.2 Disk
Pass: Support form factor of 2.5’’ or 3.5" or SSD or Flash module
1 Form factor 2.5’’ or 3.5" or SSD or Flash module
Not pass: Does not support any form factor of 2.5’’ or 3.5" or SSD or Flash module
Pass: Support SAS 6/12 Gbps interfaces
2 Interface SAS 6/12 Gbps
Not pass: Does not support SAS 6/12 Gbps interfaces
3 Speed (apply for ≥10000 rpm Pass: Disk speed ≥10000 rpm
74
HDD, not for SSD) Not pass: Disk speed < 10000 rpm
Pass: Support the Hot spare of at least 01 disk per each tray/enclosure
4 Hot spare At least 01 disk per each tray/enclosure
Not pass: Does not support the Hot spare of at least 01 disk per each tray/enclosure
Feature allows
There are features that allow hot- Pass: Support hot-swappable of hard drives
5 replacement of hot
swappable hard drives Not pass: Does not support hot-swappable of hard drives
hard drive
IV.3 Software
Pass: Support Volume Copy feature (or equivalent), with a detailed description of
Volume Copy feature (or equivalent),
features of the system Volume Copy.
with a detailed description of features of
Not pass: Does not support Volume Copy feature (or equivalent), with a detailed
the system Volume Copy
description of features of the system Volume Copy.
1 Backup feature
Pass: Support Snapshot feature (or equivalent), with a detailed description of the
Snapshot feature (or equivalent), with a
system snapshot feature.
detailed description of the system
Not pass: Does not support Snapshot feature (or equivalent), with a detailed
snapshot feature
description of the system snapshot feature.
Thin Provisioning Thin Provisioning feature to optimize the Pass: Support Thin Provisioning feature to optimize the use of space.
2
feature use of space Not pass: Does not support Thin Provisioning feature to optimize the use of space.
Pass: Support management features, monitor and generate reports for information
Management features, monitor and
about IOPS, bandwidth for the components of the storage system (LUN/RAIDgroup/
generate reports for information about
Feature performance Controller).
3 IOPS, bandwidth for the components of
monitoring system Not pass: Does not support one of the functions of management features, monitor and
the storage system
generate reports for information about IOPS, bandwidth for the components of the
(LUN/Raidgroup/Controller).
storage system (LUN/RAIDgroup/ Controller).
4 Supported operating Supported operating systems on servers Pass: Support operating systems on servers connected as: IBM AIX, Oracle Linux,
systems on a server connected as: IBM AIX, Oracle Linux, RedHat Enterprise Linux, SUSE Linux Enterprise Server, Microsoft Windows,Oracle
connected RedHat Enterprise Linux, SUSE Linux Solaris, VMWare ESX / ESXi, Xen Server, the operating system supports KVM
Enterprise Server, Microsoft (Kernel-based Virtual Machine).
75
Windows,Oracle Solaris, VMWare Not pass: Does not one of operating systems on servers connected as: IBM AIX,
ESX / ESXi, Xen Server, the operating Oracle Linux, RedHat Enterprise Linux, SUSE Linux Enterprise Server, Microsoft
system supports KVM (Kernel-based Windows,Oracle Solaris, VMWare ESX / ESXi, Xen Server, the operating system
Virtual Machine). supports KVM (Kernel-based Virtual Machine).
5 Warranty Support ≥ 3 year.
IV.4 SAN Switch
Number of SAN Pass: The number of provided SAN switch ≥ 2.
1 ≥ 2 SAN switch (to deploy HA mode).
Switch Not pass: The number of provided SAN switch < 2.
Pass: The number of activated ports supported ≥ 48.
2 Number of ports Number of activated ports ≥ 48 ports
Not pass: The number of activated ports supported < 48.
Pass: The number of provided SFP (included with ports) enough to deploy the
required connection for SAN Switch.
3 SFP (included) Enough to deploy
Not pass: The number of provided SFP (included with ports) is not enough to deploy
the required connection for SAN Switch.
Have Zoning, VSAN or equivalent Pass: The SAN switch support Zoning, VSAN or equivalent feature
4 Zoning feature
feature Not pass: The SAN switch does not support Zoning, VSAN or any equivalent feature
ISL Trunking Pass: The number of provided SAN switch ≥ 2.
5 Have License ISL, ISL Trunking
feature
Access gateway Have access gateway mode (license Pass: The number of provided SAN switch ≥ 2.
6
mode attached)
Management Pass: CLI (SSH) and GUI.
7 CLI (SSH) and GUI
interface Not pass: Does not support CLI (SSH) or GUI.
8 Power supply Have 02 power supply using power cable Pass: Support 02 power supply using power cable based on standard C13/C14,
module based on standard C13/C14, include 2 include 2 for spare parts
for spare parts Not pass: The number of power supply and power cable less than 02.
76
Pass: The equipment support standby mode for power supply: N+M (N, M ≥ 1),
Supports N + M redundancy and hot- swappable
swappable Not pass: The equipment does not support standby mode for power supply: N+M (N,
M ≥ 1) or not swappable
Operating input voltage: 200-240VAC / Pass: Support Voltage range from 200-240VAC/50-60Hz
50-60Hz. Not pass: Does not support Voltage range from 200-240VAC/50-60Hz
9 Warranty Support ≥ 3 year
Item 3. Pre - Acceptance Test

I. Pre - Acceptance Test for Connectivity Management Platform (CMP)
ID Function Detailed technical requirements Measurement method

I Connectivity Options
1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account and
installed platform.
2. Test procedure:
- Step 1: Log into the platform (web-based portal or mobile app) with the provided
account.
The platform must enable the following
- Step 2: Direct to the device management section or designated domain that can create
Connectivity types of network connectivity includes at
1 the device
Options least WiFi, Cellular-2G/3G/4G and LPWA
- Step 3: Create NB-IoT device using device template and verify that the device and send
(NB-IoT)
and receive messages.
Repeat step 1 to 3 for other connection technology including WiFi, Cellular 2G/3G/4G
and record the results.
3. Assessment: Pass if the Platform can create devices successfully and devices can send
and receive messages correctly.
2 Connectivity The platform must support the LTE-M 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account and
77
installed platform.
2. Test procedure:
account.
- Step 2: Direct to the device management section or designated domain that can create
the device
Options network connectivity
- Step 3: Create LTE-M device using device template and verify that the device and send
and receive messages.
3. Assessment: Pass if the Platform can create devices successfully and devices can send
and receive messages correctly. Accepted if the platform has the roadmap to support LTE-
M network connectivity free of charge within 06 months since the effective date of the
contract.
II Order Provisioning Management
1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
installed platform.
2. Test procedure:
account.
The platform must support order placing,
Order - Step 2: Direct to the Order provisioning section or designated domain that can provide
1 processing and provisioning
Provisioning Order provisiong.
- Step 3: Make the appropriate selection from the drop-down menu; enter the field with
the information about device (ICCID,…), service type, rate plan, application.
- Step 4: Activate the provision.
3. Assessment: Pass if the Platform can active the Devices in the system and start billing
period, and devices can send and receive messages correctly.
1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account and
The typical time (within the platform)
Order installed platform.
2 between placing the order and the asset
Provisioning 2. Test procedure:
being connected should be less than 5s
78
account.
- Step 2: Direct to the Dashboard/Report section or designated domain that can provide
statistics.
- Step 3: Query the delay or time consume for order placing and export the results and
have the average number of typical time.
3. Assessment: Pass if the statistics or performance counters from the Platform show that
the typical time (within the platform) between placing the order and the asset being
connected should be less than 5s for at least 99% of times. In case the platform does not
support to show by counters or statistics, the test will be carried out by manual test for at
least 100 times.
1. Pre-set Condition: Proposal documents provided by supplier/bidder about integration
solution, technical document about Viettel’s BSS system (BCCS 2.0, Billing, OCS).
2. Test procedure:
- Step 1: Supplier lists all requirements for integration.
The platform must support integration with - Step 2: Viettel prepare the systems to support for integration (API, interfaces and
Order
3 the current Viettel’s Order/Management standards, IP connection, firewall).
Provisioning
systems (Viettel BSS) - Step 3: Supplier do the customization and modification as needed for the integration of
CMP with Viettel’s BSS.
3. Assessment: Pass if the CMP is integrated successfully with Viettel’s BSS.
Accepted if the CMP is integrated successfully with Viettel’s BSS within 6 months since
the effective date of the contract.
4 Order The platform must support to manage the 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management connected estate via a portal installed platform.
2. Test procedure:
account.
- Step 2: Direct to the Order Management section or designated domain that can manage
79
the connected status of device.
- Step 3: Query the device connected status.
- Step 4: Edit, change the connected status of the device.
3. Assessment: Pass if the Platform show that the connected status of the device was
changed accordingly.
installed platform.
The platform must support to access via a 2. Test procedure:
Order web browser (http, https) without any - Step 1: Log into the platform (web-based portal or mobile app) with the provided
5
Management hardware restriction (desktop, laptop, account.
tablet, mobile device) - Step 2: Direct to the Order Management section or designated domain.
Repeat above step for each type of hardware (desktop, laptop, tablet, mobile device)
3. Assessment: Pass if the Platform support to access via any types of device.
installed platform.
2. Test procedure:
account.
The platform must support to change - Step 2: Direct to the Order Management section or designated domain support to change
Order
6 existing subscriptions, activate SIM existing subscriptions.
Management
/deactive SIM via API or Web portal - Step 3: Search a SIM by numeric input then select to view details.
- Step 4: Try to change the value of activation/deactivation field.
- Step 5: Save the change and quit.
- Step 6: Login and search that SIM again and verify the status of subscriptions.
Repeat above step for API or Web portal.
3. Assessment: Pass if the Platform support to change the SIM subscription successfully.
III Subscription Management
80
installed platform.
2. Test procedure:
account.
The platform must support to manage - Step 2: Direct to the Subscription Management section or designated domain support
Subscription
1 subscriptions, to add connections, and to to manage subscriptions.
Management
change data plans - Step 3: Search a subscriber by text/numeric input then select to view details.
- Step 4: Select drop-down menu to add more connection.
- Step 5: Select drop-down menu to change data plan for group of connections.
- Step 6: Login and search that subscriber again and verify the status of subscriptions.
3. Assessment: Pass if the Platform support to change data plan and add more
connections.
installed platform.
2. Test procedure:
- Step 1: The supplier provide the dimension and design document to show that the
The platform must support to manage up to system can support 180.000 subscribers on the same instance.
2 Scalability
180.000 subscribers on the same instance
- Step 2: The supplier support to load a temporary 180.000 subscriber license.
- Step 3: The supplier support to load 180.000 virtual IoT devices into the platform
3. Assessment: Pass if the Platform working normally in term of function and
performance aspects.
3 Provisioning and The platform must support OTA 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Activation subscription provisioning including OTA installed platform.
eSIM provisioning (eSIM Profile 2. Test procedure:
Download, Enable, Change, Delete) - Step 1: Log into the platform (web-based portal or mobile app) with the provided
account.
- Step 2: Direct to the Subscription Management section or designated domain support to
81
manage OTA eSIM subscription provisioning.
- Step 3: Search a subscriber by text/numeric input then select to view details.
- Step 4: Select drop-down menu to select eSIM Profile Download/ Enable/ Change/
Delete.
- Step 5: Reset the device with eSIM.
3. Assessment: Pass if the Platform support to Download/Enable/ Change/ Delete
subscription using eSIM.
installed platform.
2. Test procedure:
account.
Provisioning and The platform must support also eSIM, manage SIM profile.
4
Activation multi IMSI SIM profile - Step 3: Search a eSIM subscriber by text/numeric input then select to view details.
- Step 4: Select drop-down menu to change Subscription.
- Step 5: Reset the device with SIM.
Repeat the above steps for Multi SIM subscriber
3. Assessment: Pass if the Platform support to change subscription of eSIM or Multi
IMSI profile
5 Provisioning and The platform must support Subscription 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Activation Activate, Deactivate, Pause and Terminate installed platform.
2. Test procedure:
account.
- Step 2: Direct to the Subscription Management section or designated domain support
82
to manage subscriptions.
- Step 3: Search a subscriber by text/numeric input then select to view details.
- Step 4: Select drop-down menu to change Subscription status (Activate, Deactivate,
Pause and Terminate)
3. Assessment: Pass if the Platform support to change Subscription status (Activate,
Deactivate, Pause and Terminate).
installed platform.
2. Test procedure:
account.
The platform must support to use - Step 2: Direct to the Subscription Management section or designated domain support
Provisioning and
6 “Automation Rule” to change SIM status to use “Automation Rule” to change SIM status through predefined conditions.
Activation
through predefined conditions - Step 3: Search a subscriber by text/numeric input then select to view details.
- Step 4: Select drop-down menu to apply “Automation Rule” to change SIM status
through predefined conditions (for example, Active the SIM when the Device is sold
out).
3. Assessment: Pass if the Platform support to change Subscription status to Active.
7 Provisioning and The platform must support SIM order 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Activation management in bulk with appropriate price installed platform.
plan 2. Test procedure:
account.
SIM order management in bulk with appropriate price plan.
- Step 3: Select drop-down menu to upload a file with multiple SIM information.
83
- Step 5: Select drop-down menu to choose appropriate price plan for group of SIMs.
3. Assessment: Pass if the Platform support to change price plan and activate SIM order
in bulk.
installed platform.
2. Test procedure:
account.
The platform must support to change SIM - Step 2: Direct to the Subscription Management section or designated domain support to
Provisioning and change SIM status.
8 status via WebGUI/ API individually or
Activation - Step 3: Select drop-down menu to upload a file with multiple SIM information.
collectively
- Step 4: Select drop-down menu to change SIM status between Active/Deactive.
Repeat above step for WebGUI and API.
3. Assessment: Pass if the Platform support to change SIM status individually (without
step 3) or collectively (in bulk).
9 Provisioning and The platform must support changing 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Activation Physical SIM card on Device installed platform.
2. Test procedure:
account.
change SIM card.
- Step 3: Find the number whose SIM need to be changed.
- Step 4: In the menu, enter the information of the new SIM card or get information from
the Device.
- Step 5: Login and search that subscriber again and verify the information of the
84
associated SIM card.
3. Assessment: Pass if the Platform support to change Physical SIM associated with the
subscriber.
installed platform.
2. Test procedure:
account.
The platform must enable automatic SIM - Step 2: Direct to the Subscription Management section or designated domain support to
Provisioning and view Device and SIM status.
10 activation only when the device is powered
Activation
on for the first time - Step 3: Search for device detail information, for Device which was not sold and still in
the store, the status should be Inactive.
- Step 4: Power on the device for the 1st time.
- Step 4: The Device status should have SIM change to activation status.
3. Assessment: Pass if the Platform support to change SIM status to Activation when the
device is powered on for the first time.
installed platform, a device with SIM is in distribution channel (deactivated).
2. Test procedure:
account.
The platform must support a non-billable
Provisioning and - Step 2: Direct to the Subscription Management section or designated domain support to
11 state for the SIM while device is in
Activation view Device and SIM status.
distribution channel
- Step 3: Search for device detail information, for Device which was not sold and still in
the store, the status should be Inactive or flagged as non-billable. Even though this device
may pass data, it will not be charged for that data usage
3. Assessment: Pass if the Platform support a non-billable state for the SIM while device
is in distribution channel.
85
installed platform.
2. Test procedure:
The platform must support to enable account.
Provisioning and instant state changes to the SIM, including - Step 2: Direct to the Subscription Management section or designated domain support to
13 change SIM status.
Activation moving from Activated to Deactivated
individually or in bulk. - Step 3: Select drop-down menu to upload a file with multiple SIM information.
- Step 4: Select drop-down menu to change SIM status between Active/Deactive.
3. Assessment: Pass if the Platform support to enable instant state changes to the SIM
(within 5s) individually (without step 3) or collectively (in bulk).
installed platform.
2. Test procedure:
customer account.
Provisioning and The platform must support different - Step 2: Direct to the Subscription Management section or designated domain support to
14 change customer account state (Active, Deactivate/ Locked).
Activation transition states per Customer account
- Step 3: Select drop-down menu to choose state of customer account.
- Step 5: Login and search that customer again and verify the status of customer
account.
3. Assessment: Pass if the Platform support different transition states per Customer
account.
15 Provisioning and The platform must provide measures to 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Activation detect removal of SIM from one device to installed platform.
another and take preventive measures to 2. Test procedure:
prevent fraud and abuse. - Step 1: Log into the platform (web-based portal or mobile app) with the provided
86
account.
view Device and SIM status.
- Step 3: Search for a device detail information, with normal state.
- Step 4: Remove the SIM from that Device.
- Step 5: The Device status should have alarm (IMEI change) to inform that Device is
removed and ask user for preventive measures to prevent fraud and abuse including
deactivate the SIM or accept the removal of the SIM to another device.
3. Assessment: Pass if the Platform support to detect removal of SIM and recommend for
appropriate actions.
installed platform.
2. Test procedure:
The platform must support different account.
Provisioning and provisioning rules and transition states per - Step 2: Direct to the Subscription Management section or designated domain support to
16 view rules and transition states.
Activation roam zone within a single Customer
account - Step 3: Let the device enters a roaming zone with difference rates and plans.
- Step 4: The platform will ask for the new applied rule includes changing to less
expensive rate plan to reduce the roaming cost.
3. Assessment: Pass if the Platform support different provisioning rules and transition
states per roam zone within a single Customer account.
17 Provisioning and The platform must support to change MNO 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Activation service provider of eSIM at least between installed platform.
Viettel and their subsidiaries (in Vietnam, 2. Test procedure:
Laos, Cambodia, Myanmar, Timor Leste, - Step 1: Log into the platform (web-based portal or mobile app) with the provided
Haiti, Peru, Tanzania, Burundi, Cameroon, account.
Mozambique) - Step 2: Direct to the Subscription Management section or designated domain support to
87
view eSIM status.
- Step 3: Let the device enters a roaming zone between Viettel and subsidiaries in
overseas.
- Step 4: Go to remote eSIM provisioning section.
- Step 4: Change the eSIM profile of Viettel to other eSIM profile by Viettel’s oversea
mobile networks.
3. Assessment: Pass if the Platform support to change MNO service provider of eSIM.
installed platform.
2. Test procedure:
The platform must enable the ability to account.
Provisioning and manage SIMs that have been transferred to - Step 2: Direct to the Subscription Management section or designated domain support to
18
Activation other operators' networks from a single manage transferred SIMs.
point of access.
- Step 3: Query the list of transferred SIMs.
- Step 4: Take manage action (Active, Deactive, Swap SIMs).
3. Assessment: Pass if the Platform support to manage transferred SIMs (Active,
Deactive, Swap SIMs).
19 Subscriptions The platform must support Pausing/ 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management Resuming service installed platform.
2. Test procedure:
account.
control service plan.
- Step 3: Select drop-down menu to service plan.
- Step 5: Select drop-down menu to Pausing service and vice versa.
88
3. Assessment: Pass if the Platform support Pausing/ Resuming service.
installed platform.
2. Test procedure:
account.
Subscriptions The platform must support buying buying additional services.
20
Management additional service for data, SMS, voice
- Step 3: Select drop-down menu to service plan.
- Step 4: Select drop-down menu to choose appropriate plan for additional data, SMS and
voice volume.
3. Assessment: Pass if the Platform support buying additional service for data, SMS,
voice.
installed platform.
2. Test procedure:
The platform must support Subscriber account.
Subscriptions - Step 2: Direct to the Subscription Management section or designated domain support
21 Payment individually or collectively (in
Management invoicing/customer payment.
bulk)
- Step 3: Select drop-down menu to Subscriber Payment.
- Step 4: Invoicing all connections belong to that Subscriber proceed for Payment.
3. Assessment: Pass if the Platform support Subscriber Payment individually or
collectively (in bulk).
22 Multi-Operator The platform must support remote eSIM 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management profile transfers from one operator to installed platform.
89
2. Test procedure:
account.
another to support Customer's multi-region view eSIM status.
deployment requirements.
- Step 3: Select OTA swap to transfer of a SIM’s credentials (ICCID, IMSI, MSISDN)
from one operator to another.
3. Assessment: Pass if the Platform support remote eSIM profile transfers from one
operator to another
IV Rating Management
installed platform.
2. Test procedure:
The platform must support multi rate plan account.
1 Rate plan includes at least prepaid, postpaid, - Step 2: Direct to the Rating Management section or designated domain support to
individual and pooled plans. view rating plan.
- Step 3: Select drop-down menu to choose between subscriber types of prepaid or
postpaid and usage type of individual or pooled.
3. Assessment: Pass if the Platform support multiple tariff options includes prepaid,
postpaid, and pooled plans.
2 Rate Plan The platform must support to change price 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management plan installed platform.
2. Test procedure:
account.
- Step 2: Direct to the Rating Management section or designated domain support to view
rating plan.
90
- Step 3: Select drop-down menu to choose between rate plans.
3. Assessment: Pass if the Platform support to change price plan.
installed platform.
2. Test procedure:
Rate Plan The platform must support selecting of rate - Step 1: Log into the platform (web-based portal) with the provided account.
4
Management plans via web interface - Step 2: Direct to the Rating Management section or designated domain support to view
rating plan.
- Step 3: Select drop-down menu to choose between rate plans.
3. Assessment: Pass if the Platform support to change price plan via web interface.
installed platform.
2. Test procedure:
The platform must support per-term plans - Step 1: Log into the platform (web-based portal) with the provided account.
Rate Plan
7 (at least xMBs or xMonths, whichever - Step 2: Direct to the Rating Management section or designated domain support to view
Management
comes first) rating plan.
- Step 3: Select drop-down menu to choose between rate plans per-term (xMBs or x
Months whichever comes first).
3. Assessment: Pass if the Platform support per-term plans.
installed platform.
2. Test procedure:
Rate Plan The platform must support volume-based - Step 1: Log into the platform (web-based portal) with the provided account.
8
Management pre-paid plans - Step 2: Direct to the Rating Management section or designated domain support to view
rating plan.
- Step 3: Select drop-down menu to choose volume-based rate plans (xMBs).
3. Assessment: Pass if the Platform support volume-based rating plans.
91
installed platform.
2. Test procedure:
- Step 1: Log into the platform (web-based portal) with the provided account.
Rate Plan The platform must support time-based pre-
9 - Step 2: Direct to the Rating Management section or designated domain support to view
Management paid plans
rating plan.
- Step 3: Select drop-down menu to choose between time-based pre-paid plans with
different fees for off peak and time-related zones.
3. Assessment: Pass if the Platform support time-based pre-paid plans.
installed platform.
2. Test procedure:
Rate Plan
10 The platform must support roam zones - Step 2: Direct to the Rating Management section or designated domain support to view
Management
rating plan.
- Step 3: Select drop-down menu to choose between rate plans per roaming zones with the
charges associated with the zone.
3. Assessment: Pass if the Platform support rating per roaming zones.
11 Rate Plan The platform must support discount tiers 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management by total account payment or subscribers installed platform.
2. Test procedure:
discount tiers in rating plan.
- Step 3: Select drop-down menu to view discounts per number of subscribers, the overall
money will substract from the total.
3. Assessment: Pass if the Platform support discount tiers by total account payment or
92
subscribers.
installed platform.
2. Test procedure:
Rate Plan The platform must support discount tiers - Step 1: Log into the platform (web-based portal) with the provided account.
13
Management by roam zone - Step 2: Direct to the Rating Management section or designated domain support to view
discount tiers in rating plan.
- Step 3: Select drop-down menu to change discounts by apply new roaming zone.
3. Assessment: Pass if the Platform support discount tiers by roaming zone.
installed platform.
2. Test procedure:
Rate Plan The platform must support APN-based APN-based rating.
14
Management rating
- Step 3: Select drop-down menu to specify which APNs the device can use for data
services that results in different communication plan.
3. Assessment: Pass if the Platform support APN-based rating.
Accepted if the platform have roadmap to support APN-based rating free of charge within
06 months since the effective date of the contract.
15 Rate Plan The platform must support peak and off- 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management peak rating installed platform.
2. Test procedure:
peak and off-peak rating.
- Step 3: Select drop-down menu to manage off peak usage and fees through time-related,
a single rate plan can have one zone that defines access and
93
charges during normal business hours and another for off peak times.
3. Assessment: Pass if the Platform support peak and off-peak rating.
Pass: The platform support different overage rates by roam zone.
Rate Plan The platform must support different Accepted: The platform must have roadmap to support different overage rates by roam
16
Management overage rates by roam zone zone free of charge within 06 months since the effective date of the contract.
Not pass: The platform does not support different overage rates by roam zone.
installed platform.
2. Test procedure:
Rate Plan The platform must support different
17 overage rates in rating plan.
Management overage rates by peak and off peak
- Step 3: Select drop-down menu to switch IoT device from its standard rate (off peak)
plan to a premium rate plan (peak plan). The premium plan must have a lower overage
rates, and it could help eliminate even more costly overage charges than if the device were
to remain on the standard plan.
3. Assessment: Pass if the Platform support different overage rates by peak and off peak.
installed platform.
2. Test procedure:
Rate Plan The platform must support proration of
Management service fees based on activation
services fees.
- Step 3: Select drop-down menu to switch IoT device from its proration policy (monthly,
daily).
3. Assessment: Pass if the Platform support proration of service fees based on activation.
19 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,

94
installed platform.
2. Test procedure:
Management session rounding per rate plan
session rounding per rate plan adjustment.
- Step 3: Select drop-down menu to view adjustment for specified device per rate plan.
3. Assessment: Pass if the Platform support session rounding per rate plan by round up
and round down.
installed platform.
2. Test procedure:
Management session rounding per roam zone
session rounding per roam adjustment.
- Step 3: Select drop-down menu to view adjustment for specified device per roam zone.
3. Assessment: Pass if the Platform support session rounding per roam zone by round up
and round down.
installed platform.
2. Test procedure:
The platform must support rating
Rate Plan - Step 1: Log into the platform (web-based portal) with the provided account.
21 calculations based on commercial terms
Management - Step 2: Direct to the Rating Management section or designated domain support to view
and not on activation status of SIM
rating detailed information for a SIM card which is not activated yet but has the
commercial terms to make it billable.
3. Assessment: Pass if the Platform support commercial based rating.
22 Rate Plan The platform must support IMEI based 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management rating installed platform.
2. Test procedure:
95
IMEI based rating.
- Step 3: Select drop-down menu to select IMEI information.
3. Assessment: Pass if the Platform support IMEI based rating.
installed platform.
2. Test procedure:
The platform must support rating based on
Rate Plan - Step 1: Log into the platform (web-based portal) with the provided account.
23 URL, group of URL's, IP address and IP
Management - Step 2: Direct to the Rating Management section or designated domain support to view
address range based rating
URL, IP based rating.
- Step 3: Select drop-down menu to select different IP range, URL.
3. Assessment: Pass if the Platform support URL, IP based rating.
installed platform.
2. Test procedure:
Rate Plan The platform must support time-of-day,
Management day-of-week based rating.
time based rating.
- Step 3: Select drop-down menu to select different time-of-day, day-of-week.
3. Assessment: Pass if the Platform support time (time-of-day, day-of-week) based rating
with different charge.
25 Rate Plan The platform must support location (MCC- 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,
Management MNC, RAC, TAC) based rating installed platform.
2. Test procedure:
location based rating.
96
- Step 3: Select drop-down menu to select different location (MCC-MNC, RAC, TAC) or
has device enters different geographic region with different network information (MCC-
MNC, RAC, TAC).
3. Assessment: Pass if the Platform support location (MCC-MNC, RAC, TAC) based
rating.
installed platform.
2. Test procedure:
The platform must support access - Step 1: Log into the platform (web-based portal) with the provided account.
Rate Plan
26 technology type (2G, 3G, LTE) based - Step 2: Direct to the Rating Management section or designated domain support to view
Management
rating. technology based rating.
- Step 3: Select drop-down menu to select different technology type (2G, 3G, and LTE).
3. Assessment: Pass if the Platform support access technology type (2G, 3G, LTE) based
rating.
V Usage/Cost Management
1. Pre-set Condition: Proposal documents provided by vendor
Usage The platform must support both manual 2. Test procedure: Read and analyze the documents, follow the instruction to test this
1
Monitoring and automatic usage monitoring options requirement
3. Assessment: Pass if meet the requirement
1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
administrator account
Usage The platform must support to display all 2. Test procedure:
2
Management invoice details online. - Step 1: Log into the platform using the provided account
- Step 2: Direct to the invoice management portal
3. Assessment: Pass if the administrator can see all the invoice details online
3 Usage The platform must support to generate 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Management invoice which include by type of administrator account
97
2. Test procedure:
- Step 1: Log into the platform using the provided account
connectivity service and all applicable - Step 2: Direct to the invoice and billing management portal
charges - Step 3: Generate the invoice of a SIM or a set of SIMs. The information in the invoice
include by type of connectivity service and all applicable charges
3. Assessment: Pass if satisfy every steps
The platform must support invoice 2. Test procedure:
Usage
4 searching by SIM, Rate Plan, and Sub- - Step 1: Log into the platform using the provided account
Management
Customer or Customer-division. - Step 2: Direct to the invoice and billing management portal
- Step 3: Search the invoice by SIM, Rate Plan, and Sub-Customer or Customer-division.
3. Assessment: Pass if the search results show correctly
2. Test procedure:
The platform must support to provide - Step 1: Log into the platform using the provided account
Usage invoice and billing details available at a - Step 2: Direct to the invoice and billing management portal
5
Management summary level and broken out at an - Step 3: View/read the invoice and billing at summary level (The total number of invoice
individual SIM level. and billing, the total of data used, the total paid amount…)
- Step 4: Choose a SIM and view the detail information of invoice and billing related to
this SIM
3. Assessment: Pass if satisfy all the steps
6 Usage The platform must support to export 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Management invoice data to Excel (.csv) format, via administrator account
API, or over a data warehouse feed. 2. Test procedure:
98
- Step 2: Direct to the invoice/billing management portal
- Step 3: Choose a report and export the report to pdf. The export can be done using GUI,
APIs or over dataware house feed.
3. Assessment: Pass if the satisfy every steps
Usage The platform must support to displays all 2. Test procedure:
7
Management rate plans available - Step 1: Log into the platform using the provided account
- Step 2: Direct to the rate plan management portal
3. Assessment: Pass if the administrator can see all the rate plans available
administrator account, a list of SIM that need to change rate plan store in a dataset file
(Excel, CSV…)
2. Test procedure:
The platform must enable rate plan - Step 1: Log into the platform using the provided account
Usage
8 changes by SIM, Sub-Customer or block of - Step 2: Direct to the rate plan management portal
Management
SIMs via the web, bulk upload or API - Step 3: Upload the dataset file that contain the information of SIMs that needed to
change rate plan (via GUI or APIs) into the rate plan management portal.
- Step 4: Check if all the SIMs listed in the dataset file are automatically changed rate
plan.
9 Usage The platform must support automatic 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Management disablement of SIM usage when SIM administrator account
reaches its pre-configured overage limit for 2. Test procedure:
the billing cycle. Platform must support - Step 1: Log into the platform using the provided account
override of this disablement - Step 2: Direct to the billing management portal
- Step 3: Configure the overage limit number of a SIM (easy to reach for testing purpose).
99
- Step 4: Monitor to see if the platform automatically disable the SIM usage when SIM
reaches its pre-configured overage limit for the billing cycle.
- Step 5: Re-configure the overage limit number
- Step 6: Override the disablement of SIM usage (enable it back)
The platform must support automatically 2. Test procedure:
Usage notify selected users when a SIM or block - Step 1: Log into the platform using the provided account
10
Management of SIMs is about to exceed its expected - Step 2: Direct to the user management portal
usage in a 24hour or 30-day period - Step 3: Monitor the selected user to see if the users are notified when a SIM or block of
SIMs is about to exceed its expected usage in a 24hour or 30-day period
The platform must support to display total 2. Test procedure:
Usage data, SMS and voice consumed by a SIM - Step 1: Log into the platform using the provided account
11
Management at any point within a billing cycle - Step 2: Direct to the user billing management portal/feature
(monthly). - Step 3: The administrator can see the detailed information of total data, SMS and voice
consumed by a SIM at any time in the billing cycle
3. Assessment: : Pass if satisfy every steps
12 Usage The platform must support to enable 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Management automatic transition to another rate plan at administrator account
the end of a pre-paid subscription plan 2. Test procedure:
- Step 2: Direct to the rate plan management portal
- Step 3: Monitor the portal to see if the rate plan is automatically changed to another rate
100
plan at the end of a pre-paid subscription plan
2. Test procedure:
The platform must supports automatic
Usage - Step 1: Log into the platform using the provided account
13 change of rate plan assignment based on
Management - Step 2: Direct to the rate plan management portal
network registration and roam zone usage
- Step 3: Monitor the portal to see if the rate plan assignment is automatically changed
based on network registration and roam zone usage.
The platform must support automatically 2. Test procedure:
notify selected users when a pool of SIMs - Step 1: Log into the platform using the provided account
Usage
14 reaches a certain % of its data or SMS - Step 2: Direct to the automation/rule portal
Management
allotment. Threshold to initiate a - Step 3: Set up a low threshold and monitor the selected user to see if the users are
notification must be configurable. notified when a pool of SIMs reaches the pre-defined % (threshold) of its data or SMS
allotment
15 Usage The platform must support billing and 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Management usage management based on type of administrator account
service as defined by URL(s), IP Address, 2. Test procedure:
device type (IMEI), access type (2G, 3G, - Step 1: Log into the platform using the provided account
4G), time of day/day of week and location - Step 2: Direct to the user billing and usage portal/feature
- Step 3: The administrator can see the detailed information of subscriptions about:
 Type of service as defined by URL(s)
 Type of service as defined by IP Address
101
 Type of service as defined by device type (IMEI)
 Type of service as defined by access type (2G, 3G, 4G)
 Type of service as defined by time of day/day of week
 Type of service as defined by location
3. Assessment: Pass if the administrator can see all the detail information list in step 3.
2. Test procedure:
The platform must provide Dashboard to
16 compare stream level usage over two time
Management - Step 2: Direct to the dashboard/chart portal
periods (weekly or monthly)
- Step 3: The platform has the dashboard or chart to compare stream level usage over two
time periods (weekly or monthly)
3. Assessment: Pass if meet the requirements
2. Test procedure:
The platform must support to display
17 airtime billing, total amount of charge at
Management - Step 2: Direct to the user management portal/feature
the time of requesting report
- Step 3: The administrator can see the detailed information of subscriptions about airtime
billing, total amount of charge at the time of requesting report
3. Assessment: Pass if the administrator can see all the detail information in step 3.
18 Usage The platform must support to display used 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Management amount/ the rest/ total paid amount of data administrator account
2. Test procedure:
- Step 2: Direct to the user management portal/feature
- Step 3: The administrator can see the detailed information of subscriptions:
102
 Used amount of data
 The rest amount of data
 Total paid amount of data
2. Test procedure:
Usage The platform must support to display used - Step 2: Direct to the user management portal/feature
19 - Step 3: The administrator can see the detailed information of subscriptions:
Management amount/ the rest/ total paid amount of SMS
 Used amount of SMS
 The rest amount of SMS
 Total paid amount of SMS
2. Test procedure:
The platform must support to display used - Step 2: Direct to the user management portal/feature
Usage
20 amount/ the rest/ total paid amount of - Step 3: The administrator can see the detailed information of subscriptions:
Management
voice
 Used amount of voice
 The rest amount of voice
 Total paid amount of voice
21 Usage For sharing data plans among a number of 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Management subscription, the platform must support to administrator account
103
2. Test procedure:
show: - Step 3: The administrator can see the detailed information of each number in a sharing
- Total used amount/ the rest/ the paid data plans:
amount  Total used amount of data
- Effective time of different block of data  The rest amount of data
 The paid amount of data
 Effective time of different block of data
The platform must support to manage 1. Pre-set Condition: Proposal documents provided by vendor
billing, invoicing and cost management
Usage 2. Test procedure: Read and analyze the documents, follow the instruction to test this
22 across multiple operators' networks in a
Management requirement
multi-operator network/region deployment
scenario 3. Assessment: Pass if meet the requirement
VI Billing Management
Billing options The platform must support to collect 2. Test procedure: Read and analyze the documents, follow the instruction to test this
1
/flexibility billing data via CDR or other file formats requirement
2 Billing options/ The platform must support to manage 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
flexibility rating and charging administrator account
2. Test procedure:
- Step 2: Direct to the billing management portal/feature
- Step 3: Check if the administrator can do all these actions:
104
 View/read the available rating and charging plan in the platform
 Create new rating and charging plan
 Update/change the rating and charging plan
 Delete the rating and charging plan
1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
account
2. Test procedure:
Billing options/ The platform support to present invoice
3 - Step 1: Log into the platform using the provided account
flexibility and bill to the customer
- Step 2: Direct to the customer billing management portal/feature
- Step 3: Check if the invoice and bill related to the user is available
3. Assessment: Pass if the invoice and bill related to the user is available
The platform must support to integrate 2. Test procedure:
with Viettel billing system (via secure FTP - Step 1: Log into the platform using the provided account
Billing
4 for the exchange of CDR, invoices and - Step 2: Check if the platform has independent airtime billing system.
integration
reports) or provide independent airtime - Step 3: If not, vendor must cooperate with Viettel technical team to integrate the
billing system within CMP platform with Viettel billing system (via secure FTP for the exchange of CDR, invoices
and reports)
5 Billing The platform must support to present 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
management detailed invoices for all subscribed administration account
services, by type of service and device 2. Test procedure:
- Step 3: Check if the detailed invoices for all subscribed services, by type of service and
105
device is available
- Step 4: Search and sort all the invoices
administration account
2. Test procedure:
The platform must support to display all - Step 1: Log into the platform using the provided account
Billing
6 the invoice information in the web - Step 2: Direct to the billing management portal/feature
management
interface - Step 3: Check if the feature of split-billing based on multiple rating for multiple service
types is available
3. Assessment: Pass if the feature of split-billing based on multiple rating for multiple
service types is available in the platform
2. Test procedure:
The platform must support split-billing
Billing - Step 3: Check if the feature of split-billing based on multiple rating for multiple service
7 based on multiple rating for multiple
management types is available
service types
3. Assessment: Pass if the feature of split-billing based on multiple rating for multiple
service types is available in the platform
Note: In case the platform does not support this requirement, vendor should have the
roadmap to support free of charge within 06 months since the effective date of the
contract.
8 Billing The platform must support APN based 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
management split billing administration account
2. Test procedure:
106
- Step 3: Check if the feature of split-billing based on APN is available
3. Assessment: Pass if the feature of split-billing based on APN is available in the
platform
contract.
2. Test procedure:
Billing The platform must support split-billing on
9 - Step 3: Check if the feature of split-billing on Classified Data Streams is available
management Classified Data Streams
3. Assessment: Pass if the feature of split-billing on Classified Data Streams is available
in the platform
contract.
VII Troubleshooting and Fault management procedures, Help Desk and SLA criteria
Troubleshooting/ The platform must have the reporting
2. Test procedure: Read and analyze the documents, follow the instruction to test this
1 Fault procedure for loss of one or more
requirement
Finding connections
2 Troubleshooting/ The platform must support the rectification 1. Pre-set Condition: Proposal documents provided by vendor
Fault of faults and notification processes relating 2. Test procedure: Read and analyze the documents, follow the instruction to test this
Finding to loss of connection or loss of services requirement
107
administration account, a device that are connected to the system (can be a virtual device)
2. Test procedure:
Troubleshooting/ - Step 1: Log into the platform using the provided account
The platform must support to figure out the
3 Fault - Step 2: Direct to the device management portal/tool
last time of checked connection
Finding - Step 3: Disconnect the device (physically or logically)
- Step 4: Check in the platform to see the last time the device change connection status
3. Assessment: Pass if the platform correctly show the last time that the device change
connection status
2. Test procedure:
Troubleshooting
The platform must support to figure out the - Step 1: Log into the platform using the provided account
4 /Fault
last location and display on the map - Step 2: Direct to the device management portal/tool
Finding
- Step 3: Check the last location of device in platform and see how it reflects in the map
3. Assessment: Pass if the last location of device is available and reflects correctly in the
map
2. Test procedure:
Troubleshooting
The platform must support to make call or - Step 1: Log into the platform using the provided account
5 /Fault
send SMS to test the connection - Step 2: Direct to the portal/tool that support SMS or call feature
Finding
- Step 3: Send SMS or make a call to a device using device’s number to see if the device
is test the connection of device
3. Assessment: Pass if the meet the requirement
6 Service Level The platform must provide the mechanism 1. Pre-set Condition: Proposal documents provided by vendor
108
Agreements to measure and report the key SLA/QoS
requirement
(SLAs) metrics
2. Test procedure:
The platform must provide or support - Step 2: Check if the platform has Helpdesk capabilities
7 Help Desk integration of Helpdesk capabilities for the - Step 3: If not, vendor must cooperate with Viettel technical team to integrate the
customer platform with the Helpdesk system of Viettel.
contract.
1. Pre-set Condition: Proposal documents provided by vendor with detail information of
how to integrate with Viettel Customer Care System with the hotline for helpdesk support
The platform must support the integration 2. Test procedure: Viettel provides the needed of integration listed in the documents
8 Help Desk with Viettel Customer Care System with (APIs, web services, URL). The vendor cooperate with Viettel technical team to integrate
the hotline for helpdesk support the platform with Viettel Customer Care System with the hotline for helpdesk support
3. Assessment: Pass if successfully integrate with Viettel Customer Care System with the
hotline for helpdesk support
1. Pre-set Condition: Proposal documents provided by vendor with detail information of
how to integrate with Viettel Trouble Ticket
The platform must support the integration
Network 2. Test procedure: Viettel provides the needed of integration listed in the documents
9 with Viettel Trouble Ticket System for
Monitoring (APIs, web services, URL). The vendor cooperate with Viettel technical team to integrate
technical issues
the platform to Viettel Trouble Ticket System.
3. Assessment: Pass if successfully integrate with Viettel Trouble Ticket System
109
The platform must support monitoring and 1. Pre-set Condition: Proposal documents provided by vendor
Network reporting on abusive devices, defined by 2. Test procedure: Read and analyze the documents, follow the instruction to test this
10
Monitoring specified number of authorization attempts requirement
within a given period 3. Assessment: Pass if meet the requirement
Network 2. Test procedure: Read and analyze the documents, follow the instruction to test this
11 provide a pass through link to Operators
Monitoring requirement
Support platform
VIII Diagnostic
The platform must provide network 1. Pre-set Condition: Proposal documents provided by vendor
activity diagnostics to resolve technical 2. Test procedure: Read and analyze the documents, follow the instruction to test this
1 Diagnostic
issues regarding communications (at least requirement
for NB-IoT devices) 3. Assessment: Pass if meet the requirement
The platform must support to display real- 1. Pre-set Condition: Proposal documents provided by vendor
time session status, including IP address, 2. Test procedure: Read and analyze the documents, follow the instruction to test this
2 Diagnostic
operator, session start time (at least for requirement
NB-IoT devices) 3. Assessment: Pass if meet the requirement
The platform must support to evaluate the 1. Pre-set Condition: Proposal documents provided by vendor
SIM’s ability to attach to the wireless
3 Diagnostic network by checking its current status on
requirement
the HLR as well as the HLR logs (at least
for NB-IoT devices) 3. Assessment: Pass if meet the requirement
4 Diagnostic The platform must support to send SMS to 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
specified device to determine whether or administration account
not it is reachable over the operator 2. Test procedure:
network - Step 1: Log into the platform using the provided account
110
- Step 2: Direct to the portal/tool that support SMS feature
- Step 3: Send SMS to a device using device’s number to see if the device is reachable
3. Assessment: Pass if the meet the requirement
Pass: The platform support to ping specified device to determine whether or not it is
reachable over the operator network.
Accepted: The platform does have the ability to tell if the subscriber is online or offline.
Not pass: The platform does not support to ping specified device to determine whether or
not it is reachable over the operator network and does have the ability to tell if the
subscriber is online or offline.
The platform must support to ping administration account
specified device to determine whether or
5 Diagnostic 2. Test procedure:
not it is reachable over the operator
network - Step 1: Log into the platform using the provided account
- Step 2: Direct to the Diagnostic for Fault Management portal/feature
- Step 3: Ping specified device to see if the device is reachable or using alternative
mechanism to check whether the device is online of offline.
3. Assessment: Pass if the result meet the requirement
contract.
IX Alarm management
1 Alarm The platform must support alarm setting 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
management for threshold: administration account
- Dramatically used daily, weekly, monthly 2. Test procedure:
over limitation - Step 1: Log into the platform using the provided account
- Rarely used daily, weekly, monthly under - Step 2: Direct to the alarm management portal/feature
limitation
- Step 3: Create an alarm with an alarm message
111
- Step 4: Set up a rule that send an SMS to a number when some events happens:
 Dramatically used daily, weekly, monthly over limitation
- Lost connection.  Rarely used daily, weekly, monthly under limitation
- Wrong mapping between IMSI & IMEI  Device lost connection
in pool of device  Wrong mapping between IMSI & IMEI in pool of device
- Step 5: Trigger the rule and see if all the alarm messages are sent
2. Test procedure:
- Step 2: Direct to the alarm management portal/feature
The platform must support to configure the
moment of rising alert: - Step 3: Create an alarm with an alarm message
Alarm - Step 4: Configure all the parameter related to alarm:
2 - Immediately when event occurs
management
- After an amount of time after occuring  Immediately when event occurs
- Duration of effectiveness of alarm  After 2 minutes time after occuring
 1 min of effectiveness of alarm
- Step 5: Create a rule to trigger the alarm and check if the alarm works properly with all
the parameters in step 4.
3 Alarm The platform must support method of 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
management generating alarm via: administration account
- SMS 2. Test procedure:
- Email - Step 1: Log into the platform using the provided account
- Direct call - Step 2: Direct to the alarm management portal/feature
All SMS/ Call/ Email are sent from the
- Step 3: Create an alarm with an alarm message
system
112
- Step 4: Set up a rule that when triggered, send an alarm SMS to a number, an alarm
email to an email address and call another number with a pre-defined voice message
- Step 5: Trigger the rule and see if all the alarm messages are sent
- Step 6: Disable the rule and do step 5 again, the alarm message should not be sent
2. Test procedure:
- Step 2: Direct to the alarm management portal/feature
The platform must support the general - Step 3: Create an alarm with an alarm message
Alarm configuration:
4 - Step 4: Set up a rule that when triggered, send an alarm message to a number
management - Enable/ Disable alarm
Step 5: Trigger the rule and see if the alarm message is sent
- Modify the content of the message
Step 6: Disable the rule and do step 5 again, the alarm message should not be sent
Step 7: Enable the rule
Step 7: Modify the alarm message and do step 5 again to see if the alarm message is
changed
X Location based services
1 Location based The platform must support to locate the 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
services position of devices. administration account
2. Test procedure:
- Step 2: Direct to the map/location management portal/feature
- Step 3: Try to zoom-in - zoom-out on the map ( mouse-scroll )
- Step 4: Select one of ICCID from the list and check for the SIM location
113
contract.
2. Test procedure:
Location based The platform must support using different
2 - Step 2: Direct to the map/location management portal/feature
services colors for displaying different status
- Step 3: Disconnect a device in the map
- Step 4: The administrator should see the color of device that is disconnected different
with other connected devices.
2. Test procedure:
The platform must support the quick - Step 1: Log into the platform using the provided account
Location based
3 search for subscription & connectivity on - Step 2: Direct to the map/location management portal/feature
services
the map - Step 3: Search a device using name or id
- Step 4: The administrator should see all devices related to the search keyword with
highlight color on the map
XI Security
1 Security of The platform must provide capabilities to 1. Pre-set Condition: Proposal documents provided by vendor
connection ensure security of connection by providing 2. Test procedure: Read and analyze the documents, follow the instruction to test this
capabilities to different users based on requirement
profiles and IP access management to limit 3. Assessment: Pass if meet the requirement
114
access only from predefined IP address or
range.
contract.
The platform must provide capabilities to
Security of data 2. Test procedure: Read and analyze the documents, follow the instruction to test this
2 ensure the security of transmission
transmission requirement
including HTTPS or SSL
The platform must support to provide
3 Security connection via public/ private APN and
requirement
dynamic/ static IP address
The platform must support IP-address 2. Test procedure: Read and analyze the documents, follow the instruction to test this
4 Security
filtering features via APN requirement
The platform must support password
5 Authentication protected authentication to allow access to
requirement
the network
The platform must not display passwords,
6 Password control either via email or an web-based password
requirement
reminder function.
7 Fraud The platform must prohibit the use of a 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
management SIM outside of its unintended device. administration account, an actual device connected to the system and a SIM that is not
Platform must send notification when assigned to the device
fraudulent activity is attempted
115
2. Test procedure:
- Step 2: Direct to the automation rule management portal/feature
- Step 3: Set up a rule trigger when an unassigned SIM is attached to the device and notify
administrator in the platform
- Step 4: Swap the SIM of the device with the provided SIM
- Step 5: The administrator should see the notification of the action
contract.
The platform must support for IMEI 2. Test procedure: Read and analyze the documents, follow the instruction to test this
8 Filtering
whitelisting requirement
1. Pre-set Condition: Proposal documents provided by vendor 2. Test procedure: Read
The platform must support for SMS
9 Filtering and analyze the documents, follow the instruction to test this requirement
whitelisting
1. Pre-set Condition: Proposal documents provided by vendor 2. Test procedure: Read
The platform must support for Voice
10 Filtering and analyze the documents, follow the instruction to test this requirement
whitelisting
11 Track events The platform must support to track actions 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
performed by users in the system, administration account
including time stamp for actions like 2. Test procedure:
changing a rate plan or what events - Step 1: Log into the platform using the provided account
triggered automation rules - Step 2: Direct to the rate plan management portal/feature
- Step 3: Change the rate plan of a subscription
116
- Step 4: Direct to the portal/feature that support tracking the events in the system
- Step 5: The administrator should see the event of changing rate plan with correct time
stamp.
XII IP Addressing MechaniSMS and Access Point Name - APN (private and public) provisioning
IP Addressing The platform must support both static and 2. Test procedure: Read and analyze the documents, follow the instruction to test this
1
MechaniSMS dynamic IP addressing requirement
Access Point 1. Pre-set Condition: Proposal documents provided by vendor
Name - APN
The platform must support both public and 2. Test procedure: Read and analyze the documents, follow the instruction to test this
2 (private and
private APN provisioning requirement
public)
provisioning 3. Assessment: Pass if meet the requirement
XIII Application Program interfaces (APIs)/Developer Tools

1. Pre-set Condition: Proposal documents provided by vendor with detail information
The platform must provide API libraries about the APIs for all major functions including Order provisioning, Subscription
Application Management, Rating Management, Usage Management
for all major functions including Order
1 Program
provisioning, Subscription Management, 2. Test procedure: Read and analyze the documents, follow the instruction to test this
Interfaces (APIs)
Rating Management, Usage Management requirement
2 Application The platform must provide API for 1. Pre-set Condition: Proposal documents provided by vendor with detail information
Program integrating with other enterprise system about APIs and how to integrate into CRM and AEP
Interfaces (APIs) including Customer Relation Management 2. Test procedure: Vendor cooperate with Viettel and AEP side until successful
(CRM), Application Enablement Platform integration
(AEP) for below actions 3. Assessment: Pass if meet the requirement
- Get connection status of SIM, operation
117
status of subscription
- Get history of usage
- Get history of billing
- Get location-base info
- Get alert info
1. Pre-set Condition: Proposal documents provided by vendor with detail information
Application about APIs to support the provisioning of devices and services.
The platform must provide APIs to support
3 Program 2. Test procedure: Read and analyze the documents, follow the instruction to test this
the provisioning of devices and services.
Interfaces (APIs) requirement
XIV Administration
2. Test procedure:
The platform must support administrative
- Step 2: Check if Service Desk, Data Centre Management and Disaster Recovery
capabilities including Service Desk, Data
1 Administration Management are available
Centre Management and Disaster
3. Assessment: Pass if Service Desk, Data Centre Management and Disaster Recovery
Recovery Management
Management are available.
Note: In case the platform does not have one of the two: Service Desk, Data Centre
Management and Disaster Recovery Management vendor should have the roadmap to
support free of charge within 06 months since the effective date of the contract.
2 Administration The platform must support to Add/ 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
Modify/ Delete user administration account
2. Test procedure:
- Step 2: Direct to user management portal/feature
- Step 3: The organization administrator must have the ability to view/read, create/add,
118
update/modify and delete user
2. Test procedure:
The platform must support to Add/
3 Administration Modify/ Delete the hierarchy of
- Step 2: Direct to organization management portal/feature
organization with at least 3 layer of users
- Step 3: The organization administrator must have the ability to view/read, create/add,
update/modify and delete organization with at least 3 layer of users
2. Test procedure:
- Step 3: Create a user account and does not grant permission to access to the platform
The platform must support to grant
4 Administration - Step 4: Log out and log in using the newly created user account. The account should not
permission to access the Platform
be access to the platform
- Step 5: Log in using the administrator account again
- Step 6: Grant permission to access to the platform to the created account in step 3.
- Step 7: Log out and log in using the newly create account. The account should be able to
access to the platform
5 Administration The platform must support customer admin 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, an
to manage and authorize their accounts in administration account
the organization by themselves 2. Test procedure:
119
- Step 3: Create a new organization administrator account
- Step 4: Log out and log in using the newly created organization administrator account
- Step 5: The organization administrator must have the ability to do these actions:
 View, read, create, update, delete account, role of the organization
 Assigned resources (data, features, apps) to each user account of the organization
 Assign user to role
1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a role-
based administration account
2. Test procedure:
Role-based The platform must support role-based - Step 1: Log into the platform using the provided account
6
Access administration - Step 2: Direct to role management portal/feature
- Step 3: Check if the role-based administrator is able to view the roles, create and delete
role, assign resource to role and assign role to user
7 Role-based The platform must support specialized 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a role-
Access role, allowing access only for customer based administration account
support personnel, with no financial 2. Test procedure:
information - Step 1: Log into the platform using the provided account
- Step 2: Direct to role management portal/feature
- Step 3: Check if the role management portal have the pre-defined role that allowing
access only for customer support personnel, with no financial information
- Step 4: If no, create a role and grant authority to access to only customer support
personnel, with no financial information
- Step 6: Create an account and assign to the role
- Step 7: Log out and log in using the account created
120
- Step 8: Check to see if the account can access to only the customer support personnel,
with no financial information
contract.
2. Test procedure:
- Step 3: Check if the role management portal have the pre-defined role that allowing
The platform must support specialized access only for financial personnel.
Role-based - Step 4: If no, create a role and grant authority to access to only financial personnel
8 role, allowing access only for financial
Access
personnel - Step 6: Create an account and assign to the role
- Step 8: Check to see if the account can access to only the financial personnel
contract.
9 Role-based Platform must support sub-management 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a role-
Access roles, limiting information and activity to based administration account
subset of SIMs allocated 2. Test procedure:
- Step 3: Check if the role management portal have the pre-defined sub-management role.
121
- Step 4: If yes, check the resources that is assigned for the role
- Step 5: If no, create the sub-management role and assign resources to it
- Step 6: Create an account and assign to the role
- Step 8: Check to see if the account can access to the resources assigned
Platform must support features to allow a 2. Test procedure:
Role-based resale model whereby Customer can - Step 1: Log into the platform using the provided account
10
Access support multiple Sub-Customers in a - Step 2: Direct to the feature that support the release model
management and billing capacity. - Step 3: Create and assign a resale model/plan to a subscription
3. Assessment: Pass if platform has feature to allow to create and assign the resale model
to a subscription.
XV Dashboard, Reporting and Inventory Management
The platform must provide dashboard for account
controlling connectivity status, including 2. Test procedure:
ratio chart for connection type: - Step 1: Log into the platform using the provided account
1 Dashboard - SIM control status: connected/ - Step 2: Direct to the dashboard portal/feature
disconnected - Step 3: Change the SIM control status (connected/ disconnected)
- Subscription control status: Active/ - Step 4: Change the Subscription control status (Active/ Deactive/ Pause/ Terminate)
Deactive/ Pause/ Terminate - Step 5: Check if platform has ratio chart for connection type
3. Assessment: Pass if satisfy the test procedure
2 Dashboard The platform must provide dashboard for 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
total daily amount usage for: data, SMS, account
voice 2. Test procedure:
122
- Step 2: Direct to the dashboard portal/feature
- Step 3: Check if the platform has dashboard/chart show the total daily amount usage for:
data, SMS, voice
3. Assessment: Pass if the platform has dashboard/chart show total daily amount usage
for: data, SMS, voice
account
2. Test procedure:
The platform must provide dashboard for - Step 1: Log into the platform using the provided account
3 Dashboard total monthly, cumulative usage/ total paid - Step 2: Direct to the dashboard portal/feature
amount for: data, SMS voice - Step 3: Check if the platform has dashboard/chart show the total monthly, cumulative
usage/ total paid amount for: data, SMS voice
3. Assessment: Pass if the platform has dashboard/chart show the total monthly,
cumulative usage/ total paid amount for: data, SMS voice
account
2. Test procedure:
The platform must provide the history of - Step 1: Log into the platform using the provided account
4 Dashboard
usage, status for subscription - Step 2: Direct to the dashboard portal/feature
- Step 3: Check if the history of usage and status of subscription is available
3. Assessment: Pass if the history of usage and status of subscription is available in the
dashboard portal
5 Dashboard The platform must support for searching a 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
subscription for all information account
2. Test procedure:
- Step 2: Direct to the subscription management portal/feature
123
- Step 3: Search the subscription by name, SIM, active date…
3. Assessment: Pass if the search result show correctly
account
The platform must support to provide the 2. Test procedure:
6 Dashboard table of IMSI SIM & IMEI Device - Step 1: Log into the platform using the provided account
mapping - Step 2: Direct to the mapping portal/feature
- Step 4: Check if the table of IMSI SIM and Device IMEI mapping is available.
3. Assessment: Pass if the table of IMSI SIM and Device IMEI mapping is available.
The platform must support the mapping of account
subscription & device identification. 2. Test procedure:
7 Dashboard Customer can manage the mapping - Step 1: Log into the platform using the provided account
between subscription & device by IMEI - Step 2: Direct to the mapping portal/feature
themselves - Step 4: Mapping between subscription and device using IMEI
3. Assessment: Pass if the mapping is successful.
account
2. Test procedure:
Dashboard & Chart of alarm by daily,
8 Dashboard - Step 2: Direct to the dashboard portal/feature
weekly, monthly. Ratio chart by alarm
- Step 4: Check if platform has the dashboard/chart that shows the alarm by daily, weekly,
status (New/ Fixed)
monthly.
3. Assessment: Pass if platform has the dashboard/chart that shows the alarm by daily,
weekly, monthly.
9 Dashboard The platform must support to provide 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
Dashboard & Chart of using data plans account
124
2. Test procedure:
- Step 2: Direct to the dashboard portal/feature
- Step 4: Check if platform has the dashboard/chart that show the information of using
data plans
3. Assessment: Pass platform has the dashboard/chart that show the information of using
data plans
account
2. Test procedure:
The platform must support to provide - Step 1: Log into the platform using the provided account
10 Dashboard Dashboard & Chart of history for usage, - Step 2: Direct to the dashboard portal/feature
connectivity, airtime rating and billing - Step 4: Check if platform has the dashboard/chart that show the history for usage,
connectivity, airtime rating and billing
3. Assessment: Pass if platform has the dashboard/chart that show the history for usage,
connectivity, airtime rating and billing
account
2. Test procedure:
The platform must support to provides - Step 1: Log into the platform using the provided account
11 Reporting data, voice and SMS usage by SIM, Sub- - Step 2: Direct to the reporting portal/feature
Customer and Rate Plan - Step 4: Check if the report about data, voice and SMS usage by SIM, Sub-Customer and
Rate Plan is available
3. Assessment: Pass if report data, voice and SMS usage by SIM, Sub-Customer and Rate
Plan is available.
12 Reporting The platform must support to provide 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
details of every pdp context activation, account
including start time, duration and data 2. Test procedure:
125
- Step 2: Direct to the reporting portal/feature
- Step 4: Check if the report about information of pdp context activation (start time,
volume as a minimum.
duration and data volume) is available
3. Assessment: Report about information of pdp context activation (start time, duration
and data volume) is available.
account
The platform must support to provides 2. Test procedure:
13 Reporting reporting on the number of active vs. - Step 1: Log into the platform using the provided account
inactive SIMs - Step 2: Direct to the reporting portal/feature
- Step 4: Check if the report about number of active and inactive SIMs is available
3. Assessment: Pass if report about number of active and inactive SIMs is available
account
The platform must support to provide time- 2. Test procedure:
14 Reporting based session information for analytical - Step 1: Log into the platform using the provided account
purposes - Step 2: Direct to the reporting portal/feature
- Step 4: Check if the report about time-based session is available
3. Assessment: Pass if the time-based session information is available
15 Reporting The platform must support to store an audit 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
trail of every action taken in the platform, account
including action, affected SIM and userid 2. Test procedure:
of the person who made the change - Step 1: Log into the platform using the provided account
- Step 2: Make a change in the platform
- Step 3: Direct to the log portal/feature
- Step 4: View the log to see if the action before is logged by the platform
126
3. Assessment: Pass if the action is logged by the platform and is viewable in the log file
account
2. Test procedure:
Inventory - Step 1: Log into the platform using the provided account
16 easily searchable dashboard of all SIMs,
Management - Step 2: Direct to the SIMs dashboard
organized by ICCID and MSISDN
- Step 3: Search by SIM number
- Step 4: Organize the SIM by ICCID and MSISDN
3. Assessment: Pass if user can search the SIM and organize by ICCID and MSISDN
XVI Automation
The platform must support rules-based 1. Pre-set Condition: Proposal documents provided by vendor
business process automation with intuitive, 2. Test procedure: Read and analyze the documents, follow the instruction to test this
1 Automation
easy and non-programmatic way to create requirement
automation rules beyond notification 3. Assessment: Pass if meet the requirement
account
2. Test procedure:
The platform must support automated SIM
provisioning: SIM Rate Plan Changes,
2 Automation - Step 2: Direct to the automation/rule portal
SIM State Changes, and SIM custom field
- Step 3: Set up the automation scenario related to SIM Rate Plan changes, SIM State
changes.
Changes and SIM custom field changes.
- Step 4: Monitor the rule until it is triggered and check if the notification is sent
3. Assessment: Pass if get the notification when each rule is triggered
3 Automation The platform must support automated 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
preventative security diagnostics: account
Notification when a SIM has a credential 2. Test procedure:
mismatch and when the IMEI in the - Step 1: Log into the platform using the provided account
package is different from the previous
127
- Step 2: Direct to the automation/rule portal
- Step 3: Set up the rules in which the platform send notification to assigned user when a
SIM has a credential mismatch or when the IMEI from the package is different from the
IMEI for a SIM
previous IMEI for a SIM
The platform must support the automated
subscription management, including: 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
+ SIM data limit, triggered when a prepaid account
plan comes close to using its included 2. Test procedure:
usage
4 Automation + SIM expiration, triggered when a SIM on
a prepaid plan comes close to its expiration
- Step 3: Set up the rules for each scenario listed in the requirement.
dat
+ SIM plan completion, triggered when a - Step 4: Monitor the rule until it is triggered and check if the notification is sent
SIM's prepaid plan term ends due to either 3. Assessment: Pass if get the notification when each rule is triggered
term expiration or data consumption
5 Automation The platform must support standard 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
automated business rules that are triggered account
when: 2. Test procedure:
+ any SIM starts a session - Step 1: Log into the platform using the provided account
+ any SIM ends a session - Step 2: Direct to the automation/rule portal
+ a SIM has more connections than - Step 3: Set up the rules for each scenario listed in the requirement.
expected in the current billing cycle
+ a SIM has more/fewer connections than
expected in the trailing 24 hours
+ per SIM when the SIM has not been
connected for [Offline_Hours] hours
+ a SIM registers to the network in a
128
selected zone in the trailing 24 hours
+ a SIM's cycle to date data usage is above
the specified threshold
+ a SIM's cycle to date data usage is above
the specified threshold in a zone
+ per account/zone when data usage for the
zone is over the limit for the pooled plans
+ per SIM when usage is over limit in the
trailing 24 hours
+ per account per zone when SMS usage
for the zone is over the limit for the pooled
plans
+ a SIM's cycle to date voice usage is
above the specified threshold
+ a SIM's cycle to date voice usage is
above the specified threshold in a zone
+ a SIM's daily voice usage is above the
specified threshold
account
2. Test procedure:
The platform must support the ability to - Step 1: Log into the platform using the provided account
6 Automation automatically notify the assigned business - Step 2: Direct to the automation/rule portal
owner of excessive usage for that account - Step 3: Set up the automation send notification message to the assigned business owner
about the excessive usage of the owner’s account every pre-defined amount of time.
- Step 6: Run and monitor the rule
3. Assessment: Pass if the rule trigger properly.
7 Automation The platform must support the ability to 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
automatically notify the assigned business account
129
2. Test procedure:
owner of numerous logins within the
platform - Step 3: Set up the rule that when there are numerous login (>5) within the platform, send
notification message to the assigned business owner.
account
2. Test procedure:
automatically notify the assigned business
8 Automation - Step 2: Direct to the automation/rule portal
owner when the account is nearing a
prescribed usage threshold - Step 3: Set up the rule that when the account is nearing the usage threshold, send
notification message to the assigned business owner.
account
2. Test procedure:
9 Automation automatically notify the assigned business - Step 2: Direct to the automation/rule portal
owner of SIM activations - Step 3: Set up the rule that when a device’s SIM is active, send notification message to
the assigned business owner.
take action against defined business rules account
130
2. Test procedure:
and triggers. Should support the ability to - Step 2: Direct to the automation/rule portal
specify multiple follow-up actions, - Step 3: Set up the few-steps rule that when a device is changing location, platform send
allowing you to make temporary changes alert message to the device’s owner and send message to the device to active the alert
to the device behavior in response to mode in the device which makes the device send message that has location information to
business conditions platform every 5 minutes
account
The platform must support the ability to 2. Test procedure:
send an email message to one or more - Step 1: Log into the platform using the provided account
11 Automation email addresses or to the end user - Step 2: Direct to the automation/rule portal
associated with the device, based on a - Step 3: Set up the rule that the platform sends email address to the end user associated
business rule with the device when the device changes the location
send an SMS directly to your device when account
triggered by a certain event. Some devices 2. Test procedure:
are programmed to “wake up” when they - Step 1: Log into the platform using the provided account
receive an SMS or to send diagnostic - Step 2: Direct to the automation/rule portal
information back to a server when they
- Step 3: Set up the rule that the platform sends the message to device to tell device send
receive an SMS. Depending on how your
the diagnostic information back to the platform at a certain time/schedule (the time is pick
device is programmed, the SMS action can
for easy testing purpose)
help you interact directly with your devices
in the field
131
account
2. Test procedure:
push an API message. Platform should be - Step 2: Direct to the automation/rule portal
13 Automation
able to send a programmatic message to a - Step 3: Set up the rule in which a device lost connection, a XML message will send back
URL you specify when a rule is triggered. to your system contain the information of the device (name, id, time lost connection, last
location).
account
2. Test procedure:
14 Automation automatically change a device’s SIM state - Step 2: Direct to the automation/rule portal
when a rule is triggered - Step 3: Set up the rule in which when the data sent from device reach 100KB, the
platform automatically change the state of SIM from ready to active.
automatically change a device’s rate plan account
when a rule is triggered. For example, if a 2. Test procedure:
device uses more data than expected, - Step 1: Log into the platform using the provided account
platform should be able to switch it from a - Step 2: Direct to rate plan management portal
standard rate plan to a premium rate plan - Step 3: Create two data rate plans that are low and close to each other (for easy testing
purpose)
132
- Step 5: Set up the rule based on two rate plans that platform should automatically switch
to the higher rate plan when devices reach the limit of lower rate plan.
3. Assessment: Pass if platform automatically switch rate plan when the rule is triggered.
account
2. Test procedure:
The platform must support the ability to - Step 2: Direct to the automation/rule portal
limit or filter the devices that are subject to
16 Automation - Step 3: Pick up a few devices (SIM numbers) and set up a rule with a low threshold (for
the rule, so that an automation rule only
easily triggered purpose) that is applied only to these devices.
applies to a subset of devices
- Step 4: Monitor how the rule works
3. Assessment: Pass if:
- Other devices (not pre-chosen devices) meet the threshold and the rule is not triggered
- One device in the pre-chosen devices set meets the threshold and the rule is triggered
17 Automation The platform must support automation 1. Pre-set Condition: Proposal documents provided by vendor, installed platform, a user
based on the following special rules: account
+ Session Start, Session End Notify when a 2. Test procedure:
device begins or closes connection to the - Step 1: Log into the platform using the provided account
wireless network - Step 2: Direct to the automation/rule portal
+ CDR Streaming - Step 3: Set up the rules for each scenario listed in the requirement.
+ Push raw CDR to destination URL
+ SMS-MO Received
+ Monitor SMS Usage for fraud or abuse
+ Get Notified when device sends SMS to
a specific short code
+ OTA Swap: for over-the-air SIM swaps,
133
especially with Global SIM feature
+ OTA MSISDN: sync device MSISDN
XVII General Requirements for Platform
1. Pre-set Condition: Documents provided by vendor, in which have all the detail
information about the data and control in platform and how to access them from web-
Platform All data and control found within the
based UI
1 Integration Platform must be accessible by a web-
Capability based interface
requirement
Assessment: Pass if meet the requirement.
1. Pre-set Condition: Instruction documents provided by vendor
Platform Web-based UI should be customizable to
2. Test procedure: Read and analyze the documents, follow the instruction to customize
2 Integration allow users to choose the appropriate view
the view of the web-based UI.
Capability relevant to their operational needs.
3. Assessment: Pass if the web-based UI is changeable
1. Pre-set Condition: Documents provided by vendor, in which have all the detail
Platform information of APIs and the corresponding data and controls in the platform.
All data and control found within the
3 Integration 2. Test procedure: Read and analyze the documents, pick one or two random APIs
Platform must be accessible via API
Capability related to the data in platform and use them to fetch the data.
Assessment: Pass if the data fetched using the APIs is same as the data in platform.
Platform
The platform must support Pull and Push 2. Test procedure: Read and analyze the documents, follow the instruction to test this
4 Integration
APIs requirement
Capability
1. Pre-set Condition: Instruction documents provided by vendor.
Platform The platform must support sandbox 2. Test procedure:
5 Integration environment for API testing outside of Read and analyze the documents, pick one or two random APIs to test the sandbox
Capability production environment based on the instructions in the documents.
3. Assessment: Pass if satisfy the test procedure.
134
2. Test procedure:
Platform
The platform must support to provide Read and analyze the documents, follow the instructions to test the REST APIs using
6 Integration
REST APIs testing tools/environment suggested or provided by vendor or using common testing tools
Capability
like SoapUI
2. Test procedure:
Read and analyze the documents, follow the instructions to test the XML APIs and SOAP
Platform
The platform must support to provide APIs using testing tools suggested by vendor or using common testing tools like SoapUI
7 Integration
XML APIs and SOAP APIs 3. Assessment: Pass if satisfy the test procedure.
Capability
contract.
The platform must support the capability
of integration with all Viettel connections
all over the globe, Viettel subsidiaries in
Global expansion 2. Test procedure: Read and analyze the documents, follow the instruction to test this
8 11 countries (Vietnam, Laos, Cambodia,
support requirement
Myanmar, Timor Leste, Haiti, Peru,
Tanzania, Burundi, Cameroon,
Mozambique)
1. Pre-set Condition: Proposal documents provided by supplier/bidder
Platform must support Multilingual (at
9 Multilingual least Vietnamese and English) and have
requirement
method to add new language into system.
9 Delivery and The platform must support fully delivered 1. Pre-set Condition: Proposal documents provided by vendor
Product Release as a hosted service or on premise, Private 2. Test procedure: Read and analyze the documents, follow the instruction to test this
Cycle Cloud or hybrid cloud requirement
135
The platform must not have any single 1. Pre-set Condition: Proposal documents provided by vendor
Delivery and
point of failure and ensure IoT services 2. Test procedure: Read and analyze the documents, follow the instruction to test this
10 Product Release
will not be interrupted by a single failure requirement
Cycle
for 99.999% of time. 3. Assessment: Pass if meet the requirement
Delivery and
The life span of the hardware equipments
12 Product Release Commitment of vendor
of the platform is at least 4 years
Cycle
Delivery and
The minimum warranty time for the whole
13 Product Release Commitment of vendor
system (hardware and software) ≥ 01 year
Cycle
Delivery and The minimum time the vendor commit to
14 Product Release provide technical support service (after Commitment of vendor
Cycle warranty time) ≥ 03 year
1. Pre-set Condition: Installed platform, a user account
2. Test procedure:
The platform must support connectivity - Step 1: Log into the platform using the provided account
Connectivity - Step 2: Direct to the analytic portal/feature
15 analytic provided based on the conditions
Analytics
of networks - Step 3: View the connectivity analytic charts and compare to the conditions of networks.
- Step 4: Change status of some connectivity and see the change in the charts.
3. Assessment: Pass if platform has the analytic chart reflects the condition of network
The platform must support the ability to 2. Test procedure: Read and analyze the documents, follow the instruction to test this
16 Cloud supporting
route to cloud storage services requirement
17 Backup Application protection at the level of N+1 1. Pre-set Condition: Proposal documents provided by vendor
(for the whole system) to ensure that even 2. Test procedure: Read and analyze the documents, follow the instruction to test this
136
when one node down, the application still requirement
running on other nodes. 3. Assessment: Pass if meet the requirement
Server protection at the level of N+1 (for 1. Pre-set Condition: Proposal documents provided by vendor
the whole system) to ensure that even 2. Test procedure: Read and analyze the documents, follow the instruction to test this
18 Backup
when one node down, the platform still can requirement
run normally on other nodes. 3. Assessment: Pass if meet the requirement
The original data and backup data is stored
in separated storage (Storage protection at
19 Backup the level of N+1) to ensure that data is
requirement
always availability even when 01 storage
system got errors.
The availability of hardware and software 2. Test procedure: Read and analyze the documents, follow the instruction to test this
20 Availability
for the whole system ≥ 99.99% requirement
Response time ≤ 100 ms for at least 99%
of messages (only considering the time the
21 Response time messages is routing within the platform,
requirement
not include the time messages are routing
via radio access network)
1. Pre-set Condition: Platform's setup file, private cloud ready to install platform
provided by Viettel.
Viettel can install many tenants of platform 2. Test procedure:
22 License model
as needed (the minumum is 22 tenants). - Step 1: Install two platform tenants into the private cloud provided by Viettel .
- Step 2: Using two accounts created while installing to log into two platform tenants.
3. Assessment: Pass if the platform two tenants works properly after installing
Deployment The Platform should support On Premises 1. Pre-set Condition: Platform's setup file, hardware system or private cloud ready to
23
model and Private Cloud deployment by installed install platform provided by Viettel.
137
2. Test procedure:
in Viettel data center, or Viettel's Customer - Step 1: Install the platform into hardware system or private cloud provided by Viettel.
Premises. - Step 2: Using the account created while installing to log into the platform.
3. Assessment: Pass if the platform works properly after installing
The Platform should be operated by
24 Operation model Commitment of vendor
Viettel.
The Platform should be used under Viettel
25 Brandname Commitment of vendor
Brand name.
The Platform must have the hardware
ready to support at least 180.000
subscribers with the following 1. Pre-set Condition: Proposal documents provided by vendor
requirements: 2. Test procedure: Read and analyze the documents, follow the instruction to test this
26 Capacity
- Updates their usage information at least requirement
once per 15 minutes. 3. Assessment: Pass if meet the requirement
- Support at least 2500 concurrent network
connections per second.
The system must support the integration
with AEP - Application Enablement
Platform that Viettel has plan to deploy
that may include but not limited to AEP by
Thingworx, Nokia IMPACT, Yodiwo, 1. Pre-set Condition: Proposal documents provided by vendor
ZTE, IBM, Ayala. 2. Test procedure: Vendor publish their APIs and interworking with the AEP side to
27 AEP Integration integrate their platform to AEP.
The system must publish its APIs for
3. Assessment: Pass if user can see the information (connectivity status, billing
intergration including but not limited to:
information, subscription information) and can send SMS to SIM using the AEP platform.
- Get connectivity status
- Get billing information
- Get subscription information.
138
In case the vendor of CMP or AEP have
update or upgrade, the existing CMP
vendor must support to cooperate for the
Future proof of
future integration with the new version of
28 AEP Commitment of vendor
AEP. Viettel has the right to choose the
interworking
standards, methods that both CMP and
AEP vendor must follow for the successful
integration of CMP and AEP
Platform can automatically increase the
29 Auto scaling capacity of the system when the load
requirement
increases.
Platform must have the ability to update or
30 Hot maintenance turn off some nodes in the system without
requirement
affecting the overall system.
Every node in the system has load
31 Load balancing balancing feature so that the load can be
requirement
share to many other nodes.
Platform must have the ability to log every
32 Logging errors, user actions, system actions for
requirement
trouble shooting purpose later.
Platform must have interface to view all 1. Pre-set Condition: Proposal documents provided by supplier/bidder
Server the server in the system with information 2. Test procedure: Read and analyze the documents, follow the instruction to test this
33
monitoring such as load, status, errors and has tools to requirement
troubleshoot when errors happen. 3. Assessment: Pass if meet the requirement
139
Platform must have interface to view load 2. Test procedure: Read and analyze the documents, follow the instruction to test this
34 Node monitoring
and status of all nodes in the system. requirement
Platform must support mail and SMS
notification when abnormal events in the
35 Notification system happen.
requirement
User can easily define abnormal events and
configure who can receive notification.
-System load of servers and other network
devices of the system when running with
the maximum number of subscibers
(180,000 subscribers) must meet the
following criteria:
+Device for storing data: IOPS ≤ 80%,
36 System load hard disk space usage ≤80%
requirement
+Network device: Number of ports used
and device throughput ≤80%.
In case equipment is deployed active-
active redundancy model, even if one of
the equipment is faulty and stop operation,
the remaining equipment must meet the
system load parameters as above.
II. Pre - Acceptance Test for Application Enablement Platform (AEP)
140
ID Function Description Measurement method
Functional requirements
1. Device Management
1.1 Device's information management
1. Pre-set Condition: Installed platform, a user account and a device
(virtual or real device) that is turned on.
2. Test procedure:
- Step 1: Log into the platform (web-based portal or mobile app) with
the provided account.
Platform must provide a GUI (web portals, mobile apps) - Step 2: Check if the device is automatically available in platform or
General information
1.1.1 or APIs to manage the general information of the device provide a method to find the device
management
such as name, producer, id - Step 3: Check if the general information of device (name, producer) is
shown in platform
- Step 4: Check if the general information of device can be updated.
- Step 5: Delete the device, check if the device can be deleted
- Step 6: Repeat from step 2 to step 4 for 5 times with different outputs.
1.1.2 Device template Platform has the ability to manage device templates (all 1. Pre-set Condition: Installed platform and a user account
management the device's specifications such as the general 2. Test procedure:
information of the device, device's attributes and - Step 1: Log into the platform (web-based portal or mobile app) with
device's commands). the provided account.
New device can be created based on the pre-defined - Step 2: Create a device template with pre-defined specification
device template. including general information (name, id), device's attribute and device’s
command.
- Step 3: Update the device template including general information
(name, id), device’s attribute and device’s command.
- Step 4: Create a new device based on the device template in step 3.
- Step 5: Delete the device template
141
1. Pre-set Condition: Installed platform, an admin account and two
different User accounts
2. Test procedure:
the admin account.
Platform has the ability to group devices into collections - Step 2: Group devices that are available in platform (virtual or real
ID Function by different criteria such as location, device type.
Description devices) into two collections and assign method
Measurement them to two provided User
Device collection
1.1.3 These collections can be organized into data structure accounts
management
such as tree, list and also can be assigned with their own - Step 3: Log out of the admin account
roles, rules and users. - Step 4: Log into each User account to check if they can see the
collection that is assigned to them.
3. Assessment: Pass if:
- Successfully groups devices into collections
- Each account see its assigned collections
1. Pre-set Condition: Installed platform, a user account has been
created
2. Test procedure:
- Step 1: Log into the platform (web-based portal) with the user account.
Platform have to show the location of devices on the
- Step 2: Create a device with location data.
Device location map, support at least Google Map.
1.1.4 - Step 3: Move to the device information page or create a dashboard with
management Pal form also have to provide a method to add new map
map
or change the map if necessary.
- Step 4: Open the map, and view the location of the device on the map.
- Step 5: Repeat from step 2 to step 4 for 5 times.
3. Assessment: Pass if successfully view the location of the device on
the map.
1.1.5 Device version and Platform has the ability to manage the information of 1. Pre-set Condition: Installed platform, a user account has been
firmware version and firmware of the device. created
management Platform also can change and update the firmware 2. Test procedure:
142
- Step 2: Create a device with firmware
- Step 3: View the firmware version of the device
- Step 4: Update the firmware of the device from the platform
directly and remotely when needed.
ID Function Description - Step 5: View the new firmware version.method
Measurement
3. Assessment: Pass if successfully update and view the firmware
version.
1.2 Device's data management
created
2. Test procedure:
Platform has the ability to store the real time data of the - Step 2: Create a device.
Real time data
1.2.1 device, allow access the data in real time via User - Step 3: Use a testing tool to send device data to the cloud.
management
Interface (UI) or APIs. - Step 4: View the data on a User Interface
- Step 5: Use a test tool to call the API and view the data.
3. Assessment: Pass if successfully send the data and view the data via
UI and test tool.
1.2.2 Historical data Platform has the ability to store historical data of the 1. Pre-set Condition: Installed platform, a user account has been
management device in storage for at least 1 months, allow access the created
data via UI and APIs. 2. Test procedure:
- Step 2: Create a device.
- Step 3: Use a testing tool to send device data to the platform.
- Step 4: View the historical data on a User Interface.
- Step 5: Use a test tool to call the API and view the historical data.
3. Assessment: Pass if successfully send the data and view the data via
143
UI and test tool.
1.3. Device' status Management
created
2. Test procedure:
- Step 2: Create a device and connect it to the Platform
Device connectivity Platform can monitor the connectivity status of the
1.3.1 - Step 3: Periodically send data from the device to the Platform.
status Management devices such as online, offline.
- Step 4: Shut down the connection between the device and the Platform.
- Step 5: After some minutes, the status of the device change to offline.
3. Assessment: Pass if the status of the device successfully change to
offline after shutting down the connection.
1. Pre-set Condition: Installed platform, and user account has been
created
2. Test procedure:
- Step 2: Create a device and connect it to the Platform
- Step 3: Create an error on the device
Device status Platform can monitor the status of the device including - Step 4: After some minutes, the status of the device change to error.
1.3.2
management but not limited to: error, operation status, battery levels - Step 5: Create device’s battery level attribute
- Step 6: Wait for battery runs low,
- Step 7: After some minutes, the battery level of the device change to
low.
3. Assessment: Pass if the status of the device successfully change to
offline after shutting down the connection.
1.4. Device Controlling and updating
1.4.1 Device Controlling Platform support user to use commands to control 1. Pre-set Condition: Installed platform, a user account has been
devices via UI and APIs created
144
2. Test procedure:
- Step 2: Create a device with a controlling function.
- Step 3: Move to the device information page or predefined dashboard
- Step 4: Send a command to the device.
- Step 5: The device executes the command
3. Assessment: Pass if successfully send a command to the device.
ID Function Description created Measurement method
2. Test procedure:
- Step 2: Create a device with a configuration.
Device configuration Platform support user to view and update the device's
1.4.2 - Step 3: Move to the device information page
updating configurations via UI and APIs.
- Step 4: Update the configuration of the device.
- Step 5: Check if configuration of the device is updated successfully.
- Step 5: Repeat from step 4 to 5 for 5 times.
3. Assessment: Pass if successfully update the configuration of the
device.
1.5 Device integration
1. Pre-set Condition: Proposal documents provided by supplier/bidder.
2. Test procedure:
Platform has security mechanism to guarantee that only
Supplier/bidder show the technical document about the security
1.5.1 Security authorized devices can connect to the system and can
mechanism that show how the system can be protected from
kick abnormal devices out of the system.
unauthorized device, and can block abnormal device from the system.
1.5.2 Protocol integration Platform has a method to add new Adapter, Software 1. Pre-set Condition: Instruction documents provided by
Gateway or similar technology in order to integrate new supplier/bidder.
protocols, standards into the system. It should be done 2. Test procedure:
by programming the adapter or by using a scripting Supplier/bidder show the instruction document of how to integrate a new
145
device with new protocol into the system.
language.
created
2. Test procedure:
- Step 2: Create a device with HTTP Standard.
ID Function Description - Step 3: Send a messageMeasurement
from the devicemethod
Standards
1.5.3 Platform support at least standards: HTTP, MQTT - Step 4: Check if the message is stored in the Platform successfully.
conformance
- Step 5: Create a device with MQTT Standard.
- Step 6: Send a message from the device
- Step 7: Check if the message is stored in the Platform successfully.
3. Assessment: Pass if successfully send and store the message to the
Platform
2. Application Enablement
2.1. Automated scenario
2.1.1 Time trigger Platform allows user to create scenarios based on time so 1. Pre-set Condition: Installed platform, a user account has been
that at a predefined time, the system does some tasks created
including but not limited to: sending SMS, sending mail, 2. Test procedure:
controlling the device, send command to the outside - Step 1: Log into the platform (web-based portal) with the user account.
system. - Step 2: Create a time trigger with a predefined time and a sending SMS
action.
- Step 3: A SMS is sent when the predefined time comes.
- Step 4: Create a time trigger with a predefined time and a sending
email action.
- Step 5: An email is sent when the predefined time comes.
command to device action.
- Step 7: A command is sent to the device when the predefined time
146
comes.
command to outside system action.
- Step 9: A command is sent to outside system when the predefined time
comes.
3. Assessment: Pass if successfully execute the actions.
created
2. Test procedure:
- Step 2: Create a location trigger with a predefined location and a
sending SMS action.
- Step 3: A SMS is sent when the device enters and exits predefined
ID Function Description location. Measurement method
Platform allows user to create scenarios based on - Step 4: Create a location trigger with a predefined location and a
location so that when a device enters or exits an area sending email action.
(predefined on the map), the system does some tasks - Step 5: An email is sent when the device enters and exits predefined
2.1.2 Location trigger
including but not limited to: sending SMS, sending mail, location.
controlling the device, send command to the outside - Step 6: Create a location trigger with a predefined location and a
system. sending command to device action.
- Step 7: A command is sent to the device when the device enters and
exits predefined location.
- Step 8: Create a location trigger with a predefined location and a
sending command to outside system action.
- Step 9: A command is sent to outside system when the device enters
and exits predefined location.
3. Assessment: Pass if successfully execute all the actions.
2.1.3 Automation scenario Platform allows user to create automation scenarios, on 1. Pre-set Condition: Installed platform, a user account has been
which system or devices react when one or more devices created
147
2. Test procedure:
- Step 2: Create a device
- Step 4: Create a threshold for a device's attribute and sending SMS
action
- Step 5: A SMS is sent when the device attribute exceed the threshold
- Step 6: Create a threshold for a device's attribute and sending email
meet some criteria. For instance, when a device's
action
attribute exceed the predefined threshold, system
- Step 7: An email is sent when the device attribute exceed the threshold
automatically does some tasks including but not limited
- Step 8: Create a threshold for a device's attribute and sending
to: sending SMS, sending email, controlling the device
command to device action
and other devices and sending command to outside
- Step 9: An command is sent to a device when the device attribute
system.
ID Function Description exceed the threshold Measurement method
- Step 10: Create a threshold for a device's attribute and sending
command to outside system action
- Step 11: An command is sent to an outside system when the device
attribute exceed the threshold
3. Assessment: Pass if successfully execute the actions.
Platform allows user to create complicated business 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
process flows in order to handle the business flow from 2. Test procedure:
Business process the device through many user's predefined steps. The Supplier/bidder show the technical document that describes the business
2.1.4
flow management output of the data in each step decides which actions will process flow of the system. Follow the document to create a new flow
be taken by the system such as controlling other devices, that can control device, interact with outside system.
interact with outside system. 3. Assessment: Pass if satisfy the test procedure.
2.2. Dashboard
2.2.1 Flexible dashboard User can create flexible dashboard without coding: 1. Pre-set Condition: Installed platform and a user account
- Inputs of dashboard including but not limited to: 2. Test procedure:
device's real time data, device historical data, data from - Step 1: Log into the platform (web-based portal or mobile app) with
other system. the provided account.
148
- Step 2: Direct to the dashboard portal
- Step 3: Setup the input data for the charts in dashboard (device's real
time, device historical data, and data from other system)
- Can organize charts into group.
- Step 4: Organize (drag-drop) charts in dashboard in one specific order.
- Can drag-drop the charts into flexible layout.
- Step 5: Change the size, layout of dashboard
2.2.2 Dashboard reflect User can create dashboard reflect the locations of the 1. Pre-set Condition: Installed platform and a user account
real map devices in real map or in user-defined map. 2. Test procedure:
+ With real map:
- Step 2: Direct to the dashboard portal that support real map
- Step 3: Add the devices with locations to the map to see how it reflects
in the map.
- Step 4: Change the locations of devices to see how it reflects in the
ID Function Description map. Measurement method
- Step 5: Delete 1 or 2 devices to see how it reflects in the map.
+ With user-defined map:
- Step 2: Direct to the dashboard portal
- Step 3: Insert a user-defined map into the dashboard
- Step 4: Add the devices with locations to the user-defined map to see
how it reflects in the map.
- Step 5: Change the locations of devices to see how it reflects in the
user-defined map.
- Step 6: Delete 1 or 2 devices to see how it reflects in the user-defined
map.
149
3. Assessment: Pass if satisfy one of two maps (real map or user-defined
ID Function Description map) Measurement method
2.3. Application Enablement
1. Pre-set Condition: Installed platform, and user account.
2. Test procedure:
- Step 2: Direct to the device simulation portal/area.
Device Simulation Platform has tools to simulate the devices for developing - Step 3: Create a virtual device and set up its attributes (for instance, a
2.3.1
tools application without real devices. light with name, id, status, dimming level)
- Step 4: Update/change the attributes of this device and see the
differences.
- Step 5: Delete the device.
- Step 6: Repeat from step 3 to step 5 for 5 times with different inputs.
2.4. API management
Platform must have APIs for application to connect, use
1. Pre-set Condition: Proposal documents about APIs and method to
and gather information. The APIS are including but not
test APIs from supplier/bidder (Web-based document, pdf files)
limited to:
2.4.1 Developer API 2. Test procedure: Read and analyze documents, pick 5 random APIs
- Device management APIs
to test based on the document provided by supplier/bidder
3. Assessment: Pass if all 5 APIs work properly
2.4.2 API Specification Platform has detailed specifications for each API on the 1. Pre-set Condition: Installed platform, a user account
system, and those specifications can be easily modified. 2. Test procedure:
- Step 2: Direct to the APIs documents portal/feature.
- Step 3: Pick an API document to see it has content.
- Step 4: Change the content of this API
150
1. Pre-set Condition: Installed platform, a user account, document with
detail information on how to integrate new API into platform provided
Platform allows users to integrate their own APIs into by supplier/bidder.
ID Function Description
the system. 2. Test procedure: Measurement method
2.4.3 User's APIs - Step 1: Log into the platform (web-based portal or mobile app) with
- Step 2: Follow the instruction of the documents to integrate new API
into platform.
1. Pre-set Condition: Installed AEP platform, and user account.
2. Test procedure:
- Step 2: Direct API usage management portal/feature.
User can view/read the usage of the APIs including but - Step 3: Check if the result of API usage (number of API call, result of
2.4.4 API usage not limited to: number of API call, result of API call API call and successful rate) is available in the portal.
(success or fail), and successful rate. 3. Assessment: Pass if satisfy every steps
Note: If the platform does not have API usage management portal,
supplier/bidder must provide methods to calculate the API usage or
guarantees to provide this function without any additional charge within
06 months since the effective date of the contract and will be tested
before the FAC..
1. Pre-set Condition: Instruction documents provided by
supplier/bidder.
Platform must provide security mechanism to ensure that
2. Test procedure:
2.4.5 Security only authorized user can access to the corresponding
Read and analyze the documents, follow the instructions to create an
APIs.
API that only authorized user can access.
2.4.6 Protocol Platform support at least RESTful protocol. 1. Pre-set Condition: Instruction documents provided by
151
supplier/bidder.
2. Test procedure:
Read and analyze the documents, follow the instructions to test the
ID Function Description RESTful service using testing tools suggested
Measurement by supplier/bidder or
method
using common RESTful testing tools like Postman.
3. Analytic Platform
3.1. Storage
supplier/bidder.
Platform has the ability to store data in big data storage 2. Test procedure:
3.1.1 Big data storage and must provide tools or APIs to access and query the Read and analyze the documents, follow the instructions to manipulate
data. the data in big data storage (fetch, search) using data tools or API
suggested by the supplier/bidder in the documents
supplier/bidder.
Platform has the ability to store time series data and 2. Test procedure:
3.1.2 Time series database must provide tools or APIs to quickly access, query and Read and analyze the documents, follow the instructions to manipulate
search the data. the data in time series database (fetch, search) using data tools or API
suggested by the supplier/bidder in the documents
supplier/bidder.
Platform has the ability to manage real time data 2. Test procedure:
3.1.3 Real time data streaming and provide tools or APIs to access, query and Read and analyze the documents, follow the instructions to manipulate
manipulate the data. the real time data (fetch, search) using data tools or API suggested by the
supplier/bidder in the documents
152
3.2. Processing
1. Pre-set Condition: Proposal documents provided by supplier/bidder,
user account, installed platform.
2. Test procedure:
ID Function Platform has the ability to analyze the system's data
Description the provided account. Measurement method
3.2.1 Statistics using statistical methods and provide a dashboard/chart - Step 2: Direct to the dashboard/chart system that provide analytic
system to visually view the analytic results. results
- Step 3: Read and analyze the documents, compare the analyze method
and results to the analytic results in the dashboard/chart system.
3. Assessment: Pass if the Platform dashboard can show the right
analytic results.
supplier/bidder
Platform provides a method to search for specific pattern 2. Test procedure: Read and analyze the documents, follow the
3.2.2 Data analytic
in data and notify users about abnormal events. instruction to search for specific pattern and notify user about abnormal
event.
supplier/bidder
Platform provides tools for user to build the data
3.2.3 Customized analytic 2. Test procedure:
analytical features by themselves.
Follow the instruction to build a new data analytical feature
Platform allows user to build statically model based on supplier/bidder
3.2.4 Predictive historical data and then predict the trend of data and 2. Test procedure: Read and analyze the documents, follow the
future event. instruction to test this requirement
3.2.5 Real time processing Platform provides a method to search for the specific 1. Pre-set Condition: Instruction documents provided by
pattern in flow of real time data and notify users about supplier/bidder
153
2. Test procedure: Read and analyze the documents, follow the
abnormal events. instruction to test this requirement
ID Function Description 1. Pre-set Condition: Instruction documents

Measurement provided by
method
supplier/bidder
Platform provides search engine to quickly search in big
3.2.6 Search engine 2. Test procedure: Read and analyze the documents, follow the
data.
instruction to test this requirement
supplier/bidder
Platform provides rule engine to process the data flow so
3.2.7 Rule engine 2. Test procedure: Read and analyze the documents, follow the
that the user can define rules to process the data.
3.3. Integration
Platform has the ability to send data to the outside Big
supplier/bidder
3rd Big data Platform data Platform to process externally. It should be done by
3.3.1 2. Test procedure: Read and analyze the documents, follow the
integration sending directly in real time from the Platform or
sending indirectly via storage.
supplier/bidder
Data Source Platform allows user to input the data from various
3.3.2 2. Test procedure: Read and analyze the documents, follow the
Integration sources: devices, external system.
Platform allows user to input the data from various supplier/bidder
Data Source
3.3.3 datasets including but not limited to: Excel file, csv, 2. Test procedure: Read and analyze the documents, follow the
Integration
database file instruction to test this requirement
154
4. Additional Services
4.1. Map
1. Pre-set Condition: Installed platform, proposal documents from
supplier/bidder and a user account
2. Test procedure:
+ Test the built-in map:
Platform provide a ready-to-use map and provide a way
4.1.1 Map to integrate other maps to the system including but not
- Step 2: Direct to the dashboard portal that has built-in map
limited to Viettel map, Google map.
- Step 3: Check the map
+ Test the map integration:
Read and analyze the documents, follow the instruction to integrate a
map to platform.
3. Assessment: Pass if meet the requirements
4.2 Communication
supplier/bidder
4.2.1 SMS Platform must have method to send SMS in Vietnam 2. Test procedure: Read and analyze the documents, follow the
supplier/bidder
4.2.2 Mail Platform must have method to send email 2. Test procedure: Read and analyze the documents, follow the
5. Platform on the Edge
5.1. Device Management
5.1.1 Device management Platform has the ability to manage information of 1. Pre-set Condition: Installed edge platform, a user account has been
devices connecting to gateway. created
155
2. Test procedure:
- Step 1: Log into the edge platform.
- Step 2: View information of all device that connects to the gateway.
- Step 3: Add a device from the gateway
- Step 4: Remove a device from the gateway
3. Assessment: Pass if successfully view/add/remove the device.
ID Function Description 1. Pre-set Condition: Installed edge platform,

Measurement methoda user account has been
created
2. Test procedure:
- Step 1: Log into the edge platform.
Connectivity Platform must support popular connectivity standard
5.1.2 - Step 2: Create and connect a WiFi device
Standard including but not limited to: WiFi, Bluetooth, ZigBee.
- Step 3: Create and connect a Bluetooth device
- Step 4: Create and connect a ZigBee device
3. Assessment: Pass if successfully create and connect the devices.
5.2 Cloud Integration
1. Pre-set Condition: Installed edge platform, a user account has been
created
2. Test procedure:
- Step 1: Create a device and connect the gateway
Platform has the ability to connect to Cloud and receive
Cloud integration - Step 2: Send a message from the device to the gateway to the Cloud by
5.2.1 commands from Cloud using international message
standard MQTT Protocol
standard including but not limited to MQTT.
- Step 3: Send a message from the Cloud to the gateway by MQTT
protocol to the device
3. Assessment: Pass if successfully send the message.
5.2.2 Multiple Cloud IoT Platform has the ability to connect to different IoT Cloud 1. Pre-set Condition: Instruction documents provided by
Platform Supporting environments. This should be done by programming the supplier/bidder.
adapter or using simple script language. 2. Test procedure:
156
Supplier/bidder show the tutorial of how to connect the gateway to
different IoT Cloud.
ID Function Description Measurement
3. Assessment: Pass if satisfy method
the test procedure.
5.3. Data processing
created
2. Test procedure:
- Step 1: Create a device and connect to the gateway
Temporarily data Platform has the ability temporarily store data from - Step 2: Send a message from the device to the gateway
5.3.1
storage devices while there is no connection to the server. - Step 3: The message is store locally in the gateway.
- Step 4: View the message in the gateway.
3. Assessment: Pass if successfully view the temporary data in the
gateway.
created
2. Test procedure:
Platform must have schedule feature for use to control - Step 1: Log on to the gateway
5.3.2 Scheduler
the connected device - Step 2: Create a schedule to control the device
- Step 3: A command is sent to the device follow the schedule
3. Assessment: Pass if successfully send the command
5.3.3 Rule engine Platform must provide a way to process simple rules 1. Pre-set Condition: Installed edge platform, a user account has been
based on at least device's status, time in order to control created
the device 2. Test procedure:
- Step 1: Log in to the gateway
- Step 2: Create a rule based on device status
- Step 3: Create a rule based on time
- Step 4: Send a command to the device when the defined time or device
status is met.
157
ID Function Description 3. Assessment: Pass if successfully
Measurement create rules.
method
5.4. Modifiability
supplier/bidder.
Adding new Platform must have a method to add new connectivity 2. Test procedure:
5.4.1
connectivity standard standard to the gateway. Supplier/bidder show the tutorial of how to add new connectivity
standard
5.5. Management
created
2. Test procedure:
- Step 1: Log in to the gateway or Cloud Platform
User can remotely update the software and firmware of
5.5.1 Remote update - Step 2: View the firmware version of the IoT Gateway
the IoT gateway.
- Step 3: Update a new firmware version of the IoT Gateway
- Step 4: View the new firmware version of the IoT Gateway
3. Assessment: Pass if successfully update the firmware.
created
2. Test procedure:
User can monitor all the IoT gateway connecting to IoT
- Step 1: Log on to the gateway
Platform from an administrator interface. Administrator
5.5.2 Monitoring - Step 2: View all the information, status, event, configuration of the IoT
should visually see all the information, status, events,
Gateway.
and configurations of the IoT gateway.
- Step 3: Repeat step 2 for 3 times.
3. Assessment: Pass if successfully view all the information of the IoT
gateway
5.5.3 Remotely configure User can remotely configure the IoT gateway. 1. Pre-set Condition: Installed edge platform, a user account has been
158
created
2. Test procedure:
- Step 1: Log in to the gateway
- Step 2: View the configuration
- Step 3: Update the configuration of the IoT gateway
- Step 4: View the new configuration
3. Assessment: Pass if successfully update the configuration.
created
2. Test procedure:
Platform has the ability to log every error, event, action - Step 1: Log in to the gateway
5.5.4 Logging
for administrator to remotely troubleshoot. - Step 2: View all the event, action, error that occurred.
- Step 5: Repeat step 2 for 3 times.
3. Assessment: Pass if successfully view all the event, action, error that
occurred
2. Test procedure:
Platform can run on popular OS including but not
5.5.5 OS support Supplier/bidder show the Proposal that describe all the requirement
limited to: Window , Linux and Android
about the supported OS.
6. Developer environment
6.1 Developer Portal
1. Pre-set Condition: Installed platform, two different users.
2. Test procedure:
- Step 1: Log in to the platform with two different users simultaneously
Many company can develop separated IoT Applications
6.1.1 Multi-tenant - Step 2: Both users do some actions with the platform (call APIs, view
on the same environment.
dashboard)
3. Assessment: Pass if both users can function properly at the same
time.
159
1. Pre-set Condition: Installed platform, company's administrator
account.
2. Test procedure:
- Step 1: Log in to the platform with company's administrator account
Platform must have the ability to create administrator - Step 2: Direct to the user management portal/feature
Company
6.1.2 account for each company. This account can manage the - Step 3: View the resources, applications, developers.. of the company.
management
resources, applications, developers of the company. - Step 4: Pick one developer and update the information of this
developer and see if it change properly
- Step 5: Delete the developer.
- Step 6: Repeat from step 4 to step 5 5 times.
3. Assessment: Pass if satisfy every steps.
1. Pre-set Condition: Installed platform, a company's administrator
ID Function Description account. Measurement method
2. Test procedure:
- Step 3: Create three developer users.
Platform must have the ability to manage the developers
- Step 4: Update the 3rd user information and see if it change properly.
Developer in one company. The Developer Portal should be able to
6.1.3 - Step 5: Delete the 3rd user.
management create different account for different developers and
- Step 6: Assign a specific application to 1st user.
each account has it owned assigned roles, resources.
- Step 7: Log out and log in using 1st user. This user must see the
application that is assigned to him.
- Step 8: Log out and log in using 2nd user. This user must not see the
application that is assigned to 1st user.
- Step 9: Repeat from step 3 to step 8 three times.
6.1.4 Application Platform must have Developer Portal in which user can 1. Pre-set Condition: Installed platform, a company's administrator
management manage the list of applications belong to one company, account, a developer user.
and can assign developers for each application. 2. Test procedure:
- Step 2: Direct to the application management portal/feature
160
- Step 3: Create two applications
- Step 4: Update the 2nd application's information and see if it change
properly.
- Step 5: Delete the 2nd application.
- Step 6: Assign the developer user to the 1st application.
- Step 7: Log out and log in using the developer user. This user must see
ID Function Description the application that is assigned to him. method
Measurement
- Step 7: Repeat from step 3 to step 7 three times.
Platform must have permission management mechanism
Permission 2. Test procedure: Read and analyze the documents, follow the
6.1.5 so that company, developer, application can only access
management instruction to test this requirement
to assigned data.
Platform must have the ability to separate the 1. Pre-set Condition: Proposal documents provided by supplier/bidder
development environment and production environment, 2. Test procedure: Read and analyze the documents, follow the
6.1.6 Release management
and have method to migrate the data between instruction to test this requirement
development environment and production environment. 3. Assessment: Pass if meet the requirement
6.2. Developer SDK
Platform must have Software Development Kit (SDK)
6.2.1 Developer SDK for developers to develop software on devices. The SDK
can have many form such as library, software agent.
Compatible with Platform's SDK can run on popular hardware kit 2. Test procedure: Read and analyze the documents, follow the
6.2.2
devices including but not limited to Arduino, Rasberry Pi. instruction to test this requirement
6.3. Billing
6.3.1 Billing information Platform must have the ability to store the billing 1. Pre-set Condition: Proposal documents provided by supplier/bidder
information such as number of requests, number of 2. Test procedure: Read and analyze the documents, follow the
161
devices for billing purpose.
ID Function Description 3. Assessment: Pass if meet the requirement
Measurement method
Non Functional requirement
1. Architecture
Platform must have the ability to deploy into flexible 2. Test procedure: Supplier/bidder show the proposal documents that
Deployment
1.1 deployment architectures including on premise, public describe in fully detail about three deployment architecture: on premise,
Architecture
cloud and private cloud. public cloud and private cloud.
1. Pre-set Condition: Platform setup file, instruction documents from
supplier/bidder, virtual infrastructure and installed VMware and
OpenStack provided by Viettel, or Kubernetes or vendor provide their
Platform must support at least VMWare and OpenStack, own IaaS Platform free of charge
IaaS infrastructure
1.2 or Kubernetes or vendor provide their own IaaS 2. Test procedure:
support
Platform free of charge. Supplier/bidder install the platform into VMWare and OpenStack
hypervisor, or Kubernetes or vendor’s own IaaS Platform.
3. Assessment: Pass if successfully installed into VMWare and
OpenStack hypervisor, or Kubernetes or vendor’s own IaaS Platform.
2. Modifiability
White label interface allow user easily modify to embed 2. Test procedure: Read and analyze the documents, follow the
2.1 White label interface
Viettel brand image into the platform. instruction to test this requirement
supplier/bidder.
User can use built-in script language to modify data 2. Test procedure:
2.2 Scripting
flows from outside system to the platform Read and analyze the documents, follow the instructions to use built-in
script to modify the data flows from outside system to platform
162
supplier/bidder.
Platform must have APIs or other methods to get data
2. Test procedure:
(both real time data and stored data) from system to
2.3 Data access Read and analyze the documents, follow the instructions to manipulate
external system for further processing such as data
the data (real time or in storage) from system to external system using
analytic.
ID Function Description data tools or API suggested by the supplier/bidder
Measurement method in the documents
Platform must support Multilingual (Vietnamese and
2.4 Multilingual English) and have method to add new language into
system.
3. Integration
Platform must have the ability to integrate many kinds of 1. Pre-set Condition: Proposal documents provided by supplier/bidder
devices by adding adapter to convert the data from the 2. Test procedure: Read and analyze the documents, follow the
3.1 Device Integration
device, adapter should be added by programming or instruction to test this requirement
scripting language. 3. Assessment: Pass if meet the requirement
Platform must integrate with the CMP (Connectivity
Management Platform) that Viettel paln to deploy using
the APIs that is provied by CMP side. APIs including
but not limited to: 1. Pre-set Condition: Proposal documents provided by supplier/bidder
- Get connectivity status 2. Test procedure: Supplier/bidder integrate their platform to CMP of
3.2 CMP Integration
- Get billing information Viettel
- Get subscription information. 3. Assessment: Pass if meet the requirement
Platform must provide a GUI for user to view these
information and send SMS to SIM.
3.3 CMP Integration Supplier/bidder must maintaince the integration between Commitment from supplier/bidder.
future commitment the Platform and the CMP within the technical support
time (at least 3 years). In case there is an intergration
problem in the future that two sides (AEP and CMP) can
163
not handle (Example: new CMP version with new
standards and APIs and AEP side can not integrate),
Viettel will provide the integration rules and two sides
have to follow these rules until succesful integration.
1. Pre-set Condition: Proposal method
documents provided by supplier/bidder
VMS integration Platform must have the ability to integrate Video 2. Test procedure: Supplier/bidder integrate their platform to Video
3.4 (Video management management system or streaming server and allow user management system or streaming server and provide a dashboard to
System) to view video on the dashboard. show the video to user.
Platform must have the ability to integrate with
Other system 2. Test procedure: Supplier/bidder integrate their platform to
3.5 integration frameworks which support REST API and
Integration integration framework.
MQTT
4. Operability
Administrator can deploy the topology of the system,
4.1 Auto deployment add or remove node easily via the platform's built-in
interface.
Platform can automatically increase the capacity of the 2. Test procedure: Read and analyze the documents, follow the
4.2 Auto scaling
system when the load increases. instruction to test this requirement
Platform must have the ability to update or turn off some 2. Test procedure: Read and analyze the documents, follow the
4.3 Hot maintenance
nodes in the system without affecting the overall system. instruction to test this requirement
5. Availability
5.1 Load balancing Every node in the system has load balancing feature so 1. Pre-set Condition: Proposal documents provided by supplier/bidder
that the load can be share to many other nodes. 2. Test procedure: Read and analyze the documents, follow the
164
ID Function Description 1. Pre-set Condition: Proposal documents

Measurement provided by supplier/bidder
method
Every node in the system has back up mechanism (active
5.2 Back up standby or active active), so that if one node goes down,
the system still runs smoothly.
6. Capacity
Every node in the system can increase the capacity such 2. Test procedure: Read and analyze the documents, follow the
6.1 Scale out
as storage by adding more servers. instruction to test this requirement
Can add more devices by scaling out the system (adding 2. Test procedure: Read and analyze the documents, follow the
6.2 Device capacity
more servers). instruction to test this requirement
7. Monitoring
Administrator can visually monitor overall of the system 1. Pre-set Condition: Proposal documents provided by supplier/bidder
including all the nodes (including but not limited to web 2. Test procedure: Read and analyze the documents, follow the
7.1 Topology monitoring
server, database, and proxy), configurations of the nodes instruction to test this requirement
and relationship between nodes. 3. Assessment: Pass if meet the requirement
Platform must have the ability to log every errors, user
7.2 Logging actions, system actions for trouble shooting purpose
later.
Platform must have interface to view all the server in the
7.3 Server monitoring system with information such as load, status, errors and
has tools to troubleshoot when errors happen.
165
Platform must have interface to view load and status of 2. Test procedure: Read and analyze the documents, follow the
7.4 Node monitoring
all nodes in the system. instruction to test this requirement
Platform must support mail and SMS notification when 1. Pre-set Condition: Proposal documents provided by supplier/bidder
abnormal events in the system happen. 2. Test procedure: Read and analyze the documents, follow the
7.5 Notification
User can easily define abnormal events and configure instruction to test this requirement
who can receive notification. 3. Assessment: Pass if meet the requirement
8. Security
Platform must have security mechanism to protect the
connection between device and Cloud, device and
8.1 Connectivity security gateway, gateway and Cloud, make sure that the data is
consistent, cannot be modified or eavesdrop by
unauthorized person.
Platform must have security mechanism to protect the 2. Test procedure: Read and analyze the documents, follow the
8.2 Cloud security
data on Cloud instruction to test this requirement
Platform must have security mechanism to protect the 2. Test procedure: Read and analyze the documents, follow the
8.3 Edge security
data on IoT gateway. instruction to test this requirement
9. Performance
The system can handle the throughput of message 1. Pre-set Condition: Proposal documents provided by supplier/bidder
coming from the devices to the cloud at least 7000 2. Test procedure: Read and analyze the documents, follow the
9.1 Throughput
messages per second, and can increase the throughput by instruction to test this requirement
adding more server. 3. Assessment: Pass if meet the requirement
9.2 System load -System load of servers and other network devices of the 1. Pre-set Condition: Proposal documents provided by supplier/bidder
system when running with throughput 7000 messages 2. Test procedure: Read and analyze the documents, follow the
166
per second (messages coming from the devices to the
cloud) must meet the following criteria:
+Device for storing data: IOPS ≤ 80%, hard disk space
usage ≤80%
+Network device: Number of ports used and device
ID Function Description 3. Assessment: Pass if meet the requirement
Measurement method
throughput ≤80%.
In case equipment is deployed active-active redundancy
model, even if one of the equipment is faulty and stop
operation, the remaining equipment must meet the
system load parameters as above.
10. General requirement
1. Pre-set Condition: Platform's setup file, an account, additional
license and hardware ready to install platform provided by Viettel.
Viettel can expanse the platform to install at least 22
2. Test procedure:
10.1 License model instances of platform at different data centers including
- Step 1: Install the platform into hardware provided by Viettel.
Viettel's data centers or data center of Viettel's customer.
- Step 2: Log into the platform using provided account
3. Assessment: Pass if the platform works properly after installing
10.2 Operation model Platform must be operated by Viettel. Commitment of supplier/bidder
10.3 Brand name Platform must be used under Viettel Brand name. Commitment of supplier/bidder
10.4 Connectivity Platform must support NB-IoT, eMTC, LoRa 1. Pre-set Condition: Installed platform, a user account (provided by
Standard Connectivity standards supplier/bidder), infrastructures and devices that support NB-IoT,
eMTC, LoRa (provided by Viettel).
2. Test procedure:
- Step 2: Check if the platform is able to connect to the NB-IoT device.
- Step 3: Repeat from step 2 with eMTC and LoRa devices.
Note: If Viettel is not able to provide the infrastructure and devices that
167
support any of these connectivity standards, supplier/bidder must
provide evidences of support method
regarding these standards such as
successful case studies deployed in the past.
III. Pre - Acceptance Test for minimum hardware requirement (apply for both CMP’s hardware and AEP’s hardware)
General
I
requirement
instruction to test this requirement.
3. Assessment: Pass if hardware warranty duration ≥ 03 years.
Include full accessories to deploy in the Viettel’s data
2 Accessories instruction to test this requirement.
center
3. Assessment: Pass if full accessories to deploy in the Viettel’s data
center are provided.
All hardware and software support concurrent Ipv4 and
3 Support Ipv6 instruction to test this requirement.
Ipv6
3. Assessment: Pass if all hardware and software support concurrent
Ipv4 and Ipv6.
All applications, databases, storage, networking, power
4 HA supply have to be deployed in HA model (active –
3. Assessment: Pass if all applications, databases, storage, networking,
active or active – standby)
power supply have to be deployed in HA model (active – active or active
– standby).
168
II Physical server
Number of CPU sockets per server ≥ 02 CPU Intel
1 CPU instruction to test this requirement
Scalable or newer version
3. Assessment: Pass if the number of CPU sockets per server ≥ 02 CPU
Intel Scalable or newer version
Memory type: DDR4
3. Assessment: Pass if RAM type is DDR4
Memory bus ≥ 2666 MT/s
2 RAM instruction to test this requirement.
3. Assessment: Pass if memory bus speed ≥ 2666 MT/s.
Memory protection: ECC/Advanced ECC instruction to test this requirement.
3. Assessment: Pass if memory protection mechanism using
ECC/Advanced ECC
Speed per port ≥ 10Gbps
3. Assessment: Pass if speed per port ≥ 10Gbps
3 Card NIC 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
Number of ports ≥ 2
3. Assessment: Pass if number of ports ≥ 2 ports
Number of cards ≥ 2 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
169
3. Assessment: Pass if number of cards ≥ 02 cards.
Number of cards ≥ 2
3. Assessment: Pass if number of cards ≥ 02 cards.
4 Card HBA (if any) 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
Port speed ≥ 16 Gbps, Fibre Channel, Auto-sensing instruction to test this requirement.
3. Assessment: Pass if speed per port ≥ 16Gbps and support Fibre
Channel, Auto-sensing
5 RAID controller RAID (0, 1, 5): supported
3. Assessment: Pass if RAID controller support RAID (0, 1, 5)
Support the below operating system (OS) or equivalent: instruction to test this requirement.
+ Windows server 2012/2016 3. Assessment: Pass if support the installation of all below operating
Operating System
6 + RedHat Enterprise Linux ≥ 6.9 system (OS) or equivalent:
(OS)
+ VMWare vSphere ≥ 6.0 + Windows server 2012/2016
+ KVM (Kernel Base Virtual Machine) + RedHat Enterprise Linux ≥ 6.9
+ VMWare vSphere ≥ 6.0
+ KVM (Kernel Base Virtual Machine)
7 Administration Supporting remote managing hardware via Web/console 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
interface 2. Test procedure: Read and analyze the documents, follow the
3. Assessment: Pass if support to remote manage hardware via
170
Web/console interface
Supporting remote installation and configuration
3. Assessment: Pass if support remote installation and configuration.
Supporting troubleshoot via logs, and capture logs instruction to test this requirement.
3. Assessment: Pass if supporting troubleshoot via logs, and capture
logs.
Supporting SNMP protocol (v2c, v3)
3. Assessment: Pass if supporting SNMP protocol (v2c, v3)
8 Firmware Using the latest version by manufacturer instruction to test this requirement.
3. Assessment: Pass if the firmware using the latest version by
manufacturer
III Switching Equipment
1 Rack mount Support Rack 19” (inch)
3. Assessment: Pass if the switch support rack 19” (inch)
171
Number of interfaces for management includes at least
Management instruction to test this requirement.
2 ≥1 x serial (console) RJ-45, 1 x management (Gigabit
interfaces 3. Assessment: Pass if the number of interfaces for management
LAN) RJ-45 and 1 x USB
includes at least 01 x serial (console) RJ-45, 01 x management (Gigabit
LAN) RJ-45 and 01 x USB.
Jumbo Frame 2. Test procedure: Read and analyze the documents, follow the
3 Support MTU size ≥ 9000 bytes
Support instruction to test this requirement.
3. Assessment: Pass if support MTU size ≥ 9000 bytes.
4 Operating mode Support Layer 2, Layer 3 operation
3. Assessment: Pass if the switch support Layer 2, Layer 3 operation.
5 L2 function 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
Number of supporting VLAN ≥ 2000
3. Assessment: Pass if the number of supporting VLAN ≥ 2000.
Support loop-free protocol
3. Assessment: Pass if support Spanning Tree Protocol.
Support LACP, Cross stack ether-channel or equivalent instruction to test this requirement.
3. Assessment: Pass if support LACP, Cross stack ether-channel or
equivalent.
Support Port mirroring 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
172
3. Assessment: Pass if support Port mirroring
L3 function (apply 2. Test procedure: Read and analyze the documents, follow the
Support RIP V2, OSPF, Static route
for core switch (if instruction to test this requirement.
any), distribute 3. Assessment: Pass if support RIP V2, OSPF, Static route.
6
switch (if any), not 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
for management 2. Test procedure: Read and analyze the documents, follow the
switch (if any)) Support VRRP or equivalent
3. Assessment: Pass support VRRP or equivalent.
Support Access control list (ACL)
3. Assessment: Pass if support Access control list (ACL).
7 Security Support Storm control
3. Assessment: Pass if support Storm control or equivalent protocol.
Support Control plane protection or equivalent
3. Assessment: Pass if support Control plane protection or equivalent.
8 Management 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
protocols 2. Test procedure: Read and analyze the documents, follow the
Support CLI
3. Assessment: Pass if support CLI.
Support telnet, SSH, console 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
173
3. Assessment: Pass if support Telnet, SSH, console.
Support SNMP v2c, v3, NTP
3. Assessment: Pass if support SNMP v2, v3, NTP
Support 02 power supply using power cable based on
standard C13/C14, include 2 for spare parts
3. Assessment: Pass if support 02 power supply using power cable
based on standard C13/C14, include 2 for spare parts
9 Power supply Voltage: 200-240VAC/50-60Hz instruction to test this requirement.
3. Assessment: Pass if support Voltage range from 200-240VAC/50-
60Hz
Standby N+1 (N ≥ 1) instruction to test this requirement.
3. Assessment: Pass if the equipment support standby mode for power
supply: N+N (N ≥ 1), swappable
IV Storage
1 Storage Form Standard Rack 19 "(inch)
3. Assessment: Pass if the switch support rack 19” (inch)
2 Hot-swappable and These components must be hot-swappable and hot- 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
174
pluggable, the actions of hot-plugging and hot-swapping
must not interrupt the read/write operations between the
hosts and the volumes in the storage, and must not
3. Assessment: Pass if all the components (Disk drive, Cooling system,
hot-pluggable degrade the storage performance:
Power module, Storage controller) are hot-swappable and hot-pluggable
capabilities - Disk drive (all types)
without the interruption of the read/write operations between the hosts
- Cooling system
and the volumes in the storage, and must not degrade the storage
- Power supply system
performance.
- Storage controller
The upgrading firmware process of the storage must not
Online firmware instruction to test this requirement.
3 interrupt read/write operations between the hosts and the
upgrade operation 3. Assessment: Pass if the upgrading firmware process of the storage
volumes in the storage
must not interrupt read/write operations between the hosts and the
volumes in the storage
Management Number of management interfaces (100/1000Base-T) ≥
4 instruction to test this requirement.
interfaces 02 port
3. Assessment: Pass if the number of management interfaces
(100/1000Base-T) ≥ 02 port.
Management 2. Test procedure: Read and analyze the documents, follow the
5 Web-based GUI, CLI
Interface instruction to test this requirement.
3. Assessment: Pass if support Web-based GUI, CLI management.
6 Cache redundancy Battery-backed cache to disk de-stage or equivalent. instruction to test this requirement.
3. Assessment: Pass if support Battery-backed cache to disk de-stage or
equivalent.
7 Support mix all kinds Support for hard drives plug types, different capacity 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
175
of hard disk
3. Assessment: Pass if support for hard drives plug types, different
capacity.
The ability to
upgrade hardware Allow upgrades to expand capacity by adding more
8 instruction to test this requirement.
when the device is drives or expand tray when the device is running
3. Assessment: Pass if support upgrading expand capacity by adding
active
more drives or expand tray when the equipment is running.
Support 02 power supply using power cable based on
9 Power supply module Supports N + N redundancy and hot-swappable instruction to test this requirement.
Operating input voltage: 200-240VAC / 50-60Hz. instruction to test this requirement.
60Hz
IV.1 Controller
1 Controller Quantity ≥ 2 1. Pre-set Condition: Proposal documents provided by supplier/bidder
176
3. Assessment: Pass if the number of Controller ≥ 2.
All Controller operation in Mesh-Active or Active-
Active architecture which allows each LUN in System
3. Assessment: Pass if all Controller operation in Mesh-Active or
to be active on every controller in the system
Active-Active architecture which allows each LUN in System to be
active on every controller in the system
2 Support RAIDs 1/5/6/10 or equivalent
3. Assessment: Pass if RAID controller support (1/5/6/10)
IV.2 Disk
1 Form factor 2.5’’ or 3.5" or SSD or Flash module instruction to test this requirement.
3. Assessment: Pass if support form factor of 2.5’’ or 3.5" or SSD or
Flash module
2 Interface SAS 6/12 Gbps
3. Assessment: Pass if SAS 6/12 Gbps interfaces
Speed (apply for 2. Test procedure: Read and analyze the documents, follow the
3 ≥10000 rpm
HDD, not for SSD) instruction to test this requirement.
3. Assessment: Pass if disk speed ≥10000 rpm
4 Hot spare At least 01 disk per each tray/enclosure 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
177
3. Assessment: Pass if support the Hot spare of at least 01 disk per each
tray/enclosure
Feature allows
5 replacement of hot There are features that allow hot-swappable hard drives
hard drive
3. Assessment: Pass if support hot-swappable of hard drives
IV.3 Software
Volume Copy feature (or equivalent), with a detailed
description of features of the system Volume Copy
3. Assessment: Pass if support Volume Copy feature (or equivalent),
with a detailed description of features of the system Volume Copy.
1 Backup feature
Snapshot feature (or equivalent), with a detailed
description of the system snapshot feature
3. Assessment: Pass if support Snapshot feature (or equivalent), with a
detailed description of the system snapshot feature.
Thin Provisioning
2 Thin Provisioning feature to optimize the use of space instruction to test this requirement.
feature
3. Assessment: Pass if support Thin Provisioning feature to optimize the
use of space.
Management features, monitor and generate reports for
Feature performance instruction to test this requirement.
3 information about IOPS, bandwidth for the components
monitoring system 3. Assessment: Pass if support management features, monitor and
of the storage system (LUN/RAIDgroup/Controller).
generate reports for information about IOPS, bandwidth for the
components of the storage system (LUN/RAIDgroup/ Controller).
178
Supported operating systems on servers connected as: 2. Test procedure: Read and analyze the documents, follow the
IBM AIX, Oracle Linux, RedHat Enterprise Linux, instruction to test this requirement.
Supported operating
SUSE Linux Enterprise Server, Microsoft 3. Assessment: Pass if support operating systems on servers connected
4 systems on a server
Windows,Oracle Solaris, VMWare ESX / ESXi, Xen as: IBM AIX, Oracle Linux, RedHat Enterprise Linux, SUSE Linux
connected
Server, the operating system supports KVM (Kernel- Enterprise Server, Microsoft Windows, Oracle Solaris, VMWare ESX /
based Virtual Machine). ESXi, Xen Server, the operating system supports KVM (Kernel-based
Virtual Machine).
5 Warranty Support ≥ 3 year.
IV.4 SAN Switch
Number of SAN 2. Test procedure: Read and analyze the documents, follow the
1 ≥ 2 SAN switch (to deploy HA mode).
Switch instruction to test this requirement.
3. Assessment: Pass if the number of provided SAN switch ≥ 02 switch.
2 Number of ports Number of activated ports ≥ 48 ports
3. Assessment: Pass if the number of activated ports ≥ 48 ports.
3 SFP (included) Enough to deploy instruction to test this requirement.
3. Assessment: Pass if the number of provided SFPs (included with
ports) is enough to deploy all necessary connection for SAN Switch.
4 Zoning feature Have Zoning, VSAN or equivalent feature 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
179
3. Assessment: Pass if support Zoning, VSAN or equivalent feature.
5 ISL Trunking feature Have License ISL, ISL Trunking
3. Assessment: Pass if support ISL, ISL Trunking.
Access gateway 2. Test procedure: Read and analyze the documents, follow the
6 Have access gateway mode (license attached)
mode instruction to test this requirement.
3. Assessment: Pass if support access gateway mode (license attached).
Management 2. Test procedure: Read and analyze the documents, follow the
7 CLI (SSH) and GUI
interface instruction to test this requirement.
3. Assessment: Pass if support Web-based GUI, CLI management.
8 Power supply module 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
Have 02 power supply using power cable based on
Supports N + M redundancy and hot-swappable instruction to test this requirement.
Operating input voltage: 200-240VAC / 50-60Hz. 1. Pre-set Condition: Proposal documents provided by supplier/bidder.
180
60Hz
9 Warranty Support ≥ 3 year
181

5.1 - Annex 1 - IoT Platform

Uploaded by

Document Information

Original Description:

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

5.1 - Annex 1 - IoT Platform

Uploaded by

Copyright:

Available Formats

ANNEX 1: TECHNICAL REQUIREMENTS

Interconnection between CMP and Viettel’s existing network

Interconnection between AEP and Viettel’s existing network

ID Function Description Evaluated criteria

ID Function Pass: User is able to fetch data (real-timecriteria

ID Function Every node in the system has back up

Item 3. Pre - Acceptance Test

ID Function Detailed technical requirements Measurement method

19 1. Pre-set Condition: Proposal documents provided by supplier/bidder, user account,

XIII Application Program interfaces (APIs)/Developer Tools

II. Pre - Acceptance Test for Application Enablement Platform (AEP)

ID Function Description 1. Pre-set Condition: Instruction documents

ID Function Description 1. Pre-set Condition: Installed edge platform,

ID Function Description 1. Pre-set Condition: Proposal documents

You might also like