Questions_and_Answers_-_22_Oct_19.pdf

PDF 118 KB Posted

Attached to
Request for Proposal (RFP) Item Master Logistics Capability Initiative (IMLCI) Federal contract opportunity
Solicitation number
FA8770-20-R-0004
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Maxwell Air Force Base

About this file

This document contains questions and answers related to a Request for Proposal issued by the Department of the Air Force Materiel Command Lifecycle Management Center. The solicitation seeks an Indefinite-Delivery, Indefinite Quantity contract for the Item Master Program, including Delivery Order 01, to provide an enterprise capability to generate and manage comprehensive, accurate, and reliable item-specific data within the Air Force Logistics enterprise. This will include item standardization, configuration management, and serving as a single authoritative source. The document provides clarification on requirements, evaluation factors, licensing strategies, and technical questions from potential offerors. Responses aim to ensure offerors have the necessary information on scope, evaluation, and technical details to develop proposals due for Gate 1 on October 18, 2019 and the full proposal due date to be determined.

View the file

Other files for this federal contract opportunity

Other files attached to Request for Proposal (RFP) Item Master Logistics Capability Initiative (IMLCI), newest first.
File Type Posted
Questions and Answers - 5 Dec 19.pdf PDF
Questions and Answers - 26 Nov 19.pdf PDF
Questions and Answers - 20 Nov 19.pdf PDF
Questions and Answers - 14 Nov 19.pdf PDF
Questions_and_Answers_-_4_Nov_19.pdf PDF
RFP_Attachment_11_-_TEP_Workbook_v.2.xlsx XLSX spreadsheet
Questions_and_Answers_-_21_Oct_19.pdf PDF
RFP_Attachment_04_-_Technical_Data_Package_(TDP)_Base_Document.docx DOCX document
Questions_and_Answers_-_17_Oct_19.pdf PDF
Questions_and_Answers_-_16_Oct_19.pdf PDF
Questions_and_Answers_-_15_Oct_19.pdf PDF
RFP_Attachment_4.M_-_CCE_Services_Description_V4.1_MAR_2019.pdf PDF
RFP_Attachment_12_-_Basic_IDIQ_Model_Contract.pdf PDF
RFP_Attachment_8_-_Product_Eval_Supplement.xlsx XLSX spreadsheet
RFP_Attachment_3_-_Requirements_List.xlsx XLSX spreadsheet
RFP_Attachment_5_-_Section_L_-_Instructions,_Conditions,_and_Notices_to_Offerors_or_Respondents.pdf PDF
RFP_Attachment_4.B_-_ManageItemMaster.pdf PDF
RFP_Attachment_4.D_-_AssignManagementInformationToIM_ARLineItem.pdf PDF
RFP_Attachment_10_-_SOO-CLIN_Matrix.xlsx XLSX spreadsheet
RFP_Attachment_2_-_ITFR_Capability_Assertion_List.xlsx XLSX spreadsheet
RFP_Attachment_4.K_-_TermsDefinitionsAcronyms.docx DOCX document
RFP_Attachment_4.C_-_ManageItemMasterAssistanceRequest.pdf PDF
RFP_Attachment_11_-_TEP_Workbook.xlsx XLSX spreadsheet
RFP_Attachment_4.E_-_ManageFederalCatalogAction.pdf PDF
RFP_Attachment_4.A_-_IMLCI101Brief.pptx PPTX presentation
RFP_Attachment_4.I_-_InformationAssets.xlsx XLSX spreadsheet
RFP_Attachment_7_-_Contract_Data_Requirements_List_(CDRL).pdf PDF
RFP_Attachment_4.G_-_ProcessNames.xlsx XLSX spreadsheet
RFP_Attachment_4.F_-_ExecuteProvisioning.pdf PDF
RFP_Attachment_6_-_Section_M_-_Evaluation_Factors_for_Award.pdf PDF
RFP_Attachment_9_-_Quality_Assurance_Surveillance_Plan_(QASP).pdf PDF
RFP_Attachment_4.L_-_Interface_Information.docx DOCX document
RFP_Attachment_1_-_Statement_of_Objectives_(SOO).pdf PDF
RFP_Attachment_4.H_-_Activities.xlsx XLSX spreadsheet
RFP_Attachment_4.J_-_DataReferenceModel.xlsx XLSX spreadsheet
Show all 35

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Item Master Logistics Capability Initiative (IMLCI) Request for Proposal FA8770-20-R-0004 Questions and Answers

