5 Actions of ARC personnel in emergency situations 1

5.1 In the event of failure of the ARC automation equipment complex (CCA ARC), the notification transmission system, the notification radio system, group subscriber sets, the employees serving on the ARC and the ARC employees are obliged to:

In the shortest possible time, take measures to restore the operability of the ARC automation complex (CCA ARC), the notification transmission system, the notification radio system in accordance with the step-by-step algorithm of actions of the ARC personnel to replace the failed ARC AWP and control equipment of the ARC (RSPI). If necessary, use the operational exchange fund of a personal computer and SPI equipment (RSPI);

If necessary, take measures to restore the operability of the SPI equipment and auxiliary equipment installed in the cross halls of the automatic telephone exchange;

Determine the objects that were under protection, failed notification transmission systems, radio notification transmission systems, organize work on their protection in accordance with the terms of the contract. If necessary, use the forces and means of the territorial ATS, working in the system of a single deployment in the serviced territory;

Inform the duty officer of the PCO (TsOU, GOSDNP), the operational duty officer of the Internal Affairs Directorate and act according to their instructions;

Upon receipt of a notification of a malfunction of the group subscriber set at the facility (directions of the notification transmission system), organize the elimination of the malfunction in cooperation with the territorial division of the Federal State Unitary Enterprise "Okhrana" of the Ministry of Internal Affairs of Russia or another service organization;

After elimination of malfunctions in the operation of the notification transmission system, the notification transmission radio system and group subscriber sets, determine and work out changes in the security status of objects.

5.2 When the power supply to the ARC is disconnected, the employees serving on the ARC and the ARC employees are obliged to:

Switch on (in the absence of an automatic transfer) the power supply of the ARC from a standby (autonomous) source (second independent input, diesel or petrol generator, batteries);

Find out the cause of the accident from the operator on duty, the measures taken and the timing of elimination;

Report a power outage at the ARC to the ARC on duty (TsOU, GOSDNP), the operational officer on duty of the territorial ATS and act according to their instructions;

Inform GZ SP VOP about the power supply failure of the central heating station;

Ensure the maximum possible protection of objects, apartments and MHIG in accordance with the terms of the contract. If necessary, use the forces and means of the territorial ATS, working in the system of a single deployment in the served territory;

If the power supply of the building (room) is cut off for a long time (weeks, months), take measures to transfer the ARC to another building (room).

5.3 In case of accidents in telephone communications between the PBX and the ARC, the employees serving on the ARC and employees of the ARC are obliged to:

Report a malfunction connecting lines to employees of the telecom operator, find out the cause of the accident, the measures taken and the time frame for elimination. Organize measures to switch to backup communication lines;

Report on the failure of telephone communications and the measures taken to the CCO on duty (TsOU, GOSDNP), the ATS operative on duty and act according to their instructions;

Inform the GZ SP VOP about the failure of the connecting lines between the automatic telephone exchange and the ARC;

Ensure the maximum possible protection of objects, apartments and MHIG in accordance with the terms of the contract. If necessary, use the forces and means of the territorial ATS, working in the system of a single deployment in the served territory.

5.4 In the event of massive power outages at facilities and ATS accidents, employees serving on the ARC and ARC employees are obliged to:

Find out the reason from the power grid operator or telecom operator, the measures taken and the deadline for elimination;

Report communications failures and the measures taken to the CCO on duty (TsOU, GOSDNP), the ATS operative on duty and act on their instructions;

Report to the GZ SP VOP the area of ​​the settlement where there were accidents of power grids or subscriber telephone communications;

Provide the maximum possible protection of objects in accordance with the terms of the contract. If necessary, use the forces and means of the territorial ATS, working in the system of a single deployment in the served territory.

_________________________________________
1 As amended by the Order of the Ministry of Internal Affairs of Russia dated June 16, 2011 No. 676 "On approval of the Instruction for organizing the work of centralized security points of private security units"

Complex software tools automation of the activities of the operational personnel of the centralized security posts (KSA PTSO "Aegida") is designed to automate the activities of the operational personnel of the central security center - duty operators and officers by executing control commands and transmitting telegrams of telesignalization, as well as information support of personnel actions when processing service and alarm messages.

• Connection and hand-held terminal devices of notification transmission systems "Phobos", "Phobos-A", "Phobos-TR", "Phobos-3", "Neva-10M", "Struna-3M", "Vista-501", UO- 4C
• Protection, management and monitoring of facilities using channels cellular communication GSM (SMS messages)
• Automated monitoring of the state of guarded objects, taking into account the security mode (entry time, security schedule by days of the week, holidays, long-term security) and the type of loop (security, fire, alarm)
• Automatic control of the execution of operator commands
• Event logging
• Working as a duty operator and duty officer
• Automatic transmission of data on the alarmed object to the pager of the arrest group
• Information and network compatibility with KSA PCO R&D Center "Protection"
• Automatic transmission of alarming information to the automated workplace of the DPCO R&D Center "Protection"
• Workplace networking
• "Hot" reservation of information and operational bases data

