Department of Defense Catalog Data Standard Draft Public Meeting Overview
The Department of Defense is hosting a public meeting on December 6, 2022, to discuss the draft Catalog Data Standard. The meeting will cover administrative matters, submission of comments, technical architecture, and open discussions on use cases. Attendees are encouraged to provide input on areas such as schema structure, enumerations, and concept of operations. Feedback can be submitted online under Docket Number DARS-2022-0028.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Department of Defense Catalog Data Standard Draft Standard Overview Public Meeting 6 December 2022 Docket Number DARS 2022 0028
Agenda Welcome Mr. John Tenaglia, Director, Defense Pricing and Contracting Administrative matters - Lisa Romney, Director, Contracting eBusiness Recap of request for comments How to submit comments Overview of needs and objectives Bruce Propert, Contracting eBusiness Technical architecture Bruce Propert, Contracting eBusiness Walkthrough of draft XML schema with questions and open discussion Bruce Propert, Contracting eBusiness, and Judy Critzer, Peraton Open discussion of use cases - Lisa Romney, Director Contracting eBusiness
Reminders Public meeting is not being transcribed or recorded This public meeting is not related to any open Federal Acquisition Regulation (FAR) or Defense FAR Supplement (DFARS) case Any comments should be sent to https://www.regulations.gov under Docket Number DARS 2022 0028. Search for Docket Number DARS-2022- 0028. Select Comment and follow the instructions to submit a comment. Please include your name, company name (if any), and Docket Number DARS-2022-0028 on any attached document(s). DoD s draft Catalog Data Standard (CDS) Concept of Operations (CONOPS) and schema available at DoD Procurement Toolbox (https://dodprocurementtoolbox.com/site-pages/ebusiness-data- standards-schemas) (scroll to the bottom)
Federal Register Notice Request for Comments (1 of 3) DoD requests comments on the following areas: The CDS Schema Structure and Formats. Enumerations. DoD requests inputs in particular on: Existing industry standards that can be used to identify products across suppliers within a given industry, such as pharmaceuticals. Standard descriptive information that can also be used to identify characteristics of items within a particular industry or set of industries. Standards for defining commercial services that are used within a specific industry such as automotive vehicle maintenance or medical procedures.
Federal Register Notice Request for Comments (2 of 3) Authoritative Sources. For any sources of enumerations identified, DoD requests input on whether authoritative sources exist that can validate either the information or the formats for the information. Concept of Operations (Discussion Draft). DoD requests comments on the notional Concept of Operations document. Use of catalog submissions as standing price quotations. DoD requests comments on the potential use of the notional CDS in the context of Federal Acquisition Regulation section 13.103. Use of catalogs as baseline documents in developing blanket purchase agreements or other ordering instruments.
Federal Register Notice Request for Comments (3 of 3) Ability to map existing catalog data to the XML format in the notional CDS. Cost to develop and deliver the catalogs using the notional CDS, and the extent to which those costs would be offset by: Eliminating the need to maintain Government-specific information on contractor websites. Reducing the volume of requests for quotations by use of the catalog. Use of the notional CDS for submitting bills of materials as either prime contractors to the Government or as suppliers/subcontractors to prime contractors or higher tier subcontractors. Any other general comments on the notional CDS and potential uses.
Submission of Comments Submit comments to: Federal eRulemaking Portal: https://www.regulations.gov. Search for Docket Number DARS-2022-0028. Select Comment and follow the instructions to submit a comment. Please include your name, company name (if any), and Docket Number DARS-2022-0028 on any attached document(s).
Electronic Commercial Catalog Need and Benefits Problem Statement: DoD has excellent data on how much we are spending in contracts. DoD does not have good data on what it is DoD is buying and who produces those items. Descriptions of items are non-standard and often insufficient: different vendors/resellers may call the same thing different names, contracting officers may document descriptions differently contract to contract. While DoD can easily identify the contract awardee, there is often little or no information about the provenance of the item. Commercial Catalog Data Standard + Validations provides standard data to verify: WHAT is DoD buying - current and accurate product information a standard, comparable method HOW MUCH is DoD paying standard pricing information WHO is DoD buying from information on companies in the supply chain (manufacturer, reseller, etc.) to better establish the provenance of item Will allow access to catalog data in an electronic means for use in purchasing and reuse in contracts. Bring benefits to industry partners to reduce multiple and disparate submissions of catalog data to DoD offices and potential use with subcontractors / suppliers to standardize data
Standard validations based on schema requirements, e.g. length, format, optional/required, etc. Use of authoritative sources and artificial intelligence to find anomalies and outliers across catalogs. Electronic Commercial Catalog Environment GEX Schema Validations Catalog Validations Possible validations against outside data sources (e.g. GSA certifications tables). Vendor creates or updates catalog in the standard data format. May send via XML or upload directly to website. Storage in EDA Outside Data Sources Full catalog stored in EDA and available via API. Contract Writing System FedMall eCommerce Site Contracting officer can pull product name and descriptions for use in contract line items. eCommerce sites pull standard catalog data (full catalog or items) real time from authoritative source.
Potential business use cases Streamline the simplified acquisition process by having contractors use the CDS when submitting catalogs of commercial items for IDIQs or BPAs where prices are based on catalog or market prices; Develop and maintain price lists in ordering instruments; Enable prime and subcontractors to submit standardized bills of materials; Enable item traceability for supply chain transparency. Submissions of bills of material as prime contractors, or as a vendor/subcontractor proposing to a prime contractor or higher tier subcontractor Use for submission of data on contractor acquired property, especially when the contract is likely to have commercial items charged (e.g. information technology)
Understanding the Schema Solid Box denotes a mandatory element or section. x- : Must provide x or more instances of the element or section. In this case, one instance is required. More may be provided. : Denotes that this is a section not an element. If absent, denotes that the item is an element that can be populated with data. ContactMethod : XML Tag Name of the section. Dotted Box denotes an optional element or section. Only one instance of the element or section allowed (0- , 1- , etc. missing). This is an element that can contain data, not a section since is missing. TitleOrFunction : XML Tag Name of the element. Sequence. Elements and sections following the sequence must be provided in the order shown. Choice Only one of the Elements and sections following the sequence may be provided.
Understanding the Schema Sample XML snippet: <Contact> <TitleOrFunction>Contracting Officer</TitleOrFunction> <Name>Joseph Smith</Name> <ContactMethod> <MethodDescription>Email</MethodDescription> <MethodValue>JSmith@anywhere.mil</MethodValue> </ContactMethod> </ContactMethod> <MethodDescription>Telephone</MethodDescription> <MethodValue>540-329-0110 x231</MethodValue> </ContactMethod> </Contact> (2) (3) (1) (2) (5) (6) (4) 1.Sequence of 3 elements and 1 section. 2.Optional data elements TitleOrFunction and OfficeCode . 3.Mandatory data element Name . 4.1- : Must provide one or more instances of the ContactMethod section. 5.For each ContactMethod section, the data elements MethodDescription and MethodValue are required. 6.When the phrase See list. or (see list) is at the end of a data element s description, there is an enumeration list (pick list) of acceptable values.
Submission of Comments Submit comments to: Federal eRulemaking Portal: https://www.regulations.gov.Search for Docket Number DARS-2022-0028. Select Comment and follow the instructions to submit a comment. Please include your name, company name (if any), and Docket Number DARS-2022-0028 on any attached document(s).
