Data Collection Methodology. The CODAP Project exchanges data on passive component degradation and failure, including service-induced wall thinning, non-through wall crack, leaking through-wall crack, pinhole leak, leak, rupture and severance (pipe break caused by external impact). For non-through wall cracks the CODAP scope encompasses degradation exceeding design code allowable for wall thickness or crack depth as well as such degradation that could have generic implications regarding the reliability of in-service inspection (ISI) techniques. The following failure modes are considered: • Non-through wall defects (e.g., cracks, wall thinning) interpreted as structurally significant and/or exceeding design code allowable. • Loss of fracture toughness of cast austenitic stainless steel piping. The loss of fracture toughness is attributed to thermal aging embrittlement. • Through-wall defects without active leakage (leakage may be detected following a plant operational mode change involving depressurization and cool-down, or as part of preparations for non-destructive examination, NDE). • Small leaks (e.g., pinhole leak, drop leakage) resulting in piping repair or replacement; • Leaks (e.g., leak rates within Technical Specification limits); • Large leaks (e.g., flow rates well in excess of Technical Specification limits); • Major structural failure (pressure boundary "breach" or "rupture"). In other words, the CODAP Event Database collects data on the full range of degraded conditions, from "precursors" to major structural failures. The structural integrity of a pressure boundary is determined by multiple and interrelated reliability attributes and influencing factors. Depending on the conjoint requirements for damage and degradation, certain combinations of material, operating environment, loading conditions together with applicable design codes and standard, certain passive components are substantially more resistant to damage and degradation than others. As an example, for stabilized austenitic stainless steel pressure boundary components, there are no recorded events involving active, through-wall leakage. By contrast, for unstabilized austenitic stainless steel, multiple events involving through-wall leakage have been recorded, albeit with relative minor leak rates. Flow-accelerated corrosion (FAC), if unmonitored, is a relatively aggressive degradation mechanism that has produced major structural failures, including double-ended guillotine breaks (DEGB). The types of pipe failure...
Data Collection Methodology. Guidance: This section describes in detail who is responsible for data collection and management (Director of Programs, M&E officer, others), and in what format (database, spreadsheets) data will be managed, and who is responsible for producing which reports. Aspects of quality control at all stages should be described. Relevant details about types of data collection issues such as sampling, tool design, use of sub-contractors and project staff for data collection, etc. would go here. The specific methods used to collect data for the specified indicators are described in detail in each PIRS.
Data Collection Methodology. A single field visit was completed on March 14, 2018 to assess and document the presence of vegetative and wildlife species within the study area. The vegetation field survey for species composition, and community mapping was completed in general accordance with the Ecological Land Classification (ELC) for Southern Ontario. Observations of wildlife (mammals, birds) were recorded during the field visit along with locational information of the sighting. During the field survey, emphasis was placed on species at risk with the potential to occur within the study area, and a review of potential impacts to the PSW. Xxxxxx Group Page 2
Data Collection Methodology. It was decided jointly by the evaluator and the project’s senior management staff that given the time available, the evaluator would visit four of the six implementation provinces including Phnom Penh. It was further decided to visit one district within each province and two communes per district. The project management staff was actively involved with the evaluator in determining the provinces, districts and communes to be visited according to criteria put forward by the evaluator, and provided a wealth of information upon which to base the selection. The selection criteria for provinces, districts and communes were:
Data Collection Methodology. Provided that Client is in compliance with its obligations under Section 4, Press Xxxxx shall use commercially reasonable efforts to:
Data Collection Methodology a. Contractor shall adhere to the prevailing federal HMIS Data Standards and Sonoma County HMIS Lead recommended program workflow(s) for each homeless program type.
Data Collection Methodology
