Who should join this training?

Freshers, maintenance engineers, electrical engineers, instrumentation engineers and working professionals can join this practical automation training.

Is corporate training available?

Yes. Softwell Automation provides customized corporate and in-plant automation training for industrial teams.

SQL Reporting Manual | Softwell Automation

P01

Softwell Digital Practical Manual

Practical 01 - Install SQL Server Express

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Install SQL Server Express and SQL Server Management Studio on the engineering laptop.

Done

STEP 02

Open SQL Server Management Studio and connect to the local SQL instance.

Done

STEP 03

Confirm the server name, authentication mode and connection status.

Done

STEP 04

Create a folder named D:\Softwell_Training\SQL_Reporting for scripts and exports.

Done

STEP 05

Save a screenshot or note of the successful connection for the practical record.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Install SQL Server Express.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Install SQL Server Express	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

SQL Server is installed, SSMS opens correctly, and the local SQL instance is ready for reporting work.

Talk to Automation Advisor

Get expert guidance for course selection, corporate training, project support and practical learning path.

Course GuidanceSelect the correct PLC SCADA, corporate, online or Industry 4.0 path.

Batch SupportGet schedule, duration, mode and prerequisite guidance.

Project AdviceDiscuss plant, automation, reporting or training requirement.

P02

Softwell Digital Practical Manual

Practical 02 - Create Training Database

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

In SSMS, right-click Databases and select New Database.

Done

STEP 02

Database name: Softwell_Reports.

Done

STEP 03

Keep default file locations unless your trainer gives a project server path.

Done

STEP 04

Click OK and refresh the database list.

Done

STEP 05

Expand Softwell_Reports and confirm Tables, Views and Programmability folders are visible.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Training Database.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Create Training Database	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Database Softwell_Reports is created and ready for table design.

Skills & Tools You Will Learn

Important automation skills are arranged for job-level, project-level and Industry 4.0 learning.

PLC ProgrammingLadder, SCL/ST, hardware, I/O mapping and troubleshooting.

SCADA / HMITags, screens, alarms, trends, scripts and reporting.

Industry 4.0 ToolsOPC UA, SQL Server, Python, dashboards and Excel/PDF reports.

P03

Softwell Digital Practical Manual

Practical 03 - Create Production Table

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Open a new query window on Softwell_Reports.

Done

STEP 02

Create table ProductionLog with columns ID, TimeStamp, MachineName, BatchNo, GoodCount, RejectCount and SpeedRPM.

Done

STEP 03

Execute the CREATE TABLE query.

Done

STEP 04

Refresh Tables and confirm dbo.ProductionLog exists.

Done

STEP 05

Open Design view and verify data types are correct.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Production Table.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Create Production Table	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

ProductionLog table is available with the required reporting columns.

P04

Softwell Digital Practical Manual

Practical 04 - Create Alarm History Table

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create table AlarmHistory with ID, TimeStamp, AlarmCode, AlarmText, Status and AcknowledgeUser.

Done

STEP 02

Set ID as an identity primary key.

Done

STEP 03

Execute the query and refresh Tables.

Done

STEP 04

Insert one test alarm record manually using an INSERT query.

Done

STEP 05

Run SELECT TOP 10 * FROM AlarmHistory to verify the record.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Alarm History Table.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Create Alarm History Table	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

AlarmHistory table stores timestamped alarm records correctly.

Why Choose Softwell Automation

Learn automation with practical examples, industrial troubleshooting approach and complete IT/OT learning path.

Industry Experienced TrainerReal plant examples and project based training.

Hands-on LearningPLC logic, SCADA, VFD, communication and reporting practice.

Flexible ModesOnline, classroom, corporate and in-plant options.

P05

Softwell Digital Practical Manual

Practical 05 - Insert Manual Test Records

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Prepare five INSERT statements for ProductionLog.

Done

STEP 02

Use different machine names, batch numbers and count values.

Done

STEP 03

Execute the script and confirm no SQL errors.

Done

STEP 04

Run SELECT * FROM ProductionLog ORDER BY TimeStamp DESC.

Done

STEP 05

Verify all manual records appear in the correct order.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Insert Manual Test Records.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Insert Manual Test Records	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Manual production records are inserted and visible in the report table.

Course Contents / Curriculum

The curriculum follows a practical sequence from fundamentals to project integration.

Level 01Basic PLC, wiring, addressing and ladder logic.

Level 02Advanced PLC, networking, SCADA and diagnostics.

Level 03OPC UA, SQL, Python, reports and IT/OT integration.

P06

Softwell Digital Practical Manual

Practical 06 - Import CSV Data

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create a CSV file with production columns matching ProductionLog.

Done

STEP 02

Use Import Flat File or BULK INSERT to load the CSV into SQL.

Done

STEP 03

Map CSV columns to table columns carefully.

Done

