Core Ontology for Petroleum Installations · INF-UFRGS-Ontologies · CNPq INF-UFRGS-ENERGIA inf.ufrgs.br/ontologies/copi dee69df
exported equivalent
pig trap
IRI: http://www.inf.ufrgs.br/ontologies/copi#Pigtrap
Generated on 2026-04-16
Natural Language Definition
EN
A pig trap is an assembly that bears the function of launching and receiving pipe pigs for pipeline maintenance and has both launcher and receiver components.
PT-BR
Uma armadilha de pig é um conjunto que possui a função de lançar e receber pigs de tubulação para manutenção de dutos e possui componentes de lançador e receptor.
Formal Axioms
Semi-formal (Aristotelian)
Every pig trap is an assembly that bears a pig launching and receiving function and has component parts that are a pig launcher and a pig receiver.
First-Order Logic Theory
Loading…
▸ Stored override ∀x(PigTrap(x) ↔ Assembly(x) ∧ ∃f(PigLaunchingAndReceivingFunction(f) ∧ bearerOf(x,f)) ∧ ∃l(PigLauncher(l) ∧ hasComponentPartAtAllTimes(x,l)) ∧ ∃r(PigReceiver(r) ∧ hasComponentPartAtAllTimes(x,r)))
OWL 2 / Turtle
@prefix copi: <https://www.inf.ufrgs.br/ontologies/copi/> . @prefix : <https://www.inf.ufrgs.br/ontologies/copi/> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix bfo: <http://purl.obolibrary.org/obo/> . @prefix iof-core: <https://spec.industrialontologies.org/ontology/construct/> . @prefix iof-av: <https://spec.industrialontologies.org/ontology/annotation/> . @prefix skos: <http://www.w3.org/2004/02/skos/core#> . @prefix qudt: <http://qudt.org/schema/qudt/> . @prefix dcterms: <http://purl.org/dc/terms/> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix apv: <http://inf.ufrgs.br/ontologies/apv#> . ### COPI — Core Ontology for Petroleum Installations ### Class module: PigTrap <https://www.inf.ufrgs.br/ontologies/copi> rdf:type owl:Ontology ; dcterms:title "Core Ontology for Petroleum Installations (COPI)"@en ; dcterms:title "Ontologia Core para Instalações de Petróleo (COPI)"@pt-br ; dcterms:description "BFO/IOF-Core conformant ontology of equipment classes for petroleum production plants, developed using the five-step RDL enrichment method."@en ; skos:scopeNote "Material artifacts (bfo:material_entity) that (i) are part of a petroleum production plant, and (ii) bear at least one function whose realization involves the transport (e.g. production and injection), processing (separation and other processes), control, monitoring, measurement, containment or offloading of material or energy."@en ; skos:scopeNote "Artefatos materiais (bfo:material_entity) que (i) fazem parte de uma planta de produção de petróleo, e (ii) possuem ao menos uma função cuja realização envolve o transporte (p. ex. produção e injeção), processamento (separação e outros processos), controle, monitoramento, medição, contenção ou escoamento de material ou energia."@pt-br ; skos:scopeNote "COPI provides high-level equipment categories defined by function to demonstrate the defined-class mechanism. Equipment subtypes are annotated with references to CFIHOS and PCA RDL terms. COPI is not a reference data library; organizations should use CFIHOS, PCA RDL, or ISO 14224 for comprehensive equipment classification."@en ; skos:scopeNote "COPI fornece categorias de alto nível de equipamentos definidas por função para demonstrar o mecanismo de classe definida. Os subtipos de equipamentos são anotados com referências aos termos do CFIHOS e do PCA RDL. COPI não é uma biblioteca de dados de referência; organizações devem utilizar o CFIHOS, o PCA RDL ou a ISO 14224 para classificação abrangente de equipamentos."@pt-br ; owl:versionInfo "1.1.0" ; owl:imports <https://spec.industrialontologies.org/ontology/core/Core/> ; owl:imports <http://purl.obolibrary.org/obo/bfo/2020/bfo.owl> ; dcterms:creator "Nicolau Oyhenard dos Santos"@en ; dcterms:contributor "Cauã Antunes" ; dcterms:contributor "Haroldo Rojas" ; dcterms:contributor "Rafael Petry" ; dcterms:contributor "Régis Romeu" ; dcterms:contributor "Mara Abel" ; dcterms:isPartOf <https://inf.ufrgs.br/projetos/OntoKG> ; dcterms:publisher "Universidade Federal do Rio Grande do Sul (UFRGS)"@en ; dcterms:license <https://creativecommons.org/licenses/by/4.0/> ; dcterms:created "2026-04-08"^^xsd:date ; dcterms:modified "2026-10-07"^^xsd:date ; apv:GlobalMinLanguageCoverage "en pt-br" ; apv:ClassURIFormationRule "https://www[.]inf[.]ufrgs[.]br/ontologies/copi/(COPI_[0-9]{7}|[A-Z][A-Za-z0-9]*)" ; apv:ClassMinAnnotationCoverage "rdfs:label https://spec.industrialontologies.org/ontology/annotation/naturalLanguageDefinition" . iof-av:naturalLanguageDefinition rdf:type owl:AnnotationProperty ; apv:MinAnnotationLength 20 . ### Identity-giving function :COPI_0000590 rdf:type owl:Class ; # PigLaunchingAndReceivingFunction rdfs:subClassOf iof-core:DesignedFunction ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty bfo:BFO_0000054 ; # realizedIn owl:allValuesFrom :COPI_0000591 # PigLaunchingAndReceivingProcess ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty bfo:BFO_0000054 ; # realizedIn owl:someValuesFrom :COPI_0000591 # PigLaunchingAndReceivingProcess ] ; rdfs:label "pig launching and receiving function"@en ; rdfs:label "função de lançamento e recebimento de pig"@pt-br . ### Process type :COPI_0000591 rdf:type owl:Class ; # PigLaunchingAndReceivingProcess rdfs:subClassOf iof-core:PlannedProcess ; rdfs:label "pig launching and receiving process"@en ; rdfs:label "processo de lançamento e recebimento de pig"@pt-br . :COPI_0000591 # PigLaunchingAndReceivingProcess rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasInput ; owl:someValuesFrom :COPI_0000037 # PortionOfFluid ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasInput ; owl:someValuesFrom :COPI_0000598 # PipelinePig ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasSpecifiedOutput ; owl:someValuesFrom :COPI_0000037 # PortionOfFluid ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasSpecifiedOutput ; owl:someValuesFrom :COPI_0000598 # PipelinePig ] . ### Equipment universal: PigTrap :COPI_0000320 rdf:type owl:Class ; # PigTrap owl:equivalentClass [ rdf:type owl:Class ; owl:intersectionOf ( iof-core:Assembly [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasFunction ; # Object branch (MaterialArtifact/Assembly/Object/FiatObjectPart) owl:someValuesFrom :COPI_0000590 # PigLaunchingAndReceivingFunction ] [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasComponentPartAtAllTimes ; owl:someValuesFrom :COPI_0000318 # PigLauncher ] [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasComponentPartAtAllTimes ; owl:someValuesFrom :COPI_0000319 # PigReceiver ] ) ] ; rdfs:label "pig trap"@en ; rdfs:label "armadilha de pig"@pt-br ; iof-av:naturalLanguageDefinition "A pig trap is an assembly that bears the function of launching and receiving pipe pigs for pipeline maintenance and has both launcher and receiver components."@en ; skos:definition "A pig trap is an assembly that bears the function of launching and receiving pipe pigs for pipeline maintenance and has both launcher and receiver components."@en ; iof-av:naturalLanguageDefinition "Uma armadilha de pig é um conjunto que possui a função de lançar e receber pigs de tubulação para manutenção de dutos e possui componentes de lançador e receptor."@pt-br ; iof-av:semiFormalNaturalLanguageAxiom "Every pig trap is an assembly that bears a pig launching and receiving function and has component parts that are a pig launcher and a pig receiver."@en ; iof-av:firstOrderLogicAxiom "∀x(PigTrap(x) ↔ Assembly(x) ∧ ∃f(PigLaunchingAndReceivingFunction(f) ∧ bearerOf(x,f)) ∧ ∃l(PigLauncher(l) ∧ hasComponentPartAtAllTimes(x,l)) ∧ ∃r(PigReceiver(r) ∧ hasComponentPartAtAllTimes(x,r)))"@en ; skos:definition "[ISO 15926-4] A <PIG TRAP> is an <ARTEFACT> and a <TOOL> that is a pipeline maintenance tool, which includes a launcher and receiver, introducing a <PIPE PIG> into the line"@en ; skos:definition "[CFIHOS] A facility on a pipeline for inserting and retrieving a scraper or pig."@en ; skos:definition "[POSC Caesar] \""@en . :COPI_0000318 rdf:type owl:Class ; # PigLauncher rdfs:subClassOf iof-core:MaterialArtifact ; rdfs:label "lançador de pig"@pt-br ; rdfs:label "pig launcher"@en . :COPI_0000319 rdf:type owl:Class ; # PigReceiver rdfs:subClassOf iof-core:MaterialArtifact ; rdfs:label "recebedor de pig"@pt-br ; rdfs:label "pig receiver"@en . # Disjointness: PigTrap and Filter [] rdf:type owl:AllDisjointClasses ; owl:members ( :COPI_0000320 :COPI_0000081 ) . # PigTrap, Filter # Disjointness: PigTrap and Separator [] rdf:type owl:AllDisjointClasses ; owl:members ( :COPI_0000320 :COPI_0000084 ) . # PigTrap, Separator # Disjointness: PigTrap and Valve [] rdf:type owl:AllDisjointClasses ; owl:members ( :COPI_0000320 :COPI_0000077 ) . # PigTrap, Valve
Axiomatization Decision Log
1 Identity-Giving Function
Function class
PigLaunchingAndReceivingFunction ⊑ DesignedFunction
Realized in
PigLaunchingAndReceivingProcess ⊑ PlannedProcess
The identity-giving function is the capability to launch and receive pipe pigs for pipeline maintenance operations. This is what makes a pig trap distinct from other pipeline equipment - it enables the insertion and retrieval of cleaning, inspection, or maintenance devices into/from the pipeline.
2 Genus Determination
Assembly bfo:Object (BFO_0000030)

