Mobility has brought home the need for an interoperable data strategy for the Federal Government that is simple and allows for an agency to express its vocabulary and usage through an HTML5 type of interface. There are numerous projects being developed and NIST needs to stand up and be counted in this exercise. Leaving it to OMB reference models will continue to hamper efficiency.
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.
Develop a platform that will allow citizens to consume government services.
The platform should support:
* Service Aggregation, Discovery & Distribution
* Allow citizens to provide feedback on a service
* Host Data Dictionaries & API across agencies to allow small biz, citizens to develop apps (spark innovation)
* Provide Governance & Policy to manage the citizen engagement
Consistent policies need to be created across like agencies like civilian and DoD that allow all like agencies to implement areas like mobile security the same. This will provide economies of scale cost savings allowing the same or similar devices and software. It also allows for a reference implementation that can be used by all agencies.
If Federal end users are being completely defined by their mission and lifestyle along with all the mission data needed to accomplish their role; there will be a large increase in productivity of the government. Smart Lean government will be defined by a series of tiny mobile apps. These apps will define true end to end service desire the government has tried to fulfill for years.
Instead of creating a mobile version of an existing web capability, innovate to create experiences only made possible with mobile technology.
Require the justification of the experiences being created as a result of the mobile solutions, to help drive quality and prevent a flood of mobile apps that offer little value add.
What if...? The Federal Government is the legal owner or tennant of tens or hundreds of thousands of servers, network and storage devices and probably millions of desktops and laptops worldwide... Imagine if a mobile app available on all pupular mobile devices could automatically scan, identify and assign location to every federal IT asset with a barcode. Then it could communicate that encrypted information over existing ...more »
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.
Mobile technology has become so essential to all aspects of the government mission. Organizations should give it mission critical status and develop detailed mobility IT strategies and long-term mobility roadmaps. Now is the time to think about priorities and objectives for a mobility strategy. By leveraging current mobile technology investments, as well as those in enterprise applications, organizations can create a ...more »
Mobile devices should have a minimal footprint. In order to this, use cloud computing to do most of the heavy-lifting and don't have applications that only work on one platform (hardware or operating system).
A federal identity management standard combined with set of mobile applications for communication (web, voice, text, e-mail, video), collaboration (online document sharing), productivity (word processing, spreadsheets, presentations, online publishing), HR, travel and expense reporting that would empower all federal workers to fully support their mission at any time from anywhere on any device.