U.S Marshals plot data strategy
- By Adam Mazmanian
- Jul 10, 2014
WHAT: The Marshals Service is in the market for an enterprise upgrade.
WHY: The agency that runs the federal witness protection program has some pretty strict security needs for a planned data integration platform.
The Marshals' needs for data processing, analytics, and storage are expected to grow, and users across the 94 districts and headquarters need access to a variety of data, including documents and biometrics. There's personally identifiable information that needs a high security storage solution -- federal witnesses, jury information, DNA evidence and more. The agency also needs analytics and geospatial tools to maximize efficiencies and logistics across its transportation line of business -- the U.S. Marshals Service moves 280,000 prisoners each year.
Marshals aren’t in the big data business, but their needs are expected to increase over the current capacity of 15 terabytes, according to a July 8 request for information posted on FedBizOpps. The word "cloud" doesn't appear once in the 14-page RFI. Instead, the document refers to "an integrated solution which may involve more than one vendor," that includes commercial, government, and open source elements.
Plans include the integration of agency financial data with in the solution, to support decision making. Any system must also be able to control and track access to records.
Click here to read the RFI.
Adam Mazmanian is executive editor of FCW.
Before joining the editing team, Mazmanian was an FCW staff writer covering Congress, government-wide technology policy and the Department of Veterans Affairs. Prior to joining FCW, Mazmanian was technology correspondent for National Journal and served in a variety of editorial roles at B2B news service SmartBrief. Mazmanian has contributed reviews and articles to the Washington Post, the Washington City Paper, Newsday, New York Press, Architect Magazine and other publications.
Click here for previous articles by Mazmanian. Connect with him on Twitter at @thisismaz.