giggidygig
Dump local staff, re-hire in the other country. Dump local back office staff, re-hire in the other country, or, they already have it outsourced.
If its on some executive's KPI or has their yearly bonus at risk... mountains can be moved in a blink of an eye.
I'm based in Australia, while i regularly work with teams from the US.
I've found my US counterparts are extremely bad at using their time efficiently and productively, even though, they are intelligent, knowledgeable and easy going (hands down, some of the best problem solvers i've ever worked with).
I was asked to work late once (due to time differences), and they were shocked when i said "i'm only available during working hours". They took it as a slight, or that i was being rude. I was even called "lazy".
It wasn't until i had an "offline" conversation with some of them that we both got the opportunity to discuss each others points of views.
My US counterparts admitted that one of their main reasons for not saying "no", was Health Care, or the risk of losing health care if you lost your job.
I think this (no fault to my US colleagues, i would probably feel/think the same way), results in bad work practices being perpetuated, resulting in unnecessary work hours, or, at least the perception that its required in order for you to be seen to be "doing a good job".
There's working longer when there's actual work that needs doing, but then there is working longer because your being held hostage to a job because your petrified of getting sick without one.
Case in point, one of my US colleagues was working 2 days after having heart bypass surgery. TWO DAYS!!!!
I still believe the accuracy and trustworthiness of said data would still have to be proven or guaranteed in some fashion in order for it to become considered a true resource with a tangible value attached to it.
Possibly have an associated physicality to it (i.e stocks attached to companies, money attached to physical currency/gold etc..).
Ask HN: What is the perfect IT organizational/team structure?
A question that has intrigued and frustrated me for a long time. What is the perfect IT organization/team structure which benefits both the business requirements and those who work within it?Flat hierarchy (ala Valve), full outsourced, small start-up, large multi-leveled corporate, or a hybrid?Or is it possible this perfect mix just doesn't exist?
1) Downhole Telemetry Systems (Communication for Downhole tools) - using EM, Fixed Wire in Drill Pipe and Mud Pulses (Pressure changes in Mud) http://www.halliburton.com/en-US/ps/sperry/drilling/telemetr... http://www.slb.com/services/drilling/mwd_lwd/mwd/powerpulse....
2) Point the Bit/Push the bit/Rotary Steerable Systems - ability to remotely point the drill bit in a desired direction http://www.halliburton.com/en-US/ps/sperry/drilling/directio... http://www.slb.com/services/drilling/drilling_services_syste...
3) Loggin While Drilling Technology - having inbuilt sensors of various types on the drill bit, collecting/sampling while drilling http://www.halliburton.com/en-US/ps/sperry/drilling/lwd.page... http://www.slb.com/services/drilling/mwd_lwd.aspx
Oil Companies think large and long term (10-50 yr cycles), meaning their payback/revenue period is also longer, and as a result their business strategy/forecasting is longer.
The cycle usually starts with a lot of upfront Capital to build up the capability to find/drill/produce/refine/sell the oil.
Once they have that capability, then the focus is on producing oil in the cheapest most efficient way possible over the 10-50 yr life of the oil field.
Compare this to the services/contractor companies, whose work is mainly fixed/short-term contract based, as a result their business strategy forecasting is alot shorter. It is also more competitive, so they have to constantly think up new and better services to provide the oil companies, while also trying to reduce their own operating expense to extract as much margin as possible.
So being smaller, with shorter business cycles, and more focus on doing things better, smarter, cheaper, the result is that the service/contractor companies really have more opportunity and an inherent need to innovate, simply as a way to survive and make profit.
1) The smaller the company, the more agile/nimble you are forced to be out of pure need (no money or resources), this means you have to look at automating things in order to just get you're job done. Because if you dont, you end up working 24/7 because you are the only one there to do it. Just like a start-up.
2) The bigger the company, the less agile/nimble, more bureaucracy/politics and people, the same driver is just not there anymore, so the focus on automation isn't as intense.
3) The contractor/service companies (Halliburton, Schlumberger, BakerHughes/GE, Transocean, Nabors etc..) are probably the only ones in the industry that could successfully develop and use these types of automation technologies, because it would make their services cheaper for them, NOT make it cheaper for the oil companies.
4) The big oil companies have the money, but they simply don't have the ability to effectively produce/innovate internally as a smaller company would.Hence the only way they would adopt anysort of automation tech, would be as a service, even then it wouldn't quiet match up with their own internal business needs as the company just isn't wired to think that way.
5) Currently, the buzzword/hype vortex within big oil is all BigData/Cloud/Automation/AI etc.., but is sadly used internally to blind higher ups to approve internal projects that really aren't much more than a hobbled together mess of ancient tech.
So from my perspective, automation will eventually get there in oil/gas, but it will take a glacial pace for it to happen for the oil companies themselves, but once it eventually get's there, that's when you will see the major watershed "automation" changes in the industry.