Ümit Tunç
139 lines
5.1 KiB
Markdown
139 lines
5.1 KiB
Markdown
# Ferrit Log User Guide
|
|
|
|
## What is the Ferrit Log Module?
|
|
|
|
The Ferrit Log module tracks and manages ferrite content measurements and testing records. This module helps monitor ferrite levels, track testing results, and ensure proper ferrite content management for welding and material quality control.
|
|
|
|
## Getting Started
|
|
|
|
To access Ferrit Log:
|
|
1. Login to the system
|
|
2. Click on **NDT** in the main menu
|
|
3. Select **Ferrit Log** from the submenu
|
|
|
|
## Key Features
|
|
|
|
### Primary Functions
|
|
- **Ferrite Testing**: Track ferrite content measurements
|
|
- **Result Management**: Manage testing results and records
|
|
- **Quality Control**: Monitor ferrite content quality
|
|
- **Documentation**: Maintain testing documentation
|
|
|
|
### Secondary Functions
|
|
- **Report Generation**: Generate ferrite testing reports
|
|
- **Data Analysis**: Analyze ferrite content trends
|
|
- **Export Options**: Export testing data in various formats
|
|
- **Compliance Monitoring**: Monitor ferrite content compliance
|
|
|
|
## How to Use
|
|
|
|
### Managing Ferrit Logs
|
|
1. Click **"Add Test"** button
|
|
2. Select material for ferrite testing
|
|
3. Conduct ferrite content measurement
|
|
4. Record testing results
|
|
5. Document testing conditions
|
|
6. Update ferrite log
|
|
7. Generate testing reports
|
|
|
|
### Testing Management
|
|
1. Review ferrite testing requirements
|
|
2. Conduct ferrite content measurements
|
|
3. Record testing results accurately
|
|
4. Monitor ferrite content trends
|
|
5. Generate testing reports
|
|
|
|
### Testing Categories
|
|
- **Weld Testing**: Ferrite content in welds
|
|
- **Base Material Testing**: Ferrite content in base materials
|
|
- **Component Testing**: Ferrite content in components
|
|
- **Quality Control Testing**: Quality control ferrite testing
|
|
|
|
## Best Practices
|
|
|
|
### Usage Guidelines
|
|
- ✅ Conduct ferrite testing accurately
|
|
- ✅ Record testing results promptly
|
|
- ✅ Monitor ferrite content trends
|
|
- ✅ Maintain proper documentation
|
|
|
|
### Quality Assurance
|
|
- ✅ Verify testing accuracy and completeness
|
|
- ✅ Ensure proper testing procedures
|
|
- ✅ Monitor testing effectiveness
|
|
- ✅ Regular review of testing processes
|
|
|
|
## Table Field Mapping
|
|
|
|
### Critical Field Name Differences
|
|
|
|
**IMPORTANT**: The `ferrite` table and `weld_logs` table have different field names:
|
|
|
|
1. **Result Field**:
|
|
- **ferrite table**: `result_ferrite`
|
|
- **weld_logs table**: `ferrite_result`
|
|
|
|
2. **Test Laboratory Field**:
|
|
- **ferrite table**: `tester_name`
|
|
- **weld_logs table**: `test_laboratory_ferrite`
|
|
|
|
3. **Check Date Field**:
|
|
- **ferrite table**: `ferrite_request_date`
|
|
- **weld_logs table**: `date_of_ferrite_check`
|
|
|
|
### Common Fields Between Tables
|
|
|
|
The following fields are shared between `ferrite` and `weld_logs` tables:
|
|
- `contractor`, `project`, `design_area`, `line_specification`, `line_number`
|
|
- `fluid_code`, `service_category`, `fluid_group`
|
|
- `operating_temperature_s`, `operating_pressure_mpa`, `external_finish_type`
|
|
- `iso_number`, `quantity_of_iso`, `iso_rev`, `spool_number`
|
|
- `type_of_joint`, `no_of_the_joint_as_per_as_built_survey`, `type_of_welds`
|
|
- `welding_date`, `wps_no`, `welding_method`
|
|
- `welding_materials_1`, `welding_materials_1_lot_no`, `welding_materials_1_certificate_no`
|
|
- `welding_materials_2`, `welding_materials_2_lot_no`, `welding_materials_2_certificate_no`
|
|
- `welder_1`, `welder_2`, `certificate_no_1`, `wpq_report_1`, `certificate_no_2`, `wpq_report_2`
|
|
- `member_no_1`, `material_no_1`, `ru_material_group_1`, `certificate_number_of_1`, `heat_number_1`
|
|
- `nps_1`, `thickness_by_asme_1`, `outside_diameter_1`, `wall_thickness_1`, `element_code_1`
|
|
- `member_no_2`, `material_no_2`, `ru_material_group_2`, `certificate_number_of_2`, `heat_number_2`
|
|
- `nps_2`, `thickness_by_asme_2`, `outside_diameter_2`, `wall_thickness_2`, `element_code_2`
|
|
- `ferrite_scope`, `ferrite_request_no`
|
|
- `no_of_ferrite_check`
|
|
- `real_welder_1`, `real_welder_2`
|
|
|
|
### Special Field Mappings
|
|
|
|
The `weldlog_update_system.php` handles special field mappings automatically:
|
|
|
|
```php
|
|
// Automatic field mapping when updating from ferrite to weld_logs
|
|
if(isset($data['tester_name'])) {
|
|
$updateData['test_laboratory_ferrite'] = $data['tester_name'];
|
|
}
|
|
|
|
if(isset($data['ferrite_request_date'])) {
|
|
$updateData['date_of_ferrite_check'] = $data['ferrite_request_date'];
|
|
}
|
|
```
|
|
|
|
### Developer Notes
|
|
|
|
When updating data from `ferrite` table to `weld_logs` table:
|
|
1. Always use `ferrite_result` (NOT `result_ferrite`) in `weldlog_accepted_columns()` function
|
|
2. `test_laboratory_ferrite` and `date_of_ferrite_check` are NOT in `weldlog_accepted_columns()` - they are mapped separately
|
|
3. Special field mappings are handled automatically by the system
|
|
4. Ensure field names match the target table schema
|
|
|
|
## Troubleshooting
|
|
|
|
### Common Issues
|
|
1. **Testing errors**: Check equipment calibration and procedure
|
|
2. **Result recording issues**: Verify data entry accuracy
|
|
3. **Equipment problems**: Contact equipment maintenance
|
|
4. **Field mapping errors**: Ensure correct field names are used (`result_ferrite` for ferrite table, `ferrite_result` for weld_logs table)
|
|
|
|
### Getting Help
|
|
- Contact the NDT department for technical support
|
|
- Consult ferrit log procedures and guidelines
|
|
- Check testing equipment and calibration records
|