View source for Detail Release Notes V1.4

From FPDS-NG

You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in the group: Users.
You can view and copy the source of this page.
__NOEDITSECTION__
==Schedule==      
<TABLE border=2 id="box-table-a" style="width:460px">
<tr><th align="center"><b>Description</b></th><th align="center"><b>Start Date</b></th><th align="center"><b>End Date</b></th></tr>
<tr><td nowrap>Phase I Alpha</td><td nowrap>November 23, 2009</td><td nowrap>December 3, 2009</td></tr>
<tr><td nowrap>Phase I Functional Qualification Testing</td><td nowrap>December 14, 2009</td><td nowrap>December 23, 2009</td></tr>
<tr><td nowrap>Phase II Alpha</td><td nowrap>January 11, 2010</td><td nowrap>January 22, 2010</td></tr>
<tr><td nowrap>Phase II Functional Qualification Testing</td><td nowrap>February 8, 2010</td><td nowrap>February 26, 2010</td></tr>
<tr><td nowrap>Installation in Production</td><td nowrap>March 12, 2010</td><td nowrap>March 12, 2010</td></tr>
</table>
==Documentation Changes== 
<TABLE border=2 id="box-table-a" style="width:470px">
<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>Web Services</td><td align="center">Yes</td></tr>
<tr><td nowrap>Data Dictionary </td><td align="center">Yes</td></tr>
<tr><td nowrap>NASA Specific Data Dictionary</td><td align="center">Yes</td></tr>
<tr><td nowrap>Use Case Summary</td><td align="center">Yes</td></tr>
<tr><td nowrap>Validation Rules</td><td align="center">Yes</td></tr>
<tr><td nowrap>Online Help</td><td align="center">Yes</td></tr>
<tr><td nowrap>Computer-Based Training</td><td align="center">Yes</td></tr>
<tr><td nowrap>Report Manual</td><td align="center">Yes</td></tr>
</table>

