Final_HCMS_OEM_IDIQ_Questions_Answers (U).pdf

Classification: UNCLASSIFIED#

SOURCE SELECTION INFORMATION

SEE FAR 2.101 AND 3.104

# Reference (Section / Paragraph) Page # Question Response

1 4.2 / HCMS OEM SW TO 0002

SOW

or 10 of 22

Would the government please clarify what percentage of work is anticipated to be performed at the DIA site? The government does not have a precise percentage, but it will likely be a small percentage.

2 14.10 / Section C HCMS SOW 34 of 240 or 16 of 22

Does DIA provide the license for the Collaborative Supply Portal in order to provide an API to/from CSP repository? Which vendor hosts the CSP?

Please see updated SOWs

3 2- Background / HCMS OEM SW

TO 0002 SOW

or 1

The Diagram on page 41 references Oracle/Peoplesoft HCMS. Would the government please clarify whether Oracle/Peoplesoft HCM is the current product being replaced?

Yes, this acquisition is for the MyHR replacement which is based on the Oracle Peoplesoft application.

4 4.2 / HCMS OEM SW TO 0002

SOW

or 3

Please confirm that the sandbox will be cloud hosted by the contractor. If this is not the case and DIA requires an on-prem sandbox, does DIA have the necessary infrastructure, networking and data in place in order to meet the timeline?

The government confirms the sandbox will be hosted by contractor (whether thick client or cloud), allowing access to both government and SI as necessary.

5 5-Constraints / HCMS OEM SW

TO 0002 SOW

or 4

Given the JWICS modernization effort using Cloud, are there any known constraints that could affect timeline, security or potential HCMS requirements?

The government is not aware of any known constraints at this time.

6 5-Constraints / HCMS OEM SW

TO 0002 SOW

or 4

Does DIA have a specific constraint on which cloud hosting provider is to be used (i.e. Azure, AWS, Oracle) or is the cloud hosting provider to be recommended by the contractor

DIA assumes the OEM may have constraints for what cloud environment the solutions can be deployed

in. The only constraint for DIA is the cloud environment must be able to deploy in the C2E

7 2.5 / Instructions / Volume 1 233 of 240 or 4

In the Volume Table, specific to Volume 1-Requirements Identification Matrix, it states "Template Provided" Can the gov't please confirm that section 3.1 instruction is considered the template or can they please document where in the Template can

Updated on SAM.gov

8 2.5 /Instructions/ Volume 1 233 of 240 or 4

Would the government please provide attachments 3 and 4 in excel format to facilitate Volume 1 Requirements Identification Matrix completion?

Updated on SAM.gov

9 J.2/Attachment 2 167 of 240 Is it possible to provide Attachment 2 in Excel Format? Updated on SAM.gov 10 J.2/Attachment 2 171 of 240 The government references an Independent Government Cost Estimate, however the estimate is blank. Would the government please provide its IGCE?

No, this will be corrected

11 TO#2 SOW 44 of 240 The government references CDRL A009 as a deliverable, however CDRL A009 referenced on page 132 of 240 is the Status of Government Furnished Equipment (GFE) Report. Can the government confirm the reference on Page 44 of 240 should be to

CDRL A008 ?

Please see updated SOWs

12 ITO 231 of 240 Does the government intend to offer another round of questions during the RFQ phase? Not at this time 13 ITO 233 of 240 Table 2: Written Volume Page Limitations references a template provided for Requirements Identification Matrix (RIM). It does not appear that the template was attached. Can the government please send out the RIM template?

Updated on SAM.gov

14 Solicitation / Contract / Order for Commercial Items

3 of 240 The NAICS code referenced, NAICS 334290 Other Communications Equipment Manufacturing, is not an expected fit for this commercial software procurement. The Draft Solicitation contained the NAICS Code 541512 Computer System Design Services which seems to be more in line with this procurement. Was the NAICS Code for this procurement intentionally changed? If not, would the government consider revising the NAICS code to 541512 to more properly align with the

The NAICS code has been changed to 541512. See updated ITO.

15 Solicitation / Contract / Order for Commercial Items

3 of 240 Will the Government provide a breakdown of users based on full-time, part-time, hourly contract, or other categories to better estimate the cost for 30,000 users with our solution?

DIA is prepared to adopt the selected offeror's role system to service the full ~30,000 users. An example of current role and affiliate types are listed on the "Continuation" tab to assist in cost estimation.

16 4.2.3 Subfactor 1.3: Technical and Program Management (Volume 4)

237 of 240 The Government provide 25 pages for the Volume 4 response but the evaluation criteria requests that a technical and program management response be provided for both the IDIQ and TO2 SOWs. Would the Government consider increasing the page limit to 35 pages for this volume to ensure full coverage of all requirements? In addition, can the Government confirm that the usual exemptions apply for page limitations - e.g., not including Table of Contents, Cover Letter, Resumes, Compliance/Cross- Reference Matrix, etc.

See updated ITO

17 Instructions to Offerors (ITO) 232 of 240 1.14: We respectfully request an extension of two (2) weeks. Unfortunately at this time we can not grant the extension.

18 Solicitation General Will the Government clarify the delineation between OEM professional services and SI professional services? OEM professional services will be provided in support of the OEM SW, the SI professional services will be provided in support of the overall HCMS solution (to which the OEM SW is a component)

