Questions_W9128Z-26-R-DeCA-EPC.xlsx
XLSX spreadsheet 29 KB Posted
- Solicitation number
- W9128Z-26-R-DeCA-EPC
About this file
This is a Questions and Answers document addressing clarifications on a Call for Solutions for an Enterprise Grocery Product Content Creation, Management, and Syndication Software-as-a-Service (SaaS) solution issued by the Defense Commissary Agency (DeCA) under Army Contracting Command - Aberdeen Proving Ground (ACC-APG). The Call solicits integrated solutions combining Digital Asset Management (DAM) and Product Information Management (PIM) capabilities across four Areas of Interest (AOI): Core Product Content Management, Digital Asset Management, Brand Collaboration/Supplier Portal, and Industry Standard Integration.
The Phase 1 Solution Brief submission deadline was extended to October 13, 2026, at 10:00 AM EDT. Responses must not exceed 10 pages (12-point Times New Roman, single spacing, 1-inch margins), with Title Pages, Intellectual Property Statements, and Organizational Conflict of Interest analyses excluded from page count; smaller fonts are permitted for tables, captions, and headers. Submissions must be in PDF format (maximum 25 MB) via email or portal. The anticipated period of performance is one base year plus four option years as a firm-fixed-price contract. Critical deadlines include Production Go-Live for AOI 1 (Core PCM) and AOI 2 (ADAM) by January 26, 2027, and launch of Pilot Implementation for AOI 3 by January 31, 2027. The solution must comply with CMMC Level 2, FedRAMP High/DoD Impact Level 5 hosting standards, support secure federal identity federation with CAC and MFA, integrate with DeCA's GS1 GDSN data pool and SAP/ARTS systems, achieve 99.5 percent monthly uptime, and support multi-channel supplier ingestion (GDSN, bulk file uploads, and web portal). Phase 1 offerors must provide a Rough Order of Magnitude (ROM) covering the entire performance period, a technical concept, and a high-level schedule; detailed pricing and staffing plans are deferred to Phase 3. The Government will publish all Q&A responses on SAM.gov and does not require past performance information, CPARS evaluations, or formal accessibility reports (VPAT) until Phase 3. AI-assisted development tools are permitted but must be disclosed. There is no stated set-aside, and the acquisition is unrestricted; additional eligibility conditions will be determined in Phase 3.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Questions
| Question # | Attachment / Document | Page or Section | Question | Government Response |
| 1 | Call for Solutions (28 Sep 2026) | Section 6.1.1, first paragraph | Section 6.1.1 sets a ten page limit and 12-point Times New Roman font for a written Solution Brief but does not state page margins or line spacing. Are 1 inch page margins, single line spacing and 8.5 x 11 inch pages acceptable? | Pages must be 8.5x11. 1 inch margins and single line spacing are acceptable. |
| 2 | Call for Solutions (28 Sep 2026) | Section 5 (Visible Text and Document Formatting Compliance); Section 6.1.1 | Section 5 states that diagrams and graphics count toward the page limits. Do tables, charts and graphics all count toward the ten page limit, and is a smaller font size (for example 10-point) permitted for text inside tables, figures, captions, headers and footers, provided it is readable without magnification? | Smaller font may be used for tables, captions, headers, and footers. Tables and figures, the ROM, and the executive summary do count towards the page limit. |
| 3 | Call for Solutions (28 Sep 2026) | Section 6.1.1 a, e and f; Section 9 | Please confirm that the Title Page (a), the Intellectual Property Statement (e) and the Organizational Conflict of Interest analysis (f) are outside the ten page limit, and state whether a table of contents or a list of acronyms, if included, would count against it. | The Call for Solutions document that was posted to SAM.gov specifies that the Title Page, Intellectual Property Statement, and Organizational Conflict of Interest analysis do not count towards the page limit. If included, a table of contents and list of acronyms would count towards the page limit. |
| 4 | Call for Solutions (28 Sep 2026) | Section 6.1.1, first paragraph | If an offeror submits briefing slides instead of written pages, do the Title Page, Intellectual Property and OCI content count toward the twenty slide limit, and does a minimum font size apply to slides? | Slides must be readable. The title slide, IP Statement, and OCI do not count towards the page limit. |
| 5 | Call for Solutions (28 Sep 2026) | Section 6 and Section 6.1.1 | For submission by email rather than through a portal: (a) is a single PDF the only accepted file format, (b) should the file naming convention repeat the full subject line including the company name, (c) is there a file size cap on the Government mailboxes and may DoD SAFE be used if the file exceeds it, and (d) will the Government acknowledge receipt of each Solution Brief by email? | PDF is the only acceptable file format. Maximum file size that can be accepted by our email system is 25MB. If files exceed that size limitation, you may request a DoD SAFE link from the contracting office. Please apply the naming convention for the email subjects to the Phase 1 files.The Govt intends to acknowledge receipt. |
| 6 | SAM.gov notice description | Description, last sentence (question deadline of 01 October 2026) | Will the Government post its answers to all questions as an amendment to the Call on SAM.gov so that all interested parties receive the same information, and if the answers change the requirement will the Government extend the response date of 12 October 2026? | The Government's response to all questions will be published on SAM.gov. The closing date is being extended to Tuesday, 13 October 2026 ay 10:00AM EDT. |
| 7 | Call for Solutions (28 Sep 2026) | Sections 5 and 6 (silent) | Is the use of AI-assisted development tools (GitHub Copilot, Claude Code and similar) permitted in preparing the Solution Brief and in performing the resulting contract or agreement, and does the Government require the offeror to disclose such use? | The Government does not explicitly prohibit the use of AI-assisted development tools (such as GitHub Copilot, Claude Code, or similar) in preparing the Solution Brief or in performing the resulting contract or agreement. However, the Government does require the offeror to explicitly disclose any use of AI-assisted development tools within their Phase 1 Solution Brief. |
The burden of compliance with all solicitation requirements—particularly regarding intellectual property, data rights, and security—rests solely with the offeror.
| 8 | Call for Solutions (28 Sep 2026) | Section 7.1 b (January 31, 2027 expiration of current services) | Please identify, for each Area of Interest, the incumbent contractor name, the contract number and the current contract value (annual and total) of the current services that expire on January 31, 2027, and state whether the incumbent is paid by the Government, by suppliers, or both. | This information is not neccessary to provide a Phase 1 response. |
| 9 | Call for Solutions (28 Sep 2026) | Section 3 (Transition and Descoping Support, optional CLIN structures); Section 6.3 | What period of performance does the Government anticipate (base period and option periods), what contract line item structure is planned for each Area of Interest, and is the award expected to be firm fixed price for the full period? | The anticipated PoP is one base year plus four option years. This will be a firm-fixed-price award. Line item structure will be established at time of award. |
| 10 | Call for Solutions (28 Sep 2026) | Section 7.1 b; Section 6.1.1 c.v | What is the anticipated award date, how does the Government define Full Operational Capability for each Area of Interest, and must Full Operational Capability be reached before January 31, 2027 or is Initial Operational Capability by that date sufficient? | By January 26, 2027, the selected vendor must achieve Production Go-Live for AOI 1 (Core PCM) and AOI 2 (ADAM), and launch the Pilot Implementation for AOI 3 (Brand Collaboration). Vendor's Phase 1 Solution Brief must outline a high-level schedule capable of meeting these rapid milestones. |
| 11 | Call for Solutions (28 Sep 2026) | Section 7.1 b (transition approach); SOO Section 4.0 (On-boarding) | Is the incumbent funded and required to provide knowledge transfer during the phase-in period, including an export of the existing product images, attributes, dimensions and supplier records, and in what formats and by what date will that content be provided to the new contractor? | This information is not neccessary to provide a Phase 1 response. |
| 12 | Call for Solutions (28 Sep 2026) | Section 6.1.1 b.iii and d.ii; Sections 6.2 and 6.3 | Will a past performance questionnaire be required at any phase? If so, may Contractor Performance Assessment Reporting System (CPARS) evaluations be substituted to reduce the burden on references? | Past performance information will not be required prior to Phase 3. Phase 3 requirements will be specified in any invitation(s) issued to submit a Phase 3 proposal. |
| 13 | Call for Solutions (28 Sep 2026) | Section 6.1.1 c.iv (ROM); Section 6.3 (Firm-Fixed-Price commercial proposal) | To make the firm fixed price assumptions complete: (a) should the ROM show labor categories and hours for services, or a single price per Area of Interest, (b) what will the Government provide as government furnished equipment and information (interface specifications, test endpoints and credentials for SAP ARTS, Oracle, POS and FreshOp), (c) should travel and other direct costs (ODCs) be priced separately, and (d) who bears licensing responsibilities for third-party data networks and data pool subscriptions? | Please separate the software licenses from the service and training portions, but a detailed breakdown of the labor categories, hours, etc. is not required at this point. Please note that we are only looking for a ROM in Phase 1, not a detailed price proposal. The ROM should cover all costs necessary to provide your solution. |
| 14 | Attachment 0001, Statement of Objectives (28 Aug 2026) | Section 4.0 (Geographic Scope); SAM.gov notice, Place of Performance (blank) | What is the place of performance: will work be performed on-site at the Government facility at Fort Lee or at commissary locations, or remotely at contractor facilities, and where on-site work is required who furnishes workspace, badges and equipment? Is in-person training at OCONUS locations expected? | This information is not necessary to provide a Phase 1 response. For Phase 1 Solution Brief, offerors only need to confirm their solution meets technical capabilities rather than on-site logistics. |
| 15 | Call for Solutions (28 Sep 2026) | Section 6.1.1 c.iii (technical team) | Are any roles designated key personnel, are resumes required with the Solution Brief or only at Phase 3, and are there minimum qualifications, citizenship requirements or background investigation requirements for contractor staff who administer the platform or access DeCA systems? | This information is not necessary to provide a Phase 1 response. For the Phase 1 Solution Brief, offerors are only required to submit a high-level conceptual approach and a rough schedule outline. Detailed staffing plans, resumes, and personnel security clearances are not evaluated until Phase 3. |
| 16 | Call for Solutions (28 Sep 2026) | Section 5 (eligibility); SAM.gov notice (NAICS 518210, no set-aside shown) | Please confirm that the Call is unrestricted with no set-aside, state whether any Area of Interest may be set aside for small business or whether small business status will be considered in selection, and confirm whether any eligibility condition beyond those in Section 5 (for example nontraditional defense contractor participation or cost sharing for an Other Transaction) applies. | This is information that will be finalized in Phase 3. |
| 17 | Call for Solutions (28 Sep 2026) | Section 6.1.1 a.ii | Item a.ii asks the offeror to list which of the "four (3)" Areas of Interest the Solution Brief addresses. Please confirm that there are four Areas of Interest as listed in Section 3 and in the Statement of Objectives. | There are four Areas of Interest. |
| 18 | Attachment 0001, Statement of Objectives (28 Aug 2026) | Section 5.5, fifth bullet (Industry Standard Integration); Call Section 3.4 | Section 5.5 of the Statement of Objectives lists a fifth objective for Area of Interest 4, Industry Standard Integration, that does not appear in Section 3.4 of the Call. Is it part of a complete solution for Area of Interest 4? Which commercial retail data networks does DeCA use today (for example the GS1 Global Data Synchronisation Network), and does DeCA hold the data pool subscription the contractor would connect to? | Yes, the fifth objective, Industry Standard Integration, is a required part of a complete solution for Area of Interest (AOI) 4; its omission from Section 3.4 of the Call was an administrative oversight, and offerors must address it in their Phase 1 conceptual approach. Regarding current infrastructure, DeCA utilizes the GS1 Global Data Synchronization Network (GDSN) as its primary commercial retail data network today. Finally, DeCA holds and maintains the GDSN data pool subscription, meaning the selected contractor will not need to provide a subscription but will be responsible for building the integration points to connect the proposed platform directly to DeCA's existing endpoint. |
| 19 | Call for Solutions (28 Sep 2026) | Section 3.2, fifth bullet; SOO Section 5.3, fifth bullet | Section 3.2 of the Call says collaborative workspaces are for planogram and assortment designs, while Section 5.3 of the Statement of Objectives says product specifications and imagery. Which statement governs? | The Statement of Objectives (SOO) Section 5.3 governs the required capabilities for the collaborative workspaces. The primary purpose of these workspaces is to facilitate the secure exchange, review, and approval of product specifications and imagery between DeCA and external brand partners. While planograms and assortment designs may be referenced within the system, the platform is not required to serve as a primary planogram design tool. Offerors should align their Phase 1 technical concepts and functional capabilities with the requirements detailed in the SOO. |
| 20 | Attachment 0001, Statement of Objectives (28 Aug 2026) | Section 4.0 (On-boarding, Deployment, and IOC); Call Section 3 (Desired Attributes) | The Statement of Objectives says the contractor must achieve Initial Operational Capability within thirty calendar days of award, while the Call lists onboarding in under thirty days as a Desired Attribute. Which governs? Because Initial Operational Capability includes a validated data exchange with SAP ARTS, will DeCA make the interface endpoint, credentials and a test environment available at award? | The Call for Solutions Section 3 governs. The 30-day Initial Operational Capability (IOC) is a desired attribute that will be evaluated favorably, not a mandatory requirement for the Phase 1 submission. |
| 21 | Attachment 0001, Statement of Objectives (28 Aug 2026) | Section 5.1 (Platform Usability and Availability; Government Testing and Validation Support) | Beyond 99.5 percent monthly uptime, are support service levels defined (response and resolution times by severity, help desk hours across CONUS and OCONUS time zones, and the contract-defined severity timelines referenced in Section 5.1)? Do any open issues or Plan of Action and Milestones (POA&M) items on the existing systems transfer to the new contractor? | This information is not necessary to provide a Phase 1 response. For Phase 1, offerors only need to propose a high-level conceptual approach and a rough schedule outline. Detailed Support Service Level Agreements (SLAs), operational help desk hours, and specific system transition risk items (such as inheriting an existing POA&M) awill be negotiated and finalized during Phase 3 (Request for Prototype Proposals). |
| 22 | Call for Solutions (28 Sep 2026) | Section 3 (Cybersecurity, CMMC Level 2); SOO Section 4.0 | For the hosted SaaS platform: (a) is a FedRAMP authorization or a DoD Impact Level required in addition to CMMC Level 2, and would the Government accept a FedRAMP High Ready platform hosted in AWS GovCloud that is completing FedRAMP 20x assessment, (b) what is the expected authorization boundary and who is the authorizing official, and (c) is a CMMC Level 2 self-assessment recorded in SPRS sufficient, or is a C3PAO certification required at award? | Because this platform operates within a Department of War (DoW) environment, offerors must confirm that their proposed commercial Software-as-a-Service (SaaS) platform natively complies with high-level DoD security and integration baselines. This includes hosting the solution in an environment approved for Impact Level 5 (IL5) operations (compliant with FedRAMP High / DoD CC SRG IL5 controls), encrypting all data in transit (REST APIs, SFTP, HTTPS) using FIPS 140-2 (or newer) validated cryptographic modules, and supporting secure federal identity federation (Single Sign-On and Multi-Factor Authentication via CAC) for internal DeCA users (admins, category managers, etc). Any specific requirements will be detailed in any Request(s) for Proposal that are released in Phase 3. |
| 23 | Call for Solutions (28 Sep 2026) | Section 3 (Complete AOI Solutions); Section 4 (multiple awards) | If the Government awards Area of Interest 4 and Area of Interest 2 to different offerors, which platform is the system of record for approved content, and will each awardee be required to expose open REST APIs to the others? Should a standalone Area of Interest 4 solution include its own repository for supplier submissions under review? | The AOI 1 (Core Product Content Management/PCM) platform remains the master system of record for all approved product data, while the AOI 2 (ADAM) platform serves as the system of record specifically for digital assets. In the event of split awards, both awardees will be required to expose open, fully documented REST APIs to facilitate seamless, automated synchronization between the ADAM platform (AOI 2) and the Integration platform (AOI 4). Additionally, a standalone AOI 4 solution must include its own temporary repository or staging area to hold, validate, and review supplier submissions before they are formally approved and pushed to the core PCM system of record. |
| 24 | Call for Solutions (28 Sep 2026) | Section 6.1.1 c.iv; Section 7.1 b | Should the ROM be priced for the base period only or for the full anticipated period, is the ROM price binding at award or refined in the Phase 3 proposal, and can the Government share the budget range against which ROM realism will be assessed? | The ROM should cover the entire period. The Phase 1 ROM is for informational and planning purposes only. Offerors invited to submit a Phase 3 proposal will prepare and submit detailed pricing as part of the Phase 3 proposal that will be the basis for the award. As we are requesting the ROM for planning purposes, no budget information will be shared. |
| 25 | Call for Solutions (28 Sep 2026) | Section 3 (Data Rights and Internal Use); Section 6.1.1 e | Does the irrevocable internal use license apply to the product data and content DeCA ingests (which DeCA keeps after the subscription ends), or also to continued use of the SaaS platform itself after the period of performance? | The Government's irrevocable internal use license applies solely to the product data, digital assets, and content ingested, generated, or processed by the system during the period of performance. DeCA retains perpetual, unrestricted ownership and extraction rights to all such data and content, which will be exported and retained after the subscription ends. The license does not grant the Government continued access to, or use of, the proprietary commercial SaaS platform itself after the contract's period of performance has expired |
| 26 | Call for Solutions (28 Sep 2026) | Section 5 (180 day validity); Section 6.1.1 | Must the Solution Brief be signed by an official authorized to bind the company, and if so where should the signature appear? | Phase 1 briefs are not binding, signature is not required. |
| 27 | Call for Solutions (28 Sep 2026) | Section 6.1.1 a.ii; Section 3 (teaming encouraged) | May an offeror selected for further consideration add teaming partners or subcontractors, or propose additional Areas of Interest, at Phase 2 or Phase 3? | Teaming arrangements will be specified in Phase 3. Areas of Interest are determined by the Government. Any capability beyond the AOIs specified that offerors would like to share information about should be covered in the Phase 1 brief. |
| 28 | Call for Solutions (28 Sep 2026) | Section 6 (Phase 2) and Section 6.2 | If Phase 2 is held, when does the Government expect to issue invitations, will pitch sessions and demonstrations be virtual or in person, and how much preparation time will offerors have for a technical demonstration or challenge? | For any Phase 2 presentations, invitations will be sent upon the conclusion of the evaluation of the Phase 1 briefs. Pitch sessions and demonstrations will be virtual, held on Microsoft Teams. Demonstrations will be scheduled a few days in advance. |
| 29 | Call for Solutions (28 Sep 2026) | Section 3 (Platform Accessibility and Usability) | Will the Government require an Accessibility Conformance Report for the user-facing portal under Section 508 of the Rehabilitation Act at Phase 1 or at a later phase? | Offerrors are not required to submit an Accessibility Conformance Report (ACR/VPAT) with their Phase 1 Solution Brief. Bidders should confirm in their Phase 1 brief that their commercial platform is built to support modern web accessibility standards (WCAG 2.1 AA / Section 508). |
| 30 | Call for Solutions (28 Sep 2026) | Please identify the current product-content systems or service providers, the datasets and digital assets expected to be migrated, available export formats and metadata, approximate data volumes, and whether incumbent transition assistance will be available. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating their platform's native commercial capabilities, rapid-deployment timeline, and integration flexibility. | |
| 31 | Call for Solutions (28 Sep 2026) | At what acquisition milestone must an offeror demonstrate CMMC Level 2 compliance, and are FedRAMP authorization, a DoD cloud impact level, data-residency restrictions, or U.S.-person support requirements applicable to the proposed SaaS environment? | See response to Question 22. | |
| 32 | Call for Solutions (28 Sep 2026) | Please provide or describe the SAP/ARTS integration specifications, available test environment, supported authentication and exchange protocols, Government-furnished integration resources, and objective acceptance criteria for the validated data exchange required to achieve IOC within 30 calendar days. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on proving their platform's native integration flexibility, data validation engine, and high-level architectural compatibility. | |
| 33 | Call for Solutions (28 Sep 2026) | If AOIs are awarded to different contractors, will DeCA define and govern the cross-AOI interfaces and data contracts, and may an AOI 4 offeror satisfy repository, content-acquisition, and syndication dependencies by integrating with Government-selected providers for AOIs 1 through 3? | DeCA will define and govern the overarching enterprise data standards, schemas, and security requirements, but in a multi-award scenario, the selected awardees will be contractually required to collaborate directly and utilize open, fully documented REST APIs to establish seamless data exchange between their respective platforms. Furthermore, an AOI 4 offeror proposing a standalone integration solution may satisfy core repository, digital asset, and collaboration dependencies by integrating with the Government-selected providers for AOIs 1 through 3. However, the proposed AOI 4 solution must still include its own temporary staging and validation capability to process and verify incoming supplier feeds before securely transmitting the approved data to the primary systems of record. | |
| 34 | Call for Solutions (28 Sep 2026) | Section 3; Section 7.1 | For AOI 3, please identify the authoritative source system for each product-content element to be syndicated, including images, descriptions, nutrition data, dimensions, weight, taxonomy, pricing-related promotional content, and product-status attributes. Please also identify which system will serve as the final approval authority when data conflicts occur between the proposed platform, SAP/ARTS, Oracle, FreshOp, POS, and planogramming systems. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating their platform's flexible data governance, data normalization, and workflow approval engine. |
| 35 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please define the expected integration scope for FreshOp, including available interface specifications, authentication methods, supported inbound and outbound payload formats, event or batch-processing expectations, error handling, and whether DeCA will provide a non-production FreshOp environment for integration testing. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating their platform's native outbound syndication capabilities, data mapping flexibility, and export automation. |
| 36 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Is FreshOp to remain as a core DeCA solution of the environment? Or could vendors propose an alternative to FreshOp? | Replacing or proposing an alternative to FreshOp is strictly out of scope for this solicitation. FreshOp remains DeCA’s core customer-facing eCommerce solution and is not being competed under this Call for Solutions. |
| 37 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please identify all Government-furnished systems that require integration at award, distinguish mandatory integrations from future or optional integrations, and identify the expected sequence in which integrations must achieve operational status. | To establish a consistent baseline, the mandatory integrations required at award to meet the January 26, 2027 Production Go-Live include establishing the inbound connection to DeCA's GS1 GDSN data pool, configuring basic supplier flat-file onboarding, and exposing outbound syndication endpoints to DeCA's enterprise product master (SAP/ARTS) and digital storefront (FreshOp). Phased or optional post-launch integrations include launching the AOI 3 interactive supplier onboarding pilot by January 31, 2027, followed by secondary internal tools, such as planogramming and specialty merchandising systems, which will be expanded post-award. The expected technical sequence of these integrations begins with establishing the inbound data ingestion baseline, followed by standing up the Core PCM and ADAM repositories to validate product records, configuring outbound syndication to SAP/ARTS and FreshOp to clear the Go-Live gate, and finally expanding the AOI 3 collaboration workflows and secondary downstream merchandising endpoints. |
| 38 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please clarify whether DeCA expects near-real-time synchronization for all integrations or whether different latency requirements apply by data domain, interface, user population, and operational use case. For each interface, please provide the target update frequency, maximum acceptable latency, operating hours, and recovery expectations following an integration outage. | This information is not necessary to provide a Phase 1 response. For Phase 1, offerors should focus on proving that their platform natively supports a flexible, resilient hybrid-data architecture. |
| 39 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please provide the anticipated interface volumes for initial implementation and steady-state operations, including number of active items, assets per item, supplier submissions, daily content changes, API transactions, batch files, and concurrent users. Please distinguish CONUS and OCONUS operational volumes where applicable. | This information is not necessary to provide a Phase 1 response. For Phase 1, offerors should focus on demonstrating their platform's global cloud scalability, latency management, and access controls. |
| 40 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please clarify whether DeCA requires the contractor to create and maintain a canonical product-content data model and crosswalks among SAP/ARTS, Oracle, FreshOp, POS, replenishment, and planogramming platforms. If so, please identify any existing Government data standards, taxonomies, identifier conventions, or schemas that must be adopted. | This information is not necessary to provide a Phase 1 response. For Phase 1, offerors should focus on demonstrating their platform's native data modeling, mapping, and taxonomy governance capabilities. |
| 41 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please describe the expected process for validating product dimensions, weight, and other physical attributes before syndication to planogramming and replenishment systems. Please clarify whether validation will rely on supplier attestations, automated rules, Government review, physical measurement, third-party data feeds, or a combination of these methods. | This information is not necessary to provide a Phase 1 response. For Phase 1, offerors should focus on demonstrating the flexibility and power of their platform's native validation and workflow engine. |
| 42 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please identify the downstream planogramming solution or solutions in scope and provide the required asset formats, image-resolution standards, dimensional-data standards, identifiers, import mechanisms, and frequency of updates needed to support planogram-ready content. | This information is not necessary to provide a Phase 1 response. For Phase 1, offerors should focus on demonstrating their platform's native digital asset transformation, metadata tagging, and rendering capabilities. |
| 43 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please clarify whether DeCA expects the proposed solution to generate shelf visualization images, provide only validated source images and attributes to a Government-furnished planogramming tool, or support both functions. If both are required, please identify the expected division of responsibilities between the contractor and DeCA. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating how easily and reliably their platform package data for downstream space-planning tools. |
| 44 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please define the scope of digital merchandising capabilities required for product comparisons, related-item recommendations, promotions, and seasonal campaigns. Please clarify whether DeCA expects configurable business rules, recommendation algorithms, manual merchandising tools, campaign analytics, and direct publishing controls. | This information is not necessary to provide a Phase 1 response. Phase 1 requires a high-level conceptual approach and a rough schedule outline for managing and syndicating the core product content. Phase 1 offerors should focus on proving that their platform can store and deliver the rich marketing data that feeds these external tools. |
| 45 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please identify the performance measures DeCA will use to assess improvements in eCommerce search and discoverability, such as search-result relevance, zero-result searches, product-detail-page completeness, conversion-related measures, content publication timeliness, or other measures. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating their platform's native reporting, auditing, and data-quality dashboards and offerors are encouraged to propose their own standard commercial metrics and reporting capabilities that demonstrate how their platform improves data quality and content velocity. Illustrative performance measures that align with the Government's objectives include: |
Product Detail Page (PDP) Data Completeness: The percentage of active catalog items that meet 100% of DeCA's required core attributes, descriptions, and nutritional/dimension standards.
Digital Asset Coverage: The percentage of active SKUs linked to approved, planogram-ready, high-resolution primary and secondary images.
Time-to-Publish (Content Velocity): The average cycle time elapsed from initial supplier submission to validation, approval, and downstream syndication.
First-Pass Validation Yield: The rate at which incoming supplier data passes automated validation rules without requiring manual exception handling or rejection
| 46 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please clarify whether DeCA has established product taxonomy, metadata, keyword, SEO, accessibility, and content-quality standards that the contractor must implement. If standards do not exist, please confirm whether the contractor is expected to propose and govern these standards as part of the solution. | This information not necessary to provide a Phase 1 response. Offerors are only expected to outline a high-level conceptual architecture and a rough schedule and demonstrate their platform’s native taxonomy management, data-validation flexibility, and accessibility support. | |
| 47 | Call for Solutions (28 Sep 2026) | Section 3.3; SOO Section 5.4 | Please identify the required image formats, minimum and maximum image dimensions, file-size limits, color profiles, background requirements, mobile-rendering requirements, and accessibility requirements for assets published to each consumer-facing channel. | This information is not necessary to provide a Phase 1 response. For Phase 1, offerors should focus on demonstrating their platform’s native asset automation, rendering, and processing capabilities. | |
| 48 | Call for Solutions (28 Sep 2026) | Section 3.4; SOO Section 5.5 | Please clarify whether DeCA will require the supplier portal to support delegated administration by supplier organizations, including supplier-managed user onboarding, role assignment, account deactivation, and multi-factor authentication administration. | Yes, the Government requires the supplier portal to support delegated administration by the supplier organizations.Phase 1 offerors should focus on demonstrating the simplicity and security of their platform’s native user management engine. | |
| 49 | Call for Solutions (28 Sep 2026) | Section 3.4; SOO Section 5.5 | Please describe the required supplier onboarding process, including data-sharing agreements, identity proofing, training, user provisioning, test submissions, and approval to transact in production. Please clarify which onboarding activities DeCA will perform and which activities the contractor must perform. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating how their platform's design naturally simplifies and accelerates the supplier onboarding journey. | |
| 50 | Call for Solutions (28 Sep 2026) | Section 3.4; SOO Section 5.5 | Please define the minimum automated-validation rules required for supplier-submitted content, including completeness, image quality, image composition, identifier accuracy, duplicate detection, attribute consistency, dimensional-data validation, taxonomy compliance, and prohibited-content checks. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating the simplicity and power of their platform’s native business-rules engine. | |
| 51 | Call for Solutions (28 Sep 2026) | Section 3.4; SOO Section 5.5 | Please clarify whether DeCA will provide a defined content-quality scorecard, severity hierarchy, and acceptable-error thresholds for supplier submissions. If not, please confirm whether offerors should propose validation thresholds, exception classifications, and remediation workflows. | This information ois not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating the native data-quality dashboards, scoring tools, and automated workflow triggers in their commercial platform. | |
| 52 | Call for Solutions (28 Sep 2026) | Section 3.4; SOO Section 5.5 | Please describe the required approval and rejection workflow model, including approval roles, routing stages, service-level expectations, escalation paths, rework cycles, delegation rules, audit-trail requirements, and whether workflow rules vary by product category, supplier type, or content type. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating the usability, flexibility, and auditability of their platform’s native workflow engine. | |
| 53 | Call for Solutions (28 Sep 2026) | Section 3.4; SOO Section 5.5 | Please clarify whether suppliers must be able to submit content through multiple channels, such as portal entry, bulk upload, secure SFTP, REST APIs, or industry-standard retail data networks. For each required channel, please identify expected file formats, volume limits, validation requirements, and response-message standards. | Yes, the proposed platform must support a multi-channel ingestion model to accommodate DeCA's diverse supplier base. Offerors must confirm that their solution natively supports three primary channels: direct GS1 GDSN integration for automated synchronization with national brands, bulk file uploads (via standardized Excel or CSV templates) for batch validation, and direct manual web-portal entry (featuring user-friendly web forms and drag-and-drop file uploads) to support smaller local suppliers. File formats, volume limits, etc, is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating the versatility and user-friendliness of their ingestion layer. | |
| 54 | Call for Solutions (28 Sep 2026) | Section 3.4; SOO Section 5.5 | Please identify the industry-standard commercial retail data networks DeCA expects offerors to use for national-brand product content ingestion and validation. Please clarify whether DeCA requires connectivity to specific networks or will evaluate commercially available network options proposed by offerors. | DeCA requires direct connectivity specifically to the GS1 Global Data Synchronization Network (GDSN) as its primary commercial retail data network for national-brand product content ingestion and validation. The Government will not evaluate alternative commercial retail networks, as DeCA’s existing product data ecosystem is standardized on GS1 guidelines. Offerors must demonstrate in their Phase 1 Solution Brief their platform's native capability to securely integrate with the GS1 GDSN to ingest and validate standardized product content. | |
| 55 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please provide the technical and security architecture constraints applicable to REST APIs, SFTP connections, API gateways, network allowlisting, encryption, certificates, identity federation, logging, monitoring, and data-retention practices for all enterprise integrations. | Detailed, low-level technical and security integration specifications are not required for the Phase 1 Solution Brief. However, because this platform operates within a Department of War (DoW) environment, offerors must confirm that their proposed commercial Software-as-a-Service (SaaS) platform natively complies with high-level DoD security and integration baselines. This includes hosting the solution in an environment approved for Impact Level 5 (IL5) operations (compliant with FedRAMP High / DoD CC SRG IL5 controls), encrypting all data in transit (REST APIs, SFTP, HTTPS) using FIPS 140-2 (or newer) validated cryptographic modules, and supporting secure federal identity federation (Single Sign-On and Multi-Factor Authentication via CAC) for internal DeCA users (admins, category managers, etc). Additionally, the platform must maintain robust, centralized audit logs for integration with Government security monitoring tools (SIEM). | |
| 56 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please clarify the expected CMMC Level 2 evidence at Phase 1, Phase 2, and Phase 3, including whether DeCA requires a current certification, assessment results, System Security Plan, Plan of Action and Milestones, incident-response materials, or other cybersecurity artifacts before award. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating their platform's native high-level security features and hosting infrastructure readiness. | |
| 57 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please indicate whether existing system components (e.g., FreshOp, SAP/ARTS, Oracle, point-of-sale (POS)) in the environment comply with CMMC Level 2. If system components do not meet CMMC Level 2, will DeCA expect to migrate to CMMC Level 2 or provide a waiver? | The cybersecurity compliance status of DeCA’s internal legacy infrastructure (such as SAP, Oracle, or POS systems) is strictly outside the scope of a vendor's proposal. Offerors are only responsible for the security compliance of their own proposed platform. DeCA maintains full responsibility for the security authorizations and compliance of its own internal systems. Phase 1 offerors should focus on demonstrating their own platform's secure boundary lines and data-handoff protocols. | |
| 58 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please identify the Government-defined boundaries for Controlled Unclassified Information and sensitive operational data within this requirement. Please clarify which data elements, interfaces, environments, supplier functions, and contractor personnel will handle such data. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on proving that their platform natively protects and isolates CUI data by design. | |
| 59 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please clarify the required data-residency, hosting, backup, disaster-recovery, and continuity-of-operations requirements, including whether DeCA requires domestic hosting, geographic redundancy, recovery-time objectives, recovery-point objectives, and periodic disaster-recovery testing. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors must confirm that their proposed commercial Software-as-a-Service (SaaS) platform complies with standard DoD Impact Level 5 (IL5) hosting and residency requirements. Phase 1 offerors should focus on demonstrating the native resilience, scalability, and high-availability of their commercial cloud architecture. | |
| 60 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please clarify the expected transition approach from current services, including incumbent systems or services, available data inventories, data-export formats, historical-data retention requirements, asset migration volumes, transition responsibilities, and any constraints on access to incumbent data. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating their platform’s native bulk data ingestion and validation flexibility. | |
| 61 | Call for Solutions (28 Sep 2026) | Section 7.1; SOO Section 4.0 | Please confirm the date by which Initial Operational Capability must be achieved and clarify whether the 30-calendar-day requirement applies to each awarded AOI independently. Please also identify the minimum production capabilities, users, data, and validated SAP/ARTS exchange required for Government acceptance of Initial Operational Capability. | By the hard deadline of January 28, 2027, the selected vendor must achieve 'Production Go-Live' for Area of Interest (AOI) 1 (Core PCM) and AOI 2 (ADAM), and launch the 'Pilot Implementation' for AOI 3 (Brand Collaboration). The 30-calendar-day requirement for validated SAP/ARTS exchange applies specifically to the baseline integration under AOI 1 (Core PCM). The minimum production capabilities, users, data, etc is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on proving their platform’s rapid-deployment capability and schedule feasibility. | |
| 62 | Call for Solutions (28 Sep 2026) | Section 7.1; SOO Section 4.0 | Please identify the Government dependencies that could affect the 30-day Initial Operational Capability schedule, including availability of Government personnel, access approvals, interface documentation, test environments, credentials, network connectivity, security reviews, and test data. Please clarify how schedule impacts caused by unavailable Government dependencies will be addressed. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating how their deployment methodology naturally mitigates schedule risk and dependency delays. | |
| 63 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please describe DeCA's anticipated Enterprise Master Data Management modernization initiative at a level sufficient for offerors to design modular transition and descoping approaches. Please identify likely affected data domains, estimated timing, integration expectations, and whether DeCA anticipates phased replacement of specific platform capabilities. | This information is not necessary to provide a Phase 1 response. DeCA's long-term, agency-wide Enterprise Master Data Management (MDM) modernization initiative is an independent, future strategic program that is not part of the immediate scope of this commercial acquisition. Phase 1 offerors should focus on demonstrating the modularity, extensibility, and open standards of their commercial platform. | |
| 64 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please clarify the process, notice period, acceptance criteria, data-transfer requirements, knowledge-transfer requirements, and pricing expectations for modular descoping or transition of capabilities to DeCA's future Master Data Management environment. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating the simplicity of their platform's native data portability, export utilities, and open standards. | |
| 65 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please clarify the required scope of the commercial internal-use license for raw product data, digital assets, metadata, proprietary datasets, and platform-generated outputs. Please identify whether the license must survive contract expiration or termination and whether DeCA may share the data internally with other Department of War components or support contractors. | DeCA’s irrevocable internal use license applies perpetually to all raw product data, digital assets, metadata, and platform-generated outputs ingested or created during the contract's period of performance. This data-use license survives the expiration or termination of the contract, and DeCA retains the unencumbered right to export and retain all such data. | |
| 66 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 4.0 | Please clarify the Government's expected treatment of supplier-provided content that carries supplier-imposed license restrictions. Please identify whether DeCA will require the contractor to obtain and maintain supplier permissions for internal storage, public display, syndication, archival, and use in planogramming environments. | Offerors must understand that the selected contractor is not responsible for negotiating, obtaining, or maintaining individual licensing agreements with third-party suppliers or brand partners for standard product content (such as product descriptions, nutritional facts, dimensions, and standard marketing imagery). Phase 1 offerors should focus on demonstrating the simplicity and automated compliance features of their portal onboarding flow. | |
| 67 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please describe the required non-production environment architecture, including the number of environments, permitted test-data types, integration connectivity, release-management controls, Government access, test-support responsibilities, and criteria for promoting changes to production. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors must confirm that their proposed commercial SaaS solution incldues at least two distinct, isolated environments: non-production/staging test environment and a production environment. Phase 1 offerors should focus on demonstrating the simplicity and isolation of their environment management tools. | |
| 68 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please provide the defect severity definitions, response and resolution service levels, measurement methodology, exclusions, reporting expectations, and remedies associated with the requirement to resolve 95 percent of identified system defects within contract-defined severity timelines. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating the maturity, reliability, and transparency of their commercial support ecosystem. | |
| 69 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please clarify whether the 99.5 percent monthly availability requirement applies to the entire SaaS platform, each portal, each interface, API services, data exports, and supplier-facing capabilities. Please identify planned-maintenance windows, measurement methods, exclusions, reporting requirements, and any service-credit expectations. | This information is not necessary to provide Phase 1 response. Phase 1 offerors should focus on demonstrating the native high availability, redundancy, and operational transparency of their cloud architecture. | |
| 70 | Call for Solutions (28 Sep 2026) | Section 3; SOO Section 5.1 | Please identify the expected training audiences, estimated participant counts, locations, delivery methods, training-security requirements, required course topics, and success criteria for initial training, quarterly refreshers, and on-demand training materials. | This information is not necessary to provide a Phase 1 response. Phase 1 offerors should focus on demonstrating the native user-friendliness, intuitive design, and self-guided training features of their commercial platform. | |
| 71 | Call for Solutions (28 Sep 2026) | Section 6.1.1; Section 7.1 | Please clarify whether the Government expects the Phase 1 ROM estimate to include all transition, migration, integration, cybersecurity-compliance, training, test-environment, operational-support, licensing, and optional-service costs for each proposed AOI as a fully standalone price. | We are not looking for a detailed price proposal in Phase 1. The ROM should cover all costs necessary to provide your solution. | |
| 72 | Call for Solutions (28 Sep 2026) | Section 6.1.1; Section 7.1 | Please clarify the anticipated period of performance, option structure, subscription term, anticipated funding profile, and preferred pricing format for any Phase 3 proposal. Please also identify whether DeCA anticipates fixed-price pricing by AOI, user count, supplier count, transaction volume, asset volume, or another consumption metric. | The anticipated period of performance is one base year plus four option years. The remaining requested information is not neccessary to provide a Phase 1 response. | |
| 73 | Call for Solutions (28 Sep 2026) | Section 6.1.1; Section 7.1 | Please clarify whether DeCA will evaluate technical merit, schedule and cost feasibility, and viability independently for each AOI when an offeror proposes an integrated solution spanning AOI 3 and AOI 4. Please identify how the Government will evaluate shared platform costs, shared integrations, and interdependencies while preserving standalone AOI pricing. | The ROM pricing being provided with the Phase 1 brief is for informational purposes, and is not being evaluated. If only one solution is proposed to encompass AOIs 3 and 4, that solution will be evaluated in accordance with the Evaluation Criteria. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .