When the benefits of mobile working, flexiplace, etc. are offered before any discussion of releasing exclusive claims to a specific desk, the release of space is an uphill battle.
Short codes are great, but they are only available from a monopoly, and are expensive. Government gets a very small discount.
Long Codes are a viable alternative in some circumstances and are very inexpensive because of competition.
For government use of text messaging, consider using which is best for specific need. www.uslongnumbers.com
Begin with a focus for updating guidance (e.g. FIPS-201, NIST SP800-53) to call out for the use of strong authentication credentials (PIV, PIV-I, CAC) with mobile devices. Yes, the idea of attaching an additional device/sled to a mobile device in order to swipe,store, or scan your PIV/CAC card sounds cumbersome. But there is no reason why mobile devices can't be tapped to enable technologies such as cert-cloning/biometrics... more »
Of course everyone wants an AppStore for work.. government can have one without paying a zillion dollars to a large SI to build one from scratch. Start with a COTS product and customize.. one that can create web-services, orchestrate them and deliver data to mobile apps.. in other words build apps fast without a huge investment.
Before any major initiative can even be discussed, the US government MUST pass laws to protect online speech at the same levels of offline speech. This must include, but not be limited to: - Warrants to access GPS signals - Bans on data mining of personal data (including anonymized approaches) - Bans on roving wiretaps - Bans against Deep Packet Inspection - Strict limitations on acceptable uses of cookies - 4th amendment... more »
We also need to get the data right to reap the full benefits of mobile technology. This requires effective, forward-thinking inter-agency coordination on geospatial data to allow users to discover more information about places they visit with their mobiles. Users should be able to get apps that answer questions like: What watershed am I in? What is the soil type here? What are the demographics? What is the weather forecast... more »
Consider updating federal websites to incorporate responsive web design. It allows the arrangement of your content to change to fit the browser screen. Imagine a seamless user experience across federal websites and across a wide range of platforms. With responsive web design you get the same content on a laptop, a tablet, or a smartphone and it is displayed in a way that best suits the device you are using. This... more »
1. Cost per mobile unit for an agency---leveraging volume and smarter acquisition approaches should demonstrate strong savings and cost avoidance.
2. Cost per MB equivalent---Smarter acquisition and improved management of mobile assets should drive significant cost avoidance as usage increased and mobile data applications increase.
In view of the recently released DoD Mobile Device Management (MDM) procurement standards (which I believe is being used to encourage discussion for a national MDM solution),healthcare mobile computing quality challenges communicated by the DHHS & Healthcare Information & Management Systems Society last December (many concerns regarding data protection, privacy, security & growing acceptance of BYOD),it's apparent that... more »
While the current EA process does not yield the correct level of data it should be possible to have every agency report what it spends on plain-old telephone systems (POTS).
I suspect it would then be easy to do a cost analysis as to whether _all_ employees can go mobile, vs. allowing this to tricle out.
I've seen some talk in the press that the Federal CIO doesn't specifically think the Gov should be building apps.
However, I believe that it's critical for Gov to build apps, even just initially. Make the source free, get a nonprofit to own it later but apps and workflow will be two powerful tools for leveraging mobility for the Federal workforce.
End nodes (mobile devices in this case) are by far easier to penetrate than big, federal networks/clouds and are used in both risky and trusted areas (thus the End Node Problem). AFRL is developing (and will soon deploy) a authentication testbed any federal agency may use to evaluate (mobile) devices while accessing Google Apps for Government. Recommend the FMS include support for R&D of security since most commercial... more »
a contrarian POV: Desktop, PDA, laptop, smartphone, iPad, eyeglasses, brain implants, dial-up, Ethernet, WiFi, 4G, whatever... its all just a computer that becoming faster, more powerful, and more connected. Its all the same! We didn't have a Federal Dial-up Strategy, why do we need a Federal Mobility Strategy? The implementation of a FMS will prevent the end result sought - to make us more mobile. We cannot "take... more »
It strikes me that the USG has been incentivized by legislation (Telework Enhancement Act), innovation (plethora of mobile devices on the market), and sustainability (hoteling versus offices) to embrace mobility.
I propose senior executives take part in the mobility movement to prove it works.
Since each agencies have web content that is being used on day-to-day basis, extending the web content to Mobile approach helps to easily adopt mobile strategy for any agency. Based on the Page-Views of the Web-Content it will be easy to prioritize the content portability to mobile.