This is a personnel tracking software application. Each person is tagged with a tracking device. The tracking device reports the person’s location sensor data to a central server. The central server processes the data to figure out the location coordinates of the tag. The server then forwards the location coordinates to clients. Web clients (Flash/Flex clients, C# clients, Java clients) can receive streams of location information from the central server and, in real-time, display the latest location of the tracked person. Within a single enterprise building, all persons can be tracked with the tag as they move within the building.
A person can message another person’s tag through the server, like an “instant message.?? A client displays all the incoming/outgoing instant messages for each tag. The client can also send instant messages to tags. Each wing of the building contains a wireless gateway that transmits information to tags within that wing. A building can have 1 - 50 wings, each wing can have 20-40 persons, the entire building can have 100 to 1000 personnel. Each gateway sends/receives data a software program called GBIF (Gateway Board Interface) that sends data to the server. Each building has one central server. Each of the wings in the building has one gateway, so there could be 1-50 GBIFs per server.
1. Architecture design document for the server
2. Design meeting with Customer to review architecture proposal. Customer MUST agree to architecture prior to development.
3. Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
4. Deliverables must be in ready-to-run condition, Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
5. All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
· Two types of data are sent from GBIF (sensor streams and messages), processed by server algorithms, and then sent to the clients. The server must provide HTTP web services that support pushing and streaming data to clients.
· Clients may send messages to tags. The server will be responsible to keeping track of which GBIF is related to which tag.
· GBIF is written in Java 1.5.
· Web clients are written in Flex/Actionscript 3.0, C# 2.0, and Java 1 and 2. All web clients must communicate with the server through web services.
· The server is deployed on a 32 bit Windows 2003 server with .NET 2.0 and MS SQL Server.