EUHW Attch 13, GOMO Interface Control Document (ICD) FINAL.docx

GOMO Interface Control Document (ICD) s

NAVAL ENTERPRISE NETWORK PROGRAM

UNITED STATES NAVY

Solicitation: N00039-18-R-0004 Attachment 13, GOMO Interface Control Document (ICD)

Version: 1.0 Date: 17 September 2018

Program Executive Office Enterprise Information Systems Program Manager, Naval Enterprise Networks 1325 10th Street, SE, Suite 301 Washington, DC 20374

Table of Contents

GOMO Interface Control Document

Document Version History

Introduction

Service Order Management is the planning, submission, review, funding, approval, receipt, delivery (to include initial ordering, modification, discontinuance, and cancellation of services), validation, and reporting on services contained in the Service Catalog in the Government Owned and Managed Ordering (GOMO) Application. GOMO Application represents the current and future Navy Marine Corps Intranet (NMCI) Enterprise Service Tool (NEST) which includes but is not limited to, the Requirements Award Process Tool (RAPT) and NMCI Enterprise Tool (NET). The Contractor shall integrate their applications with GOMO application as within 90 days of completing the certification and accreditation process. This document describes the current outgoing and incoming interfaces between NEST and the vendor’s corresponding endpoints. The document will outline the three required NEST interfaces: task order, delivery, and service request. Additional interfaces will be established based on requirements found during the transition period. All interface details are based on the current environment, the vendor will be notified of any changes in structure during transition and will be required to update accordingly. In addition, all interfaces must be DFARS compliant.

In order to maximize compatibility across disparate hardware and technology platforms, these interfaces follow industry standards for RESTful (Representational State Transfer) communication between endpoints. Each interface employs multiple levels of security that comply with established industry standards and best practices to ensure cross-platform compatibility between the DON and vendor systems. While NEST is primarily developed using the Microsoft technology stack, the communication protocols are intended to be compatible with both Microsoft development tools and Java-based platforms on both Windows and UNIX-based hardware environments. The following documentation and guidelines will allow a vendor to develop a functioning interface with NEST.

Purpose

This document defines the high-level framework that will be used to support submission of task order, delivery, and service request XML/JSON data from NEST to a vendor system. The Interface Control Document (ICD) provides information on how the NEST external data transfer framework transmits messages to vendor endpoints and describes standard data load formats required for transmission.

In addition to the data transmission capability from NEST to a vendor system, a similar secure RESTful web service is available using industry standards to transmit a standard XML message from a vendor back to NEST. These XML messages are validated using XSD schema definitions to ensure the validity of both the format and the content of the incoming message.

Scope

The ICD provides details of the NEST external file and message transfer process and information on how NEST will provide task order, delivery, and service request data to different vendors. Additionally, the ICD includes inbound interface requiements detailing the specifications of the corresponding vendor to NEST interfaces.

Intended Audience

This document is to be leveraged by vendors, technical development team members, technical architects, and database designers that support the development of the vendor endpoints for the NEST interface.

Assumptions

This document makes the following assumptions:

· The hardware environment and network connectivity between NEST servers and vendor endpoints are established and maintained. The actual architecture of the network connectivity between endpoints is described at a high level and supports a variety of configurations, but the detailed specifics of an architectural network design are beyond the scope of this document. There are a variety of industry-standard technologies for establishing secure communications between two endpoints using VPN technologies and appliances. There is nothing inherent in the technical information within this ICD that would preclude the use of these additional technologies to further enhance the security infrastructure.

· Pre-determined file format specifications are maintained. The XML and JSON message content is designed to be flexible and to allow for communications of new requests and their corresponding status. Messages which do not conform to the definitions defined here cannot and will not be processed and will generate an error back to the sending system.

· Pre-determined file transmission procedures are maintained. End-to-end communication requires monitoring and alert mechanisms when links are broken or experience temporary anomalies. The monitoring and control of communication links is outside the scope of this document and is assumed to be part of any production infrastructure.

Key POCs

SME

PM Tim Savoy

Overall Design of NEST Interfaces

The following specifications outline the general design of the task order, delivery, and service request interfaces with NEST. These specifications are common across each of the three interfaces; further interface-specific details are provided in sections 4, 5, and 6.

NEST-to-Vendor Interface Design

The communication interface between endpoints will be REST-based and will follow industry standards for communication via HTTPS. Security will be further enhanced by the required use of security certificates, as well as a username and password exchange, to comply with DoD security standards and follow industry best practices.

NEST External Data Transfer Process

