IVB
Senior Member
Well, not to rewind this thread at all, but got told some info in my "real job" that has an interesting parallel to this thread.
As if the universe was out to reaffirm my fear of "quiltmaking" different companies together, at work I was just told yesterday that the two companies I hired to build me something have a disagreement on how to support a given feature. We're currently in the middle of development, way past rqmts & design. These are 2 tightly integrated business partners, combined methodologies, joint proposal, etc., and this mess is now in my lap. Plus, they're claiming the way their contract reads, neither of them are actually responsible for this issue. I'm going to have to go to the CFO and ask for another month and $1M just to accomplish that which we thought we had already paid for. Either that, or get in a real ugly legal battle, which in itself will delay the release by much more than 1 month. Even if I end up not paying the bill, i'll miss the fiscal year-end, which means it comes out of next years budget so I'm still hosed financially.
I may be a DIY'er, but I don't like to take unecessary risks. I generate plenty of risks myself, I don't need anybody else forcing their risks on me. Life's too short for that.
With any luck, I still have a job tomorrow, and have the $$ to continue this HA work.
2- The system would need to support a large number of devices and support them DIRECTLY. The problem with connecting a bunch of different subsystems together is that the limitations of each subsystem becomes a limitation of the overall autmation setup. If, for example, you depend on an ELK panel to provide your interface to RCS thermostats, you will only be able to access those thermostat features that are supported by the ELK firmware. If ELK decides they don't want to report manual changes to thermostat setpoints in their firmware then that information is forever unavailable to the PC controller.
A true PC based automation system must support the direct attachment of most devices to PC ports without depending on the business priorities of any other company.
As if the universe was out to reaffirm my fear of "quiltmaking" different companies together, at work I was just told yesterday that the two companies I hired to build me something have a disagreement on how to support a given feature. We're currently in the middle of development, way past rqmts & design. These are 2 tightly integrated business partners, combined methodologies, joint proposal, etc., and this mess is now in my lap. Plus, they're claiming the way their contract reads, neither of them are actually responsible for this issue. I'm going to have to go to the CFO and ask for another month and $1M just to accomplish that which we thought we had already paid for. Either that, or get in a real ugly legal battle, which in itself will delay the release by much more than 1 month. Even if I end up not paying the bill, i'll miss the fiscal year-end, which means it comes out of next years budget so I'm still hosed financially.
I may be a DIY'er, but I don't like to take unecessary risks. I generate plenty of risks myself, I don't need anybody else forcing their risks on me. Life's too short for that.
With any luck, I still have a job tomorrow, and have the $$ to continue this HA work.