The complex provides:

• work with SPI "Phobos", "Phobos TR", "Phobos-3", "Phobos-A", "Neva-10M", "Atlas-2M", "Struna-3M"
• informational and functional compatibility with the KSA PCO Research Center "Protection" of the GUVO of the Ministry of Internal Affairs of Russia
• convenient user interface
• work in graphical mode
• visibility of information presentation
• optimization of operator actions
• independence from the structure of the object and the type of used SPI *
• connection of combined security systems *
• support for scripting devices, zones and partitions *
• hot software backup *
• static and dynamic data flow control *

*Note. When working with a DB of the IB DataBase 5.5 format

AWP DPU

1. Added "bookmark" filters
2. Changed the color display of the details of an object with the "special" status
3. Added settings for displaying the message "Unauthorized arming / disarming", "Skipping test signal".
4. Added "Alarm messages" protocol filter
5. Added support for the board LPS SPI "Altair"
6. Added the ability to display the levels of received signals from LARS transmitters
7. Fixed a bug when working with UO-4S on switchable workplaces
8. Fixed a bug when changing encryption keys for BR and SPI "Atlas-20"
9. Introduced a watchdog timer to prevent freezing of processors in the Atlas-20 SPI rack
10. For SPI with one-way exchange, the function of canceling the alarm situation is returned by pressing the F8 key. Added the function of restoring the previous state by the combination of keys "Alt +"
11. Fixed error with displaying information when working with "String-3M"
12. Changed the polling algorithm of the repeater in "Phobos" to increase the speed of execution of TC commands
13. Changed fields for entering encryption keys for SPI "Atlas-20" in the "Driver Server"

AWP ABD

1. Added "Password" field for subscribers, with data output to AWP DPU
2. The mode of import / export of the "Orion" UO configuration from / to Uprog has been introduced
3. Changed mode of operation with code pages for MAT transmitters. The code page for transmitters is used to create the structure of the transmitter.
4. Added the ability to create a LARS code page according to the transmitter structure
5. Added the ability to convert from the database of JSC "Argus-Spectrum"
6. Fixed bug with displaying search window
7. Added a change in the indication of keys of devices SPI "Atlas-20", programmed in the devices
8. Added the ability to change the type of device for the SPI "Atlas-20"
9. Added the status of the AL "Control of the order" for "Prima-3A"
10. Added search by range of subscriber numbers
11. Added setting for displaying address in Excel reports (in one or more columns)
12. Added the ability to merge databases "Aegis"
13. Changed the interface for entering the security schedule for zones
14. Added reports on SPI "Altair"

AWP WPC

1. Added the ability to redistribute information from guarded objects to different AWPs

AWP ABD

• The field "Key duplicates" has been added to the output form of the "Search" command
• The mode of editing the field "Date of termination of the contract" has been introduced
• Introduced a mode of automatic notification of the terms of termination of contracts
• The security mode "Saving the line" has been entered

AWP DPU

• Added the ability to work with KTsN "Altair"
• Added the ability to work with the S2000-IT AL
• Changed the reinitialization algorithm to reduce the restart time

AWP ABD

• Added object category - normal / special
• Added search by object category
• Added the ability to quickly search for free subscriber numbers
• Added RSPI Trikdis
• Added a service for automatic logging of work with the database
• Added the ability to transfer UT between the lines of the QPC
• Added hints to line numbers "Atlas-20" like Phobos "local / end-to-end"
• Added comments to address line"Atlas-20"
• KTsN "Altair". Added the ability to transfer LPP, LPZ, LPF between RTR slots
• Added selection of subscriber numbers of synonyms in the search window
• Added the ability to copy and paste text into the input fields of the AWS ADB using the Windows clipboard
• Added plugin for printing envelopes
• Fixed a bug with the "Phone" field in the "Services" service
• Fixed bug when converting database

AWP DPU

• Added the ability to program BB and UOO Jupiter
• Fixed function "Outgoing test UO-4S" through UOP
• Output of the "Address" field from BB Jupiter
• Added Jupiter to the protocol filter by faults
• Fixed filter by SPI (KPTSO)
• Added command "Take after exit" (Jupiter-Atlas, Jupiter-Center)
• Fixed bug with SMS notification
• Optimized SMS notification format for multi-zone objects
• Fixed a bug when working with zone plans
• Added command to re-capture UT (Jupiter)

AWP ABD

