Archive for Customer Success Stories

A Top 10 Pharmaceutical Leverages CorasWorks for Program Management of $200M Global Product Serialization Initiative


The pharmaceutical industry is going through a significant change in manufacturing and supply chain management driven by emerging global government mandates for them to “serialize” their products.  Each unit of product must have a unique ID that can be tracked through the full supply chain to the end user customer. This is to insure quality, to enable tracing, and also, to suppress the use of counterfeit drugs (estimated at 10% of the worlds’ drugs).  The mandates have been coming out across the globe over the last few years.  The US is on the verge of putting their “mandate” in place this year.  (Click here to learn more about pharmaceutical product serialization.)

In this article I will look at how our customer, one of the top 10 pharmaceuticals, used CorasWorks to create a Program Management solution that is used to manage their $200M global product serialization manufacturing change program.  I will also address how the process worked as this story is a great example of how customers are able to achieve breakthrough results without the risks, costs, and time delays that are common for most enterprise application projects.

The Challenge

This customer is a very large manufacturer of pharmaceuticals – one of the worlds largest.  These mandates from around the world are requiring them to update all of their manufacturing lines to support the unique ID serialization requirements for each unit that is produced.  Different mandates from different countries/regions also have different requirements.  This process will cost our customer 200 million dollars over the next five years.  They will need to upgrade more than 100 different manufacturing lines in 400 different projects around the world in more than 20 countries.

The objective of our customer was to be able to centrally manage the program across the globe.  They had a strategic team in place to drive this initiative globally.   They had very precise requirements such as:

  • They needed top down management visibility and the ability to then drill down in details.
  • They wanted to be able to see all of the projects by a) defined KPI’s for the b) defined stages of work.
  • Their process requires that each local manager provide updates on each project each month.
  •  Most projects actually had two workstreams, so two different updates, for a total of 400 managers providing updating.
  • They wanted the ability for comments for each update.
  • These updates drive the KPI’s from the bottom, up the stack.
  • There were very complex KPI roll-up calculations so that KPIs would cascade upward from the base project to the top of the Mandate, Geography, Country, Product, etc.
  • The customer then wanted to be able to see where everything stood by different pivots such as by Mandate, by Country, by Product, by Workstream, by Line within in a real time, interactive interface.

The customer had detailed, application specific requirements for the Program Management system. Yet, time was short.  Some projects were already under way, so they wanted the system relatively quickly targeting about 4 months. They had evaluated options of custom development however the cost, risk of delivery, and length of time to delivery deterred them from this option.  They also looked at leveraging other owned Project Portfolio Management systems, however, they needed very precise features and in effect this made the use of these systems as risky as custom development.

So, the challenge was how to:

  • get a Program Management system that met their very precise requirements
  • in a relatively short time frame
  • at the lowest cost possible and without “breaking the bank”
  • with an acceptable level of risk of delivery
  • that would support changes as the program evolved and lessons were learned
  • and that was acceptable to IT today and supportable over the 5 years of the program.

The Solution

This customer uses SharePoint 2010.  In fact, they are in the Top 100 of SharePoint deployments supporting more than 80,000 users across four global regions.  They have adopted an Enterprise Shared Services Environment (ESSE) model in which they have a common infrastructure that is shared across all global geographies, all business groups, and, all employees.  They have three different farms (server environments) for different categories of work.

  • The Enterprise Shared Services Environment for those applications that do not require any custom compiled code.
  • A Custom Environment that allows custom code but is much more expensive to manage.
  • A Regulated Environment that is certified for regulated processes and information such as Clinical Trials.

They have been a CorasWorks customer since 2004.  The CorasWorks  v11 Work Management Platform is part of the infrastructure on the Enterprise Shared Services Environment available to all 80,000+ users.  The complex requirements of this Program Management application were more sophisticated than just about any other application running on ESSE.  However, they believed that it might be possible to build and deploy it on ESSE.  This would mean that it would have to be created without requiring custom coding, just leveraging the CorasWorks Work Management Advanced Configuration Tools.  If it worked, it would also mean that they could meet all of the challenge criteria noted above.

Working with the customers’ Service Delivery Team for the manufacturing group (that delivers applications to that group on ESSE) we did a quick pilot to simulate the applications’ operating requirements in the ESSE environment.  This was successful and the business customer decided to go with CorasWorks software and CorasWorks Professional Services to build the application on the ESSE environment.

This was a joint application development project.  The Service Delivery Team had built other applications using CorasWorks within ESSE so they were familiar with the core capabilities of CorasWorks.  They were able to work closely with CorasWorks on the design, the requirements, the testing, and changes.  They also handled the interactions with the business group.  The teams approach was an Agile methodology with the objective of having an early working solution in place, that would be built through sprints with user input.  In sum, it was a highly collaborative project between CorasWorks, the customers’ Service Delivery Team, and the business user group.

The Result

The base application was deployed for initial testing within 60 days.  The ability to quickly get the base application with a full information data set up and running was important for real time user input and changes.  It went through a series of sprints for additional phases and changes.  In addition, the application was re-factored three times in order to accommodate the changes and stay within the specified end user performance limits.

In sum, within 5 months the system went from development to enterprise production within the ESSE environment. Comparing the results to the challenge criteria stated above, the system was delivered:

  • meeting the specified technical requirements and the ones that came up through ongoing changes
  • almost within the time frame (it actually took an extra month to finish the project due to elapsed time delays with changes, user testing, and data loading) – but the project was still 2x faster than alternatives had been estimated
  • within the specified budget – that was about half of the initial estimate for competitive alternatives
  • the risk was mitigated by the known factor of CorasWorks capabilities on the ESSE environment
  • the resulting system is fully supportable by the customers’ Service Delivery Team since it is built on the open standard CorasWorks platform
  • and IT was already supporting ESSE and CorasWorks and will continue to support it as part of their global ESSE environment

My Wrap Up

This customer now has the capability to manage the global product serialization program.  They are in a great position to work towards success.  The program, an important one for them (remember counterfeiting is 10% of drugs), is also very important to the health and safety of all of us.  By investing to put the proper, well specified, program management system in place to support their defined process they have decreased their risks and increased their probability of success because they are providing a lot more visibility which drives greater accountability for results.

