You are here: Home Ideas Complete Accountability and Transparency For Every Process
 

Jump into the discussion

Here's a question to get you started:

What platforms for displaying and manipulating data are most likely to be relevant to a large audience of average citizens?

Complete Accountability and Transparency For Every Process

idea

What is the idea?

The Challenge: At the core of accountability and transparency is visibility into the status, information, and processes of each program. 

Unfortunately, most processes in place today are manual—this not only means poor visibility but manual reporting which leaves room for error. Plus, means of automating theses processes are too expensive and take too long to implement to satisfy the timeframe of Recovery Act guidelines.  This is not an option when speed is an important factor.

The Solution: Lean Business Process Management (BPM) offers a swift and pragmatic approach to process management. Lean BPM solutions make is simple to design and deploy collaborative applications quickly—these applications automate processes, capture critical data at every step, and provide full transparency across a process.
Full Audit History and Comprehensive Reports

Additionally, Lean BPM solutions are built for non-coders, people like Business Analysts, so they can quickly make changes to their collaborative applications (without involving technical resources) as guidelines continue to evolve.
Visual Designer for Rapid Implementation 
See An Example: Here’s an example of a Lean BPM application powered by Serena Business Mashups. It’s an application that manages the process for ARRA Project Submission, Review, and Approval. In true lean fashion, it was built in just hours, and deployed in minutes. You can check it out on Serena’s site at www.serena.com/go/arra.

Why is it important?

Manual processes make full traceability and accountability a nearly impossible goal. What’s more is that traditional systems for automating processes are expensive, cumbersome, and require costly technical resources.

Lean BPM solutions offer an alternative. With Lean BPM you design and deploy your own collaborative applications without coding skills. These applications bring speed to your organization with streamlined processes and have detailed audit logs built right in.

Agency Example: U.S. Office of Personnel Management
Over the last five years, OPM has been leveraging a Lean BPM solution powered by Serena Business Mashups. The collaborative applications OPM deployed manage the communication, collaboration and enforcement of its standard processes, such as legal reviews, purchase requests and employee on-boarding. In that timeframe, their Lean BPM solution has been instrumental in developing roughly 80 process solutions in the areas of health benefits, background checks, FOIA requests, OMB Circular A123 compliance, processes for federal acquisitions and IT defect and enhancement management.

Currently 60% of OPM employees use these collaborative applications and that is expected to grow to 100% in the next two years.

Many of the processes that typically took over a year to deploy in prior systems are now being deployed in less than two months. Before using their Lean BPM solution, managing processes was highly labor intensive and inefficient, and managers had very little visibility into whether projects were proceeding in a timely manner, or if resources were allocated strategically.

Now, with Serena’s Lean BPM solution, managers know where projects and processes stand and quickly identify and clear bottlenecks. Because workflow is automated and tracked, employees and teams are fully accountable for the work they perform and cannot bypass standard procedures.

Thanks to reminders, escalations and other notifications, employees know exactly what’s expected of them and when they’ve received ownership.

Automated processes built with Serena's Lean BPM tool are also helping OPM better manage Freedom of Information Act and Privacy Act requests. The agency processes 20,000 of these requests per year and must report on the results to the Department of Justice and on its own Web site.  Using Serena to develop a process to do that was far less expensive for OPM than an available commercial off-the-shelf product.

There are a host of agencies and departments streamlining processes with Serena’s Lean BPM solution. If you'd like to learn more, feel free to contact me.

Note:  This submission was provided by Serena Software, Inc. Serena Software was recently selected to participate in the "Six Strategies to Survive the Stimulus" event on April 29th at the National Press Club in Washington, DC. Additionally, Serena participated in the panel discussions along with GAO, OPM, and DOT.

Submitted by cbonamassa from Serena Software (Application Development) on May 01, 2009

This idea is now closed to further comments.

Current number of stars: 3
based on 4 votes
Tags:

2 Comments

Member comment

Lean business processes are important - in order to create efficiencies, processes must be streamlined.  Process and information go hand in hand.  Information is built off of data and is put into the context of experience to create knowledge; which in turn leads to improved decision making.  Making decisions blindly (without knowledge or supporting facts) or with partial knowledge, or by gut feel, or based on myth are dangerous.  For ARRA and Recovery.com to succeed, it will be critical that the right data foundation be implemented so that the evolution from data to knowledge and empowerment becomes real.  Most often, this occurs as an evolution rather than a big-bang event. 

However process modification streamlines the Federal government and its agencies, it will not necessarily accomplish the goal of improving Recovery.com nor provide detail around the ARRA investment the Federal government is making in the country's future.  That said, there is a symbiotic relationship between process management and information management and most importantly data management.  Give individuals access to the right, reliable, and accurate data when its needed in the form that its needed and processes must change.  The data will always tell the truth. 

Having worked at a leading data warehouse company for the past 10 years, I have seen many implementations fail because the business was unwilling to recognize the process change that was needed.  They implemented a system based on their historic view of what data warehouses are meant to do as a result of a limited functionality of some data warehouses available on the market that were being used for analysis but designed as a transactional system.  Similarly, I have seen many leading companies succeed when they adopted a powerful database technology and understood the value that insight would bring and did modify internal processes to support available when making a decision within minutes meant, vs typically hours or weeks later when the complete data became available.

Data is complex.  Management of data is complex.  Many have pointed out on this web site that variability of data formats, structures, users and usage will add to that complexity.   The government, therefore, will need to implement a 9-step process:

1. Identify the project's goals and objectives; what are the success measures?

2.  Identify the data that's needed to fulfill those goals and objectives; then identify goals and objectives you haven't considered yet and the data that's needed for those.

3.  Identify the ability to collect the data, the type of data, the timing of the data and the sources of data; Identify the gaps in the data

4.  Identify the users and uses of that data - in the short term, mid-term, and long term; what questions will be asked of the data?

5. Plan for the unexpected

6.  Identify the platform for the data that's scalable, and a structure that's flexible, so that the platform can change and grow as the users and uses change and grow - with minimal investment of resource and capital

7.  Identify the ways to access the data, how to display it, how to ensure data that should be secure is secure

8. Continue to monitor and grow the platform and users and uses over time

9.  Annually review the success metrics of the project and adjust as necessary

As the "centerpiece of the President's commitment to transparency and accountability," Recovery.gov must be reliable, fact-based and timely.  And it must be built on a solid foundation that facilitates process change and provides confidence to the public, the policymakers, and the president. 

 

Comment from mon351 at Teradata Corporation on May 02, 2009
Member comment

While I agree with BPM (this idea was previously raised by RSchrader), i would prefer to see lean six sigma rather than just lean.  Too often in government, i have seen lean efforts get rid of necessary controls and reporting because the process owners didn't see the value in making their program transparent or accountable -- it was seen as non-valuable paperwork burden.

Comment from maforman on May 03, 2009