Transaction System



Requirements
Interface Mockup
top

Today's installation process revolves around the transaction processing and data management stored in many separate systems and shadow databases. To develop a smooth process, the technology simply needs to be addressed. Here are some examples of the goofiness...

  • transaction tracking: performed today via local filemaker databases, FO database and an assortment of group oriented mailing lists.
  • scheduling: performed today via meeting maker and other local ad hoc solutions.
  • billing: performed today with a 4D database, ICE9, TCM and the 5ESS.
  • host management: performed today with moira but not tied to billing or network management.
  • inventory management: performed from the controller database, moira and ad hoc files.
  • underground cable management: performed today with ICE9
  • 5ESS management: performed today with ICE9
  • network management: performed from the controller database, moira and ad hoc configuration files.

These just name a few and manual processes exist to attempt to tie all of this information together. Technically, the transaction processing and the management of the network and 5ESS services can reside in separate systems using a tools such as java to glue them together. It is also not recommended at this time to tackle all 3 together. The recommended route is to implement installation transactions followed by a phasing in of network and jack management, host management, and circuit management. The complexity of the ICE9 system, although no saint in this process either, is a project for another day and another group.