Difference between revisions of "Anomaly Reports- Phase II"

From FPDS-NG
 
(11 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
<tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th>
 
<tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th>
 
<th width=34% align="center"><b>End Date</b></th></tr>
 
<th width=34% align="center"><b>End Date</b></th></tr>
−
<tr><td nowrap>BETA Installation </td><td nowrap>Friday Mar 16, 2012</td><td nowrap>Friday Mar 16, 2012</td></tr>
+
<tr><td nowrap>BETA Installation </td><td nowrap>Monday Mar 19, 2012</td><td nowrap>Monday Mar 19, 2012</td></tr>
 
<tr><td nowrap>Functional Qualification Testing</td><td nowrap>Tuesday Mar 20, 2012</td><td nowrap>Thursday Mar 22, 2012</td></tr>
 
<tr><td nowrap>Functional Qualification Testing</td><td nowrap>Tuesday Mar 20, 2012</td><td nowrap>Thursday Mar 22, 2012</td></tr>
 
<tr><td nowrap>Installation in Production</td><td nowrap>Friday Mar 30, 2012</td><td nowrap>Friday Mar 30, 2012</td></tr>
 
<tr><td nowrap>Installation in Production</td><td nowrap>Friday Mar 30, 2012</td><td nowrap>Friday Mar 30, 2012</td></tr>
Line 30: Line 30:
 
<td>What Delivery Orders/Task Orders and BPA Calls that were placed against an IDV by an agency that does not have the authority to use the Referenced IDV (based on the Who Can Use value on the iDV)
 
<td>What Delivery Orders/Task Orders and BPA Calls that were placed against an IDV by an agency that does not have the authority to use the Referenced IDV (based on the Who Can Use value on the iDV)
 
</td>
 
</td>
 +
<td>
 
1. A new Standard report, “Orders Referencing Incorrect IDV” shall be developed to display Delivery Orders/Task Orders and BPA Calls that were placed against an IDV by an agency that does not have the authority to use the Referenced IDV. Anomaly combinations are:
 
1. A new Standard report, “Orders Referencing Incorrect IDV” shall be developed to display Delivery Orders/Task Orders and BPA Calls that were placed against an IDV by an agency that does not have the authority to use the Referenced IDV. Anomaly combinations are:
−
<TABLE>
+
<TABLE id="box-table-b" border=2>
 
<th>IDV “Who can Use”</th><th>Order/Call’s Contracting Agency</th>
 
<th>IDV “Who can Use”</th><th>Order/Call’s Contracting Agency</th>
 
<tr><td>Defense</td><td>Civilians</td></tr>
 
<tr><td>Defense</td><td>Civilians</td></tr>
Line 38: Line 39:
 
<tr><td>Codes/Other</td><td>Agency outside the specified codes</td></tr>
 
<tr><td>Codes/Other</td><td>Agency outside the specified codes</td></tr>
 
</TABLE>
 
</TABLE>
−
+
 
 
2. This report shall have a Summary report that will display the dollars and the number of anomaly actions for a given Department
 
2. This report shall have a Summary report that will display the dollars and the number of anomaly actions for a given Department
  
Line 56: Line 57:
 
*Transaction Number
 
*Transaction Number
 
3. This report shall have award detail with comprises of the standard award detail plus the following fields
 
3. This report shall have award detail with comprises of the standard award detail plus the following fields
−
• IDV Who Can Use
+
*IDV Who Can Use
−
• IDV Department Name (ID)
+
*IDV Department Name (ID)
−
• IDV Contracting Agency Name (ID)
+
*IDV Contracting Agency Name (ID)
−
 
+
</td>
 +
<td>NO</td>
 +
</tr>
 +
<tr>
 +
<td>HOW; Unique Vendors Report</td>
 +
<td>How many Unique Vendors are used on contracts in a given Fiscal Year</td>
 
<td>
 
<td>
 +
*A new Standard report, “Unique Vendors” shall be developed to display the number of Unique DUNS numbers along with the Contracting Officer’s Determination of Business Size for a given Fiscal Year.
 +
*Final Stand-alone Awards (Purchase Orders (PO), Definitive Contracts (DCA)) and IDVs (FSS, GWAC, BOA, Part 13 BPA and IDC) shall be considered in this report.
 +
*The query screen will be modified to be able to select “Bases only”.
 
</td>
 
</td>
−
<td>NO</td>
+
<td>No</td>
 
</tr>
 
</tr>
−
 
−
<tr><td>HOW; Subcontracting Plan Report</td><td>How many final Stand Alone Award and IDV bases are marked as ‘Plan Required – Incentive Not Included’, ‘Plan Required – Incentive Included’ or ‘Plan Required (Pre 2004)’ in FPDS-NG for the Fiscal Year selected? What are the PIID level details for each of these actions so our department can validate against our internal systems? Is the data different between FPDS-NG and our internal system so we should correct it?
 
−
 
−
</td><td>1. A new Informatica Standard report, “Subcontracting Plan” shall be developed to display base documents that have chosen “Subcontracting Plan” as one of the following values:
 
−
 
−
*Plan Required – Incentive Not Included
 
−
 
−
*Plan Required – Incentive Included
 
−
 
−
*Plan Required (Pre 2004)
 
−
 
−
2. Final Purchase Orders (PO), Definitive Contracts (DCA), FSS, GWAC, BOA, BPA and IDC shall be considered in this report.
 
−
 
−
3. This report shall have a detail layout with details shown for each qualified PIID.
 
−
 
−
4. This report will include enhanced features being incorporated in standard reports. Details can be found at [https://www.fpds.gov/wiki/index.php/Standard_Reports_Enhancements-_Phase_II Standard Reports Enhancements- Phase-II]</td><td>NO</td></tr>
 
−
 
−
 
−
<tr><td>HOW; Competitive Procedures, but one Offer Report</td><td>How many ‘Competed Under SAP’, ‘Full and Open Competition’ ‘Full and Open Competition after Exclusion of Sources’ or ‘Fair Opportunity’ final contracts have only one offer marked in FPDS-NG for the Fiscal Year selected? What are the PIID level details for each of these actions so our department can initiate a corrective action?
 
−
 
−
</td><td>1. A new Informatica Standard report, “Competitive Procedures, but one Offer Report” shall be developed to display “Competed” documents that have received one offer.
 
−
 
−
2. The existing “Competition Report” shall serve as the basis for this report that would also include an additional condition of one offer.
 
−
 
−
3. This report shall have:
 
−
 
−
*A summarized layout by Department to highlight the “Competed” numbers
 
−
 
−
*Competed workflow to exclude Orders subject to Fair Opportunity
 
−
 
−
*Competed workflows to include Orders subject to Fair Opportunity
 
−
 
−
*Award Detail to display the contractual data for each PIID that qualifies to be in this report
 
−
 
−
4. This report will include enhanced features being incorporated in standard reports. Details can be found at [https://www.fpds.gov/wiki/index.php/Standard_Reports_Enhancements-_Phase_II Standard Reports Enhancements- Phase-II]
 
−
 
−
</td><td>NO</td></tr>
 
−
 
−
<tr><td>HOW; IDVs whose Orders are over the Ceiling Amount Report</td><td>How many IDVs have referencing Orders (Delivery/Task Orders and BPA Calls) whose cumulative dollar obligation is over the cumulative ultimate contract value? What are the PIID level details for each of these actions so our department can initiate a corrective action?
 
−
 
−
</td><td>1. A new Informatica Standard report, “IDVs whose Orders are over the Ceiling Amount” shall be developed.
 
−
 
−
2. Final Delivery/Task Orders and BPA Calls that have obligated dollars over their referenced IDVs’ ultimate contract value shall be considered in this report.
 
−
 
−
3. This report shall have a detail layout with details shown for each qualified PIID.
 
−
 
−
4. This report will include enhanced features being incorporated in standard reports. Details can be found at [https://www.fpds.gov/wiki/index.php/Standard_Reports_Enhancements-_Phase_II Standard Reports Enhancements- Phase-II]
 
−
</td><td>NO</td></tr>
 
−
 
−
<tr><td>HOW; Orders placed after IDV’s Last Date to Order Report</td><td>How many IDVs have referencing Orders (Delivery/Task Orders and BPA Calls) that were placed later than the Last Date to Order? What are the PIID level details for each of these actions so our department can initiate a corrective action?
 
−
 
−
</td><td>1. A new Informatica Standard report, “Orders placed after IDV’s Last Date to Order” shall be developed.
 
−
 
−
2. Final base Delivery/Task Orders and BPA Calls that are signed or have come into effect later than the “Last Date to Order” on their referenced IDVs shall be considered in this report.
 
−
 
−
3. This report shall have a detail layout with details shown for each qualified PIID.
 
−
 
−
4. This report will include enhanced features being incorporated in standard reports. Details can be found at [https://www.fpds.gov/wiki/index.php/Standard_Reports_Enhancements-_Phase_II Standard Reports Enhancements- Phase-II]
 
−
 
−
</td><td>NO</td></tr>
 
−
 
−
<tr><td>HOW; Small Top 100 Federal Contractors Report</td><td>How many top 100 Federal contractors are marked as "Small Business" in FPDS-NG?
 
−
 
−
</td><td>1. A new Informatica Standard report, “Small Top 100 Federal Contractors” shall be developed.
 
−
 
−
2. After the report is executed for Global level vendor, it shall be drilled down to the individual contractual level vendor and then the top 100 Federal Government contractors that are marked as “Small Business” by the contracting officers are identified and displayed.
 
−
 
−
3. This report shall have a detailed layout.
 
−
 
−
4. This report will include enhanced features being incorporated in standard reports. Details can be found at [https://www.fpds.gov/wiki/index.php/Standard_Reports_Enhancements-_Phase_II Standard Reports Enhancements- Phase-II]
 
−
 
−
</td><td>NO</td></tr>
 
 
</TABLE>
 
</TABLE>

Latest revision as of 15:52, 20 March 2012

Schedule

DescriptionStart Date End Date
BETA Installation Monday Mar 19, 2012Monday Mar 19, 2012
Functional Qualification TestingTuesday Mar 20, 2012Thursday Mar 22, 2012
Installation in ProductionFriday Mar 30, 2012Friday Mar 30, 2012

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary No
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
Online HelpNo
Computer-Based TrainingNo
User ManualNo
Report ManualYes
Help FilesYes

Report Listing

Report Category/Name#Business ObjectiveResolutionImpact to Users and Integrators
WHO; Orders Referencing Incorrect IDV What Delivery Orders/Task Orders and BPA Calls that were placed against an IDV by an agency that does not have the authority to use the Referenced IDV (based on the Who Can Use value on the iDV)

1. A new Standard report, “Orders Referencing Incorrect IDV” shall be developed to display Delivery Orders/Task Orders and BPA Calls that were placed against an IDV by an agency that does not have the authority to use the Referenced IDV. Anomaly combinations are:

IDV “Who can Use”Order/Call’s Contracting Agency
DefenseCivilians
CivilianDoD
Only My AgencyOther agencies
Codes/OtherAgency outside the specified codes

2. This report shall have a Summary report that will display the dollars and the number of anomaly actions for a given Department

3. The following drill path will be available

  • Department
  • Fiscal Year
  • IDV Who Can Use
  • Contracting Agency
  • MACOM
  • SUBCOM
  • Region Code
  • Contracting Office
  • Vendor Name
  • Reference PIID
  • PIID
  • Modification Number
  • Transaction Number

3. This report shall have award detail with comprises of the standard award detail plus the following fields

  • IDV Who Can Use
  • IDV Department Name (ID)
  • IDV Contracting Agency Name (ID)
 NO
HOW; Unique Vendors Report How many Unique Vendors are used on contracts in a given Fiscal Year
  • A new Standard report, “Unique Vendors” shall be developed to display the number of Unique DUNS numbers along with the Contracting Officer’s Determination of Business Size for a given Fiscal Year.
  • Final Stand-alone Awards (Purchase Orders (PO), Definitive Contracts (DCA)) and IDVs (FSS, GWAC, BOA, Part 13 BPA and IDC) shall be considered in this report.
  • The query screen will be modified to be able to select “Bases only”.
 No
Retrieved from "https://fpds.gov/wiki/index.php?title=Anomaly_Reports-_Phase_II&oldid=4065"