STEP 04

Run a SELECT query after import.

Done

STEP 05

Compare row count in SQL against the CSV row count.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Import CSV Data.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Import CSV Data	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

CSV production data is imported into SQL without missing rows.

Frequently Asked Questions About SQL Reporting Manual Database Reporting Practical Manual

Who can join this training?

Students, freshers, working engineers, maintenance teams and corporate plant engineers can join based on their requirement.

Is practical training included?

Yes. The training is focused on PLC, SCADA, HMI, VFD, communication, troubleshooting and project based practice.

Can I request online or corporate training?

Yes. Softwell Automation provides classroom, online, corporate and in-plant training options.

P07

Softwell Digital Practical Manual

Practical 07 - Create Shift Report View

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create a SQL view named vw_ShiftProduction.

Done

STEP 02

Group production by MachineName, BatchNo and shift date.

Done

STEP 03

Calculate TotalGood, TotalReject and TotalProduction.

Done

STEP 04

Execute the CREATE VIEW query.

Done

STEP 05

Select from vw_ShiftProduction and verify grouped output.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Shift Report View.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Create Shift Report View	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Shift production view summarizes raw production data into report-ready rows.

P08

Softwell Digital Practical Manual

Practical 08 - Daily Summary Query

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Write a query for today's production records.

Done

STEP 02

Use SUM for GoodCount and RejectCount.

Done

STEP 03

Calculate rejection percentage using a safe divide-by-zero expression.

Done

STEP 04

Order the result by machine name.

Done

STEP 05

Save the query as daily-summary.sql.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Daily Summary Query.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Daily Summary Query	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Daily summary query produces machine-wise production totals and rejection percentage.

P09

Softwell Digital Practical Manual

Practical 09 - Alarm History Report Query

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Write a query for alarms between two timestamps.

Done

STEP 02

Filter AlarmHistory by TimeStamp range.

Done

STEP 03

Sort by TimeStamp descending.

Done

STEP 04

Show AlarmCode, AlarmText, Status and AcknowledgeUser.

Done

STEP 05

Save the query as alarm-history-report.sql.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Alarm History Report Query.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Alarm History Report Query	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Alarm report query lists filtered alarm history with acknowledgement details.

P10

Softwell Digital Practical Manual

Practical 10 - Energy Report Table

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create EnergyLog table with TimeStamp, MeterName, kWh and DemandKW.

Done

STEP 02

Insert sample energy records for at least two meters.

Done

STEP 03

Write a query to show total kWh per meter.

Done

STEP 04

Add date filtering to the query.

Done

STEP 05

Verify totals against sample data.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Energy Report Table.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Energy Report Table	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Energy report table and query calculate meter-wise consumption.

P11

Softwell Digital Practical Manual

Practical 11 - Stored Procedure Report

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create stored procedure sp_DailyProductionReport.

Done

STEP 02

Add parameters @FromTime and @ToTime.

Done

STEP 03

Use the parameters in the WHERE clause.

Done

STEP 04

Execute the stored procedure with sample dates.

Done

STEP 05

Confirm the output matches the daily summary query.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Stored Procedure Report.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Stored Procedure Report	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Stored procedure generates reusable production report output for any date range.

P12

Softwell Digital Practical Manual

Practical 12 - Batch Report

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Write a query filtered by BatchNo.

Done

STEP 02

Join production and alarm data by time window if sample data allows.

Done

STEP 03

Show batch counts, rejects and related alarms.

Done

STEP 04

Save the query as batch-report.sql.

Done

STEP 05

Test with at least two batch numbers.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Batch Report.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Batch Report	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Batch report displays production and quality data for selected batches.

P13

Softwell Digital Practical Manual

Practical 13 - Export Report to CSV

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Run the daily summary query in SSMS.

Done

STEP 02

Use Save Results As or SQLCMD export method.

Done

STEP 03

Save output as DailyProductionReport.csv.

Done

STEP 04

Open the CSV in Excel and verify headings and rows.

Done

STEP 05

Store the file in D:\Softwell_Training\SQL_Reporting\Exports.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Export Report to CSV.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Export Report to CSV	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

SQL report output exports cleanly to CSV for Excel use.

P14

Softwell Digital Practical Manual

Practical 14 - Excel Report Connection

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Open Excel and use Get Data from SQL Server.

Done

STEP 02

Connect to the local SQL instance and Softwell_Reports database.

Done

STEP 03

Select vw_ShiftProduction or a report query.

Done

STEP 04

Load the result into a worksheet.

Done

STEP 05

Refresh the Excel connection and confirm updated SQL rows appear.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Excel Report Connection.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Excel Report Connection	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Excel is connected to SQL and can refresh reporting data.

P15

Softwell Digital Practical Manual

Practical 15 - PDF Report Preparation

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Format the Excel report with title, date range and totals.

Done