# Question Answer

In RFP Attachment 5: Section L there is no mention of the timeline between completion of the Assertion Gate and to offer to submit a full proposal other than “… The due date for full proposal submission shall be determined/ communicated by the PCO at the conclusion of the Gate. Offerors will receive 30 days from the date of notification to submit a full proposal…”

As we must have resources available to meet a 30 day turn, we would request more detailed information on how much time the program office is planning for review of the assertions. 10 days?

30 Days? 90 Days? Any approximation would be helpful.

The Government intends to notify offerors whether or not they are provided the opportunity to submit a full proposal on or around 1 November 2019.

2 Reference: Section K, FAR 52.204-08 We would like to clarify the solicitation offeror size standard since the Reps & Certs includes the SB NAICS code 541511, yet this does not appear to be a small business set-aside in other text.

Please confirm what size standard of offerors will this solicitation will be awarded.

The referenced information is simply identifying the NAICS code for this acquisition and the associated size standard. This acquisition IS NOT a small business set aside, rather a full and open competition in accordance with FAR 15.3 as stated in the solicitation.

3 Reference: Section L, 4.2.4.4 Subfactor 4 – Product Evaluation

“…Populate the website with data prepared by the Offeror in sufficient detail to demonstrate each capability; the Offeror can create and pre-populate as many data structures as necessary to enable the desired capabilities…”

Is it your intention to provide this data upon acceptance of the ITFR assertions? Is it possible to get this added to the current solicitation?

The Government does not intend to provide a data set for this subfactor. The Offeror should prepare the proposed product with a data set of their choosing that will demonstrate the product’s capabilities.

4 Reference: Section L, 4.2.4.4 Subfactor 4 – Product Evaluation

“…Provide the capability to manage interface integrations using the Offeror’s exchange framework (See RFP Attachment 8, Product Evaluation Supplement) to allow the Source Selection Team to complete the following:

a. Create new interfaces (3 inbound and 3 outbound)

b. Update an existing interface by changing a data element (name, structure, and/or length)

There is no DID associated with subfactor 4 for the RFP. Formats for legacy interfaces are in the TDP and the DLA spec will be released post contract award.

c. Update an existing interface by adding a data element

d. Import and Export test data (stubbed data load);

e. Test business rules and error handling against stubbed data loads in accordance with the Offeror’s instructions…”

Will there be any specific DID or formats that these interfaces will be required to meet? Any existing APIs to current data, specific sources, etc? Again is it possible to get this information as soon as possible?

5 This RFP contemplates procurement of commercial items, yet it cites DFARS 252.227- 7013, Rights in Non-Commercial Technical Data;

-7014, Rights in Non-Commercial Computer Software; and -7015, Rights in Commercial Technical Data as the governing Data Rights clauses for this procurement. These clauses are not applicable to commercial computer software and commercial computer documentation. Please confirm that offerors are permitted to propose that commercial computer software and documentation be subject to the offeror’s standard commercial license as contemplated in FAR 12.212.

Offerors are permitted to propose commercial computer software and documentation to be subject to the offeror’s commercial license.

However, any non-commercial technical data or non-commercial software would be subject to the applicable DFARS clauses.

6 In the Basic IDIQ Model Contract, section AFLCMC/HIK-H003(1)(a) states that the Contractor must deliver source code if it “ceases to support the Source Code Materials generally.”

Could you please provide further detail on what ceasing to support Source Code means?

Ceasing to support shall occur when the offeror no longer provides sustainment, bug fixes, patches etc… that maintains the underlying product.

7 IM.ITFR.1.02.21 - Solution shall have the capability to manage individual workload by configuring desktop features

Do you mean that the user can accept tasks or are you looking for an automated process to level workloads?

a. Desktop features that can be configured include but not limited to things such as:

i. Filters (e.g. priorities, status, and AR types)

ii. Icons and widgets

iii. Notifications

b. Enable the User to set "reminders" to themselves to help manage their workload (frequency, message, medium)

8 IM.ITFR.1.01.02 - Solution shall provide the capability to systematically present AR templates to end users

a. Would it possible to provide a sample AR form.

a. Refer to the RFP_Attachment_4.J_- _DataReferenceModel.xlsx and tab “Item Master Assistance Request”

b. All phases of the lifecycle. ARs are used to manage changes.

c. CAs are assigned to the attribute as opposed to ARs or line items.

