• be_ixf; php_sdk; php_sdk_1.4.11
  • 75 ms
  • iy_2023; im_05; id_29; ih_23; imh_26; i_epoch:1.68542801423E+12
  • ixf-compiler; ixf-compiler_1.0.0.0
  • py_2020; pm_05; pd_14; ph_21; pmh_20; p_epoch:1.58951645988E+12
  • link-block-publisher; link-block-publisher_link-block-publisher; bodystr
  • pn_tstr:Thu May 14 21:20:59 PST 2020; pn_epoch:1.58951645988E+12
  • 0 ms
  • be_ixf; php_sdk; php_sdk_1.4.11
  • https://www.naes.com/news/when-communication-goes-awry/
  • https://www.naes.com/news/when-communication-goes-awry/
Skip to content
NAES
  • Twitter
  • LinkedIn
  • Services
    • Power Services
    • Compliance & Fleet Services
      • Engineering
      • E3 Consulting
      • O&M Services
      • Complete Compliance Services
      • Maximo Services
      • Field Engineering and Research
    • Fabrication, Maintenance, & Construction
    • Staffing Services
  • About Us
    • Subsidiaries
    • Leadership
  • Communications
    • News
    • Case Studies
    • Press Releases
  • Careers
  • Contact
    • Careers
    • Contact a Location
    • NAES Login Center
Solar Panels

In the News

Home Communications In the News When Communication Goes Awry

9.10.2016

Technically Speaking

When Communication Goes Awry

When Communication Goes Awry

An offhand remark is taken as blanket approval…with costly consequences

by Dave Righthouse – Senior Project Manager, Plant Operations

 

Recently at a NAES-operated facility, an environmental services contractor contacted the facility’s asset manager about installing a number of monitoring wells. The contractor proposed several sites for the wells, which would range from 15 to 30 feet in depth.

The contact started as a phone call that was followed up by an email to recap the discussion. The asset manager reminded the contractor that his personnel would require safety training and basic facility orientation before they could start any work. The email exchange included the proposed coordinates of the monitoring wells, which were to be drilled at various locations within the site confines.

The contractor was looking for approval to begin work and suggested a start date for the work. The asset manager responded that “on the surface everything looked good” and reminded the contractor to get in touch with site personnel for their safety orientation and walk-through. Site personnel provided the environmental contractor with underground piping diagrams and site plans.

The site walk-through was scheduled and the proposed monitoring wells were marked out. To be sure that the locales were safe for drilling, the contractor used a sonar device to detect any underground objects. However, the device proved accurate to a depth of only 6 feet due to the heavily compacted soil.

Technically Speaking_NAES

Once the mark-outs were completed, the site team scheduled the drilling contractor to begin work. The first two wells were drilled without incident. However, on the third well, after performing a soft-drill to a depth of 6 feet, the auger hit something hard at 9 feet below grade. The contractor backfilled the well and abandoned it. A couple of days later, the backfill had sunk significantly. After a second backfilling, the same sinking was observed. The site was excavated, which revealed that the drilling had punctured an active pipeline.

Technically Speaking_NAES

NAES conducted a root cause analysis, during which it was noted that the contractor had interpreted the words “on the surface everything looked good” to mean that the proposed well sites had been cleared for drilling. He didn’t refer to the drawings he had received because in his view, the site team had approved the proposed sites. The site team had assumed that the contractor had utilized the drawings and was simply safeguarding the process by using the sonar device. No one realized that the sonar device was only accurate to about 6 feet given the soil conditions.

In short, a simple statement that things looked good was taken as a work scope approval. The mindset of looking for approval – and reading it into a conversation – had led the contractor down a path that it was OK to proceed. Fortunately, the incident produced a relatively minor incident and may provide a much greater opportunity for teaching us how we can assure that things are safe before we begin work.

One question to ask in such cases as these is ‘How do we know it’s safe to proceed?’ If the answer doesn’t include hard, factual evidence that can be traced back to well-founded conclusions, then it’s time to stop and double-check. In this case, an offhand remark was taken as approval and resulted in a costly mishap.

When Communication Goes Awry

Join the Conversation

  • Twitter
  • LinkedIn
NAES

© Copyright 2023 NAES. All rights reserved.

  • Privacy Policy
  • Terms of Use
  • Do Not Sell My Personal Information

Website design by Jordan Crown

  • Services
    • Power Services
    • Compliance & Fleet Services
      • Engineering
      • E3 Consulting
      • O&M Services
      • Complete Compliance Services
      • Maximo Services
      • Field Engineering and Research
    • Fabrication, Maintenance, & Construction
    • Staffing Services
  • About Us
    • Subsidiaries
    • Leadership
  • Communications
    • News
    • Case Studies
    • Press Releases
  • Careers
  • Contact
    • Careers
    • Contact a Location
    • NAES Login Center

