fpa1974
Well-Known Member
My point was made from the point of view of being able to index on certain pieces of data and not based on how close to real time you need to process it. While related to a point they are not the same and yes you are correct that certain (most) data has some aging constraints (like in your example where data becomes stale or irrelevant after a short (or a long) while.Well, it sorta does. It depends on what systems what data is in. Some services might not refresh quickly enough to be useful for some applications.As a normal example, I have Ecoobee presence sensors for my thermostat. But I can't use them to trigger smart lights in my HA system because the refresh rate is so bad you'd likely be out of the room again before it registered.
Insurance companies (because this is what we are talking about) do not really need real time data. They are ok with batches spanning seconds/minutes/hours//days or even a bit more - at least based on how the industry is setup at this point. It would be fun to think about a world where rates adjust more dynamically based on real time data feed but we are not there yet (fortunately or unfortunately depending on how you look at it). Or FordPass making you offers based on where you are at a certain point in time (this is where the ability to process data close to real time is important).If the data were pulled once a month for a report, then ya, probably wouldn't matter. But as I said earlier, if you wanted to make this data available for folks to consume for their internal reporting or ingest in their own systems (like an insurance carrier), it would need to be prepped, structured, and a system built to provide access to do so (assuming we are talking about it in terms of a "service offering"). The systems running Fordpass would make that kind of stuff easy as I assume they have a huge data lake powering stuff in the back end. If they don't, then they're even more behind then I thought it.
Not going to argue this one since you are spot on. That is why I mentioned that it is possible technically - that is not a guarantee of success as you pointed out because of many other factors.Still, I'd argue that ya'll are forgetting one thing - corporate red tape. Just because it could be done from a technical standpoint, doesn't mean it's realistically feasible for the budgets, skill set, and infrastructure the company has. I see stuff every day in my job that I could turn on and configure in minutes, but spend years trying to get customers to do
I think in the end @drummerboy 's point is probably what IMO we should be concerned - they are collecting our data (PII on top of everything else). And without clear retention policies or the right to be forgotten, while potentially incapable technically to do something useful with it nowadays that can change with enough time and money. Or they might get hacked tomorrow and that data ends up in the wrong places because they are not that top notch, security conscious tech company as we agreed. I would rather not risk it
Sponsored