<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Yize</title>
    <description>The latest articles on DEV Community by Yize (@yize).</description>
    <link>https://dev.to/yize</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4202417%2F63db8e21-658b-44d8-bb91-7d15d5cc4f44.png</url>
      <title>DEV Community: Yize</title>
      <link>https://dev.to/yize</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yize"/>
    <language>en</language>
    <item>
      <title>[Boost]</title>
      <dc:creator>Yize</dc:creator>
      <pubDate>Tue, 17 Nov 2026 09:55:43 +0000</pubDate>
      <link>https://dev.to/yize/-a61</link>
      <guid>https://dev.to/yize/-a61</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/yize/the-hard-part-of-a-bazi-calculator-isnt-the-astrology-its-the-time-zones-3fho" class="crayons-story__hidden-navigation-link"&gt;The hard part of a BaZi calculator isn't the astrology - it's the time zones&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/yize" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4202417%2F63db8e21-658b-44d8-bb91-7d15d5cc4f44.png" alt="yize profile" class="crayons-avatar__image" width="800" height="533"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/yize" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Yize
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Yize
                
                
              
              &lt;div id="story-author-preview-content-5056123" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/yize" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4202417%2F63db8e21-658b-44d8-bb91-7d15d5cc4f44.png" class="crayons-avatar__image" alt="" width="800" height="533"&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Yize&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/yize/the-hard-part-of-a-bazi-calculator-isnt-the-astrology-its-the-time-zones-3fho" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Nov 17&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/yize/the-hard-part-of-a-bazi-calculator-isnt-the-astrology-its-the-time-zones-3fho" id="article-link-5056123"&gt;
          The hard part of a BaZi calculator isn't the astrology - it's the time zones
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/backend"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;backend&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/programming"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;programming&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/softwaredevelopment"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;softwaredevelopment&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
            &lt;a href="https://dev.to/yize/the-hard-part-of-a-bazi-calculator-isnt-the-astrology-its-the-time-zones-3fho#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            4 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;


</description>
      <category>programming</category>
      <category>softwaredevelopment</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>The hard part of a BaZi calculator isn't the astrology - it's the time zones</title>
      <dc:creator>Yize</dc:creator>
      <pubDate>Tue, 17 Nov 2026 09:53:50 +0000</pubDate>
      <link>https://dev.to/yize/the-hard-part-of-a-bazi-calculator-isnt-the-astrology-its-the-time-zones-3fho</link>
      <guid>https://dev.to/yize/the-hard-part-of-a-bazi-calculator-isnt-the-astrology-its-the-time-zones-3fho</guid>
      <description>&lt;p&gt;When I started building a BaZi (Four Pillars) calculator, I assumed the hard part would be the astrology — the rules, the terminology, the interpretation. The rules turned out to be a lookup table. The hard part was that every birth record in the world gives you a time that isn't the time the calculation actually needs.&lt;/p&gt;

&lt;p&gt;Here are the five traps, roughly in the order they bit me.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. IANA time zones are city-based. Birthplaces are not.
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;Asia/Shanghai&lt;/code&gt; has been a flat &lt;code&gt;+08:00&lt;/code&gt; since 1901. That's true for the zone. It is not true for a birthplace.&lt;/p&gt;

&lt;p&gt;China spans about 60 degrees of longitude and uses a single zone. Standard time is defined at 120°E. Chengdu sits at 104.07°E:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;(104.07 - 120) × 4 minutes per degree ≈ -64 minutes
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Local mean time in Chengdu runs roughly &lt;strong&gt;64 minutes behind&lt;/strong&gt; the clock on the wall. Use the zone offset naively and the hour pillar can land in the wrong two-hour branch.&lt;/p&gt;

&lt;p&gt;The general rule is one degree of longitude equals four minutes of time, and IANA will never tell you that.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Mean solar time is not solar time
&lt;/h2&gt;

&lt;p&gt;Fixing longitude gets you local mean time. The sun does not run on mean time. Earth's orbit is elliptical and its axis is tilted, so apparent solar time drifts from mean solar time across the year by up to about ±16 minutes — the equation of time.&lt;/p&gt;