• for UO-4S added the ability to disable SMS "Receipt"
• the order of maintaining the list of TM keys (access codes) for automated UO has been changed. The list of keys has been moved to the structure of the UO; for each key, you can specify a list of AL and a subscriber number. The subscriber number has ceased to be identical to the key number, which makes it possible to describe large objects where the number of subscribers is greater than the number of keys in the UO
• for the keys of the TM devices "Atlas-20", UO-1A and UO-3K added the ability to select the type of user from the list: "Subscriber", "Electrician", "Detention group". When the user "Electrician" or "Detention Group" is selected, the disarming in the automated workplace of the DPU will be "alarming"
• introduced different indications for zones connected and not connected with AL
• fixed errors when working with ADB from the keyboard (transitions between fields, opening combo boxes)
• added the ability to copy LARS code pages
• added the ability to assign and reassign events to RSPI LARS transmitters
• to automate the removal / removal of a section
• added the ability to minimize the search window
• fixed a bug when working with the reference book of sites and the list of equipment.

AWP DPU

• reduced CPU load by optimizing algorithms
• the color indication of the status of the zones has been changed: the cell simultaneously displays
  current, previous state and state of SPI
• the programming procedure for the Atlas-20 SPI has been simplified. To change the status of a loop or x / o, it is enough to send the command of the same name to the control panel without reprogramming the device. When adding a new control panel, there is no need to program the upper-level devices
• • 130-zone alarm
  • 137-alarm hack
  • 143-module failure
  • 144-opening the detector
  • 145-opening the module
  • 320-siren malfunction
• modified test signal processing algorithm for "UO-4S isp.02"
• fixed a bug when working with the UOP T-34 to notify subscribers
• the algorithm for processing the level of the received signal of the GSM-modem has been changed. When the signal level decreases, the color of the level scale changes; when a critical value is reached, a warning is displayed in the DPU protocol.

AWP WPC

• added field "Indicator lamp installation location"
• fixed a bug when displaying the security schedule in the list mode

AWP Reports

• changed program interface
• if there are no paths to the copies of the protocols, a reminder is displayed about the need to create them

Event server

• when working without a network card, the possibility of activating the gateway is automatically blocked
• to ensure greater reliability in the parameters of the transport layer, it is now possible to set a broadcast mask

AWP ABD

• !!! parameter "protocol type" RTR SPI "Phobos-3" moved from COM to RTR
• added the ability to connect external custom loadable modules (plugin)
• changed the type of AL for the PPK SPI "Atlas-20" by default: 1 AL "with delay", the rest "perimeter"
• added the ability to select tactics for working with the "Signal-20" control panel via "UO-Orion" (manual / automatic)
• for "UO-4S" added the ability to disable SMS "Receipt"
• the order of maintaining the list of TM keys (access codes) for automated UO has been changed. The list of keys has been moved to the structure of the UO; for each key, you can specify a list of AL and a subscriber number. The subscriber number has ceased to be identical to the key number, which makes it possible to describe large objects where the number of subscribers is greater than the number of keys in the UO.
• added the ability to change the access level for "Atlas-20" devices. With an access level other than "Khozorgan", disarming in the automated workplace of the DPU will be "alarming"
• fixed a bug when working with canceled objects (apartments) with AN 00000
• fixed a bug when working with the reference book of areas and the list of equipment
• fixed an error (changing the name of the node "objects without a contract") when adding a new contract

AWP DPU

• significantly reduced CPU load by optimizing algorithms
• the color indication of the state of the zones has been changed: the cell simultaneously displays the current, previous states and the state of the SPI
• the programming procedure for the Atlas-20 SPI has been simplified. To change the status of a loop or x / o, it is enough to send the command of the same name to the control panel without reprogramming the device. When adding a new control panel, there is no need to program the upper-level devices.
• added new codes for working with Vista panels:
  • 130-zone alarm
  • 137-alarm hack
  • 143-module failure
  • 144-opening the detector
  • 145-opening the module
  • 320-siren malfunction
  • 350-no connection with the monitoring station
  • 351-telephone line malfunction
• fixed error when processing the event "Pass test signal" for "S2000-IT"
• fixed error when displaying information "not taking" from "UO-2A"

AWP WPC

• fixed a bug when clicking on the security schedule
• added the ability to print a report when changing duty

AWP Reports

• changed program interface
• if there are no paths to the copies of the protocols, a reminder is displayed about the need to create them
• it is possible to work without an event server
• it is possible to work directly with AWP protocols
• the ability to view the WPCO protocols from an assembly version of at least 2-2-2-358

1. SPI "Altair" has been added to AWS ABD
2. The system codifier is supplemented with events for dumping the encryption keys of the SPI "Atlas-20"
3. Fixed database conversion error (CopyServer.exe, Install.exe)

AWP DPU

1. Added the ability to select the type of interface for SPI "Phobos2:" USI-Phobos ", Modem," S2000-PI "
2. PBX number has been added to the parameters of RTR "Phobos" repeaters
3. Changed interface for numbering loops when connecting "UO-Orion". Now the numbering of absolute AL numbers is automatic
4. Added search mode by lists
5. Added to the printing of object cards:
   • security schedule for facility zones
   • subscriber addresses
   • printing of all plans of the object