19 Solicitation General For tasks that exist in both the OEM and Professional Services solicitations, how will the Government determine the contract on which the work will be performed?

These determinations will be made following the SI contract award, and to be discussed during SI contract kickoff.

20 General, Cloud Authorization N/A In order to satisfy any cloud requirements as it relates to this acquisition, will the Government coordinate with C2E Contracting Officer to provide a Letter of Authorization and/or release a specific TOPR under the C2E for either the OEM or SI, to procure cloud hosting for this acquisition?

Yes, the Government intends to complete this for the C2E

21 Section A, Block 8 1 of 240 Based on the criticality of the Government's response to questions regarding this requirement, will the Government consider granting a two week extension if answers are not received by 9/25/23 to allow sufficient responses to the revised and clarified requirements?

Unfortunately at this time we can not grant the extension.

22 Section A, CLIN table, II. and III 3 of 240 II. identifies a Contract Minimum of $2,500.00, while III identifies a Contract Minimum of $150,000,000.00.

What is the difference between II. Contract Minimum and III Contract Minimum? Is $150,000,000.00 a Contract Maximum/Ceiling?

See updated Schedule B

23 Section A, CLIN table, CLIN 0001 3 of 240 States that the funding will support OHR OEM SOW Task 11, Contract Project Management and Common Tasks. That doesn't appear to be a valid reference.

Will the Government update to the correct reference?

See updated schedule B.

OHR MOD PMO OEM

Questions / Comment Matrix

# Classification: UNCLASSIFIED UNCLASSIFIED

SEE FAR 2.101 AND 3.104

# Reference (Section / Paragraph) Page # Question Response

OHR MOD PMO OEM

Questions / Comment Matrix

24 Section C, C.1 23-40 of

Many of the IDIQ SOW tasks and CDRLs appear to apply to the SI contract instead of the OEM contract.

Can the Government confirm which SOW tasks and CDRLs are required for the OEM contract?

CDRLs are defined at the IDIQ level of the contract as potential deliverables that may be asked for in each task order. The CDRLs have been identified for the OEM contract, not the SI contract (although they will likely have overlap) and offer flexibilities for the government in what will be asked for over the course of the lifecycle of the entire program. CDRLs that will be required for each task order will be defined in those respective task orders.

25 Section C, C.1, 2.2.2. 23 of 240 States "...the selected Systems Integrator (SI) partner..." Will the Government confirm that the SI reference is for a the separate acquisition and not for the Original Equipment Manufacturer (OEM) acquisition?

The SI will be a separate acquisition.

26 Section C, C.1, 2.2.3., 2.2.3.9. 23 of 240 States "(U) The contractor shall deliver an HCM environment capable of operating in concert with DIA infrastructure, security, and network policies to include, but not limited to:

. . . (U) Systems integration."

Will the Government provide a list of integrations so the offeror can properly price?

The intent of the "Systems integration" should be understood that the OEM will likely be involved in the integration, but the SI will primarily be responsible for overall system integration.

27 Section C, C.1, 2.2.4. 24 of 240 States the following: "(U) The contractor shall work with the government to map existing DIA workflows and standard operating procedures to out of the box system functionality. The contractor shall take government-provided documentation and map to system functionality, as Well as, conduct functional exchanges with the government to document system functionality and solutions for "to be" workflows." Will the Government define the "to be" state so that Offerors can appropriately price?

The "to be workflows" will be provided at the time that the completion of the functional mapping for existing processes.

28 Section C, C.1, 2.2.5. 24 of 240 States the following: "2.2.5. (U) The contractor has up to a five-year period to deliver a software solution that is supportive of multiple domain operations, including unclassified, Impact Level 5 (IL5) Authorization within the DIA NIPRNet boundary and Top Secret/Sensitive Compartmented Information (TS//SCI) networks. The government will serve as a sponsor and will assist both the contractor and the selected Systems Integrator (SI) partner with these activities. All software and infrastructure, on both the unclassified and TS//SCI networks, will be authorized for use according to DIA cyber security policies and procedures, further outlined in the Bidders Library. These solutions may be single-tenant or multi-tenant SaaS, or on-prem software."

The Cloud PMO wants to onboard simultaneously across all fabrics and certain datasets are in TS region. Will the Government support connectivity to the cloud regions proposed by the Offeror across all fabrics?

The SI will primarily be responsible for insuring authorities to operate on all appropriate networks, this information was intended to relay the timeline and current requirements to OEM to be informative on processes and efforts the OEM will need to support. The offeror should recommend a solution that best meets government requirement.

29 Section C, C.1, 2.2.5 24 of 240 States the following: "software solution that is supportive of multiple domain operations."

A software solution may be deployed in various domains; however, only a single domain can be the source of record. Can the Government clarify their interpretation of "multiple domain operations"?

Software instances of the solution will reside on multiple networks, however only the TS/SCI version will be system of record.

30 Section C, C.1, 2.2.5.1. 24 of 240 This paragraph is portion-marked "U//FOUO". If this paragraph is truly FOUO, then recommend the Government change the classification headers/footers of this document from "UNCLASSIFIED" to "UNCLASSIFIED//FOR OFFICIAL USE ONLY" so that potential Offerors can appropriately handle this document.

Please see updated SOWs

