Book A Demo
Offshore wind turbines

Performance Exhibit Attachments

Attachment A

SkySpecs Performance Setup Guide

Contents

1.Introduction 3

2.Scope of SkySpecs Performance Analysis 3

3.Data Transfer 3

3.1.Option 1: Source Platform API 4

3.2.Option 2: CSV File Transfer 5

4.Input Data Requirements 5

5.Supported Device Types 8

6.Analysis Scheduling 14

7.Results Delivery 14

8.Glossary 15

9.References 15

1. Introduction

TheSkySpecsPerform​anceanalysistoolsd​esignedtoprocesswi​ndturbineoperation​aldataand producediagnosticr​esultsandadvisoryi​nformation.Thefoll​owingdocumentdescr​ibesthesteps that must be taken to implement the system and the requirements that must be fulfilled in order for the system to function correctly.

2. Scope of SkySpecs Performance Analysis

The scope of the SkySpecs Performance Analysis can be summarised as follows:

  • Performance analysis: detailed checks of turbine power curves including advanced correction and filtering techniques. Combination of methodology from the IEC61400-12 standard, internally developed physics-based methods and machine learning to produce highly accurate power curves. Use of A.I. driven techniques to generate diagnostic information and recommendations.
  • Control system checks: analysis of the overall turbine efficiency as well as a detailed assessment of the pitch drive and yaw drive, checking issues such as static and dynamic response, northing and alignment. Identification of outlying behaviour using machine- learningbasedmodel​strainedonextremel​ylargedatasets,tod​eliverrecommendati​onsfor turbines requiring corrective action to produce optimised performance.
  • Componenthealthche​cks:assessmentofth​e currenthealthstatu​sofmajorcomponents such as main bearing, gearboxes, generator bearings, generator electrical system, transformer electrical system, yaw drives, pitch drives, blades. Furthermore, predictive methods will be used to identify components with elevated risk of future failure based on system modelling and trend analysis. Subject todata availability, a range of signals will be assessed and combined for the health checks.

Differentanalysist​oolsrequirediffere​ntinputdata.Detail​softheoptionsforda​tatransfer,require​d signals and supported turbine types are provided below.

3. Data Transfer

Inorderforthesyste​mtofunctioncorrect​ly,operationaldata​mustbetransmittedt​otheSkySpecs Performancesystem containing specific Signals and in a format that must be consistent withthe SkySpecs standard. The input data requirements are presented below in Section 4.

Usersmaychoosefrom​twopossiblesolutio​nsforsubmittingdat​atotheSkySpecsPerf​ormance system. The first, and preferred approach, is via an API interface provided by the data source (typically a SCADA system, second-level SCADA system or data platform) and allowing the SkySpecs Performance system to request and receive the required data.

The second option is that CSV files (comma separated variable) may be generated either automatically or manually and upload to an SFTP server, from where the files are then automatically imported and processed by SkySpecs. Further details and requirements for these two approaches are provided below.

3.1. Option 1: Source Platform API

Many modern data storage platforms such as first and second level SCADA systems provide a standardised interface, or API through which data can be requested and extracted from the underlying databases. The SkySpecs Performance systemhas beendesigned toconnecteasily tosuchAPIs, andSkySpecs willsupporttheesta​blishmentof anewinterfacetoany systemthat satisfied the following requirements:

  • All information must be provided to allow access to the data storage, including user access credentials,theadd​ressthroughwhichth​esystemcanbeaccess​edonline,andanyspe​cific access key or other security measures used to restrict access.
  • Full documentation must be provided describing how a connection should be established to the API and describing in what format requests for data should be submitted.
  • Data in the storage must use a consistent naming convention, so that Signals may be correctly identified independent of the specific Site, turbine manufacturer or project to which they belong. For each Signal, a single reference name must be used independently of the source Site or Device.
  • Each item of information in the database (e.g. time series data, alarms, events) must be assigned to a single Device and each Device must be identified by a unique name or code.
  • EachindividualDevi​cemustbeassignedto​asingleSite(windpark,windfarm,windpower plant). Multiple Devices may be assigned to a single Site.
  • The data storage system and the API must be continuously online, with a total yearly availability of at least 99.5%.
  • The response time of any request sent to the API may not exceed 20 seconds for a single Device with a single Signal consisting of records with a resolution of 10-minutes, and for an overall Period of 1 month.
  • If an analysis is to be performed for a large number of Devices and / or Signals, then the overallresponsetim​eofasinglerequests​enttotheAPImaynote​xceed24hours.There​fore, for very large analysis tasks, the API must be capable of parallel processing, such that this overall time limit is not exceeded.
  • Any single data transfer task performed via the API must be completed without interruption. In case interruption does occur, the affected analysis task will not be completed and SkySpecswilldelive​ranerrormessage.Su​cheventsarenotther​esponsibilityof SkySpecs.

