Gps III Rollout Provider Manual v146 20120126

GPS III Rollout Provider Manual
Project: GPS III

Sub-function: Documentation and Training
Forum: none
Pad / Config: none
MonitoringID: none
Systems affected:
BASF IS Page 1 of 301

GPS III Rollout Provider Manual, 1.46
Document Control
Version of Template
1.00 – 2010-07-21
Format: GPS III Rollout Provider Manual.dotx
Set the format via: Entwicklertools|Dokumentenvorlage | Anfügen to the file GPS III Rollout
Provider Manual.dotx
Change Record
Author Versio Change Reference

n
2011-07-15 Christoph 1.00 Set to Version 1.0
Albrecht
2011-08-11 Norbert 1.01- Version as of Rollout Provider Trainer 2011-08-10/11
Braun 1.20
2011-08-11 Norbert 1.21 Updated Figure GPS III asset; GPS III Data Migration Wizard
Braun
2011-08-11 Norbert 1.22 Update Docu ISS (Markus Schwaiger)
Braun
2011-08-17 Norbert 1.23- Layout changes
Braun 1.25
2011-08-18 Norbert 1.26 Inserted Technical Experts Phone Numbers EMEA
Braun
2011-08-18 Norbert 1.27 Correct typo in .3.2.5; 24/7 DTM Support Team
Braun
2011-08-23 Norbert 1.28 Updated 3.3.5.1, removed Rollout Technician login.
Braun
2011-09-09 Christoph 1.29 Holiday dates corrected;
Albrecht (QG4) Chapter 3.2.5: Definition of HW bundles added;
Chapter 3.3.5.1: Deactivation of UMTS/smartcard added;
Chapters 3.3.9, 3.4.4 and 4: instructions concerning docking
stations with hard disks added;
Chapter 3.3.11.5: Step 5 added: Set the correct APN;
Table 4: Pilot Regions and Countries corrected;
Chapter 3.3.7: BitLocker process changed
2011-09-14 Christoph 1.30 Chapters 3.3.8 and 3.3.5: Create ticket note added; 3.3.2,
Albrecht 3.3.8: proceeding in case of User’s no-show changed: create
ticket
Chapter 3.3.11.3: no-show case: steps reformulated
Chapter 3.3.5.2: Smartcard rollout: special cases and process
changed
Chapter 3.3.5.4: Step 3, Inform User about IT catalog, added
Chapters 3.3.11.4 and 5 (UMTS and iPass): Verify that GPS III
Service desk is to be informed;
Chapter 6.4: Contact data Technical Expert Team SA and NA
added;
Chapter 3.3.11.8 replaced by new chapter 3.3.5.1 (Deactivate

UMTS card reader)
2011-09-21 Christoph 1.31 Chapters 3.3.9, 3.3.10, 3.4.2: Information protection measures
Albrecht described more in detail;
Chapter 4.2.3. Mechanical destruction of the hard disk if the
User is a VIP
2011-09-23 Christoph 1.32 Chapter 3.3.6: Initial Acceptance Procedure: Monitor,
Albrecht Reference to Substitute User in BISTRO Manual
Chapters 3.3.11.4 and 5 (UMTS and iPass): Verify that GPS III
Service desk is to be informed if credentials are not at hand;
Chapter 3.2.4: Warning added: no docking station; WLAN
switch must be On.
Chapter 3.3.6.: Special case Substitute User for IA added
References to BISTRO Manual updated
Chapter 3.2.4 waiting time before installation can begin
extended to min. 1 hour.
2011-09-29 Christoph 1.33 Chapter 3.3.7: new USB Hard disk screenshot;
Albrecht Chapter 3.3.4: Step 5 - 8, Novell Secure Login added;
Chapter 3.3.6: Special case Substitute User added
2011-09-30 Christoph 1.34 Former Chapter 3.3.5.1: “Ensure the UMTS card reader is
Albrecht deactivated” removed: The deactivation of the UMTS card
reader is no longer necessary
For more convenience when updating printed copies, each
chapter begins on a new page.
2011-10-21 Christoph 1.35 Chapters 2.1.3.5 and 3.3.1, Prerequisites DP3
Albrecht Chapter 2.3.5 and 7.3.7: “browser” replaced by “MS Internet
Explorer 8”
Table 17: assignee group names corrected
Table 20: address AP corrected:
Table 21: Hardware configuration of GPS III asset models: item
Health Card added
Chapter 6.4, table 32: contact data corrected
Chapter 3.1.2: step 3.D added for DOA case at DP1
Chapter 3.2.4. step 4 for DOA case at DP2 added
Chapter 3.3.3. step 4.B and chapter 3.3.11.3, step 4 for
guarantee case at DP3 added
Chapter 3.3.6: IA: let User perform functional tests only for
business-critical applications
To describe how to process a rejected GPS III asset the
following was added: chapter 3.3.2, Step 5; chapter 3.3.11.8;
chapter 3.3.6, Step 8;
Special case Substitute User revised: Chapter 3.3.2: step 6
plus warning, chapter 3.3.3: prerequisites, Chapter 3.3.4: step
7; chapter 3.3.5.1: step 1; chapter 3.3.11.4: step 2.
Process defective GPS II assets: Chapter 4.2, step 3 B and
chapter 3.4.5, step 1 changed.
Chapter 3.3.5.2: renamed to „Perform additional services“
Chapter 3.4.6.1: Special case „Return legacy GPS II asset to
User“ described more precisely, chapter 2.3.7.2 changed
accordingly
2011-11-02 Christoph 1.36 Chapter 3.3.2, step 3.C.I waiting time in no-show case
Albrecht Chapter 3.3.7: BitLocker encryption process corrected

