ce_Category Egress_Service_Category EndPoint_Type AAL2_Path_ID TPI_Interface_ID TPI_VPI TPI_VCI Ownership LOCAL LOCAL Loss_Ratio Mux_Delay Figure A.7 Example of a core network parameter sheet Network Commissioning and Integration Initial Process Documentation Preparation Result Board room Expectations Testing Documentation Planning Regular (weekly) Laboratory Reporting Testing Report of IOT Reporting Verification Figure A.8 Different stages of IOT In such cases the scope of technical management is enlarged as it includes multivendor integration (MVI). Such a diversified and large-scale integration process requires its own planning, preparation, testing and reporting schedules. A.3.8 System Verification and Feature Testing The integration process is followed by verification. This ensures end-to-end continuity by rooting out bottlenecks and obstacles that might be present due to planning or implementation flaws. It involves all kinds of testing of all the network elements and their individual as well as combined performances, including monitoring of messages across the interfaces. Feature testing verifies that the complied features actually work in their true fashion and also that the total system performance is stable. Feature testing can involve software level testing or network element level testing or system level testing, depending on the test cases. This can be very time-consuming and laborious, generally done at the customer's pilot site. Feature testing is dependent on software and hardware levels and with every new release it has to be done again, as continuity of basic existing features need to be verified again and new features also need to be verified. As discussed earlier, multiple vendors can also supply the network, which leads to a different field of activity known as interoperability testing (IOT) and involves verification of an interface between network elements from different manufacturers, on a functional level, in accordance with the relevant standards. IOT is of two types: Network IOT Terminal