N3943019R2126-0006.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to :

1) Provide response to Offer's questions.

2) Include Factor 3 in Section M.3 header.

3) Define title of paragraph C.3.2.3.3

4) DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.239-7010, and FAR 52.209-7 clauses are now in full text.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 64

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 11-Jul-2019

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N3943019R2126

X 9B. DATED (SEE ITEM 11)

22-May-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

11-Jul-2019

CODE

NAVFAC EXWC

CODE ACQ / NAVAL BASE VENTURA COUNTY

1100 23RD AVE BLDG 1100

PORT HUENEME CA 93043-4301

N39430 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N3943019R2126

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 6

a) Provide Government answers to the following contractor’s questions:

Q1: Page 15 of 40, Section C.3.2.3.14, Amendment 0001: Can the Government define “high availability?” Are any SLAs in place related to NITC environments?

A1: High Availability (HA) is a characteristic of a system, which aims to ensure an agreed level of operational performance, usually uptime, for a higher than normal period.

No specific SLAs are referenced with relation to the NITC Environment within the scope of this contract. SLAs may be part of individual task orders defined at time of task order generation.

Q2: Page 3, Amendment 0002, L.7 (4) Question 7 Specified in the Answer "There is no specific number or mix of past performance references required by the prime vs proposed subcontractor(s)."

Are we correct in reading that the Government requests no more than a total of three (3) past performance references without regard to the mix of references between prime and subcontractor(s)? Question 7 Specified in the Answer "There is no specific number or mix of past performance references required by the prime vs proposed subcontractor(s).”

A2: The limit is three total past performance references. It is at the Offeror’s discretion to use Prime only, Subcontractor only, or a mixture of Prime and Subcontractor.

Q3: Page 3 of 9, Amendment 002, L.7(4): Is there a minimum amount of references that must be submitted by the Prime?

A3: There is not a minimum amount of references that must be submitted by the Prime.

Q4: Page Numbers 48-49 of 80, Original Solicitation: 52.219-14 Deviation2019-O0003 Limitations on Subcontracting (Jan 2019) (Deviation 2019-O0003)

Based on the potential complexity of the tasks (services, construction, materials) that are awarded under this IQIQ MAC; where will the government account for the “50.1%” prime rule? Will this be applied for each awarded individual task order value, or at the final aggregate contract value to account for the 8(a) prime having generated more than 50% of the revenue on the contract?

A4: The Government will account for the 50.1% prime rule at the Task Order level.

Q5: Page 9 of 80, PWS, Section 3.1 Basic Requirements says “NITC requires all custom software developed by the government or its contractors furnished or maintained to be committed to the NITC managed/maintained Source Control Management (SCM) System prior to deployment into any NITC functional environment (on premise or cloud based).”

What SCM system NITC is using? Is it a COTS system, what is its names and who is the vendor? Or is it an in-house system?

A5: Currently NITC is standardized on a Git based SCM specifically, GitLab. The system is currently hosted onsite at the NITC Data Center. This may or may not be the case in the future, as such offerors should be prepared to support potential changes to the SCM in terms of the base technology (i.e. Git), management abstraction layer (i.e. GitLab), or the location in which it is hosted (i.e. Onsite at the NITC Data Center).

Q6: Page 72 of 80, Section L.7(4) Factor 4, Past Performance: To use a past performance reference from a subcontractor are they required to be a significant subcontractor? If they are required to be a significant subcontractor what is the minimum percentage of work/cost to be performed by a significant subcontractor?

A6: They are not required to be a significant subcontractor.

Q7: Page 73 of 80, Section L.7(5) Factor 5, Price: For pricing, can the Government please provide an anticipated start date?

A7: The anticipated start date is May 2020 (three months after the estimated award date).

Q8: Page 4 of 80, PWS, Section C.1.3 Scope: in the scope of the contract it lists seven functional areas. PWS 3 Performance Requirements page 9 only has detailed PWS areas for five of the functional areas.

Please clarify if the Cloud Operations/Migration/System Development and Secure DevOps Infrastructure are to be detailed in the offeror’s proposal. And if so, are there any specific requirements under these two functional areas that you would like offerors to address?

A8: Offeror’s may choose to detail “Cloud Operations/Migration/System Development and Secure DevOps Infrastructure” capability/experience within technical approach and past performance. Specific requirements are not outlined.

Q9: Amendment 0003, Page 5, Section L.7(4), Paragraph 3: Please clarify that we can reference only three project/ contract that we are providing Attachment J-2 for in our technical proposal.

A9: Only three projects/contracts can be referenced.

Q10: Amendment 0003, Page 5, Section L.7(4), Paragraph 3: Please confirm that Factor 4, Past Performance is only CPAR or Attachment J-2. Please let us know if a write up is also required.