6. The removal of the hardware section of the FSA has been improved: now the zones of the hardware section from the object are not deleted, but only excluded from the section and can be used to associate with new UOs
7. Added export of passwords for a month in Microsoft Word editor
8. Added the ability to copy and paste data via the Windows clipboard:
   • zone (or several zones)
   • subscriber (or several subscribers)
   • several subscribers and zones of the object
   • address (or multiple addresses)
   • phone (or several phones)
9. Added export of reference books and codifiers to Microsoft Word:
   • Dictionaries-> References-> Export
   • Dictionaries-> Codifiers-> Export
10. Added the ability to selectively print in object cards
11. Added ability to set default phone mask
12. Added SPI system "Vista-101"
13. Added the ability to change the type of the panel "Vista-501" to the type SPI "Vista-101"
14. Added information line to exclude the input of duplicate subscriber numbers of devices
15. Added the ability to enter additional equipment (not related to the FSA structure) to the object: Object menu-> Equipment. Added data export to Microsoft Excel
16. Added location and capacity report for "Atlas-20", "Struna-3M" and "UO-4S" JVS
17. Added devices "Bastion-1", "Bastion-2", "UO-3K" and "UO-1AI"
18. Added input of code pages for transmitters and panels NX RSPI LARS: Dictionaries-> Code pages LARS
19. Added search for objects by the name of the electrician and by the name of the inspector
20. Added the "address" parameter for the Jupiter BB and the Kometa GC
21. Added search by the address of the FSA device
22. Added modem initialization string in COM-port parameters when connecting Phobos-3 repeaters with "modem" interface type
23. Added the "Subscriber notification" parameter for the "UPO T-34" device
24. Added UPO T-34 modem for working with SPI "Vista" and ISO "Orion"
25. Added work with the rack "Atlas-20"
26. Added error statistics with logging in the ArmABD_error.log file
27. The main menu of the AWP ABD program has been supplemented and updated:
    • the menu is made with a more logical division by functionality
    • added help call
    • added link to the site www.bolid.ru
28. For convenience, the settings for printing cards have been moved to the window itself, where reports on object cards are generated
29. The object page is made in the form of 2 tabs:
    • Description of the object
    • Object plan
30. Added a report on the number of busy and free directions of repeaters, as well as a summary of the number of connected objects and apartments
31. Added a call to the "Service Areas" window in the parameters of electricians and inspectors
32. Added the ability to change the type of repeater "Phobos" to "Phobos-A" (and vice versa)
33. Added selective dislocation of numbers "Vista" and "UO-4C": Reports-> Dislocation
34. The use of the "Alder" board has been excluded. Instead of not? the UPO T-34 modem is now used
35. At the FSA access level, additional options have been added that allow prohibiting the deletion of computers, COM ports, Phobos repeaters, etc. in the FSA structure.
36. Added the ability to quickly switch from AL to the security zone back and forth (if there is a connection between them) by Ctrl + Enter or Ctrl + left mouse button
37. Upon termination of contracts, the date of termination is requested
38. Added security system "Cerberus S62" (like "Vista-101")
39. Added security system "Altair"
40. The repeater "Phobos3-1200" is excluded 41
41. The device "UO-2K" is excluded
42. Added the "Processor version" parameter for the "Phobos-3M" repeater
43. Added sorting of contracts by contract number in the search window
44. Added security system "RS-202"
45. Fixed reading of Touch-memory keys. The key is read and displayed immediately, but is written to the database only after clicking the "Save" button
46. When a section of the Vista panel is added, it is assigned the Vista panel number by default. Also added a zero section "Vista"
47. For "Signal-VK4", "UO-3K" there is a built-in prompt on linking a zone with a loop through the hardware section
48. Added "Automatic removal" mode for KTL zones (when removing the panel)
49. Added "Password" parameter for BR "Atlas-20"? to reset encryption keys
50. Selections of objects during the search were made with the indication of the crossed phones
51. Two LARS code pages are included in the "Aegis-2" distribution kit (if installed "from scratch")
52. Improved interface for entering phone numbers and addresses in the structure of the OO

Bugs fixed:

1. Streets, subscriber statuses, zone types were recorded in the database, but the values ​​were not always visually updated
2. "Abstract error"
3. After checking the database for errors in the reference books, a service area with number -1 appeared
4. After updating the data of the FSA system structure, all computers marked with a red cross as missing from the network were no longer marked
5. The number of ABD AWPs connected to the database was displayed incorrectly
6. When adding the Phobos-3M / 1200 repeater, the interface type of the COM port changed incorrectly
7. Extra parameters remained visible at the DBA access levels if a transition was made from the TOE access level to the DBA access level
8. When the main window of AWS ADB was expanded, it closed the taskbar
9. If an error occurred during the database check in one of the checks, then the entire database check was stopped.
10. The buttons of the function keys in the main window of the AWS ABD stuck when pressed, for example, when trying to save an object without a name
11. Periodic freeze when editing graphical plans of an object due to the error "Stack overlow"
12. Fixed a bug when exporting contracts for apartments to Excel