NEST implements a custom data transfer framework with the ability to send transmissions to external destinations. While this infrastructure supports various legacy interfaces, the primary protocol used for all vendor communications will be REST. The infrastructure described below has built-in recovery and retry logic to further ensure reliable communications.

An external data transfer within NEST consists of three main components: the transmission request, the transmission destination, and the transmission log. These components are integrated with the database, which allows for programmability of the transfer entities. Through the implementation of a transfer service, the system uses a transfer destination type to determine the destination and format of the data. Each vendor will be configured as a destination with an appropriate certificate, username, and password.

The NEST outbound transmission service is designed to be resilient and persistent, with configurable and automatic retries when a vendor endpoint is temporarily unavailable. It is also adaptable to allow the use of multiple protocols that can be selected to transmit the same XML or JSON-based content in a “near-real-time” environment. However, for all inbound vendor communications, only the REST protocol is supported and is a requirement for sending and receiving all applicable data to NEST.

Vendors have flexibility in tuning the automatic retry logic for their endpoint, which also controls the throttling of concurrent connections to their servers to keep the message flow within the performance capabilities of the deployed endpoint hardware. The following table outlines the protocols NEST’s data transfer framework supports.

Protocols Supported

Authentication

NEST will use a vendor-supplied user id, password, and client certificate to access the vendor endpoint and submit the applicable data.

Likewise, NEST will provide a client certificate to be installed on the vendor’s endpoint server for the vendor endpoint to authenticate with NEST.

NEST-to-Vendor Data Transfer Layout

NEST is hosted on the Navy/Marine Corps Intranet (NMCI) Network and is compatible with various vendor environment configurations. The following configurations are supported:

1. Vendor system is hosted on the NMCI Network

2. Vendor system is hosted external to NMCI Network and is accessible through a firewall

3. Vendor system is hosted external to NMCI Network and is accessible via Enterprise Middleware

NEST and Vendor System Connectivity

Regardless of vendor endpoint configuration, it is likely that there will be firewalls to isolate each endpoint. These firewalls need to be configured to allow HTTPS connectivity on the agreed upon port number, and can be further configured to allow access to specific IP addresses or ranges of IP addresses for failover. When data leaves one environment to enter another environment, it must always be encrypted using the HTTPS protocol. Authentication and authorization will be accomplished via the exchange of certificates and login credentials.

The diagram below contains the general architectural components and data flow that will occur, using either a secure connection over the public internet or a private line. The flexible use of open standards will allow network design engineers to determine the optimal configuration for a specific environment.

The NEST server is responsible for communicating data to vendors and for processing incoming data. This server may optionally leverage the use of an enterprise middleware for communications.

Once data leaves the application server, it is secured and in most configurations will be transmitted between both a DoD firewall and a vendor-supplied firewall before reaching the vendor’s endpoint. This transmission may occur through the public Internet, a VPN connection, a private leased line, or some combination for establishing IP-based connectivity between environments.

Vendor-to-NEST Interface Design

NEST will provide a standard REST web service endpoint to accept vendor status data. This web service will be implemented using NET 4.5x framework and will be hosted on an IIS server. This web service will be available for consumption directly or via middleware.

Authentication

The vendor’s system will use the NEST system supplied user id, password, and a client certificate to access the NEST endpoint and submit the vendor confirmation data.

The vendor will also provide a client certificate that will be installed on the NEST endpoint server so the remote endpoint can authenticate the vendor’s system.

Vendor-to-NEST Data Transfer Layout

The three network configurations supported for outbound messages are also supported for inbound messages sent to NEST from the external vendor systems. These include environments where the vendor system is hosted:

1. On the same network as NEST within the Navy’s NMCI infrastructure

2. On a remote server external to the NMCI network

3. On a remote server where access is via an enterprise data transfer layer

NEST Task Order Interface Design

The task order interface will serve as the notification process to identify new and/or modified task orders that are approved in NEST and ready for obligation. The interface allows NEST to send outbound task order data as well as receive inbound vendor response data.

NEST-to-Vendor Interface

This section describes the NEST-to-vendor outbound interface for task orders. This interface will send a single Procurement Data Standard (PDS) XML-formatted message with new and/or modified task order details in near-real-time as the task order is approved and is ready for vendor delivery and fulfillment. Vendors are provided with the XSD in order to validate these messages prior to processing.

Outbound Message Data Format

Procurement Data Standard (PDS) Schema NEST routinely processes the request and approval of new and/or modified task orders. Once a task order is ready for obligation, the task order is communicated to the vendor using a PDS XML message. The PDS order data will conform to the following XML schema.

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

