<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://riskengineering.org/index.php?action=history&amp;feed=atom&amp;title=Predictive_analytics</id>
	<title>Predictive analytics - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://riskengineering.org/index.php?action=history&amp;feed=atom&amp;title=Predictive_analytics"/>
	<link rel="alternate" type="text/html" href="https://riskengineering.org/index.php?title=Predictive_analytics&amp;action=history"/>
	<updated>2026-09-15T08:54:24Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://riskengineering.org/index.php?title=Predictive_analytics&amp;diff=261&amp;oldid=prev</id>
		<title>Pooyan at 23:23, 29 November 2025</title>
		<link rel="alternate" type="text/html" href="https://riskengineering.org/index.php?title=Predictive_analytics&amp;diff=261&amp;oldid=prev"/>
		<updated>2025-11-29T23:23:54Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;a href=&quot;https://riskengineering.org/index.php?title=Predictive_analytics&amp;amp;diff=261&amp;amp;oldid=260&quot;&gt;Show changes&lt;/a&gt;</summary>
		<author><name>Pooyan</name></author>
	</entry>
	<entry>
		<id>https://riskengineering.org/index.php?title=Predictive_analytics&amp;diff=260&amp;oldid=prev</id>
		<title>Pooyan: Created page with &quot;== Basic considerations ==   == Logical Framework ==   == Legislative Framework ==   == Procurement/Contractual Framework == ==  The Contracting objective is to ensure that the client (public or private) receives conforming products and services while keeping the overall costs of client contract surveillance reasonable. This objective is based on the premise that the Contractor is responsible for the management and quality control of the contract products and services an...&quot;</title>
		<link rel="alternate" type="text/html" href="https://riskengineering.org/index.php?title=Predictive_analytics&amp;diff=260&amp;oldid=prev"/>
		<updated>2025-11-29T23:17:33Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;== Basic considerations ==   == Logical Framework ==   == Legislative Framework ==   == Procurement/Contractual Framework == ==  The Contracting objective is to ensure that the client (public or private) receives conforming products and services while keeping the overall costs of client contract surveillance reasonable. This objective is based on the premise that the Contractor is responsible for the management and quality control of the contract products and services an...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Basic considerations ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Logical Framework ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Legislative Framework ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Procurement/Contractual Framework == ==&lt;br /&gt;
