Consolidating the IT functions into one company, and listing on the TSE (2001)
A function that became saleable by being put back into one company
Sales to the parent, which had accounted for eighty per cent at the outset, had fallen to sixteen — that single point is what made the 2001 re-consolidation and the following year’s listing possible. Putting four separate companies back into one, and taking over even the upstream functions still held by the parent, was done less to tidy the organisation than to create a company that could accept cross-industry contracts through a single window. It can be seen as a judgement that experience in building systems which must not stop a steel mill would carry over to a bank’s core accounts and to a retailer’s order processing.
Yet it took thirteen years to reach the ¥200 billion in sales the company had set out, and on the day of listing the share price fell below the offer price. The market did not immediately reinterpret an origin as a steel group’s IT subsidiary. That a proposal to drop “Nippon Steel” from the company name was rejected shows that the credit of the parent was chosen over the banner of independence. Compared with the other blast-furnace makers, which handed their IT subsidiaries to IBM Japan in the same period, the road diverged; but the gap between the speed of going to market and the slowness with which the valuation settled expresses the difficulty of the user-affiliated systems integrator as a business form.
Revenue and net margin, FY1996–FY2006
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2001 onwards — after it was taken.
Source: securities reports
Read the full dossier in Japanese →
The Japanese edition carries the complete record of this decision — the situation that forced it, the options weighed, what actually followed, and the sources behind every claim.
Yen amounts are converted at the average rate of each figure’s own year — not today’s rate; the revenue chart is shown in yen. Exchange rates & sources — the full ¥/US$ table →
Disclaimer
- This page is provided for general information only and is not investment advice, nor a recommendation to buy or sell any security.
- Figures are compiled independently and include our own estimates, approximations and machine-processed data; we make no warranty as to their accuracy or completeness.
- Sources are primarily each company’s securities reports and other public filings, but errors and omissions may remain.
- Any use of this information is at the reader’s own risk. Past performance does not indicate future results.
- Company names, logos and other marks belong to their respective owners.
Data API
NS Solutions’s history, financials, executives and
shareholders are published as static JSON — no key, plain GET.
Full specification →
| Method | Endpoint | Returns |
|---|---|---|
| GET | /api/companies.json | All companies |
| GET | /api/2327/manifest.json | Resource index |
| GET | /api/2327/history.json | History overview |
| GET | /api/2327/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/2327/decisions.json | Management decisions (index) |
| GET | /api/2327/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/2327/executives.json | Executives |
| GET | /api/2327/shareholders.json | Major shareholders |
| GET | /api/2327/financials.json | Financial statements |
| GET | /api/2327/financials-longterm.json | Long-term results |
| GET | /api/2327/segments.json | Business segments |
| GET | /api/2327/regions.json | Sales by region |
| GET | /api/2327/workforce.json | Workforce |