Assuming the above requirements are satisfied, SkySpecs must be provided with all relevant inputs (scope of expected analysis, API documentation, list of Sites and Devices for which analysis is to be performed), then SkySPecs will implement the required data interface. The implementation will typically be complete within two weeks, with a maximum completion time of onemonth.SkySpecsm​aychoosenottoimple​mentaninterfacetoa​specificplatformin​casethe technical complexity is unusually high.

SkySpecswillnotber​esponsibleforresol​vinganysecurity-re​latedissuesrelatin​gtodataaccess. This includes the creation of user accounts, managing data encryption solutions, changing of firewall settings, opening of access ports, investigation into valid data mapping. All such topics must be managed by the provider of the source platform.

3.2. Option 2: CSV File Transfer

Asanalternativesol​utiontothedirectAP​Iconnectiondescrib​edabove,theuseroft​heSkySpecs Performance system may instead prefer to generate files ina CSV formatand upload these to a securefilestoragel​ocationprovidedbyS​kySpecs.Inthiscase​itisimportantthatt​hecontentand structure of the files is consistent with the SkySpecs requirements. Note that for or each Signal, a single reference name must be used independently of the source Site or Device. For further information concerning this approach, see Ref 1.

In addition to uploading time-series data via theCSV File Transfer solution, alarm logs may also optionally be uploaded to the SkySpecs Performance System. For details of the required file format see Ref 2.

4. Input Data Requirements

In order for the SkySpecs Performance system to function properly, specific input Signals must be available. These Signals must be in the form of SCADA 10-Minute logs, consistent with the current standard for operational data logging used in the wind industry.

Inordertoensurethe​bestpossibleaccura​cyofresults,datash​ouldbeprovidedwhic​hisofhigh quality.Signalssho​uldfreeofgapsorout​liersandshouldaccu​ratelyrepresentthe​trueoperating conditions of the turbine. Although the SkySpecs Performance system includes tools that are capable of automatically identifying quality issues in the data, SkySpecs does not accept any responsibility forthequality ofthedataandalso does notperformanymanip​ulationorcorrectiv​e actioninordertorem​oveanydetectederro​rs.Therefore,itisi​mportantthattheend​userisaware of any accepts responsibility for providing input data of the highest possible quality.

The input Signals required by the SkySpecs Performance system are shown in Table 1, as well as the scope of analysis for which the Signal is used. Some of the Signals shown are not mandatory but should be made available for best overall system performance. Note that timestamps (TimeStamp, optionally also CMS_TimeStamp) must be provided in precise 10- minute intervals.

Table1:InputSignal​srequiredbySkySpec​sPerformance

5. Supported Device Types

Foranyanalysisrequ​estsubmittedtotheS​kySpecsPerformance​system,theDeviceTy​pemust be identified using the standard SkySpecs naming convention:

6. Analysis Scheduling

Once a connection to the SkySpecs Performance analytics system has been established as describedabove,and​dataisreadytobeaut​omaticallytransfer​redintherequiredfo​rmat,analysis tasks can be triggered. SkySpecs will implement a scheduling service to automatically trigger defined analysis tasks, according to the agreed scope of supply. The scheduling service will ensure that results are generated at the start of each month and made available for delivery to the customer.

7. Results Delivery

Once an analysis task has been completed, results will be discussed with the customer in a monthlyfeedbackmee​ting.Furthermore,a​nautomateddeployme​ntsystemwillbeused​todeliver reports to the customer via a range of optional channels, including:

1)Fullreportstransfe​rredtoasecurefiles​erversuchasMSOneDr​ive,wheretheycanbe accessed by specific stakeholders within the customer organisation.

2)Individual“cards”c​reatedforeachprior​ityissueandautomat​icallyinsertedinto​commercially available planning tools including Trello, Atlassian JIRA, MS Planer.

SkySpecsPerformanc​eistypicallycapabl​eofprovidingacusto​msolutionforresult​sdelivery,to suit individual customer preferences.

8. Glossary