b. At which phases(s) of the system lifecycle are these submitted?

c. Does each AR have one and only one Cognizant Authority or may each line item have separate CAs?

d. Can CAs change over lifecycle?

d. Yes, CAs will change over the lifecycle.

9 IM.ITFR.1.01.40 - Solution shall have the capability to associate lot/serial number information to contract

a. Where is contract information stored?

a. Key contract attributes will be part of into the solution. The data will either be entered manually or will be pulled from the appropriate system.

10 IM.ITFR.1.01.56 - Solution shall have the capability to identify Federal Cataloging actions based on IM AR attributes

a. What are the actions that are expected?

b. Is this an attribute driven work flow?

a. Refer to the RFP_Attachment_4.J_- _DataReferenceModel.xlsx and tab “Federal Catalog Data” and (Asset Description and Asset Business Rules fields)

b. Workflow can be action, attribute, and business rule driven.

11 IM.ITFR.1.02.05 - Solution shall have the capability to populate the estimated response date based on response time AF business rules

a. Are their metrics for cycle times or is this to be intuited via analytics?

b. Assume we can grab and update a field.

a. Each action has a policy directed response time.

b. Yes, the Estimated Response Data is derived from the policy direct response times.

12 IM.ITFR.1.02.07 - Solution shall have the capability to identify the Assistance Request to the performing activity when the request type is other than an access or provisioning request

a. What are the other request types?

a. Examples of AR types are in the Data Reference model, tab Item Master Assistance Request, line 12. Refer also to the activity descriptions for context.

(RFP_Attachment_4.J_- _DataReferenceModel.xlsx and tab “Item Master Assistance Request” and RFP_Attachment_4.H_-_Activities.xlsx)

13 IM.ITFR.1.02.08 - Solution shall have the capability to identify an access only AR based on the user profile of the Originator

a. Are you referring to Read-Only access?

a. Read/write permissions are governed by the role assigned to each user. Please note there is a difference between authorized users and CAs. Refer to the “Roles and Permissions” tab of the Data Reference Model. (RFP_Attachment_4.J_- _DataReferenceModel.xlsx)

14 IM.ITFR.2.02.02 - Solution shall have the capability to create multiple legacy-based item identification number schemas

a. What do you mean by legacy part numbers?

b. Is this a new part that is identified as "Do Not

Use" or "Obsolete" or the like?

a. This ITFR concerns the item identification number schema and not the part numbers.

b. This is item identification and not item status.

15 IM.ITFR.2.02.06 - Solution shall have the capability to associate Items to approved organization upon CA approval

a. Is this the CAGE Code or other Organization?

a. Not CAGE Code, this would be an Organization.

16 IM.ITFR.G.2.02.10 - Solution shall notify CA of attribute authorization requirements

a. What kind of requirements are requested?

a. Requests include add, change, or delete attributes and attribute values that required CA approval.

17 IM.ITFR.G.3.03.15 - Solution shall provide requestor of Like Item search results

a. Can originators and requestors be different?

a. Yes

18 IM.ITFR.4.02.01 - Solution shall have the capability to systematically assemble the Coordination Package

a. What is the Coordination Package used for?

Collaboration?

a. Coordination Package is used for collaboration.

19 IM.ITFR.4.05.01 - Solution shall have the capability for the ILM Team to modify the AR that is used to generate a Coordination Package

a. Is the intent to auto-generate the coordination package from the AF Item Record?

b. What is the responsibility of the ILM Team?

a. No, coordination packages are derived from AF templates. AR templates are based on a combination of action, attribute, and business rule.

b. Refer to the “Roles and Permissions” tab of the Data Reference Model.

(RFP_Attachment_4.J_- _DataReferenceModel.xlsx)

20 IM.ITFR.4.06.01 - Solution shall have the capability to assemble AF originated Federal Cataloging data

a. How do you know if the Federal Cataloging data was originated by the AF? Assumption is to add an AF Item Master if it does not exist.

b. Are attributes to be auto populated?

a. Attributes on an AR and an Item Record identify the submitter, originator, and approver. New items are added to Item Master if the AR is approved. This is true for stocklisted and non stocklisted items.

b. Yes, as much as possible based workflow and AR template.

21 IM.ITFR.4.06.03 - Solution shall have the capability to identify discrepancies between the Federal Catalog request and Federal Catalog response

a. What types of differences are likely to be found?

a. By policy, DLA is the authoritative source for cataloging and has the right to change attributes and attribute values.

