markets  
 NHS healthcare
 Human Resources
 financial services
 logistics and transport
 mobile telecoms
 retail

Customer Installation Information

Installation is a simple process, and can be zero-footprint for client PCs. On the server side, a scheduled data collection agent securely pushes data to Oceansblue out of production hours.

A data collection process will be installed on the RosterPro Central Server. On a scheduled basis, this will collect ward-based metrics (not staff details) and transmit these to a server, hosted by Oceansblue. Data is then absorbed and processed into a cube structure, for later rapid access by browser clients. From a client perspective, access would typically be via a Silverlight 4-enabled browser as this gives the best user experience.

For non-Silverlight browsers (typically mobile iDevices) or where preferred, the presentation layer can be rendered as HTML5. Further, and if required, mobile applets for iDevices running iOS, Android and Blackberry exist, offering a custom view of KPIs in a low screen real estate environment.

KPI alerts are typically pushed by email (and can include images of the dashboard, showing areas at risk) from the Oceansblue server to the interested user's email address, on a subscription/elective basis, so the Oceansblue mailserver should whitelisted. Finally, a Sharepoint Web Part and ASP.NET API exists so that elements of the dashboard can be incorporated in the Trust's Intranet, for example: various performance league tables.

Ongoing presentation layer updates are handled by Oceansblue. The should be no additional maintenance for the Trust's IT Department to accommodate, save perhaps reviewing escalatory email alerts where the extractor process fails (Oceansblue will monitor this anyway and also).

The SMART exporter agent is a C# application that would typically sit on the RosterProCentral Server. The Oceansblue exporter is TSQL-based and sits side-by-side with this. The definitions determining export construct for the Oceansblue extractor are self-updating over the internet. A scheduler is typically set up inside SQL Server as an Agent Task, to drive collection and transmission.

A managed FTP over SSL service (typically using WinSCP/FileZilla) will push the resultant extracts to the Oceansblue server. Email alerts or system server log entries (which can be picked up with server monitoring software) can be generated in the event of process step failure, although failures are automatically retried. A nightly run is normal and appropriate. Installation and testing should not interrupt service and should take ½ day with pre-planning, and can be achieved remotely, if permitted.

A summary installation and requirement checklist would be:

This is very benign, with no client-side installation required (assuming Silverlight is deployed as part of Windows Update). The typical install will be on IE6 (XP) or above. PC minimum specification would be 1Ghz x86 with 1GB RAM. The operating system would be XP SP3, Vista or Windows 7. Internet access to our server is required, over HTTP. Mac OS X is also supported as a client environment. There are no elements of Oceansblue software installed client-side.

Our solution will be placed in a resilient cloud-based environment, comprising Windows Web Server, SQL Server SE or MySQL, RAID-5 disk and sufficient RAM and CPU power to deliver a performant solution. We would adjust server resources in line with demand, for example if a higher number of client licenses were purchased.

Silverlight 4 is non-64bit. The specific minimum client level is 4.0.50826.0.

Mobile apps minimum OS levels are:

For HTML Viewing (if required) higher browser versions are needed:

quicklinks