The General Challenge.  Most business-driven Program Management solutions are very custom.  It is the nature of the beast.  It is also a key to competitive differentiation.  Your programs/initiatives tend to be your big value creating or risk reducing activities.  But, it is very difficult and almost counter-productive for a vendor to try and build a general product for this purpose.  There are some COTS Program Management systems, but, if you try to use them for a significant program like this one you’d have to basically rip them apart to deliver on a typical set of requirements.  The unique flexibility of the CorasWorks Work Management platform makes it a very effective way to deliver on these custom Program Management applications.  As shown in this example, effectively they used a COTS product (CorasWorks) on an existing enterprise shared services (ESSE) platform to create a very custom Program Management solution without requiring any new custom compiled code.


$1B+ Top 25 Government Contractor Enhances Contract/Program Management for Customer and Supplier Interaction

Hub-Spoke PM

This customer is a top 25 Federal Government Contractor with more than $1B in annual revenue.  They are an existing CorasWorks customer using CorasWorks in their Extranet and Intranet work environments running on Microsoft SharePoint 2010.  This is a story of how they have enhanced their Program Management environment (Contract, Programs, IDIQs, Task Orders, etc) to support managed, interactivity between their Employees and their Customers and Suppliers.  The key interactive process they are focused on is Customer Reporting, primarily CDRL deliverables.  The article will describe the design of their solution, what we call the Hub and Spoke design, which enables this managed, configurable type of “role-based” interactivity. 


They have defined and are building out a broad Integrated Program Management System (IPMS) with multiple sub-systems.  They are doing this leveraging their SharePoint environment.  They are using CorasWorks for specific sub-systems of this environment such as IDIQ Task Order Management.  They are also using CorasWorks to enhance certain custom built sub-systems such as the subject of this article.

They had a version 1 of a Program Management sub-system that is targeted to encompass more than 1,000 contracts/programs when fully rolled out.  Their objective is to be able to manage the work for each contract/program that they have as part of a unified system.  Like most SharePoint systems, with v1, they had a basic framework with a Program site at its core.  This is where the Program Manager and internal team could collaborate.  But, the v1 lacked the key capability to interact with Customers and Suppliers, particularly around CDRL deliverables. With customers, they wanted to structure the Customer Reporting (primarily CDRLs) workstream.  They also wanted customers to be able to make requests.  With Suppliers, they wanted them to provide their reports to them in a structured way which then became part of the reporting to customers.  They also wanted to be able to interact with the Suppliers.

Their key design objective was for the internal employees to be able to see and manage all of the activity, but, the Customers and the Suppliers would only be able to see, contribute, and act with information/tasks that were specifically available to them.  In addition, they needed flexible.  Effectively every contract/program is somewhat different.  So, the system had to accommodate the need to make changes at the Program level to meet the specific needs of the customer.


They leveraged CorasWorks to get to their new version 2.  For this version, they shifted the system to their Extranet environment.  This reflects the key recognition that program interactivity between Employees, Customers, and Suppliers simply has to live outside of the Intranet.   

As above, the core new process was the management of the CDRL deliverables for each Contract/Program.  The general design is as follows:

  • Each contract/program has a site – lets call it the Program hub.  This is where the internal employees work.
  • When a Program Hub is created they can auto-provision a separate Customer site and one or more Supplier sites as required.  We refer to these as Consoles.  They are effectively Spokes of the Hub. 
  • The Program Manager manages their work and interactivity with Customers and Suppliers through the Program Hub.
  • With CDRLs, they define each CDRL in the Program Hub.  Effectively, it is a task with a due date that can be tracked and managed.
  • When it is time, they prepare the reports, which might include interactivity with Suppliers.
  • The CDRL deliverable is then “published” for access by the Customer.  They are automatically notified and can go to their Customer console to view the information and interact. 

In addition to the enhancement around Customer Reporting, they enhanced a number of other features. Two key enhancement were:

  • Integration with their external ERP system to provide real-time updates to the Program Manager.
  • Task (Action Item) management for the Program members with work automation.


So far, they have brought up more than 100 Contracts/Programs into the new system.  For each contract/program the CDRL process is managed as above.  Some Programs don’t have Suppliers, while others do.  The full cycle is now tracked (to insure completion of the deliverable) and documented (for auditing).

The flexibility that they wanted is achieved just by their use of CorasWorks.  This enables the Program Managers to modify the CDRLs that are delivered and to turn on and off features as required by the contract.


Wrap Up and Summary

This solution is a good example of how to leverage CorasWorks to enhance a system that you already have on SharePoint.  I’ll drill down into two important capabilities that make a big difference in the success of this solution.

Cross-Connect – CorasWorks has the native capability to enable you to See, Contribute, and Act across SharePoint Sites and SharePoint Site Collections.  This “cross-connect” capability enables the Hub and Spoke, interactive design that was used for this solution.  Effectively, you are creating role-based “work consoles” that only enable uses to see, contribute, and act as you determine.  This means that you DO NOT have to give these external parties direct access into a SharePoint site.

Feature Flexibility – A key benefit of their use of CorasWorks is the feature flexibility on a program by program basis.  If you have a fixed, custom built, proprietary system, then, it would either a) be very difficult to change to accommodate each customer/program (unlimited permutations) or b) be very costly to set up and maintain separate systems for each program and customer to accommodate their specific needs.  Using CorasWorks, the customer has the flexibility to add new interactive features on a program by program basis.  These features become part of the framework and may be simply turned on and off (by business users such as the Program Manager) to meet the needs of the Customer and/or Supplier.  Features enabled for one program do not affect other programs.


Shared Contract Work Order Management System for Federal Agency and Contractor

How can we make the work on contracts more efficient and effective?  One powerful way is to enable people from the Federal Agency and the winning vendor Contractor team to work together in a shared environment to manage the work.  In this article, I’ll review a work management system that we just delivered that does just this.

The story is about how we were able to take our off-the-shelf IDIQ Task Order Management solution and rapidly apply it to meets the custom requirements of an RFP from a Federal Agency for a shared Contract Work Order Management System.  The story is partially about our solution, but, it is also about how a Federal Contractor can leverage CorasWorks (software and people) to outdo the competition, win business, and, stay close to their customer.


