Skip Navigation
acfbanner  
ACF
Department of Health and Human Services 		  
		  Administration for Children and Families
          
ACF Home   |   Services   |   Working with ACF   |   Policy/Planning   |   About ACF   |   ACF News   |   HHS Home

  Questions?  |  Privacy  |  Site Index  |  Contact Us  |  Download Reader™Download Reader  |  Print Print      


The Child Care Bureau   Advanced
Search

Child Care Administrator’s Improper Payments Information Technology Guide

Download Guide in Word (993 KB) or PDF (635KB) format.


B. Descriptions of the Technical Approaches (continued)

3. Contracting

In addition to in-house development and the purchase and integration of COTS products, many State Agencies consider contracting development to a third party. In the human services field, this practice has been common for the State Automated Child Welfare Information System (SACWIS), child support, benefit determination, and case management systems. Variations exist, including contracting a third party to build a customized system residing within the Agency’s environment or purchasing the services of an Application Service Provider (ASP) that would develop and host a solution.

Agencies often consider contracting when their internal development staff is fully engaged on other projects or when moving to a different technical environment in which their current staff members do not have the requisite skills and experience. Additionally, some Agencies recognize that IT development and support are outside their core competency and choose to contract most or all their IT development and support needs. They use Agency business analysts, contract managers, and project management staff to oversee contracts with third-party vendors.

The following table describes the advantages, challenges, and key considerations related to contracting.

Table 3 – Contracting

Advantages

Challenges

Key Considerations

  • Access to staff with the appropriate technical skills and experience
  • The ability to move to a new technical environment with less State staff turnover or retraining because the contractor’s technical staff perform the system development and maintenance function instead of State staff
  • Greater control over project schedule because contractor resources may be more flexible than State resources
  • Reduced likelihood that competing demands could take away project resources because of the contractual commitment of resources
  • Possible cost savings by substituting internal development and maintenance costs with a COTS application or a potentially more efficient development process
  • Shared project risk—some risk and liability assumed by contractor
  • Frees Agency staff to focus on other high-priority needs and tasks
  • Time and cost of procurement
  • Requires properly scoped contracts to avoid schedule and cost overruns (Chapter III, Section B offers more discussion on this point)
  • Validating that contract staff members have sufficient program knowledge
  • Flexibility and ability to accommodate changing program regulations, policies, and processes without expensive and time-consuming change orders
  • Loss of organizational competencies if development occurs outside the Agency because no State staff work on the application
  • Dependence on a third-party contractor that may not have the same organizational goals and mission and thus may be more focused on meeting their business and profit objectives than meeting the Agency’s service objectives
  • Difficulty in communicating program mission, goals, and service requirements to contract technical staff
  • Is there at least one supplier available to perform the scope of work?
  • Is the Agency confident that the chosen vendor has the capacity to meet the contract deliverable? Is the vendor stable enough for the State to feel confident they will be in business for the life of the contract?
  • Does the Agency have the expertise to develop and evaluate a Request for Proposal (RFP) that adequately scopes the project?
  • Is there a good communications plan in place between the Agency and vendor?
  • Are the contract deliverables and deadlines realistic, including any deadlines for State staff to review and sign off on work products?
  • Has human resources been involved in the decision-making process to ensure that contracting fits with the Agency’s plans for developing and maintaining competencies within the organization?
  • If layoffs are part of the formula for implementation, has the State accounted for full cost of severance?
  • If significant program knowledge is required, does the contractor possess this knowledge or would Agency staff members be required to provide this expertise?
  • Does the Agency have a project manager qualified to oversee an IT project?

 

These three approaches to IT investment are not mutually exclusive. The following descriptions demonstrate blended approaches using two or more of these approaches. A State may choose both a COTS product and a third-party contractor to perform the integration and maintenance of the system.

A State may choose a COTS product, which is an enterprise framework technology, and then train State staff to configure that product to meet the business and service needs of the child care program. Enterprise framework technologies in the human services arena offer the ability of users to configure the software to support many core functions including eligibility determination, case management, reporting, financial management, workflow management, and the development of on-line forms and web pages. Business analysts configure the software and do not require technical programmers.

A State may choose to bring in a third-party to plan and implement its systems architecture, which may include a combination of current applications developed in-house, COTS applications, and web services developed in-house or available from outside entities. This option may be more frequent in States with a SOA.

Previous Page | Table of Contents | Identifying and Evaluating Alternatives >>

Posted on January 23rd, 2008.