&lt;p&gt;If a day-branch boundary falls a few minutes from midnight, that drift is enough to flip the day.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;true solar time = civil time
                + (longitude - standard meridian) × 4 min
                + equation of time
                + historical DST offset
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Historical offsets are not what you think
&lt;/h2&gt;

&lt;p&gt;Modern zone data is orderly. Historical data is not:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;China observed DST from 1986 to 1991.&lt;/li&gt;
&lt;li&gt;Wartime and occupation periods shifted offsets by an hour or more.&lt;/li&gt;
&lt;li&gt;Some regions changed their standard meridian outright.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a 1988 birth in Shanghai, the IANA row is a starting point, not an answer. You have to ask what offset was actually in force that day, and be honest when the answer is "we are not certain".&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Correcting the time can move the date
&lt;/h2&gt;

&lt;p&gt;This is the subtle one. Apply a correction near midnight and the resulting solar time belongs to the previous or next day. That changes the day pillar, which changes everything downstream.&lt;/p&gt;

&lt;p&gt;An implementation that treats the correction as "adjust the clock" instead of "produce a new instant plus a date-shift flag" will silently produce wrong charts. The output has to say &lt;em&gt;this rolled over&lt;/em&gt;, not just hand back a formatted string.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Calendar months are not solar months
&lt;/h2&gt;

&lt;p&gt;Year and month pillars don't start on January 1 or on the first of any month. The year begins at 立春 (Lichun), and month boundaries are the 节 solar terms — each of which happens at a specific instant, not on a date. A birth on the calendar day of a term boundary can belong to either month depending on the hour.&lt;/p&gt;

&lt;p&gt;Solar terms are astronomical events. You need ephemeris-backed calculation, not a hardcoded date table.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for the design
&lt;/h2&gt;

&lt;p&gt;The mistake I made first, and the one I'd warn anyone about: collapsing all corrections into a single offset. Once you return one number, nobody downstream can tell whether a strange result came from longitude, from the equation of time, or from a DST rule.&lt;/p&gt;

&lt;p&gt;So return the components:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"civilTime"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"1990-05-20T14:30:00+08:00"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"utc"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"1990-05-20T06:30:00Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"trueSolarTime"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"1990-05-20T13:29:46"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"longitudeCorrectionMinutes"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;-63.73&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"equationOfTimeMinutes"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;3.5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"daylightSavingMinutes"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"dateShift"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"warnings"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"engineVersion"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"..."&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three properties I'd keep in any version of this:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Separate the components.&lt;/strong&gt; A single &lt;code&gt;offsetMinutes&lt;/code&gt; is a debugging dead end.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Flag the boundaries.&lt;/strong&gt; If the corrected time lands within a few minutes of midnight, or within a few hours of a solar term, say so. A confident wrong answer is worse than a hedged right one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Version the engine.&lt;/strong&gt; The rules have schools and conventions — treating 23:00 as the start of the next day instead of midnight is one such choice. When results change, callers need to know which engine produced them.&lt;/p&gt;

&lt;p&gt;None of this is specific to BaZi. It applies to anything that starts from "a date, a time, and a place" — genealogy, astronomy, anything touching pre-1970 records in a country that changed its clocks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where I landed
&lt;/h2&gt;

&lt;p&gt;I ended up splitting the time normalization out as standalone, read-only MCP servers, because re-implementing it per project was getting silly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;calculate_true_solar_time&lt;/code&gt; — civil time, IANA zone, and longitude in; UTC, true solar time, and each correction component out&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;calculate_four_pillars&lt;/code&gt; — the same inputs, plus solar-term boundaries, out as year/month/day/hour pillars&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Both are MIT, with no geocoding, no stored birth data, and no LLM anywhere in the calculation path:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/cdaily1995-create/true-solar-time-mcp" rel="noopener noreferrer"&gt;https://github.com/cdaily1995-create/true-solar-time-mcp&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/cdaily1995-create/four-pillars-mcp" rel="noopener noreferrer"&gt;https://github.com/cdaily1995-create/four-pillars-mcp&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Disclosure, since this is my own work: I also run the calculator these came from, and you can see the output on a real chart at &lt;a href="https://bazi-calculator.co/" rel="noopener noreferrer"&gt;https://bazi-calculator.co/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you've hit this class of bug in another domain, I'd like to hear how you handled it — especially the "this local time never existed" case around DST transitions, which is still the part I trust least.&lt;/p&gt;

