ode. These parameters can vary depending on the data requirements; e.g. for open interfaces the data headings will be same irrespective of the equipment vendor or in other cases it can be vendor specific. Typical data can be related to information exchanged between two network elements interfaces, e.g. the number of links, size of transmission packets or pipes, IP addresses, protocols followed, naming Network Commissioning and Integration Common Alarm Inspection Door Open alarm Smoke alarm Fire Alarm HVAC failure alarm Power Outage alarm Battery low alarm Unit failure alarm Unit State Change alarm Transmission link failure alarm Figure A.6 Alarm list conventions, delays, limits, error rates, user data content type and volumes, etc. Figure A.7 shows an example of a parameter sheet designed by core network engineers, providing data that are used for the creation of an Iu interface integrating a radio network controller with a media gateway unit. A.3.6 Tools and Macros After finalisation the parameter sheets can be fed into the network integration tools or composed into macros, which are then run on to the network elements either manually or downloaded via the centralised monitoring systems. Some common software programs used for running macros or individual commands are Reflection, HyperTerminal, HIT (holistic integration tool), Unix or Linux shells, ProComm or even DOS (disk operating system) windows. Other programs can have graphical user interfaces where data can be just entered and fed into the equipment via direct or remote connections. Normal laptops or workstations are capable of running these tools and macros. The DOS window is also used to connect to the network element by a simple Telnet connection. A.3.7 Integration of Elements Once the elements are 'up and running', they are then connected by transmission links. The field engineers are then sent out to individual equipment sites for the first stage of integration. Thereafter it may be possible to run future upgrades remotely. It is mandatory for the fie