A civilian Federal Agency released an RFP as a small business set aside valued at about $100M over its term.  It is an outsourcing contract for IT-related Services.  The format of the contract is a single-award IDIQ with general Task Orders and specific Work Orders supporting about 30 core work areas.  The Work Orders are the primary method for getting the work done.

The new wrinkle is that the agency required, as part of the proposal, that the vendor provide a shared, collaborative, online work management system enabling the participants from the Agency to work with the participants from the Prime contractor and their team.  The system had to support the release of specific Work Orders that would come in as Agency requests, get released for estimates, get estimates, and drive the approval process.  In addition, the system had to support visibility into the work in progress including planning, tracking the work, ongoing collaboration, issue flagging, and reporting.

The big practical challenge for the Prime contractor and team was that the Agency required the vendor to have the system up and running on the date of submittal of the proposal.  It would be a live system, accessible by the Agencies review team during the proposal review phase and would then be migrated post-award.  This was a major compliance challenge that could have doubled or tripled the cost of submitting the proposal.  And, whatever system they proposed, they were going to have to live with for the duration of the contract.


A member of the Prime bidder’s team was a Top 10 Federal Contractor that is a CorasWorks customer and was familiar with our IDIQ Task Order Management solution that runs on Microsoft SharePoint.  This solution is designed for use within Federal Contractors, primarily in a multi-award situation, to manage the process of responding to task orders.  Upon review, it was decided that this solution would be the base for the required Work Order Management System.  The primary reasons were:

  • the core off-the-shelf feature set is very close to the needs of this contract work order management system
  • the configurability of CorasWorks would enable the team to deliver the required demonstration environment at a very reasonable cost and on time
  • CorasWorks is an open application environment, ie., not a proprietary code base, and thus, it be custom-configured, enhanced, and extended, by the Contractor team, to meet ongoing needs.


The solution was implemented by CorasWorks with our bidding team of the Prime Contractor and subcontractors.  We started with our off-the-shelf IDIQ Task Order Management solution running in a CorasWorks provided online environment.  We then applied it to the Agencies requirements.  This work took a couple of weeks of configuration and testing. Some key requirements for the system were:

  • The system was designed to support Federal Agency participants and Contractor participates within a common, online collaborative work environment requiring appropriate control of permissions and work action authority.
  • The system was setup up to support two workstreams (distinct stage-based processes).  One for Work Orders that cover the core contract work areas (the bulk of the work).  The other for new Task Orders that would be released to expand the scope of the contract.  Each workstream was a bit different.
  • Each workstream had to support 2 work Phases.  One was the Approval Process with the key stages of Request, Review, Estimating, and Approval.  The other was for approved work orders, Work In Progress, covering Working Planning, Work in Progress, and Closeout.
  • The system needed robust reporting to show process metrics and exception reporting across the life cycle of work.
  • Each work order or task order has its own Workspace that contains the detailed information for the item across its life-cycle and supports the collaborative activity required to drive the item forward.


The system was delivered within cost and exactly on time which was objective one for compliance and is now in ongoing support mode.  The system met the compliance requirements of the Agency and included an interactive checklist to make it easy for the Agency to validate compliance.  While this system is not the core reason why the Agency will award the contract to a vendor team, it was perceived as a major reason why a team would be knocked out of the competition.

In addition, after working with the system, the Prime Contractor is now in process to procure CorasWorks for internal use and to leverage this Contract Work Order Management system to create a standard way of working on each of its major single-award contracts and for use for its IDIQ task order management.

My Comments

It is not uncommon for CorasWorks to be used to bring up collaborative work environments that bring together participants from Federal Agencies, Prime Contractors, and, contract teaming partners.  In fact, this particular agency has had experience working in similar CorasWorks-based environments for two other major contracts/programs with another Top 10 Federal Contractor (see Large Federal Contractor Drives Customer Intimacy and Value with Dedicated Program Workplaces on SharePoint).

However, this particular application of our IDIQ Task Order Management system was new.  Instead of focusing on winning the work, as in the typical multi-award IDIQ scenarios, it is all about getting the work done with visible participation of all members (Agency and Contractor).  Our existing solution provided 90% of the base system allowing the team to get where it needed to be very quickly.

I can see the use of CorasWorks for Contract Work Order Management in three scenarios.

  • One where a Federal Contractor uses it just within their organization and working with teaming partners to manage work requests on their single-award contracts.
  • Another is for a Federal Agency to manage their request processes within the Agency and the interaction with their vendors.
  • The third is an integrated, shared work environment as in this scenario.

I believe that this last scenario, the integrated work environment, is the top of the food chain in terms of driving efficiency and effectiveness of the work delivered on Federal Government contracts.  We’ve seen it before and it is proven.  However, you need an enlightened agency and a contractor that can handle the transparency to make it work.  Like any collaborative process, it takes the team some time to learn how to work together and how they work will continually evolve as they learn.



See additional articles for IDIQ Task Order Management in this blog.

Visit CorasWorks IDIQ Task Order Management for product information.

New Solutions and Case Studies for Federal Contractors

We continue to enhance our support for Federal Government Contractors.  We just updated the Federal Contractor microsite section of our web site.  Assuming that you have been there before, press CNTRL-F5 to refresh the content.

We now highlight 5 solutions for Federal Contractors.  We have 6 new Case Studies for a total of 10.  The solutions are:

  • IDIQ Task Order Management
  • Capture and Proposal Management
  • Program, Project and Portfolio Management
  • Idea and Innovation Management (new)
  • Shared Services Work Management Environments

For an overview of our Federal Contractor vertical in 2012 and solution plans in 2013 see the following article:

CorasWorks’ Federal Contractor Business Grows 75% in 2012 Fueled by Accelerating Industry Competition–Review and 2013 Plans

Do More With Less and Do More for Less

The new solutions and case studies are evidence of our core message to Federal Contractors which is how we enable them to Do More With Less (the competitive business value) and Do More For Less (our cost improvement value proposition).  As we invest in this area and “standardize” the solutions, our value proposition just gets stronger.

