Exhibit_B-_Laboratory_Report_File_Specification_LabSync_2.0_(flat_file_).pdf

EXHIBIT “B”

Laboratory Report File Specification LabSync-2.0 (flat file)

October 2018

Laboratory Report File Specification LabSync_2.0 (flat file)

Linko Technology Inc.

1999 Broadway Suite 830 Denver, CO 80202

Tel: 303-275-9968 Fax: 303-275-9949

Toll Free: 1 877-546-5699 support@linkotechnology.com www.linkotechnology.com

Linko Laboratory Report File Format LabSync_2.0

© Linko Technology Inc.

3/1/2016

Contents

Laboratory Data Report File Format: LabSync_2.0 General Concepts

Updating Report Data File Format File Name

LabSync Process Overview Components Implementation Steps Workflow Summary Information to be Provided to LIMS Data Provider Field Definitions

Optional Fields Lab Sample Event Type Reporting Limit (RL) and Method Detection Limit (MDL) Valid Result Values Mass Base Result Calculations Lab Status

Error Checking on FTP upload Proprietary Information Example Failure and Success Emails Example Fields and Sample Files

3/1/2016 page 1

Laboratory Data Report File Format: LabSync_2.0

File Version: 2.0 Description: A simple pipe delimited ASCII flat file representing one report containing any number of samples

General Concepts A file represents a “report”, analogous to paper reports that would traditionally be supplied to a client. As such, only one client can be identified in each report file.

A report can contain any number of samples, any number of different analyte tests per sample, and can contain results for different sampling locations or labs.

Each line in the file represents one analyte test result in its entirety, and although there is no interdependence between the lines of a file, several of the fields will by necessity be identical in each line.

Updating Report Data A report file can contain data that has not been previously reported or data that has changed since a previous report was submitted.

Each analytical result value can be designated as “Approved” or “Not Approved”.

If nothing is specified, “Approved” is assumed. “Not Approved” represents preliminary findings and are reviewed and emailed (not inserted to the compliance system) where as “Approved” means the findings are final.

Data cannot be deleted from a report file after the file is submitted. The data must be deleted using the LinkoCTS software.

If a result value is being sent as an updated result, the LabReportedDate is required.

File Format ASCII file Fields delimited with the pipe “|” character Any optional fields left empty must be fully delimited (eg. "||") with the exception of the last field which will be accepted with or without a trailing delimiter.

End of line character is carriage return/line feed

File Name Extension must be “txt” No requirements for file naming, but the use of a unique file name is recommended (e.g. YourLabAbbrv_20150115.txt).

File name must be less than 255 characters including the .txt extension. It is also advisable to keep the name as short as possible.

3/1/2016 page 2

LabSync Process Overview

Linko LabSync software provides the automatic import of lab analysis data from a LIMS into the Linko client/server software. LabSync may also create COCs and export those to LIMS for auto-login – this is outlined in a separate document.

Components

The LabSync Lab Data Upload consists of the following components.

1. LIMS Database – the Laboratory Information Management System that stores the sample analysis performed by the Lab

2. FTP Server – the server that accepts uploaded Lab Data Files that are to be parsed and available for LabSync to process. Lab process ends after this step.

3. CTS_LIMS - a new database we create to hold the data sent by the LIMS; as well as related configuration information

4. CTS_Data – the Linko database that stores all analytical results and related data and performs the LabSync processing

Implementation Steps

Here is the basic workflow for implementing the LabSync Lab Data Upload for a Linko customer.

1. Linko sends required information (clientID, labID, and FTP credentials) to LIMS data provider.

2. Lab creates test file and provides to client or Linko Implementation Specialist.

3. When format is confirmed, client uploads two test files (one with valid data and one with invalid data) to FTP.

4. Lab automates process for data export and FTP transfer.

3/1/2016 page 3

Workflow Summary

Here is the basic workflow for using the LabSync Lab Data Upload for a Linko customer.

1. Work order, COC, and sample is received at lab.

2. Lab enters analytical results.

3. Optional: lab results are sent to Linko as not approved.

a. Data is not imported; it is only reviewed for priority and email notices are sent to client/user.

b. Lab will receive confirmation email or failure email notice

4. Lab results are validated and sent to Linko.

a. Lab will receive confirmation email or failure email notice

Information to be Provided to LIMS Data Provider

1. Implementation Instructions: (this document).

2. Data Examples: (Excel template and txt files).

3. FTP Credentials: ftp address, username and password..

4. ClientID: Static value to be included in each record to indicate the Lab’s client ID for

Linko reference.

5. LabID: Static value to be included in each record to indicate the Lab’s ID for Linko reference.

6. Lab Successful/Failed Upload Email(s): Who at the Lab will get emails when FTP and

LinkoParser process a file. This is optional but recommended.

6/29/2023 page 4

Field Definitions The table following summarizes the report file field order, name, format, and purpose. Do not include field headings within the file.

