Difference between revisions of "Sustainability Attributes Report"

From FPDS-NG

 
 
(15 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>Monday November 26, 2012</td><td nowrap>Monday November 26, 2012</td></tr>
+
<tr><td nowrap>BETA Installation </td><td nowrap>Tuesday December 11, 2012</td><td nowrap>Tuesday December 11, 2012</td></tr>
−
<tr><td nowrap>Functional Qualification Testing </td><td nowrap>Tuesday November 27, 2012</td><td nowrap>Thursday November 27, 2012</td></tr>
+
<tr><td nowrap>Functional Qualification Testing </td><td nowrap>Wednesday December 12, 2012</td><td nowrap>Thursday December 13, 2012</td></tr>
−
<tr><td nowrap>Installation in Production</td><td nowrap>Friday November 30, 2012</td><td nowrap>Friday November 30, 2012</td></tr>
+
<tr><td nowrap>Installation in Production</td><td nowrap>Friday December 21, 2012</td><td nowrap>Friday December 21, 2012</td></tr>
 
</table>
 
</table>
 
==Document Changes==
 
==Document Changes==
 
<TABLE border=2 id="box-table-a">
 
<TABLE border=2 id="box-table-a">
 
<tr><th align="center"><b>Documentation</b></th><th align="center"><b>Changes Required</b></th></tr>
 
<tr><th align="center"><b>Documentation</b></th><th align="center"><b>Changes Required</b></th></tr>
−
<tr><td nowrap>XML Specifications</td><td align="center">Yes</td></tr>
+
<tr><td nowrap>XML Specifications</td><td align="center">No</td></tr>
−
<tr><td nowrap>Web Services</td><td align="center">Yes</td></tr>
+
<tr><td nowrap>Web Services</td><td align="center">No</td></tr>
−
<tr><td nowrap>Data Dictionary </td><td align="center">Yes</td></tr>
+
<tr><td nowrap>Data Dictionary </td><td align="center">No</td></tr>
 
<tr><td nowrap>NASA Specific Data Dictionary</td><td align="center">No</td></tr>
 
<tr><td nowrap>NASA Specific Data Dictionary</td><td align="center">No</td></tr>
−
<tr><td nowrap>Use Case Summary</td><td align="center">Yes</td></tr>
+
<tr><td nowrap>Use Case Summary</td><td align="center">No</td></tr>
−
<tr><td nowrap>Validation Rules</td><td align="center">Yes</td></tr>
+
<tr><td nowrap>Validation Rules</td><td align="center">No</td></tr>
 
<tr><td nowrap>Reporting</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Reporting</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Online Help</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Online Help</td><td align="center">Yes</td></tr>
−
<tr><td nowrap>User Manual</td><td align="center">Yes</td></tr>
+
<tr><td nowrap>User Manual</td><td align="center">No</td></tr>
 
</table>
 
</table>
 
==SPR Listing==
 
==SPR Listing==
Line 26: Line 26:
 
<tr>
 
<tr>
  
−
<td style="width:120px" valign="center">Inherently Governmental Functions - Software Changes</td>
+
<td style="width:120px" valign="center">Sustainability Report</td>
−
<td>FPDS-NG needs to provide a method for identifying the records outlined in the OMB policy letter in a more efficient manner.  Therefore, FPDS needs to create and implement a back end procedure to identify the following by means of a tag in the “Description of Requirement” field:  
+
<td>As per the requirements provided by GSA:
  
−
1. For actions closely associated to Inherently Governmental Functions: include “Closely Associated” in the “Description of Requirement” field
+
1. The assessment of agency progress is being determined by inclusion of required clauses in a contract action as recorded in FPDS against a baseline of all the applicable contract actions.
  
−
2. For critical functions: include “Critical Functions” in the “Description of Requirement” field
+
2. The data to be extrapolated and used for analysis include:
  
−
3. For other functions:  include “Other Functions” in the “Description of Requirement” field 
+
a. The total $ obligated by agency for each attribute in 8L
  
−
An XML tag shall be created for each of the OMB mandated categories. Existing actions shall also be identified and tagged. Users shall be able to easily query these actions by category. The tags shall be allowed for any action, created via any means. The information will be available via ATOM feeds, web services, Standard and Ad hoc Reports.
+
b. The total # of transactions by agency for each attribute in 8L
  
−
<td> <b>DATA COLLECTION</b>
+
c. The total $ obligated by agency for the sum of all attributes in 8L as a percentage of the total $ obligated through eligible contracts by the agency
  
−
1. Civilian Awards and IDVs signed on or after 03/01/2012, having “Product or Service Code” as a ‘Service’ (PSC starting with A through Z) should answer whether the value of the "Inherently Governmental Functions" (IGF) is one of the following  in the “Description of Requirements” data element:
+
d. The total # of transactions by agency for  the sum of all the attributes in 8L as a percentage of the total # of eligible transactions by agency
  
−
  1.'Closely Associated Functions' (CL)
+
e. The PSC associated with each of the obligations/transactions (will mean a unique line item for each obligation/transaction)
−
  2.'Critical Functions' (CT)
 
−
  3.'Other Functions' (OT)
 
−
  4.The combination of CL and CT
 
  
−
Note: IGT is optional for DoD.
+
f. The NAICS associated with each of the obligations/transactions (will mean a unique line item for each obligation/transaction)
  
−
2. Following are the allowable formats to submit the IGF value:
+
3. In determining the eligible contracts for the standard report, contracts for weapons systems will be excluded.
  
−
  1.IGF::CL::IGF
+
4. In determining the eligible contracts for the standard report, contracts with place of performance outside the United States will be excluded.  If the agency head determines that application of sustainable to this type of contract is in the best interest of the US (as allowed by the EO), the agency would need to run their own ad-hoc report to add those actions and dollars back in to both the baseline and the award.
−
  2.IGF::CT::IGF
 
−
  3.IGF::OT::IGF
 
−
  4.IGF::CL,CT::IGF or IGF::CT,CL::IGF
 
  
−
Validation rules shall be displayed if an invalid IGF format or value is submitted.
+
<td> The purpose of the report is to determine the type and usage of Recovered Materials.
  
−
3. FPDS-NG shall display a validation rule to prevent the IGF entry if a valid IGF value is provided for a pre 03/01/2012 base document or a modification document done against a pre 03/01/2012 base document.
+
1. The new standard report, “Sustainability Report” shall be placed in the “HOW” category.
  
−
4. FPDS-NG shall extract the IGF value from the “Description of Requirements” field only if “Product or Service Code” is a ‘Service’.
+
2. The search criteria screen shall offer the following filters:
  
−
5. This enhancement shall apply to the following document types:
+
  1. From Date (mm/dd/yyyy) – mandatory
 +
  2. To Date (mm/dd/yyyy) – mandatory
 +
  3. From PSC - optional
 +
  4. To PSC - optional
 +
  5. NAICS - optional
 +
  6. Department ID - optional
 +
  7. Contracting Agency ID - optional
 +
  8. Organization Code - optional
 +
  9. Contracting Office Region - optional
 +
  10. Contracting Office ID - optional
  
−
  1.Purchase Order
+
3. The eligible Document Types (includes base documents and their modifications) are:
−
  2.Definitive Contract
 
−
  3.Delivery/Task Order
 
−
  4.BPA Call
 
−
  5.BOA
 
−
  6.BPA
 
−
  7.IDC
 
  
−
6. This enhancement shall apply to the following contractual operations:
+
  1. DO
 +
  2. PO
 +
  3. DCA
 +
  4. BPA Call (Part 8 and Part 13)
 +
  5. GWAC
 +
  6. IDC
  
−
  1.Create
+
4. The report shall represent the data in the following forms:
−
  2.Update
 
−
  3.isComplete
 
−
  4.Approve
 
−
  5.Correct
 
  
−
<b>DATA MANAGEMENT</b>
+
  1. Summary report
 +
  2. Drill-path
 +
  3. Award Detail
  
−
For the existing data that are signed on or later than 03/01/2012 and that have a PSC as a Service, if the “Description of Requirements” field contains the following phrases, the corresponding labels defined below will be applied:
+
5. The report shall exclude the following:
  
−
   1. "Closely Associated" - IGF::CL::IGF
+
  1.   Actions that are performed outside of the US.  
−
  2. "Critical Function" - IGF::CT::IGF
+
  2.  Actions that have "Claimant Code" as 'Weapon Systems':
−
   3. "Other Function" - IGF::OT::IGF
+
        A1A, A1B, A1C, A2, A3, A4A, A5 or A6.
−
  4. "Closely Associated and Critical Function" - IGF::CL,CT::IGF
 
−
  5. "Critical Function and Closely Associated" - IGF::CL,CT::IGF
 
  
−
General processing rules for all of the above:
+
6. Description, Appendix and Help File shall be provided to help the users about the report.
−
 
 
−
1. All words in each phrase must be consecutive (if an additional word(s) appears between the words listed above, they will be ignored. Only white spaces are allowed in between words).
 
−
 
 
−
2. Searches are not case sensitive.
 
−
 
 
−
3. If the word “not” or other negation wording appears, the contract will still get tagged as defined above
 
−
 
 
−
'''NOTE''': If the “Description of Requirements” field does not contain the phrases mentioned above, then FPDS-NG will not tag such data. Agencies should correct the data.
 
−
 
 
−
<b> DATA DISSEMINATION</b>
 
−
 
 
−
1. ezSearch and ICD shall allow IGF search and display data accordingly.
 
−
 
 
−
2. Atom Feeds shall display IGF data in a separate tag.
 
−
 
 
−
3. The Award Detail for Standard reports shall be enhanced to display the IGF values in a separate column. 
 
−
 
 
−
4. The Ad hoc report function shall allow users to search and filter for IGF values and display data accordingly.
 
−
 
 
−
<b>DOCUMENTATION</b>
 
−
 
 
−
The documentation for Data Validation Rules, Reports, ezSearch, ICD, Atom Feeds, FAQs, User Manuals and Schema updates shall be updated to reflect the details of this enhancement @ https://www.fpds.gov/fpdsng_cms/index.php/worksite
 
−
</td>
 
−
<td align="center">No</td>
 
−
 
 
−
<tr>
 
−
<td style="width:95px" valign="center">Inherently Governmental Functions Actions and Dollars Standard Report</td>
 
−
<td>To report the Inherently Governmental Functions actions and dollars, a new Standard Report shall be created. 
 
−
 
 
−
<td><b>INHERENTLY GOVERNMENTAL FUNCTIONS ACTIONS AND DOLLARS REPORT</b>
 
−
 
 
−
1. This report shall be Government-wide and may be executed by the Federal Government and the public.
 
−
 
 
−
2. This report shall be included in the “WHAT” category.
 
−
 
 
−
3. This report shall display <b>final service actions (when PSC is a ‘service’)</b> for the following “Inherently Governmental Functions” values:
 
−
 
 
−
  1.‘Closely Associated Functions’
 
−
  2.‘Critical Functions’
 
−
  3.‘Other Functions’
 
−
  4.‘Null Inherently Governmental Functions’
 
−
 
 
−
NOTE: The actions whose IGF value is a combination of 'Closely Associated Functions' and 'Critical Functions' are counted in both the 'Closely Associated Functions' and 'Critical Functions' areas.
 
−
 
 
−
4. This report shall include all finalized base and modification documents for the following document types:
 
−
 
 
−
  1.Purchase Order
 
−
  2.Definitive Contract
 
−
  3.Delivery/Task Order
 
−
  4.BPA Call
 
−
  5.BOA
 
−
  6.BPA
 
−
  7.IDC
 
−
 
 
−
5. This report shall offer the following search filters:
 
−
 
 
−
  1.From Date - mandatory
 
−
  2.To Date - mandatory
 
−
  3.Department ID - optional
 
−
  4.(Contracting) Agency ID - optional
 
−
  5.Organization Code - optional
 
−
  6.Contracting Office Region - optional
 
−
  7.Contracting Office - optional
 
−
 
 
−
6. The search criteria screen shall display the following two footnotes:
 
−
 
 
−
<b>"From Date" and "To Date" correspond to the "Date Signed" on the FPDS-NG documents.</b>
 
−
 
 
−
<b>FPDS-NG started accepting data for ‘Inherently Governmental Functions’ with date signed on or after March 1, 2012.</b>
 
−
 
 
−
7. This report shall offer a Summary report, a drill path and an Award Detail.
 
−
 
 
−
<b>SUMMARY REPORT</b>
 
−
 
 
−
The Summary report shall offer the following columns:
 
−
 
 
−
  1.Department Name (Code)
 
−
  2.Total Actions (IGF value + no IGF value)
 
−
  3.Total Dollars (IGF value + no IGF value)
 
−
  4.Closely Associated Actions
 
−
  5.Closely Associated Dollars
 
−
  6.Critical Functions Actions
 
−
  7.Critical Functions Dollars
 
−
  8.Other Functions Actions
 
−
  9.Other Functions Dollars
 
−
  10.Null IGF Actions
 
−
  11.Null IGF Dollars
 
−
 
 
−
<b>DRILL PATH</b>
 
−
 
 
−
The drill path shall offer the following selections:
 
−
 
 
−
  1.Fiscal Year
 
−
  2.Contracting Agency
 
−
  3.Major Command Code (for DoD)
 
−
  4.Sub command Code 1 (for DoD)
 
−
  5.Sub command Code 2 (for DoD)
 
−
  6.Sub command Code 3 (for DoD)
 
−
  7.Contracting Office Region
 
−
  8.Contracting Office
 
−
  9.Vendor Name
 
−
  10.Referenced IDV PIID
 
−
  11.PIID
 
−
  12.Modification Number
 
−
  13.Transaction Number (for DoD)
 
−
 
 
−
<b>AWARD DETAIL</b>
 
−
 
 
−
Award Detail shall be the standard version (that the "Federal Contract Actions and Dollars Report displays), with an additional column for the "Inherently Governmental Functions".
 
−
 
 
−
8. This report shall offer a Preview with a snapshot of the Summary report, Award Detail, Description and Appendix.
 
−
 
 
−
9. The standard Informatica features like Active Filters, Export, Send, Charts, Show/Hide Header and Footer, Workflow, Show/Hide Table, Show/Hide report data actions tabs shall apply to this report.
 
−
 
 
−
10. A Help File shall be developed to assist users with the functionality of this report.
 
  
 
</td>
 
</td>

Latest revision as of 16:00, 18 December 2012

Schedule

DescriptionStart Date End Date
BETA Installation Tuesday December 11, 2012Tuesday December 11, 2012
Functional Qualification Testing Wednesday December 12, 2012Thursday December 13, 2012
Installation in ProductionFriday December 21, 2012Friday December 21, 2012

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary No
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
ReportingYes
Online HelpYes
User ManualNo

SPR Listing

SPR #EnhancementSolutionImpact to Users and Integrators
Sustainability Report As per the requirements provided by GSA:

1. The assessment of agency progress is being determined by inclusion of required clauses in a contract action as recorded in FPDS against a baseline of all the applicable contract actions.

2. The data to be extrapolated and used for analysis include:

a. The total $ obligated by agency for each attribute in 8L

b. The total # of transactions by agency for each attribute in 8L

c. The total $ obligated by agency for the sum of all attributes in 8L as a percentage of the total $ obligated through eligible contracts by the agency

d. The total # of transactions by agency for the sum of all the attributes in 8L as a percentage of the total # of eligible transactions by agency

e. The PSC associated with each of the obligations/transactions (will mean a unique line item for each obligation/transaction)

f. The NAICS associated with each of the obligations/transactions (will mean a unique line item for each obligation/transaction)

3. In determining the eligible contracts for the standard report, contracts for weapons systems will be excluded.

4. In determining the eligible contracts for the standard report, contracts with place of performance outside the United States will be excluded. If the agency head determines that application of sustainable to this type of contract is in the best interest of the US (as allowed by the EO), the agency would need to run their own ad-hoc report to add those actions and dollars back in to both the baseline and the award.

The purpose of the report is to determine the type and usage of Recovered Materials.

1. The new standard report, “Sustainability Report” shall be placed in the “HOW” category.

2. The search criteria screen shall offer the following filters: 

  1.	From Date (mm/dd/yyyy) – mandatory
  2.	To Date (mm/dd/yyyy) – mandatory
  3.	From PSC - optional
  4.	To PSC - optional
  5.	NAICS - optional
  6.	Department ID - optional
  7.	Contracting Agency ID - optional
  8.	Organization Code - optional
  9.	Contracting Office Region - optional
  10.	Contracting Office ID - optional

3. The eligible Document Types (includes base documents and their modifications) are: 

  1.	DO
  2.	PO
  3.	DCA
  4.	BPA Call (Part 8 and Part 13)
  5.	GWAC
  6.	IDC

4. The report shall represent the data in the following forms: 

  1.	Summary report
  2.	Drill-path
  3.	Award Detail

5. The report shall exclude the following: 

  1.   Actions that are performed outside of the US. 
  2.   Actions that have "Claimant Code" as 'Weapon Systems':
       A1A, A1B, A1C, A2, A3, A4A, A5 or A6.

6. Description, Appendix and Help File shall be provided to help the users about the report.

No
Retrieved from "https://fpds.gov/wiki/index.php?title=Sustainability_Attributes_Report&oldid=4175"