The key is that CorasWorks on SharePoint is a platform approach that is enabling Federal Contractors to get great leverage through a Shared Services model.  Once you have the platform in place, any and all of the solutions we offer or that you build can be dropped in, natively integrated, re-purposed, enhanced and extended.  It just works.

Make sure to look at the 2 case studies under “Shared Services Work Management Environments”.  These given a sense of how this approach has worked for a 1,000 person and a 20,000 person organization.


CorasWorks’ Federal Contractor Business Grows 75% in 2012 Fueled by Accelerating Industry Competition–Review and 2013 Plans

In 2012, we started our Federal Government Contractor practice.  Federal Contractors (including Aerospace & Defense providers) have been a significant part of CorasWorks’ business since we began in 2003.  In 2012, we created a dedicated team to focus on this industry and build and deliver industry specific solutions.  With the increased competition in this industry in recent years and the threat of the Fiscal Cliff and Sequestration in 2013 – we figured it was the perfect time to engage deeply and help our customers Do More for Less and drive their competitive position.  We focused on solutions for the internal operations of Federal Contractors.  In this article, I do a review of our work in this industry in 2012 and provide you with a heads up of our plans for 2013.

2012 in Review

  • Our business with Federal Government contractors for internal use grew 75%, making it our fastest growing industry segment last year
  • We served a broad group of Top 100 Federal Contractors such as Lockheed Martin, General Dynamics, Rockwell-Collins, HP Enterprise Services, Booz Allen Hamilton, BAE Systems, Serco, Chenega and Salient.
  • We focused our industry-specific solution investment in solutions for Business Development (BD) Operations, particularly IDIQ-based activities for Prime and Sub-contractors – a major area of intense competition in 2012 and going forward.
  • We expanded our BD solution set to integrate with existing Proposal Development applications and introduced solutions for Capture & Proposal Management providing comprehensive visibility and process management for BD operations
  • We began the process of cross-industry pollination, by bringing solutions from other industry customers into Federal Contractors such as Idea Challenge Management and Work Management for Engineering and Resource Planning and Program Management/Delivery based upon the CorasWorks Project Portfolio Management solution
  • We continued to expand our footprint in the Federal Government (Military and Civilian) with large deployments in the Navy, Army, Air Force and Marines that enables Federal Contractors to leverage CorasWorks on SharePoint to deliver more competitive services and systems to their customers.

We learned a great deal more about the industry, the solutions, and the way of working within Federal Contractors over the year.  It is pretty clear that the internal operations of Federal Contractors have a lot of room to benefit by increased efficiency and effectiveness.  The BD area of IDIQ work was a real winner where most customers have a) older, legacy systems or b) nothing but email (NBE).  We’ve taken this segment to a new level in terms of lower cost and higher efficiency and effectiveness.  The best testament of our success with BD solutions and in other Federal Contractor business functions are our Customer Successes.  You can read about these by looking at articles of this blog (See Category of Federal Government Contractors, with 9 articles, or by a specific solution Category) or reading about our Solutions and Case Studies at our Federal Contractor micro-site of the CorasWorks web site.

What’s Ahead in 2013

Sequestration still looms. Continued increase in competition is a fact.  To help you compete, we are pushing our Collaborative Work Management solutions for Federal Contractors forward in 2013 in the following areas:

  • We will continue our focus on solutions for BD Operations.  Here you simply have to be at your best.  We will continue to move our IDIQ oriented solutions forward to make our customers the top in internal efficiency and effectiveness and the robustness of partner engagement.  We are also deepening our integration and support for Capture & Proposal Management activities and integration with third-party legacy applications for CRM (notably Deltek GovWin’s CRM), ERP, HR, and Contract Administration.
  • We are “verticalizing” the CorasWorks Project Portfolio Management solution to more specifically support work for Program Management, Delivery and Operations in Federal Contractors (what you do after you win the business – the downstream activities).
  • We are deepening our presence in the Engineering business function by bringing Engineering solutions from other industries into the Federal Contractor space, such as Engineering Work Management, Configuration Management, Idea and Innovation Management, Resource Planning and Demand Management.  This need is being accelerated as our customers start separating their services business from their systems businesses and are looking to set new benchmarks in the management of globally distributed engineering resources.
  • We will continue to expand our set of solutions for cross-functional activities with corporate functions such as HR, IT, Finance, and Legal and cross-pollinate these solutions into our customer base.
  • We are putting new programs in place to help our Federal Contractor customers build CorasWorks competencies internally that help them be more competitive when delivering solutions to Federal customers that leverage SharePoint – a growing segment of the services sector.

CorasWorks – At Your Service

In 2013, it is not going to get any easier to win business or deliver it profitably.  The way to succeed is by getting better and being more innovative.  As part of this we feel that you truly do need to a) eliminate the noise of redundant, ad hoc, wasted activity, b) break the silos, and c) provide the visibility and embedded collaboration to focus resources when and where you need it.

As innovative leaders in Collaborative Work Management solutions on SharePoint and with our focus on Federal Government Contractors we can help you get you where you want and need to be – more quickly, at less cost and with less risk.  We look forward to serving you in 2013.


$250M Federal Contractor Leverages CorasWorks to Bring Together Integrated Business Development System

This story gets to the heart of how CorasWorks can be leveraged to bring together distributed enterprise systems and integrate them to create a new corporate capability.  In the article, we’ll go through the steps of how a fast-growing $250 Million revenue Federal Contractor used CorasWorks to put in place an integrated work management system for Business Development.

The Situation

Over the last year, our customer started investing in, winning and acquiring a number of new IDIQs as a Prime Contractor. They see the IDIQ Prime vehicle as a key strategic revenue driver.  They wanted to put in place a way of working that would provide Program Managers with an efficient and effective way of managing Task Orders from these IDIQs to win business.  The ideal solution would allow them to support multiple different IDIQs that were managed in the business groups, yet, leverage a central Proposal Management center and other corporate systems.  They wanted the best of both worlds: centralized and distributed.

Like most Federal Government Contractors, they had a stable of the standard, siloed, departmentally managed systems.  The diagram below lays them out: CRM, Proposal Development, HR Recruiting/Resumes, and Contract Management.  The question was how could they implement a new capability for managing the IDIQs and Task Orders that would bring these different systems together into an integrated system.