Field Name Status Format Field Size Description Example Data

1) LinkoVersionNo Required Text 25 Assigned by Linko. This is the version number of this file format LabSync_2.0

2) LinkoClientID Required Integer Assigned by Linko to uniquely identify a client 333

3) LinkoLabID Required Integer Assigned by Linko to uniquely identify a laboratory 999

4) LabPermitMPID Required Text 250

A unique identifier for the location from which the sample was taken, such as the Industry Name and Monitoring Point. Linko Industries - MP001

5) LabSampleName Required Text 50

Sample name, this could refer to one or more Lab Sample IDs, it represents the Client’s Sample Event or Sample ID, commonly it is the LIMS lab Sample ID 20131130

6) LabDateSampled Required Date* Date of sample collection.

Format must be mm/dd/yyyy. 12/05/2013

7) LabStartDateTimeSampled Optional Date/Time* Date and time sample collection was started.

Format must be mm/dd/yyyy hh:nn:ss AM/PM 12/04/2013 3:00:00 PM

8) LabStopDateTimeSampled Optional Date/Time* Date and time sample collection was completed.

Format must be mm/dd/yyyy hh:nn:ss AM/PM 12/05/2013 3:00:00 PM

9) LabSampleID Optional Text 50 Lab Sample Name - typically the SampleID from

LIMS 20131130-001

10) LabSampleEventType ~ Optional Text 50 The type of sample to be created in Linko; such IU_SAMPLE or AUTH_SAMPLE AUTH_SAMPLE

11) LabCollectMethod Optional Text 50 Sample Collection Method Grab

12) LabSampler Optional Text 254 Person or Entity who collected the sample from the sampling point CGW

6/29/2023 page 5

13) LabAnalysisDate Optional Date/Time* Date and/or date and time sample was analyzed by the lab

12/11/2013

- or -

12/11/2013 3:00:00 PM

14) LabAnalysisMethod Optional Text 50 EPA analysis method – as found in LIMS EPA200.7

15) LabParamName Required Text 254 Analyte/Pollutant compound name – as found in LIMS, no pre-system mapping required. Copper

16) LabResult Required Text 50 Analytical Result (includes "ND", "NA", "<200") See Valid Result Values below 0.1

17) LabNumResult Optional Float Numeric equivalent of the LabResult; must be a number 0.1

18) LabResultFlag Optional Text 50 Lab flag which qualifies LabResult field "J", "<", etc.

19) LabResultUnits Required Text 50 Units of measure for Result, RepLim & MDL mg/L

20) LabRepLimit Optional Text 50 Reporting Limit for LabParamName - see discussion below 0.001

21) LabMDL Optional Text 50 Method Detection Limit - see discussion below 0.0005

22) IsLabQCResult Optional Bit Whether the LabResult is a QC result (Blank) or not (use 1 for True or 0 for False) 1

23) LabReportedDate Optional Date/Time*

Date & Time the analysis was Reported or Approved by the Lab. Required if data provided is an updated value. 1/15/2014 9:45

24) LabSampleComments Optional Text 1000 Free form comments that show in the Sample Comments field in Linko

Comments about the sample

25) LabResultComments Optional Text 1000 Free form comments that show in the Result Comments field in Linko

Comments about the results

26) LabStatus Optional Text 50 Indicates if the data is approved by the lab and can be used in Linko Compliance calcs

Approved -or- Not Approved

* Linko LabSync can accept most U.S. date and datetime formats. The formats shown here are recommended.

6/29/2023 page 6

Optional Fields

It is strongly recommended that the data for the optional fields also be included if it is available.

Start/Stop date and collection method are often necessary for compliance review by the final users.

Lab Sample Event Type

This is used to identify the differences between Publicly Owned Treatment Works (POTW) Samples vs. IU Samples (Self-Monitoring Data). Sample data from POTW sampling OR sample data from IU sampling may be imported with Linko LabSync. These samples should be identified with different LabSampleEventType values. If not included, all samples will be imported with a default value assigned by the Client Administrator.

Reporting Limit (RL) and Method Detection Limit (MDL)

What is the difference between Reporting Limit (RL) and Method Detection Limit (MDL)?

The RL is the lowest concentration standard in the calibration range of each compound analyzed. This value is also the low limit for unqualified quantitative data. The MDL is determined via experimentation and verified through additional testing. This value represents the lowest concentration of each compound that can be qualitatively identified by the method in use. It is common that uploads will include data where RL equals MDL.

Valid Result Values

Linko LabSync will accept the following values for the Result field: 0.098 (any numeric value), ND (for non detect), NA (for not analyzed), >0.035 (where > is immediately followed by any numeric value - no spaces), <0.045 (where < is immediately followed by any numeric value - no spaces), IR (for Invalid Result), NF (for No Flow), MP (for Missing Parameter). Any other non-numeric values may be included in LabResultFlag, LabSampleComments or LabResultComments.

