ovider to provider as much as interfaces. For example, one ILEC might require loop and number portability requests to be sent over the same interface at the same time, while others require them over different interfaces at completely different points in the loop unbundling process. There is inconsistency in the level of reporting ILECs provide as to the status of orders and trouble tickets. Few provide accurate status reports, and some provide none at all, regardless Chapter 2 - A Detailed Look at OSS of whether they meet firm order confirmation (FOC) dates. Interconnect gateways therefore are designed to help overcome these challenges. 2.6 Gateway Components Generally, interconnect gateways consist of three basic component areas: interfaces, a workflow manager and translation engines. Because ILECs are required to publish their interface requirements, vendors can build interface components to meet ILEC specifications - sometimes without a customer, and sometimes for a specific customer - and then reuse the developed interface as a component available in their product. Gateways are not sold or licensed with all possible interfaces on-board. Pricing is generally incremental, based on the number and type of interfaces the IIC customer requires. The workflow manager component is the mediator between the ILEC's processes and the IIC's processes. It incorporates a rules engine that acts as the traffic cop, telling the IIC's order management workflow engine when to deliver certain information based on a specific LEC's process requirements. This is particularly important when the IIC gateway is communicating with multiple suppliers. Rules engines should be designed for easy configuration, allowing a business analyst to adjust process rules through a graphical user interface (GUI) rather than requiring a software developer to alter programming code. The gateway workflow manager must be tightly integrated with the order management workflow engine to ensure that processes are flowing as efficiently as possible between the 