ERPNext Webshop Setup Guide

2026-02-25T07:10:32Z

BabiSender: Blanked the page

ERPNext Webshop Setup Guide

2026-02-25T07:10:18Z

BabiSender: Created page with "= ERPNext Webshop: Installation, Bulk Item Management & Setup Guide = This guide outlines the end-to-end process for installing and populating the ERPNext Webshop, ensuring items are correctly categorized, imported, and visually optimized for both internal administration and the customer-facing storefront. == Sources == * https://docs.frappe.io/erpnext/v13/user/manual/en/ecommerce/set-up-ecommerce * https://github.com/frappe/webshop * https://docs.frappe.io/erpnext/v13..."

= ERPNext Webshop: Installation, Bulk Item Management & Setup Guide =

This guide outlines the end-to-end process for installing and populating the ERPNext Webshop, ensuring items are correctly categorized, imported, and visually optimized for both internal administration and the customer-facing storefront.

== Sources ==
* https://docs.frappe.io/erpnext/v13/user/manual/en/ecommerce/set-up-ecommerce
* https://github.com/frappe/webshop
* https://docs.frappe.io/erpnext/v13/user/manual/en/ecommerce/website-item
* https://docs.frappe.io/erpnext/v13/user/manual/en/ecommerce/ecommerce_settings

== Step 1: Install Webshop ==

You can install the Webshop module in two ways:

=== Option 1: Via Bench (Self-hosted) ===
<pre>
bench get-app https://github.com/frappe/webshop
bench --site [your-site-name] install-app webshop
bench restart
</pre>

=== Option 2: Via Frappe Cloud ===
# Go to the '''Frappe Cloud Dashboard'''.
# Choose '''Sites''' or '''Server → Application'''.
# Under '''Apps''', click '''Install App''' and select '''Webshop'''.

== Step 2: Set Up Item Groups ==

You can use the default Item Groups (e.g. ''Products'' or ''Services'') or create new ones.

# Go to '''Item Group List''' and create or edit an Item Group.
# '''Crucial:''' Check the "'''Show in Website'''" box so the group appears in shop navigation.
# Configure the Item Group's '''taxes, terms, and conditions''' for accurate pricing and compliance.

== Step 3: Configure Webshop Settings ==

Navigate to: '''Webshop Settings'''

=== Display Settings ===
* Products per Page: '''24''' (recommended)
* ☑ Enable Variant Selection
* ☑ Show Price
* ☑ Show Contact Us Button
* (Optional) Show Stock Availability
* (Optional) Show Apply Coupon Code
* (Optional) Allow items not in stock to be added to cart

=== Shopping Cart Settings ===
* '''Company:''' Comfac Corporation
* '''Default Customer Group:''' All Customer Groups
* '''Price List:''' Standard Selling
* '''Quotation Series:''' <code>SAL-QTN-YYYY.-</code>
* ☑ Enable Shopping Cart
* (Optional) Allow Non-Website Items in Cart Quotation

=== Checkout Settings ===
* ☑ Show Price in Quotation
* ☑ Save Quotations as Draft
* (Optional) Enable Checkout — activate when payment systems are ready

== Step 4: Bulk Item Creation (Core Item) ==

You must create the '''Item''' entry before the '''Website Item'''.

# Download the '''Item Import Template''' from the Data Import tool.
# Fill in the template using the critical fields below.

=== Critical Item Fields & Defaults ===

{| class="wikitable"
! Field !! Required Value / Default !! Note
|-
| '''Item Code''' || ''Unique SKU'' || Must be correct; this links all records.
|-
| '''Series''' || <code>STO-ITEM-.YYYY.-</code> || Standard naming series.
|-
| '''Item Name''' || ''Product Name'' || Display name for the product.
|-
| '''Item Group''' || ''Category Name'' || Must match a created Item Group.
|-
| '''Default Unit of Measure''' || Unit || Standard UOM.
|-
| '''Maintain Stock''' || 1 || Set to 1 for physical goods.
|-
| '''Standard Selling Rate''' || ''Price'' || The base price of the item.
|-
| '''Description''' || ''Details'' || Internal/Technical description.
|-
| '''Brand''' || ''Manufacturer'' || e.g., Dell, Netgate.
|-
| '''Default Material Request Type''' || Purchase || Standard procurement flow.
|-
| '''Published in Website''' || 1 || '''Mandatory''' for web visibility.
|-
| '''UOM (UOMs)''' || Unit || Child table UOM entry.
|-
| '''Conversion Factor (UOMs)''' || 1 || Relationship to base UOM.
|-
| '''Company (Item Defaults)''' || ''Your Company'' || e.g., Comfac Corporation.
|-
| '''Default Warehouse (Item Defaults)''' || ''Warehouse Name'' || e.g., Stores - CC.
|}

== Step 5: Attaching Item Pictures ==

After the bulk Item upload, attach image files to each record:

# Open the '''Item''' record.
# Use the '''"Attach File"''' button in the sidebar.
# Upload high-resolution product images.
# These attached images are what the Slideshow will eventually "Fetch."

== Step 6: Bulk Website Item Creation ==

The '''Website Item''' is the public face of your product. Use the '''Website Item Import Template'''.

=== Critical Website Item Fields ===

{| class="wikitable"
! Field !! Required Value / Default !! Note
|-
| '''Website Item Name''' || ''Marketing Name'' || The title shown on the webshop.
|-
| '''Item Code''' || ''Matching SKU'' || '''Must match exactly''' the code from Step 4.
|-
| '''Naming Series''' || <code>WEB-ITM-.####</code> || Standard website item series.
|-
| '''Has Variants''' || 0 || Set to 0 for standalone items.
|-
| '''Published''' || 1 || Set to 1 to make it live.
|-
| '''Item Name''' || ''Internal Name'' || Matches the Core Item name.
|-
| '''Item Group''' || ''Category'' || Website category for navigation.
|-
| '''Stock UOM''' || Unit || Must match the Core Item UOM.
|-
| '''Item Description''' || ''Full Details'' || Long-form text for the item page.
|-
| '''Brand''' || ''Manufacturer'' || Displayed for filtering.
|-
| '''Image Description''' || ''Alt Text'' || Used for SEO and accessibility.
|-
| '''Short Website Description''' || ''Teaser'' || Shown in the grid/list view.
|-
| '''Website Description''' || ''Rich Content'' || Detailed marketing description.
|}

== Step 7: Website Slideshows ==

To provide a premium feel, use the '''Website Slideshow''' feature.

# Navigate to '''Website Slideshow'''.
# '''Naming Convention:''' Use the '''Website Item Name''' or '''Item Code''' to name the entry.
# '''Fetch Images:''' Click '''"Fetch attached images from the document"''' — this pulls images attached to the Item record in Step 5.
# '''Link to Website Item:''' Go to the Website Item record → '''Display Images''' section → select your new Slideshow.
# The '''Main Picture''' on the shop page is pulled from the primary attached picture on the Website Item entry.

== Step 8: Bulk Editing & Fine-Tuning ==

Only perform bulk editing ''after'' the initial creation has been inspected and verified.

* Use the '''"Update Records"''' mode in the Data Import tool to adjust prices or descriptions.
* Verify that each item has a unique '''Route''' to avoid 404 errors.
* Once published, products will appear under <code>/all-products</code> by default.

[[Category:ERPNext]]
[[Category:Webshop]]
[[Category:Setup Guides]]

Frappe Links and References

2026-02-25T07:02:58Z

BabiSender: Created page with "= Frappe Links and References = == Official Documentation == * [https://docs.frappe.io/erpnext/user/manual/en/india ERPNext India Localization – User Manual] * [https://docs.indiacompliance.app/docs/getting-started/introduction India Compliance App – Getting Started] * [https://docs.frappe.io/cloud/guidelines-for-contributing-regional-localisation Frappe Cloud – Guidelines for Contributing Regional Localisation] * [https://docs.frappe.io/cloud/local-fc-setup Frap..."

= Frappe Links and References =

== Official Documentation ==