Home and Travel User rollout: Chapters 3.3.11.9 and 3.3.11.10
added, chapter 3.3.2., step 14.B added accordingly
Chapter 6.2.1.2 with numbers to call the GPS III Service Desk
APAC from outside a BASF site added
2011-11-15 Christoph 1.37 To speed up the rollout process, the content of chapter 3.3.5.1
Albrecht is integrated in chapters 3.3.3 and 3.3.4, respectively.
Chapter 3.3.3, step 10 (Hint reformulated as step: inform User
about how to continue working with the GPS II asset during
migration.
Chapter 3.3.9 added (User information about POIS phase)
Glossary increased.
2011-11-16 Christoph 1.38 Chapter 3.3.7. Warning added that the external hard disk must
Albrecht be locked via password, not smartcard, step 8 added: inform
User about ways to recover data.
Chapter 3.3.11.5: Warning added that step 5 is to be
performed only in Germany
2011-11-23 Christoph 1.39 Chapter 3.3 Hint “Delayed rollout process” added with
Albrecht reference to chapter 3.3.8 (general proceeding to report
incidents).
Chapter 3.3.2, step 3.C.ii added: report incidents in BISTRO,
Chapter 3.3.8 changed accordingly.
Chapter: 3.3.6. Step 7 added: Incident ticket number to be
added in the IA Coments field, Chapter 3.3.8 changed
accordingly.
To cover the case a GPS II asset is not available, we have
added, in chapter 3.3.2, step 13, and chapter 3.3.11.11.
Chapter 6, GPS III troubleshooting contact data: Warning
added to use the contact data indicated in this chapter; to
highlight the use cases matrix, chapter headline 6.1 was added
2011-12-08 Christoph 1.40 Chapter 1.2.2: How to read graphics added;
Albrecht Chapter 3.3.3, Start data migration: To solve LANCrypt issues,
step 7.D is added.
Chapter 3.3.4, Check Activation of Pre-Boot Authentication:
Entering Novell Single Sign On passphrase no longer required
Activation steps to be skipped in countries where hardware-
encrypted hard disks are prohibited
Chapter 3.3.7 (Bitlocker Encryption): step 7added.
2011-12-13 Christoph 1.41 Chapter 3.3.2, step 8, and chapter 3.2.5, table 21: description
Albrecht of how to attach the BGV A3 Prüfplaketten corrected
2011-12-13 Christoph 1.42 Chapter 3.3.2, step 8, and chapter 3.2.5, table 21: description
Albrecht of how to attach the BGV A3 Prüfplaketten extended:
Switzerland included
2011-12-14 Christoph 1.43 Chapter 3.3.9 (Remove old GPS II assets): Due to explosion risks,
Albrecht the rollout technicians are strictly advised to no longer collect loose
batteries. We have inserted a warning.
Chapter 3.3.2, step 8, and chapter 3.2.5, table 21: extension to
Switzerland removed again (until change request is processed)
2011-12-21 Christoph 1.44 Chapter 3.3.3 (Start data migration): Steps 5 to 7 added (connect

Albrecht external hard disk)
2011-01-13 Christoph 1.45 Chapter 2.4.6: Process “Process stolen GPS III assets” added
Albrecht Chapter 3.3.2, step 8, and chapter 3.2.5, table 21: description of how
to attach the BGV A3 Prüfplaketten extended: Switzerland included
(according to CR097)
Chapter 3.3.3: Information added that the display language of the
Migration User is English
In chapter 6.2.2 (EMEA Service Desk contact info): Table 28
replaced by sub-chapters to allow easier access to support contact
information
2011-01-24 Christoph 1.46 No changes. To avoid confusion with an “inofficial” Version 1.45, we
Albrecht just set the counter to 1.46.

Reviewers
Name Position
Ilker Oezbek Lead Rollout Coordination GPS III
Mirta Jarnjak Lead Communications GPS III
Delegated to Thomas Schock Lead PMO
Anke Roden Project Assistance
Delegated to Guido Roth Lead BISTRO
Andreas Zabanoff, Uwe Will EMEA Regional Coordinator
Delegated to Mayank Gupta, Danni Bhadrahn AP Regional Coordinator

Herchiel j. Devalcourt NA Regional Coordinator
Marcos A. Ferreira de Silva, Rodrigo Matiello SA Regional Coordinator
Delegated to Paulette Feller Rollout Coordination
Distribution
Copy Name Location
File Location
GPS III Teamplace - 2. 4. 1.12 Documentation Training Manual > GPS II Rollout Provider
Manual

Content
1 Introduction........................................................................................................................ 14
1.1 Abstract ......................................................................................................................... 14
1.2 Usage of this Document ............................................................................................... 15
1.2.1 How to interpret symbols ................................................................................... 15
1.2.2 How to read graphics......................................................................................... 15
1.2.3 Wording ............................................................................................................. 16
1.3 GPS III Organization and Process ................................................................................ 17
1.3.1 GPS III Project Organization .............................................................................. 17
1.3.2 GPS III Countries............................................................................................... 18
1.3.3 GPS III Rollout Process Stages & Roles ............................................................ 21
1.3.4 GPS III Rollout Timelines and Milestones .......................................................... 23
1.4 GPS III Hardware ........................................................................................................... 26
1.4.1 Hardware Specification ...................................................................................... 26
1.4.1.1 Ultra Portable Notebook (13") Dell Latitude E6320 ..................................... 26
1.4.1.2 Desktop Replacement Notebook (15") Dell Latitude E6520 ........................ 28
1.4.1.3 Portable Workstation Notebook (17") Dell Precision M6600........................ 29
1.4.1.4 Desktop – Minitower Dell OptiPlex 990 ....................................................... 30
1.4.1.5 Desktop Workstation (Tower) Dell Precision T3500 .................................... 31
1.4.2 Pictures ............................................................................................................. 32
1.4.2.1 Ultra Portable Notebook (13") Dell Latitude E6320 ..................................... 32
1.4.2.2 Desktop Replacement Notebook (15") Dell Latitude E6520 ........................ 35
1.4.2.3 Desktop Replacement Workstation Notebook (17") Dell Precision
M6600 ........................................................................................................ 38
1.4.2.4 All Purpose Desktop – Minitower Dell OptiPlex 990 .................................... 40
1.4.2.5 Workstation Desktop (Tower) Dell Precision T3500 .................................... 43
1.4.2.6 Dell External Mini USB Modem ................................................................... 45
2 Rollout Provider ................................................................................................................. 46
2.1 Basic Conditions for Rollout ........................................................................................ 46
2.1.1 Rollout Provider Employees............................................................................... 46
2.1.1.1 Behavior and Appearance during the Rollout .............................................. 46
2.1.1.2 Teams ........................................................................................................ 47
2.1.2 BASF Infrastructure and Tools........................................................................... 48

2.1.2.1 Active Directory........................................................................................... 48
2.1.2.2 Intranet ....................................................................................................... 48
2.1.2.3 BISTRO ...................................................................................................... 49
2.1.2.4 IS Service Desk and GPS III Rollout Service Desk ..................................... 49
2.1.2.5 Smartcard ................................................................................................... 50
2.1.3 Rollout Provider-provided Materials ................................................................... 51
2.1.3.1 Basic Equipment (General Infrastructure) ................................................... 51
2.1.3.2 Basic Equipment (Carried by Rollout Technician) ....................................... 52
2.1.3.3 Delivery Point 1........................................................................................... 53
2.1.3.4 Delivery Point 2........................................................................................... 53
2.1.3.5 Delivery Point 3........................................................................................... 54
2.1.3.6 Delivery Point 4........................................................................................... 55
2.1.3.7 Delivery Point 5........................................................................................... 57
2.1.4 Rollout Provider On-Site Activities ..................................................................... 58
2.1.4.1 Ensure compliance with BASF Security Guidelines .................................... 58
2.1.4.2 Ensure transport security of assets ............................................................. 58
2.1.4.3 Process Dead on Arrival (DOA) cases ........................................................ 59
2.1.4.4 Scan Assets................................................................................................ 59
2.2 4Q Reporting ................................................................................................................. 60
2.3 Using gAHD ................................................................................................................... 61
2.3.1 Introduction........................................................................................................ 61
2.3.2 Access to gAHD ................................................................................................ 61
2.3.3 Process description ........................................................................................... 62
2.3.4 Notification about Incident Tickets ..................................................................... 65
2.3.5 gAHD Login ....................................................................................................... 66
2.3.6 Creating a New gAHD Incident Ticket................................................................ 67
2.3.7 Editing an Existing Incident Ticket ..................................................................... 67
2.3.7.1 Incident Ticket Selection ............................................................................. 67
2.3.7.2 Assigning a gAHD Incident Ticket to an assignee group ............................. 68
2.3.7.3 Self-assignment of an incident ticket ........................................................... 70
2.3.7.4 Assignment of an incident ticket to a member of your assignee group ........ 71
2.3.7.5 Updating the gAHD Incident Ticket Status .................................................. 72
2.3.8 Sending an E-mail Notification to a User............................................................ 74
2.3.9 Searching for an Incident Ticket ........................................................................ 75
2.3.9.1 Searching for an Incident Ticket with Incident Ticket Number Not
Available ..................................................................................................... 75
2.3.9.2 Searching for all Incident Tickets of a Certain User..................................... 77
2.3.10 Displaying Asset Information ............................................................................. 79
2.3.11 Displaying Contact Information .......................................................................... 84

2.4 Rollout Provider Central Operations............................................................................ 86
2.4.1 H.29 Central Check of Goods ............................................................................ 86
2.4.2 Check technical readiness of staging area......................................................... 87
2.4.3 Monitor the Installation of GPS III Assets........................................................... 88
2.4.4 Monitor the Migration Status Centrally ...............................................................
2.4.5 89
Relocate a GPS II asset during the POIS Phase ............................................... 90
2.4.6 Process stolen GPS III assets ........................................................................... 91
3 Rollout Provider: Handling at Delivery Points ................................................................. 93
3.1 Delivery Point 1 – Storage Area – New Equipment ..................................................... 93
3.1.1 Prerequisites ..................................................................................................... 93
3.1.2 H.24 Takeover of Assets ................................................................................... 96
3.1.3 H.25 Maintain availability of Assets in BISTRO .................................................. 98
3.1.4 H.32 Move asset to DP2 .................................................................................... 99
3.2 Delivery Point 2 – Staging Area.................................................................................. 100
3.2.1 Prerequisites ................................................................................................... 100
3.2.2 H.33 Assign Asset to Rollout Case .................................................................. 103
3.2.3 Create a bootable USB hard disk..................................................................... 105
3.2.4 H.35 Setup and Install GPS III Asset incl. User-spec. BSAs and Feedback to
BISTRO ........................................................................................................... 108
3.2.5 H.37 Transport reported Assets to Delivery Point 3 ......................................... 115
3.2.6 Special Cases.................................................................................................. 118
3.2.6.1 GPS III asset is returned from DP3 ........................................................... 118
3.3 Delivery Point 3 – Users' Desk ................................................................................... 119
3.3.1 Prerequisites ................................................................................................... 119
3.3.2 H.38: Unpack and Install of Asset at User's desk ............................................. 122
3.3.3 H.39 Start Data Migration ................................................................................ 126
3.3.4 Check Activation of Pre-Boot Authentication.................................................... 140
3.3.5 H.41 Finalize Data Migration and prepare Initial Acceptance. Update GPS III
Asset location in BISTRO ................................................................................ 142
3.3.5.1 Personalize the User’s Smartcard............................................................. 143
3.3.5.2 Perform additional services....................................................................... 144
3.3.6 B.42 Perform functional test to receive Initial Acceptance by the User............. 145
3.3.7 Start Configuration of BitLocker Encryption on an external USB hard disk....... 147
3.3.8 H.50 Report Incidents ...................................................................................... 155
3.3.9 H.47 Remove old GPS II Asset from User's desk ............................................ 157
3.3.10 H.48 Transport to Delivery Point 4 ................................................................... 162
3.3.11 Special Cases.................................................................................................. 166

3.3.11.1 Rollout assets to VIPs............................................................................... 166
3.3.11.2 Remove a BIOS password........................................................................ 169
3.3.11.3 Return GPS III Asset from DP3 to DP2.5 or DP1 ...................................... 172
3.3.11.4 Perform the User’s iPass registration ........................................................ 174
3.3.11.5 Install UMTS if user's UMTS card is available ........................................... 178
3.3.11.6 Install LR applications ............................................................................... 186
3.3.11.7 Install locally attached devices and local business-specific applications
(BSA) ........................................................................................................ 191
3.3.11.8 Process a GPS III asset whose Initial Acceptance was rejected ............... 192
3.3.11.9 Rollout GPS III assets to Home Users ...................................................... 193
3.3.11.10 Rollout GPS III assets to Travel Users.................................................... 196
3.3.11.11 Rollout a GPS III asset when the GPS II asset is not available ............... 198
3.4 Delivery Point 4 – Storage Area – Legacy Equipment .............................................. 199
3.4.1 Prerequisites ................................................................................................... 199
3.4.2 H.49 Maintain Asset Location for old GPS II Assets ........................................ 200
3.4.3 H.54 Deletion of data stored on old GPS II Asset ............................................ 202
3.4.4 H.55 Report all assets, whose data was deleted, in BISTRO ........................... 203
3.4.5 H.59 Transport to Delivery Point 5 ................................................................... 204
3.4.6 Special Cases.................................................................................................. 205
3.4.6.1 Return a GPS II asset to the User............................................................. 205
3.4.6.2 Print a DP4 inventory list........................................................................... 207
3.5 Delivery Point 5 – Handover ....................................................................................... 208
3.5.1 Prerequisites ................................................................................................... 208
3.5.2 H.60 Hand-over old GPSII Assets to Broker .................................................... 210
3.5.3 H.63 Maintain old GPS II Assets handed over to Broker in BISTRO ................ 212
4 Removal Provider: Deleting data at Delivery Point 4 .................................................... 213
4.1 General Prerequisites ................................................................................................. 213
4.2 Delete data ................................................................................................................... 215
5 Exceptions and Error Handling....................................................................................... 219
5.1 Delivery Point 1 – Storage Area – New Equipment ................................................... 219
Defective asset while located at DP1 or at transport to DP2 ............................... 219
5.2 Delivery Point 2 – Staging Area.................................................................................. 220
No access to AD ................................................................................................... 220
No BISTRO access .............................................................................................. 220
Insufficient numbers / wrong / defective assets delivered from DP1.................... 220
Issues concerning the rollout wizard .................................................................... 220
5.3 Delivery Point 3 – User's Desk ................................................................................... 221
Rollout numbers cannot be reached .................................................................... 221
Replanning of the rollout because of errors or complaints or incidents ............... 221
User relocates, rollout is carried out in a new location ......................................... 221
User cannot be found at location described in rollout appointment ..................... 221

User has requested a schedule change ............................................................... 221
Rollout Technician cannot keep appointment ...................................................... 222
User has no time at the time of the scheduled appointment. ............................... 222
5.4 Connection problems ................................................................................................. 223
Rollout Technician cannot connect to BISTRO .................................................... 223
Smartcard: User cannot log on to MyID ............................................................... 223
5.4.1 VIP .................................................................................................................. 224
VIP: Technical problems during rollout................................................................. 224
VIP: installation cannot be terminated .................................................................. 224
5.4.2 GPS III Asset ................................................................................................... 225
GPS III Asset has to be returned .......................................................................... 225
Card reader is defective ....................................................................................... 225
The wrong GPS III asset is delivered ................................................................... 225
Missed or wrongly supplied periphery of GPS III asset ........................................ 225
A defective PC was delivered ............................................................................... 226
A defective keyboard, mouse or docking station was delivered or hardware
is incomplete ......................................................................................................... 226
5.4.3 GPS III Software .............................................................................................. 227
User wants to change software on GPS III asset ................................................. 227
Lotus Notes icons are missed .............................................................................. 227
Business-critical BSA is not available .................................................................. 227
Non-business-critical BSA is not available ........................................................... 228
User has taken the new hardware with him ......................................................... 228
User wants to test BSAs ....................................................................................... 228
User wants to test special Services not ordered .................................................. 229
User wants installation of additional Services which were not ordered ............... 229
5.4.4 GPS II Asset and Periphery ............................................................................. 230
User's printer / scanner not declared via BISTRO beforehand ............................ 230
User wants to keep GPS II asset.......................................................................... 230
5.4.5 Approval / Acceptance ..................................................................................... 231
User and Information Manager agree to refuse the acceptance of the new
computer ............................................................................................................... 231
Postponed Initial Acceptance overview (Installation cannot be completed
during normal working hours) ............................................................................... 231
Migration has passed successfully, but user has no time left and does not
want to perform the Initial Acceptance at present. ............................................... 232
User is not present for signing the Initial Acceptance .......................................... 232
User wants to have incident tickets processed .................................................... 232
5.4.6 Data Migration Wizard and Smartcard Enrollment ........................................... 233
User has forgotten/broken his employee badge................................................... 233
Smartcard: “..device ready to be collected” is missing ......................................... 233
Smartcard: User is not available during rollout..................................................... 233
Data Migration Wizard runs a long time and user has to leave............................ 233
Data Migration Wizard runs past the end of the normal working day .................. 234
Data migration fails on GPS III asset ................................................................... 234
Data Migration Wizard aborts ............................................................................... 234
Data Migration Wizard icon not at desktop........................................................... 235
Data counter idle on the GPS III asset, script seems to have stopped ................ 235
Data Migration Wizard runs again after the user's first logon following the
migration ............................................................................................................... 235
GPS II-script does not start / aborts in the user environment .............................. 236

6 Troubleshooting: Contacting the GPS III support services .......................................... 237
6.1 Use cases for GPS III support services ..................................................................... 237
6.2 GPS III Rollout Service Desk ...................................................................................... 238
6.2.1 GPS III Rollout Service Desk Service Times.................................................... 238
6.2.2 GPS III Rollout Service Desk EMEA ................................................................ 239
6.2.2.1 EMEA: Central .......................................................................................... 240
6.2.2.2 EMEA: CIS Countries ex Russia ............................................................... 241
6.2.2.3 EMEA: CIS Countries Russian Federation ................................................ 242
6.2.2.4 EMEA: Middle East / South Africa............................................................. 243
6.2.2.5 EMEA: North............................................................................................. 239
6.2.2.6 EMEA: South ............................................................................................ 240
6.2.2.7 EMEA: West ............................................................................................. 239
6.2.2.8 EMEA: Switzerland ................................................................................... 241
6.2.3 GPS III Rollout Service Desk: Phone numbers APAC...................................... 244
6.2.3.1 Calls from within a BASF site .................................................................... 244
6.2.3.2 Calls from outside a BASF site ................................................................. 244
6.2.4 GPS III Rollout Service Desk: Phone numbers NA .......................................... 246
6.2.5 GPS III Rollout Service Desk: Phone numbers SA .......................................... 247
6.2.6 GPS III Rollout Service Desk: E-mail addresses APAC, NA, SA...................... 248
6.3 24/7 DTM Support Team.............................................................................................. 249
6.4 Technical Expert Team ............................................................................................... 250
6.5 Rollout Coordination................................................................................................... 251
7 Appendix .......................................................................................................................... 252
7.1 FAQ .............................................................................................................................. 252
7.2 GPS III Process Chart ................................................................................................. 254
7.3 GPSIII Infrastructure Storage Server -Prerequisites and Configuration for
Staging Areas .............................................................................................................. 260
7.3.1 Introduction...................................................................................................... 260
7.3.1.1 Purpose .................................................................................................... 260
7.3.1.2 Requirements ........................................................................................... 260
7.3.1.2.1 Infrastructure Storage Server (MYPACK.BASF.NET) ...................... 260
7.3.1.2.2 Hardware .......................................................................................... 260
7.3.1.2.3 Software............................................................................................ 260
7.3.1.2.4 Communication (Ports and Protocols) .............................................. 262
7.3.2 Configure software repository of GPSIII Infrastructure Storage Server ............ 262
7.3.3 Installation and Configuration of GPSIII Infrastructure Storage Server............. 270
7.3.4 Installation ....................................................................................................... 270
7.3.5 Configuration ................................................................................................... 272
7.3.6 File permission for Anonymous Authentication ................................................ 277
7.3.7 Testing Download ............................................................................................ 278

7.4 Work instruction: Creating a script for keeping DTM Software Repositories up-
to-date .......................................................................................................................... 280
7.4.1 Introduction...................................................................................................... 280
7.4.1.1 Requirements ........................................................................................... 280
7.4.2 Creating a script to sync the repository ............................................................ 280
7.4.3 Scheduling a synchronization job .................................................................... 281
7.5 Tables........................................................................................................................... 285
7.6 Figures ......................................................................................................................... 287
7.7 Bibliography ................................................................................................................ 294
7.8 Glossary....................................................................................................................... 295

1 Introduction
1.1 Abstract
This document is a work instruction for the Rollout Provider of the Global
PC Standardization (GPS) III rollout of BASF. The document defines in
detail the requirements of BASF regarding the Service of the Rollout
Provider for the BASF project GPS III:
 Services required from Rollout Provider.
 Details of accomplishment of Services.
o Handling of Services at properties of BASF.
o Usage of dedicated IT-services and dedicated tools of

BASF.
o Organization and management of rollout.
o Details of service execution at Delivery Points (DP) of

service.
o Error and escalation management.
This document introduces the GPS III project, processes and assets, in
addition several policies, procedures and basic conditions to provide
Services at BASF as well as detailed information on planning, reporting and
service delivery for the Rollout Provider for GPS III.

1.2 Usage of this Document
1.2.1 How to interpret symbols

The following symbols are used to explain specific situations to the reader.
Critical information about show-stopping situations
Important information to avoid problems

 Requirements and prerequisites to fulfill the following steps
 Single step to be carried out
 System reaction to a user input
1.2.2 How to read graphics

The figures used in this document contain position numbers which indicate
certain positions (e.g. a button which you have to click). To easily relocate a
position to which an instruction refers, the position numbers are arranged
clock-wise around the respective figure. The order of position numbers
does not correspond to the order of steps to be performed.

1.2.3 Wording
Screenshots of forms are always referenced in the related text blocks.
 Several UI-elements are shown within the screenshots. These UI-

elements will be referenced via their identifier, written bold.
 Reader-related actions in forms
o Actions on buttons are indicated by the phrase click.
o Actions on text boxes are indicated by the phrase insert.
o Actions on check boxes are indicated by the phrase check.
o Actions on menus, record tabs, combo-boxes, list-boxes,

lists and tables are indicated by the phrase select.
o Actions on table manipulation buttons, e.g. open, close, first,

next, previous, last, are indicated by their name.

1.3 GPS III Organization and Process
GPS stands for Global PC Standardization.
 Approximately 100,000 PCs will be replaced in 120 countries,

country-by-country, site-by-site, building-by-building and floor-by-
floor.
 The replacement procedure (mass rollout) will start in parallel in all

regions in October 2011 and will end in March 2012.
 Up to 5,000 software packages will be individually installed to the

new workplace environment.
Leading system for rollout information and coordination is BISTRO, see

chapter 2.1.2.3.
1.3.1 GPS III Project Organization

The Organization of the project Global Physical Rollout:
 Project Manager: Udo Wagner
 Project Office: Anke Roden
 BISTRO: Christopher Zyzik
 Logistic Coordination: Ulrike Klamm
 Rollout Coordination: Ilker Özbek
 Regional Rollout Coordinators:
o EMEA: Andreas Zabanoff, Günter Keller, Uwe Will
o AP: Alvina Chai, Mayank Gupta, Danny Bhadran
o NA: Herchiel J. Devalcourt
o SA: Marcos A. Ferreira de Silva, Rodrigo Matiello
 Point of Contact for GPS III Rollout Service Desk: Roland Socher,
Sebastian Jurischka

1.3.2 GPS III Countries
Table 1: Business Centers
Region Region / Business Center
SA Brazil
North
South
West
NA Canada
Central America
Mexico & Central America
Northeast Region
Northwest Region
Southeast Region
Southwest Region
EMEA Central
North
Russia & CIS
South
South Africa
Switzerland
Turkey & MENA
West
Germany
AP /
Table 2: Regions and Countries
EMEA AP NA SA
Algeria Australia Canada Argentina
Denmark Bangladesh Costa Rica Bolivia
Finland China Guatemala Brazil
Great Britain Hong Kong Dominican Chile
Republic
Ireland India Panama Colombia
Latvia Indonesia El Salvador Ecuador
Lithuania Japan Honduras Paraguay
Norway Malaysia Mexico Peru
Sweden New Zealand New York Uruguay
Azerbaijan Pakistan New Jersey Venezuela
Belarus Philippines Pennsylvania
EMEA AP NA SA
Kazakhstan Singapore Delaware
Russian Federation South Korea Minnesota
Ukraine Sri Lanka Michigan
Uzbekistan Taiwan Ohio
Greece Thailand Wisconsin
Italy Vietnam Oregon
Malta Illinois
Portugal Hawaii
Spain Iowa
South Africa Nebraska
France Washington
Germany Georgia
Switzerland Tennessee
Bahrain South
Carolina
Egypt North
Carolina
Jordan Florida
Morocco Virginia
Oman Kentucky
Qatar Puerto Rico
Saudi Arabia Texas
Tunisia Arizona
Turkey Louisiana
United Arab Emirates Mississippi
Belgium Colorado
Netherlands California
Austria Alabama
Czech Republic Missouri
Slovakia Arkansas
Slovenia
Bosnia and Herzegovina
Croatia
Serbia
Hungary
Poland
Bulgaria
Romania

Table 3: Pre-Pilot Regions and Countries
Region Countries
AP Singapore
NA New York, New Jersey
SA Brazil
EMEA Germany
Table 4: Pilot Regions and Countries
Region Countries
AP Taiwan, Singapore
NA New York, Georgia, Texas
SA Brazil
EMEA Germany

1.3.3 GPS III Rollout Process Stages & Roles
The GPS III workflows are defined in detail in a process chart (see
chapter 7.2). See Figure 1 for an overview of the Delivery Points. A
definition of the roles within GPS III Rollout process is shown in Table 5.
Figure 1: GPS III Process by Stages
Table 5: Roles in GPS III Rollout Process
Role Description
User Gets the GPS III assets, accepts the GPS III asset and the
successful Rollout via Initial Acceptance.
Information Manager User escalation instance within the GPS III Rollout Process
Program Management Overall responsibility for the program; escalation instance for
project managers
Site Coordinator Contact to provide information about sites and locations
Regional Rollout Contact to coordinate rollouts at sites and locations
Coordinator
IS Service Desk Service Desk for all incidents; moves; changes and additions
(IMAC) with exception to the GPS III Rollout Process
GPS III Rollout Service Service Desk for all incidents; moves; changes and additions
Desk (IMAC) within the GPS III Rollout Process
Rollout Coordinator Schedule and coordinates the rollout
Rollout Provider Delivers defined Services
Rollout Technician Executes the hardware exchange according to the defined
GPS III Rollout Process
Hardware Provider Provides new hardware
Removal Provider Removal and Salvage Provider processes Data Deletion on
DP4 and removes the Hardware.
Role Description
Hardware Broker Is responsible for legacy equipment received from Removal
and Salvage Provider Delivery Point 5

1.3.4 GPS III Rollout Timelines and Milestones
The GPS III Rollout timeline is divided into 4 main rollout phases, separated
by 2 rollout breaks and 3 holiday periods (see Table 6).
The main replacement procedure starts in parallel in all regions in October

2011 with the mass rollout and ends in March 2012. See Table 7, Table 8,
Table 9 and Table 10 for the expected rollout volume.
Table 6: GPS III Timelines
Phase Start End Rollout Latest HW

Volumes delivery at
DP1
Pre-Pilot
th
August 29 , 2011 September 9 , 2011
th
~200 th
August 15 ,
2011
th rd
Rollout Break September 12 , 2011 September 23 , 2011
th
Pilot September 26 , 2011 October 7th, 2011 ~800 September
th
12 , 2011
th st
Rollout Break October 10 , 2011 October 21 , 2011
th th
Ramp Up October 24 , 2011 November 18th, 2011 ~12.245 October 10 ,
(EMEA, AP, NA) 2011
st
October 31 , 2011 (SA)
st st
Mass Rollout November 21 , 2011 March 31 , 2012 ~87.125 November
th
7 , 2011
Holiday Periods
1 st th
Thanksgiving November 21 , 2011 November 26 , 2011
st th
Christmas and December 22 , 2011 January 6 , 2012
New Year
st st
Chinese New January 20 , 2012 January 27 , 2012
2
year
1
United States only
2
All countries in APAC which are celebrating this event, e.g. China,
Taiwan, Malaysia, Korea, Hong Kong, Singapore

Table 7: Rollout Volume Pre-Pilot
Approximately
Duration PCs per PCs per PCs per
(CW) Region rollout phase months week PCs per day
2 EMEA 50 50 25 5
2 NA 50 50 25 5
2 SA 50 50 25 5
Pre-Pilot 2 APAC 50 50 25 5
Total per Rollout Phase 200
Table 8: Rollout Volume Pilot
Approximately
Duration PCs per PCs per PCs per
(CW) Region rollout phase months week PCs per day
2 EMEA 200 200 100 20
2 NA 200 200 100 20
2 SA 200 200 100 20
Pilot 2 APAC 200 200 100 20
Total per Rollout Phase 800
Table 9: Rollout Volume Ramp Up Phase
Approximately
PCs per day PCs per week
Dura PC's
tion week week week week week week week week per
(CW) Region 1 2 3 4 1 2 3 4 month
4 EMEA 150 300 450 600 750 1.500 2.250 3.000 7.500
4 NA 50 100 150 200 250 500 750 1.000 2.500
4 SA / 33 66 100 / 165 330 500 995

Ramp
-up 4 APAC 25 50 75 100 125 250 375 500 1.250
Total per Rollout Phase 12.245

Table 10: Rollout Volume Mass Rollout
Approximately
Duration Total PCs to be
(CW) Region rolled out PCs per week PCs per day
17 EMEA 54.876 3.228 646
17 NA 15.882 934 187
17 SA 4.479 263 53
Mass
rollout 17 APAC 11.888 699 140
Total per Rollout Phase 87.125

1.4 GPS III Hardware
1.4.1 Hardware Specification

The hardware specifications of the GPS III asset types are as follows:
 Table 11: Ultra Portable Notebook (13") – Dell Latitude E6320
 Table 12: Desktop Replacement Notebook (15") - Latitude E6520
 Table 13: Portable Workstation Notebook (17") – Dell Precision

M6600
 Table 14: Desktop – Minitower – Dell Optiplex GX990
 Table 15: Desktop Workstation (Tower) – Dell Precision T3500
Every specification can be printed out separately on one or two pages.
1.4.1.1 Ultra Portable Notebook (13") Dell Latitude E6320

Table 11: Ultra Portable Notebook (13") – Dell Latitude E6320
Ultra Portable Dell Latitude E6320

Notebook (13")
Operating Windows 7 Professional SP 1 64Bit
System
Processor Intel® Core™ i5-2520M (Dual Core, 2.5GHz, 3MB cache),
with vPro / iAMT 7.0
Harddisk 256GB SSD with SED Function OPAL Std.
RAM 8GB (2x4GB) 1333MHz DDR3 dual channel
CD Drive 8 x DVD+/-RW drive
Graphics Intel® integrated HD Graphics 3000
onboard
Sound onboard sound onboard
Network integrated 10/100/1000GB Ethernet
Interface
WLAN Interface Intel WiFi Link 6205 2x2 802.11 a/b/g/n
Modem External 56k worldwide USB Modem
Modem Dell Wireless™ 555 HSPA+ Mini Card5
Bluetooth Dell Wireless 375 Bluetooth
Interface
Input Devices USB dual tone optical mouse and QuietKey USB dual tone
keyboard
Input Devices Touchpad and country specific keyboard.
onboard
Input Devices Internal backlit keyboard
onboard
Interfaces 1 x USB 2.0; 1 x eSATA / USB 2.0

Ultra Portable Dell Latitude E6320
Notebook (13")
Onboard
Cam Integrated camera with microphone
Storage Card 6-in-1 SD card reader
Reader
Card reader Read/write capabilities: reads and writes to all ISO 7816
1/2/3/4 microprocessor cards (T=0, T=1)
Cards supported: 3V and 5V
Program technology supported: Java cards
Interface speed: 9600–115,200 BPS
EMV level: level 1 certified
WHQL certification
Battery 6 Cell 60Whr
Docking Station Dell Latitude E-Port (VGA, Display Port, DVI-D, HDMI, 6x
USB, eSATA)

1.4.1.2 Desktop Replacement Notebook (15") Dell Latitude E6520
Table 12: Desktop Replacement Notebook (15") - Latitude E6520
Desktop Dell Latitude E6520

Replacement
Notebook (15")
System
Processor Intel® Core™ i5-2520M (Dual Core, 2.5GHz, 3MB cache),
onboard
Interface
Modem Internal 56k Modem
Interface
keyboard
onboard
onboard
Interfaces 3 x USB 2.0; 1 x eSATA / USB 2.0
Onboard
Reader
WHQL certification
USB, eSATA)

1.4.1.3 Portable Workstation Notebook (17") Dell Precision M6600
Table 13: Portable Workstation Notebook (17") – Dell Precision M6600
Desktop Dell Precision M6600

Replacement
Workstation
Notebook (17")
Processor Windows 7 Professional SP 1 64Bit
Processor Intel® Core™ i7-2720QM (Dual Core, 2.2GHz, 6MB cache),
Graphic NVIDIA® Quadro™ 3 M 2GB
Interface
Modem External 56k worldwide USB Modem
Interface
keyboard
onboard
onboard
Interfaces 2 x USB 2.0; 1 x eSATA / USB 2.0; 2 x USB 3.0
Onboard
Reader
WHQL certificati
USB, eSATA)

1.4.1.4 Desktop – Minitower Dell OptiPlex 990
Table 14: Desktop – Minitower – Dell Optiplex GX990
All Purpose Dell OptiPlex 990

Desktop -
Minitower
System
Processor Intel® Core™ i5 25 (3.3 GHz, 6MB,), with vPro / iAMT 7.0
Slots 1 full height PCIe x16,
1 full height PCIe x16 (wired x 4),
1 full height PCIe x1,
1 full height PCI
Harddisk 320GB 7200 RPM Opal SED Hard Disk Drive
onboard
Interface
Interfaces USB 2.0 4 x Front and 6 x Back
keyboard
Storage Card optional external USB Solution avaliable
Reader

1.4.1.5 Desktop Workstation (Tower) Dell Precision T3500
Table 15: Desktop Workstation (Tower) – Dell Precision T3500
Workstation Dell Precision T3500

Desktop (Tower)
Operating System Windows 7 Professional SP 1 64Bit
Processor Intel XEON E3503 (2,4GHz, 4MB,2C), TPM, no vPro

Support;
Systems with vPro/iAMT support will be aviable est.
September 2011
Slots Two PCIe x8 slot wired as x4 (half-length); two PCIe x16
Gen 2 graphics slots; two PCI slots
Slots Two internal 3.5" HDD bays; two external 5.25" optical bays,
one of which can accommodate a third HDD in desktop
orientation;
One external 3.5" flex bay for floppy or media card reader
Eleven USB 2.0: two on front panel, six on back panel, three
internal
Controller SAS 6/iR Controller for SAS Support
Bus Type 6-channel SATA-II (3.0 Gbps)

with
RAID 0
RAID 1
RAID 0+1
RAID 5 Support
Graphic NVIDIA® Quadro™ 2 1GB
Harddisk Hitatchi Ultrastar 15K600 300GB 15.000rpm SAS HDD with

Opal SED
24 GB
Network Interface integrated 10/100/1000GB Ethernet
Interfaces USB 2.0 2 x Front 6 x Back; 1 x e-SATA Port
keyboard
Storage Card optional external USB Solution avaliable
Reader

1.4.2 Pictures
Find the pictures of the assets in the following chapters.
1.4.2.1 Ultra Portable Notebook (13") Dell Latitude E6320
Find the following pictures of the ultra portable notebook (13") Dell Latitude
E6320:
 Figure 2: Dell Latitude E6320; Front Side
 Figure 3: Dell Latitude E6320; Right Side
 Figure 4: Dell Latitude E6320; Back Side
 Figure 5: Dell Latitude E6320; Card Reader
 Figure 6: Dell Latitude E6320; Bottom Side
 Figure 7: Dell Latitude E6320; Bottom Side; Service Tag (serial

number)
Figure 2: Dell Latitude E6320; Front Side
Figure 3: Dell Latitude E6320; Right Side

Figure 4: Dell Latitude E6320; Back Side
Figure 5: Dell Latitude E6320; Card Reader
Figure 6: Dell Latitude E6320; Bottom Side

Figure 7: Dell Latitude E6320; Bottom Side; Service Tag (serial number)

1.4.2.2 Desktop Replacement Notebook (15") Dell Latitude E6520
Find the following pictures of the desktop replacement notebook (15") Dell
Latitude E6520:
 Figure 8: Dell Latitude E6520, Front Side
 Figure 9: Dell Latitude E6520, Left Side
 Figure 10: Dell Latitude E6520, Right Side
 Figure 11: Dell Latitude E6520, Back Side
 Figure 12: Dell Latitude E6520, Bottom Side
 Figure 13: Dell Latitude E6520, Bottom Side; Service Tag (serial
number)
Figure 8: Dell Latitude E6520, Front Side
Figure 9: Dell Latitude E6520, Left Side

Figure 10: Dell Latitude E6520, Right Side
Figure 11: Dell Latitude E6520, Back Side
Figure 12: Dell Latitude E6520, Bottom Side

Figure 13: Dell Latitude E6520, Bottom Side; Service Tag (serial number)

1.4.2.3 Desktop Replacement Workstation Notebook (17") Dell Precision
M6600
Find the following pictures of the workstation desktop (tower) Dell Precision
T3500:
 Figure 14: Dell Precision M6600; Left Side
 Figure 15: Dell Precision M6600; Right Side
 Figure 16: Dell Precision M6600; Back Side
 Figure 17: Dell Precision M6600; Bottom Side
 Figure 18: Dell Precision M6600; Bottom Side; Service Tag (serial
number)
Figure 14: Dell Precision M6600; Left Side
Figure 15: Dell Precision M6600; Right Side

Figure 16: Dell Precision M6600; Back Side
Figure 17: Dell Precision M6600; Bottom Side
Figure 18: Dell Precision M6600; Bottom Side; Service Tag (serial number)

1.4.2.4 All Purpose Desktop – Minitower Dell OptiPlex 990
Find the following pictures of the all purpose desktop –minitower Dell
OptiPlex 990:
 Figure 19: Minitower Dell OptiPlex 990; Front Side
 Figure 20: Minitower Dell OptiPlex 990; Left Side
 Figure 21: Minitower Dell OptiPlex 990; Back Side
 Figure 22: Minitower Dell OptiPlex 990; Back Side, Service Tag
(used to identify Asset Inventory Number)
Figure 19: Minitower Dell OptiPlex 990; Front Side

Figure 20: Minitower Dell OptiPlex 990; Left Side
Figure 21: Minitower Dell OptiPlex 990; Back Side

Figure 22: Minitower Dell OptiPlex 990; Back Side, Service Tag (used to
identify Asset Inventory Number)

1.4.2.5 Workstation Desktop (Tower) Dell Precision T3500
Note: The Dell Precision T3500 will be delivered as of February 2012.
Find the following pictures of the workstation desktop (tower) Dell

Precision T3500:
 Figure 23: Dell Precision T3500; Front Side
 Figure 24: Dell Precision T3500, Top Side
 Figure 25: Dell Precision T3500; Back Side
 Figure 26: Dell Precision T3500 Back Side, Service Tag (used to
identify Asset Inventory Number)
Figure 23: Dell Precision T3500; Front Side

Figure 24: Dell Precision T3500, Top Side
Figure 25: Dell Precision T3500; Back Side

Figure 26: Dell Precision T3500 Back Side, Service Tag (used to identify
Asset Inventory Number)
1.4.2.6 Dell External Mini USB Modem
Figure 27: Dell External Mini USB Modem

2 Rollout Provider
2.1 Basic Conditions for Rollout
2.1.1 Rollout Provider Employees

2.1.1.1 Behavior and Appearance during the Rollout
Inappropriate behavior:
Racism, discrimination, sexual harassment, salaciousness or other

inappropriate behavior (alcohol, drug abuse) will not be tolerated and will
result in immediate exclusion from the project and from any property of
BASF.
During the GPS III rollout the Rollout Technicians represent BASF
Information Services. Therefore the following rules of conduct must be
followed:
 Wear the BASF external company ID in a clearly visible place on

the upper body.
 Clean and orderly appearance.
 Shorts or torn trousers are not acceptable in the User environment.
 No inappropriate casual remarks or artifacts like obtrusive ear rings,

finger rings (wedding rings permitted), visible tattoos, symbols of
clubs, organizations, attitudes, etc. other than BASF or Rollout
Provider.
Maintain a professional appearance and behavior at all times:
 Greet with "Good morning" or "Good afternoon".
 Announce yourself as employee of the Rollout Provider.
 Announce the delivery of the User's PC on behalf of BASF

Information Services.
Examples of appropriate communication:
 "Good morning, my name is Miller. I'm here from Getronics and

would like to deliver your new PC on behalf of BASF Information
Services."

 "According to my information, we've scheduled an appointment with
you for today at 10:00 am."
 When late: "Please excuse me for being late."

Utmost importance: Avoid conflicts
In case of escalations:
 Communication with the user must always remain polite.
 Do not engage in argumentative discussion with User.
 Contact the Rollout Coordination:
o Brief them to contact the responsible Information Manager.

Before PC installation:
 Explain to the User with a few words what is going to happen.
 Brief User about the need of their presence after the installation to
enter their password for Login and to finalize the installation and for
Initial Acceptance.
Privacy of User:
 Turn away from User when User enters password.
Initial Acceptance: Support the process of Initial Acceptance described in

detail in chapter 3.3.4.
2.1.1.2 Teams
The Rollout Provider shall provide qualified teams at every Site to achieve
the rollout volumes for the Site as proposed in the Initial Rollout Plan (IRP).
The Rollout Provider shall exchange or add staff in the following cases:
 Rollout volumes are not achieved.
 Staff violates security or behavior rules, see chapter 2.1.1.1.
 Other major faults of the Rollout Provider to the rollout plan of

Rollout Coordination.

2.1.2 BASF Infrastructure and Tools
The Rollout Provider shall use several tools of the BASF tool infrastructure.
 Typically, the usage of these tools needs some preparation and

planning beforehand.
 The Rollout Provider is responsible for the timely initiation of the

preparation.
2.1.2.1 Active Directory
For GPSIII there will be one global domain called BASFAD.
2.1.2.2 Intranet
BASF uses the BASF Corporate Network (BCN). The major BASF tools
work within this network from every BASF site. To access the BASF
intranet, you have ensured the following:
 Every Rollout Technician has a BASF user account (BASFAD

account) (to be requested in advance).
 For the data migration, a Migration User BASFAD account is set up

at every GPS III asset. The Rollout Technician are informed about
the credentials:
o Migration User login: MigrationUser
o Migration User password: GPS3Rollout

2.1.2.3 BISTRO
BISTRO (BASF Information Services Tool for Rollout Activities) is

developed by BASF and is designed to support the general process for a
global physical rollout of new computer hardware.
The functions provided by BISTRO:
 Coordination of global physical rollout activities.
 User Communication
 Consolidation of rollout relevant information during GPS III project.
 Overall support of the Global Physical Rollout Process by bringing

the involved roles and their responsibilities together.
Access to BISTRO:
 You have a PC or Notebook with MS Internet Explorer 8 or higher.
 To access BISTRO, in the address field, insert the following URL:

https://IS-my-new-gpsiii-pc.basf.net/
For more information about BISTRO and its usage, see the (BASF:
BISTRO Manual, 2011).
2.1.2.4 IS Service Desk and GPS III Rollout Service Desk
Find the introductions to use gAHD in chapter 2.3.

2.1.2.5 Smartcard
The smartcards enrollment will be performed within the GPS III Rollout
Process. For more information, see chapter 3.3.5.1.
Categories of smartcards:
 Employee badge with chip already available (Figure 28).
 White blank card with the chip on it, to be handed out to the user by
the Rollout Technician (Figure 29).
The Users' GPSIII rollout day is as well the day of smartcard enrollment.
 An enrollment job for every user is prepared before the rollout day
by BASF smartcard enrollment.
 Several steps have to be fulfilled during the rollout day, see chapter
3.3.5.1.
Figure 28: Smartcard, Personalized
Figure 29: Smartcard, Not Personalized

2.1.3 Rollout Provider-provided Materials
To globally enable a continuous and errorless rollout at every BASF site,
the Rollout Provider shall provide all required materials at his own
expenses.
2.1.3.1 Basic Equipment (General Infrastructure)
You provide the basic equipment for the Rollout Provider personnel on any
Delivery Point. This basic equipment comprises, for example, the following
items:
 BASF gAHD account as described in chapter 2.3.
 Cell phones without camera, incl. call charges incurred.
 Other communication devices as required.
 Contact list with telephone numbers (team leader, Hotline).
 Work vehicles for on-site technicians such as trolleys, carts, cars,

trucks and other devices for material movement.
 All typical kinds of office equipment like phone, paper and pen.
 All typical kinds of IT-working equipment like IT-equipment to

access BASF intranet and BASF tools.
 Safety equipment (where demanded by BASF security): Minimum

Personal Protective Equipment which includes safety glasses, hard
hats (protective helmet), and steel toe shoes.

2.1.3.2 Basic Equipment (Carried by Rollout Technician)
You provide the basic equipment for the Rollout Provider personnel on any
Delivery Point. This basic equipment comprises, for example, the following
items:
 BASF AD account as described in chapter 2.1.2.1.
 BASF intranet access as described in chapter 2.1.2.2.
 BISTRO account as described in chapter 2.1.2.3.
 Hand-held barcode scanner of the following specification (Figure

30):
o Able to emulate keyboard input.
o Able to be configured to send additional characters

(i.e. carriage return) after scan.
o USB interface
Figure 30: Barcode Scanner, Example

2.1.3.3 Delivery Point 1
You provide, for example the following material to equip the Storage Area
where assets are being set-up and installed (Delivery Point 2):
 Basic equipment, see chapter 2.1.3.1 and chapter 2.1.3.2.
 Storage place for the storage of assets.
You provide, for example the following material to equip the Staging Area
where assets are being set-up and installed (Delivery Point 2):
 Server with Microsoft Server 2008 R2 with IIS – Infrastructure

Storage Server, e.g. Hewlett Packard ML350 T06 (Man. No.:
487928-421), Xeon Quad Core, 6x2GB RAM, 5x 600GB HDD (Man.
No.: 581286-B21) (Installation already delivered to Rollout Provider
in a separate document)
 LAN access to the local Infrastructure Storage Server.
 Patch cables
 Monitor
 Keyboard, Mouse
 Gigabit Switch LWL-Ports, e.g. Cisco SRW2048-K9-EU. The size

depends on how many PCs have to be staged.
 Din A4 Printer to print the label for both the new GPS III and the
legacy GPS II asset.

You provide the equipment for Rollout Technicians (Delivery Point 3), such
as Rollout Technicians. This equipment includes, but is not limited to, the
following items:
 PC/Notebook with UMTS for access to BISTRO
 Printer to print asset lists to be attached to delivery notes

If the GPS III asset is delivered to Home or Travel Users, it might be
advisable to print the asset lists in advance.
 For rollouts to Travel Users during sales meetings you have a

VPN Router (e.g., Draytek Vigor 3100)
 For rollouts to Travel Users during sales meetings the Rollout

Coordination has ensured an internet connection is available at the
respective site so that the BASF Corporate network is available via
the VPN router.
 5-port Gigabit-switches (e.g., TP-Link TL-SF1005D)
 LAN cables (2 per switch)
 Cable fixer
 5-socket power bar / per switch
 10m power extension cord per switch
 Scotch tape (to attach the routing slip on the legacy equipment)
 Tools and equipment that is mutually agreed (e.g., workshop tools,

screwdriver, tongs)
 Display to start the Data Migration Wizard on new assets without

monitor, therefore a so called monitor switch / crossover switch (if
legacy equipment has monitor) or a 17" TFT display
 Permanent marker

You provide, for example, the following material to equip the Storage Area
– Legacy Equipment where assets are stored until final date of erasure
(Delivery Point 4):
It is recommended to prepare separate storage places for assets according

to the following constraints:
 Storage place for the deletion of assets
o Store assets prepared for data deletion.
 Storage place for the return of assets
o Store assets prepared to be returned to the user until final

date of erasure is reached.
o Store assets prepared for data deletion at the storage place

for the deletion of assets.
 Storage place for the quarantine of assets
o Quarantine assets are assets with open tickets, therefore

incomplete incidents.
o Store assets prepared to be taken to storage place for the

return of assets if ticket is closed.
o Store assets prepared to be returned to user until final date

of erasure is reached.
It is recommended to prepare the deletion of assets:
 If the Rollout Provider is responsible for the data deletion, he shall

ensure that the data deletion complies with the following
requirements, standards and recommendations:
o U.S. Department of Defense (DOD5220.22-M)
o German Federal Office for Security in Information

Technologies (BSI)
 BSI Baseline Protection Manual M 2.167 and M 4.32
 The deletion of assets shall be prepared in advance.
Prepare deletion stations:
 Equipped with DoD-certified software to irretrievably delete the data

on the hard drives of the devices.
 Equipped to connect simultaneous to several devices

Prepare the provision of deletion logs:
 Create separate directories with logs for each "deletion day".
 Prepare additional data per asset, to be provided to BASF, on a

daily basis (see Table 16).
Prepare assets for deletion:
 Load batches of 15 devices each in 3 levels in a rolling container.
 The device connection ports must all be accessible from the front.
Table 16: Additional Deletion Information, example
Information Value
Rollout ID PC 47000
Serial number F13NP1J
Inventory number 70090798
Employee ID FFDOCKK
Production day 15 Nov. 2011

 You have requested information about third party to handover

assets (Hardware Provider, Hardware Broker) via rollout manager.

2.1.4 Rollout Provider On-Site Activities
On-site activities of the Rollout Provider shall be in accordance with BASF
rules and regulations:
 Strictly follow orders of Site security. Noncompliance will result in

immediate prohibition of access to BASF properties global and
potential additional sanctions to Rollout Provider.
 No hardware is allowed to enter or leave site without explicit

permission of site security.
 It is strictly forbidden to take pictures / videos / audios or any other

media recording of BASF properties.
 It is strictly forbidden to use so called social media (twitter,

facebook, etc.) about BASF related topics.
 It is strictly forbidden to use open fire except in specially designated

areas (smoking areas).
 It is strictly forbidden to place and/or consume alcohol or drugs at a

BASF property.
Site security is allowed to carry out identity and security checks to any
person on site.
With the entering of a BASF site one agrees to any of the BASF rules and
regulations. One should not enter the site if this is not agreed to.
2.1.4.1 Ensure compliance with BASF Security Guidelines
 Ensure compliance with the BASF Security Guidelines. For more

information, under https://www.basf.net, select Guidelines.
2.1.4.2 Ensure transport security of assets
 If an asset is moved from on location to another and if this asset has to

leave and reenter BASF property, ensure that the BASF rules of
security (BASF GPS III PO: GSA - General Service Agreement, 2010)
are being observed.

2.1.4.3 Process Dead on Arrival (DOA) cases
Dead on Arrival (DOA) is defined as follows:
 At DP1 (receipt of goods), a GPS III asset does not pass the visual
check. For more information, see chapters 3.1.2 and 3.1.3.
 At DP2 (staging area), a GPS III asset cannot be booted and

installed. For more information, see chapter 3.2.4.
 At DP3 (User’s desk), a GPS III asset cannot be booted or (if

applicable) a GPS III monitor is defective. For more information, see
chapter 3.3.3.
2.1.4.4 Scan Assets
The rollout provider shall scan the asset's service tag (to be found on the
asset). See chapter 1.4.2 for the location of the service tag:
 The service tag on workstations is usually on the back side of the

workstation.
 The service tag on laptops is usually on the bottom side of the

laptop.

2.2 4Q Reporting
The Rollout Provider shall report the 4Q report on a weekly basis. Find the
4Q report template in Figure 31 and Figure 32.
Figure 31: 4Q-Report Page 1
Figure 32: 4Q-Report Page 2

2.3 Using gAHD
The Rollout Provider shall use the global Advanced Help Desk (gAHD)
globally.
Incidents: The Rollout Provider shall solve incidents assigned within gAHD
to the Rollout Provider.
2.3.1 Introduction
The global Advanced Help Desk (gAHD) is the BASF used internal ticketing
system. Usage of global gAHD:
 gAHD is used by the IS Service Desk and GPS III Rollout Service
Desk.
 gAHD shall be used by the Rollout Provider
Objectives of the GPS III Rollout Service Desk:
 Support during communication phase of GPS III rollout
 Rollout support
 POIS = Post Installation Support: rollout day + 5 days
 VIP-POIS: rollout day + 6 weeks
2.3.2 Access to gAHD

You can access the gAHD via the BASF intranet:
 Link: http://support.basf-it-services.net (intranet)
 Access
o Access via gAHD account
o Request gAHD account beforehand via GPS III PO.
o The Rollout Provider shall name a responsible contact for

every gAHD Rollout Provider assignee groups (see chapter
2.3.3) with the request of the gAHD account.
o If the Rollout Providers wants to get email notifications for

incident tickets (see chapter 2.3.4) the Rollout Provider has
to provide one email address for the regions AP, EMEA, NA
and SA with the request of the gAHD account.

2.3.3 Process description
The Rollout Provider is responsible for the solving of all incidents assigned
to the gAHD Rollout Provider assignee groups (see Table 17), e.g.
incidents like shown in Table 18:
 Assignee process
A. GPS III Rollout Service Desk assigns incident tickets to the

gAHD Rollout Provider assignee groups.
B. Rollout Provider shall solve the incident.
 Incident solving
o The Rollout Provider shall solve incidents assigned to the

gAHD Rollout Provider assignee groups.
 The Rollout Provider shall process the incident

tickets as sketched in Table 19.
 The Rollout Provider shall not close tickets, as tickets

are closed by the GPS III Rollout Service Desk.
 For the general gAHD incident process and status

codes, see Figure 33.
 See the following subchapters for detailed

instructions on the usage of gAHD.
o Execution of the post installation service requests of the user

is in the responsibility of the Rollout Provider
Table 17: gAHD Rollout Provider Assignee Groups
Region Rollout Provider assignee groups

EMEA eu.project.gps3.rollout-provider
NA na.project.gps3.rollout-provider
SA sa.project.gps3.rollout-provider
APAC ap.project.gps3.rollout-provider
Table 18: Incident Examples
Incident example Incident type

Defective hardware (HDD, mainboard. RAM) gw.project.gps3.hw
Rollout Technician left tools or other items at user desk gw.project.gps3.other
Data migration is not finished and has to be post- gw.project.gps3.post-poned
poned to next day
Incident example Incident type
Rollout Technician misses rollout appointment gw.project.gps3.other
Parts of the periphery of the GPS III asset were not gw.project.gps3.hw
delivered
Legacy equipment has to be returned to user gw.project.gps3.other
Table 19: Rollout Provider Processing of Incident Tickets
Nr. Step Detail

1 Assignment Assign incident ticket to you or a person in your group, see
chapter 2.3.7.2.
2 Ticket Process incident ticket, for example:
processing  Set status work in progress, see chapter 2.3.7.2.
 Insert respective exception / error descriptions, see
chapter 2.3.7.5.
 Insert other relevant information / solution, see
chapter 2.3.7.5.
 If User not available to solve the incident ticket
A. Set status wait for user action, see chapter 2.3.7.5.
B. Send an email to the User, see chapter 2.3.8.
3 End ticket End the ticket process if incident is fixed or incident is assigned to
process another group:
 Set incident to fixed: Set status Fixed (automatically QM will
start), see chapter 2.3.7.5.
 Assign incident ticket to another group, set status to Open,
see chapter 2.3.7.2.

Figure 33: gAHD Incident Process and Status Codes

2.3.4 Notification about Incident Tickets
The Rollout Provider shall be instantly aware of incidents assigned to the
gAHD Rollout Provider assignee groups. This can be done via real-time
monitoring or via e-mail notifications:
 Real-time monitoring via gAHD
 Communication about new incidents in the respective groups per

email (see Figure 34).
o Get an email about the incident status open, reopen and

assign.
o Request email notifications when requesting the gAHD

account via GPS III PO, see chapter 2.3.2.
Figure 34: E-mail Incident Notification

2.3.5 gAHD Login
gAHD login:
1. In MS Internet Explorer 8, open the following URL:

http://support04.basf-it-services.net
 The form Unicenter Service Desk is displayed (Figure 35).
Figure 35: Login to gAHD
2. Insert User Name and Password
3. Click Log In
 The main form of gAHD is displayed (Figure 36).
Figure 36: Main form of gAHD

2.3.6 Creating a New gAHD Incident Ticket
 To create a gAHD incident ticket, do the following:
A. Contact the GPS III Rollout Service Desk.
B. Brief them about the incident.
C. Ask them to open a gAHD incident ticket.
2.3.7 Editing an Existing Incident Ticket

2.3.7.1 Incident Ticket Selection
To select an existing incident ticket for editing, do the following:
1. Login to gAHD. For more information, see chapter 2.3.5.
Figure 37: Edit an Existing incident ticket in gAHD
2. Click Group Incidents/Problems (Figure 37).
 All incidents dedicated to your group are displayed in the

table Ticket List.
3. Click Ticket # to display the details (Figure 37).
 Details of the ticket are displayed.

2.3.7.2 Assigning a gAHD Incident Ticket to an assignee group
After having processed a gAHD incident ticket it can be necessary that

further process steps are carried out. If you have, for example, returned a
GPS II asset to a User, the Rollout Coordination has to document this in
BISTRO.
To assign a gAHD incident ticket to an assignee group, do the following:
1. Open the incident ticket, see chapter 2.3.7.1
 The incident ticket is displayed (Figure 37).

2. Select Activities – Transfer (Figure 39).
Figure 38: Assign a gAHD incident ticket: Activities – Transfer
 The Transfer Incident dialog box is displayed (Figure 39).

Figure 39: Assign a gAHD incident ticket: Transfer Incident dialog box
3. Under New Group (Figure 39-2), insert the assignee group (e.g.,
“eu.project.gps3.rollout-coordination”).
4. Under User Description (Figure 39-3), insert a description of what

is expected to be carried out by the assignee group (e.g., “In
BISTRO, assign the Reactivation of legacy PC service to the
rollout case”).
5. Click Save (Figure 39-1).
6. To transfer the gAHD incident ticket to the assignee group, do the

following:
A. Select Activities | Update Status.
B. Under New Status, select, for example, Open or Work on

Verfication, according to the respective case.
For more information about updating the gAHD incident
ticket status, see chapter 2.3.7.5.

2.3.7.3 Self-assignment of an incident ticket
To solve an incident, you assign a gAHD inceident ticket to yourself.
1. Open the incident ticket, see chapter 2.3.7.1

2. Select Activities | Take… (Figure 37).
 The responsibility of the ticket is set to you.
Figure 40: Self-assignment of an incident ticket

2.3.7.4 Assignment of an incident ticket to a member of your assignee group
1. Open the incident ticket. For more information, see chapter 2.3.7.1.
Figure 41: Incident Ticket Assignment, Menu Activities | Transfer…
2. Select Activities – Transfer… (Figure 41).
 The Transfer Incident form is displayed (Figure 42).
Figure 42: Incident Ticket Assignment to a Member of your Assignee Group
3. Insert the name of the person to New Assignee (Figure 42).
4. Click Save (Figure 42).
 The incident is assigned to the new assignee.

2.3.7.5 Updating the gAHD Incident Ticket Status
Update incident ticket status
1. Open the incident ticket. For more information, see chapter 2.3.7.1

2. Select Update Status… (Figure 43).
 The Incident Summary form is displayed.
Figure 43: Incident Ticket Status, Menu Activities | Update Status…
3. Select New Status, set status to the status you want.

Insert required additional information.
Set, for example, the status to the following values:
o Set status to Work in Progress
I. Select New Status, set status to Work in Progress,

(Figure 44).
Figure 44: Update Incident Ticket Status; Set Status to Work in Progress
o Set status to Wait for User Action
I. Select New Status, set status to Wait for User

Action (Figure 45).

II. If you want to stop the KPI time up to a respective
date while you wait for user's feedback: Insert the
respective date to Call Back Date / Time (Figure
45).
III. Insert User Description: The description of the

incident given by the user (Figure 45).
Figure 45: Update Incident Ticket Status; Set Status to Wait for User Action
o Set status to Fixed:
I. Select New Status, set status to Fixed (Figure 46). II.
Insert User Description (Figure 46): The description

of the incident given by the user.
III. Insert Resolver of the incident, usually your assignee

group (Figure 46).
IV. Select Solution Category, set Solution Category to

Repaired if the incident is repaired (Figure 46).
The automated quality assurance check starts (the
User is asked via e-mail if the incident is fixed).
Figure 46: Update Incident Ticket Status; Set Status to Fixed
4. Click Save
 The status of the incident ticket is set to the status you have
selected.
2.3.8 Sending an E-mail Notification to a User
To create an e-mail notification of a user, do the following:
1. Open the incident ticket, see chapter 2.3.7.1.

2. Select Manual Notify… (Figure 47).
 The Manual Notify form is displayed.

3. Insert the users you want to notify.
 An e-mail is sent to the user containing the status of the

ticket.
Figure 47: Manually Notify User about Status of Incident Ticket

2.3.9 Searching for an Incident Ticket
2.3.9.1 Searching for an Incident Ticket with Incident Ticket Number Not
Available
To search for an gAHD incident ticket when the gAHD incident ticket
number is not available, do the following:
1. Login to gAHD, see chapter 2.3.5.

2. Select Search – Incident (Figure 48).
 The form Incident Search is displayed (Figure 49).
Figure 48: Search for an Incident Ticket
Figure 49: Search for an Incident Ticket with Incident Ticket Number Not
Available
3. Set Active to empty (Figure 49).
4. Click Search (Figure 49).

Search for all tickets, included closed tickets.
 The form Incident List is displayed.

5. Select Incident # to display incident ticket (Figure 50).
 The incident ticket is displayed.

Figure 50: Select incident ticket to be displayed

2.3.9.2 Searching for all Incident Tickets of a Certain User
To search for all incidents of a certain user, do the following:
Figure 51: gAHD Main Form, Menu Search | Profile Browser
Figure 52: Profile Browser Contact Search
2. Select View – Profile Browser… (Figure 51).
 The form Profile Browser Contact Search is displayed

(Figure 52).
3. Insert user name in Last Name (or insert data to any other field in
the form) (Figure 52).
 The form Profile Browser Contact List is displayed (Figure

53).

Figure 53: Profile Browser Contact List
Figure 54: Incident History
5. Click the Name you want to display (Figure 53).
 The form Incident History is displayed (Figure 54).

6. Click the Incident History (Figure 54)..
 The respective incidents are displayed (Figure 55).
Figure 55: Incident History Table
7. Click the Click the Incident-# you want to display (Figure 55).
 The respective incidents details are displayed.

2.3.10 Displaying Asset Information
To search for and display asset information if a gAHD incident ticket
number is not available, do the following:
Figure 56: gAHD Main Form; Menu Search | Configuration Items
2. Select Search | Configuration Items (Figure 56).
 The Configuration Item Search form is displayed (Figure

57).

Figure 57: Configuration Item Search
3. Search for the respective configuration item. Related to your search

strategy use the fields to specify the search. Common search
strategies are the search for:
o Active and inactive assets
o Inventory number
o Serial number
o Certain contact
o Other information about the asset
Examples:
o Search for active and inactive assets (Figure 57).
I. Set Active to Empty (Figure 57).
II. Click Search (Figure 57).
o Inventory number (Figure 58).
I. Insert the inventory number to Alt CI ID (Figure 58).

Figure 58: Configuration Item Search
o Certain contact (Figure 59).
I. Insert Contact (Figure 59).
II. Insert Class (Figure 59).
III. Click Search (Figure 59).
Figure 59: Configuration Item List
o Name
I. Click Name (Figure 60).

Figure 60: Configuration Item List
Figure 61: Configuration Item Detail; Tab 4. Service
 After the click Search, the form Configuration Item Details

is displayed (Figure 62).
4. To display asset information, you have, for example, the following
options:
o To display the assets location, click 6. Location (Figure 62).
 The form Configuration Item Details tab 6. Location is

displayed (Figure 62).
Figure 62: Configuration Item Detail; Tab 6. Location

o To display the recorded contact(s), click 7. Contacts (Figure
63). The secondary contact (the one who uses an asset)
might be missed.
Figure 63: Configuration Item Detail; Tab 7. Contacts
o To display the guarantee period, click 2. Inventory.

2.3.11 Displaying Contact Information
Display contact information:
1. Login to gAHD, see chapter 2.3.5
Figure 64: gAHD Main Form
2. Select View | Profile Browser (Figure 64).
 The form Profile Browser Contact Search is displayed

(Figure 65).
Figure 65: Profile Browser Contact Search
1. To filter the data, insert data to any of the fields, e.g. insert the
User’s name in the Last Name field (Figure 65).
 The form Contact Information is displayed (Figure 66).

Figure 66: Contact Information
3. To display the contact data of the User, click Information (Figure

66).
 The Contact Information for <user> form is displayed

(Figure 66).
4. To display the hardware configuration assigned to the User, click
Environment (Figure 66).
 The Environment for <user> form is displayed (Figure 67).
Figure 67: Contact Information for <User>

2.4 Rollout Provider Central Operations
The description of the Rollout Provider's central operations is closely
oriented on the process steps as described in the GPS III process overview
chart, see chapter 7.2.
2.4.1 H.29 Central Check of Goods

In this step (see Figure 161), you ensure that a sufficient number of assets
is available for the rollout.
You can identify assets whose serial numbers are not matched to an order
confirmation and a rollout case.
Precondition: F26: Report of Differences in BISTRO (BISTRO)
Steps:
1. For all asset installations for rollout at the respective location, check
the delivery status of the assets.
For more information, in the BISTRO Manual, see Chapter 8.2.1
Check availability of assets (Central Check of Goods) (BASF:
BISTRO Manual, 2011)
2. If assets have not been delivered or are damaged, you ask the
Hardware Provider to deliver replacement assets.
3. If no spare assets are available and replacement assets cannot be

delivered in time, you call the Rollout Coordinator to possibly
reschedule the rollout of the asset.
4. You take notes of your actions taken in respect of the goods not
delivered or damaged. You enter your notes in BISTRO.
Check availability of assets (Central Check of Goods) (BASF:
BISTRO Manual, 2011)
5. Identify unmatched assets via BISTRO.

Identify assets not assigned to an order confirmation) (BASF:
Postcondition: E.30: Processing of Delta List (Rollout Coordination)

2.4.2 Check technical readiness of staging area
In this step, you ensure that the technical infrastructure required for setting
up assets is available at a DP2 location, according to the schedule.
Precondition: F31: Report Installations because of Rollout is near (BISTRO)
Steps:
1. At DP2, connect a sample asset to the BASF Corporate Network.
2. Perform a test installation of the asset. (Use the first installation of

an asset at Delivery Point 2 as test installation.)
3. If the test installation can be performed successfully, in BISTRO,

approve that the installation can be performed successfully.
For more information, in the BISTRO Manual, see Chapter 8.3
Check readiness of sites (DP2) (Move Asset to DP2) (BASF:
4. If the installation cannot be performed, contact the 24/7 DTM

Support Team.
Postcondition: H.33 Assign Asset to Rollout Case (Rollout Provider)

2.4.3 Monitor the Installation of GPS III Assets
You want to do the following:
 Inform the installation technician about finished installation
 Inform the 24/7 DTM Support Team about failed installations.
To do so, during the installation, you monitor the installation status

centrally.
For more information about monitoring the installation status, in the

BISTRO Manual, see Chapter 8.6 Monitor the installation process
(BASF: BISTRO Manual, 2011).
You do the following:
 To identify the failed installations: For more information about

monitoring the installation status, in the BISTRO Manual, see
Chapter 8.6.2 Monitor failed installations (BASF: BISTRO
Manual, 2011).
 To identify the finished installations: For more information about

monitoring the installation status, in the BISTRO Manual, see
Chapter 8.6.3 Identify asset ready for delivery to the User

2.4.4 Monitor the Migration Status Centrally
To ensure that all migrations processes are completed and the user can
continue to work as soon as possible, check the migration status centrally.
For more information, in the BISTRO Manual, see Chapter 8.8 Monitor the
migration of legacy data (BASF: BISTRO Manual, 2011).
You do the following:
 If the status Finished is displayed for an asset, send the Rollout

Technician to complete the migration process.
 If the status Error is displayed for an asset, the Technical Expert

Team is informed and restarts the migration remotely. If restarting
the migration by the Technical Expert Team seems to take too
much time, contact the Technical Expert Team.
After the Initial Acceptance (see chapter 3.3.6) the migration status is no
longer displayed in BISTRO.

2.4.5 Relocate a GPS II asset during the POIS Phase
You want to relocate an GPS II asset during the POIS phase, e.g. because
the asset is to be returned to the user from DP4 to the User's desk.
Steps
 In BISTRO, relocate the GPS II asset.

Relocate an asset during the POIS phase) (BASF: BISTRO Manual,
2011).

2.4.6 Process stolen GPS III assets
You detect that a GPS III cannot be retrieved in the warehouse and
therefore cannot be rolled out. To minimize the risk of delaying the rollout
you ensure that, as soon as possible, GPS III Logistics can place a new
order and that Rollout Coordination can reschedule the rollout case. To do
so, you register the missing GPS III asset(s), in gAHD, as stolen.
Steps
1. To create a gAHD incident ticket, contact the GPS III Rollout

Service Desk and ensure you provide the following data:
o Logical location: DP1, DP2 (after the GPS III asset was
assigned to a rollout case), or DP2.5
o Physical site and location
o Type of the location: BASF site or non-BASF site
o Serial number of the GPS III asset (Dell service tag)
o If applicable: Purchase order number
o If applicable: Rollout ID
o Name of the person who detected the theft
o Date and time when the theft was detected
 As soon as the gAHD incident ticket is created, it is assigned

to the gw.project.gps3.logistic assignee group. Logistics is
informed about the theft and carries out the following
activities:
 If no replacement asset(s) can be taken from the
buffer stock, create a new order
 Instruct the Rollout Coordination to reschedule the

rollout case(s)
 If the asset was stolen on a BASF campus, inform

the BASF investigation devision to start an
investigation and report the theft to the police
 If the asset was already assigned to ta rollout case,

instruct BISTRO to dissolve the assignment (so-
called divorce)
 Inform BASF Material Management
 Inform BASF Controlling

2. If the GPS III asset was stolen at a non-BASF site, additionally do
the following:
A. Note the incident ticket number.
B. Report the incident to the police.
C. In gAHD, do the following:
I. Open the incident ticket.
II. Upload a copy of the police theft report.
III. Ensure the incident is assigned to the

gw.project.gps3.logistic assignee group.
For more information about editing gAHD incident tickets,

see chapter 2.3.7.

3 Rollout Provider: Handling at Delivery
Points
The description of the handling at the Delivery Points (DPs) is closely

oriented on the process steps as described in the GPS III process overview
chart, see chapter 7.2:
 All the process steps at Delivery Points are named as described in

the GPS III process overview chart.
 Every process step the Rollout Provider has to perform is described

so that the goal of the respective process step can be met.
 For every process step of the Rollout Provider the respective pre-
and postcondition of the process is stated as described in the GPS
III process overview chart.
3.1 Delivery Point 1 – Storage Area – New

Equipment
Overview delivery of hardware:
 Rollout Provider get the hardware and handles the further Services
at the location (including logistics).
 The standard operating system and application images will not yet
have been installed.
3.1.1 Prerequisites
 Equipment for Delivery Point 1, see chapter 2.1.3.3.

30):


o USB interface

3.1.2 H.24 Takeover of Assets
In this step (see Figure 160), you ensure that the Hardware Provider
delivers the correct number and type of assets as indicated in the delivery
note.
Precondition: G.22 Shipping to Storage Area (Hardware / Leasingprovider)
Prerequisites:
 Optional: To scan the delivery note and send it to the GPS III
logistics team, you have a scanner.
Steps:
1. Receive hardware from the Hardware Provider. The delivery

personnel of the Hardware Provider have to stay at Delivery Point 1
until the delivery note of the asset is delivered.
2. Unpack the pallet.
3. Check the GPS III assets for Dead on Arrival (DOA). If the packing
of a GPS III asset is damaged, do the following:
A. Open the packing.
B. Check if the GPS III asset is damaged.
C. If the GPS III asset is damaged, decline the acceptance of

the GPS III asset.
D. To solve the issue, contact the Hardware Provider.
4. Note any declined GPS III asset on the delivery note.
5. Verify the correct quantity of the assets delivered:
A. Check incoming assets against the delivery note – is the

delivery note correct?
B. Note any fault on the delivery note.
6. To process the delivery notes, do the following:
A. Give Hardware Provider part of delivery note back to the

Hardware Provider.
B. Collect the customer part of the delivery notes to hand over

to BASF on request of BASF.
C. Optional:
I. Scan the customer part of the delivery note.

II. Send the customer copy of the delivery note, as a
PDF file, to the respective address provided in Table
20.
Table 20: Addresses for delivery note and transport documentation
Region Email Postbox

EMEA Gps3-logistic@basf.com
NA GPSIII-NA-Rollout-Team@basf.com
SA Gpsiii.sa@basf.com
AP is-gpsiii-logistics-ap@basf.com
7. Temporarily store the GPS III assets at an appropriate location (dry,

dust-free and secure).
8. Put defective GPS III assets aside.
Postcondition: H.25 Maintain availability of Assets in BISTRO (Rollout

Provider)

3.1.3 H.25 Maintain availability of Assets in BISTRO
In this step (see Figure 160), you ensure that all assets delivered by the
Hardware Provider are registered to BISTRO. To enable the repair of
defected assets, you ensure that defected GPS III assets are registered.
Precondition: H.24 – Takeover of Assets (Rollout Provider)
Steps:
1. To register the GPS III to BISTRO, you can do the following:
o Scan the asset.
o Insert the serial number manually.
o Upload an asset info file in csv format, exported from the

ERP system.
2. If the GPS III asset has a visible defect or if you are in doubt
whether the GPS III asset is damaged, in BISTRO, mark the asset
as defective.

Register assets at DP1 (Maintain Availability of Assets) (BASF:
Postcondition: F26: Report of Differences in BISTRO (BISTRO)

3.1.4 H.32 Move asset to DP2
In this step (see Figure 161), you ensure that the assets can be set up at
DP2, according to the schedule.
Precondition: F31: Report Installations necessary because Rollout is near.

(BISTRO)
Steps:
1. To identify the assets to be delivered within the next 10 business

days, and print a pickling list, use BISTRO.
For more information, in the BISTRO Manual, see Chapter 8.4 Plan
the installation of assets (Report Installations Necessary)
2. If you identify missing assets, contact the Rollout Coordinator.

Brief the Rollout Coordination to decide whether to postpone or to
deliver a spare part.
For more information about how to identify missing assets, in the
BISTRO Manual, see Chapter 8.4 Plan the installation of assets
(Report Installations Necessary) (BASF: BISTRO Manual, 2011).
3. Move the packages with the assets to Delivery Point 2.
Postcondition: H33: Assign asset to Rollout Case (Rollout Provider)

3.2 Delivery Point 2 – Staging Area
3.2.1 Prerequisites
 Server with Microsoft Server 2008 R2 with IIS – Infrastructure

Storage Server, e.g. Hewlett Packard ML350 T06 (Man. No.:
487928-421), Xeon Quad Core, 6x2GB RAM, 5x 600GB HDD (Man.
No.: 581286-B21) (Installation already delivered to Rollout Provider
in a separate document)
 LAN access to the local Infrastructure Storage Server.
 Patch cables
 Monitor
 Keyboard, Mouse
 Gigabit Switch LWL-Ports, e.g. Cisco SRW2048-K9-EU. The size

depends on how many PCs have to be staged.
 Din A4 Printer to print the label for both the new GPS III and the
legacy GPS II asset.


30):

o USB interface

3.2.2 H.33 Assign Asset to Rollout Case
In this step (see Figure 161), you ensure the following:
 You ensure that gAHD is able to configure the personalized

installation data and thus make possible the automatic installation of
each asset. To do so, for every site (or floor) you assign the
available assets to individual users (rollout cases).
 You ensure that a routing slip, containing the serial number, User
name and address as well as hardware and services to be
delivered, is attached to each GPS III asset assigned to a User.
Precondition: H32: Move asset to DP2 (Rollout Provider)
Prerequisites:
 You have verified the technical readiness of the staging area. For
more information, see chapter 2.4.2.
Steps:
1. Unpack the GPS III asset.
2. Connect the GPS III asset to power.
3. If the GPS III asset is a desktop PC, connect the asset to a monitor.
4. In BISTRO, do the following:
A. Assign the asset to a rollout case.
B. Print the respective routing slips for the GPS III asset to be
delivered to the User’s desk and the GPS II asset to be
removed from the User’s desk.
For more information, in the BISTRO Manual, see
Chapter 8.5 Assign assets to rollout cases (BASF:
Installation not carried out correctly
Due to technical reasons, the configuration and installation of the asset is

not to be carried out prior to 15 working days before the planned rollout
date. Otherwise the installation is not carried out. The GPS III asset would
be delivered without software, to the User (DP3). The Initial Acceptance by
the User would have to be declined.
To ensure you do not prepare the installation of assets whose rollout date
lies in a too distant future, specify a date range not exceeding the current
date plus 15 working days.

5. Attach the routing slip to the respective GPS III asset.
Postcondition: F34: Configuration of Back End Systems (e.g.BASFAD,

gAHD, etc.) (BISTRO)

3.2.3 Create a bootable USB hard disk
The Rollout Provider shall use the GPS III image for the deployment of the
USB-hard disk.
Prerequisites:
 You have the latest version of GPS III image.
 Request the GPS III Image Master disk from the GPS III Project
Office.
 The deployment environment includes the necessary IT

environment. For more information, see chapter 2.1.3.
 You have a PC with DVD/CD-ROM drive.
Locally registered (LR) applications are not installed via USB-disk. For
more information about the LR application installation, see
chapter 3.3.11.6.
Steps:
1. Via a LAN cable, connect a PC to the BASF corporate network.
2. Connect the USB disk, to which the GPS III image is to be

deployed, to the PC.
3. To connect a boot medium to the PC, you can do the following:
o Insert the GPS III Image Master disk in the DVD/CD-ROM

drive.
o Connect a USB hard disk containing the GPS III Image to

the PC.
4. Start the PC.
5. To enter the Boot menu, press F12.
 The boot menu is displayed (Figure 68).

Figure 68: Boot menu (= F12 Hotkey) during start-up-/boot-process
6. Depending on the boot medium, select the respective option:
o If you boot from a CD-ROM hard disk, select CD/DVD/CD-

RW Drive.
o If you boot from a USB hard disk, select USB Storage

Device (Figure 68-1).
 If you boot from a USB hard disk, the Windows

Deployment Wizard appears (Figure 69).
Figure 69: Windows Deployment Wizard
7. Select Administrative tasks (Figure 69-1).
8. Click Next (Figure 69-2).

 The Tools for support BIS PE dialog box appears (Figure
70).
Figure 70: Tools for support BIS PE
9. Select Create USB Disk (Figure 70-1).
 The Create BIS PE Boot Stick dialog box appears (Figure

71).
Figure 71: Create BIS PE Boot Stick
10. In the Create BIS PE Boot Stick options, select the USB Device
(Figure 71-1).
11. Click Create (Figure 71-2).
 A message is displayed that all data on the hard disk will be

removed.
12. To start the creation of the USB hard disk, confirm the data on the
USB hard disk can be removed.
 The USB disk creation process runs.

13. When USB disk creation process has finished, click Close (Figure
71).

3.2.4 H.35 Setup and Install GPS III Asset incl. User-spec.
BSAs and Feedback to BISTRO
In this step (see Figure 161), you ensure that each GPS III asset is installed
with the software package configured for the individual user. You monitor
the installation status and ensure that the 24/7 DTM Support Team restarts
failed installations if necessary.
Remote support during the installation process is not available. As soon as

the 24/7 DTM Support Team Rollout Wizard shows up, the system is
remotely reachable via the 24/7 DTM Support Team RC Viewer.
Do not change the preconfigured boot order, as setup and install could fail
if boot order is changed.
If you do not have access to the local Infrastructure Storage Server at DP2,
the setup and installation of the GPS III asset will fail.
Precondition: F.34 Configuration of Back End Systems (e.g.BASFAD,

gAHD, etc.) (BISTRO)
Prerequisites:
 At least 60 minutes have to be passed between assigning a rollout

case to the asset and installing the asset at DP2.
 You have created a bootable USB hard disk, see chapter 3.2.3.
 You have connected the local Infrastructure Storage Server at DP2,

see chapter 7.3.
 For the 24/7 DTM Support Team to be able to monitor the

installation process, you have connected the GPS III asset to BASF
network.
Steps:
1. Connect the asset to the local Infrastructure Storage Server.
2. If the GPS III asset is a notebook, do the following:
A. Ensure the WLAN switch is in position On (Figure 72-1).
B. Connect a bootable USB hard disk to the GPS III asset. For
more information about how to create a bootable USB hard
disk, see chapter 3.2.3.

The bootable disk must be connected directly to the
GPS III asset. Do not connect it to the docking station.
 On the Dell M6600, use one of the white USB 2.0 ports
located on the left side of the M6600. Do not use the
red USB 3.0 ports located on the right side of the
M6600.
Figure 72: WLAN switch in position On.
3. Switch on the GPS III asset.
4. If the GPS III asset cannot be booted, do the following:
A. To create a gAHD incident ticket, contact the GPS III Rollout

Service Desk.
The assignment of the User will be revoked.

B. To solve the issue, inform the Hardware Provider about the
DOA case.
C. In BISTRO, register a GPS III asset from the DOA pool. For
more information about how to register GPS III assets at
DP1, in the BISTRO Manual, see Chapter 8.1 Register
assets at DP1 (Maintain Availability of Assets) (BASF:
D. Repeat chapter 3.2
When you assign the GPS III replacement asset from the
DOA pool to the User, you have to confirm that it is a
replacement asset.
5. Press F12.
 The Boot Menu is displayed (Figure 73).

Figure 73: Boot Menu
6. In the Boot menu, select USB Storage Device (Figure 73-1).
7. Click Return on the keyboard.
 The respective files are loaded to the asset (Figure 74 and

Figure 75).
Figure 74: Boot PC from USB device
Figure 75: Boot PC from USB device
 The IP address is displayed.

 The Windows Deployment Wizard opens (Figure 76).

Figure 76: Windows Deployment Wizard
8. Select GPS3Deploy (Figure 76-1).
 The following happens without any interaction of the user:

o The distinguished name of the computer is generated.
o The installation process starts automatically (Figure 77,

Figure 78, Figure 79, Figure 80, Figure 81).
Figure 77: Windows Deployment
Figure 78: Windows Deployment: Expanding Windows files

Figure 79: Windows Deployment: Starting of services
Figure 80: Windows Deployment: Completing of the installation
Figure 81: Windows Deployment, Reboot
o Windows reboots (Figure 81).
o Windows starts. The GPS III asset is being configured for

the first boot (Figure 82 and Figure 83).

Figure 82: Windows starts
Figure 83: Windows Desktop preparation
o The Installation Wizard starts and installs additional settings

(Figure 84).
Figure 84: Installation wizard: Installing extra settings
o The Installation wizard reboots Windows.
o Windows 7 starts up.
o The Rollout Wizard starts (Figure 85).

Figure 85: Rollout wizard
o The Rollout Wizard performs final configurations and reboots

MS Windows.
o The GPS III asset is rebooted. The MS Windows Login

screen is displayed.
o The GPS III asset is installed and usable.
Postcondition: F36: Recognize Installation Status Information and report

FINISHED Setups (BISTRO)

3.2.5 H.37 Transport reported Assets to Delivery Point 3
In this step (see Figure 161), you ensure that each GPS III asset with the
software and hardware package configured for the individual user is
securely transported to the User desk (DP3), according to the schedule.
Precondition: F36: Recognize Installation Status Information and report

FINISHED Setups (BISTRO)
Prerequisites:
 You have printed a routing slip to be attached to the GPS II asset.
 You have provided standard items to be included in the package to

be delivered to the User, e.g. How-to-Start brochures, cables,
labels.
 The installation status, displayed in BISTRO, is Finished.
If applications have not been installed completely, do the following:

1. Contact the 24/7 DTM Support Team.
2. Rollout the GPS III asset to the User.
Steps:
1. Identify the assets which can be transport according to the schedule

as defined in the rollout planning.
Identify assets ready for delivery to the end user (Recognize
Installation Status) (BASF: BISTRO Manual, 2011)
2. To organize the transport of assets, you can, for example assign

assets to groups (e.g. “shelf 4”) and print, for example, checklists
via MS Excel.
Optional: Transport reported assets to DP3 (BASF: BISTRO
Manual, 2011).
3. To prepare an asset to be moved to Delivery Point 3, you ensure

the all items are included in the package to be delivered to the User.
For more information about which items belong to which asset type,
see Table 21.

Table 21: Hardware configuration of GPS III asset types
Hardware Pro- Desktop PC Desktop Ultra Portable Notebook

vided Model Replace-ment Notebook Dell Precision
by Optiplex Notebook Dell Latitude M6600
990MT Dell Latitude E6320 (see figures
(see figures E6520 (see figures in chapter
in chapter (see figures in chapter 1.4.1.3)
1.4.2.4) in chapter 1.4.1.1)
1.4.2.2)
Routing slip
to be attached to the GPS II asset
GTN    
How-to-Start brochure BASF    
Applicable only in EMEA: Health
Card
BASF    
Mouse pad BASF    
External USB hard disk
plus USB cable
GTN    
USB smartcard reader
plus USB cable
GTN  If ordered (see the routing slip)
Keyboard Dell KB212-PL
Quietkey USB Dualtone/Grey
DELL    
Dell USB Dual Tone Mouse DELL    
Power cord DELL 
Display Port to DVI Adapter DELL 
Power supply
(AC adapter + power cord)
DELL   
Port replicator + power supply
(AC adapter + power cord)
DELL   
Applicable only in Germany and
Switzerland: BGV A3 Prüfplakette
PC 5 and PC 1 labels for the
mobile power supply unit and the
corresponding power cable (see BASF   
Figure 86 and Figure 87,
respectively). The labels are
delivered to German Staging Area
(Herrenberg) by BASF.
Dell external USB modem
(see figure in chapter 1.4.2.6)
DELL  
Monitor with:
 Power cord
 DVI cable DELL If ordered (see the routing slip)
 VGA cable
 USB cable

4. Remove the following items from the asset and put the items aside
for later destruction:
o MS Windows 7 OEM CD/DVD
o MS Windows Manual
o Driver CD-ROMs
Climatic impact
To avoid climatic impact on GPS III assets (e.g. in winter):
If the rollout provider wants to use a Delivery Point 2.5 (post-staging area at
physical location of Delivery Point 3), request the location from BASF GPS
III Project Office in advance. BASF GPS III Project Office is not bound to
agree on the request, e.g. if no location is available, the request will be
declined.
If the location of DP2 is not identical with the physical location of Delivery
Point 3, on the appointment date of the User, transport the GPS III assets
to Delivery Point 2.5. Request the location of Delivery Point 2.5 from the
Regional Coordinator.
5. Securely move the GPS III assets to Delivery Point 3.
For more information, see chapter 2.1.4.2.
6. Remove the GPS III assets from the rolling container.
7. Take the GPS III asset to the respective User workplace.
Postcondition: H.38: Unpack and Install of Asset at User's desk (Rollout

Provider)

3.2.6 Special Cases
3.2.6.1 GPS III asset is returned from DP3
If a GPS III asset is returned from DP3, see the instructions in

chapter 3.3.11.3.

3.3 Delivery Point 3 – Users' Desk
Delayed rollout process
The GPS III rollout can be delayed if issues are not solved rapidly.
 Report and document all incidents.
For more information about reporting incidents, see chapter 3.3.8.
3.3.1 Prerequisites
 PC/Notebook with UMTS for access to BISTRO
 Printer to print asset lists to be attached to delivery notes

If the GPS III asset is delivered to Home or Travel Users, it might be
advisable to print the asset lists in advance.
 For rollouts to Travel Users during sales meetings you have a

VPN Router (e.g., Draytek Vigor 3100)
 For rollouts to Travel Users during sales meetings the Rollout

Coordination has ensured an internet connection is available at the
respective site so that the BASF Corporate network is available via
the VPN router.
 5-port Gigabit-switches (e.g., TP-Link TL-SF1005D)
 LAN cables (2 per switch)
 Cable fixer
 5-socket power bar / per switch
 10m power extension cord per switch
 Scotch tape (to attach the routing slip on the legacy equipment)
 Tools and equipment that is mutually agreed (e.g., workshop tools,

screwdriver, tongs)
 Display to start the Data Migration Wizard on new assets without

monitor, therefore a so called monitor switch / crossover switch (if
legacy equipment has monitor) or a 17" TFT display
 Permanent marker


30):

o USB interface

3.3.2 H.38: Unpack and Install of Asset at User's desk
In this step (see Figure 161), you ensure the GPS III asset is correctly
connected to the GPS II asset, to start the migration of legacy data.
Precondition: H.37 Transport the reported Assets to Delivery Point 3

(Rollout Provider)
Prerequisites:
 You have a GPS III switch.
 You have 2 LAN cables.
If the User is a VIP: Perform the additional steps described in

chapter 3.3.11.1.
Steps:
1. In BISTRO, identify the location of the asset to be delivered to the

user.
Identify assets ready for delivery to the end user (Recognize
Installation Status) (BASF: BISTRO Manual, 2011).
2. Via the routing slip attached to the GPS III asset, identify the User’s
room where the GPS III asset is to be delivered to.
Time window
The Rollout Technician has a time window of +/- 15 minutes from the
agreed appointment to arrive at the user's desk.
3. If the User is not present in the room indicated on the routing slip,
do the following:
A. Do not exchange the GPS II asset, do not start the rollout

procedure.
B. If you are informed that the User has moved to another

room, to ensure you keep to the timetable, do the following:
I. Roll out the GPS III asset only if the new room is right
next to the room indicated on the routing slip.
II. If you need more than 5 minutes to find the room, do

the following:
a. To create a gAHD incident ticket and

document the no-show of the User (due to

wrong location of the User), contact the
GPS III Service Desk.
b. Proceed with the next User.
C. If the room is correct but the User is absent, to ensure you

keep to the timetable, do the following:
I. Do not wait longer than 15 minutes after the time

agreed upon for the appointment with the User.
II. To report the incident, do the following:
a. To create a gAHD incident ticket and

document the no-show of the User, contact
the GPS III Service Desk.
b. In BISTRO, document the issue.
For more information about reporting incidents, see

chapter 3.3.8.
III. Proceed with the next User.
D. To take the GPS III asset back to DP2.5, put the GPS III
asset into the rolling container. For more information about
how to return GPS III assets back to DP2.5, see chapter
3.3.11.3.
4. If the User is present at his desk, unpack the GPS III asset.
5. If the User denies to accept the GPS III asset, do the following:
A. In BISTRO, let the User verify the hardware specification of

the GPS III asset. For more information, in the BISTRO
Manual, see chapter 5.3 Check and edit a proposal
(Check/Edit GPS III Proposal).
B. If the GPS III asset does not meet the specification or if the
User rejects the GPS III asset though the specification is
met, to process the rejected GPS III asset, proceed with
chapter 3.3.11.8.
6. To avoid an interruption of the rollout process, verify the availability

of the User for carrying out the Initial Acceptance.
Availability of the User
The User must be present to carry out, after the data migration was carried
out, the finalization of the data migration and the Initial Acceptance. The
data migration normally takes 3 hours, but it can take up to 24 hours. If the
User cannot be present on the next day, for example due to a business trip,

the User can designate a Subtitute User to carry out the Initial Acceptance.
To ensure the rollout can be carried out smoothly, do the following:
 To make provision for the case that the data migration takes more time
than normal, ensure the User can carry out the Initial Acceptance within
the next day(s).
 If a Substitute User must be designated, ensure the Substitute User

logs in to the User’s GPS II asset with the Substitute User’s AD
credentials, at least once.
Note: Designating a Substitute User is costly and is advisable only in

exceptional circumstances. If the Initial Acceptance has to be carried out by
Substitute User, the following User-specific services, if applicable, have to
be carried out after the rollout, in the BAU phase:
 Smartcard enrollment
 iPass registration
 BitLocker encryption of an external USB hard disk
Do not exchange peripherals.
7. Exchange the power connection with the one delivered with the
GPS III asset.
8. Applicable only to notebooks used in Germany and Switzerland:

Attach the BGV A3 Prüfplakette PC 5 (Figure 86-1) and PC 1
(Figure 87-1) labels to the respective items:
Figure 86: BGV A3 Prüfplakette PC 5 for mobile power supply units

Figure 87: BGV A3 Prüfplakette PC 1 for power cables
A. Attach the BGV A3 Prüfplakette PC 5 (Figure 86) to the

mobile power supply unit of the notebook.
B. Attach the BGV A3 Prüfplakette PC 1 (Figure 87) to the

power cable for the mobile power supply unit of the
notebook.
9. Connect the GPS III asset to power.
10. Connect the peripherals (e.g. monitor, keyboard and mouse) to the
GPS III asset.
11. If an external card reader is delivered with the GPS III asset,
connect the external card reader.
12. Connect the GPS III asset to the GPS III switch via LAN cable.
13. If the GPS II asset is not available, proceed with chapter 3.3.11.11.
14. Connect the GPS II asset to the GPS III switch via LAN cable.
15. To connect the GPS III to the BASF network, do the following:
A. If the rollout is carried out at a BASF site, connect the GPS

III switch to the BASF network socket.
B. If the rollout is carried out for a Home or Travel User,

connect the GPS III switch to the configured VPN router. For
more information about the VPN router, see chapters
3.3.11.9 (Home User rollout) or 3.3.11.10 (Travel User
rollout).
Postcondition: H.39 Start Data Migration (Rollout Provider)

3.3.3 H.39 Start Data Migration
In this step (see Figure 162), you ensure that the Migration Wizard
transfers legacy data from the User’s GPS II asset to the GPS III asset.
Precondition: H.38: Unpack and Install of Asset at User's desk (Rollout

Provider)
Prerequisites:
 You have a “Do not touch” note to be placed on the assets during
the migration process.
 If it is foreseeable that a Substitute User will have to carry out the

Initial Acceptance, the Substitute User was logged in to the Users’s
GPS II asset at least once.
Steps:
1. Ask the User if Windows 7 is already installed on the GPS II asset.
o If Windows 7 is already installed on the GPS II asset, do the

following:
 Brief the user: User is responsible for data migration,

possible installation of missing applications using
ongoing process and asset removal in ongoing
process.
 Do not carry out the data migration. Proceed with

chapter 3.3.6.
2. Ask the User whether the GPS II asset is secured via a BIOS
password (typically in the APAC region).
o If the GPS II asset is secured via a BIOS password, reset

the BIOS Password. For more information, see
chapter 3.3.11.2.
The Data Migration Wizard does not run if a BIOS password of an asset is
set.
3. If the GPS III asset is a notebook, ensure that WLAN is deactivated.

To do so, at the right side of the notebook, switch the WLAN
off (Figure 90-1).

Figure 88: WLAN switch in position Off
4. To login to the GPS III asset, do the following:
A. Switch on the GPS III asset.
 The Windows 7 Login is displayed (Figure 89).
Figure 89: MS Windows 7 Start Screen
B. If the GPS III asset cannot be booted or if the monitor (if

applicable) is defective, proceed with chapter 3.3.11.3,
step 3.
C. To login to Windows on the GPS III asset, in the User Name

field, insert MigrationUser (Figure 89-1).
D. In the Password field, insert GPS3Rollout.

E. Press Enter.
 The MS Windows desktop is displayed (Figure 91).
MigrationUser language is always English

To ensure the Technical Experts Team can remotely access GPS III
assets, globally, the displayed language of the MigrationUser is English.
 If necessary, inform the User that the User’s display language is as

defined in the GPS III asset proposal the User has approved.
 In the system tray, the Wi-Fi inactive icon is displayed

(Figure 90-1).
Figure 90: Wi-Fi inactive icon
F. Identify the IP address of the GPS III asset. To do so, on the

GPS III screen, click the GPS III Migration icon (Figure
91-1).
Figure 91: GPS III asset: Start GPS III Data Migration Wizard
 After some time, the GPS III Data Migration Wizard form is
displayed on the GPS III asset. The form displays the
<IP Address> (Figure 92-1).

Figure 92: GPS III Data Migration Wizard: Identify IP address of GPS III asset
 The External hard disk was not found message is

displayed.
Figure 93: GPS III Data Migration Wizard: External hard disk was not found
message
5. Connect the external USB hard disk to the GPS III asset.
6. To confirm the External hard disk was not found message, click
Retry (Figure 93-1).
7. If the External DATA partition is not empty message is displayed,

click Yes (Figure 94-1).

Figure 94: GPS III Data Migration Wizard: External DATA partition is not
empty message
8. Ensure the User is logged in to the GPS II asset.
9. On the GPS II asset, to ensure that network drives are mapped, do

the following:
A. Start the Windows Explorer.
B. Under My Computer, check whether network drives are

available (Figure 95-1).
Figure 95: Windows Explorer: Network drives
C. If no network drives are displayed, ensure the User is logged

in to Novell (applicable only in EMEA, NA, SA):
I. In the system tray, right-click on the Novell icon

(Figure 96).

Figure 96: Novell icon in system tray
II. In the context menu, select Novell Login (Figure

97-1).
Figure 97: Novell context menu
 The Novell login dialog box appears (Figure 98).
Figure 98: Novell login

III. Insert your Novell credentials (Figure 98-1).
IV. To confirm, click OK (Figure 98-2).
V. In the Windows Explorer, under My Computer, verify

that network drives are available (Figure 91). If no
network drives are displayed, contact the GPS III
Rollout Service Desk.
10. To start the migration process, do the following:
A. On the GPS II PC, in the Windows Start Menu click Run

(Figure 99-2).
 The Run form is displayed (Figure 100).
Operating System language

The name of the Run command depends on the operating system
language. In German, for example, the name of the command is
Ausführen.
Figure 99: GPS II PC; Search and Start Run

Figure 100: GPS II PC; Run the GPS II Data Migration Wizard
B. In the Open field, insert

\\<IP address>\migration\scripts\GPSii.exe (Figure 100-1)
where the placeholder <IP address> is to be replaced by the
IP address of the GPSIII asset as displayed by the Data
Migration Wizard (Figure 92).
C. Click OK (Figure 100-2).
 The GPS II Data Migration Wizard is displayed (Figure

101).
Figure 101: GPS II PC; GPS II Data Migration Wizard
D. If the LANCrypt key is red message appears, do the

following:
I. Press Yes (Figure 102-1).
The GPS II Data Migration Wizard is aborted.

II. To let the User login to LANCrypt, do the following:
a. In the system tray, right-click on the LANCrypt

icon.
b. Select Load encryption rules.
III. To restart the GPS II Data Migration Wizard, repeat

step 10.
Figure 102: GPS II Data Migration Wizard message: LANCrypt key is red
 Data of all user accounts used during the past 120 days is
being migrated.
E. Optional: Let the user confirm the message in which the
User is informed the migration is monitored centrally.
 When the migration is finished, on the GPS III asset, the

message GPS III Migration done completely is displayed.
11. To start the smartcard enrollment while the data migration is
running, perform the sub-steps indicated below.
This step applies in the following cases only:

 The User already has an employee badge with chip.
 The User does not have a smartcard yet. From the

local smartcard coordinator you have picked a
smartcard which is to be enrolled on the respective
day or the next day.
For a list of the local smartcard coordinators, see the
BASF intranet page Responsible Person
Smartcard Management (under
https://gu.basf.net/portal/basf/en/dt.jsp?setCurso
r=1_542598_542573).
For more information about smartcards, see chapter

2.1.2.5.

Special cases
 The User has more than one smartcard.
 Enroll the smartcard of the company the user

belongs to.
 You have rolled out an asset which is used by

multiple Users (Multi User computer).
 Perform the personalization for only one User.
Personalization of other users will be handled

separately for each user calling GPS III Rollout
Service Desk later.
 The User is a Travel User or Home User.
Travel Users or Home Users might not have an

employee badge with chip – as they might use the
mobile services only (VPN to connect to the BCN).
 To perform the smartcard enrollment, hand out a

white blank card, if available, to the Travel User
or Home User.
A. In the following cases skip this chapter and proceed with

step 12.
 No smartcard is to be rolled out.
 A Substitute User carries out the finalization of the

data migration.
B. Ensure that no smartcard is inserted in the smartcard reader

of the GPS III asset.
Due to technical reasons, the smartcard enrollment cannot

be carried out, if a smartcard is inserted in the smartcard
reader.
C. Start Microsoft Internet Explorer.

Figure 103: Microsoft Internet Explorer Address Bar
D. In the address bar, insert https://pki-smarttoken.basf.net/

(Figure 103-1).
 The MyID Login page is displayed (Figure 104).
Figure 104: MyID Login
E. Let the User, in the Username and Password fields, insert

the AD username and AD password, respectively (Figure
104-1 and Figure 104-2).
F. Let the User click Logon (Figure 104-3).
 MyID Main Menu is displayed (Figure 105).
Figure 105: MyID Main Menu
G. Let the User click the highlighted message (Figure 105-1) or

Collect My Card (Figure 105-2).

 MyID Select Job is displayed (Figure 106).
Figure 106: MyID Select Job
H. Let the User click the table row with the requested job
(Figure 106-1).
 The User is asked to insert the smartcard into the smartcard

reader (Figure 107). The message displayed depends on the
site scenario.
Figure 107: MyID Select Job Notification: Insert Smartcard
I. Insert the User’s smartcard into the smartcard reader slot.
 The MyID Create Card page is displayed (Figure 108).
Figure 108: MyID Create Card

J. Let the User, in the New PIN field, enter a PIN (password)
(Figure 108-1).
Recommendation Use the Active Directory password as smartcard PIN (password).
K. Let the User, in the Confirm PIN field, repeat the PIN
(password) (Figure 108-2).
L. Let the User click Next.
 The smart card enrollment starts. A message is displayed

(Figure 109).
The enrollment process can take up to 10 minutes.
Figure 109: MyID Message
Smartcard enrollment process corrupted
The enrollment process can take up to 10 minutes. If you reboot during this
time, you will not be able to login with your smartcard.
 During the enrollment process, ensure the following:
 The PC is not switched off.
 The smartcard remains inserted in the smartcard reader.
 When the enrollment has finished, the MyID Start page is

displayed (Figure 110).

Figure 110: MyID Main Menu after Smartcard Enrollment
M. Let the User log off from MyID (Figure 110).
N. Take out the smartcard from the smartcard reader.
12. Place a note on the GPS III asset indicating that the user should not
touch the PC until the technician returns for Initial Acceptance.
13. Inform the User about the following:
o The User can use the GPS II asset.
o Files currently saved on the hard disk are not necessarily

migrated.
o It is recommended to store new or changed files on a

network drive and later migrate the files to the GPS III asset.
14. Proceed with the next rollout case.
15. If you are informed that the migration was completed, to confirm the
GPS III Migration done completely message, click OK.
16. Close the Migration Wizard.
Do not reboot the GPS III asset
To check the activation of the Pre-boot authentication, in the next step, the
GPS III asset must be shut down.
17. Shut down the GPS III asset. (Do not reboot the GPS III asset.)
Postcondition: F.40: Recognize Migration Status Information's and report

FINISHED ones (BISTRO)
3.3.4 Check Activation of Pre-Boot Authentication
In this step, you ensure the Pre-Boot Authentication is active.
Prerequisites:
 The migration process is finished. For more information about how

to be informed about finished migrations, see chapter 2.4.4.
 The GPS III asset is shut down.
You have to perform the following steps together with the User:
1. Switch on the GPS III asset.

The Pre-Boot Authentication Login is displayed (Figure 111).
Software images without pre-boot authentication in certain countries

In certain countries such as China or the CIS countries, the usage of self-
encrypting hard disks is prohibited. The software images installed on the
Users’ GPS III assets was adapted accordingly. The activation of the pre-
boot authentication must therefore not be carried out.
 If the Pre-Boot Authentication Login is not displayed, proceed with step

6.
Figure 111: Pre-Boot Authentication Login; Start Screen
2. Let the User, in the User Name list, check whether all Users who
are supposed to use the GPS III asset are listed. If Users are
missing (including your own), do the following:
A. Note the missing Users.
B. Ask the GPS III Rollout Service Desk to qualify the missing
User(s) for Pre-boot Authentication.
3. From the User Name list, select any User (Figure 111-1).
4. In the Password field, insert the temporary password Start123

(Figure 111-2).
If the User has already switched on and logged in to the GPS III asset, the
temporary password is overwritten. In this case, ask the user to log in with
his MS Windows password.
5. To confirm, press the Enter key or click on the arrow symbol (Figure
111-3).
 The start of the GPS III asset continues, the MS Windows

login screen is displayed.
6. Let the User login in with the AD User name and password.
 The MS Windows desktop is displayed.

7. To let the User log off from Windows (but not reboot the PC), let the
User select Start | Shut Down | Log off.
8. Insert the smartcard in the smartcard reader.
9. Let the User insert the smartcard PIN.
From now on, the User is allowed to reboot the PC.

3.3.5 H.41 Finalize Data Migration and prepare Initial
Acceptance. Update GPS III Asset location in BISTRO
 Only applicable to notebooks: You ensure the UMTS card reader is

deactivated.
 For the user to have a valid smartcard, you ensure the user
personalizes a smartcard.
 If applicable: For the user to be able to login to ISDN and DSL

networks, you ensure the user performs the T-Systems iPass User
Registration.
 If applicable: For the user to be able to use UMTS connections, you

ensure the User’s SIM (Subscriber Identity Module) is inserted
correctly in the GPS III asset and the GPS III Rollout Service Desk
can connect to the GPS III asset to finish the UMTS installation.
 For the user to be able to use the devices attached to the GPS II
asset, you connect the devices to the GPS III asset and, for
example, install the respective drivers.
 If applicable: You ensure business-specific applications are

installed.
 To ensure the user can continue his work as usual with the GPS III
asset, you perform functional tests.
 If the functional tests can be performed successfully, you ensure an

Initial Acceptance is signed by the user.
Precondition: F.40: Recognize Migration Status Information and report

FINISHED ones (BISTRO)
3.3.5.1 Personalize the User’s Smartcard
As of Version 1.37 of this Rollout Provider Manual, this chapter is

integrated in chapters 3.3.3 and 3.3.4, respectively.
3.3.5.2 Perform additional services
1. Via the routing slip, check the services ordered by the User.
2. Ask the User if the following cases apply and perform the steps
described in the respective chapter:
 If the User of a notebook has an iPass account and the iPass

user credentials, an iPass registration is to be performed. For
more information, see chapter 3.3.11.4.
 If the User of a notebook has a UMTS SIM card (either in

PCMCIA card or USB Stick or in the GPS II notebook), the
UMTS SIM card is to be inserted in the GPS III notebook. For
more information, see chapter 3.3.11.5.
 If applicable, install locally registered applications (LR

applications). For more information, see chapter 3.3.11.6.
 If applicable, install locally attached devices. For more

information, see chapter 3.3.11.7.
3. Inform the User that additional stuff (additional power supply, bags,
for example) can be ordered via the IT catalog.
3.3.6 B.42 Perform functional test to receive Initial
Acceptance by the User
The User has to perform the Initial Acceptance together with the Rollout
Technician.
Special cases
 If a secondary User exists, the secondary User has to carry out the
Initial Acceptance. Otherwise the primary User has to carry out the
Initial Acceptance.
 If the User has to leave his desk before the Initial Acceptance can be
carried out, a Substitute User (BASF employee with AD account) can
carry out the Initial Acceptance.
 If the User is a VIP, see chapter 3.3.11.1.
Steps:
1. Start the GPS III asset (if necessary).
2. Ask the User to login with the AD User credentials.
3. To open, in BISTRO, the Initial Acceptance form, do the following:
o If the User carries out the Initial Acceptance, let the User log
in to BISTRO and click, in the Home menu, Initial
Acceptance.
o If a Substitute User carries out the Initial Acceptance, on

any computer log in to BISTRO as the rollout technician and
click, in the Rollout Provider menu, Initial Acceptance by
Substitute.
4. If the Substitute User had not been logged on the GPS II asset prior
to the data migration and can therefore not log in to the GPS III
asset, do the following:
A. In the Initial Acceptance form, do not mark any functional

tests.
B. Proceed with step 6.
5. Together with the User, perform the functional tests indicated in the
Initial Acceptance form.
For more information about how to carry out the functional tests, in
the BISTRO Manual, see Chapter 5.5 Sign the Initial Acceptance
(BASF: BISTRO Manual, 2011)
Rollout process can be delayed
When the availability of applications is to be checked, this

does not mean function tests of the applications. If function
tests of the applications were performed, too much time
would be spent.
 Ask the User to only check whether the applications are
displayed under Start | All programs.
 Ask the User to perform function tests only of core

applications as mentioned in Initial Acceptance form.
6. If Windows 7 is already installed on the GPS II asset, in the Initial

Acceptance form, under Returned Computer, ensure the
Windows 7 installed checkbox is checked.
7. If incidents occurred during the rollout, insert the gAHD incident

ticket numbers in the Comments field of the Initial Acceptance
form.
For more information about reporting incidents, see chapter 3.3.8.
8. Ask the User to sign the Initial Acceptance form.
9. If the User denies the Initial Acceptance, to process the rejected

GPS III asset, proceed with chapter 3.3.11.8.
3.3.7 Start Configuration of BitLocker Encryption on an
external USB hard disk
You ensure that BitLocker is configured on the external USB hard disk
delivered with the GPS III asset. To do so, you ask the User to carry out the
following steps.
Corruption of the external hard disk or of the data synchronization
The BitLocker encryption can take up to 10 hours. The encryption can be

stopped and restarted. But to ensure the encryption process is carried out
smoothly, it is strongly recommended not to interrupt the encryption
process.
 If the User has to leave the User’s desk during the encryption, ask the
User to do the following:
 Do not pause the encryption process and shut down the GPS III
asset.
 Lock the GPS III asset, under MS Windows.

The encryption process is carried out in the background.
Prerequisites:
 The User is logged in to the GPS III asset, with the AD User
credentials.
Steps:
1. Plug the USB hard disk into the GPS III asset.
 In the MS Windows Explorer, the USB hard disk is displayed

as an icon called DATA (typically mapped to drive “(F:)” or,
for example, drive “(E:)”; see Figure 112-1).
Figure 112: MS Windows Explorer: USB Hard disk mapped to drive F: or, for
example, drive E:
2. In MS Windows Explorer, right-click on the DATA icon (Figure

112-1).
3. In the context menu, select Turn on BitLocker.
 A dialog box is displayed (Figure 113).
Figure 113: BitLocker Drive Encryption

Corruption of the GPS III mobility concept
You have to make sure the correct unlock method is selected when
encrypting the external hard disk. Otherwise the User cannot use the hard
disk when using PCs without smartcard reader.
The correct method is the password method.
The wrong method is the smartcard method.
Selecting the correct unlock method also speeds up the process.

 In the following step 4, ensure the Use a password to unlock the
drive check box is selected.
4. Check the Use a password to unlock the drive check box (Figure
113-1).
5. In the Type your password field, let the User insert a password
(Figure 113-2).
To ensure sufficient protection of data, ask the User to do the following:
 Insert at least eight characters.
 Use letters, numbers and special characters.
6. In the Retype your password field, let the User insert the
password a second time (Figure 113-4).
7. If a smartcard is rolled out, do the following:
A. Ensure the smartcard is inserted in the GPS III asset.
B. Check the Use my smartcard to unlock the drive check

box (Figure 113-5).
8. To confirm, click Next (Figure 113-3).

Figure 114: BitLocker Recovery Key
Loss of data
If the User loses the smartcard or forgets the password, the only way to
restore the data on the USB hard disk is with the recovery key.
 Ask the User to do the following:
 Save the key in the MyBASFData folder.
 Ensure not to mistakenly delete the recovery key saved in the

MyBASFData folder.
 Ensure the recovery key can be identified, e.g. after the User has
changed the password several times and saved a new recovery
keys.
 Optional: Print the recovery key and store it at a safe place.
The recovery key is automatically backed up only if it is stored in the

MyBASFData folder.
9. Inform the User that data can be restored either via password,
smartcard or a recovery key.
10. To save the recovery key in the MyBASFData folder, click the Save
the recovery key to a file option (Figure 114-1).

12. Select the MyBASFData folder (Figure 115-1).
Figure 115: Save BitLocker Recovery Key
13. Click Save (Figure 115-2).
Figure 116: BitLocker Drive Encryption: Recovery Key saved dialog box
Figure 117: BitLocker Drive Encryption: Start Encrypting
15. Click Start Encrypting (Figure 117-1).
 The encryption starts. The progress of the encryption

process is displayed (Figure 118).
Figure 118: BitLocker Drive Encryption Progress
16. Open the system tray (Figure 119-2).
17. In the system tray menu, click on the Data Synchronisation icon
(Figure 119-1).
Figure 119: System Tray: Data Syncchronisation icon
 The Data Synchronization with GPS III USB disk dialog box
is displayed (Figure 120).
Figure 120: Data Synchronization with GPS III USB disk dialog box
18. Select the USB device displayed under Sync Devices (Figure
120-1).
19. Click Set as Sync Device (Figure 120-2).
 A message box is displayed (Figure 121).

Figure 121: Data Synchronization message box
20. To confirm, click OK (Figure 121-1).
21. Remind the User of the following:
o Encrypting the USB hard disk can take 10 hours.
o To ensure the encryption process is carried out smoothly,

the User is asked not to pause the encryption and not to
shut down the GPS III asset until the encryption process is
finished.
o When the encryption process is finished, a message box is

displayed (Figure 122). To use the encrypted external hard
disk, the User has to click Close (Figure 122-1)
Figure 122: BitLocker encryption process finished
22. To inform the User about the following, refer to the How-to-start
brochure:
o Ensuring the Automatically unlock on this computer now

on check box is not checked
o Using the smartcard to unlock the drive
o Changing the settings of the BitLocker USB hard disk

encryption
3.3.8 H.50 Report Incidents
To ensure that the GPS III Rollout is performed smoothly, you report
incidents to the GPS III Service Desk or the Rollout Coordination,
immediately.
In general, you distinguish the following issue classes:
 Issues which affect the rollout process (several rollout cases at the
same time)
 Issues which affect a single rollout case:
o Issues which prevent the Initial Acceptance from being

carried out.
o Issues which do not prevent the Initial Acceptance from

being carried out.
Efficient incident reporting
 To ensure proper reporting of incidents, for every incident concerning a

single rollout case, do the following:
1. To create a gAHD incident ticket, contact the GPS III Service Desk.
2. To make possible the most efficient processing of incidents, provide

the following information:
o Rollout ID
o Name of the User
o Serial number (Dell service tag) of the new GPS III asset
o Inventory number or serial number of the legacy GPS II

asset.
o Reason of the problem
For more information about how to create gAHD incident tickets, see
chapter 2.3.6
Precondition: H.41 Finalize Data Migration and prepare Initial Acceptance.

Update GPS III Asset location in BISTRO. (Rollout Provider)
To report incidents, do the following:
1. If an interruption of the rollout process occurs (truck accident or

delay, for example), immediately address the issue to the Rollout
Coordination.
For more information about how to contact the Rollout Coordination,
see chapter 6.5.
2. If an issue does not prevent the User from carrying out the Initial
Acceptance (e.g., software missing, Lotus Notes does not work), do
the following:
A. To collect the issues, take notes.
B. To pass the incidents in a single call, at the end of the rollout

to the respective User, contact the GPS III Rollout Service
Desk.
For more information about how to contact the GPS III

Rollout Service Desk, see chapter 6.2.
In order to support the GPS III Rollout Service Desk, after
the ticket is opened, the User is asked to speak directly to
the GPS III Rollout Service Desk employee.
C. Pass the phone to the User.
A ticket is opened for each issue.

D. Insert the ticket numbers in the Comments field of the Initial
Acceptance form.
3. If an issue prevents the User from carrying out the Initial

Acceptance (e.g. no-show of the User, technical problems), do the
following:
A. To create a gAHD incident ticket, contact the GPS III Service

Desk.
The Rollout Coordination is informed by the GPS III Service

Desk.
B. In BISTRO, under Rollout Provider | Asset Info Page,
document the issue.
For more information about how to document issues, in the

BISTRO Manual, see chapter 8.9.2.
The information can be accessed by the Rollout Provider
team leaders and the Technical Expert Team.
Postcondition: J.51: Trace and / or solve incidents
3.3.9 H.47 Remove old GPS II Asset from User's desk
 You ensure that GPS II assets are securely removed from the
user’s desk.
 You ensure the removal of GPS II assets complies with the BASF
information protection guidelines.
 You ensure that routing slips are attached to the GPS II assets
which allow for easily identifying the GPS II assets during the POIS
phase.
Precondition: B42: Sign Initial Acceptance (User)
Prerequisites:
 You have printed routing slips to be attached to the GPS II assets.

For more information about printing routings slips for GPS III and
GPS II assets, in the BISTRO Manual, see Chapter 8.5 Assign
assets to rollout cases (Users) (BASF: BISTRO Manual, 2011).
 You have rolling containers which can be locked.
Steps:
1. If you have rolled out the GPS III asset to a Home User, skip this
chapter. For more information about the rollout to Home Users, see
chapter 3.3.11.9.
2. To collect the GPS II asset and the corresponding legacy

equipment, do the following:
o If Windows 7 is already installed on the GPS II asset, do not

collect GPS II asset and legacy equipment.
o Even if the user ordered remain of legacy equipment

beforehand, the Information Manager decides whether
legacy equipment can actually remain at the User’s desk.
This applies even in the following cases:
 The GPS III asset is technically not working.
 A business critical application is not working.
 The GPS III rollout fails.
o If the Information Manager decides to leave hardware at the

User's desk, brief the Information Manager as well as the
user about ongoing costs for the hardware at the User’s
desk.
o If the user requests to retain his legacy equipment, do the
following:
I. Ask the Rollout Coordination to contact and brief the

Information Manager about the issue.
II. If the Information Manager agrees on the User’s

request to retain the GPS II PC, in the Initial
Acceptance, mark the service.
o If legacy equipment remains at the User’s desk, inform the

User about the following:
 Charging for legacy equipment will continue.
 Legacy equipment shall be removed via ongoing

processes.
3. Attach the respective routing slip to the GPS II asset. (You find the
routing slip at the user's GPS III asset.)
4. Inform the User the GPS II asset will held onsite for 5 days (POIS
phase) in case the User discovers anything missing. After the POIS
phase the GPS II asset will be wiped and recycled.
Docking stations with hard disks

GPS II docking stations (for a picture, see chapter 4.2) can contain
encrypted backup hard disks. Though the data is user-specific, it is not
necessary to store the docking station together with the GPS II asset.
 Do not attach a routing slip to the docking station.
Information protection
With the exception of hard disks contained in the docking stations, no other
storage devices such as USB sticks or external USB hard disks are to be
removed.
 Leave other storage devices at the User’s desk. These devices can only
be removed, if the User wishes so, after the rollout, in the ongoing
process.
Danger of fire or explosion
To avoid short circuits and warming, it is not permitted to transport or store

loose batteries. The regulations for transporting dangerous goods apply. To
avoid risks, do the following:
 Leave spare batteries for GPS II notebooks at the User’s desk.
 Ask the User to use the BAU process for the disposal of GPS II spare
batteries.
5. Put the GPS II PC and legacy equipment back to the container from
which the GPS III asset was taken.
o This is a suggestion to the placement of legacy equipment in

containers to assure transport security:
 Desktop PCs (Figure 123).
 Place desktops PCs in a row (Figure 123-1).
 If not enough desktop PCs are available to fill

the row, place desktop on the side (Figure
124-1).
 Accessories (Figure 123).
 Place accessories in the lowest tray (Figure

123-2).
 Notebooks (Figure 125).
 Do not stack notebooks (Figure 125-1).

Figure 123: Collection of Desktops
Figure 124: Collection of Desktops - Row not filled

Figure 125: Collection of Notebooks
6. Put back returns (GPS III equipment, which could not be delivered)
into the container from which they were taken.
GPS II assets and hard disks contained in docking stations removed from
the User’s desk contain data. Until the data is deleted, the GPSII assets
must be secured against unauthorized access.
 Ensure the GPS II assets are secured mechanically against

unauthorized removal.
 Ensure you comply with the BASF information protection regulations.
7. Lock the rolling container.
8. Ensure the GPS II assets are transported to DP4 on the same day.
Postcondition: H.48 Transport to Delivery Point 4 (Rollout Provider)

3.3.10 H.48 Transport to Delivery Point 4
 You ensure that all GPS II or GPS III assets are transported safely
to DP4.
 You ensure that storing and transport of GPS II or GPS III assets
and hard disks contained in docking stations comply with the BASF
information protection regulations.
 You ensure that all GPS III assets (which, for example, have not
received the Initial Acceptance) are identified and transported back
to DP2.
Precondition: H.47: Remove old GPS II Asset from user's desk (Rollout
Provider)
Prerequisites:
 You have a PC/Notebook with UMTS and WLAN access to

BISTRO.
 You have a hand-held barcode scanner as specified in

chapter 2.1.3.
 You have a Printer.
 You have unconspicuous closed transport vehicles (up to 7.5 t) with

“GPS III Rollout Vehicle” labels.
 BIS has provided delivery note forms (office material no. 9034909)
 To be able to sign valid transport documents, the authorized person

has registered the signature to the Regional Corporate Security.
 If GPS II assets or GPS III assets to which data has been migrated
are to be removed from a DP3 site without security service, you
have ensured the following:
o A mobile security service or an authorized BASF employee

(e.g. a Home User) will seal the transport vehicles or
transport cases. For information about the mobile security
service, contact the shift supervisor of the corporate security
service.
o If authorized BASF employees have to seal transport

vehicles or transport cases, you have a corresponding
number of numbered seals, provided by the security service.
o A separate transport vehicle or transport case is to be used

for each DP3 site.
Steps:
The removal of the legacy equipment from the location may only take place
through dedicated shipping gates. Contact the Site Coordinator for
information.
1. In BISTRO, scan the legacy GPS II assets and new GPS III assets
(e.g. whose Initial Acceptance was denied).
Scan assets to be transported to DP4 or back to DP2
(Transport to DP4) (BASF: BISTRO Manual, 2011).
2. Identify the various kinds of assets:
o GPS II assets
o GPS III assets to be transported back to DP2.
To do so, print out asset lists (to be attached to delivery notes for
the transport at the BASF gates if required).

Generate a list of assets to be transported to DP4 or back to
DP2 (BASF: BISTRO Manual, 2011).
 If GPS II assets are temporarily not mechanically secured, ensure that

the GPS II assets are under permanent surveillance.
Example To be moved up or down stairs the GPS II assets have to be removed

from the rolling containers. The unlocked rolling container and the
unlocked truck are under permanent surveillance.
 If no security service is available at a site, ensure the GPS II assets are

removed from the User’s desk and transported to Delivery Point 4 on
the same day.
3. Move the GPS II to Delivery Point 4.
If the assets have to pass a BASF gate, do the following:
A. Load the GPS II assets on a closed vehicle.
B. Fill out the BASF delivery note.
C. Print an asset list. The asset list is to be attached to the

delivery note.
For more information, in the BISTRO Manual, see
Chapter 8.10.2 Generate a list of assets to be
transported to DP4 or back to DP2 (BASF: BISTRO
Manual, 2011).
D. Let the authorized person sign both the delivery note and the
asset list.
E. To ensure the transport is carried out in correctly sealed

transport vehicle, do the following:
I. For the security service at the outbound gate be able

to identify trucks which have to be sealed, mark the
truck with a label in DIN A4 format, in the respective
language, as “GPS III Rollout Vehicle”.
II. At the BASF outbound gate, ensure the security

officer (either of BASF or of a third party security
service) or an authorized BASF employee (e.g.
Home User) does the following:
a. Seal the truck or transport case with a

numbered seal.
b. Inform the security officer at the incoming

gate about the following:
o Number of the seal
o Licence plate number of the transport

vehicle
o Name of the driver
III. For the security service at the inbound gate be able

to identify trucks from which a seal has to be
removed, mark the truck with a label in DIN A4
format, in the respective language, as “GPS III
Rollout Vehicle.
IV. At the BASF inbound gate, ensure the security

officer does the following
a. Confirm the number of the numbered seal
b. Confirm the numbered seal is intact
c. Remove the numbered seal
d. Sign the delivery note
V. If the seal is broken, contact the Rollout

Coordination.
If, for example, GPS II assets are missing, the BASF security officer
contacts the project lead.
4. At Delivery Point 4, remove the assets from the rolling container.
5. Process the assets as necessary:
o To store GPS II assets during the POIS phase, proceed with

chapter 3.4.
o Transport GPS III asset, back to DP2.
Postcondition: H.49: Maintain Asset Location for old GPS II Asset (Rollout
Provider)
3.3.11 Special Cases
3.3.11.1 Rollout assets to VIPs
You perform a rollout to a VIP, which is to be performed with increased

accuracy.
You have to follow the rules of conduct with VIPs:

 You are especially skilled with adequate dress code and excellent
communication skills, reliability, accuracy.
 You did a special training for the VIP Rollout Technicians on VIP-
related items like UMTS profile setup etc.
 You are able to give an introduction to the new GPS III functions on
request.
Questions regarding the VIP rollout:

 EMEA: Handled by the GPS III VIP rollout service desk or the VIP
Rollout Coordination
 Other regions: Handled by the GPS III rollout service desk or the
VIP Rollout Coordination.
In case of technical problems during the VIP rollout, do the following:

 Contact the Technical Expert Team immediately, see chapter 6.4.
 In EMEA, contact the GPS III VIP Service Desk.
In other regions, contact the GPS III Service Desk.
 Contact the VIP Rollout Coordination

Used exclusively for VIP rollout. Calls concerning standard rollouts
are not accepted.
If the VIP rollout cannot be terminated at the rollout date, contact the VIP
Rollout Coordination immediately.
Perform the following additional steps at the respective process points:
 H.38: Unpack and Install of Asset at User's desk
o When the GPS III asset is to be rolled out to a VIP, ensure

the following:
 No Interruptions of the VIP’s workflow caused by the

absence of the Rollout Technician.
 You have provided your mobile phone number to the
VIP’s assistant or the VIP.
 After a call by the VIP, within 15 minutes, you are

available at the VIP assistant’s or VIP’s desk.
 H.41 Finalize Data Migration and prepare Initial Acceptance. Update

GPS III Asset location in BISTRO.
o Install locally attached devices: If VIP has locally installed

software
 If there is a license and a data medium to install

software
 If not in region AP
o Install the software (e.g. CD or an

installation file available)
Else
o Contact Rollout Coordination to start

escalation.
o Brief them to contact the Information

Manager.
Else
 Contact Rollout Coordination to start

escalation.
 Brief them to contact the Information

Manager.
 Legacy equipment peripherals have to be installed

on the GPS III asset, if possible
 B.42 Perform functional test to receive Initial Acceptance by the VIP

The VIP has to perform the Initial Acceptance together with the
Rollout Technician.
A. Perform additional tests
 WLAN, if an access point is available
 UMTS, if the card is installed and the SIM card is

available
 VPN, if UMTS is installed or another external internet

access is available
 Data migration, with support to find data which is not

copied 1:1
B. User (Process step B.42 Sign Initial Acceptance): To sign
the Initial Acceptance, perform functional tests and
document the results of the functional tests In BISTRO.
For more information about carrying out the functional tests,
in the BISTRO Manual, see Chapter 5.5 Sign the Initial
Acceptance (BASF: BISTRO Manual, 2011).
3.3.11.2 Remove a BIOS password
If the GPS II asset is secured via a BIOS password (in the APAC region,
typically), you have to remove the BIOS password from the GPS II asset.
1. Start / restart GPS II asset.
2. Upon reaching the first boot up Dell Screen, press F12 on the
keyboard.
 A white screen is displayed which prompts to insert the

administrator password (Figure 126).
Figure 126: BIOS Screen GPS II PC
3. Insert the administrator password AP8105hw.
 The BIOS screen is displayed (Figure 127).

4. To reset the system password, select System Password (Figure
127-1).
 The system password screen is displayed (Figure 127).

Figure 127: BIOS Setup; System Password
5. If the Present setting states Set (Figure 127-2) ,do the following:
A. Press Enter.
B. Insert the system administrator password: AP8105hw
 The screen to set the new password is displayed.

C. Press Enter to select the empty password as the new
password.
D. Press Enter to retype the empty password as the new

password.
 The screen shows the setting Not Set (Figure 127-2).

6. To reset the administrator password, select Administration
Password (Figure 128-1).
 The administrator password screen is displayed.

7. If the Present setting states Set (Figure 128-2), do the following:
A. Press enter
B. Insert the administrator password: AP8105hw
 The screen to set the new password is displayed.

C. Press Enter to select the empty password as the new
password.
D. Press Enter to retype the empty password as the new

password.
 The screen shows the setting Not Set (Figure 128-2).

Figure 128: BIOS Setup, Admin Password
8. To exit the BIOS setup, press the Esc key on the keyboard.
3.3.11.3 Return GPS III Asset from DP3 to DP2.5 or DP1
In the following cases assets have to be returned from Delivery Point 3 to

Delivery Point 2.5:
 No-show of User
 The GPS III asset cannot not be booted or the monitor (if
applicable) is defective.
If one of the reasons above applies, do the following:
1. To create a gAHD incident ticket and describe the type of incident,

contact the GPS III Rollout Service Desk.
2. If the User is absent (no-show), to store the GPS III asset until a
possible new appointment with the user, transport the GPS III asset
back to Delivery Point 2.5.
The Rollout Coordination tries to contact the User and to reschedule

the appointment.
If the appointment cannot be rescheduled, the following happens:
o The GPS III asset is assigned to another rollout case.
o The Rollout Provider is advised to transport the GPS III

asset, via DP4, back to DP2. For more information, see
chapter 3.3.10.
o The Rollout Coordination, in BISTRO, marks the rollout case

as no-show on the part of the User.
o The User will have to replace the old GPS II asset via
ongoing processes.
3. If the Initial Acceptance could not be carried out, proceed with

chapter 3.3.11.8.
4. If the GPS III asset cannot be booted or if the monitor (if applicable)
is defective, do the following:
A. Ensure you have created a gAHD incident ticket.
The assignment of the User will be revoked.

The rollout is rescheduled.
In BISTRO, the incident is documented as a no-show on the
part of GTN.
B. To solve the issue, inform the Hardware Provider about the
guarantee case.
C. Transport the GPS III asset back to DP1.

D. In BISTRO, register a GPS III asset from the DOA pool. For
more information about how to register GPS III assets at
DP1, in the BISTRO Manual, see Chapter 8.1 Register
assets at DP1 (Maintain Availability of Assets) (BASF:
3.3.11.4 Perform the User’s iPass registration
 The User has an iPass account and the iPass user credentials.
Without the credential the registration cannot be performed.
Steps:
1. If the User does not have the iPass credentials at hand, do the
following:
A. To open an incident ticket, contact the GPS III Rollout

Service Desk.
B. Proceed with the next service to be rolled out to the User.
2. If a Substitute User carries out the finalization of the data migration,

skip this chapter and proceed with the next service to be rolled out
to the User.
3. If a smartcard was not rolled out, restart the GPS III asset.
4. Let the User login to MS Windows with the users’ credentials (in
case the user is not already logged in).
5. Ensure the iPass client is not running.
The iPass client can be mistakenly started, e.g., if you mistake the
T-Systems iPass Client for the T-Systems iPass User Registration.
In case the iPass client has already been started, you have the following
options:
 In the Windows Task Manager, try to abort the following task:

iPassConnectEngine.exe.
 Reboot the computer.
6. Let the User select Start | All Programs | T-Online | T-Systems

iPass User Registration.
 The iPass User Registration starts (Figure 129).
Figure 129: iPass Login; Username

7. Ask the user to insert his credentials to the login forms.
User names are defined as iPass prefix combined with the Users’
LDAP/Directory login name. The iPass prefix is defined as BASFX#, where
X equals the region (Table 22).
For example: BASFN#MillerA for Andreas Miller from North America.
Table 22: IPass User Names
Region User account

EMEA BASF#Username
NA BASFN#Username
SA BASFS#Username
ASIA/AP BASFA#Username
A. Let the User insert the user name and click OK.
 The iPass password dialog box is displayed (Figure 130).
Figure 130: iPass Login; Password
B. Let the User insert the User’s password and lick OK.
 The iPass password confirmation dialog box is displayed

(Figure 131).
Figure 131: iPass Login; Confirm Password
C. To confirm the password, let the User insert the User’s

password again and click OK.
8. To start the iPass client, in the Windows Start menu, select
All Programs | T-Online | T-Systems iPass Client.
 The iPass Client is displayed (Figure 132).

9. To verify that the user credentials have been stored, select
Settings | Login information (Figure 132).
Figure 132: iPass Client
 The iPass Client Login Information is displayed (Figure

133).
Figure 133: IPass Login Information
10. Check whether the fields are filled with username and the user
password (asterisks).
11. If the user name and/or password is not displayed, do the following:
Ask the GPS III Rollout Service Desk to open an incident regarding
the iPass registration of the user.
3.3.11.5 Install UMTS if user's UMTS card is available
 The asset is shut down.
Steps:
1. Ask the User the following:
o whether the GPS II asset has a UMTS card with SIM card
inside
or
o whether the GPS II asset has a PCMCIA or USB Stick from

the BASF pool with SIM card inside.
2. If the User's GPS II asset has a UMTS card with SIM card inside
o Remove the SIM card from the GPS II asset.

Else
o Remove the SIM card from the PCMCIA or USB Stick.
3. Relocate the SIM card slot on the respective GPS III asset model:
o E6320
Figure 134: Model E6320: Location of SIM card slot
o E6520
Figure 135: Model E6520: Location of SIM card slot

o M6600
Figure 136: Model M6600: Location of SIM card slot
4. Insert the SIM card into the GPS III asset.
Germany only!
The following step 179 (Set the correct Access Point Name) is to be carried
out only in Germany.
 In countries other than Germany, skip step 179 and its sub-steps A to
S.
Due to technical reasons, in Germany the Access Point Name (APN) of the
broadband connection, after the first connection, is not set correctly and
must be corrected once.
5. Applicable only in Germany: Set the correct Access Point

Name (APN):
A. If a Substitute User carries out the rollout, skip the following

steps.
B. If the User does not have the UMTS SIM card PIN at hand,
do the following:
I. Ask the user to contact the local IS-Service Desk for

support regarding establishing a UMTS connection to
the BASF network, after the Initial Acceptance is
signed.
II. Proceed with the next service to be rolled out to the

User.
C. If the User has the UMTS SIM card PIN at hand, start the
GPS III asset.
D. In the system tray, click the Wi-Fi icon (Figure 137-1).

Figure 137: Wi-Fi icon
 The Wi-Fi menu is displayed (Figure 138).
Figure 138: Wi-Fi menu: Mobile Broadband Connection icon
E. In the Wi-Fi menu, select the Mobile Breitbandverbindung

menu item (Figure 138-1).
 The network connection icon is displayed.

F. Click Verbinden (Figure 138-2).
 The Verbindung mit einem Netzwerk herstellen -

Entsperren dialog box appears (Figure 139).
Figure 139: Verbindung mit einem Netzwerk herstellen - Entsperren
G. In the PIN-Nummer field, let the User insert the UMTS SIM
card PIN (Figure 139-1).
H. Click Fortsetzen (Figure 139-2).
 The Verbindung mit einem Netzwerk herstellen –

Automatische Verbindung dialog box appears (Figure
140).
Figure 140: Verbindung mit einem Netzwerk herstellen - Automatische

Verbindung
 To avoid multiple network connections being established,

select the Nie automatisch verbinden list item (Figure
140-1).
I. Click Fortsetzen (Figure 140-2).
 The SIM card is unlocked.

J. In the system tray, click the Wi-Fi icon (Figure 137-1).
 Under Mobile Breitbandverbindung, the status of the
Vodafone.de connection is Verbunden (Figure 141-1).
Figure 141: Vodafone.de connection status Verbunden
K. Right-click on Vodafone.de (Figure 141-1).
L. In the context menu, select Eigenschaften (Figure 142-1).
Figure 142: Mobile Broadband Connection context menü
 The Eigenschaften von mobilem Breitband Vodafone.de

dialog box appears (Figure 143).
Figure 143: Eigenschaften von mobilem Breitband Vodafone.de: Profil
M. Click the Profil tab page (Figure 143-1).
N. In the APN field, replace “event.vodafone.de” by

“web.vodafone.de” (Figure 143-2).
O. To confirm, click OK (Figure 143-3).
P. In the system tray, click the Wi-Fi icon.
 The Wi-Fi menu is displayed (Figure 144).

Figure 144: Vodafone.de connection - Trennen
Q. Under Vodafone.de, click Trennen (Figure 144-1).
R. Under Vodafone.de, click Verbinden (Figure 145-1).
Figure 145: Vodafone.de connection - Verbinden
S. To verify that the APN is correctly set, start the Juniper

Network Client:
I. Ensure the smart card is inserted in the smartcard

reader.
II. Ensure other connections like LAN or WIFI are not
connected.
a. Unplug the LAN cable.
b. In the Wi-Fi menu, under

Drahtlosnetzwerkverbindung (Figure
146-1), for all wireless network connections
(Drahtlosverbindungen) with the Status
Verbunden, select Trennen (Figure 146-2).
Figure 146: Wi-Fi menu: Drahtlosnetzwerkverbindung trennen
III. In the Windows Start menu, select Alle Programme |

Juniper Networks | Network Connect.
 You are logged in to the BASF network.

 The Juniper Network icon is set to active (Figure 147-1).
Figure 147: Juniper Network icon in active status
IV. Plug in the LAN cable.
6. If the notebook is not rolled out in Germany, ask the user to contact
the local IS-Service Desk for support regarding the installation of the
SIM card and establishing a UMTS connection to the BASF
network, after the Initial Acceptance is signed.
3.3.11.6 Install LR applications
Steps:
1. Ask the GPS III Rollout Service Desk if the LR-application is

ordered.
2. If no LR-application is ordered, do the following:
o Ask the user to order the application via the IT catalog.
o Continue with chapter 3.3.11.7.
3. Ask the GPS III service desk to provide the local administration user
(“GPS”) and password.
4. Check the LR sources at the local client
o Local registered software is deployed to the following

directory on the client (<GRID> is the placeholder for the
name of the software package) (Figure 152).
o In the MS Windows Explorer, go to

C:\WINDOWS\LANDESK\CACHE\<GRID.PK-CAB>
Figure 148: LR Package example on the Local Hard Disk
I. If application sources are not locally available, you

deploy the LR applications to the client to install the
application in a next step.
II. Double-click Desktop Manager (Figure 149-1).

Figure 149: Desktop Manager Icon on Windows Desktop
 The LANDesk Desktop Manager is displayed (Figure 150).

III. Select the <application name> to be installed (see
Figure 150-1 for an example).
Figure 150: LANDesk Desktop Manager with LR application example
IV. To start software deployment, click Deploy Package

(Figure 150-2).
 The download of the software starts.

 The package sources are deployed to the client.
 The information window is displayed (Figure 151-1).
Figure 151: LANDesk Information
V. Click OK
 The software is ready to be installed.

5. Navigate to the directory where the LR package is stored on the
local hard disk (Figure 152).
o Local registered software will be always deployed to the

following directory (<GRID> is the placeholder for the name
of the software package):
C:\WINDOWS\LANDESK\CACHE\<GRID.PK-CAB>
Figure 152: LANDesk LR Package example on the Local Hard Disk
 In the directory you will find two directories, Docu and

Source.
Docu contains all necessary documentation for manual
installation.
Source holds the required installation sources.
6. Open the documentation provided (Figure 153).
Figure 153: LANDesk LR Application Documentation example
7. Install the application as described in the installation instructions

given in the documentation (Figure 154-1).
Figure 154: LR Application Documentation example
 The the installation has completed successfully.

8. In the Source folder, double-click the .reg file (Figure 155-1).
Figure 155: LR Application example .reg-File
 The Registry Editor notification is displayed (Figure 156).
Figure 156: Registry Editor Notification with LR application example
9. Click Yes (Figure 156-1).
 The Registry Editor confirmation is displayed (Figure 157).
Figure 157: Registry Editor Confirmation with LR application example
10. Click OK (Figure 157-1).
 The installation of the LR application is finished.

3.3.11.7 Install locally attached devices and local business-specific
applications (BSA)
You install, for example, printers, scanners, USB cradles, so-called non-
standard equipment (e.g. ergonomic keyboard, optical cordless mouse) if
these devices are supported by drivers compliant with the BASF standard
by connecting the device to the PC.
 If local business-specific applications are to be installed, the User

has provided installation media, licenses and
installation/configuration procedures.
If the asset is rolled to a VIP, perform additional steps. For more

Steps:
1. On the routing slip, check if local business-specific applications

(BSA) have been ordered.
2. If the BSA have been ordered, install the BSA.
3. Try to connect the non-standard equipment to the GPS III asset.
o Check if hardware is supported by the drivers of the GPS III

asset.
o Remain the peripheral devices of the GPS III asset at user's

desk.
4. Record process in the free text field of Initial Acceptance, see

chapter 3.3.6.
5. In case of errors, ask the user to contact the GPS III Rollout Service
Desk. Do not perform an error analysis.
3.3.11.8 Process a GPS III asset whose Initial Acceptance was rejected
In the following cases, you have to process GPS III assets whose Initial
Acceptance was rejected:
 The GPS III asset hardware was not delivered as specified in the
proposal.
 The User rejects the Initial acceptance though the Information

Manager has advised the User to perform the Initial Acceptance.
Steps:
1. To create an gAHD incident ticket, contact the GPS III Rollout

Service desk.
o If the GPS III asset hardware was not delivered as specified,

the Rollout Coordination does the following:
 In BISTRO, the incident is documented as a no-show

on the part of the Rollout Provider.
 The rollout is rescheduled.
o If the User rejects the GPS III asset though the GPS III asset
was delivered as specified, the Rollout Coordination does
the following:
 In BISTRO, the incident is documented as a no-show

on the part of the User.
2. To transport the GPS III asset back to DP2 (via DP4), proceed with
chapter 3.3.10.
GPS III assets are equipped with self-encrypting hard disks. If data was
migrated from a GPS II asset, the data does not need not be deleted.
3.3.11.9 Rollout GPS III assets to Home Users
Scope: EMEA
This chapter decribes the rollout of GPS III assets to Home Users in EMEA.
In the respective regions, the regional coordinators on part of BASF and on

part of the Rollout Providers organize the rollout accordingly.
As for the rollout to Home Users, there are three rollout scenarios. The
GPS III asset is rolled out
 At the User’s BASF workplace.
 At a BASF pickup site specified, in BISTRO, as the Optional

Delivery Address
 At the home address of the User specified, in BISTRO, as the

Optional Delivery Address
If the rollout is carried out on a BASF site, the standard procedure applies.
If the rollout is carried out at the User’s home office, the rollout is divided
into two parts:
 The Rollout Provider rolls out the GPS III asset to the User (steps 3
to 4).
 The Removal Provider picks up, after the POIS phase has expired,
the GPS II asset and transports it to DP4 (steps 5 to 6).
Prerequisites
 The Rollout Coordination has provided a report containing the

following information:
o Names of the Home Users
o Date and location of the of the rollout (home address or

location of the BASF pickup site)
o Contact data of the local Information Manager if the rollout is

carried out at a BASF pickup site
 At DP2, you have set up the GPS III assets and printed the routing
slips.
 You have ensured you meet the prerequisites described in chapter

3.3.1. If the third scenario applies (rollout at the home address of
the User), you have ensured in particular, for example, the following
prerequisites:
o You have a configured VPN router

o You have printed in advance the required documents, e.g.:
 Pickup confirmation forms
 Delivery notes
 Asset lists
o You have ensured you meet the prerequisites to perform

additional services if applicable, e.g. blank smartcards.
 To transport the GPS II asset, after the POIS phase has expired, to
DP4, as the Removal Provider you have ensured you meet the
prerequisites necessary to transport GPS II assets according to the
data protection guidelines, for example the following:
o Numbered seals
o Transport boxes
For more information about transporting GPS II assets to DP4, see

chapter 3.3.10.
Steps
1. If the rollout is carried out at the BASF workplace of the User, skip
this chapter and proceed with the standard rollout procedure
described in chapter 3.3.
2. If the rollout is carried out at a BASF pickup site, do the following:
A. Ensure the local Information Manager has provided the

infrastructure required.
B. Ensure you meet the prerequisites.
C. Proceed with the standard rollout procedure described in

chapter 3.3.
3. If the rollout is carried out at the home address of the Home User,
transport the GPS III asset to the Optional Delivery Address
indicated on the routing slip. For more information about process
step H.37 Transport reported Assets to Delivery Point 3, see
chapter 3.2.5.
4. Perform the following steps according to the standard procedure:
A. Unpack and install the GPS III asset. For more information,
see chapter 3.3.2.
B. Start the data migration. For more information, see chapter

3.3.3.
C. Check the activation of the pre-boot authentication. For more

information, see chapter 3.3.4.
D. Finalize the data migration. For more information, see
chapter 3.3.5.
E. Perform functional tests and carry out the Initial Acceptance.

For more information, see chapter 3.3.6.
F. Start the configuration of the BitLocker Encryption. For more

information, see chapter 3.3.7.
G. Report incidents. For more information, see chapter 3.3.8.
H. Leave the GPS II asset at the User’s desk.
During the POIS phase, the GPS II asset remains in the

User’s home office. The GPS II is not transported to DP4.
5. To identify GPS II assets whose POIS phase has expired, in
BISTRO, print the Assets to be deleted report. For more
information, in the BISTRO Manual, see Chapter 8.12.1 Erase
hard disks to release assets for handing over (Report: Assets
to be Deleted) (BASF: BISTRO Manual, 2011).
6. To delete the GPS II asset after the POIS phase has expired, as the
Removal Provider do the following:
A. At the User’s home office, remove the GPS II asset from the
User’s desk. For more information, see chapter 3.3.9.
B. Put the GPS II asset in a transport box.
C. Seal the transport box with a numbered seal.
D. To confirm that you have picked up the GPS II asset and

that the GPS II transport box was correctly sealed, for the
User and yourself fill out two copies of the Pickup
Confirmation.
E. Transport the GPS II asset to DP4. For more information,

see chapter 3.3.10.
F. To delete the data stored on the GPS II asset, proceed with

chapter 3.4.3.
3.3.11.10 Rollout GPS III assets to Travel Users
As for the rollout to Travel Users, there are three rollout scenarios. The
GPS III asset is rolled out
 At the User’s BASF workplace.
 At a BASF pickup site specified, in BISTRO, as the Optional

Delivery Address
 At a Sales Meeting at a BASF site whose address is specified, in

BISTRO, as the Optional Delivery Address
If the rollout is carried out at the User’s desk or at a BASF pickup site, the
standard procedure applies. The
Prerequisites:
 The Rollout Coordination has provided a report containing the

following information:
o Names of the Travel Users
o Date and location of the rollout (location of the BASF pickup

site or )
o Contact data of the local Information Manager responsible

for providing infrastructure like storage room (DP2.5,
temporary DP4) and BASF network access, if the rollout is
carried out at a BASF pickup site or a BASF Sales Meeting
site
 At DP2, you have set up the GPS III assets and printed the routing
slips.
 If the rollout at a Sales Meeting is scheduled beyond the regular

rollout for the respective site or location, you have ensured the local
Information management, at the respective BASF site where the
sales meeting takes place, has provided the following temporary
storage facilities and infrastructure:
o DP2.5 to store the GPS III assets before the rollout
o DP4 to store the GPS II assets after the rollout
 You have ensured you meet the prerequisites described in chapter

3.3.1. You have ensured in particular, for example, the following
prerequisites:
o You have ensured the local Information manager has

provided BASF network access
o You have a configured VPN router

o You have ensured you meet the prerequisites to perform
additional services if applicable, e.g. blank smartcards.
Steps:
1. If one of the following scenarios applies, skip this chapter and

proceed with the standard rollout procedure described in chapter
3.3:
o Rollout at the BASF workplace of the User
o Rollout at a BASF pickup site
2. If the rollout is scheduled beyond the regular rollout for the

respective site or location, transport the GPS III assets to DP2.5
agreed upon with the local Information Manager.
3. Transport the GPS III assets to the location of the sales meeting.
For more information about process step H.37 Transport reported
Assets to Delivery Point 3, see chapter 3.2.5.
4. To perform the standard procedure for the rollout to the User at

DP3, proceed with chapter 3.3.
3.3.11.11 Rollout a GPS III asset when the GPS II asset is not available
You want to rollout a GPS III asset, but the User tells you the GPS II asset
is not available.
You have to distinguish the following cases:
 Temporarily missing GPS II asset: The User has, for example,

forgotten the GPS II asset at home.
 Permanently missing GPS II asset: The location of the GPS II

asset is unknown.
Steps:
1. If the GPS II asset is only temporarily not available, do the following:
A. To create a gAHD incident ticket and document a no-show

of the User (due to missing GPS II asset), contact the
GPS III Service Desk.
B. Proceed with the next User.
The Rollout Coordination does the following:
o In BISTRO, the incident is documented as a no-show on the

part of the User.
o The rollout is rescheduled.
2. If the User is unable to specify the location of the GPS II asset, do

the following:
A. To create a gAHD incident ticket and document the missing

asset case, contact the GPS III Service Desk.
B. Note the gAHD incident ticket number.
C. To carry out the rollout, in chapter 3.3.2 proceed with step

14 and skip the data migration (chapter 3.3.3).
D. In the Initial Acceptance form, in the Comments field, insert

the gAHD incident ticket number.
3.4 Delivery Point 4 – Storage Area – Legacy
Equipment
3.4.1 Prerequisites
 Equipment for Delivery Point 4, see chapter 2.1.3.6

30):

o USB interface

3.4.2 H.49 Maintain Asset Location for old GPS II Assets
 You ensure that all GPS II assets can be relocated during the POIS
phase. To do so, in BISTRO, you scan the GPS II asset and assign
a description of the place where a GPS II asset is stored at DP4
(e.g. “shelf_1”).
 To comply with the BASF information protection regulations, you

ensure that GPS II are secured against unauthorized access.
Precondition: H.48: Transport to Delivery Point 4 (Rollout Provider)
Prerequisites:
 You have a warehouse which can be locked and which is secured

by an alarm system.
Steps:
1. In BISTRO, scan the GPS II assets.

Register GPS II assets at DP4 (Maintain Asset Location for Old
GPS II Asset) (BASF: BISTRO Manual, 2011).
2. If an asset is collected together with valuable equipment (GPRS

card, CD/DVD/BluRay Disk, for example), hand over the equipment
to BASF.
Until the data stored in the GPS II assets is deleted, the GPS II assets must
be permanently secured against unauthorized access.
 When leaving the warehouse, lock the warehouse.
 When leaving the warehouse, activate the alarm system and inform the
BASF or third party security service about the activation of the alarm
system.
 If the warehouse cannot be secured by an alarm system, ensure it is

under permanent surveillance.
 If Delivery Point 4 is not on BASF property, ensure a BASF or third

party security officer accompanies the asset transport until data deletion
of the assets at Delivery Point 4.
3. Store the GPS II asset in the warehouse according to the BASF

information protection guidelines.
Postcondition: F.44: Update in gAHD (BISTRO)
3.4.3 H.54 Deletion of data stored on old GPS II Asset
In this step (see Figure 163), the responsible entity (the Rollout Provider or
a third party, depending on the local rollout scenario) ensures the following:
 The hard disks of all GPS II assets whose POIS phase has expired,
are erased according to the BASF information protection regulations
(see chapter 2.1.3.6).
 The deletion logs are transmitted to BASF in an electronic format.
Precondition: F.53: Report: Asset to be deleted (BISTRO)
Steps:
1. In BISTRO, print the Assets to be deleted Report. For more

information, in the BISTRO Manual, see Chapter 8.12.1 Erase
hard disks to release assets for handing over (Report: Assets
to be Deleted) (BASF: BISTRO Manual, 2011).
2. If the Rollout Provider is responsible for the data deletion, perform

the data deletion as described in chapter 4.
Else
o The Rollout Provider shall allow the third party responsible

for the data deletion to perform the data deletion at Delivery
Point 4.
o The third party responsible for the data deletion shall

perform the data deletion at Delivery Point 4 as described in
chapter 4.
o With a data deletion protocol in electronic form (pdf), the

third party responsible for the data deletion confirms the data
deletion of any asset to the Rollout Provider with a data
deletion protocol in electronic form (pdf).
Postcondition: H.55: Report all assets data was deleted in BISTRO (Rollout
Provider)
3.4.4 H.55 Report all assets, whose data was deleted, in
BISTRO
In this step (see Figure 163), you ensure that the deletion status of GPS II
assets is recorded in BISTRO.
 If the Rollout Provider is responsible for the data deletion, you

ensure that the Is deleted status, in BISTRO, is assigned only to
those GPS II assets, whose hard disk was actually deleted
according to the deletion log.
 If a third party is responsible for the data deletion, the third party
responsible for the data deletion ensures that the Is deleted status,
in BISTRO, is assigned only to those GPS II assets, whose hard
disk was actually deleted according to the deletion log.
Documentation of the deletion status

The deletion status must not be recorded if the hard disk is contained in
GPS II docking stations.
The data stored on backup hard disks in GPS II docking stations is

encrypted. Therefore, after the deletion of the data, no further action is
required:
 The deletion of the data must not be reported in BISTRO.
 No log files must be sent to BASF.
Precondition: H.54: Deletion of data stored on old GPS II Asset (Rollout

Provider)
Steps:
1. For each GPS II asset whose hard disk was erased according to the
deletion log, in BISTRO, confirm that the hard disk was erased.
Erase hard disks to release assets for handing over (BASF:
2. To report data deletion services, you can generate monthly reports.

To invoice data deletion services, generate monthly reports
(Report Assets Deleted) (BASF: BISTRO Manual, 2011).
Postcondition: A.57: Report: Assets to be hand-over to Hardware Broker

(Procurement)
3.4.5 H.59 Transport to Delivery Point 5
In this step (see Figure 163), you ensure that GPS II assets, in BISTRO,
are grouped into asset bundles which can be handed over to a Hardware
Broker.
Precondition: A.57: Report: Assets to be hand-over to Broker.

(Procurement)
1. Place the assets on pallets.
o Group the assets into groups of the same asset type (e.g.
PC, notebook).
o Put defective GPS II assets on a separate pallet.
2. In BISTRO, scan the assets and assign the assets to bundles (e.g.
the name of the pallet).
Register assets to be handed over (Hand-over old GPS II
Assets to Broker, 1) (BASF: BISTRO Manual, 2011).
Postcondition: H.60: Hand-over old GPSII Assets to Broker (Rollout

Provider)
3.4.6 Special Cases
3.4.6.1 Return a GPS II asset to the User
You want to relocate a GPS II asset during the POIS phase.
Example: A GPS III asset does not work. The User requests to return the
GPS II asset from DP4 to the User's desk. A corresponding incident ticket
is assigned to your Rollout Provider assignee group.
Prerequisite:
 You have a gAHD account. For more information, see chapter 2.3.
Steps:
1. To identify the User, open the gAHD incident ticket. For more
information, see chapter 2.3.7
2. In BISTRO, identify the location of the GPS II asset.

Register GPS II assets at DP4 (Maintain Asset Location for Old
GPS II Asset) (BASF: BISTRO Manual, 2011).
3. To return the GPS II asset (together with the legacy equipment) to

the User, via gAHD, make an appointment with the User.
4. Return the asset to the User's desk and connect it to power,

network and peripherals.
5. To process the gAHD incident ticket, do the following:
A. Open the gAHD incident ticket. For more information about

searching a gAHD incident ticket of a User, see chapter
2.3.9.2.
B. Assign the gAHD incident ticket to the respective Rollout

Coordination assignee group. For more information about
assigning a gAHD incident ticket to an assignee group, see
chapter 2.3.7.2.
Do the following:
I. In the New Group field, insert the name of the
respective rollout coordination assignee group (see
Table 23: gAHD Rollout Coordination Assignee
Groups).
Table 23: gAHD Rollout Coordination Assignee Groups
Region Rollout Coordination assignee groups

EMEA eu.project.gps3.rollout-coordination
NA na.project.gps3.rollout-coordination
SA sa.project.gps3.rollout-coordination
APAC ap.project.gps3.rollout-coordination
II. In the User Description field, insert the following

note: “GPS II asset is returned to User. In BISTRO,
please assign the ‘Reactivation of legacy PC service’
to the rollout case.”
III. Set the gAHD incident ticket status to Work on

Verification.
 The Rollout Coordination marks, in BISTRO, the GPS II

asset as returned to the User.
 The GPS III asset will be processed during the BAU process.
3.4.6.2 Print a DP4 inventory list
You want to print an inventory list of the GPS II assets stored at DP4.
Step:
 In BISTRO, print an inventory list.

Relocate an asset during the POIS phase or generate an inventory
list (BASF: BISTRO Manual, 2011).
3.5 Delivery Point 5 – Handover
3.5.1 Prerequisites
 You have requested information about third party to handover

assets (Hardware Provider, Hardware Broker) via rollout manager.

30):

o USB interface

3.5.2 H.60 Hand-over old GPSII Assets to Broker
In this step (see Figure 163), you ensure that the required documents, e.g.
a delivery note, are delivered and filed when asset bundles are handed
over to a Hardware Broker.
Precondition: H.59 Transport to Delivery Point 5 (Rollout Provider)
Prerequisites:
 In BISTRO, you have printed a list of assets to be handed over. For

more information, in the BISTRO Manual, see Chapter 8.13.2
Generate a catalog of assets which can be handed over to a
Hardware Broker (Report: Assets removed and to be handed
over to Broker) (BASF: BISTRO Manual, 2011).
 You have grouped the GPS II assets into asset bundles (e.g.
pallets). For more information, see chapter 3.4.5.
 To hand over the asset bundles, the Rollout Provider has scheduled
an appointment with the Hardware Broker.
Steps:
1. Hand over the asset bundle to the Hardware Broker.
2. In BISTRO, print a delivery note.

Hand over asset bundles to the Hardware Broker (Hand-over
old GPS II Assets to Broker) (BASF: BISTRO Manual, 2011).
3. Provide documents:
C. At request of Rollout Coordination: Hardware Broker shall

provide a scrapping certificate for each individual device.
The list shall contain serial number of asset, date of hand
over of asset, asset model, signature of an authorized
person of Hardware Broker.
D. File duplicates.
4. Send the delivery note of any delivery of assets (in electronic form
as pdf file) to the address provided in Table 24.
Table 24: Addresses for delivery note and transport documentation

NA GPSIII-NA-Rollout-
Team@basf.com
SA gpsiii.sa@basf.com
AP IS-gpsiii-AP-logistic@basf.com
Postcondition: K.61: Take Over old GPSII Assets with conformation

(Broker)
3.5.3 H.63 Maintain old GPS II Assets handed over to Broker
in BISTRO
In this step (see Figure 163), you ensure that asset bundles handed over to
a Hardware Broker are registered to BISTRO.
Precondition: K.61: Take Over old GPSII Assets with conformation (Broker)
Step:
 In BISTRO, you confirm you have handed over the asset bundle to the
Hardware Broker.

Confirm handing-over (Maintain old GPS II Assets handed over to
Broker in BISTRO) (BASF: BISTRO Manual, 2011).
Postcondition: F.64: Create Report: "Assets delivered to Broker" for further

usage (BISTRO)
4 Removal Provider: Deleting data at
Delivery Point 4
You delete the data stored in the following devices:
 Hard disks in GPS II assets
 Hard disks contained in GPS II docking stations
4.1 General Prerequisites

 BASF gAHD account as described in chapter 2.3.
 Cell phones without camera, incl. call charges incurred.
 Other communication devices as required.
 Contact list with telephone numbers (team leader, Hotline).
 Work vehicles for on-site technicians such as trolleys, carts, cars,

trucks and other devices for material movement.
 All typical kinds of office equipment like phone, paper and pen.
 All typical kinds of IT-working equipment like IT-equipment to

access BASF intranet and BASF tools.
 Safety equipment (where demanded by BASF security): Minimum

Personal Protective Equipment which includes safety glasses, hard
hats (protective helmet), and steel toe shoes.

4.2 Delete data
You ensure that legacy data stored on GPS II storage devices is deleted
according to the BASF information protection guidelines.
Prerequisites:
 You have set up the data deletion environment. For more

 If hard disks have to be mechanically destroyed in locations other

than the physical location of DP4 (e.g. central degaussing facilities)
and therefore have to leave BASF property temporarily, you have
provided the required transporting infrastructure, for example:
o Sealed transport boxes or bags
o Numbered seals
For more information about transporting GPS II assets according to

the BASF information protection guidelines, see chapter 3.3.10.
Steps:
1. To identify GPS II assets to be deleted, in BISTRO generate the

Assets to be deleted report. For more information, in the BISTRO
Manual, see Chapter 8.12.1 Erase hard disks to release assets
for handing over (Report: Assets to be Deleted) (BASF: BISTRO
Manual, 2011).
2. For every GPS II asset indicated in the Assets to be deleted

report, do the following:
A. To delete the hard drive, use the BASF certified software

tool.
B. If the GPS II asset PC does not boot, do the following:
I. In gAHD, check if the GPS II asset is still covered by

the guarantee period. For more information about
how to display the guarantee period, see chapter
2.3.10.
II. If the GPS II asset is still under guarantee, do the

following:
a. To create an incident ticket, contact the

GPS III Rollout Service desk and note the
incident ticket number.
b. To the GPS II asset, attach a slip containing

the incident ticket number and an information
that the GPS II asset is defective.
c. Put the asset aside.
III. If the guarantee of the GPS II asset is expired, do the

following:
a. Remove the hard disk from the GPS II asset.
b. Install the hard disk in a carrier PC or a drive

cage.
c. To delete the hard disk, use the BASF

certified software tool.
d. If the hard drive cannot be deleted, remove

the hard disk from the carrier PC or drive
cage.
e. To destroy the hard disk mechanically,

degauss or shred the hard disk.
f. To the GPS II asset attach a slip indicating

that the GPS II is defective.
D. Check the services indicated on the routing slip. If the User

is a VIP (VIP Rollout) or if the User has selected the
Mechanical destruction of hard disk service, do the
following:
I. To delete the hard disk, use the BASF certified

software tool.
II. To destroy the hard disk mechanically, do the

following:
a. Remove the hard disk from the GPS II asset.
b. Degauss or shred the hard disk.
E. Send the data deletion protocol (and the destruction protocol

if applicable), in electronic form (pdf), to the address
provided in Table 25.
Table 25: Addresses for data deletion protocol

NA GPSIII-NA-Rollout-
Team@basf.com
SA gpsiii.sa@basf.com
AP IS-gpsiii-AP-logistic@basf.com
F. To delete backup hard disks contained in docking stations,
do the following:
I. To remove the hard disk from the docking station,

press the button (Figure 158-1).
Figure 158: GPS II docking station with encrypted backup hard disk
II. To delete the data, you have the following options:
 Mechanically destroy the hard disk.
 Degauss the hard disk.
G. Ensure the deletion status of GPS II assets is recorded in

BISTRO.
For more information, see chapter 3.4.4.
Documentation of the deletion status

The deletion status must not be recorded if the hard disk is contained in
GPS II docking stations.
The data stored on backup hard disks GPS II docking stations is encrypted.
Therefore, after the deletion of the data, no further action is required:
 The deletion of the data must not be reported in BISTRO.
 No log files must be sent to BASF.

5 Exceptions and Error Handling
Reporting
 To ensure proper reporting of incidents, for every incident contact the

GPS III Service Desk to create a gAHD incident ticket.
For more information, see chapter 2.3.6
5.1 Delivery Point 1 – Storage Area – New

Equipment
Defective asset while located at DP1 or at transport to DP2
 Solve the issue directly with Hardware Provider.

5.2 Delivery Point 2 – Staging Area
No access to AD
To open an incident ticket, call the GPS III Rollout Service Desk.
No BISTRO access
To open an incident ticket, contact the GPS III Rollout Service Desk.
Insufficient numbers / wrong / defective assets delivered from DP1

To open an incident ticket, contact the GPS III Rollout Service Desk.
Issues concerning the rollout wizard

Call the (regional) Technical Expert Team.

5.3 Delivery Point 3 – User's Desk
Escalation types at Delivery Point 3

 Technical problems: Contact the Technical Expert team.
 Other problems (e.g. conflict with user): Contact the Rollout

Coordination to start escalation.
Rollout numbers cannot be reached

An interruption at locations < 200 PCs is performed only after consulting
with the Rollout Coordination.
Replanning of the rollout because of errors or complaints or incidents

In case of exceptions or errors or complaints or incidents: Contact the
Rollout Coordination for rescheduling of the rollout.
User relocates, rollout is carried out in a new location

To ensure the correct user data is maintained in gAHD, contact GPS III
Rollout Service desk.
User cannot be found at location described in rollout appointment

If the user is not located at the location described in rollout appointment
 Ask the other users in the room described in rollout appointment

about the location of the user.
 If the user is in the same building
o Ask for user's location and move asset to this location.
o Achieve the rollout at user's location.

Else
o Return asset to Delivery Point 2, see chapter 3.3.11.3 for

more instructions.
User has requested a schedule change

The user has requested a change in scheduling, but the change has not
been taken into account in rollout planning.
 Contact Rollout Coordination to start escalation.
o Brief them to contact the Information Manager.
 If Information Manager decides to install as planned
o Install asset as planned by Rollout Coordination

Else return the asset to Delivery Point 2
Rollout Technician cannot keep appointment

 Contact Rollout Coordination. Brief them about the issue.
 Identify the GPS III asset is with the delivery note or the identifier of
the rolling container.
 Transport GPS III asset back to DP2.
 Contact Rollout Coordination to arrange a second appointment with

the User.
User has no time at the time of the scheduled appointment.

 Contact Rollout Coordination. Brief them about the issue.
 Identify GPS III hardware with the rollout ID and return hardware to
Delivery Point 2.

5.4 Connection problems
Rollout Technician cannot connect to BISTRO
Rollout Technician shall create gAHD ticket and Rollout Technician shall
contact Rollout Coordination.
Smartcard: User cannot log on to MyID

When the smartcard user’s profile is not imported to MyID, he will not be
able to log on to MyID.
 The Rollout Technician shall contact the GPS III Rollout Service
Desk.
 The GPS III Rollout Service Desk has to try the following:
o Get the user imported.
o Get enrollment job created.
 If the GPS III Rollout Service Desk is successful, the enrollment of

the smartcard shall be continued.
Else No enrollment of smartcard is possible.
o The User needs to enroll the card on his own with the help of
the IS Service Desk.

5.4.1 VIP
VIP: Technical problems during rollout
 Contact expert team immediately, see chapter 6.4.
 If EMEA: Consult GPS III VIP Service Desk.
Else contact GPS III Service Desk.
 Consult VIP Rollout Coordination.
Used exclusively for VIP rollout. Calls concerning standard rollouts are not
accepted.
VIP: installation cannot be terminated

If the installation cannot be terminated at the rollout date:
 Contact the VIP Rollout Coordination immediately.

5.4.2 GPS III Asset
GPS III Asset has to be returned
 If the rollout procedure is interrupted at the instruction of the
Information Manager, the new GPS III hardware is identified via the
rollout ID and returned to Delivery Point 2.
 The User must be able to work with the GPS II asset with no
restrictions.
 The interrupted procedure is documented in BISTRO with a

thorough explanation and forwarded to Rollout Coordination for
further decisions.
Card reader is defective

If ordered by the User, for notebooks there will be two smartcard readers,
an internal and an external one. The external one can be connected via
USB.
If the card reader is defective, there is no way to enroll the card during
rollout.
 Please check (there is no tool for diagnosis) if both card readers are
defect!
 If both card readers are defect
o Report the defective card reader to GPS III Rollout Service

Desk.
 Brief them to initiate the replacement of the defective

device.
The wrong GPS III asset is delivered

Wrong GPS III asset delivered means another asset type than defined in
BISTO is delivered to the user.
 Label the GPS III asset via the rollout ID (taken from the Routing
Slip)
 Transport the GPS III asset back to DP2.
 Contact the Rollout Coordination, brief them about the issue and
brief them about the need for a new appointment with the User.
Missed or wrongly supplied periphery of GPS III asset

 If user and Information Manager decide to accept the GPS III asset,
do the following
o Report missing parts to the GPS III Rollout Service Desk.

o Record missing parts on the delivery document.
o Record missing parts in the Initial Acceptance.
o The missing hardware is delivered by BASF Information

Services to the user as soon as possible.
o The respective legacy equipment is left at user's desk.

Else
o Contact the Rollout Coordination. Brief them about the issue.
o Identify the GPS III asset is with the delivery note or the
identifier of the rolling container.
o Transported GPS III asset back to the DP2.
o Contact Rollout Coordination to arrange the user down for a

second appointment.
A defective PC was delivered

 Report the defective device to the GPS III Rollout Service Desk
o Initiate guarantee claims and / or replacements.
 Contact the Rollout Coordination about the issue.
 Identify the defective PC via the rollout ID (taken from the BISTRO
database)
 Transport the GPS III asset back to DP2.
A defective keyboard, mouse or docking station was delivered or

hardware is incomplete
o Brief the Rollout Coordination to contact the Information

Manager.
 The Information Manager decides if the Initial Acceptance is granted

later.
 If the Initial Acceptance is granted later, contact the GPS III Rollout
Service Desk for replacement hardware.
 The respective legacy equipment is left at the User's desk.

5.4.3 GPS III Software
User wants to change software on GPS III asset
Brief the User to order the application via the IT catalogue.
Lotus Notes icons are missed

 Brief the User: Missing Lotus Notes icons can be added at a later
time by calling the GPS III Rollout Service Desk and initiating an
incident ticket.
Business-critical BSA is not available

 In case of:
o Software ordered, but not installed and not available:
 The user decides whether or not to retain his legacy

equipment.
 If the User retains his legacy equipment
 If enough space on user desk to place GPS II

and GPS III asset
 The User signs the Initial Acceptance.
 In the Initial Acceptance form, the service

GPS II asset remaining at user’s desk is
documented to be received.
Else
 Return GPS III asset to DP2.
o Ordered, not installed and available:
 The Initial Acceptance must be signed.
 Open an incident ticket with the GPS III Rollout

Service Desk.
 The software is installed later by the GPS III Rollout

Service Desk.
o Not ordered and not installed:
 The Initial Acceptance must be signed.
 The user has to order the software.
 If user refuses to sign initial acceptance
o Contact Rollout Coordination to start escalation.

 Brief them to contact the Information Manager.
Non-business-critical BSA is not available

 The user has to sign the Initial Acceptance.
 In case of:
o Software ordered but not installed
 Open incident ticket to GPS III Rollout Service Desk.
 The software is installed later by the GPS III Rollout

Service Desk.
o Software not ordered
 User has to order software via GPS III Rollout

Service Desk.
 If user refuses Initial Acceptance
o Contact Rollout Coordination to start escalation.
 Brief them to contact the Information Manager.
User has taken the new hardware with him

After initiating the Data Migration Wizard, a note is always left on the GPS
III asset indicating that the user should not touch the PC until the technician
returns for acceptance. If the user took away the GPS III asset:
 The Information Manager will contact the user by telephone to tell

the user to immediately return to his desk together with his GPS III
machine.
 If the user does not return immediately: Left a message for the user
telling him to contact the GPS III Rollout Service Desk in order to
arrange a new appointment.
User wants to test BSAs

User insists on testing all BSAs before granting Initial Acceptance:
 If the Information Manager decides that the user should perform the
tests

o Ask Rollout Coordination to decide whether to wait or return
at a later time.
Else return GPS III asset to DP2.
User wants to test special Services not ordered

User insists on testing additional services which he did not order (e.g.
headset):
 If Information Manager decides to let user perform the test
o Ask Rollout Coordination to decide whether to wait or return

at a later time.
Else return GPS III asset to DP2.
User wants installation of additional Services which were not ordered

Installation of additional Services which were not ordered is not taken over
by Rollout Technician.
 The user must open an incident ticket with the GPS III Rollout
Service Desk.

5.4.4 GPS II Asset and Periphery
User's printer / scanner not declared via BISTRO beforehand
Contact GPS III Rollout Service Desk for ticket to install printer / scanner.
User wants to keep GPS II asset

If user wants to keep GPS II asset:
 If Information Manager agrees to user request: Keep GPS II asset

at user's desk.
Else
o Return GPS III asset to DP 2

5.4.5 Approval / Acceptance
User and Information Manager agree to refuse the acceptance of the
new computer
 Identify GPS III hardware with the rollout ID and return hardware to
Delivery Point 2.
Postponed Initial Acceptance overview (Installation cannot be

completed during normal working hours)
Several acceptance scenarios can result in the need to complete the Initial
Acceptance at a later time, in order to avoid a large number of no-shows.
Such cases are referred to as postponed Initial Acceptances.
Conceivable scenarios for completion of Initial Acceptance at a later time:
 The Data Migration Wizard runs a long time and the User has to
leave.
 The Data Migration Wizard runs past the end of the normal working
day.
 The user is not present at the acceptance.
 The user has taken the new hardware with him.
 The user wants to test BSAs.
 The user wants to test special Services which were not ordered.
 The user wants to have incident tickets processed.
If the new device remains with the user without Initial Acceptance:
 Report to Rollout Coordination.
 The acceptance is set neither on given nor denied. Only if the

Initial Acceptance is accomplished, this value is set in BISTRO.
 Record delays in the Initial Acceptance form
o Use exact times (begin and end of the installation, begin and
end of the Initial Acceptance.
 Complete the postponed Initial Acceptance latest by the end of the

next working day.
 Exception: In coordination with regional Rollout Coordination,

postponed Initial Acceptance can be delayed for up to five days.

 If the Initial Acceptance cannot be retrieved on the same day, the
start time of the installation is set on the indicated time for the end of
the installation.
Migration has passed successfully, but user has no time left and does
not want to perform the Initial Acceptance at present.
 If the Information Manager is contacted
o Information Manager decides if no-show or postponed Initial

Acceptance
User is not present for signing the Initial Acceptance

User is not present when the Rollout Technician returns for Initial
Acceptance
 Rollout Technician: Contact Rollout Coordination
o Ask whether the user has left a message indicating when he

will again be available.
o If this is not the case, the matter is escalated to the

responsible Information Manager.
 Information Manager
o Reach the user by telephone. Tell him to immediately return

to his desk.
o If the user does not return immediately
 Information Manager decides if no-show or

postponed Initial Acceptance
User wants to have incident tickets processed

The user wants to see the open incident tickets resolved before signing the
Initial Acceptance.
 If the Information Manager decides processing of the incident tickets
o Ask Rollout Coordination if to wait for the end of the

processing or to proceed to next rollout and come back later
this day for Initial Acceptance.

5.4.6 Data Migration Wizard and Smartcard Enrollment
User has forgotten/broken his employee badge
When a user has forgotten his card/employee badge, or it is defective or
broken on the day of rollout, the Rollout Technician may exchange his PC
without enrolling his badge.
 If the user has forgotten his smartcard, the rollout personnel will not
enroll this card!! The enrollment will be done via BAU Process.
 The user will be able to log on with his username and password as
usual.
If it is not sure if the card is defect or not, please try to enroll it on another
PC (if possible) to make sure that the card is defect.
Smartcard: “..device ready to be collected” is missing

If no enrollment job has been created, there won’t be an entry in MyID that
states “There is 1 device ready to be collected”.
 Click Collect My Card to be sure no job is listed!
 If no job is listed contact GPS III Rollout Service Desk to get an

enrollment job created immediately
 Continue with the enrollment of the smartcard.
Smartcard: User is not available during rollout

No enrollment of smartcard possible.
 The User needs to enroll the card on his own with the help of the IS
Service Desk.
Data Migration Wizard runs a long time and user has to leave
User has to leave for another appointment with the Data Migration Wizard
still running and before the initial acceptance with the technician.
 User reports to the GPS III Rollout Service Desk and name a time
after which he will again be reachable at his workstation.
o This should be on the same day and no later than on the

following day.
o The GPS III Rollout Service Desk notifies Rollout

Coordination of the new scheduled appointment via incident
ticket.
o Rollout Coordination then schedules this exception in the

current rollout planning.

Data Migration Wizard runs past the end of the normal working day
Script takes substantially longer than the end of the normal working day:
 Contact GPS III Rollout Service Desk.
o Brief them to request a schedule of the appointment from the

Rollout Provider for the next working day at which the
acceptance can be performed with the user.
 Report appointment to Rollout Coordination
 Report appointment to Rollout Provider
o Brief Rollout Provider to include appointment in rollout

scheduling
Data migration fails on GPS III asset

 Contact regional technical expert team.
o If Data migration still fails:
 If the user and the Information Manager both agree:
 Left GPS III asset on location.
 User has to open a ticket at the GPS III

Rollout Service Desk.
 Initial Acceptance has to be signed by the

user
 Document the procedure in the Initial

Acceptance.
Else individual decision by Rollout Coordination and

Information Manager / User
Data Migration Wizard aborts

If the Data Migration Wizard aborts with an error message:
 Check cabeling and network connection.
 Both PCs will have to be restarted and the Data Migration Wizard
will have to be started again.
 If the data migration aborts again
o Contact the regional technical expert team to solve the

problem.
o If problem is not solved
 Contact GPS III Rollout Service Desk

 Brief them with the exact error message.
Data Migration Wizard icon not at desktop

The symbol for the data Data Migration Wizard is missed at the desktop of
the GPS III asset:
 The Rollout Technician must check the network connection
 If the network connection exists, the GPS III asset must be

completely restarted.
 If the issue is not fixed, contact the regional Technical Expert Team.
Data counter idle on the GPS III asset, script seems to have stopped
 Check script status
o The current summaries for the data migration are displayed

on the screen.
 Check for errors
o If the counter is idle and the script appears to have paused

during Scanstate or Robocopy, this may indicate a problem
with the script.
 Check script state with task manager
 Check performance
o The number of files in the migration directory and the size of

the data volume on the GPS III asset do not increase for
more than 30 minutes.
o If script is not idle
 Do not interrupt the script
 If problem remains or situation is unclear
o Contact technical experts group
Data Migration Wizard runs again after the user's first logon following
the migration
 Contact Technical Expert Team
 Do not interrupt the script.
 Rollout Technician shall confirm in initial acceptance that Data

Migration Wizard runs in the present user context
 Do not open an incident ticket

GPS II-script does not start / aborts in the user environment
 Login to GPS II PC with migration account.
 Start script again

6 Troubleshooting: Contacting the GPS III
support services
6.1 Use cases for GPS III support services

GPS III support services are delivered during and after the GPS III rollout
for several target groups and use cases, see Table 26.
Incorrect access to GPS III Rollout support services
To avoid misdirected support calls, do the following:

 As the Rollout Provider, ensure you exclusively use the contact data
indicated in the chapters below.
 Ask the Users to contact the GPS III Service Desk via the contact data
provided in BISTRO, under Home | Help, or in the rollout mails.
Target group User Approver, IM, Rollout Provider

Rollout
Coordination,
GPS III Procurement
support
service
GPS III Rollout Problems during rollout, BISTRO problems All problems except for
Service Desk asset in POIS phase. installation (DP2) and
Access exclusively via migration. E.g.: BISTRO
contact data in BISTRO problems, GPS II assets
Help or rollout mails. missing, no-show of User…
Rollout Coordination Problems concerning the

rollout process (e.g. delays of
trucks), problems concerning
the User (e.g. User rejects
GPS III asset)
24/7 DTM Support Problems during installation

Team (DP2)
Technical Expert Problems during migration

Team (DP3)
IS-Service Desk Asset in BAU phase
Table 26: GPS III support services and target groups

6.2 GPS III Rollout Service Desk
6.2.1 GPS III Rollout Service Desk Service Times
If you want to call the helpdesk outside the support time period, call the
common helpdesk number of your region.
Location Service Hours
EMEA Schwarzheide (German/English) 7:30 – 17:30 CET
Schwarzheide (catch & dispatch, German + English) Out of service time
EMEA Tarragona (Spanish) 8:00 – 18:00 CET
EMEA Antwerp (Dutch/French/English) 8:00 – 18:00 CET
EMEA Cesano (Italian) 8:00 – 18:00 CET
EMEA Reduced Service Countries (RSC) 7:30 – 17.30 local time
APAC 7:00 – 19:00 local time
NA (English) 7:00 – 19:00 local time
SA 7:00 – 19:00 local time
Table 27: GPS III Rollout Service Desk Service Times

6.2.2 GPS III Rollout Service Desk EMEA
6.2.2.1 EMEA: North
Country Helpdesk POSS-Hotline email (only internal)

(only internal)
Denmark Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Finland Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Great Britain Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Ireland Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Latvia Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Lithuania Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Norway Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Sweden Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Table 28: GPS III Rollout Service Desk EMEA: North
6.2.2.2 EMEA: West

(only internal)
Belgium Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
France Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Netherlands Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Germany Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Table 29: GPS III Rollout Service Desk EMEA: West
6.2.2.3 EMEA: South

(only internal)
Greece Athens +30 2106860102/126 hellas-it-service-desk@basf.com
Italy Cesano +39 0362.512 801 cesanomaderno-gps3@basf.com
Malta Cesano +39 0362.512 801 cesanomaderno-gps3@basf.com
Portugal Tarragona +34 977.25.6883 tarragona-gps3@basf.com
Spain Tarragona +34 977.25.6883 tarragona-gps3@basf.com
Table 30: GPS III Rollout Service Desk EMEA: South
6.2.2.4 EMEA: Central

(only internal)
Austria Bratislava +421 258 266 123 it.euc-w@basf.com
Bosnia and Budapest +36 1 250 9777 it.euc-e@basf.com
Herzegovina
Bulgaria Bucharest +40 21 5299 031 euc-e@basf.com
Croatia Budapest +36 1 250 9777 it.euc-e@basf.com
Czech Republic Bratislava +421 258 266 123 it.euc-w@basf.com
Hungary Budapest +36 1 250 9777 it.euc-e@basf.com
Poland Warsaw +48 22 570 9888 it.basfpolska@basf.com
Romania Bucharest +40 21 5299 031 euc-e@basf.com
Serbia Budapest +36 1 250 9777 it.euc-e@basf.com
Slovakia Bratislava +421 258 266 123 it.euc-w@basf.com
Slovenia Budapest +36 1 250 9777 it.euc-e@basf.com
Table 31: GPS III Rollout Service Desk EMEA: Central
6.2.2.5 EMEA: Switzerland
Town Helpdesk POSS-Hotline email (only internal)

(only internal)
Au Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Basel Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Bern Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Evionnaz Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Grenzach- Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Wyhlen
Huningue Cedex Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Kaisten Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Monthey Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Safenwil Antwerp +49 621 60 77674 antwerpen-gps3@basf.com
Schaffhausen Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Schweizerhalle Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
(Muttenz)
Waedenswil Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Winterthur Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Zuerich Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Zug Schwarzheide +49 621 60 77671 schwarzheide-gps3@basf.com
Table 32: GPS III Rollout Service Desk EMEA: Switzerland
6.2.2.6 EMEA: CIS Countries ex Russia

(only internal)
Azerbaijan Sumgait +994 18 653 08 00 IS_Azerbaijan@basf.com
Belarus Minsk +375 17 202 24 71 IS_Belarus@basf.com
Kazakhstan Almaty +7 727 2790013 IS_Kazakhstan@basf.com
Ukraine Kyiv +38 044 5915595 IS_Ukraine@basf.com
Table 33: GPS III Rollout Service Desk EMEA: CIS Countries ex Russia
6.2.2.7 EMEA: CIS Countries Russian Federation
Town Helpdesk POSS-Hotline email (only internal)

(only internal)
Belgorod Moscow +7 495 2317217 IS_Russia@basf.com
Blagoveshensk Moscow +7 495 2317217 IS_Russia@basf.com
Bolshoe Tolbino Moscow +7 495 2317217 IS_Russia@basf.com
Ekaterinburg Moscow +7 495 2317217 IS_Russia@basf.com
Kaluga Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Kamen-Rybolov; Moscow +7 495 2317217 IS_Russia@basf.com
Krasnoselskaia str
Kazan Moscow +7 495 2317217 IS_Russia@basf.com
Krasnodar Moscow +7 495 2317217 IS_Russia@basf.com
Krasnogorsk Moscow +7 495 2317217 IS_Russia@basf.com
Krasnoyarsk Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Kurgan Moscow +7 495 2317217 IS_Russia@basf.com
Kursk Moscow +7 495 2317217 IS_Russia@basf.com
Lipetsk Moscow +7 495 2317217 IS_Russia@basf.com
Moscow Moscow +7 495 2317217 IS_Russia@basf.com
Moscow (Wintershall) Moscow +7 495 2312835 IS-Russia-
(Wintershall) W intershall@wintershall.com
Nishnekamsk Moscow +7 495 2317217 IS_Russia@basf.com
Nizhny Novgorod Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Novosibirsk Moscow +7 495 2317217 IS_Russia@basf.com
Novosibirsk Moscow +7 495 2317217 IS_Russia@basf.com
Omsk; Livenskaya str Moscow +7 495 2317217 IS_Russia@basf.com
Orel Moscow +7 495 2317217 IS_Russia@basf.com
Pavlovsky Posad Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Penza Moscow +7 495 2317217 IS_Russia@basf.com
Podolsk Pavlovsky Posad +7 49643 51949 IS_Russia@basf.com
pos. Novopushkinskoe Moscow +7 495 2317217 IS_Russia@basf.com
pos.Gorodishe Moscow +7 495 2317217 IS_Russia@basf.com
pos.im.Kuibysheva Moscow +7 495 2317217 IS_Russia@basf.com
pos.Shushary Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Pushkino; Malinovskogo Moscow +7 495 2317217 IS_Russia@basf.com
Str
Rostov-na-Donu Moscow +7 495 2317217 IS_Russia@basf.com
Ryanzan Pavlovsky Posad +7 49643 51949 IS_Russia@basf.com
Samara Pavlovsky Posad +7 49643 51949 IS_Russia@basf.com
Smolensk Moscow +7 495 2317217 IS_Russia@basf.com
St. Petersburg Moscow +7 495 2317217 IS_Russia@basf.com
Stavropol Moscow +7 495 2317217 IS_Russia@basf.com
Surgut Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Tiumen Moscow +7 495 2317217 IS_Russia@basf.com
Toghliatti Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Ufa Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Vladivostok Moscow +7 495 2317217 IS_Russia@basf.com
Volgograd Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Voronezh Moscow +7 495 2317217 IS_Russia@basf.com
Vsevolozhsk Pavlovsky Posad +7 49643 51949 IS-Russia-W ostok@basf.com
Zherdevka Moscow +7 495 2317217 IS_Russia@basf.com
Table 34: GPS III Rollout Service Desk EMEA: CIS Countries – Russian
Federation
6.2.2.8 EMEA: Middle East / South Africa

(only internal)
Algeria Istanbul +90 216 577-7757 istanbul-sd@basf.com
Bahrain Dubai +9714-8817757 istanbul-sd@basf.com
Egypt Cairo +2-016-555-7757 istanbul-sd@basf.com
Jordan Cairo +2-016-555-7757 istanbul-sd@basf.com
Morocco Istanbul +90 216 577-7757 istanbul-sd@basf.com
Oman Dubai +9714-8817757 istanbul-sd@basf.com
Saudi Arabia Dammam +96638121140 - Ext. istanbul-sd@basf.com
775
South Africa Midrand +27 860 109 788 rsa.helpdesk@basf.com
Tunisia Istanbul +90 216 577-7757 istanbul-sd@basf.com
Turkey Istanbul +90 216 577-7757 istanbul-sd@basf.com
United Arab Dubai +9714-8817757 istanbul-sd@basf.com
Emirates
Table 35: GPS III Rollout Service Desk EMEA: Middle East / South Africa
6.2.3 GPS III Rollout Service Desk: Phone numbers APAC
Which number you dial to reach the GPS III Service Desk depends on
where you are located:
 If you call from within a BASF office, see chapter 6.2.3.1, Table 36.
 If you call from outside a BASF office, see chapter 6.2.3.2, Table
37.
 To reach the GPS III Service Desk, dial the respective number and
press 8.
6.2.3.1 Calls from within a BASF site
English-language speakers across the region can call the Manila SD.
Site Country BCN IDD

Chengdu China 8696 9017 + 603 2246 9017
Chengdu Hong Kong 8696 9020 + 603 2246 9020
Chengdu Japan BJL, BPZ 8696 9021 + 603 2246 9021
Chengdu Japan BCJ 8696 9023 + 603 2246 9023
Chengdu Japan BIC 8696 9024 + 603 2246 9024
Chengdu Korea 8696 9007 + 603 2246 9007
Chengdu Taiwan 8696 9014 + 603 2246 9014
Manila Australia 8696 9001 + 603 2246 9001
Manila Bangladesh 8696 9002 + 603 2246 9002
Manila India 8696 9004 + 603 2246 9004
Manila New Zealand 8696 9009 + 603 2246 9009
Manila Pakistan 8696 9010 + 603 2246 9010
Manila Philippines 8696 9011 + 603 2246 9011
Manila Singapore 8696 9012 + 603 2246 9012
Manila Vietnam 8696 9025 + 603 2246 9025
Singapore Indonesia 8696 9005 + 603 2246 9005
Singapore Malaysia 8696 9008 + 603 2246 9008
Singapore Malaysia BASC 8696 9003 + 603 2246 9003
Singapore Thailand 8696 9019 + 603 2246 9019
Table 36: GPS III Rollout Service Desk: Phone numbers APAC for calls from
within a BASF site
6.2.3.2 Calls from outside a BASF site
Country Toll Free Numbers Toll Paid Numbers

Australia 1800025560 +61(0)280318515
Bangladesh 888 517 7267 +60 362074470
China 8008100408 +86(0)10 6476 2233
Hong Kong 800903297 +852 30713713
India 8004401958 -
Indonesia 1803442347 -
Japan 531650541 +81(0)364042834
South Korea 7986517508 +82(0)234831413
Malaysia 1800806581 +60(0)362074470
New Zealand 800452701 +64(0)99127607
Pakistan 80090044120 -
Philippines 180089086382 +63(0)26262473
Singapore 8001863010 +65 66221796
Taiwan 806651949 +886(0)277457260
Thailand 18004413662 -
Vietnam 12011147 -
Table 37: GPS III Rollout Service Desk: Phone numbers APAC for calls from
outside a BASF site
6.2.4 GPS III Rollout Service Desk: Phone numbers NA
Site Country Toll Toll-Free
Sao El Salvador (current) 011 800 6680

Paulo (planned) 800 6860
Sao Panama 00800 054 0363

Paulo
Sao Honduras 8000 122 pin 8367
Paulo
Sao Nicaragua 1800 0166 - pin 8368
Paulo
Sao Dominican 1-800-888-8000
Paulo Republic PIN:8323
Sao Costa Rica 0800-016-1086

Paulo
Sao Mexico 1-800-123-4627
Paulo
Sao Guatemala 1-800-300-0075
Paulo
Manila USA 1-513-336- 1-800-542-3020
1421
Manila Canada 1-513-336- 1-800-542-3020

1421
Table 38: GPS III Rollout Service Desk: Phone numbers NA

6.2.5 GPS III Rollout Service Desk: Phone numbers SA
Site Country Internal External
Sao Argentina 7757 0800 333 0749

Paulo
Sao Bolivia 7757 800 100 857
Paulo
Sao Brazil 7757 0800 770 2105
Paulo
Sao Chile 7757 800 201 706
Paulo
Sao Colombia 7757 018 009 171 086
Paulo
Sao Equador 7757 1800 102 043
Paulo
Sao Paraguay 7757 009 800 542 0058
Paulo
Sao Peru 7757 800 54 650
Paulo
Sao Uruguay 7757 000 405 4093

Paulo
Sao Venezuela 7757 800 100 4619
Paulo
Table 39: GPS III Rollout Service Desk: Phone numbers SA

6.2.6 GPS III Rollout Service Desk: E-mail addresses APAC,
NA, SA
Location Email
APAC GPSIII-PROJECT-ASIAPACIFIC@basf.com
NA GPSIII-NA-Rollout-Team@basf.com
SA GPSIII-SA@basf.com
Table 40: GPS III Rollout Service Desk: E-mail addresses APAC, NA, SA
6.3 24/7 DTM Support Team
Service Times: 24/7
Telephone: +49 621 60-52010
E-mail: is-dtmsupport-gps3rollout@basf.com
Languages: English, German

6.4 Technical Expert Team
Service Times: The Technical Expert Team is available 8 a.m. to 5 p.m.
local time.
Contact data: See Table 41.
Region Name Hotline Email
EMEA Tobias Stichter 97500 tobias.stichter@basf.com
NA Thomas Wardell 973-895-8428 thomas.wardell@basf.com
SA Anderson Romero 85511-3688 or anderson.romero@basf.com

+55 11 3043-3688
AP Revant Singh +65 6398 5193 revant.singh@partners.basf.com

(ESN: 865 5193)
Zoran Begic +65 6398 5184 zoran.begic@partners.basf.com

(ESN: 865 5184)
Table 41: Contact Data Technical Expert Team

6.5 Rollout Coordination
Service Times: The Rollout Coordination is available 8 a.m. to 5 p.m. local
time.
Contact data: See Table 42.
Region Country Name Phone Email
EMEA Ilker Oezbek +49 621 Ilker.oezbek@partners.basf.com

60 41891
NA Gary Wane +1 973 gary.wane@basf.com

895 8262
Mark Wickenheiser +1 973 mark.wickenheiser@basf.com

895 8331
SA Rodrigo Matiello +55 11 rodrigo.matiello@basf.com

3043 3712
AP China Magic Ou Liang +86 021 liang.ou@partners.basf.com

2320 3431
Korea Paul Kim +82 2 sungwoong.kim@partners.basf.com

3707 6096
Japan Akiko Yagi +81 3 akiko.yagi@partners.basf.com

3796 4106
Other Yikwen Goo +65 yikwen.goo@partners.basf.com

Countries 6398 5181
Eugene Fong eugene.fong@partners.basf.com
Table 42: Contact Data Rollout Coordination

7 Appendix
7.1 FAQ
Defective asset while located at DP1 or at transport to DP2 ............................... 219
No access to AD ................................................................................................... 220
No BISTRO access .............................................................................................. 220
Insufficient numbers / wrong / defective assets delivered from DP1.................... 220
Issues concerning the rollout wizard .................................................................... 220
Rollout numbers cannot be reached .................................................................... 221
Replanning of the rollout because of errors or complaints or incidents ............... 221
User relocates, rollout is carried out in a new location ......................................... 221
User cannot be found at location described in rollout appointment ..................... 221
User has requested a schedule change ............................................................... 221
Rollout Technician cannot keep appointment ...................................................... 222
User has no time at the time of the scheduled appointment. ............................... 222
Rollout Technician cannot connect to BISTRO .................................................... 223
Smartcard: User cannot log on to MyID ............................................................... 223
VIP: Technical problems while rollout .................................................................. 224
VIP: installation cannot be terminated .................................................................. 224
GPS III Asset has to be returned .......................................................................... 225
Card reader is defective ....................................................................................... 225
The wrong GPS III asset is delivered ................................................................... 225
Missed or wrongly supplied periphery of GPS III asset ........................................ 225
A defective PC was delivered ............................................................................... 226
A defective keyboard, mouse or docking station was delivered or hardware
is incomplete ......................................................................................................... 226
User wants to change software on GPS III asset ................................................. 227
Lotus Notes icons are missed .............................................................................. 227
Business-critical BSA is not available .................................................................. 227
Not-Business-critical BSA is not available............................................................ 228
User has taken the new hardware with him ......................................................... 228
User wants to test BSAs ....................................................................................... 228
User wants to test special Services not ordered .................................................. 229
User wants installation of additional Services which were not ordered ............... 229
User's printer / scanner not declared via BISTRO beforehand ............................ 230
User wants to keep GPS II asset.......................................................................... 230
User and Information Manager agree to refuse the acceptance of the new
computer ............................................................................................................... 231
Postponed Initial Acceptance overview (Installation cannot be completed
during normal working hours) ............................................................................... 231
Migration has passed successfully, but user has no time left and does not
want to perform the Initial Acceptance at present. ............................................... 232
User is not present for signing the Initial Acceptance .......................................... 232
User wants to have incident tickets processed .................................................... 232
User has forgotten/broken his employee badge................................................... 233
Smartcard: “..device ready to be collected” is missing ......................................... 233
Smartcard: User is not available during rollout..................................................... 233
Data Migration Wizard runs a long time and user has to leave............................ 233
Data Migration Wizard runs past the end of the normal working day .................. 234
Data migration fails on GPS III asset ................................................................... 234
Data Migration Wizard aborts ............................................................................... 234
Data Migration Wizard icon not at desktop........................................................... 235
Data counter idle on the GPS III asset, script seems to have stopped ................ 235
Data Migration Wizard runs again after the user's first logon following the
migration ............................................................................................................... 235
GPS II-script does not start / aborts in the user environment .............................. 236
7.2 GPS III Process Chart
The GPS III process chart is attached as a figure, displayed via 5 pages
(Figure 159, Figure 160, Figure 161, Figure 162 and Figure 163).
Figure 159:GPS III Process Sheet, Part 1

Figure 160 : GPS III Process Sheet, Part
2
3
4
Figure 163: GPS III Process Sheet, Part 5

7.3 GPSIII Infrastructure Storage Server -
Prerequisites and Configuration for Staging
Areas
7.3.1 Introduction
7.3.1.1 Purpose
During provisioning process all installation files (OS image, application

sources) are downloaded from a software repository which is hosted on the
GPSIII Infrastructure Storage Server located within each staging area.
This chapter describes the requirements and configuration of a GPSIII

Infrastructure Storage Server (mypack.basf.net) in staging areas.
7.3.1.2 Requirements
7.3.1.2.1 Infrastructure Storage Server (MYPACK.BASF.NET)
 Local Functional Replication Account (used for automated SW

repository sync)
o Name: admSWREPADM
o Pass: adm4SWREP$
 Deactivated Windows Firewall
 Deactivated UAC
 Static IP address taken from the defined IP range for the staging
area. Recommendation: Use IP address x.x.x.10 for the ISS server
7.3.1.2.2 Hardware
 Min. 1 Processor machine with 4 GB RAM
 1 disk volume (drive F:) with at least 1500 GB free disk space
7.3.1.2.3 Software
 Microsoft Windows 2008 R2
 IIS7
 Activate Alias Resolution:
o HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\p
arameters
 "DisableStrictNameChecking"=dword:00000001
o HKLM\SYSTEM\CurrentControlSet\Control\Lsa

 "DisableLoopbackCheck"=dword:00000001

7.3.1.2.4 Communication (Ports and Protocols)
See Figure 164 for an overview of the communication ports and protocols.
Figure 164: Communication; Ports and Protocols
7.3.2 Configure software repository of GPSIII Infrastructure

Storage Server
You want to configure the software repository (SWREP) for the GPSIII
Infrastructure Storage Server.
The definition of drive letter for software repository could be different.
The drive letter has to be defined by the infrastructure team.
In this steps below the drive letter F: is used for for the software repository.
Steps:
1. Open Windows Explorer
2. Create SWREP folder: Create folder F:\SWREP (Figure 165).
 Folder F:\SWREP is displayed in the Windows Explorer.
Figure 165: Create Folder
3. Define permission on root drive F:\
A. Right-click the drive F:/
B. Select Properties.
 The form (F:) Data Properties is displayed.

C. Select Security.
D. Click Advanced.
 The form Advanced Security Settings for Data (F:) is

displayed.
E. Select Everyone.
F. Click Change Permissions.
G. Select Everyone.
H. Click Edit.
I. Change file permission in Data (F) Properties (Figure 166

and Figure 167):
 Administrators: Full Control
 SYSTEM: Full Control
 Everyone: READ (for this folder only!)
J. Click OK.

Figure 166: User Properties
Figure 167: Change Properties
4. Create and set share permissions of SWREP in Advanced Sharing

(Figure 168).

Figure 168: Advanced Sharing
A. Open Properties of F:\SWREP
 The form SWREP is displayed.

B. Select Sharing Tab
C. Open Advanced Sharing
 The form Advanced Sharing is displayed.

D. Click Share this folder.
E. Set Share name: SWREP
F. Set Comments: DTM Software Repository
G. Open Permissions
 The form Permissions for SWREP is displayed.

H. Share permission in Permissions for SWREP (Figure 169):
 Administrators: Full Control
 admSWREPADM: Full Control
 Everyone: Full Control

Figure 169: Share Permissions
I. Click OK.

J. Open Caching
K. Deactivate offline folder options: Set offline folder options to

No files or programs from the shared folder are available
offline (Figure 170).
L. Click OK.

M. Click OK.

Figure 170: Offline Settings
5. Set folder permission of F:\SWREP.
A. Select Security
B. Select Advanced
C. Click Change Permission
 The form Advanced Security Settings for SWREP is

displayed.
D. Deactivate Replace all child object permissions with
inheritable permissions from this object (Figure 171).

Figure 171: Set Folder Permissions
E. Click Add.
 The form Advanced Security Settings for SWREP is

displayed.
F. Click OK.

G. Edit Permissions for SWREP (Figure 173).
Figure 172: Edit Permissions
 Set folder permission:
 SYSTEM: Full Control
 Administrators: Full Control
 admSWREPADM: Full Control
 Everyone: Read
H. Click OK.

Figure 173: Set Permissions

7.3.3 Installation and Configuration of GPSIII Infrastructure
Storage Server
7.3.4 Installation
You want to install the GPSIII Infrastructure Storage Server.
 You have configured the software repository (SWREP) for the

GPSIII Infrastructure Storage Server, see chapter 7.3.2.
Steps:
1. From Windows, open Start Menu | Administrative Tools | Internet

Information Services (IIS)
2. Open Server Manager / Roles / Add Roles
 The form Before You Begin is displayed.

3. Skip form Before You Begin with Next.
 The form Select Server Roles is displayed.

4. Select Server Roles: Web Server IIS (Figure 174).
Figure 174: Select Server Roles
5. Click Next (Figure 174).
 The Web Server (IIS) form is displayed.

Figure 175: Web Server (ISS)
 The Select Role Service form is displayed.
Figure 176: Select Role Service
7. Check default settings as shown in Figure 176.

 The form Confirm Installation Selection is displayed.
Figure 177: Confirm Installation Selection
9. Click Install (Figure 177).
Figure 178: Installation Results
 The Installation is finished when the form shows the

message Installation succeeded.
10. Click Close (Figure 178).
7.3.5 Configuration
You want to configure the GPSIII Infrastructure Storage Server.

 You have installed the GPSIII Infrastructure Storage Server, see

chapter 7.3.3.

Steps:
1. From Windows, open Start Menu | Administrative Tools |

Internet Information Services (IIS) Manager
2. Define new Application Pool.
A. Right-click on Application Pools (Figure 179).
Figure 179: Add Application Pool
B. Select Add Application Pool (Figure 180).
C. Set Name to SWREP.
Figure 180: Add Application Pool
D. Click OK.
3. Right-click on DefaultWebSite (Figure 181).
4. Select Add Application.

Figure 181: DefaultWebSite
5. Set Alias name: SWREP (Figure 182).
6. Select Application pool: SWREP.
7. Set Physical path: F:\SWREP.
8. Click OK.
Figure 182: Add Application
9. Select SWREP Home.
10. Check Authentication (Figure 183).
Figure 183: Check Authentication

11. Set Anonymouse Authentication to Enabled (Figure 184).
Figure 184: Authentication
12. Switch to SWREP Home.
13. Open MIME Types (Figure 185).
Figure 185: MIME Types
14. Add MIME Type (Figure 186).
A. Set File name extension to .*
B. Set MIME type to application/octet-stream.
Figure 186: Add MIME Types

Figure 187: MIME Types
15. Switch to SWREP Home.
16. From the MS Windows menu, open CMD.exe.
17. Enter IISRESET.
18. Press Return on the keyboard.

7.3.6 File permission for Anonymous Authentication
You want to set the file permission for anonymous authentication for the
GPSIII Infrastructure Storage Server.

GPSIII Infrastructure Storage Server. For more information, see
chapter 7.3.2.
 You have installed the GPSIII Infrastructure Storage Server. For

 You have configured the GPSIII Infrastructure Storage Server. For

Steps
1. Start the Windows Explorer.
2. Right-click F:\SWREP.
3. Select Properties.
 The form F:\SWREP Properties is displayed.

4. Select Security
5. Click Edit.
 The form Permission for F:\SWREP is displayed.

6. Click Add
 The form Select Users, Computers, Service Accounts, or

Groups is displayed.
7. Insert IUSR to Enter the object bames to select.
8. Click OK.
9. Set the following folder permissions (Figure 188):
o SYSTEM: Full Control
o Administrators: Full Control
o admSWREPADM: Full Control
o Everyone: Read
o IUSR: Read
10. Click OK.

Figure 188: Permission for SWREP
7.3.7 Testing Download

You want to test the download oft he software repository.

 You have installed the GPSIII Infrastructure Storage Server, see

chapter 7.3.3.
 You have configured the GPSIII Infrastructure Storage Server, see

chapter 7.3.5.
 You have set the file permission for anonymous authentication for
the GPSIII Infrastructure Storage Server, see chapter 7.3.6.
Steps
1. Open the Windows Explorer.
2. Copy the application notepad.exe into the folder F:\SWREP.
3. In MS Internet Explorer 8, insert the following URL in the adress bar

(Figure 189).
o url: http://SW REPServer/SW REP/notepad.exe

Figure 189: File Download Security Warning
 The form File Download – Security Warning is displayed.

4. Click Save.
5. Save file on desktop.
 After successful download, the webserver is running fine.

7.4 Work instruction: Creating a script for keeping
DTM Software Repositories up-to-date
7.4.1 Introduction
The DTM Software Repository (SWREP) is hosted on local Infrastructure
Storage Servers (ISS) and is used as a source for application source files
during the staging process. The repository needs to be updated regularly to
avoid installation issues
This chapter describes how to keep DTM Software Repositories

synchronized using a script.
7.4.1.1 Requirements
 ISS server (running on Windows Server 2008)
 Administrative rights on the ISS server hosting the DTM Software

Repository
7.4.2 Creating a script to sync the repository

You want to create a script to synchronize the central BASF SWREP
repository with your local SWREP repository on your local GPSIII
Infrastructure Storage Server.
Synchronization tool:
 To synchronize the SWREP repository the tool Robust File Copy

for Windows (robocopy) is used.
 This tool is already installed on Windows Server 2008 and requires

no additional installation step.
Synchronization account:
 To synchronize the SWREP repository, the following account is

used:
o Name: basfad\dtmgtn
o Password: DtmGTN3$
Prior to creating the script you have to determine the following:
 Destination path: The exact path on the ISS server where the
repository server is located (e.g. I:\SWREP)

 Source path: The UNC path of a Level 1 SWREP server located in
the BASF corporate network (e.g. \\dmdelumypack.basf.net\swrep).
Please refer to Table 44 for a list of all Level 1 SWREP servers.
Use the following robocopy-commands to synchronize the repository:
 robocopy /mir /w:10 /r:2 <source path> <destination path>
Scripting the synchronization of the SWREP repository:
 See the script described in Table 43 for an example script with the
robocopy command and the destination and source path.
 Save the script in the folder c:\temp\syncSWREP.cmd.

Table 43: Example Script
Example script (please adapt values for source and destination

accordingly)
@echo off
set MyDir=%~dp0
set source=\\dmdelumypack.basf.net\swrep
set destination=f:\swrep
rem authenticate
net use %source% DtmGTN3$ /user:basfad\dtmgtn
robocopy /mir /w:10 /r:2 /np %source% %destination%
/log+:%MyDir%\SWREPSync.log
7.4.3 Scheduling a synchronization job

To avoid issues during staging process we strongly recommend to
synchronize the local SWREP Repository folder on a regular basis using a
scheduled script.
See Table 44 for a list of available Level1 SWREP servers.

Table 44: List of all available Level1 SWREP servers
dmdelumypack.basf.net Level1 SWREP server

EMEA
WUSANDISSL101.basfad.basf.net Level1 SWREP server

NA
WUSYTPISSL101.basfad.basf.net Level1 SWREP server
NA
WSGSIN3447594.basfad.basf.net Level1 SWREP server
APAC
WHKHKG3562480.basfad.basf.net Level1 SWREP server
APAC

WBRQSBISSL101.basfad.basf.net Level1 SWREP server
SA
 A synchronization script as described in chapter 7.4.2 has been

created and stored on the ISS server as
c:\temp\syncSWREP.cmd.
 Administrative rights on the ISS server.
Steps
1. Store the scheduled task definition (see Table 45) in c:\temp on the
ISS server.
2. On the ISS server:
A. Open the Windows Task Scheduler.
 The form Task Scheduler is displayed.

B. Click Import Tasks to import the xml file (Figure 190).
Table 45: Scheduled Task Definition: syncSWREP.xml
syncSWREP.xml
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2"
xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2011-08-03T15:42:46.4800661</Date>
<Author>system</Author>
<Description>synchronizes DTM SW repository with a level1 SWREP
server</Description>
</RegistrationInfo>
<Triggers>
<CalendarTrigger>
<StartBoundary>2011-08-03T22:00:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>W72GXYT4J\admSWREPADM</UserId>
<LogonType>Password</LogonType>
<RunLevel>LeastPrivilege</RunLevel>

</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>P3D</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>C:\Temp\syncSWREP.cmd</Command>
<WorkingDirectory>c:\temp</WorkingDirectory>
</Exec>
</Actions>
</Task>
Figure 190: Task Scheduler
C. After importing the xml file:

I. Select the tasks syncSWREP in the Task Scheduler
Library of the form Task Scheduler.
II. Check task properties (e.g. when is the script

triggered), see Actions area in the form Task
Scheduler.
III. Confirm any changes with OK (Figure 191).
Figure 191: Create Task

7.5 Tables
Table 1: Business Centers........................................................................ 18
Table 2: Regions and Countries ............................................................... 18
Table 3: Pre-Pilot Regions and Countries ................................................. 20
Table 4: Pilot Regions and Countries........................................................ 20
Table 5: Roles in GPS III Rollout Process................................................. 21
Table 6: GPS III Timelines ........................................................................ 23
Table 7: Rollout Volume Pre-Pilot ............................................................. 24
Table 8: Rollout Volume Pilot.................................................................... 24
Table 9: Rollout Volume Ramp Up Phase ................................................ 24
Table 10: Rollout Volume Mass Rollout .................................................... 25
Table 11: Ultra Portable Notebook (13") – Dell Latitude E6320 ................ 26
Table 12: Desktop Replacement Notebook (15") - Latitude E6520 ........... 28
Table 13: Portable Workstation Notebook (17") – Dell Precision M6600 ... 29
Table 14: Desktop – Minitower – Dell Optiplex GX990 ............................. 30
Table 15: Desktop Workstation (Tower) – Dell Precision T3500 ............... 31
Table 16: Additional Deletion Information, example .................................. 56
Table 17: gAHD Rollout Provider Assignee Groups .................................. 62
Table 18: Incident Examples .................................................................... 62
Table 19: Rollout Provider Processing of Incident Tickets ........................ 63
Table 20: Addresses for delivery note and transport documentation......... 97
Table 21: Hardware configuration of GPS III asset types ........................ 116
Table 22: IPass User Names .................................................................. 175
Table 23: gAHD Rollout Coordination Assignee Groups ......................... 206
Table 24: Addresses for delivery note and transport documentation....... 210
Table 25: Addresses for data deletion protocol ....................................... 216
Table 26: GPS III support services and target groups............................. 237
Table 27: GPS III Rollout Service Desk Service Times ........................... 238

Table 32: GPS III Rollout Service Desk EMEA: North............................. 239
Table 34: GPS III Rollout Service Desk EMEA: West ............................. 239
Table 33: GPS III Rollout Service Desk EMEA: South ............................ 240
Table 28: GPS III Rollout Service Desk EMEA: Central .......................... 240
Table 35: GPS III Rollout Service Desk EMEA: Switzerland ................... 241
Table 29: GPS III Rollout Service Desk EMEA: CIS Countries ex Russia241
Table 30: GPS III Rollout Service Desk EMEA: CIS Countries – Russian
Federation .............................................................................................. 243
Table 31: GPS III Rollout Service Desk EMEA: Middle East / South Africa
............................................................................................................... 243
Table 36: GPS III Rollout Service Desk: Phone numbers APAC for calls
from within a BASF site .......................................................................... 244
Table 37: GPS III Rollout Service Desk: Phone numbers APAC for calls
from outside a BASF site ........................................................................ 245
Table 38: GPS III Rollout Service Desk: Phone numbers NA ................. 246
Table 39: GPS III Rollout Service Desk: Phone numbers SA.................. 247
Table 40: GPS III Rollout Service Desk: E-mail addresses APAC, NA, SA
............................................................................................................... 248
Table 41: Contact Data Technical Expert Team ..................................... 250
Table 42: Contact Data Rollout Coordination .......................................... 251
Table 43: Example Script........................................................................ 281
Table 44: List of all available Level1 SWREP servers ............................. 281
Table 45: Scheduled Task Definition: syncSWREP.xml .......................... 282

7.6 Figures
Figure 1: GPS III Process by Stages ........................................................ 21
Figure 2: Dell Latitude E6320; Front Side ................................................. 32
Figure 3: Dell Latitude E6320; Right Side ................................................. 32
Figure 4: Dell Latitude E6320; Back Side ................................................. 33
Figure 5: Dell Latitude E6320; Card Reader ............................................. 33
Figure 6: Dell Latitude E6320; Bottom Side .............................................. 33
Figure 7: Dell Latitude E6320; Bottom Side; Service Tag (serial number). 34
Figure 8: Dell Latitude E6520, Front Side ................................................. 35
Figure 9: Dell Latitude E6520, Left Side ................................................... 35
Figure 10: Dell Latitude E6520, Right Side ............................................... 36
Figure 11: Dell Latitude E6520, Back Side................................................ 36
Figure 12: Dell Latitude E6520, Bottom Side ............................................ 36
Figure 13: Dell Latitude E6520, Bottom Side; Service Tag (serial number)
................................................................................................................. 37
Figure 14: Dell Precision M6600; Left Side ............................................... 38
Figure 15: Dell Precision M6600; Right Side............................................. 38
Figure 16: Dell Precision M6600; Back Side ............................................. 39
Figure 17: Dell Precision M6600; Bottom Side.......................................... 39
Figure 18: Dell Precision M6600; Bottom Side; Service Tag (serial number)
................................................................................................................. 39
Figure 19: Minitower Dell OptiPlex 990; Front Side................................... 40
Figure 20: Minitower Dell OptiPlex 990; Left Side ..................................... 41
Figure 21: Minitower Dell OptiPlex 990; Back Side ................................... 41
Figure 22: Minitower Dell OptiPlex 990; Back Side, Service Tag (used to
identify Asset Inventory Number) .............................................................. 42
Figure 23: Dell Precision T3500; Front Side ............................................. 43
Figure 24: Dell Precision T3500, Top Side................................................ 44
Figure 25: Dell Precision T3500; Back Side.............................................. 44

Figure 26: Dell Precision T3500 Back Side, Service Tag (used to identify
Asset Inventory Number) .......................................................................... 45
Figure 27: Dell External Mini USB Modem ................................................ 45
Figure 28: Smartcard, Personalized.......................................................... 50
Figure 29: Smartcard, Not Personalized ................................................... 50
Figure 30: Barcode Scanner, Example ..................................................... 52
Figure 31: 4Q-Report Page 1.................................................................... 60
Figure 32: 4Q-Report Page 2.................................................................... 60
Figure 33: gAHD Incident Process and Status Codes............................... 64
Figure 34: E-mail Incident Notification ...................................................... 65
Figure 35: Login to gAHD ......................................................................... 66
Figure 36: Main form of gAHD .................................................................. 66
Figure 37: Edit an Existing incident ticket in gAHD ................................... 67
Figure 38: Assign a gAHD incident ticket: Activities – Transfer ................. 68
Figure 39: Assign a gAHD incident ticket: Transfer Incident dialog box .... 69
Figure 40: Self-assignment of an incident ticket........................................ 70
Figure 41: Incident Ticket Assignment, Menu Activities | Transfer… ......... 71
Figure 42: Incident Ticket Assignment to a Member of your Assignee Group

................................................................................................................. 71
Figure 43: Incident Ticket Status, Menu Activities | Update Status… ........ 72
Figure 44: Update Incident Ticket Status; Set Status to Work in Progress 72
Figure 45: Update Incident Ticket Status; Set Status to Wait for User Action
................................................................................................................. 73
Figure 46: Update Incident Ticket Status; Set Status to Fixed .................. 73
Figure 47: Manually Notify User about Status of Incident Ticket ............... 74
Figure 48: Search for an Incident Ticket ................................................... 75
Figure 49: Search for an Incident Ticket with Incident Ticket Number Not
Available................................................................................................... 75
Figure 50: Select incident ticket to be displayed ....................................... 76
Figure 51: gAHD Main Form, Menu Search | Profile Browser ................... 77
Figure 52: Profile Browser Contact Search ............................................... 77

Figure 53: Profile Browser Contact List..................................................... 78
Figure 54: Incident History ........................................................................ 78
Figure 55: Incident History Table .............................................................. 78
Figure 56: gAHD Main Form; Menu Search | Configuration Items............. 79
Figure 57: Configuration Item Search ....................................................... 80
Figure 58: Configuration Item Search ....................................................... 81
Figure 59: Configuration Item List ............................................................. 81
Figure 60: Configuration Item List ............................................................. 82
Figure 61: Configuration Item Detail; Tab 4. Service................................. 82
Figure 62: Configuration Item Detail; Tab 6. Location ............................... 82
Figure 63: Configuration Item Detail; Tab 7. Contacts .............................. 83
Figure 64: gAHD Main Form ..................................................................... 84
Figure 65: Profile Browser Contact Search ............................................... 84
Figure 66: Contact Information ................................................................. 85
Figure 67: Contact Information for <User>................................................ 85
Figure 68: Boot menu (= F12 Hotkey) during start-up-/boot-process ...... 106
Figure 69: Windows Deployment Wizard ................................................ 106
Figure 70: Tools for support BIS PE ....................................................... 107
Figure 71: Create BIS PE Boot Stick ...................................................... 107
Figure 72: WLAN switch in position On................................................... 109
Figure 73: Boot Menu ............................................................................. 110
Figure 74: Boot PC from USB device...................................................... 110
Figure 75: Boot PC from USB device...................................................... 110
Figure 76: Windows Deployment Wizard ................................................ 111
Figure 77: Windows Deployment ............................................................ 111
Figure 78: Windows Deployment: Expanding Windows files ................... 111
Figure 79: Windows Deployment: Starting of services ............................ 112
Figure 80: Windows Deployment: Completing of the installation ............. 112
Figure 81: Windows Deployment, Reboot............................................... 112

Figure 82: Windows starts ...................................................................... 113
Figure 83: Windows Desktop preparation ............................................... 113
Figure 84: Installation wizard: Installing extra settings ............................ 113
Figure 85: Rollout wizard ........................................................................ 114
Figure 86: BGV A3 Prüfplakette PC 5 for mobile power supply units ...... 124
Figure 87: BGV A3 Prüfplakette PC 1 for power cables .......................... 125
Figure 88: WLAN switch in position Off................................................... 127
Figure 89: MS Windows 7 Start Screen .................................................. 127
Figure 90: Wi-Fi inactive icon.................................................................. 128
Figure 91: GPS III asset: Start GPS III Data Migration Wizard................ 128
Figure 92: GPS III Data Migration Wizard: Identify IP address of GPS III
asset....................................................................................................... 129
Figure 93: GPS III Data Migration Wizard: External hard disk was not found
message................................................................................................. 129
Figure 94: GPS III Data Migration Wizard: External DATA partition is not
empty message ...................................................................................... 130
Figure 95: Windows Explorer: Network drives ........................................ 130
Figure 96: Novell icon in system tray ...................................................... 131
Figure 97: Novell context menu .............................................................. 131
Figure 98: Novell login ............................................................................ 131
Figure 99: GPS II PC; Search and Start Run .......................................... 132
Figure 100: GPS II PC; Run the GPS II Data Migration Wizard .............. 133
Figure 101: GPS II PC; GPS II Data Migration Wizard ............................ 133
Figure 102: GPS II Data Migration Wizard message: LANCrypt key is red
............................................................................................................... 134
Figure 103: Microsoft Internet Explorer Address Bar .............................. 136
Figure 104: MyID Login .......................................................................... 136
Figure 105: MyID Main Menu.................................................................. 136
Figure 106: MyID Select Job .................................................................. 137
Figure 107: MyID Select Job Notification: Insert Smartcard .................... 137
Figure 108: MyID Create Card................................................................ 137

Figure 109: MyID Message..................................................................... 138
Figure 110: MyID Main Menu after Smartcard Enrollment ...................... 139
Figure 111: Pre-Boot Authentication Login; Start Screen ........................ 140
Figure 112: MS Windows Explorer: USB Hard disk mapped to drive F: or,
for example, drive E:............................................................................... 148
Figure 113: BitLocker Drive Encryption................................................... 148
Figure 114: BitLocker Recovery Key....................................................... 150
Figure 115: Save BitLocker Recovery Key.............................................. 151
Figure 116: BitLocker Drive Encryption: Recovery Key saved dialog box 151
Figure 117: BitLocker Drive Encryption: Start Encrypting........................ 152
Figure 118: BitLocker Drive Encryption Progress.................................... 152
Figure 119: System Tray: Data Syncchronisation icon............................ 153
Figure 120: Data Synchronization with GPS III USB disk dialog box....... 153
Figure 121: Data Synchronization message box..................................... 154
Figure 122: BitLocker encryption process finished.................................. 154
Figure 123: Collection of Desktops ......................................................... 160
Figure 124: Collection of Desktops - Row not filled ................................. 160
Figure 125: Collection of Notebooks ....................................................... 161
Figure 126: BIOS Screen GPS II PC ...................................................... 169
Figure 127: BIOS Setup; System Password ........................................... 170
Figure 128: BIOS Setup, Admin Password ............................................. 171
Figure 129: iPass Login; Username........................................................ 174
Figure 130: iPass Login; Password ........................................................ 175
Figure 131: iPass Login; Confirm Password ........................................... 175
Figure 132: iPass Client.......................................................................... 176
Figure 133: IPass Login Information ....................................................... 176
Figure 134: Model E6320: Location of SIM card slot............................... 178
Figure 135: Model E6520: Location of SIM card slot............................... 178
Figure 136: Model M6600: Location of SIM card slot .............................. 179

Figure 137: Wi-Fi icon ............................................................................ 180
Figure 138: Wi-Fi menu: Mobile Broadband Connection icon ................. 180
Figure 139: Verbindung mit einem Netzwerk herstellen - Entsperren...... 181
Figure 140: Verbindung mit einem Netzwerk herstellen - Automatische

Verbindung ............................................................................................. 181
Figure 141: Vodafone.de connection status Verbunden.......................... 182
Figure 142: Mobile Broadband Connection context menü....................... 182
Figure 143: Eigenschaften von mobilem Breitband Vodafone.de: Profil .. 183
Figure 144: Vodafone.de connection - Trennen ...................................... 184
Figure 145: Vodafone.de connection - Verbinden ................................... 184
Figure 146: Wi-Fi menu: Drahtlosnetzwerkverbindung trennen............... 185
Figure 147: Juniper Network icon in active status ................................... 185
Figure 148: LR Package example on the Local Hard Disk ...................... 186
Figure 149: Desktop Manager Icon on Windows Desktop....................... 187
Figure 150: LANDesk Desktop Manager with LR application example.... 187
Figure 151: LANDesk Information........................................................... 188
Figure 152: LANDesk LR Package example on the Local Hard Disk ...... 188
Figure 153: LANDesk LR Application Documentation example............... 189
Figure 154: LR Application Documentation example .............................. 189
Figure 155: LR Application example .reg-File ......................................... 190
Figure 156: Registry Editor Notification with LR application example...... 190
Figure 157: Registry Editor Confirmation with LR application example ... 190
Figure 158: GPS II docking station with encrypted backup hard disk ...... 217
Figure 159:GPS III Process Sheet, Part 1............................................... 255
Figure 160: GPS III Process Sheet, Part 2.............................................. 256
Figure 164: Communication; Ports and Protocols ................................... 262

Figure 165: Create Folder....................................................................... 263
Figure 166: User Properties.................................................................... 264
Figure 167: Change Properties ............................................................... 264
Figure 168: Advanced Sharing ............................................................... 265
Figure 169: Share Permissions............................................................... 266
Figure 170: Offline Settings .................................................................... 267
Figure 171: Set Folder Permissions........................................................ 268
Figure 172: Edit Permissions .................................................................. 268
Figure 173: Set Permissions................................................................... 269
Figure 174: Select Server Roles ............................................................. 270
Figure 175: Web Server (ISS)................................................................. 271
Figure 176: Select Role Service ............................................................. 271
Figure 177: Confirm Installation Selection............................................... 272
Figure 178: Installation Results............................................................... 272
Figure 179: Add Application Pool............................................................ 273
Figure 180: Add Application Pool............................................................ 273
Figure 181: DefaultWebSite.................................................................... 274
Figure 182: Add Application.................................................................... 274
Figure 183: Check Authentication ........................................................... 274
Figure 184: Authentication ...................................................................... 275
Figure 185: MIME Types ........................................................................ 275
Figure 186: Add MIME Types ................................................................. 275
Figure 187: MIME Types ........................................................................ 276
Figure 188: Permission for SWREP........................................................ 278
Figure 189: File Download Security Warning .......................................... 279
Figure 190: Task Scheduler.................................................................... 283
Figure 191: Create Task ......................................................................... 284

7.7 Bibliography
[Bericht] BASF: BISTRO Manual. - GPS III PO, 2011.
[Bericht] BASF GPS III PO: Contract Rollout Providers - BASF; GPS III
Rollout. - BASF Intern, 2010.

7.8 Glossary
Abbreviation or Full Version Comment
Term
AD Active Directory AD is a directory service created by Microsoft to
provide a variety of network services. It allows
administrators to assign policies and to deploy and
update software .
AD Application
Dashboard
ADI Application
Dashboard Interface
ADSp Allgemeine Deutsch General German Carrier Conditions
Speditionsbedingung
en
ANZ Australia New
Zealand
AO Application of Oracle
AO / TC Application Owner /
Technical Contact
AOB Any Other Business also common: Miscellaneous
APAC Asia PACific
Asset Asset Asset is any data, device, or other component of
the environment that supports information-
related activities. Assets generally include
hardware (eg. servers and switches), software (eg.
mission critical applications and support systems)
and confdential information.
BASF IS BASF Information The global competence Center Information
Services Services is responsible for all the BASF Group's IT/
IS activities worldwide.
BAU Business As Usual BAU Help Desk: after Rollout-phase…
BC Business Center
BCE Business Center East
BD Bangladesh
BGV A3 Label to be attached to the power supply units of
Prüfplakette GPS III docking stations and notebooks in
Germany.
BISTRO BASF Information BASF developed application, GPS III Planning Tool
Services Tool for of BASF
Rollout Activities
BR Brazil
BSA Business Specifc scriptesd SW package ready for installation
Application
BSA Business Specifc
Application
BU Business Unit
BuH Local Business Hours
CAD Computer Aided An application system for computer-supported
Design product development, design and construction
techniques.

CAM Computer Aided Computer-supported manufacturing, i.e
Manufacturing production in computer-supported processing
plants. Used for the computer-generated support
and monitoring of operating resources in
manufacturing processes.
CCHR Central HR data base
CMDB Confguration Software and hardware information of every asset
Management
Database
CN China
CSC Customer Service
Center
Data Deletion Third party responsible for deleting GPS II assets.
Provider See "Deletion"
Data migration Process of transferring legacy data from a User's
GPS II asset the the new GPS III asset
DE Deutsch (German)
Deletion (of a GPS Erasing data on hard disks of legacy assets. To
II asset) comply with the BASF information protection
guidelines no GPS II asset can leave BASF property
without the data being erased. The erasing can be
with a BASF certifed software or by mechanically
deleting (degaussing or shredding) the hard disk.
Delivery Point Logical Point where certain process steps are to be
performed. Multiple Delivery Points can be located
at the same physical location.
Delivery Point 1 Location where GPS III asseta are delivered to by
(DP1) the hardware provider.
Delivery Point 2 Location where an asset is setup by the rollout
(DP2) provider. Physically, this location can be the same
as for DP1.
Delivery Point 2.5 Location where an asset is temporarily stored after
(DP2.5) staging. Physically, this location can be the same as
the location of DP3.
Delivery Point 3 User's desk where an asset is delivered to the User
(DP3) by the rollout provider and where the data
migration and Initial Accetance takes place.
Delivery Point 4 Location where the GPS II assets are stored during
(DP4) the POIS phase and where they are deleted after
the POIS phase has expired
Delivery Point 5 Location where deleted GPS II assets are handed
(DP5) over to the Hardware Broker. Physically, this
location is the same as the location of DP4.
DiP Discussion in
Progress
DNS Domain Name
System
DOA Defective on Arrival
DP Delivery Point
DP Delivery Point Logical Point where certain process steps are to be
performed. Multiple Delivery Points can be located
at the same physical location.
EB Chemistry (BASF
Business Unit)

EC BASF Business Unit
EC Coating BASF Business Unit
(siehe EC)
EDI Electronic Data
Interface
EMEA Europe Middle East
Africa
Entitlement Period Entitlement Period Complete Phase of Rollout per PC incl. 2 days PoIS
EOB End Of Business End of working day
EPM Enterprise Project
Management
Frozen zone Frozen zone Time between end of planning and start of Rollout;
can be applied to subsets as well. No changes of
the asset are allowed within the timeline.
Functional account A functional account is an account that provides
you with several additional functionality for the
respective rollout case. As an Approver or
Information Manager you get your functional
account credentials with the rollout e-mails. In
addition to the functional account, you have to
login with your BASF AD credentials.
GAHD Global Advanced Ticketing System
Help Desk
GPS Global PC
Standardization
GPS Global PC
Standardization
GPS II see GPS
GPS III See GPS With the GPS III Project, BASF will replace around
95,000 PCs (including Cognis PCs) in 120 countries.
GSDM Global Service

Delivery Modell
GT Engineering &
Maintenance
GWSS Group-Wide
Workplace Support
Services
HECD Hardware Encrypted Conventional hard disks have a magnetized surface
Conventional Disks on which data is stored
HK Hong Kong
HSDPA High-Speed Downlink High-Speed Downlink Packet Access (HSDPA) is an
Packet Access enhanced 3G (third generation) mobile telephony
communications protocol in the High-Speed Packet
Access (HSPA) family, also dubbed 3.5G, 3G+ or
turbo 3G, which allows networks based on
Universal Mobile Telecommunications System
(UMTS) to have higher data transfer speeds and
capacity.
ID Indonesia
IM Information Manager Approves to resp. Ordering
IN India
Infrastructure Prerequisite for the staging of GPSIII assets at DP2
Storage Server

Intel Core I5/I7 Intel Core I5/I7 Processor – central processing unit
IRP Initial Rollout Plan
ISS Infrastucture Storage
Server
JP Japan
KPI Key Performance
Indicators
KR Korea
LAN Local Area Network
Legacy PC GPS II asset
Locally Registered Software whose installation media are in
Applications possession of the User or which is available on a
local server.
Location Building / campus (exception Berlin)
LR applications Locally Registered Applications
M&A Mergers and
Acquisitions
MUI Multilingual User
Interface
MY Malaysia
NA North America
No-show on part of The no-show on Part of BASF is documented, for
BASF example, in the following cases: The rollout case
has not been scheduled in time; the GPS III assets
have not been ordered in time, BISTRO has not
been available
No-show on part of The no-show on Part of the Rollout Provider is
the Rollout documented, for example, in the following cases:
Provider At DP2, the GPS III has not been installed in time;
the rollout technician did not show up at the
User’s desk at the scheduled time; at DP3, the GPS
III asset hardware was not delivered as specifed
and therefore was rejected by the User.
No-show on part of The no-show on Part of the User is documented,
the User for example, in the following cases: The User does
not show up at the User’s desk at the scheduled
time; the location of the User has changed to a
room which is not in direct proximity of the room
specifed on the routing slip; the User rejects the
GPS III asset though the GPS III asset was delivered
as specified.
NTR Nothing to Report
OD Operation Division
Order Order Pproduct and/or service-request from the
customer.
OSS On Site Service

PC Personal Computer IT asset of BASF.
PDC Primary Data
Conversion

PH Philipines
PK Pakistan
PMO Project Management
Ofce
PMO Project Management
Ofce
PN Package Number
PoIS Post Installation
Support
POIS phase Retention period until a GPS II asset is deleted.
Standard User: 1 week (5 business days), VIP: 6
weeks (30 business days)
PoIS-OSS Post of Installation
Support On Site
Support
PoIS-UHD Post of Installation
Support User Help
Desk
Primary User User who is responsible for the asset, but not
necessarily the actual User
Proposal Proposal Product and /or service delivered by IS to a
customer.
PWD Password
RACI Responsible,
Accountable,
Consulted, Informed
RC Rollout Coordination
RC Regional Coordinator
RDR Rollout Data
Readiness
RFP Request for Proposal
RO Roll Out
RoC Rollout Coordination

Role Role BASF uses the role-concept with GPS III to add
several authorizations to users, e.g. to manage
appointments (role Rollout Coordinator) or to
approve proposals (role Approver).
Rollout case The complete process steps from rollout e-mail 1

to the handover of legacy assets.
The rollout case comprises a User-specifc software
confguration which is assigned to a GPS III aseet.
Multiple rollout cases can be assigned to a single
User.
Routing slip Sheet of paper attached to the GPS III asset after
the GPS III asset is assigned to a User. For the
Rollout technician to be able to deliver the GPS III
asset, the routing slip contains the User's name,
the User's location, delivery date and services to
be delivered.

RP Rollout Provider
SA South America
SDB Solution Data Base Tool for Help Desk
Secondary User The actual User of an asset
Service tag Dell name for "serial number"
SG Singapore
Silence means If you do not reply to a request within the given
Acceptance timeframe, the request is supposed to be
answered positively.
SIS Siemens Information
Services
Site Site A location of BASF, build up by several buildings.
site city
Site Contact A BASF employee, for example, an Information
Manager. Information Manager/Site Coordinator,
who is responsible for the Site/Company/Business
Unit, respectively.
Site contact A BASF employee, for example, an Information
Manager. Information Manager/Site Coordinator,
who is responsible for the Site/Company/Business
Unit, respectively.
SL Sri Lanka
SLA Service Level
Agreement
SMA Silence Means Policy during Rollout
Acceptance
SmA Silence means If you do not reply to a request within the given
Acceptance. timeframe, the request is supposed to be
answered positively.
SPOC Single Point Of
Contact
SSD Solid State Disks SSDs use “flash” memories (fast, non-volatile
memories that permanently store data even when
the power is switched off). SSDs allow you to
access data much faster, enabling 1000 queries per
second to be answered .
Substitute User Any BASF employee who confrms the Initial
Acceptance if the User is absent
SW REP Software Repository
Tab Tabulator A tabbed document interface (TDI) is one that
allows multiple documents to be contained within
a single window, using tabs as a navigational
widget for switching between sets of documents.
It is an interface style most commonly associated
with web browsers, web applications, text editors,
and preference panes.
tbd to be defined
TC Technical Contact
TFS Team Foundation
Server

TFVC Team Foundation
Version Control
TH Thailand
TW Taiwan
UAT User Acceptance Test
UDMS User Data
Management System
UDMS HR Master data
UHD User Help Desk
UI User Interface A user interface is the system by which people
(users) interact with a machine.
UI User Interface
UMTS Universal Mobile One of the third-generation (3G) mobile
Telecommunications telecommunications technologies. The name
System UMTS, introduced by ETSI, is usually used in
Europe. Outside of Europe, the system is also
known by other names such as FOMA[1] or W-
CDMA.[nb 1][1] In marketing, it is often referred to
as 3G or 3G+.
USMT User State Migration Microsoft
Tool
VIP Very Important Manager level 2 and 3 +assistents + opion leaders
Person
VN Vietnam
VPN Virtual Private
Network
vPro v6 – 64bit OS vPro v6 – 64bit OS vPro Version 6 – 64-bit Operating System
VSS Visual Source Safe MS Source Code Management System
WiP Work in Progress
WLAN 2.0 Wireless local area Standardized global WLAN authentifcation which
network uses WPA2 encryption; end users dial into one
BASF global network – “Chemie2”


Gps III Rollout Provider Manual v146 20120126

Uploaded by

Copyright:

Available Formats

You might also like

Gps III Rollout Provider Manual v146 20120126

Uploaded by

Document Information

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

Gps III Rollout Provider Manual v146 20120126

Uploaded by

Copyright:

Available Formats

GPS III Rollout Provider Manual

Project: GPS III

BASF IS Page 1 of 301

Author Versio Change Reference

BASF IS Page 2 of 301

BASF IS Page 3 of 301

BASF IS Page 4 of 301

BASF IS Page 5 of 301

Delegated to Mayank Gupta, Danni Bhadrahn AP Regional Coordinator

Copy Name Location

BASF IS Page 6 of 301

BASF IS Page 7 of 301

BASF IS Page 8 of 301

BASF IS Page 9 of 301

BASF IS Page 10 of 301

BASF IS Page 11 of 301

BASF IS Page 12 of 301

BASF IS Page 13 of 301

 Services required from Rollout Provider.

 Details of accomplishment of Services.

o Handling of Services at properties of BASF.

o Usage of dedicated IT-services and dedicated tools of

o Organization and management of rollout.

o Details of service execution at Delivery Points (DP) of

o Error and escalation management.

BASF IS Page 14 of 301

1.2.1 How to interpret symbols

Critical information about show-stopping situations

Important information to avoid problems

 Single step to be carried out

 System reaction to a user input

1.2.2 How to read graphics

BASF IS Page 15 of 301

 Several UI-elements are shown within the screenshots. These UI-

 Reader-related actions in forms

o Actions on buttons are indicated by the phrase click.

o Actions on text boxes are indicated by the phrase insert.

o Actions on check boxes are indicated by the phrase check.

o Actions on menus, record tabs, combo-boxes, list-boxes,

o Actions on table manipulation buttons, e.g. open, close, first,

BASF IS Page 16 of 301

 Approximately 100,000 PCs will be replaced in 120 countries,

 The replacement procedure (mass rollout) will start in parallel in all

 Up to 5,000 software packages will be individually installed to the

Leading system for rollout information and coordination is BISTRO, see

1.3.1 GPS III Project Organization

 Project Manager: Udo Wagner

 Project Office: Anke Roden

 BISTRO: Christopher Zyzik

 Logistic Coordination: Ulrike Klamm

 Rollout Coordination: Ilker Özbek

 Regional Rollout Coordinators:

o EMEA: Andreas Zabanoff, Günter Keller, Uwe Will

o AP: Alvina Chai, Mayank Gupta, Danny Bhadran

o NA: Herchiel J. Devalcourt

o SA: Marcos A. Ferreira de Silva, Rodrigo Matiello

BASF IS Page 17 of 301

Region Region / Business Center