Are efforts to integrate components actively or passively hampered by the supply industry?
By Ryan Skinner (email)
In the first four parts of this series, we studied how software integration issues were hindering progress in, among other areas, environmental improvements to shipping, and looked at a few avenues for addressing these issues.
These efforts to drive shipboard systems into a common framework are, however, not gaining wider traction in the industry yet. Equipment suppliers are loath to embrace an arrangement in which shipowners could more easily switch out their systems with competitors', or seek service or spare parts from third parties. For many suppliers, the ability to offer competitive prices comes at the cost of proprietary systems and vendor lock-in. The suppliers themselves, however, characterize the lack of a common framework as the unavoidable outcome of a fragmented industry.
As for the shipyards, most if not all lack the sophistication to push for ship-wide integration of systems; they do not have the in-house software engineering experience, and therefore the desire, to drive all of their suppliers into a common software architecture. "The shipyards are like LEGO brick-builders; they just put the pieces together. If you're going to ask them to integrate all of the systems, you're going to have to consider paying a lot more for your ship," said Arnesen. He confirms, however, that Wilhelmsen is currently negotiating with shipyards, which are suddenly more pliant and willing in the recession, to address these kinds of software architecture issues.
Some question whether an open architecture would lead to security and safety risks, as faults in one component could spill over into a ship-wide problem. Fagerhus responded to this concern with exasperation: "It's a common complaint, but these same suppliers often won't offer warranties on software faults in their own systems. So it's specious for them to express fears of other components contaminating their products." Further evidence dispelling the safety argument is the use of open software architecture in the US Navy and much of the process industry.
The conclusion of this development cannot be foretold, but one thing is certain: Increasing costs and complications, coupled with demands to environmental performance, will force a harmonization in the software systems running merchant ships. What remains is a power struggle over who will establish the nature of that harmonization: a coalition of owners, a few large suppliers, regulators or a gaggle of idealistic engineers?
For more details and interviews on the subject of a common software framework in the marine industry, follow this blog, where posts will continue to explore the topic.
Comments