</description>
      <category>backend</category>
      <category>programming</category>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>I Brought AI Into My Family's Steel Fabrication Business, Starting With One RFQ Email</title>
      <dc:creator>Yize</dc:creator>
      <pubDate>Mon, 26 Oct 2026 10:53:59 +0000</pubDate>
      <link>https://dev.to/yize/i-brought-ai-into-my-familys-steel-fabrication-business-starting-with-one-rfq-email-48bb</link>
      <guid>https://dev.to/yize/i-brought-ai-into-my-familys-steel-fabrication-business-starting-with-one-rfq-email-48bb</guid>
      <description>&lt;p&gt;I work in the internet and AI industry, and my family happens to run a steel fabrication business.&lt;/p&gt;

&lt;p&gt;After spending a lot of time with AI, automation, and content systems, I kept wondering what these technologies could solve inside a traditional factory.&lt;/p&gt;

&lt;p&gt;Our business provides structural steel detailing, fabrication, and overseas delivery services. Internationally, we operate under the &lt;a href="https://www.findingsteel.com/" rel="noopener noreferrer"&gt;FindingSteel&lt;/a&gt; brand, with more information available on our &lt;a href="https://www.findingsteel.com/en/services/" rel="noopener noreferrer"&gt;structural steel fabrication and delivery services&lt;/a&gt; page.&lt;/p&gt;

&lt;p&gt;I initially saw many possible applications. AI could help process RFQs, organize business knowledge, improve website content, and support Generative Engine Optimization (GEO).&lt;/p&gt;

&lt;p&gt;Once I looked closely at the actual workflow, all of those ideas led back to the same problem.&lt;/p&gt;

&lt;p&gt;The factory already had a large amount of data and experience. Drawings, quotations, material standards, equipment specifications, project records, and customer conversations were created every day. They were scattered across email, chat histories, shared folders, and the experience of individual employees.&lt;/p&gt;

&lt;p&gt;There was plenty of information, but very little of it could be accessed consistently or handed directly to an AI system.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens after an RFQ reaches the factory
&lt;/h2&gt;

&lt;p&gt;An overseas RFQ arrives at a steel fabrication company. The attachments include CAD drawings, a PDF specification, and an incomplete bill of quantities.&lt;/p&gt;

&lt;p&gt;The customer wants a quote quickly, but the material standard, surface treatment, destination port, installation scope, and delivery schedule are not fully specified.&lt;/p&gt;

&lt;p&gt;Sales reviews the files and forwards them to engineering. Engineering identifies missing details and sends a list of questions back to sales. Sales contacts the customer again. When the additional information arrives, procurement, detailing, and production still need to review it separately.&lt;/p&gt;

&lt;p&gt;The files move between email, chat, and shared folders. The RFQ is eventually processed, but the reasoning behind the decisions rarely enters a reusable system.&lt;/p&gt;

&lt;p&gt;Steel projects are difficult to standardize completely. The same type of member may be produced under different standards, material grades, connection methods, corrosion-protection systems, inspection requirements, and delivery boundaries.&lt;/p&gt;

&lt;p&gt;Important knowledge is distributed across different roles. Sales knows the customer and previous quotations. Engineers understand risks hidden in the drawings. Production teams know the limitations of equipment and processes. Project managers know which details usually create problems on site.&lt;/p&gt;

&lt;p&gt;By the time information reaches the website team, it has often been summarized several times. What remains is usually a list of capacity figures, equipment, certifications, and project names.&lt;/p&gt;

&lt;p&gt;This information structure affects both internal efficiency and customer acquisition.&lt;/p&gt;

&lt;p&gt;An internal AI system can read an old quotation, but it does not know whether the price is still valid. It can extract an equipment specification from an old page, but it may not know whether that number describes axis positioning, a cutting process, or the tolerance of a finished component.&lt;/p&gt;

&lt;p&gt;Customers using AI to search for suppliers face the same gap. If a company website only says “experienced” and “high quality,” an AI system has little evidence for answering specific procurement questions.&lt;/p&gt;

&lt;p&gt;It needs to know what the company can deliver, which projects the capability applies to, what information the customer must provide, and which commitments still depend on contract and project conditions.&lt;/p&gt;

