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 »
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.
Everyone is building their own open database and hosting it on fragmented channels. This makes it difficult for authorities and the general public to find and use available opendata. A simple, standard design would be a 3-field record: key (16 characters), content (140 characters) and expiration date. This data would be hosted by the respective owners, but made available on a countrywide aggregating portal - such ...more »
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.
With implementation of the Affordable Care Act (ACA) in 2014, all consumers will be able to enroll in health coverage and apply for subsidies online. CMS will be issuing a prototype online application for use in states and should develop it in a manner that supports multiple platforms, including mobile. The effort should be supported by development of federal standards and protocols to ensure privacy, data security, ...more »
Why not create a framework for enabling the private sector (where most innovation comes from anyway) to contribute ideas/solutions in a free market fashion...publish an enterprise architecture based on industry standards (data models, security, identity provisioning, message formats) - you could even form an advisory council with key industry players to craft the EA. Then publish the API's for accessing the various agency ...more »
SLAs with mobility providers should ensure that cloud-stored user data and device-stored user data is always in sync with minimal user fiddling. This can be challenging technically with all the OSes and devices out there. Mismatched information could impede mobile productivity and increase help-desk calls.
Agency efforts to leverage use of mobile computing are rapidly evolving from… • Tackling Policy and Governance (are we going to deploy mobile devices and what controls should be in place?), to… • Implementing Device Management (actively managing use of deployed devices (e.g., MDM, identity management), to… • Deploying disruptive apps (getting apps done now for specific missions and using challenges and other new agile ...more »
encourage the industry to define a standard virtual mobile application platform spec. that all major device vendors can support and implement. Like a Java Virtual machine so a application can be built once and run on all devices.
Although the need for device management is a top priority, perhaps we need to elevate the discussion to encompass a Mobile Service Management framework and architecture. Device management is a critical component but only a subset to an end-to-end management solution. Device management is important as it will hopefully start to shed light on the true scope of the mobility management and security issues – it is not just ...more »
Whether using thin client mobile tablets to access official databases or smartphones with hypervisors to transmit the production information the system integrators see that connectivity, bandwidth, and latency all play a part in ensuring that real work still gets done.
The mobility strategy should establish circuit requirements for ensuring that people can connect.
Mobile workers will need new advance intelligent applications to accelerate decision making in the absence of direct supervisors they may have relied upon in the past. Whether managing projects, conducting assessments, verifying inventories, or validating component installations, some mobile applications will help accelerate the data collection. In other cases, where new data needs to be collected, an intelligent system ...more »
In projects the primary constraint is time. The beauty of mobility in managing projects is that task managers can overcome uncertainty and variation by having a mobile application for project execution which assists with managing their priorities. The mobile application which orchestrates and synchronizes all of the feeder chains and tells the task manager which task across all of the projects they must do now, helps ...more »
Mobility offers the federal workforce an unprecedented and exciting opportunity to innovate, streamline processes, eliminate redundancies and integrate departments and agencies , but the key to success I believe is connection and integration. In Connection, the mobility strategy should assess organizations and functions within two categories, connection-oriented and connectionless. Connection-oriented organizations ...more »