Causally unified material artefact composed of physically connected, separable MaterialComponent parts. Satisfies Assembly ⊑ MaterialArtifact ⊑ bfo:Object.

No domain-specific parent candidates are appropriate. 'TOOL' is too general and 'piping and pipeline equipment' is not a formal ontological class. A pig trap is a complex mechanical assembly with launcher and receiver components that work together as a unified maintainable unit. It fits the Assembly pattern as a causally unified artifact with physically connected removable subcomponents.
3 Necessary Parts
Part class Parent Relation
PigLauncher MaterialArtifact hasComponentPartAtAllTimes
PigReceiver MaterialArtifact hasComponentPartAtAllTimes
These parts are constitutive of the pig trap's ability to perform its function. The launcher and receiver are definitional components, while closures are operationally necessary for safe pig handling.
4 Process Participation Signature ⟨I, O, T⟩
Inputs (I)
PortionOfFluid — flowing through pipeline
PipelinePig — maintenance device
Outputs (O)
PortionOfFluid — continuing through pipeline
PipelinePig — after maintenance operation
Transformation (T)
pig insertion/retrieval without interrupting main fluid flow
The pig trap enables pig operations while maintaining pipeline flow continuity. The pig is inserted via launcher and retrieved via receiver while the process fluid continues flowing.
5 Axiom Mode Decision

Necessary + Sufficient — modelled as a defined class (≡, EquivalentClass). Automatic classification is appropriate for this concept.

Disjointness Axioms
Filter Separator Valve
C2: Valve. C4: Filter, Separator. These equipment types have incompatible process signatures - filters/separators modify fluid composition, valves control flow directly, while pig traps handle maintenance device insertion/retrieval without modifying the main process stream
Cross-Standard Observations
ISO 15926 emphasizes the tool aspect and dual launcher/receiver structure, while CFIHOS focuses on the pipeline facility aspect for inserting/retrieving scrapers. Both align on the core function but use different terminology (pig vs scraper). POSC Caesar definition is empty but the concept exists in their hierarchy.

Suggest a change

Opens a pre-filled GitHub issue on the COPI repo — nothing is sent until you submit it there.