FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2007206171> ?p ?o ?g. }

• W2007206171 abstract "Abstract Geographic Response Plans (GRP's) are under development by both industry andagencies. The more generic version of these plans is becoming more common inthe Area Contingency Plans. These GRP's often serve as the base for developingmore detailed tactical plans for emergency response and regulatory compliance. These detailed GRP's can effectively identify human and environmental resourcesthreatened by a potential release, as well as displaying what can be done tocontain or mitigate the release. Such plans are being developed by the pipelineindustry, refineries, terminals, and exploration/production operations. Whenthese plans are developed in a Geographic Information System (GIS), they can becombined with newer software tools to become powerful additions to an Incident Management System. The GIS data from these plans can be quickly incorporatedinto an electronic Incident Action Plan and combined with output from newtrajectory models (such as NOAA's GNOME software). The combination createseffective tools to use in response to actual events. Although GIS data andsoftware will not clean up a spill, pre-planning in the proper format can speedup the initial response and greatly improve information flow during anincident. Introduction Rapid and effective response is essential to minimize the damage from an oilspill or hazardous substance release. When a spill or release occurs, responders must quickly determine:what resources are threatened;what are the response priorities, or objectives;which plans will best achieve those objectives;what resources are needed to implement those plans; andwhere to get those resources. This requires that the tedious portion ofdefining detailed response strategies be done in advance of an incident. Thepre-defined strategies must be specific to each geographic area, or sensitivityto be protected (thus the term, Geographic Response Plan). When these areadequately defined in advance, responders can simply choose which strategies toimplement (or modify) based on the conditions present during that incident. With the proper combination of planning, data, and software, these steps canquickly result in an effective initial response, as well as a good Incident Action Plan for the next response period." @default.
• W2007206171 created "2016-06-24" @default.
• W2007206171 creator A5018464813 @default.
• W2007206171 creator A5055476300 @default.
• W2007206171 date "2000-05-01" @default.
• W2007206171 modified "2023-09-25" @default.
• W2007206171 title "Using Geographic Response Plans and GIS Data Effectively in Incident Management Systems" @default.
• W2007206171 doi "https://doi.org/10.4043/11988-ms" @default.
• W2007206171 hasPublicationYear "2000" @default.
• W2007206171 type Work @default.
• W2007206171 sameAs 2007206171 @default.
• W2007206171 citedByCount "0" @default.
• W2007206171 crossrefType "proceedings-article" @default.
• W2007206171 hasAuthorship W2007206171A5018464813 @default.
• W2007206171 hasAuthorship W2007206171A5055476300 @default.
• W2007206171 hasConcept C104345477 @default.
• W2007206171 hasConcept C1668388 @default.
• W2007206171 hasConcept C205649164 @default.
• W2007206171 hasConcept C41008148 @default.
• W2007206171 hasConcept C41856607 @default.
• W2007206171 hasConcept C62649853 @default.
• W2007206171 hasConcept C77088390 @default.
• W2007206171 hasConcept C9770341 @default.
• W2007206171 hasConceptScore W2007206171C104345477 @default.
• W2007206171 hasConceptScore W2007206171C1668388 @default.
• W2007206171 hasConceptScore W2007206171C205649164 @default.
• W2007206171 hasConceptScore W2007206171C41008148 @default.
• W2007206171 hasConceptScore W2007206171C41856607 @default.
• W2007206171 hasConceptScore W2007206171C62649853 @default.
• W2007206171 hasConceptScore W2007206171C77088390 @default.
• W2007206171 hasConceptScore W2007206171C9770341 @default.
• W2007206171 hasLocation W20072061711 @default.
• W2007206171 hasOpenAccess W2007206171 @default.
• W2007206171 hasPrimaryLocation W20072061711 @default.
• W2007206171 hasRelatedWork W186026152 @default.
• W2007206171 hasRelatedWork W2011713215 @default.
• W2007206171 hasRelatedWork W2183037306 @default.
• W2007206171 hasRelatedWork W2365992249 @default.
• W2007206171 hasRelatedWork W2515954986 @default.
• W2007206171 hasRelatedWork W2517951119 @default.
• W2007206171 hasRelatedWork W2592527442 @default.
• W2007206171 hasRelatedWork W2592781854 @default.
• W2007206171 hasRelatedWork W2947930229 @default.
• W2007206171 hasRelatedWork W2990714020 @default.
• W2007206171 hasRelatedWork W2998000891 @default.
• W2007206171 hasRelatedWork W3083098586 @default.
• W2007206171 hasRelatedWork W32247871 @default.
• W2007206171 hasRelatedWork W561615308 @default.
• W2007206171 hasRelatedWork W642846803 @default.
• W2007206171 hasRelatedWork W827216529 @default.
• W2007206171 hasRelatedWork W2615480058 @default.
• W2007206171 hasRelatedWork W2914275998 @default.
• W2007206171 hasRelatedWork W3085862600 @default.
• W2007206171 hasRelatedWork W963698980 @default.
• W2007206171 isParatext "false" @default.
• W2007206171 isRetracted "false" @default.
• W2007206171 magId "2007206171" @default.
• W2007206171 workType "article" @default.