Gaps Module User Guide
Introduction
Assessment of Facility Data Sheet (FDS) readiness is paramount before the installation of tools within a fabrication. A "Gap" refers to identifying a missing Facility Point of Connection (FPOC) required for design and construction approval.
The Gaps application is crucial for the Integration team to outline any missing Points of Contact (POCs). Once this comprehensive list is compiled, it undergoes a meticulous review by Design Managers responsible for granting their approval.
When a disparity arises between the requirements of a given tool and the provisions made available by the FDS, diligent monitoring and resolution of such discrepancies become imperative; a process facilitated through the utilisation of the Gaps List Tracker.
The Gap creation depends on the synchronisation and record availability of tools, schedule and FPOC data, and accessible FASTr domains (Ra4, Rp1, D1D, AFO).
Refer to the Scribe guide below to understand Gaps application navigation.
The "Scribe" guide provided above offers comprehensive instructions on how to effectively navigate Gaps application. However, refer to the below section to get more details on:
-
The fields available in Default View
-
The fields available in Detailed View
-
The fields available in Create Gap option
-
How to work with different options available under Action column in each view
Default View fields list
The default view includes the following fields. These fields contains details of each gap in the view.
| Field | Description |
| Gap ID | A Gap Id is created by the application whenever a gap is saved. |
| Gap Name | Saved Gap Name |
| Utility Group | Saved utility group associated with the gap |
| Utility | Saved utility associated with the gap |
| Last Edited By | The credentials of the last user who edited the gap |
| Last Edited On | The date stamp of the last edit |
| Gap Type | The change gap type saved |
| Gap Status | The current status of the Gap. The values can be: * Saved * Open * Closed |
| Change Driver | The change driver captured from the Gap data |
| Facility | The saved building associated with the gap |
| QB/SOW | The saved Scope of Work associated with the gap |
| Gap Details | The saved Gap Details |
| Earliest SL1 Tool | Date of SL1 Construction Finish (CF) |
| Earliest SL1 | Earliest date of SL1 Construction Finish (CF) |
| Earliest IFC Tool | Date Field |
| Earliest IFC | Date Field |
| Date Opened | The date stamp whenever the status of the Gap is changed to Submitted |
| Date Closed | The closure date if a Gap is closed |
| Closure Bucket | The value of the selected closure bucket if a Gap is closed |
| Sum of Demand | The value must be computed through the records. Computation: The total value of the Avg Demand Logic of all the TPOCs associated with the particular GAP will be displayed in this column. |
| Sum of Peak Demand | The value must be computed through the records. Computation: The total value of the Peak Demand Logic of all the TPOCs associated with the particular GAP will be displayed in this column. |
Detailed View fields list
The detailed view includes the following fields. These fields contains details of each gap in the view.
| Field | Description |
| Gap ID | The gap ID of the selected Gap |
| Gap Name | Saved Gap Name |
| Utility Group | Saved utility group associated with the gap |
| Utility | The utility associated with the TPOC |
| Gap Type | The change gap type saved |
| Gap Status | The current status of the Gap. The values can be: * Saved * Submitted * Closed |
| Gap Details | The saved Gap Details |
| Date Opened (Submitted) | The date stamp whenever the status of the Gap is changed to Submitted |
| Date Closed | The closure date if a Gap is closed |
| Design Finish | The date of finishing the design |
| Closure Bucket | The value of the selected closure bucket if a Gap is closed |
| TPOC | The TPOC name |
| Tool | The tools associated with the TPOC |
| Peak Demand | The value needs to be computed. Computation: Group all TPOC basis Column X: "mastertoolconnectionname" For all the TPOCs in that group which does not have 0 or null value in column AQ "Toolconnectionmeasuredpeakdemand," add the values of that particular column. For the remaining TPOCs of that group, which do not have 0 or null value in column "Mod Value" available in FaSTr (currently, we don't have permission to access), add the values of that particular column. For the remaining TPOCs of that group, add the values in column AS "Toolconnectionpeakdemand" |
| Average Demand | The value must be computed through the records Computation: Group all TPOC basis Column X: "mastertoolconnectionname" For all the TPOCs in that group that do not have 0 or null value in column AP, "toolconnectionmeasuredavgdemand" adds the value of that particular column. For the remaining TPOCs of that group, add the values in column AM "toolconnectionavgdemand." |
| Sum of Demand | The value must be computed through the records. Computation: The total value of the Avg Demand Logic of all the TPOCs associated with the particular GAP will be displayed in this column. |
| Sum of Peak Demand | The value must be computed through the records. Computation: The total value of the Peak Demand Logic of all the TPOCs associated with the particular GAP will be displayed in this column. |
| UOM | Unit of Measurement |
| Connection Status | The connection status of the TPOC |
| Event Date | Date of Event |
| FtpocDP | Future Pipe Connection name |
| DPseg | Future Pipe name |
| TPOC Comment | The comments provided for this TPOC |
| Tool DS | Disconnect Tool Start |
| Tool DF | Disconnect Tool Finish |
| Tool SL1 CF | SL1 Construction Finish |
| Last Edited By | The credentials of the last user who edited the gap |
| Last Edited On | The date stamp of the last edit |
| Demo Life | Demo life of the TPOC |
| Change Driver | The change driver captured from the Gap data |
| Facility | The saved building associated with the gap |
Create Gap field list
| Field | Description |
| Gap Name | Gap Name (Mandatory) |
| Facility | Captures the building/s in which the created Gap must be acknowledged (Mandatory) |
| Utility | The supplies and utilities against which the Gap tickets need to be raised (Mandatory) |
| Utility Group | The utility group will be auto-populated with the value selected in Utility (Mandatory) |
| QB/SoW | The project code/ID related to the tool installation (Optional) |
| Change Driver | The reason for the Gap creation (Mandatory) |
| Gap Details | Other Gap Details or Comments, if any (Optional) |
Refer to the Scribe guide below to understand how to work with the options available under the Action column in each view.