We are soliciting fixed bid price quotes for developing a Windows-based handheld device application. The application will run on a Motorola MC-65 initially, but it should run on any Windows Mobile 6 device. It will present several screens (approximately 10, most very similar to one another) to the user (available upon request) and will use a barcode scanner, manual input, Web Services invocations, and GPS reads to populate various fields. It will transmit data in a prescribed XML format to an HTTPS URL over a WiFi connection and will store data locally until transmission is successful.
The handheld application will need to "join" a network/application infrastructure that is detailed in this section. The network will be available by connecting to a default SSID with a default WPA2 key. The network infrastructure will contain wireless nodes, called ecoNets, that form a wireless mesh network and ultimately connect to a server known as EDS. A default EDS URL will be provided to act as the "primary" EDS server with which the handheld communicates. Meters, Load Control Switches, and Thermostats will also be connected on this wireless network. All interactions performed on the handheld will result in the posting of an XML document to the EDS server.
The EDS server is a Tomcat Server that will be deployed either on the end customer's data center (customer EDS) or a cloud-based deployment (primary EDS). It exposes services as REST-ful URLs and encodes all incoming Request and outgoing Responses with JSON. We will provide URLs and Java class definitions for all request and response formats. On the server side we use Spring-MVC annotation-based mappings, so it should be easy to derive the JSON representation from these class and URL definitions.