==Description Of Changes==
===Treasury Account Symbol===
<ul><li>GUI element “Treasury Account Symbol” with sub elements “Agency Identifier”, “Main Account”, “Sub Account” will be added to the Document Information section for Version 1.3 and Version 1.4
</li><li>A read-only GUI element “Initiative” will be added to the Document Information section of the screen for Version 1.3 and Version 1.4.
</li><li>Version 1.4 XML schema will accommodate for the above data elements. There is no impact on earlier Version schemas
</li><li>For Civilian documents with a positive or negative obligation, “Agency Identifier”, “Main Account” portions of “Treasury Account Symbol” is mandatory to ‘approve’ or ‘correct’ of Version 1.3 and higher Version documents.
</li><li>For Civilian documents with no dollars obligated, “Agency Identifier”, “Main Account” portions of “Treasury Account Symbol” is optional.
</li><li>For Civilian documents regardless of the dollars obligated, “Sub Account” portion of the “Treasury Account Symbol” is optional
</li><li>The Civilian rules as above apply for NASA grant and cooperative agreement, and space act agreement documents. NASA Intergovernmental actions will not have the symbol available.
</li><li>For DoD documents, regardless of the dollars obligated, “Agency Identifier”, “Main Account”, “Sub Account” portions of the “Treasury Account Symbol” are optional
</li><li>The “Initiative” field is a read-only field on the screen and any value sent through Business Services will be ignored. Recovery actions will be identified based on the “Treasury Account Symbol” and the field will be populated with ‘American Recovery and Reinvestment Act'
</li><li><b>Submitting Values for Treasury Account Symbol</b>
*Version 1.4: The value can be entered on the GUI fields available on the Web Portal/launching the GUI screen or through Business Services using the appropriate XML tags as defined in the Version 1.4 schema
*Version 1.3: The value can be entered on the GUI fields by launching the GUI screen or through the Business Services under the “descriptionOfContractRequirement” XML tag in the format TAS::XX XXXX::TAS or TAS::XX XXXX XXX::TAS. When the Version 1.3 screen is launched, all TAS codes submitted will display in the “Treasury Account Symbol” GUI element
</li><li>“Treasury Account Symbol” will be added to Award Detail of all Standard reports. It will be available on ezSearch, ICD, Adhoc\ BI views, and all search features.
</li><li>“Initiative” will be added to the Adhoc attribute listing
</li><li>[http://www.fpdsng.com/downloads/Unification_validation_rules.xls Click here] for Validation Rules
</li><li>Use cases changes are listed in the [http://www.fpdsng.com/downloads/FPDSNG_DataDictionary_V1.4.pdf Data Dictionary]
</li><li>Appropriate changes will be made to the User manual, Data Dictionary, Validation rules and Other documentation as necessary
</li></ul>
<TABLE id="box-table-a" border=2 style="width:750px">
<tr><th colspan=2 align="center"><b>Impact Analysis for Users and Integrators</b></th></tr>
<tr><td nowrap>GUI Interface</td><td valign="left">New fields will be added to the Version 1.3, Version 1.4 screens</td></tr>
<tr><td nowrap>Business Services</td><td valign="left">Treasury Account Symbol will be required for Civilian agencies</td></tr>
<tr><td nowrap>Reports and Report Services</td><td valign="left">Treasury Account Symbol will be added to the “Award Detail” of Standard Report. Treasury Account Symbol and Initiative will be available as attribute in Adhoc.</td></tr>
<tr><td nowrap>Data Dissemination</td><td valign="left">XML archives for Version 1.4 will contain the Treasury Account Symbol.</td></tr>
</TABLE>

===BPA, BOA, BPA Call for DoD===
<ul><li>
BPA, BOA and BPA Call modules will be available for DoD users starting Version 1.4
</li><li>The existing Award privileges will apply for a BPA Call and IDV privileges will apply for BPA and BOA
</li><li>BPA/BPA Call for DoD
* DoD users will be able to enter a BPA as a Part 8 that references an FSS and a Part 13 BPA that is a stand alone BPA with the 9th character of the PIID as ‘A’.
* Starting Version 1.4, DoD users will not be able to create an IDC document type with the 9th character of the PIID as ‘A’
* Starting Version 1.4, FPDS-NG will ensure DoD users use the BPA Call form and not the Delivery Order form to place orders against Civilian BPA/Version 1.4 DoD BPA.
* DoD users can continue to place Delivery Orders against existing IDC’s with 9th character as ‘A’
* DoD BPA Calls will have a provision to provide transaction number
* Obligation amount for a DoD BPA can only be $0
</li><li>BOA for DoD
* DoD users will be able to create BOA document types starting Version 1.4 with the 9th character of the PIID as ‘G’
* Starting Version 1.4, DoD users will not be able to create an IDC document type with the 9th character of the PIID as ‘G’
* DoD users will continue to be able to create Delivery Orders referencing Version 1.4 BOA/Prior version IDC with 9th character as ‘G’
* Obligation amount for a DoD BOA can only be $0
</li><li>DoD and Civilians
* “Multiple or Single Award IDV” will be required on a Version 1.4 BOA for Civilian and DoD
* When a Delivery Order is referencing a Multiple Award BOA, the “Solicitation Procedures” on the Delivery Order will be open for user’s selection
* On a BPA Call referencing Part 13 BPA and a Delivery Order referencing BOA, for both DoD and Civilian 
**“Extent Competed” can only be ‘Competed Under SAP’ or ‘Not Competed Under SAP’
**“Solicitation Procedures” can only be ‘Simplified Acquisition’
</li><li>The new documents will be available via the following applications:
* ezSearch
* ICD
* BI Views
* Adhoc reports
* Advanced Search
</li><li>[http://www.fpdsng.com/downloads/Unification_validation_rules.xls Click here] for Validation Rules
</li><li>Use cases changes are listed in the [http://www.fpdsng.com/downloads/FPDSNG_DataDictionary_V1.4.pdf Data Dictionary]
</li><li>Appropriate changes will be made to the User manual, Data Dictionary, Validation rules and Other documentation as necessary
</li></ul>
<TABLE id="box-table-a" border=2 style="width:750px">
<tr><th colspan=2 align="center"><b>Impact Analysis for Users and Integrators</b></th></tr>
<tr><td style="width:200px">GUI Interface</td><td valign="left">New forms available for DoD</td></tr>
<tr><td nowrap>Business Services</td><td valign="left">New forms available for DoD</td></tr>
<tr><td nowrap>Reports and Report Services</td><td valign="left">New document types will be available for DoD in the reports</td></tr>
<tr><td nowrap>Data Dissemination</td><td valign="left">Version 1.4 data archives will contain the new DoD document types</td></tr>
</TABLE>

===Other Transactions for DoD and DHS===
<ul><li>DoD and DHS will be able to report “Other Transactions” to FPDS-NG starting Version 1.4
</li><li>There will be three forms available on the FPDS-NG Home Page only to DHS and DoD
*Other Transaction Agreement (under the Award section)
*Other Transaction Order (under the Award section)
*Other Transaction IDV  (under the IDV section)
</li><li>Other Transaction Orders can only reference approved Other Transaction IDVs
</li><li>These forms will be available for the below personnel by default and they can be distributed further
* DHS Agency System Administrators
* DoD Department Administrators
</li><li>These forms can be accessed via Business Services, GUI services or the Web Portal
</li><li>The fields available on the forms and their behavior for DHS and DoD are listed in the Excel Spreadsheet below
[http://www.fpdsng.com/downloads/Version1.4_OT_Fields_RequirementStates.xls Other Transaction Fields Requirement]
</li><li>Transaction number field will not be available for this type of document
</li><li>Contracting Office and Contracting Agency on this type of documents can only belong to DHS or DoD
</li>
*<b>New “Reason for Modification” value ‘Termination for Cause’ will be added to all document types </b>
*<b>Existing “Reason for Modification” value ‘Terminate for Default (complete or partial)’ will not be available for Other Transactions </b>
</li><li>The only “Extent Competed” values that will be available for this type of documents are ‘Competed’  and ‘Not Competed’
</li><li>The only “Solicitation Procedures” values that will be available for this type of documents are ‘Broad Agency Announcement (BAA)’, ‘Program Solicitation’ and ‘Only One Source’
</li><li>The drop-down for data element “Nontraditional Government Contractor Participation” will display the values ‘Nontraditional Significant Participation’, ‘Cost Sharing’ and ‘Determination of Exceptional Circumstances’
</li><li>The ‘Other Transaction Agreement’, ‘Other Transaction Order’ and ‘Other Transaction IDV’ will be available via the following applications:
*ezSearch
*ICD
*BI Views
*Adhoc reports
*Advanced Search
</li><li>The ‘Other Transaction Agreement’, ‘Other Transaction Order’ and ‘Other Transaction IDV’ will not be available in the Standard reports.
</li><li>Version 1.4 XML extracts, archives and specifications will contain ‘Other Transaction’ data.
</li><li>A new Sys Admin Standard report similar to ‘Federal Contract Actions and Dollars’ will be available to display only ‘Other Transaction’ documents.
</li><li>No CBT additions will be done for these documents. DHS and DoD will have User Manuals available for the respective users.
</li></ul>
<TABLE id="box-table-a" border=2 style="width:750px">
<tr><th colspan=2 align="center"><b>Impact Analysis for Users and Integrators</b></th></tr>
<tr><td style="width:200px">GUI Interface</td><td valign="left">New forms will be available for DHS and DoD</td></tr>
<tr><td nowrap>Business Services</td><td valign="left">New forms will be available for DHS and DoD</td></tr>
<tr><td nowrap>Reports and Report Services</td><td valign="left">New Sys admin Report will be available</td></tr>
<tr><td nowrap>Data Dissemination</td><td valign="left">Version 1.4 XML archives will contain ‘Other Transactions’</td></tr>
</TABLE>

===Unify DoD and Civilian===
<ul><li>
Use Cases:  The Unification Requirement document shows each data element as it is currently and also how each will be when the unification project is implemented.
</li>
*Use cases changes are listed in the [http://www.fpdsng.com/downloads/FPDSNG_DataDictionary_V1.4.pdf Data Dictionary]

<li>Validation Rules: The Validation Rules document lists the new rules and changes to the existing rules 
</li>
[http://www.fpdsng.com/downloads/Unification_validation_rules.xls Unification Validation Rules]
</ul>
<TABLE id="box-table-a" border=2 style="width:750px">
<tr><th colspan=2 align="center"><b>Impact Analysis for Users and Integrators</b></th></tr>
<tr><td style="width:200px">GUI Interface</td><td valign="left">New use cases and validation rules apply
</td></tr>
<tr><td nowrap>Business Services</td><td valign="left">New use cases and validation rules apply
</td></tr>
<tr><td nowrap>Reports and Report Services</td><td valign="left">No Impact</td></tr>
<tr><td nowrap>Data Dissemination</td><td valign="left">No Impact</td></tr>
</TABLE>

==New Validation Rules/Validation Rules Impacted==
<TABLE id="box-table-a" border=2 style="width: 750px">
<th width=20% align="center"><b>Module</b></th><th width=80% align="center"><b>Description of changes</b></th>
<tr>
<td style="width:200px" align="center">Treasury Account Symbol</td>
<td valign="top">Error message 6M01 will no longer fire through Version 1.3  GUI Services and the rule will not fire for all Version 1.4 services.

<b>6M01:</b>Treasury Account Symbol should be of format TAS::XX XXXX::TAS or TAS::XX XXXX XXX::TAS and should not contain special characters.
</td>
</tr>
<tr>
<td style="width:200px" align="center">Treasury Account Symbol</td>
<td valign="top">Warning message 6M01WARN will no longer fire through Business services

<b>6M01WARN:</b>Treasury Account Symbol should be of format TAS::XX XXXX::TAS or TAS::XX XXXX XXX::TAS and should not contain special characters.
</td>
</tr>
<tr>
<td style="width:200px" align="center">Treasury Account Symbol</td>
<td valign="top">The following new validation messages will fire for Version 1.4 documents and for Version 1.3 documents when accessed from the Web Portal/GUI service

<b>6M02 (Civilian Only):</b>"Agency Identifier" and "Main Account Code" are required when "Action Obligation" is either greater than zero or less than zero.

<b>6M04:</b> "Agency Identifier", "Main Account Code" and "Sub Account Code" must only have alpha numeric values

<b>6M05:</b> "Agency Identifier" must be two characters in length.

<b>6M06:</b> "Main Account Code" must be four characters in length.

<b>6M07:</b> "Sub Account Code" must be three characters in length.
</td>
</tr>
<tr>
<td style="width:200px" align="center">Treasury Account Symbol</td>
<td valign="top">The following new validation messages will fire for Version 1.0, Version 1.1, Version 1.2 documents and for Version 1.3 documents when accessed from the Business Services

<b>6M02A (Civilian Only):</b> "Treasury Account Symbol" is mandatory. Please provide a value for the "Treasury Account Symbol" in the "Description of Requirements"

<b>6M04A:</b> "Treasury Account Symbol" can not contain special characters.
</td>
</tr>
<tr>
<td style="width:200px" align="center">BPA, BOA, BPA Call for DoD</td>
<td align="center">[http://www.fpdsng.com/downloads/Unification_validation_rules.xls Unification Validation Rules]</td>
</tr>
<tr>
<td style="width:200px" align="center">Other Transactions (for DHS and DoD agencies only)</td>
<td align="center">[http://www.fpdsng.com/downloads/FPDS-NG-FDD-V1.4-Other-Transactions.doc Other Transactions Validation Rules]</td>
</tr>
<tr>
<td style="width:200px" align="center">Unify Civilian and DoD</td>
<td align="center">[http://www.fpdsng.com/downloads/Unification_validation_rules.xls Unification Validation Rules]</td>
</tr>
</table>
Return to Detail Release Notes V1.4.
Retrieved from "https://fpds.gov/wiki/index.php/Detail_Release_Notes_V1.4"