STEP 02

Set print area and page orientation.

Done

STEP 03

Export the Excel sheet as PDF.

Done

STEP 04

Open the PDF and verify layout, headings and totals.

Done

STEP 05

Save as DailyProductionReport.pdf.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for PDF Report Preparation.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	PDF Report Preparation	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

SQL report is converted into a readable PDF report.

P16

Softwell Digital Practical Manual

Practical 16 - Schedule Auto Report

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create a batch file or PowerShell script to run a saved SQL export.

Done

STEP 02

Test the script manually from Command Prompt or PowerShell.

Done

STEP 03

Open Windows Task Scheduler.

Done

STEP 04

Create a daily task for the report script.

Done

STEP 05

Run the task manually and confirm the export file is created.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Schedule Auto Report.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Schedule Auto Report	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Report export runs automatically through a scheduled task.

P17

Softwell Digital Practical Manual

Practical 17 - Database Backup

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Right-click Softwell_Reports and choose Tasks > Back Up.

Done

STEP 02

Select Full backup type.

Done

STEP 03

Save backup as Softwell_Reports.bak.

Done

STEP 04

Run the backup and confirm success.

Done

STEP 05

Copy the backup file to the training backup folder.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Database Backup.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Database Backup	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Database backup file is created for reporting project safety.

P18

Softwell Digital Practical Manual

Practical 18 - Database Restore Test

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create a restore test database named Softwell_Reports_Test.

Done

STEP 02

Restore from Softwell_Reports.bak.

Done

STEP 03

Check Tables, Views and Stored Procedures after restore.

Done

STEP 04

Run one report query from the restored database.

Done

STEP 05

Confirm restored data matches the original database.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Database Restore Test.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Database Restore Test	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Backup file restores successfully and reports run from restored data.

P19

Softwell Digital Practical Manual

Practical 19 - User Permission Setup

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Create a SQL login or database user for report reading.

Done

STEP 02

Assign read-only permission to report tables and views.

Done

STEP 03

Test login access from SSMS.

Done

STEP 04

Confirm the user can SELECT report data.

Done

STEP 05

Confirm the user cannot modify table structure.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for User Permission Setup.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	User Permission Setup	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Report user has safe read-only access for reporting.

P20

Softwell Digital Practical Manual

Practical 20 - Final SQL Reporting Project

Philosophy: Open the software, open the Softwell manual, and perform the practical.

SQL ReportingDatabaseReportsAutomation

Software: SQL Server Express / SQL Server Management Studio
Setup: Engineering laptop, sample production and alarm dataset

A. Step-by-Step Procedure

STEP 01

Prepare production, alarm and energy tables.

Done

STEP 02

Create required views and stored procedures.

Done

STEP 03

Export one CSV report and one PDF report.

Done

STEP 04

Schedule one automated report task.

Done

STEP 05

Demonstrate backup, restore and read-only user access.

Done

B. Verification Checklist

The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Final SQL Reporting Project.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.

C. If the Result Is Wrong

Symptom	Probable cause	Diagnostic check	Corrective action
Compile or configuration error	Unresolved device, tag, type, address or parameter	Open the first diagnostic entry and trace it to the configured object	Correct the source item, compile again and save a new evidence record
No online/runtime response	Wrong connection, command source, permissions or scan state	Monitor live values from input through logic to output	Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value	Scaling, initial state, timing or version mismatch	Compare raw and engineering values and review the installed version	Correct scaling/state, reset the lab safely and retest

D. Student Evidence Record

Environment

Record software version, controller/device firmware, driver and license status.

Project evidence

Save the project/archive name, modified block/object and parameter list.

Runtime evidence

Capture a verified screenshot, trend, alarm, tag table or measured value.

Conclusion

Write the pass condition, fault tested, correction made and final observation.

VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE

Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.

Practical	Final SQL Reporting Project	Pass condition	Observed result matches the stated objective and can be repeated.
Evidence filename	________________	Trainer / self-check	________________

Expected Result

Complete SQL reporting workflow is ready with tables, queries, exports, automation and backup.

SQL Reporting and Analytics Examples

This page is the reporting companion: it reads validated historian data and produces shift, alarm, trend and KPI outputs without changing the source records.

Parameterized time-range dataset

Use explicit UTC boundaries supplied by the report.

SELECT TagName, TagValue, QualityCode, SampleTimeUtc
FROM automation.TagHistory
WHERE SampleTimeUtc >= @StartUtc AND SampleTimeUtc < @EndUtc
  AND TagName = @TagName
ORDER BY SampleTimeUtc;

Verify: Run two non-overlapping periods and confirm no duplicate boundary row.

Hourly trend aggregation

Aggregate count, average, minimum and maximum by hour.