31 Section C, C.1, 2.2.6. 24 of 240 States the following: "(U) The HCM environment shall provide secure data flows, primarily of recruitment information, to and from the various networks in accordance with DIA cross domain capabilities and policies. The primary data will be transferred from unclassified to TS//SCL A limited amount of unclassified data will be transferred from TS//SCI to the unclassified network."

Will the DIA permit Offerors to employ/utilize DIA's native cross-domain solutions?

The SI will primarily be responsible for any data transfers across network boundaries and will utilize native cross-domain solutions, this information was intended to relay the timeline and current requirements to OEM to be informative on processes and efforts the OEM will need to support.

32 Section C, C.1, 2.3.1. 25 of 240 States "(U) The contractor shall identify a (1) program manager and (1) contract manager as IDIQ-level "key personnel:"

Will there be a separate program manager and contract manager for the SI (and OEM)?

Each contract (SI and OEM) will have their own contract and program managers.

33 Section C, C.1, 2.3.1. 25 of 240 States that the contractor shall provide labor, to include a program manager and a contract manager, "as IDIQ-level 'key personnel'". This labor is typically not included in standard COTS licenses.

Shall the OEM Contractor price and bid this labor as part of the IDIQ pricing, or will it be procured in subsequent TOs?

The government accounted for this as part of the G&A fees.

34 Section C, C.1, 2.3.1.2. 25 of 240 The requirement of a contracts manager as key personnel with specific responsibilities assumes the offeror is organized as a traditional Government contractor operating in a System Integrator fashion. Commercial OEM companies are organized in a different manner than traditional Government contractors and the specific role may not exist as stated in Section 2.3.1.2.

Will the Government remove the key personnel requirement for the contracts manager as a whole, or remove the specific reporting requirements that may be provided by a different role?

Our requirement is that we need a point of contact for contract administration on the OEM end.

35 Section C, C.1, 2.3.1.3., 2.3.2. 25-27 of

Shall the OEM Contractor scope and price all tasks listed in 2.3.1.3. as well as the effort required to produce the deliverables listed in 2.3.2. as part of the IDIQ pricing, or are those items listed as potential tasks/deliverables that could be included in future TOPRs?

As seen in the footnote, these are representative CDRLs, actual work to be performed will be done at the task order level and those corresponding CDRLs will be defined in each task order.

SEE FAR 2.101 AND 3.104

# Reference (Section / Paragraph) Page # Question Response

OHR MOD PMO OEM

Questions / Comment Matrix

36 Section C, C.1, 3.1., 3.4., 3.5. 27 of 240 Sections contemplate development for TS/SCI (SOW 2.2.5.3); however, this requirement is for OOB (or minimally customizable) commercial solutions.

Will the Government validate that it intends to only acquire commercial license rights for the TS//SCI fabric and not rights associated with cooperative development of a new capability that would implicate non-commercial developmental rights and associated deliverables? The current requirements for source code are inconsistent with the procurement of commercial products and services.

If the evolution of any software solutions or requirements involves source code access in the future, this section will allow for such deliverables. Because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

37 Section C, C.1, 3.1. 27 of 240 The requirement for non-proprietary information may unnecessarily limit the type and amount of information delivered to the Government. The Government maintains the right to use proprietary data inside the Government.

Will the Government clarify the intent behind the requirement for non-proprietary information (i.e., does the Government have a need to share information in a way that is inconsistent with proprietary markings?)?

Does this authorize the commercial provider to withhold proprietary information from deliverables under Section 3.?

How does an offeror include proprietary in deliverables associated with commercial offerings?

The purpose of this section of the SOW is enforce proper portion marking of proprietary information, data provided by the contract will be typically be a mixture of both information types. Indication that a deliverable contains trade secret/proprietary information allows the govenrment to apply secondary dissemination protections, e.g. ensuring only support contractors with a non-disclosure agreement are allowed to see such information.

38 Section C, C.1, 3.1., 3.5.

Section C, C.1, 13.1.

The inclusion of “materials created” in Sections 3.1., 3.5., and 13.1. contemplate that all materials created in the performance of this contract are non-commercial; however, being that this contract is predominantly for OOB commercial solutions, there is significant potential that many deliverables will not be “created” and would only be subject to commercial rights clauses. The inclusion of “materials created” in Section 3.1 Deliverables is inconsistent with the procurement of commercial products and services. The mixing of developmental activities with deliverables of commercial products and services unnecessarily confuses the characterization of delivered products and services from an intellectual property perspective. Further, such confusion may result in unnecessarily higher pricing.

If the evolution of any software solutions or requirements involves "materials created" in the future, this section will allow for such deliverables. Because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

39 Section C, C.1, 3.3. 27 of 240 Section 3. DELIVERABLES includes Section 3.3. Hardware Deliverables.

This procurement is for a commercial software solution with no Hardware Deliverables anticipated. Can the Government clarify the intent to include Hardware Deliverables? If not applicable, then recommend removing the Section.

If the evolution of any software solutions or requirements involves HW in the future, this section will allow for such deliverables. It is not anticipated that HW will be involved in this contract, but because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

40 Section C, C.1, 6.1. 28 of 240 The Government references performance at OCONUS locations.

If the software solution is being deployed in CONUS Cloud/On-Prem regions, can the Government clarify what performance is anticipated OCONUS? If not applicable, recommend removing the requirement for OCONUS performance.

