Skip to content

QA/QC Learning Guide for Large-Scale Infrastructure Projects

Practical Knowledge for Solar Farm Construction

Document Control

  • Document No: QAR-LEARN-001
  • Revision: A
  • Date: October 2025
  • Contractor: Qaremy Construction Company
  • Purpose: Educational resource for understanding quality management in major infrastructure

1. Introduction - Understanding QA and QC

1.1 The Fundamental Difference

┌─────────────────────────────────────────────────────────────────┐
│                    QUALITY ASSURANCE (QA)                       │
│                                                                 │
│  "Are we doing things RIGHT?"                                   │
│  ✓ Process-focused                                              │
│  ✓ Preventative approach                                        │
│  ✓ Planning and systematic activities                           │
│  ✓ Creates confidence that quality requirements will be met     │
│                                                                 │
│  Examples:                                                      │
│  • Developing quality procedures                                │
│  • Training personnel                                           │
│  • Conducting internal audits                                   │
│  • Reviewing supplier qualifications                            │
│  • Document control systems                                     │
└─────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│                    QUALITY CONTROL (QC)                         │
│                                                                 │
│  "Is this thing RIGHT?"                                         │
│  ✓ Product-focused                                              │
│  ✓ Detective approach                                           │
│  ✓ Inspection and testing activities                            │
│  ✓ Identifies defects before they reach the customer            │
│                                                                 │
│  Examples:                                                      │
│  • Inspecting installed work                                    │
│  • Testing electrical circuits                                  │
│  • Measuring concrete strength                                  │
│  • Verifying torque on bolts                                    │
│  • Checking material certificates                               │
└─────────────────────────────────────────────────────────────────┘

1.2 How They Work Together

QA ensures you have the right processes, procedures, and people.
QC ensures those processes are being followed and the output meets requirements.

Real-World Example (Qaremy Construction NSW Solar Farm):

A tracker foundation pile needs to be installed to 1.5m depth and achieve 12 kNm torque.

  • QA Activities:

    • Develop Installation Test Plan (ITP) specifying requirements
    • Train installers on correct pile installation procedure
    • Ensure depth measurement tools are available and calibrated
    • Qualify the pile installer (check their competency)
  • QC Activities:

    • Measure actual pile depth (is it ≥1.5m?)
    • Record torque reading (is it ≥12 kNm?)
    • Inspect pile verticality (is it within 1°?)
    • Document results on inspection form

2. The Inspection Hierarchy - Who Checks What?

Large-scale projects use multiple layers of inspection to ensure quality. Each layer has a specific role:

┌──────────────────────────────────────────────────────────────────┐
│ LEVEL 1: SELF-INSPECTION (Installer/Worker)                     │
├──────────────────────────────────────────────────────────────────┤
│ • Performed by the person doing the work                         │
│ • First line of quality control                                  │
│ • Worker checks their own work before calling for inspection     │
│ • Example: Electrician checks connections before QC inspector    │
└──────────────────────────────────────────────────────────────────┘

┌──────────────────────────────────────────────────────────────────┐
│ LEVEL 2: CONTRACTOR QC (Independent QC Inspector)               │
├──────────────────────────────────────────────────────────────────┤
│ • Performed by contractor's QC team                              │
│ • Independent from the installation crew                         │
│ • Verifies work meets specifications                             │
│ • Documents results on inspection forms                          │
│ • Issues pass/fail decision                                      │
│ • Most common inspection level                                   │
│ • Example: QC Inspector verifies string voltage measurements     │
└──────────────────────────────────────────────────────────────────┘

┌──────────────────────────────────────────────────────────────────┐
│ LEVEL 3: CLIENT QA / ENGINEER'S REPRESENTATIVE                  │
├──────────────────────────────────────────────────────────────────┤
│ • Performed by client's quality team or independent engineer     │
│ • Oversight of contractor's QC processes                         │
│ • Witnesses critical hold points                                 │
│ • Reviews and approves documentation                             │
│ • Can halt work if quality issues identified                     │
│ • Example: Engineer witnesses HV cable pressure test             │
└──────────────────────────────────────────────────────────────────┘

┌──────────────────────────────────────────────────────────────────┐
│ LEVEL 4: THIRD-PARTY CERTIFICATION / REGULATORY                 │
├──────────────────────────────────────────────────────────────────┤
│ • Independent testing laboratories (NATA accredited)             │
│ • Regulatory authorities (SafeWork NSW, Council)                 │
│ • Certifying authorities (electrical compliance)                 │
│ • Final verification for legal/regulatory requirements           │
│ • Example: Electrical contractor certifies HV substation         │
└──────────────────────────────────────────────────────────────────┘

