The file's text, extracted by GovTribe without its formatting.
DIBBS Requirements (2)
| Req ID | Capability | Sub-Capability | Capability Classification | Desired Future-State | | | |
| Functional and Technical Requirement | SNOW | SAP | Hybrid Solution Technology | | | | | |
| 1 | 1.0 Features | 1.1 Quoting | Must Have | The vendor end user shall be able to upload attachments (Word, PDF, etc.) to their quote prior to submission (e.g., Surplus Labels, MSDS, Hazardous Material Labels, or traceability documentation).Add the functionality to upload attachments to the quotable solicitations (RFQs). This will also apply to batch quotes | X | X | SAP with ServiceNow Portal UI |
| 2 | 1.0 Features | 1.1 Quoting | Must Have | The system shall handle quote revisions (after submission) including attachments by prepopulating previously submitted data, including all attachments upon revision, and providing a list of the attachments and file names at the bottom of the quote form. | X | X | SAP with ServiceNow Portal UI |
| 3 | 1.0 Features | 1.1 Quoting | Must Have | The platform shall support non-quotable submissions(i.e., RFPs) and extract specified data points and attachments. | X | X | SAP with ServiceNow Portal UI |
| 4 | 1.0 Features | 1.1 Quoting | Must Have | Platform will enable users to upload attachments when submitting bids on non-quotable solicitations. | X | X | SAP with ServiceNow Portal UI |
| 5 | 1.0 Features | 1.1 Quoting | Must Have | Platform shall apply dynamic data fields and validations generated by the solicitation requirements (originating from the CWS) for all quote methods by enabling conditional inputs and noting/flagging exceptions. | X | X | SAP with ServiceNow Portal UI |
| 6 | 1.0 Features | 1.1 Quoting | Must Have | Platform shall support multiple quote methods (batch, web, EDI). | | | |
| See DIBBS Batch and EDI 864 File Format: https://www.dibbs.bsm.dla.mil//refs/help/quoting/batch/batchformat.aspx | X | X | SAP with ServiceNow Portal UI | | | | |
| 7 | 1.0 Features | 1.1 Quoting | Must Have | Platform shall collect and store vendor quote data at multiple levels (e.g., header, line, item/NSN/material (NIIN) level). | X | SAP |
| 8 | 1.0 Features | 1.1 Quoting | Must Have | Platform shall auto-duplicate solicitation responses for lines corresponding to identical material (NSN+ FSC)/NIIN requirement, based on initial entries provided. | | |
Note: The platform should render the entry ONCE, though the quote submission file should record and store ALL corresponding(repetitive) material entries.
| See Product-Level requirements in DIBBS Batch File Format Layout. | | X | SAP | | | | | |
| 9 | 1.0 Features | 1.1 Quoting | Must Have | Platform shall enable cascading for designated data elements (i.e., pricing and delivery across line items) | X | | ServiceNow |
| 10 | 1.0 Features | 1.1 Quoting | Must Have | Platform shall auto-populate applicable quote submission fields based on Supplier Defaults indicated/designated in end-user profile. | X | | ServiceNow |
| 11 | 1.0 Features | 1.1 Quoting | Must Have | Platfom shall visually render quote summaries prior to submission. | X | | ServiceNow |
| 12 | 1.0 Features | 1.1 Quoting | Must Have | Platform allows for attachment upload for proposals. | | X | SAP |
| 13 | 1.0 Features | 1.1 Quoting | Must Have | Vendor end-user shall be able to cancel/withdraw a previously submitted quote. | | X | SAP |
| 14 | 1.0 Features | 1.1 Quoting | Must Have | Vendor end-user shall be able to schedule upcoming quote (Yet to Quote) submission--designate date and freeform field for explanation/justification | | X | SAP |
| 15 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall provide "quick search capability" for Solicitations/Amendments and Awards/Modifications via landing page and end-user profile homepage | | | |
Solicitation/Amendment search by type and data/criteria requested therein such as PR, NSN/Part Number, FSC (4 characters or less), Solicitation # (with or without dashes), Nomenclature, Approved CAGE, Approved PN, Buyer Code, Issue Date, Closing Date, Posting Date Range
Award Modification Search by the following criteria: Awardee CAGE, Award/Basic Number, Delivery Order, Award Basic Delivery Order Counter, Solicitation #, PR, NSN, Part Number, Nomenclature, Award Date (and date range), Award Post Date (and date range)
| X | | ServiceNow | | | | | |
| 16 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall save search criteria in background. (ex. when a user hits the back button, take them back to their search criteria. Right now it will erase it.) | X | | ServiceNow |
| 17 | 1.0 Features | 1.2 Searching / Filtering | Must Have | When a user searches for a purchase request or solicitation, the system shall indicate to the user that there are other open (available for quoting) purchase requests/solicitations for that same material on DIBBS. Allow for this indicator to be a link to the other open solicitations. | X | X | SAP with ServiceNow Portal UI |
| 18 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall provide option to save search results to vendor end-user "My Opportunities" interface. | X | | ServiceNow |
| 19 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform provides ability to search by approved sources. | X | | ServiceNow |
| 20 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall support the ability to search submitted quotes based on timeframes (today, specific date, date range) solicitation number, supplier reference quote number, etc. Requires the supplier to be logged on. | X | | ServiceNow |
| 21 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall index inbound PDFs from CWS to enable Solicitation/Amendment key word search | X | | ServiceNow |
| 22 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall index inbound PDFs from CWS to enable Award/Modification key word search | X | | ServiceNow |
| 23 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall support multiple and various filtering of Solicitations based on type, status, avaiability for quoting, “Technical package available”, “NAICS”, “National Drug Code”, Issue Date, Closing Date, Posting Date Range | X | | ServiceNow |
| 24 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall support filtering Awards based on Posted Today, Past 15 Days, ALL, Posted for Date Range: Start (MM/DD/YYYY) – End (MM/DD/YYYY), Award for Date Range: Start (MM/DD/YYYY) – End (MM/DD/YYYY) | X | | ServiceNow |
| 25 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall populate restricted solicitation search results where applicable, driven by supplier end-user account pre-approval for NSN, FSC and additional qualifying criteria based | X | | ServiceNow |
| 26 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall support capability to export search results in various file formats. | X | X | Both |
| 27 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall support capability to perform Pre-Award Request Search by DoDAAC, Contract Number, PAR Number and Date Range | | X | SAP |
| 28 | 1.0 Features | 1.2 Searching / Filtering | Must Have | Platform shall support capability to perform PAR Search by DoDAAC, Contract Number, PAR Number and Date Range | | X | SAP |
| 29 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | Platform shall support/enable PAR entrypoint from vendor end-user profile landing page or My Awards screen. | | | |
Current Tech constraint---ECC and SRM don’t cross validate, therefore ECC only contract PARS cannot be initiated in DIBBS
| Future-State Requirement: DCMA visibility to administor DCMA Contracts and PARs. | X | | ServiceNow | | |
| 30 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | Platform enables vendors to initiate a request for contract changes after award, including payment issues, delivery date change, and vendor requested cancellation. |
| This includes the ability to designate a Contract Number (PIID),CLIN(s), PAR Reason Code, Consideration Amount (if applicable, according to reason code) | X | | ServiceNow | | | | |
| 31 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | Platform allows vendor to add multiple attachments (of different file types) to New PAR Request | X | ServiceNow |
| 32 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | Platform allows vendor should be able to enter free form text in "Notes/Comments to Administrator" field | X | ServiceNow |
| 33 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | System shall generate PAR submission acknowledgment. | X | ServiceNow |
| 34 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | System shall be able to generate error messages for unsucessful validation, submission or system downtime | X | ServiceNow |
| 35 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | Platform shall keep communications secure by restricting the transfering of internal notes to any other systems/vendor end-user chat log. | | |
| (i.e, notes internal to DLA should not transmit to chat/PAR updates to vendor)--Focus on Data Segregation component) | X | | ServiceNow | | | | | |
| 36 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | Platform shall enable DCMA and DFAS users that are CAC enabled or .mil address to create PARS through the DIBBS/PAR functionality, and have all the capability that users have on DIBBS to create a PAR and/or check status of an existing PAR. | X | | ServiceNow |
| 37 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | Platform shall validate based on the Admin or Payment office DoDAAC of the user submitting the PAR, will match that to the Admin office if the user is from DCMA or if the user is from DFAS the office payment DoDAAC to the award on which the user is submitting the PAR. If it does not match, there will be a pop up stating their DoDAAC does not match the admin office. | X | | ServiceNow |
| 38 | 1.0 Features | 1.3 Post Award Requests (PARs) | Must Have | AVN added requirement via TMT: Platform shall enable the ability for DLA to initate PAR to supplier. This must also be able to be performed in mass (e.g. sending the same message for multiple awards/suppliers). | | X | SAP |
| 39 | 1.0 Features | 1.4 Pre Award Requests | Must Have | Platform supports PRE- AWARD communication on open soliciations/ open quotse between buyer (acq specialist) and vendor. (should comms be prompted with pre-populated categories) ( Functionality should be available during Quote Submission Draft) | X | | ServiceNow |
| 40 | 1.0 Features | 1.5 Two-Way Communication | Must Have | Platform enables vendor and contract administrator communication for post-award actions and/or changes in a measurable, trackable way at the contract level. | X | | ServiceNow |
| 41 | 1.0 Features | 1.6 Directed Notifications | Must Have | Platform shall automatically notify vendor end users that meet specific criteria based on supplier profile data and quoting activity.(e.g., volume, small business, etc.) | X | | ServiceNow |
| 42 | 1.0 Features | 1.6 Directed Notifications | Must Have | Platform shall send notifications to vendors, specific to updates pertaining to the solicitation process (e.g., award and and modification notifications, closing date extension, supplier not yet provided quote, solicitation closing soon). | | | |
| Platform shall inform vendors end-users of relevant information via multiple notification methods within the user interface (alerts, push notifications, email or other). | X | | ServiceNow | | | | |
| 43 | 1.0 Features | 1.6 Directed Notifications | Must Have | Platform shall support attachments(PDF or other) in push notifications to vendor end users. | X | ServiceNow |
| 44 | 1.0 Features | 1.7 Workflow Automation | Should Have | Platform shall detect invalid email address and trigger end-user to verify/update email address upon login. | | |
| Technical Requirement: Determine what will validate if the primary email address is valid/invalid. | X | | ServiceNow | | | | | |
| 45 | 1.0 Features | 1.7 Workflow Automation | Must Have | Platform shall accept quote submissions and automatically stop when cancelation or award is triggered. L&M added requirement via TMT: or when an award cannot be made due to constrained funding ("Ready for Funding" box is checked). | X | X | Both |
| 46 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | Platform shall enable user to access: “Solicitations”, “Quote”, “Award”, “Technical Data”, “Post Award Search”, “Forecasting”, “Supplier Registration”, “Help", from the home page submenus. | X | | ServiceNow |
| 47 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | Platform shall provide a vendor end-user homepage Capability for the user to access: “My Opportunities,” “My Quotes,” “My Awards,” “My PARs”, “My Account", from the home page main menu | X | | ServiceNow |
| 48 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | The platform shall populate solicitations and related data via the My Opportunities Screen by using the directed solicitation table in DIBBS and the DIBBS supplier directed solicitation notification section of their profile | X | | ServiceNow |
| 49 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | Fast Track Quoting: Add the ability to use Fast Track Quoting from any page on the platform. NOTE: if user enters an RFx number, take the user to the Upload Proposals/Quote page. | X | | ServiceNow |
| 50 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | Platform shall have a pop-up feature to display relevant notices and tips to the user interface | X | | ServiceNow |
| 51 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | Platform should clearly call out required text boxes/fields that need to be completed and/or corrected before moving forward (i.e., 508-compliant highlight with reason for system error). | X | | ServiceNow |
| 52 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | Platform shall clearly indicate/ highlight user account password requirements during initial and reset. Specifically, the corresponding violation should pop-up based on the end-user error. | | | |
| Note: Upcoming ICAM policy will remove password requirements for all end-user accounts on all applications. Moving to certificate-based log-in. | X | | ServiceNow | | | | |
| 53 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | When the platform website is down, the platform shall direct the end user to another page stating, “DIBBS is currently down, and technicians are currently working the problem”. NOTE: State estimated time it will be down if possible. | X | ServiceNow |
| 54 | 2.0 User Experience | 2.1 Basic Navigation (Ease of Use) | Must Have | Generate new Ts&Cs acknowledgement to each Super User / sub user accounts based on language/admin updates | X | ServiceNow |
| 55 | 2.0 User Experience | 2.2 User Support | Should Have | Platform shall provide a "Contact Us' Form to collect feedback and basic information (from drop-down options and free-form text) needed to resolve user help requests, track users issues to improve platform help, or identify needed platform improvements. | | |
| Underlying Technical Logic: Drop down options will drive redirection to Supplier Portal, Help Page, or other DLA Procurement Information Hubs. | X | | ServiceNow | | |
| 56 | 2.0 User Experience | 2.2 User Support | Could Have | Platform shall support access for non-supplier and non-vendor end users (e.g., APEX Accelerators for vendor support). |
| Special end-user account with access to production for search, status updates, reporting, test quote/ proposal submission capabilities. | X | X | Both | | | | | |
| 57 | 2.0 User Experience | 2.3 Application Support | Must Have | Platform offers application support for admin end users to address bugs and upgrades. | X | X | Both |
| 58 | 2.0 User Experience | 2.3 Application Support | Must Have | Platform offers multiple communication methods for admin end users to contact platform support (chat, email, phone). | | | Both |
| 59 | 2.0 User Experience | 2.3 Application Support | Must Have | Platform provider has ability to manage and triage incidents (site down, latency, cannot perform platform actions). | X | X | Both |
| 60 | 2.0 User Experience | 2.3 Application Support | Must Have | Platform provider has a ticketing system to manage and track incidents. | X | X | Both |
| 61 | 2.0 User Experience | 2.4 Training | Should Have | Platform provider can develop job aids and training for all end user groups. | X | X | Both |
| 62 | 2.0 User Experience | 2.4 Training | Should Have | Platform provide can tailor job aids and training artifacts to educate on agency-customized platform functionalities. | X | X | Both |
| 63 | 3.0 Admin | 3.1 Platform Admin | Must Have | Ability to edit Contact Us Form and update associated help categories via drop-down menu | X | | ServiceNow |
| 64 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform allows for attachments to be included in notices. | X | | ServiceNow |
| 65 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform shall maintain historical notices and enable platform admin users to search records via multiple methods/filters. | X | | ServiceNow |
| 66 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform enables multiple platform admin levels with associated levels of access. | X | X | Both |
| 67 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform readily displays super lockout reason codes to applicable platform admin users. | X | | ServiceNow |
| 68 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform enables admin users to archive and/or (limit visibility of) and solicitations(RFQ/RFP) awards/amendments/modifications. | X | | ServiceNow |
| 69 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform allows for multiple admin roles with varying levels of access. | X | X | Both |
| 70 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform can provide an agency-specific home page that can be easily configured to display relevant notices and include attachments (PDF or other). | X | | ServiceNow |
| 71 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform can provide an agency-specific home page that can be easily configured to display hyperlinks to other DLA or Federal sites. | X | | ServiceNow |
| 72 | 3.0 Admin | 3.1 Platform Admin | Must Have | Platform admins can designate target group criteria for adhoc notifications. | X | | ServiceNow |
| 73 | 3.0 Admin | 3.1 Platform Admin | Must Have | Ability for functional admin end-users to readily access back-end production data tables (in a low-code format) | X | X | Both |
| 74 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform enables admin users to directly update or delete vendor end user accounts. | X | | ServiceNow |
| 75 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform enables admin end-users (SuperLock) multiple account look-up methods (search by text, sorting, and filtering). | X | X | Both |
| 76 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform has self-service password reset. | X | | ServiceNow |
| 77 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform provides ability to centrally manage all vendor end user accounts and show multiple account statuses (locked, unlocked, expired, etc.) | X | | ServiceNow |
| 78 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform to enable multiple vendor end-user accounts associated with a CAGE Code to be notified of award. | X | | ServiceNow |
| 79 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform will enable platform admin to manage/update super and sub-user account designations. | X | | ServiceNow |
| 80 | 3.0 Admin | 3.2 User Account Management | Must Have | Admin end-users shall be able to restrict access and permissions to a limited group of people and various end-user | X | | ServiceNow |
| 81 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform shall support the capability to lock and unlock vendor end users out of the platform | X | | ServiceNow |
| 82 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform shall support the capability to limit the number of quotes that an entity/end-user account can submit within a configurable number of hours (for example 24 hours), number of quotes, or turn it off. | | | |
| This includes the Ability to designate default and exception by CAGE code per configurable number of hours | X | | ServiceNow | | |
| 83 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform offers capability to view suppliers’ account information. This includes IP addresses used, quote volumes (by time period), sub user accounts etc. in a reportable format. |
| This includes access to visual renderings of associated quote forms and attachements, | X | | ServiceNow | | | | |
| 84 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform offers capability to configure specific third party companies responsible for interfacing quote data to the Government (similar to the value added networks in EDI) | X | ServiceNow |
| 85 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform offers capability to configure specific agents that are authorized to prepare and submit quotes on behalf of other companies | X | ServiceNow |
| 86 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform end user roles include multiple Super Users that can add, edit, delete sub-user accounts for a specific vendor entity. ( establish quote defaults and sub user notifications) | X | ServiceNow |
| 87 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform end user roles include a sub-user that is managed by a Super User within a specific vendor entity. | X | ServiceNow |
| 88 | 3.0 Admin | 3.2 User Account Management | Must Have | Add the functionality so that when the Super User creates a sub-account an email is sent to the sub-user instructing them to logon. After logon, the sub-account will be active. | X | ServiceNow |
| 89 | 3.0 Admin | 3.2 User Account Management | Must Have | Platform shall support multiple end-users per vendor entity to receive push and/or email notifications for solicitation, awards, mods and amendments updates (also include No-Quote solicitations). Super User can designate the vendors to receive updates.via profile; ENERGY added requirement via TMT: Energy requests the ability for a vendor super user to be able to target notifications to a vendor end user - for example, a vendor super user can designate by long term contract CLIN which vendor users will receive notifications for associated delivery orders. | X | ServiceNow |
| 90 | 3.0 Admin | 3.3 Supplier End User Registration | Must Have | Platform shall require Prepared By CAGE accounts to designate Quote For CAGE(s) email addresses for email notifications (awards, solicitations). | | |
| X | | ServiceNow | | | | |
| 91 | 3.0 Admin | 3.3 Supplier End User Registration | Must Have | Platform prompts new vendors to register and establish end-user/company account (per valid cage). | X | ServiceNow |
| 92 | 3.0 Admin | 3.3 Supplier End User Registration | Must Have | Platform tracks a registrant's status/stage within the registration and certification processes. | X | ServiceNow |
| 93 | 3.0 Admin | 3.3 Supplier End User Registration | Must Have | Platform has connectivity to commercial or federal/state databases to verify registrant entity information based on specified criteria. | | |
| NOTE: DLA must agree/vet data sources being used for upfront verification. | | X | SAP | | | | |
| 94 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Must Have | The system shall transmit all revisions to submitted quote attachments to CWS RM (similar to quotes today), and remain associated with the original corresponding quote submission (visual rendering) | X | SAP |
| 95 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Must Have | Platform updates solicitation file when it is canceled in the CWS. | X | SAP |
| 96 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Must Have | Platform shall perform dynamic validations with Enterprise Supplier Risk databases/repositories. | X | SAP |
| 97 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Must Have | Platform can support customized interfaces and integrations with external systems to exchange and store data throughout the procurement process, and auto-populate/validate relevant field in the quote forms. (e.g., solicitation, bid, award, and PAR data). | | |
| X | SAP | | | | | |
| 98 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Must Have | Platform can interface with external systems in multiple formats (GUI, API, file exchange, or other). | | X | SAP |
| 99 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Must Have | Platform can receive and validate data (i.e, SAM, CAGE, order fulfillment data) in Enterprise Vendor Master Data Table and update when needed (additions/deletions). | | X | SAP |
| 100 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Could Have | AVN added requirement via TMT: Platform can ingest order status from suppliers via standard data interfaces (e.g. EDI) | X | X | SAP with ServiceNow UI |
| 101 | 4.0 Platform Performance | 4.1 Integration with Other Systems | Could Have | AVN added requirement via TMT: Platform can ingest Goods Receipt and Invoice Data from ERP | | X | SAP |
| 102 | 4.0 Platform Performance | 4.2 Performance Optimization | Must Have | Platform promptly notifies user of error with accurate error code, explanation, and correlating action. Error codes are based on criteria. | X | | ServiceNow |
| 103 | 4.0 Platform Performance | 4.3 Low-Code Programming | Should Have | Platform is readily configurable to update workflows/required user actions and end-user interface. | X | | ServiceNow |
| 104 | 5.0 Data | 5.1 Data Exporting | Must Have | Platform enables data downloads in various file formats (e.g, .csv, .txt.). L&M added requirement via TMT: these files are required for batch quoting. Batch quoting is a "Must Have" capability. | | X | SAP |
| 105 | 5.0 Data | 5.1 Data Exporting | Must Have | System shall generate zip files of solicitations posted for the day (PDF files) and a corresponding index file with solicitation data. L&M added requirement via TMT: these files are required for batch quoting. Batch quoting is a "Must Have" capability. | | X | SAP |
| 106 | 5.0 Data | 5.1 Data Exporting | Should Have | System shall generate zip files of awards/modifications posted for the day (PDF files) and a corresponding index file with awards/modifications data. | | X | SAP |
| 107 | 5.0 Data | 5.1 Data Exporting | Must Have | System shall generate daily file of approved sources for specific solicitations as applicable. (Contains approved manufacturers and part numbers). | | | |
This requirement enables Batch Quote submissions to meet data submission criteria/format for "Products Offered" question in quote form.
| L&M added requirement via TMT: these files are required for batch quoting. Batch quoting is a "Must Have" capability. | | X | SAP | | |
| 108 | 5.0 Data | 5.1 Data Exporting | Must Have | System shall generate daily solicitation data used in the batch/EDI process (example: FOB, QTY, Material/NSN, Delivery Requirement, Etc.). |
Based on solicitation requirements in Batch Upload template. (see BQ .txt file example)
| L&M added requirement via TMT: these files are required for batch quoting. Batch quoting is a "Must Have" capability. | | X | SAP | | | | |
| 109 | 5.0 Data | 5.1 Data Exporting | Must Have | Platform should transmit visual rendered quote PDF to CWS for record management (PR-INT-14369) | X | SAP |
| 110 | 5.0 Data | 5.2 Vendor Data Maintenance | Must Have | | | |
System shall require yearly verification of profile information (i.e., email addresses). Platform will trigger a 30-day notice prior to expiration.
| X | | ServiceNow | | |
| 111 | 5.0 Data | 5.2 Vendor Data Maintenance | Must Have | Ability for any user to update their account profile. This should include the award and solicitation email notifications & email addresses, notification settings for awards/solicitations. |
| X | | ServiceNow | | |
| 112 | 5.0 Data | 5.2 Vendor Data Maintenance | Must Have | Vendor end user shall be able to designate multiple NAICS/business sizes to enable supplier defaults. |
| Note: Upcoming connectivity with SBA data to validate supplier defaults. | X | | ServiceNow | | | | |
| 113 | 5.0 Data | 5.2 Vendor Data Maintenance | Must Have | Ability to track supplier user account information/setting changes. All changes will be displayed by the last name of the user in the account for tracking purposes. When changes are made, the Super User will also get an email notification of the change. | X | ServiceNow |
| 114 | 5.0 Data | 5.2 Vendor Data Maintenance | Must Have | Add to the user profile the ability to fill in a default for the following: FOB City, FOB State, FOB Country; Business size representation (small, large, etc.) by NAICS and overall. | | |
| This is auto-populate on web quote form. | X | | ServiceNow | | | | | |
| 115 | 5.0 Data | 5.2 Vendor Data Maintenance | Could Have | AVN added requirement via TMT: In addition to a standard order status interface, suppliers can manually provide order status for their open orders. | X | | ServiceNow |
| 116 | 5.0 Data | 5.3 Reporting | Should Have | Platform shall generate summary electronic Contract File for all pushalerts sent to vendor user profile account and transmit to Records Management (receiving system) | X | X | Both |
| 117 | 5.0 Data | 5.3 Reporting | Should Have | Platform shall generate canned and adhoc reports on website traffic, vendor end-user monitoring, and procurement (RFxs posted, awards) metrics. | X | | ServiceNow |
| 118 | 5.0 Data | 5.3 Reporting | Could Have | AVN added requirement via TMT: Users can download open orders and supplier provided statuses. | | X | SAP |
| 119 | 5.0 Data | 5.4 Data Visualization | Could Have | Platform has dashboard capability to visualize open bids, awards, PARs, and other relevant vendor data. | X | | ServiceNow |
| 120 | 5.0 Data | 5.4 Data Visualization | Could Have | Platform can support an Open Opportunities screen that provides a list of searchable and filterable solicitations for general public, without an end-user account. | | | |
| X | | ServiceNow | | | | | |
| 121 | 5.0 Data | 5.4 Data Visualization | Could Have | Platform offers capability to provide an Awards screen. This is a supplier specific list of awards with related data where the logged in supplier can see a list of all of the awards they have received. | X | | ServiceNow |
| 122 | 5.0 Data | 5.4 Data Visualization | Could Have | AVN added requirement via TMT: Platform shows suppliers open vs. closed orders with associated goods receipt and invoice data. | X | X | SAP with ServiceNow UI |
| 123 | 5.0 Data | 5.4 Data Visualization | Could Have | AVN added requirement via TMT: Platform shows supplier possible opportunities for bid based previous quote history as well as supplier's capability. | X | X | SAP with ServiceNow UI |
| 124 | 5.0 Data | 5.4 Data Visualization | Could Have | AVN added requirement via TMT: Platform shows how many times a solicitation has been viewed and which suppliers viewed the solicitation. | X | X | SAP with ServiceNow UI |
| 125 | 5.0 Data | 5.5 Demand Forecast | Should Have | Platform can ingest raw data from another demand planning source system to enable vendor search, filter, and data visualization. | X | X | SAP with ServiceNow UI |
| 126 | 5.0 Data | 5.5 Demand Forecast | Should Have | Platform allows vendors to filter demand forecasts by agency buyer (i.e., supply chain, FSC or NIIN). | X | X | SAP with ServiceNow UI |
| 127 | 6.0 Security | 6.1 Access Security | Must Have | Platform provides an account timeout/session expiration warning for supplier end-user. | X | | ServiceNow |
| 128 | 6.0 Security | 6.1 Access Security | Must Have | Platform shall consider a user as active when there is a key stroke or click on the screen and only time out when the user is not actively entering information into the platform. | X | | ServiceNow |
| 129 | 6.0 Security | 6.1 Access Security | Must Have | Capability for the individual DIBBS users to self-unlock, without assistance. Capability can be managed/disabled by the DIBBS admin end-user Super Lockout functionality. | X | | ServiceNow |
| 130 | 6.0 Security | 6.1 Access Security | Must Have | Platform shall generate a pop up window after the user has submitted their password if the user violates the following password rules. | | | |
| i. | New password must differ from your last 10 passwords. | | | | | | | |
| ii. | New password characters must differ from previous password by at least 4 characters. | X | | ServiceNow | | | | |
| 131 | 6.0 Security | 6.1 Access Security | Must Have | System shall automatically log the user into platform after the user changes their password. Allow this action to constitute “activity” so that the user does not get an inactivity email right away. | X | | ServiceNow |
| 132 | 6.0 Security | 6.1 Access Security | Must Have | Platform requires Multi-Factor Authentication (MFA) during login and password reset. | X | | ServiceNow |
| 133 | 6.0 Security | 6.2 Compliance | Must Have | Platform must be able to accommodate password reset every 60 days for all users. | X | | ServiceNow |
| 134 | 6.0 Security | 6.2 Compliance | Must Have | Platform is FEDRAMP certified or in the process of attaining certification. | | X | SAP |
| 135 | 6.0 Security | 6.2 Compliance | Must Have | Platform is compatible with IL4 or IL5 cloud capability designations. | | X | SAP |
Defense Logistics Agency