Browse Arkansas Code titles and sections
14 U.S.C. § 1133 — Preliminary development and demonstration
Federal law — U.S. Code and appendices · legal_authorities
**(a) In General.—** The Commandant shall ensure that developmental test and evaluation, operational test and evaluation, life-cycle cost estimates, and the development and demonstration requirements applied by this chapter to acquisition projects and programs are met to confirm that the projects or programs meet the requirements identified in the mission-analysis and affordability assessment prepared under section 1131(a)(2), the operational requirements developed under section 1132(a)(1) and the following development and demonstration objectives:
(1) To demonstrate that the design, manufacturing, and production solution is based upon a stable, producible, and cost-effective product design.
(2) To ensure that the product capabilities meet contract specifications, acceptable operational performance requirements, and system security requirements.
(3) To ensure that the product design is mature enough to commit to full production and deployment.
**(b) Tests and Evaluations.—**
(1) **In general.—** — The Commandant shall ensure that the Coast Guard conducts developmental tests and evaluations and operational tests and evaluations of a capability or asset and the subsystems of the capability or asset in accordance with the master plan prepared for the capability or asset under section 1132(d)(1).11 See References in Text note below.
(2) **Use of third parties.—** — The Commandant shall ensure that the Coast Guard uses independent third parties with expertise in testing and evaluating the capabilities or assets and the subsystems of the capabilities or assets being acquired to conduct developmental tests and evaluations and operational tests and evaluations whenever the Coast Guard lacks the capability to conduct the tests and evaluations required by a master plan.
(3
Source: Supplied U.S. Code snapshot — release unconfirmed · 14 U.S.C. § 1133
Stored review status: release_metadata_unconfirmed. A text match is a research starting point; applicability is not established.
Original supplied file — preserved unchanged
Download original Markdown file
File SHA-256: 24826da2b0e03b40c5436cc1b8938c376ffaf84c2e4860dd7f6b2702c8e3ee8d. The original may include catalog metadata, neighboring provisions, or embedded records outside this collection's scope. Search shows only the selected federal record. Historical editions and unverified snapshots are not a statement of current law.
Authority boundary: historical or unconfirmed source not current law verified.
Open the recorded source website ↗
Record provenance
Stable record: federal_law:legal_authorities:record_usc_f42da34476ef2060fd6df7a3
Source file: Laws/federal/codes/united-states-code/title-14/section-1133-preliminary-development-and-demonstration--8bf9fe3001.md
Pages: Not recorded – Not recorded
Passage SHA-256: f7078aa98ebe30ba88e11d1af9c7c01c2bb665d8f0e4ba11f7f2d1562305bfb5
Source location: Title 14, Chapter 11, § 1133; chapter-011-acquisitions.md
Stored source content
**(a) In General.—** The Commandant shall ensure that developmental test and evaluation, operational test and evaluation, life-cycle cost estimates, and the development and demonstration requirements applied by this chapter to acquisition projects and programs are met to confirm that the projects or programs meet the requirements identified in the mission-analysis and affordability assessment prepared under section 1131(a)(2), the operational requirements developed under section 1132(a)(1) and the following development and demonstration objectives:
(1) To demonstrate that the design, manufacturing, and production solution is based upon a stable, producible, and cost-effective product design.
(2) To ensure that the product capabilities meet contract specifications, acceptable operational performance requirements, and system security requirements.
(3) To ensure that the product design is mature enough to commit to full production and deployment.
**(b) Tests and Evaluations.—**
(1) **In general.—** — The Commandant shall ensure that the Coast Guard conducts developmental tests and evaluations and operational tests and evaluations of a capability or asset and the subsystems of the capability or asset in accordance with the master plan prepared for the capability or asset under section 1132(d)(1).11 See References in Text note below.
(2) **Use of third parties.—** — The Commandant shall ensure that the Coast Guard uses independent third parties with expertise in testing and evaluating the capabilities or assets and the subsystems of the capabilities or assets being acquired to conduct developmental tests and evaluations and operational tests and evaluations whenever the Coast Guard lacks the capability to conduct the tests and evaluations required by a master plan.
(3) **Communication of safety concerns.—** — The Commandant shall ensure that independent third parties and Government employees that identify safety concerns during developmental or operational tests and evaluations or through independent or Government-conducted design assessments of capabilities or assets and subsystems of capabilities or assets to be acquired by the Coast Guard communicate such concerns as soon as practicable, but not later than 30 days after the completion of the test or assessment event or activity that identified the safety concern, to the program manager for the capability or asset and the subsystems concerned and to the Chief Acquisition Officer.
(4) **Reporting of safety concerns.—** — The Commandant shall ensure that any safety concerns that have been communicated under paragraph (3) for an acquisition program or project are reported to the appropriate congressional committees at least 90 days before the award of any contract or issuance of any delivery order or task order for low, initial, or full-rate production of the capability or asset concerned if they will remain uncorrected or unmitigated at the time such a contract is awarded or delivery order or task order is issued. The report shall include a justification for the approval of that level of production of the capability or asset before the safety concerns are corrected or mitigated. The report shall also include an explanation of the actions that will be taken to correct or mitigate the safety concerns, the date by which those actions will be taken, and the adequacy of current funding to correct or mitigate the safety concerns.
(5) **Asset already in low, initial, or full-rate production.—** — The Commandant shall ensure that if an independent third party or a Government employee identifies a safety concern with a capability or asset or any subsystems of a capability or asset not previously identified during operational test and evaluation of a capability or asset already in low, initial, or full-rate production—
(A) the Commandant, through the Assistant Commandant for Capability, shall notify the program manager and the Chief Acquisition Officer of the safety concern as soon as practicable, but not later than 30 days after the completion of the test and evaluation event or activity that identified the safety concern; and
(B) the Deputy Commandant for Mission Support shall notify the Commandant and the Deputy Commandant for Operations of the safety concern within 50 days after the notification required under subparagraph (A), and include in such notification—
(i) an explanation of the actions that will be taken to correct or mitigate the safety concern in all capabilities or assets and subsystems of the capabilities or assets yet to be produced, and the date by which those actions will be taken;
(ii) an explanation of the actions that will be taken to correct or mitigate the safety concern in previously produced capabilities or assets and subsystems of the capabilities or assets, and the date by which those actions will be taken; and
(iii) an assessment of the adequacy of current funding to correct or mitigate the safety concern in capabilities or assets and subsystems of the capabilities or assets and in previously produced capabilities or assets and subsystems.
**(c) Technical Certification.—**
(1) **In general.—** — The Commandant shall ensure that any Level 1 or Level 2 acquisition project or program is certified by the technical authority of the Coast Guard after review by an independent third party with capabilities in the mission area, asset, or particular asset component.
(2) **TEMPEST testing.—** — The Commandant shall—
(A) cause all electronics on all aircraft, surface, and shore capabilities and assets that require TEMPEST certification to be tested in accordance with TEMPEST standards and communications security (comsec) standards by an independent third party that is authorized by the Federal Government to perform such testing; and
(B) certify that the assets meet all applicable TEMPEST requirements.
(3) **Cutter classification.—**
(A) *In general.—* — The Commandant shall cause each cutter, other than a National Security Cutter, acquired by the Coast Guard and delivered after the date of enactment of the Coast Guard Authorization Act of 2010 to be classed by the American Bureau of Shipping before final acceptance.
(B) Repealed. Pub. L. 112–213, title II, § 210(c)(2)(B), Dec. 20, 2012, 126 Stat. 1551.]
(4) **Other vessels.—** — The Commandant shall cause the design and construction of each National Security Cutter, other than National Security Cutters 1, 2, and 3, to be assessed by an independent third party with expertise in vessel design and construction certification.
(5) **Aircraft airworthiness.—** — The Commandant shall cause all aircraft and aircraft engines acquired by the Coast Guard to be assessed for airworthiness by an independent third party with expertise in aircraft and aircraft engine certification before final acceptance.
Cross-references
Connections may be documented source relationships, shared citations or nearby passages. Each explains its basis; a connection alone does not establish applicability to your situation.
Federal law — U.S. Code and appendices · legal_authorities
**(a) In General.—** The Commandant may not establish a Level 1 or Level 2 acquisition project or program until the Commandant—
(1) clearly defines the operational requirements for the project or program;
(2) establishes the feasibility of alternatives;
(3) develops an acquisition project or program baseline;
(4) produces a life-cycle cost estimate; and
(5) assesses the relative merits of alternatives to determine a preferred solution in accordance with the requirements of this section.
**(b) Submission Required Before Proceeding.—** Any Coast Guard Level 1 or Level 2 acquisition project or program may not begin to obtain any capability or asset or proceed beyond that phase of its development that entails approving the supporting acquisition until the Commandant submits to the appropriate congressional committees the following:
(1) The key performance parameters, the key system attributes, and the operational performance attributes of the capability or asset to be acquired under the proposed acquisition project or program.
(2) A detailed list of the systems or other capabilities with which the capability or asset to be acquired is intended to be interoperable, including an explanation of the attributes of interoperability.
(3) The anticipated acquisition project or program baseline and acquisition unit cost for the capability or asset to be acquired under the project or program.
(4) A detailed schedule for the acquisition process showing when all capability and asset acquisitions are to be completed and when all acquired capabilities and assets are to be initially and fully deployed.
**(c) Analysis of Alternatives.—**
(1) **In general.—** — The Coast Guard may not acquire an experimental or technically immature capability or asset or implement a Level 1 or L
Source: Supplied U.S. Code snapshot — release unconfirmed · 14 U.S.C. § 1132
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) In General.—** In carrying out authorities provided to the Secretary to design, construct, accept, or otherwise acquire assets and systems under section 501(d), the Secretary, acting through the Commandant or the head of an integrated program office established for a major acquisition program, may enter into contracts for a major acquisition program and 3 Polar Security Cutters in addition to those approved as part of a major acquisition program on November 1, 2019.
**(b) Authorized Methods.—** Contracts entered into under subsection (a)—
(1) may be block buy contracts;
(2) may be incrementally funded;
(3) may include combined purchases, also known as economic order quantity purchases, of—
(A) materials and components; and
(B) long lead time materials; and
(4) as provided in [section 3501 of title 10](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3501&num=0&edition=prelim), may be multiyear contracts.
**(c) Subject to Appropriations.—** Any contract entered into under subsection (a) shall provide that any obligation of the United States to make a payment under the contract is subject to the availability of amounts specifically provided in advance for that purpose in subsequent appropriations Acts.
Source: Supplied U.S. Code snapshot — release unconfirmed · 14 U.S.C. § 1137
Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
Page 100
TITLE 14—COAST GUARD
§ 1133
tended to minimize technical, cost, and sched-
ule risk as early as practicable in the develop-
ment of the project or program.
(2) TEST
AND
EVALUATION
STRATEGY.—The
master plan shall—
(A) set forth an integrated test and evalua-
tion strategy that will verify that capa-
bility-level or asset-level and subsystem-
level design and development, including per-
formance and supportability, have been suf-
ficiently proven before the capability, asset,
or subsystem of the capability or asset is ap-
proved for production; and
(B) require that adequate developmental
tests and evaluations and operational tests
and evaluations established under subpara-
graph (A) are performed to inform produc-
tion decisions.
(3) OTHER
COMPONENTS
OF
THE
MASTER
PLAN.—At a minimum, the master plan shall
identify—
(A) the key performance parameters to be
resolved through the integrated test and
evaluation strategy;
(B) the performance data to be used to de-
termine whether the key performance pa-
rameters have been resolved;
(C) critical operational issues to be as-
sessed in addition to the key performance
parameters;
(D) the results during test and evaluation
that will be required to demonstrate that a
capability, asset, or subsystem meets per-
formance requirements;
(E) specific development test and evalua-
tion phases and the scope of each phase;
(F) modeling and simulation activities to
be performed, if any, and the scope of such
activities;
(G) early operational assessments to be
performed, if any, and the scope of such as-
sessments;
(H) operational test and evaluation phases;
(I) an estimate of the resources, including
funds, that will be required for all test, eval-
uation, assessment, modeling, and simula-
tion activities; and
Source: Supplied 2024 U.S. Code historical extraction · 14 U.S.C. § 1133
Stored review status: historical_2024_not_currentness_verified. Same stored citation; legal effect and authority still require review.