Release Notes V1.4
From FPDS-NG
Contents
Schedule
| Description | Start Date | End Date |
|---|---|---|
| Phase I Alpha | November 23, 2009 | December 3, 2009 |
| Phase I Functional Qualification Testing | December 14, 2009 | December 23, 2009 |
| Phase II Alpha | January 11, 2010 | January 22, 2010 |
| Phase II Functional Qualification Testing | February 8, 2010 | February 26, 2010 |
| Installation in Production | March 12, 2010 | March 12, 2010 |
Documentation Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | Yes |
| Web Services | Yes |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | Yes |
| Use Case Summary | Yes |
| Validation Rules | Yes |
| Online Help | Yes |
| Computer-Based Training | Yes |
| Report Manual | Yes |
Description Of Changes
Treasury Account Symbol
Version 1.4 will contain a new data element – the Treasury Account Symbol. Recovery Treasury Account Symbols entered in the correct format in the Description of Requirement field will be pasted into this new TAS field. Version 1.3 documents will also have the TAS field. This field is required to be filled out by all civilian agencies on any actions where the action obligation is other then $0. The field is optional for DoD. Version 1.3 business services only users who do not have the TAS field programmed will need to enter the TAS in the description of requirement field using one of the following formats:
TAS::XX XXXX::TAS or TAS::XX XXXX XXX::TAS (if your agency is using the optional sub account code).
Users on Version 1.4 or Version 1.3 GUI Services will enter the TAS in the new data element which will be formatted to contain the two character agency code (XX), the four character account code (XXXX), and the optional three character sub account code (XXX).
An error message will be received for civilian version 1.3 business services only users if the TAS format above is not provided in the description of requirement field.
All other users will receive an error message when the field itself is not filled out.
Actions that are $0 do not require a TAS but users may enter one if they wish.
Until February, 2010, FPDS users should only input Recovery TAS codes in the description of requirement field.
After the February 2010 date, FPDS will validate which TAS codes represent Recovery funded actions and automatically mark these actions as Recovery. This indicator will be supplied in the “Initiative” field which will be available in ad hoc.
PLEASE NOTE- If you are not a business services only user on version 1.3 you SHOULD NO LONGER be entering the TAS in the description of requirement field once the software is implemented!!! The TAS data element will be available on 1.3 documents. Only those business services only systems on version 1.3 should enter the TAS in the description of requirement field and only those systems will have this information pasted into the new data element.
Data Element Use Case Changes
The following data elements will now be Required. Some of these data elements are currently Required but only generate warning messages for those contract writing systems using business services only. These warning messages will now be replaced by error messages, meaning you will be unable to submit your action without providing the expected information. Additionally, some of these data element changes will be required on both Versions 1.3 and 1.4.Please make sure your system is prepared for the changes on these data elements.
The following table shows data elements that will be changed for all or multiple versions:
| Element Name | Required on versions |
|---|---|
| Type of Contract | 1.3 and 1.4 All record types except modifications |
| Multiple or Single Award IDV | 1.3 and 1.4 FSS, GWAC, IDC, BOA, Part 8 BPA, Part 13 BPA except modifications |
| Description of Requirement | All versions & All record types |
| Contract Bundling | All versions & All record types except modifications |
| Place of Manufacture | All versions for DoD.All DO, PO, Part 8 BPA Call, Part 13 BPA Call,DCA
And 1.4 for civilians All DO,PO,Part 8 BPA Call, Part 13 BPA Call, DCA |
| Commercial Item Test Program | Version 1.2,1.3 and 1.4 All PO, DCA, FSS, GWAC, BOA, IDC, Part 13 BPA |
| Last Date to Order | All versions FSS, GWAC, IDC, BOA, Part 8 BPA, Part 13 BPA |
| Subcontracting Plan | Civilian and DoD: All versions for Award Types PO, DCA.
Civilian – All version IDVs except Part 8 BPA DoD - BOA, BPA Part 13 for Version 1.4 and IDC for all Versions. |
| Sea Transportation | All versions - but validation rule will only require DoD to complete |
| Funding Agency | 1.4 - Civilian and DoD FSS, GWAC, BOA, Part 8 BPA, Part 13 BPA, IDC
All versions - Civilian and DoD All DO, all PO, DCA, Part 8 BPA Call, Part 13 BPA Call, Mod |
| Funding Office | 1.4 - Civilian and DoD FSS, GWAC, BOA, Part 8 BPA, Part 13 BPA, IDC
All versions - Civilian and DoD All DO, all PO, DCA, Part 8 BPA Call, Part 13 BPA Call, Mod |
NOTE: Data element changes for Version 1.4 will be added to this release notes in the future
FAR part 8 and FAR part 13 BPAs and their calls
Distinction between FAR part 8 and FAR part 13 BPAs and their calls. Distinction between Orders against a BOA. DoD will adopt the use of BPAs, BPA calls, and BOAs.
Beginning with Version 1.4 FPDS will distinguish between FAR Part 8 BPAs and FAR Part 13 BPAs. A FAR part 8 BPA will reference a FSS and FAR part 13 BPA will not. Competition information will vary accordingly.
Note: The Referenced IDV ID will no longer be available for edit on a BPA after the document has been saved; this change applies to all versions.
Unification of DoD and Civilian agencies use cases
DoD and Civilian agencies will adopt similar use cases with a number of validation rule changes. Many DoD validation rules will become common rules for all users. There will still be specific DoD validation rules to distinguish between what is a DoD specific data element and what is not.
A spreadsheet showing the changes to data elements in version 1.4 will be linked to this release notes in the near future.
DHS and DoD Other Transactions
DHS and DoD will report Other Transactions (defined as R and D Prototypes under the NDAA of 2008). Only DoD and DHS will report these transactions. Information will be provided separately.
PLEASE NOTE: Changes\additions to Version 1.4 may occur.Please make sure to review the Release Notes frequently on www.fpds.gov
| OPTIONAL FIELDS DO NOT MEAN YOU CAN IGNORE THE FIELD- YOU MUST FILL IT OUT IF IT IS APPLICABLE. APPLICABILITY DEPENDS ON ANSWERS PROVIDED ELSEWHERE AND/OR VALIDATION RULES. DO NOT HARD CODE OPTIONAL FIELDS!!!! |