Anomaly Reports
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
From FPDS-NG
Schedule
Description | Start Date | End Date |
---|---|---|
BETA Installation | Friday 12/01/2011 | Friday 12/01/2011 |
Functional Qualification Testing | Monday 12/05/2011 | Friday 12/09/2011 |
Installation in Production | Thursday 12/15/2011 | Thursday 12/15/2011 |
Document Changes
Documentation | Changes Required |
---|---|
XML Specifications | No |
Web Services | No |
Data Dictionary | No |
NASA Specific Data Dictionary | No |
Use Case Summary | No |
Validation Rules | No |
Online Help | No |
Computer-Based Training | No |
Report Manual | Yes |
User Manual | No |
Help Files | Yes |
Report Listing
Report Category/Name# | Business Objective | Resolution | Impact to Users and Integrators |
---|---|---|---|
HOW; Contract Termination for Default-Cause Report | How many final Award and IDV modifications are marked as either ‘Terminate for Cause’ or ‘Terminate for Default (complete or partial)’ 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? | 1. A new Informatica Standard report, “Contract Termination For Default/Cause” shall be developed to display modification documents that have chosen “Reason for Modification” as one of the following values:
2. Final Delivery/Task Orders (DO/TO), Purchase Orders (PO), Definitive Contracts (DCA), BPA Calls, 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 Standard Reports Enhancements- Phase_II | NO |
HOW; Subcontracting Plan Report | 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? | 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:
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 Standard Reports Enhancements- Phase-II | NO |
HOW; Competitive Procedures, but one Offer Report | 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? | 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:
4. This report will include enhanced features being incorporated in standard reports. Details can be found at Standard Reports Enhancements- Phase-II | NO |
HOW; IDVs whose Orders are over the Ceiling Amount Report | 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? | 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 Standard Reports Enhancements- Phase-II | NO |
HOW; Orders placed after IDV’s Last Date to Order Report | 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? | 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 Standard Reports Enhancements- Phase-II | NO |
HOW; Small Top 100 Federal Contractors Report | How many top 100 Federal contractors are marked as "Small Business" in FPDS-NG? | 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 Standard Reports Enhancements- Phase-II | NO |