During deployment of the SW as an enterprise, there is some possibility that OEM services may be required at OCONUS locations. Additionally, because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future. The contractor is not expected to provide SW that is compliant with foreign countries' standards or practices.

41 Section C, C.1, 6.3. 29 of 240 States "It is the Government's expectation that the Contractor Program Manager will be available in near real time by phone and/or email but from the contractor's facility during the Government's standard operating hours."

Is it the Government's desire that the OEM Contractor propose pricing for a full-time, dedicated PM to meet these availability requirements?

Program management requirements (as measured by part-time versus full-time) will be dictated by the scope of work needed to be accomplished in each task order. This statement is intended to convey the need to have communication pathway between the government and contractor to address PM-related matters during normal business hours.

42 Section C, C.1, 7.1. 29 of 240 States "(U) A DD-254 is not anticipated to be required at this time for the HCMS OEM IDIQ." However, there are a plethora of security requirements germane to the performance of the TS//SCI component of this acquisition.

Can the government please confirm that no DD254 will be issued at the IDIQ level?

The TS//SCI portion of the work is anticipated to be done entirely by the SI. If the requirements change, a DD254 will be issued to reflect those changes.

43 Section C, C.1, 8. 30 of 240 The Government includes reference to Government Property. As this is a procurement of a commercial solution to be delivered to the Government, no Government Property is anticipated during the performance of this contract.

Can the Government clarify what anticipated Government Property will be provided under this contract? If not applicable please consider removing the section.

It is not uncommon for the government to provide both GFP or GFI as part of task orders, but that GFP/GFI will be specified at the task order level when relevant.

44 Section C, C.1, 8.4. 31 of 240 Pursuant to IDIQ SOW 2.2.5., the Agency requires an OEM with a single-tenant or multi-tenant SaaS, or on-prem solution.

Section 8.4 contains a requirement for ad-hoc hardware and a mandatory requirement for the OEM to procure hardware within 10 days of receipt of the requirement. Inclusion of a requirement for the OEM to develop and maintain a procurement system meeting this requirement may result in unnecessarily higher pricing. This requirement appears to be more consistent with the functions of an SI rather than an OEM.

If the evolution of any software solutions or requirements involves HW in the future, this contract will allow for such deliverables. It is not anticipated that HW will be involved in this contract, but because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

45 Section C, C.1, 10.1.1. 31 of 240 The section states: "Contractors shall be able to fulfill full development efforts in less than 24 months."

This procurement is for the acquisition of a commercial solution based on commercially available features native to the product.

It is unclear the Government's intent/expectation when possibly defining Government niche requirements that currently do not fit a specific commercial product. The Government may request a feature enhancement, however the Government cannot dictate the acceptance and/or the development timeframe for a commercially available product. Please remove this section from the OEM RFP and include in the SI RFP, as the SI has the ability to alter and develop non-commercial enhancements to satisfy the Government's requirements.

See updated Section C.

SEE FAR 2.101 AND 3.104

# Reference (Section / Paragraph) Page # Question Response

OHR MOD PMO OEM

Questions / Comment Matrix

46 Section C, C.1, 14.4., 14.5. 33 of 240 States "(U) The contractor shall provide a solution that ensures that all systems, hardware, software, software engineering, and information technology associated with this effort is made in a manner that is accessible for people with disabilities as directed in the DIA Policy and Section 508 of the Rehabilitation Act of 1973 as amended in 1998 (Section 508)."

This procurement is for a commercial software solution. Can the Government clarify the intent to include hardware in this

If the evolution of any software solutions or requirements involves HW in the future, this contract will allow for such deliverables. It is not anticipated that HW will be involved in this contract, but because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

47 Section C, C.1, 14.10. 34 of 240 States " . . . . The contractor shall provide an API to the Agency for near real-time data ingest from the CSP repository to a consolidated Agency repository for use. in assessing risk to determine whether to approve a procurement and/or order removal of currently implemented hardware or software."

This procurement is for a commercial software solution. Can the Government clarify the intent to include hardware in this

See updated SOW that has this quoted text removed. However, if the evolution of any software solutions or requirements involves HW in the future, this contract will allow for such deliverables. It is not anticipated that HW will be involved in this contract, but because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

48 Section C, C.1, 14.11. 34 of 240 States "(U) Ensure the SCRM adheres to Agency standards, policies, and directives regarding allowable equipment; alignment with Agency risk management and procurement requirements; and the recapitalization and upgrade of hardware."

This procurement is for a commercial software solution. Can the Government clarify the intent to include hardware in this

If the evolution of any software solutions or requirements involves HW in the future, this contract will allow for such deliverables. It is not anticipated that HW will be involved in this contract, but because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

49 Section C, C.1, 14.12. 34 of 240 14.12. (U) Ensure that there is parity with publicly available secure hosting for generational recapitalization and upgrading of all contractor-furnished hardware, while complying with all supply chain risk management requirements and policies.

This procurement is for a commercial software solution. Can the Government clarify the intent to include hardware in this Section?

If the evolution of any software solutions or requirements involves HW in the future, this contract will allow for such deliverables. It is not anticipated that HW will be involved in this contract, but because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

50 Section C, C.1, 15.3 35 of 240 This is an acquisition for commercial software; non-commercial software is not anticipated to be provided.