A10: Offerors should not provide a narrative for past performance in addition to a CPARS or Attachment J-2.

Q11: Page 78 of 80, Paragraph (4) Factor 4 Past Performance (fifth bullet) states: " Relevancy of projects based on the Past Performance Relevancy Rating Method table below. The term “magnitude” refers to projects/contracts within a range of $3.5 to $4 million, the terms “scope” and complexity” in the Past

Performance Relevancy Rating Method table below have broad meaning such that evaluators will consider any feature of a past project/contract which has a predicative effort on performance on the current contract."

Does this mean that each past performance (project/contract) must be at least $3.5 to $4 million in value to be consider relevant or did the Government use these values as an example?

A11: For Past Performance to be considered more relevant, projects/contracts must be at least $3.5 to $4 million in value.

Q12: Section M, (5) Factor 5 Price (page 80) states that the Government will evaluate price by comparison of proposed prices received in bidders responses, proposed prices with the IGCE, use of historical information and market survey results. To ensure fair, equitable and reasonable comparison between bidders prices, and comparison with historical and market survey results, the Government will need basic information about how each bidder defined and qualified the labor category titles in Attachment J-1, and which work location was used.

Salary rates will differ greatly between a position with a bachelors degree and 10 years of experience and a masters degree and 20 years of experience, or work performed in Washington, DC vs. Norfolk, VA.

How will the Government ensure fair, equitable, and reasonable comparison between bidders responses for their price evaluation?

A12: Price evaluation is based on the total price not on each labor category level. Additionally, all offerors were provided with location percentage estimates for offeror’s pricing consideration in Amendment 0004 and 0005.

Q13: Page 72 of 80, Section L.7 (3) Factor 3 Safety: We have EMR 1.0 and DART and TRC 0. Should we still need to submit those factors in the document? Please clarify.

A13: Yes, you still need to submit those factors in the document.

Q14: We just completed our CMMI L-3 V2.0 reappraisal 2 weeks ago and we are still waiting for the assessment results to be published. Our current CMMI L-3 V1.3 expired on a week ago. Can we submit the appraisal confirmation from the CMMI institute?

A14: CMMI appraisal confirmation may be submitted.

Q15: In reviewing CDRL 0005 in Amendment 004, it requires a System Security Plan ( as outlined in PWS 4.1.8.1) be submitted NLT 10 business days following contract award. No work may begin on this contract until the plan is approved. This applies to contractors and subcontractors. Since this is a multiple-award IDIQ, is it okay if the SSP can be delivered NLT 10 business days of receiving a Task Order award?

A15:The SSP can be delivered NLT 10 business days of receiving a Task Order award

Q16: Amendment 0004, page 10 of 40. When asked in Q25: “Page 4, Section C.1.3 Scope, Paragraph 1, Amendment 0001: Bullets 1, 2, 3, 4, and 7 in this list correspond to the five functional areas in the PWS. Is the offeror expected to respond to bullets 5 and 6 as part of their Technical Approach, given they are not distinctly broken out as sections in the PWS?” The Government response was, “A25: Corrected. Each item is now broken out.” It appears now that the previous 7 areas have been expanded to 9 areas. But the PWS within Amendment 004 still addresses requirements for only the same 5 areas. Cloud Operations, - Cloud Migration, Cloud System

Development and Secure DevOps Infrastructure requirements are not outlined in the Performance Requirements.

It appears that each item has not been broken out into specific requirements as stated. It is unclear how Offerors are to respond to the requirements with this change given Section L asks Offerors to respond to 5 areas.

Could the Government clarify its Performance Requirements to align with the scope of specific tasks and to Section L submission requirements?

A16: Offeror’s may choose to detail “Cloud Operations/Migration/System Development and Secure DevOps Infrastructure” capability/experience within technical approach and past performance. Specific requirements are

Q17: The updated list of functional areas listed under C.1.3 of Amendment 4 includes areas not listed as requiring a detailed narrative response under L.7(1). For the proposed Technical Approach should the added functional areas of Cloud Operations, Cloud Migration, Cloud System Development, and Secure DevOps Infrastructure be addressed as subsections of IT Operations Management and Enterprise? That would line up the functional areas listed under Section C.1.3. with the five functional areas listed in Section L.7(1) (SDLC, Cyber Security, Business Systems, IT Operations, and Analysis and Management). Please confirm.

If this is accurate, will the government please amend PWS C.3.2.4 to include Cloud Operations, Cloud Migration, Cloud System Development and Secure DevOps Infrastructure? This will allow us to provide an accurate proposal response to the requirements of L.7(1).

A17: Offeror’s may choose to detail “Cloud Operations/Migration/System Development and Secure DevOps Infrastructure” capability/experience within technical approach and past performance. Specific requirements are

Q18: Page 4 of 6, Amendment 0003, Section L.7(1): Factor 1, Technical Approach requires Offerors to provide a copy of the appraisal and/or certificate for its CMMI or equivalent model-based process maturity certification.

Will the government confirm that the appraisal/certificate will not be included in the page count for Volume I?

A18:The appraisal/certificate will not be included in the page count.

Q19: Page 76 of 80, Section M.3: Header says Evaluation Factors apply only to Technical Factors 1 & 2.

However, Body of text (2. Definitions) says Evaluation Factors apply to “each nonprice factor.” No other adjectival rating, description, or definitions is provided for Technical Factor 3.

Will the Government clarify/confirm if Technical Factor 3 is included in M.3 Evaluation Factors?

A19: Technical Factor 3 is included in M.3 Evaluation Factors. Section M.3 header now states: “M.3

ADJECTIVAL RATINGS, DESCRIPTIONS, DEFINITIONS FOR TECHNICAL

FACTORS 1, 2, & 3”.

Q20: Page 71 of 80, Section L.7 (1), Paragraph 2: Offerors shall also describe relevant Capability Maturity Model Integration (CMMI) or equivalent model-based process maturity certification. As a part of this description, offerors shall identify the granting organization, applicable model, level achieved and provide a copy of the appraisal and/or certificate.

Are the appraisal certificates included as part of the page count, or can this document be submitted as an Appendix without taking up page count?

A20: Appraisal certificates are not included as part of the page count. A similar question was answered in Amendment 0002, Page 2 of 9, Question 2.

Q21: Page 71 of 80, Section L.7 (2), 2nd Sentence: The proposed plan must include a quality management plan which describes your approach in accordance with ANSI/ISO/ASQC-9000 (for hardware) and IEEE/EIA 730 (for software) standards.

We demonstrate Software Quality Assurance (SQA) capabilities as described in the CMMI-Dev Process & Product Quality Assurance (PPQA) practice area. Do you agree that a management plan that meets CMMI-Dev LIII SQA practice area capabilities would be in accordance with the IEEE 730.2014 standard?

A21: Quality management plans will be assessed based on requirements within the solicitation.

Q22: Pages 9 & 14 of 80, Sections C.3.1 & C.3.2: Does NAVFAC want the contractor to use existing systems including HP Service Manager, HP Quality Center (HPQC) and Service Ticketing System (STS) to manage all IT workloads or are you expecting us to introduce new systems of management for Business System and enterprise IT Operations?

A22: Offerors would be expected to manage workloads on existing and future NITC management systems.

Introduction of new systems of management are not a specific criteria in this solicitation.

Q23: Page 24 of 44, Amendment 0004, Section 3.2.3.3: Performance Work Statement (PWS) paragraphs 3.2.3.2 and 3.2.3.3 are both titled "Recurring Support."

Will the Government remove the title "Recurring Support" from PWS paragraph 3.2.3.3 and bold the title "Change Management Procedures" if this is the intended paragraph title?

A23:Yes, the Government will remove the title "Recurring Support" from PWS paragraph 3.2.3.3 and bold the title to "Change Management Procedures"

Q24: Page 3 of 6, Amendment 0003, Section L.5.d.: Each section shall start on a new page...

Can the Government confirm that by "each section," it is referring to each Factor? I.e., Factor 2: Management Plan will begin on a new page even if the Technical Approach does not fill all space on the prior page, but subsections inserted within each factor need not begin on a new page, which would present a challenge to remaining within the page limitations.

A24: Each Section is referring to each Factor.

Q25: Page 5 of 6, Amendment 0003, Section L.7 (5): For Volume II Price Proposal, is the contractor required to provide a more detailed cost narrative detailing direct labor, indirects, and supporting documentation, or just provide the information requested in letters a through c of the instructions?

A25: Pricing submission requirements are delineated in Section L.7 (5), items “a” through “c”. There is no requirement for cost narratives detailing direct labor, indirects, and/or supporting documentation.

Q26: Page 3 of 6, Amendment 0003, Section L.5.d.: The Cover Letter, blank pages, tables of contents, and indexes are not considered a 'page' for purposes of the above page limit.

Can the Government confirm when it refers to a "Cover Letter" it is referring to the proposal title page, or is a cover letter required as part of the submission?

A26: A Cover Letter is required as part of the submission.

Q27: Page 2 of 80, Section B: Is the offeror required to submit a completed Section B with its proposal as part of Volume II Price Proposal?

A27: Yes, the Offeror is required to submit a completed Section B with its proposal as part of Volume II Price Proposal.

Q28: Page 3 of 6, Amendment 0003, Section L.7 (5): For the VETS-4212 report filing, representations and certifications, and company financial statement reports, can the Government provide guidance to joint venture offerors on whether these documents should be submitted in the name of the offeror/joint venture, in the name of the joint venture managing member, or in the name of each joint venture member?

