Internship with Daimler South East Asia Sample Essay

The 22 hebdomad Industrial Attachment programme is a nucleus faculty of the Engineering Undergraduate grade at Nanyang Technological University. The undermentioned study presents the undertakings undertaken by the writer and the undertakings performed by him at his attachment administration – Daimler South East Asia Pte. Ltd. from 9th July. 2012 to 8th December. 2012. During his fond regard at Daimler South East Asia Pte. Ltd. . the writer worked on multiple undertakings for their Information Technology Infrastructure-Overseas section under the supervising of their Technical Manager of Singapore. The chief undertakings undertaken by the writer involved: * Following up with users in the Singapore Organisational units on migration of user letter boxs from Lotus Notes to Microsoft Outlook. * Ensuring Network Compliance for the Active Directory of the Singapore division of Daimler AG harmonizing to policies laid down by the central offices at Stuttgart. Germany. * Developing and implementing an online engagement system for meeting suites and equipment for assorted sections. The writer besides worked on other undertakings which are briefly discussed in this study.


We will write a custom essay sample on
Internship with Daimler South East Asia Sample Essay
or any similar topic only for you
Order now

First. the writer would wish to thank Nanyang Technological University’s Career and Attachment Office for their attempts in sourcing the Industrial fond regard with Daimler South East Asia Pte. Ltd. The writer is highly grateful to Daimler South East Asia Pte. Ltd. and Mr. Ryan Ong. the author’s supervisor. for supplying him a fantastic acquisition experience through this fond regard. Mr. Ryan Ong played an of import function in the author’s industrial fond regard by – supplying disputing undertakings with the freedom to run independently and do determinations. besides giving seasonably valuable unfavorable judgment and explicating questions patiently to assist understand the author’s undertakings better. thereby steering him through the class of this fond regard. The writer is besides grateful to his co-workers at Daimler South East Asia Pte. Ltd. – Mr. Liang Zhanrong. Ms. Hyacinth Pichay. Mr. Clinston Tan and Mr. Shaun Tay for their aid and support during the fond regard. Last but non the least. the writer is extremely thankful to Prof. Yvonne Lam Ying Hung. his fond regard supervisor from Nanyang Technological University. for her involvement and support for the fond regard. The writer would wish to thank Prof. Yvonne Lam Ying Hung for taking clip out of her busy agenda to see him at his workplace and supply valuable constructive feedback which encouraged him to endeavor better.


Fig 1. Outlook posting prepared for show across common countries in office Fig 2. Follow-up electronic mail sent by users to guarantee successful migration Fig 3. Spread sheet shared among the direction on Migration advancement Fig 4. Push installing performed to put in Lync utilizing SDWI Fig 5. SSDM tool
being run to reassign archive and encrypted electronic mails to Outlook Fig 6. Archive electronic mails made available to users after running SSDM Fig 7. Conformity study generated monthly by the Active Directory Service Desk Fig 8. UsersIrregular list created utilizing admin. Internet

Fig 9. Removal of irregular user histories utilizing admin. Internet
Fig 10. Clients Invalid Name study generated from admin. Net Fig 11. History locked in admin. Internet and deleted 2 hebdomads subsequently from AD Fig 12. Pinging server names to look into their being in the web Fig 13. Removing locked/unused waiters from AD

Fig 14. PasswordNeverExpiresWOExceptions study generated from admin. Net Fig 15. Modifying histories to follow with standard watchword policy Fig 16. Detailss of client machines obtained from HP Asset director Fig 17. Creation of resources in WAMS

Fig 18. Workflow for meeting room engagement
Fig 19. Workflow for equipment engagement

1. Introduction

1. 1 Purpose

The present study describes all the undertakings undertaken and the undertakings performed by the writer during his 22 hebdomad industrial fond regard at Daimler South East Asia. The present study besides inside informations the valuable work experience gained besides the assorted accomplishments learnt during the fond regard.

1. 2 Scope

