Managed Mobility FAQs

The Managed Mobility Program offers agencies the information and resources they need to identify and procure centralized management solutions for mobile devices. Mobile Device and Application Management (MDM/MAM) and Mobile Lifecycle & Expense Management (ML&EM) solutions are the focus of this program to date.

GSA was assigned the Managed Mobility Program by OMB as a result of its core strengths in IT and networking, along with its leadership contributions to the mobility components of the Federal CIO’s Digital Government Strategy. Item # 5.5 calls on GSA to “develop a governmentwide mobile device management program” to support agency acquisition of Managed Mobility solutions. After initially addressing MDM/MAM, the Managed Mobility Program attention is focused on addressing Telecommunication Expense Management and Mobile Lifecycle Management (TEM & MLM).

The Managed Mobility Program does not create new acquisition vehicles. This program instead identifies and evaluates solutions that are currently on existing vehicles and can be procured today. The program creates and maintains a list of enterprise-class mobile management solutions that meet the greatest number of governmentwide requirements.

GSA will periodically re-evaluate both government needs/requirements and the marketplace’s ability to address those needs. Some agencies that are participating in the requirements and assessment selection are: ATF, CMS, DISA, DHS, DoD, DoJ, FBI, NIST, NOAA, USDA, USMC, and GSA.

Yes! And you can use the Managed Mobility program’s central repository, information, and staff to help you buy the solution that best meets your requirements.

See the Managed Mobility User Guides for details.

IT (non-mobile) equipment and services and IT (non-mobile) focused management solutions are not part of this program. No-charge or purchased mobile devices and associated service plans are part of the FSSI Wireless program, available at

The program utilized four key factors/areas to evaluate the solutions. These included Technical, Compliance, Acquisition Vehicle, and Experience/Scalability factors. Additional information and details about these factors are provided in the User Guides.

Solutions from OEM vendors as well as integrators were assessed. It is expected that as the market and specific solutions evolve, additional solutions will be assessed in the future.

The list of selected vendors and integrators is available at our Enterprise Mobility Industry Partners page.

Agencies are not required to procure solutions exclusively from this list. The solutions on the list have been carefully evaluated and would provide benefits including lower acquisition, implementation and management costs and risks. However, agencies are free to procure solutions not on this list. If agencies have requirements not reflected in this program, they are encouraged to forward those requirements to the Managed Mobility program office to better understand and share future requirements/needs with other agencies. In addition to the solutions listed below, other MDM/MAM and TEM/MLM partner solutions may also be able to meet an agency’s specific needs. No solution can be precluded from competition in compliance with the Federal Acquisition Regulations (FAR). Refer to the User Guide for more information about potential sources of supply and acquisition vehicles.

The repository can be found on our Resources page and contains all the information an agency needs in terms of what to consider when procuring an MDM/MAM or ML&EM solution, and potential pathways to procure them. It includes a User Guide, Potential Sources of Supply, FAQs, Fact Sheet, Governmentwide Requirements, White Paper, Success Story, and contact information for Program Expert and Staff.

The program adheres to several, including the following: White House Digital Government Strategy (DGS), dated May 23, 2012, Executive Order 13576--Delivering an Efficient, Effective and Accountable Government FISMA, as implemented through NIST SP 800-53 and DoDD 8500.1M FIPS 140-2 to protect, control and manage data in transit between the MDM and the device using FIPS 140 certified cryptographic modules.

You should first consider that generally integration costs are likely to outweigh any functional increase. See the User Guide for details.

Last Reviewed 2016-05-26