‹ › ×
    Manage Cookie Consent
    We use cookies to optimize our website and our service.
    Functional cookies Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    Manage options Manage services Manage vendors Read more about these purposes
    View preferences
    {title} {title} {title}
    CAISO Generator Modeling Process and Data Requirements

    Don’t wait until the last minute. You should allow time for at least one iteration with CAISO so that you are complete and deemed compliant before your deadline.

    On August 1, 2018, CAISO introduced a revised Business Practice Manual for Transmission Planning Process (BPM), which includes new data requirements for interconnected generation resources within the ISO’s footprint. Section 10 of the BPM establishes revised data requirements and compliance procedures for all participating generators including non-NERC registered entities. While additional requirements have been placed on larger NERC registered facilities, these changes may pose an even greater burden to entities that have been exempt from NERC mandated modeling and protection requirements.

    New data requirements include voltage and frequency protection models, power flow models, and in some cases, sub-synchronous resonance models. These models must be verified using criteria listed in the BPM, which can only be performed by entities with modeling software and knowledge of modeling practices.

    NAES is prepared to assist entities with data aggregation, modeling, and testing to ensure compliance with CAISO’s data requests. The following links will allow entities to determine when to expect their individual data requests (phase) and what data will be required (category).

    Business Practice Manual (BPM)

    Entity Category and Phase Listing

    CAISO Transmission Planning Website

    TPL-007

    TPL-007 establishes planning criteria for induced currents caused by geomagnetic disturbances. The standard is applicable to facilities using transformer(s) with a high side, wye grounded winding operated above 200 kV and can require both submittal of general geomagnetic data (R2) and thermal impact assessments (R6) depending on results of Planning Coordinator analysis.

    VOLTAGE AND REACTIVE (VAR) STANDARDS

    VAR-501-WECC

    VAR-501-WECC requires applicable entities within the WECC region to confirm performance settings and characteristics of Power System Stabilizers (PSS). NAES provides physical testing and reporting services to address WECC’s specific PSS requirements.

    PERSONNEL PERFORMANCE, TRAINING AND QUALIFICATIONS

    PER-006

    PER-006 requires Generator Operators to provide training to personnel who are responsible for the Real-time control of a generator. NAES has developed specific protection system training materials suitable for compliance with the Standard and provides this training both on and off site

    PROTECTION AND CONTROL (PRC) STANDARDS

    PRC-001

    PRC-001 requires entities to coordinate protection system changes with other affected parties. NAES offers both procedural documentation and engineering services to establish the required coordination for both PRC-001 and PRC-027.

    PRC-002

    PRC-002 requires the installation and operation of disturbance monitoring equipment (DME) for applicable entities. NAES can assist with the design and installation of DME as well as ongoing compliance support.

    PRC-019

    PRC-019 requires applicable entities to show coordination between voltage regulating controls, limiters, equipment capabilities, and protection settings. NAES produces PRC-019 specific coordination studies for both traditional generators and renewable projects to establish compliance with the Standard.

    PRC-023

    PRC-023 requires load responsive protective relays be set according to criteria within the Standard to ensure settings do not limit transmission loadability. NAES provides full engineering analyses to maintain compliance with this Standard.

    PRC-024

    PRC-024 requires applicable entities to ensure generator protective relays do not trip within predefined frequency and voltage limits. NAES can complete protection settings analyses and provide compliance documentation that clearly identifies protection settings as they relate to NERC’s “no trip” zones.

    PRC-025

    PRC-025 establishes minimum settings requirements for load-responsive relays protecting generators, step up transformers, and auxiliary transformers. NAES utilizes predefined calculation options as well as simulations to determine a facility’s compliance status and development of new relay settings if required.

    PRC-026

    PRC-026 requires applicable entities to perform load responsive relay settings analyses based on criteria identified within the Standard. Entities are typically notified by the Planning Coordinator when an analysis is required. NAES performs all required studies to establish compliance.

    MODELING, DATA, AND ANALYSIS (MOD) STANDARDS

    MOD-025

    MOD-025 requires Real and Reactive Power capability testing for individual generating units over 20 MVA or facilities with over 75 MVA of generation capacity. NAES offers site specific test procedures and/or complete onsite testing services to meet the requirements of this standard.

    MOD-026

    MOD-026 requires verification of excitation or volt/var control dynamic models through utilization of either system disturbances or physical testing. NAES offers full testing and modeling services to meet the requirements of this standard.

    MOD-027

    MOD-027 requires verification of governor or active power/frequency control dynamic models through utilization of either system disturbances or physical testing. NAES offers full testing and modeling services to meet the requirements of this standard.