The N2 controllers stay right where they are - Tridium does not yet have unitary-type controllers with any real level of I/O (although that's rumored to be right around the corner). BACnet is the key to getting JCI stuff into Tridium - an N30 programmed to broadcast each needed point will be easily detected by the JACE, and it's Tridium programming from there...
Alternatively, without an N30, a clever person could configure Tridium's Configurable Serial Driver to emulate the N2 protocol (since you can't buy an N2 driver from Tridium anymore), then you'd wire the N2 trunk straight into the JACE's RS-485 port. But such a person would have to be mighty clever, and then I'd want to know exactly how he did it...
Now that would be handy!! Mind you, PMI has some fairly decent scheduling, trending, alarming, etc., etc., but M-Web is fairly expensive, and Tridium has some fairly advanced Web features, so I could see the potential for a Tridium addition to an N1 installation. I wonder if this will actually give Johnson's extended architecture (NIE, NAE) a run for its money.
It is rumored that the new Johnson front end is a Tridium JACE controller. You definitely can bring the n2 bus in through the configurable serial driver or as suggested use a n30 to a Tridium front end using BACnet ip.
Tridium uses a JAVA/XML protocol to program with a thin client web server. Every protocol BACnet, Lon, ModBus etc.. requires "propritary" configuration software to set up the controllers. And if you are just talking about a web server then Tridium is more expensive. But if you are integrating a variety of different protocols to the web, Tridium is more cost effective than a Plexus front end which uses a Field Server gateway. Nothing in the controls industry today is cheap. And Tridium isn't the easiest product to use.
If I am setting up my LON network I can take my pick of network tools. I can also take my pick or use a combination of front ends. The only sticking points are OEM's like Trane that use their own style of plugin and vendors like H-well that don't put the programming software into a plugin. If I would stick to companies like Circon, Douglas, and Echelon I don't need any extra software or proprietary software for programmables. You know, NONE.
....and I don't need a proprietary framework to throw in web servers at a very low cost.
Can't do that with BACnet or Modbus. They require proprietary network tools.
Maybe you want to clarify your LON position. And, the ilon100 is very cheap $/point.
Look I integrate all types of control systems. Reguardless of the brand of controls you have to buy software to integrate. Don't you have to pay for credits to bind LNS networks? Don't you have to pay for Lon Maker Software? Proprietary just means they want you to buy their software and training. The good news is that the availability for integrating systems is getting better everyday. The companies that were the worst offenders have had to go to the standard protocols like Lon & BACnet (mainly due to sales in the European Union) leaving themselves open to creative individuals that don't necessarily have to be at their mercy.
I pay for credits. I pay for Lonmaker, or Circon NI, or Distech. I interchange the universal database between the softwares. I can use Distech software to completely setup Circon devices or vice-versa. One software package. Pick one.
-not nearly as much as you pay for Tridium's Niagra Framework. You don't pay for credits, but you pay dearly elsewhere.
Also, my web servers aren't tied to some proprietary framework. Easily interchanged. Once you are in the framework your options are zero.