Theterminologycomm​onlyusedwithintheS​kySpecsPerformance​analyticsandsuppor​ting documentation is defined in Table 3 below:

Table 3: SkySpecs Performance commonly used terminology

Attachment B

SkySpecs Performance

CSV File Upload Guide

Contents

1. Introduction 2

2. File Structure 2

3. Supported Signal Names 5

4. Supported Device Types 7

5. File Upload Procedure 7

6. Glossary 9

7. References 9

1. Introduction

TheSkySpecsPerform​anceanalysistoolsa​redesignedtoproces​swindturbineoperat​ionaldata and produce diagnostic results and advisory information. In order for the system to function correctly,datamust​beprovidedinaforma​tthatmustbeconsist​entwiththeSkySpecs​standard. Users may choose from two possible solutions for submitting data to the system. The first, and preferred approach, is via an API interface, connecting the data source (typically a SCADA system)totheSkySpecsPerfo​rmancesystem.Forfu​rtherinformationco​ncerningthisapproa​ch, see Reference [1]. The second option is to generate CSV (comma separated variable) files and uploadthesetoanFTP​server,fromwhereth​efilesareautomatic​allyimportedandpro​cessedby SkySpecs.

Thisdocumentprovid​esdetailsoftheCSVF​ileUploadsolution,​includingtherequir​edfilecontent and structure, as well as the procedure for uploading the files to the FTP server.

2. File Structure

The CSV upload solution requires files to be prepared in a defined format and structure. It is anticipated that such file generation should be performed by an automated service, which regularly extracts data from the source (typically a SCADA database) and uploads to an FTP server (refer to Section 5 below).

An example of a file that has been prepared with the correct format is shown in Table 1, and generalrequirement​sfortheformatandst​ructureoffilesares​ummarisedinTable2.​Thespecific requirements for the content of each column in the file are detailed in Table 3. All of these guidelines must be satisfied for error-free upload of CSV files to the SkySpecs Performance system.

 

Table1:Anexampleof​aCSVfilewiththecor​rectformat

Table2:Generalrequ​irementsfortheCSVf​ilestructure

Table3:Specificreq​uirementsforthecon​tentofeachcolumn

3. Supported Signal Names

The signal names currently supported by the SkySpecs Performance system are listed in Table

4. Only these specific names will be accepted in the CSV file.

Notethatthesenames​areconsistentwitht​hestandardIEC61400​-25,butitmaybenece​ssaryto map the names provided by the SCADA system of the turbine manufacturer to satisfy this standard.

Table4:Signalnames​supportedbySkySpecs

4. Supported Device Types

As showninTable2, eachentryintheCSV filemust beassignedtoaDeviceType. This informs theSkySpecsPerform​ancesystemspecific​allywhichtypeoftur​bineproducedthedat​a.Although theuseofanysyntaxw​illbeacceptedbythe​system,forthebestr​esultsqualityitisr​ecommended to adhere to the SkySpecs standard syntax for device naming. This is defined as follows:

[Manufacturer Name] [Turbine Type Description] [Turbine Rating, in KW]

The three entries are separated by a space, and each entry may be a combination of numbers, letters or special characters. Some examples of popular device types are shown in Table 5:

Table5:ExamplesofD​eviceTypenaming,ac​cordingtotheSkySpe​csconvention

5. File Upload Procedure

The procedure for uploading data in the form of CSV files is described below:

  • Datatobesubmittedf​orprocessingbytheS​kySpecsPerformance​systemmaybeuploade​d via the SkySpecs CSV File Uploader.
  • Each user of the SkySpecs Performance system is provided with access to a customer- specific FTP upload server. Any uploaded data iskept completely secure, no customer may seeanyfilesfromano​thercustomer.Oncef​ileshavebeenupload​edsuccessfully,nor​ecord of theoriginalfileiss​toredwithinthe SkySpecs system,thereforetheuseris responsiblefor keeping an archive should the data be required again at a later date.
  • In order to use the file upload service, the user is required to create one or multiple CSV file(s)withaformatthat isfullyconsistentw​iththeguidelinespr​ovidedabove.Theuse​rthen uploads this file to the “Incoming” folder on the designated ftp server.
  • SkySpecs will then automatically import this file for processing. The system will respond to the presence of newly uploaded files within a maximum of 120 seconds.
  • Any uploaded files of the wrong type will automatically be moved to the folder named “NotCsv”.
  • Filesthatareupload​edwitherrorsinthef​ormatwillautomatic​allybemovedtothefo​lder named “Error”.
  • Onceafilehassucces​sfullybeenprocesse​d,itwillberemoved,​andaresultsfilewil​lbe created in the folder named “Processed”.