Vendor-to-NEST Interface

After PDS task order data is sent to the vendor’s system, NEST expects to receive a response verifying that the information has been validated and sucsessfully loaded into the vendor tool. Vendors are provided the XSD in order to correctly formulate these response messages.

Inbound Message Data Format

Procurement Data Standard (PDS) Response Schema After validating the task order data sent from NEST, the vendor system will send a response message back to the tool. The PDS Response message will conform to the following XML schema.

https://www.acq.osd.mil/dpap/pdi/eb/procurement_data_standard.html NEST Delivery Request Interface Design

The delivery request interface will allow NEST to submit delivery requests for vendor fulfillment and allow the vendor to post delivery request status updates back to NEST.

NEST-to-Vendor Interface

This section describes the NEST-to-vendor outbound interface for delivery requests. This interface will send a single XML formatted message with new delivery request details in near real-time as a new delivery request is approved and is ready for vendor fulfillment. Vendors are provided with the XSD in order to validate these messages prior to processing.

Outbound Message Data Format

Once a delivery request is approved and ready for vendor fulfillment, the request is communicated from NEST to the vendor using an XML message. All new delivery requests will conform to the same XML schema but can be broken down into two main categories:

Delivery Request New – a notification of a new NET delivery request

1. Account Delivery Requests

2. Service Delivery Requests

Vendor-to-NEST Interface

After a delivery request data is sent successfully to the vendor’s system, NEST expects to receive status updates for the delivery request each time there is a change in its status.

Inbound Message Data Format

The vendor can send multiple status updates for each delivery request as it is processed by the vendor through various stages of the delivery process. The vendor delivery request update XML schema provides a means to communicate these various status events:

The vendor shall send rejection reasons, detailed rejection comments, and vendor POC information (for the vendor rejecting the service/account) when sending rejected services/accounts back to NEST. The vendor will utilize the standard listing of rejection reasons listed below:

Rejection Reasons:

1. Service Request User Information Missing/Invalid Examples of missing user information include:

a. NMCI email provided but cannot match to users in user directory (currently active directory)

2. Account Request User Information Missing/Invalid

3. Delivery POC Information Missing/Invalid (from Delivery POC assigned in Delivery Request Header) Examples of missing POC information include:

a. Address in invalid for specified delivery POC

4. Service Location Information Missing/Invalid

5. Service ID Missing/Invalid

6. Seat Refresh Request Missing Asset ID

7. CLIN Invalid

8. CLIN is End of Life

9. Account Request Contains Duplicate EDIPI

10. User Cancelled Delivery Request (reference ticket # or email/phone call, and/or user name)

11. Delivery Request Cancelled (reference ticket #)

12. Other Please utilize the 'Other' rejection reason if rejection reason is not listed above, or if your rejection is due to multiple rejections listed above.

** all delivery request rejection reasons will also require comments from vendor regarding specific rejection situation ** vendors will be required to provide vendor contact information for the POC who is rejecting the service/account on the vendor side ** Additional rejection reasons to be determined once vendors have finalized service/account data requirements for NGEN-R contracts. Examples of these additional rejection reasons include, but are not limited to:

9. Services are not mapped/are incorrectly mapped

The detailed rejection comments should be detailed enough so that users know what actions they need to take to appropriately correct rejected service/account information and send back to vendor. The vendor POC information provided should include the vendor name, phone number, and email address for the corresponding POC that is rejecting the service/account.

NEST Service Request Interface Design

A service request occurs when there is a change or addition to the services that are delivered to the end user or to a seat. The service request interface will allow NEST to submit service requests for vendor fulfillment and allow the vendor to post service request status updates back to NEST.

NEST to Vendor Interface

This section describes the NEST to vendor outbound interface for service requests. This interface will send a single XML formatted message with new service request details in near real-time as a new service request is approved and is ready for vendor buildout and fulfillment. Vendors are provided with the XSD in order to validate these messages prior to processing.

Outbound Message Data Format

Service requests are submitted by Customer Technical Representatives (CTRs) on behalf of the end users who are receiving the services. There are two common types of changes: 1) an ‘admin’ change that can be fulfilled by logical means and 2) a ‘physical’ change which will require hands-on intervention.

The schema for a Service Request Update follows:

Vendor-to-NEST Interface

After service request data is sent successfully to the vendor’s system, NEST expects to receive status updates for the service request each time there is a change in its status. This data is captured for reporting and to track service request and service fulfillment performance.

