procurement data standards (pds) · web view2018/03/23 · which financial systems are contacted...

Procurement Data Standards (PDS)

Schema Implementer Guide

Version 5.2

DRAFT 23 March 2018

Prepared For:OUSD(ATL)/DPAP3060 Defense Pentagon, Room 3B855Washington, DC 20301Attn: Bruce Propert

Prepared By:Northrop Grumman Systems Corporation7575 Colshire DriveMcLean, VA 22102

This page intentionally left blank.

Table of Contents1 Introduction...............................................................................................................................................................

1.1 Purpose...................................................................................................................................................................1.2 Document Organization..........................................................................................................................................1.3 Reference Documents.............................................................................................................................................1.3.1 Business Rules Document............................................................................................................................31.3.2 Enumeration Annotation Document...........................................................................................................31.3.3 Instructions for Reading the Documents.....................................................................................................3

2 XML Terms and Formatting........................................................................................................................................2.1 XML Terms..............................................................................................................................................................2.2 XML Formatting.......................................................................................................................................................2.2.1 Special Characters.......................................................................................................................................52.2.2 Empty XML Elements..................................................................................................................................6

3 Definitions..................................................................................................................................................................3.1 Document Purpose.................................................................................................................................................3.2 Other Amounts.......................................................................................................................................................3.3 Limits.....................................................................................................................................................................

4 How to: Contract Awards.........................................................................................................................................4.1 Originator Details..................................................................................................................................................4.1.1 DoD System Example.................................................................................................................................124.1.2 Non-DoD System Examples.......................................................................................................................12

4.2 Procurement Instrument Form.............................................................................................................................4.3 Procurement Instrument Identifiers.....................................................................................................................4.3.1 Awards......................................................................................................................................................194.3.2 Call, Delivery, and Task Orders..................................................................................................................204.3.3 Solicitation Number...................................................................................................................................24

4.4 Addresses..............................................................................................................................................................4.4.1 Construction Project..................................................................................................................................324.4.2 Issued By...................................................................................................................................................344.4.3 Administered By........................................................................................................................................354.4.4 Contractor.................................................................................................................................................364.4.5 Mail Invoices to Address Shown In............................................................................................................414.4.6 Payment Will Be Made By.........................................................................................................................424.4.7 Ship To/Mark For.......................................................................................................................................434.4.8 Remittance................................................................................................................................................474.4.9 Party to Receive Offer...............................................................................................................................49

4.5 Contingency Contract............................................................................................................................................4.6 Signature Blocks....................................................................................................................................................4.6.1 Offeror.......................................................................................................................................................524.6.2 Contractor Representative........................................................................................................................544.6.3 Contracting Officer....................................................................................................................................56

4.7 Dates.....................................................................................................................................................................4.7.1 Effective Date............................................................................................................................................574.7.2 Delivery Dates...........................................................................................................................................594.7.3 Period of Performance..............................................................................................................................61

4.8 Solicitation/Offer Information...............................................................................................................................4.8.1 Acquisition Information.............................................................................................................................644.8.2 Type of Solicitation....................................................................................................................................674.8.3 Solicitation Issue Date...............................................................................................................................684.8.4 Offer Delivery Information........................................................................................................................69

PDS v2.5.1 Schema Implementer Guide – 23 March 2018 Draft i

4.8.5 Solicitation Acceptance Calendar Days......................................................................................................714.8.6 Solicitation Contact...................................................................................................................................734.8.7 Acknowledgement of Amendments..........................................................................................................744.8.8 Delivery Lead Time....................................................................................................................................764.8.9 Performance Payment Bonds (Calendar Days)..........................................................................................784.8.10 Offer Guarantee........................................................................................................................................79

4.9 Pricing...................................................................................................................................................................4.9.1 Pricing Arrangement.................................................................................................................................804.9.2 Accounting and Appropriation Data..........................................................................................................834.9.3 Currency....................................................................................................................................................894.9.4 Total Amount............................................................................................................................................904.9.5 Discount Terms/Prompt Payment.............................................................................................................92

4.10 Delivery FOB..........................................................................................................................................................4.11 Attachments..........................................................................................................................................................4.12 Schedule of Supplies/Services...............................................................................................................................4.13 Ordering Information..........................................................................................................................................4.13.1 Estimated Quantity.................................................................................................................................1024.13.2 Limits.......................................................................................................................................................1044.13.3 Ordering Capability.................................................................................................................................1054.13.4 Order Variation.......................................................................................................................................1064.13.5 Response Days to Reject Order...............................................................................................................108

4.14 Clauses................................................................................................................................................................4.15 Reference Numbers............................................................................................................................................4.15.1 Federal Supply Classification and Product Service Code.........................................................................1154.15.2 Defense Priorities and Allocations System Priority Rating.......................................................................1154.15.3 Requisition Number/Project Number/Purchase Request Number..........................................................116

4.16 Brief Description.................................................................................................................................................4.17 Authority for Using Other than Full and Open Competition...............................................................................4.18 Construction Project Details................................................................................................................................4.18.1 Project Title and Location........................................................................................................................1214.18.2 Project Number.......................................................................................................................................122

4.19 Signed Order Copies............................................................................................................................................4.20 Multiple Line Items Information.........................................................................................................................

5 How to: Contract Modifications.............................................................................................................................5.1 Modification Number..........................................................................................................................................5.1.1 Modification to a 4-digit Order................................................................................................................129

5.2 Modification Details............................................................................................................................................5.2.1 Documents Being Modified.....................................................................................................................1305.2.2 Description of Modification.....................................................................................................................1335.2.3 Project Number.......................................................................................................................................1345.2.4 Type of Modification and Modification Authority...................................................................................135

5.3 Changing Existing Contract Data.........................................................................................................................5.3.1 Method 1: Changing a Data Element or Section Using Attributes...........................................................1375.3.2 Method 2: Providing Complete Section Details.......................................................................................141

5.4 Changing Amounts..............................................................................................................................................

PDS v2.5.1 Schema Implementer Guide – 23 March 2018 Draft ii

Document Change RecordVersion Change Owner Change Date Changes5.0 NG/Jessica Huckabee 8/31/2015 First published version5.1 NG/Jessica Huckabee 2/29/2016 Added Originator Details section

Updated ‘Limit’ section to expand on definition

Added Line Item Add, Change, Delete section

5.2 NG/Jennifer Neale 3/23/2018 Reorganized, updated, and added many new sections to the document

PDS v2.5.1 Schema Implementer Guide – 23 March 2018 Draft iii

1 Introduction

1.1 PurposeThis document is designed for those who are tasked with meeting the Procurement Data Standard (PDS) requirement to generate and utilize PDS XML (Extensible Markup Language) documents. By using the Standard Forms (SF) and Department of Defense (DD) forms commonly used during the procurement process, a crosswalk between the forms and the PDS is provided. An example mapping from a block on the forms to the PDS XML element is provided to help individuals involved in the creation and consumption of a PDS XML document. Though the XML details are based on the PDS Award and Modification v2.5.1, much of the information is transferrable to other standards and versions such as PRDS Purchase Request v3.0 and PDS Solicitations and Amendments v2.5.1.

1.2 Document OrganizationThe document has several sections:

An XML Terms and Formatting section that provides term definitions and formatting conventions that must be adhered to.

A Definitions section that provides definitions of terms and the impact of their use on the XML transaction if applicable.

A How to section for awards that shows how each block on the form is mapped to a PDS XML document. A How to section for modifications section that describes how to use the PDS XML to issue contract

modifications.

The following example shows how the “How to” section would be organized for the blocks that are used for discount terms (a complete example is provided later). Based on what mapping is being illustrated, a “How To” section may be organized differently and may not contain all of the following subsections:

Form Location: For each element, the corresponding block and its title is listed for the applicable forms. Below is the list of forms and blocks where discount terms are provided:

Form Block Number Block TitleDD 1155 12 DISCOUNT TERMSSF 26 9 DISCOUNT FOR PROMPT PAYMENTSF 33 13 DISCOUNT FOR PROMPT PAYMENTSF 1447 15 PROMPT PAYMENT DISCOUNTSF 1449 12 DISCOUNT TERMS

It is important to note that the inclusion of elements varies by form and not each element is found on each form. Some information is not entered in the form blocks, but in additional continuation sheets of the form.

Sample Block: For each element, an example is provided by showing the block as seen on the corresponding form to represent the link between the form and the XML schema shown in the section below.

9. DISCOUNT FOR PROMPT PAYMENT2%/ 20, Net Days 30SF 26, Block 9

PDS v2.5.1 Schema Implementer Guide – 23 March 2018 Draft 1

Schema Location: For each element, the data is shown as it is found in the schema using the same data shown in the example above it. To more succinctly represent the data, the common path used by all elements is located at the beginning of the section, and the ‘@’ symbol is used to represent the common path found at the beginning of each unique element path.

For example, the paths for the three discount terms elements with their respective values in quotes are:

ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ PaymentDiscount/ Terms/ Percent/ “2.00”ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ PaymentDiscount/ Terms/ DaysDue/ “20”ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ PaymentDiscount/ NetDays/ “30”

the common path is provided as:

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/

and the truncated version is:

@ PaymentDiscount/ Terms/ Percent/ “2.00”@ PaymentDiscount/ Terms/ DaysDue/ “20”@ PaymentDiscount/ NetDays/ “30”

XML Sample: This section shows the data as it would be seen in the XML. This example uses the data shown in the “Sample Block” section above:

Schema View: This section contains a picture of the schema taken from the XMLSpy application. The picture shows the relationship of the elements within the XML schema.


<PaymentDiscount><Terms>

<Percent>2.00</Percent><DaysDue>20</DaysDue>

</Terms><NetDays>30</NetDays>

</PaymentDiscount>

1.3 Reference DocumentsInformation about the PDS and other enterprise initiatives are provided on the Defense Procurement and Acquisition Policy (DPAP) E-Business website - http://www.acq.osd.mil/dpap/pdi/eb/procurement_data_standard.html. The site also provides several documents that help the implementer produce successful PDS XML documents. Some of the documents are described below.

1.3.1 Business Rules DocumentThe PDS standard format for procurement instruments is defined in an XML Schema Definition (xsd) file which can be used to validate the structure of a PDS XML document. While many of the functional business rules regarding what and when data are required are part of the schema, others are described in the annotations or in the regulations and must be enforced by validations outside of the schema. The “PDS Business Rules” document provides the details about those validations or Business Rules and unless explicitly stated, applies to all previous PDS schema versions.

1.3.2 Enumeration Annotation DocumentEach published version of the schema also has a “PDS Enumeration Annotation” document for items in the schema. In this document, the full list of identifiers are provided as well as their associated definition, acceptable values, and format. This information is also found in the schema file (.xsd), but this document is useful for those who do not have a schema reader.

1.3.3 Instructions for Reading the DocumentsFor those new to XML schemas, the “Instructions for Reading the Documents” PowerPoint file provides explanations of the various symbols that appear in the schema views used in this document.


http://www.acq.osd.mil/dpap/pdi/eb/procurement_data_standard.html

2 XML Terms and FormattingThis section provides definitions for XML terms and how they are used throughout this document. It also provides direction on conventions that need to be followed in order for the PDS XML document to process successfully.

2.1 XML TermsThese XML terms are used throughout the document as defined here.

A tag marks the start or end of an element.

Examples: <price> and </price>

An attribute provides extra information within a tag.

Example: <price currency="dollar">

An element is a value surrounded by an opening tag and a closing tag.

Example: <price currency="dollar">29.99</price>

A complex element is an element that contains child element(s) and/or attributes. For readability, the term section will be used in this document to describe a complex element and its contents. When referring to a section within a particular section, the term subsection will be used.

Example:<book category="fiction"> <title>Harry Potter</title> <author>J K. Rowling</author> <year>2005</year></book>

The XML Schema Definition (XSD) describes the structure of an XML document. It defines the building blocks of an XML document such as:

the elements and attributes that can appear in a document the number of (and order of) child elements data types for elements and attributes default and fixed values for elements and attributes

Example:<xs:element name="book"> <xs:complexType> <xs:attribute name="category" type="xs:string"/> <xs:sequence> <xs:element name="title" type="xs:string"/> <xs:element name="author" type="xs:string"/> <xs:element name="year" type="xs:positiveInteger"/> </xs:sequence> </xs:complexType></xs:element>


2.2 XML FormattingThe following formatting conventions must be adhered to in order for a PDS XML document to be processed successfully.

2.2.1 Special CharactersMany special characters cannot be included in the PDS XML. They must be handled through a separate process in order for the XML to correctly represent the character. PDS has a predefined list of codes to use in place of the special characters. In addition, the use of “CDATA” is not allowed.

Here are some examples of special characters that are not allowed and their replacements:

Special Character Replacement& &

< <

> >

‘ '

For a full list of special characters that are not permitted in the PDS, please see the most up to date version of the PDS Business Rules document.

Sample Block

M5000-15-P-0111

Section B SF 1449 – CONTINUATION SHEET

ITEM NO. SUPPLIES/ SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 SUPPLIES OR SERVICES AND PRICES/COSTS

FFPSafety Rope100’ of Continuous Rescom Communications Rope

100 UN 1.00 $100.00

SF 1449, Section B – Supplies or services and prices/costs


XML Sample

2.2.2 Empty XML ElementsPDS does not accept empty elements. An element is considered to be empty when it has one of the following formats:

<Year></Year> <Year> </Year> <Year/>


<ContractLineItems><LineItems>

<LineItemBasicInformation><ProductServicesOrdered>

<ProductorService>PersonalProperty</ProductorService><ProductServiceDescription>

Safety Rope 100' of Communications Rope</ProductServiceDescription>

</ProductServicesOrdered></LineItemBasicInformation>

</LineItems> </ContractLineItems>

3 Definitions This section provides the meanings of various terms. Where applicable, it also describes the impact of their use on an XML transaction.

3.1 Document Purpose The <DocumentPurpose> element is used to indicate why the procurement document is being submitted and affects how it is processed by the Global Exchange Service (GEX) and recipient systems. Some values allow the submitter to validate the xml and address any issues prior to signing the award or other document the xml represents. Some signal that pre-signature funds certification is requested while others are for transmitting a signed document.

<DocumentPurpose> is located in the schema at:

ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/

An example of the populated element in a PDS XML is:

The table below provides a definition for each value. The values are grouped according to their function.

<DocumentPurpose> Value Group DefinitionCancellation C Indicates that a draft transaction has been cancelled. Only used on telecommunication

documents (DD Form 428).Conformance Text A Use to determine whether a contract modification will successfully conform to earlier

contract actions. May only be used by the Electronic Document Access (EDA) system at this time.

Draft C Indicates that a procurement document is being sent to the contractor for review and comment prior to issuing an original. Only used on telecommunication documents (DD Form 428).

Funds Certification Request B Initiates a pre-award funds certification process known as Handshake 2 of the Procure-to-Pay (P2P) process.

Original C Indicates an original, signed procurement document.Retransmission C Use when an original document is being retransmitted.Transfer C Use to transfer an award instrument or modification to another organization. For

example, to another Contract Administrative Office for administration.Validation Test A Initiates a pre-award validation process. It is highly recommended that a document be

tested before signing since the only way to correct an error on a signed document is to issue a modification.

The functionality for each group is as described below:

Group A – Pre-Signature Validation : These values are used when the submitter wants to validate the procurement document without a copy being sent to any other system. In addition, it provides the document writer the chance to find and correct any errors before they sign it. The xml file is sent to the GEX where the validations check that the xml structure and contents are following the schema definition and that the document follows procurement regulations. The results are returned to the submitter in a Validation Result xml as shown in the diagram below. Some DoD systems capture and display the results to the document writer.

Note: When requesting a validation or conformance test, the signature date on the document should be the date that the request is being submitted.


<ProcurementInstrumentHeader><BasicInformation>

<DocumentPurpose>Original</DocumentPurpose></BasicInformation>

</ProcurementInstrumentHeader>

Note: This is the only time a web service connection may be used with GEX.

Group A – Pre-Signature Validation Data Flow

Group B – Funds Certification Request : This value is used when Handshake 2 of the Procure-to-Pay (P2P) process is requested via the GEX. The document must successfully pass the PDS validations before it will be passed on to one or more financial systems. Which financial systems are contacted is determined by the accounting data in the document and by the individual financial system’s capability to perform the certification electronically.

The PDS validation results are returned to the submitter in a Validation Result xml along with the list of financial systems who must perform funds certification and which were contacted by the GEX. Funds certification with those systems that are not contacted by GEX must be performed outside of this process.

After a designated period of time, the results from the financial systems contacted by GEX will be collected into another Validation Result xml and provided to the requesting system. Thus, unless none of the needed financial systems have implemented a GEX connection for this process or the PDS XML failed to pass the validations, each funds certification request will result in two Validation Response xml transactions.

Note: When requesting a funds certification request, the signature date on the document should be the date that the request is being submitted.

Group B – Funds Certification Request Data FlowGroup C – Signed Documents: These values are used when the document has been signed and released. The document must successfully pass the PDS validations before it will be passed onto any other system including the Electronic Document Access (EDA). To fix any errors, a modification must be issued.

The xml file is sent to the GEX where the validations check that the xml structure and contents follow the schema definition and check that the document follows procurement regulations. The results are returned to the submitter in a Validation Result xml as shown in the diagram below. Some DoD systems capture and display the results to the document writer.


Group C –Signed Documents Data Flow

3.2 Other AmountsEach contract requires various amounts other than obligated amounts based on the pricing arrangement and whether or not a contract has been definitized. The Business Rules document contains detailed information about which other amount values should be provided.

The amounts are provided in the <OtherAmounts> sections of the schema located at the following:

Document level: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAmounts/ OtherAmounts

Line item level: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ LineItemAmounts/ ItemOtherAmounts

An example of the populated element in a PDS XML is:

The table below provides a definition for each type of amount.

<AmountDescription> Value DefinitionAward Fee The total pool of award money that a contractor can earn over the life of the contract. The

actual amount of the award for each evaluation period is based on the contractor’s performance against a set of predefined criteria that are laid out in the award-fee plan.

Base Price The price of the contract before any economic price adjustments are applied. Base Price is mainly applicable to Fixed Price contracts with Economic Price Adjustment.

Cancellation Ceiling The amount at which the Government can cancel the contract. This provides protection to the contractor in the event that the Government cannot continue the contract due to lack of funds. It should only be provided when the procurement instrument is a multi-year contract.

Ceiling Price The maximum amount that may be paid to the contractor, except for any adjustment under other contract clauses. When the price of the contract exceeds this ceiling, the contract can be terminated by the Government.

Estimated Cost The level of cost that the contractor most likely obtains under normal performance conditions. Estimated Cost is used with cost-reimbursement types of contracts for the purpose of obligating funds and establishing a ceiling that the contractor may not exceed without the approval of the contracting officer.

Fee for using Contract Vehicle The fee charged for using a contract vehicle such as a Blanket Purchase Agreement or an Indefinite Delivery Contract.

Firm Price A price that is not subject to any adjustment on the basis of the contractor’s cost in performing the contract.


<ProcurementInstrumentHeader><ProcurementInstrumentAmounts>

<OtherAmounts><AmountDescription>Estimated Cost</AmountDescription><Amount>150,000</Amount>

</OtherAmounts><OtherAmounts>