Will the Government clarify its intent for requiring non-commercial data on a commercial acquisition? If not applicable, consider removing the section.

If the evolution of any software solutions or requirements involves non-commercial data in the future, this contract will allow for such deliverables. It is not anticipated that HW will be involved in this contract, but because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

51 Section C, C.2, 4. 42 of 240 The tasks and requirements identified for the OEM are significantly integration and implementation focused.

With the acquisition strategy to separately procure SI services in support of this transformation, can the Government define the division of labor and clarify which activities are to be lead by the SI vs. the OEM?

OEM professional services will be provided in support of the OEM SW, the SI professional services will be provided in support of the overall HCMS solution (to which the OEM SW is a component). The OEM contractor will provide support services to enable the SI and integration, but will not be solely responsible for traditional systems integration.

52 Section C, C.2., 4.1.5. 43 of 240 IDIQ SOW 18.0 Appendix B (Common Data Deliverables) calls CDRL A004 the "Management Plan." TO2 SOW Section 4.1.5 calls CDRL A004 the "Program Management Plan."

For consistency, recommend updating IDIQ SOW 18.0 Appendix B's title to the "Program Management Plan."

Please see updated SOWs

53 Section C, C.2., 4.1.5. 43 of 240 Redundantly shows CDRL A003 and also associates an incorrect title with it. Recommend removing "CDRL A003, PMP". Please see updated SOWs 54 Section C, C.2, 4.2.1. 43 of 240 Who shall have access to the sandbox environment described in Section 4.2, Task 2? Is it the Government's intent that the OEM

Contractor provide this Environment for use and access by the Government and the SI Contractor, or is it only for the OEM to provide "user/operational demonstrations"?

Government, SI and OEM personnel need access to the sandbox.

55 Section C, C.2, 4.2.1. 43 of 240 Does the OEM Contractor need to perform or obtain any accreditation for the sandbox environment? No 56 Section C, C.2, 4.2.1. 43 of 240 For the sandbox environment, shall the OEM Contractor provide ongoing operations and maintenance (O&M) of the environment, to include all patching and updates of the OEM product, for the entire TO Pop?

The O&M for this sandbox system will be minimal and mostly require software patching/upgrades as necessary.

57 Section C, C.2, 4.2.1. 43 of 240 Does the sandbox environment need to be deployed in a regulated cloud region (e.g., IL2, FedRAMP High, IL4, FedRAMP+, IL5), or can it be deployed in a commercial cloud region? Will any Controlled Unclassified Information (CUI), Personally Identifiable Information (PII), and/or Protected Health Information (PHI) be used in the sandbox environment?

The government confirms the sandbox will be hosted by contractor (whether thick client or cloud), allowing access to both government and SI as necessary.

58 Section C, C.2, 4.2.1. 43 of 240 Are there any interfaces to or external dependencies of the sandbox environment? No 59 Section C, C.2, 4.2.1. 43 of 240 Will the Government provide sample data to use in the sandbox environment, or is the OEM Contractor responsible for generating and providing sample data?

The government will provide sample data.

60 Section C, C.2, 4.3. 43 of 240 Is the Government requesting full time, dedicated resources to perform Process and Solution Mapping? If not, what is the anticipated level of effort the Government is requesting for this support?

The government anticipated full-time allocation, but the offeror should propose labor hours and types to best meet the government's requirement.

61 Section C, C.2., 4.3.1 44 of 240 The CDRL number referenced for the Product Drawings/Models and Associated Lists is incorrect. Change A009 to A008. Please see updated SOWs 62 Section C, C.2., 5.1.1 44 of 240 Section references topics/documents that are not listed in Section J, J.7 Attachment 6, Bidder's Library and are not provided.

These include 5.1.1.1 DIA RMF processes, 5.1.1.2 POA&M maintenance, and 5.1.1.5 DIA CIO Cyber & Security guidelines/policies/procedures.

Will the Government provide?

The responsibilities for adherence to these policies, procedures, and guidelines are primarily the responsibility of the SI, who will govern overall system solution.

63 Section C, C.2, 10.1 45 of 240 The Table identifies the Product Drawings/Models and Associated Lists CDRL Item # as A009. Change to A008. Please see updated SOWs 64 Section C, C.2, 12. 46 of 240 Incorrectly references CDRL Item A010 as the GFP report. Change A010 to A009. Please see updated SOWs 65 Section C, C.2., 12.1.1 46 of 240 References 12.1.1.1 HRMS FRD -- should be HCMS RFD; references 12.1.1.2 HRMS TRD -- should be HCMS TRD;

references 12.1.1.3 HRMS Interface Control Documentation, which was not provided in the RFQ solicitation document.

Please see updated SOWs

66 Section E 52 of 240 Recommend removing the following clauses, as Inspection/Acceptance for commercial products and commercial services is provided under paragraph (a) of 52.212-4:

52.246-2, 52.246-4, 52.246-6, 52.246-7, 52.246-9, 52.246-15

The clauses have been removed from solicitation.

SEE FAR 2.101 AND 3.104

# Reference (Section / Paragraph) Page # Question Response

OHR MOD PMO OEM

Questions / Comment Matrix