1. Optimized exchange of AWP DPU with repeaters "Phobos", "Phobos-A", "Phobos-TR", "Phobos-3"
2. Added the ability to work with the BR "Atlas-20" (release) and the rack "Atlas-20 (beta)
3. Added the ability to record the protocol of exchange with repeaters "Phobos", "Phobos-A", "Phobos-TR", "Phobos-3", "Atlas-20" and "Jupiter" with AWP into a text file
4. In case of unsuccessful sending of an SMS message to the subscriber's cell phone AWP DPU makes three attempts to send the message. If SMS has not been sent, a message about this is displayed in the DPU protocol
5. Added arming / disarming mode "UO-A" without subscriber number
6. Optimized operation of "UO-4C" with a GSM modem when using different operators cellular communication
7. Increased reliability of network work of workplaces, also when switching workplaces
8. Added indicator of received signal strength of GSM-modem
9. Added indication of the reason for the impossibility of copying the backup database to workstations
10. To reduce messages in the protocol, service messages from Vista panels are associated with the zone with the lowest number
11. When the AWP DPU is opened, the operator selection cursor appears on the operator who closed the AWP DPU
12. Added progress bar for copying database
13. Added confirmation request to disconnect AN
14. Added function of dynamic change of encryption keys for BR "Atlas-20"
15. Added support for working with "UO-3K" Added support for working with the T-34 modem
16. Added the ability to block the subscriber key
17. Added the ability to manually copy protocol backups

Bugs fixed:

1. An error occurred during the operation of the driver server with "Phobos-TR", the repeater went off in an accident
2. Fixed a bug with copying the backup database to workstations
3. Fixed a bug when working with graphical plans of objects and apartments
4. Fixed leak bug random access memory in AWP DPU
5. Fixed a bug when working with the RSPI "Struna" (the message "switching to backup power" did not go through)
6. Fixed bugs during operation of Phobos-3M repeaters in PPL mode

1. Fixed a bug related to incorrect calculation of the Actual protection time
2. In the filter window, subscriber numbers of apartments and objects are separated by color (green and blue, respectively)

AWP DPU

• added report on CCC inspections
• added filter "Not removed by the deadline"
• added comments to UT "Comet"
• added a mode for scrolling the protocol to the left? to the right
• fixed restart of the task in the DPU in the large card
• added an automatic request for the status after resetting the emergency for the "Atlas-20"
• added zone table filter for SPI "Jupiter"

• fixed the mode of folding bookmarks

• added the ability to select the type of interface when connecting SPI Phobos: "USI-Phobos", Modem, "S2000-PI"
• PBX number has been added to the parameters of SPI "Phobos" repeaters
• added the mode of automatic numbering of absolute numbers of the "UO-Orion" AL when connected to the SPI "Phobos-3M"
• added the ability to search for information in a case-insensitive manner
• the report "Print cards" has been improved. Added a schedule for the protection of zones, addresses of subscribers, printing of all plans of the object
• the mode of deleting / adding the hardware partition of the FSA has been improved. Now the zones of the hardware partition are not deleted, but are excluded from the partition, remaining in the object. When adding a multi-loop control panel (hardware partition), free zones are automatically associated with its loops
• added export of passwords for a month to Microsoft Word editor

Complex composition

AWP PCO- automated workplace operator on duty and / or officer

AWP ABD- automated workstation for creating and maintaining a database

Development environment- "Delphi 5.0"

Operating environment- operating system "Windows NT / 2000"

Database formats- FoxPro 2.6 and IB DataBase 5.5.

The recommendations reflect the main types of work and labor costs for routine maintenance of wired SPI and RSPI by the engineering and technical staff of the ARC of the private security units, as well as the terminal equipment that are part of them.

M Ministry of Internal Affairs of the Russian Federation

Main Directorate of Private Security

WITH main works
according to the regulatory
maintenance
wire and radio channel SPI,
recommended for use
in non-departmental security units

R 78.36.025-2012

Moscow 2012

The recommendations were developed by the staff of the Federal State Institution of Scientific Research Center "Protection" of the Ministry of Internal Affairs of Russia A.E. Pomazuev, I.F. Balueva, I.A. Zakharov, S.V. Belan, E.A. Nurmukhamedov, D.A. Nikolaev, A.R. Familnov, K.V. Kolesov, A.I. Krotov, under the leadership of A.G. Zaitsev.

LIST OF ABBREVIATIONS

AWP - automated workstation

ASTSN - automated centralized surveillance system

AFT - antenna-feeder path

BVR - remote radio channel unit

BM - basic module

BPO - wired object block

BPU - universal console unit

BR - radio channel unit

BRO - radio channel object unit

BRR - radio channel relay unit