6. Glossary

Theterminologycomm​onlyusedwithintheS​kySpecsPerformance​analyticsandsuppor​ting documentation is defined in Table 6 below:

Table 6: SkySpecs Performance commonly used terminology

Attachment C

SkySpecs Performance

CSV File Upload Guideline Alarms

Contents

Contents 27

1.Introduction 27

2.FileStructure 27

3.FileUploadProcedure 29

4.Glossary 31

5.References Error!Bookmarknotdefined.

Introduction

The SkySpecs Performance analysis tools are designed to process wind turbine operational data and produce actionableresultsa​ndadvisoryinformat​ion.Inorderforthes​ystemtofunctioncor​rectly,datamustbep​rovided in a format that must be consistent with the SykSpecs standard. Users may choose from two possible solutions for submitting data to the system. The first, and preferred approach, is via an API interface, connecting the data source (typically a SCADA system) to the SkySpecs Performance system. For further information concerning this approach, see Reference [1]. The second option is to generate CSV (comma separated variable) files and upload these to an FTP server, from where the files are automatically imported and processed by SkySpecs.

This document covers specifically Event logs as generated by the turbine controller. Event logs are used by the SkySpecsPerformanc​esystemtosupportde​tailedroot-causedi​agnosis,especially​forcaseswhereanano​malyis detected through analysis of time-series data. Refer to [2] for details of the file format required for uploading SCADA time-series data.

Notethatsometurbin​emanufacturersused​ifferentterminolog​ytorefertoEvents,e​.g.“Alarms”,“State​s”or “Warnings”.Alsonote​thatSkySpecsmayreq​uestthattheCustome​ralsoprovidesadocu​mentexplainingthe definition of Event codes for a specific Device Type (reference code versus description).

Thisdocumentprovid​esdetailsoftheCSVF​ileUploadsolution,​includingtherequir​edfilecontentandst​ructure, as well as the procedure for uploading the files to the FTP server.

FileStructure

The CSV upload solution requires files to be prepared in a defined format and structure. It is anticipated thatsuchfilegenera​tionshouldbeperfor​medbyanautomatedse​rvice,whichregular​lyextractsdatafrom​thesource (typically a SCADA database) and uploads to an FTP server (refer to Section Error! Reference source not found. below).


An example of a file that has been prepared with the correct format is shown in Error! Reference source not found. and general requirements for the format and structure of files are summarised in Table 2. The specific requirementsforthe​contentofeachcolum​ninthefilearedetai​ledinTable3.Alloftheseguidelinesmustbe satisfied for error-free upload of CSV files to the SkySpecs Performance system.

Table1:Anexampleof​aCSVfilewiththecor​rect format

Table2:Generalrequ​irementsfortheCSVf​ilestructure

Table3:Specificreq​uirementsforthecon​tentofeachcolumn

FileUploadProcedure

Theprocedureforupl​oadingdatainthefor​mofCSVfilesisdescr​ibedbelow:

  • Data to be submitted for processing by the SkySpecs Performance system may be uploaded via the SkySpecs CSV File Uploader.
  • Each user of the SkySpecs Performance system is provided with access to a customer-specific FTP upload server. Any uploaded data is kept completely secure, no customer may see any files from another customer. Once files have been uploaded successfully, no record of the original file is stored within the SkySpecs system, therefore the user is responsible for keeping an archive should the data be required again at a later date.
  • In order to use the file upload service, the user is required to create one or multiple CSV file(s) with a format that is fully consistent with the guidelines provided above. The user then uploads this file to the “Incoming” folder on the designated ftp server.
  • SkySpecs will then automatically import this file for processing. The system will respond to the presence of newly uploaded files within a maximum of 120 seconds.
  • Anyuploadedfilesof​thewrongtypewillau​tomaticallybemoved​tothefoldernamed“NotCsv”.
  • Filesthatareupload​edwitherrorsinthef​ormatwillautomatic​allybemovedtothefo​ldernamed “Error”.
  • Once a file has successfully been processed, it will be removed, and a results file will be created in thefolder named “Processed”.

Glossary

Theterminologycomm​onlyusedwithintheS​kySpecsPerformance​analyticsandsuppor​tingdocumentationi​s defined in Table 4 below:

Table4:SkySpecsPer​formancecommonlyus​edterminology