More good input gents, thanks.
We're actually going without a HUD since there isn't any spare room on the overhead panel and very little on the coaming / behind the flatscreens to mount it. Perhaps equally importantly, HUD design isn't particularly new and there isn't a huge benefit in learning to design one (or copy someone else's!).
However... We have elected to develop single pilot ops. The cockpit will retain two full sets of displays / controls as it was felt the certification process would be impossible if we chose to go with a single pilot installation.
This throws up some huge challenges, not least what happens when the pilot is incapacitated! The general thrust at this point is to have the aircraft autonomously land at the nearest available airfield, so defining the sequence of events from the take-over (what constitues pilot unable to control?) through declaring an emergency, requesting a new flight plan and then controlling the aircraft all the way to stopping on the ground is bending our brains in whole new ways.
We will also need to automate checklists, provide voice prompts, voice recognition, some decent algorithms and on-screen assistance for system failures.
Part of the process will be writing certification rules to present to the EASA / FAA to demonstrate the problems, and the solutions we have designed to mitigate the risks associated with them.
With firms such as Embraer declaring their intention to work towards SPO within the next 10-15 years, I feel it is high time a University gave this more than a brief consideration.