| FAST HOME | HELP | WHAT'S NEW | COMMENTS | SEARCH |
| Acquisition Strategy Paper
(Revised 09/99)
PURPOSE The Acquisition Strategy Paper defines the business and technical
approach the Integrated Product Team will use to implement the
acquisition program within constraints of the Acquisition Program
Baseline. It consolidates planning that was recorded in separate
documents prior to implementation of the AMS such as the Acquisition
Plan, Program Management Plan, Program Implementation Plan, Risk
Management Plan, Human Factors Plan, Test and Evaluation Master
Plan, and Integrated Logistics Support Plan. DESCRIPTION The Acquisition Strategy Paper documents the strategy for executing
the program during the Solution Implementation and for managing
fielded products and services during InService Management.
It is based on market surveys and analysis conducted during Investment
Analysis. The Acquisition Strategy Paper defines management roles
and responsibilities for key program participants, and addresses
the entire job of acquiring, fielding, and managing the required
capability. For many programs, this includes the acquisition of
systems and equipment, the modification or construction of facilities,
improvements to the physical infrastructure, the acquisition of
real estate, the functional integration of complex hardware and
software, and the procurement of specialized services. The Acquisition
Strategy Paper also integrates planning for all functional disciplines
associated with program implementation such as systems engineering,
inservice support, test and evaluation, security, quality
assurance, human integration, and configuration management, as
appropriate. Development of the Acquisition Strategy Paper is the primary task
of the Integrated Product Team immediately after program approval
at the Investment Decision. It is the basis for the Integrated
Program Plan which defines the detailed actions and work activities
that will be executed to achieve program requirements. APPROVAL The
co-leaders of the Integrated Management Team approve the Acquisition Strategy
Paper and any update or revision to it. For those programs not within the
purview of an Integrated Management Team, Directors from the appropriate
sponsoring and providing organizations approve the ASP. The Acquisition Strategy
Paper must be updated for any subsequent corporate decision concerning the
acquisition program, or when there is a significant change to the Acquisition
Program Baseline. (Revised 09/99)
Note: The Acquisition Strategy Paper must be approved before
release of a Screening Information Request or Request for Offer
for a proposed contract, transfer of funds, or commitment to any
interagency agreement for program implementation. Requests for
information may be released before approval.
DISTRIBUTION
Distribute copies of the approved Acquisition Strategy Paper to
all headquarters, regional, and other personnel associated with
the program. Send a copy to ASD-200, Program Evaluation Office,
which maintains a central repository of approved acquisition documents
for the Joint Resources Council.
CONTENT The following summarizes the content of the Acquisition Strategy Paper. A complete template and instruction is available in
FAST via the Internet at http://fast.faa.gov. The ASP template
must be used when preparing the ASP. Signature Page. Include: the title "Acquisition Strategy Paper" and name of the acquisition program; version number; signature of the co-leaders of the
Integrated Management Team and approval dates; and the name, organizational
code, phone number and FAX number of contacts for the sponsoring
organization and the Integrated Product Team.
Table of Contents. List every section, subsection, and
other element in the Acquisition Strategy Paper and provide the
page number.
Background. Briefly summarize the mission need and any
other high-level agency document supporting this acquisition program.
Briefly summarize the status of the program. Identify the key
products of the acquisition program.
Overview. Describe the overall strategy for achieving
the capability specified in the Acquisition Program Baseline,
and explain why it is appropriate for the risk and special conditions
and constraints associated with the acquisition program. Identify
all key elements of the program including, as appropriate, system/equipment
acquisition, facility construction or modification, physical infrastructure
modifications, functional integration with existing capabilities,
and procurement of services.
Funding. Use the funding table format in the ASP Template
found on FAST to display RE&D, F&E, and OPS funding by
fiscal year in then-year dollars for the acquisition program.
Be consistent with the cost requirement in the Acquisition Program
Baseline.
Schedule. Use the schedule table format in the ASP Template
found on FAST to display the schedule for primary program events
and milestones by fiscal year. Be consistent with the schedule
baseline in the Acquisition Program Baseline.
Benefits. Describe how benefits in the Acquisition Program
Baseline will be tracked and verified during in-service management
of the products and services of this acquisition program.
Management. Define the strategy for managing this acquisition
program including: the roles and responsibilities of all supporting
organizations and individuals; how the program will be controlled
(i.e., how progress will be measured, reported, evaluated, and
acted on); how contractors supporting the program will be managed;
and how requirements and risk will be managed). Describe the contracting
strategy for each procurement and explain how or whether competition
will be achieved.
Physical Integration. Explain the strategy for integrating
the products of this acquisition program into the physical environment
for the following, as appropriate: real estate, space, environment,
energy conservation, heating, ventilation, air conditioning, grounding,
bonding, shielding lightning protection, cables, hazardous materials,
power systems and commercial power, telecommunications, special
considerations.
Functional Integration. Explain the strategy for integrating
the products of this acquisition program with other elements of
the National Airspace System and nonNAS capabilities. Explain
the strategy for satisfying requirements related to hardware/software
integration, spectrum management, and standardization.
Human Integration. Explain the strategy for ensuring the
product(s) of this acquisition program will be appropriate for
the human workforce that will operate and maintain it. This includes
optimizing the human-product interface to achieve best performance
from a total product perspective, as well as satisfying requirements
related to employee heath and safety and obtaining special skills
and capabilities for operators, maintainers, and support personnel.
Security. Explain the strategy for satisfying requirements
related to physical security, contractor-unique security, NAS
information security, and security personnel.
In-Service Support. Explain the strategy for satisfying
requirements related to the support of products of this acquisition
program for the following, as appropriate: staffing, supply support,
support equipment, technical data, training and training support,
first and second level repair, packaging, handling, shipping,
and transportation.
Test and Evaluation. Explain the strategy for satisfying
test and evaluation requirements including, as appropriate: mandatory
evaluations of safety, environmental, and energy conservation
issues prior to joint acceptance and inspection, system testing,
operational testing at the FAA Technical Center before testing
at an operational site, independent operational test and evaluation,
and field familiarization testing. Be sure the test strategy fully
addresses test conditions, the test environment, test resources,
test sites, test tools, test personnel, test plans and test reports.
Implementation and Transition. Explain the strategy for
satisfying requirements related to transition from the current
capability to the new capability so on-going operations are not
disrupted. Typically, this encompasses implementation planning,
preinstallation checkout, installation and checkout, site
integration, system shakedown, dual operations, and removal/disposal
of replaced systems, equipment, land, facilities, and other items.
Quality Assurance. Explain the strategy for satisfying
quality assurance requirements related to contractor status reporting,
metrics, inplant QRO, independent verification and validation,
vendor quality assurance, and Capability Maturity Model assessment
of the software development processes of potential suppliers.
Configuration Management. Explain the strategy for satisfying
requirements associated with managing the configuration of hardware,
software, facilities, data, interfaces, tools, and documentation
throughout the lifecycle of the acquisition program. In-Service Management. Explain how the product or services of this program will be monitored and evaluated during the In-Service Management phase to provide the basis for sustaining and optimizing operations, and for planning major upgrades that will be needed to satisfy future demand for services. |