The present study explains the inside informations of the author’s primary undertakings which involved following up with users on migration of letter boxs from Lotus Notes to Microsoft Outlook. guaranting the Active Directory ( AD ) of Singapore division of Daimler AG was compliant with policies and ordinances laid down by the central offices in Stuttgart. Germany and implementing an online engagement system for meeting suites and equipment. The present study elaborates on the stairss which the writer took to understand his undertakings. the jobs faced. the stairss taken to decide the jobs. the determinations made. the solutions that the writer came up with and the experience and cognition gained. The present study besides elaborates on the other undertakings that the writer undertook during his industrial fond regard at Daimler South East Asia.

2. Project

Daimler AG had been utilizing IBM Lotus Notes as the electronic mail client and IBM Sametime Connect as the instant messaging client throughout its planetary web. The Daimler AG central office in Stuttgart. Germany had announced the transportation of its users from Lotus Notes and Sametime Connect to Microsoft Outlook and Microsoft Lync severally from 2012. The undertaking was being rolled out for the Singapore division from end-July 2012 to mid-Aug 2012. The migration procedure took topographic point in batches of users every twenty-four hours. The migration of users was initiated at 8pm every twenty-four hours and the procedure would hold been completed by 8am the undermentioned twenty-four hours. The writer was responsible for following up with users on their migration position and deciding issues. if any. related to the migration. He attended hebdomadal meetings with the members of the undertaking. discussed hebdomadal advancement and provided feedback on issues faced. 2. 1. 1 FOLLOW UP WITH USERS

Along with his co-workers. the writer prepared and stuck postings ( Fig 1 ) in common countries across the office supplying users with cardinal inside informations about the migration.

Fig 1. Outlook posting prepared for show across common countries in office. The writer sent electronic mails ( Fig 2 ) to users every twenty-four hours. who had been scheduled for migration the twenty-four hours earlier. to guarantee successful migration. The electronic mail besides provided users with information on Outlook user usher. created by the author’s co-workers ; to assist users understand the characteristics available in Outlook and trouble-shooting steps for common issues.

Fig 2. Follow-up electronic mail sent by users to guarantee successful migration. A migration from Lotus Notes to Microsoft Outlook was considered successful. if a user could direct and have electronic mails through Outlook. Similarly. the migration from Sametime Connect to Microsoft Lync was considered successful. if the user could subscribe in to Lync and chat with users within the Daimler web. The writer recorded the users’ response and consolidated them into a dispersed sheet ( as shown in Fig 3 ) based on the undermentioned standards: * Users and groups with successful migration were marked as Yes. * Users and groups that had been exempted from the migration were listed as NA. * Users and groups that faced jobs were marked as No.

Fig 3. Spread sheet shared among the direction on Migration advancement. Every twenty-four hours. the writer sent updates to the members of the undertaking on the migration attaching the above spread sheet. The dispersed sheet was besides shared online on Share point with the direction to supervise the advancement of the undertaking.

2. 1. 1 Resolution ISSUES
During the migration followup. the writer was notified by the users about jobs which they had encountered. The writer responded to the users by electronic mail and in some instances. personally attended to users to acquire elaborate description of the job and work out simple issues. He analysed the issues faced by the users and tried work outing most of them by himself. Issues which were beyond the range of the users’ cognition. were forwarded by him to the Local User Helpdesk – which was either solved by Onsite Engineers or escalated to the central office in Germany. Brief descriptions of the issues solved by the writer are as follows: * Microsoft Lync missing:

During the initial phases of migration. the writer found that the Microsoft Lync communicator had non been installed In User machines after the migration. The writer performed a push installing of Microsoft Lync to the users’ computing machine utilizing an office application named SDWI ( Fig 4 ) .

Fig 4. Push installing performed to put in Lync utilizing SDWI.

To guarantee that the same job would non be faced once more. the writer performed push installing of Lync all user computing machines a twenty-four hours prior to the migration. This resolved the issue of losing Lync after the migration and was non reported thenceforth.

* Electronic mails older than 30 yearss non transferred:
Under the migration undertaking. electronic mails which were 30 yearss older than the migration day of the month were non transferred to users’ Outlook letter box. In order to reassign older and archive electronic mails from Lotus notes to Outlook. the writer ran the Self-service desktop migrant ( SSDM ) application ( Fig 5 ) . an application which had been provided by the central office at Germany to reassign archive and encrypted electronic mails to Outlook. on the user machines. Fig 5. SSDM tool being run to reassign archive and encrypted electronic mails to Outlook.