A28: For the VETS-4212 report filing, representations and certifications, and company financial statement reports, documents should be submitted in the name of the Offeror/Joint Venture.

Q29: Page 43 of 80, Section I: Section I includes clauses such as 252.227-7013, 252.227-7014, 52.209-7, and 252.239-7010 that are typically required to be filled by the offeror as part of its proposal.

Can the Government confirm these clauses are only required to be filled as part of task order proposals solicited under the IDIQ, or otherwise release these clauses in full text to be filled and submitted as part of Volume II Price Proposal?

A29: DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.239-7010, and FAR 52.209-7 clauses are required to be filled out at the IDIQ level and are now in full text in Section I and Section K.

Q30: Page 13 of 40, Amendment 0004, Section C: Section C is titled both Statement of Work and Performance Work Statement.

Can the Government please clarify whether the RFP Section C provides a Statement of Work or PWS?

If ECITS is to be a performance-based contract, will the Government provide well-defined performance criteria?

Given that this is a Firm Fixed Price (FFP) contract, what is the penalty for a poorly performing contractor who is awarded an FFP contract?

How will the Government judge and evaluate the performance?

A30: The RFP Section C provides a Performance Work Statement. All performance evaluation criteria will be provide at the Task Order level.

Q31: Page 14 of 40, Amendment 0004, Section C.1.3: "The scope of this effort is to acquire IT services and solutions through the performance of broad ranges of services across multiple functional areas..."

Is the Government's intent to evaluate the proposed offeror across each of the IT services and functional areas?

If yes, then the Government has opted to effectively set aside this procurement for either (a) A very large super 8(a), e.g., Alaska Native Corporation or Native Indian Tribe Owned Company or (b) a mentor-protégé joint venture between a very large company and an 8(a) company.

We tremendously appreciate the Government's intent to have this opportunity set aside for 8(a); however, in order to avoid limiting competition, we request that the Government clarify that the contractor evaluation criteria will be demonstrating best value to the Government in one or a few of the areas outlined, and that it is not necessary for the contractor to have demonstrated experience across all areas.

RESERVED. WILL BE ANSWERED IN AMENDMENT 7.

Q32: Page 5 of 6, Amendment 0003, Section L.7 (4): In order to facilitate the Government's evaluation of the multiple CPARS/PPQ documents submitted with Factor 4: Past Performance, may the offeror opt to include a separate table of contents as part of this factor?

A32: Yes, it is at the Offeror’s discretion to include a separate table of contents for Factor 4, Past Performance.

Q33: Page 25 of 40, Amendment 0004, Section 3.2.4.14: Provide for the installation, configuration, maintenance, sustainment and operation of storage for each designated environment including but not limited to configuring redundant storage systems for high availability and data integrity.”

Can the Government define “high availability?” Are any SLAs in place related to NITC environments?

A33: High availability (HA) is a characteristic of a system, which aims to ensure an agreed level of operational performance, usually uptime, for a higher than normal period.

No specific SLAs are referenced with relation to the NITC Environment within the scope of this contract. SLAs may be part of individual task order defined at time task order generation.

Q34: Page 6 of 6, Section L.7 (4): “Rates shall be fully priced direct labor hourly rates which include: base pay rate, fringe benefits, operations overhead, general and administrative (G&A) expense, profit, and any other applicable rates and factors..”

Please confirm that offerors do not need to submit a breakdown of the costs (base pay, fringe, overhead, etc.) for the rates proposed.

A34: There is currently no requirement to submit any cost element breakdowns.

Q35: May the offeror submit key personnel resumes as appendices to the Management Plan outside page count in order to further detail our ability to manage the contract effectively upon award?

A35: It is at the Offeror’s discretion to submit personnel resumes and will be included in your page count;

anything beyond 55 pages will be evaluated.

Q36: Page 4 of 6, Section L.7 (2): "If subcontracting is contemplated, offerors shall provide a full description of:

the proposed subcontractors"

We recognize the rapid evolution of technology and tools to be utilized in performing the work. Therefore, a successful offeror likely will need to add additional subcontractors beyond the original list of subcontractors submitted with the proposal in order to provide optimal support. Can the Government confirm that a prime contractor selected for an award will be able to add additional subcontractors after award of the original multi-award IDIQ?

A36: Yes, Prime contractors can add additional subcontractors after award of the original multi-award IDIQ.

Q37: Page 14 of 40, Amendment 0004, Section C.1.3: "The scope of this effort is to acquire IT services and solutions through the performance of broad ranges of services across multiple functional areas, including but are not limited to:

- Systems Development Lifecycle Support

- Cyber Security Support

- Business Systems Operations and Support

- IT Operations Management and Enterprise

- Cloud Operations

- Could Migration

- Cloud System Development

- Secure DevOps Infrastructure

