Cleanroom, hook-up, tool install

    Commissioning software for fabs where tool install depends on twelve facility systems.

    A fab is a facility project and a tool installation programme running at the same time. Deskely tracks cleanroom, ultrapure water, bulk and specialty gases, exhaust, chilled water and power as subsystems, and every tool hook-up as an asset that depends on them.

    Facility
    UPW, gases, exhaust, power
    Unit
    Tool and hook-up
    Constraint
    Cleanroom protocol
    Gate
    Tool release to process
    FAB 1 — BAY 14HOOK-UP SET · REV 4FAB 1 — BAY 14ETCH-03LITHO-07CVD-11SUB-FAB — FACILITY SERVICESUPWCDA / VACSPECIALTY GASEXHAUSTABATEMENTTOOL LITHO-07 — HOOK-UPSG-SIH4-03 purity pendingTAG REGISTERLITHO-07Lithography toolRecords signedUPW-B14UPW branch, bay 14In testSG-SIH4-03Silane supply linePreservationEX-ACID-11Acid exhaust branchPunch open310 toolsunder one system hierarchy

    The problem

    Tool install waits on facilities, and nobody agrees on which ones.

    Each tool needs a specific combination of bulk and specialty gases, UPW, exhaust and abatement, chilled water, vacuum and power. The facility contractor knows its systems; the tool vendor knows its tool; nobody holds the intersection until hook-up day.

    The result is tools delivered into a bay that cannot yet support them, and hook-up crews standing idle.

    Deskely holds tool-level utility dependencies against facility subsystems, so bay readiness is a query rather than a meeting.

    NOBODY HOLDS THE INTERSECTIONTool install vs facility systemsEach tool needs a specific combination of gases, water, exhaust and powerTool vendorknows the toolFacility contractorknows the systemsgapTOOL DEPENDENCIES vs FACILITY READINESSUPW supply — Bay 4bay readySpecialty gas — silane linebay not readyProcess exhaust and abatementbay readyVacuum and chilled waterbay not readyTOOLS DELIVERED INTO A BAY THAT CANNOT SUPPORT THEM2 of 4dependencies unresolved at deliveryBay readiness, a query not a meetingDeskely holds tool-level utility dependencies against facility subsystems.

    Setting up the register

    Facility systems and tools live in the same register.

    Ultrapure water, bulk gases, specialty gases, exhaust and abatement, process cooling, vacuum and power are subsystems with their own record sets and completion paths.

    Tools are assets with hook-up scopes beneath them: connections, interlocks, monitoring and safety devices, each tagged and tested.

    Drawings and schedules are parsed into that structure so no one maintains parallel lists.

    1 · SOURCE DOCUMENTSFacility P&IDs rev 462 sheetsTool list and hook-up sc…310 toolsSpecialty gas schedule48 linesExhaust and abatement li…180 branchesPARSE + MATCHtag · description · drawing ref2 · ONE TAG REGISTERLITHO-07Lithography toolBAY 14UPW-B14UPW branch, bay 14FACILITYSG-SIH4-03Silane supply lineSPECIALTY GASEX-ACID-11Acid exhaust branchEXHAUSTTWO DOCUMENTS DISAGREEFacility P&IDs re…Silane supply lineTool list and hoo…Abbreviated descriptionEngineer picks the sourcedecision loggedWeeks of transcription become a draft an engineer reviews.

    Execution

    Hook-up and verification recorded under cleanroom protocol.

    Field capture on tablets suits gowned work far better than paper: forms are completed at the tool, with photos and measured values where they matter.

    Leak checks, purity results, interlock tests and safety verifications are held against the tool and its connections.

    Punch is categorised by whether it blocks tool release, so the hook-up queue is prioritised by consequence.

    HOOK-UP TO TOOL RELEASETool ETCH-14, Bay 4Facility subsystem availabilitySigned offHook-up — connections, interlocksSigned offLeak, purity and interlock verificationIn progressPunch categorised by release impactAwaiting predecessorTool released to processAwaiting predecessor2 of 5release steps cleared for this tool0tools released with an open interlock testA tool is released to process only when its facility dependencies are signed.

    Tool release

    A tool is released to process when its dependencies are signed.

    Release depends on facility subsystems being available and the hook-up record set being complete, both enforced from the data.

    The evidence pack per tool goes to the process organisation with the installation history intact.

    That pack is also what supports later moves, upgrades and requalification.

    LITHO-07 — release ladderHook-up gated on facility subsystemsSETTool set and levelIssued 03 NovPlacement and levellingin toleranceSeismic anchoragesignedHUHook-up completeBlocked — gas lineUPW, CDA, vacuumconnected and testedSpecialty gas SG-SIH4-03purity pendingRELTool release to processBlocked — hook-upInterlock testingnot signedBlocking punch3 open

    Particle and contamination control

    A tool can be mechanically and electrically complete and still fail release because the bay cannot hold its particle count.

    Fab acceptance carries a test category that has no equivalent on a conventional production line: airborne particle counts have to be demonstrated at the tool footprint under as-built, as-occupied conditions, and a single non-conformance can trace back to a sealant, a filter, or a gowning breach months after the tool was mechanically signed off.

    UPW resistivity, TOC and particle count, and specialty gas purity, all have to be proven at the point of use — at the tool's own connection — not just at the distribution header, because a clean header feeding a contaminated drop line is functionally no different to no UPW system at all.

    Deskely holds particle count results, UPW point-of-use verification and specialty gas purity records against the specific tool connection they qualify, alongside the mechanical hook-up records, so a release decision is made against the full contamination-control picture rather than the mechanical checklist alone.

    TOOL-TO-FACILITY DEPENDENCY MAPTool ETCH-14, Bay 4FACILITY SUBSYSTEMS THIS TOOL REQUIRESUltrapure water, Bay 4 branchavailableSpecialty gas — silane linenot readyProcess exhaust and abatementavailableVacuum and chilled wateravailableBay readiness is a query against these subsystems, not a coordination meeting.HOOK-UP EVIDENCE, GOWNED CAPTURELeak check, all process connectionsPurity result, gas delivery lineInterlock test, EMO and gas cabinetPunch categorised by release impact3 of 4facility subsystems ready, ETCH-141dependency holding tool releaseRelease depends on the data, not a walk-down of the bay.

    How it runs

    From base build to tools running process.

    Fab schedules are dominated by dependency management, which is exactly what a structured register is for.

    1. 01

      Model facility subsystems

      UPW, bulk and specialty gases, exhaust, process cooling, vacuum and power as separate paths.

    2. 02

      Register tools and hook-ups

      Each tool tagged with its connections, interlocks, monitoring and safety devices.

    3. 03

      Map utility dependencies

      Tool-level prerequisites recorded against facility subsystems to make bay readiness explicit.

    4. 04

      Execute gowned on tablet

      Hook-up, leak, purity and interlock checks captured at the tool under cleanroom protocol.

    5. 05

      Categorise punch by release

      Items marked as blocking tool release or not, with owners and dates.

    6. 06

      Release tools with evidence

      Release certificates issued from signed records, with a per-tool pack handed to process.

    FAQ

    Questions about Semiconductor fabs scopes.

    Ready to digitize
    commissioning and
    handover?

    We use cookies to improve your experience.
    You can opt out of certain cookies.
    Find out more in our privacy policy.