ikinci temizlik tamamlandı

2026-04-28 21:15:09 +03:00
parent f80443aec0
commit 37e7296527
8313 changed files with 2400677 additions and 0 deletions
@@ -0,0 +1,253 @@
+# Weldlog User Guide
+
+## What is Weldlog?
+
+Weldlog is your simplified welding tracker - a streamlined version of Weldmap focused on essential welding information. Use it for quick weld logging and basic quality tracking when you need speed over detailed documentation.
+
+## Getting Started
+
+To access Weldlog:
+1. Login to the system
+2. Click on **QC** in the main menu
+3. Select **Weldlog** from the submenu
+
+## Quick Weld Entry
+
+### Creating a New Entry
+1. Click the **"+"** button to add a new weld
+2. Fill in the essential information:
+   - **Joint Number**: Your unique weld identifier
+   - **ISO Number**: Drawing reference
+   - **Welding Date**: When the weld was completed
+   - **Welder Name**: Who performed the welding
+
+### Key Fields to Complete
+- **Line Number**: Select from the dropdown
+- **WPS Number**: Choose the welding procedure
+- **Welding Position**: Specify position (1G, 2G, 3G, 4G, 5G, 6G)
+- **Status**: Mark as Complete, In Progress, or Hold
+
+## Working with the Interface
+
+### Grid Navigation
+- **Scroll** through records using your mouse wheel
+- **Click headers** to sort columns
+- **Use filter boxes** to find specific welds
+- **Double-click cells** to edit (when permitted)
+
+### Quick Actions
+- **Enter key**: Save your changes
+- **Escape key**: Cancel editing
+- **Tab key**: Move to next field
+- **Arrow keys**: Navigate between cells
+
+## Data Entry Tips
+
+### Efficient Workflow
+1. **Start with the most recent welds** at the top
+2. **Use copy-paste** for repetitive information
+3. **Tab through fields** rather than clicking
+4. **Save frequently** by pressing Enter
+
+### Required Information
+Always ensure you have:
+- Valid joint number
+- Correct ISO reference
+- Accurate welding date
+- Qualified welder assignment
+
+## Quality Tracking
+
+### Test Status Updates
+When inspection results come in:
+1. Find the weld record
+2. Update **Test Result** field
+3. Add **Report Numbers** if available
+4. Mark **Date of Test** completion
+
+### Status Indicators
+- **🟢 Green**: Accepted welds
+- **🔴 Red**: Rejected welds requiring repair  
+- **🟡 Yellow**: Pending inspection
+- **⚪ Gray**: Not yet tested
+
+## Common Tasks
+
+### Daily Weld Logging
+1. Open Weldlog at start of shift
+2. Add new welds as they're completed
+3. Update any pending test results
+4. Review daily progress before leaving
+
+### Finding Specific Welds
+**By Date Range:**
+1. Use date filter at top of grid
+2. Select start and end dates
+3. Click Apply to filter results
+
+**By Welder:**
+1. Click welder column filter
+2. Type welder name or ID
+3. View all welds by that person
+
+**By Status:**
+1. Filter by completion status
+2. Review pending items
+3. Prioritize follow-up actions
+
+### Weekly Reporting
+1. Set date filter for the week
+2. Export data to Excel
+3. Review completion rates
+4. Identify any bottlenecks
+
+## Mobile Usage
+
+### Phone/Tablet Access
+- Interface adapts to smaller screens
+- Touch-friendly controls
+- Swipe to scroll horizontally
+- Pinch to zoom if needed
+
+### Field Entry
+- Use device keyboard for text
+- Date picker for dates
+- Dropdown selection still available
+- Voice input supported on some devices
+
+## Integration with Other Modules
+
+### Link to Weldmap
+- Detailed records sync with Weldmap
+- Use Weldlog for quick entry
+- Switch to Weldmap for detailed inspection data
+
+### NDT Coordination
+- Test requirements flow from Line List
+- Results feed back to quality reports
+- Automatic notifications for pending tests
+
+## Troubleshooting
+
+### Common Issues
+
+**Can't add new record:**
+- Check your user permissions
+- Ensure all required fields are available
+- Try refreshing the page
+
+**Data not saving:**
+- Verify internet connection
+- Check for field validation errors
+- Make sure you pressed Enter to save
+
+**Missing dropdown options:**
+- Contact admin to verify master data
+- Check if you're assigned to correct project
+- Ensure your user level has access
+
+### Quick Fixes
+- **Refresh page** for display issues
+- **Clear browser cache** if buttons don't work
+- **Check internet connection** for slow loading
+- **Try different browser** if problems persist
+
+## Best Practices
+
+### Daily Habits
+- ✅ Log welds immediately after completion
+- ✅ Update test results same day received
+- ✅ Review previous day's entries each morning
+- ✅ Keep joint numbering consistent
+
+### Weekly Reviews
+- ✅ Export data for backup
+- ✅ Check for missing information
+- ✅ Coordinate with inspection team
+- ✅ Update supervisor on progress
+
+### Data Quality
+- ✅ Use standard abbreviations
+- ✅ Double-check joint numbers
+- ✅ Verify welder qualifications
+- ✅ Maintain accurate dates
+
+## Getting Help
+
+**For Quick Questions:**
+- Check this guide first
+- Ask experienced colleagues
+- Use the search function
+
+**For Technical Issues:**
+- Note exact error messages
+- Screenshot any problems
+- Contact IT support with details
+
+**For Process Questions:**
+- Consult your supervisor
+- Review project procedures
+- Check welding standards
+
+Remember: Weldlog is designed for speed and simplicity. Master the basics first, then explore advanced features as needed!
+
+## 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. The `weldlog_update_system.php` file handles all mappings automatically