- Analysis and Management Services."

Bullets 1, 2, 3, 4, and 9 in this list correspond to the five functional areas in the PWS, paragraphs 3.2.1-3.2.5. Is the offeror expected to respond to bullets 5 through 8 as part of their Technical Approach, since they do NOT directly correspond to any section 3.2.X of the PWS?

A37: The services and functional areas listed within bullets 5-8 may be addressed by Offeror within the scope of the PWS overall technical approach and/or individual PWS paragraphs.

Q38: Page 4 of 80, Section C.1.3: The scope of the contract lists seven functional areas. PWS 3 Performance Requirements page 9 only has detailed PWS areas for five of the functional areas. Please clarify if the Cloud Operations/Migration/System Development and Secure DevOps Infrastructure are to be detailed in the offeror’s proposal. And if so, are there any specific requirements under these two functional areas that you would like offerors to address?

A38: Offerors may choose to detail “Cloud Operations/Migration/System Development and Secure DevOps Infrastructure” capability/experience within technical approach and past performance. Specific requirements are

Q39: Page 27 of 40, Amendment 0004, Section C.3.2.4.2: There are many types of Mainframe architectures (HW and SW) that have been utilized by the Government of the years (i.e. AS/400, AIX, HP-UX, etc.) What type of mainframe systems (HS/SW) will the contractor be required to support?

A39: OS: Mainframe z/OS (Operating System for Batch); CICS (Operating System for Online version, reports);

Database: CA Datacom; Application: COBOL/IDEAL

Q40: Page 10 of 40, Amendment 0004, Question 25: As per Amendment 0004 Q&A 25 it states that each item is broken out in relation to the functional area. Yet the Government has now 9 functional areas in the Scope of Work but have only provided a detailed breakdown of 5 of the functional areas. Is the Government planning to breakdown Cloud Operations, Cloud Migration, Cloud System Development, and Secure DevOps Infrastructure under the performance requirements (PWS 3.2)?

A40: Offerors may choose to detail “Cloud Operations/Migration/System Development and Secure DevOps Infrastructure” capability/experience within technical approach and past performance. Specific requirements are

Q41: Page 72 of 80. Section L.7 (4): Factor 4 Past Performance requires offerors to submit either a CPARS and/or PPQ for Factor 4. If a subcontractor’s CPARS is considered to proprietary information, can the subcontractor submit a separate sealed past performance package with the CPARS OR should the subcontractor’s sealed past performance package be included with the Prime’s package?

A41: Yes, a Subcontractor can submit a separate sealed past performance package with CPARS.

Q42: We ask that the government extend the proposal due date one week, to Monday, July 29, 2019, to ensure that Offerors have sufficient time to submit a compliant proposal that incorporates any and all last minute changes and/or revisions to the RFP.

A42: No, the proposal due date will remain 22 July 2019 before 5:00 PM PST as stated in Amendment 0004 and Amendment 0005.

Q43: Per Amendment 0005 response confirming that proposals are due to the cited address no later than 22 July 2019 at 5:00 PM PST requires Offerors not in the local area to ship its proposal as early as Thursday, 18 July to ensure the Overnight delivery gets to the installation and mailstop location in a prompt and assured time. Will the Government consider extending the proposal due date to coincide with 3 weeks after its release of, “A consolidated document will be provided in the next Amendment for Offeror’s final proposal submissions” as stated in A17 and A29 response in order for Offerors to have proper time to review the final document and ensure all changes provide in al amendments are identified and addressed.

A43: No, the proposal due date will remain 22 July 2019 before 5:00 PM PST as stated in Amendment 0004 and Amendment 0005.

Q44: Page 10 of 20, Amendment 0005, paragraph 2 states, “4. The max number of pages for Factors 1, 2, and 3 has been changed from a 44-page limit to a 55-page limit. However, in Amendment 0004, the Government provided this guidance on page 9 of 40 in A21, “At this time 55 page increase is allowable.” The content of the response suggested the entire Volume I including Factors 1, 2, 3 and 4, were increased by 55 pages. Please confirm the max pages for Factors 1, 2 and 3 and that Factor 4 has no page limit

A44: As stated on page 10 of 20, Section L.2, Amendment 0005, the max number of pages for Factors 1, 2, and 3 has a total limit of 55 pages. Any pages that exceed the 55-page limit will not be evaluated.

Q45: Does the government require Offerors to acknowledge/sign/submit SF 1449 and all amendments in its submission? If so, how is this to be accomplished?

A45: An SF 1449 in not applicable or required for this Solicitation.

B. Portion of the Solicitation were altered as follows:

1. The header of Section M.3 now states: “M. 3 ADJECTIVAL RATINGS, DESCRIPTIONS, DEFINITIONS

FOR TECHNICAL FACTORS 1, 2, & 3.”

2. DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.239-7010, and FAR 52.209-7 clauses are required to be filled out at the IDIQ level and are now in full text in Section I and Section K.

3. “Recurring Support” was removed from Section C.3.2.3.3, “Change Management Procedures” is now the title.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

PERFORMANCE WORK STATEMENT

ENTERPRISE COMPUTER AND INFORMATION TECHNOLOGY SERVICES (ECITS)

1. INTRODUCTION

The Naval Facilities Engineering Command (NAVFAC) Command Information Officer (CIO) is procuring information technology services including Systems Development Lifecycle support, Cyber Security support, Business Systems Operations and Support, IT Operations Management, and Enterprise Analysis and Management Services in support of all NAVFAC personnel, stakeholders and users throughout the world. The NAVFAC Information Technology Center (NITC) serves as NAVFAC primary Information Technology service provider offering a wide variety of technical solutions and support to the NAVFAC organization.

1.1. Mission

NITC is NAVFAC center of excellence for delivery of Enterprise Business Systems and applications.

NITC is focused on IT service delivery and support of Enterprise business applications that enable Navy business processes. NITC is responsible for the complete system life cycle (design, development, implementation, operations/maintenance, enhancement), Enterprise Operations support, system cyber security, Information Technology (IT), Cloud Systems Operations and Development, as well as supporting NAVFAC business systems, applications, hardware and software. NITC is the Central Design Agency (CDA) for NAVFAC business systems and provides/manages the hosting infrastructure for non-mainframe business systems. NITC is the CDA for mainframe systems that are unique to NAVFAC (e.g. FIS).

1.2. Background

NAVFAC Command Information Officer (CIO) is responsible for the oversight and management of Information Technology tools and capabilities to NAVFAC personnel, stakeholders and users throughout the world. NITC reports to the CIO office. The NITC organization provides the expertise, management discipline, and specialized technical skills necessary to ensure that best value Information Technology is acquired and managed in a manner consistent with law, and DoD and DoN policies and procedures. NITC delivers a range of services including: CDA responsible for software configuration and sustainment of Navy facilities systems;

production system support for all NAVFAC enterprise systems; command-wide management of Navy Marine Corps Internet (NMCI) / Next Generation (NGEN) and Navy Enterprise Network (ONE-NET) services; IT/IM acquisition and portfolio management; telecommunications support, NAVFAC Cloud Brokerage; and Cyber Security and Cyber Security compliance for systems, devices and networks.

1.3. Scope

NOTE: Complete list of acronyms applicable to this Performance Work Statement (PWS) are explained in Appendix B.

The scope of this effort is to acquire IT services and solutions through the performance of broad ranges of services across multiple functional areas, including but are not limited to:

- Systems Development Lifecycle Support

- Cyber Security Support

- Business Systems Operations and Support

- IT Operations Management and Enterprise

- Cloud Operations

- Cloud Migration

- Cloud System Development

- Secure DevOps Infrastructure

- Analysis and Management Services.

The contractor may be required to possess one or more of the following credentials at the individual task order level:

ISO 9001:2000

ISO 9001:2008

CMMI Level III (or higher) – DEV CMMI Level III (or higher) – SVC Oracle Certified Gold Partner Microsoft Certified Partner

ISO/IEC 20000

Information Technology Infrastructure Library (current version)

PARTNER PROGRAM

2. GENERAL REQUIREMENTS

2.1 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

2.2 Business Relations

The contractor shall successfully integrate and coordinate all activity needed to execute the requirement.

The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel.

2.3 Contract Administration and Management

The following subsections specify requirements for contract, management, and personnel administration.

2.3.1 Contract Management

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The contractor must maintain continuity between the support operations at various locations and the contractor's corporate offices. Localities requiring support may include, but not limited to:

1. Port Hueneme, CA

2. San Diego, CA

3. Washington DC

4. Pearl Harbor, HI

5. Norfolk, VA

6. Yokosuka, Japan

7. Kansas City, MO

8. Bremerton, WA

Specific place of performance will be addressed at the task order level.

2.3.2 Contract Administration

The contractor shall establish processes and assign appropriate resources to effectively administer the requirement. The contractor shall respond to Government requests for contractual actions in a timely fashion. The contractor shall have a single point of contact between the Government and Contractor personnel assigned to support contracts or task orders. The contractor shall assign work effort and maintaining proper and accurate time keeping records of personnel assigned to work on the requirement.

2.3.2.1 Contractor Personnel Security Status Report. The purpose of this report is to maintain current and accurate records of the hiring and related clearance status of all contractor and subcontractor personnel. Information contained is considered Personally Identifiable Information

(PII) and must be protected and transmitted as such. Verification of U.S. citizenship and background investigation results for all personnel will be conducted by the government Security Management Office.

The report shall contain, at minimum:

a. Full name, with middle name, as applicable, with social security number;

b. Citizenship status with date and place of birth;

c. Proof of the individual’s favorably adjudicated background investigation at the applicable level

(as required by each functional area of the PWS), consisting of identification of the type of investigation performed, date of the favorable adjudication, name of the agency that made the favorable adjudication, and name of the agency that performed the investigation. If personnel shall be performing across multiple functional areas with different required IT levels, the personnel shall demonstrate performance at the highest required IT level;

d. Company name, address, phone and fax numbers with email address;

e. Location of on-site workstation or phone number if off-site;

f. Delivery order or contract number and expiration date; and name of the Contracting Officer;

g. Contract labor category

h. Date request letter sent to Contracting Officer’s Representative (COR)

i. Date of Common Access Card (CAC) issuance and expiration;

j. Comments (if applicable)

The Contractor Personnel Security Status Report shall be delivered within 10 business days of award. The Contractor is required to provide and keep current the information for each individual.

Should any contractor or subcontractor personnel information or status change, or if contractor/subcontractor employees are added or removed from employment on this contract, the Contractor shall provide an updated information list within 3 business days of the change. See CDRL 0001- Contractor Personnel Security Status Report.

2.3.2.2 Monthly Contract Status Report. Each Prime contractor shall create and maintain a contract summary monthly status report which reports on high level metrics, performance, cost (including Earned Value Management metrics when applicable)/price and schedule elements for all active awards within the reporting time period. Strategic planning, staffing/training and certification status, risk management, problem and issue identification/resolution and action plans shall be included. See CDRL 0002- Monthly Contract Status Report.

2.3.2.3 Monthly Contract Status Report Meeting. Each Prime contractor shall participate in a contract summary monthly status meeting with government personnel such as the contracting officer and CORs. The prime shall ensure participation from their designated staff. The contract summary monthly status report shall be reviewed and discussed.

2.3.2.4 Contract Corrective Action Plan. A corrective action plan is a step by step plan of action that is developed to achieve targeted outcomes for resolution of identified problems or issues. The government may request that the contractor submit a corrective action plan for contract administration and management issues (including safety, training, security, clearance and cybersecurity workforce issues) if determined necessary. To be submitted ad hoc in accordance with CDRL- 0003 Contract Corrective Action Plan upon request.

2.3.3 Personnel Administration

The contractor shall provide management and support as required. The contractor shall provide for their employees during designated Government non-work days or other periods where Government offices are closed due to weather or security conditions. The contractor shall maintain the good standing of their employees by providing initial and refresher training as required to meet the performance work statement (PWS) and basic contract requirements. The contractor shall make necessary travel arrangements for employees. The contractor shall provide necessary infrastructure to support contract tasks for on-site and off-site support on a task order basis. The contractor shall provide administrative support to employees in a timely fashion (time keeping, leave processing, pay, emergency needs).

2.3.3.1 Contractor Training Requirements. All active contractor personnel working under this contract, including all subcontractor personnel, shall successfully complete the current applicable version of the DoD Cyber Awareness Challenge on an annual basis. The current version is Cyber Awareness Challenge 2019;

it is available in TWMS for resources with TWMS access or via DISA website (URL will be provided or KIOSK located in EXWC Buildings made available). All active contractor personnel, including subcontractors, are required to successfully complete an online OPSEC training course on an annual basis.

All contractor personnel, including subcontractor personnel, requiring a NMCI email account or system access shall successfully pass the required annual training to maintain the account and/or access. See section 4.1.3 for access requirements.

Additionally, all contractor personnel (including subcontractor personnel) located at a Government facility (such as Naval Base Ventura County) shall successfully complete and keep current any safety and security training required by that on-site location. Training may include, but is not limited to:

1. Active Shooter training

2. Naval Criminal Investigation Service (NCIS)

3. Records Management

4. Privacy and PII Awareness Training

The contractor shall maintain and keep up-to-date their employee Cyber certification and base safety/security and access training, and shall pay for all labor, training, training travel, study time, exam and certification/re-certification. The government may request proof of completion at any time.

2.4 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations.

2.5 Contractor Personnel, Disciplines, and Specialties

The contractor shall accomplish the assigned work by employing and utilizing qualified personnel. The contractor shall match personnel skills to the work or task with a minimum of under/over employment of resources. All resources assigned shall meet all personnel requirements, including clearance standing and cybersecurity workforce standing, at time of task order award.

Contractor and subcontractor personnel may be required to hold professional certifications, as noted within individual task orders. See Appendix C – Professional Certifications for further information regarding professional certifications. See PWS section 4.1.7 for Cyber Security Workforce requirements.

The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

2.5.1 Contractor Identification

All Contractor employees shall ensure that when participating in meetings with Government and/or other Contractor employees, that their personnel properly identify themselves as Contractor employees so that their actions will not be construed as acts of Government officials.

