© 2009 Copyright by Siemens Switzerland Ltd The End-User must not remove any proprietary, copyrights, trade secret or warning legend from the Documentation when making copies thereof. Note THESE GUIDELINES ARE BEING PROVIDED SOLELY FOR INFORMATIONAL PURPOSES AND SIEMENS DOES NOT WARRANT OR REPRESENT THAT THEY WILL SATISFY THE SPECIFIC REQUIREMENTS OF ANY PROJECT.
About this document The service manual was developed to provide all necessary information when performing service on a MM8000. The target groups of this document are local Siemens service technicians for MM8000. Chapter 1 to 5 describes all activities for preventive- and corrective maintenance in detail. Chapter 6 provides an example for reporting the yearly maintenance activities. The goal is to visualize the service and to discuss the results with the customers.
1 Introduction .............................................................................................7 2 General Instruction .................................................................................9 3 3.1 3.1.1 3.1.2 3.1.3 3.1.3.1 3.1.3.2 3.1.3.3 3.1.4 3.1.4.1 3.1.5 3.1.5.1 3.1.5.2 3.1.6 3.1.6.1 3.2 3.2.1 3.2.1.1 System Maintenance Services.............................................................11 Preventive maintenance ..............................................................
Introduction 1 Introduction The service manual provides all relevant information needed to carry out maintenance work in a country. The different chapters describe different aspects including ingredients or even recipes to provide a checklist for MM8000 service. The goal is to support the service technicians in their efforts to provide consistent MM8000 service and to raise the quality of the service to a higher level.
General Instruction 2 General Instruction – Set a service date for maintenance work with the person responsible for the sys- tem – Discuss and remedy system-related problems and explain functions – Provide information about new functions and software options – Any works to be taken must be in accordance with the contract in force; some work may not be included in the service agreement and needs a separate invoice. – Before any service starts a back up plan must be agreed with the client and in place.
System Maintenance Services 3 System Maintenance Services 3.1 Preventive maintenance 3.1.
System Maintenance Services 3.1.2 Software update Check software status and possibly run maintenance updates In case an upgrade as described in Chapter 4 is installed, an update will not be necessary. Software Description – Compare the installed version to the latest maintenance versions of MM8000.
System Maintenance Services 3.1.3.3 Check communication interfaces with connected systems Connected systems can include: – Access control systems – Intrusion detection system – Fire detection systems, make an event on the MM8000 e.g.: – switch on/off day/night organization – switch on/off detector/group/zone – CCTV systems – ESPA / Email / SMS systems – Network components – common Remote Service Platform (cRSP) Remark: functional test of above mentioned systems are not a part of the MM8000 service.
System Maintenance Services 3.1.5 Data protection 3.1.5.1 Check and inspect the database backup and historical archive at regular intervals Software Description – Check whether automatic backups as per the cus- tomer’s backup procedures are actually made Make project database backup and historical archive of backups – Manually create an additional historical archive, copy of the history browser – Purge old backup versions. Ensure that the system only contains useable backups.
System Maintenance Services 3.2 Corrective maintenance 3.2.1 Data recovery 3.2.1.1 Correct error messages This chapter only applies when error messages have actually been issued.
Life Cycle Management 4 Life Cycle Management The implementation of upgrades to later versions with new functionalities etc. is covered by the scope of the service agreement. Such upgrades shall always be implemented in consultation with the customer. It is standard procedure for a new version of MM8000 to be released once every year. This new version can automatically be “spooled” on the management system.
Life Cycle Management 4.1.2 Supported upgrade paths MM8000 system software Upgrade paths Tab. 13 4.1.3 Description – Upgrading to the most recently released version is possible from every version of MM8000. There are no upgrade restrictions. Supported upgrade paths Upgrade exclusions MM8000 system software Description – Make sure that none of the sub-systems require an upgrade to the recom- mended MM8000 release – Upgrades of other installed components, e.g.
Upgrade procedure 5 Upgrade procedure Before you start, make sure that all the required files are on the MM8000 PC using a DVD or a connected HDD. You could prepare points 15 to 24 on another MM8000 PC with 3.20.02 (notebook with VMware) to limit inconvenience for the customer as much as possible. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Make a backup clone of the C: drive on F: using Ghost. Make a backup of the browsing history on D:\HistoricalArchiveBackup.
Upgrade procedure 25 26 27 28 29 30 31 32 If linked through NK822x. Add new firmware to the list. Select new firmware from the pull-down menu for each NK822x. Download all NK822xs with the new firmware. (e.g. C:\Program Files\DMS8000\NK822x – Firmware). Note that the Nk822x_3.20-02_200307_25.zip is for the NK8225. The 25 at the end is not the version, but the NK type. Download all NK822x with the new configuration. Download project. Check whether Locksystem.
Service report MM8000 6 Service report MM8000 Service Report MM8000 Installation number Notification number Site address Period Interval Date Service technician 1.
Service report MM8000 3.4 MM8000 TFT screen Brand / type: see below Screen no. Check for functional and mechanical faults Electrical sharpness Raster Brightness Screen settings optimized 3.5 MM8000 NK 82xx controller Type: Check for mechanical faults Check and test (in consultation with the customer) the offline status in MM8000 3.6 Scalance Switches Type Check for mechanical faults Start Web-Based Management (WBM) on switches 4.
Service report MM8000 Functional tests Test NK 82xx function (interactions) Shut down and restart fire alarm system Make I/O controls Check MM8000 events using above mentioned functional tests 7. User data Storage of user data Adjust access rights of users Update the user list 8.
Service report MM8000 12. Power supplies Check if UPS is provided for MM8000 Shared UPS supply with other systems Dedicated UPS supply only for MM8000 - Fault indication battery disconnect - Fault indication battery low - Fault indication charger failure disconnect - Mains failure indication - System runs on UPS supply when mains is disconnected Satisfactory (list faults under details) Yes No Corrected N/A 13. Technical details 14.
Diagnosis of MM8000 faults (flow chart) 7 Diagnosis of MM8000 faults (flow chart) In case of a problem of the MM8000 the customer/operator will call Siemens and ask for assistance or a service technician to solve the problem. During the call intake the Siemens operator creates a notification and dispatches the customer question to the helpdesk during working hours or standby technician outside working hours.
Diagnosis of MM8000 faults (flow chart) Problems with MM8000 Remote access available? No A Yes Customer is called by telephone to ask for remote access permission Is Ultra VCN application working? Customer is called by telephone Yes Yes Interpret customer problem description B No Can the regional cRSP hotline solve the problem? Is connection to other technics on site available and working? No Is the cRSP ping before starting the application succesful? No Yes Yes No C Is Remote Desktop
Diagnosis of MM8000 faults (flow chart) A Did it work before? Should it be working according to what has been sold? No Yes Yes When did it stop working? What has been changed? Is this the first time this problem is reported? Yes No Look in SAP what the previous solution was B Hand over to sales department No C Unidentified event present? No Yes Subsystems reachable? Yes Problems with access rights? No Problem with MM8000 server/client application? Problem with Operating system No N
Tables and Figures 8 Tables and Figures 8.1 Tables 8.2 Tab. 1 Tab. 2 Tab. 3 Tab. 4 Tab. 5 Tab. 6 Tab. 7 Tab. 8 Tab. 9 Tab. 10 Tab. 11 Tab. 12 Tab. 13 Tab. 14 Tab. 15 Component inspection ............................................................................11 Software Update .....................................................................................12 Software check........................................................................................12 System check..................
