Difference between revisions of "V1.5 SP 18 August Fast Path"

From FPDS-NG
Line 153: Line 153:
 
   <th align="center"><b>Rule Code</b></th><th align="center"><b>Message</b></th>
 
   <th align="center"><b>Rule Code</b></th><th align="center"><b>Message</b></th>
 
   <tr>
 
   <tr>
−
   <td align="center">10M14</td><td>If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the ‘Extent Competed’ must be ‘Not Available for Competition’.</td>
+
   <td align="center">10M14</td><td>If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the "Extent Competed" must be ‘Not Available for Competition’.</td>
 
   </tr>
 
   </tr>
 
   <tr>
 
   <tr>
−
   <td align="center">10M15</td><td>If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the "Contracting Office Agency ID" must be 9700 (DOD).</td>
+
   <td align="center">10M15</td><td> If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the Contract Awarding Department must be DOD (9700).</td>
 
     </tr>
 
     </tr>
 
   <tr>
 
   <tr>
−
   <td align="center">10M16</td><td>If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the ‘Date Signed’ must be on or after 10/1/2022.</td>
+
   <td align="center">10M16</td><td> If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the "Date Signed" must be on or after 10/1/2022.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>

Revision as of 16:36, 2 August 2023

Schedule

DescriptionStart Date End Date
Beta Deployment08/07/202308/07/2023
Government Acceptance Testing 08/14/202308/18/2023
Production Deployment 08/26/202308/26/2023

Document Changes

DocumentationChanges Required
XML SpecificationsYes
Web ServicesYes
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryYes
Validation RulesYes
ezSearchYes
Atom FeedsYes
Online HelpYes
User ManualYes

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators

IAEMOD-15731/IAEPOL-9

Per FAR Case 2017-09, in support of the updates to the policy changes on the Joint Ventures program FPDS will add two new Entity Socio Economic Indicators.

The two new Entity Socio Economic Indicators are:

  1. Small Business Joint Venture
  2. Service-Disabled Veteran-Owned Business Joint Venture.
 FAR Case 2017-019:

Policy on Joint Ventures.

FPDS will accept and store the following two new Entity Socio-Economic Indicators and display their values in the “Certifications” section of the FPDS Contracts screen. These indicators will apply to Awards and Indefinite Delivery Vehicles, but not to Other Transaction Awards/IDVs. These new Entity Socio-Economic Indicators will be stored in existing generic booleans as follows:

  1. Small Business Joint Venture (stored in genericBoolean01)
  2. Service-Disabled Veteran-Owned Business Joint Venture (stored in genericBoolean02)

Three existing Entity Socio-Economic Indicators will be renamed as follows:

  1. From: Joint Venture Women-Owned Small Business
    To: Women-Owned Small Business (WOSB) Joint Venture eligible under the WOSB Program
  2. From: Joint Venture Economically Disadvantaged Women-Owned Small Business
    To: Economically Disadvantaged Women-Owned Small Business (EDWOSB) Joint Venture
  3. From: Other than one of the preceding
    To: Individual or concern other than one of the preceding

In FAADC, the three new Entity Socio-Economic Indicators will be renamed as follows:

  1. From: Joint Venture Women-Owned Small Business
    To: Women-Owned Small Business (WOSB) Joint Venture eligible under the WOSB Program
  2. From: Joint Venture Economically Disadvantaged Women Owned Small Business
    To: Economically Disadvantaged Women-Owned Small
    Business (EDWOSB) Joint Venture
  3. From: Other than one of the preceding
    To: Individual or concern, other than one of the preceding

In FAADC, the two new Entity Socio-Economic Indicators will be stored in generic strings as follows:

  1. Small Business Joint Venture will be stored in genericString05
  2. Service-Disabled Veteran-Owned Business Joint Venture will be stored in genericString02

Existing validations will be updated to reflect these new values.

Yes

IAEMOD-15732/IAEPOL-10

Per FAR Case 2020-013, in support of the Small Business Administration’s Women-Owned Small Business (WOSB) program, FPDS will add (2) new Entity Flags:
  1. SBA-Certified Women-Owned Small Business
  2. SBA-Certified Economically Disadvantaged Women-Owned Small Business
 FAR Case 2020-013:

Certification of Women-Owned Small Businesses.

FPDS will accept and store the following two new Entity Socio-Economic Indicators and display their values in the “Certifications” section of the FPDS Contracts screen. These indicators will apply to Awards and Indefinite Delivery Vehicles, but not to Other Transaction Awards/IDVs. These new Entity Socio-Economic Indicators will be stored in existing generic booleans as follows:

  1. SBA-Certified Women-Owned Small Business (stored in genericBoolean03)
  2. SBA-Certified Economically Disadvantaged Women-Owned Small Business (stored in genericBoolean04)

Two existing Entity Socio-Economic Indicators will be renamed as follows:

  1. From: Joint Venture Women-Owned Small Business To: Women-Owned Small Business (WOSB) Joint Venture eligible under the WOSB Program/li>
  2. From: Joint Venture Economically Disadvantaged Women-Owned Small Business To: Economically Disadvantaged Women-Owned Small Business (EDWOSB) Joint Venture

In FAADC, the two new Entity Socio-Economic Indicators will be stored in generic strings as follows:

  1. SBA-Certified Women-Owned Small Business will be stored in genericString03
  2. SBA-Certified Economically Disadvantaged Women-Owned Small Business will be stored in genericString04

Existing validations will be updated to reflect these new values.

Yes

IAEMOD-15734 /IAEPOL-28

The 2019 NDAA requires that DoD deploy a pilot program that allows the Department to count Employers of Persons with Disabilities toward small disadvantaged business goals at both the contract and subcontract levels.



FPDS will need to be able to collect the new value selection called DFARS 226.72 Demo Project


Collect data for DoD Pilot Program per NDAA for Eligible Employers of Persons with Disabilities.


This is a change request to add the new value "DFARS 226.72 Demo Project" (Code: DDP) to the existing Data Element 10M ‘Solicitation Procedures’.

This new value will establish two new ‘Validation Rules’ with a start date of 10/01/2022.

Rule CodeMessage
10M14If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the "Extent Competed" must be ‘Not Available for Competition’.
10M15 If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the Contract Awarding Department must be DOD (9700).
10M16 If Solicitation Procedures is ‘DFARS 226.72 Demo Project’, then the "Date Signed" must be on or after 10/1/2022.


Additionally, existing validation rules below will be updated for rule codes :

  • DOD10U01 – If Local Area Set Aside is yes, then Solicitation Procedures cannot be 'Only One Source' or ‘DFARS 226.72 Demo Project’.
  • DOD10M03A – If "Solicitation Procedures" is 'Only One Source' or ‘DFARS 226.72 Demo Project’ and "Type of Set Aside" is '8(a) Sole Source', 'HUBZone Sole Source' or 'SDVOSB Sole Source', 'Veteran Sole Source', 'Women Owned Small Business Sole Source', or 'Economically Disadvantaged Women Owned Small Business Sole Source' then "Other than Full and Open Competition" must be 'Authorized by Statute'.
  • DOD10C01 – If Solicitation Procedure is ‘Only One Source’ or ‘DFARS 226.72 Demo Project’ then Other Than Full and Open Competition cannot be blank.
  • DOD10C04A – If “Other than Full and Open Competition” is ‘Authorized by Statute’ or ‘Authorized Resale’, then “Solicitation Procedures” must be ‘Only One Source’, or ‘DFARS 226.72 Demo Project’, or ‘Simplified Acquisition’.
 Yes

IAEMOD-16014

Defect: Product Service Codes that start with a number and also contain an alpha character are not recognized as a product, causing incorrect behavior of Validation Rule 6T07.

This defect is allowing users to approve contracts with both a PSC for a product (such as 7A20) and an IGF value.

IGF rule incorrectly does not fire when PSC is for a product code but contains an alpha character.


This is a defect fix to correct the logic of Validation Rule 6T07 (below) so it will fire properly on a contract when Product/Service Code starts with a number but also contains an alpha character and IGF has a value. This rule was added in SP17 so it has an effective date of 4/29/2023.

  • Rule 6T07: When PSC is a Product or PSC = R497, then “Inherently Governmental Functions” value must be blank.
 Yes
Retrieved from "https://beta.fpds.gov/wiki/index.php?title=V1.5_SP_18_August_Fast_Path&oldid=5026"