67 Section F 53 of 240 This procurement is for the acquisition of commercial products and commercial services. The following clauses are applicable to supplies which are defined in FAR 2.101: Supplies means all property except land or interest in land. It includes (but is not limited to) public works, buildings, and facilities; ships, floating equipment, and vessels of every character, type, and description, together with parts and accessories; aircraft and aircraft parts, accessories, and equipment; machine tools; and the alteration or installation of any of the foregoing.

Recommend removing the following clauses as not applicable:

52.211-17, 52.211-8, 52.211-9, 52.211-9 ALT I, 52.211-9 ALT II, 52.211-9 ALT III, 52.211-16, 5552.211-9005

The clauses have been removed from solicitation, with the exception of DARSI 5552.211-9005 which is required for any FFP contracts.

68 Section G, G.3 60 of 240 Clause 5552.232-9001 references "Cost Reimbursable Contracts". This acquisition is anticipated to be FFP, LH, and T&M, not cost-reimbursable. Recommend removing.

This is the payment clause for any T&M/LH contract with DIA.

69 Section H, H.1 - H.2 65 of 240 These clauses reference security clearances; however, Section C, C.1 (IDIQ SOW), 7.1, states: "A DD-254 is not anticipated to be required at this time for the HCMS OEM IDIQ."

Can the Government clarify the security requirements without a DD-254?

Unclassified as of right now, but the clause has been added in the event of a TO needing a DD-254.

This was also done to ensure that any potential bidders understand there maybe a requirement for FCL in the future.

70 General, Small Business Subcontracting

N/A The Solicitation includes several requirements regarding small business subcontracting. These requirements would necessitate the OEM to subcontract the majority if not all professional services associated with this solicitation.

Based on the acquisition strategy of having separate contracts for OEM and SI, is it the Government's intent to have the OEM subcontract the majority of the professional services as an additional intermediary between the OEM and the selected SI? If not, suggest the Government remove the subcontracting requirement for the OEM to more directly collaborate with the selected SI.

The government intends to leave the subcontracting information in the RFQ because if there are opportunities that exist for subcontracting then those opportunities will have to have a commercial subcontracting plan submitted.

71 Section I, I.26 - I.38 80-81 of

The referenced clauses are applicable when Certified Cost & Pricing Data is anticipated. The acquisition of commercial products and commercial services are exempt from the requirements for Certified Cost & Pricing Data. Recommend removing.

Some of the clauses have been removed; while others are required per DCMA and our payment clauses.

72 Section I, I.40 - I.42 81 of 240 The referenced clauses are for the order of supplies as defined in FAR 2.101 and not for the acquisition of commercial products and commercial services. Recommend removing.

The government will not remove these clauses

73 Section I, I.43 - I.44 81 of 240 These clauses are applicable only when a cost-reimbursement contract or a time-and-materials contract (other than a contract for a commercial product or commercial service) is contemplated. Recommend removing.

The government will not remove these clauses

74 Section I, I.45 81 of 240 This clause is applicable only when a cost-plus-incentive-fee contract is contemplated. Recommend removing. The clause has been removed from solicitation.

75 Section I, I.54 81 of 240 This clause is applicable only when the head of the contracting activity designates programs or requirements for which it is necessary that contractors be required to notify the Government of actual or potential labor disputes that are delaying or threaten to delay the timely contract performance. Has this program been designated by the head of the contracting activity? If not, recommend removing.

The clause has been removed from solicitation.

76 Section I, I.55 82 of 240 This clause is applicable only when a cost-reimbursement contract is contemplated. Recommend removing. Removed 77 Section I, I.56 82 of 240 This clause is not applicable in contracts for commercial products and commercial services. Recommend removing. Removed 78 Section I. I.57 82 of 240 This clause is applicable only for construction contracts. Recommend removing. Removed 79 Section I, I.59 82 of 240 This clause is applicable only for construction contracts. Recommend removing. Removed 80 Section I, I.66 82 of 240 Will the Government identify the anticipated hazardous material to be delivered under this contract? If not applicable, recommend removing.

The clause has been removed from solicitation.

81 Section I, I.69 82 of 240 This clause is not applicable in contracts for commercial products and commercial services. Recommend removing. The clause has been removed from solicitation.

82 Section I, I.70 82 of 240 This clause is applicable only in contracts for contractor operation of Government-owned or -leased facilities. Recommend removing.

The clause has been removed from solicitation.

83 Section I, I.79 83 of 240 Can the Government clarify the anticipated OCONUS performance under this contract necessitating this clause? If not applicable, recommend removing.

The clause has been removed from solicitation.

84 Section I, I.81 83 of 240 This clause is for non-competitive acquisitions and is to be used in lieu of 52.229-3. Recommend removing this clause, as this contract is being openly competed.

The clause has been removed from solicitation.

85 Section I, I.82-I.85 83 of 240 These clauses are not applicable per 48 CFR 9903.201-1(b)(6). Recommend removing. The clauses have been removed from solicitation 86 Section J, J.1 Exhibit A- CDRLs, A001-A007, A009-A031 123-129 of 132-166 of

CDRLs A001-A007, A009-A031 are all mapped to CLIN X009. CLIN X009 is the POT Unpriced Option JWICs licensing up to 30,000 users. Should these CRDLs be mapped to CLINs X003 (Labor) and/or X008 (Data Deliverables)?

See updated 1423 (CDRLs)

