Federal Mobility Strategy Browse Popular ideas

Develop government-wide shared services catalog that houses code, application programming interfaces (APIs), and web-services that agencies and the public can easily access and use. This will encourage cross-sharing of data, code, etc. (emulating forge.mil – “forge.gov”).

Define and establish common infrastructure layers to support mobility (network security, device management, etc.).

Design government mobility products and services based on citizen and employee needs, behaviors, and desires.

Use telecom expense management (TEM) services to efficiently manage mobile and wireless expenses in agencies.

Develop government-wide (vs agency-specific) policies, guidance, metrics, and tools to support and accelerate mobility adoption (one privacy policy, one accessibility policy, etc.).

Create a government-only mobile app store to provide a separate distribution channel from commercial applications and improve functionality

Establish centers of excellence for common security services like app vetting, device/OS evaluations, certification and accreditation (i.e. mobile FedRAMP).

Create a Federal mobility reference architecture to enable adoption of common solutions (e.g., for BYOD).

Develop agency-level mobility plans that include government to citizen, government to business, government to government, and government to employee plans, priorities, and timelines for implementation.

Apps that work well for alerting first responders, apps that work well for collecting information, apps that work well for citizens requesting services all have specific and even unique requirements in their supporting infrastructures. Acquisition, governance, and other strategies for common application across agencies need to reflect those differences intelligently to maximize benefits of standardization while minimizing... more »

75% of enterprises now have "Bring Your Own Device' (BYOD) policies, according to the Aberdeen Group. Given the power, availability, and relative affordability of today's smartphones and tablets, the Federal government cannot keep up on technology and shouldn't have to. Instead, provide standard mobile data management (MDM) security protocols to allow employees to use their own, privately owned devices. Agencies should... more »

Don't force the technology worker to use one brand for a SmartPhone (Blackberry, Android, MS Windows, Apple). Leverage what the user is already buying. Give the end user a set amount of funds to purchase technology every three years.

Is the Federal government wants to truly go mobile, recommend eliminating all landline phones and replacing them with either employee-owned or government smartphones. This will not only save money, but make life easier for all Feds. Also, let's implement secure wireless systems to replace the old ethernet wired systems. This will allow more employees to work in less space, promote office-sharing, and provide true mobility... more »

Agencies need to stop overbuying. Agencies are buying the newest smartphones and then disabling many of the features for "secutity reasons". don't pay for what you will not allow employees to use.

leverage what other agencies(like the FAA) have already done and use a SaaS platform solution like AirWatch to manage mobile devices. This solution is a no-brainer...web based, role based access, easy push down of controls, remote wiping capabilities and metrics (that which is measured is improved)