DPU - control panel attendant

Engineer - engineering and technical worker

UPS - source uninterruptible power supply

KPTSO - switchboard of the centralized protection point

KSA - a set of automation tools

VSWR - standing wave ratio

KSPI - notification transmission system controller

KTsN - centralized surveillance complex

LAN - local area network

MHIG - places of storage of property of citizens

ОМ - object module

PC - software package

Software - software

EPROM - read-only programmable memory

PPKO - security control device

PPKOP - security and fire control device

PS - message transmitter

PU - control panel

PUU - universal control panel

CMS - centralized surveillance console

ARC - centralized security point

PC - personal electronic computer

RPD - radio transmitter

RPM - radio receiver

RPMPD - transceiver

RPU - radio receiving device

PC - radio watchman

RSPI - radio channel notification transmission system

RT - repeater

RE - operation manual

SPI - notification transmission system

TA - telephone

TO - maintenance

TSO - technical means of protection

UO - terminal device

UOO - terminal object device

UOOR - terminal object relaying device

UOS - communication device

UT - broadcast device

UT-Ts - central broadcasting device

2. GENERAL PROVISIONS

In accordance with the legislation of the Russian Federation, subdivisions of non-departmental security of territorial bodies of internal affairs in order to implement the functions of centralized protection on a contractual basis of the property of citizens and organizations carry out technical routine maintenance of wired, radio channel SPI and channel-forming equipment for them, computer equipment, registration of negotiations, video surveillance systems , control and management of access and other auxiliary equipment installed in the premises of telecom operators and ARC.

These recommendations reflect the main types of work and labor costs for routine maintenance of wire SPI and RSPI by the engineering and technical staff of the ARC of the private security units, as well as the terminal equipment that are part of them.

The typical composition of wired and radio channel SPI and equipment subject to mandatory maintenance includes repeaters and group concentrators for them, personal computers, auxiliary console equipment, network equipment, modems (converters), software (AWP).

3. MAINTENANCE AND REGULATORY WORK

The technical maintenance of the TSO is carried out on a planned basis in accordance with the requirements of the regulatory legal acts of the Ministry of Internal Affairs of Russia and the operational documentation of the manufacturing plants.

When carrying out maintenance work on the SPI and RSPI, one should observe the "PUE-98. Electrical Installation Rules ”and be guided by the“ Safety Instructions ”,“ Guidelines for the Maintenance of Security and Fire Alarm Systems ”,“ Standard Rules for the Maintenance of Fire Automation Installations VSN 25-09.68.85 ”.

Scheduled maintenance of devices SPI, RSPI, auxiliary equipment installed on the ARC and in the premises telephone exchanges, is carried out with the following frequency:

in the amount of regulation No. 1 - 4 times a month;

within the scope of regulation No. 2 - once every 3 months.

In addition, in order to identify the causes and eliminate false alarms, as well as in the event of failures in the operation of the SPI and RSPI equipment, when their cause cannot be eliminated by carrying out regulations No. 1 and No. 2, an unscheduled maintenance is carried out.

The scope of the scheduled maintenance work performed by the TSO is controlled by the ITR of the PCO, is recorded in the logbook of the PCO electrician, followed by a mark by the control panel on duty in the checklist (log) of the ARM of the ARC.

The total scope of maintenance work for all wire and radio channel SPIs is shown in Table No. Appendix No. contains their content and technical requirements for routine maintenance performed. Schemes and procedure for carrying out measurements of electrical parameters are given in Appendix No.

Table 1

When carrying out work related to the disconnection of the main and backup power supply of an automated workplace not connected to the LAN, before starting maintenance, it is mandatory to copy (archive) (if possible to removable media) the database and the state of all terminal devices connected to the repeaters.

If necessary, a printout of the state of protected objects is made before and after maintenance work and their comparison.

4. PERSONNEL REQUIREMENTS

For maintenance work and routine maintenance work on wire and radio channel SPIs, PCO electricians who have undergone special training and have a qualification grade of at least 4 are allowed.

Maintenance and routine maintenance work on the AWS of the KSA and the LAN of the CCA is carried out by engineers who have undergone special training and have the appropriate qualifications.

5. MEASURING EQUIPMENT, TOOLS AND CONSUMABLES

Metrological support is carried out in accordance with the legislation and other regulatory legal acts of the Russian Federation and the Ministry of Internal Affairs of Russia.

Measuring instruments used to observe the parameters of the SPI and RSPI, without evaluating their values ​​with standardized accuracy, may be referred to as indicator measuring instruments and not subject to verification.

An approximate list and norms for the position of measuring instruments and bench equipment for one ARC are given in the table.

table 2

"_____" _____________________ 20______

Notes:

1 The schedule is drawn up taking into account the labor costs for each product and the work of electricians on weekends, holidays, the second and third shifts.

