Changes

1,614 bytes removed ,  18 March
no edit summary
Line 1: Line 1: −
__TOC__
+
===MEA certificates===
   −
=1.Terms and descriptions=
+
The MEA table below contains information about the MEA region certificates possessed by Teltonika Telematics devices.
   −
# '''TPS''' – Technical support department;
+
{| | class="wikitable mw-collapsible mw-collapsed vertical-align: middle; text-align: left"
# '''PV''' – Sales manager;
+
|+
# '''RnD''' – "Research and Development" department;
+
! colspan="2" rowspan="2" style=" color:black;" |
# '''TVS''' – Procurement Department;
+
! colspan="4" |MEA
# '''TDK''' - Technical Documentation Coordinators.
+
CERTIFICATIONS
 +
!CELLULAR
 +
APPROVALS
    +
HOMOLOGATIONS
 +
|-
   −
==2. Procedure==
+
! style=" color:black; white-space: nowrap;" |
 
+
<span style="writing-mode: vertical-rl;  transform: rotate(180deg); width: 45px;">
In this page you will find more information about procedure of uploading client's sticker.
+
<span>CITC</span>
Down bellow,  step by step procedure is  presented  how to do it:
+
<span style="font-size:10px; display:block;"> [Saudi Arabia] </span>
 
+
</span>
# '''PV''' creates a ticket in '''HelpDesk''' platform, specifying details of '''client's sticker''', what kind of information should be on the sticker: logotype itself, layout of other client information, size of the sticker, color code etc.;
+
!<span style="writing-mode: vertical-rl; transform: rotate(180deg); width: 45px;">
# '''TPS engineer''', after he has received a ticket from '''PV''' in '''HelpDesk''' platform, has to evaluate whether this change is necessary at all ( e.g.: maybe he could find and/or offer already existing sticker alternative ) and '''re-check''' whether all necessary information about the sticker is presented: logotype itself, layout of other client information, size of the sticker, color code etc.;
+
<span>TDRA</span>
# Received and '''re-checked''' information about client's sticker is then forwarded through '''JIRA''' platform to '''RnD department'''. NOTE: before forwarding information, you have to make sure, that all necessary information about client's sticker is collected properly: logotype itself, layout of other client information, size of the sticker, color code etc.;
+
<span style="font-size:10px; display:block;"> [UAE] </span>
# The template of client's sticker, received from '''RnD department''', is returned back to '''PV''' for client's approval;  
+
</span>
# After '''TPS engineer''' receives confirmation from '''PV''', that sticker template is '''OK''', '''TPS engineer''' addresses to '''TVS department''', that they could find supplier for creating client's sticker and order some '''SAMPLE''' stickers;
+
!<span style="writing-mode: vertical-rl;  transform: rotate(180deg); width: 45px;">
# Price of confirmed sticker '''SAMPLE''' is negotiating with '''[email protected]'''. '''NOTE:''' Negotiation of price is needed, IF client's sticker is very unique or extraordinary;
+
<span>TRC</span>
# Evaluation must be done whether unique instructions of assemblance is needed. If so, then you need to contact '''TDK team''' for creation of such instructions;  
+
<span style="font-size:10px; display:block;"> [Jordan] </span>
# Template of approved  client’s stickers  and / or instructions of assemblance are uploaded to '''AVS''' platform, based on [[Failų į AVS kėlimo procedūrą]] article. If necessary, new order code is created;
+
</span>
# '''RnD department''' must be informed about newly created position ( Reason: addition of new part ).
+
!<span style="writing-mode: vertical-rl; transform: rotate(180deg); width: 45px;">
'''NOTE:''' Client, who orders his own '''BRAND'''  or '''NO BRAND''' on Teltonika devices, he must sign: [[Media:Responsibility confirmation.docx|Responsibility confirmation]].
+
<span>SIRA</span>
 
+
<span style="font-size:10px; display:block;"> [UAE] </span>
[[Category: Technical Support division]]
+
</span>
 +
!APPROVAL NAME
 +
OR COUNTRY