Create a simple GUI for a control system using Unity3D and C#

We require a relatively simple GUI for a flow/control system using Unity and C#. It will be used to monitor statistics associated with a set of nodes between which flows occur. The GUI will consist of a main screen on which a graph of the system (think flow chart, but snazzier) is displayed along with animated flows between components and selected stats overlayed on those components. The user may choose the statistics, issue command to us (like pausing or unpausing a component), and scroll/zoom the graph itself. In addition, there will be the following overlays: help, general options, keyboard/controller config, server-connection config, and a "list view" which displays all stats for all components. The key aspects of the project are discussed below, but first a word on process. Bids should be for the entire project as stated and include an est time to completion. We may provide additional details upon receipt of a bid and execution of our own (rather standard) NDA/IP-agreement (US-based). We expect that our description below captures the complexity of the project and, if anything, overstates it. We require no "test" project or any such nonsense. We're new to freelancer.com and understand that bidders don't know us. We will set milestones in such a way that the first portion of the project itself will serve as a (paid) test project. We wish to minimize reliance on external Unity packages, but will employ them if needed. Any such packages must be widely supported (ex. NGUI), have nonrestrictive licensing terms, and any associated code must be in C# and included as source (rather than provided as a DLL). No elements specific to the "professional" version of Unity should be used. The following elements will be involved in the project: 1. Design and construction of a cross-platform Unity GUI for our system, with any scripts written in C#. We prefer an emphasis on programmatic management of the GUI (as opposed to using the Unity IDE itself for this purpose) -- but are open to both. 2. The final code and Unity package must be presented to us in a way that allows for their maintenance and extension on our end. 3. Secure Unity server-client communication model using RPCs and SSL. 4. Particle or similar animation of flows along tubes rendered as splines. Graph topology and spline control points may be generated internally (ideal) or provided by our system externally (current). 5. A minimap 6. Two-way communication of the game server with our backend system via sockets, shared-memory or files. This is the means by which our backend system updates the state info that is conveyed to the client GUI and by which they subscribe to it. 7. Tight animation and snappy responsiveness of the client GUI. 8. An input system that is configurable and allows both keyboard and mouse/joystick/etc control of the GUI. 9. Sensible behavior of both the screen and inputs on different devices (including different window-sizes, etc). The GUI must be portable and run on mac, pc, linux, iphone, android, and in a web-browser. 10. Attractive buttons and other UI elements -- both on the main screen and on the options screens. 11. Ability to load/save configuration info on the Client GUI end. 12. The monitoring program should run in 3 modes: unity server (no gui, connects to our backend via sockets or other, and manages subscriptions/etc), unity client (the monitoring GUI which connects to the server, subcribes to certain statistics, etc), and standalone (has the gui, connects to our backend, and involves no Unity server-client communication).