Why Multiple Layers?

  • Risk mitigation: Catches errors missed by previous layers
  • Independence: Each layer is independent from the work being checked
  • Specialization: Different parties focus on different aspects (workmanship vs compliance vs regulatory)
  • Accountability: Clear chain of responsibility for quality

3. Understanding Inspection Points: H, W, R

Every activity in an ITP has an inspection type. Understanding these is crucial:

🛑 Hold Point (H) - WORK MUST STOP

Definition: Work cannot proceed until inspection is completed and documented approval is given.

When Used:

  • Critical activities affecting safety or structural integrity
  • Irreversible activities (can't undo once completed)
  • Activities with high risk of defects
  • Activities requiring specialized verification

Examples:

  • Concrete pour (can't un-pour concrete)
  • HV cable termination (safety-critical)
  • Pile embedment depth (hidden once backfilled)
  • Material certification review (must confirm before installation)

Process:

  1. Contractor notifies inspector 48 hours in advance
  2. Work stops at the hold point
  3. Inspector attends site
  4. Inspection conducted and documented
  5. Inspector signs approval
  6. Work proceeds

Real-World Scenario:

You're installing a 33kV cable termination. This is a Hold Point.

Wrong: Installer completes termination, then calls QC inspector to review the finished work.

Correct: Installer prepares materials, notifies QC inspector 48 hours ahead. Inspector arrives on site. Installer performs termination work while inspector witnesses. Inspector verifies each step (cable preparation, stress cone installation, crimping). Inspector signs off. Cable can now be tested.

Why it matters: If the termination is done incorrectly and inspector isn't present, you may need to cut off the termination kit (costly) and redo it. The hold point ensures it's done right the first time.


👁️ Witness Point (W) - OPPORTUNITY TO WITNESS

Definition: Inspector must be given the opportunity to witness, but if they choose not to attend or are unavailable, work may proceed.

When Used:

  • Important but not critical activities
  • Activities where post-inspection is possible
  • Activities where risk is moderate

Examples:

  • Compaction testing (can do additional tests if needed)
  • Torque verification on sample bolts (can re-torque if issues)
  • Functional testing of trackers (can re-test)

Process:

  1. Contractor notifies inspector 24 hours in advance
  2. Inspector decides whether to attend
  3. If inspector attends: Work proceeds with witness
  4. If inspector doesn't attend: Work proceeds, contractor documents results

Real-World Scenario:

You're performing a slump test on concrete delivery. This is a Witness Point.

You notify the QC inspector. Inspector says "I'm on another part of the site, proceed without me but document results."

You perform slump test, record result (95mm), take photo, complete form. Work proceeds. Inspector reviews your documentation later.


📋 Review Point (R) - DOCUMENT REVIEW

Definition: Documentation must be submitted for review, but work may continue while review is in progress (unless otherwise stated).

When Used:

  • Document submittals
  • Material certificates
  • Design calculations
  • Test reports
  • As-built drawings

Examples:

  • Material receiving inspection report
  • Survey reports
  • Test certificates from laboratories
  • Manufacturer datasheets

Process:

  1. Contractor submits documentation
  2. Work may continue (unless stated otherwise)
  3. Reviewer checks documentation
  4. Approves or comments returned
  5. Contractor addresses comments if required

Real-World Scenario:

You've received a shipment of PV modules. You complete the Material Receiving Inspection Report. This is a Review Point.

You submit the report to the Document Controller. Modules are moved to storage (work continues). QA Manager reviews your report over the next few days and confirms it's complete. If there were issues, they'd contact you to address them.


4. The Inspection and Test Plan (ITP) - Your Roadmap

The ITP is the single most important quality document on site for each discipline. It tells you:

  • WHAT needs to be inspected
  • WHEN it needs to be inspected
  • WHO needs to inspect it
  • WHAT STANDARD applies
  • WHAT is acceptable
  • WHAT RECORDS are required

4.1 Reading an ITP Table

Let's decode a sample ITP entry:

┌──────────────────────────────────────────────────────────────────────────┐
│ Activity: String Insulation Resistance Test                              │
├──────────┬─────────┬──────┬───────┬─────────────┬─────────────┬──────────┤
│Inspection│  Type   │Party │  Ref  │  Acceptance │   Records   │          │
│  /Test   │         │      │Standard│  Criteria   │             │          │
├──────────┼─────────┼──────┼───────┼─────────────┼─────────────┼──────────┤
│Insulation│    H    │ QC,  │AS/NZS │   >1 MΩ     │ Insulation  │          │
│resistance│         │  TP  │ 5033  │at 500V DC   │    test     │          │
│test      │         │      │       │             │ certificate │          │
└──────────┴─────────┴──────┴───────┴─────────────┴─────────────┴──────────┘

Breaking it down:

  • Activity: String insulation resistance test - this is WHAT you're inspecting
  • Type: H - This is a HOLD POINT. Work stops until this is done and approved
  • Party: QC, TP - Contractor QC Inspector AND Third Party (NATA lab or qualified electrician)
  • Reference Standard: AS/NZS 5033 - The standard that defines this requirement
  • Acceptance Criteria: >1 MΩ at 500V DC - This is the pass/fail threshold
  • Records: Insulation test certificate - This document must be produced

What this means in practice:

  1. Before you can connect the string to the inverter (Hold Point), you must:
  2. Measure insulation resistance using a 500V DC megger
  3. Have both QC Inspector and Third Party present
  4. Achieve a reading greater than 1 MΩ
  5. Document on an insulation test certificate
  6. Get signatures from QC and TP
  7. Submit certificate to Document Controller
  8. ONLY THEN can you proceed to connect the string

If you get 0.5 MΩ (FAIL):

  • Work stops
  • Issue Non-Conformance Report (NCR)
  • Investigate cause (moisture in connector? Damaged cable? Earth fault?)
  • Fix the problem
  • Re-test
  • Must pass before proceeding

5. Traceability - Following the Thread

Traceability is the ability to trace the history, application, or location of an item through recorded identification.

Why Traceability Matters

Imagine you're asked: "Show me evidence that Row 15, Tracker 8 was installed correctly."

With proper traceability, you can follow the thread:

1. Foundation Records

   Pile installation log → Pile ID: P-15-08

   Torque reading: 11.5 kNm (pass)

   Depth measurement: 1.65m (pass)

   Pile load test certificate (sample test on Row 15)

   Civil ITP signed off: ✓

2. Mechanical Installation Records

   Tracker assembly log → Tracker ID: T-15-08

   Torque tube installation checklist

   Bearing installation record

   Module clamp torque log (sample 10%)

   Mechanical ITP signed off: ✓

3. Electrical Connection Records

   String assignment: Strings S-449 to S-456 on Tracker T-15-08

   String test sheet S-449: Voc 1350V, Isc 11.2A, IR 180 MΩ ✓

   String test sheet S-450: Voc 1348V, Isc 11.3A, IR 195 MΩ ✓

   [... all strings tested ...]

   Electrical ITP signed off: ✓

4. Module Serial Numbers

   Module register → Tracker T-15-08

   Serial numbers: Module positions 1-32

   Module flash test reports (from manufacturer)

   Material receiving inspection (batch accepted)

Complete traceability from pile in ground → through assembly → to energized tracker.

What Breaks Traceability?

❌ Missing serial number records
❌ Inspection forms not filled out completely
❌ Test certificates not linked to specific equipment
❌ "We installed it correctly but didn't write it down"

Golden Rule: "If it's not documented, it didn't happen."


6. Non-Conformance Management - When Things Go Wrong

Non-conformances will happen on every project. How you handle them is what matters.

6.1 The NCR Lifecycle

┌─────────────────────────────────────────────────────────────────┐
│ IDENTIFY                                                        │
│ • Non-conformance discovered during inspection                  │
│ • Could be failed test, incorrect installation, defective       │
│   material, or missed procedure                                 │
└────────────────────────────┬────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ ISOLATE & DOCUMENT                                              │
│ • Stop work in affected area                                    │
│ • Tag or mark non-conforming work/materials                     │
│ • Take photos                                                   │
│ • Issue NCR form (within 24 hours)                              │
└────────────────────────────┬────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ INVESTIGATE ROOT CAUSE                                          │
│ • How did it happen?                                            │
│ • Why wasn't it caught earlier?                                 │
│ • Is this an isolated incident or systemic?                     │
│ • Use "5 Whys" technique for major issues                       │
└────────────────────────────┬────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ PROPOSE CORRECTIVE ACTION                                       │
│ • Repair, rework, replace, concession, or reject                │
│ • Detailed method statement                                     │
│ • Get approval from QA Manager / Engineer                       │
└────────────────────────────┬────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ IMPLEMENT CORRECTION                                            │
│ • Execute approved corrective action                            │
│ • Document the correction process                               │
│ • Take "after" photos                                           │
└────────────────────────────┬────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ VERIFY                                                          │
│ • QC Inspector verifies correction is effective                 │
│ • Re-test if required                                           │
│ • Accept or reject corrective action                            │
└────────────────────────────┬────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ PREVENTIVE ACTION                                               │
│ • What will prevent this from happening again?                  │
│ • Training? Procedure update? Additional checks?                │
│ • Implement preventive measures                                 │
└────────────────────────────┬────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ CLOSE NCR                                                       │
│ • All actions complete and verified                             │
│ • QA Manager approval                                           │
│ • Update NCR register                                           │
│ • File complete package                                         │
└─────────────────────────────────────────────────────────────────┘

6.2 Real-World NCR Example

NCR-087: Tracker Foundation Piles Under-Torqued

Discovery: During QC inspection, piles in Row 22 were found to have torque readings of 6-8 kNm (requirement: ≥12 kNm).

Immediate Action:

  • Work stopped in Row 22
  • 24 piles affected
  • Area tagged "DO NOT PROCEED"
  • NCR issued same day

Investigation (5 Whys):

  • Why 1: Why was torque low? Installation equipment set to wrong torque limit
  • Why 2: Why was equipment set wrong? Operator adjusted setting for different soil zone
  • Why 3: Why wasn't setting verified? No check process before starting new row
  • Why 4: Why is there no check process? Work instruction doesn't specify pre-start verification
  • Why 5: Why wasn't it in the work instruction? Original instruction written for single soil type

Root Cause: Inadequate work instruction for sites with variable soil conditions.

Corrective Action:

  • Extract all 24 piles
  • Reinstall to minimum 1.5m depth with correct torque (≥12 kNm)
  • Verify settings before each row
  • QC Inspector to witness torque verification at start of each row

Implementation:

  • Extraction and reinstallation completed over 2 days
  • All 24 piles reinstalled successfully
  • Torque readings: 12.5-14.2 kNm (all pass)
  • Re-tested and documented

Preventive Action:

  • Updated work instruction to include:
    • Pre-start equipment verification checklist
    • Torque setting confirmation before each row
    • First pile of each row as witness point
  • Toolbox talk conducted for all pile installation crews
  • Increased QC surveillance during pile installation

Verification:

  • No further under-torque issues in subsequent rows
  • Pre-start checklists being completed consistently
  • NCR closed after 15 days

Lessons Learned:

  • Variable site conditions require flexible procedures
  • Pre-start verification prevents batch defects
  • Early detection (during installation, not after completion) minimized rework

7. Key Quality Concepts for Infrastructure

7.1 First Time Quality (FTQ)

Definition: The percentage of work that passes inspection on the first attempt, without requiring rework or correction.

Why it matters:

  • Rework is expensive (labor + materials)
  • Rework delays the schedule
  • Rework demoralizes the workforce
  • Prevention is always cheaper than correction

Target: >95% FTQ rate

How to achieve it:

  • Competent, trained workforce
  • Clear, accessible procedures and specifications
  • Adequate toolbox talks and briefings
  • Self-inspection before calling QC
  • Learning from non-conformances

7.2 Right First Time vs Fix Later

┌─────────────────────────────────────────────────────────────────┐
│                  COST OF QUALITY                                │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  PREVENTION COST (QA)                                           │
│  Training: $5,000                                               │
│  Planning: $3,000                                               │
│  Procedures: $2,000                                             │
│  ────────────────────                                           │
│  Total: $10,000                                                 │
│                                                                 │
│          vs                                                     │
│                                                                 │
│  FAILURE COST (Rework)                                          │
│  Extract 24 piles: $12,000                                      │
│  Reinstall: $15,000                                             │
│  Re-test: $3,000                                                │
│  Schedule delay: $8,000                                         │
│  ────────────────────                                           │
│  Total: $38,000                                                 │
│                                                                 │
│  → Spending $10k on prevention saved $28k in rework            │
└─────────────────────────────────────────────────────────────────┘

The quality paradox: Spending money on quality (QA) feels like overhead, but it saves multiples in rework costs (QC failures).


7.3 Documentation is Everything

In infrastructure projects, documentation serves multiple purposes:

Legal Protection:

  • Evidence of compliance with regulations and standards
  • Defense against warranty claims or litigation

Traceability:

  • Proves what was installed, when, by whom, and how

Maintenance:

  • Future maintenance teams need to understand what's installed and where

Performance Verification:

  • Proves the asset was built to specification

Knowledge Transfer:

  • Lessons learned for future projects

Common saying: "If it's not documented, it didn't happen."

What this means in practice:

  • Every inspection requires a completed form
  • Every test requires a certificate
  • Every material requires certification
  • Every change requires a record
  • Photos are mandatory for most activities

8. Career Pathways in QA/QC

8.1 Entry-Level Positions

QC Inspector / Junior QC Inspector

  • Conduct routine inspections
  • Complete inspection checklists
  • Document results
  • Report non-conformances

Typical Background:

  • Trade qualification (electrical, mechanical, civil)
  • 2-5 years site experience
  • Understanding of relevant standards

Day-to-Day Activities:

  • Site inspections (foundations, installations, testing)
  • Witnessing hold points
  • Material receiving inspections
  • Completing inspection forms
  • Taking photos
  • Communicating with subcontractors

8.2 Mid-Level Positions

Lead QC Inspector (by discipline)

  • Supervise QC inspectors
  • Develop inspection schedules
  • Review inspection records
  • Coordinate with subcontractors
  • Support NCR investigations

QA Coordinator

  • Document control
  • NCR tracking
  • Audit coordination
  • Training coordination
  • Quality reporting

Typical Background:

  • 5-10 years quality experience
  • Trade background + quality qualification
  • Strong documentation and organizational skills

8.3 Senior Positions

QA Manager

  • Overall quality management system
  • Develop and maintain QMS documentation
  • Internal audits
  • Interface with client
  • NCR approval and closure
  • Quality performance reporting
  • Management reviews

Typical Background:

  • 10+ years quality experience
  • Formal quality qualifications (ISO 9001 lead auditor, quality management diploma)
  • Multi-project experience
  • Strong leadership and stakeholder management

8.4 Skills to Develop

Technical Skills:

  • Reading and interpreting drawings and specifications
  • Understanding relevant Australian Standards
  • Inspection techniques (visual, dimensional, testing)
  • Use of inspection equipment (torque wrenches, multimeters, survey equipment)

Documentation Skills:

  • Clear and concise report writing
  • Photography for documentation
  • Database and spreadsheet proficiency
  • Document management systems

Soft Skills:

  • Communication (explaining non-conformances without being confrontational)
  • Negotiation (working with subcontractors to resolve issues)
  • Attention to detail
  • Problem-solving
  • Time management (multiple inspections, tight deadlines)

Qualifications to Consider:

  • ISO 9001:2015 Internal Auditor training
  • Certificate IV in Quality Auditing
  • Diploma of Quality Auditing
  • Trade qualifications (electrical, engineering, construction)
  • Specialized training (AS/NZS 5033 for solar, AS 3000 for electrical, etc.)

9. Practical Tips for Working in QA/QC

9.1 Communication Best Practices

When Issuing an NCR: ❌ "You guys stuffed this up." ✅ "During inspection, I found [specific observation]. Per [specification reference], the requirement is [X], and the actual condition is [Y]. This doesn't meet the acceptance criteria. Let's discuss how to address it."

Be Objective, Not Personal:

  • Focus on facts and evidence
  • Reference specifications and standards
  • Separate the work from the worker
  • Frame as "we" not "you" - everyone wants quality

9.2 Independence is Critical

The Golden Rule: QC inspectors must be independent from the work being inspected.

Why?

  • Prevents conflict of interest
  • Maintains objectivity
  • Builds client confidence
  • Meets ISO 9001 requirements

In practice:

  • QC inspectors don't report to construction supervisors
  • QC inspectors are often from a different company or separate division
  • QA Manager may have dual reporting (administratively to Project Manager, technically to Client)

9.3 Know When to Escalate

Not every issue requires an NCR. Learn to distinguish:

Issue NCR When:

  • Clear non-compliance with specification
  • Failed test result
  • Significant defect affecting safety or performance
  • Repeated minor issues indicating systemic problem

Handle Informally When:

  • Very minor cosmetic issue with no functional impact
  • Administrative error easily corrected
  • Observation during work in progress (before final inspection)
  • Educational opportunity (first occurrence, no impact)

Always Escalate:

  • Safety hazards
  • Critical non-conformances
  • Client complaints
  • Regulatory violations
  • Anything you're unsure about

9.4 Building Relationships

With Subcontractors:

  • Explain requirements clearly
  • Be consistent in your inspections
  • Acknowledge good work, not just defects
  • Help them understand "why" requirements exist
  • Be available when they have questions

With Project Team:

  • Provide timely feedback
  • Focus on solutions, not just problems
  • Understand schedule pressures (but don't compromise quality)
  • Communicate proactively

With Client:

  • Professional and transparent
  • Provide evidence, not opinions
  • Escalate issues appropriately
  • Regular reporting and communication

10. Learning from Real Projects - Common Issues

10.1 Top 10 Non-Conformances on Solar Farms

Based on industry experience, these are the most common:

  1. Under-torqued fasteners (tracker systems, electrical connections)

    • Prevention: Calibrated tools, verification sampling, training
  2. String insulation resistance failures (moisture in DC connectors)

    • Prevention: Proper connector installation training, weather protection
  3. Missing or incorrect labels (strings, cables, equipment)

    • Prevention: Labeling as you go, not at end of job
  4. Incomplete documentation (missing signatures, test results not recorded)

    • Prevention: Don't let installers leave until forms complete
  5. Material certificates not received (proceed with installation before verification)

    • Prevention: Hard stop - no materials on site without certs
  6. Pile depths below minimum (soil conditions change, inadequate verification)

    • Prevention: Every pile measured, not just samples
  7. Cable installation without clearances (burial depth, separation from other services)

    • Prevention: As-built survey before backfill
  8. Concrete strength failures (inadequate curing, wrong mix, poor compaction)

    • Prevention: Proper curing regime, test every pour
  9. Damaged galvanizing (during transport, installation)

    • Prevention: Inspection on receipt, touch-up damaged areas immediately
  10. Bypass of hold points (proceeding without approval)

    • Prevention: Clear communication, understanding of consequences

11. Final Thoughts - The Quality Mindset

Quality is not about:

  • Being the "quality police"
  • Saying "no" to everything
  • Making work harder
  • Finding faults

Quality is about:

  • Preventing problems before they occur (QA)
  • Catching defects early when they're cheap to fix (QC)
  • Building confidence that the asset will perform as designed
  • Protecting the project, company, and ultimately public safety
  • Creating value by reducing rework and warranty issues

Remember:

  • Quality is everyone's responsibility, not just the QA/QC team
  • The cheapest defect is the one that never happens
  • Documentation is not bureaucracy; it's evidence of compliance
  • Independence and objectivity are your most valuable assets
  • A solar farm must operate reliably for 25-30 years - quality during construction determines that performance

12. Continuing Your Learning

Standards to Read:

  1. AS/NZS ISO 9001:2016 (understand QMS principles)
  2. AS/NZS 5033:2021 (solar installation)
  3. AS/NZS 3000:2018 (electrical wiring rules)

Online Resources:

  • Standards Australia (www.standards.org.au)
  • Clean Energy Council (Australia) - solar industry resources
  • ASQ (American Society for Quality) - quality management knowledge base

Industry Experience:

  • Seek mentorship from experienced QA/QC professionals
  • Attend project site visits if possible
  • Participate in internal audits
  • Volunteer for quality working groups

Professional Development:

  • ISO 9001 Internal Auditor training
  • Industry-specific courses (solar, electrical, construction)
  • Attend quality conferences and seminars

13. Conclusion

Quality management in large-scale infrastructure is systematic, rigorous, and essential. By understanding:

  • The difference between QA (process) and QC (product)
  • The inspection hierarchy and levels of oversight
  • How to read and implement ITPs
  • The importance of traceability and documentation
  • How to manage non-conformances effectively

...you'll be well-prepared to work effectively in QA/QC roles on major projects.

The solar industry in Australia is growing rapidly. There is strong demand for competent quality professionals who understand both the technical requirements and the systematic approach to managing quality. Use this QMS as a foundation for your learning and build on it with practical experience.

Developed by Qaremy Construction Company for NSW solar infrastructure projects.

Good luck with your upskilling journey!


Revision History

RevisionDateDescriptionPrepared ByApproved By
AOct 2025Initial IssueQA ManagerProject Manager

END OF DOCUMENT

Quality Management System for Educational Purposes