<AmountDescription>Not to Exceed Amount (Funding)</AmountDescription><Amount>170,000</Amount>

</OtherAmounts></ProcurementInstrumentAmounts>


<AmountDescription> Value DefinitionFixed Fee A fee payable to the contractor at the end of the contract period if the performance is

considered satisfactory by the Government.Funded Amount The amount of funds obligated under the contract.Header Only – Total Contract Value

The total value of the contract at its completion. This value can only be provided at the header level of the document.

Initial Target Cost Used with Fixed Price Incentive (Successive Targets) contracts. These targets may be revised during the performance of the contract once more reliable pricing information is available.

Initial Target Profit Used with Fixed Price Incentive (Successive Targets) contracts. These targets may be revised during the performance of the contract once more reliable pricing information is available.

Minimum Fee The minimum fee limitation used when adjusting the contractor’s fee after contract performance.

Maximum Fee The maximum fee limitation used when adjusting the contractor’s fee after contract performance.

Not to Exceed Amount (Funding) The maximum amount of funds that can be obligated. Organizations should not obligate funds in excess of the Not to Exceed Amount. Used for incrementally funded contracts, undefinitized contracts, and cost-reimbursement contracts.

Profit Floor The minimum value of the contractor’s total profit.Profit Ceiling The maximum value of the contractor’s total profit.Target Cost The targeted cost that the contractor earns for fulfilling the contract.Target Profit The targeted profit that the contractor earns for fulfilling the contract.Target Price The sum of the target cost and the target profit.

3.3 LimitsLimits are used on ordering instruments. They indicate the amounts of supplies or services that may be ordered under the contract. The limits may be stated either as number of units or as dollar values.

The table below provides a definition for each <LimitDescription> value.

<LimitDescription> Value DefinitionAllowed Per Order The total minimum and maximum quantity of supplies or services the Government is

obligated to order for each order under the ordering instrument. Contractor Obligation to Deliver The minimum and maximum quantity that the contractor is obligated to deliver under the

contract.Government Obligation to Order The minimum and maximum quantity that the government is obligated to order under the

contract.


4 How to: Contract Awards

This section shows how to map contract writing system metadata and procurement form data to the corresponding elements in the PDS XML document.

4.1 Originator DetailsThe data in the <OriginatorDetails> section contains metadata about the DoD or Non-DoD contract writing system that is producing the PDS document. This system data is not provided on the forms but is required when producing a PDS document. It can be used to determine if a trend is indigenous to a particular application or instance of an application.

These elements must be provided for DoD Systems:

Element ExplanationInternal Document Number Used to track a contract action internally. Some contract writing systems use a number unique to the

system while others use the contract award or modification number. DoD Information Technology Portfolio Repository (DITPR) Number

Used to identify the originating contract writing system. The DoD assigns a unique DITPR number for each DoD IT system. To determine the DITPR number for a system, use this link (requires a CAC): https://ditpr.dod.mil/

System Administrator DoD Activity Address Code (DoDAAC)

Used to identify the organization that administers the contract writing system. This is usually different from the contract issuing office(s) that use the application.

These elements must be provided for non-DoD Systems:

Element ExplanationInternal Document Number Used by the contract writing system to track a contract action internally. Some use a number unique to

the system while others use the contract award or modification number. System Name The name of the originating contract writing system. Can be up to 30 characters.

System Version The version of the originating System.

Non-DoD Entity Identifier Identifies the entity responsible for the contract writing system. One or more of the following optional codes must be provided:

Activity Address Code (AAC): This code is a Federal AAC and must be in the authorized Federal AAC list located at DAASINQ (DAASC Inquiry System).

CAGE Code: The Commercial and Government Entity (CAGE) Code is an ID number used extensively within the Federal Government, assigned by the Defense Logistics Agency (DLA). The official data source for these codes is the DLA CAGE system.

DUNS Number: The Data Universal Numbering System (DUNS) number is issued and maintained by Dun & Bradstreet (D&B).

DUNS +4: This DUNS identifier with a four character suffix. This suffix is created by registrants in the Central Contractor Registration (CCR) system when there is a need for more than one bank/Electronic Funds Transfer (EFT) account for a location.

Alternate Identifier: An alternate type of data for identifying an entity. This is comprised of a description element and a value element.


https://ditpr.dod.mil/

4.1.1 DoD System ExampleEach DoD system has a number assigned within the DoD Information Technology (IT) Portfolio Repository (DITPR). This number must be provided along with the System Administrator DoDAAC which identifies the organization that administers the system.

Schema LocationMajor Path: ProcurementDocument/ OriginatorDetails/

@ InternalDocumentNumber/ “407066”@ DoDSystem/ DITPRNumber/ “00000431”@ DoDSystem/ SystemAdministratorDoDAAC/ “FA2521”

Note: The DITPR number “00000431” indicates that the system of origin is an SPS instance.

XML Sample

4.1.2 Non-DoD System ExamplesOriginating non-DoD Systems must provide an system name, version, and at least one identifier for the system.

4.1.2.1 Example 1: Using a single <NonDoDIdentifier>

This example demonstrates using an activity address code to identify the system.

Schema Location

Major Path: ProcurementDocument/ OriginatorDetails/

@ InternalDocumentNumber/ “428646”@ NonDoDSystem/ NonDoDEntityIdentifier/ ActivityAddressCode/ “123142”@ NonDoDSystem/ SystemName/ “USDA Integrated Acquisition System (IAS)”@ NonDoDSystem/ SystemVersion/ “4.0”

XML Sample


<OriginatorDetails> <InternalDocumentNumber>407066</InternalDocumentNumber <DoDSystem> <DITPRNumber>00000431</DITPRNumber> <SystemAdministratorDoDAAC>FA2521</SystemAdministratorDoDAAC> </DoDSystem>`</OriginatorDetails>

<OriginatorDetails> <InternalDocumentNumber>428646</InternalDocumentNumber <NonDoDIdentifier> <ActivityAddressCode>123142</ActivityAddressCode > <NonDoDIdentifier> <SystemName>USDA Integrated Acquisition System (IAS)</SystemName> <SystemVersion>4.0</SystemVersion></OriginatorDetails>

4.1.2.2 Example 2 – Using multiple <NonDoDIdentifier>s

This example demonstrates using an activity address code, a DUNS +4 number, and an alternate identifier (USDA Office) to identify the system.

Schema Location

Major Path: ProcurementDocument/ OriginatorDetails/

@ InternalDocumentNumber/ “428646”@ NonDoDSystem/ NonDoDEntityIdentifier/ ActivityAddressCode/ “123142”@ NonDoDSystem/ NonDoDEntityIdentifier/ Duns4Number/ “088365767”@ NonDoDSystem/ NonDoDEntityIdentifier/ AlternateIdentifier/ Description/ “USDA Office”@ NonDoDSystem/ NonDoDEntityIdentifier/ AlternateIdentifier/ Value/ “POD-WDC(3142)”@ NonDoDSystem/ SystemName/ “USDA Integrated Acquisition System (IAS)”@ NonDoDSystem/ SystemVersion/ “4.0”

XML Sample


<OriginatorDetails> <InternalDocumentNumber>428646</InternalDocumentNumber <NonDoDIdentifier> <ActivityAddressCode>123142</ActivityAddressCode >

<Duns4Number>088365767</Duns4Number><AlternateIdentifier> <Description>USDA Office</Description> <Value>POD-WDC(3142)</Value></AlternateIdentifier>

<NonDoDIdentifier> <SystemName>USDA Integrated Acquisition System (IAS)</SystemName> <SystemVersion>4.0</SystemVersion></OriginatorDetails>

Schema View

4.2 Procurement Instrument FormThe <ProcurementInstrumentForm> element is the form number used for the procurement document and is used by the Electronic Document Access (EDA) system to produce a readable version of the XML. There are three types of forms used by procurement documents:

1. Standard Forms (SF) 2. Department of Defense Forms (DD)3. Optional Forms (OF)


The following forms are available for use in the PDS:

Form Form Type Usage

DD 428 COMMUNICATION SERVICE AUTHORIZATION Awards, Mods

DD 1155 ORDER FOR SUPPLIES OR SERVICES Awards, Mods

OF 307 CONTRACT AWARD Awards, Mods

SF 26 AWARD/ CONTRACT Awards, Mods

SF 30 AMENDMENT OF SOLICITATION/ MODIFICATION OF CONTRACT Amendments, Mods

SF 33 SOLICITATION, OFFER, AND AWARD Solicitations, Awards, Mods

SF 252 ARCHITECT-ENGINEER CONTRACT Awards, Mods

SF 1442 SOLICITATION, OFFER, AND AWARD (Construction, Alteration, or Repair) Solicitations, Awards, Mods

SF 1447 SOLICITATION/CONTRACT Solicitations, Awards, Mods

SF 1449 SOLICITATION/ CONTRACT/ ORDER FOR COMMERCIAL ITEMS Solicitations, Awards, Mods

Form Location

The form number can be found at the bottom of most forms.

Sample

Bottom of SF 1449

Schema Location/ ProcurementDocument/ ProcurementInstrumentForm/ “SF 1449”

XML Sample


<ProcurementDocument> <SchemaVersionUsed>2.5.1</SchemaVersionUsed> <ProcurementInstrumentForm>SF 1449</ProcurementInstrumentForm></ProcurementDocument>

Schema View

4.3 Procurement Instrument IdentifiersThese identifiers are contained in the <ProcurementInstrumentIdentifier> section of the schema and are unique values used to identify procurement instruments numbers such as an award, order, schedule, etc. Depending on the situation, there are three subsections in which a procurement instrument identifier may be provided:

<ProcurementInstrumentNumber> - used to capture numbers for documents originating from the DoD. <UniformProcurementInstrumentIdentifier> - used to capture non-DoD numbers that follow the FAR

procedures for assigning procurement instrument identifiers. <NonDoDNumber> - used to capture non-DoD numbers that do not follow the FAR.

Within the <ProcurementInstrumentIdentifier> section of the schema, there are three additional elements that contain data that is not part of the procurement instrument identifier:

<ProcurementInstrumentOrigin> - the organization (i.e. “Department of Defense” or “General Services Administration”) which issued the contract action.

<ProcurementInstrumentVehicle> - the type of contract or solicitation (i.e. “Indefinite Delivery Indefinite Quantity” or “Request for Quotation – Automated”).

<ProcurementInstrumentDescription> - how this instance of the <ProcurementInstrumentIdentifer> section is related to the information in the document. For instance, if the element contains “Represented Contract”, then this instance of <ProcurementInstrumentIdentifer> contains the identifier for the contract represented by the data in the XML document.

Note: There may be other instances of the <ProcurementInstrumentIdentifier> section that are used as references to instruments that are related to the instrument represented by the PDS XML. One example of this would be a reference to the Ordering Instrument being used for an Order. In this case, the <ProcurementInstrumentDescription> would contain “Ordering Instrument”.

The following Schema Views are used throughout the rest of this section:Schema View (with <UniformProcurementInstrumentIdentifier> section expanded)


Schema View (with <ProcurementInstrumentNumber> section expanded)


4.3.1 AwardsThis section addresses all Award types except for delivery, call, and task orders. They are covered in the next section.

Form Location

Form Block Number Block TitleDD 1155 1 CONTRACT/ PURCH ORDER/ AGREEMENT NO. (when block 2, DELIVERY ORDER/ CALL NO., is

empty)OF 307 1 CONTRACT NUMBERSF 26 2 CONTRACT (Proc. Inst. Ident.) NO.SF 33 2 CONTRACT NUMBERSF 252 1 CONTRACT NO.SF 1442 4 CONTRACT NUMBERSF 1447 2 CONTRACT NUMBERSF 1449 2 CONTRACT NO. (when block 4, “ORDER NUMBER”, is empty)

Sample Block

2. CONTRACT NO.

FA5702-17-C-0029DD 1449, Block 2

Schema Location

The Contract Number from the forms is used to populate the <ProcurementInstrumentIdentifier> section of the PDS XML file. Each piece of the contract number is captured in the separate data elements <EnterpriseIdentifier>, <Year>, <ProcurementTypeCode>, and <SerializedIdentifier>.

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentIdentifier/

@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Contract (Definitive)”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “FA5702”@ ProcurementInstrumentNumber/ Year/ “17”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “C”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “0029”@ ProcurementInstrumentDescription/ “Represented Contract”


XML Sample

4.3.2 Call, Delivery, and Task Orders Call, delivery, and task orders require providing two iterations of the <ProcurementInstrumentIdentifier> section of the schema: one for the order number and one for the ordering instrument number.

Form Location: Order Number

Form Block Number Block TitleDD 1155 2 DELIVERY ORDER/CALL NO.SF 1449 4 ORDER NUMBER

Form Location: Ordering Instrument Number

Form Block Number Block TitleDD 1155 1 CONTRACT/PURCH ORDER/AGREEMENT NO.SF 1449 2 CONTRACT NUMBER

4.3.2.1 Example 1: DoD Order against a DoD Ordering Instrument

This example demonstrates the numbering for a DoD order made against a DoD ordering instrument. There are two iterations of the <ProcurementInstrumentIdentifier> section: one for the order and the other for the ordering instrument.

Sample Block

1. CONTRACT/PURCH ORDER/AGREEMENT NO. 2. DELIVERY ORDER/CALL NO. FA5702-17-A-0029 SP4701-18-F-0001

DD 1155, Blocks 1 and 2


…<ProcurementInstrumentHeader>

<ProcurementInstrumentIdentifier><ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Contract (Definitive)</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>FA5702</EnterpriseIdentifier><Year>17</Year><ProcurementInstrumentTypeCode>C</ProcurementInstrumentTypeCode><SerializedIdentifier>0029</SerializedIdentifier>

</ProcurementInstrumentNumber><ProcurementInstrumentDescription>Represented Contract</ProcurementInstrumentDescription>

</ProcurementInstrumentIdentifier></ProcurementInstrumentHeader>…

Schema Location

The order should have a <ProcurementInstrumentDescription> of “Represented Contract.” This indicates that the data in the XML file pertains to the order. The ordering instrument should have a <ProcurementInstrumentDescription> of “Ordering Instrument”.


@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Delivery Order”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “SP4701”@ ProcurementInstrumentNumber/ Year/ “18”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “F”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “0001”@ ProcurementInstrumentDescription/ “Represented Contract”

@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Blanket Purchase Agreement”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “FA5702”@ ProcurementInstrumentNumber/ Year/ “17”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “A”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “0029”@ ProcurementInstrumentDescription/ “Ordering Instrument”

XML Sample

4.3.2.2 Example 2: DoD Order against a GSA Schedule

This example demonstrates the numbering for a DoD order made against a GSA schedule which is a non-DoD ordering instrument. There are two iterations of the <ProcurementInstrumentIdentifier> section: one for the order and the other for the ordering instrument.



<ProcurementInstrumentIdentifier><ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Delivery Order</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>SP4701</EnterpriseIdentifier><Year>18</Year><ProcurementInstrumentTypeCode>F</ProcurementInstrumentTypeCode><SerializedIdentifier>0001</SerializedIdentifier>


</ProcurementInstrumentIdentifier><ProcurementInstrumentIdentifier>

<ProcurementInstrumentOrigin>Department Of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Blanket Purchase Agreement</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>FA5702</EnterpriseIdentifier><Year>17</Year><ProcurementInstrumentTypeCode>A</ProcurementInstrumentTypeCode><SerializedIdentifier>0029</SerializedIdentifier>

</ProcurementInstrumentNumber><ProcurementInstrumentDescription>Ordering Instrument</ProcurementInstrumentDescription>

</ProcurementInstrumentIdentifier>…

</ProcurementInstrumentHeader>…

Sample Block

1. CONTRACT/PURCH ORDER/AGREEMENT NO. 2. DELIVERY ORDER/CALL NO. GS-35F-0265X N00014-17-F-4011


Schema LocationMajor Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentIdentifier/

@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Delivery Order”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “N00014”@ ProcurementInstrumentNumber/ Year/ “17”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “F”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “4001”@ ProcurementInstrumentDescription/ “Represented Contract”

@ ProcurementInstrumentOrigin/ “General Services Administration”@ ProcurementInstrumentVehicle/ “Schedule”@ NonDoDNumber/ “GS-35F-0265X”@ ProcurementInstrumentDescription/ “Ordering Instrument”

Note: The iteration for the ordering instrument contract number uses the <NonDoDNumber> element because the contract number does not follow the numbering rules laid out by the FAR. If the contract number did follow the FAR rules, the number would be mapped using the separate elements within the <UniformProcurementInstrumentIdentifier> section.

XML Sample


…<ProcurementInstrumentIdentifier>

<ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Delivery Order</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>N00014</EnterpriseIdentifier><Year>17</Year><ProcurementInstrumentTypeCode>F</ProcurementInstrumentTypeCode><SerializedIdentifier>4011</SerializedIdentifier>



<ProcurementInstrumentOrigin>General Services Administration</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Schedule</ProcurementInstrumentVehicle><NonDoDNumber>GS-35F-0265X</NonDoDNumber><ProcurementInstrumentDescription>Ordering Instrument</ProcurementInstrumentDescription>


4.3.2.3 Example 3: DoD Order against a DoD Ordering Instrument under a GSA Schedule

This example demonstrates the numbering for a DoD order made against a DoD Ordering Instrument that is under a GSA schedule. In this case, there are three iterations of the <ProcurementInstrumentIdentifier> section: one for the order, one for the DoD ordering instrument, and one for the GSA Schedule.

Sample Block

1. CONTRACT/PURCH ORDER/AGREEMENT NO. 2. DELIVERY ORDER/CALL NO. N44255-18-A-4036 N44255-18-F-4016


Schema LocationMajor Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentIdentifier/

@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Delivery Order”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “N44255”@ ProcurementInstrumentNumber/ Year/ “18”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “F”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “4016”@ ProcurementInstrumentDescription/ “Represented Contract”

@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Blanket Purchase Agreement”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “N44255”@ ProcurementInstrumentNumber/ Year/ “18”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “A”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “4036”@ ProcurementInstrumentDescription/ “Ordering Instrument”

@ ProcurementInstrumentOrigin/ “General Services Administration”@ ProcurementInstrumentVehicle/ “Schedule”@ NonDoDNumber/ “GS-35F-0265X”@ ProcurementInstrumentDescription/ “Ordering Instrument”


XML Sample

4.3.3 Solicitation NumberOn an award, the Solicitation Number is used to identify the Government’s original request for offers or quotations for the goods or services supplied by the contract.

Form Location

Form Block Number Block TitleOF 307 3 SOLICITATION NUMBERSF 26 18 Your bid on Solicitation NumberSF 33 3 SOLICITATION NUMBERSF 1442 1 SOLICITATION NUMBERSF 1447 4 SOLICITATION NUMBERSF 1449 5 SOLICITATION NUMBER

Sample Block

3. SOLICITATION NUMBER

N00183-16-T-0167SF 33, Block 3




<EnterpriseIdentifier>N44255</EnterpriseIdentifier><Year>18</Year><ProcurementInstrumentTypeCode>F</ProcurementInstrumentTypeCode><SerializedIdentifier>4016</SerializedIdentifier>



<ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Blanket Purchase Agreement</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>N44255</EnterpriseIdentifier><Year>18</Year><ProcurementInstrumentTypeCode>A</ProcurementInstrumentTypeCode><SerializedIdentifier>4036</SerializedIdentifier>

</ProcurementInstrumentNumber><ProcurementInstrumentDescription>Ordering Instrument</ProcurementInstrumentDescription>


<ProcurementInstrumentOrigin>General Services Administration</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Schedule</ProcurementInstrumentVehicle><NonDoDNumber>GS-35F-0265X</NonDoDNumber><ProcurementInstrumentDescription>Ordering Instrument</ProcurementInstrumentDescription>


Schema Location

The solicitation number is contained in an iteration of <ProcurementInstrumentIdentifier> that has a <ProcurementInstrumentDescription> of “Solicitation Number.”


@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Request for Quotation - Automated”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “N00183”@ ProcurementInstrumentNumber/ Year/ “16”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “T”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “0167”@ ProcurementInstrumentDescription/ “Solicitation Number”

XML Sample

4.4 AddressesThe information from the various address blocks on a form is used to populate the <ProcurementInstrumentAddresses> section of the schema. General information about the schema is provided here. Specific examples of types of addresses is provided in the following subsections.

Schema Location

While addresses can be located both at the header and line item levels, addresses on the forms appear at the header level.

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAddresses/Major Path – Line Item: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAddresses/


…<ProcurementInstrumentHeader> <ProcurementInstrumentIdentifier> <ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin> <ProcurementInstrumentVehicle>Request for Quotation - Automated</ProcurementInstrumentVehicle> <ProcurementInstrumentNumber> <EnterpriseIdentifier>N00183</EnterpriseIdentifier> <Year>16</Year> <ProcurementInstrumentTypeCode>T</ProcurementInstrumentTypeCode> <SerializedIdentifier>0167</SerializedIdentifier> </ProcurementInstrumentNumber> <ProcurementInstrumentDescription>Solicitation Number</ProcurementInstrumentDescription> </ProcurementInstrumentIdentifier> ….<ProcurementInstrumentHeader>…

Schema View


With the exception of Project Title and Location, all addresses covered by this section use the “AddressDetailType” data type, which is defined in the PDS schema. As seen in the schema view above, each one contains the following elements or sections:

<AddressDescription> or <AlternateAddressDescription>. These elements contain a description of the type of address. One or the other must be provided. Using the <AddressDescription> element limits the value to a specific list of options (Acceptance Location, Contract Administering Office, etc.). The <AlternateAddressDescription> element should only be used when the address is not one of the standard options.

<Address>. This section consists of the <OrganizationID> and <OrganizationNameAddress> sections. At least one of the elements or sections within <OrganizationID> must be provided. One of the following sections must be used to provide the details of an address: <FreeFormAddress>, <RealPropertyAddress>, or <USPostalAddress>. Examples of each of these options are provided in the sections for specific address types.

<Contact>. This section holds the details for one or more points of contact for the address.

<AcceptanceInspection>. This section provides instructions for how acceptance and inspection of good and services should be performed. It is provided with an inspection or acceptance address.

<BusinessClassification>. This section is provided with a contractor address. It consists of details about the type of business such as whether or not it is a small business, an educational institution, American Indian owned, etc.

The “AddressDetailType” is a very large structure. The following schema views have various elements expanded so that the lower level structures are visible.


Schema View: Organization ID


Schema View: Free Form Address


Schema View: Real Property Address


Schema View: US Postal Address


4.4.1 Construction ProjectThis example uses the <RealPropertyAddress> section for the address. The structure for Real Property Addresses comes from the DoD Business Enterprise Architecture (BEA).

Note: Although the current version of the BEA is 11.0, the PDS schema and validations are based on BEA 4.1.

Within the <RealPropertyAddress> section, there are three required Geographic Location Code (GLC) elements that can be determined using information provided on the General Services Administration (GSA) website:

<GLCCityCode> corresponds to the city in which the site is located. If the site does not have a city associated with it, the element should identify the closest city.

< GSAGLACountryPrimaryDivisionCode> corresponds to the country subdivision where the site is located. For US addresses, this would be the state.

<GSAGLACountrySubdivisionCode> corresponds to the county or county-equivalent where the site is located.

The address for this example does not have a street number. This can happen when a building is under construction and no concrete address has been defined. In this case, the optional <OrganizationCoordinates> section can be used to provide an exact location.

Form Location

Form Block Number Block TitleSF 252 5 PROJECT TITLE AND LOCATION

Sample Block

5. PROJECT TITLE AND LOCATION

WASTE WATER TREATMENT PLANTBOLSA AVEHUNTINGTON BEACH, CA 92647

City Code: 1660State Code: 006County Code: 059Latitude: 33.747792Longitude: -118.037423

DD SF 252, Block 5


Schema LocationMajor Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ConstructionProjectDetails/

@ ConstructionProjectTitle/ “WASTE WATER TREATMENT PLANT”@ ConstructionProjectAddress/ RealPropertyAddress/ StreetName/ “BOLSA”@ ConstructionProjectAddress/ RealPropertyAddress/ StreetTypeCode/ “AVE” @ ConstructionProjectAddress/ RealPropertyAddress/ GSAGLCCityCode/ “1660”@ ConstructionProjectAddress/ RealPropertyAddress/ GSAGLACountryPrimaryDivisionCode/ “006” @ ConstructionProjectAddress/ RealPropertyAddress/ GSAGLACountrySubdivisionCode/ “059”@ ConstructionProjectAddress/ RealPropertyAddress/ PostalZoneCode/ “92647”@ ConstructionProjectCoordinates/ Latitude/ “33.747792”@ ConstructionProjectCoordinates/ Longitude/ “-118.037423”

XML Sample



…<ConstructionProjectDetails>

<ConstructionProjectTitle>WASTE WATER TREATMENT PLANT</ConstructionProjectTitle><ConstructionProjectAddress>

<RealPropertyAddress><StreetName>BOLSA</StreetName ><StreetNumber>1660 </StreetNumber><StreetTypeCode>BCH</StreetTypeCode><GSAGLCCityCode>1660</GSAGLCCityCode> <GSAGLACountryPrimaryDivisionCode>

CAL</GSAGLACountryPrimaryDivisionCode> <GSAGLACountrySubdivisionCode>059</GSAGLACountrySubdivisionCode><CountryISOA3Code>USA</CountryISOA3Code><CountryISON3Code>840</CountryISON3Code><CountryName>United States of America (the)</CountryName><LocationDirectionsText>

CAMP ROBERTS MILITARY BASE</LocationDirectionsText>

<PostalZoneCode>92647-2099</PostalZoneCode> </RealPropertyAddress>

</ConstructionProjectAddress><ConstructionProjectCoordinates>

<Latitude>33.747792</Latitude><Longitude>-118.037423</Longitude>

</ConstructionProjectCoordinates> </ConstructionProjectDetails></ProcurementInstrumentHeader>…

4.4.2 Issued ByThis is the name and address of the office that issued the procurement document. The example uses the Free Form option for the address.

Form Location

Form Block Number Block TitleDD 1155 6 ISSUED BYOF 307 5 ISSUED BYSF 26 5 ISSUED BYSF 30 6 ISSUED BYSF 33 7 ISSUED BYSF 252 4a. DEPARTMENT OR AGENCY AND ADDRESS (Include ZIP Code)SF 1442 7 ISSUED BYSF 1447 7 ISSUED BYSF 1449 9 ISSUED BY

Sample Block6. ISSUED BY CODE S0530ADCMA BOEING HUNTINGTON BEACH5301 BOLSA BEACHHUNTINGTON BEACH, CA 92647

DD 1155, Block 6

Note: the code portion of the block contains the DoDAAC for the issuing office.

Schema LocationMajor Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAddresses/

@ AddressDescription/ “Contract Issuing Office”@ Address/ OrganizationID/ DoDAAC/ “S0530A”@ Address/ OrganizationNameAddress/ OrganizationName/ “DCMA BOEING HUNTINGTON BEACH”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “5301 BOLSA BEACH”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “HUNTINGTON BEACH, CA 92647


XML Sample

4.4.3 Administered ByThis is the name and address of the office that administers the procurement instrument when it differs from the issuing office. The example uses the Free Form option for the address.

Form Location

Form Block Number Block TitleDD 1155 7 ADMINISTERED BY (If other than 6)OF 307 6 ADMINISTERED BY (If other than Item 5)SF 26 6 ADMINISTERED BY (If other than Item 5)SF 30 7 ADMINISTERED BY (If other than 6)SF 33 24 ADMINISTERED BY (If other than 7)SF1442 26 ADMINISTERED BYSF 1447 12 ADMINISTERED BYSF 1449 16 ADMINISTERED BY

Sample Block7. ADMINISTERED BY (if other than 6) CODE W56JJGDLA LAND AND MARITIMELAND SUPPLY CHAIN ESOC BUYSATTN: VATPO BOX 3990COLUMBUS, OH 43218-3990

DD 1155, Block 7

The code portion of the block contains the DoDAAC for the contract administration office.

As stated above, the “Administered By” block can refer to the “Issued By” block if the addresses are the same.


…<ProcurementInstrumentAddresses>

<AddressDescription>Contract Issuing Office</AddressDescription><Address>

<OrganizationID> <DoDAAC>S0530A</DoDAAC>

</OrganizationID><OrganizationNameAddress> <OrganizationName>DCMA BOEING HUNTINGTON BEACH</OrganizationName>

<OrganizationAddress> <FreeFormAddress>

<AddressLine1>5301 BOLSA BEACH</AddressLine1><AddressLine2>HUNTINGTON BEACH, CA 92647</AddressLine2>

</FreeFormAddress></OrganizationAddress>

</OrganizationNameAddress></Address>

</ProcurementInstrumentAddresses>…


@ AddressDescription/ “Contract Administrative Office”@ Address/ OrganizationID/ DoDAAC/ “W56JJG”@ Address/ OrganizationNameAddress/ OrganizationName/ “DLA LAND AND MARITIME”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “LAND SUPPLY CHAIN ESOC BUYS”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “ATTN: VAT”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine3/ “PO BOX 3990”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine4/ “COLUMBUS, OH 43218-3990”

XML Sample

4.4.4 ContractorThis is the address of the contractor. The example uses the US Postal option for the address which is the address structure as defined by the United States Postal Service (USPS).

Form Location

Form Block Number Block TitleDD 1155 9 CONTRACTOR NAME AND ADDRESSOF 307 7, 9 NAME AND ADDRESS OF CONTRACTOR, UNIQUE ENTITY IDENTIFIER, TAXPAYER’S

IDENTIFICATION NUMBERSF 26 7 NAME AND ADDRESS OF CONTRACTORSF 30 8 NAME AND ADDRESS OF CONTRACTOR, CODE, and FACILITY CODESF 33 15 NAME AND ADDRESS OF OFFEROR, CODE, FACILITY, and TELEPHONE NUMBERSF 252 3 NAME OF ARCHITECT-ENGINEER, TELEPHONE NUMBER, ADDRESS OF ARCHITECT-ENGINEERSF 1442 14, 15 NAME AND ADDRESS OF OFFEROR, CODE, FACILITY CODE, and TELEPHONE NUMBERSF 1447 13 CONTRACTOR OFFEROR, CODE, FACILITY CODE, TELEPHONE NUMBER, and UNIQUE ENTITY

IDENTIFIERSF 1449 17 CONTRACTOR/OFFEROR, CODE, FACILITY CODE, and TELEPHONE NO.


<ProcurementDocument> <AwardInstrument> <ProcurementInstrumentHeader> … <ProcurementInstrumentAddresses> <AddressDescription>Contract Administrative Office</AddressDescription> <Address> <OrganizationID> <DoDAAC>W56JJG</DoDAAC> </OrganizationID> <OrganizationNameAddress> <OrganizationName>DLA LAND AND MARITIME</OrganizationName> <OrganizationAddress> <FreeFormAddress> <AddressLine1>LAND SUPPLY CHAIN ESOC BUYS</AddressLine1> <AddressLine2>ATTN: VAT</AddressLine2> <AddressLine3>PO BOX 3990</AddressLine3> <AddressLine4>COLUMBUS, OH 43218-3990</AddressLine4> </FreeFormAddress> </OrganizationAddress> </OrganizationNameAddress> </Address> </ProcurementInstrumentAddresses>

…

Sample Block

17a. CONTRACTOR/ OFFEROR CODE 42WK5 FACILITY CODE

US SUPPLY CORPORATION3421 THIS WAYCOLUMBUS, OH 43228-3805USA

TELEPHONE NO. (703) 427-8892SF 1449, Block 17a

Several forms contain additional blocks for a “CODE” and a “FACILITY CODE”. The “CODE” block contains a CAGE or some other code to identify the contractor. If the work covered by the order is to be performed at an address different from the address represented by the contractor code, then the “FACILITY CODE” block contains the CAGE code for the address where the work is performed.

When multiple facilities are involved, the codes for all facilities at which work is to be performed, including the contractor's code if work is performed at that address, may be included in Uniform Contract Format (UCF) Section B and the facility code block read “see schedule.” These multiple addresses are placed in the schema at the line item level.


@ AddressDescription/ “Contractor”@ Address/ OrganizationID/ CAGE/ “42WK5”@ Address/ OrganizationNameAddress/ OrganizationName/ “US SUPPLY CORPORATION”@ Address/ OrganizationNameAddress/ OrganizationAddress/ USPostalAddress/ Recipient/ “US SUPPLY CORPORATION”@ Address/ OrganizationNameAddress/ OrganizationAddress/ USPostalAddress/ DeliveryAddressLine/ “3421 THIS WAY”@ Address/ OrganizationNameAddress/ OrganizationAddress/ USPostalAddress/ City/ “COLUMBUS”@ Address/ OrganizationNameAddress/ OrganizationAddress/ USPostalAddress/ StateOrProvince/ “OH”@ Address/ OrganizationNameAddress/ OrganizationAddress/ USPostalAddress/ PostalCode/ USZipCode/ “43228”@ Address/ OrganizationNameAddress/ OrganizationAddress/ USPostalAddress/ PostalCode/ USZipCodeExtension/ “3805”@ Address/ OrganizationNameAddress/ OrganizationAddress/ USPostalAddress/ Country/ “United States of America (the)”@ Contact/ Name/ “US SUPPLY CORPORATION”@ Contact/ ContactMethod/ “Telephone”@ Contact/ MethodValue/ “(703) 427-8892”


XML Sample



<AddressDescription>Contractor</AddressDescription><Address>

<OrganizationID><CAGE>42WK5</CAGE>

</OrganizationID><OrganizationNameAddress>

<OrganizationName>US SUPPLY CORPORATION</OrganizationName><OrganizationAddress>

<USPostalAddress><Recipient>US SUPPLY CORPORATION</Recipient><DeliveryAddressLine>3421 THIS WAY</DeliveryAddressLine><City>COLUMBUS</City><StateOrProvince>OH</StateOrProvince><PostalCode>

<USZipCode>43288</USZipCode><USZipCodeExtension>3805</USZipCodeExtension>

</PostalCode><Country>United States of America (the)</Country>

</USPostalAddress></OrganizationAddress>

</OrganizationNameAddress></Address><Contact>

<Name>US SUPPLY CORPORATION</Name><ContactMethod>

<MethodDescription>Telephone</MethodDescription><MethodValue>(703) 427-8892</MethodValue>

</ContactMethod></Contact>


4.4.4.1 Business Classification

The <BusinessClassification> section in the PDS contains many different elements that describe the contractor’s business. The required <OrganizationType> element classifies a business as either “Small” or “Other than Small”. The <BusinessType> section contains contract categories such as federally recognized organizations, minority owned, Limited Liability Corporation, and socio-economic qualified organizations and businesses among others.

Form Location

Form Block Number Block TitleDD 1155 11 X IF BUSINESS IS

Sample Block

11. X IF BUSINESS IS

X SMALLSMALL DISADVANTAGED

X WOMEN-OWNEDSF 1449, Block 10

Schema Location

The schema follows the structure of the Federal Procurement Data System - Next Generation (FPDS-NG) which is the authoritative source for Government-wide contract award data. Two elements are required by the schema but are not on the forms. These are the <IRSDesignation> and <ProfitStructure> elements.

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAddresses/ BusinessClassification/

@ OrganizationType/ “Small”@ BusinessType/ OrganizationCategory/ BusinessOrOrganization/ SocioEconomic/ SocioEconomicGroup/ “Women Owned Business”

XML Sample



<AddressDescription>Contractor</AddressDescription>…<BusinessClassification>

<OrganizationType>Small</OrganizationType><BusinessType>

<OrganizationCategory><BusinessOrOrganization>

<IRSDesignation>International Organization<IRSDesignation><ProfitStructure>For-Profit Organization</ProfitStructure><SocioEconomic>

<SocioEconomicGroup>Women Owned Business</SocioEconomicGroup></SocioEconomic>

</BusinessOrOrganization></OrganizationCategory>

</BusinessType></BusinessClassification>


Schema View


4.4.5 Mail Invoices to Address Shown InThis is the address where invoices should be submitted. The example uses the Free Form option for the address.

Form Location

Form Block Number Block TitleDD 1155 13 MAIL INVOICES TO THE ADDRESS IN BLOCKOF 307 10 SUBMIT INVOICES (4 copies unless otherwise specified) TO

ITEM 5 ITEM 6 ITEM 8 OTHER (Specify)SF 26 10 SUBMIT INVOICES (4 copies unless otherwise specified) TO THE ADDRESS SHOWN INSF 33 23 SUBMIT INVOICES TO ADDRESS SHOWN IN (4 copies unless otherwise specified) ITEMSF 1442 24 SUBMIT INVOICES TO ADDRESS SHOWN IN (4 copies unless otherwise specified) SF 1447 14 SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCKSF 1449 18b SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

Sample Block

When the address itself is not contained in the block, it contains a reference to the block containing the address or 'See Schedule'. See example for “Payment Will Be Made By” below showing how to enter the paying office.

13. MAIL INVOICES TO THE ADDRESSES IN BLOCK

See Block 15

DD 1155, Block 13

15. PAYMENT WILL BE MADE BY CODE HQ0104

DFAS-COLUMBUS CENTERMARINE CORPSPO BOX 123123COLUMBUS, OH 12345-1234

DD 1155, Block 15


@ AddressDescription/ “Party to receive Invoice”@ Address/ OrganizationID/ DoDAAC/ “HQ0104”@ Address/ OrganizationNameAddress/ OrganizationName/ “DFAS-COLUMBUS CENTER”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “MARINE CORP”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “PO BOX 123123”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine3/ “COLUMBUS, OH 12345-1234”


XML Sample

4.4.6 Payment Will Be Made ByThis address contains the DoDAAC, name, and address of the office that makes the payments. The example uses the Free Form option for the address.

Form Location

Form Block Number Block TitleDD 1155 15 PAYMENT WILL BE MADE BYOF 307 8 PAYMENT WILL BE MADE BYSF 26 12 PAYMENT WILL BE MADE BYSF 33 25 PAYMENT WILL BE MADE BYSF 1442 27 PAYMENT WILL BE MADE BYSF 1447 14 PAYMENT WILL BE MADE BYSF 1449 18 PAYMENT WILL BE MADE BY

Sample Block

15. PAYMENT WILL BE MADE BY CODE: SL1702DEF FIN AND ACCOUNTING SVCBSMCOLUMBUS, OH 43333-3333 USA

DD 1155, Block 15


<ProcurementDocument> <AwardInstrument> <ProcurementInstrumentHeader> … <ProcurementInstrumentAddresses> <AddressDescription>Party to receive Invoice</AddressDescription> <Address> <OrganizationID> <DoDAAC>HQ0104</DoDAAC> </OrganizationID> <OrganizationNameAddress> <OrganizationName>DFAS-COLUMBUS CENTER</OrganizationName> <OrganizationAddress> <FreeFormAddress> <AddressLine1>MARINE CORP</AddressLine1> <AddressLine2>PO BOX 123123</AddressLine2> <AddressLine3>COLUMBUS, OH 12345-1234</AddressLine3> </FreeFormAddress> </OrganizationAddress> </OrganizationNameAddress> </Address> </ProcurementInstrumentAddresses> …


@ AddressDescription/ “Paying Office”@ Address/ OrganizationID/ DoDAAC/ “SL1702”@ Address/ OrganizationNameAddress/ OrganizationName/ “DEF FIN AND ACCOUNTING SVC”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “BSM”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “COLUMBUS, OH 43333-3333”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine3/ “USA”

XML Sample

4.4.7 Ship To/Mark ForThis block contains a ship-to address and, if needed, a mark-for address that applies to the entire document. If there are multiple ship-to or mark for addresses, the block reads, “See Schedule” and the addresses are provided on the line items. In this case, the information is not in the <Addresses> section for the line item; it is in the <Delivery> section.

Sometimes the “Ship To/Mark For” block contains additional information such as:

Criticality – a code assigned by the contracting officer that corresponds to the degree of importance to the Government of the supplies or services provided by the contract. See FARS 42.1104 - Surveillance requirements.

Pre-Award Survey (PAS) – an evaluation of a prospective contractor’s capability to perform a proposed contract.


<ProcurementDocument> <AwardInstrument> <ProcurementInstrumentHeader> … <ProcurementInstrumentAddresses> <AddressDescription>Paying Office</AddressDescription> <Address> <OrganizationID> <DoDAAC>SL1702</DoDAAC> </OrganizationID> <OrganizationNameAddress> <OrganizationName>DEF FIN AND ACCOUNTING SVC</OrganizationName> <OrganizationAddress> <FreeFormAddress> <AddressLine1>BSM</AddressLine1> <AddressLine2>COLUMBUS, OH 43333-3333</AddressLine2> <AddressLine3>USA</AddressLine3> </FreeFormAddress> </OrganizationAddress> </OrganizationNameAddress> </Address> </ProcurementInstrumentAddresses> …

These values are captured in the <ReferenceNumber> section of the schema.

The example uses the Free Form option for the address.

Form Location

Form Block Number Block TitleDD 1155 14 SHIP TOSF 26 11 SHIP TO/MARK FORSF 1449 15 DELIVER TO

Sample Block

11. SHIP TO/MARK FORSHIP TO:DEFENSE LOGISTICS AGENCYDISTRIBUTION SAN JOAQUIN25600 S CHRISMAN ROADTRACY, CA 95304

CODE: W62G2T

MARK FOR:DLA LAND AND MARITIMEATTN: JOHN DAVISPO BOX 326COLUMBUS, OH 43218-3990

CODE: HQ0337

Criticality: C PAS: None

SF 26, Block 11, one address

14. SHIP TO CODE:

SEE SCHEDULE, DO NOT SHIP TO ADDRESSES ON THIS PAGE

SF 26, Block 11, multiple addresses



@ AddressDescription/ “Ship To”@ Address/ OrganizationID/ DoDAAC/ “W62G2T”@ Address/ OrganizationNameAddress/ OrganizationName/ “DEFENSE LOGISTICS AGENCY”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “DISTRIBUTION SAN JOAQUIN”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “25600 S CHRISMAN ROAD”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine3/ “TRACY, CA 95304”

@ AddressDescription/ “Mark for Party”@ Address/ OrganizationID/ DoDAAC/ “HQ0337”@ Address/ OrganizationNameAddress/ OrganizationName/ “DLA LAND AND MARITIME”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “ATTN: JOHN DAVIS”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “PO BOX 326”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine3/ “COLUMBUS, OH 43218-3990”

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/

@ ReferenceNumber/ ReferenceDescription/ “Surveillance Criticality Designator”@ ReferenceNumber/ ReferenceValue/ “C”

@ ReferenceNumber/ ReferenceDescription/ “Pre-Award Survey”@ ReferenceNumber/ ReferenceValue/ “None”


XML Sample


<ProcurementDocument><AwardInstrument>

<ProcurementInstrumentHeader>…

<ProcurementInstrumentAddresses> <AddressDescription>Ship To</AddressDescription> <Address> <OrganizationID> <DoDAAC>W62G2T</DoDAAC> </OrganizationID> <OrganizationNameAddress> <OrganizationName>DEFENSE LOGISTICS AGENCY</OrganizationName> <OrganizationAddress> <FreeFormAddress> <AddressLine1>DISTRIBUTION SAN JOAQUIN</AddressLine1> <AddressLine2>25600 S CHRISMAN ROAD</AddressLine2> <AddressLine3>TRACY, CA 95304</AddressLine3> </FreeFormAddress> </OrganizationAddress> </OrganizationNameAddress> </Address> </ProcurementInstrumentAddresses> <ProcurementInstrumentAddresses> <AddressDescription>Mark for Party</AddressDescription> <Address> <OrganizationID> <DoDAAC>W62G2T</DoDAAC> </OrganizationID> <OrganizationNameAddress> <OrganizationName>DLA LAND AND MARITIME</OrganizationName> <OrganizationAddress> <FreeFormAddress> <AddressLine1>ATTN: JOHN DAVIS</AddressLine1> <AddressLine2>PO BOX 326</AddressLine2> <AddressLine3>COLUMBUS, OH 43218-3990<AddressLine3> </FreeFormAddress>

</OrganizationAddress> </OrganizationNameAddress> </Address> </ProcurementInstrumentAddresses>

…<ReferenceNumber>

<ReferenceDescription>Surveillance Criticality Designator</ReferenceDescription> <ReferenceValue>C</ReferenceValue> <ReferenceSection>A</ReferenceSection> </ReferenceNumber>

<ReferenceNumber> <ReferenceDescription>Pre-Award Survey</ReferenceDescription> <ReferenceValue>None</ReferenceValue> <ReferenceSection>A</ReferenceSection> </ReferenceNumber>

…

Schema View

The picture below is the Reference Number portion of the schema. The picture for the addresses is located at the beginning of the “Addresses” section of this document.

4.4.8 RemittanceThe Remittance Address is the address where the contractor’s payments should be sent. Many times, this address is not needed because it is the same as the Contractor Address.



Form Location

Form Block Number Block TitleSF 33 15C. CHECK IF REMITTANCE ADDRESS IS DIFFERENT FROM ABOVESF 1442 16 REMITTANCE ADDRESS (Include only if different than Item 14.)SF 1447 13 CHECK IF REMITTANCE IS DIFFERENTSF 1449 17b. CHECK IF REMITTANCE IS DIFFERENT

Sample Block

16. REMITTANCE ADDRESS (Include only if different than Item 14.)

LMN ConstructionAccounts Receivable P.O. Box 958381 Tracy, CA 95304

CODE: 436786214

SF 1442, Block 16

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAddresses/

@ AddressDescription/ “Remit To”@ Address/ OrganizationID/ DunsNumber/ “436786214”@ Address/ OrganizationNameAddress/ OrganizationName/ “LMN Construction”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “Accounts Receivable”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “P.O. Box 958381”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine3/ “Tracy, CA 95304”

XML Sample



<AddressDescription>Remit To</AddressDescription><Address>

<OrganizationID><DunsNumber>436786214</DunsNumber>


<OrganizationName>LMN Construction</OrganizationName><OrganizationAddress>

<FreeFormAddress><AddressLine1>Accounts Receivable</AddressLine1><AddressLine2>P.O. Box 958381</AddressLine2><AddressLine3>Tracy, CA 95304</AddressLine3>




4.4.9 Party to Receive OfferThis is the address where the solicitation offer is to be sent. Many times, this address is the same as the Issuing Office.


Form Location

Form Block Number Block TitleSF 33 8 ADDRESS OFFER TO (If other than 7)SF 1442 8 ADDRESS OFFER TO

Sample Block

16. ADDRESS OFFER TO (If other than item 7)

NAVAL SEA SYSTEMS COMMAND (HQ)1333 ISAAC HULL AVE SEWASHINGTON NAVY YARD DC 20376-2020

CODE: N00024

SF 33, Block 8

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAddresses/

@ AddressDescription/ “Party to receive Proposal”@ Address/ OrganizationID/ DoDAAC/ “N00024”@ Address/ OrganizationNameAddress/ OrganizationName/ “NAVAL SEA SYSTEMS COMMAND (HQ)”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine1/ “1333 ISAAC HULL AVE SE”@ Address/ OrganizationNameAddress/ OrganizationAddress/ FreeFormAddress/ AddressLine2/ “WASHINGTON NAVY YARD DC 20376-2020”

XML Sample



<AddressDescription>Party to receive Proposal</AddressDescription><Address>

<OrganizationID><DoDAAC>N00024</DoDAAC>


<OrganizationName>NAVAL SEA SYSTEMS COMMAND (HQ)</OrganizationName><OrganizationAddress>

<FreeFormAddress><AddressLine1>1333 ISAAC HULL AVE SE </AddressLine1><AddressLine2> WASHINGTON NAVY YARD DC 20376-2020</AddressLine2>




4.5 Contingency ContractContingency contracts are used to procure supplies and services in support of contingency operations. Contingency operations include operations such as domestic and overseas armed conflict, stability operations, and disaster relief efforts. Although there is not a block on the forms for identifying whether or not a contract is a contingency contract, there is a required <ContingencyContract> element in the XML schema which must be populated with “true” or “false”.

Schema LocationProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ ContingencyContract/ “true”

XML Sample


… <BasicInformation>

<ContingencyContract>true</ContingencyContract>…

</BasicInformation>…

Schema View


4.6 Signature Blocks The signature block includes information about the person signing the document, their signature, and the date of that signature.

4.6.1 Offeror The offeror is the person who represents the company providing the offer for the goods/services described in the solicitation. The signature block for the offeror includes their basic information, their signature, and the date of that signature. Currently, SF 33 and SF 1442 are the only relevant forms because they are the only ones that carry offer signatures on award documents. Once the PDS can be used to submit solicitations, more forms will be relevant and will be included in this section.

Form Location

Form Block Number Block TitleSF 33 16, 18 NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER, OFFER DATESF 1442 20 NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER, OFFER DATE

Sample Block

16 NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER (Type or print)Henry Smith, Sales Associate

17. SIGNATURE 18. OFFER DATE2014 JAN 16

SF 33, Blocks 16, 17, and 18Schema LocationMajor Path:

ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ OfferSignature

@ SignatureDate/ “20140106”@ SigneeDetails/ TitleOrFunction/ “Sales Associate”@ SigneeDetails/ Name/ “Henry Smith”@ SigneeDetails/ ContactMethod/ Method Description/ “Telephone”@ SigneeDetails/ ContactMethod/ Method Value/ “703-327-1234”

Note: Although Contact Method is not found on most of the forms, it is a required element in the PDS Schema and must be provided.


XML Sample

Schema View

4.6.2 Contractor Representative The signature block for the contractor representative includes information about the person who is authorized to act on behalf of the contractor, their signature, and the date of their signature.


…<SolicitationOfferInformation>

<OfferSignature><SignatureDate>20140106</SignatureDate><SigneeDetails>

<TitleOrFunction>Sales Associate</TitleOrFunction><Name>Henry Smith</Name><ContactMethod>

<MethodDescription>Telephone</MethodDescription><MethodValue>703-327-1234</MethodValue>

</ContactMethod></SigneeDetails>

</OfferSignature></SolicitationOfferInformation>…

Form Location

Form Block Number Block TitleDD 428 13 SIGNATURE OF CONTRACTOR’S REPRESENTATIVE, DATE SIGNEDDD 1155 16 TYPED NAME AND TITLE and DATE SIGNEDOF 307 14 NAME OF SIGNER, TITLE OF SIGNER, and DATESF 26 19 NAME AND TITLE OF SIGNER, DATE SIGNEDSF 30 15 NAME AND TITLE OF SIGNER, DATE SIGNEDSF 252 11 NAME AND TITLES of ARCHITECT-ENGINEER OR OTHER PROFESSIONAL SERVICES CONTRACTORSF 1442 30 NAME AND TITLE OF CONTRACTOR OR PERSON AUTHORIZED TO SIGN, DATESF 1447 27 NAME AND TITLE OF SIGNER, DATE SIGNEDSF 1449 30 NAME AND TITLE OF SIGNER, DATE SIGNED

Sample Block

19A. NAME AND TITLE OF SIGNER (Type or Print)

Jane DoeProject Manager

19B. NAME OF CONTRACTOR 19c. DATE SIGNEDBY _______________________________________ 2015 07 07

(Signature of person authorized to sign)SF 26, Block 19

Schema LocationMajor Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentDates/ ContractorRepresentative/

@ SignatureDate/ “2015-07-07”@ SigneeDetails/ TitleOrFunction/ “Project Manager”@ SigneeDetails/ Name/ “Jane Doe”@ SigneeDetails/ ContactMethod/ MethodDescription/ “Telephone”@ SigneeDetails/ ContactMethod/ MethodValue/ “703-327-1234”

Note: Although Contact Method is not found on most of the forms, it is a required element in the PDS Schema and at least one must be provided.


XML Sample

Schema View


…<ProcurementInstrumentDates>

<ContractorRepresentative><SignatureDate>2015-07-07</SignatureDate><SigneeDetails>

<TitleOrFunction>Project Manager</TitleOrFunction><Name>Jane Doe</Name><ContactMethod>



</ContractorRepresentative></ProcurementInstrumentDates>…

4.6.3 Contracting OfficerThe signature block for the contracting officer includes information about the person who is designated to administer the contract on behalf of the Government, their signature, and the date of their signature.

Form Location

Form Block Number Block TitleDD 428 12 AUTHORIZING OFFICIALDD 1155 24 UNITED STATES OF AMERICAOF 307 15 AWARDSF 26 20 NAME OF CONTRACTING OFFICER, DATE SIGNEDSF 30 16 NAME AND TITLE OF CONTRACTING OFFICER, DATE SIGNEDSF 33 26,28 NAME OF CONTRACTING OFFICER, AWARD DATESF 252 12 UNITED STATES OF AMERICASF 1442 31 NAME OF CONTRACTING OFFICER, DATESF 1447 28 NAME OF CONTRACTING OFFICER, DATE SIGNEDSF 1449 31 NAME OF CONTRACTING OFFICER, DATE SIGNED

Sample Block

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print)John DoeContracting Officer

31c. DATE SIGNED2015 07 07

SF 1449, Block 13

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentDates/ ContractingOfficer/

@ SignatureDate/ “2015-07-07”@ SigneeDetails/ TitleOrFunction/ “Contracting Officer”@ SigneeDetails/ Name/ “John Doe”@ SigneeDetails/ ContactMethod/ MethodDescription/ “Email”@ SigneeDetails/ ContactMethod/ MethodValue/ “[email protected]”

Note: Although Contact Method is not found on most of the forms, it is a required element in the PDS Schema and at least one must be provided.

XML Sample


…<ProcurementInstrumentDates>

<ContractingOfficer><SignatureDate>2015-07-07</SignatureDate><SigneeDetails>

<TitleOrFunction>Contracting Officer</TitleOrFunction><Name>John Doe</Name><ContactMethod>

<MethodDescription>Email</MethodDescription><MethodValue>[email protected] </MethodValue >


</ContractingOfficer></ProcurementInstrumentDates>…

mailto:[email protected]%3C/MethodValue

Schema View

4.7 DatesDate: In the XML document, all dates must be specified in the ‘CCYY-MM-DD’ format unless otherwise specified 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.

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.

4.7.1 Effective DateThe effective date is the date that the contract or contract modification goes into effect. The structure of the data on the forms is the four position numeric year, three position alpha month, and two position numeric day (YYYYMMMDD).


Form Location

Form Block Number Block TitleDD 1155 3 DATE OF ORDER/CALLOF 307 2 EFFECTIVE DATESF 26 3 EFFECTIVE DATESF 30 3 EFFECTIVE DATESF 252 2 DATE OF CONTRACTSF 1447 3 AWARD/EFFECTIVE DATESF1449 3 AWARD/EFFECTIVE DATE

Sample Block

3. DATE OF ORDER/CALL (YYYYMMMDD)

2014 JAN 16SF 1155, Block 3

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentDates/ ProcurementInstrumentEffectiveDate/ “2014-01-16”

XML Sample


<AwardInstrument><ProcurementInstrumentHeader>

…<ProcurementInstrumentDates> <ProcurementInstrumentEffectiveDate>2014-01-16</ProcurementInstrumentEffectiveDate>

</ProcurementInstrumentDates>

…


</AwardInstrument>

Schema View

4.7.2 Delivery DatesThe <DeliveryDates> section contains dates or date ranges that relate to a delivery. If the delivery information varies by line, it is captured at the line (schedule). Each delivery date includes a delivery description. Possible descriptions include:

Delivery AfterDelivery BeforeDelivery CycleDelivery Estimated ByDelivery MonthDelivery On Or BeforeDelivery PeriodDelivery Requested ByDelivery Required OnDelivery Week Starting

Form Location

Form Block Number Block TitleDD 1155 10 DELIVER TO FOB POINT BY/ SCHEDULE OF SUPPLIES/SERVICES


Sample Block

10. DELIVER TO FOB POINT BY (Date)(YYYYMMDD)

2015 DEC 14SF 1155, Block 10

Schema Location

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ DeliveryDetails/ DeliveryDates/Major Path – Line Item: ProcurementDocument/AwardInstrument/ContractLineItems/LineItems/Delivery/ItemDeliveryDates

@ DeliveryDescription/ “Delivery Before”@ DeliveryDate/ DateElement/ “2015-12-14”

XML Sample


…<DeliveryDetails>

<DeliveryDates><DeliveryDescription>Delivery Before</DeliveryDescription><DeliveryDate>

<DateElement>2015-12-14</DateElement></DeliveryDate>

</DeliveryDates></DeliveryDetails>…

Schema View

4.7.3 Period of PerformanceThe Period of Performance is the timeframe allowed or required for performance of the work as laid out in the contract to be completed.

Form Location

The Period of Performance is not located on any of the forms. It is specified on the lines in the schedule.


Sample Block

This is an example of how the Period of Performance may be provided in text on a contract line item.

SF

1449, Section B

Schema Location

If the Period of Performance is the same for all the line items on a contract, it can be mapped at the header level.

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentDates/ ProcurementInstrumentPeriods/

@ PeriodDescription/ “Period of Performance”@ StartDate/ “2015-01-15”@ EndDate/ “2016-01-15”

If the Period of Performance varies by line item, it must be mapped at the line item.

Major Path – Line Item: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ LineItemDates/

@ LineItemDateDescription/ “Period of Performance”@ PeriodStart/DateElement/ “2015-01-15”@ PeriodSEnd/DateElement/ “2016-01-15”

XML Sample – Header


<ProcurementInstrumentHeader>…<ProcurementInstrumentDates>

<ProcurementInstrumentPeriods><PeriodDescription>Period of Performance</PeriodDescription><StartDate>2015-01-15</StartDate><EndDate>2016-01-15</EndDate>

</ProcurementInstrumentPeriods></ProcurementInstrumentDates>…


ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT0001 1 Lot $504,203.78 $504,203.78

LaborFFPNon-Personal Services, Firm-Fixed Price. The contractor shall perform all requirements in the attached Performance Work Statement (PWS).

Period of Performance (PoP) is January 1, 2015 through January 1, 2016.

XML Sample – Line Item

Schema View - Header


<LineItems>…<LineItemDates>

<LineItemDateDescription>Period of Performance</LineItemDateDescription><LineItemPeriod>

<PeriodStart><DateElement>2015-01-15</DataElement>

</PeriodStart><PeriodEnd>

<DateElement>2016-01-15</DataElement></PeriodEnd>

</LineItemPeriod ></LineItemDates>…

</LineItems>

Schema View – Line Item

4.8 Solicitation/Offer InformationThis section covers form blocks that hold information about the solicitation.

4.8.1 Acquisition InformationThis block is used for indicating whether the solicitation is a) unrestricted or b) has some portion of the contract earmarked for a small business. If the solicitation has a set aside, the block provides the percentage that is set aside and the type of company it is set aside for.

In addition to the set aside information, the following elements are also contained in the block:

<NAICSCode> - the North American Industry Classification System (NAICS) code is the standard used by Federal statistical agencies in classifying business establishments for the purpose of collecting, analyzing, and publishing statistical data related to the U.S. business economy.

<SizeStandard> – the threshold of employees or income that the offeror/bidder must meet to respond to the solicitation.

Form Location

Form Block Number Block TitleSF 1447 8 THIS ACQUISITION ISSF 1449 10 THIS ACQUISITION IS


Sample Block

10. THIS ACQUISITION IS UNRESTRICTED OR X SET ASIDE: _25_% FOR

SMALL BUSINESS WOMEN-OWNED SMALL BUSINESS (WOSS) ELIGIBLE UNDER THE WOMEN-OWNED SMALL BUSINESS PROGRAMHUBZONE SMALL BUSINESS

NAICS: 336411

SERVICE-DISABLED VETERAN-OWNED SMALL BUSINESS

EDWOSB SIZE STANDARD: 7M

X

8 (A)SF 1449, Block 10

Schema Location

The data from this block is provided in the <SolicitationOfferInformation> section of the schema. The percentage of the contract that is set aside for small business and the type of company it is set aside for is contained in the <SetAsideDetails> subsection. If the solicitation is unrestricted, the <SetAsideDetails> subsection should not be included.

The enumeration list for the <SmallBusinessType> element contains values that correspond to each of the small business types in contained in the block. In this case, the value is “Service-Disabled Veteran-Owned Small Business”.

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/

@ NAICSCode/ “336411”@ SizeStandard/ AnnualReceipts/ “7000000”@ SetAsideDetails/ SetAsidePercent/ “25”@ SetAsideDetails/ SmallBusinessType/ “Service-Disabled Veteran-Owned Small Business”

XML Sample


<ProcurementInstrumentHeader>…<BasicInformation>


<NAICSCode>336411</NAICSCode><SizeStandard>

<AnnualReceipts>7000000</AnnualReceipts><SizeStandard><SetAsideDetails>

<SetAsidePercent>25</SetAsidePercent><SmallBusinessType>Service-Disabled Veteran-Owned Small Business</SmallBusinessType>

</SetAsideDetails></SolicitationOfferInformation>



Schema View


4.8.2 Type of SolicitationThis block indicates whether the type of solicitation is a Request for Quote (RFQ), an Invitation for Bid (IFB), or a Request for Proposal (RFP).

Form Location

Form Block Number Block TitleSF 33 4 TYPE OF SOLICITATIONSF 1442 2 TYPE OF SOLICITATIONSF 1447 5 SOLICITATION TYPESF 1449 14 METHOD OF SOLICITATION

Sample Block

14. METHOD OF SOLICITATIONRFQ IFB X RFP

SF 1449, Block 14

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ SolicitationType/ “Request for Proposal”

XML Sample




<SolicitationType>Request for Proposal</SolicitationType></SolicitationOfferInformation>



Schema View

4.8.3 Solicitation Issue DateForm Location

Form Block Number Block TitleSF 33 5 DATE ISSUED SF 1442 3 DATE ISSUEDSF 1447 6 SOLICITATION ISSUE DATESF 1449 6 SOLICITATION ISSUE DATE

Sample Block

6. SOLICITATION ISSUE DATE

2016 JAN 17SF 1449, Block 6

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ SolicitationIssuedDate/ “2016-01-17”


XML Sample

Schema View

4.8.4 Offer Delivery InformationForm Location

Form Block Number Block TitleSF 33 9 Sealed Offers in original….SF 1442 13a. Sealed offers in original…SF 1449 8 OFFER DUE DATE

Sample Block

9. Sealed offers in original and 3 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if hand carried in the depository location in Alexandria, VA until 2:00 PM EST, July 25, 2016.

SF 33, Block 9




<SolicitationIssuedDate>2016-01-17</SolicitationIssuedDate></SolicitationOfferInformation>



Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ OfferDelivery

@ SealedCopies/ “3”@ Depository Location/ “Alexandria, VA”@ RequiredBefore/ DateElement/ “2016-07-25”@ RequiredBefore/ TimeElement/ TimeElement/ “14:00:00”@ RequiredBefore/ TimeElement/ TimeZone/ “Eastern Standard Time”

XML Sample

Schema View


…<BasicInformation>


<SealedCopies>3</SealedCopies><DepositoryLocation>Alexandria, VA</DepositoryLocation><RequiredBefore>

<DateElement>2016-07-25</DateElement><TimeElement>

<TimeElement>14:00:00</TimeElement><TimeZone>Eastern Standard Time</TimeZone>

</TimeElement></RequiredBefore>

</SolicitationOfferInformation></BasicInformation>…

4.8.5 Solicitation Acceptance Calendar DaysIf the Government accepts the offer/bid within the number of days specified in this block, the offeror/bidder agrees to furnish any or all items in accordance with the price set, the designated delivery point(s), and the stated schedule. If not provided by the offeror/bidder, 60 days is the default.

Form Location

Form Block Number Block TitleSF 33 12 In compliance with the above, the undersigned agrees,…SF 1442 13d. Offers providing less than…SF 1447 11 IF OFFER IS ACCEPTED BY THE GOVERNMENT WITHIN

Sample Block

11. IF OFFER IS ACCEPTED BY THE GOVERNMENT WITHIN ____100____ CALENDAR DAYS (60 CALENDAR DAYS UNLESS OFFEROR INSERTS A DIFFERENT PERIOD) FROM THE DATE SET FORTH IN BLOCK 9 ABOVE, THE CONTRACTOR AGREES TO HOLD ITS OFFERED PRICES FIRM FOR THE ITEMS SOLICITED HEREIN AND TO ACCEPT ANY RESULTING CONTRACT SUBJECT TO THE TERMS AND CONDITIONS STATED HEREIN

SF 1447, Block 11

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ AcceptWithinDays/ “100”

XML Sample


<AwardInstrument> <ProcurementInstrumentHeader>


<SolicitationOfferInformation> <AcceptWithinDays>100</AcceptWithinDays>

</ SolicitationOfferInformation ></BasicInformation>

</ProcurementInstrumentHeader></AwardInstrument>

Schema View


4.8.6 Solicitation ContactThis block contains the contact information for the person to call if more information about the solicitation is needed.

Form Location

Form Block Number Block TitleSF 33 10 FOR INFORMATION CALL:SF 1442 9 FOR INFORMATION CALL:SF 1449 7 FOR SOLICITATION INFORMATION CALL:

Sample Block

10. FOR INFORMATION

CALL:

A. NAME B. TELEPHONE NUMBER (no collect calls) C. E-MAIL ADDRESS

Joyce BrownAREA CODE

761NUMBER876-3234

EXTENSIONX6700 [email protected]

SF 33, Block 10

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ SolicitationContact/

@ Name/ “John Brown”

@ ContactMethod/ MethodDescription/ “Telephone”@ ContactMethod/ MethodValue/ “571-876-3234 x6700”

@ ContactMethod/ MethodDescription/ “Email”@ ContactMethod/ MethodValue/ “[email protected]”

XML Sample



<SolicitationContact><Name>Joyce Brown</Name><ContactMethod>


</ContactMethod><ContactMethod>

<MethodDescription>Email</MethodDescription><MethodValue>[email protected]</MethodValue>

</ContactMethod></SolicitationContact>

</SolicitationOfferInformation>…

Schema View

4.8.7 Acknowledgement of AmendmentsForm Location

Form Block Number Block TitleSF 33 14 ACKNOWLEDGEMENT OF AMENDMENTS SF 1442 19 ACKNOWLEDGEMENT OF AMENDMENTS SF 1447 26 AWARD OF CONTRACTSF 1449 29 AWARD OF CONTRACT:

Sample Block

14. ACKNOWLEDGEMENT OF AMENDMENTS (The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

AMENDMENT NO. DATE AMENDMENT NO. DATE0001 2016-07-260002 2016-08-31

SF 33, Block 14


Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ AcknowledgedAmendments/

@ AmendmentNumber/ “0001”@ AmendmentDate/ “2016-07-26”

@ AmendmentNumber/ “0002”@ AmendmentDate/ “2016-08-31”

XML Sample



<AcknowledgedAmendments><AmendmentNumber>0001</AmendmentNumber><AmendmentNDate>2016-07-26</AmendmentDateNumber>

</AcknowledgedAmendments><AcknowledgedAmendments>

<AmendmentNumber>0002</AmendmentNumber><AmendmentNDate>2016-08-31</AmendmentDateNumber>

</AcknowledgedAmendments></SolicitationOfferInformation>…

Schema View

4.8.8 Delivery Lead TimeThe <DeliveryLeadTime> section of the schema provides information about when various milestones should take place in relation to the occurrence of a certain event.

Form Location

Form Block Number Block TitleSF 1442 11 The contractor shall begin performance within…

Sample Block

11. The contractor shall begin performance within _7_ calendar days and complete it within _ 21 _ calendar days after receiving award notice to proceed. This performance period is mandatory negotiable (See FAR Clause 52.211-10 ).

SF 1442, Block 11


Schema Location

Major Path: ProcurementDocument/AwardInstrument/ProcurementInstrumentHeader/DeliveryDetails/DeliveryLeadTime

@ LeadTimeDescription/ “From date of lead time event to beginning of performance”@ DeliveryLeadTime/ DurationUnit/ “Calendar Days”@ DeliveryLeadTime/ DurationValue/ “7”@ LeadTimeEvent/ “Date of Award Receipt”@ PerformancePeriodFirmness/ “Mandatory”@ PerformancePeriodComments/ “FAR Clause 52.211-10”

@ LeadTimeDescription/ “From date of lead time event to completion of performance”@ DeliveryLeadTime/ DurationUnit/ “Calendar Days”@ DeliveryLeadTime/ DurationValue/ “21”@ LeadTimeEvent/ “Date of Award Receipt”@ PerformancePeriodFirmness/ “Mandatory”@ PerformancePeriodComments/ “FAR Clause 52.211-10”

XML Sample


…<DeliveryDates>

<DeliveryLeadTime><LeadTimeDescription>From date of lead time event to beginning of performance</LeadTimeDescription><DeliveryLeadTime>

<DurationUnit>Calendar Days</DurationUnit><DurationValue>7</DurationValue>

</DeliveryLeadTime><LeadTimeEvent>Date of Award Receipt</LeadTimeEvent><PerformancePeriodFirmness>Mandatory</PerformancePeriodFirmness><PerformancePeriodComments>See FAR Clause 52.211-10</PerformancePeriodFirmness>

</DeliveryLeadTime><DeliveryLeadTime>

<LeadTimeDescription>From date of lead time event to completion of performance</LeadTimeDescription><DeliveryLeadTime>

<DurationUnit>Calendar Days</DurationUnit><DurationValue>7</DurationValue>

</DeliveryLeadTime><LeadTimeEvent>Date of Award Receipt</LeadTimeEvent><PerformancePeriodFirmness>Mandatory</PerformancePeriodFirmness><PerformancePeriodComments>See FAR Clause 52.211-10</PerformancePeriodFirmness>

</DeliveryLeadTime></DeliveryDates>…

Schema View

4.8.9 Performance Payment Bonds (Calendar Days)When a contractor is required to furnish performance payment bonds, they must agree to provide those bonds within a certain number of calendar days after the contract has been awarded.

Form Location

Form Block Number Block TitleSF 1442 12a & b THE CONTRACTOR MUST FURNISH…? and CALENDAR DAYS

Sample Block

12a. THE CONTRACTOR MUST FURNISH ANY REQUIRED PERFORMANCE AND PAYMENT BONDS? (If “YES”, indicate within how many calendar days after award in Item 12b.)

12b. CALENDAR DAYS

YES NO 15SF 1442, Block 13b


Schema LocationPath: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ PerformancePaymentBonds/ “15”

Note: The absence of the <PerformancePaymentBonds> element indicates that the contractor does not need to furnish any performance and payment bonds. In this case, 12a would have “NO” checked.

XML Sample

Schema View

4.8.10 Offer GuaranteeAn offer guarantee ensures that the contractor will furnish any required performance and payment bonds within a certain number of days after the contract is awarded.

Form Location

Form Block Number Block TitleSF 1442 13b. An offer guarantee….

Sample Block

b. An offer guarantee is,

is not required.

SF 1442, Block 13b



<PerformancePaymentBonds>15</PerformancePaymentBonds></SolicitationOfferInformation>…

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SolicitationOfferInformation/ OfferGuaranteeRequired/ “true”

Note: The absence of the <OfferGuaranteeRequired> element indicates that an offer guarantee is not required. In other words, “false” is not a valid value for <OfferGuaranteeRequired>.

XML Sample

Schema View

4.9 Pricing4.9.1 Pricing ArrangementThe pricing arrangement describes the type of contract. The contract types are grouped into two broad categories: fixed-price contracts (see FAR Subpart 16.2) and cost-reimbursement contracts (see FAR Subpart 16.3). The specific contract types range from firm fixed price, in which the contractor has full responsibility for the performance costs and resulting profit (or loss), to cost plus fixed fee, in which the contractor has minimal responsibility for the performance costs and the negotiated fee (profit) is fixed. In between are the various incentive contracts (see FAR Subpart 16.4), in which the contractor’s responsibility for the performance costs and the profit or fee incentives offered are tailored to the uncertainties involved in contract performance.



< OfferGuaranteeRequired>true</ OfferGuaranteeRequired></SolicitationOfferInformation>…

On the forms, the Pricing Arrangement is typically included on the line items. In the PDS XML Schema, <PricingArrangement> is required at the header level as well as the line item. The pricing arrangement at the header level is determined by the following logic:

For each line with the same pricing arrangement, total the obligated amounts. The pricing arrangement at the header level is the pricing arrangement with the largest total amount.

This logic will be demonstrated in the XML Sample.

When the contract is an ordering instrument, the pricing arrangement may be “Order Dependent”.

Form Location

N/A

Schema LocationMajor Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/

@ PricingArrangement/ PricingArrangementBase/ “Firm Fixed Price”

Major Path – Line Item: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ LineItemBasicInformation/

Line 1: @ PricingArrangement/ PricingArrangementBase/ “Firm Fixed Price”Line 2: @ PricingArrangement/ PricingArrangementBase/ “Firm Fixed Price”Line 3: @ PricingArrangement/ PricingArrangementBase/ “Cost Plus Fixed Fee”


XML Sample


<ProcurementInstrumentHeader>…<BasicInformation>

…<PricingArrangement>

<PricingArrangementBase>Firm Fixed Price</PricingArrangementBase></PricingArrangement>


</ProcurementInstrumentHeader><ContractLineItems>

…<LineItems>

…<LineItemBasicInformation>

<PricingArrangement>Firm Fixed Price</PricingArrangement>…

</LineItemBasicInformation><LineItemAmounts>

<ItemObligatedAmount><ObligatedAmount>20000</ObligatedAmount>…

</ItemObligatedAmount></LineItemAmounts>

</LineItems><LineItems>


<PricingArrangement>Firm Fixed Price</PricingArrangement>…






<PricingArrangement>Cost Plus Fixed Fee</PricingArrangement>…




Schema View – Header

Schema View – Line Item

4.9.2 Accounting and Appropriation DataThe Accounting and Appropriation Data block contains information about how the products or services covered by the procurement instrument are funded. In the XML, the document level carries the Obligated Amount, the Accounting Classification Reference Number (ACRN), and the associated Line of Accounting (LOA). Only the ACRN and line item Obligated Amount are provided on a line item.


Form Location

Form Block Number Block TitleDD 1155 17 ACCOUNTING AND APPROPRIATION DATA/ LOCAL USESF 26 14 ACCOUNTING AND APPROPRIATION DATA/ LOCAL USESF 30 12 ACCOUNTING AND APPROPRIATION DATASF 33 21 ACCOUNTING AND APPROPRIATIONSF 252 9 ADMINISTRATIVE, APPROPRIATION, AND ACCOUNTING DATASF 1442 23 ACCOUNTING AND APPROPRIATION DATA/ LOCAL USESF 1447 23 ACCOUNTING AND APPROPRIATION DATA/ LOCAL USESF 1449 25 ACCOUNTING AND APPROPRIATION DATA/ LOCAL USE

Schema View


4.9.2.1 Example 1: Single Funding Source

If there is a single source of funding for the contract, the funding information may be included in the Accounting and Appropriation block of the form or in the schedule. The funded line items should have the same ACRN as the ACRN in the block and the obligated amount for the ACRN on the form should be the sum of the obligated amounts of the funded line items.

Sample Block

Funding information for the contract as a whole may be included in the Accounting and Appropriation Data block:

14. ACCOUNTING AND APPROPRIATION DATA

AA: 9710400 1320 H521 P1P30 2525 DPAC 1 5365 S12136 63767EObligated Amount: $6,000.00

SF 26, Block 14

Funding information for the line items is included in the schedule of the contract:

Schema Location

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAmounts/ ObligatedAmounts

@ ObligatedAmount/ “6000”@ FinancialReference/ FinancialCodeDescription/ “Accounting Classification Reference Number (ACRN)”@ FinancialReference/ FinancialCodeValue/ “AA”@ LoaDetails/ Blob/ “9710400 1320 H521 P1P30 2525 DPAC 1 5365 S12136 63767E”

Major Path – Line Item: ProcurementDocument/ ContractLineItems/ LineItems/ LineItemAmounts/ ItemObligatedAmount

Line 1: @ ObligatedAmount/ “2000”@ FinancialReference/ FinancialCodeDescription/ “Accounting Classification Reference Number (ACRN)”@ FinancialReference/ FinancialCodeValue/ “AA”



SF 26, Block 15

15A. ITEM NO 15B. SUPPLIES/SERVICES 15C. QUANTITY 15D. UNIT 15E. UNIT PRICE 15F. AMOUNT0001 Enterprise Networking Services

ACRN: AA Amount: $80,000.0020 Labor Hours $100.00 $2,000.00

0002 Distributed Computing ServicesACRN: AA Amount: $40,000.00

40 Labor Hours $100.00 $4,000.00

15G. TOTAL AMOUNT OF CONTRACT $6,000.00

XML Sample

4.9.2.2 Example 2: Multiple Funding Sources

If there are multiple funding sources on a contract, the information may be included on the continuation sheet for Section G.


<ProcurementInstrumentHeader>…<ObligatedAmounts>

<ObligatedAmount>6000</ObligatedAmount><FinancialReference>

<FinancialCodeDescription>Accounting Classification Reference Number

</FinancialCodeDescription><FinancialCodeValue>AA</FinancialCodeValue>

</FinancialReference><LOADetails>

<Blob>9710400 1320 H521 P1P30 2525 DPAC 1 5365 S12136 63767E</Blob></LOADetails>

</ObligatedAmounts></ProcurementInstrumentHeader><ContractLineItems>

<LineItems>…<ItemObligatedAmount>

<ObligatedAmount>2000</ObligatedAmount><FinancialReferenceCode>



</FinancialReferenceCode></ItemObligatedAmount>


…<ItemObligatedAmount>





</LineItems></ContractLineItems>

Sample Block

14. ACCOUNTING AND APPROPRIATION DATA/LOCAL USE

SEE SECTION GSF 26, Block 14

Section G - Contract Administration Data

ACCOUNTING AND APPROPRIATION DATAAA: 9710400 1320 H521 P1P30 2525 DPAC 1 5365 S12136 63767EAMOUNT: $80,000.00

AB: 9720400 1320 H521 P2P30 2525 DPAC 2 5089 S12136 63767EAMOUNT: $90,000.00

SF 26, Continuation Sheet

Schema Location

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAmounts/ ObligatedAmounts

ACRN AA:@ ObligatedAmount/ “80000”@ FinancialReference/ FinancialCodeDescription/ “Accounting Classification Reference Number (ACRN)”@ FinancialReference/ FinancialCodeValue/ “AA”@ LoaDetails/ Blob/ “9710400 1320 H521 P1P30 2525 DPAC 1 5365 S12136 63767E”

ACRN AB:@ ObligatedAmount/ “90000”@ FinancialReference/ FinancialCodeDescription/ “Accounting Classification Reference Number (ACRN)”@ FinancialReference/ FinancialCodeValue/ “AB”@ LoaDetails/ Blob/ “9720400 1320 H521 P2P30 2525 DPAC 2 5089 S12136 63767E”

Major Path – Line Item: ProcurementDocument/ ContractLineItems/ LineItems/ LineItemAmounts/ ItemObligatedAmount


Line 2: @ ObligatedAmount/ “40000”@ FinancialReference/ FinancialCodeDescription/ “Accounting Classification Reference Number (ACRN)”@ FinancialReference/ FinancialCodeValue/ “AB”

Line 3: @ ObligatedAmount/ “50000”@ FinancialReference/ FinancialCodeDescription/ “Accounting Classification Reference Number (ACRN)”@ FinancialReference/ FinancialCodeValue/ “AB”


1SF 26, Block 15

15A. ITEM NO 15B. SUPPLIES/SERVICES 15C. QUANTITY 15D. UNIT 15E. UNIT PRICE 15F. AMOUNT0001 Enterprise Networking Services

ACRN: AA Amount: $80,000.0010 Labor Hours $8,000.00 $80,000.00

0002 Distributed Computing Services – East CoastACRN: AB Amount: $40,000.00

10 Labor Hours $4,000.00 $40,000.00

0003 Distributed Computing Services – West CoastACRN: AB Amount: $50,000.00

10 Labor Hours $5,000.00 $50,000.00

15G. TOTAL AMOUNT OF CONTRACT$170,000.00

XML Sample


<ProcurementInstrumentHeader>…<ObligatedAmounts>


<FinancialCodeDescription>Accounting Classification Reference Number</FinancialCodeDescription><FinancialCodeValue>AA</FinancialCodeValue>



</ObligatedAmounts><ObligatedAmounts>


<FinancialCodeDescription>Accounting Classification Reference Number</FinancialCodeDescription><FinancialCodeValue>AB</FinancialCodeValue>



</ObligatedAmounts></ProcurementInstrumentHeader><ContractLineItems>

<LineItems>…<ItemObligatedAmount>









</FinancialCodeDescription><FinancialCodeValue>AB</FinancialCodeValue>






</FinancialCodeDescription><FinancialCodeValue>AB</FinancialCodeValue>


</LineItems></ContractLineItems>

4.9.3 CurrencyThe currency elements in the PDS XML schema contain the buying and/or paying currency for the contract or contract line item. These elements are only used when the currency is something other than US Dollars. The currency name must be found in ISO 4217 from the International Organization for Standardization (ISO). If a currency element is provided, the exchange rate attribute must also be provided. This rate indicates the currency’s value in comparison to the US Dollar.

Form Location

N/A. There is no currency block on the forms.

Sample Block

N/A.

Schema Location

If the buying and payment currencies are the same for all the line items, they are at the header level. Otherwise, they are on each individual line item.

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentAmounts/ HeaderCurrency

@ AwardCurrency/ BuyingCurrency/ “Sol” (exchange rate = “3.488”)@ AwardCurrency/ PaymentCurrency/ “Euro” (exchange rate = “0.9049”)

Major Path – Line Item: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ LineItemAmounts/ ItemCurrency

@ BuyingCurrency@ PaymentCurrency

XML Sample


…<ProcurementInstrumentAmounts>

<HeaderCurrency><AwardCurrency>

<BuyingCurrency exchangeRate="3.488">Sol</BuyingCurrency><PaymentCurrency exchangeRate="0.9049">Euro</PaymentCurrency>

</AwardCurrency>…

</HeaderCurrency>…

</ProcurementInstrumentAmounts>

Schema View

4.9.4 Total AmountThis block contains the total contract amount of the order or instrument.

Form Location

Form Block Number Block TitleDD 1155 25 TOTALOF 307 13 TOTAL AMOUNT OF CONTRACTSF 26 15G TOTAL AMOUNT OF CONTRACTSF 33 20 AMOUNTSF 252 7 CONTRACT AMOUNT (Express in words and figures)SF 1442 22 AMOUNTSF 1447 24 TOTAL AWARD AMOUNT (For Government Use Only)SF 1449 26 TOTAL AWARD AMOUNT (For Govt. Use Only)

Sample Block

24. TOTAL AWARD AMOUNT(For Government Use Only)

$100.00SF 1447, Block 24


Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAmounts/

@ OtherAmounts/ AmountDescription/ “Header Only – Total Contract Value”@ OtherAmounts/ Amount/ “100”

XML Sample

Schema View


…<AwardInstrument>

…<ProcurementInstrumentAmounts>

<OtherAmounts><AmountDescription>Header Only – Total Contract Value</AmountDescription><Amount>100</Amount>

</OtherAmounts></ProcurementInstrumentAmounts>

</AwardInstrument>…

4.9.5 Discount Terms/Prompt PaymentThis block contains discount terms associated with prompt payments. Days due is the number of calendar days by which payment must be made to receive the discount. Net Days is the number of days until the total invoice amount is due. This value must be between 1 and 30 inclusive.

Form Location

Form Block Number Block TitleDD 1155 12 DISCOUNT TERMSSF 26 9 DISCOUNT FOR PROMPT PAYMENTSF 33 13 DISCOUNT FOR PROMPT PAYMENTSF 1447 15 PROMPT PAYMENT DISCOUNTSF 1449 12 DISCOUNT TERMS

Sample Block

13. DISCOUNT FOR PROMPT PAYMENT 10 Calendar Days 20 Calendar Days 30 Calendar Days Calendar Days(See Section I, Clause No. 52.232-8) 3% 2%

SF 33, Block 13

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ PaymentDiscount

@ Terms/ Percent/ “3.00”@ Terms/ DaysDue/ “10”

@ Terms/ Percent/ “2.00”@ Terms/ DaysDue/ “20”

XML Sample


…<PaymentDiscount>

<Terms><Percent>3.00</Percent><DaysDue>10</DaysDue>

</Terms></PaymentDiscount><PaymentDiscount>

<Terms><Percent>2.00</Percent><DaysDue>20</DaysDue>

</Terms></PaymentDiscount>…

Schema View

4.10 Delivery FOB

The Free On Board (FOB) point determines when the transfer of ownership occurs, who pays freight, and who bears the risks of damage to the goods during shipping. For example, if the FOB point is “Destination", then the seller pays shipping costs and remains responsible for the goods until the buyer takes possession.

Several of the forms have a block for Delivery FOB, but often times, the FOB point is in Section F Deliveries or Performance.

If the FOB point is “Terminal”, the 5 character United Nations code must be provided.

Form Location

Form Block Number Block TitleDD 1155 8 DELIVERY FOBSF 26 8 DELIVERYSF 1449 11 DELIVERY FOR FOB DESTINATION UNLESS BLOCK IS MARKED

Sample Block - Destination

When “Destination” is checked, the Delivery FOB information is mapped at the header level.

8. DELIVERY FOB X DESTINATION

OTHER(See schedule if other)

DD 1155, Block 8


Sample Block - Other

When “Other” is checked, the Delivery FOB information is mapped at the line item level.

8. DELIVERY FOB DESTINATION X OTHER

(See schedule if other)DD 1155, Block 8

SECTION F DD1155 CONTINUATION SHEET

DELIVERY INFORMATION

M52300-15-P-0111

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS UIC

0001 30-JUL-2015 100 DEFENSE LOGISTICS AGENCY20000 DELIVERY DRIVEHUNTINGTON BEACH, CA 92647-2099FOB: TerminalUnited Nations Code: ZA9B8

SW3225

DD 1155, Section F

Schema LocationMajor Path – Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ Shipping/ FoBDetails

@ PaymentMethod/ “Contractor”@ FoBPoint/ “Destination”

Major Path – Line Item: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ Shipping/ FoBDetails

@ PaymentMethod/ “Contractor”@ FoBPoint/ “Terminal”@ UnitedNationsCode/ “ZA9B8”

Note: There is no place on the form to indicate the Payment Method, but it is a required element in the PDS XML schema. In this example, the <PaymentMethod> is “Contractor”, because typically, the Seller is responsible for the shipping costs up until the goods reach the FOB Point.

XML Sample - Header



…<Shipping>

<FoBDetails><PaymentMethod>Contractor</PaymentMethod><FoBPoint>Destination</FoBPoint>

</FoBDetails></Shipping>



Schema View

4.11 AttachmentsAdditional information about a procurement instrument can be added to the document in the form of attachments.

The standard types of attachments are provided in the enumerations list for the <AttachmentDescription/ StandardAttachment> element. If the attachment type is not included in the list of standard types, a description must be entered in the <AttachmentDescription/ OtherAttachment> element.

The absence of the “AttachmentSecurityLevel” attribute on the <AttachmentName> element indicates that the attachment is unclassified. In this case, the attachment can be provided in one of two ways:

Including the attachment as binary text. This method requires that a data format be specified. By specifying a URL which points to the attachment.

It is also possible to provide neither a binary text nor a URL. This would indicate that there is an attachment, but the actual contents of the attachment would not accessible from within the PDS XML.

If the attachment is classified, the “AttachmentSecurityLevel” attribute should be populated. In this case, binary text cannot be provided.


…<ContractLineItems>

<LineItems>…<FoBDetails>

<PaymentMethod>Contractor</PaymentMethod><FoBPoint>Terminal</FoBPoint><UnitedNationsCode>ZA9B8</UnitedNationsCode>

</FoBDetails></LineItems>

</ContractLineItems>

Form Location

Form Block Number Block TitleSF 252 10 The United States of America (called the Government) represented by the

Contracting Officer executing this contract, and the Architect-Engineer agree to perform this contract in strict accordance with the clauses and the documents identified as follows, all of which are made a part of this contract:

SF 1442 10 THE GOVERNMENT REQUIRES PERFORMANCE OF THE WORK DESCRIBED IN THESE DOCUMENTS (Title, identifying number, date)

Sample Block

SF 252, Block 10

Schema Location

This example shows four types of attachments:

1) An unclassified attachment that is provided using binary text.2) An unclassified attachment that is provided by specifying a URL.3) A classified attachment that is provided by specifying a URL.4) A non-standard, unclassified attachment that is only a reference to a document. No binary text or URL is

provided.

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentAttachments/

@ AttachmentDescription/ StandardAttachment/ “Subcontractor Plan”@ AttachmentName/ “HC1011-15-D-0001 Subcontractor Plan”@ AttachmentBinaryText/ “zc1Njf/L08gNjgvRSD/Nj”@ AttachmentDataFormat/ “Microsoft Word”

@ AttachmentDescription/ OtherAttachment/ “Resumes”@ AttachmentName/ “HC1011-15-D-0001 Personnel”@ AttachmentURL/ “http:/abc.osd.mil”

@ AttachmentDescription/ StandardAttachment/ “Statement of Work”@ AttachmentName/ “HC1011-15-D-0001 SOW” (AttachmentSecurityLevel = “Secret”)@ AttachmentURL/ https://xyz.smil.mil/

@ AttachmentDescription/ OtherAttachment/ “Architectural Diagram”@ AttachmentName/ “HC1011-15-D-0001 Architectural Diagram”


10. The United States of America (called the Government) represented by the Contracting Officer executing this contract, and the Architect-Engineer agree to perform this contract in strict accordance with the clauses and the documents identified as follows, all of which are made a part of this contract:

1. HC1011-15-D-0001 Subcontractor Plan2. HC1011-15-D-0001 Personnel3. HC1011-15-D-0001 SOW (Secret)4. HC1011-15-D-0001 Architectural Diagram

https://xyz.smil.mil/

XML Sample



…<ProcurementInstrumentAttachments>

<AttachmentDescription><StandardAttachment>Subcontractor Plan</StandardAttachment>

</AttachmentDescription><AttachmentName>HC1011-15-D-0001-0001 Subcontractor Plan</AttachmentName><AttachmentBinaryText>zc1Njf/L08gNjgvRSD/Nj…</AttachmentBinaryText><AttachmentDataFormat>Microsoft Word</AttachmentDataFormat>

</ ProcurementInstrumentAttachments > <ProcurementInstrumentAttachments>

<AttachmentDescription><OtherAttachment>Resumes</OtherAttachment>

</AttachmentDescription><AttachmentName>HC1011-15-D-0001-0001 Personnel</AttachmentName><AttachmentURL>http:/abc.osd.mil</AttachmentURL>

</ ProcurementInstrumentAttachments ><ProcurementInstrumentAttachments>

<AttachmentDescription><StandardAttachment>Statement of Work</StandardAttachment>

</AttachmentDescription><AttachmentName AttachmentSecurityLevel=”Secret”>HC1011-15-D-0001-0001 SOW</AttachmentName><AttachmentURL>http:/xyz.smil.mil</AttachmentURL>

</ ProcurementInstrumentAttachments > <ProcurementInstrumentAttachments>

<AttachmentDescription><OtherAttachment>Statement of Work</OtherAttachment>

</AttachmentDescription><AttachmentName>HC1011-15-D-0001 Architectural Diagram</AttachmentName>

</ ProcurementInstrumentAttachments ></ProcurementInstrumentHeader>

Schema View


4.12 Schedule of Supplies/ServicesThis section contains details about what exactly was ordered for each line item.

Form Location

Form Block Numbers Block TitlesDD 1155 18-23 18. ITEM NO.

19. SCHEDULE OF SUPPLIES/SERVICES20. QUANTITY ORDERED/ ACCEPTED21. UNIT22. UNIT PRICE23. AMOUNT

SF 26 15A-15F 15A. ITEM NO.15B. SUPPLIES/SERVICES15C. QUANTITY15D. UNIT15E. UNIT PRICE15F. AMOUNT

SF 1447 17-22 17. ITEM NUMBER 18. SCHEDULE OF SUPPLIES/SERVICES19. QUANTITY20. UNIT21. UNIT PRICE22. AMOUNT

SF 1449 19-24 19. ITEM NO.20. SCHEDULE OF SUPPLIES/SERVICES19. QUANTITY22. UNIT23. UNIT PRICE24. AMOUNT

Sample Block – on form

19. ITEM NO. 20. SCHEDULE OF SUPPLIES OR SERVICES 21. QUANTITY 22. UNIT 23. UNIT PRICE 24. AMOUNT00010002

BoxCrate

1001,000

UnitUnit

2.003.00

$200.00$3000.00

SF 1449, Block 19

Sample Block – on continuation sheet

19. ITEM NO. 20. SCHEDULE OF SUPPLIES OR SERVICES 21. QUANTITY 22. UNIT 23. UNIT PRICE 24. AMOUNT

SEE SCHEDULE

SF 1449, Block 19


M5000-15-P-0111


ITEM NO. SCHEDULE OF SUPPLIES/ SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001

0002

BOXLARGE STORAGE BOXVENDOR PART NUMBER: BX-001

CRATEWOODEN SHIPPING CRATEVENDOR PART NUMBER: CT-222

100

1000

Unit

Unit

2.00

3.00

$200.00

$3,000.00

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/

@ LineItemIdentifier/ DFARS/ LineItem/ LineItemType/ “CLIN”@ LineItemIdentifier/ DFARS/ LineItem/ LineItemBase/ “0001”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductOrService/ “Personal Property”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductServiceDescription/ “Large storage box”@ LineItemBasicInformation/ ProductServicesOrdered/ Quantity/ “100”@ LineItemBasicInformation/ ProductServicesOrdered/ ItemUIDRequired/ “false”@ LineItemBasicInformation/ ProductServicesOrdered/ UnitOfMeasure/ “Unit”@ LineItemBasicInformation/ ProductServicesOrdered/ UnitPrice/ “2.00”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductServiceData/ Data Description/ “Vendor’s (Seller’s) Part Number”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductServiceData/ DataValue/ “BX-001”

@ LineItemIdentifier/ DFARS/ LineItem/ LineItemType/ “CLIN”@ LineItemIdentifier/ DFARS/ LineItem/ LineItemBase/ “0002”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductOrService/ “Personal Property”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductServiceDescription/ “Wooden Shipping Crate”@ LineItemBasicInformation/ ProductServicesOrdered/ Quantity/ “1000”@ LineItemBasicInformation/ ProductServicesOrdered/ ItemUIDRequired/ “false”@ LineItemBasicInformation/ ProductServicesOrdered/ UnitOfMeasure/ “Unit”@ LineItemBasicInformation/ ProductServicesOrdered/ UnitPrice/ “3”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductServiceData/ Data Description/ “Vendor’s (Seller’s) Part Number”@ LineItemBasicInformation/ ProductServicesOrdered/ ProductServiceData/ DataValue/ “CT-222”


SF 1449, Continuation Sheet

XML Sample



<LineItems><LineItemIdentifier>

<DFARS><LineItem>

<LineItemType>CLIN</LineItemType><LineItemBase>0001</LineItemBase>

</LineItem></DFARS>

</LineItemIdentifier><LineItemBasicInformation>

…<ProductServicesOrdered>

<ProductOrService>Personal Property</ProductOrService><ProductOrServiceDescription>Large Storage Box</ProductOrServiceDescription><Quantity>100</Quantity>< ItemUIDRequired>false</ItemUIDRequired><UnitOfMeasure>Unit</UnitOfMeasure><UnitPrice>2.00</UnitPrice><ProductServiceData>

<DataDescription>Vendor’s (Seller’s) Part Number</DataDescription><DataValue>BX-001</DataValue>

</ProductServiceData></ProductServiceOrdered>

</LineItemBasicInformation></LineItems><LineItems>

<LineItemIdentifier><DFARS>

<LineItem><LineItemType>CLIN</LineItemType><LineItemBase>0002</LineItemBase>

</LineItem></DFARS>

</LineItemIdentifier><LineItemBasicInformation>

…<ProductServicesOrdered>

<ProductOrService>Personal Property</ProductOrService><ProductOrServiceDescription>Wooden Shipping Crate</ProductOrServiceDescription><Quantity>1000</Quantity>< ItemUIDRequired>false</ItemUIDRequired><UnitOfMeasure>Unit</UnitOfMeasure><UnitPrice>3.00</UnitPrice><ProductServiceData>

<DataDescription>Vendor’s (Seller’s) Part Number</DataDescription><DataValue>CT-222</DataValue>

</ProductServiceData></ProductServiceOrdered>

</LineItemBasicInformation></LineItems>

</ContractLineItems>

Schema View

4.13 Ordering InformationThe <OrderingInformation> section of the schema provides parameters related to the orders on ordering instruments.

4.13.1 Estimated QuantityEstimated quantity is the realistic estimate of the total quantity of supplies or services that will be ordered (e.g. estimated number of labor hours). This information is typically found in Section B Supplies or Services and Prices/Costs.


Form Location

N/A

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ OrderingInformation/ EstimatedQuantity/

@ QuantityValue/ “3000”@ UnitOfMeasure/ “Labor Hours”

XML Sample

Schema View



<OrderingInformation><EstimatedQuantity>

<QuantityValue>3000</QuantityValue><UnitOfMeasure>Labor Hours</UnitOfMeasure>

</EstimatedQuantity></OrderingInformation>


4.13.2 LimitsLimits are used to detail restrictions on the quantity of orders against the ordering instrument. The three types of limits are:

Allowed Per Order Contractor Obligation to Deliver Government Obligation to Order

Limit information is typically found in Section B Supplies or Services and Prices/Costs. For definitions of each of the limit types, see the “Definitions” section of this document.

Form Location

N/A

Schema LocationMajor Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ OrderingInformation/ Limits/Major Path – Line Item: ProcurementDocument/ ContractLineItems/ LineItems/ LineItemBasicInformation/ OrderingInformation/ Limits/

@ LimitDescription/ “Allowed Per Order”@ Minimum/ “10”@ Maximum/ “100”@ UnitOfMeasure/ “Each”

XML Sample


… <OrderingInformation>

<Limits><LimitDescription>Allowed Per Order</LimitDescription><Minimum>10</Minimum><Maximum>100</Maximum><UnitOfMeasure>Each</UnitOfMeasure>

</Limits></OrderingInformation>…

Schema View:

4.13.3 Ordering CapabilityThis section specifies which entities can and cannot place orders against the ordering instrument.

<UnitedStatesGovernment> - denotes whether or not a US Government entity can place an order. <DoDMultiAgency> - specifies which DoD Services and Agencies may place an order. <DoDAgencyWide> - denotes whether or not any entity within the DoD can place an order. <SpecificEntities> - denotes whether or not only specific entities may place an order.

Form Location

N/A. This information is typically found in Section B Supplies or Services and Prices/Costs.

Schema LocationMajor Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ OrderingInformation/ OrderingCapability/

@DoDMultiAgency/ “Air Force”@DoDMultiAgency/ “Army”


XML Sample

Schema View

4.13.4 Order VariationThis section contains the permitted variations expressed as a quantity or a percentage. The percentage should be expressed as a decimal in the PDS XML document – for example, express 4.25% as 4.25.

Form Location

N/A. This information is not shown on the forms but on a continuation sheet in the applicable section.

Schema LocationMajor Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ OrderingInformation/ OrderVariation/

@ Percentage/ PercentUnder/ “3.50”@ Percentage/ PercentOver/ “3.50”

Major Path – Line Item: ProcurementDocument/ ContractLineItems/ LineItems/ LineItemBasicInformation/ OrderingInformation/ OrderVariation/

@ Quantity/ QuantityUnder/ “10”@ Quantity/ QuantityOver/ “15”



<OrderingInformation><OrderingCapability>

<DoDMultiAgency>Air Force</DoDMultiAgency><DoDMultiAgency>Army</DoDMultiAgency>

</OrderingCapability></OrderingInformation>


@ Quantity/ UnitOfMeasure/ “Each”

XML Sample - Header


Schema View


…<OrderingInformation>

<OrderVariation><PercentUnder>3.50</PercentUnder><PercentOver>3.50</PercentOver>

</OrderingVariation></OrderingInformation>…


<OrderVariation><QuantityUnder>10</QuantityUnder><QuantityOver>15</QuantityOver><UnitOfMeasure>Each</UnitOfMeasure

</OrderingVariation></OrderingInformation>…

4.13.5 Response Days to Reject OrderIf the Government places an order that exceeds the maximum quantity, the contractor has a period of time in which they can reject the order. This element contains the number of days in which the contractor can reject the order.

This information is not shown on the forms but on a continuation sheet in the applicable section.

Form Location

N/A

Schema LocationPath: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ OrderingInformation/ ResponseDaysToRejectOrder/ “20”

XML Sample

Schema View



<ResponseDaysToRejectOrder>20</ResponseDaysToRejectOrder></OrderingInformation>…

4.14 ClausesClauses are used to clearly define the terms of a contract. Most contracts use the Uniform Contract Format (UCF) in accordance with FAR 14.201-1. Part II, Section I of the UCF is reserved for clauses, but clauses may be provided in any of the other sections as well.

Construction contracts are exempt from using the UCF and may use the Construction Specification Institute (CSI) format. This guide addresses the UCF.

Clauses can be provided by reference or by full text. If a clause requires text to be inserted (e.g. a date), the clause may be provided as full text with the required text embedded or by reference with the fill-in section used.

There are two special types of “variation clauses” that can be used:

A deviation is a clause that has an approved change or “deviation” from the original FAR or DFARS clause. An alternate is an approved clause that may be used in place of the original clause.

Form Location

Form Block Number Block TitleSF 252 10 The United States of America (called the Government) represented by the

Contracting Officer executing this contract, and the Architect-Engineer agree to perform this contract in strict accordance with the clauses and the documents identified as follows, all of which are made a part of this contract:


Sample Block

Schema Location

Since the examples above are not associated with any particular line item or group of line items, they are located at the header level and apply to all the line items. Each of the clauses has its own iteration of the <ClauseDetails> section. Instances of the <RegulationURL> element provide links to the websites that have the details for the clauses cited by the contract. The schema only has the <RegulationURL> element at the header level – it cannot be provided on a line item.


10. The United States of America (called the Government) represented by the Contracting Officer executing this contract, and the Architect-Engineer agree to perform this contract in strict accordance with the clauses and the documents identified as follows, all of which are made a part of this contract:

CLAUSES INCORPORATED BY REFERENCE

252.225-7048 Export-Controlled Items JUN 2013

52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders -- Commercial Items (Deviation 2013-O0019) NOV 2017

52.212-5 Alt I Contract Terms and Conditions Required to Implement Statutes or Executive Orders -- Commercial Items (Deviation 2013-O0019) FEB 2000

CLAUSES INCORPORATED BY FULL TEXT

52.215-8 ORDER OF PRECEDENCE—UNIFORM CONTRACT FORMAT (OCT 1997)Any inconsistency in this solicitation or contract shall be resolved by giving precedence in the following order:(a) The Schedule (excluding the specifications).(b) Representations and other instructions.(c) Contract clauses.(d) Other documents, exhibits, and attachments.(e) The specifications.

52.222.49 Service Contract Labor Standards -- Place of Performance Unknown (May 2014)(a) This contract is subject to the Service Contract Labor Standards statute, and the place of performance was unknown when the solicitation was issued. In addition to places or areas identified in wage determinations, if any, attached to the solicitation, wage determinations have also been requested for the following: Huntsville, AL [insert places or areas]. The Contracting Officer will request wage determinations for additional places or areas of performance if asked to do so in writing by 5PM on 2/12/2017 [insert time and date].

(b) Offerors who intend to perform in a place or area of performance for which a wage determination has not been attached or requested may nevertheless submit bids or proposals. However, a wage determination shall be requested and incorporated in the resultant contract retroactive to the date of contract award, and there shall be no adjustment in the contract price.

SF 252, Block 10

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ClauseInformation/

@ RegulationURL/ “http://farsite.hill.af.mil/vmdfara.htm”@ RegulationURL/ “http://farsite.hill.af.mil”

Major Path - Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ClauseInformation/ Major Path – Line Item: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ LineItemClauses/

Example 1: Clause Incorporated by Reference

@ ClauseDetails/ RegulationOrSupplement/ “DFARS”@ ClauseDetails/ ClauseNumber/ “252.225-7048”@ ClauseDetails/ ClauseTitle/ “Export-Controlled Items”@ ClauseDetails/ ClauseEffectiveDate/ “2013-06”@ ClauseDetails/ Section/ “I”

Example 2: Clause Variation - Incorporated by Reference

@ ClauseDetails/ RegulationOrSupplement/ “FAR”@ ClauseDetails/ ClauseNumber/ “52.212-5”@ ClauseDetails/ ClauseTitle/ “Contract Terms and Conditions Required to Implement Statutes or Executive Orders”@ ClauseDetails/ ClauseEffectiveDate/ “2017-11”@ ClauseDetails/ ClauseVariation/ AlternateOrDeviation/ “Alternate”@ ClauseDetails/ ClauseVariation/ VariationEffectiveDate/ “2000-02” @ ClauseDetails/ ClauseVariation/ VariationName/ “I”@ ClauseDetails/ ClauseVariation/ AlternateOrDeviation/ “Deviation”@ ClauseDetails/ ClauseVariation/ VariationEffectiveDate/ “2013-09” @ ClauseDetails/ ClauseVariation/ VariationName/ “2013-O0019”@ ClauseDetails/ Section/ “I”

Example 3: Clause Incorporated by Full Text

@ ClauseDetails/ RegulationOrSupplement/ “FAR”@ ClauseDetails/ ClauseNumber/ “52.215-8”@ ClauseDetails/ ClauseTitle/ “ORDER OF PRECEDENCE—UNIFORM CONTRACT FORMAT”@ ClauseDetails/ ClauseEffectiveDate/ “1997-10”@ ClauseDetails/ ClauseText/ ClauseFullText/ “Any inconsistency in this solicitation or contract shall be resolved by giving precedence in the following order:(a) The Schedule (excluding the specifications).(b) Representations and other instructions.(c) Contract clauses.(d) Other documents, exhibits, and attachments.(e) The specifications.”@ ClauseDetails/ Section/ “I”

Example 4: Clause Incorporated by Fill-in Text

@ ClauseDetails/ RegulationOrSupplement/ “FAR”@ ClauseDetails/ ClauseNumber/ “52.222-49”@ ClauseDetails/ ClauseTitle/ “Service Contract Labor Standards -- Place of Performance Unknown”@ ClauseDetails/ ClauseEffectiveDate/ “2014-05”@ ClauseDetails/ ClauseText/ ClauseFillinText/ FillinSequenceNumber/ “1”@ ClauseDetails/ ClauseText/ ClauseFillinText/ FillinText/ “Huntsville, AL”@ ClauseDetails/ ClauseText/ ClauseFillinText/ FillinSequenceNumber/ “2”@ ClauseDetails/ ClauseText/ ClauseFillinText/ FillinText/ “5PM on 2/12/2017”@ ClauseDetails/ Section/ “I”

XML Sample


<ClauseInformation> <RegulationURL>http://www.acq.osd.mil/dpap/dars/index.html</RegulationURL> <RegulationURL>http://farsite.hill.af.mil</RegulationURL> <ClauseDetails> <RegulationOrSupplement>DFARS</RegulationOrSupplement> <ClauseNumber>252.225-7048</ClauseNumber> <ClauseTitle>Export-Controlled Items</ClauseTitle> <ClauseEffectiveDate>2013-06</ClauseEffectiveDate> <Section>I</Section>

Schema View


<ClauseInformation> <RegulationURL>http://www.acq.osd.mil/dpap/dars/index.html</RegulationURL> <RegulationURL>http://farsite.hill.af.mil</RegulationURL> <ClauseDetails> <RegulationOrSupplement>DFARS</RegulationOrSupplement> <ClauseNumber>252.225-7048</ClauseNumber> <ClauseTitle>Export-Controlled Items</ClauseTitle> <ClauseEffectiveDate>2013-06</ClauseEffectiveDate> <Section>I</Section>

4.15 Reference NumbersThe <ReferenceNumber> section is used to provide numbers referencing documents (MIPR, SOW, GBL, Requisition etc.), numbers (FMS Case, Package, Drawing etc.), Codes (FSC, Project, Weapon System, etc.) and other reference values.

Schema View

Note: The <ReferenceNumber> section is the same at both the Header and the Line Item levels.


4.15.1 Federal Supply Classification and Product Service CodeA Product Service Code (PSC) describes a product or service purchased by the federal Government. Federal Supply Classification (FSC) codes describe products and are a subset of the PSCs.

Each separately identifiable contract line or subline item must include a PSC that relates to the products or services to be delivered or completed. If both an FSC and a PSC exist on a line item, their values must be the same. FSCs and PSCs can also be provided at the header-level.

Form Location

N/A. These codes are not found on the forms but on the continuation sheets in Section B.

Schema LocationMajor Path – Header: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ReferenceNumber/ Major Path – Line Item: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ ReferenceNumber/

@ ReferenceDescription/ “Federal Supply Classification Code”@ ReferenceValue/ “1315”@ Section/ “B”@ ReferenceDescription/ “Product Service Code”@ ReferenceValue/ “1315”@ Section/ “B”

XML Sample

4.15.2 Defense Priorities and Allocations System Priority RatingThe Defense Priorities and Allocations System (DPAS) Priority Rating helps ensure the timely performance of contracts and orders placed in support of FEMA programs such as preparedness for natural disasters.

Form Location

Form Block Number Block TitleDD 1155 5 PRIORITYSF 26 1 THIS CONTRACT IS A RATED ORDER UNDER DPAS (15 CFR 700)SF 33 1 THIS CONTRACT IS A RATED ORDER UNDER DPASSF 1447 1 RATINGSF 1449 13 THIS CONTRACT IS A RATED ORDER UNDER DPAS, RATING



<ReferenceDescription>Federal Supply Classification Code</ReferenceDescription><ReferenceValue>1315</ReferenceValue><ReferenceSection>B</ReferenceSection>

</ReferenceNumber><ReferenceNumber>

<ReferenceDescription>Product Service Code</ReferenceDescription><ReferenceValue>1315</ReferenceValue><ReferenceSection>B</ReferenceSection>

</ReferenceNumber>…

Sample Block

X 13a. THIS CONTRACT IS A RATED ORDER UNDER DPAS (15 CFR 700)

13b. RATINGDO-09

SF 1449, Block 13

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ReferenceNumber/

@ ReferenceDescription/ “Defense Priorities Allocation System (DPAS) Priority Rating”@ ReferenceValue/ “DO-09”@ Section/ “A”

XML Sample

4.15.3 Requisition Number/Project Number/Purchase Request NumberThe Requisition, Project, and Purchase Request Numbers identify the document generated to notify a purchasing or contracting department of items and/or services it needs, the quantity, and the timeframe. It may also contain the authorization to proceed with the purchase.

Form Location

Form Block Number Block TitleDD 1155 4 REQUISITION/PURCH REQUEST NO.OF 307 4 REQUISITION/PROJECT NUMBERSF 26 4 REQUISITION/PURCHASE REQUEST/PROJECT NO.SF 30 4 REQUISITON/PURCHASE REQUEST NUMBERSF 33 6 REQUISITION/PURCHASE NO.SF 1442 5 REQUISITON/PURCHASE REQUEST NUMBERSF 1449 1 REQUISITION NUMBER

4.15.3.1 Example 1: Header Level

Sample Block

4. REQUISITION/PURCHASE REQUEST/PROJECT NO.HE1280626606

SF 26, Block 4


<ProcurementInstrumentHeader>…<ReferenceNumber>

<ReferenceDescription>Defense Priorities Allocation System (DPAS) Priority Rating</ReferenceDescription><ReferenceValue>DO-09</ReferenceValue><Section>A</Section>

</ReferenceNumber></ProcurementInstrumentHeader>

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ Reference Number

@ Reference Description/ “Purchase Requisition Number”@ Reference Value/ “HE1280626606”@ Section/ “A”

XML Sample

4.15.3.2 Example 2: Line Item Level

When the requisition number differs by line item, the numbers are listed on a schedule and the block is populated with “See Schedule.” In this case, the numbers are placed at the line item level of the schema.

Sample Block

4.

REQUISITION NUMBER

See ScheduleSF 1449, Block 1

M5000-15-P-0111


ITEM NO. SUPPLIES/ SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 Acetylene gasNational Stock Number: 6830-00-270-6216Federal Supply Classification (FSC) Code: 6830Standard Industry Classification (SIC) Code: 5169Purchase Requisition Number: FB250021649475ACRN: AA

2 Cylinder 15.00 $30.00

SF 1449, Continuation SheetSchema Location

Major Path: ProcurementDocument/ AwardInstrument/ ContractLineItems/ LineItems/ Reference Number/

@ ReferenceDescription/ “Purchase Requisition Number” @ ReferenceValue/ “FB250021649475”@ Section/ “B”




<ReferenceDescription>Purchase Requisition Number</ReferenceDescription><ReferenceValue>HE1280626606</ReferenceValue><Section>A</Section>



XML Sample

4.16 Brief DescriptionThis block contains a short description of the supplies or services that will be delivered.

Form Location

Form Block Number Block TitleOF 307 12 BRIEF DESCRIPTIONSF 252 6 CONTRACT FOR (General description of services to be provided)SF 1447 10 ITEMS TO BE PURCHASED (Brief Description)

Sample Block

8. CONTRACT FOR (General description of services to be provided)

RENOVATIONS TO EXISTING WAREHOUSE FOR OFFICE SPACEDD 252, Block 6

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ ContractDescription/ “RENOVATIONS TO EXISTING WAREHOUSE FOR OFFICE SPACE”

XML Sample



<LineItems><LineItemIdentifier>

<DFARS><LineItem>

<LineItemType>CLIN</LineItemType><LineItemBase>0001</LineItemBase>

</LineItem></DFARS>

</LineItemIdentifier>…<ReferenceNumber>

<ReferenceDescription>Purchase Requisition Number</ReferenceDescription><ReferenceValue>FB250021649475</ReferenceValue><Section>B</Section>


</ContractLineItems>…


<ContractDescription>RENOVATIONS TO EXISTING WAREHOUSE FOR OFFICE SPACE</ContractDescription>…

<BasicInformation>…

Schema View

4.17 Authority for Using Other than Full and Open CompetitionIf the contract was not awarded using full and open competition, this block contains the legal authority by which this was allowed.

Form Location

Form Block Number Block TitleSF 26 13 AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:Sf 33 22 AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:SF 1442 25 OTHER THAN FULL AND OPEN COMPETITION PURSUENT TOSF 1447 16 AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION

Sample Block

13. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 USC. 2304(c)( 2 ) 10 USC. 2304(c)( )

SF 26, Block 13


Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ NotFullOpenCompetition/ “Unusual and Compelling Urgency (10 U.S.C. 2304(c)(2))”

XML Sample

Schema View



…<NotFullOpenCompetition>Unusual and Compelling Urgency (10 U.S.C. 2304(c)(2))</NotFullOpenCompetition>…


4.18 Construction Project DetailsThe <ConstructionProjectDetails> section provides information about construction project contracts. The <ConstructionProjectAddress> and <ConstructionProjectCoordinates> subsections are covered in the Addresses section of this document.

Schema View

4.18.1 Project Title and LocationThe Project Title and Location block contains a short title and abbreviated location for the project.

Form Location

Form Block Number Block TitleSF 252 5 PROJECT TITLE AND LOCATION

Sample Block

5. PROJECT TITLE AND LOCATION

RENOVATIONS TO EXISTING WAREHOUSE FOR OFFICE SPACE, POLAND AVE WHARF, NEW ORLEANS, LA

DD 252, Block 5


Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ConstructionProjectDetails/

@ ProjectTitle/ “RENOVATIONS TO EXISTING WAREHOUSE FOR OFFICE SPACE” @ Project Location/ “POLAND AVE WHARF, NEW ORLEANS, LA”

XML Sample

4.18.2 Project NumberForm Location

Form Block Number Block TitleSF 1442 6 PROJECT NUMBER

Sample Block

6. PROJECT NUMBER

SAXC 03-1006

DD 1442, Block 6

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ ConstructionProjectDetails/ ConstructionProjectNumber/ “SAXC 03-1006”

XML Sample




<ConstructionProjectTitle>RENOVATIONS TO EXISTING WAREHOUSE FOR OFFICE SPACE</ConstructionProjectTitle><ConstructionProjectLocation>POLAND AVE WHARF, NEW ORLEANS, LA</ConstructionProjectLocation>

</ConstructionProjectDetails>…




<ConstructionProjectNumber>SAXC 03-1006</ConstructionProjectNumber></ConstructionProjectDetails>…


4.19 Signed Order CopiesWhen the contracting officer checks this box, the contractor is required to provide written acceptance of the Purchase Order before providing the materials for or beginning work on the contract and return the specified number of copies of the order.

Form Location

Form Block Number Block TitleDD 1155 16 TYPE OF ORDER/If this box is marked, supplier must sign Acceptance…

Sample Block

DD 1155, Block 16

Schema Location

Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ BasicInformation/ SignedOrderCopies/ “5”

XML Sample



…<SignedOrderCopies>5</SignedOrderCopies>…


Schema View


4.20 Multiple Line Items InformationCertain elements can have the same value for more than one line item. In this case, instead of repeating that element for each line item, the <MultipleLineItemsInformation> section can be used. The example below shows how the <MultipleLineItemsInformation> section can be used to specify Share Ratio information that is the same for two line items.

Form Location

N/A

Sample Block

N/A

Schema Location

Major Path: ProcurementDocument/ AwardInstrument/ ProcurementInstrumentHeader/ MultipleLineItemsInformation/ GroupShareRatio/

@ LineItemList/ DFARS/ LineItem/ CLIN/ “0002”@ LineItemList/ DFARS/ LineItem/ CLIN/ “0011”

@ ShareRatio/ GovernmentShare/ SharePercentage/ “70”@ ShareRatio/ ContractorShare/ SharePercentage/ “70”

XML Sample


…<MultipleLineItemsInformation>

<GroupShareRatio><LineItemList>

<DFARS><LineItem>

<CLIN>0002</CLIN></LineItem>

</DFARS><DFARS>

<LineItem><CLIN>0011</CLIN>

</LineItem></DFARS>

</LineItemList><ShareRatio>

<GovernmentShare><SharePercentage>70.0</SharePercentage>

</GovernmentShare><ContractorShare>

<SharePercentage>70.0</SharePercentage></ContractorShare>

</ShareRatio></GroupShareRatio>

</MultipleLineItemsInformation>…

Schema View


5 How to: Contract ModificationsThis section provides information about how to use a PDS XML document to modify a procurement instrument. It covers those elements on the SF 30 (Amendment of Solicitation/Modification of Contract) that are specific to contract modifications; the other elements on the SF 30 are covered in the “How To” section.

5.1 Modification NumberForm Location

Form Block Number Block TitleSF 30 2 AMENDMENT/MODIFICATION NUMBER

Sample Block

2. AMENDMENT/MODIFICATION NUMBER

FA5702-17-C-0029-A00001SF 30, Block 2

Schema Location

The modification number for an award is provided in the <ProcurementInstrumentModificationIdentifier> element of the <AwardModificationInstrument> portion of the schema.

Major Path: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentIdentifier/

@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Contract (Definitive)”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “FA5702”@ ProcurementInstrumentNumber/ Year/ “17”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “C”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “0029”@ ProcurementInstrumentNumber/ ProcurementInstrumentModificationIdentifier/ “A00001”@ ProcurementInstrumentDescription/ “Represented Contract”

XML Sample



<ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Contract (Definitive)</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>FA5702</EnterpriseIdentifier><Year>17</Year><ProcurementInstrumentTypeCode>C</ProcurementInstrumentTypeCode><SerializedIdentifier>0029</SerializedIdentifier><ProcurementInstrumentModificationIdentifier>A00001</ProcurementInstrumentModificationIdentifier>



Schema View

< AwardModificationInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentIdentifier> Section


5.1.1 Modification to a 4-digit OrderThere is one exception to the numbering policy described above. An older policy allowed the use of 4-digit order numbers. This example demonstrates how to number a modification to one of these older orders using the 4-digit <OrderNumber> element and the 2 digit <OrderModificationIdentifier> element.

Sample Block

2. AMENDMENT/MODIFICATION NUMBER

FA5702-17-C-0029-0001-01SF 30, Block 2

Schema Location

Major Path: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ProcurementInstrumentIdentifier/

@ ProcurementInstrumentOrigin/ “Department of Defense”@ ProcurementInstrumentVehicle/ “Delivery Order”@ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “SP4701”@ ProcurementInstrumentNumber/ Year/ “16”@ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “D”@ ProcurementInstrumentNumber/ SerializedIdentifier/ “0089”@ ProcurementInstrumentNumber/ OrderNumber/ “0001”@ ProcurementInstrumentNumber/ OrderModificationIdentifier/ “01”@ ProcurementInstrumentDescription/ “Represented Contract”

XML Sample




<EnterpriseIdentifier>SP4701</EnterpriseIdentifier><Year>16</Year><ProcurementInstrumentTypeCode>D</ProcurementInstrumentTypeCode><SerializedIdentifier>0089</SerializedIdentifier><OrderNumber>0001</OrderNumber><OrderModificationIdentifier>01</OrderModificationIdentifier>


</ProcurementInstrumentIdentifier>

5.2 Modification DetailsWhen a modification is issued, the <ModificationDetails> section of the PDS XML schema must be provided. This section includes details about which procurement instrument is being modified, descriptive information about the change and the reason for the change, relevant addresses, and information about who is authorizing the change.

5.2.1 Documents Being ModifiedThe procurement instrument identifiers for the document being modified is provided in the <DocumentsBeingModified> section of the schema.

Form Location

Form Block Number Block TitleSF 30 10 MODIFICATION OF CONTRACT/ORDER NUMBER and DATED

Sample Block

SF 30, Block 10

Schema View


5.2.1.1 Example 1: Modification against an Original ContractIf the modification is against a contract that has no previous modifications against it, one iteration of the <DocumentsBeingModified> section is provided.

Schema Location

Major Path: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ModificationDetails/ DocumentsBeingModified/

@ DocumentBeingModified/ ProcurementInstrumentOrigin/ “Department of Defense”@ DocumentBeingModified/ ProcurementInstrumentVehicle/ “Contract (Definitive)”@ DocumentBeingModified/ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “FA5702”@ DocumentBeingModified/ ProcurementInstrumentNumber/ Year/ “17”@ DocumentBeingModified/ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “C”@ DocumentBeingModified/ ProcurementInstrumentNumber/ SerializedIdentifier/ “0029”@ DocumentBeingModified/ ProcurementInstrumentDescription/ “Contract Being Modified - Award”@ DocumentBeingModifiedSignedDate/ “2017-12-09”

XML Sample


…<ModificationDetails>

<DocumentsBeingModified><DocumentBeingModified>

<ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Contract (Definitive)</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>FA5702</EnterpriseIdentifier><Year>17</Year><ProcurementInstrumentTypeCode>C</ProcurementInstrumentTypeCode><SerializedIdentifier>0029</SerializedIdentifier>

</ProcurementInstrumentNumber><ProcurementInstrumentDescription>Contract Being Modified – Award</ProcurementInstrumentDescription>

</DocumentBeingModified><DocumentBeingModifiedSignedDate>2017-12-09</DocumentBeingModifiedSignedDate>

</DocumentsBeingModified>…

</ModificationDetails>

5.2.1.2 Example 2: Modification against a Contract that has Previous Procurement and Administrative Modifications

If the modification is to a contract that already has modifications, an iteration must be provided for the last modification. If both procurement and administrative modifications already exist, two iterations must be provided – one for latest modification of each type.

Schema Location

Major Path: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ModificationDetails/ DocumentsBeingModified/

@ DocumentBeingModified/ ProcurementInstrumentOrigin/ “Department of Defense”@ DocumentBeingModified/ ProcurementInstrumentVehicle/ “Delivery Order”@ DocumentBeingModified/ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “N00019”@ DocumentBeingModified/ ProcurementInstrumentNumber/ Year/ “17”@ DocumentBeingModified/ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “F”@ DocumentBeingModified/ ProcurementInstrumentNumber/ SerializedIdentifier/ “0029”@ DocumentBeingModified/ ProcurementInstrumentNumber/ ProcurementInstrumentModificationIdentifier/ “P00003”@ DocumentBeingModified/ ProcurementInstrumentDescription/ “Contract Being Modified – PCO Modification”@ DocumentBeingModifiedSignedDate/ “2017-12-09”

@ DocumentBeingModified/ ProcurementInstrumentOrigin/ “Department of Defense”@ DocumentBeingModified/ ProcurementInstrumentVehicle/ “Delivery Order”@ DocumentBeingModified/ ProcurementInstrumentNumber/ EnterpriseIdentifier/ “N00019”@ DocumentBeingModified/ ProcurementInstrumentNumber/ Year/ “17”@ DocumentBeingModified/ ProcurementInstrumentNumber/ ProcurementInstrumentTypeCode/ “F”@ DocumentBeingModified/ ProcurementInstrumentNumber/ SerializedIdentifier/ “0029”@ DocumentBeingModified/ ProcurementInstrumentNumber/ ProcurementInstrumentModificationIdentifier/ “A00008”@ DocumentBeingModified/ ProcurementInstrumentDescription/ “Contract Being Modified – ACO Modification”@ DocumentBeingModifiedSignedDate/ “2013-02-02”


XML Sample

5.2.2 Description of ModificationA description of the modification must be provided.

Form Location

Form Block Number Block TitleSF 30 14 DESCRIPTION OF AMENDMENT/MODIFICATION

Sample Block

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

INCREMENTALLY FUND THE CONTRACT BY $165,000.00, THEREBY INCREASING THE TOTAL AMOUNT OBLIGATED FROM "$932,284.00" TO "$1,097,284.00".

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

SF 30, Block 14

Schema Location



<DocumentsBeingModified> <DocumentBeingModified>


<EnterpriseIdentifier>N00019</EnterpriseIdentifier><Year>17</Year><ProcurementInstrumentTypeCode>F</ProcurementInstrumentTypeCode><SerializedIdentifier>0029</SerializedIdentifier><ProcurementInstrumentModificationIdentifier>P00003<ProcurementInstrumentModificationIdentifier>

</ProcurementInstrumentNumber><ProcurementInstrumentDescription>Contract Being Modified – PCO Modification</ProcurementInstrumentDescription>


</DocumentsBeingModified><DocumentsBeingModified>

<DocumentBeingModified><ProcurementInstrumentOrigin>Department of Defense</ProcurementInstrumentOrigin><ProcurementInstrumentVehicle>Delivery Order</ProcurementInstrumentVehicle><ProcurementInstrumentNumber>

<EnterpriseIdentifier>N00019</EnterpriseIdentifier><Year>17</Year><ProcurementInstrumentTypeCode>F</ProcurementInstrumentTypeCode><SerializedIdentifier>0029</SerializedIdentifier><ProcurementInstrumentModificationIdentifier>A00008<ProcurementInstrumentModificationIdentifier>

</ProcurementInstrumentNumber><ProcurementInstrumentDescription>Contract Being Modified – ACO Modification</ProcurementInstrumentDescription>


</DocumentsBeingModified>…

</ModificationDetails>…

Path: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ModificationDetails/ ModificationDescription

XML Sample

Schema View

5.2.3 Project NumberIf a there is a Project Number for the contract being modified, it should be provided.

Form Location

Form Block Number Block TitleSF 30 5 PROJECT NUMBER

Sample Block

5. PROJECT NUMBER (if applicable)640-396

SF 30, Block 5

Schema Location

Path: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ModificationDetails/ ProjectNumber/ “640-396”


…<ModificationReason>

INCREMENTALLY FUND THE CONTRACT BY $165,000.00 , THEREBY INCREASING THE TOTAL AMOUNT OBLIGATED FROM "$932,284.00" TO "$1,097,284.00".

</ModificationReason>…

XML Sample

Schema View

5.2.4 Type of Modification and Modification AuthorityThis block indicates the type of the modification and the corresponding authority under which the modification is issued. It also indicates whether or not the contractor is required to sign the document.

Form Location

Form Block Number Block TitleSF 30 13 THIS ITEM APPLIES ONLY…

Sample Block

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE

X A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NUMBER IN ITEM 10A. 52.243-1 Alt II

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes is paying office, appropriation data, etc.) SET FORTH IN ITEM 14. PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor _X_ is not ___is required to sign this document and return __ copies to the issuing office.

SF 30, Block 13



…<ProjectNumber>640-396</ProjectNumber>…

</ModificationDetails>…

Schema LocationMajor Path: ProcurementDocument/ AwardModificationInstrument/ ProcurementInstrumentHeader/ ModificationDetails/ ModificationAuthority/

ContractorSignatureRequired/ “false”ChangeOrderAuthority/ “52.243-1 Alt II”

Note: The example above is for when 13A has been checked. The other checkboxes correspond to the following elements in the Schema:

13B: <AdministrativeChanges> 13C: <SupplementalAgreementAuthority> 13D: <OtherAuthority>

XML Sample

Schema View

5.3 Changing Existing Contract DataThere are two methods within the PDS schema for making changes to existing contract data. The method to use varies according to the location in the schema. The following sections describe these methods and provide some examples. Further examples are provided in the Business Rules Document.


…<ModificationAuthority>

<ContractorSignatureRequired>false</ContractorSignatureRequired><AdministrativeChanges>52.243-1 Alt II</AdministrativeChanges>

</ModificationAuthority>…

5.3.1 Method 1: Changing a Data Element or Section Using AttributesXML attributes are used to describe the addition, modification, or deletion of a data element or section.

5.3.1.1 Example 1: Modifying an Element Using Attributes

This example demonstrates changing the value of the <ContingencyContract> element from “true” to “false”. The attributes are:

changeFlag: indicates whether the element has been modified changeText: provides a description of the change previousValue: provides the old value for the element

Note: For optional elements, the changeFlag attribute has three possible values: “Added”, “Deleted”, and “Modified”. This is not the case for the <ContingencyContract> element. Since it is a required element with a single instance, it must always be present and can only be modified. Therefore, the only allowed value for the “changeFlag” attribute is “Modified”.

XML Sample

Schema View


…<ContingencyContract changeFlag="Modified" changeText="True to false" previousValue="true">

false</ContingencyContract>…

5.3.1.2 Example 2: Modifying a Section Using Attributes

This example demonstrates changing an instance of the <MiscellaneousTextDetails> section using attributes. The attributes are:

changeFlag: indicates that the value for the element has been added, modified, or deleted. changeText: provides a description of the change previousMiscellaneousText: provides the old value for <MiscellaneousText> element previousSection: provides the old value for <Section> element

XML Sample


…<MiscellaneousTextDetails changeFlag="Modified" changeText="Miscellaneous text Details are modified" previousMiscellaneousText="Allotment of Funds It is hereby understood and agreed that this contract will not exceed a total amount of $411,946.00." previousSection="G">

<MiscellaneousText>Allotment of Funds It is hereby understood and agreed that this contract will not exceed a total amount of

$511,946.00.</MiscellaneousText><Section>G</Section>

</MiscellaneousTextDetails>…

Schema View


5.3.1.3 Example 3: Deleting a Section Using Attributes

This example demonstrates deleting an instance of the <MiscellaneousTextDetails> section using attributes. In this case, only the “changeFlag” attribute is needed.

XML Sample

5.3.1.4 Example 4: Adding a Section Using Attributes

This example demonstrates adding an instance of the <MiscellaneousTextDetails> section using attributes. In this case, only the “changeFlag” attribute is needed.

XML Sample


…<MiscellaneousTextDetails changeFlag="Deleted">

<MiscellaneousText>Allotment of Funds It is hereby understood and agreed that this contract will not exceed a total amount of 411,946.00.

</MiscellaneousText><Section>G</Section>


…<MiscellaneousTextDetails changeFlag="Added">

<MiscellaneousText>Allotment of Funds It is hereby understood and agreed that this contract will not exceed a total amount of 411,946.00.

</MiscellaneousText><Section>G</Section>


5.3.2 Method 2: Providing Complete Section DetailsFor larger sections, complete details are provided for the added, deleted or changed sections. For changed sections, the details for the previous section must be provided along with the details for the current section. A description of the change is also required. Line Items and CDRLs use this method.

The example below is for the <ReferenceNumber> section.

XML Sample


…<ReferenceNumber> <AddedReferenceNumber>

<ReferenceDescription>Product Service Code</ReferenceDescription><ReferenceValue>1555</ReferenceValue><ReferenceSection>C</ReferenceSection>

</AddedReferenceNumber><AddedReferenceNumber>


</AddedReferenceNumber><DeletedReferenceNumber>


</DeletedReferenceNumber><ChangedReferenceNumber>

<ReferenceNumberChangeText>Updated: 1677 to 1725</ReferenceNumberChangeText><CurrentReferenceNumber>


</CurrentReferenceNumber><PreviousReferenceNumber>


</PreviousReferenceNumber> </ChangedReferenceNumber></ReferenceNumber>…

Schema View


5.4 Changing AmountsWhen changing amounts the delta between the old amount and the new amount must be provided. The example below demonstrates a change to an obligated amount using the <ObligatedAmountsModificationDetails> section of the schema.

XML Sample

Schema View


…<ObligatedAmountsModificationDetails>

<ChangedObligatedAmounts> <ObligatedAmountsChangeText>Changed from 110000.00 to 106750.00</ObligatedAmountsChangeText>

<ObligatedAmountDelta>-3250.00</ObligatedAmountDelta><CurrentObligatedAmount>

<ObligatedAmount>106750.00</ObligatedAmount>…

</CurrentObligatedAmount><PreviousObligatedAmount>

<ObligatedAmount>110000.00</ObligatedAmount>…

</PreviousObligatedAmount></ChangedObligatedAmounts>

</ObligatedAmountsModificationDetails>…