22 IM.ITFR.5.04.01 - Solution shall have the ability to send a complete provisioning data set

a. What data is contained in a complete provisioning data set?

a. This includes a LSA-036 and associated technical data package attachments.

(RFP_Attachment_4.J_- _DataReferenceModel.xlsx tabs “PIO”, “PoP, “Provisioning Data (LSA-036)” and “Provisioning Parts List”)

23 IM.ITFR.5.03.02 - Solution shall support import of contractor data

a. Is this to add related content or update attributes?

a. Both

24 Reference: RFP Attachment 11 TEP Spreadsheet "...Vendors shall propose only one of four licensing strategies…" The Air Force has prenegotiated agreements in place for several COTS software products. Some of these agreements do not fit within the four licensing strategies outlined in the RFP. Will the Government consider allowing vendors to provide an alternate licensing strategy to take advantage of these existing prenegotiated agreements that offer significant savings to the Government?

No. Vendors shall propose only one of the four licensing strategies.

25 Reference: RFP Attachment 11 TEP Spreadsheet Our proposed solution includes more than one COTS software product. Each COTS product has its own licensing strategy. Would the Government consider updating the template to allow multiple licensing strategy entries, one for each COTS product?

Per RFP Attachment 1 - Statement of Objectives (SOO), Paragraph 2, "If the proposed solution includes multiple products, those products shall be integrated and fully operational at the time of product delivery to the USAF."

26 Reference: Questions and Answers 16 Oct 2019 "...The Government does not intend to provide a data set for this subfactor. The Offeror should prepare the proposed product with a data set of their choosing that will demonstrate the product’s capabilities…" If the Air Force has provided access to or data for any previous pilot or capability demonstration concerning the Item Master initiaitive, will the Government consider sharing this with all vendors? If the Government has previously provided this data, and will not provide it for this procurement, please confirm that the Government will not assess the content of the sample data in evaluating the proof of concept.

Data content will not be evaluated. Product functionality will be evaluated per Section M.

27 Reference: RFP Attachment 5 Section L “How and where the product leverages industry best practices regarding the use of open architectural standards and open source utilities in a pipeline by describing the technology stack, server and storage requirements, and technical configuration options…” Please confirm "pipeline" refers to a DevSecOps CI/CD pipeline, or clarify what “in a pipeline” refers to.

Yes

28 RFP Attachment 1: Statement of Objectives (SOO) – Page 2, Para. 3

The Government states that “Product selection will not require a System Integrator (SI). The Government will serve as the SI and all work shall be coordinated by the IM Product Owner(s), using an agile delivery method.” However, Labor that is to be priced by the Offeror into the Technical Support Services CLIN 3000 appears to cover responsibilities that are typical of an SI to include Program, Development, Configuration, Cyber Security, Integration, and FIAR Auditability Support. This potential overlap could impact the proposed labor of the Offer if Government SI roles are not clearly defined.

Can the Government provide a list of the specific responsibilities the Government will be providing as the SI and additionally, can the Government provide a list of the labor roles and expected Government FTEs that will be supporting those responsibilities.

No. Knowing Government labor roles and expected Government FTEs are not required to respond to this RFP.

29 Can the Government provide guidance on where the Production system is expected to be hosted?

(Cloud One?)

Refer to section 6 of the TDP Base Attachment 4 -Hosting/Infrastructure Requirements

30 Per RFP Attachment 5: Section L, Section 2.1 "...., in order to guarantee a response, the clarification request must be received no later than 1 week prior to the Gate due date and 2 weeks prior to the full proposal due date."

Please confirm that Gate 1 Questions are due 10/18/19 and Gate 2 questions are due 2 weeks prior to the Full Proposal due date (now TBD).

To guarantee a response prior to the Gate due date, questions are due 10/18/19. To guarantee responses prior to full proposal submittal, questions are due two weeks prior to the full proposal due date.

31 Reference: Attachment 1, SOO, Section 4.

Delivery Order 01 (DO01); 4.2. Requirements “For DO01, the product shall enable the IPO to meet the requirements of Item Master Core as described in the TDP (RFP Attachment 4, paragraph 4.9.3, Item Master Product Roadmap).”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

32 Reference: Attachment 1, SOO, 4.2.3 Technical Support Services; A. Hosting Support “This support enables the IPO to install and maintain the IM solution in multiple environments, using one or more Cloud Service

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

