Edit Parts - Initial - Version 2

Creating New Version Based On: Version 2

Original created: Jul 29, 2025 21:31 by admin

Note: Editing will create a new version and automatically activate it. The original version will be preserved in the history.

Prompt Content *

This is the user-editable portion of the prompt. Technical structure (like Response Structure, CSV headers, etc.) is handled automatically by the system.

# VALVE/PARTS DATA EXTRACTION FOR QUOTATION

OBJECTIVE: Extract structured valve/parts information from technical documents for accurate quotation purposes.

## ANALYSIS STEPS:

1.  DOCUMENT SCAN
    * Identify ALL potential valve/parts information sources:
        * Traditional tabular lists
        * Parts catalogs or bill of materials (BOM)
        * Numbered specifications (any format)
        * Technical drawings with callouts
        * Sections labeled "Equipment List," "Valve Schedule," or similar

2.  DATA IDENTIFICATION
    * Look specifically for these key fields:
        * Identifiers: "ITEM NO", "MTO REFERENCE"
        * Quantities: "QTY," "QUANTITY," "NO. REQUIRED"
        * Dimensions: "SIZE," "DN," "NPS," "DIAMETER"
        * Classifications: "TYPE," "MODEL," "DESCRIPTION"
        * References: "DATA SHEET," "SPECIFICATION," "VALVE CODE"

3.  EXTRACTION RULES
    * PRIMARY SOURCE: Extract from dedicated valve/parts lists when available
    * FRAGMENTED DATA: Correlate information across document sections when necessary
    * UNSTRUCTURED DATA: Reconstruct specifications for clearly identified items
    * MULTIPLE LISTS: Select ONLY ONE list with highest confidence (prioritize item numbers over tag numbers).
        * If a list is grouped by headings/categories like "Manual valves" or "Actuated valves", you should treat these as a single list.
        * IMPORTANT: Each row in the valve schedule should be treated as a separate item with its own entry in the output, even if it shares similar specifications with other valves.
    * ANOMALOUS FORMATS: If identifier format changes significantly mid-list (e.g., "1.1" to "162-BWYY-2823"), treat as separate lists

4.  CONFIDENCE SCORING
    * For each extracted field, assess your confidence in the accuracy of the extraction on a scale of 0.0 to 1.0:
        - 1.0: Explicitly stated in clear documentation with exact match
        - 0.9: Clearly documented but may require minor interpretation
        - 0.8: Well-documented but some uncertainty in mapping to field
        - 0.7: Reasonable inference from available information  
        - 0.6: Educated guess based on partial information
        - 0.5: Uncertain extraction with limited source data
        - 0.4 or lower: Very uncertain, possibly incorrect

5.  TAG NUMBERS
    * When a document lists multiple tag numbers with identical specifications (e.g., same size, type etc) ON A SINGLE ROW OF THE SCHEDULE:
        * Treat this as a SINGLE item with a quantity equal to the number of tags listed
        * For example: If "3/4" x 1/2" - 11MV537889;11MV537906;11MV537923;11MV537948;11MV537949;11MV537950" appears,
            this represents ONE item with quantity = 6
        * Do NOT create separate entries for each tag number
        * If tags are grouped under categories like "SKID" or "LOOSE", create one item per group
        * Don't use any tag number as the item number in the CSV output, create a new sequential number
        * IMPORTANT: Valves that appear on SEPARATE ROWS in a valve schedule should always be treated as separate items, even if they have similar specifications.

## FIELD GUIDANCE:

- item_no: Primary identifier (MTO reference if available)
		* If no identifiers exist, use sequential numbers (1, 2, 3...).
		* For multiple similar lists, choose ONE list only.

