One of the advantages of our system is that any information in the system can be made available.

When using our system as an internal user - you are using a form that has been loaded onto your machine (a WPF form for those who are technical).

But - there is no logic on that form - all the logic is on the server.

Also - that form communicates with the server using Secure XML.  XML is a generic communication that can be used by websites, portals, iPhone and Android implementations

So - any screen or logic in the system can be easily made available to external users.

In Practice

In practice there is a number of steps to take (we can help you with any or all of these)

1. Decide the business flows that you want to support
2. Draw up the screens you will need to support those flows
3. Check if any changes are required to support your chosen flows - ie is this the way the system already operates
4. A Web Designer can build the screens as you like (note we may have a close starting point for them)
5. A Web Developer can then wire up the fields on the screens to our system (note we may have existing models for them to copy from)

Examples

Tour Coach Drivers Portal Development

The flow required was:

1. Confirm I will be driving (must be done the previous day or alerts happen)
2. Check my bus - report defects
3. Change my bus if defect found
4. Change driver if another driver did not make it
5. Check my pickups
6. Mark people onboard
7. Capture dietary and other notes
8. Capture lunch requests as qty per meal (eg steak dinner