- Introduction to WorkXpress
- Building Your Application
- Examples and Best Practices
- Technical Manual
TechEngine is an app that is designed to serve companies that hire techs from around North America to perform various types of technical tasks for residential and commercial clients. Important features in this application include:
This application was developed by Noah Coburn.
Monday, October 8, 2012
Today was spent planning designs for the application. The database structure and most of the automation was planned out, as well as a few of the key interfaces for the application.
Tuesday, October 9, 2012
Today was spent finishing off the designs for the automation and interfaces. Agile design concepts were used to decompose the various aspects of the application into the atomic user stories that compose the application.
Wednesday, October 10, 2012
Today was only partially spent on this application, as other duties took me away for a time. The designs were reviewed and approved on a conference call with the client, then development actually began. Several administrative tables were created, such as Skill Categories, Skill Names, Certification Vendors, Certification Names, Application Settings and more.
Thursday, October 11, 2012
Today, I concentrated on developing the self-enrollment pages for techs. This allows the tech to enter their basic contact info, skills, location, and more. When complete, the tech will appear in the enrollment queues for the internal employees to review and approve. This is a four-step process that goes back and forth between the tech and the internal employees. This process was about 80% finished today.
Friday, October 12, 2012
Today, I finished the remainder of the enrollment process, and started to create the basics of the work order creation and view pages.
Monday, October 15, 2012
Today was spent developing some more of the work order creation process, and a bit of the interface to view and manage the work order. Also, spent a bit of time developing the pages to manage tenants, accounts, and clients.
Tuesday, October 16, 2012
Today was spent responding to some change requests from the client. Changes were made to the registration pages, some of the administration tables, and a great deal of the work order pages.
Wednesday, October 17, 2012
Today was spent on the dispatching automation for work orders. This includes the ability to search the active techs for those who are a) in the appropriate area (geolocation radius search from ZIP code), b) have the appropriate skills, and c) are available to accept the work order. Also, once the appropriate techs are found, the application needs to send out emails or SMS messages to the techs to inquire as to whether they are available to take the work order. Various statuses for the work order dispatches need to be managed in this process as well. The manual dispatch process was about 60% completed today.
Thursday, October 18, 2012
Today was spent finishing the manual dispatching functionality. Change requests were completed as well, and some of the administration pages were updated per the client's request.
Friday, October 19, 2012
Received a client request to change the method by which the tech specifies level of skill, which required a moderately lengthy change to the automation. In addition, started to develop the employee dashboard, one of the key interfaces in the application.
Monday, October 22, 2012
Finished the employee dashboard today. Also, added some additional views to the tenant, account, and client pages. These will allow employees to have in-depth views to tables related to each of these tables (accounts related to tenants, clients related to accounts, work orders related to accounts, work orders related to clients).
Tuesday, October 23, 2012
Today, I worked on the financial calculations on work orders, and worked on the tech dashboard. Click here to see a video of me building the work order financial calculations automation.
Wednesday, October 24, 2012
Today, I focused on the workflow associated with taking a work order through the process from start to finish. Click here to see a video of me building the main part of the workflow. Off the video, I fine-tuned some of the steps that needed a bit more interface focus, and made a couple changes the customer had requested (mostly interface changes).