As per DFARS 211.106, “Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. All contractor employees shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.”

Contractor shall ensure that external correspondence signed by Contractor employees is on company letterhead. Internal correspondence, including e-mail and memoranda, must include the name of the company in the signature line or in another clearly identifiable location. In all contact with the public and Government officials, contractor personnel shall identify themselves as contractor employees working under contract to NAVFAC.

Contractor shall ensure that their onsite personnel, when receiving or placing telephone calls, identify their employer, in addition to whatever other appropriate greeting are used.

All Contractor staff working on-site at any of the client installations during task order performance shall wear at all times a DoD or Contractor furnished Identification. Additionally, contractor workspaces will be clearly marked “contractor” and their company name and their name.

The Contractor must comply with the implementation of Federal Information Processing Standards (FIPS) Publication Number 201, Personal Identify Verification of Federal Employees, and Contractors.

2.6 Location and Hours of Work

Accomplishment of the results contained in this PWS requires work at contractor facilities, on-site at government facilities, locations during travel in support of designated activities. Remote work may be authorized as described within individual task orders.

The exact locations of individual efforts will be designated on each individual task order as described in section 2.3.1.

Hours of work shall vary based on the task being performed, but will generally conform to the NAVFAC standard business hours of 0600-1800. Certain tasks may require work and travel after normal business hours, including evenings, weekends, and holidays. NITC is a 24/7/365 facility. Some task orders will require support 24/7/365 and/or on-call support after standard business hours.

Actual hours of work will be included within individual task orders.

Normal workdays are Monday through Friday except US Federal Holidays. Workers typically work eight

(8) hours per day, 40 hours per week. Flextime workers start not earlier than 0600 and not later than 0900.

All employees are expected to be available during core hours (0900 to 1500).

2.7 Travel / Temporary Duty (TDY)

Travel locations include both CONUS and OCONUS and will be specified at the task order level.

Anticipated locations include but are not limited to:

1. Port Hueneme, CA

2. San Diego, CA

3. Washington DC

4. Pearl Harbor, HI

5. Norfolk, VA

6. Yokosuka, Japan

7. Kansas City, MO

8. Bremerton, WA

9. Charleston, SC

10. Naples, Italy

11. Rota, Spain

12. Marianas, Guam

3. PERFORMANCE REQUIREMENTS

3.1 Basic Requirements

Contractor support is required to assist NITC in achieving their goals and objectives. Primary areas of consideration are Systems Development Lifecycle, Cyber Security, Production Systems, IT Operations Support, Operations Support, and Enterprise Analysis and Project Management. This PWS specifies the tasks to be performed, deliverables to be provided and performance objectives to be met in support of NAVFAC business systems.

The Contractor shall furnish all work, management, supervision, labor and materials necessary to ensure the effective and efficient performance of functions identified throughout this PWS which make up this requirement.

The Contractor must be capable of providing flexible, responsive, and high quality services and support. The Contractor will conduct travel and reviews that are necessary to ensure the effective and efficient performance of functions identified throughout this PWS which make up this requirement.

NOTE: Any proposed use of open source technology must be pre-approved by the Government at its discretion.

Approval is not guaranteed. Any code developed under this contract is the property of the government and any portion of the code must be submitted to the government upon request.

It should be understood that delivery of requirements includes meeting setup, attendance, phone calls or any other support activity. Further requirements relating to these support activities will be noted in individual task orders.

NITC requires the usage of work induction, tracking and monitoring tools such as HP Service Manager (HPSM), HP Quality Center (HPQC) and Service Ticketing System (STS) for assigned deliverables/tasking. Specific usage requirements will be noted in individual task orders.

NITC requires all custom software developed by the government or its contractors furnished or maintained to be committed to the NITC managed/maintained Source Control Management (SCM) System prior to deployment into any NITC functional environment (on premise or cloud based).

NITC reserves the right to require all require all custom software developed by the government or its contractors to be built/compiled/deployed from NITC SCM System, through NITC managed/maintained delivery and integration toolchains, and not received via offsite or localized deployment or build processes. Custom software developed by the government or its contractors may be required to pass functional and operational analysis tasks prior to allowing deployment possibly including, but not limited to: unit/integration testing, static code analysis, UI/GUI testing, dynamic system analysis, included library security and licensing validation.

NITC reserves the right to require all require all custom software developed by the government or its contractors and Commercial-Off-the Shelf (COTS) systems be deployed from NITC managed/maintained artifact repositories.

NITC reserves the right to require all require all custom software developed by the government or its contractors to be developed in NITC specified architectures, languages, and/or frameworks. Specific requirements will be noted in individual task orders.

3.2 Performance Requirements

The Contractor shall perform the following tasks in accomplishing the requirements of this contract.