After choosing the necessary options in SSDM. the archive electronic mails was made available to users in their Mentality letter boxs under a new booklet by the name of Lotus Notes emails as observed in Fig 6.

Fig 6. Archive electronic mails made available to users after running SSDM.

At the terminal of the migration undertaking. the writer had consolidated the migration position of the Singapore users. the issues that had been faced. and the actions performed to repair the assorted issues. A elaborate study of the same was passed on to the direction to be used for the migration rollout in other states in the Asia-Pacific part.


The concern units of Daimler AG are split into 3 parts – EMEA ( Europe. Middle East and Africa ) . APAC ( Asia Pacific ) and NAFTA ( North and South America ) . The chief central office of Daimler AG is present in Stuttgart. Germany while Singapore is the central office for the Asia Pacific concern units. The Singapore division has 3 organisational units. viz. : * A128 – Daimler South East Asia Pte. Ltd.

* A481 – Daimler Financial Services.
* A830 – Mercedes Benz Financial services.
The writer of this study was assigned with the duty of guaranting that the Active directory in Singapore. and thereby the 3 organisational units. were compliant in all facets with the policies and ordinances laid down by the central offices in Stuttgart. Germany. Whenever an object is in misdemeanor of any company protocols. it is listed under a study named after the protocol violated in a SQL database ( called the active directory ) that can be accessed utilizing the Daimler AG administrative tool called admin. Internet. The local decision maker of the Organizational units can see studies restricted to their duty country. Objects listed as erroneous under each conformity study had to be resolved before the figure of objects listed reached a certain threshold per centum degree. neglecting which the position of the conformity study will be escalated to warning or critical status depending on the threshold per centums set for each conformity study.

Organizational unit ( OU ) conformance position study is sent to the OU decision maker along with the conformance mark at the terminal of every month. A conformance mark of 100 agencies that all studies are All right and none are in a critical or warning state of affairs and a mark of 0 agencies all studies are critical. The author’s undertaking aim was to better the conformance mark for all the organisational units to 100. Sometimes non-complaint objects in Active Directory could non be fixed with sensible attempt. so no betterment of the conformance position can be achieved in a short term. In such instances concern units can raise exclusions from the Active Directory Service Desk. Exceptions will run out after a limited clip ( soap. one twelvemonth ) but reclamation is possible. The monthly AD conformance study contains the position of the protocols for the conformance study along with the description of exclusions raised as shown in Fig 7.

Fig 7. Conformity study generated monthly by the Active Directory Service Desk. The following tabular array shows the conformity position of the organisational units A128. A481 and A830 when the writer began work on the conformity studies from July 2012. Organisational Unit| Conformity mark

An luxuriant description of some of the conformity studies that the writer worked on during the class of his fond regard are as follows:

2. 2. 1 COMPLIANCE REPORT – UsersIrregular

* Rule:
Non Corporate Directory ( CD ) based history names must get down with & lt ; TopLevelOUName_ & gt ; . CD-based user histories have to be deleted within the grace period after decommissioning in CD. CD-based user histories must match to an bing CD-User ID

* Description:
This study shows the entire figure of irregular user objects. An irregular user object fulfils one of the undermentioned three standards: I ) The Daimler naming convention for non-Corporate Directory ( CD ) based user histories is violated ( “Invalid Name” ) . two ) A Cadmium object was deprovisioned and deleted and the grace period of 3 month for the being of the CD-based user object in AD has expired ( “Deletion Grace Period Expired” ) . The warning threshold is 10 % . the critical threshold is 20 % .

* Hazard:
I ) AD user objects must hold a alone name. In order to guarantee coexistence of many workss and concern units in the planetary AD. the Daimler AD naming conventions provide a separate namespace for each location. User accounts with non-conform names should be renamed to avoid jobs. two ) After a specified period of clip Cadmium based user objects deleted in Cadmium must be deleted in AD. excessively. These histories are a possible security hazard and violate Daimler corporate policies.

* Solution:
The writer used the Admin. NET study “UsersIrregular” to bring forth list of these defective histories and to decommission them ( Fig 8 ) . Fig 8. UsersIrregular list created utilizing admin. Internet