The Solution

The solution was to leverage CorasWorks on SharePoint.  CorasWorks v11 software and solutions were used to create the new core IDIQ Task Order Management system and to integrate, enhance and extend the other systems.  Microsoft SharePoint provides the foundation for data, security and administration.

How They Did It

The following goes through the sequence of steps of how they brought it all together.

Upgraded Proposal Development System

Their existing system was focused on the proposal development process based upon native SharePoint and the Lohfeld Consulting Group’s Capture & Proposal Management methodology.  They upgraded their existing system system to become a CorasWorks-based system while maintaining the Lohfeld methodology.  This new sub-system became more efficient and more easily opened up to integrate with the other elements of the overall system (see this article for the Top 7 Enhancements of Capture & Proposal Management Systems using CorasWorks).

Implement Core IDIQ Task Order Management System

They then implemented the standard CorasWorks IDIQ Task Order Management system on SharePoint.  This includes IDIQ Program Management sites for the Program Managers to manage the overall process and the integration working sites for each task order.  They also implemented a standard design for the Teaming Partner Portal and Engagement of Partners, and, set the standard for customer portals for reporting.

Integrating with GovWin CRM and Proposal Management

Next was the integration of the core systems that are part of the primary work stream.  In this case, they wanted to insure that their GovWin CRM was the source for all opportunities including new Task Orders. Leveraging CorasWorks the CRM opportunities were integrated into the IDIQ TOM system.  Then, instead of using separate Task Order working sites, they used the CorasWorks-based IDIQ TOM system to auto-provisioning working sites within the Proposal Management Center.  These working sites now became a mix between Task order working sites and Proposal Development sites so that they would have a single site that would support the life cycle of a Task Order.

Tying In Supporting Systems

The HR and Contract Management systems are supporting systems that are commonly leveraged during the process.  During the process of working on Task Orders and Proposals, they need to interact with the HR recruiting staff who leverages their custom HR resume system.  In addition, they integrated with their Contract Management system to access information and store completed contracts.

The Resulting System of Systems for BD

With the approach above, they successfully deployed this system of systems for Business Development and are off and running.  The Proposal Center manages more than 400 proposals/task orders per year.

The result is that the Program Manager is able to get a 360 degree view of an IDIQ and each Task Order from a single CorasWorks Console.  They can manage the process and access the relevant information in supporting systems.  In addition, a key element of the overall design is that they are able to rapidly create new IDIQ sub-systems that are tweaked to the needs of each Program Manager.  Thus, they do get the best of both worlds: a localized solution for each IDIQ and the centralized management of separate departmental systems.



See additional articles for IDIQ Task Order Management in this blog.

Visit CorasWorks IDIQ Task Order Management for product information.

Full Service Proposal Center of Federal Contractor Driving $250 Million a Year in New Business

Many SharePoint users make use of team sites to manage individual proposals – primarily leveraging basic document management.  Most don’t get much further.  This leaves a vast untapped potential for driving Business Development results and efficiency waiting to be exploited.  Using CorasWorks, leading companies are making it happen…

One of our customers is a billion dollar plus Federal Government Contractor.  A few years ago they acquired a company that came with a proposal management system built with CorasWorks on SharePoint.  They adopted it and have since enhanced and extended the system to serve as a full service Proposal Center supporting 400 proposal projects per year, in a 24/7 operation, that drives $250m/year in new business.  In this article, I’ll provide an overview of their Proposal Center system, the business impact, and, how they are taking it even further.


The Proposal Center System

The original system was built using CorasWorks on SharePoint 2003.  It went live in 2005.  When our customer bought the company that built it – they got it.  It was decided that this system would become the core for a new Proposal Management Center that would offer their service to all business units of the company and that would provide a flexible set of services to meet varying business needs.

NOTE: This decision was surprising.  At the time our customer was a complete SAP shop – even for their Intranet/My SAP portal.  The company they acquired used CorasWorks/SharePoint for their Intranet and many other operations.  Our customer killed everything SharePoint from the acquired company, except for this proposal system. This one app has kept the SharePoint flame burning in the organization which over the years is now starting to more broadly adopt SharePoint.

At the core of the Proposal Center is a good solid proposal development system based upon SharePoint.  Each proposal or proposal project is a SharePoint site (at least one) managed as part of an ongoing portfolio of work.  The native SharePoint capabilities have been enhanced with CorasWorks to automate many aspects of the proposal life-cycle and flesh out the system to support a range of different levels of business development capture and proposal projects and information resources as follows:

- Standard RFP Responses – The standard proposal project is a full response to a government RFP using internal resources.  For this, they use a standardized color review process.  The system structures the work, manages the content, and, keeps everyone up to date via email notifications and workflow.

- Smaller BD Projects – It also supports smaller projects.  Sometimes a business group may only require input on the Executive Summary, a short response to an RFI, Past Performance information, or work on a Pricing matrix.

- Managed Knowledge Resources – In addition to managing the projects, the Proposal Center has become a central source for standardized information such as Past Performance, forms, policies, proposal snippets, pricing information, etc.  People working on proposals can “fetch” relevant information from various managed KM repositories and pull it into the working site.  Over time, the Proposal Center has built up an extensive set of knowledge that is reusable as well as knowledge about the process and results of all Business Development operations activity.

- Large Teamed Responses – Further, the system is designed to also support large proposals involving a broad number of teaming partners.  Leveraging CorasWorks and its “secure separation” design each teaming partner is able to interactively participate within the system but only sees the information that they are supposed to see.  Yet, the core company proposal team gets a holistic view of all of the activity.

- IDIQ Task Order Responses – Last year, a new module was added to the system to support IDIQ Task Order Management where they serve as the Prime contractor.  The Task Order responses are managed through the system.  As IDIQ Task Orders, these have unusually short deadlines, such as 10 days, and require an expedited process.

All of the different types of projects are managed via overall portfolio dashboards and work consoles that allow the business development managers to see, act, and contribute as needed.  It provides extensive real-time reporting across the system for business development executives, program managers, and, overall executives.