87 Section J, J.1 Exhibit A- CDRLs, A006, A031

Block 4 Authority DI-MISC-80711A/T is identical in both the DIDs and CDRL Table of Contents "DID Reference") for both A006 and A031. Was this intentional?

This is intentional, A031 is a specific type of Scientific and Technical Report with subtitle Process Mapping Document

88 Section J, J.1 Exhibit A- CDRLs, A008

130 of 240 Block 4 Authority does not reference the most recent version. Will the Government confirm which version is applicable? See updated 1423 (CDRLs)

89 Section J, J.1 Exhibit A- CDRLs, A008

130-131 of

CDRL A008 is not mapped to a CLIN. Should this CRDL be mapped to CLIN X003 (Labor) and/or CLIN X008 (Data Deliverables)?

See updated 1423 (CDRLs)

90 Section J, J.1 Exhibit A- CDRLs, A010

The Block 4 Authority on this DID is shown as FAR 52.219-9; however, on the CDRL Table of Contents, the "DID Reference" is shown as DI-MISC-80508B. Which is correct?

See updated 1423 (CDRLs)

91 Section J, J.1 Exhibit A- CDRLs, A013

141 of 240 The Backup Sheets, beginning on this page, are labeled "Backup Sheets to CDRL A014" and "ATTACHMENT 1 TO CDRL SEQUENCE NUMBER A014" but are located within the document immediately after the CDRL Item A013 DID. Will the Government confirm that the Backup Sheets pertain to CDRL Item A013?

See updated 1423 (CDRLs)

SEE FAR 2.101 AND 3.104

# Reference (Section / Paragraph) Page # Question Response

OHR MOD PMO OEM

Questions / Comment Matrix

92 Section J, J.1 Exhibit A- CDRLs A017

152 of 240 Block 4 Authority does not reference the most recent version. Will the Government confirm which version is applicable? See updated 1423 (CDRLs)

93 Section J, J.1 Exhibit A- CDRLs, A019, A021, A022

Block 4 Authority DI-MISC-80508B is identical in the DIDs for A019, A021, and A022 but different in the CDRL Table of Contents ("DID Reference"). Will the Government confirm which is correct?

See updated 1423 (CDRLs)

94 Section J, J.1 Exhibit A- CDRLs A020

155 of 240 DID states "Contractor shall deliver all executable code or access to application code". With a SaaS solution, application code is not provided. Recommend the Government update the DID.

If the evolution of any software solutions or requirements involves application code access in the future, this section will allow for such deliverables. Because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

95 Section J, J.1 Exhibit A- CDRLs, A021

122 of 240 The "DID Reference" shown in the CDRL Table of Contents for this CDRL Item (DI-IPSC-81488) specifies providing details regarding source code. Source Code is not provided with SaaS. Recommend the Government revise.

If the evolution of any software solutions or requirements involves source code access in the future, this section will allow for such deliverables. Because this contract could have a ten-year period of performance, the government is employing flexibility within the contract to account for some unforeseen changes in the future.

96 Section J, J.1 Exhibit A- CDRLs, A026

161 of 240 Block 4 Authority does not reference the most recent version. Will the Government confirm which version is applicable? See updated 1423 (CDRLs)

97 Section J, J.2, J.3 167-191 of

The labor portion of the pricing templates appears to be for cost-type contracts/TOs (CPFF, CPAF, etc.). The OEM IDIQ is for commercial products and services, which are exempt from providing certified cost data. Will the Government update the pricing templates to reflect T&M labor?

The Government is specifically asking for the information to help with price realism analysis that maybe conducted.

98 Section J, J.4, Requirement 25 194 of 240 Does the government intend to provide access to the HCM system for spouses and dependents? No 99 Section J, J.4, Requirement 35 196 of 240 How extensive are the tests and does this include proctored exams? Is the government looking to certify a skill or test The exams will not be proctored or extensive.

100 Section J, J.4, Requirement 39 196 of 240 How is the total cost of ownership calculated and what are the development products and services? This is a potential discussion to be had following contract award.

101 Section J, J.4, Requirement 41 197 of 240 Does the Agency have the triggers for automation identified? This is a potential discussion to be had following contract award.

102 Section J, J.4, Requirement 25 197 of 240 Are the promotion steps already identified? How is a promotion initiated: by employee, manager, HR, other? This is a potential discussion to be had following contract award.

103 Section J, J.4, Requirement 48 197 of 240 Will the government be more specific about "the HCM and partner applications"? Is this referring to other applications in the

DIA ecosystem? Or previous employer's applications?

This reference is to other applications in the DIA HCMS ecosystem

104 Section J, J.4, Requirement 63 199 of 240 Does the "and coordinating with partner applications for the removal/update/validation of credentials and system access." refer to applications within the DIA ecosystem? Or external to the Agency?

This reference is to other applications in the DIA HCMS ecosystem

105 Section J, J.4, Requirement 67 199 of 240 Will the government clarify the process is for "student loan repayment"? This is a potential discussion to be had following contract award.

106 Section J, J.5, 1.1.6. 202 of 240 States the following: "(U) As outlined in the Functional Requirements as a future, potential requirement, the government desires to provide a limited subset of HCM services to civilian employees in an unclassified HCM instance. This may be an extension or separate instance from the recruitment solution, or in conjunction with other DIA technologies already employed on the unclassified network." Will the Government quantify and clarify the "limited subset of HCM services"?