* The writer observed that most of the histories featured on this list included users who had transferred or departed from the company. But. the histories had non been removed from the AD following the omission scheduled omission period. The writer deleted these user histories utilizing admin. NET as shown in Fig 9.

Fig 9. Removal of irregular user histories utilizing admin. Internet.
* The writer conducted questions on histories with invalid name ( non following the user appellative convention ) and found that these histories had been created for proving and preparation intents. The writer filed these histories for freedom.

2. 2. 2 COMPLIANCE REPORT – ClientsInvalidName

* Rule:
Client history name must get down with “C/M & lt ; Location ID & gt ; ” eg. C128D54608PS

* Description:
This study shows the entire figure of clients with an invalid name. Any computing machine history where the operating system information does non incorporate “Server” or the name does non get down with “S” or “T” is checked. Client names must get down with “C” or “M” . followed by the three-character location identifier nowadays in the Top-Level OU name. For illustration. the name of a client located in the Top-Level OU A128 must get down with “C128” . The warning threshold is 1 % . the critical threshold is 10 % .

* Hazard:
If appellative conventions are violated. the computing machine can non be associated to the duty country. Scripts and package distribution tools may do usage of the location codification. If the client name does non get down with M or C it complicates development of tools and books and may besiege execution of planetary procedures and direction tools. Although a individual false named computing machine history does non hold a serious impact on Active Directory. every individual history might non be in range of certain mechanisms that require conform computing machine names ( aggregations in Software Distribution. etc. ) . Correctly named computing machines help to * place object types or object location by name.

* allow for tool based mass actions.

* Solution:
In order to place clients with invalid names the Admin. NET Report “ClientsInvalidName” was generated by the user. Fig 10. displays the list of clients with invalid names.

Fig 10. Clients Invalid Name study generated from admin. Internet.

First. the invalid clients had to be located by the writer to find if they existed in the web. If the client was active. so it was renamed and if the client was inactive so it was scheduled for omission. The writer checked the names of the invalid clients utilizing the Daimler AG office application – SDWI to find the last login user and thereby the client’s location.

* The writer found multiple entries of a individual machine but utilizing different appellative conventions ( since Daimler AG had revised its calling convention in the yesteryear ) . He removed the clients which featured the old naming convention and ensured that lone clients with the latest appellative convention existed in the Active Directory. * Besides. the writer located machines which were running on Windows XP. Daimler South East Asia Pte. Ltd. had shifted from Windows XP to Windows 7 in the beginning of 2012. Few clients intend for proving intents entirely ran on Windows XP. whereas other XP machines had been disposed by the company.

The user identified the non-testing purpose machines and removed them from the active directory ; and raised exclusions for clients used for proving intents. * The writer inquired with the Infosys squad on the names of their Indian Personal computers which did non have the regular naming convention ( the most likely company with to hold invalid client names in the active directory since Daimler hires batch of contracted employees from Infosys. who are stationed in India ) . The writer locked the clients which were confirmed to be inactive. along with those whose position was unknown for a period of 2 hebdomads. If after 2 hebdomads. no expostulation had been raised the clients were deleted from the active directory ( Fig 11 ) .

Fig 11. History locked in admin. Internet and deleted 2 hebdomads subsequently from AD.

2. 2. 3 COMPLIANCE REPORT – ServersPotUnused365

* Rule:
The waiter did non logon to the sphere for more than 365 yearss. This indicates a stale computing machine history.

* Description:
This study shows the entire figure of server computing machine histories in Active Directory ( AD ) which were potentially non used for more than one twelvemonth. A waiter is considered as fresh if the figure of yearss since last logon. last password alteration or object creative activity is greater than 365. These standards are evaluated for enabled every bit good as handicapped computing machines. The warning threshold is 10 % . the critical threshold is 25 % .

* Risk/Benefit:
A waiter which is joined to the sphere will ab initio put several history belongingss which will be updated on a regular basis during usual waiter activity. Inactive waiters will no longer update these objects properties. Although a individual. non-used ( outdated ) waiter history does non present a serious status in Active Directory. a important sum of dead histories affects the dependability of AD and Server Management System ( SMS ) study informations. A clean environment helps to * derive more dependability and comparison on describing informations. * cut down SMS find operating expense during processing. event logging. and informations hive awaying. * keep physical AD database file smaller and rush up AD hunts and supply clear position when naming client objects.

