mobile premium services vendor monitoring requirementsv3 - cl
Post on 06-Apr-2018
217 Views
Preview:
TRANSCRIPT
-
8/2/2019 Mobile Premium Services Vendor Monitoring Requirementsv3 - CL
1/4
-
8/2/2019 Mobile Premium Services Vendor Monitoring Requirementsv3 - CL
2/4
-
8/2/2019 Mobile Premium Services Vendor Monitoring Requirementsv3 - CL
3/4
-
8/2/2019 Mobile Premium Services Vendor Monitoring Requirementsv3 - CL
4/4
17 Backend process for interacting with
Aggregator / Content Provider needs to be
streamlined and administratively efficient
Y
18 The carriers will define a tolerance and
engagement policy that the monitoring
company will follow when dealing with the
aggregator and content provider
breaches. This will be fine-tuned during an
initial 3 month period.
19 Vendor to make available to CPs a pre-verification component to allow CPs to
engage the vendor to audit advertising,
SMS or WAP flows before launch. The
charge for this would be for time and
materials only and would be charged to
the CP directly. By using this service, the
audited material would not be excluded
from standard BAU audits.
Aegis has established processes and systems in place for the pre-verification ofadvertising, SMS or WAP prior to launch. The Aegis Program Activation Tool (PACT)
allows for a systematic approach to testing and reporting for verification of these
mobile programs and ads. Verification standards are implemented in the PACT
workflow based on Carrier and industry guidelines. These rules can be expeditiously
updated to reflect the changing market conditions and requirements. The PACT tool
is set up to accommodate the multiple, and ever changing, matrix of handsets that
carriers offer to their user base. The PACT can also be used by the Carrier to
manage their own testing resources if desired.
Contractperiod
20 Each carrier to contract with vendor
individually for initial term of 12 months
with an option of a further term of 12
months or more at its discretion.
Pricing
21 Vendor to provide initial costings - for both
2 and 3 carriers including all the above
broken down in both a single price and a
component price. The additionalrequirements on WAP Billing options
should be only included in the component
price. Any carrier-specific requirements
will be separately costed after successful
vendors' discussion with each individual
carrier.
22 Vendor to provide line-by line
confirmation on this document on whether
the vendor can comply with the
requirements and provide any comments
in relation to the Y/N response. Vendor toprovide pricing and completed document
by COB Wednesday 10th June.
Timefram
e
23 Vendor to reply to all parties with final
pricing and completed requirements
document by COB Wednesday 10th June.
top related