I am talking about the actual database structure and set-up. It isn't as simple as adding a few more subsets and datafields.

IT had to be an adopt and go strategy because you can't just make the two systems talk to each other (it would take nearly as long to do this as to just develop a new customized it backbone and reporting structure). I don't really like SAP, (very limited experience) and would prefer a customized wholly owned solution but this is very expensive to develop and maintain.

I agree that it is about usability and productivity and flight ops is not the only user of the system.