&lt;br /&gt;
The Contracting objective is to ensure that the client (public or private) receives conforming products and services while keeping the overall costs of client contract surveillance reasonable. This objective is based on the premise that the Contractor is responsible for the management and quality control of the contract products and services and the client is responsible for performance assessment.&lt;br /&gt;
&lt;br /&gt;
The client interfaces to the contractor on a number of levels; the contract level, the periodic work plan level, the work package level and often for critical deliverables or products and services.[1]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Practice Framework ==&lt;br /&gt;
&lt;br /&gt;
=== Information Technology ===&lt;br /&gt;
&lt;br /&gt;
Microsoft Press defines Acceptance Criteria as “Conditions that a software product must satisfy to be accepted by a user, customer or other stakeholder.” Google defines them as “Pre-established standards or requirements a product or project must meet.”&lt;br /&gt;
&lt;br /&gt;
* Acceptance Criteria are a set of statements, each with a clear pass/fail result, that specify both functional (e.g., minimal marketable functionality) and non-functional (e.g., minimal quality) requirements applicable at the current stage of project integration. These requirements represent “conditions of satisfaction.” There is no partial acceptance: either a criterion is met or it is not.[2]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Further Guidance ==&lt;br /&gt;
&lt;br /&gt;
=== Contracting Definitions ===&lt;br /&gt;
&lt;br /&gt;
* “Acceptance” is defined as the act of an authorized representative of the Government such as a Task Order Manager or COTR by which the Government, for itself or as agent of another, approves specific deliverables, products, or services (“deliverables”) rendered as partial or complete performance of the contract, task order or PG quality requirements (“contract quality requirements”) (Also reference FAR 52.256-5 Inspection of Services – Cost Reimbursement).&lt;br /&gt;
&lt;br /&gt;
* “Authorized Company Certifying Official” is defined as a certification attested to by an authorized representative of the Contractor.&lt;br /&gt;
&lt;br /&gt;
* “Acceptable Quality Level” is the maximum allowable quantity of non-conforming products or services defined as either an absolute number or as a percent defective (or defects per hundred units) for which lots will be accepted; most of the time by the sampling procedures being used.&lt;br /&gt;
&lt;br /&gt;
* “Certification” is defined as the act of determining, verifying, and attesting in writing to the status of deliverables, personnel, processes, procedures, or items in accordance with specified requirements.&lt;br /&gt;
&lt;br /&gt;
* “Certification System” is defined as the administrative procedures for completing, reviewing, and approving the certificate of conformance; signed by an authorized party responsible for overall quality of the product or service.&lt;br /&gt;
&lt;br /&gt;
* “Certificate of Conformance” is defined as a document signed or otherwise authenticated by an authorized individual certifying the degree to which items or services meet specified requirements.&lt;br /&gt;
&lt;br /&gt;
* “Contract quality requirements” are the technical requirements in the contract relating to the quality of the product or service and those contract clauses prescribing inspection, and other quality controls incumbent on the PMO contractor, to assure that the deliverable conforms to the contractual requirements. (Task Order and Contract are used interchangeably in this definition.)&lt;br /&gt;
&lt;br /&gt;
* “Conditional acceptance” is defined as the acceptance of deliverables that do not conform to contract quality requirements, or are otherwise incomplete, that the contractor is required to correct or otherwise complete by a specified date.&lt;br /&gt;
&lt;br /&gt;
* “Critical nonconformance” means a nonconformance (inclusive of being incomplete or delayed as applicable) that is likely to prevent performance (at the programmatic level) of a vital oversight function or substantially reduce the usability, functionality or reliability of the products or services for their intended end purpose.&lt;br /&gt;
&lt;br /&gt;
* “Critical Requirements”: Critical requirements are ones that are vital to the programmatic oversight function.&lt;br /&gt;
** Examples of vital programmatic oversight functions are contractor products that are major inputs into critical decisions that are transmitted to senior executives, legislative staff, or other agencies.&lt;br /&gt;
&lt;br /&gt;
* “Government contract quality assurance” means the various functions, including inspection, performed to determine whether a contractor has fulfilled the contract obligations pertaining to quality and quantity.&lt;br /&gt;
&lt;br /&gt;
* “Inspection” is defined as the examination and testing supplies or services to determine whether they conform to contract requirements.&lt;br /&gt;
&lt;br /&gt;
* “Latent Defect” is defined as a defect that exists at the time of acceptance but cannot be discovered by a reasonable inspection.&lt;br /&gt;
&lt;br /&gt;
* “Major nonconformance” means a nonconformance, other than critical, that is likely to materially reduce the usability, functionality or reliability of the products or services for their intended end purpose.&lt;br /&gt;
&lt;br /&gt;
* “Minor nonconformance” means a nonconformance that is not likely to materially reduce the usability, functionality or reliability of the products or services for their intended end purpose, or is a departure from established standards having little bearing on the effective use of the products or services, or reliance on the contractor’s assessments, evaluations or data.&lt;br /&gt;
&lt;br /&gt;
* “Patent Defect” is defined as any defect that exists at the time of acceptance and is not a latent defect.&lt;br /&gt;
&lt;br /&gt;
* “Quality Assurance” (QA) is defined as those actions taken by the government to check PMO contractor performed services to determine whether they meet the requirements and specifications of the work statement. QA activities include all those actions that provide confidence that the required level of quality for contractor products and services is achieved.&lt;br /&gt;
&lt;br /&gt;
* “Quality Assurance Surveillance” is defined as the monitoring of PMO contractor performance to assure that services received are timely and consistent with contract quality requirements.&lt;br /&gt;
&lt;br /&gt;
* “Quality Assurance Surveillance Plan” (QASP) is defined as the document used for contract quality assurance planning.&lt;br /&gt;
&lt;br /&gt;
* “Quality Control” (QC) is defined as those actions taken by the PMO contractor to control the output of services so that they meet the requirements and specifications of the*&lt;/div&gt;</summary>
		<author><name>Pooyan</name></author>
	</entry>
</feed>