Chapter 86: The Security of Production
Location: Prime Minister's Office, South Block, New Delhi
Date: 18 January 1972 — 10:30 Hours
---
The expansion had outpaced the structure meant to protect it.
Steel output was no longer confined to a handful of public plants. Petrochemical complexes were moving from paper to land. Private industrial clusters—quietly mapped within the Ministry as Special Economic Zones—were beginning to take physical shape. Not scattered factories, but concentrated engines of production.
And that concentration changed the nature of risk.
A delay was no longer a delay. It was a chain reaction.
A shutdown in one plant meant halted inputs for another. Transport schedules slipped. Contracts stalled. Output projections collapsed across sectors that had no direct connection to the original disruption.
The system had grown.
The protection around it had not.
Inside South Block, that imbalance had been reduced to a single file placed at the center of the Cabinet table.
Prime Minister Indira Gandhi did not open the discussion immediately. She allowed the room to settle, papers to be reviewed, margins to be marked.
Around her sat men who understood power—not as rhetoric, but as control over systems.
C. Subramaniam had already gone through the draft twice. Yashwantrao Chavan was reading it for implications, not content. Jagjivan Ram had underlined sections related to authority.
At the far end, not part of the Cabinet but present by decision, Karan Shergill sat with a thinner file—his version, distilled.
Indira finally looked up.
"This is not a routine amendment," she said, her voice even. "If we pass this as written, we are not adjusting a force. We are redefining control over industrial output."
She turned slightly.
"Subramaniam. Walk us through it."
Subramaniam didn't waste words.
"The proposal amends the mandate of the Central Industrial Security Force. At present, it is limited primarily to public sector undertakings. The amendment expands jurisdiction to all designated Special Economic Zones and critical industrial areas, irrespective of ownership."
He flipped a page, continuing in a steady tone.
"Three operational changes follow. One—permanent CISF deployment across notified zones. Two—grant of policing powers within those zones. Three—restricted entry and operational role of state police unless formally coordinated."
The silence that followed was not confusion.
It was calculation.
Chavan closed his file halfway.
"You are creating a parallel law enforcement structure," he said. "Inside economically critical zones, the Union supersedes the states."
Subramaniam met the statement directly.
"Yes. Because the output from those zones is not local. The loss from disruption is national."
Chavan leaned forward slightly.
"That logic is expandable. Today industrial zones. Tomorrow ports. Eventually urban centers."
Before Subramaniam could respond, Karan spoke—not interrupting, but inserting clarity.
"The boundary is not geographic," he said calmly. "It is functional."
That shifted attention toward him.
He continued without raising his voice.
"A steel plant producing at scale is not a local asset. It feeds rail, construction, defense manufacturing. If it stops, the effect is not contained within a district."
He let the logic build without emphasis.
"State policing is designed for law and order. Crime response. Public control. Industrial continuity requires a different structure—predictable, embedded, and aligned with production cycles."
Mohan Kumaramangalam nodded slightly.
"We've already seen the gaps," he added. "Local interference in logistics. Labor disputes escalating without containment. Delays that extend beyond the plant itself."
Chavan didn't dispute the examples.
"That is administrative failure," he said. "Not justification for structural override."
Karan didn't dismiss the point.
"It begins as administrative failure," he replied. "It becomes structural when response time cannot match consequence."
Jagjivan Ram joined in, his tone measured.
"If CISF is given policing authority, we create overlap. A crime inside a zone—who investigates? CISF or the state?"
Subramaniam answered.
"Primary authority lies with CISF within notified zones. State police enter through defined coordination protocols."
Jagjivan Ram frowned slightly.
"That is not coordination. That is restriction."
Karan responded, not defensively, but precisely.
"It is restriction," he said. "But it is limited to high-output zones where delay has cascading impact."
Chavan tapped the table lightly.
"And who defines 'high-output'? Ministries change. Priorities shift."
Subramaniam answered this time with more structure.
"Designation will be based on measurable criteria—output volume, strategic classification, supply chain centrality. It will not be discretionary."
Indira interjected, sharpening the point.
"It will not be discretionary," she repeated. "Because if we centralize authority, we also centralize accountability."
She looked directly at Subramaniam.
"I want thresholds. Not descriptions. Numbers that cannot be interpreted differently by different governments."
Subramaniam nodded.
"That will be formalized."
Indira shifted her attention back to the room.
"Why CISF?" she asked. "Why not expand state industrial units or create a new structure?"
Karan answered immediately.
"Because CISF already operates inside industrial environments," he said. "Their training is aligned with infrastructure protection, not public policing."
He broke it down in practical terms.
"Access control. Shift-based deployment. Internal perimeter security. Coordination with plant management. These are not add-ons—they are core functions."
He paused briefly.
"Most importantly, consistency. Industrial systems cannot operate if security protocols vary across districts."
Kumaramangalam added,
"And unlike private security, CISF operates under national command. That gives uniformity."
Jagjivan Ram leaned back.
"So the objective is standardization across industrial zones."
Karan nodded.
"At scale, standardization becomes efficiency."
Chavan shifted the discussion.
"This expansion will require manpower. Training. Infrastructure. Have we calculated the cost?"
This time, Karan opened his file.
"Yes," he said.
He didn't read from it. He summarized.
"Initial expansion will require phased recruitment. But the cost must be evaluated against loss prevention, not expenditure alone."
Chavan looked at him steadily.
"Quantify that."
Karan didn't hesitate.
"A three-day shutdown in a major steel facility costs more than annual CISF deployment for that zone. Not in accounting terms—in downstream impact."
He continued, keeping it grounded.
"Delayed rail production. Construction slowdowns. Defense supply chain gaps. These are not isolated costs."
Chavan absorbed that, but didn't concede.
"And personnel conditions?" he asked. "CISF is not currently structured for this scale."
That was expected.
Subramaniam responded, but Karan continued the chain.
"This amendment cannot be limited to authority," Karan said. "It must include structural reform within CISF itself."
Indira's eyes narrowed slightly—not in disagreement, but in focus.
"Specify."
Karan spoke without shifting tone.
"Revised salary structures aligned with operational risk. Defined shift rotations to prevent fatigue. Housing within or near industrial zones to reduce transit delays."
He continued, methodically.
"Technical training specific to industrial environments. Equipment upgrades. Clear career progression to retain experienced personnel."
There was no rhetoric in his voice.
Just inevitability.
"If we expand responsibility without improving conditions, the system will fail from within."
Jagjivan Ram nodded slowly.
"That is a valid concern," he said. "Fatigue alone can compromise security."
Chavan added,
"And morale affects discipline. That cannot be ignored."
Indira leaned back slightly, processing the full scope now—not just authority, but sustainability.
"So this is not just a CISF amendment," she said. "It is a restructuring of industrial security as a national function."
Karan didn't respond immediately.
Then—
"Yes."
The room settled into that answer.
Not because it was dramatic.
Because it was complete.
Indira closed the main file.
"Then we proceed with clarity," she said.
She began outlining the decision, point by point.
"The CISF mandate will be expanded to cover all notified Special Economic Zones and critical industrial areas."
"No ambiguity in jurisdiction. Within these zones, CISF will hold primary operational authority."
"State police access will be restricted but not removed—coordination protocols will be defined clearly."
"Designation of zones will be based on measurable industrial criteria, not administrative discretion."
She paused, then added the part that had shifted the conversation.
"And CISF itself will be restructured. Compensation, working conditions, training, and infrastructure will be upgraded to match responsibility."
She looked around the table.
"This is not negotiable. If we expect continuity of production, we must ensure continuity of those who protect it."
Chavan gave a small nod.
"That addresses financial and structural concerns," he said. "With defined thresholds, the expansion remains controlled."
Jagjivan Ram added,
"And with proper training and conditions, operational risk is manageable."
Subramaniam closed his file.
"The Ministry will finalize the amendment draft accordingly."
Indira gave a single nod.
"Do it."
There was no need for a formal vote.
The decision had already aligned.
As the meeting began to dissolve, the implications moved faster than the paperwork.
For the first time, industrial zones in India would not depend on local administrative capacity for continuity.
They would operate under a unified security structure.
Production would no longer negotiate with disruption.
It would be insulated from it.
And across ministries, states, and industries, one shift became clear—quietly, without announcement.
India was no longer just building capacity.
It was beginning to protect it with intent.