Mass Base Result Calculations

Linko LabSync can automatically calculate mass based results as long as you include a flow and flow units for that sample in the LIMS data.

Lab Status

Linko LabSync can notify you of Potential Violations before Lab data is finalized; approved for reporting. Having the Lab indicate a status of Approved tells LabSync that the data is final and ready to be imported as Samples and Results into the Linko software and then used in Compliance calculations. Indicating Not Approved tells LabSync the Lab data is preliminary but LabSync will still compare the analysis to Permit Limits and notify the user that a potential violation exists. Not Approved data will not be imported into the compliance system. The user can then ask the Lab to prioritize that sample analysis for final approval.

6/29/2023 page 7

Error Checking on FTP upload Upon receipt of a file, Linko examines it for errors. If errors are found, a descriptive email is sent to the email address configured during initial LabSync set up. Each line of the file is checked for the following items upon file receipt:

1. The required fields (as identified in the table above) must all be present and contain valid information. Optional fields can be provided at the Laboratory’s discretion, and left empty if not used.

2. The Linko LabID must be valid.

3. The LinkoClientID must be valid.

4. The LabResult field must be numerical or one of the allowable Valid Result

Values listed above.

5. The length of the text values must not exceed the lengths identified in the table above.

6. The data must be in the format specified in the table above. (i.e. a date must be a valid date in a supported format)

7. The file must not be blank.

8. The file must be an ASCII file format with a .txt extension

If a file contains errors in any line, the file will be rejected and no data is loaded into Linko. The file can therefore be corrected and resubmitted without concern for duplicating data in Linko.

Proprietary Information The Linko report file specifications is proprietary and may only be used by laboratories to submit client data to Linko. Use for any other purpose without written authorization from Linko Technology Inc. is prohibited.

Example Failure and Success Emails

6/29/2023 page 8

Example Fields and Sample Files The flat file is a .txt file matching a predefined format. Data elements are separated with pipe ( | ) characters. No header or columns names are present in the file. Even if a data element is not included, the | characters are required as placeholders where that data would have existed had it been present in the file.

Typical Example LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|03/05/2014 16:10|03/06/2014 16:10|20141130|AUTH_SAMPLE|Composite|CGW|1/3/2014|EPA 200.7.9.4|As|0.035|0.035||mg/L|0.01|0.005|0|1/5/2014|||Approved LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|03/05/2014 16:10|03/06/2014 16:10|20141130|AUTH_SAMPLE |Composite|CGW|1/3/2014|EPA 200.7.9.4|Cd|<.005|0.005||mg/L|0.01|0.005|0|1/5/2014|||Approved LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|2014/03/05 16:10|03/06/2014 16:10|20141130|AUTH_SAMPLE |Composite|CGW|1/3/2014|EPA 200.7.9.4|Cr Tot|0.8|0.8||mg/L|0.01|0.005|0|1/5/2014|||Approved LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|03/05/2014 16:10|03/06/2014 16:10|20141130|AUTH_SAMPLE |Composite|CGW|1/3/2014|EPA 200.7.9.4|Ni |.5012300|.5012300||mg/L|0.01|0.005|0|1/5/2014|||Approved LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|03/05/2014 16:10|03/06/2014 16:10|20141130|AUTH_SAMPLE |Composite|CGW|1/3/2014|EPA 200.7.9.4|pb|ND|0.01||mg/L|0.01|0.005|0|1/5/2014|||Approved LabSync_2.0|333|999|Linko Industries - MP001Linko Industries|20141130|03/05/2014|03/05/2014 4:10PM|03/06/2014 16:10|20141130|AUTH_SAMPLE |Composite|CGW|1/3/2014|EPA 200.7.9.4|ZN|1.2|1.2||mg/L|0.01|0.005|0|1/5/2014|||Approved LabSync_2.0|333|999|Linko Industries - MP001Linko Industries|20141130|03/05/2014|03/05/2014 4:10PM|03/06/2014 16:10|20141130|AUTH_SAMPLE |Grab|CGW|1/3/2014|Field|Field pH|7.3|||S.U.| ||1|1/5/2014|||Approved

Minimum Required Data Example LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|||| | | || |As|0.035|||mg/L|||||| LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|||| | | || |Cd|<.005|0.005|||mg/L|||||| LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|||| | | || |Cr Tot|0.8|0.8|||mg/L|||||| LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|||| | | || |Ni |.5012300|||mg/L|||||| LabSync_2.0|333|999|Linko Industries - MP001|20141130|03/05/2014|||| | | || |pb|ND|||mg/L|||||| LabSync_2.0|333|999|Linko Industries - MP001Linko Industries|20141130|||| | | || |ZN|1.2|||mg/L|||||| LabSync_2.0|333|999|Linko Industries - MP001Linko Industries|20141130|||| | | || |Field pH|7.3|||S.U.||||||