There are also many unique features to the system that were created to drive productivity within the specific operating environment of our customer.  One of these is the integration with the customers’ SAP HR system.  Our customer responds to a large number of service-oriented RFPs that are dependent on people. Thus, easy access to resumes and integration of vetted individuals into the proposal is a big productivity boost.  Using CorasWorks, the customer integrated with their SAP HR system which allows them to locate people/resumes, which when selected are dynamically formatted based upon pre-defined templates to be incorporated into their proposals.

NOTE: CorasWorks v11, our latest platform release, contains an advanced toolset enabling customers to integrate with Deltek Costpoint, Deltek GovWin CRM, SAP, Oracle Siebel, MS CRM/Dynamics, Taleo HR, Peoplesoft and most other enterprise CRM, ERP, and HR systems used by Federal Government Contractors.  It supports read/write integration, business logic, and is done without custom development leveraging CorasWorks adapters.


Impact on Business

When they first began, they were running fewer than 100 projects through their nascent proposal center using very manual processes.  The Proposal Center’s impact and scope of services has grown considerably over the last two years.  They are now running at 400 proposals/projects per year.  The output is currently driving $250M of new business for the organization each year.  The range of services continues to expand and help drive up the quality and consistency of organizational BD output as well as mitigate the risk of ad hoc activities. Using CorasWorks, non-developer business people in the BD operations groups (vs. IT) are able to maintain the system and enhance and extend it to meet evolving requirements.  This drives down costs and makes continuous innovation practical and efficient.


Next Steps

The customer is currently in the process of migrating the system to SharePoint 2010 and expanding its capacity.  In addition, they are enhancing the system to be a broader Business Development system that manages the full life-cycle with proposals as a core process.  To support this breadth, they are moving the overall design to a broad stage-activity-gate approach to give them 360 degree visibility across the life-cycle.  They will be building up and out their IDIQ/GWAC capabilities to create a full service Center of Excellence.    In addition, the system is going deeper to provide additional supporting processes working across other staff functions such as Organizational Conflicts of Interest, At Risk Authorizations, Finance requests and approvals, and Risk Management that are specific to Federal Government Contractors.

And, there is even more on the roadmap.  But, it is a competitive world so I’ll save that for later.  The key takeaway is that many organizations are leaving a lot of value on the table by using just native SharePoint or legacy rigid proposal systems.  There is a better way




See additional articles for Capture and Proposal Management in this blog.

Visit CorasWorks Capture and Proposal Management for product information.

Large Federal Contractor Drives Customer Intimacy and Value with Dedicated Program Workplaces on SharePoint

Our customer is one of the top 10 largest Federal Government Contractors.  Being so big you’d think that they would act it.  But, when it comes to contracts, performance, and customer value they have found a way to act small, local and drive very tangible customer value.  They are accomplishing this by creating dedicated Program Workplaces using CorasWorks on SharePoint.  In this article, I’ll tell the story of one $150M contract/program and how this has become a successful model that is spreading. By the end of 2012 this approach will cover 5 contracts/programs worth more than $1 Billion dollars.  And, as you’ll see, it is a story of organic innovation at the edge of the business, where the customer value is created.


The Challenge

Our customer won a contract worth $150 million over 5 years.  The contract is for services for a program for a Civilian Agency that involves delivering on a schedule of similar yet differing “projects”.  The user base is about 500 people with 200 of them being employees from our customer and the rest being customer and partner employees.  Our customer believed that the best results could be achieved by enabling their employees, partners, and Agency customer participants to work together in a dedicated, seamless, program work environment.


The Solution

A year ago the contract started.  Our customers’ Program Manager decided to invest in their Program Workplace out of their own pocket.  They deployed an extranet infrastructure based upon “vanilla” SharePoint.  They then used CorasWorks to build out their Program Workplace.  It took just a month to get the environment up, built and being actively used.

Now, this is not some passive intranet or a skinny extranet portal.  It is a dynamic, integrated, seamless, interactive, role-based workplace for everyone involved with the mission of the program.  Here is what this means:

- it is a dedicated environment for employees, partners, and customers working on the program

- it is role based – the Agency customer people have their work consoles, the functional managers have their work consoles, and the contributors have their consoles and places to go to get the work done.  They are enabled to see, act and contribute from wherever they work.  They see only the information and activities that they have rights to see.

- everything is there – it is a self-contained environment.  All of the information, reporting, processes, collaboration that relates to the program are there.

- it is about the mission and the work – it is a workplace dedicated to delivering the projects on schedule.  Effectively, the projects are managed through a structured set of stages with a final result.  All of the users have their roles and participate in the work.  Any supporting processes are part of the environment

- it evolves – effectively, the workplace gets better every month.  They learn with each project, they make changes in their work processes and the workplace, they get better.

Each project of this program is mission critical.  A project either succeeds or fails.  Everyone is accountable.  By having this workplace, the users share accountability.  And, in the last year they have succeeded with each project.


What makes this Workplace Different from an Extranet

Most SharePoint extranets are designed and built as appendages of an Intranet.  They are skinny – a place customers can go to maybe see reports and access information.  What happens is that the extranet is separate from the intranet where the internal people work.  Thus, the work and information environment have lots of seams (holes, gaps, barriers, cracks).  Lots of information, productivity and accountability thus gets lost – it is a seamy way to work with others.

With their dedicated Program Workplace, our customer has changed the game.  They designed it top down from the perspective of the whole team to accomplish the mission of the program.  Thus, everyone works equally together.  The result is that the work and information flow from person to person and task to task instantly and seamlessly.

Technically, the environment has more than 200 SharePoint sites.  But, unlike most SharePoint environments this fact is transparent and irrelevant to the users.  They do not have to navigate to the sites to see what is going on, contribute or act.  The majority of the sites just store information and establish security barriers.  Instead, the users see, contribute and act from their role-based consoles.  The information, work to be done, and results come to them.  You don’t prepare reports, you just do your work – the system takes care of the rest.  It is role-based and seamless. Imagine, a workplace that makes it easy and convenient to be productive.

What is truly unique here is that this customer invested from their own budget to bring up a dedicated environment, that they own, and that has become part of their service offering for this contract.  Plain and simply, it is a better solution for driving customer value and achieving contract success – breakthrough stuff.