Providers (CSPs), and a variety of approved tools as referenced in the TDP (RFP Attachment 4).”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

RFP Attachment 04 - Technical Data Package (TDP) Base Document

33 Reference: Attachment 1, SOO, 4.2.3 Technical Support Services; D. Program Support “All DO01 work shall be coordinated by the IM Product Owner(s), using an agile delivery method, as identified in SOO paragraph 2.3.D and TDP (RFP Attachment 4) paragraph 5” There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

34 Reference: Attachment 1, SOO, Section 2.3 and Section 4.2.3 Technical Support Services

Will the Government be responsible for data cleansing and standardization of existing Item Master (IM) data?

Yes, the plan is to use business rule capability to facilitate this work.

35 Reference: Attachment 1, SOO, Section 4.2 Requirements “For DO01, the product shall enable the IPO to meet the requirements of Item Maser Core as described in the TDP (RFP Attachment 4, paragraph 4.9.3, Item Master Product Roadmap).”

It appears that the Item Master Product Roadmap is missing from the referenced attachment. Will the Government please provide RFP Attachment 4, paragraph 4.9.3, Item Master Product Roadmap?

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Section 4.9 discusses the roadmap. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

36 Reference: Attachment 1, SOO, Section 4.2.3 (D), Bullet 2 “Participate in agile meetings, ceremonies, and daily activities” Please decribe the activities the contractor is expected support in daily Agile meetings? Will the contractor serve as the Scrum Master, Product Owner, Product Manager, or any other core role in the Agile development process?

Contractor will be a team member to help us learn the product. The role of vendor is to advise IPO on all work required to host, configure, test and go live.

37 Reference: Attachment 1, SOO, Section 4.2.3 (C) “This area involves API and integration architecture expertise to ensure the stability, reliability, scalability and availability of the IM solution, as identified in SOO paragraph 2.3.C.”

How many external system interfaces are there and will the government provide the number and

Interfaces are identified in the TDP.

techical details of external interfaces as related to this procument?

38 Reference: Attachment 1, SOO, Section 2.3 (D) Technical Support Services “The Government will serve as the SI and all work shall be coordinated by the IM Product Owner(s), using an agile delivery method as outlined in paragraph 5 of the TDP (RFP Attachment 4).”

Since the government will serve as the SI, will the Government share the Responsible, Accountable, Consulted, and Informed (RACI) matrix, or equivalent artifact?

Contractor will be a team member to help us learn the product. The role of vendor is to advise IPO on all work required to host, configure, test and go live.

39 Reference: Attachment 11; Tab B; Figure B-1

It appears there may be computational errors in Y2 and Y5 taking information from Tab E. Can the government please review?

RFP Attachment 11 – TEP Workbook has been edited to fix the identified errors and uploaded to FBO.

40 Reference: Attachment 11; Tab C; Figure C-1

It appears there may be computational errors in Y2 and Y5 taking information from Tab F. Can the government please review?

RFP Attachment 11 – TEP Workbook has been edited to fix the identified errors and uploaded to FBO.

41 Reference: Attachment 11; Tab F; Figure F-1

How should a contractor account for potential inflationary maintenance increases in the out years? For example: If the government purchases licenses and first year support for the licenses in Year 3 how do we account for an increased support cost for the year 2 support (for the licenses purchased in Year 3) in Year 4?

Offerors shall completely fill out TAB E and TAB F of RFP Attachment 11 – TEP Workbook to account for inflation throughout the life of the IDIQ.

42 Reference: Attachment 11, Instructions Tab Section F “Vendors shall propose only one of four licensing strategies. Only the prices and/or bands for the licensing strategy proposed should be present in this workbook.”

Will the government consider a license strategy that contains a mix of Perpetual Software Licenses and Annual Software Licenses?

No. Vendors shall propose only one of the four licensing strategies.

43 Reference: Attachment 11, Tab B; Figure B-1.

Perpetual Software Licenses and Figure B.2 - Annual Software Licenses

Can the government confirm the quantities outlined in columns C through G are application users?

Those quantities are the most probable orders to support application users.

44 Reference: Attachment 4: IMLCI 101 Brief

a) Refer to the RFP Attachment 11 - TEP Workbook for most probable future orders.

Can the Government share volumetric details related to:

a) Number of users expected in the future platform

b) Volume of unique item records and item-location records expected in the future state

b) Our starting point is 2 million active part records.