&lt;p&gt;AI can find relevant text. It cannot decide which business fact is approved for use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give every business fact a status
&lt;/h2&gt;

&lt;p&gt;Many companies build a knowledge base by importing PDFs, web pages, and internal documents in one batch. The document count increases, but conflicting statements enter the system at the same time.&lt;/p&gt;

&lt;p&gt;I believe the first step should be a business fact registry. Each fact should record at least six fields.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Field&lt;/th&gt;
&lt;th&gt;Question it answers&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Claim&lt;/td&gt;
&lt;td&gt;What does the company want to communicate?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scope&lt;/td&gt;
&lt;td&gt;Which company, equipment, process, or project does it apply to?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Status&lt;/td&gt;
&lt;td&gt;Is it approved, unverified, contradicted, or retired?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Evidence&lt;/td&gt;
&lt;td&gt;Where is the contract, certificate, equipment record, or inspection report?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Owner&lt;/td&gt;
&lt;td&gt;Who can confirm and update it?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reviewed at&lt;/td&gt;
&lt;td&gt;When was it last checked?&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;“Designed annual capacity of 40,000 tons” and “40,000 tons delivered in a specific year” are different claims. Equipment axis-positioning accuracy and finished-component tolerance should not be treated as the same measurement either.&lt;/p&gt;

&lt;p&gt;The fact registry needs to preserve these boundaries. Content systems, RAG pipelines, and automation workflows should only use approved versions.&lt;/p&gt;

&lt;p&gt;This step sounds basic, but it determines whether the rest of the AI system can operate safely. The more documents a company has, the greater the risk of reusing an incorrect statement.&lt;/p&gt;

&lt;p&gt;Once an unverified fact enters automated writing, translation, and multi-channel publishing, it can quickly appear in several languages and on multiple external platforms.&lt;/p&gt;

&lt;h2&gt;
  
  
  Automate the information handoff first
&lt;/h2&gt;

&lt;p&gt;A steel fabrication company should not let AI complete quotations independently at this stage. Material prices, project risks, detailing effort, transport conditions, and installation scope still require professional judgment.&lt;/p&gt;

&lt;p&gt;The RFQ workflow already contains many tasks that are suitable for automation.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Receive the RFQ email and attachments
→ Identify drawings, bills of quantities, and technical specifications
→ Extract materials, sizes, quantities, standards, surface treatment, and destination
→ Compare the request with an RFQ checklist
→ Generate questions for missing information
→ Route the request to sales and engineering
→ Review scope, risks, and quotation conditions manually
→ Draft a response and save the processing record
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;AI handles extraction, classification, comparison, and drafting. Sales and engineering remain responsible for judgment and commitments.&lt;/p&gt;

&lt;p&gt;The system can begin by converting an RFQ into a structured record.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"project_type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"industrial_warehouse"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"material_standard"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;null&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"surface_treatment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"hot_dip_galvanizing"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"destination_port"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Lagos"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"installation_scope"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"unclear"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"missing_information"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="s2"&gt;"material_standard"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="s2"&gt;"installation_scope"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="s2"&gt;"required_delivery_date"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"review_status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"engineering_review_required"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The value of this record goes beyond saving data-entry time. It gives the company a way to measure which information is most often missing, which questions repeatedly consume engineering time, and which project types create misunderstandings around quotation and delivery boundaries.&lt;/p&gt;

&lt;p&gt;Those findings can improve RFQ forms, sales communication, and internal review checklists.&lt;/p&gt;

&lt;p&gt;My current view of AI transformation in traditional manufacturing is fairly conservative. The first goal is to let AI turn scattered material into inputs that people can review quickly, then preserve the corrections and decisions made by those people.&lt;/p&gt;

&lt;p&gt;Once this workflow is stable, the company can move on to project handoffs, quality documentation, export paperwork, website content, and GEO. A faster system built on unreliable information will only repeat old errors faster.&lt;/p&gt;

&lt;p&gt;I would love to hear from developers, manufacturers, and operators working on similar problems. If you are experimenting with AI in manufacturing, RAG pipelines, workflow automation, or GEO, feel free to share your approach, lessons, or disagreements in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>manufacturing</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