Inbound Message Data Format

The vendor can send multiple service status updates for each service request and service as it is processed by the vendor through various stages of the delivery process. The vendor service request response XML schema provides a means to communicate these various status events:

image1.png image3.png image4.emf

PDS_Schema_v2.5.1.xsd

Level 1: top level of Procurement Data Standard for a procurement instrument document.

The root element for any procurement instrument document

The version of the Procurement Data Standard schema used to produce the procurement instrument. (see list)

The Standard (SF) or Department of Defense (DD) form used to render a copy of the procurement instrument. (see list)

Information about the system producing the procurement document.

The internal system identifier of the document by which it is tracked by the system referenced by the DITPR Number.

Identifies the Department of Defense system or application used to generate the XML document.

The DoD Information Technology Portfolio Repository (DITPR) Number assigned to the application or system that generated the XML document.

The DoDAAC of the entity that administers the application or system that generated the XML document.

Identifies the system or application used to generate the XML document when it is not a Department of Defense system or application.

The CAGE, DUNS, Activity Address Code or other identifier of the organization who administers the application or system. This may or may not be the same entity that uses the application or system.

The Activity Address Code (AAC).

CAGE: Commercial and Government Entity

DUNS+4: Data Universal Numbering System identifier with four character suffix.

DUNS: Data Universal Numbering System Identifier.

Use to provide an identifier that isn't provided as a distinct element.

The name of the application or system.

The version of the application or system.

The award instrument.

The award modification instrument or the solicitation amendment.

Enumeration list for Acceptance and Inspection Action

Enumeration list for Acceptance and Inspection Location

Enumeration list for Effort Category

Enumeration list for Change Flag: add, delete

Enumeration list for Change Flag: add, delete, modify

Enumeration list for Change Flag: modify

Enumeration list for Document Purpose

Enumeration list for DoD Multi-Agency

Enumeration list for Payment Method

Enumeration list for Limit Description

Enumeration list for Not Full and Open Competition

Enumeration list for Payment Method

Enumeration list for Period Description

Enumeration list for the Procurement Description

Enumeration list for the Procurement Instrument Origin

Enumeration list for the Procurement Instrument Type Code

Enumeration list for the Transmission Acknowledgement

For Modifications and Amendments, captures additions and deletions with change text to an element.

For Modifications and Amendments,, captures additions and deletions without change text to an element

For Modifications and Amendments, captures changes to a date element.

For Modifications and Amendments, captures changes to an DoDAAC element.

For Modifications and Amendments, captures changes to a positive integer element.

For Modifications and Amendments, captures changes to an integer element.

For Modifications and Amendments, captures changes to a string element.

For Modifications and Amendments, captures changes to a TrueType element.

For Modifications and Amendments, captures changes to a required TrueFalseType element.

For Modifications and Amendments, captures changes to an optional TrueFalseType element.

Records changes to the Award Instrument Security Level element

Records changes to the Effort Category element

Records changes to the Document Purpose element

Records changes to the DoD Multi Agency element

Records changes to the Not Full and Open Competition element

Records changes to the Special Handling Code element

Records changes to the Transmission Acknowledgement element

Records changes to the Transportation Method element

Records changes to the Transportation Service Level element

Records changes to an Acceptance and Inspection section

Records changes to the Currency section

Records changes to an Estimated Quantity section

Records changes to an Estimated Quantity section

Records changes to an Order Variation/Percentage section

Records changes to a Procurement Instrument Identifier section

Records changes to the Group Item Other Amounts section

Records changes to the Hazardous Material section

Records changes to a Limits section

Records changes to the Miscellaneous Text section

Records changes to an Order Variation/Percentage section

Records changes to the Order Variation/Quantity section

Records changes to the Other Amounts section

Records changes to an Pricing Arrangement section

Records changes to a Procurement Instrument Identifier section

Records changes to a Procurement Instrument Identifier and Number section

Award Instrument document

Data common to the entire procurement instrument.

The line item information of the procurement instrument.

Information about a Contract Data Requirements List (CDRL).

Information about contract line items.

Award Modification Instrument or Solicitation Amendment Document.

Data common to the entire procurement instrument.

The line item information of the procurement instrument.

Information about added, changed, and deleted Contract Data Requirements List (CDRL).

Contains CDRLs that were added.

Contains CDRLs that were removed.

Contains CDRLs that were modified.

Description of the change to the CDRL.

The CDRL after the change was applied. The result.

The CDRL before the change was applied. The original.