SELECT DATEADD(hour,DATEDIFF(hour,0,SampleTimeUtc),0) AS HourUtc,
       AVG(TagValue) AS AvgValue, MIN(TagValue) AS MinValue,
       MAX(TagValue) AS MaxValue, COUNT(*) AS Samples
FROM automation.TagHistory
WHERE TagName=@TagName AND SampleTimeUtc>=@StartUtc AND SampleTimeUtc<@EndUtc
GROUP BY DATEADD(hour,DATEDIFF(hour,0,SampleTimeUtc),0)
ORDER BY HourUtc;

Verify: Compare one hour manually with the aggregate output.

Shift classification

Define shift rules explicitly and retain UTC/source timestamps.

SELECT SampleTimeUtc, TagName, TagValue,
 CASE
  WHEN CAST(SampleTimeUtc AS time) >= '06:00' AND CAST(SampleTimeUtc AS time) < '14:00' THEN 'A'
  WHEN CAST(SampleTimeUtc AS time) >= '14:00' AND CAST(SampleTimeUtc AS time) < '22:00' THEN 'B'
  ELSE 'C' END AS ShiftCode
FROM automation.TagHistory;

Verify: Test boundary times 05:59, 06:00, 13:59, 14:00, 21:59 and 22:00.

Alarm Pareto dataset

Return count and accumulated duration for a selected period.

SELECT TOP (20) AlarmText, COUNT(*) AS Occurrences,
       SUM(DurationSeconds) AS TotalDurationSeconds
FROM automation.AlarmHistory
WHERE EventTimeUtc>=@StartUtc AND EventTimeUtc<@EndUtc
GROUP BY AlarmText
ORDER BY Occurrences DESC, TotalDurationSeconds DESC;

Verify: Compare the first alarm with a filtered source list.

Report-safe quality filter

Separate bad-quality values rather than silently averaging them.

SELECT TagName,
 AVG(CASE WHEN QualityCode=192 THEN TagValue END) AS GoodAverage,
 SUM(CASE WHEN QualityCode<>192 THEN 1 ELSE 0 END) AS BadSamples
FROM automation.TagHistory
WHERE SampleTimeUtc>=@StartUtc AND SampleTimeUtc<@EndUtc
GROUP BY TagName;

Verify: Inject one bad-quality lab row and confirm it is counted but not averaged.

Reusable reporting view

Expose stable column names to report tools.

CREATE OR ALTER VIEW automation.vw_TagHistoryReport
AS
SELECT TagHistoryId, TagName, TagValue, QualityCode, SampleTimeUtc
FROM automation.TagHistory;

Verify: Connect the lab report to the view and refresh the dataset.

Practice, Viva and Mini-Project

Practice: Modify one input, predict the result, execute the code and compare the output.
Viva: Explain the data flow, failure behavior, safe-use boundary and recovery method.
Mini-project: Combine at least three examples into one reviewed, versioned solution with an evidence pack.
Acceptance: A second learner can run the saved solution and reproduce the documented result.

Before You Start: Prerequisites, Tested Version, Safety and Evidence

This manual is a practical training workbook, not a substitute for the installed product manual or the site's approved engineering procedure. Record the exact software, firmware, license and hardware before following a step because menus and supported functions can vary by release.

Tested-version planning scope: Confirm SQL Server Version 2019 or later and the approved SSRS, Power BI or SCADA-reporting client used in the training lab. Enter the exact lab-tested software, firmware and hardware in the record below before course delivery; never assume cross-version compatibility.

Environment record

Software build, firmware, device catalog, driver, communication interface and license status.

Safe lab boundary

Use an isolated training system. Follow electrical, mechanical, process and cybersecurity controls before energizing or downloading.

Evidence pack

Keep the source project, parameter/code export, screenshot/trend, fault test, correction and final pass result.

Technical review

Last reviewed by Softwell Automation Technical Training Team on 17 July 2026.

Field	Learner record	Verification
Software / firmware	________________	Matches the training device and official compatibility information
Project / backup	________________	Saved before and after the practical
Pass evidence	________________	Runtime value, trend, alarm, diagnostic or report attached
Fault tested	________________	Symptom, cause, check and corrective action documented

Practice, Viva and Extension Challenge

Practice

Change one approved input or parameter, predict the result, execute the test and explain any difference.

Viva

Explain the data flow, safety boundary, first diagnostic check and recovery method without opening the answer.

Extension challenge

Add one useful function while preserving the original pass criteria, alarm behavior and rollback path.

Graded mini-project

Combine at least three practicals, submit a versioned project and evidence pack, and demonstrate repeatable recovery.

Industrial SQL Reporting four-stage practical lab, runtime verification, diagnosis and backup workflow — Instructional workflow diagram: complete configuration, measurable verification, controlled diagnosis and recovery evidence in sequence.

Microsoft SQL — official documentation

Content status: Substantively reviewed and expanded 17 July 2026. Verify release-specific details against the linked official documentation.