* [https://docs.frappe.io/erpnext/user/manual/en/india ERPNext India Localization – User Manual]
* [https://docs.indiacompliance.app/docs/getting-started/introduction India Compliance App – Getting Started]
* [https://docs.frappe.io/cloud/guidelines-for-contributing-regional-localisation Frappe Cloud – Guidelines for Contributing Regional Localisation]
* [https://docs.frappe.io/cloud/local-fc-setup Frappe Cloud – Local FC Setup]

Modern Guide: pfSense Captive Portal with FreeRADIUS & ACME

2026-02-25T07:02:37Z

BabiSender: Created page with "= Modern Guide: pfSense Captive Portal with FreeRADIUS & ACME = '''Based on the Lawrence Systems Methodology''' Reference Videos: * [https://www.youtube.com/watch?v=hdHDCafeFdU pfSense Captive Portal with FreeRADIUS – Lawrence Systems] * [https://www.youtube.com/watch?v=qlcVx-k-02E Quick and Easy Local SSL Certificates for Your Homelab – Wolfgang's Channel] This guide focuses on a "production-ready" setup that minimizes browser errors (SSL warnings) on modern devi..."

= Modern Guide: pfSense Captive Portal with FreeRADIUS & ACME =

'''Based on the Lawrence Systems Methodology'''

Reference Videos:
* [https://www.youtube.com/watch?v=hdHDCafeFdU pfSense Captive Portal with FreeRADIUS – Lawrence Systems]
* [https://www.youtube.com/watch?v=qlcVx-k-02E Quick and Easy Local SSL Certificates for Your Homelab – Wolfgang's Channel]

This guide focuses on a "production-ready" setup that minimizes browser errors (SSL warnings) on modern devices by using proper Let's Encrypt certificates and Split DNS. It also covers per-user bandwidth limiting and strict content whitelisting.

----

== Prerequisites ==

* '''pfSense Firewall:''' Version 2.4/2.5 or higher.
* '''Domain Name:''' You need a domain name (buy one or use DuckDNS).
* '''Guest Network:''' A dedicated interface/VLAN (e.g., 192.168.2.1/24) for guests.
* '''Packages:''' Install <code>freeradius3</code> and <code>acme</code>.

----

== Phase 1: WebGUI Configuration (Port Conflict Prevention) ==

# Navigate to '''System > Advanced > Admin Access'''.
# '''TCP Port:''' Change this to <code>5555</code>.
# '''WebGUI Redirect:''' Ensure "Disable webConfigurator redirect rule" is '''unchecked'''.
# Click '''Save'''.

----

== Phase 2: Free SSL Certificates (DuckDNS & Let's Encrypt) ==

'''The Problem:''' Modern browsers block "Self-Signed" certificates.
'''The Fix:''' Use DuckDNS (free) to get a valid certificate.

=== Step A: Get a Free DuckDNS Domain ===
# Go to [https://www.duckdns.org DuckDNS.org].
# Create a domain (e.g., <code>mywifinetwork</code>).
# Copy your '''Token'''.

=== Step B: Configure ACME on pfSense ===
# '''Install ACME:''' Go to '''System > Package Manager''' and install <code>acme</code>.
# '''Create Account Key:''' Services > ACME > Account Keys > Add.
#* Name: <code>LetsEncryptKey</code>
#* Server: Let's Encrypt Production
# '''Issue the Certificate:'''
#* Go to '''Services > ACME > Certificates'''.
#* Click '''Add'''.
#* '''Name:''' <code>CaptivePortalCert</code>
#* '''Domain name:''' <code>mywifinetwork.duckdns.org</code>
#* '''Method:''' DNS-DuckDNS
#* '''Token:''' Paste your token
#* Click '''Save''' then '''Issue/Renew'''.

----

== Phase 3: Split DNS Configuration ==

Ensure users resolve the domain to the local IP.

# Navigate to '''Services > DNS Resolver'''.
# Go to '''Host Overrides > Add'''.
#* '''Host:''' <code>mywifinetwork</code>
#* '''Domain:''' <code>duckdns.org</code>
#* '''IP Address:''' <code>192.168.2.1</code> (Guest Interface IP)
# Click '''Save''' and '''Apply Changes'''.

----

== Phase 4: Configure FreeRADIUS (Users & Bandwidth) ==

We will define three users with specific bandwidth limits.

=== 1. Interfaces & Client ===
* '''Services > FreeRADIUS > Interfaces:''' Add <code>*</code> for ports 1812 & 1813.
* '''Services > FreeRADIUS > NAS / Clients:''' Add <code>127.0.0.1</code> with secret <code>SecretPass123</code>.

=== 2. Create Users ===

{| class="wikitable"
|-
! User
! Username
! Password
! Bandwidth Down
! Bandwidth Up
|-
| '''Admin (Full Access)'''
| <code>adminuser</code>
| <code>adminpass</code>
| Unlimited (leave blank)
| Unlimited (leave blank)
|-
| '''Resident (0.1 Mbps)'''
| <code>resident</code>
| <code>resident123</code>
| 100 Kbps
| 100 Kbps
|-
| '''Guest (0.01 Mbps)'''
| <code>guest</code>
| <code>guest123</code>
| 10 Kbps
| 10 Kbps
|}

----

== Phase 5: Firewall Rules & Whitelisting ==

=== Step A: Define Admin Devices (Static IPs) ===
# Go to '''Services > DHCP Server > [Guest Interface]'''.
# Scroll to '''Static Mappings'''.
# Add your Admin Device's MAC Address and assign a specific IP (e.g., <code>192.168.2.10</code>).
# Repeat for all Admin devices.

=== Step B: Create Aliases (The Whitelist) ===
# Go to '''Firewall > Aliases'''.
# '''Create Admin Alias:'''
#* '''Name:''' <code>Admin_IPs</code>
#* '''Type:''' Host(s)
#* '''Content:''' <code>192.168.2.10</code> (and other admin IPs)
# '''Create Apps Alias:'''
#* '''Name:''' <code>Allowed_Domains</code>
#* '''Type:''' Host(s)
#* '''Content:''' <code>grab.com</code>, <code>lalamove.com</code>, <code>api.grab.com</code>, <code>api.lalamove.com</code>
# '''Create Messaging Ports Alias:'''
#* '''Name:''' <code>Messaging_Ports</code>
#* '''Type:''' Port(s)
#* '''Content:''' 3478 (WhatsApp/Messenger STUN), 5222 (WhatsApp/XMPP), 443 (HTTPS), 53 (DNS)

=== Step C: Apply Strict Rules ===
Go to '''Firewall > Rules > [Guest Interface]'''. '''Delete''' any existing "Allow All" rules. Create these rules in this '''exact order''':

{| class="wikitable"
|-
! Rule #
! Action
! Source
! Destination
! Result
|-
| 1
| Pass
| Single Host or Alias → <code>Admin_IPs</code>
| Any
| Admins bypass all blocks.
|-
| 2
| Pass (UDP)
| Any
| Port 53 (DNS)
| Everyone needs DNS to function.
|-
| 3
| Pass (TCP/UDP)
| Any
| <code>Allowed_Domains</code>, Port 443
| Allows traffic to Grab/Lalamove IPs.
|-
| 4
| Pass (TCP/UDP)
| Any
| Any, Port → <code>Messaging_Ports</code>
| Allows WhatsApp/Messenger calls.
|-
| 5
| '''Block'''
| Any
| Any
| Blocks YouTube, Social Media, general browsing for Residents/Guests.
|}

----

== Phase 6: Configure the Captive Portal ==

# '''Enable Portal:'''
#* Go to '''Services > Captive Portal'''.
#* Add Zone <code>GuestZone</code>, Enable it, select Guest Interface.
# '''Authentication:'''
#* '''Method:''' RADIUS Authentication
#* '''Primary Server:''' <code>127.0.0.1</code>, Secret: <code>SecretPass123</code>
#* '''Re-authentication:''' Checked (Every minute)
#* '''RADIUS Options:''' Check '''Use RADIUS per-user bandwidth attributes'''
# '''HTTPS Login:'''
#* '''Enable HTTPS:''' Checked
#* '''Host Name:''' <code>mywifinetwork.duckdns.org</code>
#* '''Certificate:''' <code>CaptivePortalCert</code>
# Click '''Save'''.

----

== Phase 7: Verification ==

=== Test Admin ===
* Connect with an Admin device (ensure it gets Static IP <code>192.168.2.10</code>).
* Log in as <code>adminuser</code>.
* Try YouTube. '''Result:''' Should work.

=== Test Resident ===
* Connect with a random phone.
* Log in as <code>resident</code>.
* Try Fast.com. '''Result:''' Speed capped at 0.1 Mbps.
* Try YouTube. '''Result:''' Blocked.
* Try Grab App. '''Result:''' Should load.

=== Test Guest ===
* Log in as <code>guest</code>.
* Try Fast.com. '''Result:''' Speed capped at 0.01 Mbps (very slow).

Viber Focus-Stealing

2026-02-25T07:02:21Z

BabiSender: Created page with "== Disable Viber Notifications (Ubuntu Flatpak Version) == Follow these steps to stop Viber from interrupting your typing or switching your active window. === 1. Open Viber === Launch the Viber application from your applications menu. === 2. Go to Settings === Click the gear icon in the upper-right corner of the Viber window. === 3. Select Notifications === In the sidebar menu, click '''Notifications'''. === 4. Turn Off All Notification Types === Inside the Noti..."

== Disable Viber Notifications (Ubuntu Flatpak Version) ==

Follow these steps to stop Viber from interrupting your typing or switching your active window.

=== 1. Open Viber ===

Launch the Viber application from your applications menu.

=== 2. Go to Settings ===

Click the gear icon in the upper-right corner of the Viber window.

=== 3. Select Notifications ===

In the sidebar menu, click '''Notifications'''.

=== 4. Turn Off All Notification Types ===

Inside the Notifications section, switch '''off''' the following items:

* 1-on-1 messages
* Group messages
* Communities / Channels
* Service messages
* Mentions
* All messages (sound)
* Combined notifications
* Unread badge (effects)

This prevents Viber from triggering pop-ups or requesting attention.

----

== What is "Focus Stealing"? ==

"Focus stealing" happens when an application forces itself to the front or grabs the keyboard focus while you're actively using another window. On Ubuntu, this can cause:

* Keystrokes going into the wrong app
* The active window losing control
* Your typing suddenly doing nothing

Some apps do this when displaying notifications. Disabling notifications prevents Viber from grabbing the focus and interrupting your work.

Mailcow + Thunderbird Setup Guide (Email + Calendar)

2026-02-25T07:02:04Z

BabiSender: Created page with "= Mailcow + Thunderbird Setup Guide (Email + Calendar) = This guide shows staff how to properly connect '''Thunderbird''' to '''Mailcow''' for: * Email (IMAP + SMTP) * Calendar (CalDAV via SOGo) {{Note|If your account has '''2FA enabled''', you '''must use an App Password'''. Thunderbird will not work with your normal login password.}} ---- == 1. Create an App Password in Mailcow == # Log in to your Mailcow webmail account. # Open the '''Mailbox''' menu. # Select ''..."

= Mailcow + Thunderbird Setup Guide (Email + Calendar) =

This guide shows staff how to properly connect '''Thunderbird''' to '''Mailcow''' for:
* Email (IMAP + SMTP)
* Calendar (CalDAV via SOGo)

{{Note|If your account has '''2FA enabled''', you '''must use an App Password'''. Thunderbird will not work with your normal login password.}}

----

== 1. Create an App Password in Mailcow ==

# Log in to your Mailcow webmail account.
# Open the '''Mailbox''' menu.
# Select '''App Passwords'''.
# Click '''Create app password'''.
# Name it something like: <code>Thunderbird</code>.
# Choose allowed protocols:
#* IMAP
#* SMTP
#* DAV (for calendar)
# Copy the generated password.

----

== 2. Configure Email in Thunderbird ==

# Open Thunderbird.
# Go to '''Account Settings → Add Mail Account'''.
# Enter:
#* Your full email address
#* Any name you prefer
#* '''App Password''' from Mailcow ('''NOT''' your main password)
# Thunderbird should auto-detect settings.

=== Required Server Settings ===

{| class="wikitable"
|-
! Setting
! Value
|-
| '''Incoming (IMAP) – Host'''
| Your Mailcow server domain
|-
| '''Incoming (IMAP) – Port'''
| 993
|-
| '''Incoming (IMAP) – SSL'''
| SSL/TLS
|-
| '''Incoming (IMAP) – Authentication'''
| Normal Password
|-
| '''Outgoing (SMTP) – Host'''
| Your Mailcow server domain
|-
| '''Outgoing (SMTP) – Port'''
| 465 (or 587 if needed)
|-
| '''Outgoing (SMTP) – SSL'''
| SSL/TLS
|-
| '''Outgoing (SMTP) – Authentication'''
| Normal Password
|}

----

== 3. Enable CalDAV Calendar in Thunderbird ==

Mailcow uses SOGo for calendar sync.

# In Thunderbird, go to '''Calendar'''.
# Click '''+ New Calendar'''.
# Choose '''On the Network'''.
# Select '''CalDAV'''.
# Enter your calendar URL (example format):
<pre>https://your-mailcow-server/SOGo/dav/your-email/Calendar/personal/</pre>
# When prompted:
#* '''Username:''' Your full email address
#* '''Password:''' Your '''App Password'''
# Complete setup.

----

== 4. Common Issues to Avoid ==

* Using your '''main password''' instead of an '''App Password''' → causes "wrong credentials."
* Forgetting that the calendar URL must end with a '''trailing slash''' <code>/</code>.
* Choosing the wrong authentication type (must be '''Normal Password''').
* Having saved old passwords in Thunderbird. Clear them here:
** '''Settings → Privacy & Security → Saved Passwords''' → Remove old entries.

----

== 5. Verification Checklist ==

* Email works for sending and receiving.
* Calendar events appear in Thunderbird.
* Your App Password is active in the Mailcow App Passwords list.

----

If these steps are followed, Thunderbird will reliably sync both email and calendar with Mailcow.

Spoof Timezone Extension – Setup Guide for Comfac Staff

2026-02-25T07:01:39Z

BabiSender: Created page with "= Spoof Timezone Extension – Setup Guide for Comfac Staff = This guide explains how to configure the '''Spoof Timezone''' extension in LibreWolf/Firefox so staff can maintain '''privacy protection''' while ensuring '''Nextcloud, Mailcow, and other Comfac tools display correct timestamps'''. Use this setup if you rely on privacy extensions that hide your timezone, but still need accurate time and calendar functionality on Comfac systems. ---- == 1. Open the Spoof Ti..."

= Spoof Timezone Extension – Setup Guide for Comfac Staff =

This guide explains how to configure the '''Spoof Timezone''' extension in LibreWolf/Firefox so staff can maintain '''privacy protection''' while ensuring '''Nextcloud, Mailcow, and other Comfac tools display correct timestamps'''.

Use this setup if you rely on privacy extensions that hide your timezone, but still need accurate time and calendar functionality on Comfac systems.

----

== 1. Open the Spoof Timezone Extension Settings ==

Paste the following into your browser address bar:

<pre>moz-extension://e2416390-3967-4dec-9c8b-36eacabf59ce/data/options/index.html</pre>

If this link changes on another device, open: '''Extensions → Spoof Timezone → Options'''

----

== 2. Confirm Your Real Timezone ==

Under '''Timezone''', set:

<pre>Asia/Manila (GMT+8)</pre>

Make sure '''both''' the dropdown and the text field show <code>Asia/Manila</code>.

Leave the following '''unchecked''':
* Automatically update timezone based on my IP address
* Pick a random time zone

----

== 3. Do NOT Change "Protection Scope" ==

Keep the default:

<pre>*://*/*</pre>

This means the extension protects every website '''except''' those you explicitly whitelist. No need to modify this section.

----

== 4. Add Comfac Services to the Whitelist ==

In the '''Whitelisted Sites''' box, add the following entries '''one per line''':

<pre>
*://challenges.cloudflare.com/*
*://mail.comfac-it.com/*
*://next.comfaccorp.com/*
</pre>

=== What Whitelisting Does ===

Whitelisting a site tells the extension:

: '''"Do NOT spoof the timezone for this domain. Use the real timezone."'''

This is required for:
* Correct email timestamps (Mailcow)
* Correct event times & reminders (Nextcloud Calendar)
* Correct file edit timestamps

----

== 5. Save Your Settings ==

# Click '''Save Options''' at the bottom.
# Refresh any open Comfac tabs.

----

== 6. When to Use This Setup ==

Staff should follow this guide if they:
* Use LibreWolf or Firefox hardened with privacy extensions
* Use Nextcloud calendar, tasks, files, or Mailcow webmail
* Want privacy protection without breaking time-sensitive tools

If you encounter incorrect times in calendar or email, re-check the whitelist entries.

----

== 7. Support ==

For help, contact IT:

<pre>it@comfac-it.com</pre>

Or send a screenshot to the IT support group chat.

Introduction: Why Self-Host Your Email?

2026-02-25T07:01:13Z

BabiSender: Created page with "= Introduction: Why Self-Host Your Email? = Self-hosting your email provides complete control, privacy, and security over your communications. This guide details the process from start to finish, even for those unfamiliar with server management. '''Reference Video:''' [https://www.youtube.com/watch?v=CvQny6sYVxg How to Self-Host Email the Right Way (to avoid the spam folder)] === What This Guide Covers === # Launch a cloud-based Ubuntu Virtual Private Server (VPS). #..."

= Introduction: Why Self-Host Your Email? =

Self-hosting your email provides complete control, privacy, and security over your communications. This guide details the process from start to finish, even for those unfamiliar with server management.

'''Reference Video:''' [https://www.youtube.com/watch?v=CvQny6sYVxg How to Self-Host Email the Right Way (to avoid the spam folder)]

=== What This Guide Covers ===
# Launch a cloud-based Ubuntu Virtual Private Server (VPS).
# Configure all necessary DNS records for your custom domain.
# Install Docker and Docker Compose.
# Set up and configure mailcow, a comprehensive open-source mail server suite.
# Test and validate email deliverability.

----

== Phase 1: Server and DNS Prerequisites ==

Before you begin, you must have two things:

=== 1. A Domain Name ===
You need a domain (e.g., <code>yourdomain.com</code>) purchased from any registrar (like Netim, GoDaddy, Namecheap, etc.).

=== 2. A Cloud VPS ===
You '''cannot''' host this at home, as most Internet Service Providers (ISPs) block '''Port 25''', which is essential for email.

* '''Provider:''' You must use a hosting provider (like Verpex) that explicitly '''allows Port 25''' and lets you set '''PTR (Pointer) records'''.
* '''System Requirements:'''
** '''Minimum:''' 6GB RAM, 20GB disk space, 1 CPU.
** '''Budget (Not Recommended):''' 4GB RAM will work, but you '''must disable the antivirus (ClamAV) component''' in mailcow, reducing security.
* '''Operating System:''' This guide uses '''Ubuntu'''.

Once your VPS is active, locate its public '''IP Address'''. This will be used in all following steps.

----

== Phase 2: Initial DNS Record Configuration ==

This is the most critical step for ensuring your server can be found. Go to your domain registrar's DNS management panel.

'''Replace <code>yourdomain.com</code> with your actual domain.'''
'''Replace <code>[Server IP]</code> with your VPS's public IP address.'''

{| class="wikitable"
|-
! Type
! Name / Host
! Value / Target
! Priority
! Details
|-
| '''A'''
| @ (or yourdomain.com)
| [Server IP]
| N/A
| Points your root domain to the server.
|-
| '''A'''
| mail (or mail.yourdomain.com)
| [Server IP]
| N/A
| Creates the hostname for the mail server itself.
|-
| '''MX'''
| @ (or yourdomain.com)
| mail.yourdomain.com
| 10
| Directs all email for your domain to your new mail server.
|-
| '''CNAME'''
| autodiscover
| mail.yourdomain.com
| N/A
| Helps email clients (like Outlook) automatically find settings.
|-
| '''CNAME'''
| autoconfig
| mail.yourdomain.com
| N/A
| Helps email clients (like Thunderbird) automatically find settings.
|-
| '''SRV'''
| _autodiscover._tcp
| mail.yourdomain.com
| 0 (Prio) 0 (Weight) 443 (Port)
| An additional record for auto-discovery services.
|}

After saving, use '''mxtoolbox.com''' to do a "DNS Lookup" for <code>mail.yourdomain.com</code> and verify your server IP. DNS propagation can take up to 24 hours.

----

== Phase 3: The PTR (Reverse DNS) Record ==

This record is essential for deliverability and proving you aren't a spammer. It maps your server's IP address ''back'' to your domain.

# You '''cannot set this record yourself'''.
# You must open a '''support ticket''' with your hosting provider.
# Send them a message like: ''Hello, please set the PTR (Reverse DNS) record for my server's IP address [Server IP] to point to the hostname mail.yourdomain.com.''

----

== Phase 4: Server Setup & Docker Installation ==

Open a Terminal (macOS/Linux) or Command Prompt/PowerShell (Windows).

# '''Log in as root:'''
<pre>ssh root@yourdomain.com</pre>

# '''Update Your Server:'''
<pre>apt update
apt upgrade -y</pre>

# '''Install Dependencies:'''
<pre>apt install git openssl curl -y</pre>

# '''Create a New User''' (Security Best Practice — replace <code>tony</code> with your username):
<pre>adduser tony</pre>

# '''Give New User Sudo Privileges:'''
<pre>usermod -aG sudo tony</pre>

# '''Switch to Your New User:'''
<pre>su - tony</pre>

# '''Install Docker:'''
<pre>curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh</pre>

# '''Add Your User to the Docker Group:'''
<pre>sudo usermod -aG docker $USER</pre>

# '''Reboot the Server:'''
<pre>sudo reboot</pre>

----

== Phase 5: Install & Configure mailcow ==

# '''Log Back In''' after reboot as your new user (e.g., <code>ssh tony@yourdomain.com</code>).

# '''Set umask:'''
<pre>umask 0022</pre>

# '''Clone mailcow''' (install in <code>/opt/</code>):
<pre>cd /opt/
sudo git clone https://github.com/mailcow/mailcow-dockerized
cd mailcow-dockerized/</pre>

# '''Find Your Timezone:'''
<pre>timedatectl list-timezones</pre>
To search: <code>timedatectl list-timezones | grep 'New_York'</code>

# '''Generate Configuration File:'''
<pre>sudo ./generate-config.sh</pre>
You will be asked:
#* '''Mail server hostname (FQDN):''' Enter <code>mail.yourdomain.com</code>
#* '''Timezone:''' Enter your timezone (e.g., <code>America/New_York</code>)
#* '''Which branch:''' Choose <code>1</code> for stable master branch

# '''Pull & Run mailcow:'''
<pre>sudo docker compose pull
sudo docker compose up -d</pre>

# '''Verify Installation:'''
<pre>sudo docker compose ps</pre>
Check the "Status" column. If anything is "down" or "unhealthy," wait a few minutes and check again.

----

== Phase 6: mailcow Admin & Domain Setup ==

# '''Access mailcow Admin:''' Go to <code>https://mail.yourdomain.com</code> in your browser.
# '''Log In as Admin:'''
#* Click the '''"Login as admin"''' link at the bottom.
#* '''Username:''' <code>admin</code>
#* '''Password:''' <code>moohoo</code>
# '''CRITICAL: Change Admin Password:'''
#* Go to '''System > Configuration > Access'''.
#* Click '''Edit''' next to the admin user, enter a strong password, and '''Save Changes'''.
# '''Add Your Email Domain:'''
#* Go to '''Email > Configuration > Domains''' tab.
#* Click '''Add Domain'''.
#* '''Domain:''' Enter your root domain (e.g., <code>yourdomain.com</code>).
#* Leave other settings as default.
#* Click '''"Add domain and restart SOGO"'''.
# '''Create Your First Mailbox:'''
#* Go to '''Mailboxes > Mailboxes'''.
#* Click '''Add mailbox'''.
#* '''Username:''' Enter the first part of your email (e.g., <code>tony</code>).
#* '''Domain:''' Select <code>yourdomain.com</code>.
#* Enter your name and a strong password.
#* Click '''Add'''.

----

== Phase 7: Final DNS Records for Deliverability ==

# In mailcow admin, go to '''Email > Configuration > Domains''' tab.
# Click the '''"DNS"''' button next to your domain.
# Add the following records to your domain registrar:

{| class="wikitable"
|-
! Type
! Name / Host
! Value / Target
! Notes
|-
| '''TXT (DKIM)'''
| dkim._domainkey
| v=DKIM1; k=rsa; p=[...long string...]
| '''Copy the exact Name and Value from the mailcow DNS page.'''
|-
| '''TLSA'''
| _25._tcp.mail
| 3 1 1 [...long hash string...]
| '''Copy the exact Name and Value.''' Your registrar may have separate fields for Usage (3), Selector (1), and Matching (1).
|-
| '''TXT (SPF)'''
| @
| v=spf1 mx a -all
| Strict starting value — only your A and MX records are allowed to send mail.
|-
| '''TXT (DMARC)'''
| _dmarc
| v=DMARC1; p=none
| '''WAIT!''' Add this only '''48 hours''' after SPF/DKIM are set. <code>p=none</code> means "monitor only."
|}

4. '''Enable DNSSEC:''' In your domain registrar's settings, find '''DNSSEC''' and '''Enable''' it. Required for the TLSA record to function.

----

== Phase 8: Testing Deliverability ==

# '''Log in to Your New Inbox:'''
#* Go to <code>https://mail.yourdomain.com</code>.
#* Log in as your user (e.g., <code>tony@yourdomain.com</code>).
# '''Test with Mail-Tester:'''
#* Go to [https://mail-tester.com mail-tester.com].
#* Copy the unique email address provided.
#* Compose a '''realistic email''' (subject: ''Inquiry about your services'', body: a few real sentences — ''not'' "test").
#* Send to the mail-tester address and check your score. Aim for '''10/10'''.
# '''Test with a Real Provider (Gmail):'''
#* Send a realistic email to a Gmail, Outlook, or Yahoo address you own.
#* '''Check if it lands in the Inbox.''' If it goes to spam, double-check all DNS records.

----

== Phase 9: Critical Next Steps (Maintenance) ==

* '''Email Warm-Up:''' Do NOT start blasting hundreds of emails. Your new IP has no reputation. Send a few emails per day and gradually increase volume over weeks.
* '''Server Security:'''
** '''Enable a Firewall (UFW):''' Block all ports except those needed (SSH, HTTP/S, and mail ports).
** '''Harden SSH:''' Disable password-based login and use '''SSH keys only'''. This is the single most important security measure.
** '''Stay Updated:''' Regularly run <code>sudo apt update && sudo apt upgrade -y</code> to apply security patches.

PfSense CE → pfSense Plus Upgrade Guide

2026-02-25T07:00:48Z

BabiSender: Created page with "= pfSense CE → pfSense Plus Upgrade Guide = '''Reference Video:''' [https://www.youtube.com/watch?v=Fa1NAuWDzjs Comparing pfSense Plus & pfSense CE: Cost and Key Differences Explained] '''Official Netgate Migration Guide:''' [https://docs.netgate.com/pfsense/en/latest/install/migrate-to-plus.html Migrate from pfSense CE to pfSense Plus] This guide consolidates the full set of steps and best practices for upgrading a system from '''pfSense Community Edition (CE)''' t..."

= pfSense CE → pfSense Plus Upgrade Guide =

'''Reference Video:''' [https://www.youtube.com/watch?v=Fa1NAuWDzjs Comparing pfSense Plus & pfSense CE: Cost and Key Differences Explained]

'''Official Netgate Migration Guide:''' [https://docs.netgate.com/pfsense/en/latest/install/migrate-to-plus.html Migrate from pfSense CE to pfSense Plus]

This guide consolidates the full set of steps and best practices for upgrading a system from '''pfSense Community Edition (CE)''' to '''pfSense Plus'''.

----

== Differences Between pfSense CE and pfSense Plus ==

=== 1. Cost & Licensing ===
* '''pfSense CE:''' Completely free, community-supported.
* '''pfSense Plus:''' Free for '''home''' and '''lab''' use. Automatic entitlement when used on Netgate hardware; CE → Plus migration requires registration but remains free.

=== 2. Support Model ===
* '''CE:''' Community forums only.
* '''Plus:''' Eligible for paid Netgate TAC support.

=== 3. Base System & Release Cadence ===
* Both share the same FreeBSD base (FreeBSD 14 as of 2023).
* '''Plus''' receives '''more frequent releases''' and hotfixes.
* '''CE''' has a '''longer release cycle'''.

=== 4. Features Exclusive to pfSense Plus ===

{| class="wikitable"
|-
! Feature
! CE
! Plus
|-
| Boot Environments (automatic snapshots)
| ❌
| ✔️
|-
| QAT Crypto Acceleration
| ❌
| ✔️
|-
| OpenVPN DCO (Data Channel Offload – Beta)
| ❌
| ✔️
|-
| OpenVPN Client Import Tool
| ❌
| ✔️
|-
| AWS VPN Wizard
| ❌
| ✔️
|-
| IPsec Export for Apple Profiles
| ❌
| ✔️
|-
| IPsec Export for Windows PowerShell
| ❌
| ✔️
|}

=== 5. Features Fully Available on Both ===
Both versions support: High Availability (CARP), VLANs, OpenVPN, WireGuard, IPSec, L2TP, ZFS file system, and all major routing & firewall features.

=== 6. ZFS & Boot Environments Clarification ===
* '''Both''' CE and Plus support ZFS.
* '''Only Plus''' includes the Boot Environment GUI tools + auto-snapshot during upgrades.
* CE requires more manual ZFS handling.

=== 7. Security Patch Handling ===
* Plus receives '''faster updates''' to the base OS when needed.
* CE updates are slower but still maintained and not considered unsafe.

----

== 1. Before You Begin ==

=== A. Confirm Requirements ===
* A Netgate account with an activated pfSense+ subscription or device entitlement.
* Your pfSense CE must be '''2.6 or later'''.
* Internet connectivity for the upgrade process.

=== B. Prepare Backups ===
* Go to '''Diagnostics → Backup/Restore'''.
* Download the latest full configuration backup.
* If virtualized: take a VM snapshot.
* If physical: prepare a USB installer for pfSense+ (failsafe recovery option).

=== C. Review Boot Environments ===
* pfSense CE/Plus uses ZFS Boot Environments.
* Each upgrade automatically creates a new boot environment (snapshot).
* You may manually create one via: '''System → Boot Environments → Create'''.

----

== 2. Clean Up Before Upgrading ==

=== A. Evaluate Installed Packages ===
Netgate best practice:
* '''Uninstall all third-party packages''' before upgrade.
* When uninstalling, choose '''"Keep configuration files"'''.
** This allows you to reinstall packages after the upgrade with your settings intact.

If you decide to upgrade with packages installed:
* Do this '''only if you understand the risks'''.
* Some packages may break the upgrade or behave unpredictably.

----

== 3. Enable Upgrade to pfSense Plus ==

=== A. Purchase, Receive Token, and Prepare for Migration ===

==== 1. Purchase the Correct Subscription ====
* Go to the '''Netgate Store'''.
* Choose '''pfSense+ Software Subscription with TAC Lite Support''' (or the appropriate plan).
* In the dropdown, select: '''Upgrade from pfSense CE to pfSense Plus'''
** ''(Do NOT leave it on Renewal/New Install.)''
* Add to cart and complete checkout.

After purchase, '''Netgate will email the activation token''' to the email address on the store account.

{{Note|If the token email does not arrive quickly, check spam/junk folders. Tokens are '''single-use''' — ensure the CE system is stable and in its intended configuration before proceeding.}}

=== B. Register pfSense CE Using the Token ===
# In the pfSense CE GUI, navigate to '''System → Register'''.
# Paste the activation token.
# Click '''Register'''.
# Confirm registration success on the page.

=== C. Switch to the pfSense Plus Upgrade Branch ===
# Go to '''System → Update'''.
# The page should now announce availability of the pfSense Plus migration branch.
# Set '''Branch''' to: '''pfSense Plus Upgrade'''
# Wait for the update check to finish.

=== D. Begin the Migration Upgrade ===
* Click '''Confirm''' to start the migration.
* This will convert CE → Plus as part of the upgrade process.

=== E. Switch Update Branch (Post-Migration) ===
# Go to '''System → Update'''.
# Click the '''Update Settings''' tab.
# Change '''Branch''' to: '''Current Stable Version (Plus 25.07 or newer)'''.

=== F. Verify Licensing ===
If your CE system is not yet entitled for pfSense+:
* Go to '''System → Registration'''.
* Log in using your Netgate account.
* Attach device to your subscription.

----

== 4. Perform the Upgrade ==

=== A. Start the Upgrade ===
# Go to '''System → Update'''.
# Click the '''Cloud icon''' to retrieve latest metadata.
# Wait for system to check installed version vs available version.
# When the upgrade path appears (example: ''24.11 → 25.07''), click '''Confirm Update'''.

=== B. DO NOT Leave the Page ===
* Keep the browser tab '''open and running''' during the entire upgrade process — do not close, refresh, or navigate away.
* If possible, monitor via the physical console.

=== C. Automatic Reboot ===
* System will download packages, verify signatures, create a new boot environment, apply updates, then reboot.
* During reboot: do '''not''' power off or reset.
* Expect '''long startup times''' — sometimes several minutes. The system is applying updates and rebuilding components. '''Do not assume it is stuck; give it plenty of time.'''

The browser will auto-refresh and reconnect when the web GUI is back.

----

== 5. Post-Upgrade Validation ==

=== A. Log In and Verify Version ===
* Dashboard should show: '''pfSense Plus 25.07.xx''' (or newer).

=== B. Verify Package Compatibility ===
# Go to '''System → Package Manager'''.
# Click '''Available Updates'''.
# Ensure all installed packages are updated.

=== C. Check for Hotfix Patches ===
# Go to '''System → Patches'''.
# Confirm that no new patches are required.

----

== 6. Restore Packages (If You Uninstalled Them Earlier) ==

# Go to '''System → Package Manager → Available Packages'''.
# Reinstall packages one by one.
# Your previous configurations should auto-apply.

----

== 7. Rollback (If Something Breaks) ==

=== Option A: Restore Boot Environment ===
# Reboot pfSense.
# From bootloader menu choose '''Boot Environments'''.
# Select the older (pre-upgrade) environment.

=== Option B: Reinstall Using Online Installer ===
# Boot from USB installer.
# Choose '''Recover Configuration from URL'''.
# Upload or paste your backup file.

----

== Comfac-IT Internal Note (Licensing for Clients) ==

Some Comfac-IT clients prefer to purchase '''pfSense Plus licenses''' through us. When we buy from the Netgate Shop, we receive the '''activation tokens''', and we are responsible for their issuance and tracking.

'''Internal workflow:'''
* Schedule a '''calendar reminder''' exactly '''1 month before token expiration'''.
* Coordinate with the client early to ensure tokens are used on time.

{| class="wikitable"
|-
! Item
! Amount
|-
| Token cost from Netgate
| PHP 7,740
|-
| Comfac-IT selling price
| PHP 8,000
|-
| Margin
| PHP 260
|}

These amounts are small, so efficiency and proper scheduling are critical.

----

== 8. Final Recommendations ==

=== A. Maintain Good Upgrade Hygiene ===
* Always backup before upgrading.
* Always keep a recovery USB.
* Only upgrade when you have a recovery window (off-hours).

=== B. Best for Production ===
* Physical hardware for stable routing.
* Virtualization for labs and home setups.

=== C. Verify Logs ===
* Check '''Status → System Logs → General / Package / Boot''' for anomalies.

LibreOffice / Nextcloud Office – "Due Tasks" Conditional Formatting

2026-02-25T07:00:30Z

BabiSender: Created page with "== LibreOffice Calc – "Due Tasks" Conditional Formatting == Highlight whole rows in '''red''' when a task is due and must be acted on. ---- == Goal and Logic == === Core Conditions === For a row to be considered '''due''', two things must be true: ; Target Date condition : The '''Target Date''' in column <code>E</code> must be '''today or earlier'''. Past dates have smaller numeric values than today, so the check is: <code>TODAY() >= TargetDate</code> ; Is It Du..."

== LibreOffice Calc – "Due Tasks" Conditional Formatting ==

Highlight whole rows in '''red''' when a task is due and must be acted on.

----

== Goal and Logic ==

=== Core Conditions ===

For a row to be considered '''due''', two things must be true:

; Target Date condition
: The '''Target Date''' in column <code>E</code> must be '''today or earlier'''. Past dates have smaller numeric values than today, so the check is: <code>TODAY() >= TargetDate</code>

; Is It Due flag
: Column <code>F</code> ('''IS IT DUE''') must evaluate to '''TRUE'''. Typically this is a formula in F2 like <code>=TODAY() >= E2</code>, which returns TRUE when the target date is today or in the past.

; Target Date must exist
: Column <code>E</code> must contain a real date value — not text and not blank — so empty rows do not turn red.

=== Combined Logical Test ===

To safely check all three rules inside Conditional Formatting:

<syntaxhighlight lang="text">
AND(ISNUMBER($E2); $F2=TRUE())
</syntaxhighlight>

{| class="wikitable"
|-
! Part !! Meaning
|-
| <code>ISNUMBER($E2)</code> || TRUE only if there is a valid date in column E
|-
| <code>$F2=TRUE()</code> || TRUE only if the IS IT DUE column is TRUE
|-
| <code>AND()</code> || Both conditions must be TRUE to trigger highlighting
|-
| <code>$</code> on the column || Locks the column; the row number changes as the rule applies down the sheet
|}

If either condition is false — no date in E, or F is FALSE — the row stays unformatted.

----

== Step-by-Step Setup ==

=== Step 0 – Prepare the Sheet ===

# Make sure column '''E''' contains real dates (the formula bar shows something like <code>11/14/2025</code>, not <code>251114</code>).
# Make sure column '''F''' returns actual TRUE/FALSE values using a formula like <code>=TODAY()>=E2</code>.

=== Step 1 – Select the Rows to Format ===

Click and drag to select the full range you want to affect, for example:
* <code>A2:F200</code>
* or <code>A2:XFD25839</code> if you want the rule to span the full width of each row.

=== Step 2 – Open Conditional Formatting Manager ===

Go to: '''Format → Conditional → Manage…'''

In the dialog, confirm the '''Cell Range''' at the bottom matches your selection (e.g. <code>A2:F200</code>).

=== Step 3 – Add a New Condition ===

# Click '''Add''' to insert a new condition line.
# Change the first dropdown from <code>Cell value is</code> to '''<code>Formula is</code>'''.
# In the formula box, enter:

<syntaxhighlight lang="text">
AND(ISNUMBER($E2); $F2=TRUE())
</syntaxhighlight>

=== Step 4 – Define the Red Row Style ===

# In '''Apply Style''', click the dropdown and choose '''New Style…'''
# Give it a clear name such as <code>DueRowRed</code>.
# Go to the '''Background''' tab and choose a red or light red fill color.
# Optionally set text to '''Bold''' or change the font color for extra emphasis.
# Click '''OK''' to save the style.

=== Step 5 – Apply and Test ===

# Click '''OK''' to close the Conditional Formatting dialog.
# Test a few rows:
#* Put a valid date in <code>E2</code> that is today or in the past.
#* Confirm <code>F2</code> evaluates to TRUE (<code>=TODAY()>=E2</code>).
#* The row should now turn red.

Test edge cases:

{| class="wikitable"
|-
! Scenario !! Expected Result
|-
| Blank E cell with F=TRUE || Row does '''not''' turn red (<code>ISNUMBER</code> returns FALSE)
|-
| Future date in E || F formula returns FALSE → row stays neutral
|-
| Non-date text in E || <code>ISNUMBER($E2)</code> returns FALSE → row stays neutral
|}

----

== Summary ==

{| class="wikitable"
|-
! Element !! Detail
|-
| Business rule || A task is due when it has a target date (E) that is today or earlier, and IS IT DUE (F) is TRUE
|-
| Formula column F || <code>=TODAY()>=E2</code>
|-
| Conditional format formula || <code>AND(ISNUMBER($E2); $F2=TRUE())</code>
|-
| Result || Only real, due tasks highlight red; incomplete or future tasks stay neutral
|}

Partner Reseller Pricing 251109

2026-02-25T07:00:04Z

BabiSender: Created page with "= Partner Reseller Pricing = == Summary == * The standard pricing multiplier is '''1 / 0.6 = 1.67 (rounded up from 1.6666)'''. This means there is a '''33% margin''' difference between the at-cost price and the selling price. * '''Subcon-Partner Pricing:''' Defines how AA and Comfac split profits (60% Comfac / 40% AA) and handle material and labor costs, including warranty and support. * '''Comfac Partner-Level-1 (P1) Pricing:''' Used when Comfac sells technology or sy..."

= Partner Reseller Pricing =

== Summary ==

* The standard pricing multiplier is '''1 / 0.6 = 1.67 (rounded up from 1.6666)'''. This means there is a '''33% margin''' difference between the at-cost price and the selling price.
* '''Subcon-Partner Pricing:''' Defines how AA and Comfac split profits (60% Comfac / 40% AA) and handle material and labor costs, including warranty and support.
* '''Comfac Partner-Level-1 (P1) Pricing:''' Used when Comfac sells technology or systems (e.g., BMS) to ESCO, Cornersteel, or other strategic partners at 15% markup based on internal 1.67 multiplier.
* '''Reseller Agreement:''' Applies to approved resellers who get a 25% discount on Comfac's 1.67 pricing, with Comfac keeping 15.15% net margin.
* '''ESCO Note:''' ESCO manages warranty and planned maintenance. Future coordination required for pricing and coverage.

----

== Definition of Terms ==

{| class="wikitable"
|-
! Term
! Definition
|-
| '''At-Cost Price'''
| The total direct cost of materials and labor before applying any margin or multiplier.
|-
| '''Multiplier (1.67)'''
| Derived from 1 / 0.6, used to calculate selling price from cost, reflecting a 33% margin over at-cost.
|-
| '''Margin'''
| The percentage difference between at-cost and selling price; typically 33% for Comfac pricing models.
|-
| '''Buffer'''
| Additional 20% added to labor and material estimates to cover unforeseen costs or contingencies.
|-
| '''Warranty Period'''
| One-year coverage included in the Subcon-Partner pricing for post-project support.
|-
| '''PR-PO System'''
| Comfac's internal Purchase Request–Purchase Order tracking in ERPNext used for recording materials and project costs.
|}

----

== 1. Subcon-Partner Pricing (AA and Comfac) ==

This refers to AA/Subcon-Partner pricing for '''Labor and Materials''', inclusive of '''Support and Warranty for one year'''.

=== 1.1 Estimation and Approval ===
Materials and labor estimates are prepared by RJ and Andrei, then submitted to Jun and Jonathan for pricing review and approval.

* '''1.1.1''' Materials can have a margin calculated as '''Materials / 0.6 (or 166.66%)''', supported by a detailed BOM and breakdown.
* '''1.1.2''' Materials and Labor must include a '''20% buffer''' and '''Warranty''' allowance.

=== 1.2 Profit Sharing ===
Profit is shared '''60% (Comfac)''' and '''40% (AA)''' after costs.

* '''1.2.1''' Comfac covers labor (as RJ and Andrei's salaries), so AA's remittance is '''40% profit + material costs'''.
* '''1.2.2 Example:'''

{| class="wikitable"
|-
! Item
! Amount
|-
| Project Value
| ₱360,000
|-
| Cost (₱80,000 materials + ₱50,000 labor)
| ₱110,000 (note: labor ₱50k listed separately)
|-
| Net Profit
| ₱250,000
|-
| Comfac Share (60%)
| ₱150,000
|-
| AA Share (40%)
| ₱100,000
|-
| Comfac remits to AA
| ₱100,000 (profit) + ₱80,000 (materials) = ₱180,000
|}

=== 1.3 Labor Baseline ===
Standard labor baseline: '''₱1,500 per man-day.'''

=== 1.4 Procurement ===
Material procurement and cost control managed by AA, tracked through Comfac PR-PO system in ERPNext.

----

== 2. Comfac Partner-Level-1 Pricing (P1 Pricing) ==

This applies to '''Comfac selling technology or systems''' (e.g., BMS) to '''ESCO, Cornersteel, or other strategic partners'''.

* '''2.1''' P1 pricing is set at '''15% markup''' for sister companies, assuming internal '''At-Cost / 0.6 or ×1.67''' pricing.
* '''2.2''' Comfac's share under P1 pricing equals '''60% of the total proposal/sales-invoice value'''.
** If P1 lowers the client price, Comfac still gets the '''quoted 60% share'''.
** If P1 increases the price, Comfac gets '''59.88% of the final collected price''', or whichever results in the '''higher amount due to Comfac'''.
* '''2.3''' Maximum discount P1 can offer clients: '''20%'''.
** This changes the multiplier from '''1.67 → 1.336''', giving P1 an '''18.9% margin''' after paying Comfac.
** Comfac retains '''15% gross margin''', split as '''9% Comfac / 6% Subcon Partner + Materials'''.

----

== 3. Reseller Agreement ==

For partners under a formal '''Comfac Reseller Agreement''', Comfac approves and co-signs the final pricing to ensure transparency.

* '''3.1''' Comfac's standard pricing: '''1.67 × Total Cost'''.
** Example: ₱1M cost → ₱1.67M selling price.
** ₱266,666 + materials remitted to Partner Contractor.
* '''3.2''' Resellers under agreement receive '''25% discount''' off Comfac's selling price.
** Comfac earns '''1.2525× cost''', keeping '''15.15% net margin'''.
* '''3.3''' Resellers can set client pricing and apply discounts, but Comfac always takes '''75% of the final quoted or invoiced price''', or '''whichever amount is higher between the reseller's client price or Comfac's quoted price.'''
* '''3.4''' Any deviation or unapproved pricing nullifies the agreement; Comfac will not produce or deliver products or services under those terms.

----

== 4. Note on ESCO ==

ESCO is designated as the '''planned maintenance and warranty provider''' for clients.

* Future discussions will define how ESCO prices preventive maintenance and full support over a 1-year warranty period.
* Responsibility and pricing for warranty coverage must be coordinated with ESCO's team and integrated into Comfac's pricing models.

🧠 Process: Selecting and Installing the Right Ollama Model for Your Hardware

2026-02-25T06:59:45Z

BabiSender: Created page with "= Process: Selecting and Installing the Right Ollama Model for Your Hardware = '''Reference Video:''' [https://www.youtube.com/watch?v=FQTorLqMyMU&list=PL5dOVtYynU23YPMqfIeekEJ7HTxYq2BG0 Which Ollama Model Is Best For YOU?] ---- == Step 1: Understand Your System Limitations == Before choosing a model, identify your system's available resources: * '''CPU:''' Intel i5 / AMD Ryzen 5 or better. * '''RAM:''' Minimum 8GB (16GB recommended). * '''GPU VRAM:''' Minimum 4GB (..."

= Process: Selecting and Installing the Right Ollama Model for Your Hardware =

'''Reference Video:''' [https://www.youtube.com/watch?v=FQTorLqMyMU&list=PL5dOVtYynU23YPMqfIeekEJ7HTxYq2BG0 Which Ollama Model Is Best For YOU?]

----

== Step 1: Understand Your System Limitations ==

Before choosing a model, identify your system's available resources:

* '''CPU:''' Intel i5 / AMD Ryzen 5 or better.
* '''RAM:''' Minimum 8GB (16GB recommended).
* '''GPU VRAM:''' Minimum 4GB (6GB+ preferred for smoother operation).

If your GPU is older (e.g., GTX 1060), focus on '''quantized models (Q4 or Q5)''' that are optimized for lower VRAM usage.

----

== Step 2: Install Ollama ==

# Go to [https://ollama.com/ https://ollama.com/]
# Download the version for your OS (Windows, macOS, or Linux).
# Follow the installation instructions for your platform:
#* '''Linux:'''
<pre>curl -fsSL https://ollama.com/install.sh | sh</pre>
#* '''Windows/macOS:''' Run the installer package.
# Verify installation:
<pre>ollama --version</pre>

----

== Step 3: Learn Model Naming and Suffixes ==

Model names contain critical information about their size, optimization, and performance level. Example:

<pre>mistral-7b-instruct-v0.2-q4_0</pre>

{| class="wikitable"
|-
! Part
! Meaning
|-
| <code>mistral</code>
| Model family (developer/architecture)
|-
| <code>7b</code>
| Number of parameters (7 billion) — larger models = smarter, but heavier
|-
| <code>instruct</code>
| Fine-tuned to follow instructions (good for general chat and Q&A)
|-
| <code>v0.2</code>
| Version — higher means newer and often more optimized
|-
| <code>q4_0</code>
| Quantization level — smaller numbers mean lighter models
|}

=== Quantization Levels ===

{| class="wikitable"
|-
! Code
! Meaning
! Use Case
|-
| q2
| Very light, lowest VRAM use, least accurate
| For 4GB GPUs
|-
| q3
| Light, faster but slightly less accurate
| For 4–6GB GPUs
|-
| q4
| Balanced, good trade-off between speed and quality
| For 6–8GB GPUs
|-
| q5
| Higher accuracy, slower
| For 8GB+ GPUs
|-
| fp16
| Full precision, highest VRAM use
| For 12GB+ GPUs
|}

----

== Step 4: Explore Available Models ==

You can browse models from the Ollama library:
* '''Official List:''' [https://ollama.com/library https://ollama.com/library]
* Models can be sorted by size, purpose, or creator.

Look for quantized models (with suffixes like <code>q4_0</code>, <code>q5_1</code>, etc.) if your GPU has limited VRAM.

----

== Step 5: Install and Test Models ==

Use these commands to download and run models:

<pre>
# Install Phi-3 model
ollama run phi3

# Install Mistral 7B Instruct
ollama run mistral-7b-instruct
</pre>

Once installed, test the model:

<pre>ollama run phi3</pre>

Then type a prompt like:

<pre>What is Newton's Third Law?</pre>

----

== Step 6: Install Ollama Web UI (Optional but Recommended) ==

For a ChatGPT-like interface:

# Visit the Ollama Web UI project (search GitHub for "Ollama WebUI").
# Follow setup instructions, typically:
<pre>
git clone https://github.com/ollama-webui/ollama-webui.git
cd ollama-webui
docker compose up -d
</pre>
# Access via browser (usually <code>http://localhost:11434</code>).

----

== Step 7: Switch Between Models ==

<pre>
ollama run mistral-7b-instruct
ollama run codellama
</pre>

Each model serves a different purpose:
* '''phi3''' → General Q&A, lightweight.
* '''mistral-7b-instruct''' → Balanced performance, good for reasoning.
* '''codellama''' → Programming and code completion.

----

== Step 8: Pro Tips ==

* Always use the '''latest version''' of models.
* Try different quantization levels to find your ideal balance.
* Keep your Ollama installation updated.
* Use '''quantized models''' for offline, efficient, and private AI processing.

----

== Key Commands Summary ==

{| class="wikitable"
|-
! Task
! Command
|-
| Install Phi-3
| <code>ollama run phi3</code>
|-
| Install Mistral
| <code>ollama run mistral-7b-instruct</code>
|-
| Check version
| <code>ollama --version</code>
|-
| List models
| <code>ollama list</code>
|-
| Remove model
| <code>ollama rm <modelname></code>
|}

----

== Useful Links ==

* Ollama Download: [https://ollama.com/ https://ollama.com/]
* Model Library: [https://ollama.com/library https://ollama.com/library]
* Ollama Web UI: Search GitHub for "Ollama Web UI"

Backblaze Drive Stats for Server and Storage Qualification

2026-02-25T06:59:26Z

BabiSender: Created page with "= Backblaze Drive Stats for Server and Storage Qualification = '''Reference:''' [https://www.backblaze.com/blog/backblaze-drive-stats-for-q3-2024/ Backblaze Drive Stats Q3 2024] ---- == 1. Purpose of Using Backblaze Data == Backblaze operates tens of thousands of drives in data centers and publishes quarterly reliability data. These datasets help organizations evaluate HDD reliability in real-world, high-load environments. The goal is to use these statistics to make..."

= Backblaze Drive Stats for Server and Storage Qualification =

'''Reference:''' [https://www.backblaze.com/blog/backblaze-drive-stats-for-q3-2024/ Backblaze Drive Stats Q3 2024]

----

== 1. Purpose of Using Backblaze Data ==

Backblaze operates tens of thousands of drives in data centers and publishes quarterly reliability data. These datasets help organizations evaluate HDD reliability in real-world, high-load environments. The goal is to use these statistics to make evidence-based choices for servers, NAS, and archival storage.

----

== 2. How to Use the Data for Informed Decisions ==

=== Step 1: Download Historical Data ===
* Visit the [https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data Backblaze Drive Stats Archive].
* Download the '''CSV datasets''' for each quarter and the accompanying '''PDF summaries'''.
* Store them in your internal Wiki or documentation system for reference and trend analysis.

=== Step 2: Analyze Key Metrics ===
Use spreadsheet tools or Python scripts to process the following fields:
* '''Model and Manufacturer''' (e.g., Seagate ST16000NM001G)
* '''Drive Count''' – number of units tested
* '''Drive Days''' – cumulative operational time
* '''Annualized Failure Rate (AFR)''' – observed failure probability per year
* '''Average Age''' – indicates maturity and reliability over time

=== Step 3: Evaluate by Category ===

{| class="wikitable"
|-
! Drive Use Case
! Ideal AFR
! Notes
|-
| '''Mission-Critical Storage (ZFS, Enterprise NAS)'''
| < 1%
| Prioritize proven models with >1M drive days
|-
| '''General Purpose / Backup Storage'''
| < 2%
| Balance cost and reliability
|-
| '''Archive / Cold Storage'''
| < 3%
| Accept higher AFR, focus on capacity per dollar
|}

=== Step 4: Summarize Trends by Brand ===

Aggregate the AFR data across quarters to identify consistent performers.

{| class="wikitable"
|-
! Brand
! Observed Trend (Q3 2024)
! Remarks
|-
| '''HGST / Western Digital Ultrastar'''
| Low AFR (~0.5% average)
| Consistently strong reliability in enterprise tiers
|-
| '''Seagate Exos / IronWolf'''
| Moderate AFR (~1.2%)
| High capacity models improving, but some lots show spikes
|-
| '''Toshiba MG Series'''
| Low to mid AFR (~0.7%)
| Competitive reliability; smaller dataset but strong trend
|-
| '''WDC / Consumer Models'''
| Higher AFR (>2%)
| Not ideal for 24/7 workloads
|}

=== Step 5: Apply to Procurement ===
When qualifying HDDs for servers:
* Select models with '''proven historical reliability''' (low AFR, large sample size).
* Verify '''batch consistency''' and '''firmware revisions''' before large orders.
* Combine Backblaze AFR data with '''vendor specifications''' for workload rating, vibration tolerance, and power draw.

=== Step 6: Update Regularly ===
Include quarterly updates in your Wiki, adding:
* Download link to the latest PDF (e.g., Q3 2024)
* Table of AFR trends per brand and capacity range
* Notes on any anomaly or large-scale failure trend

----

== 3. Example Wiki Section Layout ==

'''Page Title:''' HDD Reliability Qualification

'''Sections:'''
# [https://www.backblaze.com/blog/backblaze-drive-stats-for-q3-2024/ Q3 2024 Backblaze Report (PDF)]
# Historical Data: CSV and PDF Links
# Summary of Brand Reliability Trends
# Recommended Models (AFR < 1%)
# Procurement and Burn-In SOP

----

== 4. Actionable Takeaways ==

* Use '''Backblaze AFR''' as an empirical complement to manufacturer MTBF figures.
* Favor drives with '''>1M drive days''' for statistically relevant reliability data.
* Keep a '''rolling 2-year summary''' of AFR trends for vendor comparison.
* Perform '''local burn-in tests''' before production deployment.
* Document and review changes quarterly to align procurement with real-world performance.

Comfac GPU Scaling and AI Research Goals

2026-02-25T06:59:07Z

BabiSender: Created page with "= Comfac GPU Scaling and AI Research Goals = == Objective == To develop and scale a high-performance AMD-based AI compute cluster, capable of running large-scale models (e.g., Qwen 2.5 235B) and supporting educational and R&D initiatives through open collaboration with partner schools. ---- == Goals and Steps == === 1. Platform and Motherboard Selection === * Identify and procure a motherboard or server platform that supports extensive GPU scaling and PCIe bifurcati..."

= Comfac GPU Scaling and AI Research Goals =

== Objective ==

To develop and scale a high-performance AMD-based AI compute cluster, capable of running large-scale models (e.g., Qwen 2.5 235B) and supporting educational and R&D initiatives through open collaboration with partner schools.

----

== Goals and Steps ==

=== 1. Platform and Motherboard Selection ===
* Identify and procure a motherboard or server platform that supports extensive GPU scaling and PCIe bifurcation (similar to the setup demonstrated by PewDiePie).
* Ensure compatibility with ROCm and vLLM for distributed inference and multi-GPU coordination.

=== 2. Initial Scaling (Pilot Models) ===
* Begin with '''well-known, stable models''' to validate infrastructure performance and reliability.
* '''Pilot hardware:''' AMD '''Radeon PRO R9700 AI''' or equivalent AI-focused GPU.
* Validate thermal performance, power delivery, and driver stability for continuous inference workloads.

=== 3. Progressive Hardware Replication ===
* Once stable results are achieved with R9700 PRO, replicate the same environment using '''RX 7900 XTX''' and other AMD GPUs to benchmark performance scaling.
* Document compatibility issues, driver updates, and quantization performance metrics.

=== 4. Cluster and Swarm Development ===
* Establish a '''Cluster System''' for large-model distributed inference and training.
* Build a '''Swarm System''' capable of parallelizing smaller AI instances (e.g., 7700 and lower-end GPU nodes) for local and academic deployment.
* Optimize inter-node communication, synchronization, and monitoring tools for mixed hardware setups.

=== 5. Funding and Laboratory Deployment ===
* Fund the creation of a '''dedicated AI Lab''' focused on testing, documentation, and educational use.
* Provide access to partner schools for research, benchmarking, and AI model fine-tuning.

=== 6. Open Compute and Tokenization Participation ===
* Study and participate in open-source projects that allow community-based compute contributions (similar to Folding@home).
* Learn and experiment with decentralized compute-sharing models that enable contributors to sell '''tokens or compute time''' securely and transparently.

----

== Reference ==

* Inspirational video: [https://youtube.com/qw4fDU18RcU?si=TJ8hYQPIjuQuiORk Watch on YouTube]

----

== End Goal ==

To make Comfac and its academic partners a recognized hub for open, scalable, and sustainable AI research using AMD technologies.

Comfac CRM – Customer Qualification & Conversion Process

2026-02-25T06:58:48Z

BabiSender: Created page with "= Comfac CRM – Customer Qualification & Conversion Process = == Overview == This process defines how Comfac classifies, qualifies, and converts prospects through the ERPNext CRM and Sales Module — from unqualified leads to fully realized sales transactions. Each stage (Customer Qualification → Lead → Opportunity → Quotation → Sales Order → Sales Invoice) has measurable data points and performance weights. ---- == Customer Qualification == '''Purpose:''..."

= Comfac CRM – Customer Qualification & Conversion Process =

== Overview ==

This process defines how Comfac classifies, qualifies, and converts prospects through the ERPNext CRM and Sales Module — from unqualified leads to fully realized sales transactions. Each stage (Customer Qualification → Lead → Opportunity → Quotation → Sales Order → Sales Invoice) has measurable data points and performance weights.

----

== Customer Qualification ==

'''Purpose:''' Identify which organizations are worth pursuing by documenting their business profile, offerings, and potential budget.

=== Procedure ===
# Search existing database for duplicates or prior engagements.
# If new, create '''Customer Record''' with <code>Customer Type</code>, <code>Industry</code>, <code>Territory</code>, and <code>Tier</code> (MSME classification).
# Under the '''More Information''' section, fill the '''Offering Table (Child Table)''':
#* '''Item Group''' – Product/Service type relevant to the customer (e.g., ERP, Networking, HVAC, IoT, etc.)
#* '''Frequency''' – How often they purchase (Monthly, Quarterly, Annually)
#* '''Budget''' – Estimated value per cycle or per year
#* '''Last Verified Date''' – When the data was last updated

=== Reporting ===
'''Report:''' ''Qualified Customer Opportunity Potential''

* Filters: Time Period, Territory, Industry
* Metrics:
** Total number of qualified customers
** Sum of all '''Budget''' values per <code>Item Group</code>
** Opportunity Potential = Σ(Budget × Frequency) of qualified customers

=== Rules ===
* Data older than 6 months triggers "Needs Verification."
* Customers without an active Offering Table are ''unqualified''.
* Customers can have multiple item groups; each treated as a separate potential line.

----

== Lead Management ==

'''Purpose:''' Capture and assess new prospects that are not yet customers.

=== Procedure ===
# Create '''Lead''' with contact info, industry, territory, and source.
# Assign to '''Sales Rep''' or '''Lead Generation Officer'''.
# Conduct initial outreach and note response or requirements.
# If interest confirmed, convert to a '''Customer''' (Qualified) and log in the Offering Table.

=== Report: Leads Conversion Summary ===
* New Leads this period
* Converted to Qualified Customers
* Leads Disqualified or Stale
* Average conversion time (Lead → Customer)

=== SLA Rules ===
* Status must change within 3 business days of creation.
* Auto-alert if <code>status</code> not updated in 5 business days.

=== Scoring ===
* Lead captured & contacted = '''1 point'''
* Lead converted to Customer = '''+2 points'''

----

== Opportunities ==

'''Purpose:''' Track concrete sales prospects derived from qualified customers or leads.

=== Procedure ===
# Create '''Opportunity''' linked to Customer or converted Lead.
# Set Stage, Probability, and Expected Value.
# Update with activities (calls, meetings, quotations sent).
# Convert to Quotation when requirements are confirmed.

=== SLA ===
* Stage movement required within 7 days.
* If inactive >10 days, flag as stale.

=== Scoring ===
* New Opportunity created = '''+3 points'''
* Opportunity converted to Quotation = '''+5 points'''

----

== Quotations ==

'''Purpose:''' Formalize offers to customers; source either from Opportunity or Webstore.

=== Procedure ===
# Generate '''Quotation''' from Opportunity or Webshop submission.
# Include proper Item Group and Territory Pricing.
# Route for approval via link-based workflow.
# Upon submission, link to Opportunity for reporting.

=== Report: Quotation Pipeline ===
* Quotations count by type: (Webstore vs. Opportunity-based)
* Total quoted value by region and item group

=== Scoring ===
* Quotation generated = '''+8 points'''
* Quotation converted to Sales Order = '''+10 points'''

----

== Sales Orders & Sales Invoices ==

'''Purpose:''' Confirmed deals and revenue recognition.

=== Sales Order (SO) ===
* Generated upon Quotation approval.
* Uses '''temporary SO#''' until accounting assigns final SO#.
* Must link to corresponding Opportunity and Customer.

'''Scoring:''' +15 points per approved SO.

=== Sales Invoice (SI) ===
* Issued upon delivery or project billing.
* Linked to SO for continuity.

'''Scoring:''' +20 points per posted SI.

----

== Performance Tracking Summary ==

{| class="wikitable"
|-
! Stage
! Activity
! Points
! SLA
! Report
|-
| Customer Qualification
| Offering Table completed
| 0 (Base)
| 6 months refresh
| Qualified Customer Report
|-
| Lead
| Captured/Converted
| 1–3
| 3–5 days
| Leads Conversion Summary
|-
| Opportunity
| Created/Converted
| 3–5
| 7–10 days
| Opportunities by Stage
|-
| Quotation
| Generated/Converted
| 8–10
| Within 5 days of Opportunity
| Quotation Pipeline
|-
| Sales Order
| Approved
| 15
| Within 3 days of Quotation
| SO Conversion Report
|-
| Sales Invoice
| Posted
| 20
| Within 7 days of SO
| Invoice Posting Report
|}

----

== Objective ==

This process ensures that every step — from first contact to final invoice — is traceable, measurable, and rewarded proportionally to its impact on revenue. It drives consistent qualification standards, timely updates, and accurate reporting across the Sales lifecycle.

Biz Analysis Methodology 251109

2026-02-25T06:58:02Z

BabiSender: Created page with "= Business Analysis Methodology = == Objectives and Timeline == === Objective === To conduct a structured discovery, analysis, and high-level design (HLD) process that integrates Comfac-IT's core '''Business Analysis Techniques'''. The goal is to produce accurate, ERPNext-aligned process documentation that clarifies workflows, roles, and improvement opportunities across all operational domains. This methodology is grounded in '''Lean process analysis''' and '''ISO 900..."

= Business Analysis Methodology =

== Objectives and Timeline ==

=== Objective ===
To conduct a structured discovery, analysis, and high-level design (HLD) process that integrates Comfac-IT's core '''Business Analysis Techniques'''. The goal is to produce accurate, ERPNext-aligned process documentation that clarifies workflows, roles, and improvement opportunities across all operational domains.

This methodology is grounded in '''Lean process analysis''' and '''ISO 9001 principles''', emphasizing quantifiable efficiency through '''Touch Time''' (value-added work) and '''Data Handling Time''' (administrative or waiting time). By mapping how work is performed and where time is lost, the process guides digitization and continuous improvement.

----

== Methodology Overview ==

The analysis follows a structured three-phase framework designed for iterative learning and validation.

----

== Phase 1: Pre-Visit Preparation ==

'''Objective:''' Lay the groundwork for efficient stakeholder engagement and structured data collection.

=== 1. Stakeholder Identification ===
* Request existing org charts and process flowcharts from the client.
* Identify key process owners and approvers across functional areas.
* Confirm the list of subject matter experts (SMEs) available for interview.

=== 2. Interview Scheduling ===
* Allocate 45–60 minute sessions per SME.
* Ensure interviews cover at least 90–95% of operational roles.
* Sequence sessions from upstream to downstream processes.

=== 3. Tools & Templates ===
* '''Org Chart Template:''' to validate structure and reporting lines.
* '''Process Flowchart Template:''' to record process handoffs and identify transformation versus administrative activities.
* '''Touch Time vs. Data Handling Table:''' to quantify work efficiency and highlight rework frequency.

'''Deliverables:''' Validated org chart, initial flowcharts, and baseline Touch Time vs. Data Handling Log.

----

== Phase 2: On-Site Visit ==

'''Objective:''' Map roles, processes, and pain points using Lean and ERPNext process-mapping techniques.

=== A. Stakeholder Interviews (90–95% of Time) ===

'''Purpose:''' Capture how each department operates, where data flows, and how delays occur.

==== Interview Structure ====

; Role & Responsibilities
: "What tasks do you perform daily? What approvals do you handle?"

; Touch Time Analysis
: "How much time do you spend transforming data (encoding, approving, creating scopes of work)?"
: "What value does this step add to the customer or internal process?"

; Data Handling Time Analysis
: "How much time is spent retrieving forms, chasing approvals, or validating documentation?"
: "Where do delays typically occur?"

; Challenges
: "What frustrates you about the current system?"
: "What manual processes could be automated?"

==== Validation & Discrepancies ====
* Compare provided org charts and process documents with observed practices.
* Identify deviations (e.g., "Three signatures in practice vs. two on file").
* Highlight bottlenecks and approval redundancies.

==== Deliverables ====
* Updated org and process flowcharts.
* '''Touch vs. Data Handling Log''' per role, including observed delays and rework triggers.

=== B. Environmental Assessment (5–10% of Time) ===

'''Objective:''' Identify physical and digital workflow barriers.

==== Key Areas to Observe ====
* '''Physical Forms & Digitization:''' Catalog and flag all paper-based forms.
* '''Workspace Layout:''' Note how spatial separation affects collaboration or approvals.
* '''Technology Setup:''' Review device accessibility, network performance, and ERP login friction.

==== Strategies for Digitization ====
* '''Internal Forms:''' Digitize within ERPNext using built-in approval flows.
* '''External Forms:''' Enable export to PDF for wet signatures and define scanning/archiving SOPs.

'''Deliverables:''' Environmental audit notes, list of digitization-ready forms, and identified workflow constraints.

----

== Phase 3: Post-Visit Synthesis ==

'''Objective:''' Produce optimized, ERPNext-aligned workflows and digitization roadmaps.

=== 1. Analysis & Recommendations ===
* '''Process Bottlenecks:''' Identify where Data Handling Time accumulates (e.g., waiting for cross-department approval).
* '''Touch Time Optimization:''' Remove redundant checks, automate manual entries, and streamline approvals.
* '''Organizational Alignment:''' Re-map roles to reduce handoffs and clarify accountability.

=== 2. Mapping and Charting: Visualizing Flow and Risks ===
* Process mapping seeks to answer two core questions: '''"What happens next?"''' and '''"What happens when something goes wrong?"'''
* Each process map includes '''decision points, error paths, and rework loops''', showing how exceptions propagate.
* Risks identified are annotated with '''problem triggers''' and '''required coordination protocols'''—clarifying how updates or changes in SOPs are communicated and executed.
* Rework events are traced to quantify '''resource impact''' and guide corrective measures.

=== 3. Deliverables ===
* '''Lean Process Maps:''' Show current vs. proposed workflows with quantified time savings.
* '''Digitization Roadmap:''' Rank processes and forms for ERPNext integration.
* '''Business Case:''' Estimate savings from reduced Data Handling Time and rework avoidance.

----

== Tools & Templates ==

{| class="wikitable"
|-
! #
! Tool
! Description
|-
| 1
| Touch Time vs. Data Handling Log
| Role / Task / Touch Time (mins) / Data Handling Time (mins) / Bottlenecks
|-
| 2
| Org Chart Template
| Includes roles, approvals, and cross-functional dependencies
|-
| 3
| Digitization Checklist
| Lists internal/external forms, signature needs, and archiving procedures
|-
| 4
| Process Mapping A3 Template
| Documents flow, decision points, and escalation paths
|}

----

== Reference Links and Resources ==

* [https://next.comfaccorp.com/s/XxmLWbjSnmFQgx6 Sample ERPNext Company Process Template]
* [https://www.iso.org/standard/62085.html ISO 9001:2015 Standard Overview]
** [https://www.iso.org/obp/ui/en/#iso:std:iso:9001:ed-5:v1:en Read the outline/sample content here]
** ''Cost:'' Approximately 8,000 PHP (CHF 178 for MSMEs)
* [https://www.iso.org/files/live/sites/isoorg/files/standards/docs/en/iso_9001_2015_guidance_documented_information.pdf ISO 9001 Guidance on Documented Information]

----

== Timeline Considerations ==

Project duration depends on SME availability and process maturity.

* '''Non-ISO 9001 organizations''' typically require longer interviews and iterative mapping due to undocumented workflows.
* '''ISO 9001-compliant organizations''' can progress faster, but maturity varies by department and the currency of documentation and training.

{| class="wikitable"
|-
! Phase
! Description
! Duration
! Dependencies
|-
| '''1. Discovery'''
| Stakeholder interviews, workflow collection
| 2–3 weeks
| SME access, process documentation maturity
|-
| '''2. Analysis'''
| Validation, bottleneck identification, Lean alignment
| 1–2 weeks
| Availability of validated data
|-
| '''3. HLD'''
| ERPNext process mapping, A3 document creation, procedure linking
| 1 week
| Approved workflows from prior phase
|}

'''Total Duration:''' 4–6 weeks for a medium-sized enterprise, depending on access to SMEs and process documentation depth.

----

== Key Success Metrics ==

* Reduction in Data Handling Time per role.
* Stakeholder validation of updated org and process charts.
* % of paper forms migrated to ERPNext.
* Reduction in rework and approval cycle time.

----

== Risks and Mitigation ==

{| class="wikitable"
|-
! Risk
! Description
! Mitigation
|-
| Limited SME availability
| Operational workload limits interview access
| Schedule early, break sessions into focused blocks
|-
| Undocumented or implicit processes
| Missing or informal workflows
| Use shadowing and cross-validation interviews
|-
| Outdated documentation
| Misalignment between written and actual practice
| Validate through observation and workshops
|-
| Rework from unclear instructions
| Ambiguous SOP updates
| Establish clear escalation and change communication protocol
|}

----

== Appendix: ISO 9001 and the PDCA Cycle ==

ISO 9001 serves as the foundation for all quality and process management systems. At its core, ISO 9001 can be distilled into the '''PDCA (Plan–Do–Check–Act)''' framework — a continuous improvement model that structures how organizations think, execute, and refine their work.

=== Plan ===
Planning begins with identifying '''goals''' and '''intended outcomes''', and translating these into specific, measurable actions. It requires:
* Extrapolating from goals to actionable steps.
* Verifying that each planned action logically contributes to the intended outcome.
* Ensuring all goals address a '''problem statement''' or test an '''opportunity hypothesis'''.
* Advanced practitioners also factor in '''risks, opportunities, and constraints''' (time, manpower, skills, cost, equipment, etc.) when designing plans.

=== Do ===
Execution involves '''mobilizing and communicating resources''' — including manpower, finances, tools, permissions, and authority. This phase focuses on clear delegation, coordination, and accountability to carry out the planned activities effectively.

=== Check ===
Checking requires examining the '''results of both the plan and its execution''' to identify:
* '''Gaps''' between expected and actual outcomes.
* A '''taxonomy of problems and risks''', categorized by impact and recurrence.
* The need to update documents, processes, and organizational knowledge to reflect current practice.

=== Act ===
Acting is about '''refinement and iteration''' — applying lessons learned to improve efficiency, reduce risk, and optimize future outcomes. The cycle repeats, incorporating insights from the previous Check phase to better address goals, risks, and opportunities.

By embedding PDCA into ERPNext-driven process mapping, Comfac-IT ensures that every documented workflow not only aligns with ISO 9001 principles but also creates a living system of continuous improvement and learning.

Excel Description Filler Tool 📝

2026-02-25T06:57:36Z

BabiSender: Created page with "== Excel Description Filler Tool == Automatically populate product descriptions in your Excel spreadsheet using Python. Perfect for e-commerce product imports, inventory management, and bulk data processing. ---- == What This Tool Does == # Reads your Excel file with product names # Matches products to pre-written descriptions # Fills in blank Description cells automatically # Preserves existing descriptions (will not overwrite) # Saves a new Excel file with complete..."

== Excel Description Filler Tool ==

Automatically populate product descriptions in your Excel spreadsheet using Python. Perfect for e-commerce product imports, inventory management, and bulk data processing.

----

== What This Tool Does ==

# Reads your Excel file with product names
# Matches products to pre-written descriptions
# Fills in blank Description cells automatically
# Preserves existing descriptions (will not overwrite)
# Saves a new Excel file with completed data

----

== Files Included ==

{| class="wikitable"
|-
! File !! Description
|-
| <code>description.py</code> || The main Python script (heavily commented)
|-
| <code>QUICKSTART.md</code> || Get started in 5 minutes
|-
| <code>INSTRUCTIONS.md</code> || Complete step-by-step guide
|-
| <code>TEMPLATE_GUIDE.md</code> || Examples and formatting templates
|-
| <code>README.md</code> || Project overview
|}

----

== Requirements ==

* Python 3.7+ (Python 3.9+ recommended)
* <code>pandas</code> library (data manipulation)
* <code>openpyxl</code> library (Excel file support)

Your Excel file must have these columns:
* '''Item Name''' – product names to match
* '''Description''' – column to fill (can be empty)

----

== Quick Start (5 Minutes) ==

=== Step 1 – Install Python ===

'''Windows:''' Download from [https://www.python.org/downloads/ python.org] → check "Add Python to PATH" during installation.

'''Linux (Ubuntu/Debian):'''
<syntaxhighlight lang="bash">
sudo apt install python3 python3-pip
</syntaxhighlight>

=== Step 2 – Install Required Libraries ===

'''Windows:'''
<syntaxhighlight lang="bash">
pip install pandas openpyxl
</syntaxhighlight>

'''Linux:'''
<syntaxhighlight lang="bash">
pip3 install pandas openpyxl
</syntaxhighlight>

=== Step 3 – Get Product Descriptions Using AI ===

Ask Claude or ChatGPT using a prompt like:

<syntaxhighlight lang="text">
I need concise product descriptions (50-80 words each)
for these products suitable for a professional webstore:

- Product Name 1
- Product Name 2
- Product Name 3

Include key specifications, features, and target use cases.
Format: Professional, B2B tone.
</syntaxhighlight>

=== Step 4 – Organize Your Files ===

Place both files in the '''same folder''':

<syntaxhighlight lang="text">
📂 Downloads/
├── description.py
└── your-data.xlsx
</syntaxhighlight>

=== Step 5 – Configure the Script ===

Open <code>description.py</code> and update these sections:

'''Input filename (line 19):'''
<syntaxhighlight lang="python">
path = "your-data.xlsx"
</syntaxhighlight>

'''Product descriptions (lines 24–50):'''
<syntaxhighlight lang="python">
descriptions = {
"Product A": "Description for Product A...",
"Product B": "Description for Product B...",
}
</syntaxhighlight>

=== Step 6 – Run the Script ===

'''Windows:'''
<syntaxhighlight lang="bash">
cd C:\Users\YourName\Downloads
python description.py
</syntaxhighlight>

'''Linux:'''
<syntaxhighlight lang="bash">
cd ~/Downloads
python3 description.py
</syntaxhighlight>

=== Step 7 – Check Output ===

Look for the file: <code>webstore_import_with_descriptions.xlsx</code>

----

== Description Dictionary Format ==

=== Basic Template ===

<syntaxhighlight lang="python">
descriptions = {
"Product Name 1": "Short description here.",
"Product Name 2": "Another short description.",
"Product Name 3": "Yet another description.",
}
</syntaxhighlight>

=== Multi-Line Template (Recommended) ===

<syntaxhighlight lang="python">
descriptions = {
"Product Name 1": (
"First part of the description. "
"Second part of the description. "
"Third part continues here."
),
"Product Name 2": (
"Another product with a longer description "
"that spans multiple lines for better readability."
),
}
</syntaxhighlight>

=== Common Mistakes ===

{| class="wikitable"
|-
! ❌ Wrong !! ✅ Correct
|-
| <code>"Dell OptiPlex"</code> (too generic, won't match) || <code>"Dell OptiPlex 7010"</code> (exact match)
|-
| <code>Dell OptiPlex 7010: "..."</code> (missing quotes on key) || <code>"Dell OptiPlex 7010": "..."</code>
|-
| Missing comma after entry || Each entry ends with a comma
|}

----

== The Full Script ==

<syntaxhighlight lang="python">
import pandas as pd

# ============================================================================
# CONFIGURATION SECTION - UPDATE THESE VALUES
# ============================================================================

# STEP 1: Change this to your Excel filename
path = "251106 netgate selling price.xlsx"

# STEP 2: Add your product descriptions here
descriptions = {
"Netgate 8300 TAA": (
"pfSense+ 1U security gateway with Intel Xeon D-1733NT (8-core/16-thread) and Intel AVX-512. "
"Ports: 4×10G SFP+, 4×1G SFP, 3×2.5G RJ-45; PCIe expansion up to 10/25/100G. "
"TAA-compliant hardware; built for medium/large sites, MSPs, and data centers."
),
# ADD MORE PRODUCTS HERE...
}

# STEP 3 (Optional): Change output filename
output_filename = "webstore_import_with_descriptions.xlsx"

# ============================================================================
# MAIN SCRIPT
# ============================================================================

print(f"Loading Excel file: {path}")
df = pd.read_excel(path, sheet_name=0)
print(f"✓ Loaded {df.shape[0]} rows and {df.shape[1]} columns")

def fill_desc(row):
name = str(row.get("Item Name", "")).strip()
existing = row.get("Description", "")
if pd.notna(existing) and str(existing).strip():
return existing
return descriptions.get(name, "")

print("\nProcessing descriptions...")
df["Description"] = df.apply(fill_desc, axis=1)

filled_count = df["Description"].notna().sum()
print(f"✓ Filled {filled_count} descriptions")

print(f"\nSaving to: {output_filename}")
df.to_excel(output_filename, index=False)
print("✓ File saved successfully!")
</syntaxhighlight>

----

== Troubleshooting ==

{| class="wikitable"
|-
! Issue !! Solution
|-
| <code>ModuleNotFoundError: pandas</code> || Run: <code>pip install pandas openpyxl</code>
|-
| <code>FileNotFoundError</code> || Check Excel file is in the same folder as the script
|-
| Descriptions not filling || Product names must match exactly (case and spacing)
|-
| <code>Permission denied</code> || Close the Excel file if it is currently open
|-
| Character encoding issues (e.g. Ã— instead of ×) || Save the <code>.py</code> file with UTF-8 encoding
|}

----

== Best Practices ==

# Always test with 2–3 products before bulk processing
# Keep a backup of your original Excel file
# Product names must match character-for-character
# Review the generated file before importing
# Use UTF-8 encoding to prevent character display issues

----

== Workflow Summary ==

<syntaxhighlight lang="text">
1. Get product names from Excel
↓
2. Generate descriptions using AI
↓
3. Format as Python dictionary
↓
4. Update description.py
↓
5. Run script
↓
6. Check output file
↓
7. Import to your system
</syntaxhighlight>

----

== Performance ==

{| class="wikitable"
|-
! Metric !! Value
|-
| Processing Speed || ~1,000 rows per second
|-
| File Size Limit || Tested up to 100,000 rows
|-
| Memory Usage || < 100 MB for typical files
|-
| Excel Compatibility || .xlsx, .xlsm formats
|}

ERPNext Webshop Setup and Publishing Process

2026-02-25T06:57:18Z

BabiSender: Created page with "= ERPNext Webshop Setup and Publishing Process = == Step 1: Create Item Groups == === Example Tree === All Item Groups ├── Products │ ├── Desktops │ ├── Industrial Controllers │ ├── Laptops │ ├── Network │ ├── Network Attached Storage (NAS) │ └── Servers ├── Services │ ├── Frappe ERPNext Solutions │ ├── Industrial Controller Solutions │ ├── Network Solutio..."

= ERPNext Webshop Setup and Publishing Process =

== Step 1: Create Item Groups ==

=== Example Tree ===

All Item Groups
├── Products
│ ├── Desktops
│ ├── Industrial Controllers
│ ├── Laptops
│ ├── Network
│ ├── Network Attached Storage (NAS)
│ └── Servers
├── Services
│ ├── Frappe ERPNext Solutions
│ ├── Industrial Controller Solutions
│ ├── Network Solutions
│ ├── NextCloud Solutions
│ └── Open Source Solutions
├── Raw Material
├── Sub Assemblies
└── Consumable

=== Guidelines ===
* Go to '''Stock → Item Group Tree'''.
* Create or edit groups according to your product/service taxonomy.
* Ensure correct hierarchy (e.g., "Products" and "Services" under "All Item Groups").
* For each '''Item Group''':
** Check ✅ '''Show in Website''' under ''Website Section''.
** Verify the '''route''' (URL path) is valid.
** Optionally write a short description of what the category means (can be added later).

=== Tax Configuration ===
* Groups like '''Services, Goods (Products), Rent''' → typically have Withholding Tax and VAT.
* '''Raw Material, Subassemblies, Consumables''' → generally not published on webshop, internal use only.

=== Special Notes ===
* ''Open Source Solutions'' includes SECADA, STEWARD, SYNX, and third-party open source projects (e.g., Open WebUI, Ollama, WordPress, Mailcow, etc.).

----

== Step 2: Configure Webshop Settings ==

'''Path:''' Website → Webshop Settings

# Enable ✅ ''Field Filters (Categories)''.
# Add Website Item Fields:
#* <code>brand</code>
#* <code>item_group</code>
#* <code>item_code</code>
# Enable ✅ ''Attribute Filters'' (optional, for Colour, Size, etc.).
# Save settings.

----

== Step 3: Bulk Upload and Edit Items ==

'''Path:''' Stock → Item → ⋯ (ellipses) → Import

# Download or view '''Sample Upload Template'''.
# Ensure the following default fields are included:

{| class="wikitable"
|-
! Fieldname
! Description
! Example
|-
| <code>item_code</code>
| Unique item identifier
| DELL-DC15255
|-
| <code>item_name</code>
| Display name
| Dell 15 DC15255 Laptop
|-
| <code>brand</code>
| Link to Brand DocType
| Dell
|-
| <code>item_group</code>
| Link to Item Group
| Laptops
|-
| <code>description</code>
| HTML/Text
| Intel i7, 16GB RAM, 512GB SSD
|-
| <code>standard_rate</code>
| Selling Price
| 50000
|-
| <code>show_in_website</code>
| 1 = Published
| 1
|-
| <code>image</code>
| Image URL
| /files/dell15.png
|-
| <code>stock_uom</code>
| Unit of Measure
| Nos
|-
| <code>website_item_group</code>
| Group shown on webshop
| Products
|}

3. Upload via Import Tool (Add New or Update Existing Items).
4. Save the spreadsheet at: [https://next.comfaccorp.com/f/152937 Nextcloud Product Information Folder]

All product and service images must be uploaded and stored in the respective '''Item''' entries. These images will later be fetched into slideshows automatically.

=== Bulk Automation Tip ===
For large item sets, automate editing using '''Python + Pandas + Openpyxl'''.

Install dependencies:
<pre>sudo apt install python3-pandas python3-openpyxl</pre>

* [https://erp.comfac-it.com/wiki/excel-description-filler-tool-%F0%9F%93%9D Excel Description Filler Tool]
* [https://next.comfaccorp.com/s/CYts2pyFFW8FmPc Bulk Encode Descriptions Script]
* [https://next.comfaccorp.com/s/mjJWZR5RfmsNm6z Bulk Upload File Template]

Ensure the column '''Published in Website''' is set to '''1'''.

----

== Step 4: Configure and Publish Webshop Items ==

'''Path:''' Website → Website Item

# Publish items using the "Publish to Website" action.
# Verify each entry under '''Website Item'''.
# Ensure every item has a '''Slideshow''' with matching name to its Item Code or Item Name.
# Right-click → Open linked '''Slideshow''' in new tab.

=== Slideshow Configuration ===
* Use ''Customized'' type.
* If '''Allow Bulk Edit''' is visible, it is already configured. If not visible, escalate to the system admin team to enable it.
* In the Slideshow table (columns: <code>No</code>, <code>Image</code>, <code>Heading</code>, <code>Description</code>), click the gear icon ⚙️ and add a '''URL''' field to make it visible.
* Note: when using ''Fetch Attached Images from Document'' (from Item → Item Code), ERPNext does not always save the images properly.
* After fetching, download the CSV file and copy the <code>Image</code> column contents into the <code>URL</code> column manually.
* Name each slide heading as <code><Item Code> 01</code>, <code><Item Code> 02</code>, etc.
* Upload modified CSV again (ERPNext sometimes doesn't retain inline edits).

This ensures all product images appear properly in the webshop.

----

== Summary Flow ==

{| class="wikitable"
|-
! Step
! Module
! Key Action
|-
| 1
| Stock
| Create and configure Item Groups (Show in Website)
|-
| 2
| Website
| Configure Webshop Filters (brand, website_item_group, item_code)
|-
| 3
| Stock
| Bulk upload items with all required fields
|-
| 4
| Website
| Publish items and set up slideshows
|-
| 5
| Verify
| Filters and products appear correctly in <code>/all-products</code>
|}

----

== Next Improvements ==

* Add category descriptions and icons for better UI.
* Automate bulk slideshow generation with a script.
* Use tags for easier multi-criteria filtering (e.g., ESG, Open Source, SaaS).

Comparison: TrueNAS Mini X+ vs Dell Precision 3680 Tower (2025)

2026-02-25T06:56:54Z

BabiSender: Created page with "= Comparison: TrueNAS Mini X+ vs Dell Precision 3680 Tower (2025) = {| class="wikitable" |- ! Specification ! TrueNAS Mini X+ ! Dell Precision 3680 Tower ! Notes |- | '''CPU''' | Intel Atom C3758 (8 cores, 2.2GHz, 25W TDP) | Intel Core i7-14700 (20 cores [8P+12E], up to 5.4GHz, 65–219W TDP) | Atom is a low-power CPU (25W vs 219W); Dell's higher wattage triggers need for higher-grade PSU, GPU, and cooling, which increases total system cost. |- | '''Architecture''' | Se..."

= Comparison: TrueNAS Mini X+ vs Dell Precision 3680 Tower (2025) =

{| class="wikitable"
|-
! Specification
! TrueNAS Mini X+
! Dell Precision 3680 Tower
! Notes
|-
| '''CPU'''
| Intel Atom C3758 (8 cores, 2.2GHz, 25W TDP)
| Intel Core i7-14700 (20 cores [8P+12E], up to 5.4GHz, 65–219W TDP)
| Atom is a low-power CPU (25W vs 219W); Dell's higher wattage triggers need for higher-grade PSU, GPU, and cooling, which increases total system cost.
|-
| '''Architecture'''
| Server-grade (Atom Denverton, low power, optimized for 24/7)
| Desktop/workstation-grade (Raptor Lake 14th Gen)
| Precision's CPU architecture is workstation-class, designed for mixed workloads, not constant uptime NAS use.
|-
| '''ECC Support'''
| Yes, supports ECC DDR4 up to 64GB
| Supports ECC and Non-ECC DDR5 (up to 128GB)
| [https://www.dell.com/support/manuals/en-ph/oth-3680-xe/precision_3680_tower_om/memory?guid=guid-e9d2ea83-38a4-431d-803c-96d63c1dbc34&lang=en-us Dell Precision 3680 Memory Manual] — ECC-capable CPU and motherboard are expensive and enterprise-grade.
|-
| '''RAM (Included / Max)'''
| 32GB ECC DDR4 (expandable to 64GB)
| 16GB DDR5 (expandable to 128GB)
| ECC memory ensures ZFS integrity and resilience; DDR5 non-ECC is faster but not fault-tolerant.
|-
| '''Storage (Base)'''
| Diskless chassis (5x 3.5" + 2x 2.5" bays)
| 256GB M.2 SSD + 2TB SATA HDD
| TrueNAS Mini X+ is designed for multi-drive RAID setups; Dell is optimized for workstation OS and local storage.
|-
| '''Expansion Bays'''
| 7 hot-swap bays total
| 2 internal 3.5" bays + 1 M.2 slot
| TrueNAS supports RAIDZ2 or mirrored arrays; Dell is limited for expansion.
|-
| '''Network Ports'''
| 2x 10GbE RJ45
| 1x 1GbE RJ45
| TrueNAS provides higher throughput and redundancy for storage traffic.
|-
| '''GPU'''
| Integrated (no GPU)
| NVIDIA T400 (4GB GDDR6, 3x mDP)
| GPU adds cost and power consumption but not essential for NAS workloads.
|-
| '''Power Supply'''
| Proprietary internal PSU, 250W–300W (quiet, efficient)
| Standard ATX PSU (up to 400–500W)
| Precision's power supply complexity stems from its higher CPU and GPU load.
|-
| '''Chassis Type'''
| Small form factor NAS (whisper-quiet)
| Mid-tower workstation (active cooling, louder)
| Precision 3680 has more airflow but higher acoustic footprint.
|-
| '''Operating System'''
| [https://www.truenas.com/blog/truenas-mini-x-and-mini-x-plus/ TrueNAS CORE/Scale] (FreeBSD/Linux-based NAS OS)
| Windows 11 Pro
| TrueNAS is an appliance OS built for storage; Windows is general-purpose.
|-
| '''Target Use Case'''
| Dedicated NAS / storage appliance
| General workstation, can run TrueNAS in a VM
| Precision is more flexible but not storage-optimized.
|-
| '''Power Efficiency'''
| 25W CPU, typically <60W total load
| 65–200W typical load depending on use
| TrueNAS Mini is 3–4x more power efficient, suitable for 24/7 uptime.
|-
| '''Base Price (USD)'''
| USD 2,000
| —
| [https://www.truenas.com/blog/truenas-mini-x-and-mini-x-plus/ TrueNAS Mini X+ Overview]
|-
| '''Converted Price (PHP)'''
| 2,000 × 60 = '''₱120,000'''
| ₱91,000–₱115,000
| —
|-
| '''Estimated Landed Cost'''
| '''₱156,000 landed in PH''' (₱120,000 × 1.3)
| ₱91,000–₱115,000 (local pricing)
| Landing cost includes import duties, VAT, and handling.
|-
| '''Warranty'''
| 3 years iXsystems warranty (return to base)
| 3 years ProSupport (on-site, local Dell PH service)
| TrueNAS warranty requires overseas RMA; Dell is locally supported.
|-
| '''Availability / Logistics'''
| Imported (may need stock of PSU, shipping delay for parts)
| Widely available in PH (Dell-authorized service)
| TrueNAS PSU and parts should be stocked locally to minimize downtime.
|}

----

== Observations ==

* '''Performance:''' Precision 3680's CPU and GPU make it far more powerful but also power-hungry and costly due to enterprise-class board and PSU requirements. The TrueNAS Mini X+ is slower but optimized for stability, uptime, and ZFS performance.
* '''ECC & Data Integrity:''' Both systems can support ECC memory, but TrueNAS uses it by default with ZFS, ensuring data consistency. ECC-capable Dell boards are expensive, confirming their enterprise orientation.
* '''Networking:''' TrueNAS offers dual 10GbE, vastly superior to Dell's single 1GbE port for data transfer.
* '''Noise & Efficiency:''' TrueNAS is ultra-quiet and efficient; Dell consumes more power and generates more heat under load.
* '''Expandability:''' TrueNAS wins with more drive bays and easier RAID management.
* '''Supportability:''' Dell wins for local warranty and logistics; TrueNAS requires self-maintenance and stocking spares.

----

== Conclusion ==

* For '''dedicated NAS / enterprise storage reliability''', the '''TrueNAS Mini X+''' is the better choice even at '''₱156,000 landed'''.
* For '''workstation workloads (rendering, dev, light NAS)''', the '''Dell Precision 3680''' is more flexible but costlier to operate long-term.

{{Note|If Comfac plans to adopt TrueNAS Mini units, '''keep spare PSUs and fans''' locally in stock to minimize lead time and downtime.}}

Mailcow SOGo: Creating Filters for Events, Approvals, and Organizational Emails

2026-02-25T06:56:04Z

BabiSender: Created page with "= Mailcow SOGo: Creating Filters for Events, Approvals, and Organizational Emails = '''Goal:''' Automatically organize event invitations, approval requests, and messages from students, interns, or capstone projects into dedicated folders for easier review and management. ---- == Step 1: Open SOGo Mail Preferences == # Log in to your '''Mailcow SOGo web interface'''. # In the top menu, click '''Preferences'''. # Select the '''Mail''' tab. ---- == Step 2: Go to the F..."

= Mailcow SOGo: Creating Filters for Events, Approvals, and Organizational Emails =

'''Goal:''' Automatically organize event invitations, approval requests, and messages from students, interns, or capstone projects into dedicated folders for easier review and management.

----

== Step 1: Open SOGo Mail Preferences ==

# Log in to your '''Mailcow SOGo web interface'''.
# In the top menu, click '''Preferences'''.
# Select the '''Mail''' tab.

----

== Step 2: Go to the Filters Section ==

Within Mail preferences, navigate through the tabs:
* General
* Labels
* IMAP Accounts
* '''Filters''' ← Click this one
* Vacation
* Forward

----

== Step 3: Create a Filter for Calendar Events ==

This captures Google Calendar and other event invitations.

{| class="wikitable"
|-
! Field
! Value
|-
| '''Filter name'''
| Events
|-
| '''For incoming messages'''
| Match '''any''' of the following rules
|-
| '''Condition'''
| Subject '''contains''' <code>Invitation:</code> (used by Google Calendar)
|-
| '''Condition (optional)'''
| Body '''contains''' <code>.ics</code>
|-
| '''Action'''
| File the message in Mailbox (folder) → '''Events'''
|}

This ensures any invite with the standard Google Calendar subject ("Invitation: [Event Name]") goes to your '''Events''' folder.

----

== Step 4: Create Filters for Organizational and Academic Emails ==

{| class="wikitable"
|-
! Filter Name
! Conditions
! Target Folder
|-
| '''Approvals'''
| Subject contains <code>approval</code>, <code>approved</code>, or <code>for review</code>
| Approvals
|-
| '''Students'''
| From contains <code>@edu.ph</code> or <code>student</code>
| Students
|-
| '''Interns'''
| Subject or Body contains <code>intern</code>, <code>OJT</code>, or <code>training</code>
| Interns
|-
| '''Capstones'''
| Subject contains <code>capstone</code>, <code>project</code>, or <code>final defense</code>
| Capstones
|}

Use '''Match any of the following rules''' for each filter so that related emails are automatically grouped.

----

== Step 5: Save the Filters ==

* Click '''Save & Close''' or '''Apply Changes''' after setting each filter.
* Test by sending sample messages (with keywords like "Invitation:" or "Capstone") to confirm correct routing.

----

== Step 6: Verify & Refine ==

* Review your folders after a few days to ensure emails are being categorized correctly.
* Add or edit conditions if some emails are missed (for example, new sender domains or different subject formats).

----

This configuration helps you centralize events, organizational approvals, and student or intern communication while keeping your inbox clean and organized.

Google Drive and Shared Drive Training

2026-02-25T06:55:30Z

BabiSender: Created page with "= 251028 DDC-OP-01 Google Drive and Shared Drive Training = ''Comfac Group of Companies'' ---- == Objectives == To train all departments of the Comfac Group of Companies in the proper and efficient use of Google Drive (GDrive) and Shared Drives as a centralized platform for document management, collaboration, and information accessibility. === Key Result Areas (KRAs) === * Ensure end users have '''convenient and automated backups''' of their work and files through Go..."

= 251028 DDC-OP-01 Google Drive and Shared Drive Training =
''Comfac Group of Companies''

----

== Objectives ==

To train all departments of the Comfac Group of Companies in the proper and efficient use of Google Drive (GDrive) and Shared Drives as a centralized platform for document management, collaboration, and information accessibility.

=== Key Result Areas (KRAs) ===
* Ensure end users have '''convenient and automated backups''' of their work and files through Google Drive and Shared Drive integration.
* Ensure all staff have '''continuous access''' to their files, folders, and backups from any authorized device.
* Promote '''collaborative document use''' as the ''Single Source of Truth (SSOT)'' — meaning documents edited and finalized collaboratively in GDrive become the official record, eliminating after-the-fact consolidation.
* Standardize naming conventions and folder structures across departments.
* Support ISO-compliant document control and traceability.

=== Expected Deliverables ===
* Trained users capable of managing Shared Drive folders and automated backup workflows.
* Departmental compliance with naming conventions and backup procedures.
* Improved accessibility and version control through collaboration-based workflows.

----

== Background ==

The Comfac Group transitioned to Google Workspace to improve coordination, reliability, and document access. Challenges in version control, lost files, and uncoordinated backups necessitated a standardized procedure for file organization, backup, and collaboration. This training ensures every employee can securely store, back up, and share files without reliance on manual or redundant saving methods.

----

== Scope ==

This document applies to all departments within the Comfac Group using Google Workspace. It defines the process for training, file backup automation, and collaborative document management using Google Drive and Shared Drives.

=== Activities and Methodologies ===
* Structured training sessions on GDrive and Shared Drive fundamentals.
* Hands-on exercises in file sharing, access control, and real-time collaboration.
* Implementation of automatic synchronization through Google Drive for Desktop.
* Demonstration of how collaborative documents function as live SSOT records.

* '''Estimated Duration:''' 1.5–2 hours per training session.
* '''Resources:''' Standard IT training setup, 1 trainer, and 1–2 facilitators.

=== System Requirements ===
* Browser: Google Chrome (latest version)
* Internet: Minimum 1 Mbps stable connection
* RAM: 4 GB or higher
* Google Workspace account under company domain
* Google Drive for Desktop (for automated backup)
* Access to departmental Shared Drives

----

== Definitions ==

; Single Source of Truth (SSOT)
: In the context of Google Drive collaboration, the live and collaboratively edited document is the official reference — replacing redundant versions or re-uploaded files.

; Shared Drive
: Centralized company-managed drive ensuring data persistence and continuity even if members leave.

; My Drive
: Individual user's workspace for temporary or personal files, subject to manual backup if not synchronized.

; Automated Backup
: Continuous file synchronization between local storage and GDrive via Google Drive for Desktop.

; Account Control
: The company's ability to revoke or transfer access to GDrive and Shared Drive data through IT for data continuity and security.

----

== References ==

* '''DDC-OP03''' – Control of Documents in GDrive
* '''17-04-03''' – Google Drive Training (Legacy 2017 Version)
* '''Shared Drives and Backups (Dec 2024)'''
* [https://support.google.com/a/users/answer/9308868 Google Workspace Sharing Guide]
* [https://support.google.com/drive/answer/7329379 Google Drive for Desktop Sync]

----

== Responsible ==

{| class="wikitable"
|-
! Role
! Responsibility
|-
| '''SSD Manager'''
| Oversees creation of Shared Drive folders, monitors backup compliance, and validates structure.
|-
| '''Department Managers'''
| Ensure staff participation in training, verify backup setup, and maintain document integrity.
|-
| '''IT Department'''
| Provides access, backup configuration, and troubleshooting; manages account control and data transfer.
|-
| '''Trainers/Facilitators'''
| Conduct and document training, verify successful setup of Drive sync and Shared Drive access.
|-
| '''All Employees'''
| Maintain their file organization, ensure Drive backup is active, and use Shared Drives for collaboration.
|}

----

== Procedure ==

=== 1. Preparation Phase ===
* Verify workstation readiness: internet, browser, and Drive access.
* Coordinate with IT to ensure Google Drive for Desktop is installed.
* Preload training materials and Shared Drive examples.

=== 2. Training Session ===

==== Module 1: GDrive and Shared Drive Fundamentals ====
* Explain My Drive vs Shared Drive ownership and security.
* Demonstrate automated file synchronization and backup setup.
* Configure Google Drive for Desktop for real-time cloud sync.
* Explain file version recovery and offline editing.

==== Module 2: Folder Hierarchy and Naming Convention ====
* Use standard naming: <code>ProjectName + SO#</code> and <code>ProjectName + JO# + Department</code>.
* Demonstrate access inheritance and subfolder management.
* Create shortcuts for cross-departmental references.

==== Module 3: Collaboration and File Ownership ====
* Demonstrate real-time collaboration on Docs, Sheets, and Slides.
* Discuss how collaborative versions eliminate redundant edits.
* Apply commenting (<code>Ctrl + Alt + M</code>) and linking (<code>Ctrl + K</code>).
* Set document protections and explain version history for audit trail.
* Explain '''Sharing Controls''', including using Groups or individual users for sharing and setting '''Expiring Permissions''' for temporary access.
* Highlight that Google provides '''reports identifying publicly shared documents''' within the organization.
* Demonstrate how to view document activity:
** In Docs: go to '''Tools > Activity Dashboard''' to see who viewed the document.
** In Drive: use '''Right-click > File Information > Activity''' to see recent file actions.

==== Module 4: Backup Management and Verification ====
* Walkthrough: verify Drive sync status on desktop and web.
* Demonstrate recovering files from Trash or version history.
* Ensure key folders (Desktop, Documents, Projects) are synced to GDrive.

=== 3. Post-Training Implementation ===
* Department heads confirm all users have functioning Drive backup and access.
* SSD audits folder structures and permissions quarterly.
* IT verifies backup logs and storage quota status monthly.

----

== Documentation ==

* Attendance and feedback from trainees.
* Record of Drive sync installations and account verifications.
* Backup compliance reports and periodic review results.
* Confirmation from managers of collaborative workflow adoption.

----

== Appendix ==

=== Drive Backup Setup Example ===
My Drive → Shared Drive → Local Sync

=== Standard Folder Hierarchy ===
Root → Department → Project

=== Google Drive Hotkeys Reference ===

{| class="wikitable"
|-
! Shortcut
! Action
|-
| <code>Ctrl + /</code>
| View hotkeys
|-
| <code>Ctrl + Tab</code>
| Switch tabs
|-
| <code>F11</code>
| Full screen
|-
| <code>Ctrl + \</code>
| Clear formatting
|}

Tplink Mikrotik Equivalent

2026-02-25T06:55:02Z

BabiSender: Created page with "= TP-Link vs MikroTik: Switch Equivalents and Non-China Alternatives = ---- == TP-Link vs MikroTik Switch Comparison (Lazada Philippines) == {| class="wikitable" |- ! TP-Link Model ! Description (Ports, PoE Budget, Layer Support) ! Lazada Price ! MikroTik Equivalent ! Lazada Price |- | [https://www.lazada.com.ph/products/tp-link-tl-sg3424-24-port-gigabit-l2-managed-switch-i149548514-s176532765.html '''TL-SG3424'''] | 24-Port Gigabit Managed Switch (No PoE, Layer 2) |..."

= TP-Link vs MikroTik: Switch Equivalents and Non-China Alternatives =

----

== TP-Link vs MikroTik Switch Comparison (Lazada Philippines) ==

{| class="wikitable"
|-
! TP-Link Model
! Description (Ports, PoE Budget, Layer Support)
! Lazada Price
! MikroTik Equivalent
! Lazada Price
|-
| [https://www.lazada.com.ph/products/tp-link-tl-sg3424-24-port-gigabit-l2-managed-switch-i149548514-s176532765.html '''TL-SG3424''']
| 24-Port Gigabit Managed Switch (No PoE, Layer 2)
| ₱8,900
| [https://www.lazada.com.ph/products/mikrotik-crs326-24g-2srm-cloud-router-switch-24-gigabit-port-switch-w-2-sfp-cages-in-1u-rackmount-case-dual-boot-routeros-or-switchos-crs326-i627130727.html '''CSS326-24G-2S+RM''']
| ₱10,049
|-
| [https://www.lazada.com.ph/products/tp-link-tl-sg2210mp-jetstream-10-port-gigabit-smart-switch-with-8-poe-ports-i1695704721.html '''TL-SG2210MP''']
| 10-Port Gigabit Smart Switch (8 PoE+, 150W, Layer 2+)
| ₱10,990
| [https://www.lazada.com.ph/products/mikrotik-crs112-8p-4s-in-cloud-router-switch-i647127116.html '''CRS112-8P-4S-IN''']
| ₱12,359
|-
| [https://www.lazada.com.ph/products/tp-link-tl-sg1024de-24-port-gigabit-easy-smart-switch-i111305859-s113784783.html '''TL-SG1024DE''']
| 24-Port Gigabit Easy Smart (No PoE, Layer 2)
| ₱4,000
| [https://www.lazada.com.ph/products/mikrotik-crs326-24g-2srm-cloud-router-switch-24-gigabit-port-switch-w-2-sfp-cages-in-1u-rackmount-case-dual-boot-routeros-or-switchos-crs326-i627130727.html '''CSS326-24G-2S+RM''']
| ₱10,049
|-
| [https://www.lazada.com.ph/products/tp-link-tl-sg108pe-8-port-gigabit-easy-smart-switch-4-port-poe-i138322841.html '''TL-SG108PE''']
| 8-Port Gigabit Easy Smart (4 PoE+, 55W, Layer 2)
| ₱4,295
| [https://www.lazada.com.ph/products/mikrotik-rb260gsp-5-port-gigabit-smart-switch-with-poe-out-i629619412.html '''RB260GSP''']
| ₱3,950
|-
| [https://www.lazada.com.ph/products/tp-link-tl-sg3428-jetstream-24-port-gigabit-l2-managed-switch-with-4-10g-sfp-i1642355581.html '''TL-SG3428''']
| 24-Port Gigabit Managed (No PoE, Layer 2+)
| ₱17,999
| [https://www.lazada.com.ph/products/mikrotik-crs326-24g-2srm-cloud-router-switch-24-gigabit-port-switch-w-2-sfp-cages-in-1u-rackmount-case-dual-boot-routeros-or-switchos-crs326-i627130727.html '''CSS326-24G-2S+RM''']
| ₱10,049
|-
| [https://www.lazada.com.ph/products/tp-link-tl-sg2218-jetstream-16-port-gigabit-smart-switch-with-2-sfp-slots-i1782234235.html '''TL-SG2218''']
| 16-Port Gigabit Smart (No PoE, Layer 2+)
| ₱8,299
| [https://www.lazada.com.ph/products/mikrotik-css318-16g-2s-in-smart-switch-i647127120.html '''CSS318-16G-2S+IN''']
| ₱8,699
|}

=== Footnotes ===
* Verify MikroTik specifications (Layer support, PoE wattage, uplink ports) before procurement; listings can vary slightly by seller.
* Prices are indicative; check Lazada for current rates.
* MikroTik <code>CSS</code> series uses '''SwitchOS''', while <code>CRS</code> supports both '''RouterOS''' and '''SwitchOS''' for flexible management.

----

== China (TP-Link) Alternatives in Network Equipment ==

=== Context ===
China-based brands like TP-Link have dominated the low- to mid-tier networking market for years. However, growing concerns over supply chain dependency, firmware transparency, and data sovereignty are pushing integrators and IT managers to explore '''non-China alternatives'''.

----

=== 1. Japan: The Exit of NEC and the Void Left Behind ===

* '''NEC's Exit (2024):''' NEC formally exited the network hardware market segment outside of its enterprise and telco contracts. Its managed switch line was phased out due to declining margins and internal restructuring to focus on core telecom and AI services.
* '''Impact:''' Left a vacuum in the mid-tier enterprise segment that Japan once filled with dependable, security-oriented equipment.
* '''Current Japanese Presence:''' Companies like Furukawa Electric and Hitachi Kokusai retain niche positions but not in the mass-market switch or router sectors. Japan remains strong in industrial automation networking (Ethernet/IP, Profinet, etc.), but '''not in general managed switches'''.

----

=== 2. European Alternatives ===

==== MikroTik (Latvia) ====
* '''Positioning:''' The strongest European alternative to TP-Link in terms of affordability and feature set.
* '''Product Range:''' Switches (CSS and CRS series), routers, access points, and carrier-grade routing systems.
* '''Strengths:''' RouterOS flexibility, strong VLAN/QoS/Layer3-lite functions, and open configuration environment.
* '''Weaknesses:''' Steeper learning curve; smaller support network in the Philippines.

==== Ubiquiti (USA/European operations in Lithuania and Poland) ====
* '''Positioning:''' Hybrid US/EU company with European manufacturing.
* '''Product Range:''' UniFi switches, Dream Machine routers, and APs.
* '''Strengths:''' Ecosystem integration, solid software controller, strong community support.
* '''Weaknesses:''' Closed ecosystem, proprietary controller dependencies, and higher pricing.

==== D-Link (originally Taiwan, now with EU and SEA ops) ====
* '''Positioning:''' Transitional vendor between budget and enterprise space.
* '''Strengths:''' Widely available, established Philippine distribution.
* '''Weaknesses:''' Limited innovation; slower firmware updates.

----

=== 3. Taiwan's Offerings ===

==== Zyxel (Taiwan) ====
* '''Product Range:''' Managed switches, security gateways, and WiFi access points.
* '''Strengths:''' Strong SMB presence, cloud-managed Nebula platform, and robust after-sales support in Asia.
* '''Weaknesses:''' Slightly higher cost per port than TP-Link; Nebula licensing for some features.

==== QNAP (Taiwan) ====
* '''Product Range:''' Primarily NAS but offers high-performance managed switches (QSW series).
* '''Strengths:''' High-speed 2.5G/10G switching integrated with NAS environments.
* '''Weaknesses:''' Limited management features; geared toward small offices and media setups.

==== Edgecore Networks (Taiwan) ====
* '''Product Range:''' Enterprise and telco-grade managed switches, open networking hardware (ONIE, SONiC).
* '''Strengths:''' Open networking capability; used by hyperscalers (Facebook, Google).
* '''Weaknesses:''' Requires advanced network engineering knowledge; limited retail availability.

----

=== 4. South Korea's Options ===

==== Dasan Zhone Solutions (DZS) ====
* '''Product Range:''' Managed switches, GPON/EPON access systems, and broadband access gear.
* '''Strengths:''' Industrial-grade reliability; active telco partnerships in SEA.
* '''Weaknesses:''' Higher price point; limited consumer and SMB presence.

==== HFR Networks ====
* '''Product Range:''' Metro Ethernet and 5G backhaul systems.
* '''Strengths:''' Strong in enterprise-grade and telco deployments.
* '''Weaknesses:''' Minimal SMB presence; not cost-competitive for general IT infrastructure.

----

=== 5. Distribution & Supply Chain Notes ===

* '''VST-ECS Lock-In:''' Many mainstream brands (TP-Link, D-Link, Ubiquiti, Hikvision) in the Philippines are distributed through '''VST-ECS''', creating a bottleneck and potential conflict of interest for integrators seeking vendor-neutral sourcing.
* '''Alternative Channels:''' European and Taiwanese brands (MikroTik, Zyxel, Edgecore) are increasingly available through '''independent online retailers''' or '''direct procurement via EU warehouses'''.

----

=== 6. Summary: Strategic Direction for Migration ===

{| class="wikitable"
|-
! Region
! Brand
! Market Position
! Pros
! Cons
|-
| '''Europe'''
| MikroTik
| Affordable Enterprise
| High configurability, open OS
| Steep learning curve
|-
| '''Europe/US'''
| Ubiquiti
| Ecosystem-Driven
| Integrated UI, wide support
| Proprietary control, cost
|-
| '''Taiwan'''
| Zyxel
| SMB/Enterprise Hybrid
| Nebula Cloud Mgmt, reliable
| Subscription overhead
|-
| '''Taiwan'''
| Edgecore
| Enterprise/Open Networking
| SONiC/ONIE support
| Requires network expertise
|-
| '''South Korea'''
| DZS
| Telco/Industrial
| Robust hardware
| Expensive, limited SMB support
|}

'''Conclusion:''' Migrating away from TP-Link and other China-based brands means adopting a mixed-vendor European and Taiwanese stack. MikroTik offers the most practical step for early migration due to its affordability and feature parity, while Zyxel and Edgecore can be integrated gradually for higher-end deployments.

----

== MikroTik Wireless Devices Overview ==

{| class="wikitable"
|-
! Model
! Description
! Price (PHP, ₱80/USD)
|-
| [https://mikrotik.com/product/audience '''Audience''']
| Tri-band mesh WiFi (2.4 GHz + dual 5 GHz), RouterOS powered, PoE-in, ideal for large homes or offices.
| ₱13,520
|-
| [https://mikrotik.com/product/hap_ax3 '''hAP ax³''']
| WiFi 6 router, dual-band 2.4 GHz + 5 GHz, quad-core ARM CPU, 1 GB RAM, 5× Gigabit Ethernet.
| ₱14,320 (US $179)
|-
| [https://mikrotik.com/product/cap_ax '''cAP ax''']
| Ceiling-mounted dual-band WiFi 6 AP, designed for enterprise or campus mesh networks, PoE-in supported.
| ₱9,520 (US $119)
|-
| [https://mikrotik.com/product/chateau_5g '''Chateau 5G''']
| Dual-band WiFi 5 router with built-in 5G NR modem, 5× Gigabit ports, LTE/5G WAN redundancy.
| ₱36,000 (US $450)
|-
| [https://mikrotik.com/product/chateau_lte12 '''Chateau LTE12''']
| Dual-band WiFi 5 router with CAT12 LTE modem, ideal for areas with limited wired internet access.
| ₱16,800 (US $210)
|-
| [https://mikrotik.com/product/lhg_lte6_kit '''LHG LTE6 Kit''']
| Outdoor LTE CPE with 17 dBi antenna, long-range rural connectivity, PoE-in support, single Ethernet port.
| ₱9,600 (US $120)
|-
| [https://mikrotik.com/product/wap_ac '''wAP ac''']
| Weatherproof dual-band (2.4 GHz + 5 GHz) access point for outdoor installations, compact form factor.
| ₱5,360 (US $67)
|-
| [https://mikrotik.com/product/ldf_lte6_kit '''LDF LTE6 Kit''']
| Outdoor LTE CPE designed to fit standard satellite dishes, increasing range for remote connectivity.
| ₱8,000 (US $100)
|-
| [https://mikrotik.com/product/hap_ax2 '''hAP ax²''']
| Compact WiFi 6 router, dual-band, 4× Gigabit ports, optimized for small offices and home networks.
| ₱9,520 (US $119)
|-
| [https://mikrotik.com/product/wap_ax '''wAP ax''' (wAPG-5HaxD2HaxD)]
| Weatherproof dual-band WiFi 6 AP with 2× Gigabit Ethernet, PoE-in and DC jack, RouterOS v7. '''Available stock via United Plexus.'''
| ₱5,250 (VAT INC)
|-
| [https://mikrotik.com/product/cap_ax '''cAP ax''' (RbcAPGi-5HaxD2HaxD)]
| Ceiling-mount WiFi 6 AP with PoE-in and PoE-out, 1 GB RAM, quad-core CPU, optimized for enterprise deployment. '''ETA mid-Nov via United Plexus.'''
| ₱7,600 (VAT INC)
|}

=== Summary Notes ===
* Prices converted at '''₱80 per USD''', unless otherwise noted as VAT INC.
* Models from '''United Plexus''': wAP ax (current stock) and cAP ax (mid-Nov arrival).
* Most models support '''RouterOS v7''' and PoE-in for flexible deployment.
* WiFi 6 models (hAP ax², hAP ax³, cAP ax, wAP ax) are recommended for future-proof installations.
* LTE/5G models (Chateau series, LHG LTE6, LDF LTE6) provide strong options for off-grid or rural connectivity.

2026 MIS IT KRA KPI Biz Plan

2026-02-25T06:54:39Z

BabiSender: Created page with "= 2026 MIS IT KRA KPI Business Plan = == IT Request Management and Turnaround Time Monitoring == '''Objective:''' Efficiently manage and resolve IT requests to ensure minimal downtime and maintain high service levels. Establish and monitor turnaround time for IT requests to enhance efficiency and service quality. === KPI === * '''Review Time:''' 3 calendar days (≈2 workdays) * '''Task Time:''' 3 calendar days (≈2 workdays) * '''Repairs & Emergencies:''' SLA < 1 da..."

= 2026 MIS IT KRA KPI Business Plan =

== IT Request Management and Turnaround Time Monitoring ==

'''Objective:''' Efficiently manage and resolve IT requests to ensure minimal downtime and maintain high service levels. Establish and monitor turnaround time for IT requests to enhance efficiency and service quality.

=== KPI ===
* '''Review Time:''' 3 calendar days (≈2 workdays)
* '''Task Time:''' 3 calendar days (≈2 workdays)
* '''Repairs & Emergencies:''' SLA < 1 day

=== Plan / Program ===
* Daily monitoring by '''Justin, Avie, Jun, and Mike''' using ERPNext:
** [https://erp1.cornersteelsystems.com/app/task?name=%5B%22like%22%2C%22%25ITR%25%22%5D ITR List]
** [https://erp1.cornersteelsystems.com/app/dashboard-view/ITR%20DASHBOARD Dashboard]
* Ensure all tickets are assigned, acknowledged, and have receipt confirmation.
* Dashboards show SLA by category (Access, IT Equipment, Admin Services, etc.) with 4.5-day SLA targets.
* Analyze trends to reduce delays and improve workflows.

----

== Secure and Protect Company Information Systems and Hardware ==

'''Objective:''' Ensure protection and continuous availability of all company IT assets through documented preventive maintenance, security protocols, and role-based accountability.

=== KPI ===
* Document IT preventive maintenance and security scope.
* Complete duty and procedure listings by '''Feb 2026'''.
* Integrate documentation into MIS IT Procedure Plan.

=== Plan / Program ===
* Maintain a [https://erp.comfac-it.com/wiki/home wiki-based documentation system].
* Consolidate Risk Management Plan + Biz Plan into one MIS Action Plan.
* Require IT sub-teams (ERPNext, Network, Support, QMS) to submit duties.
* Conduct monthly compliance checks via dashboards.

----

== Notes ==

{| class="wikitable"
|-
! Note
! Detail
|-
| SLA Duration Basis
| SLA durations are logged in '''calendar days'''. To compare with working days, apply a '''1.4 multiplier''' (1 workday × 1.4 = 1.4 calendar days). Therefore, 3 calendar days ≈ 2 working days.
|}

== Reference Links ==

* [https://next.comfaccorp.com/f/169723 2026 MIS IT KRA KPI Biz Plan]
* [https://next.comfaccorp.com/f/73709 2026 Risk and Opportunities]
* [https://docs.google.com/spreadsheets/d/19_AjOFAdVgNHF42QUCs8KcC6LNzyf340f_zWQnY1vYk/edit?gid=1459534687#gid=1459534687 251027 Cornersteel Users]
* [https://next.comfaccorp.com/s/qtpzGJbZaxjNAHt 2024 Audit Findings – No Risk and Opportunities Plan]

SALES INVOICE TAX OUTPUT 250829

2026-02-25T06:54:14Z

BabiSender: Created page with "= Sales Invoice Tax Output Report = This page documents the development history and SQL query versions for the '''Sales Invoice Tax Output''' custom report in ERPNext. It is used to extract VAT output tax data per sales invoice, including customer tax IDs, payment references, project links, and item descriptions. ---- == Report Columns == The final report includes the following columns: * '''Posting Date''' * '''Sales Invoice ID''' * '''Customer Tax ID''' * '''Custo..."

= Sales Invoice Tax Output Report =

This page documents the development history and SQL query versions for the '''Sales Invoice Tax Output''' custom report in ERPNext. It is used to extract VAT output tax data per sales invoice, including customer tax IDs, payment references, project links, and item descriptions.

----

== Report Columns ==

The final report includes the following columns:

* '''Posting Date'''
* '''Sales Invoice ID'''
* '''Customer Tax ID'''
* '''Customer'''
* '''Invoice Total'''
* '''Grand Total'''
* '''Amount (Sales Taxes and Charges)''' – VAT Output filtered by account head
* '''Sales Orders ID (via Project)''' – SO linked through project dimension (preferred)
* '''Sales Orders ID (from Items)''' – SO directly on SI items (secondary)
* '''Payment ID''' – Payment Entry references
* '''Account Head (Sales Taxes and Charges)'''
* '''Debit To'''
* '''Against Income Account'''
* '''Project'''
* '''Projects/JO (List)'''
* '''Description'''

----

== Query Version History ==

=== 250829 – Initial Version (Missing Description and SO) ===

<pre>
SELECT
si.posting_date AS "Posting Date:Date:100",
si.name AS "Sales Invoice ID:Link/Sales Invoice:140",
cust.tax_id AS "Customer Tax ID:Data:150",
si.customer AS "Customer:Data:200",
si.total AS "Invoice Total:Currency:150",
si.grand_total AS "Grand Total:Currency:150",
(
SELECT COALESCE(SUM(stc.tax_amount_after_discount_amount), 0)
FROM `tabSales Taxes and Charges` stc
WHERE stc.parent = si.name
AND stc.account_head = '2506 - VATOUTPUT TAXES PAYABLE - ESCO'
) AS "Amount (Sales Taxes and Charges):Currency:140",
(
SELECT GROUP_CONCAT(DISTINCT sii.sales_order SEPARATOR ', ')
FROM `tabSales Invoice Item` sii
WHERE sii.parent = si.name AND sii.sales_order IS NOT NULL
) AS "Sales Orders ID:Data:200",
(
SELECT GROUP_CONCAT(DISTINCT per.parent SEPARATOR ', ')
FROM `tabPayment Entry Reference` per
WHERE per.reference_doctype = 'Sales Invoice'
AND per.reference_name = si.name
) AS "Payment ID:Link/Payment Entry:200",
(
SELECT stc2.account_head
FROM `tabSales Taxes and Charges` stc2
WHERE stc2.parent = si.name
AND stc2.account_head = '2506 - VATOUTPUT TAXES PAYABLE - ESCO'
LIMIT 1
) AS "Account Head (Sales Taxes and Charges):Data:240",
si.debit_to AS "Debit To:Link/Account:200",
(
SELECT GROUP_CONCAT(DISTINCT sii3.income_account SEPARATOR ', ')
FROM `tabSales Invoice Item` sii3
WHERE sii3.parent = si.name
) AS "Against Income Account:Data:220",
(
SELECT sii2.project
FROM `tabSales Invoice Item` sii2
WHERE sii2.parent = si.name AND IFNULL(sii2.project, '') != ''
LIMIT 1
) AS "Project:Link/Project:120",
si.remarks AS "Remarks:Data:250"
FROM `tabSales Invoice` si
LEFT JOIN `tabCustomer` cust ON cust.name = si.customer
WHERE si.docstatus = 1
AND si.company = %(company)s
AND si.posting_date BETWEEN %(from_date)s AND %(to_date)s
ORDER BY si.posting_date, si.name
</pre>

----

=== 250829 – Final Version (Added Description, SO via Project, Projects List) ===

'''Key changes:'''
* Moved SO ID column to use '''project dimension''' (more reliable linkage).
* Kept SO ID via items as a secondary column.
* Added '''Description''' column (from SI item descriptions/names).
* Added '''Projects/JO (List)''' column.
* Reordered columns for clarity.

<pre>
SELECT
si.posting_date AS "Posting Date:Date:100",
si.name AS "Sales Invoice ID:Link/Sales Invoice:160",
cust.tax_id AS "Customer Tax ID:Data:150",
si.customer AS "Customer:Data:200",
si.total AS "Invoice Total:Currency:150",
si.grand_total AS "Grand Total:Currency:150",
(
SELECT COALESCE(SUM(stc.tax_amount_after_discount_amount), 0)
FROM `tabSales Taxes and Charges` stc
WHERE stc.parent = si.name
AND stc.account_head = '2506 - VATOUTPUT TAXES PAYABLE - ESCO'
) AS "Amount (Sales Taxes and Charges):Currency:160",
(
SELECT GROUP_CONCAT(DISTINCT sii_i.sales_order ORDER BY sii_i.sales_order SEPARATOR ', ')
FROM `tabSales Invoice Item` sii_i
WHERE sii_i.parent = si.name
AND sii_i.sales_order IS NOT NULL AND sii_i.sales_order != ''
) AS "Sales Orders ID (from Items):Data:220",
(
SELECT GROUP_CONCAT(DISTINCT per.parent ORDER BY per.parent SEPARATOR ', ')
FROM `tabPayment Entry Reference` per
WHERE per.reference_doctype = 'Sales Invoice'
AND per.reference_name = si.name
) AS "Payment ID:Link/Payment Entry:220",
(
SELECT stc2.account_head
FROM `tabSales Taxes and Charges` stc2
WHERE stc2.parent = si.name
AND stc2.account_head = '2506 - VATOUTPUT TAXES PAYABLE - ESCO'
LIMIT 1
) AS "Account Head (Sales Taxes and Charges):Data:260",
si.debit_to AS "Debit To:Link/Account:200",
(
SELECT GROUP_CONCAT(DISTINCT sii_ia.income_account ORDER BY sii_ia.income_account SEPARATOR ', ')
FROM `tabSales Invoice Item` sii_ia
WHERE sii_ia.parent = si.name
) AS "Against Income Account:Data:240",
(
SELECT sii_p.project
FROM `tabSales Invoice Item` sii_p
WHERE sii_p.parent = si.name AND IFNULL(sii_p.project, '') != ''
ORDER BY sii_p.idx ASC LIMIT 1
) AS "Project:Link/Project:140",
(
SELECT IFNULL(GROUP_CONCAT(
IFNULL(NULLIF(sii_d.description, ''), IFNULL(sii_d.item_name, sii_d.item_code))
ORDER BY sii_d.idx SEPARATOR '; '), '')
FROM `tabSales Invoice Item` sii_d
WHERE sii_d.parent = si.name
) AS "Description:Data:400",
(
SELECT IFNULL(GROUP_CONCAT(DISTINCT so_x.name ORDER BY so_x.transaction_date, so_x.name SEPARATOR ', '), '')
FROM `tabSales Order` so_x
WHERE so_x.company = si.company
AND (
EXISTS (
SELECT 1 FROM `tabSales Invoice Item` sii_px
WHERE sii_px.parent = si.name AND IFNULL(sii_px.project,'') != ''
AND so_x.project = sii_px.project
)
OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi_px
WHERE soi_px.parent = so_x.name AND IFNULL(soi_px.project,'') != ''
AND EXISTS (
SELECT 1 FROM `tabSales Invoice Item` sii_py
WHERE sii_py.parent = si.name AND IFNULL(sii_py.project,'') != ''
AND soi_px.project = sii_py.project
)
)
)
) AS "Sales Orders ID (via Project):Data:240",
(
SELECT IFNULL(GROUP_CONCAT(DISTINCT sii_pl.project ORDER BY sii_pl.project SEPARATOR ', '), '')
FROM `tabSales Invoice Item` sii_pl
WHERE sii_pl.parent = si.name AND IFNULL(sii_pl.project,'') != ''
) AS "Projects/JO (List):Data:220"
FROM `tabSales Invoice` si
LEFT JOIN `tabCustomer` cust ON cust.name = si.customer
WHERE si.docstatus = 1
AND si.company = %(company)s
AND si.posting_date BETWEEN %(from_date)s AND %(to_date)s
ORDER BY si.posting_date, si.name
</pre>

----

== Column Reference ==

{| class="wikitable"
|-
! Column
! Source
! Notes
|-
| Posting Date
| <code>tabSales Invoice.posting_date</code>
|
|-
| Sales Invoice ID
| <code>tabSales Invoice.name</code>
| Link field
|-
| Customer Tax ID
| <code>tabCustomer.tax_id</code>
| Joined from Customer table
|-
| Customer
| <code>tabSales Invoice.customer</code>
|
|-
| Invoice Total
| <code>tabSales Invoice.total</code>
| Pre-tax total
|-
| Grand Total
| <code>tabSales Invoice.grand_total</code>
| Post-tax total
|-
| VAT Amount
| <code>tabSales Taxes and Charges.tax_amount_after_discount_amount</code>
| Filtered by account head <code>2506 - VATOUTPUT TAXES PAYABLE - ESCO</code>
|-
| Sales Orders ID (from Items)
| <code>tabSales Invoice Item.sales_order</code>
| Direct link on SI items
|-
| Sales Orders ID (via Project)
| <code>tabSales Order</code> (subquery via project match)
| More reliable; matches SO linked to same project as SI items
|-
| Payment ID
| <code>tabPayment Entry Reference.parent</code>
| Payment entries referencing this SI
|-
| Account Head
| <code>tabSales Taxes and Charges.account_head</code>
| VAT output account
|-
| Debit To
| <code>tabSales Invoice.debit_to</code>
| Accounts Receivable account
|-
| Against Income Account
| <code>tabSales Invoice Item.income_account</code>
| Distinct list from all SI items
|-
| Project
| <code>tabSales Invoice Item.project</code>
| First non-null project from items
|-
| Description
| <code>tabSales Invoice Item.description</code> / <code>item_name</code>
| Concatenated with semicolon separator
|-
| Projects/JO (List)
| <code>tabSales Invoice Item.project</code>
| Distinct list of all projects on the invoice
|}

----

== Notes ==

* The '''account head''' value <code>2506 - VATOUTPUT TAXES PAYABLE - ESCO</code> must be updated if used for a different company.
* '''Sales Orders ID (via Project)''' is the preferred SO reference as it handles cases where the SO is not directly linked on the SI item.
* Report uses <code>%(company)s</code>, <code>%(from_date)s</code>, and <code>%(to_date)s</code> as ERPNext report filter parameters.

Projects in Process Report 251023

2026-02-25T06:53:50Z

BabiSender: Created page with "= Projects in Process Report = This page documents the development history and SQL query versions for the '''Projects in Process''' custom report in ERPNext. Queries are listed from earliest to latest revision. ---- == Report Columns == The final report includes the following columns: * '''PROJECT ID''' – Link to Project * '''Department''' – Link to Department * '''Customer''' – Link to Customer * '''Earliest SO''' – Link to Sales Order * '''Estimated Start..."

= Projects in Process Report =

This page documents the development history and SQL query versions for the '''Projects in Process''' custom report in ERPNext. Queries are listed from earliest to latest revision.

----

== Report Columns ==

The final report includes the following columns:

* '''PROJECT ID''' – Link to Project
* '''Department''' – Link to Department
* '''Customer''' – Link to Customer
* '''Earliest SO''' – Link to Sales Order
* '''Estimated Start Date''' (or Earliest SO Date in earlier versions)
* '''Total SI Items (Base, by Project)''' – Currency
* '''Total Purchase Invoices (Grand Total)''' – Currency
* '''Project MR (from Stores)''' – Currency (Stock Entry withdrawals from Stores)
* '''Project MRS (to Stores)''' – Currency (Stock Entry returns to Stores)
* '''Timesheets Costing Amount (by Project)''' – Currency
* '''Remainder (SI - PI - MR - TS)''' – Currency
* '''Sales Order Items (List)''' – Data

----

== Query Version History ==

=== 250828 – Initial Working Version ===
Basic report with Project ID, Department, Customer, Sales Order Date. No Timesheets or MR/MRS columns yet.

<pre>
SELECT
proj.name AS "PROJECT ID:Link/Project:120",
proj.department AS "Department:Link/Department:150",
proj.customer AS "Customer:Link/Customer:200",
(
SELECT MIN(so.transaction_date)
FROM `tabSales Order` so
WHERE so.company = proj.company
AND (
so.project = proj.name
OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi
WHERE soi.parent = so.name AND soi.project = proj.name
)
)
) AS "Sales Order Date:Date:120"
FROM `tabProject` proj
WHERE proj.company = %(company)s
ORDER BY proj.name
</pre>

----

=== 250828 – Added Sales Order Link + Items List ===
Added Sales Order name column and Sales Order Items list (plain text, no brackets).

<pre>
SELECT
proj.name AS "PROJECT ID:Link/Project:120",
proj.department AS "Department:Link/Department:150",
proj.customer AS "Customer:Link/Customer:200",
(
SELECT so.name
FROM `tabSales Order` so
WHERE so.company = proj.company
AND (
so.project = proj.name
OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi
WHERE soi.parent = so.name AND soi.project = proj.name
)
)
ORDER BY so.transaction_date ASC, so.name ASC
LIMIT 1
) AS "Sales Order:Link/Sales Order:180",
(
SELECT MIN(so.transaction_date)
FROM `tabSales Order` so
WHERE so.company = proj.company
AND (
so.project = proj.name
OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi
WHERE soi.parent = so.name AND soi.project = proj.name
)
)
) AS "Sales Order Date:Date:120",
(
SELECT IFNULL(
GROUP_CONCAT(IFNULL(soi.item_name, soi.item_code) ORDER BY soi.idx SEPARATOR ', '),
''
)
FROM `tabSales Order Item` soi
WHERE soi.parent = (
SELECT so.name
FROM `tabSales Order` so
WHERE so.company = proj.company
AND (
so.project = proj.name
OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi2
WHERE soi2.parent = so.name AND soi2.project = proj.name
)
)
ORDER BY so.transaction_date ASC, so.name ASC
LIMIT 1
)
) AS "Sales Order Items (List):Data:360"
FROM `tabProject` proj
WHERE proj.company = %(company)s
ORDER BY proj.name
</pre>

----

=== 250828 – Added Purchase Invoices + Project Stock Value ===
Added Total Purchase Invoices and Project Stock Value (current + as-of date) using Bin and Stock Ledger Entry.

<pre>
WITH
earliest_so AS (
SELECT
p.name AS project,
(
SELECT so2.name
FROM `tabSales Order` so2
WHERE so2.company = p.company
AND (so2.project = p.name OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi2
WHERE soi2.parent = so2.name AND soi2.project = p.name))
ORDER BY so2.transaction_date ASC, so2.name ASC LIMIT 1
) AS so_name,
(
SELECT MIN(so3.transaction_date)
FROM `tabSales Order` so3
WHERE so3.company = p.company
AND (so3.project = p.name OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi3
WHERE soi3.parent = so3.name AND soi3.project = p.name))
) AS so_date
FROM `tabProject` p WHERE p.company = %(company)s
),
pi_totals AS (
SELECT pii.project AS project, SUM(DISTINCT pi.grand_total) AS pi_total
FROM `tabPurchase Invoice` pi
JOIN `tabPurchase Invoice Item` pii ON pi.name = pii.parent
WHERE pi.docstatus = 1
GROUP BY pii.project
),
proj_wh AS (
SELECT p.name AS project, p.company, w.name AS wh
FROM `tabProject` p
JOIN `tabWarehouse` w ON w.company = p.company AND w.`custom_project` = p.name
WHERE p.company = %(company)s
),
bin_val AS (
SELECT pw.project, SUM(b.actual_qty * IFNULL(b.valuation_rate, 0)) AS val_now
FROM proj_wh pw
JOIN `tabBin` b ON b.warehouse = pw.wh
GROUP BY pw.project
),
asof_val AS (
SELECT pw.project, SUM(sle.stock_value) AS val_asof
FROM proj_wh pw
JOIN (
SELECT x.item_code, x.warehouse, IFNULL(x.batch_no, '') AS batch_no,
MAX(CONCAT(x.posting_date, ' ', x.posting_time, ' ', x.name)) AS maxkey
FROM `tabStock Ledger Entry` x
WHERE x.is_cancelled = 0 AND x.posting_date <= %(to_date)s
GROUP BY x.item_code, x.warehouse, IFNULL(x.batch_no, '')
) last ON last.warehouse = pw.wh
JOIN `tabStock Ledger Entry` sle
ON sle.item_code = last.item_code AND sle.warehouse = last.warehouse
AND IFNULL(sle.batch_no, '') = last.batch_no
AND CONCAT(sle.posting_date, ' ', sle.posting_time, ' ', sle.name) = last.maxkey
GROUP BY pw.project
)
SELECT
p.name AS "PROJECT ID:Link/Project:120",
p.department AS "Department:Link/Department:150",
p.customer AS "Customer:Link/Customer:200",
e.so_name AS "Sales Order:Link/Sales Order:160",
e.so_date AS "Sales Order Date:Date:110",
(
SELECT IFNULL(GROUP_CONCAT(IFNULL(soi.item_name, soi.item_code) ORDER BY soi.idx SEPARATOR ', '), '')
FROM `tabSales Order Item` soi WHERE soi.parent = e.so_name
) AS "Sales Order Items (List):Data:300",
COALESCE(pt.pi_total, 0) AS "Total Purchase Invoices (Grand Total):Currency:160",
COALESCE(bv.val_now, 0) AS "Project Stock Value (Current):Currency:160",
COALESCE(av.val_asof, 0) AS "Project Stock Value as of To Date:Currency:170"
FROM `tabProject` p
LEFT JOIN earliest_so e ON e.project = p.name
LEFT JOIN pi_totals pt ON pt.project = p.name
LEFT JOIN bin_val bv ON bv.project = p.name
LEFT JOIN asof_val av ON av.project = p.name
WHERE p.company = %(company)s
ORDER BY p.name
</pre>

----

=== 250901 – Added Timesheets Costing Amount ===
Timesheet costing amount column enabled. Stock Value columns still present at this stage.

<pre>
SELECT
p.name AS "PROJECT ID:Link/Project:140",
p.department AS "Department:Link/Department:150",
p.customer AS "Customer:Link/Customer:200",
e.so_name AS "Earliest SO:Link/Sales Order:160",
e.so_date AS "Earliest SO Date:Date:110",
COALESCE(si.si_items_total_base, 0) AS "Total SI Items (Base, by Project):Currency:180",
COALESCE(pt.pi_total, 0) AS "Total Purchase Invoices (Grand Total):Currency:170",
COALESCE(av.val_asof, 0) AS "Project Stock Value (As of Last Movement):Currency:180",
COALESCE(ts.ts_costing_amount, 0) AS "Timesheets Costing Amount (by Project):Currency:180",
(
SELECT IFNULL(GROUP_CONCAT(IFNULL(soi.item_name, soi.item_code) ORDER BY soi.idx SEPARATOR ', '), '')
FROM `tabSales Order Item` soi WHERE soi.parent = e.so_name
) AS "Sales Order Items (List):Data:300"
FROM `tabProject` p
/* ... (same LEFT JOINs as above) ... */
WHERE p.company = %(company)s
AND ( %(project_like)s = '' OR p.name LIKE %(project_like)s )
ORDER BY p.name
</pre>

----

=== 250901-01 – Replaced Stock Value with MR/MRS + Remainder Column ===
'''Key changes:'''
* Removed Project Stock Value column.
* Added '''Project MR''' (Stock Entry withdrawals where Source Warehouse LIKE <code>%Stores%</code>).
* Added '''Project MRS''' (Stock Entry returns where Target Warehouse LIKE <code>%Stores%</code>).
* Added '''Remainder''' column: SI Items − PI − MR − Timesheets.
* Replaced Earliest SO Date with '''Estimated Start Date''' (<code>p.expected_start_date</code>).

<pre>
SELECT
p.name AS "PROJECT ID:Link/Project:140",
p.department AS "Department:Link/Department:150",
p.customer AS "Customer:Link/Customer:200",
e.so_name AS "Earliest SO:Link/Sales Order:160",
p.expected_start_date AS "Estimated Start Date:Date:110",
COALESCE(si.si_items_total_base, 0) AS "Total SI Items (Base, by Project):Currency:180",
COALESCE(pt.pi_total, 0) AS "Total Purchase Invoices (Grand Total):Currency:170",
COALESCE(mr.mr_amount, 0) AS "Project MR (from Stores):Currency:160",
COALESCE(mrs.mrs_amount, 0) AS "Project MRS (to Stores):Currency:160",
COALESCE(ts.ts_costing_amount, 0) AS "Timesheets Costing Amount (by Project):Currency:180",
(
COALESCE(si.si_items_total_base, 0)
- (COALESCE(pt.pi_total, 0) + COALESCE(mr.mr_amount, 0) + COALESCE(ts.ts_costing_amount, 0))
) AS "Remainder (SI - PI - MR - TS):Currency:160",
(
SELECT IFNULL(GROUP_CONCAT(IFNULL(soi.item_name, soi.item_code) ORDER BY soi.idx SEPARATOR ', '), '')
FROM `tabSales Order Item` soi WHERE soi.parent = e.so_name
) AS "Sales Order Items (List):Data:300"
FROM `tabProject` p
LEFT JOIN (
SELECT p2.name AS project,
(SELECT so2.name FROM `tabSales Order` so2
WHERE so2.company = p2.company
AND (so2.project = p2.name OR EXISTS (
SELECT 1 FROM `tabSales Order Item` soi2
WHERE soi2.parent = so2.name AND soi2.project = p2.name))
ORDER BY so2.transaction_date ASC, so2.name ASC LIMIT 1) AS so_name
FROM `tabProject` p2
WHERE p2.company = %(company)s
AND ( %(project_like)s = '' OR p2.name LIKE %(project_like)s )
) e ON e.project = p.name
LEFT JOIN (
SELECT t.project, SUM(t.grand_total) AS pi_total
FROM (SELECT DISTINCT pi.name, pii.project, pi.grand_total
FROM `tabPurchase Invoice` pi
JOIN `tabPurchase Invoice Item` pii ON pi.name = pii.parent
WHERE pi.docstatus = 1 AND pi.company = %(company)s
AND pii.project IS NOT NULL AND pii.project != ''
AND ( %(project_like)s = '' OR pii.project LIKE %(project_like)s )) t
GROUP BY t.project
) pt ON pt.project = p.name
LEFT JOIN (
SELECT COALESCE(NULLIF(sii.project, ''), '<<NO PROJECT>>') AS project,
SUM(sii.base_net_amount) AS si_items_total_base
FROM `tabSales Invoice` si
JOIN `tabSales Invoice Item` sii ON sii.parent = si.name
WHERE si.docstatus = 1 AND si.company = %(company)s
AND ( %(project_like)s = '' OR sii.project LIKE %(project_like)s )
GROUP BY COALESCE(NULLIF(sii.project, ''), '<<NO PROJECT>>')
) si ON si.project = p.name
LEFT JOIN (
SELECT COALESCE(NULLIF(tsd.project, ''), '<<NO PROJECT>>') AS project,
SUM(tsd.costing_amount) AS ts_costing_amount
FROM `tabTimesheet Detail` tsd
JOIN `tabTimesheet` ts ON ts.name = tsd.parent
WHERE ts.docstatus = 1 AND ts.company = %(company)s
AND ( %(project_like)s = '' OR tsd.project LIKE %(project_like)s )
GROUP BY COALESCE(NULLIF(tsd.project, ''), '<<NO PROJECT>>')
) ts ON ts.project = p.name
LEFT JOIN (
SELECT COALESCE(NULLIF(COALESCE(sed.project, se.project), ''), '<<NO PROJECT>>') AS project,
SUM(IFNULL(sed.basic_amount, 0)) AS mr_amount
FROM `tabStock Entry` se
JOIN `tabStock Entry Detail` sed ON sed.parent = se.name
WHERE se.docstatus = 1 AND se.company = %(company)s
AND ( %(project_like)s = '' OR COALESCE(sed.project, se.project) LIKE %(project_like)s )
AND IFNULL(sed.s_warehouse, '') LIKE '%%Stores%%'
GROUP BY COALESCE(NULLIF(COALESCE(sed.project, se.project), ''), '<<NO PROJECT>>')
) mr ON mr.project = p.name
LEFT JOIN (
SELECT COALESCE(NULLIF(COALESCE(sed.project, se.project), ''), '<<NO PROJECT>>') AS project,
SUM(IFNULL(sed.basic_amount, 0)) AS mrs_amount
FROM `tabStock Entry` se
JOIN `tabStock Entry Detail` sed ON sed.parent = se.name
WHERE se.docstatus = 1 AND se.company = %(company)s
AND ( %(project_like)s = '' OR COALESCE(sed.project, se.project) LIKE %(project_like)s )
AND IFNULL(sed.t_warehouse, '') LIKE '%%Stores%%'
GROUP BY COALESCE(NULLIF(COALESCE(sed.project, se.project), ''), '<<NO PROJECT>>')
) mrs ON mrs.project = p.name
WHERE p.company = %(company)s
AND ( %(project_like)s = '' OR p.name LIKE %(project_like)s )
ORDER BY p.name
</pre>

----

== Column Reference ==

{| class="wikitable"
|-
! Column
! Source
! Notes
|-
| Project ID
| <code>tabProject.name</code>
| Link field
|-
| Department
| <code>tabProject.department</code>
| Link field
|-
| Customer
| <code>tabProject.customer</code>
| Link field
|-
| Earliest SO
| <code>tabSales Order</code> (subquery)
| Matches SO header OR SO Item project link
|-
| Estimated Start Date
| <code>tabProject.expected_start_date</code>
| Replaced SO Date in 250901-01
|-
| Total SI Items (Base)
| <code>tabSales Invoice Item.base_net_amount</code>
| Submitted SIs only
|-
| Total Purchase Invoices
| <code>tabPurchase Invoice.grand_total</code>
| Submitted PIs only; DISTINCT to avoid double-count
|-
| Project MR (from Stores)
| <code>tabStock Entry Detail.basic_amount</code>
| Source Warehouse LIKE <code>%Stores%</code>
|-
| Project MRS (to Stores)
| <code>tabStock Entry Detail.basic_amount</code>
| Target Warehouse LIKE <code>%Stores%</code>
|-
| Timesheets Costing Amount
| <code>tabTimesheet Detail.costing_amount</code>
| Submitted timesheets only
|-
| Remainder
| SI − PI − MR − TS
| Calculated column
|-
| Sales Order Items (List)
| <code>tabSales Order Item.item_name</code>
| GROUP_CONCAT, comma-separated, ordered by idx
|}

PfSense Sales Training Material

2026-02-25T06:53:28Z

BabiSender: Created page with "= pfSense Sales Training Material = '''Reference:''' [https://chatgpt.com/share/67c82515-7074-800e-b29c-0df75f5492f3 Full Session Log] ---- == 1. Introduction == ; Objective : Provide a clear, layman-friendly explanation of what a firewall is, why pfSense is a powerful solution, and how its key features protect networks. ; Audience : Sales teams who need to explain the technology to potential customers (non-technical decision-makers, IT managers, SMB owners). ----..."

= pfSense Sales Training Material =

'''Reference:''' [https://chatgpt.com/share/67c82515-7074-800e-b29c-0df75f5492f3 Full Session Log]

----

== 1. Introduction ==

; Objective
: Provide a clear, layman-friendly explanation of what a firewall is, why pfSense is a powerful solution, and how its key features protect networks.

; Audience
: Sales teams who need to explain the technology to potential customers (non-technical decision-makers, IT managers, SMB owners).

----

== 2. Network Basics ==

; Definition
: Networking is the ability to connect computers and systems together. It occurs when more than one device communicates with another device or group of devices.

=== Networking Disciplines ===

==== ECE (Electronics and Communication Engineering) ====
* Focuses on how electronic devices work and on designing/building network hardware from basic components.
* In the Philippines, a PRC ECE license is required to sign off plans for CCTV installations—the only legally mandated network designs (CCTV and phone lines).
* '''Sales Note:''' Clients needing custom electronic solutions (for automation or high-security requirements) will require ECE expertise.

==== IT (Information Technology) ====
* Specializes in deploying and integrating off-the-shelf networking equipment.
* Advanced configurations improve reliability, scalability (hundreds to thousands of users), and automation for convenience.
* '''Sales Note:''' Larger-scale deployments and convenience features command higher-level IT skills and corresponding investment.

=== Networking Functions ===

{| class="wikitable"
|-
! Function
! Description
|-
| '''WAN''' (Wide Area Network)
| Connects the facility to external networks (Internet or other sites).
|-
| '''LAN''' (Local Area Network)
| Connects devices within the facility for internal communications.
|-
| '''High Availability'''
| Builds redundancy and resilience so services stay online despite failures.
|-
| '''User Management'''
| Implements captive portals, LDAP, RADIUS to organize users by roles and privileges and control access.
|-
| '''Security'''
| Establishes hardened systems using DMZs (buffer zones), proxy servers (middlemen), and data hygiene practices.
|-
| '''Wireless'''
| Deploys mesh or enterprise Wi-Fi for convenient, flexible connectivity.
|-
| '''Wired'''
| Provides high-bandwidth, low-latency connections for critical systems.
|}

----

== 3. Why pfSense? ==

* '''Open Source:''' No recurring feature licenses; you pay only for support and updates. When support lapses, pfSense continues to work—only security updates stop.
* '''Enterprise Features:'''
** LAN/WAN routing and segmentation
** VPN (remote access and site-to-site)
** IDS/IPS (intrusion detection and prevention)
** High Availability & Load Balancing
** DHCP, DNS, and user Authentication
* '''Competitor Critique:''' Other vendors "rent" features that expire with licenses. pfSense features remain available indefinitely.

----

== 4. Core Functions ==

{| class="wikitable"
|-
! Function
! Explanation
|-
| '''LAN'''
| Segments and protects internal network traffic to enforce security zones.
|-
| '''WAN'''
| Controls access to the Internet; filters inbound/outbound traffic.
|-
| '''VPN'''
| Creates encrypted tunnels for secure remote access or site-to-site links.
|-
| '''IDS/IPS'''
| Monitors traffic for threats and automatically blocks or alerts on intrusions.
|}

----

== 5. Secondary Features ==

* '''Authentication:''' Integrates with Active Directory, LDAP, RADIUS for user-based firewall policies.
* '''DHCP:''' Assigns IP addresses automatically to devices on the network.
* '''DNS:''' Acts as resolver or forwarder to improve name lookup speed and security.
* '''Load Balancer / HA:''' Distributes traffic across multiple WAN links or appliances and provides failover.

----

== 6. Dispelling Key Misunderstandings ==

# '''"Anyone doesn't need a firewall"'''
#: ''Reality:'' Anyone hosting servers (web, NAS, ERP, AI apps) or running remote networks needs a firewall to block attacks and manage user access.
# '''"Firewalls only block traffic"'''
#: ''Reality:'' They also segment networks, prioritize critical traffic (e.g., video calls), and enable secure VPN connections.
# '''"Hardware firewalls exist"'''
#: ''Reality:'' All firewalls are computers running software—performance scales by upgrading NICs (100 Mbps → 1 Gbps → 10 Gbps → 100 Gbps).
# '''"Competitors offer better out-of-the-box"'''
#: ''Reality:'' Competitors lock features behind licenses that expire. pfSense provides full features without license lock-in—only updates and support require payment.

----

== 7. Sizing & Total Cost of Ownership (TCO) ==

=== Sizing Guidelines ===

{| class="wikitable"
|-
! Company Size / Bandwidth
! Recommended Model
! Notes
|-
| Under 1 Gbps Internet
| Netgate 6100 Series
| Fits most small-to-medium offices
|-
| Up to 500 Users
| 2× Netgate 4200 MAX (HA setup)
| ~120k PHP one-time cost for both appliances
|-
| Large Networks / ISPs (>1 Gbps)
| Netgate 6100+ or higher
| Only ISPs or large enterprises need these models
|}

=== Example: Makati Office (200 Users) ===

* '''Hardware Cost:''' 2×4200 MAX for HA → '''120,000 PHP''' (one-time)
* '''Annual Costs:'''
** License Renewal: 7,500 PHP × 2 = '''15,000 PHP/year'''
** TAC Support: '''45,000 PHP/year''' (one needed in HA)
** Snort Subscription: 24,000 PHP × 2 = '''48,000 PHP/year'''
** '''Total Annual: ~84,000 PHP/year'''

{{Note|'''Competitor Comparison:''' Fortinet equivalent: 150k PHP hardware + 200k PHP/year support → pfSense is more cost-effective.}}

----

== 8. Selling Process & Key Observations ==

=== Footprint ===
* Small office (<10 users), medium/large office (>100 users), or multi-building campus.
* Determine how many locations must operate as a single network to size solutions and costs.

=== Value of Data & Communication ===
* Quantify by manpower cost to change processes—high communication workloads indicate greater impact.

=== Pain Points ===
* Losses from unreliable or insecure networks: downtime, lost sales, and productivity hits.

=== Process Steps ===
# '''Discovery:''' Gather requirements (users, bandwidth, locations).
# '''Footprint Assessment:''' Map office layout and device count.
# '''Prioritize:''' Identify critical applications and data flows.
# '''Risk Analysis:''' Pinpoint security and availability concerns.
# '''Tailored Proposal:''' Match pfSense functions to customer needs.

----

== 9. Next Steps for Sales ==

# Select the right appliance (6100 vs 4200 MAX vs higher models).
# Prepare TCO comparison (pfSense vs competitor).
# Send proposal template and service brochure.

----

== Resources & References ==

* [https://www.comfac-it.com/services/netgate-pfsense-setup Setup Services]
* [https://www.comfac-it.com/blog-post/making-sense-of-unified-threat-management-utm UTM Deep Dive]
* [https://www.pfsense.org/products/ Netgate Product Info]

Steps to Repair and OCR a Scanned or Corrupted PDF in Ubuntu

2026-02-25T06:52:12Z

BabiSender: Created page with "= Steps to Repair and OCR a Scanned or Corrupted PDF in Ubuntu = ---- == Step 1: Clean or Repair the PDF == Use '''Ghostscript''' to rebuild damaged cross-reference tables and fix malformed PDF structure. <pre> sudo apt install ghostscript gs -o fixed.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress -dNOPAUSE -dBATCH "input.pdf" </pre> '''What it does:''' * Repairs broken references (<code>xref</code> errors) * Normalizes streams and compression * Outputs a clean, sta..."

= Steps to Repair and OCR a Scanned or Corrupted PDF in Ubuntu =

----

== Step 1: Clean or Repair the PDF ==

Use '''Ghostscript''' to rebuild damaged cross-reference tables and fix malformed PDF structure.

<pre>
sudo apt install ghostscript

gs -o fixed.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress -dNOPAUSE -dBATCH "input.pdf"
</pre>

'''What it does:'''
* Repairs broken references (<code>xref</code> errors)
* Normalizes streams and compression
* Outputs a clean, standards-compliant PDF (<code>fixed.pdf</code>)

If Ghostscript cannot fix the file, try '''qpdf''':

<pre>
sudo apt install qpdf
qpdf --repair "input.pdf" fixed.pdf
</pre>

----

== Step 2: Run OCR on the Cleaned PDF ==

Use '''OCRmyPDF''' to embed searchable text into the PDF.

<pre>
sudo apt install ocrmypdf tesseract-ocr tesseract-ocr-eng tesseract-ocr-fil
ocrmypdf --jobs 4 --deskew --clean -l eng+fil fixed.pdf output_ocr.pdf
</pre>

'''What it does:'''
* Performs OCR using Tesseract (English + Filipino)
* Deskews and cleans pages
* Embeds text layer for search and selection

If OCRmyPDF fails on rendering, use an alternate renderer:

<pre>ocrmypdf --pdf-renderer sandwich fixed.pdf output_ocr.pdf</pre>

If the PDF is too broken, force rasterization and OCR:

<pre>ocrmypdf --force-ocr fixed.pdf output_ocr.pdf</pre>

----

== Step 3: Verify OCR Success ==

Check if text extraction works:

<pre>pdftotext output_ocr.pdf - | head</pre>

If you see readable text, the OCR worked successfully.

----

== Summary Workflow ==

{| class="wikitable"
|-
! Step
! Tool
! Command
! Purpose
|-
| 1
| Ghostscript
| <code>gs -o fixed.pdf -sDEVICE=pdfwrite ...</code>
| Clean and repair corrupted PDF
|-
| 2
| QPDF
| <code>qpdf --repair input.pdf fixed.pdf</code>
| Alternate PDF repair if Ghostscript fails
|-
| 3
| OCRmyPDF
| <code>ocrmypdf --jobs 4 --deskew --clean fixed.pdf output_ocr.pdf</code>
| Add searchable text layer
|-
| 4
| Verify
| <code>pdftotext output_ocr.pdf - | head</code>
| Confirm OCR success
|}

IT REQUEST (OP-ERP-ITR) - EDITED 250801

2026-02-25T06:51:33Z

BabiSender: Created page with "= IT Request (OP-ERP-ITR) = ---- == 1. Objective == # To define the method how to create and process the IT Request. # To ensure every request is recorded in a systematic way for tracking and resolution. ---- == 2. Scope == IT Request is a process by which users within the organization seek assistance or services from the IT Department. === Standard Request === * Access (CCTV, Network, Files, Timelogs) * Admin Service === Complex Request === * Repair/Maintenance..."

= IT Request (OP-ERP-ITR) =

----

== 1. Objective ==

# To define the method how to create and process the IT Request.
# To ensure every request is recorded in a systematic way for tracking and resolution.

----

== 2. Scope ==

IT Request is a process by which users within the organization seek assistance or services from the IT Department.

=== Standard Request ===
* Access (CCTV, Network, Files, Timelogs)
* Admin Service

=== Complex Request ===
* Repair/Maintenance
* Training
* Product/Service Quote
* IT Equipment/Material (In house)

=== Others ===
For request types not listed above.

----

== 3. Definition ==

An ''IT Request'' is a formal submission made through the ERP system to seek assistance, service, or resources from the IT Department. It may include requests for technical support, system access, equipment repair or issuance, software installation, or resolution of IT-related issues. Each IT Request must contain sufficient details and, when necessary, supporting attachments to ensure proper review, categorization, and timely resolution.

----

== 4. References ==

* [https://drive.google.com/file/d/1WWkH9K52a8b-tUHBt844qa2qVQF072ep/view?usp=sharing ITR Procedure – Workflow (PDF)]

----

== 5. Responsibility ==

{| class="wikitable"
|-
! Role
! Responsibility
|-
| '''End User'''
| Submits the IT request through the ERP system, providing detailed information and any relevant attachments.
|-
| '''End User Manager'''
| Reviews and approves IT requests submitted by end users, ensuring that they are necessary and justified before submission.
|-
| '''IT Technical Support'''
| Reviews all IT requests and approves ''Standard requests''. Provides timely technical support for IT-related issues across the organization. Maintains regular communication with requestors, giving updates and ensuring resolution within the agreed timeframe. Escalates complex or unresolved requests to the IT Manager when needed.
|-
| '''IT Manager'''
| Approves ''Complex requests''. Provides guidance and support to IT Technical Support staff, especially in handling complex or escalated requests.
|-
| '''IT Director'''
| Approves ''Complex requests''. Addresses any escalated issues from the IT Manager that require executive decision-making. Reviews and analyzes feedback and performance metrics to drive continuous improvement in IT services.
|}

----

== 6. Procedure ==

=== A. Create IT Request ===

# Create IT Requests through the ERP system. Follow the step by step guide (ERP IT Request TM-ERP-05).
# Include detailed information about the issue or request, any relevant attachments, and the desired completion date.
#* ''Select/Type '''MIS – CSC''' in the '''Department Field''''':
#* ''Select/Type '''N/A – IT Request''' in the following fields'':
#** Customer
#** SO/JO
#** Address
# Use '''ASSIGNED TO – ASSIGN TO USER GROUP''':
#* Click the branch-specific IT Department to send them a notification.

=== B. Processing of Request ===

# The IT technical support staff will receive and evaluate the approved request. Executes the designated tasks and updates the status of requests.
# Requests requiring special authority or resources will be forwarded to the IT Manager for validation or escalated to the IT Director if it requires executive decision making.
# Because IT operates differently, the workflow status in ERPNext has specific meanings for IT Requests (ITRs). Workflow Approval does not apply to IT, so there is '''no need for Department approval'''.
# Instead, ''IT staff'' will regularly scan for ITRs with the status '''For Review'''.
#* When ''IT'' clicks '''Submit for Approval''', it signifies that the '''request has been received by the IT team'''.
#* Once the request is marked '''Approved''', it means the '''task is already ongoing'''.
#* At this stage, ''IT'' will also specify whether the request is a ''Standard'' or a ''Complex request'' and will provide an ''estimated time for completion''.
#* After completing the task, IT will write '''DONE''' in the comments section and tag the requestor to ''notify them of completion''.
#* In '''emergency situations''', requestors are advised to '''call IT first''' before creating a ticket.
#* To ensure this is easily maintained:
#** Filters are configured.
#** The assigned staff are told to check regularly.

=== C. Service Level ===

Requests should be fulfilled within '''3 days for standard requests''', and within '''30 to 45 days for complex/external dependency requests'''.

* '''Standard Request''' – Routine IT requests that can be handled entirely within the IT department. These are ''reviewed and approved by IT Staff''.
* '''Complex/External Dependency Requests''' – Requests that require input, approval, or action from other departments, which may impact the IT department's ability to meet the three-day closure target. These are ''reviewed by IT Staff'' and ''approved by the IT Manager or IT Director''.

==== Types of Requests ====

{| class="wikitable"
|-
! Type
! Examples
! SLA
|-
| '''Access''' (CCTV, Network, Files, Timelogs)
| —
| Within '''24 hours'''
|-
| '''Admin Service'''
| Password reset, Purchase Request, ERPNext and Desktop support
| Within '''24 hours'''
|-
| '''Repair/Maintenance'''
| Urgent: initial response within half a day. Item repairs follow Complex Request timeline.
| Half day (response); Complex timeline (repairs)
|-
| '''Training'''
| —
| Scheduled within '''24 hours'''; next available schedule within a Month of request accepted
|-
| '''Product/Service Quote'''
| —
| —
|-
| '''IT Equipment/Material (In house)'''
| —
| Response within '''half a day'''; issuance depends on availability
|-
| '''Problem Analysis'''
| —
| Scheduled within '''24 hours'''; task scheduled within '''2 weeks''' upon availability of End Users/Requestors
|}

=== D. Downloading ITR Reports ===

Report Filters:
* All ITR
* Period of Current Fiscal Year
* Add Column: ITR Type
* Time Difference (Prepared to Check) – Received
* Time Difference (Checked to Approved) – Ongoing
* Time Difference (Approved to Done) – Done

If targets are exceeded, proceed to Root Cause Analysis.

=== E. Collecting Feedback ===

# Conduct a survey to manage and understand requester expectations, enhancing overall satisfaction and driving continuous improvement.
# ''After fulfilling the request, send a survey link to the requestor.''
# '''IT Manager:''' Monitors survey results to ensure consistent and accurate data collection.
# '''IT Director:''' Reviews analysis results and identifies areas for improvement.

----

== 7. Documentation ==

All action request forms and related documentation should be archived systematically and retained for a '''minimum of 3 years'''.

The Google Form version of the IT Request System is replaced by this system.

----

== Document Control ==

{| class="wikitable"
|-
! Created by
! Reviewed by
! Approved by
!
|-
| Macy Milleza
| Emmilyn Requierme
| Avegail Mindanao
| Justin Aquino
|}

8D (Eight Discipline) Problem Solving Procedure

2026-02-25T06:50:59Z

BabiSender: Created page with "= 8D-OP-01: Eight Discipline (8D) Problem Solving Procedure = ''Revised for Clarity'' '''Document Control:''' 8D-OP-01 | Rev. 0 | Effective: 30-Oct-2017 | Prepared by: IMS | Approved by: Top Management [https://next.comfaccorp.com/s/MgENbcMPSZxmgRe CGG 8D Form Download] == 1. Objective == Establish a systematic, team-based approach for identifying, analyzing, correcting, and preventing problems or nonconformities in products, services, and processes. == 2. Scope ==..."

= 8D-OP-01: Eight Discipline (8D) Problem Solving Procedure =

''Revised for Clarity''

'''Document Control:''' 8D-OP-01 | Rev. 0 | Effective: 30-Oct-2017 | Prepared by: IMS | Approved by: Top Management

[https://next.comfaccorp.com/s/MgENbcMPSZxmgRe CGG 8D Form Download]

== 1. Objective ==

Establish a systematic, team-based approach for identifying, analyzing, correcting, and preventing problems or nonconformities in products, services, and processes.

== 2. Scope ==

Applies to all forms of nonconformity and complaints involving:

* Products and Services
* Fit-out category issues
* Installation work
* Customer Complaints
* Internal Complaints
* Audit findings (External and Internal)
* Any unmet target, objective, or procedural lapse

'''Note:''' Customer-requested changes to conforming products/services are '''not''' considered nonconformities.

== 3. Definitions ==

* '''Nonconformity:''' Deviation from agreed specifications or standards.
* '''Recurrence:''' Repetition of a problem due to misidentification of the root cause.
* '''PNC:''' Product Nonconformity
* '''IC:''' Internal Complaint
* '''CC:''' Customer Complaint
* '''Executive Summary:''' Summary of actions and results achieved through problem-solving.
* '''Discretion:''' IMS Team and Top Management determine if a problem warrants an 8D, based on impact and complexity.

== 4. References ==

* Process Control Charts
* Production Work Instructions
* CNCP-F01: Delivery Nonconformance Report
* CNCP-F02: Customer Complaint / Product Nonconformity Report
* CNCP-F03: Complaints / Nonconformity Action Log
* CA-OP-01: Corrective Action Procedure
* CF-OP-01: Handling Customer Complaints

== 5. Responsibilities ==

{| class="wikitable"
! Role !! Responsibility
|-
| '''Top Management / Directors''' || Monitor complaint resolution and intervene if closure is delayed.
|-
| '''All Departments''' || May raise issues using the 8D form or monitoring sheet.
|-
| '''Department Head / Supervisor''' || Default '''Team Leader'''.
|-
| '''Department Manager''' || Default '''Team Champion'''.
|-
| '''IMS Team''' || Assigns 8D teams, ensures process compliance, and maintains monitoring.
|-
| '''8D Team''' || Performs analysis, implements corrective/preventive actions, and reports results.
|-
| '''Management Representative (MR)''' || Reviews and approves the final report.
|}

== 6. Procedure ==

=== 6.1 Completing the 8D Form ===

{| class="wikitable"
! Discipline !! Description
|-
| '''D0 – Problem Awareness & Preparation''' || Identify issue, assign CAPA number, define ownership, and document references (e.g., SO, JO, ARF, NCR, CC, IC). Include details such as area, quantity, date/time, and short description.
|-
| '''D1 – Problem Description''' || Describe the issue using '''5W+2H''' (What, When, Where, Who, Why, How Many, How Much). Attach visuals (photos, flowcharts).
|-
| '''D2 – Team Formation''' || MR designates a cross-functional team to gather and analyze data.
|-
| '''D3 – Containment Actions''' || Define immediate steps to control impact and prevent escalation.
|-
| '''D4 – Root Cause Analysis''' || Identify '''Problem Cause''' (why it occurred) and '''Escape Cause''' (why it wasn't detected).
|-
| '''D5 – Corrective Actions''' || Define and verify short-term corrective actions.
|-
| '''D6 – Implementation & Validation''' || Execute and validate actions using measurable data (e.g., reduced defects, increased yield, zero recurrence).
|-
| '''D7 – Preventive Actions''' || Update processes, FMEA, risk analysis, or parameters to prevent recurrence.
|-
| '''D8 – Closure & Recognition''' || Summarize findings and results. Submit to Top Management for review and recognition of team efforts.
|}

=== 6.2 General Procedures ===

==== A. Customer Complaint Handling ====

* Applies to post-handover issues not covered in punch lists.
* Reporter completes D0 and D1, then submits to IMS.
* IMS assigns a team and sends the file for completion.
* Team has '''1 week''' to complete the 8D report, including corrective and preventive actions.
* Unresolved reports after 1 week may be subject to disciplinary review (with due process).

==== B. Internal Complaints (within CSC) ====

* '''8D Required:''' For major incidents (e.g., line stoppage, reworks, repeated PNCs, or issues requiring >0.5 man-day effort).
* '''No 8D Needed:''' Minor issues logged in the complaint master list; still require root cause and corrective actions.

==== C. Performance Review ====

* IMS issues a '''Monthly 8D Performance Report''' to Top Management summarizing open, closed, and overdue actions.

== 7. Documentation ==

# Completed 8D Reports (with attachments) must be archived by SSD for '''3 years'''.
# '''Document Numbering Format:'''
#: <code>YY-MM-CSC-[Code]-####</code>
#* Year (e.g., 17 → 2017)
#* Month (e.g., 09 → September)
#* CSC Site (P: Plant, M: Makati, C: Calbayog)
#* Type (CC: Customer Complaint, IC: Internal Complaint, etc.)
#* Series (0001…)

== 8. Clarity Improvements ==

* Simplified and unified terminology (removed redundancy and old phrasing).
* Clarified responsibility roles (Champion vs. Leader distinction).
* Added structured tables for readability.
* Aligned formatting for consistency with current Comfac-iT QMS style.
* Updated example numbering format for clarity.

[[Category:QMS]]
[[Category:Procedures]]
[[Category:IMS]]
[[Category:Comfac]]

Procedure: CC-Blast Data Breach Prevention

2026-02-25T06:50:29Z

BabiSender: Created page with "= Procedure: CC-Blast Data Breach Prevention = == Overview == A '''CC-Blast Data Breach''' occurs when someone mistakenly uses the '''CC (Carbon Copy)''' field instead of '''BCC (Blind Carbon Copy)''' when sending emails to multiple recipients. This exposes the personal email addresses of all recipients to each other. This is considered a '''personal data breach''' under the '''Data Privacy Act of 2012''' and must be handled with urgency, professionalism, and complian..."

= Procedure: CC-Blast Data Breach Prevention =

== Overview ==

A '''CC-Blast Data Breach''' occurs when someone mistakenly uses the '''CC (Carbon Copy)''' field instead of '''BCC (Blind Carbon Copy)''' when sending emails to multiple recipients. This exposes the personal email addresses of all recipients to each other.

This is considered a '''personal data breach''' under the '''Data Privacy Act of 2012''' and must be handled with urgency, professionalism, and compliance with the organization's Privacy Manual.

== Key Terms and Definitions ==

* '''CC Blast''' – Accidentally exposing multiple recipients' email addresses by placing them in the CC or To field instead of BCC.
* '''BCC Blast''' – Correctly sending a bulk email using the BCC field, which hides all recipient email addresses.
* '''Reply Storm (Reply-All Storm)''' – When recipients start replying-all in a CC blast chain, causing an uncontrollable cascade of unnecessary or sensitive emails to all parties.
* '''Clawback Limitation''' – Once personal emails are exposed in a CC blast, they cannot be taken back; the data has already been leaked.

== Precautionary Measures ==

# '''Always Check Before Sending:''' When emailing multiple external contacts (students, clients, partners, etc.), '''use BCC instead of CC'''.
# '''Tagging Personal Emails:''' Configure email systems to '''alert or warn''' when sending to recipients tagged as personal email domains (e.g., Gmail, Yahoo, Hotmail). Business/work accounts should be tagged separately.
# '''Use Templates:''' Provide standardized email templates for OJTs, interns, and staff with the '''BCC field pre-configured'''.
# '''Two-Person Verification:''' For mass external communications, have another team member verify that recipients are properly placed in the BCC field before sending.

== Response Procedure (If a CC-Blast Data Breach Happens) ==

# '''Do Not Reply-All:''' Immediately stop and '''avoid adding to the breach'''.
# '''Send a BCC Notification:''' Draft a short apology and clarification email to all recipients, but '''send it via BCC''' to prevent further exposure. Include instructions to avoid replying to the group email.
# '''Notify Management:''' Escalate the incident to the '''Privacy Officer''' and '''Data Protection Officer (DPO)'''.
# '''Mandatory Reporting:''' Evaluate the incident. If it meets reporting criteria, '''notify the National Privacy Commission (NPC)''' within the prescribed timeframe.
# '''Document the Incident:''' Record the event details (number of recipients, exposed emails, response actions, corrective measures) in the '''Privacy Incident Register'''.

== Accountability and Training ==

* '''Staff and OJTs''' must undergo periodic reminders and training distinguishing '''CC vs. BCC usage'''.
* '''Supervisors''' must enforce the policy: ''"External personal emails = BCC only."''
* '''IT/Admin''' should deploy or configure systems that:
** Alert when sending to large groups of external addresses.
** Warn or block when multiple personal emails are detected in the CC field.
** Suggest converting CCs to BCCs automatically when thresholds are exceeded.

== Conclusion ==

A CC-blast is a preventable human error that exposes personal data and risks compliance violations. Once it occurs, '''the exposure cannot be undone''', but '''swift containment using BCC communication and incident reporting''' can reduce further harm. The long-term solution lies in a '''combination of staff awareness, training, and technical safeguards'''.

[[Category:Security]]
[[Category:Data Privacy]]
[[Category:Procedures]]
[[Category:Comfac]]

Using Frappe Wiki

2026-02-25T06:49:43Z

BabiSender: Created page with "= Using Frappe Wiki = == 1. Installation == === A. Frappe Cloud Installation === # Go to your '''Dashboard'''. # Choose '''Go to Site''' or '''Go to Server'''. '''If Site:''' * Select the site. * Go to '''Apps'''. * Click '''Install App'''. * Select '''Wiki'''. '''If Server:''' * Go to '''Application Server'''. * Click '''Install App'''. * Select '''Wiki'''. === B. Self-Hosted Installation === '''If Docker-based setup:''' * Ensure persistence using '''drive volume..."

Main Page

2026-02-25T06:48:08Z

BabiSender:

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting Started ==
# [[Mediawiki Setting Up Guide]]
# [[Mediawiki Additional Configuration]]
# [[ERPNext Webshop Setup Guide]]
# [[Manufacturing v16 260125]]
# [[ERpnext Asset Management Procedure 260113 ]]
# [[260108 CGG- GitHub Administration Guide ]]
# [[ERPNext HR Module Outline ]]
# [[Controller Systems 251213-01 ]]
# [[Power Distribution Tree 251213 ]]
# [[Home ]]
# [[Standard Operating Procedure: Distributed Minute Taking & Task Ownership 251208 ]]
# [[OpenWebUI - 251128-justin ]]
# [[Comfac ERPNext Strategy Canvas (Expanded) ]]
# [[IT Purchase Requests 241126 ]]
# [[TrueNAS Business Plan: Project 251212 ]]
# [[ERPNEXT Payroll POC 251212 ]]
# [[Offline Malware Remediation & Data Recovery ]]
# [[TrueNAS Configuration Options & Scale Options 251130 ]]
# [[SOP: Network Troubleshooting & pfSense Monitoring 251130 ]]
# [[System Hardening Strategy: Win2Lin Migration & Infrastructure 251129 ]]
# [[IT IMPORTS PROCESSES ]]
# [[Skills and Competencies for IT Staff Trained in pfSense ]]
# [[pfSense Sales Training Material ]]
# [[Industrial Controllers and Water Utilities 251011 ]]
# [[Comfac Sales Knowledge Base ]]
# [[🌐 WordPress Website — *You Own Everything, Learn Everything* ]]
# [[Business Continuity ]]
# [[Using Frappe Wiki ]]
# [[Procedure: CC-Blast Data Breach Prevention ]]
# [[8D (Eight Discipline) Problem Solving Procedure ]]
# [[IT REQUEST (OP-ERP-ITR) - EDITED 250801 ]]
# [[Steps to Repair and OCR a Scanned or Corrupted PDF in Ubuntu ]]
# [[pfSense Sales Training Material ]]
# [[Projects in Process Report 251023 ]]
# [[SALES INVOICE TAX OUTPUT 250829 ]]
# [[2026 MIS IT KRA KPI Biz Plan ]]
# [[Tplink Mikrotik Equivalent ]]
# [[Google Drive and Shared Drive Training ]]
# [[Mailcow SOGo: Creating Filters for Events, Approvals, and Organizational Emails ]]
# [[Comparison: TrueNAS Mini X+ vs Dell Precision 3680 Tower (2025) ]]
# [[ERPNext Webshop Setup and Publishing Process ]]
# [[Excel Description Filler Tool 📝 ]]
# [[Biz Analysis Methodology 251109 ]]
# [[Biz Analysis Methodology 251109 ]]
# [[Comfac CRM – Customer Qualification & Conversion Process ]]
# [[Comfac GPU Scaling and AI Research Goals ]]
# [[Backblaze Drive Stats for Server and Storage Qualification ]]
# [[🧠 Process: Selecting and Installing the Right Ollama Model for Your Hardware ]]
# [[Partner Reseller Pricing 251109 ]]
# [[LibreOffice / Nextcloud Office – "Due Tasks" Conditional Formatting ]]
# [[pfSense CE → pfSense Plus Upgrade Guide ]]
# [[Introduction: Why Self-Host Your Email? ]]
# [[Spoof Timezone Extension – Setup Guide for Comfac Staff ]]
# [[Mailcow + Thunderbird Setup Guide (Email + Calendar) ]]
# [[Viber Focus-Stealing ]]
# [[Modern Guide: pfSense Captive Portal with FreeRADIUS & ACME ]]
# [[Frappe Links and References ]]

== For Users Only ==
* [[Private:Private Ngani]]

== Need Help? ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]