Information about added, changed, and deleted line items.

Contains line items that were added.

Contains line items that were removed.

Contains line items that were modified.

Descriptive text of the changes made to the line item by UCF section.

Description of the line item change that applies to the section/division provided in CSI Dvision, CSI Section, or Section.

The line item after the change was applied. The result.

The line item before the change was applied. The original.

Award Address structure

Type of addresses. (see list)

Description of the address when not covered by one of the address description options.

The address and organization identifiers.

A contact for the organization/address.

Provides acceptance and/or inspection instructions when the address denotes an entity performing acceptance, inspection, or both.

Seller's business classification such as Hospital, Large, Small, etc.

Dates other than delivery, used in award header only.

Effective date of the procurement instrument. Date in CCYY-MM-DD format. Required on an award.

A period of time applicable to the procurement instrument.

The Contracting officer's name, contact information, and signature date. The signature date is also known as the Award date. Required on an award.

The Contractor's name, contact information, and signature date. May only have more than one when Procurement Instrument Form is SF 252.

Delivery structure used in an award document.

Dates or date ranges that relate to a delivery.

Delivery lead time information.

Information on Special handling and hazardous material.

Action to be taken when the maximum total order amount is exceeded by the contractor.

Indicates consignee or a shipping contact must be notified to schedule a delivery.

Specify transportation special handling instructions and Hazardous material information.

Contains special transportation handling instructions. (see list)

Use to provide the Hazardous Material Class Code and its source.

Contains relevant information that cannot be provided elsewhere.

Ordering discount structure used in an award document.

General discounts applicable to the award instrument.

Discounts based on a range or a threshold.

Basic information for a procurement instrument.

The type of response required upon receipt of an electronic copy of the draft procurement instrument (pre-signature). (see list)

The category of the procurement instrument. (see list)

Reference line 17 of Synopsis in FAR 5.203

The common name by which the procurement instrument is referenced.

Selected if the procurement instrument is a contingency contract.

The purpose of the procurement instrument. (see list)

Denotes whether or not the procurement instrument is an Emergency action requiring expedited processing by the selling party.

Text relating to the procurement instrument that cannot be captured as discrete elements.

Competition in Contracting Act (CICA) authority for using other than full and open competition. (see list)

Highest government security classification to the procurement instrument. (see list)

The number of copies to be returned to indicate acceptance of the order.

Provides parameters for orders on an indefinite delivery contract or other ordering instrument.

Pricing arrangement type applicable to the procurement instrument. (FAR Part 16)

The government and contractor share ratios.

Miscellaneous information about solicitations, bids, and offers that pertain to the procurement instrument.

Addresses that apply to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Addresses applicable to the line item grouping.

One or more clauses that apply to a group of procurement instrument items.

A list of two or more procurement instrument line items.

The details about a clause.

A discount that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

The details about the discount.

Labor rates that apply to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Miscellaneous text that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Text relating to the procurement instrument that cannot be captured as discrete elements.

Amounts other than obligated amounts that apply to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Replacement price that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Requirements description that applies to a group of procurement instrument line items.

A list of two or more contract line items.

Uniform Contract Format (UCF) Section C. Any description or specifications needed in addition to UCF Section B. (This carries statements of objectives, performance work statements, statements of work and similar text descriptions when not separated in an attachment. Specific numbered specifications, standards, and other standardized descriptive data is handled separately under Product or Service Identifiers and Reference Numbers)

Share ratio that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Special pricing that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Variable pricing that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

The details about the variable pricing.

Zone pricing that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

Wage determination that applies to a group of procurement instrument line items.

A list of two or more procurement instrument line items.

The estimated total quantity to be ordered. The actual order quantity may be higher or lower.

Used to indicate ordering limits on the procurement instrument.

Specifies which entities are allowed to place orders against the procurement instrument.

Orders can be placed by any entity within the United States Government.

Orders may be placed by the specified DoD Agencies. (see list)

Orders can be placed by any entity within the United States Department of Defense.

Orders may be placed by specific entities only.

Permitted variations in quantity.

Response Time in number of days within which the contractor must reject an order exceeding the maximum order limits.

Variation expressed as a discrete quantity.

The quantity by which the order can be below the expected quantity.

The quantity by which the order can be above the expected quantity.

The unit of measure. (see list)

Variation expressed as a percentage.

Express 4.25% as 4.25

Express 4.25% as 4.25

Award amount structure

Currencies that apply to the procurement instrument.

The buying and/or payment currencies that apply to an award or award modification.

