Does MDT want or need ENOS?
Personally, I don't think so:
I think you are aware that Titan is developing a prototype for MDT as part of the current agreement to commmence around end of year if the latest delay on that pushed back from October is on track. So, if MDT was interested in ENOS as a whole, what is the prototype they are developing. You could say that MDT just licensed the IP just to lock it up and give Titan time to complete ENOS. So, IMO either that is the case and ENOS is still not completed to the satisfaction of MDT (at least as of Oct) or Titan is developing something else; potentially helping integrate the IP into Hugo platform? It makes sense for MDT to be able to use the same workstation platform with a Hugo MP and Hugo SP system. Acquiring ENOS as a whole does not allow that; different software and controllers, etc. Hugo MP uses individual towers so makes sense to me to for them add an SP patient tower to use with current Hugo workstation (which is already similar footprint in size and portability as the ENOS workstation. Due to timing, or lack thereof, I don't think anyone believes any of the Titan IP licensed is integrated into the CE approved Hugo MP platform so ...
I ask, where is my thinking off? Do you think Titan is developing an endoscopic solution for MDT? Highly doubtful as they can't even complete ENOS.
So I believe it leaves ONLY two scenarious:
The development agreeement in place is for:
1. MDT to help Titan complete ENOS
OR
2. Titan to integrate the licensed IP into Hugo SP platform. Sad if true as they got the IP for only $10 million and the rest of the payments were for Titan's time and engineers to integrate the IP. But remember, Titan's doors were closed and they were being sued by a vendor when MDT swooped in so you can say McNally isn't that stupid but ... guess we will find out in about six weeks (without any further delays announced)
Please tell me another scenario?????
BelizeMe
AI
Market Data 
Markets 
