ITIL is a set of best practices. You take what you can use, mold the rest in shape and it gives you a vocabulary with definitions to use in conversation so everyone has a better chance of understanding eachother. I highly recommend it for developers so they can talk the talk with service desk folks.
That said, there are some managers that raise an altar to ITIL and then start praying to the ITIL gods for deliverance. And if you do not follow the Holy Book of ITIL you are DOOOOOOOMED!
If that's the case, you're in for some heavy weather because how you do it is going to be more important than what you do. Get out fast.
On the other hand, if it's an attempt to get problem and error reporting and detection on a better footing, with more data so problems are solved earlier and better, it's a great way to go.
From the description, it's impossible to tell what's happening.
As for the whole "staying in contact with suppliers" and "project management dependencies" - the new guys apparently do like you, but they want you to take on more managerial responsibilities. Overall scope and strategy as opposed to hard-core hacking at terminals. If they didn't like you, they'd leave you alone.
Did you try talking to the managers and discussing your ideas and fears with management? If they freak out, it's time to go. If not, you could maybe have a discussion about how you see your future, versus their vision?