The currency requirements for a solicitation response.

Denotes that any currency may be used in the response. (see list)

Denotes that the response must be in US dollars. (see list)

The textual name of the foreign currency that must be used in the response (may include US Dollar). See ISO 4217 from the International Organization for Standardization for the correct values.

Taxes that apply to the total order amount.

Obligation amount. Must be greater than zero.

Amounts other than obligated amounts.

Details about a procurement instrument number as well as the procurement instrument number. For award/original document only.

Federal/ DoD Agency or Service from where the procurement instrument is originating. (see list)

Procurement instrument vehicle like a Schedule etc. (see list)

Procurement Instrument Number defined following the rules of the applicable agency and/or vehicle.

Use when the procurement instrument is non-Department of Defense and cannot be mapped using the separate fields under Procurement Instrument Number.

Describes the relationship of the procurement instrument listed to the procurement instrument represented in the transaction. (see list)

When Transportation Method contains "Pipeline", provide the Department of Defense Activity Address Code (DoDAAC) of the pipeline."

Method or type of transportation. (see list)

Level of transportation service or billing service offered by the carrier. For emergency orders, the transportation requirements. (see list)

Shipping details structure. For award/original documents only.

indicates partial shipments will not be accepted.

Indicates whether or not the item(s) will be shipped in place.

Marks and numbers assigned to shipment containers.

Freight on Board information.

High level packaging requirements.

Transportation information

Captures solicitation and Offer/Bid information that appears on an award/mod document.

The number of days from the date for receipt of offers or bids that, if the government accepts the offer/bid in that time, 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.

Provide when the solicitation incorporates by reference FAR 52.212-1 and 52.212-4; and Far 52.212-3 and 52.212.5 are attached.

The type of award instrument that is expected to be issued such as Blanket Purchase Agreement. (see list)

When FMS Solicitation is provided, contains the Foreign Military Sales Case Number if known.

Denotes that the solicitation is for Foreign Military Sales (FMS). (see list)

Solicitation conditions that are applicable to all line items. (see list)

Denotes that a multi-year contract will be awarded. (see list)

Code from the North American Industry Classification System (NAICS)

When provided, denotes that an offer guarantee is required. (see list)

The number of calendar days after award that Performance and Payment Bonds must be furnished.

Qualification requirements pertinent to the solicitation. (see list)

If the contractor is required to sign the solicitation document, provide the number of copies he must provide to the issuing office.

The threshold of employees or amount the offeror/bidder must meet to respond to the solicitation.

Number of employees.

Total income in whole figures; for example, 6000.

Date the solicitation was issued in CCYY-MM-DD format.

The type of solicitation such as RFP, RFQ, or IFB.

The list of amendments to the solicitation that the offeror/bidder acknowledges receiving.

The solicitation amendment number. Must be 4 numeric digits between 0001 and 9999.

The date the amendment became effective. (Use CCYY-MM-DD format, where CC stands for century.)

Information on where bids or offers are to be delivered such as number of copies, due date, etc.

The number of sealed copies of the bid or offer that must be provided.

Describes the place where offers or bids are taken when hand carried.

Date and time by which a bid or offer must be delivered.

The name, title, and signature date of the offeror or bidder.

Provides set aside percentage and organization type. If not provided, the solicitation is unrestricted.

Person or entity that is the contact for the solicitation.

Dates that are relevant to a solicitation.

Categorizes the date relevant to a solicitation. (see list)

A date (and time) relevant to the solicitation.

If needed, contains additional information about the date on the solicitation.

Information on wage determinations.

Wage determination information under the Davis-Bacon Act.

Wage determination information under the Service Contract Act.

Award Modification and Solicitation Amendment Address structure.

Type of addresses being changed. (see list)

Description of the address when not covered by one of the address description options.

Records addresses and contacts that have been added, removed, or modified.

Contains addresses that are added.

Contains addresses that are removed.

Contains addresses that are modified.

Description of the change to the address and contacts.

The address and contacts after the changes were applied. The results.

The address and contacts before the changes were applied. The original.

Records changes to acceptance and/or inspection instructions when the address denotes an entity performing acceptance, inspection, or both.

Records changes to a seller's business classification such as Hospital, Large, Small, etc.

Contains the business classification that is added.

Contains the business classification that is removed.

Contains the business classification that is modified.

Description of the change to the business classification.

The business classification after the changes were applied. The results.

The business classification before the changes were applied. The original.

Contains clauses or provisions that are added.

Contains clauses or provisions that are removed.