A Cost Neutral Solution

Federal Contractors, particularly with service driven contracts, have to worry about costs – margins are tight.  Initially, this contractor made the investment up front – a minor miracle.  They were clear in their objective and how to get there.  They had planned that they would get change requests from their users.  They did.  So, in addition to the normal contract task orders, the Agency customer has been issuing change requests as task orders to enhance and extend the workplace.  In this first year they received more revenue in change request task orders then they had projected for the 5 year period.  This revenue has enabled the original team to stay on the project to maintain and enhance the environment and has made the environment a cost neutral part of their offering.


The Solution Becomes a Business Model – Organically

This Program Workplace has been very successful.  The approach is being adopted for other contracts/programs across our customer…

For instance, our customer has another contract with the same agency.  They are also a user of CorasWorks but have been supporting the customer via their internal Division Intranet.  The agency has now “guided” the Program Manager to move out of the Intranet and into an extranet workplace – to provide them the benefits that their other agency comrades have on the other contract.  In fact, they are consolidating the workplace of that program into the infrastructure of the first program.

In a new contract with a different Agency to be awarded this year, our customer is including a CorasWorks-based Program Workplace as part of their bid.  This contract will be about 3 times larger than the other two mentioned above.  They intend to leverage the same Program Workplace overall design with the primary difference being the workstreams and processes.

And there is more…  There are two other contracts/programs within the same customer, with different Federal Agencies, that are also following a customer-intimate, dedicated, Program Workplace model based upon CorasWorks on SharePoint. They have been running for years. The fascinating part is that until a couple of months ago these different programs and their managers did not know what the other groups were doing. CorasWorks has now connected them up.


Innovation Happening at the Edge of the Company

The miracle of it all…

This approach was not explicitly driven by Corporate or even the Divisions.  It emerged at the edge of the company.  This very large Federal Contractor has somehow magically created a culture that has enabled the drive towards customer intimacy on these contracts.  It empowered the local program managers to truly do what is best for the customer and the mission of their contract.  It delegated accountability.  Now that they know about each other, they are starting to share their designs, approaches, practices, even application templates.  So, without explicit corporate guidance, funds, or systems, there is an evolving common approach, to drive their customers’ success, that is driving the delivery of more than $1 Billion of business.  This is pure goodness.

In our increasingly hyper-competitive world, customer intimacy that delivers exceptional results, is a (if not the) key differentiator – particularly in services based sectors. The fact that this is happening organically in a very big company, sets a new bar for competition in Federal Contracting – one that other organizations large and small should take notice of.



$0 to $250 Million in 3 Years–Federal Contractor leverages CorasWorks on SharePoint to Support Growth, Productivity and Integration

Planning began in 2009.  Through a series of acquisitions and aggressive organic growth this Federal Contractor has gone from startup to a $250 Million/year business with 1,100 employees in 3 years. Their story is a testament to solid planning and knowing how you will execute before the tornado comes.  It has been very cool to be part of this ride from the initial planning stages.  Here is their story…


The Planning

In 2009, the CEO set very aggressive goals to build a big business quickly. They began planning.  A key part of the plan was the infrastructure, systems, and processes to enable very rapid growth, keep costs down, and drive productivity.  They would have no time for experimentation – this was about execution on a business strategy.  The target was to establish an agile infrastructure that could grow to support a $500m business.

Building this infrastructure fell on their seasoned CIO and a few key IT experts who had done it before.  In particular, they had helped build a Federal Government Contractor business before and leveraged a model of CorasWorks on SharePoint to deliver what they needed.  But, this time, the IT team could do it better and leverage new tools, methods, and capabilities.  To succeed, they had to be better.

They planned to rent hosted services online and build out their initial production environment to be operational after the first acquisition  Their objective was to create a unified, seamless, virtual work environment where employees, customers, and partners could all work together.   The key is that they understood how to manage the security of the environment while also eliminating the seams of the workplace (organizationally and technically).

The plan was that as they acquired companies and contracts these would be integrated into the environment – kind of like a workplace vortex.  As an example of the detail of planning, early on they decided that the environment would fully support the use of tablets (iPads primarily) for users to be able to see, contribute, and access information when working on premise or outside.


The Beginning of Execution

After the acquisitions started they migrated the initial hosted environment into a Private Cloud environment that they had custom designed.  This environment uses VMware with massive storage and fantastic connectivity.

At the core is a new Intranet running on SharePoint.  But, theirs goes far beyond the norm.  In effect, it is a virtual, unified, seamless work environment – their Federal Contractor workplace.  It is powered by CorasWorks that provides the user experience and the glue to enable people to see, contribute, and act from wherever they work.  This environment is a blend of information and all of the various work processes that are required by a Federal Contractor.  Powered by CorasWorks and some other secret sauce their workplace is integrated with their external ERP and CRM (from Deltek) and additional enterprise systems.


Growth and Integration

There are two types of growth: acquisition and internal growth.

Each new company acquired gets merged into the work environment.  This contractor does not leave them as separate operating units.   Instead it merges the people, information, and processes into their organization.  It acquires companies that will be a fit for their integrated model and expand their competencies as they grow.  There is one company, with one culture, and one system.  No redundancies, no loss of productivity to organization or system seams – a focus on win and deliver business and driving customer value.

They are also aggressive with contract acquisition.  For instance, in the last 2 years, they have added four new IDIQs as a Prime Contractor.  These new vehicles are managed using CorasWorks as part of their work environment.  They manage the task orders, proposal responses, teaming partners, all the way through to delivery and overall program management.



They started with 1-2 Terabytes of active SharePoint data.  In 2012, they completed the upgrade from SharePoint 2007 to SharePoint 2010 in a month without major issues.   Again, this was possible because of comprehensive planning back in 2009 that included the design of an architecture and inclusion of vendors that support this type of evolution.  (CW Technote: When they started they built their workplace using CorasWorks v11 running on SP2007.  When they migrated to SP2010 they did not even have to install a new version of CorasWorks, since the same v11 runs on both SP2007 and SP2010).

