I'm an automation engineer but I hadn't spent much time around the BACnet protocol until a recent job change. Most of my work was with PLC's for machinery and processes and you can spend a career doing that and very happily avoid BACnet. Then a recent job change found myself specifying a building management system. Hello BACnet. I was also interested in ignition for said BMS so I thought I installed Maker Edition, bought myself a wireless BACnet thermostat for my home and was ready to go to town. (Contemporary Controls BASstat wireless version) I overlooked the fact that the one driver I wanted to explore was not included:( No worries, Python BAC0 library and a little ingenuity to the rescue. I'm doing this all on an old PC running Linux Mint, by the way. My solution was to use an SQLite db file as an interface between Ignition and my thermostat. A python program executes every ~5 seconds and reads the parameters I want from the database. The only thing I need to write is the setpoint. I have another database with exactly one row and when I need to change the setpoint I write a flag. When the python program reads the flag as 1 it know it needs to read the new setpoint and store it in the thermostat. I just thought I would share this in case anybody else was grumbling about the BACnet drive being absent. A little more work, but you get to learn how to read/write SQL files in Ingition at the same time.
I thought the schedule was going to be the hardest part but another forum post solved it for me. The time and temperature values are array tags. I created one tag just for the purpose of running an event every minute by setting the value equal to the system date minute and running a value change script. This compares the scheduled times with the current time and if it finds a match writes the new set point to the db file.
Neat workaround.
Was there something insufficient about the first party BACNet driver?
https://docs.inductiveautomation.com/display/DOC81/BACnet
He's abusing the Maker license for work. 
Are they? There is a post edit. Was the first version different?
Answer to the OP: you use the full version in demo mode 2 hour, and when you have your proof of concept done you buy it. If you need longer than 2 hour, you reach out to a sales rep for a 30 day trial, but don't expect them to extend this often (if at all).
The edit on the OP's post was changing Ignition to Maker, what it is now.
I don't see how the conclusion that this must be Maker running in a non-home/education environment is reached immediately whenever Maker is mentioned... in most cases, I agree - people are using Maker instead of a 2 hour trial or a sales demo license. Here, they clearly have several views built out that all center around a thermostat. If this project is for a production environment, it's pretty cheesy (in that all of the views center around one device). To me, it clearly looks like something I would build for a home system - I looked into something exactly like this for a Maker project, to connect Maker to my Carrier Infinity systems.
Again, I'm not saying that the Maker license isn't being abused, it's just annoying to see people immediately assume that when I think in this case it's pretty clear (to me) that it's probably just a home installation of Maker.
From the first post:
So, mocking up a BMS specified in the new job.
He does mention home.
Fair enough.
Just because OP has an upcoming BMS project, that does not mean the work that he's doing at home is a mockup for a full fledged BMS. If I had an oil/gas project coming up, of course I would try to integrate every pump within a 1000' radius of my house into my hypothetical Maker project- not because I'm necessarily trying to demo a solution for a future customer, but because a piece of equipment that I did not think about integrating into a home automation system before now seems like another device that can gather useful information. The Maker edition homepage clearly states that using Maker for sales demos is prohibited, as well as using it for commercial applications (so if OP is doing that, clearly violating the license for Maker). HVAC systems for residential and industrial are wildly different - even within residential systems, there does not seem to be any semblance of a standard when it comes to interfacing with them. A project that revolves around a thermostat is hardly a BMS.
Here is a scenario that I might find myself in in a few months - I want to use Ignition Maker to gather data from my house. I dislike the default themes so I will build a new one completely from scratch (for my home system). At some point in the future, I would like to use those themes elsewhere, including in commercial applications. Does that violate the Maker license?
Here is another scenario - I would like to document and share the process of building said home automation system through videos, posted on LinkedIn and YT. Those videos become popular (hah!) and become monetized at some point in the future. I use Maker edition in those videos - does that violate the Maker license?
Again, I don't know OP or their situation, so I don't know for sure how they're using the license (neither does anybody else). I'm going off of how I understood the post and the provided screenshots.
That's not true. This is entirely at my home. You could probably check this by looking up the IP address where the license is coming from and using a geo location application online. I work for a pharma manufacturer and I would never implement such an ad-hoc solution, nor would it pass GAMP5 guidelines. Rest assured, this was a combination of a nerds hobby and evaluating the software for possible future applications. Isn't that why you offer the Maker edition anyway? Lastly, I wouldn't be so stupid as to post it and jeopardize losing the Maker license. I'm somewhat impressed that you think it's a robust enough solution to be used in industry. It has been reliable thus far.
Instead of guessing at making false accusations why not just ask me? I'm honest and if I'm doing something that violates the license I will take it down. I will email you the project if you like. Though, as others have suggested, this is a trivial industrial application and is entirely overkill for 99.99% of home users. I could not find any local integrator's that knew about Ignition though I am aware of some local business that are using it. For various reasons, I had to go with a Niagara based EC-BOS-8 from Distech. That was 6 months ago. After the fact, I installed this on a Linux box at home so I could learn enough about it to either 'sell' the product to management as our future MES or find an alternative.
I conceded the point two days ago, after @jlandwerlen quoted from your OP.
Just to make sure everyone's on the same page - Phil isn't an IA employee, just a motivated third party whose opinions are his own.
"another forum post "
Do you have a link to it.
Thanks for the detailed report.
Blessed and Merry Christmas!