* Solution:
The Admin. NET study “ServersPotUnused365” was used to deduce a list of affected waiters by the writer.

First. he tried to turn up the waiters by pinging them from Command prompt as demonstrated in Fig 12.

Fig 12. Pinging server names to look into their being in the web

* Servers bing in the web responded to the Ping. The writer compiled the list of waiters which pinged back and forwarded it to his supervisor for raising exclusions. since these waiters had to be in the web. * For the waiters which failed to ping back and the 1s which could non be located by the writer. he contacted the Server squad to find the location of these machines. Active waiters were filed for exclusion whereas waiters. confirmed as unused/inactive. were locked for a period of one month. following which they were deleted from the AD as indicated in Fig 13.

Fig 13. Removing locked/unused waiters from AD

2. 2. 4 COMPLIANCE REPORT – PasswordNeverExpiresWOE

* Rule:
A user account’s watchword must run out after 30 yearss.

* Description:
This study shows the entire figure of user histories with non-expiring watchword. The Daimler Security policy requires that all user histories have to alter their watchwords after 30 yearss. Exceptions have to be reported to CoC Identity Management and can be excluded from the studies after blessing. The warning threshold is 5 % . the critical threshold is 10 % .

* Hazard:
Histories without run outing watchwords violate Daimler Corporate watchword policies. Active Directory ( AD ) has to let the anon. listing of the names of all user histories to back up Windows NT4 systems. An aggressor could acquire entree to user resources if he’s able to think a watchword. To minimise this hazard. a watchword policy was defined that requires a complex watchword which has to be changed every 30 yearss. User accounts with non-expiring watchwords enforce a possible security hazard and must be reconfigured to utilize standard watchword scenes.

* Solution:
The writer ran the Admin. NET study “PasswordNeverExpiresWOExceptions” to bring forth a list of such histories and to modify the history belongingss ( Fig 14 ) .

Fig 14. PasswordNeverExpiresWOExceptions study generated from admin. Internet

Once the list of erroneous histories was obtained. the writer sent electronic mails to the several users informing them about the Daimler Corporate watchword policy. He modified the history scenes utilizing Account options available in admin. NET as shown in Fig 15. Upon unchecking the Password ne’er expires option. the histories were set to the criterion watchword histories.

Fig 15. Modifying histories to follow with standard watchword policy The users were subsequently notified once more about the alterations made to their histories. where after their watchwords shall run out after every 30days.


The writer besides worked on other conformity studies which were similar to the studies discussed in the earlier subdivisions. The ServersInvalidName conformity study generated a list of waiters which ddi non follow the criterion calling convention. The class of action was similar to that of ClientsInvalidName. except that the writer checked with the Server squad on the being of the machines and the history was locked for a period of one month prior to omission from the AD. Clientspotunused365 was a conformity study which generated list of client computing machines non used in the past 365 yearss. The writer undertook similar action. as in the instance of Serverspotunused365. But. in this instance the writer checked the physical location of the computing machines utilizing HP Asset director. package used to keep the IT stock list by the Local User Help Desk ( Fig 16 ) .

Fig 16. Detailss of client machines obtained from HP Asset director. Based on the undermentioned position of the clients returned by the package. the writer undertook the necessary actions: * Retired: When a machine was listed as retired. the writer deleted the machine straight from the Active directory since the machine had been disposed earlier by the company. * In usage: Clients listed in usage were verified for their being by look intoing straight with the several users listed under Asset director. Exception was created to suit active machines. * Stock: The warning threshold for Clientspotunsed365 was calculated. If the figure of clients listed as stock was lower than this value. the writer left these clients untouched. When the figure of clients was more than the warning threshold. the writer forwarded the names of these clients to his supervisor.

The writer helped in bettering the AD conformance mark every month. Irregular clients. waiters and histories appeared in the conformance study every month. But. the writer was able to stamp down all critical issues in the first month and worked on cut downing issues in the Warning status. By the terminal of November. he had achieved conformance mark of 100 for A128 and A481. A831 could non make a mark of 100 due to server issues. which require at least 1 month for rectification. appeared in terminal of October. 2. 3. ONLINE RESOURCE BOOKING SYSTEM