Contains clauses or provisions that are modified.

Description of the change to the clause or provision.

The clause or provision after the changes were applied. The results.

The clause or provision before the changes were applied. The original.

Dates other than delivery, used in modification and amendment header only.

Effective date of the represented procurement instrument. Date in CCYY-MM-DD format.

The Contracting officer's name, contact information, and signature date. The signature date is also known as the Award date.

The Contractor's name, contact information, and signature date. May only have more than one when Procurement Instrument Form is SF 252.

Delivery structure used in an award modification or solicitation amendment document.

Dates or date ranges that relate to a delivery.

Contains delivery dates that are added.

Contains delivery dates that are removed.

Contains delivery dates that are modified.

Description of the change to the delivery date.

The delivery date after the change was applied. The result.

The delivery date before the change was applied. The original.

Delivery lead time information.

Contains lead time information that is added.

Contains lead time information that is removed.

Contains lead time information that is modified.

Description of the change to the lead time information.

The lead time information after the change was applied. The result.

The lead time information before the change was applied. The original.

Information on Special handling and hazardous material.

Action to be taken when the maximum total order amount is exceeded by the contractor.

Indicates consignee or a shipping contact must be notified to schedule a delivery.

Specify transportation special handling instructions and Hazardous material information.

Contains special transportation handling instructions. (see list)

Use to provide the Hazardous Material Class Code and its source.

Contains relevant information that cannot be provided elsewhere.

Ordering discount structure used in an award modification or solicitation amendment document.

Records changes to the general discounts.

Contains general discounts that are added.

Contains general discounts that are removed.

Contains general discounts that are modified.

Description of the change to the general discount.

The general discount after the changes were applied. The results.

The general discount before the changes were applied. The original.

Records changes to discounts based on a range or a threshold.

Contains discounts based on a range or threshold that are added.

Contains discounts based on a range or threshold that are removed.

Contains discounts based on a range or threshold that are modified.

Description of the change to the discounts based on a range or threshold.

The discounts based on a range or threshold after the changes were applied. The results.

The discounts based on a range or threshold before the changes were applied. The original.

Basic information for a procurement instrument.

The type of response required upon receipt of an electronic copy of the draft procurement instrument (pre-signature). (see list)

The category of the procurement instrument. (see list)

Reference line 17 of Synopsis in FAR 5.203

The common name by which the procurement instrument is referenced.

Selected if the procurement instrument is a contingency contract.

The purpose of the procurement instrument. (see list)

Denotes whether or not the procurement instrument is an Emergency action requiring expedited processing by the selling party.

Text relating to the procurement instrument that cannot be captured as discrete elements.

Competition in Contracting Act (CICA) authority for using other than full and open competition. (see list)

Highest government security classification to the procurement instrument. (see list)

Provides parameters for orders on an indefinite delivery contract or other ordering instrument.

Pricing arrangement type applicable to the procurement instrument. (FAR Part 16)

The government and contractor share ratios.

Miscellaneous information about solicitations, bids, and offers that pertain to the procurement instrument. May only be used when amending a solicitation procurement instrument.

Labor Rates used in an award modification document.

Contains labor rates that are added.

Contains labor rates that are removed.

Contains labor rates that are modified.

Description of the change to the labor rates.

The labor rates after the changes were applied. The results.

The labor rates before the changes were applied. The original.

Description of the change to the line item list.

The line item list after the changes were applied. The results.

The line item list before the changes were applied. The original.

Miscellaneous text used in an award modification or solicitation amendment document.

Contains the miscellaneous text for a section that is added.

Contains the miscellaneous text for a section that is removed.

Contains the miscellaneous text for a section that is modified.

Description of the change to the miscellaneous text.

The miscellaneous text after the changes were applied. The results.

The miscellaneous text before the changes were applied. The original.

Records changes to the effective date of the procurement instrument being modified. Date in CCYY-MM-DD format.

Records changes to a period of time applicable to the procurement instrument being modified.

Changes to addresses that apply to a group of procurement instrument line items. Include changes to the group of contract line items.

Use when the only change for an address group is to the list of line items. The addresses are unchanged.

Use when the only change is to the set of addresses. The line item list is unchanged.

The line item list to which the addresses being modified are associated.

Records address information that has been added, removed, or modified.

Use when both the addresses and the line item list of the group addresses changes.

Records line items that have been added, removed, or modified.

Records address information that has been added, removed, or modified.

Changes to clauses that apply to a group of contract line items. Include changes to the group of procurement instrument line items.

