Idea:
Just as the title says. Add the flashing hack countdown found on Null Cannons (where it flashes for 60 seconds before flipping) to installations. So when you hack an enemy installation is begins flashing for 30 seconds, while flashing it is unusable. So CRU's can no longer be spawned on, Supply Depots don't work and Turrets are disabled. If the original owners can't stop the hack in 30 seconds then it flips and now belongs to the enemy.

Reason:
Many times my squad will be holding an objective when some guy dukes of hazard's past us in a LAV, jumps out and quickly hacks the CRU right next to us before we can run back and kill him. Suddenly his team is now spewing out of the CRU like roaches and we get overrun and lose our objective. Our own CRU was our undoing since it flips instantly when hacked. The same thing happens, on a lesser scale, with friendly turrets suddenly flipping and then annihilating us from behind.

That's a war game for you lol I think they should keep it exactly the way it is....adds a serious dimension of thrill and challenges.

What you're proposing seems like hand holding to me....like you need assurance that since you hacked the NULL you get it. Its always up for grabs...learn how to use remote explosives, when someone LAV's you up and hacks the null....blow them away.

Seriously...if I'm within range on the battlefield and have dropped remote explosives...you cannot hack the null. I see it flash...BANG. Sometimes I can even respawn when you kill me, so fast that before you have hacked in (in 7 seconds) I can blow your ass up.

No hand holding necessary lol

Don't try that on me though lol.
I always clear Nulls before hacking and am able to hack the point long b4 you are able to spawn on it.

The OP is not talking about the null cannon but the instillations. How many players actually mine up there own instillations b4 moving on? Considering when the enemy starts to hack a CRU you detonate but wait.... they wasn't hacking THAT CRU but the neutral one they past up at the beginning. This isn't to say that trapping it isn't a good idea as I find it highly effective on supply depots.

The OP idea would kinda hurt the scout to be honest though. If I flank around the enemy and hack a CRU to get my team out the redline and it, instead, goes to "contested" status then I (a non-combat scout) have to fend off the enemy until it changes. Worst of all my team will probably now be getting farmed even if I succeed.

Well that's my view on the matter and gratz for getting your idea featured either way.

I still think its somewhat silly that a vital installation like the CRU can be hacked by the enemy so quickly. The time is so short than unless you are right next to the CRU (especially if its in a corner) it'll most likely flip before you can run around it and kill the guy who's hacking it. Then when you do find they guy and kill him you have to try and hack the thing immedietly before his enitre team mobs out of the CRU 10 seconds later and overwhelms you.

That's just bad.

A short contested timer gives you a chance to counterhack the CRU and stop the impending flood of enemies. You could also change the mechanic (for NULLs too) that hacking it nets you 25 WP and if it flips you get 50 WP (50 WP and 150 WP for Null Cannons). Counterhacking gives you 25 WP (50 WP for Null Cannons). That helps Scouts who flip installations far more. Hack for 25 WP and abandon it, or defend it for a hopeful 50 WP.

Either way, be it my solution or another one given by the community I think the current system where an enemy can hack a vital thing like the CRU in 10 seconds could be improved and made more strategic. No commander in their right mind would allow an asset that could grant the enemy instant access to flank / counter them to remain standing with such poor defenses.

Alright...you do bring up some valid points in the OP, however, I have to disagree with you at the same time as well. A CRU while it is important is not an objective, a counter hack to a CRU should not be available, with that being said though, a CRU should flash for 5-15 second befor fully turning over and when a CRU is being hacked enemies or friends can not spawn out of it, since it is being hacked.

Turrets and supply depos should not get the same prefential treatment as CRU's do, because CRU's are making actual clones and putting down drops, supply depos are just ammo and turrets are just weapons, nothing as complicated as a CRU is. People as it is, treat CRU's much differently then they do supply depos and turrets, in a game of ambush a CRU is actually considered one of the most valuable things upon the map, since it does produce extra clones and also is an uplink point.

So while I do not think counter hacking should be happening at CRU's I still think they deserve additional defensive options as listed within the post, which would make it significantly easier to recapture one if say an LAV raced by, capped it and was thinking they could just flood you while they drive off, they would have to put up a minor defense at least to keep the CRU safe and if they just left you could grab it back from them quickly and easily without a ton of people dropping in at once.

annihilating us from behind.

I don't see the point actually.

Consider this scenario: Suicide run with a LAV and a Cheap Logi Suit. Fly past the Defenders and jump. Start dropping Uplinks like a drunk losing coins from a hole in his pocket. If the squad is waiting for the CRU this is actually faster, can project into a wider area and actually generates more WP than a simple hack of a CRU.

The system works well as is. There is no real benefit, from the game standpoint, to blinking and timers. Don't bother. If it happens then variations on my idea will replace it faster than you can turn around in a Heavy suit.