The ipmPIPE: Overview, Lessons, Opportunities, and Challenges 1,2 3 4 4 James R. VanKirk, Scott A. Isard, Kitty F. Cardwell, AND Martin A. Draper 1Center for IPM, North Carolina State University, 1730 Varsity Dr. Suite 110, Raleigh NC 27607. 2Corresponding author, e-mail:
[email protected]. 3Departments of Plant Pathology and Meteorology, Penn State University, 205 Buckhout Laboratory, University Park, PA 16802. 4United States Department of Agriculture, National Institute of Food and Agriculture, 1400 Independence Ave. SW, Stop 2201, Washington, DC 20250-2201. J. Integ. Pest Mngmt. 3(2): 2012; DOI: http://dx.doi.org/10.1603/IPM11015 ABSTRACT. The ipmPIPE (Integrated Pest Management Pest Information Platform for Extension and Education) was first developed as a response to the threat of soybean rust (SBR), caused by the pathogen Phakopsora pachyrhizi. Since that time the ipmPIPE portfolio has grown to include “PIPEs” for soybean aphid Aphis glycines Matsumura (now discontinued), legume diseases, cucurbit downy mildew caused by the pathogen Pseudoperonospora cubensis (Berk. & M.A. Curtis) Rostovzev, pecan nut casebearer Acrobasis nuxvorella Neunzig with pecan scab caused by Cladosporium caryigenum (Ellis & Langl.) (Gottwald forecasting in development), Southern corn rust caused by Puccinia polysora Underw., and onion pests. In addition, the Western Specialty Crops ipmPIPE, the North Central ipmPIPE, and the Pennsylvania PIPE each address multiple pest situations found within defined geographic boundaries and a PIPE is in development for ornamentals that will address multiple pathogens on multiple hosts. This report explains the general concept of the ipmPIPE approach and discusses common elements of most PIPEs. It provides a brief history of funding and development.