§1171. Definitions — Inbound Citations
14 U.S.C. § 1171
Cited by 75 provisions in release 119-102.
Citations to 14 U.S.C. § 1171 as a whole
-
(A) keeping the Commandant informed of the progress of major acquisition programs (as that term is defined in section 1171);
Citations to §1171(1)
-
(c) Not later than 1 year after the date of the enactment of this Act, and annually thereafter, the Commandant shall submit to the appropriate congressional committees a report that—(1) identifies all current recurrent requirements for reports to Congress applicable to the Coast Guard;(2) estimates the total annual cost and staff hours required for compliance with such requirements; and(3) provides recommendations to Congress for sunset, consolidation, or automation of such requirements to improve efficiency, consistent applicable laws.
-
(B) shall be reviewed by an independent third party with expertise in acquisition management, and the results of that review shall be submitted to the appropriate congressional committees at least 60 days prior to the award of the contract, contract modification, or award term.
-
If, after 90 days following the elevation to the Chief Acquisition Officer of any design or other dispute regarding level 1 or level 2 acquisition, the dispute remains unresolved, the Commandant shall provide to the appropriate congressional committees a detailed description of the issue and the rationale underlying the decision taken by the Chief Acquisition Officer to resolve the issue.
-
(b) 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.
-
(4) 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.
-
(a) The Commandant shall submit a report to the appropriate congressional committees and the Committee on Homeland Security of the House of Representatives as soon as possible, but not later than 30 days, after the Chief Acquisition Officer of the Coast Guard becomes aware of the breach of an acquisition program baseline for any Level 1 or Level 2 acquisition program, by—(1) a likely cost overrun greater than 15 percent of the acquisition program baseline for that individual capability or asset or a class of capabilities or assets;(2) a likely delay of more than 180 days in the delivery schedule for any individual capability or asset or class of capabilities or assets; or(3) an anticipated failure for any individual capability or asset or class of capabilities or assets to satisfy any key performance threshold or parameter under the acquisition program baseline.
Citations to §1171(2)
-
(a) There shall be in the Coast Guard a Chief Acquisition Officer selected by the Commandant who shall be a Rear Admiral or civilian from the Senior Executive Service (career reserved) and who meets the qualifications set forth under subsection (b). The Chief Acquisition Officer shall serve at the Assistant Commandant level and have acquisition management as that individual’s primary duty.
-
(1) The Chief Acquisition Officer and any flag officer serving in the Acquisition Directorate shall be an acquisition professional with a Level III acquisition management certification and must have at least 10 years experience in an acquisition position, of which at least 4 years were spent as—(A) the program executive officer;(B) the program manager of a Level 1 or Level 2 acquisition project or program;(C) the deputy program manager of a Level 1 or Level 2 acquisition;(D) the project manager of a Level 1 or Level 2 acquisition; or(E) any other acquisition position of significant responsibility in which the primary duties are supervisory or management duties.
-
(c) The functions of the Chief Acquisition Officer include—(1) monitoring the performance of acquisition projects and programs on the basis of applicable performance measurements and advising the Commandant, through the chain of command, regarding the appropriate business strategy to achieve the missions of the Coast Guard;(2) maximizing the use of full and open competition at the prime contract and subcontract levels in the acquisition of property, capabilities, assets, and services by the Coast Guard by establishing policies, procedures, and practices that ensure that the Coast Guard receives a sufficient number of sealed bids or competitive proposals from responsible sources to fulfill the Government’s requirements, including performance and delivery schedules, at the lowest cost or best value considering the nature of the property, capability, asset, or service procured;(3) making acquisition decisions in concurrence with the technical authority, or technical authorities, of the Coast Guard, as designated by the Commandant, consistent with all other applicable laws and decisions establishing procedures within the Coast Guard;(4) ensuring the use of detailed performance specifications in instances in which performance-based contracting is used;(5) managing the direction of acquisition policy for the Coast Guard, including implementation of the unique acquisition policies, regulations, and standards of the Coast Guard;(6) developing and maintaining an acquisition career management program in the Coast Guard to ensure that there is an adequate acquisition workforce;(7) assessing the requirements established for Coast Guard personnel regarding knowledge and skill in acquisition resources and management and the adequacy of such requirements for facilitating the achievement of the performance goals established for acquisition management;(8) developing strategies and specific plans for hiring, training, and professional development;(9) reporting to the Commandant, through the chain of command, on the progress made in improving acquisition management capability; and(A) keeping the Commandant informed of the progress of major acquisition programs (as that term is defined in section 1171);(B) informing the Commandant on a continuing basis of any developments on such programs that may require new or revisited trade-offs among cost, schedule, technical feasibility, and performance, including—(i) significant cost growth or schedule slippage; and(ii) requirements creep (as that term is defined in section 3104(c)(1) of title 10); and(C) ensuring that the views of the Commandant regarding such programs on cost, schedule, technical feasibility, and performance trade-offs are strongly considered by program managers and program executive officers in all phases of the acquisition process.
-
(d) The Commandant shall maintain or designate the technical authority to establish, approve, and maintain technical requirements. Any such designation shall be made in writing and may not be delegated to the authority of the Chief Acquisition Officer established by section 308 of this title.
-
(c) The Chief Acquisition Officer shall adopt, to the extent practicable, procedures modeled after those used by the Navy Senior Acquisition Official to approve all technical requirements.
-
If, after 90 days following the elevation to the Chief Acquisition Officer of any design or other dispute regarding level 1 or level 2 acquisition, the dispute remains unresolved, the Commandant shall provide to the appropriate congressional committees a detailed description of the issue and the rationale underlying the decision taken by the Chief Acquisition Officer to resolve the issue.
-
(1) For any Level 1 or Level 2 acquisition project or program the Chief Acquisition Officer must approve a test and evaluation master plan specific to the acquisition project or program for the capability, asset, or subsystems of the capability or asset and intended to minimize technical, cost, and schedule risk as early as practicable in the development of the project or program.
-
(4) The Chief Acquisition Officer must approve an updated master plan whenever there is a revision to project or program test and evaluation strategy, scope, or phasing.
-
(A) proceed beyond that phase of the acquisition process that entails approving the supporting acquisition of a capability or asset before the master plan is approved by the Chief Acquisition Officer; or
-
(B) award any production contract for a capability, asset, or subsystem for which a master plan is required under this subsection before the master plan is approved by the Chief Acquisition Officer.
-
(3) 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.
-
(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
-
(a) The Commandant shall submit a report to the appropriate congressional committees and the Committee on Homeland Security of the House of Representatives as soon as possible, but not later than 30 days, after the Chief Acquisition Officer of the Coast Guard becomes aware of the breach of an acquisition program baseline for any Level 1 or Level 2 acquisition program, by—(1) a likely cost overrun greater than 15 percent of the acquisition program baseline for that individual capability or asset or a class of capabilities or assets;(2) a likely delay of more than 180 days in the delivery schedule for any individual capability or asset or class of capabilities or assets; or(3) an anticipated failure for any individual capability or asset or class of capabilities or assets to satisfy any key performance threshold or parameter under the acquisition program baseline.
Citations to §1171(3)
-
(1) shall represent the customer of a major acquisition program with regard to trade-offs made among cost, schedule, technical feasibility, and performance with respect to such program; and
-
(2) shall advise the Commandant in decisions regarding the balancing of resources against priorities, and associated trade-offs referred to in paragraph (1), on behalf of the customer of a major acquisition program.
Citations to §1171(4)
-
(3) In this subsection each of the terms “Level 1 acquisition” and “Level 2 acquisition” has the meaning that term has in chapter 11 of this title.
-
(1) An individual may not be assigned as the project or program manager for a Level 1 acquisition unless the individual holds a Level III acquisition certification as a program manager.
Citations to §1171(5)
-
(B) the program manager of a Level 1 or Level 2 acquisition project or program;
-
(C) the deputy program manager of a Level 1 or Level 2 acquisition;
-
(D) the project manager of a Level 1 or Level 2 acquisition; or
-
(3) In this subsection each of the terms “Level 1 acquisition” and “Level 2 acquisition” has the meaning that term has in chapter 11 of this title.
-
(2) An individual may not be assigned as the project or program manager for a Level 2 acquisition unless the individual holds a Level II acquisition certification as a program manager.
-
If, after 90 days following the elevation to the Chief Acquisition Officer of any design or other dispute regarding level 1 or level 2 acquisition, the dispute remains unresolved, the Commandant shall provide to the appropriate congressional committees a detailed description of the issue and the rationale underlying the decision taken by the Chief Acquisition Officer to resolve the issue.
-
(2) The Commandant may not initiate a Level 1 or Level 2 acquisition project or program until the Commandant—(A) completes a mission analysis that—(i) identifies the specific capability gaps to be addressed by the project or program; and(ii) develops a clear mission need to be addressed by the project or program; and(B) prepares a preliminary affordability assessment for the project or program.
-
(2) In conducting an affordability assessment under subsection (a)(2)(B), the Commandant shall develop and implement mechanisms to ensure that trade-offs among cost, schedule, and performance are considered in the establishment of preliminary operational requirements for development and production of new assets and capabilities for Level 1 and Level 2 acquisitions projects and programs.
-
(c) The Commandant shall develop staffing predictions, define human capital performance initiatives, and identify preliminary training needs required to implement each Level 1 and Level 2 acquisition project and program.
-
(a) 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) 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.
-
(1) The Coast Guard may not acquire an experimental or technically immature capability or asset or implement a Level 1 or Level 2 acquisition project or program, unless it has prepared an analysis of alternatives for the capability or asset to be acquired in the concept and technology development phase of the acquisition process for the capability or asset.
-
(1) For any Level 1 or Level 2 acquisition project or program the Chief Acquisition Officer must approve a test and evaluation master plan specific to the acquisition project or program for the capability, asset, or subsystems of the capability or asset and intended to minimize technical, cost, and schedule risk as early as practicable in the development of the project or program.
-
(2) For each Level 1 or Level 2 acquisition project or program, in addition to life-cycle cost estimates developed under paragraph (1), the Commandant shall require that—(A) life-cycle cost estimates developed under paragraph (1) be updated before—(i) each milestone decision is concluded; and(ii) the project or program enters a new acquisition phase; and(B) an independent cost estimate or independent cost assessment, as appropriate, be developed to validate life-cycle cost estimates developed under paragraph (1).
-
(1) 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.
-
(a) The Commandant shall submit a report to the appropriate congressional committees and the Committee on Homeland Security of the House of Representatives as soon as possible, but not later than 30 days, after the Chief Acquisition Officer of the Coast Guard becomes aware of the breach of an acquisition program baseline for any Level 1 or Level 2 acquisition program, by—(1) a likely cost overrun greater than 15 percent of the acquisition program baseline for that individual capability or asset or a class of capabilities or assets;(2) a likely delay of more than 180 days in the delivery schedule for any individual capability or asset or class of capabilities or assets; or(3) an anticipated failure for any individual capability or asset or class of capabilities or assets to satisfy any key performance threshold or parameter under the acquisition program baseline.
-
(c) If a likely cost overrun is greater than 20 percent or a likely delay is greater than 12 months from the costs and schedule described in the acquisition program baseline for any Level 1 or Level 2 acquisition project or program of the Coast Guard, the Commandant shall include in the report a written determination, with a supporting explanation, of whether—(1) the capability or asset or capability or asset class to be acquired under the project or program is essential to the accomplishment of Coast Guard missions;(2) there are no alternatives to such capability or asset or capability or asset class that will provide equal or greater capability in both a more cost-effective and timely manner;(3) the new acquisition schedule and estimates for total acquisition cost are reasonable; and(4) the management structure for the acquisition program is adequate to manage and control performance, cost, and schedule.
-
(2) manage department acquisition activities and act as the Acquisition Decision Authority with regard to the review or approval of a Coast Guard Level 1 or Level 2 acquisition project or program, as required by section 161 of the Office of Federal Procurement Policy Act (41 U.S.C. 414)) and related implementing regulations and directives.
-
(a) Requirements for a Level 1 or Level 2 acquisition project or program under sections 1131 through 1134 shall not apply to an acquisition by the Coast Guard that is a service life extension program.
-
(a) In carrying out a Level 1 or Level 2 acquisition project or program under this subchapter, the Commandant may publicly announce all construction, design, and engineering requirements and negotiate contracts for construction, design, and engineering services on the basis of demonstrated competence and qualification for the type of professional services required and at fair and reasonable prices.
-
(b) The following procedures may apply to the procurement of Level 1 or Level 2 acquisition project or program under this subchapter:(1) The Commandant shall require prospective contractors to submit a statement of qualifications and performance data.(2) For each proposed project, the Commandant shall—(A) evaluate statements of qualifications and performance submitted by firms regarding the proposed project; and(B) conduct discussions with firms to consider anticipated concepts and compare alternative methods for furnishing services.(3) From the firms with which discussions have been conducted under paragraph (2)(B), the Commandant shall select, in order of preference, that the Commandant considers most highly qualified to provide the services required, based on criteria established and published by the Commandant.
Citations to §1171(6)
-
(4) produces a life-cycle cost estimate; and
-
(F) a calculation of life-cycle costs including—(i) an examination of likely research and development costs and the levels of uncertainty associated with such estimated costs;(ii) an examination of likely production and deployment costs and the levels of uncertainty associated with such estimated costs;(iii) an examination of likely operating and support costs and the levels of uncertainty associated with such estimated costs;(iv) if they are likely to be significant, an examination of likely disposal costs and the levels of uncertainty associated with such estimated costs; and(v) such additional measures as the Commandant or the Secretary of the department in which the Coast Guard is operating determines to be necessary for appropriate evaluation of the capability or asset; and
-
(1) The Commandant shall implement mechanisms to ensure the development and regular updating of life-cycle cost estimates for each acquisition with a total acquisition cost that equals or exceeds $10,000,000 and an expected service life of 10 or more years, and to ensure that these estimates are considered in decisions to develop or produce new or enhanced capabilities and assets.
-
(2) For each Level 1 or Level 2 acquisition project or program, in addition to life-cycle cost estimates developed under paragraph (1), the Commandant shall require that—(A) life-cycle cost estimates developed under paragraph (1) be updated before—(i) each milestone decision is concluded; and(ii) the project or program enters a new acquisition phase; and(B) an independent cost estimate or independent cost assessment, as appropriate, be developed to validate life-cycle cost estimates developed under paragraph (1).
-
(A) life-cycle cost estimates developed under paragraph (1) be updated before—(i) each milestone decision is concluded; and(ii) the project or program enters a new acquisition phase; and
-
(B) an independent cost estimate or independent cost assessment, as appropriate, be developed to validate life-cycle cost estimates developed under paragraph (1).
-
(a) 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.
-
(5) a full life-cycle cost analysis for the capability or asset or class of capabilities or assets;
-
In carrying out the acquisition and procurement of vessels and aircraft, the Secretary of the department in which the Coast Guard is operating, acting through the Commandant, shall consider the life-cycle cost estimates of vessels and aircraft, as applicable, during the design and evaluation processes to the maximum extent practicable.
Citations to §1171(7)
-
(A) keeping the Commandant informed of the progress of major acquisition programs (as that term is defined in section 1171);
-
(A) the Polar Security Cutters approved as part of a major acquisition program as of November 1, 2019; and
-
(3) to meet the needs of customers of major acquisition programs in the most cost-effective manner practicable.
-
(a) Notwithstanding section 1105(a)(2) of this title and section 23041 of title 10, and subject to subsections (b) and (c) of this section, the Secretary may acquire additional units procured under a Coast Guard major acquisition program contract, by extension of such contract without competition, if the Director of the Cost Analysis Division of the Department of Homeland Security determines that the costs that would be saved through award of a new contract in accordance with such sections would not exceed the costs of such an award.
-
(1) the costs that would be saved through award of a new major acquisition program contract in accordance with section 1105(a)(2) for the acquisition of a number of additional units specified by the Secretary; and
-
(b) The Commandant shall seek to maintain a memorandum of understanding or a memorandum of agreement with the Secretary of the Navy to obtain the assistance of the Office of the Assistant Secretary of the Navy for Research, Development, and Acquisition, including the Navy Systems Command, with the oversight of Coast Guard major acquisition programs. The memorandum of understanding or memorandum of agreement shall, at a minimum, provide for—(1) the exchange of technical assistance and support that the Assistant Commandants for Acquisition, Human Resources, Engineering, and Information technology may identify;(2) the use, as appropriate, of Navy technical expertise; and(3) the temporary assignment or exchange of personnel between the Coast Guard and the Office of the Assistant Secretary of the Navy for Research, Development, and Acquisition, including Naval Systems Command, to facilitate the development of organic capabilities in the Coast Guard.
-
(a) 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.
Citations to §1171(8)
-
(1) An individual may not be assigned as the project or program manager for a Level 1 acquisition unless the individual holds a Level III acquisition certification as a program manager.
-
(2) An individual may not be assigned as the project or program manager for a Level 2 acquisition unless the individual holds a Level II acquisition certification as a program manager.
Citations to §1171(9)
-
(3) 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) 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) 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.
-
(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.
-
(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.
Citations to §1171(10)
-
(a) 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.
Citations to §1171(11)
-
(H) operational test and evaluation phases;
-
(a) 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.
-
(5) 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.