Navy PDS White Paper Addendum

The chart below lists and categorizes the validations within PDS, PD2 Integrity Tool and MOCAS Contract Pay Auto-Population while describing any differences. 1

COMMON RECURRING PILOT ERRORS

VALIDATION PDS INTEGRITY CPAP1. Discount Terms / Net Days

Do not free-form type in Discount Terms block• e.g. Do NOT type “NET 30 DAYS” Place cursor in Discount Terms block and press <Shift> and double-click. (The Discount Terms dialog box opens.)• Enter “30” in the “Net” field. • Click <OK>.

2. Not Separately Priced (NSP)4 key points to setting up an NSP line item in PD2:• The CLIN Type should be “Priced”• The Cost Constraint should be “NSP”• The Quantity and Unit of Issue should be entered• The Delivery information should be enteredThere should be no funding obligation associated with NSP line items, and no invoices or payments are directly associated with them either.

Integrity & CPAP: Although there are not specific validations for NSP, Unit of Issue and Delivery checks are performed on NSP lines and funding and LOA checks are circumvented when NSP is present.

3. Quantity and Unit of IssueOn priced line items, if you enter a quantity, you must enter a Unit of Issue and vice versa. Zero is not a valid entry for quantity on an award line item. NOTE: If the line item is cost type, an associated unit price is not required.

Integrity: Priced CLIN or subCLIN must have a unit of issue Integrity: A priced CLIN with a unit of issue must have a quantity specified. Bypass this check for agreements and external agreements. Integrity: A priced CLIN with a quantity must have a unit of issue specified. CPAP: If the Line Item is “Priced” (i.e., CLIN Type of the line item is equal to ‘1’), the Contract Type does not start with ‘C’ (i.e., not a “cost”, “cost plus fixed fee”, “cost plus award fee”, “cost plus incentive fee” or “cost sharing”) and the Unit Cost element doesn’t exist or is empty, the validation will fail

CPAP: If the line item doesn’t represent a cost plus contract (Contract Type does not start with ‘C’) and the Line Item Quantity element is

