Tidal and Wave Energy Editing and Proofreading Services

A device has run in the water for eleven months and produced power. This is a genuine achievement and it is also a very long way from an array of forty machines surviving twenty-five winters with a maintenance vessel that can only reach them on nine days a month. The gap between those two things has consumed most of the money this sector has ever raised, and it is usually described in documents that do not distinguish between them.

We edit what tidal and wave energy developers produce — technology readiness and development stage documentation, test programme reports and performance data, investor and grant funding applications, technical risk registers and mitigation plans, array design and scaling documentation, operations and maintenance concepts and access documentation, consenting and environmental submissions, survivability and design condition documentation, offtake and revenue support applications, supply chain and fabrication documentation, and stakeholder and community information for test and array sites. Our editors work on the distance between a prototype and a farm.

Technology readiness claims are where this sector's credibility is spent, and the failure is describing what a device has done in terms that imply what a fleet would do. A prototype that achieved a high capacity factor during a summer test has demonstrated something real and much narrower than the sentence usually says. We work through these so every performance figure carries the conditions and the duration that produced it, since eleven months including one winter and eleven months including three are different claims; so the readiness level is stated against the whole system rather than the part that is furthest advanced, because a mature turbine on an unproven foundation with an unproven connection is not a mature system; so scaling assumptions are made explicit, given that the step from one device to an array introduces wake interaction, shared infrastructure and a maintenance concept that a single machine never tested; so the access and maintenance concept is described with the weather windows it depends on, as availability in this sector is an offshore logistics problem more than an engineering one; so failures and retrievals are reported with what was learned, because a developer who publishes them is the one investors believe about everything else; and so survivability is described against the design condition and what has actually been experienced. Documents written this way get funded by people who understand what they are funding.

Everything you send is treated in confidence, including test data, designs and funding applications. We are editors rather than marine energy engineers or investment advisers, and we offer no view on technology, performance or readiness. What we can do is keep the prototype and the array clearly distinguished.