Their work environment evolves every month.  They continue to not just get bigger, but, better.  For instance, they are building a new data-smart system leveraging InfoPath forms and workflow to streamline and simplify operations.    Most information now becomes PDFs, including forms in processes.  This drives a level of consistency that is unusual which supports productivity.


My Take

This customer has done an exceptional job at building their business and providing an optimized environment to support growth, execution and evolution.  The fact that they had done the job before is critical.  Mind you, while they used CorasWorks on SharePoint before, it was in the days of SharePoint 2003, circa 2005.  Their current approach is much more holistic, integrated, current (using the latest and greatest) and just plan cooler (imagine their exec meetings where everyone is on an iPad with instant access to shared information).

As to the overall business model and workplace approach – they’ve set another new bar for competition.  For a mid-size federal contractor with a consistent set of service-based contracts, this is an optimal approach.  Instead of lots of separate siloes of work and organizations, they’ve shown how you can do it all in an integrated workplace run within your dynamic private cloud.  The way that they mapped their agile infrastructure, systems, and policies to their business strategy is just plain stellar.  And, they are setup to continually innovate – which they do.  The result is accelerated revenue growth, lower costs, and increased productivity.  It is a model that is working and that appears will take them to their objective of $500m in revenue within 5 years.


Customer Examples of Work Request Management apps for SharePoint

Over the last month, I’ve worked with a number of customers that are deploying applications for various scenarios of work request management.  This category of application is very common for all organizations and works great with CorasWorks on SharePoint.  It leverages the collaborative nature of a SharePoint environment and the work management feature set of CorasWorks.  The key design principal is to recognize that they are fundamentally cross-functional processes.  In this article, I’ll look at 4 different customer scenarios.  I’ll talk about what is common amongst them and how they differ.  I believe that any SharePoint Service Delivery Management team should make this category of app a staple of their offerings.  Once you get the core design pattern, you’ll find lots of applications for it.

Basic Work Request Management app

There are six core elements that are common to work request apps as follows:

  • They are an app, meaning there is a core site dedicated to this purpose vs. it being a feature added to a team site.
  • A requestor fills in a form to kick off a request.
  • The requestor can see, track, and engage with assigned “workers” on their requests.
  • Workers and Managers do various things (automated CorasWorks actions and forms) to respond to and complete the request.
  • Requestors and others are notified of activities and/or collaborated with.
  • You have reporting on the activity.

Customers Scenarios

Here are the 4 customer scenarios:.

Materials Storage for Pharmaceutical Manufacturing

This application is for requests to store chemicals (materials) within a manufacturing group.  People make their requests and others work the requests noting how long items are stored and where. Requestors are notified of the work and they get pinged when their storage expiration date is approaching.

IT Requests for SharePoint Work and Help Desk Tickets for Health Agency

This customer uses a couple of different WRM apps for IT to support the organization.  One allows users to log the requests for the SharePoint team for new sites, changes to sites, or new apps.  The SharePoint team then manages these requests.  The other is a WRM-based “Help Desk” app where users enter tickets and Help Desk folks work them.

Employee Requests of HR for Pharmaceutical

This customer is using WRM to enable employee across the enterprise to make requests of HR.  In this case, they created three request workstreams.  Each has a slightly different set of work management activities.  From the user perspective they are able to see the different requests in a single display from wherever they work.

HR Staffing Requests for Federal Contractor

An important process for many Federal Contractors is making requests of HR to find or recruit people to work on contracts.  In this case, a business development (BD) person working on a new proposal/task order makes requests of HR to staff specific positions.  The requests are related to specific Proposals/Task Orders.  However, HR manages all of the requests centrally.


All of the above follow the same basic design as described above.  People make requests.  People work on the requests.  There is back and forth.  The requests are closed out.  There is reporting.

The interesting part is that these are four very different “applications”.  In many organizations, they would presume that they would be looking to go out and buy or build completely different applications.  However, with CorasWorks on SharePoint each of these uses the same basic framework.  Thus, armed with one basic design you can now fill many different needs and save lots of time an money in the process.

Further, when you build them, the things that you will primarily change are also common:

  • The core data (fields) of the “work request” list are different.
  • The request form is different.
  • The worker roles are specific to the process.
  • The app navigation is different.
  • The displays and most importantly the worker/manager actions, work forms, and notifications are different.
  • Reports are different.

With CorasWorks, each of the above is easily modified using our wizards.  So, you have a common app design and you know the common things that you will be changing to accommodate the specific needs of the app.  If you look at it like an assembly line, you are all set to deliver.

Key Deployment Differences of the Apps

While the four apps have many core commonalities, there are differences in the overall deployment approach across the SharePoint environment.  This is important because work request management is fundamentally a cross-functional collaborative process.  Thus, where people go to engage, whether requestor, worker, or manager, can be different based upon the scenario.


In the Materials Storage app, all of the different users work in a single app site.  Requestors go there to make their requests.  Workers go there to do their work.  Managers go there to manage.  This makes it easier to create the app and is the way you would typically start.  However, it is not really a best practice given the ability to distribute functionality using CorasWorks.


In the IT Request app, the Requestors don’t go into the app app site to make requests.  They are able to be elsewhere across the SharePoint environment and enter their requests from their and see their requests and interact.  This makes it more convenient for the users.  Generally, you start by building the app as an All-in-one and then just distribute the displays.

Many Projects to Work Management Team (Hub and Spoke)

The HR Staffing app is a bit different.  In this specific scenario, you have many Proposal/Task Order sites (or could be project sites).  A team is working on these projects.  They enter their requests from the site.  However, the HR Work Request site is central – all of the requests feed into the one app.  HR is then able to manage it all in one place and interact with the requestors via their project sites.  This ends up as a Hub and Spoke deployment.


The Employee request design is different also.  In this case, there is a self-service page in the enterprise portal.  Users go to this one place and enter and see their requests across the three types.  The requests are funneled into the three different workstreams managed by HR.  HR is also able to work on them via a single display.

Getting You Spun Up for Work Request Management

The work request management category of app is a staple of SharePoint environments that have gone past basic site centric content sharing.  We often work with customers to train up their SDM teams to deliver this category of app.  We have a standard set of templatized apps and training to help get you going quickly.  Email for more information.