Users at Daimler AG had an online system in Lotus Notes to book meeting suites and equipment that were needed for meetings. Following the migration of users from Lotus Notes to Microsoft Outlook in August. there was no online booking system available for the users. The writer was handed over the duty of suggesting an online engagement system for the resources i. e. suites and equipment in Outlook to the Administration section. Using WAMS. an office application of Daimler AG. resources could be created which would look subsequently in the Outlook reference book. Given the sufficient entree rights. users can open the resource calendar and book meeting suites. similar to directing meeting petitions among other people. The writer explored the different capablenesss and characteristics available in Outlook calendar to be after a suited online system. He obtained inside informations from the disposal on the ownership of the resources. specifications of the equipment. and installations in the suites that were needed to make resources in WAMS as shown in Fig 17. Fig 17. Creation of resources in WAMS

* The users with Book-In policy received entree rights to book a resource by merely directing a meeting petition to the resource listed in the reference book. * The users with Request-In policy could bespeak for booking a resource by directing a meeting petition to the resource from their reference book. * Users listed under Resource delegate had the rights to O.K. petitions for use of resources. The writer carried out test-runs with his co-workers by supplying them with necessary entree rights and devised a online engagement system. Between th October. 2012 and th November. 2012 the writer had meetings with the disposal to show the working of his engagement system and to roll up feedback on its feasibleness. Harmonizing to the engagement system developed by the writer:

* Users had entree to book resources from the resource calendar but could non redact assignment made in the calendar. This was necessary to guarantee that users did non call off each other’s assignment to utilize a meeting room which would do clangs. * Users could book the resources merely 3 months from the day of the month of booking. This regulation was implemented to advance just use of the resources as some users would book manner in progress and prevent other users from booking the resource. * Equipment could non be booked straight as it was necessary for the disposal to maintain path on the equipment use. Request for equipment was approved by the disposal based on the nature of the meeting and necessity for the equipment. Though the initial response from the disposal was positive. the major concern raised by the disposal was that user information in a engaged time-slot was seeable merely to the disposal and non to other users. If user information was available among users on engaged time-slot. users could negotitate on the use of meeting room. This was solved by implementing a regulation to include the name of the organizer and his/her extension figure under the location field in meeting petitions. The work flow for the online system is demonstrated below:

All meeting suites are unfastened for booking to all users i. e. all users were given Book-In policy. Meeting organisers’ can book any meeting room utilizing the undermentioned work flow.

Fig18. Workflow for meeting room engagement
For equipment to be used in the meetings. it was necessary that the decision maker O.K. the petition for the use of the equipment i. e all users were given Request-in policy and the disposal section was the resource delegate. This is explained by the workflow below:

Fig 19. Workflow for equipment engagement
Once the engagement system was approved for usage by the disposal. a pool of users were selected for a pilot tally from November to December with programs of implementing the system in January based on feedback from these pilot users. The writer conducted preparation Sessionss for these pilot users and provided them with user ushers for their mentions. He discussed hebdomadal advancement with the disposal on the pilot tally. Merely one issue raised by a pilot user. who was non given entree to the resources. required the aid of the writer. The user’s name was subsequently included in the Book-In policy for meeting suites and Request-In policy for equipment. Thereafter. the user did non meet any jobs with the engagement system. Other jobs faced by the users were little and the solutions were available in the user usher.


Apart from the 3 chief undertakings that have been discussed earlier. the writer besides worked on other undertakings which are briefly explained below: * ITM signifiers:

The writer documented all the IT direction petition signifiers as and when required. The writer besides placed petitions for IT hardware equipment as and when required to make so on behalf of the Technical Manager of Singapore. In order to cut down the work flow of IT direction petitions and doing it more effectual. the writer consolidated the purchases of all package and hardware equipment made between 2009 and 2011 and proposed alterations in the current petition signifiers.

* Enterprise Architecture Planning:
The writer assisted the Chief Information Officer at Daimler South East Asia for the Enterprise architecture planning ( EAP ) . Using an office application called BeePRM. the writer prepared a elaborate study on the licensing fee and past purchases of the assorted package used by the employees of Daimler South East Asia Pte. Ltd. The study was used by the Chief Information Officer in the EAP for the subsequent twelvemonth.