The list of subset services will be defined at a later date, but those are included in the definitions in the FRD currently. The idea is that the unclassified instance of the SW solution will likely only need to support a subset from the FRD.

107 Section J, J.5, 1.2.4., 1.2.4.1., 1.2.4.2.

204 of 240 State the following:

1.2.4. (U) The contractor shall provide a solution that is capable of interfacing with non-affiliates.

1.2.4.1. (U) The architecture, methodology, and security approach/controls utilized to enable a non-affiliate interface shall require government approval prior to implementation.

1.2.4.2. (U) The solution shall ensure logical separation between affiliates and non-affiliates.

Will the Government define how affiliate vs. non-affiliate data is stored and accessed?

This is a potential discussion to be had following contract award.

108 Section J, J.5, 1.2.6., 1.2.6.1. 204 of 240 States "(U) The contractor shall provide a solution capable of "(U) Automatic syncing of data across the HCM environment;"

Will the Government clarify if this is within the same security domain, or across multiple security boundaries (e.g., U/S/TS)?

Software instances of the solution will reside on multiple networks, however only the TS/SCI version will be system of record. Process of synchronization of data, if required, will be that of SI.

109 Section J, J.5, 1.2.6., 1.2.6.1. 204 of 240 States "(U) The contractor shall provide a solution capable of "(U) Automatic syncing of data across the HCM environment;"

Does the Government intend this syncing for the purpose of Continuity of Operations (COOP)?

Software instances of the solution will reside on multiple networks, however only the TS/SCI version will be system of record. Process of synchronization of data, if required, will be that of SI.

110 Section J, J.5, 1.2.6., 1.2.6.4. 204 of 240 States "(U) The contractor shall provide a solution capable of: (U) Importing/Exporting data in industry standard formats;" Will the Government specify which formats?

Standard data formats include, but are not limited to, JSON, CSV, and XML. Other formats may be included following contract award and defined by the SI contractor.

111 Section J, J.5, 1.2.11. 205 of 240 States the following: "1.2.11. (U) The contractor shall provide a solution that is self-healing with automated service restoration that is seamless to the end user. All HCM computer software, firmware, and service upgrades must be non-disruptive. If the computer, software, firmware or service upgrades will be applied to the HCM system, it must be pre-coordinated and approved by the Agency." Will the Government clarify "non-disruptive"? Commercial software patches or updates have published pre-defined maintenance windows and schedules.

Non-disruptive is defined by periods where upgrades and patches cannot be applied.

112 Section J, J.5, 1.3.2. 205 of 240 States "(U) Contractor shall provide a solution that is capable of integrating with internal and external sources at points in the solution's process flow (example: externally sourced elements of the hiring process): some external elements may replace elements of the solution's native processes." Will the Government define each of these touch points so the vendor may properly

Please refer to Figure/Diagram in Section 2 (Background) of TO2 SOW.

113 Section J, J.5, 1.4.1.11. 206 of 240 States "(U) Contractor shall provide a solution which honors tags to provide RBAC and ABAC." Will the Government clarify its expectations on how ABAC / tags will influence application security?

The solution should support role-based access control and attribute-based access control to restrict/enforce access.

114 Section J, J.5, 1.4.1.18. 207 of 240 States "(U) Contractor shall purge data in accordance with Agency compliance and retention plans." Will the Government provide the purge schedules so that Offerors can price appropriately?

The information within the TRD was included to be informative on the overall HCMS requirements, but the solution determinations for these areas will be done by other contractors.

115 Section J, J.5, 1.4.1.18. 207 of 240 States "(U) Contractor shall purge data in accordance with Agency compliance and retention plans." Has the Government identified authoritative systems of record? If so, can the Government please share with perspective bidders?

The information within the TRD was included to be informative on the overall HCMS requirements, but the solution determinations for these areas will be done by other contractors.

116 Section J, J.5, 1.4.1.18. 207 of 240 States "(U) Contractor shall purge data in accordance with Agency compliance and retention plans." Does the Government intend to govern/manage organization, position, time and labor, and employee data the same?

The information within the TRD was included to be informative on the overall HCMS requirements, but the solution determinations for these areas will be done by other contractors.

SEE FAR 2.101 AND 3.104

# Reference (Section / Paragraph) Page # Question Response

OHR MOD PMO OEM

Questions / Comment Matrix

117 Section J, J.5, 1.4.1.18. 207 of 240 States "(U) Contractor shall purge data in accordance with Agency compliance and retention plans." The Government mentions a retention plan. Will the Government provide the specific compliance and retention requirements?

The information within the TRD was included to be informative on the overall HCMS requirements, but the solution determinations for these areas will be done by other contractors.

118 Section J, J.5, 1.4.1.18. 207 of 240 States "(U) Contractor shall purge data in accordance with Agency compliance and retention plans." For the data that is not purged, will the Government require the Contractor to convert/transform and/or migrate data? If the data is migrated, can it be assumed the data structure is the same?

The information within the TRD was included to be informative on the overall HCMS requirements, but the solution determinations for these areas will be done by other contractors.

119 Section J, J.5, 1.4.1.18. 207 of 240 States "(U) Contractor shall purge data in…