Difference between revisions of "Anomaly Reports- Phase II"

From FPDS-NG

 
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>

Latest revision as of 14: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