1 The PDS rules are referenced from PDS V2.3 Business Rules (.pdf) and PDS V2.3 Enumeration Annotation (.pdf) available from DPAP’s website (http://www.acq.osd.mil/dpap/pdi/eb/procurement_data_standard.html); the referenced Navy Integrity Edits are from June 2012 (Enterprise_Edits_20100602.xml with Release Notes 7.0.3.0 added); the BPEL Validations are referenced from Oracle BPEL Validation List, however, have been updated to reflect the most current version of the tool in test as of 30-03-2011.

2012-06-10 1 | P a g e

Navy PDS White Paper Addendum

COMMON RECURRING PILOT ERRORS

VALIDATION PDS INTEGRITY CPAPmissing, the validation will failCPAP: If the line item doesn’t represent a cost plus contract (Contract Type does not start with ‘C’) and the Line Item Quantity value contains a decimal point or is not a valid number, the validation will fail

CPAP: If the Delivery type is “Product” and the Line Item Quantity does not equal the Delivery Quantity, the validation will fail

4. Cost Constraint – ESTThe “Estimated” cost constraint, should not be used on Firm Fixed Price line items.

5. Negative Unit Prices

Sometimes a vendor quote will list a bottom line discount because of the amount purchased. There is no way to establish delivery of a negative line item and payment offices have no way to process such line items, therefore the PDS edits do not allow them. Do not create line items with negative unit prices. Instead, try and work with the vendors to incorporate the discounts into the unit prices at the line item and annotate the discount in the description so as to avoid creating negative unit price line items.

6. Custom Units of IssuePD2 comes with over 700 Units of Issue. Custom Units Of Issue fail the PDS. To a user, it would be hard to tell which units of issue are standard and which were manually added. System Administrators can help check by running a query on the unit_of_issue_ref. Custom Units of Issue begin with id’s of approximately 15000 and greater in the unit_of_issue_ref table. Recommend Deleting Custom Units of Issue in System Administration so they don’t get used on future contracts.

Aside from ensuring a unit of issue exists, CPAP does not check the validity of the unit of issue

7. Ship To DoDAACs and DeliveryIn PD2, there are some important points to remember when adhering to the separate delivery schedule rule in DFARS 204.7103 which applies to priced line items:• A Delivery Date must have a Ship To DoDAAC. • Ship To DoDAACs must be valid in www.daas.dla.mil/daasinq/• Organizations must have an Address • Delivery Dates, ADC Dates or Periods of Performance are required on priced line items.

Integrity: All priced CLINs or subCLINs that have not been cancelled or terminated, must have a CLIN delivery date or a performance delivery date. CLINs that have a cost constraint of NSP are excluded from this check.

Integrity: All priced CLIN/subCLINs must have a period of performance start date or a delivery date

2012-06-10 2 | P a g e

Navy PDS White Paper Addendum

COMMON RECURRING PILOT ERRORS

VALIDATION PDS INTEGRITY CPAPIntegrity: All priced CLIN/subCLINs must have a period of performance end date or a delivery date

Integrity: All priced CLIN/subCLINs must have a required delivery date or a period of performance

Integrity: Priced CLIN is missing a period of performance or a delivery date

Integrity: Ship To CAGE Code must be five characters long.

Integrity: Ship To DODAAC must be six characters long.

Integrity: Cage Code and Ship To DODAAC cannot be blank.

Integrity: Cage Code or Ship To DODAAC must be 5 or six characters.

CPAP: If the Line Item is “Priced” (i.e., CLIN Type of the line item is equal to ‘1’) and the count of Line Item Delivery elements is zero, the validation will fail

CPAP: If CheckDelivery passed and the Delivery type is “Service” and both the Delivery Start Date and Delivery Stop Date are present and not empty, validation skips to the CheckLineItemQuantity section. Otherwise, the validation will fail

CPAP: If CheckDelivery passed and the Delivery type is “Product” and there is a non-empty Requested Delivery Date or a non-empty Delivery Period Type, Delivery Period and Delivery Interval, the validation continues with 17.3 - CheckDeliveryShipToAddressDODAAC., otherwise, the validation will fail.

CPAP: If CheckDeliveryDateorLeadTime passed and the Delivery type is “Product” and the Ship-to DoDAAC is six characters long a query is run against the DAASC DoDAAC table to check for its existence and if it exists in that table,skip to CheckDeliveryQuantity, otherwise if the Ship-to DoDAAC is five characters long skip to CheckDeliveryShipToAddressCCR, otherwise the validation will fail

CPAP: If the Ship-to DoDAAC is five characters long, the validation skips to the CheckDeliveryQuantity validation (17.6) until we have access the CCR web service for checking a valid CAGE code.

CPAP: If the line item doesn’t represent a cost plus contract (Contract Type does not start with ‘C’ or isn’t ‘FPI’) and the Delivery Quantity element is missing, the validation will fail

CPAP: If the line item doesn’t represent a cost plus contract (Contract Type does not start with ‘C’ or isn’t ‘FPI’) and the Delivery Quantity value contains a decimal point or is not a valid number, the validation will fail

8. Contact MethodPD2 enforces that a contact name be entered, but not a method when you set up an organization address. However, PDS requires at least one contact method be provided with a contact name. A contact method

2012-06-10 3 | P a g e

Navy PDS White Paper Addendum

COMMON RECURRING PILOT ERRORS

VALIDATION PDS INTEGRITY CPAPwould be telephone number or an email address or fax number, so that there is a way to contact the person or office.

Now if you have a large database that currently is missing contact methods, it would be really time consuming to try and update all of them, particularly if you do not have the phone number available to you. If you could institute a local practice to add a Contact Method as the Organizations are used and be sure to mandate phone numbers are included on all new entries in organization maintenance, it would make contracts that use these addresses PDS compliant.

9. Document Classification Pricing Structure: On BPAs or Agreements that do not yet have line

items, a pricing structure must be selected to indicate the structure of future calls and orders.

Order Quantity and Order Amount: On an IDIQ, indicate a minimum and maximum quantity or amount allowed for each order.

Additionally, zero is not a valid value for quantity in the mimium or maximum field.

Ordering Period: On an IDIQ, indicate the Start and End Date for when orders can be placed under the contract vehicle. Do not enter data in these fields for delivery orders or purchase orders.

10. Vendor InformationVendor information is pulled from CCR via the CCR Punch-out capability. However, some information is not obtained from CCR such as vendor Employer Identification Number. PD2 does not need this information. Some older PD2 databases have populated the Taxpayer Identification Number in the Vendor Maintenance portion of PD2. Taxpayer Identification Numbers are issued by the IRS and have nine digits (social security numbers are one type). PDS will respond with an error if the data entered in that field is not nine digits. The PDS extract utility will remove any dashes that may have been placed in the data, but the results must be nine digits. The PDS error that will result is: “PDS_F_F_25: The value '’abcdefghijkl' is not a valid entry for <EmployerIdentificationNumber>. It must be 9 numeric digits (0-9).”

Aside from checking the Vendor Cage Code, CPAP does not check for the additional Vendor information such as TIN or EIN.

11. Unfunded Line ItemsWhen a line item is not funded, there should not be anything on the funding tab.

CPAP: If the Line Item has a Funding element and a Fund Amount greater than zero then Line Item level funding validations (i.e., CheckFundingStrip, CheckCMET, CheckACRN, CheckFunding) will be

2012-06-10 4 | P a g e

Navy PDS White Paper Addendum

COMMON RECURRING PILOT ERRORS

VALIDATION PDS INTEGRITY CPAPperformed.CPAP: If a Sub Line Item that is a child of the Line Item that failed the CheckFunding section has an Option CLIN value that is not “1” and has either no Cost Constraint or a Cost Constraint which is not ‘NSP’ or ‘NC’, has a Funding element and a Fund Amount greater than 0 then Sub-CLIN level Funding validations (i.e., CheckFundingStrip, CheckCMET, CheckACRN, CheckFunding) will be performed or the validation will fail

12. Line Items - Line Items must have a description.

Integrity: There must be a CLIN description Integrity: CLIN Description must be meaningful. The CLIN description must not contain “see atta” “see hard” or “refer to”

Integrity: CLIN Description must not contain carriage returns 12.1. Parent CLINs for deliverable subCLINs - When a CLIN is

used with priced and funded separately identifiable subCLINs, the parent CLIN should not have funds obligated against it, including zero dollars.

Integrity: Funding cannot be at both CLIN and subCLIN levels 12.2. Non-severable Priced CLINs with Informational SLINs -

When a non-severable deliverable priced CLIN is funded with multiple informational SLINs, there should not be any funding data placed on the priced CLIN. As an example, do not leave a zero obligated amount with a CIN and LOA on the priced line item if it is funded by multiple SLINs

Integrity: Funding cannot be at both CLIN and subCLIN levels 12.3. Informational Line Items and Global Change - If there

are informational lines on a contract and the global change feature is used to change the Ship To Address on priced line items, it will place the shipping information unintentionally on the informational line items as well causing the contract to fail PDS validations. Take care when using this feature on mixed line item contracts.

13. Clauses – Rule: One or more clauses are required at the contract level unless one or both of the following is true:

• The represented contract is a purchase order or• An ordering instrument number is provided.

2012-06-10 5 | P a g e

Navy PDS White Paper Addendum

COMMON RECURRING PILOT ERRORS

VALIDATION PDS INTEGRITY CPAPIntegrity: Basic D awards and MODs, must contain 3 specific clauses Integrity: Local Clauses must exist in Full Text, rather than By Reference Integrity: Fill-in Clause must have fill-in text. Integrity: If variations in quantity are specified in the award, FAR 52.211-16 or FAR 52.211-18 must be included with the award

14. Pricing

14.1. FFP - On a Firm Fixed Price line item, there must be a firm price as data. A firm price is calculated by multiplying the quantity by the unit price.

14.2. CPFF - If a line item is set up for Cost Plus Fixed Fee

(CPFF), a fixed fee should be included. Do not set up a different line item for the Fixed Fee portion.

Integrity: A Priced CLIN that is CPFF must have estimated cost and/or a fixed fee unless the line item UCA indicator is on, or "NSP" is designated is on

Integrity: An informational CLIN that is CPFF cannot contain an estimated cost or fixed fee

14.3. COST - If a cost type line item is set up, there must be an Estimated Cost. Integrity: A priced CLIN that is COST or CS must have an estimated cost unless the line item UCA indicator is on, or "NSP" is designated

15. Remit To Address - If a Remit To Address is used on a contract, the organization must have a DUNS number. Integrity: A US vendor must have a DUNS number Integrity: If there is a DUNS plus 4 for a vendor it must contain 4 numeric characters only Integrity: A Foreign vendor may have a DUNS number Integrity: A Foreign vendor contains an invalid DUNS Code

16. CLIN Number Format - CLINs must consist of four numeric digits 0001 through 9999. CPAP ignores CLINs that do not have line numbers. Integrity does not have CLIN numbering checks.

2012-06-10 6 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAP1. Public Standards Compliance - Certain public standards need to be

followed as part of the PDS business rules. These include enumeration lists for currency, country, etc. as published by a different authoritative source. Always provide names or descriptions of the entity and not the code unless directly specified.

If currency is not "$", an exchange rate must exist. (Purple) If currency is not "$", the currency chosen must not have been deleted by the system administrator. (Purple) If currency is not "$", the currency chosen the conversion should be the most current. (Purple) You must choose a currency for a foreign vendor. (Navy)

We do not check the ISO tables as part of any of our validations. My assumption is that the PDS validations use the ISO tables as a lookup. We use different symbols and descriptions for currency. This could pose a problem with compliance.

<UnitOfIssue Desc="Dollars, U.S.">DO</UnitOfIssue> as per ISO = US Dollar USD

Referencing the most recent PDS reports, we are seeing the following errors:<BuyingCurrency> cannot denote US Dollars (populated with "U.S. DOLLARS"). <PaymentCurrency> cannot denote US Dollars (populated with "U.S. DOLLARS").

However, changes to the extract utility that are not yet scheduled will correct this problem from PD2 as per guidance from BTA (Darryn Miller).2. Date, Time and Percentage Formats –

For currencies, dates, times, and percentages, follow the following formats:a. Currency: Provide the textual name of the currency from ISO 4217 from the International Organization for Standardization (ISO).b. Date: All dates must be specified as ‘CCYY-MM-DD’ format unless otherwise specified in the annotation in the schema. ‘CCYY’ is the 4 digit year (including century), ‘MM’ is the 2 digit calendar month, and ‘DD’ is the 2 digit Day of the month. Example: 1988-05-22 indicates the 22nd day of May 1988.c. Time: Indicate “Time” using a 24 hour clock in ‘HH:MI:SS’ format. ‘HH’ is the hour, ‘MI’ is the minute and ‘SS’ is the seconds. Example: 21-59-03 indicates 57 seconds before 10 PM.d. Percentage: For all percentages, include the decimal point. For example, express ‘4.25%’ as ‘4.25’.

SEE ABOVE RE: CURRENCY, OTHERWISE, NONE

3. Contractor and Issuing Office Addresses - An address for the contractor and

2012-06-10 7 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAPfor the issuing office are required on every procurement instrument.

A Vendor must have an address (Navy) An award or mod must have a vendor (Purple) A vendor address must be "current" (Purple) A vendor must be "approved" (Purple) A US vendor must have a CAGE code (Purple) The CAGE code must be 5 positions (Purple) Issuing office must be "Current" (Purple) Issuing office must be "approved" (Purple) An award or mod must have an issuing office (Purple) There must be a vendor city (Navy) US vendor must have state information (Navy) Foreign vendor must not have state information (Navy) Vendor must have country information (Navy) A US vendor must have a zip code (Navy) A U.S. vendor must have a Zip Code of at least 5 numeric characters. (Navy) A U.S. vendor must have a valid Zip Code of 5 numeric characters. (Navy) A U.S. vendor must have a Zip Code of NNNNN-NNNN numeric characters. (Navy) A U.S. vendor must have a valid NNNNN-NNNN zip code in the right format. (Navy) A Vendor must have a corporate status other than "Not a Corporate Entity" (Navy) A U.S. vendor must have a vendor category (Navy) A US vendor must have a DUNS number (Navy) If there is a DUNS plus 4 for a vendor it must contain 4 numeric characters only (Navy) A Foreign vendor may have a DUNS number (Navy) A Foreign vendor contains an invalid DUNS Code (Navy)

4. Contract Administrative Office and Issuing Office Addresses - A DoDAAC is required for the contract administration and issuing office addresses.

An award or mod must have an issuing office DODAAC (Purple) If Admin office exists, it must have an identifier (CAGE, DODAAC or DUNS) other than null or spaces. (Purple) The Issuing Office DODAAC must be 6 positions (Purple)

2012-06-10 8 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAPAdmin DODAAC must be 6 digits in length (Navy) If Admin office exists, it must be "current" (Purple) If Admin office exists, it must be "approved" (Purple) Issuing Office DODAAC must exist in the database of DoDAACs maintained by DAASC

Admin Office DODAAC must exist in the database of DoDAACs maintained by DAASC

We cover this in integrity and CPAP with validations against the authoritative DoDAAC reference. However, the fields are not locked down in SPS and thus errors can occur.

Navy errors in this category in Pilot:N00406: The value 'IAWDOS' is not a valid entry for <DoDAAC>. It must be 6 alphanumeric characters (0-9, A-Z except 'I' and 'O'). All letters must be uppercase.N40345: The value '.' is not a valid entry for <DoDAAC>. It must be 6 alphanumeric characters (0-9, A-Z except 'I' and 'O'). All letters must be uppercase.

5. Remit To Address – A nine or thirteen digit DUNS number is required for a remittance address. Both may be provided.

6. Order Number – If an order number is longer than 4 characters it must be provided as a Procurement Instrument Number. In order for Integrity to perform validations, the PIIN-SPIIN must meet FAR formatting specifications Type F award without corresponding parent contract detected...please update award. If PIIN position 9 = ‘F’, there must be a parent contract. Verify, correct, and then retry.

7. Ordering Instruments - If the represented contract is a call order, task

order, or delivery order, then at least one of the following ordering instruments must be provided except when the order number is denoted by four characters:

• Agreements including Basic and Loan• Bailment• Basic Ordering Agreement• Blanket Purchase Agreement Under Federal Supply Schedule• Blanket Purchase Agreement• Facilities Contract• Indefinite Delivery Definite Quantity• Indefinite Delivery Indefinite Quantity• Requirements• Schedule

2012-06-10 9 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAP

8. Modification Identifiers - Rule: A referenced procurement instrument number shall not include a modification identifier when the description contains one of the following:• Contract being Modified – Award• Ordering Instrument• Prior Contract to a Continuation Contract• Prior Contract to a Follow-on Contract• Small Business Administration Contract• Solicitation Number

9. Contract Performance Dates - Rule: If a period of performance, an ordering period, a lease, or a funding period is not expressed as a start and end data; then either a delivery date or a delivery lead time must be provided

Priced CLIN is missing a period of performance or a delivery date Currently, Integrity and the CPAP require either a POP or delivery date/ lead time on every priced CLIN. However, we do not check ordering period, lease, or funding period (unless these are captured by the same data element).

This error did occur in the last round of PDS reports: “When no occurrence of <Procurement Instrument Dates/Procurement Instrument Periods> is provided, then at least one occurrence of either <Delivery Details/ Delivery Dates> or <Delivery Details/Delivery Lead Time> must be provided.”

DoDAACs with error - N00189, N00244, N00604

10. Lead Time Events – Rule: If a delivery is scheduled based on date an event occurred, the event must be provided.

11. Acceptance/Inspection Entities – Rule: When an address is provided for an accepting or inspecting entity, then information on the action (acceptance, inspection, both) to be taken and the location (source, destination, other) must be provided. If the address is not for an accepting or inspecting entity, do not provide information on the action and location. An accepting entity must be provided.

If the Line Item is “Priced” (i.e., CLIN Type of the line item is equal to ‘1’) and either the InspectionTermsLocation or AcceptanceTermsLocation entries are not present (or empty) and there is no FOB entry (or its empty) validation will fail

For priced CLINs/SLINs you must have an approved Inspection Office

2012-06-10 10 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAPDODAAC For priced CLINs/SLINs you must have a valid Inspection Office DODAAC Inspection Office DODAACs and FOB are missing. For priced CLINs/SLINs you must have an approved Acceptance Office DODAAC. For priced CLINs/SLINs you must have a valid Acceptance Office DODAAC

Acceptance Office DODAACs and FOB are missing

12. Contact via File Transfer Protocol – rule: When the method for communicating with a contact is “FTP”, a URL must be provided. Contacts may be associated with an address or with a signature.

13. Ordering Limits for Indefinite Delivery/Indefinite Quantity (IDIQ) Contracts Rule: When the procurement instrument is an Indefinite Delivery/Indefinite Quantity (IDIQ) Contract, both a minimum and a maximum ordering limit must be provided.

14. Requirements Contracts – Ordering Quantity Rule: If the document is a requirements contract, then the estimated total quantity to be ordered must be provided. The actual quantity ordered may be higher or lower.

15. Requirements Contracts - Acquiring WorkRule: If the procurement instrument is used to acquire work (e.g. repair, mod, or overhaul) on existing items of Government property, a Government Property Clause, FAR 52.245-1 or FAR 52.245-2, must be included.

16. Cost Plus Incentive Fee – Clause RequirementRule: If the procurement instrument or line item has a cost plus incentive fee pricing arrangement, then FAR clause 52.216-10, Incentive Fee, must be provided.

17. Fixed Price Incentive – Clause Requirement Rule: If the procurement instrument or line item has a fixed price incentive pricing arrangement, then FAR clause 52.216-16, Incentive Price Revision – Firm Target, must be provided.

Integrity: A Priced CLIN that is FPI must have a target cost unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is FPI must have a target profit unless the line item UCA indicator is on, or "NSP" is designated

18. Multi-Year Contract - Cancellation Ceiling Rule: A cancellation ceiling amount shall be provided when the procurement instrument is a multi-year contract (FAR clause 52.217-2).

19. Recurring Payments

2012-06-10 11 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAPRule: A procurement instrument may only have recurring payments when each payment is for the same amount. Recurring payments may not be defined if the payment amount varies from one payment to the next.

20. Financial Reference for Obligated Amounts Rule: When an obligated amount is provided at the procurement instrument header level, an Accounting Classification Reference Number (ACRN) and either an Agency Accounting Identifier (AAI) or a line of accounting must be provided. When an obligated amount is provided at the line item level, the ACRN must be provided. The ACRN provided for the line item must be found with an obligated amount reported at the header level.

Integrity - MOCAS edit – when the LOA has a service designator of 97 or 17 it cannot contain an invalid AAA, TranType, or PAA field

CPAP - If the Line Item has a Funding element and a Fund Amount greater than zero then Line Item level funding validations (i.e., CheckFundingStrip, CheckCMET, CheckACRN, CheckFunding) will be performed.

CPAP - If a Sub Line Item that is a child of the Line Item that failed the CheckFunding section has an Option CLIN value that is not “1” and has either no Cost Constraint or a Cost Constraint which is not ‘NSP’ or ‘NC’, has a Funding element and a Fund Amount greater than 0 then Sub-CLIN level Funding validations (i.e., CheckFundingStrip, CheckCMET, CheckACRN, CheckFunding) will be performed or the validation will fail

CPAP - CheckACRN - If a Line Item has no associated Contract ACRN, the validation will fail

21. Total Contract Amount Rule: The total amount of the contract must be provided unless the contract is one of the following: • Agreements including Basic and Loan • Basic Ordering Agreement • Blanket Purchase Agreement • Blanket Purchase Agreement under Federal Supply Schedule • Facilities Contract • Schedule

Integrity: For non-basic contracts, there must be a total cost from CLINs, and it must be non-zero.

22. Financial Reference for Tax Amounts Rule: When a tax amount is not included in the total order amount, an Accounting Classification Reference Number must be provided. In addition, if the line of accounting was represented by an Agency Accounting Identifier (AAI), the AAI must be provided as well.

23. Percentage based Discounts Rule: When a discount is provided as a percentage, the base – line item total amount, line item unit price, total purchase amount - against which the percentage is applied, must be

2012-06-10 12 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAPprovided.Integrity: Discount terms detected, but format contains a decimal point… pleae confirm

Integrity: Discount terms detected, but days due missing or format is invalid… please update using popup

24. Percentage based Services, Allowances, and Charges

25. Unit Price when Not Separately Priced Rule: When a line item is not separately priced, the unit price must be zero.

Integrity: A Priced CLIN that is FPI must have a target cost unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is FPI must have a target profit unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is FPI must have a share ratio above unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is FPI must have a share ratio below unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is FPI must have a ceiling dollars unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is fixed price (except FPI), or T&M or LH must have a unit price unless the line item UCA indicator is on, or "NSP" is designated

Integrity: A Priced CLIN that is CPIF must have a target cost AND target profit fee unless line_item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is CPIF must have a minimum and maximum fee unless line_item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is CPIF must have a share ratio above unless the line_item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is CPIF must have a share ratio below unless the line_item UCA indicator is on, or "NSP" is designated Integrity: A priced CLIN that is COST or CS must have an estimated cost unless the line_item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is CPFF must have estimated cost and/or a fixed fee unless the line item UCA indicator is on, or "NSP" is designated is on

CPAP: Unit Price Checks are skipped if the Line Item is designated ‘NSP’

2012-06-10 13 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAP26. Share Ratio Rule: A share ratio for government and contractor is required

when the pricing arrangement is one of the following. A share ratio is not allowed for any other type of pricing arrangement:• Cost Plus Incentive Fee (Cost Based)• Cost Sharing• Fixed Price Incentive (Cost Based)• Fixed Price Incentive (Successive Targets)

Integrity: A Priced CLIN that is FPI must have a share ratio above unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is FPI must have a share ratio below unless the line item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is CPIF must have a share ratio above unless the line_item UCA indicator is on, or "NSP" is designated Integrity: A Priced CLIN that is CPIF must have a share ratio below unless the line_item UCA indicator is on, or "NSP" is designated Integrity: An informational CLIN that is FPI cannot contain a share ratio above Integrity: An informational CLIN that is FPI cannot contain a share ratio below Integrity: An informational CLIN that is CPIF cannot contain a share ratio above Integrity: An informational CLIN that is CPIF cannot contain a share ratio below

27. Contract Vehicle Fee Rule: A fee for using a contract vehicle can be levied only if the procurement instrument is a Blanket Purchase Agreement or an Indefinite Delivery Contract.

28. Labor Rates Rule: When a line item has a labor hour or time & material pricing arrangement, labor rates must be provided.

29. Small Business Administration (SBA) Contracts Rule: When either a Small Business Administration (SBA) contract number or SBA contracting office address is provided, then the other must be provided.

30. Pipeline DoDAAC Rule: Provide Department of Defense Activity Address Code (DoDAAC) of the pipeline when transportation method is specified as “Pipeline”.

31. United Nations Code Rule: Provide the United Nations code for ports and other locations (UN/LOCODE) in accordance with the United Nations Location Code Manual when the Freight on Board (FOB) point is a terminal.

32. Required Facility Clearance and Safeguard Level Rule: The required

2012-06-10 14 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAPsafeguard level cannot be higher than the level of the required facility clearance.

33. Clause Full Text and Fill-In Areas Rule: If a clause with fill in areas is

provided as full text and the fill in areas are not filled in, they must be denoted with a minimum of five underline characters.

Integrity: Fill-in Clause must have fill-in text. 34. Wage Determination Rule: Wage Determination cannot be under a

combination of the Davis Bacon Act and the Service Contract Act. A Wage Determination must be under one or the other

35. Miscellaneous Text Sections Rule: Only one block of miscellaneous text may be provided per Federal Uniform Contract Format (UCF) section.

36. Product and Service Data Rule: Information about the product is required when the purchased item is not a service.Note: Sub line items, informational sub line items, and exhibit lines may carry the product information or they may inherit it from their parent line item.

37. Information Sub-Line Items and Funded Amount Rule: When an obligated amount is provided on an information sub-line item, the funded amount must also be provided. These are the only amounts that shall be provided.

Integrity: There must be at least one funded CLIN or SubCLIN .

CPAP: If a Sub Line Item that is a child of the Line Item that passed the CheckFunding section has an Option CLIN value that is not “1” or has either no Cost Constraint or a Cost Constraint which is not ‘NSP’ or ‘NC’, it must have at least one Funding element and a Fund Amount greater than 0

38. Information Sub-Line Items and Delivery Schedules Rule: An information sub-line item cannot have a delivery schedule. CPAP: If the Line Item is “Priced” (i.e., CLIN Type of the line item is equal to ‘1’) and the count of Line Item Delivery elements is zero, the validation will fail – Delivery is not checked on Info SLINs

Integrity: All priced CLINs or subCLINs that have not been cancelled or terminated, must have a CLIN delivery date or a performance delivery date. CLINs that have a cost constraint of NSP are excluded from this check.

39. Attachment Data Format Rule: When the attachment is included in the procurement instrument document as binary text, the data format of the attachment must be provided.

40. Contract Security Classification Specification – Special Access Information Rule: Special access information requirements may be identified by

2012-06-10 15 | P a g e

Navy PDS White Paper Addendum

COMPLIANCE BUSINESS RULES (OTHER)

VALIDATION PDS INTEGRITY CPAPeither a check box or by including specific text but not by both.

2012-06-10 16 | P a g e