* Demo session for Samsung Sur 40:
The writer organised a demo session for Samsung SUR 40 to show the capablenesss of Microsoft Pixel Sense to the concern users. He gathered feedback from the attendants on the possible use of Microsoft Pixel Sense in concern countries. consolidated it and presented it to the direction for their consideration.

* Asset consolidation:
The writer verified the being and ownership of the IT hardware under assorted users. for the one-year process to accommodate all IT assets at Daimler South East Asia Pte. Ltd. He assisted his co-workers in keeping the IT stock list by turn uping losing IT hardware and printing and labelling plus ticket for IT hardware. * Management of VoIP Telephones:

The writer maintained the list of voice over IP ( VoIP ) phones used at Daimler
South East Asia Pte. Ltd. He updated the list to maintain path of the plus motion. He on occasion performed factory reset of voice over IP ( VoIP ) phones before deployment to users.

* Management of ROVA items:
ROVA is a two-factor hallmark items used by the employees at Daimler AG for logging into the Daimler Network from outside the web. The writer filed petition signifiers for ROVA items. updated the list ROVA tokens being used and ensured that the items were working decently earlier deployment to users.

* Cost Centre Update:
A list of Singapore users having wrong Cost Centre within the Daimler AG employee database was generated for the writer. He worked with supervisors of these users and ensured that necessary corrections were made to reflect right Cost Centre in the employee database.

* Red Personal computer list:
A list of users holding administrative rights on their machines without IT Management blessing was provided to the user. He contacted the users on this issue and removed decision maker entree from their several machines.

* Communication Notes:
The writer jointly developed a new templet of communicating notes for internal employee communicating. He besides prepared communicating notes for IT updates which was forwarded to all employees at Daimler South East Asia Pte. Ltd.

* Deployment of IT Hardware:
The writer deployed IT hardware to new and bing employees as and when required. During this procedure. he performed installing of IT hardware and assembly of a computing machine.

* Team Chart:
The writer besides prepared the squad chart for portfolios under the Technical
Manager of Singapore at Daimler South East Asia Pte. Ltd. . as and when new employee joined the squad or departed from the squad.

* Procurement for Office Automation squad:
The Office Automation ( OA ) squad required Netapp storage and a waiter rack for making a testing environment for one of their undertakings. The writer liaised with the OA squad and the procurance section to assist happen a suited seller.

* Printer Reports:
The writer prepared monthly studies for the accounting section for the HP and Lexmark pressmans used by the company.

* Invoices and Service Reports:
The writer besides verified and filed the bills for bringing orders and periodic studies on electrical and telegraphing plants. computing machine support system and entree control system. He besides consolidated the bills. service studies and understandings from the past 3 old ages. thereby bettering the filing system.

3. Decision

The author’s fond regard with Daimler South East Pte. Ltd. was a fantastic professional acquisition chance where he obtained valuable on the occupation experience. Through the class of his fond regard. the writer learnt about the operation of a transnational company and the ways in which different sections coordinate to accomplish their marks and present some of the best cars in the universe. Through his undertakings and association with people across assorted sections. he understood the important function of the Information Technology section in back uping assorted concern units. The primary and secondary undertakings provided a alone platform to construct and develop the author’s accomplishments. He gained new cognition. encountered and overcame challenges and has come to appreciate on the occupation preparation. All of this was received in a hands-on environment. an unforgettable experience that was beyond the range of the schoolroom.

The writer interacted with employees from different nationalities and different civilizations ; the writer has developed his societal and professional communicational accomplishments. The writer handled undertakings independently and worked together as a squad on assorted occasions. With tight deadlines and the invariably turning challenges. the writer learnt the values of continuity and presenting consequences in hard-hitting work environments. The nature of work in the IT substructure division has helped the writer hone his IT skills by working on a regular footing with Microsoft Excel. Microsoft PowerPoint. Microsoft Publisher and office applications of Daimler AG like admin. NET. SDWI and BeePRM. Overall. the fond regard provided a suited platform for the author’s growing where he developed his strengths and improved on his failings. Through the fond regard. the writer has gained valuable experience for the old ages to come.


Hi there, would you like to get such a paper? How about receiving a customized one? Check it out