**Acquisition Plan Template**

**Project Name**

**Organization/Agency**

**Date**

**Table of Contents**

[1. Acquisition background and objectives
3](#acquisition-background-and-objectives)

[1.1 Statement of need 3](#statement-of-need)

[1.2 Applicable conditions 3](#applicable-conditions)

[1.3 Cost 3](#cost)

[1.4 Capability or performance 4](#capability-or-performance)

[1.5 Delivery or performance-period requirements
5](#delivery-or-performance-period-requirements)

[1.6 Trade-offs 5](#trade-offs)

[1.7 Risks 5](#risks)

[1.8 Acquisition streamlining 6](#acquisition-streamlining)

[2. Plan of Action 6](#plan-of-action)

[2.1 Sources 6](#sources)

[2.2 Competition 7](#competition)

[2.3 Source-selection procedures 7](#source-selection-procedures)

[2.4 Acquisition considerations 8](#acquisition-considerations)

[2.5 Budgeting and funding 9](#budgeting-and-funding)

[2.6 Product or service descriptions
9](#product-or-service-descriptions)

[2.7 Priorities, allocations, and allotments
9](#priorities-allocations-and-allotments)

[2.8 Contractor versus Government performance
9](#contractor-versus-government-performance)

[2.9 Inherently governmental functions
10](#inherently-governmental-functions)

[2.10 Management information requirements
10](#management-information-requirements)

[2.11 Make or buy 10](#make-or-buy)

[2.12 Test and evaluation 10](#test-and-evaluation)

[2.13 Logistics considerations 12](#logistics-considerations)

[2.14 Government-furnished property 14](#government-furnished-property)

[2.15 Government-furnished information
14](#government-furnished-information)

[2.16 Environmental and energy conservation objectives
15](#environmental-and-energy-conservation-objectives)

[2.17 Security considerations 15](#security-considerations)

[2.18 Physical Access 15](#physical-access)

[2.19 Contract administration 15](#contract-administration)

[2.20 Other considerations 16](#other-considerations)

[2.21 Milestones for the acquisition cycle
16](#milestones-for-the-acquisition-cycle)

[2.22 Identification of participants in acquisition plan preparation
17](#identification-of-participants-in-acquisition-plan-preparation)

[2.23 Additional requirements for major systems
17](#additional-requirements-for-major-systems)

[2.24 Additional requirements for acquisitions involving bundling
18](#additional-requirements-for-acquisitions-involving-bundling)

[2.25 Additional requirements for telecommuting
20](#additional-requirements-for-telecommuting)

# Acquisition background and objectives

###  {#section .unnumbered}

## Statement of need

> Introduce the plan by a brief statement of need. Summarize the
> technical and contractual history of the acquisition. Discuss feasible
> acquisition alternatives, the impact of prior acquisitions on those
> alternatives, and any related in-house effort.
>
> *Example language:*
>
> *The contractor shall provide all necessary services and materials to
> support this effort:*
>
> *The Agency is seeking a Contractor to provide analysis, design,
> prototyping, development, testing, training, implementation, and post
> implementation support for the Enhancement Project, Phase 2, Subsystem
> redesign. A workflow management solution will also be required.*
>
> *Through market research, it has been determined that the need can be
> met utilizing the NIH CIO-SP2*i *GWAC. Requirements fall under Task
> Areas 2, 4, and 9 of this GWAC.*

## Applicable conditions

> State all significant conditions affecting the acquisition, such as---

a.  Requirements for compatibility with existing or future systems or
    programs; and

b.  Any known cost, schedule, and capability or performance constraints.

> *Example language:*
>
> *Must be compatible with existing system, in terms of functionality
> and portability. There are no known cost, schedule, or
> capability/performance constraints at this time.*

## Cost

> Set forth the established cost goals for the acquisition and the
> rationale supporting them, and discuss related cost concepts to be
> employed, including, as appropriate, the following items:

a.  *Life-cycle cost*. Discuss how life-cycle cost will be considered.
    If it is not used, explain why. If appropriate, discuss the cost
    model used to develop life-cycle-cost estimates.

b.  *Design-to-cost*. Describe the design-to-cost objective(s) and
    underlying assumptions, including the rationale for quantity,
    learning-curve, and economic adjustment factors. Describe how
    objectives are to be applied, tracked, and enforced. Indicate
    specific related solicitation and contractual requirements to be
    imposed.

c.  *Application of should-cost*. Describe the application of
    should-cost analysis to the acquisition.

> *Example language:*
>
> *The Government's cost objective in this acquisition is to obtain a
> fair and reasonable price. The following cost estimate was developed
> using historical data:*

  ------------------------------ ------------ -------- ------------ ----------------
  *Labor Category*               *Hourly      *Est.    *\# of       *Total Est.*
                                 Rate*        Hours*   Resources*   

                                                                    

  *Project Lead*                 *\$110.00*   *1376*   *1*          *\$151,360.00*

  *Requirements Spec/Mtg.        *\$85.00*    *1376*   *1*          *\$116,960.00*
  Facilitator*                                                      

  *Technical Lead*               *\$125.00*   *1376*   *1*          *\$172,000.00*

  *Technical Documentation Spec* *\$65.00*    *960*    *2*          *\$124,800.00*

  *Usability/Accessibility       *\$110.00*   *320*    *2*          *\$70,400.00*
  Specialist*                                                       

  *Web Page Designer*            *\$90.00*    *480*    *1*          *\$43,200.00*

  *Workflow Specialist*          *\$90.00*    *320*    *1*          *\$28,800.00*

  *Technical Specialists*        *\$110.00*   *1376*   *3*          *\$151,360.00*

                                                                    

                                 *\$113.25*   *7584*   *12*         *\$858,880.00*
  ------------------------------ ------------ -------- ------------ ----------------

> *Price, though not a weighted criterion or a controlling factor, will
> be an evaluation consideration in selecting a Contractor. The
> significance of price will increase with the degree of equality of
> proposals with regard to the technical-based factors on which
> selection will be based. Any premium in price must be fully justified
> by the technical superiority of the proposal. The Government's cost
> objective in this acquisition is to obtain a fair and reasonable
> price. On the NIH CIO-SP2*i *GWAC, all contract holders are provided a
> fair opportunity to participate.*

## Capability or performance

> Specify the required capabilities or performance characteristics of
> the supplies or the performance standards of the services being
> acquired and state how they are related to the need.
>
> *Example language:*
>
> *Contractor personnel must have:*

-   *Qualifications that demonstrate intimate knowledge performing
    analysis, design, prototyping, development, testing, training,
    implementation and post implementation in an environment similar to
    the Enhancement Project.*

## Delivery or performance-period requirements

> Describe the basis for establishing delivery or performance-period
> requirements (see FAR Subpart 11.4). Explain and provide reasons for
> any urgency if it results in concurrency of development and production
> or constitutes justification for not providing for full and open
> competition.
>
> *Example language:*
>
> *The contract will have a period of performance of 12 months after
> date of award.*

## Trade-offs

> Discuss the expected consequences of trade-offs among the various
> cost, capability or performance, and schedule goals.
>
> *Example language:*
>
> *A best value to the Government source selection that considers
> Management Approach, Technical Understanding, Organizational
> Experience, Quality Control, Past Performance, and Price factors will
> be used to select the Agency contractor. In the determination of best
> value, the Government may perform a price-technical tradeoff analysis
> based on significant differences between proposals. Although the
> evaluated price to the Government is an element to be taken into
> consideration in the overall integrated assessment of proposals, the
> Management Approach, Technical Understanding, and Past Performance
> factors taken as a group are of significantly greater importance.*

## Risks

> Discuss technical, cost, and schedule risks and describe what efforts
> are planned or underway to reduce risk and the consequences of failure
> to achieve goals. If concurrency of development and production is
> planned, discuss its effects on cost and schedule risks.

##  {#section-1 .unnumbered}

> *Example language:*
>
> *[Technical]{.underline}: The Phase 2 services technical risk is
> considered to be low. In conducting market research of the NIH
> CIO/SP2*i *contractors, it has been determined that there are an
> adequate number of firms that perform this type of work, including the
> incumbent. Additionally, there is a significant amount of information
> from Phase 1 of the project available to offerors that further
> mitigates technical risks.*
>
> *[Cost]{.underline}: Cost risks are considered low to moderate. This
> will be a firm-fixed price contract competed among NIH CIO/SP2*i
> *contract holder that should result in a fair and reasonable price
> being obtained. However, in Phase 1, there were cost escalations due
> to schedule slips. Phase 1 was done on a T&M basis. This effort will
> use performance-based elements and a comprehensive quality assurance
> plan will be a part of the resulting contract. Additionally,
> employment of earned value project management principles is
> anticipated on this effort to mitigate cost escalation risk and
> schedule slippage risk.*
>
> *[Schedule]{.underline}: Schedule related risks are considered low to
> moderate. See discussion under cost above.*

## Acquisition streamlining

> If specifically designated by the requiring agency as a program
> subject to acquisition streamlining, discuss plans and procedures
> to---

a.  Encourage industry participation by using draft solicitations,
    presolicitation conferences, and other means of stimulating industry
    involvement during design and development in recommending the most
    appropriate application and tailoring of contract requirements;

b.  Select and tailor only the necessary and cost-effective
    requirements; and

c.  State the timeframe for identifying which of those specifications
    and standards, originally provided for guidance only, shall become
    mandatory.

# Plan of Action

## Sources

> Indicate the prospective sources of supplies or services that can meet
> the need. Consider required sources of supplies or services and
> sources identifiable through databases including the Government-wide
> database of contracts and other procurement instruments intended for
> use by multiple agencies available at
> [www.contractdirectory.gov](http://www.contractdirectory.gov/).
> Include consideration of small business, veteran-owned small business,
> service-disabled veteran-owned small business, HUBZone small business,
> small disadvantaged business, and women-owned small business concerns,
> and the impact of any bundling that might affect their participation
> in the acquisition. When the proposed acquisition strategy involves
> bundling, identify the incumbent contractors and contracts affected by
> the bundling. Address the extent and results of the market research
> and indicate their impact on the various elements of the plan.
>
> *Example language:*
>
> *Several NIH CIO-SP2*i *contractors have been identified as capable in
> providing the Agency services that meet the Government's requirement.
> This is a commercial requirement, and all CIO-SP2*i *contract holders
> will be given fair opportunity to compete.*

## Competition

a.  Describe how competition will be sought, promoted, and sustained
    throughout the course of the acquisition. If full and open
    competition is not contemplated, cite the authority in FAR 6.302,
    discuss the basis for the application of that authority, identify
    the source(s), and discuss why full and open competition cannot be
    obtained.

b.  Identify the major components or subsystems. Discuss component
    breakout plans relative to these major components or subsystems.
    Describe how competition will be sought, promoted, and sustained for
    these components or subsystems.

c.  Describe how competition will be sought, promoted, and sustained for
    spares and repair parts. Identify the key logistic milestones, such
    as technical data delivery schedules and acquisition method coding
    conferences, that affect competition.

d.  When effective subcontract competition is both feasible and
    desirable, describe how such subcontract competition will be sought,
    promoted, and sustained throughout the course of the acquisition.
    Identify any known barriers to increasing subcontract competition
    and address how to overcome them.

> *Example language:*
>
> *A number of businesses have been identified on the CIO-SP2*i *GWAC
> that provide services similar to the Government's requirement and will
> be provided fair opportunity for award.*

## Source-selection procedures

> Discuss the source-selection procedures for the acquisition, including
> the timing for submission and evaluation of proposals, and the
> relationship of evaluation factors to the attainment of the
> acquisition objectives (see Subpart 15.3). When an EVMS is required
> (see FAR 34.202(a)) and a pre-award IBR is contemplated, the
> acquisition plan must discuss---

a.  How the pre-award IBR will be considered in the source selection
    decision;

b.  How it will be conducted in the source selection process (see FAR
    15.306); and

c.  Whether offerors will be directly compensated for the costs of
    participating in a pre-award IBR.

> *Example language:*
>
> *The proposed contract award will be based on a best value competitive
> source selection wherein the Government is more concerned with
> obtaining superior technical performance or reduced risk than in
> making an award at the lowest overall cost to the Government. However,
> if one or more Offerors are equal in technical performance, then price
> will become more important as a factor for award.*
>
> *Streamlined source selection procedures will be used. The source
> selection authority will be the Contracting Officer. The technical
> evaluation will be conducted by Agency personnel. The Specific
> Criteria Factors of the evaluation will be Management Approach,
> Technical Understanding, Approach, Capabilities, and Relevant Past
> Performance. Price and personnel qualifications will also be taken
> into consideration.*

## Acquisition considerations

a.  For each contract contemplated, discuss contract type selection (see
    Part 16); use of multiyear contracting, options, or other special
    contracting methods (see FAR Part 17); any special clauses, special
    solicitation provisions, or FAR deviations required (see FAR
    Subpart 1.4); whether sealed bidding or negotiation will be used and
    why; whether equipment will be acquired by lease or purchase (see
    FAR Subpart 7.4) and why; and any other contracting considerations.
    Provide rationale if a performance-based acquisition will not be
    used or if a performance-based acquisition for services is
    contemplated on other than a firm-fixed-price basis (see FAR
    37.102(a), 16.103(d), and 16.505(a)(3)).

b.  For each order contemplated, discuss---

> \(A\) For information technology acquisitions, how the capital
> planning and investment control requirements of 40 U.S.C. 11312 and
> OMB Circular A-130 will be met (see FAR 7.103(t) and Part 39); and
>
> \(B\) Why this action benefits the Government, such as when---
>
> \(1\) The agency can accomplish its mission more efficiently and
> effectively (*e.g., *take advantage of the servicing agency's
> specialized expertise; or gain access to contractors with needed
> expertise); or
>
> \(2\) Ordering through an indefinite delivery contract facilitates
> access to small business concerns, including small disadvantaged
> business concerns, 8(a) contractors, women-owned small business
> concerns, HUBZone small business concerns, veteran-owned small
> business concerns, or service-disabled veteran-owned small business
> concerns.
>
> *Example language:*
>
> *The contract will be firm-fixed price based on offeror NIH CIO-SP2*i
> *schedule rates. The contract will consist of a 12 month period from
> date of award.*

## Budgeting and funding

> Include budget estimates, explain how they were derived, and discuss
> the schedule for obtaining adequate funds at the time they are
> required (see FAR Subpart 32.7).
>
> *Example language:*
>
> *Adequate funding based on the IGCE for the 12-month period is
> available to be committed.*

## Product or service descriptions

> Explain the choice of product or service description types (including
> performance-based acquisition descriptions) to be used in the
> acquisition.
>
> *Example language:*
>
> *The technical requirements for the effort are described in the SOW to
> a level of detail that makes clear the nature and content of the work
> required.*

## Priorities, allocations, and allotments

> When urgency of the requirement dictates a particularly short delivery
> or performance schedule, certain priorities may apply. If so, specify
> the method for obtaining and using priorities, allocations, and
> allotments, and the reasons for them (see FAR Subpart 11.6).

## Contractor versus Government performance

> Address the consideration given to OMB Circular No. A-76 (see
> FAR Subpart 7.3).
>
> *Example language:*
>
> *OMB Circular No. A-76 does not apply to this requirement.*

## Inherently governmental functions

> Address the consideration given to FAR Subpart 7.5.
>
> *Example language:*
>
> *This requirement does not conflict with FAR Subpart 7.5.*

## Management information requirements

> Discuss, as appropriate, what management system will be used by the
> Government to monitor the contractor's effort. If an Earned Value
> Management System is to be used, discuss the methodology the
> Government will employ to analyze and use the earned value data to
> assess and monitor contract performance. In addition, discuss how the
> offeror's/contractor's EVMS will be verified for compliance with the
> American National Standards Institute/Electronics Industries Alliance
> (ANSI/EIA) Standard-748, Earned Value Management Systems, and the
> timing and conduct of integrated baseline reviews (whether prior to or
> post award). (See FAR 34.202.)
>
> *Example language:*
>
> *The Contractor will be required by the SOW to provide various
> management reports on a weekly and monthly basis.*
>
> *Due to estimated contract value and contract type (no IT development,
> maintenance, or enhancement), full EVMS methodology and compliance is
> not required. However, use of EVMS principles will be required in
> contractor management reports.*

## Make or buy

> Discuss any consideration given to make-or-buy programs (see FAR
> 15.407-2).

## Test and evaluation

> To the extent applicable, describe the test program of the contractor
> and the Government. Describe the test program for each major phase of
> a major system acquisition. If concurrency is planned, discuss the
> extent of testing to be accomplished before production release.
>
> *Example language:*
>
> *Using the approved test scripts, the government together with
> interested and invited external customers shall perform user
> acceptance testing of the system. During this testing, the Contractor
> shall document all system deficiencies using a tracking tool. At
> conclusion of the first round of testing, the Contractor shall
> schedule daily briefings with the government and development team to
> establish repair priorities, identify contractor personnel responsible
> for specific repairs, estimate time to repair each deficiency, and
> notify government of repair completion. The government shall perform a
> retest of each repair and advise the Contractor of the outcome. The
> Contractor shall fix all deficiencies found during User Acceptance
> Testing to the satisfaction of the government.*
>
> *Upon successfully repairing all deficiencies, the Contractor shall
> prepare a final report for review, approval, and signoff by the
> government.*
>
> *The system must successfully pass User Acceptance Testing before it
> can be promoted into production.*
>
> *The Phase 2 resource(s) shall have the responsibility for monitoring,
> troubleshooting, and correcting all new Phase 2 modules for thirty
> (30) calendar days from the date of system implementation. All system
> features, functions, capabilities, and components must perform for
> this entire period. If deficiencies are discovered during this period,
> the Contractor will document the deficiencies using the tracking tool.
> The COTR will rank the priority level of each deficiency. The
> Contractor must correct all deficiencies at no additional charge.
> Deficiencies will be identified as a Critical, High, Medium, & Low. A
> critical deficiency must be resolved within 24 hours. A high
> deficiency must be resolved within 2 business days. A medium
> deficiency must be resolved within 5 business days. A low deficiency
> must be resolved within 7 business days.*
>
> *Additionally, during this 30-day period, the Phase 2 technical
> resource(s) shall be responsible for training and transitioning
> support for the new modules to the existing technical support team. If
> any intractable problems arise after the 30-day period, which the
> technical support task staff cannot fix, the Phase 2 project technical
> resource(s) must be made available to troubleshoot and resolve them.*
>
> *The Contractor shall also conduct usability inspection testing during
> this phase, and document suggested improvements for consideration by
> the government.*
>
> *The Contractor shall finalize the load test report described in the
> SOW and submit it to the government for review and signoff at least 20
> business days prior to the conclusion of the Development phase. After
> signoff of the report by the government, the Contractor shall perform
> load testing under the direction of the Agency Application Integration
> Group. Upon completion of load testing, the Contractor shall document
> the test results. This document shall include the script description,
> estimated response time, date of test, actual response time,
> resolution steps (if needed), date of retest, subsequent test results.
> The Contractor shall report on the retest results to the government
> each day until all load testing is successful. Upon successful
> completion of the load testing, the Contractor shall prepare a final
> report of load test results for review, approval, and signoff by the
> government. The system must successfully pass load testing of all
> designated scripts before it will be considered for user acceptance
> testing.*
>
> *At least 20 business days prior to the conclusion of the Development
> Phase, the Contractor shall run all new web pages and links through an
> Agency-approved Section 508 software analysis tool to ensure all pages
> pass accessibility compliance. The Contractor shall fix all
> non-compliant pages and links. The Contractor shall provide the
> successful Section 508 compliant results of each page and link to the
> government for its review and signoff. The system must pass Section
> 508 compliance before the system will be considered for user
> acceptance testing.*
>
> *At least 20 business days prior to the Conclusion of the Development
> Phase, the Contractor shall advise the government that the system is
> ready for security review The Contractor shall provide any assistance
> needed by the Agency Computer Security Office to perform a security
> review on the application. The system must successfully pass the
> security review before the system will be considered for user
> acceptance testing.*
>
> *Additional T&E considerations are contained in the SOW.*

## Logistics considerations

> Describe---

a.  The assumptions determining contractor or agency support, both
    initially and over the life of the acquisition, including
    consideration of contractor or agency maintenance and servicing (see
    Subpart 7.3) and distribution of commercial items;

b.  The reliability, maintainability, and quality assurance
    requirements, including any planned use of warranties (see Part 46);

c.  The requirements for contractor data (including repurchase data) and
    data rights, their estimated cost, and the use to be made of the
    data (see Part 27); and

d.  Standardization concepts, including the necessity to designate, in
    accordance with agency procedures, technical equipment as "standard"
    so that future purchases of the equipment can be made from the same
    manufacturing source.

> *Example language:*
>
> *At least 20 business days prior to the conclusion of the Development
> Phase, the Contractor shall prepare a proposed list of training
> modules to be included in a comprehensive on-line web-based training
> manual for review and feedback by the government. Upon receipt of the
> government feedback, the Contractor shall prepare the draft on-line
> web-based training manual for review and feedback by the government.
> Upon receipt of the feedback, the Contractor shall make all requested
> revisions to the on-line web-based training manual for review,
> approval and signoff by the government. Upon signoff by the
> government, the Contractor shall post the on-line web-based training
> manual on the Home Page. The on-line web-based training manual must be
> available via the Home Page before the system will be considered for
> user acceptance testing.*
>
> *At least 20 business days prior to the conclusion of this phase, the
> Contractor shall provide a report to the government for review and
> feedback, which identifies the appropriate code segments for load
> testing. This document shall identify all segment descriptions and the
> estimated response times to complete each segment.*
>
> *AT least 20 days before completion of the Development Phase, the
> Contractor shall submit the revised Systems and Operations Manuals to
> the government for review, approval, and signoff. The Systems and
> Operations Manuals must be signed off before the system will be
> considered for user acceptance testing.*
>
> *At mid- and end-points in the Development Phase, in collaboration
> with the government, the Contractor shall host public sessions for
> external subsystem users in which they demo the system and share the
> User Manual and On-Line User Help Guide. The Contractor shall prepare
> draft and final presentation materials for review and approval by the
> government. The Contractor shall solicit and document feedback on the
> system, User Manual, and On-Line User Help Guide from the external
> subsystem users. Based on the feedback received from the external
> subsystem users at these sessions, the Contractor shall revise the
> system, User Manual, and On-Line User Help Guide for review, approval,
> and signoff (as appropriate) by the government. The final system, User
> Manual, and On-Line User Help Guide must be signed off before the
> system will be considered for user acceptance testing.*
>
> *Within one week of government approval of each working module, the
> Contractor shall submit revised system test scripts for review and
> comment by the government. Final test scripts shall be delivered to
> the government for review, approval, and signoff before the system can
> be considered for user acceptance testing.*
>
> *The Contractor shall finalize the load test report described in the
> SOW and submit it to the government for review and signoff at least 20
> business days prior to the conclusion of the Development phase. After
> signoff of the report by the government, the Contractor shall perform
> load testing under the direction of the Application Integration Group.
> Upon completion of load testing, the Contractor shall document the
> test results. This document shall include the script description,
> estimated response time, date of test, actual response time,
> resolution steps (if needed), date of retest, subsequent test results.
> The Contractor shall report on the retest results to the government
> each day until all load testing is successful. Upon successful
> completion of the load testing, the Contractor shall prepare a final
> report of load test results for review, approval, and signoff by the
> government. The system must successfully pass load testing of all
> designated scripts before it will be considered for user acceptance
> testing.*
>
> *At least 20 business days prior to the conclusion of the Development
> Phase, the Contractor shall run all new web pages and links through an
> approved Section 508 software analysis tool to ensure all pages pass
> accessibility compliance. The Contractor shall fix all non-compliant
> pages and links. The Contractor shall provide the successful Section
> 508 compliant results of each page and link to the government for its
> review and signoff. The system must pass Section 508 compliance before
> the system will be considered for user acceptance testing.*
>
> *The Contractor shall work with the government to identify the number
> and skill sets of the technical resources needed during the
> post-implementation of Phase 2. The Contractor shall provide the COTRs
> with written budget projections for this support at least 20 business
> days in advance of the system implementation date.*
>
> *Additional logistical considerations are contained in the SOW.*

## Government-furnished property

> Indicate any property to be furnished to contractors, including
> material and facilities, and discuss any associated considerations,
> such as its availability or the schedule for its acquisition (see FAR
> Part 45).
>
> *Example language:*
>
> *All Government furnished property will be included in the
> solicitation.*

## Government-furnished information

> Discuss any Government information, such as manuals, drawings, and
> test data, to be provided to prospective offerors and contractors.
> Indicate which information that requires additional controls to
> monitor access and distribution (e.g., technical specifications, maps,
> building designs, schedules, etc.), as determined by the agency, is to
> be posted via the Federal Technical Data Solution (FedTeDS) (see FAR
> 5.102(a)).
>
> *Example language:*
>
> *All Government furnished information will be included in the
> solicitation.*

## Environmental and energy conservation objectives

> Discuss all applicable environmental and energy conservation
> objectives associated with the acquisition (see Part 23), the
> applicability of an environmental assessment or environmental impact
> statement (see 40 CFR 1502), the proposed resolution of environmental
> issues, and any environmentally-related requirements to be included in
> solicitations and contracts.

## Security considerations

> For acquisitions dealing with classified matters, discuss how adequate
> security will be established, maintained, and monitored (see Subpart
> 4.4). For information technology acquisitions, discuss how agency
> information security requirements will be met. For acquisitions
> requiring routine contractor physical access to a Federally-controlled
> facility and/or routine access to a Federally-controlled information
> system, discuss how agency requirements for personal identity
> verification of contractors will be met (see FAR Subpart 4.13).
>
> *Example language:*
>
> *These are included in the solicitation.*

## Physical Access

> For acquisitions requiring contractor physical access to a
> federally-controlled facility or access to a Federal information
> system, discuss how agency requirements for personal identity
> verification of contractors will be met (see Far Subpart 4.13).

## Contract administration

> Describe how the contract will be administered. In contracts for
> services, include how inspection and acceptance corresponding to the
> work statement's performance criteria will be enforced.
>
> *Example language:*
>
> *Contract administration will be performed by the CO and the
> Contracting Officer Technical Representative (COTR). The COTR will be
> responsible for monitoring the Contractor's performance. The contract
> will include the standard service inspection clause.*

## Other considerations

> Discuss, as applicable, standardization concepts, the industrial
> readiness program, the Defense Production Act, the Occupational Safety
> and Health Act, foreign sales implications, and any other matters
> germane to the plan not covered elsewhere.

## Milestones for the acquisition cycle

> Address the following steps and any others appropriate:
>
> Acquisition plan approval.\
> Statement of work.\
> Specifications.\
> Data requirements.\
> Completion of acquisition-package preparation.\
> Purchase request.\
> Justification and approval for other than full and open competition
> where applicable and/or any required D&F approval.\
> Issuance of synopsis.\
> Issuance of solicitation.\
> Evaluation of proposals, audits, and field reports.\
> Beginning and completion of negotiations.\
> Contract preparation, review, and clearance.\
> Contract award.
>
> *Example language:*
>
> *The following Milestone Plan identifies the major milestones planned
> for this task order through the CIO-SP2i contract vehicle.*

+-------------------------------------+---------+-----------+---------+
| *MILESTONE PLAN*                    |         |           |         |
|                                     |         |           |         |
| *CIO-SPS2i Task Order*              |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Task Order Title: **INSERT TASK    |         |           |         |
| ORDER TITLE***                      |         |           |         |
|                                     |         |           |         |
| *NITAAC Authorization #: **INSERT   |         |           |         |
| NITAAC AUTHORIZATION \#***          |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *PROCUREMENT ACTIVITY*              | *Es     | *         | *Actual |
|                                     | timated | Extension | Com     |
|                                     | Com     | Dat       | pletion |
|                                     | pletion | e/Reason* | Date*   |
|                                     | Date*   |           |         |
+-------------------------------------+---------+-----------+---------+
| *Completed Task Order Requirements  |         |           |         |
| Package (TORP) Items: SOW & IGCE*   |         |           |         |
|                                     |         |           |         |
| *Other Preliminary Pre-Award        |         |           |         |
| Documents Completed and Signed as   |         |           |         |
| applicable (Exception to Fair       |         |           |         |
| Opportunity if non-competitive      |         |           |         |
| under a multiple award,             |         |           |         |
| Justification for Use of Brand      |         |           |         |
| Name, D&F for T&M, Justification    |         |           |         |
| for using non-DoD contract if DoD)* |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Acquisition Plan Completed, as     |         |           |         |
| Required by Customer Agency*        |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *NITAAC TORP Review*                |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Requirement Solicitation Posted*   |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Requirement Solicitation Closed*   |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Customer Evaluation Completed*     |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Discussions Completed (if          |         |           |         |
| required)*                          |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Solution Recommendation            |         |           |         |
| Documentation Package (SRDP)        |         |           |         |
| Completed (to include best value    |         |           |         |
| analysis)*                          |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *NITAAC Review and Approval To      |         |           |         |
| Award Task Order*                   |         |           |         |
+-------------------------------------+---------+-----------+---------+
| *Task Order Awarded*                |         |           |         |
+-------------------------------------+---------+-----------+---------+

## Identification of participants in acquisition plan preparation

> List the individuals who participated in preparing the acquisition
> plan, giving contact information for each.

## Additional requirements for major systems

> a\. In planning for the solicitation of a major system (see FAR
> Part 34) development contract, planners shall consider requiring
> offerors to include, in their offers, proposals to incorporate in the
> design of a major system---
>
> 1\. Items which are currently available within the supply system of
> the agency responsible for the major system, available elsewhere in
> the national supply system, or commercially available from more than
> one source; and
>
> 2\. Items which the Government will be able to acquire competitively
> in the future if they are likely to be needed in substantial
> quantities during the system's service life.
>
> b\. In planning for the solicitation of a major system (see FAR
> Part 34) production contract, planners shall consider requiring
> offerors to include, in their offers, proposals identifying
> opportunities to assure that the Government will be able to obtain, on
> a competitive basis, items acquired in connection with the system that
> are likely to be acquired in substantial quantities during the service
> life of the system. Proposals submitted in response to such
> requirements may include the following:
>
> 1\. Proposals to provide the Government the right to use technical
> data to be provided under the contract for competitive future
> acquisitions, together with the cost to the Government, if any, of
> acquiring such technical data and the right to use such data.
>
> 2\. Proposals for the qualification or development of multiple sources
> of supply for competitive future acquisitions.
>
> c\. In determining whether to apply paragraphs (a) and (b) of this
> section, planners shall consider the purposes for which the system is
> being acquired and the technology necessary to meet the system's
> required capabilities. If such proposals are required, the contracting
> officer shall consider them in evaluating competing offers. In
> noncompetitive awards, the factors in paragraphs (a) and (b) of this
> section may be considered by the contracting officer as objectives in
> negotiating the contract.

## Additional requirements for acquisitions involving bundling

> a\. Bundling may provide substantial benefits to the Government.
> However, because of the potential impact on small business
> participation, the head of the agency must conduct market research to
> determine whether bundling is necessary and justified
> (15 U.S.C. 644(e)(2)). Market research may indicate that bundling is
> necessary and justified if an agency or the Government would derive
> measurably substantial benefits (see FAR 10.001(a)(2)(iv) and
> (a)(3)(vi)).
>
> b\. Measurably substantial benefits may include, individually or in
> any combination or aggregate, cost savings or price reduction, quality
> improvements that will save time or improve or enhance performance or
> efficiency, reduction in acquisition cycle times, better terms and
> conditions, and any other benefits. The agency must quantify the
> identified benefits and explain how their impact would be measurably
> substantial. Except as provided in paragraph (d) of this section, the
> agency may determine bundling to be necessary and justified if, as
> compared to the benefits that it would derive from contracting to meet
> those requirements if not bundled, it would derive measurably
> substantial benefits equivalent to---
>
> 1\) Ten percent of the estimated contract or order value (including
> options) if the value is \$86 million or less; or
>
> 2\) Five percent of the estimated contract or order value (including
> options) or \$8.6 million, whichever is greater, if the value exceeds
> \$86 million.
>
> c\. Without power of delegation, the service acquisition executive for
> the military departments, the Under Secretary of Defense for
> Acquisition, Technology and Logistics for the defense agencies, or the
> Deputy Secretary or equivalent for the civilian agencies may determine
> that bundling is necessary and justified when---
>
> 1\) The expected benefits do not meet the thresholds in
> paragraphs (b)(1) and (b)(2) of this section but are critical to the
> agency's mission success; and
>
> 2\) The acquisition strategy provides for maximum practicable
> participation by small business concerns.
>
> d\. Reduction of administrative or personnel costs alone is not
> sufficient justification for bundling unless the cost savings are
> expected to be at least 10 percent of the estimated contract or order
> value (including options) of the bundled requirements.
>
> e\. Substantial bundling is any bundling that results in a contract or
> order that meets the dollar amounts specified in FAR 7.104(d)(2). When
> the proposed acquisition strategy involves substantial bundling, the
> acquisition strategy must additionally---
>
> 1\) Identify the specific benefits anticipated to be derived from
> bundling;
>
> 2\) Include an assessment of the specific impediments to participation
> by small business concerns as contractors that result from bundling;
>
> 3\) Specify actions designed to maximize small business participation
> as contractors, including provisions that encourage small business
> teaming;
>
> 4\) Specify actions designed to maximize small business participation
> as subcontractors (including suppliers) at any tier under the
> contract, or order, that may be awarded to meet the requirements;
>
> 5\) Include a specific determination that the anticipated benefits of
> the proposed bundled contract or order justify its use; and
>
> 6\) Identify alternative strategies that would reduce or minimize the
> scope of the bundling, and the rationale for not choosing those
> alternatives.
>
> f\. The contracting officer must justify bundling in acquisition
> strategy documentation.
>
> g\. In assessing whether cost savings would be achieved through
> bundling, the contracting officer must consider the cost that has been
> charged or, where data is available, could be charged by small
> business concerns for the same or similar work.
>
> h\. The requirements of this section, except for paragraph (e), do not
> apply if a cost comparison analysis will be performed in accordance
> with OMB Circular A-76.

## Additional requirements for telecommuting

##  {#section-2 .unnumbered}

> In accordance with section 1428 of Public Law 108-136, an agency shall
> generally not discourage a contractor from allowing its employees to
> telecommute in the performance of Government contracts. Therefore,
> agencies shall not---
>
> a\. Include in a solicitation a requirement that prohibits an offeror
> from permitting its employees to telecommute unless the contracting
> officer first determines that the requirements of the agency,
> including security requirements, cannot be met if telecommuting is
> permitted. The contracting officer shall document the basis for the
> determination in writing and specify the prohibition in the
> solicitation; or
>
> b\. When telecommuting is not prohibited, unfavorably evaluate an
> offer because it includes telecommuting, unless the contracting
> officer first determines that the requirements of the agency,
> including security requirements, would be adversely impacted if
> telecommuting is permitted. The contracting officer shall document the
> basis for the determination in writing and address the evaluation
> procedures in the solicitation.