In a meeting Tuesday, 12-7-2004, UNCG ResNet announced it would license PhoenixPo.com Web & Design's 'Work Order Entry System', or 'WOES' for short.
The meeting resulted in two major contract points--Hall retains ownership and access to the server (for updates) and UNCG pays Hall a licensing fee per year for the system. The ResNet representative also indicated interest in PhoenixPo.com's vision of the WOES--that of a work order system and knowledge base (KB). The knowledge base will contain three components, a KB for anonymous (student) access, internal ResNet access, and an online KB hosted on PhoenixPo.com for cross-campus users of the WOES KB. Another interesting feature utilizes RSS feeds to serve work orders to a user’s desktop (this is from a brain-storming session and not a set feature as of this writing). Other features will be added as indicated by end users.
PhoenixPo.com's WOES was developed when its owner, Christopher Hall, was still affiliated with UNCG ResNet. Hall developed the system to address ResNet's growing need of having an online system to house and distribute work orders.
The WOES has been in existence since February 2002, when the first version was developed. The current version was developed during summer of 2003. The current version allows ResNet employees to sign into the system to check which work orders are currently assigned to them, create and edit work orders, view work orders, and view fellow employees' contact information. Administrators can create and lock user accounts, assign users to dorms, and configure how work orders are automatically assigned. Screen shots are available at http://www.phoenixpo.com/portfolio/woes.asp.
The system was programmed in ASP 3. We at PhoenixPo.com W&D wish to update all our software to our current design standards and capabilities, as well as to ASP .Net. However, we will only take on a few projects at a time, and development on this system is not of a high enough priority to override this rule. If a new system is to be introduced, it will be done by August 2005 or 2006. When we begin development, we will interview end users before doing anything else.
