Retrofits, tie-ins, line moves

    Commissioning software for work inside a plant that has to keep producing.

    Retrofits, line moves and capacity upgrades happen in short windows inside a live plant. Deskely gives the window a defined record set, live readiness and punch that is owned before restart, so production is not the thing that discovers the gaps.

    Setting
    Live production plant
    Window
    Days, not months
    Risk
    Restart on time
    Scope
    Retrofit, move, upgrade
    PLANT 2 — LINE 5 RETROFITWINDOW RECORD SET · REV 1LINE 5 — RETAINEDRETAINEDSHUTDOWN WINDOW — 14 DAYSST-03ST-04ST-05T3-CAI-04Tie-in group T-3RESTART GATED ON SIGNED SAFETY AND INTERLOCK TESTSTAG REGISTERL5-ST03-NEWNew station 03Records signedT3-CAI-04Compressed air tie-inIn testL5-PNL-02Modified control panelPreservationT3-PWR-01Power feeder tie-inPunch open180 assetsunder one system hierarchy

    The problem

    The window is short and the plant is waiting to restart.

    A line relocation or retrofit gets a fixed shutdown window with a hard restart deadline set against production schedule. Everything not finished inside it — a tie-in weld, a re-terminated cable, a recommissioned safety interlock — either delays restart or gets waved through and becomes a reliability problem within the first week back in production.

    Because the scope is smaller than a greenfield project, it usually gets no structure at all — a checklist and a WhatsApp group.

    Deskely gives the window the same evidence model as a large project at a scale that fits, so restart is a decision made against records.

    THE WINDOW IS SHORT, PRODUCTION IS WAITINGRetrofit inside a live plantA checklist and a WhatsApp group is the usual structure for a scope this sizeDay 1Day 2Day 3Day 4Day 5Shutdown window — fixed, non-negotiableWHAT THE WINDOW ACTUALLY DELIVERSConveyor section relocated and alignedsignedNew drive tied into existing control panelsignedSafety interlock re-validationopen at restartUtility tie-in leak testopen at restart2 itemswaved through, become reliability problems1 viewlive readiness across the whole windowDeskely gives the window the same evidence model as a large project, sized to fit.

    Setting up the register

    Only the affected assets, with their tie-ins to what stays.

    The register covers the equipment being moved, replaced or added, plus the utility tie-ins and control interfaces to the existing plant.

    Existing assets that are only touched — a modified panel, a re-routed service — carry their own short record set.

    That boundary is what keeps a brownfield project from either drowning in scope or missing the interfaces where problems actually occur.

    1 · SOURCE DOCUMENTSModification drawings re…12 sheetsAffected asset list180 assetsTie-in schedule26 tie-insControl interface list48 signalsPARSE + MATCHtag · description · drawing ref2 · ONE TAG REGISTERL5-ST03-NEWNew station 03LINE 5T3-CAI-04Compressed air tie-inTIE-IN T-3L5-PNL-02Modified control panelCONTROLST3-PWR-01Power feeder tie-inTIE-IN T-3TWO DOCUMENTS DISAGREEModification draw…Compressed air tie-inAffected asset li…Abbreviated descriptionEngineer picks the sourcedecision loggedWeeks of transcription become a draft an engineer reviews.

    Execution

    Inside the window, status has to be current by the hour.

    Records are completed at the machine and visible immediately, so the shift handover is a look at the register rather than a reconstruction.

    Punch is raised and categorised by whether it blocks restart, which is the only question the plant manager is asking.

    Where the window overruns, the carried scope is documented with owners and dates rather than left to memory.

    RESTART AUTHORISATION LADDERShutdown window, hour 62 of 96Modified assets installed and signedSigned offUtility tie-in and control interface testedSigned offSafety and interlock re-validationIn progressBlocking punch closedAwaiting predecessorRestart authorisedAwaiting predecessor2 of 5restart steps cleared, 34 hours remaining0restarts authorised on a verbal all-clearRestart is checked from the data, hour by hour, not asserted in a call.

    Restart

    Restart authorisation has a defined evidence set behind it.

    Restart depends on the modified assets being signed, safety and interlock testing complete and blocking punch closed — checked from the data, not asserted in a call.

    The modification history stays with the assets, so the plant's records reflect what is actually installed.

    That matters at the next upgrade, when the last one is the starting point.

    Line 5 retrofit — restart ladderRestart authorised from signed evidenceINSTInstallation completeIssued day 8Modified asset recordssignedTie-ins pressure tested26 / 26SFTSafety and interlock testingBlocked — 2 itemsInterlock tests42 / 48 signedBlocking punch2 openRSTRestart authorisationBlocked — safety openSafety testingnot signedCarried punch owned6 with dates

    Re-validation after the move

    A relocated machine is not the same asset it was on the old floor, and its safety and interlock proof has to be re-earned, not carried over.

    Moving a machine changes enough about it that its prior acceptance record does not automatically transfer: new utility connections, a new safety fence layout and light curtain geometry, new conveyor tie-ins and often a new control panel interface all mean the machine's safety circuit and interlock validation has to be re-proven on the new floor, not assumed from the OEM's original documentation.

    This is the step most likely to be skipped under shutdown-window pressure, because the machine 'already worked' at the old location, and it is also the step a safety audit or an insurer will ask about first after any incident involving relocated equipment.

    Deskely treats a relocated asset's safety and interlock records as new records against the tag at its new location, with a reference back to its prior history, so restart authorisation is checked against re-proven safety evidence on the new floor rather than a document that describes a configuration that no longer exists.

    TIGHTLY-SCOPED TIE-IN REGISTERLine move, 96-hour windowREGISTER SCOPE — ONLY WHAT'S AFFECTEDConveyor section CV-08, relocatedUtility tie-in, compressed air branchControl interface, existing PLC panelAdjacent guarding, modified onlyUntouched plant stays out of scope; touched assets carry a short record set.HOUR-BY-HOUR STATUS, THIS SHIFTCV-08 mechanical installsignedTie-in leak testopenControl interface signal checksignedGuard interlock re-validationopen34 hremaining in the shutdown window2items open, owned and datedEvery carried item has an owner and a date, visible before the window closes.

    How it runs

    From last production before to first production after.

    Short windows benefit most from templated records: there is no time to design an approach once the plant is down.

    1. 01

      Scope the register tightly

      Only the assets affected, plus utility tie-ins and control interfaces to the live plant.

    2. 02

      Prepare before shutdown

      Templates, access and pre-window records set up while the plant is still producing.

    3. 03

      Execute in the window

      Records signed at the machine with status visible by the hour for every shift.

    4. 04

      Test safety and interlocks

      Safety validation and interlock testing recorded as prerequisites to restart.

    5. 05

      Categorise punch by restart

      Every item marked as blocking restart or carried, with an owner and a date.

    6. 06

      Authorise restart

      Restart released from signed evidence, and the modification history retained on the assets.

    FAQ

    Questions about Brownfield upgrades 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.