Use when the only change for a clause group is to the list of line items. The clauses are unchanged.

Use when the only change is to the set of clauses. The line item list is unchanged.

The line item list to which the clauses being modified are associated.

Records clauses that have been added, removed, or modified.

Use when both the clauses and the line item list of the group changes.

Records line items that have been added, removed, or modified.

Records clauses that have been added, removed, or modified.

Changes to discounts that apply to a group of procurement instrument line items.

Use when the only change for a discount group is to the list of line items. The discounts are unchanged.

Use when the only change is to the set of item discounts. The line item list is unchanged.

The line item list to which the discounts being modified are associated.

Records discounts that have been added, removed, or modified.

Use when both the discounts and the line item list of the group changes.

Records line items that have been added, removed, or modified.

Records discounts that have been added, removed, or modified.

Changes to labor rates that apply to a group of procurement instrument line items.

Use when the only change for a labor rates group is to the list of line items. The labor rates are unchanged.

Use when the only change is to the labor rates. The line item list is unchanged.

The line item list to which the labor rates being modified are associated.

Records labor rates that have been added, removed, or modified.

Use when both the labor rates and the line item list of the group labor rates changes.

Records line items that have been added, removed, or modified.

Records labor rates that have been added, removed, or modified.

Changes to miscellaneous text that applies to a group of procurement instrument line items.

Use when the only change for a miscellaneous text group is to the list of line items. The miscellaneous text is unchanged.

Use when the only change is to the miscellaneous text. The line item list is unchanged.

The line item list to which the miscellaneous text being modified is associated.

Records miscellaneous text that has been added, removed, or modified.

Use when both the miscellaneous text and the line item list of the group changes.

Records line items that have been added, removed, or modified.

Records miscellaneous text that has been added, removed, or modified.

Changes to amounts other than obligated amounts that apply to a group of procurement instrument line items.

Use when the only change for an other amounts group is to the list of line items. The other amounts are unchanged.

Use when the only change is to the other amounts. The line item list is unchanged.

The line item list to which the other amounts being modified is associated.

Records the other amounts that has been added, removed, or modified.

Use when both the other amounts and the line item list of the group changes.

Records line items that have been added, removed, or modified.

Records the other amounts that has been added, removed, or modified.

Changes to the replacement price that apply to a group of procurement instrument line items.

Use when the only change for a replacement price group is to the list of line items. The replacement price is unchanged.

Use when the only change is to the replacement price. The line item list is unchanged.

The line item list to which the replacement price being modified is associated.

Records the replacement price that has been added, removed, or modified.

Use when both the replacement price and the line item list of the group replacement price changes.

Records line items that have been added, removed, or modified.

Records the replacement price that has been added, removed, or modified.

Changes to Requirements Descriptions that apply to a group of procurement instrument line items. Uniform Contract Format (UCF) Section C. Any description or specifications needed in addition to UCF Section B. (This carries statements of objectives, performance work statements, statements of work and similar text descriptions when not separated in an attachment. Specific numbered specifications, standards, and other standardized descriptive data is handled separately under Product or Service Identifiers and Reference Numbers)

Use when the only change for a requirements description group is to the list of line items. The requirements description is unchanged.

Use when the only change is to the requirements description. The line item list is unchanged.

The line item list to which the requirements description being modified is associated.

Records a requirements description that has been added, removed, or modified.

Use when both the requirements description and the line item list of the group changes.

Records line items that have been added, removed, or modified.

Records a requirements description that has been added, removed, or modified.

Changes to the share ratio that applies to a group of procurement instrument line items.

Use when the only change for a share ratio group is to the list of line items. The share ratio is unchanged.

Use when the only change is to the share ratio. The line item list is unchanged.

The line item list to which the share ratio being modified is associated.

Records the share ratio that has been added, removed, or modified.

Use when both the share ratio and the line item list of the group share ratio changes.

Records line items that have been added, removed, or modified.

Records the share ratio that has been added, removed, or modified.

Changes to the special pricing that apply to a group of procurement instrument line items.

Use when the only change for a special pricing group is to the list of line items. The special pricing is unchanged.

Use when the only change is to the special pricing. The line item list is unchanged.

The line item list to which the special pricing being modified is associated.

Records the special pricing that has been added, removed, or modified.

Use when both the special pricing and the line item list of the group special pricing changes.

Records line items that have been added, removed, or modified.

Records the special pricing that has been added, removed, or modified.

Changes to variable pricing that applies to a group of procurement instrument line items.

Use when the only change for a variable pricing group is to the list of line…