- data_sheet_number: Reference number for detailed specifications
		* May be labeled as:
				- "datasheet number" / "datasheet"
				- "valve code"
				- "spec reference"
				- "VDS"
				- etc.
		* When 'Valve Code' is the source for `data_sheet_number`:
				- Be aware that 'Valve Code' values might be split into multiple parts across adjacent or nearby columns. This often results from formatting in the original source document, such as merged cells in an Excel file.
				- If you detect such a split (e.g., a primary code part in the 'Valve Code' column, followed by one or more columns that are empty or contain placeholders like "-", and then a subsequent part of the code in another column a few positions away), you should concatenate these meaningful parts.
				- A common separator for such concatenation is a hyphen ('-'). For example, if the 'Valve Code' column shows 'A2U', an intermediate column is blank or has '-', and a following column shows '5RPC', the combined `data_sheet_number` should be 'A2U-5RPC'.
				- Apply this logic carefully, focusing on clear patterns of split data related to 'Valve Code'.
		* This is NOT likely to be labelled as "pipe class", EVEN IF this appears in the enums. Prioritize values labelled as above.
		* Look for references to external documentation against an item.
		* In cases where there are ZERO enum values, and you can't find an obvious datasheet, leave this blank.
		* Note that we are NOT looking for the identifier of the CURRENT document.

- tag_numbers: Tag numbers or identifiers
		* If multiple tag numbers are listed, separate these with a semicolon and a space, "TAG-1; TAG-2".
		* If no tag number is available, leave this blank.

- type: Valve/part category
		* IMPORTANT: ALWAYS use the value specified in the dedicated "Valve Type" column when available, regardless of identifiers or descriptions.
		* The "Valve Type" column takes absolute priority over any tag numbers, descriptions, or other fields.
		* Even if the identifier contains "DBB" or "SBB" or the description mentions "Double Block & Bleed valve," the type should STILL be taken from the "Valve Type" column.
		* For example, if the tag number is "1/2"-DBB-91202" and the description says "Pressure Gauge isolation DBB valve" but the Valve Type column says "Ball valve," you MUST use "Ball valve" as the type.
		* Only if no "Valve Type" column exists should you try to infer type from identifiers or descriptions.
		* NOTE: Always use a top-level type from the "Top Level Types" list. Terms like "Triple Eccentric" should never be used as a type, as they are subtypes.
		* Try to match using the enums provided below, otherwise use exact terminology from document.

- subtype: Valve/part subcategory
		* For ball valves, if description contains "TRUNNION MOUNTED," use "Trunnion mounted" as subtype.
		* For ball valves, if description contains "FLOATING BALL" or "STANDARD FLOATING BALL," use "Floating ball" as subtype.
		* For butterfly valves, if description contains "TRIPLE ECCENTRIC" or similar terms, use "Triple offset" as subtype.
		* Try to match using the enums provided below, otherwise exact terminology from document. If not available, leave blank.

- size: Dimensional specification (numerical value preferred)
		* Single value preferred (e.g., "1 inch").
		* Use range only when single value unavailable (e.g., "1-2 inch").
		* For compound dimensions:
				- ALWAYS use format "X x Y x Z inch" with unit appearing ONLY ONCE at the end.
				- CORRECT: "3/4 x 1/2 inch" or "2 x 1.1/2 x 3/4 inch".
				- INCORRECT: "3/4 inch x 1/2 inch" or "1.13/16 inch x 1/2 inch".
		* NEVER repeat units between dimension components.
		* NEVER abbreviate or simplify ranges or compound dimensions.
		* Try to match the value(s) using the enums provided below.

- quantity: Number of units required
		* Default to "1" if unspecified.
		* Some documents may specify quantities of pneumatic accessories connected to a valve, such as "solenoid valve". We DO NOT want to use the quantity of these, as they are a sub-part of the valve, not the valve itself.

Use markdown formatting for better readability. The content will be automatically integrated with the technical structure.

Change Notes

These notes will help track what changed between versions.

Version Information

Type: Parts - Initial

Current Version: 2

New Version Will Be: 3

Status After Save: Active (current active version will be deactivated)

Cancel