321 lines
8.9 KiB
Markdown
321 lines
8.9 KiB
Markdown
# NCR Log User Guide
|
|
|
|
## What is NCR Log?
|
|
|
|
NCR Log manages Non-Conformance Reports - your system for documenting, tracking, and resolving quality issues. When something doesn't meet specifications, an NCR ensures it gets proper attention and resolution.
|
|
|
|
## Getting Started
|
|
|
|
To access NCR Log:
|
|
1. Login to the system
|
|
2. Click on **NCR** in the main menu
|
|
3. Select **NCR log** from the submenu
|
|
|
|
## Understanding Non-Conformances
|
|
|
|
### What is a Non-Conformance?
|
|
A non-conformance occurs when:
|
|
- **Materials** don't meet specifications
|
|
- **Workmanship** falls below standards
|
|
- **Procedures** aren't followed correctly
|
|
- **Documentation** is incomplete or missing
|
|
- **Safety** requirements are violated
|
|
|
|
### When to Create an NCR
|
|
Always create an NCR for:
|
|
- ✅ Failed inspections or tests
|
|
- ✅ Damaged materials or equipment
|
|
- ✅ Procedure violations
|
|
- ✅ Safety incidents
|
|
- ✅ Client-identified issues
|
|
- ✅ Supplier quality problems
|
|
|
|
## Creating a New NCR
|
|
|
|
### Starting an NCR
|
|
1. Click **"Create New NCR"** button
|
|
2. Fill in basic information:
|
|
- **NCR Number**: Usually auto-generated
|
|
- **Date Identified**: When issue was found
|
|
- **Identified By**: Who found the problem
|
|
- **Location/Area**: Where the issue occurred
|
|
|
|
### Problem Description
|
|
**Be Specific and Clear:**
|
|
- **What exactly** is wrong?
|
|
- **Where precisely** is the problem?
|
|
- **When** was it discovered?
|
|
- **How extensive** is the issue?
|
|
- **What standards** are not met?
|
|
|
|
### Supporting Evidence
|
|
**Document Everything:**
|
|
- **Photos**: Take clear pictures of the problem
|
|
- **Measurements**: Record actual vs required dimensions
|
|
- **Test Results**: Include failed inspection reports
|
|
- **Drawings**: Reference applicable specifications
|
|
- **Witnesses**: Note who else observed the issue
|
|
|
|
## Categorizing NCRs
|
|
|
|
### Severity Levels
|
|
**🔴 Critical**: Immediate safety risk or major quality impact
|
|
**🟡 Major**: Significant quality concern requiring prompt action
|
|
**🟢 Minor**: Limited impact, can be addressed in normal schedule
|
|
|
|
### Issue Types
|
|
- **Material Defect**: Raw material problems
|
|
- **Workmanship**: Construction quality issues
|
|
- **Design**: Drawing or specification problems
|
|
- **Procedure**: Process not followed
|
|
- **Documentation**: Missing or incorrect paperwork
|
|
|
|
### Affected Areas
|
|
- **Welding**: Joint quality, procedure compliance
|
|
- **Materials**: Incoming inspection, storage
|
|
- **Testing**: NDT, pressure test failures
|
|
- **Safety**: HSE violations
|
|
- **Documentation**: Missing certificates, reports
|
|
|
|
## Investigation Process
|
|
|
|
### Immediate Actions
|
|
1. **Secure the area** - prevent further non-conforming work
|
|
2. **Document everything** - photos, measurements, conditions
|
|
3. **Notify supervisors** - alert management immediately
|
|
4. **Isolate materials** - segregate non-conforming items
|
|
5. **Stop related work** - prevent spreading the problem
|
|
|
|
### Root Cause Analysis
|
|
**Ask the 5 Whys:**
|
|
1. **Why** did this happen?
|
|
2. **Why** did that cause occur?
|
|
3. **Why** wasn't it prevented?
|
|
4. **Why** wasn't it caught earlier?
|
|
5. **Why** did the system allow this?
|
|
|
|
### Investigation Team
|
|
Typically includes:
|
|
- **Quality Control** representative
|
|
- **Area supervisor** or foreman
|
|
- **Technical specialist** (if needed)
|
|
- **Safety representative** (for safety issues)
|
|
- **Client representative** (if required)
|
|
|
|
## Resolution Planning
|
|
|
|
### Correction Options
|
|
**Repair**: Fix the defect to meet requirements
|
|
**Rework**: Completely redo the work properly
|
|
**Accept**: Use as-is with engineering approval
|
|
**Reject**: Scrap and replace with conforming item
|
|
|
|
### Creating Action Plans
|
|
1. **Define specific actions** needed
|
|
2. **Assign responsibility** to individuals
|
|
3. **Set realistic deadlines** for completion
|
|
4. **Identify resources** required
|
|
5. **Plan verification** activities
|
|
|
|
### Approval Process
|
|
**Internal Approval:**
|
|
- QC manager review
|
|
- Technical authority approval
|
|
- Safety sign-off (if applicable)
|
|
- Cost impact assessment
|
|
|
|
**Client Approval:**
|
|
- Submit for client review (if required)
|
|
- Provide technical justification
|
|
- Include repair procedures
|
|
- Wait for written approval
|
|
|
|
## Tracking Resolution
|
|
|
|
### Status Updates
|
|
**📝 Open**: NCR created, investigation starting
|
|
**🔍 Under Investigation**: Analyzing root cause
|
|
**📋 Action Plan Created**: Resolution plan approved
|
|
**🔧 Implementation**: Corrective actions in progress
|
|
**✅ Verification**: Checking if fix worked
|
|
**📁 Closed**: Issue fully resolved
|
|
|
|
### Progress Monitoring
|
|
Track these metrics:
|
|
- **Days open**: How long until resolution?
|
|
- **Cost impact**: What did it cost to fix?
|
|
- **Repeat issues**: Same problem occurring again?
|
|
- **Effectiveness**: Did the fix work completely?
|
|
|
|
### Communication
|
|
**Keep Stakeholders Informed:**
|
|
- **Regular updates** to management
|
|
- **Progress reports** to client
|
|
- **Lessons learned** shared with teams
|
|
- **Trending analysis** for improvement
|
|
|
|
## Documentation Requirements
|
|
|
|
### NCR Package Contents
|
|
Each NCR should include:
|
|
- **Original NCR form** with all details
|
|
- **Investigation report** with root cause
|
|
- **Action plan** with assignments
|
|
- **Implementation evidence** (photos, reports)
|
|
- **Verification records** proving fix worked
|
|
- **Approval signatures** from authorities
|
|
|
|
### Photo Documentation
|
|
**Before Photos:**
|
|
- Show the problem clearly
|
|
- Include reference measurements
|
|
- Document extent of issue
|
|
- Take from multiple angles
|
|
|
|
**After Photos:**
|
|
- Prove work was completed
|
|
- Show quality of repair
|
|
- Demonstrate compliance
|
|
- Include final measurements
|
|
|
|
## Quality Metrics
|
|
|
|
### NCR Performance Indicators
|
|
**Volume Trends:**
|
|
- NCRs per month
|
|
- Issues by category
|
|
- Repeat problems
|
|
- Cost of quality
|
|
|
|
**Resolution Efficiency:**
|
|
- Average days to close
|
|
- First-time fix rate
|
|
- Rework percentage
|
|
- Client satisfaction
|
|
|
|
### Continuous Improvement
|
|
**Use NCR Data For:**
|
|
- **Training needs** identification
|
|
- **Procedure improvements**
|
|
- **Supplier evaluations**
|
|
- **System enhancements**
|
|
- **Best practice** development
|
|
|
|
## Common NCR Scenarios
|
|
|
|
### Failed Weld Inspection
|
|
1. **Document** the failed joint
|
|
2. **Determine** repair requirements
|
|
3. **Plan** corrective welding
|
|
4. **Execute** repairs with qualified personnel
|
|
5. **Re-inspect** to verify acceptance
|
|
|
|
### Material Non-Conformance
|
|
1. **Quarantine** suspect materials
|
|
2. **Verify** extent of problem
|
|
3. **Notify** suppliers immediately
|
|
4. **Determine** use/return decision
|
|
5. **Implement** controls to prevent recurrence
|
|
|
|
### Procedure Violations
|
|
1. **Stop** non-conforming work
|
|
2. **Retrain** personnel involved
|
|
3. **Review** procedure adequacy
|
|
4. **Implement** additional controls
|
|
5. **Monitor** for effectiveness
|
|
|
|
## Working with Teams
|
|
|
|
### QC Department
|
|
- **Report issues** promptly and clearly
|
|
- **Provide evidence** to support findings
|
|
- **Cooperate** with investigations
|
|
- **Follow** approved repair procedures
|
|
|
|
### Construction Teams
|
|
- **Stop work** when problems identified
|
|
- **Assist** with investigation
|
|
- **Implement** corrective actions
|
|
- **Prevent** similar issues
|
|
|
|
### Management
|
|
- **Support** investigation resources
|
|
- **Approve** resolution plans
|
|
- **Monitor** implementation
|
|
- **Drive** systematic improvements
|
|
|
|
## Mobile Access
|
|
|
|
### Field Reporting
|
|
Use mobile devices to:
|
|
- **Create NCRs** immediately when issues found
|
|
- **Take photos** with location data
|
|
- **Update status** from work areas
|
|
- **Access** previous NCR data for reference
|
|
|
|
### Offline Capability
|
|
- **Create reports** without internet
|
|
- **Store photos** locally
|
|
- **Sync data** when connection available
|
|
- **Backup** critical information
|
|
|
|
## Best Practices
|
|
|
|
### Prevention Focus
|
|
- ✅ Train personnel properly
|
|
- ✅ Follow procedures consistently
|
|
- ✅ Inspect work regularly
|
|
- ✅ Maintain equipment properly
|
|
- ✅ Communicate requirements clearly
|
|
|
|
### Quick Response
|
|
- ✅ Report issues immediately
|
|
- ✅ Investigate thoroughly but quickly
|
|
- ✅ Plan corrections carefully
|
|
- ✅ Implement fixes promptly
|
|
- ✅ Verify effectiveness completely
|
|
|
|
### Learning Organization
|
|
- ✅ Share lessons learned
|
|
- ✅ Update procedures based on experience
|
|
- ✅ Train teams on common issues
|
|
- ✅ Recognize improvement efforts
|
|
- ✅ Celebrate zero-defect achievements
|
|
|
|
## Troubleshooting
|
|
|
|
### Common Issues
|
|
|
|
**NCR won't save:**
|
|
- Check all required fields completed
|
|
- Verify user has creation permissions
|
|
- Try refreshing page
|
|
- Contact IT if problem persists
|
|
|
|
**Can't upload photos:**
|
|
- Check file size (usually max 10MB each)
|
|
- Ensure JPEG/PNG format
|
|
- Try different browser
|
|
- Compress large images
|
|
|
|
**Status won't update:**
|
|
- Verify proper approval workflow
|
|
- Check user permissions for status change
|
|
- Ensure all required actions completed
|
|
- Contact supervisor for process questions
|
|
|
|
## Getting Help
|
|
|
|
**For Technical Issues:**
|
|
- Review this guide first
|
|
- Try basic troubleshooting
|
|
- Contact IT support with specific error messages
|
|
- Provide NCR number for reference
|
|
|
|
**For Process Questions:**
|
|
- Consult QC supervisor
|
|
- Review project procedures
|
|
- Check applicable standards
|
|
- Ask experienced team members
|
|
|
|
Remember: NCRs are improvement tools, not blame assignments. Focus on fixing problems and preventing recurrence, not finding fault! |