45 Reference: Attachment 6: Section M (2.2.2.4) “The Offeror’s price proposal will be evaluated for award purposes based upon the TEP.”

Is the TEP the only price proposal factor being evaluated for award purposes?

Per RFP Attachment 6, Paragraph 2.2.2, “The Price Factor evaluation will assess the Offeror’s price proposal for (1) Completeness,

(2) Reasonableness, (3) Unbalanced pricing, and (4) Total Evaluated Price (TEP).”

46 If any addenda are relased, should an offeror inlcude the addenda as part of Volume 4 - Contract Documentation / Other Business Documents?

The Government is not utilizing SF 30 or requiring any amendment or modification acknowledgement form to be submitted with the proposal.

47 How many Unique Inventory Items (UII) will the AF manage in the new Item Master system?

While we are not an inventory management solution, we need the IT capability to maintain relationships. There is no limit.

48 Reference: RFP Attachment 5 - Section L - 1.

Program Information “Item Master provides the following capabilities:

Item Standardization, Item Configuration Management, and Single Authoritative Source.

Refer to Technical Data Package (TDP) (RFP Attachment 4) Sections 2 and 3 for more details.”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

49 Reference: RFP Attachment 5 - Section L -4.2.4.4 Subfactor 4 – Product Evaluation “Additional information describing the IMLCI solution and business context can be found in the TDP (RFP Attachment 4).”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

50 Reference: RFP Attachment 5 - Section L -4.2.4.4 Subfactor 4 – Product Evaluation “General Site Instructions:

• Provide a secure URL compatible with the Air Force Standard Desktop Configuration (SDC) identified in Section 5.5 of the TDP (RFP Attachment 4);”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

51 Reference: RFP Attachment 6 - Section M -

2.2.1.4 Subfactor 4: Product Evaluation

“This subfactor will evaluate the extent to which the Offeror’s product(s), as identified in SOO (RFP Attachment 1) paragraphs 2.1 and TDP (RFP Attachment 4) Section 4, Contextual Model, meets and/or exceeds Item Master Business Transformation objectives.”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

52 Reference: Attachment 1, SOO - 2.2.

Cybersecurity Compliance “The Government’s objective is to meet cybersecurity directives, regulations and guidance as identified in RFP Attachment 3, Requirements, and RFP Attachment 4, TDP paragraph 5.”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

53 Reference: Attachment 1, SOO - 2.3. Technical Support Services - A. Hosting Support “Hosting Support includes application installation of the product and ongoing maintenance services as required for release of the core product to a Government-approved Impact Level 4 (IL-4) - controlled unclassified cloud hosting environments as described in the TDP (RFP Attachment 4) paragraph 6.”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

54 References: Attachment 1, SOO - 2.3. Technical Support Services; D. Program Support “The Government will serve as the SI and all work shall be coordinated by the IM Product Owner(s), using an agile delivery method as outlined in paragraph 5 of the TDP (RFP Attachment 4).”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments 4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

55 Reference: Attachment 1, SOO - Section 2 Requirements “The product shall allow the Government the ability to sustain and maintain the IM

Refer to RFP Attachment 04 – Technical Data Package (TDP) Base Document which has been added to the solicitation. Attachments requirements and comply with the Agile Application DevSecOps specifications in the provided Technical Data Package (TDP) (RFP Attachment 4) Paragraph 4.”

There are multiple Attachment 4's included with the final RFP. Will the Government validate which Attachment 4 is being referenced? (EG.

Attachment 4.A), etc

4A-4M are associated to the TDP Base Document.

RFP Attachment 04 - Technical Data Package (TDP) Base Document

56 Reference: Attachment 1, SOO, Section 4.1.1 Period/Place of Performance “The period of performance for all services under this order will extend 12 months from date of award. The services shall be performed at or around Wright-Patterson AFB, OH for support of the Agile Teams (Formal IPO and over the shoulder training tasks), and may be performed remotely on an exception basis. Development, hosting and cybersecurity tasks may be done from remote locations” On the RFP page it outlines that Place of Performance will be located at the Government Facility, Wright-Patterson AFB, Ohio. In attachemnt 1 it outlines services may be perofrmed at, around, or remotely on an expection basis. May [a vendor] anticapte that services and access will be strictly designated on-site at WP AFB, or will remote services be allowed for the period of the contract?

The services shall be performed at or around Wright-Patterson AFB, OH and remote services may be performed on an exception basis.

File details come from the government source that posted it. Updated .