Issue link: https://let.epubxp.com/i/206367
TAL K IN G P OI N T S A D V A N C E M E N T S I N C O M M U N I C AT I O N S T E C H N O L O G Y Data challenges Alicia C. Saia Alicia works in solutions marketing on the MarkLogic public sector team. Prior to joining MarkLogic, she spent seven years leading product marketing at i2 Inc. (now part of IBM) where she was responsible for gathering and analyzing product requirements for the i2 investigative analysis software suite, working with customers in the law enforcement, military, intelligence, and commercial fraud sectors in the Americas. She also spent two and a half years performing product management and marketing at TrapWire Inc. where she worked with police departments, fusion centers, and security companies to develop software for gathering and analyzing suspicious activity report data. in law enforcement 12 things to consider when evaluating new information management solutions T he process of identifying, apprehending, and prosecuting criminals is hard enough without dealing with roach motels of data— individual systems, applications, and data sources where data goes in but you can't get it out. Law enforcement professionals shouldn't have to jump through so many hoops. I've been working with organizations and individuals in law enforcement (as well as national and homeland security and other 36 Law Enforcement Technology November 2013 www.officer.com agencies involved in catching bad guys) since shortly after 9-11, and I've never once had someone tell me how much they love their records management system (RMS) (or most any other technology product their organization has purchased). Instead, I've heard—and seen—one example after another of how hard it is just to track down the information you need (since it's usually in multiple systems that are difficult to search), let alone quickly