PLAN - SCHEDULE
compliance with the regulations for the maintenance of technical security equipment installed in the premises of telephone exchanges, as of __________ 20___

Electrician ______________________________

Compiled by ______________________________________________________________

(position, initials, surname, signature)

"___" ________ 20___

Notes:

1 The schedule is drawn up taking into account the labor costs for each product and the work of electricians on weekends, holidays, the second and third shifts.

2 In the absence of an electrician (illness, vacation, etc.), to whom the equipment is assigned, the name of the electrician who performed the work is indicated in the "note" column.

MAGAZINE
accounting and control of maintenance of software for computer systems, video and sound recording

Started on "____" _____________ 20___

Completed on "____" _____________ 20___

Accounting for work performed

MAGAZINE
electrician to ensure the functioning of centralized surveillance systems

___________________________

Started on "____" _____________ 20___

Completed on "____" ____________ 20___

Accounting for work performed

Note- The column "Type of work" indicates the number of regulations, another reason for the work (application of the customer or service organization, failure to take the object, apartment (MHIG) under protection, other reasons).

MAGAZINE
accounting of measuring instruments

Notes:

1 In the column “ Technical condition»Indicate: the date of the last verification, repair, the need to write off measuring instruments.

2 The journal is kept by engineers and technicians who supervise measuring instruments.

Development and technical support Integrated security software is a laborious and costly process. One of the ways to reduce development time and cost, increase functionality and increasing life cycle Software is the use of technology that simplifies and automates the creation and implementation of information model in the program code.

A.N. Morozov
General Director of Communication Systems Design Bureau, ASB Group of Companies

The complex of automation tools for centralized security points (KSA ARC) "Radioset" has the following main features:

• architecture based on a distributed self-synchronizing environment of operation;
• functional completeness, including the functions of security and fire alarm, video surveillance and video detection, access control and management, voice communication and notification;
• universal control panel;
• universal and adaptive operator interface, consisting of the "List", "Table" and "Plan" panels;
• extended format of subscriber numbers;
• no need for a dedicated server (peer-to-peer environment);
• the ability to change the configuration of hardware without the need to restart workstations;
• possibility of "hot" backup of AWP and databases (DB);
• the ability to flexibly configure the service areas of duty operators.

The origins of the KSA PCO "Radioset"

KSA PCO "Radioset" was created by a team of programmers who have been specializing in software development for security systems for two decades. This team has developed several generations of AWPs, which have found wide application in security units. Among these developments, the most famous are the KSA PCO NRCs "Protection" and "Aegida", which have proven themselves in operation as reliable and convenient software. In this sense, KSA ARC "Radioset" has absorbed all the previous professional experience. It seems that this experience is important and valuable not only directly for developers, but also for end users, because in operation it is very important to understand not only "how it was done", but also "why it is done this way". In this sense, when talking about the KSA, the ARC "Radioset" is appropriate to touch on brief history creation of its predecessors, which will be done below.

One of Murphy's implacable laws says: "Once a project is finally adopted, it becomes obsolete in terms of its concepts." Therefore, starting the KSA ARC "Radioset", the developers first of all revised the concepts on which the previous projects were based. The questions of economics, operation, architecture of the software and hardware platform, information model, development technology and life cycle of applied software were analyzed. The cost of the hardware and software complex for the digital signal processing center consists of the cost of the following components:

• hardware platform (computers and equipment of a local area network (LAN);
• software platforms s (operating system and database management system (DBMS);
• exploitation.

The cost of the hardware and software platforms of the KSA ARC is mainly influenced by the LAN architecture, which can be peer-to-peer or with a dedicated server. Theoretically, all other things being equal, a LAN with a dedicated server is more reliable, but much more expensive and more difficult to operate. After analyzing all the pros and cons, the hardware and software platform of the following configuration was selected for the CCA ARC "Radioset":

• peer-to-peer LAN;
• operating system Windows XP (in the short term - Windows 7);
• free distribution system for database management Firebird.

The reliability of the peer-to-peer platform KSA ARC "Radioset" is ensured by a special architecture of application software based on a distributed self-synchronizing operating environment, and is described below. The life cycle of application software of previous developments is schematically as follows. First of all, a study of the subject area (representing in this case a security system) is carried out and its information model is built. This is a rather lengthy, laborious and informal process. Errors made at this stage subsequently lead, at best, to the need for endless "patching of holes" in the form of haphazard additions to the interface that implement previously unaccounted for information and functional needs. After the development of the information model, the paths of the developers, figuratively speaking, diverge. Each of them begins to program their part of the complex. At the same time, it is essential that the previously developed information model is embodied in the program code by each programmer and in each of the AWPs. This leads to an excessively large complexity of software development and maintenance. In addition, a change in the information model in the process or a change in the domain or the concept of developers leads to the need to rewrite significant pieces of code. The latter is especially important, since the improvement of the software in the form of the release of new versions makes up the greater part of its life cycle (for example, the development of the first version of the KSA PTSO R&D Center "Okhrana" took about one year, and the release of subsequent modifications - five years). The software, as already noted, was used in previous projects.The release of new versions was complicated by the fact that in reality they had not one, but three databases (information, operational and event). Therefore, the use of technology that simplifies and to some extent automates the process of "materialization" of the information model in the program code is an obvious and essential resource for accelerating the development, increasing the functionality and increasing the software life cycle. configurable with extended language Markup (XML).

Its difference from those used earlier is that after the development of the information model, it is not transmitted in some descriptive form directly to programmers for subsequent implementation in the program code, but is used as input data for the system (i.e., intended to ensure the functioning of the complex as a whole. , but not the execution of an applied task) software components of the complex. In KSA ARC "Radioset" such a system component is called a distributed core (hereinafter referred to as a core) or a distributed self-synchronizing runtime environment. In fact, the core is a kind of "constructor" from which the interface and functionality of any of the AWPs that are part of the complex are "assembled". When new requirements for the interface and functionality appear, the core can be modified to new capabilities that become available for use in the AWS. When using this technology, the development of an automated workstation is simply an indication of what kernel resources it needs. All information describing the information model of the complex (structure and composition of the database, exchange protocols, interface elements) and necessary for its operation is contained in a textual configuration XML file. A distributed core and a configuration XML file are included in the software package for each workstation. The kernel works like this:

• when starting any type of workstation, it reads the description of the system from the configuration file, checks for the presence of a database on the local computer and creates a database in its absence in accordance with the description;
• checks the presence of a database on other computers on the LAN and, if available, automatically synchronizes the database;
• provides network interaction between workstations (exchange of data and events);
• creates and provides functionality and synchronization of content in the elements of the AWP interface (plan, table, list, card, etc.). The technology used made it possible to easily solve the problem of combining the functions of a database administrator and an engineer in one program. Previously, the complex was forced to include two AWPs - AWP ABD and AWP "Engineer", which largely duplicated the capabilities of each other. In fact, the "Engineer" workstation was a truncated ADB workstation with the functions of logging events. Now the "Protocol" window was simply added to the structure of the AWS DBA interface, the functionality of which is supported by the kernel and corresponds to the functionality of the AWP DPU;
• creates and synchronizes the states of the AWS information model objects in accordance with their description in config file and the presence in the database;
• creates and maintains virtual communication channels, distributes loads between workstations, provides hot redundancy for workstations and databases.

Composition of KSA ARC "Radioset"

KSA ARC "Radioset" integrates work with the following subsystems:

• security and fire alarm (FSA);
• access control and management;
• video surveillance and video detection;
• voice communication and notification. The FSA subsystem supports work with the following SPI and integrated security complexes (ICB):
• RSPI "Radioset":
• RSPI "Struna-3M";
• RSPI "Struna-M";
• IKB "Pakhra";
• SPI "Phobos", "Phobos-3";
• SPI "Altair".

The structure of KSA ARC "Radioset" includes the AWP of the control panel on duty (AWP DPU) and AWP of the database administrator (AWP ADB). The main screen of the AWP DPU is shown in the figure. Practice shows that the requirements for the composition of information on the screen of the AWP DPU are very contradictory. On the one hand, the operator needs detailed information about a specific protected object, on the other hand, he needs information about the current operational situation in his service area (responsibility), i.e. list of all alarming situations. In AWP DPU, this contradiction is resolved by the presence of two panels - alarm panels (10) and data panels (6, 7, 8).

The alarm panel displays a list of subscriber numbers whose zones are in alarm state. The data panel displays:

• state table (6);
• object panel (7);
• graphic plan (8). The listed panels exhaust all the information needs of the duty operators known to the author. The "Plan" panel is used to display information from a graphical database. A distinctive feature of the "Plan" panel is the absence of a rigid connection with the subscriber number, which was in previous designs. This makes it possible to display on one plan as many objects as are necessary for the operator's work.

The control panel in the left part contains a field for entering a subscriber number, and in the right part, the commands available for it. I would like to draw your attention to the fact that the panel contains not only commands that are usual for fire alarm systems, but also commands for video surveillance zones (3), access points (4) and voice communication points (5). At the bottom of the screen is the "Protocol" panel (9).

Summing up the description of the KSA of the ARC "Radioset", we note that the solutions and technologies implemented in it provide:

• functional completeness (FSA, access control and management, video surveillance and video detection, voice communication and notification);
• the minimum cost of the software and hardware platform (peer-to-peer LAN and free DBMS);
• high reliability of work due to "hot" backup of databases and operator workstations;
• the ability to quickly modify the software, the composition and structure of the database and the development of new applications.

Murphy's laws are unforgiving. Once a project is finally adopted, it becomes obsolete in terms of its concepts. However, there are exceptions to every law. We have tried to do our best to make KSA ARC "Radioset" such an exception.