Attachment_0002_-_ASC_C4IM_Section_L_&_M_Narratives.pdf

W52P1J-17-R-0064 Attachment 0002

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS (SECTION L)

AND

EVALUATION FACTORS FOR AWARD (SECTION M)

FOR

Army Sustainment Command

Command, Control, Communications, Computers, and Information Management Mission Services

L.0 INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 GENERAL INFORMATION

L.1.1 NAICS Code and Size Standard

The North American Industry Classification System (NAICS) code for this acquisition is 541513. The small business size standard is $27,500,000.00.

L.1.2 Notice of 8(a) Small Business Set-Aside

Proposals are solicited only from Section 8(a) small business concerns. This action is based on a determination by the Contracting Officer, alone or in conjunction with a representative of the Small Business Administration, that it is in the interest of maintaining or mobilizing the Nation's full productive capacity, or in the interest of war or national defense programs, or in the interest of assuring that a fair proportion of Government procurement is placed with small business concerns. Proposals received from others will be considered non-responsive. For an Offeror that submits a proposal as a FAR 9.601(1) Contractor Team Arrangement (CTA) to be considered Section 8(a) for purposes of award, the CTA must comply with SBA requirements (see 13 C.F.R. § 124.513).

L.1.3 Type of Contract and Number of Awards

It is anticipated that one award will be made from this solicitation and that award will be made on/about August 31, 2017; however, the Government reserves the right to make more than one award. The awarded contract will consist of Cost Plus Fixed Fee and Cost Reimbursable Contract Line Item Numbers (CLINs).

L.1.4 Commitment of Public Funds

The KO is the only individual who can legally commit the Government to the expenditure of public funds in connection with the proposed procurement. Any other commitment, either express or implied, is invalid.

L.1.5 Communications Prior to Contract Award

Offerors shall direct all communications to the attention of the KO cited on the Standard Form 33 found in Part I, Section A of this RFP. Communications with other officials may compromise the competitiveness of this acquisition and result in ineligibility for award.

L.1.6 Release of Information

Source selection and award information will be disclosed to Offerors in accordance with regulations applicable to negotiated acquisition. Prompt written notice will be given to unsuccessful Offerors as they are eliminated from the competition, and to all Offerors following award.

L.1.7 Preparation Costs

The Government will not reimburse Offerors for the costs of preparation and submission of a proposal.

L.1.8 Acquisition Source Selection Interactive Support Tool (ASSIST)

ASSIST is a workflow tool that will be used to manage and document the proposal evaluation.

L.2 INSTRUCTIONS TO OFFERORS

L.2.1 General Instructions

The following instructions will establish the acceptable minimum requirements for the format and contents of proposals. Offerors shall submit proposals in accordance with the format and the proposal requirements detailed in this section.

L.2.2 Electronic Submission of Proposal (No Paper)

A. Each Offeror shall submit its proposal and solicitation questions in the file formats specified in section L.2.9 below.

1. Proposals are due by 1300, Central Time, April 25, 2017. Interested Offerors shall send their proposals via e-mail to:

a. Jeff Voss, Contract Specialist: jeffrey.r.voss.civ@mail.mil

b. Tami Lord, Contracting Officer (KO): tami.l.lord.civ@mail.mil

2. Questions regarding the solicitation are due by 1300, Central Time, April 3, 2017.

mailto:jeffrey.r.voss.civ@mail.mil mailto:tami.l.lord.civ@mail.mil

3. NOTE: The Government WILL NOT accept any hard copies, facsimile, or

CDs/DVDs.

B. All word processing files provided shall be written in 2007 Microsoft Word Format or later with all external objects embedded (not linked).

C. Offerors shall ensure that all tracked changes have been “accepted” such that no revision marks are visible to the Government.

D. All spreadsheet files provided shall be in 2007 Microsoft Excel format or later with all external objects embedded (not linked).

E. The Offeror shall not prepare any portion of its proposal using sound, animation, or video files. Multimedia files will not be accepted, e.g., QuickTime or Windows Media Player. Offerors are responsible for ensuring the integrity of other types of files such as *.pdf files.

F. Files with the following extensions will not be accepted: *.exe, *.dll, *.bat, *.com.

G. Prior to submission, all electronic media must be scanned for viruses by the Offeror.

Any electronically submitted file that contains a virus will automatically be rejected by the Government. Offerors are ultimately responsible to ensure that their proposals are submitted by the due date and time.

L.2.3 Rejection of Multiple or Alternate Offers

Only one (1) offer will be accepted from a single Prime Contractor. Multiple or alternate offers from the same Prime Contractor constitute a material nonconformity and will result in all of its offers being rejected.

L.2.4 Evaluation of Proposals

The Government will evaluate proposals in accordance with the criteria set forth in SECTION M of this RFP.

L.2.5 Privacy Act – Treatment of Proposal Information

A. The Privacy Act of 1974 (P.L. 93-579) requires that a Federal agency advise each individual whom it asks to supply information, the authority which authorizes the solicitation, whether disclosure is voluntary or mandatory, the principal purpose or purposes for which the information is intended to be used, the uses outside the agency which may be made of the information, and the effects on the individual, if any, of not providing all or any part of the requested information.

B. Providing the information requested is entirely voluntary. The collection of this information is for the purpose of conducting an accurate, fair, and adequate review prior to a discussion as to whether to award a contract.

C. Failure to provide any or all of the requested information may result in a less than adequate review.

L.2.6 Point of Contact for the ASC C4IM Mission Services Solicitation

The ASC C4IM KO and Contract Specialist are the points of contact for this acquisition.

Official RFP documentation, including RFP amendments, and other related information will be available in Federal Business Opportunities (FedBizOpps) at http://www.fbo.gov.

L.2.7 System for Award Management (SAM)

The Offeror shall register in the SAM system prior to award of the contract. Offerors can access SAM at http://www.sam.gov.

L.2.8 News Releases

The Offeror shall not make any news release pertaining to this procurement without prior Government approval and then only in coordination with the KO.

L.2.9 Organization and Page Limitations

A. The proposal submission shall be clear, concise, and shall include sufficient detail to evaluate and substantiate the validity of stated claims. Offerors shall assume that the Government has no prior knowledge of the company's capability and experience.

The proposal must provide sufficient detail to clearly and concisely demonstrate that the Offeror has an understanding of all requirements specified in the solicitation.

B. The proposal shall be divided into five sections as follows:

NOTE: The page limitations provided below shall be treated as maximums. If Offerors exceed the page limitations cited, the excess pages will not be considered.

1. Section 1: General

File Naming Structure: [Offeror]_General.pdf

NOTE: Unless otherwise noted, this section will be reviewed for compliance but will not be rated in the evaluation.

a. Cover Letter (limit of 2 pages)

b. Solicitation, Offer and Award – SF 33 (no page limitation) http://www.fbo.gov/ http://www.sam.gov/

c. Optional List of Abbreviations and Acronyms (no page limitation)

d. If applicable, Contractor Team Arrangement, e.g., joint venture contract, and/or Small Business Administration (SBA) Mentor-Protégé Agreement (no page limitation)

e. Verification of 8(a) Qualification (Phase 1 Go/No-Go requirement) (no page limitation)

f. Organizational Conflict of Interest (no page limitation)

g. Verification of an adequate accounting system (including each partner or joint venture member, if applicable) (Phase 1 Go/No-Go requirement) (no page limitation)

h. Security Requirements (Phase 1 Go/No-Go requirement) (no page limitation)

i. Afghan Business License Requirements (no page limitation)

2. Section 2: Technical (limit of 50 pages)

File Naming Structure: [Offeror]_Technical.docx

3. Section 3: Overall Management Approach (limit of 30 pages)

File Naming Structure: [Offeror]_MgmtApproach.docx [Offeror]_Staffing&SkillsMatrix.xlsx

4. Section 4: Past Performance (reference L.3.4.E for limitations)

File Naming Structure: [Offeror]_PastPerf.docx

5. Section 5: Cost/Price (no page limitation)

File Naming Structure: [Offeror]_Cost-PriceToC.docx [Offeror]_C4IMPricingSheets.xlsx

NOTE: File types for any supporting documentation may be .xlsx or .docx.

There is no File Naming Structure for supporting documentation.

C. Formatting. Proposal files must follow the following format/page set up parameters:

1. Page Size:

a. Width: 8.5 inches

b. Height: 11.0 inches

2. Paragraph Spacing: Single spaced. Each paragraph shall be separated by at least one blank line.

3. Margins: Top, Bottom, Left and Right 1 inch margins for all pages

a. Headers and Footers may be placed in the margin but shall not contain proposal content.

b. Gutter – 0 inches

c. From Edge – Header, Footer – 0.5 inches

4. Font Size and Style – Minimum:

a. 10 point Arial font for Text

b. 9 point font in the Arial family for Tables

c. 8 point font in the Arial family for Graphics

5. Tables and graphics may be landscape; all other text must be portrait.

6. If the Offeror uses a different format (font size, margin, etc.), the Government reserves the right to adjust the proposal to fit the parameters of the format as stated in the RFP, and if this results in the proposal exceeding the page limitations in any one area, the Government will not consider those excess pages.

D. The Government will upload the electronic version of the Offeror’s proposal into

ASSIST. Members of the Evaluation Team will use the version in ASSIST to conduct their evaluation.

L.2.10 Exchanges

A. During the evaluation process, the Government may, at its discretion, conduct exchanges as needed. The Government need not enter into exchanges with all Offerors. All exchanges with Contractors may be accomplished through the release of Evaluation Notices (ENs). ENs may be issued via ASSIST. The Government reserves the right to conduct exchanges with Contractors outside ASSIST if it is determined to be in the best interest of the Government.

B. ASSIST2Industry may be used in conjunction with ASSIST to accomplish exchanges with Offerors after receipt of proposals. ASSIST2Industry provides the ability for the Government to issue, and the Offerors to receive and respond to, ENs in a secure online environment.

1. In order to initiate the use of ASSIST2Industry, the Government requires the names, company titles, telephone numbers, and email addresses of two (2) individuals that the Offeror has designated as responsible for receiving and responding to Government ENs through ASSIST2Industry. The designation of two (2) individuals is for the purpose of ensuring availability of one individual if the other individual is not available. The required information regarding these two (2) individuals must be submitted with the Offeror’s Proposal and included in the cover letter.

2. After the RFP’s closing date, the Government will establish an account in ASSIST2Industry for each individual identified by the Offeror that has submitted a proposal in response to this RFP. The two individuals named by the Offeror will be authorized access to that account. Two (2) separate system generated emails will be sent to each individual. One of the emails will contain the individual’s ASSIST2Industry username. The other email will contain the individual’s temporary password. Using the provided username and temporary password, each individual can then go to https://ASSIST2Industry.army.mil to access the account. NOTE: The first time a user logs in, the user will be required to change the temporary password before the user can proceed to use the site.

3. Whenever the Government issues ENs to the Offeror through ASSIST2Industry, the Government’s KO will notify the Offeror through a medium independent of ASSIST2Industry (e.g., e-mail) that the Offeror has ENs in ASSIST2Industry waiting for a response. There will be no ENs in ASSIST2Industry until such notice is issued by the KO. Offerors can contact the ASSIST2Industry helpdesk at (609) 562-7050 or (609) 562-7031 for any technical assistance that may be needed.

4. OFFERORS ARE CAUTIONED THAT THE SYSTEM GENERATED EMAILS

REFERRED TO ABOVE ARE INTENDED FOR ADMINISTRATIVE PURPOSES

ONLY. RECEIPT OF THESE EMAILS DOES NOT CONSTITUTE THE

COMMENCEMENT OF ANY TYPE OF EXCHANGE WITH THE OFFEROR.

ALL NOTIFICATIONS THAT ANY TYPE OF EXCHANGE WITH THE OFFEROR

HAS COMMENCED AND THE OFFEROR HAS ENs AVAILABLE TO RESPOND

TO, WILL BE SENT TO THE OFFEROR BY THE KO INDEPENDENTLY OF

THE ASSIST2INDUSTRY.

C. EN Responses. Responses to ENs and any resulting proposal revisions must be provided in accordance with the following instructions:

1. A complete response must be provided within the EN response, including an explanation of any revisions to the Offeror’s proposal. Please do not simply provide a reference to revisions in the Offeror’s proposal. If a response to an

EN requires a revision to the Offeror’s proposal, identify a reference in your response(s) to the location (e.g., Filename, Section #, paragraph #, etc.) of the revision in the Offeror’s proposal. In order to be considered as part of the Offeror’s proposal evaluation, the changes should be made in the Offeror’s proposal submission and the proposal must conform to the page format/limitation requirements. If a response to an EN simply requires a clarification, Offerors shall not submit a revised proposal.

2. Attach the complete resubmission file containing the proposal revisions for each file as ‘Attached Files’ with the Offeror’s reply in the last EN for the respective file (i.e. one attached file per EN, same file structure as initially submitted). Do not submit change pages or multiple copies of Offeror’s revised proposal. For clarity purposes, Offerors are required to clearly identify the corresponding changes/additions in the Offeror’s proposal (e.g. use track changes to show date, vertical line in margin, bold, and/or underline by using the redline and strikeout features).

3. Each revision on each revised page shall be identified by date (DD/MM/YY) and by revision number, which shall be done by adding a footer to indicate such revision (i.e., date of submission of the revision) for each file affected. Offerors shall also place their names within the header or footer of each page along with the section number.

4. After all ENs have been issued and responses submitted, and, when instructed by the KO, Offerors shall submit Final Proposal Revisions as specified in the Final Proposal Revision request letter.

L.3 CONTENTS

L.3.1 Section 1: General

A. Cover Letter: The Offeror shall submit a cover letter with its proposal. The cover letter shall include the following:

1. Proposed Team Member Names

2. At least two (2) Authorized Vendor Representatives/Points of Contact

B. Solicitation, Offer and Award (SF 33): As part of its proposal, the Offeror is required to submit the signed SF 33 scanned in *.pdf format. As noted in Block #9, all offers are subject to the terms and conditions contained in this solicitation. The SF 33 must be executed by a representative of the Offeror authorized to commit the Offeror to contractual obligations. The Offeror on the SF 33 must match the information for the Offeror in SAM. Acknowledgment of receipt of any amendments shall be made in Block 14 of the SF 33. The Government requires a minimum acceptance period of 180 days.

C. Optional List of Abbreviations and Acronyms: The Offeror may insert a file with any abbreviations and acronyms that will be used in the Offeror’s proposal.

D. Contractor Team Arrangements (CTAs), if applicable:

1. Potential Offerors may form CTAs as defined under FAR 9.601, but they are not required to do so. If the potential Offeror that forms a CTA wants all members of the CTA to be considered for evaluation, the CTA must be a CTA as defined under FAR 9.601(1) or be a Mentor-Protégé Arrangement that has been approved by the Small Business Administration and include with its proposal the information required under subpart 2 of this section, “Instructions regarding FAR 9.601(1) CTAs.” An Offeror may also enter into Prime/Subcontractor arrangements as defined under FAR 9.601(2). Offerors forming CTAs as defined under FAR 9.601(2) are not required to submit any additional documentation in this section regarding the proposed Prime/Subcontractor contractual relationship or qualifications of the proposed Subcontractors.

2. Instructions Regarding FAR 9.601(1) CTAs

a. The Government will evaluate a FAR 9.601(1) CTA provided that the Offeror submits a full and complete copy of the document establishing the CTA relationship and containing at least the minimum information required by the solicitation closing date. Although there is no specific form or format that the CTA documents must adhere to, an Offeror proposing as a CTA for purposes of evaluation is required to address the following in the CTA document:

i. Purpose of the CTA

The CTA documents should clearly set forth the purpose of the CTA.

ii. Identify the Parties

(1) The CTA documents should identify the entities which make up the

CTA relationship, including the primary point of contact for each of the members of the team and the managing partner, and a statement addressing the obligation of all parties to the CTA to ensure performance of the contract despite the withdrawal of any member.

The CTA documents should also identify where accounting and other administrative records will be retained during contract performance and upon completion of the contract.

(2) If proposing as a FAR 9.601(1) CTA, the proposal shall provide, at a minimum, the legal name of the CTA member, the CTA member’s corporate address, a web address, and DUNS number for the proposed CTA member.

iii. Designation of a “Team Lead”

The CTA documents shall identify the “team lead,” and clearly explain the specific duties/responsibilities of the “team lead” to the other members of the team and to the Government (Note: The Government requests that the team lead be the primary point of contact with the Government while the proposal is under consideration by the Government. This means that the Government will require permission from each non-“lead” member of the team for the Government to discuss confidential/privileged information about the non-“lead” members of the CTA with the designated team lead).

iv. Specific Duties/Responsibilities

The CTA documents shall clearly describe the specific duties/responsibilities of each member of the team as they relate to each other, and explain the specific duties/responsibilities that each team member will have for purposes of contract performance (e.g., one team member will be primarily responsible for performing specific task areas listed in the PWS, while other team members will be primarily responsible for performing other specific task/sub-task areas listed in the PWS; etc.), and any guaranteed percentages of potential work allocated to the team members.

v. Pricing and Cost

The CTA document should explain how the team members have divided responsibilities for purposes of proposing price/costs. For example, if one member of the team is responsible for proposed price/costs for a particular labor category, while another entity in the CTA is proposing price/costs for a different labor category, the CTA documents should identify which of the respective team members is responsible for proposing which specific price/cost information.

vi. Invoicing and Payment

The CTA document shall explain how the team members have addressed issues relating to invoicing and distribution of payments. For example, the CTA document shall identify which member of the team is responsible for invoicing the Government and distributing payment. Under such circumstances, the CTA document shall clearly indicate that all team members agree to this method of payment. The CTA document should also acknowledge that any dispute involving the distribution of payment will be resolved by the team members themselves, without any involvement by the Government.

vii. Replacement of Team Members

The CTA document should address the circumstances and procedures for replacement of team members, including the team lead.

viii. Duration of the CTA

The CTA document should address the duration of the CTA, including when it becomes effective, when it expires, and the basis for termination.

ix. Representations and Certifications

All members of the CTA shall submit separate representations and certifications as required under Section K.

x. Requirements for Section 8(a) CTAs

For an Offeror that submits a proposal as a CTA to be considered Section 8(a) for purposes of award, the CTA must comply with SBA requirements (see 13 C.F.R. § 124.513).

xi. Additional Requirements for Joint Ventures

Joint venture offers must be made in the name of the joint-venture entity.

The joint venture contract must identify the managing venturer, the joint venture members and who will have signature authority on behalf of the joint venture. The party signing the offer for the joint-venture shall be listed as having such authority.

3. SBA Mentor-Protégé Arrangements

Each Offeror relying upon its status in a SBA approved Mentor-Protégé relationship shall provide the SBA approved Mentor-Protégé agreement/arrangement document. Failure to provide the SBA approved Mentor-Protégé agreement/arrangement document with the offer shall result in the offer being summarily rejected.

E. Verification of 8(a) Qualification (Phase 1 Go/No-Go Requirement)

1. Offerors shall furnish evidence of qualification under the 8(a) program. In addition, to facilitate communications, the Offeror shall provide the following information regarding the Offeror’s cognizant servicing Small Business Administration (SBA) Field Office:

a. Servicing SBA Field Office

b. Address

c. Cognizant SBA Business Opportunity Specialist's Name

d. Phone and Email Address

F. Organizational Conflict of Interest

1. The term “Organizational Conflict of Interest” (OCI) is defined in FAR 2.1; also see FAR 9.502(c). For this RFP, an OCI exists when a contractor would face an actual or potential conflict of interest if it worked on the planned contract, due either to its other business interests or to the nature of the effort to be performed.

2. Contractors are encouraged to make a preliminary disclosure to the KO, prior to the due date for receipt of proposals, of any OCI issues the contractor has identified. Such preliminary disclosure will allow the KO more time to assess both the potential OCI and the contractor’s proposed strategy to negate or mitigate the OCI. This assessment may be crucial since, per FAR 9.504(e), the KO may not award a contract to a contractor with an OCI that cannot be negated or mitigated.

3. If the contractor demonstrates to the KO that there may be a possible conflict of interest arising out of an existing contract, the KO shall take the necessary action to mitigate any conflict of interest that may be present. The contractor agrees that the Government or an authorized representative may, up to three years after acceptance of all programmatic documentation to be delivered under this contract, restrict the contractor’s future participation in any resulting program managed system acquisition action(s).

4. The Government will review the apparent awardee’s OCI Mitigation Plan as part of the responsibility determination. An apparent awardee found not to be responsible will not receive an award.

5. OCI Mitigation Plan

a. The contractor shall submit with its proposal an OCI Mitigation Plan detailing the contractor’s business practices, procedures, policies and internal controls as they pertain to Business Integrity and Organizational Conflict of Interest.

b. The contractor’s OCI Mitigation Plan must explain how the contractor will protect non-public information from unauthorized disclosure. The contractor shall identify any current or potential OCIs for itself as well as any subcontractors, team members, subsidiaries or affiliates, and provide its plan to avoid or mitigate any potential or current OCI issues that may arise as a result of serving as the C4IM Mission Services contractor. The contractor shall also submit, with its proposal, a blank copy of its proposed nondisclosure agreement in accordance with L.3.1.F.6 below. To be deemed “Acceptable”, contractor proposals must meet the minimum requirements set forth below. At a minimum, the OCI Mitigation Plan shall address the following:

i. Provide an organizational chart which shows the contractor's corporate structure and highlights the elements of the company which will be performing the contract.

ii. Demonstrate on the organizational chart whether the elements of the company performing the contract will be isolated from the remainder of the company.

iii. Describe how non-public information, whether in hard copy or electronic format, will be stored and destroyed in order to preclude unauthorized transfer of information.

iv. Describe how computer networks and servers will be protected to prevent unauthorized transfer of protected information.

v. Explain the contractor's management reporting chains and address whether the contract effort and decisions related to that effort will be isolated from the remainder of the company.

vi. Address whether the organizational element performing the contract will be geographically or physically separated from the remainder of the company.

vii. Address what techniques the contractor will use to avoid or mitigate any perception that it might favor its own products or services in performance of the contract-.

viii. Address whether management outside the contractor's organizational element performing the contract will have access to key decisions for which the performing element is responsible.

ix. Address the use of Non-Disclosure Agreements for contractor personnel, including subcontractors and team members.

x. Address any personnel reassignment restrictions for any personnel who retire or leave the contract for any reason.

xi. Describe subcontractor OCI mitigation plans and procedures for the contract.

xii. Describe how the contractor will conduct periodic self-audits of its OCI

Mitigation Plan and provide results to the Government.

xiii. Describe how the contractor will provide initial and refresher OCI training for all personnel working on the contract. Ensure that the initial OCI training is provided prior to contractor personnel access to protected information.

6. Non-Disclosure Agreement

a. The contractor shall submit with its proposal a blank copy of its proposed

Non-Disclosure Agreement in accordance with the information outlined below.

The agreement shall address, at a minimum, the following:

i. Identify the parties and their relationships;

ii. Identify the program involved and the relevant Government contracts of the parties;

iii. Describe contractor interfaces by general subject matter;

iv. Specify categories of information to be exchanged or support to be provided;

v. Give expiration date (or event) of the agreement;

vi. State that if there is a conflict between the relevant Government contract and the agreement, the contract governs; and

vii. Have an agreement to protect proprietary data, including restrictions on employees.

G. Verification of an Adequate Accounting System (Phase 1 Go/No-Go Requirement)

1. Offerors must have verification from the Defense Contract Audit Agency (DCAA), the Defense Contract Management Agency (DCMA), any federal civilian audit agency, or a third-party Certified Public Accounting (CPA) firm of an accounting system that has been audited and determined adequate for determining costs applicable to this contract in accordance with FAR 16.301-3(a)(1). In the event the verification is from a third-party CPA, the verification letter shall be on the letter head of the third-party CPA firm, and certified by a certified public accountant. For those Offerors that submit a proposal in the form of a partnership or joint venture, each partner or joint venture member must show evidence that it has verification of an adequate accounting system.

2. As such, the Offeror must provide in its proposal, a contact name and contact information (i.e., phone number, address, email address) of its representative at its cognizant DCAA, DCMA, federal civilian audit agency, or third-party accounting firm and submit, if available, a copy of the Pre-Award Survey of Prospective Contracting Accounting System (SF 1408), provisional billing rates, and/or forward pricing rate agreements.

H. Security Requirements (Phase 1 Go/No-Go Requirement)

Offerors must provide proof of a current U.S. Facility Clearance at the SECRET level in accordance with Department of Defense Directive (DoDD) 5220.22, National Industrial Security Program Operating Manual. This SECRET level clearance requirement applies to the Prime Offeror and each identified partner, joint venture member and subcontractor that will perform this contract. At the time of proposal submission, Offerors shall provide the following information for the Prime Offeror and each partner, joint venture member and subcontractor: name of company, company CAGE code, company facility clearance level, and company Facility Security Officer (FSO) contact information (name, phone number, and e-mail address).

I. Afghan Business License Requirements

At the time of contract award, any Prime Offeror, identified partner, joint venture member or subcontractor that will be providing personnel to perform work in Afghanistan must possess a valid Afghan business license. The Offeror shall provide positive proof that the entity providing personnel to perform work in Afghanistan possesses, or will possess on the projected contract award date, a valid Afghan business license in accordance with the Security and Defense Cooperation Agreement between the government of Afghanistan and the United States.

Reference Section J, Attachment 0006 – Contracting in Afghanistan: BSA/SOFA Guidelines, for further information regarding the obtainment of subject license. The Government will review the apparent awardee’s proof of license as part of the responsibility determination. An apparent awardee found not to be responsible will not receive an award.

L.3.2 Section 2: Factor 1 (Technical)

A. Subfactor 1A: Defense in Depth

1. The Offeror’s proposal shall detail its approach for implementing and managing the Defense in Depth at ASLAC (PWS 4.1.1) for the total network and/or enclaves within the network, including: scanning, remediating, host and network intrusion detection/prevention, firewalls, proxy servers, web cache, virus programs, vulnerability scanning, content filtering, remote dial-in protection, Host Based Security Services, Directory Services, Risk Management Framework (RMF), DoD Instruction 5200.40, and accreditation guidance and advice in accordance with AR 25-2 and IA Best Business Practices (BBPs).

2. The Offeror’s proposal shall demonstrate its understanding of the requirements of Information Assurance Vulnerability Management (IAVM) compliance and compliance monitoring of all network connected assets in conjunction with Security Technical Implementation Guides (STIGs) and patching guidelines and deadlines established by Army and DoD enterprise authorities.

3. The Offeror’s proposal shall detail its approach to the remediation process for findings from scanning and working with IA technical personnel from outside the ASC in order to maintain a proper network security posture.

B. Subfactor 1B: Server Administration

1. The Offeror’s proposal shall provide its technical approach to system administration and operating system support for file, print, and common user application servers, server farms/banks, including hardware and software monitoring utilizing system logs, security logs, and application logs and virtual environment.

2. The Offeror’s proposal shall demonstrate its understanding of Microsoft Active Directory organizational unit (OU) administration, domain administration and service support for primary and backup domain controllers (PDC & BDC) and management of dynamic allocation of internet protocol (IP) address space.

C. Subfactor 1C: Network Administration

1. The Offeror’s proposal shall demonstrate its knowledge of management of various types of networks, including: Local Area Network, Campus Area Network, Wide Area Network connectivity to include supporting the automated systems linked to the network, and management of local VPN concentrator for remote access.

2. The Offeror’s proposal shall demonstrate its understanding of the interoperability of the networks (connectivity and operation of ICAN between LAN and computer resources); and its knowledge of enterprise management software that monitors network performance, analyzes network activity and maintains network availability.

3. The Offeror’s proposal shall demonstrate its knowledge of Wireless Network Infrastructure products, including Cisco controllers and software management products.

4. The Offeror’s proposal shall demonstrate its knowledge of configuring, implementing and maintaining VPNs for dynamic site-to-site VPN structure.

D. Subfactor 1C: Quality Control Plan (QCP)

1. The Offeror’s QCP must describe its approach as follows:

a. To achieve and sustain performance standards and metrics that align with the organization’s PWS requirements.

b. Provide a proven quality assurance methodology in accordance with the Performance Requirements Summary contained in the PWS.

c. Explain the manner in which the Contractor plans to ensure that all contract requirements are being accomplished in accordance with the PWS/contract.

d. Address the proactive monitoring, inspection, and correction of deficiencies relating to the execution of the requirements in the PWS.

e. Describe the proposed methodologies for ensuring sustained quality improvement, measuring, attaining, managing, and reporting the quality of performance over the life of the contract.

L.3.3 Section 3: Factor 2 (Overall Management Approach)

A. Subfactor 2A: Organizational Structure and Key Personnel

1. The Offeror’s proposal shall include a Basis of Estimate (BOE) containing the staffing levels and skill mix required to execute the PWS. Offerors shall provide a Staffing Levels and Skills Matrix in proposing an approach to staffing the work outlined in the PWS. In the Staffing Levels and Skills Matrix, Offerors shall present the direct productive labor hours, full-time equivalents (FTEs) for the Prime Offeror, partners, joint venture members and subcontractors, per labor category, by location identified in section 4.0 of the PWS. A description of each position, detailing the job responsibilities and minimum experience and education requirements, should also be included. Identify key positions that will ensure success to the program (including those that will be filled by subcontractors, including rationale for using these key positions and how personnel will interact with Government officials. The period for the Staffing Levels and Skills Mix Matrix shall correlate to the CLINs and PoPs. The Matrix shall span multiple periods and capture labor hours for each period if differing from the prior period’s hours. The Staffing Levels and Skills Matrix does not count toward any page limitation and shall be submitted as a separate file.

2. The Offeror’s proposal shall address how the functions in its organizational chart cross reference to the PWS structure to ensure success in performing the PWS.

The Offeror’s proposal shall explain how the minimum qualifications for and the number of non-key positions were established. The proposal must describe decision-making authority responsibility for staffing and reporting up the chain.

The proposal shall include for each key position, a full description with associated responsibilities and accountabilities, required certifications, skill levels, etc. Key

Personnel shall have demonstrated experience and qualifications to successfully lead and manage an information technology organization commensurate with their proposed roles.

B. Subfactor 2B: Recruitment and Retention Plan

1. The Offeror’s proposal shall describe the corporate processes applicable to all employees (practices, policies, procedures, and tools) that will be employed by the Prime Offeror and any major subcontractors/CTA members to recruit and retain a sufficient number of qualified personnel with the requisite knowledge, skills, education, and experience to ensure successful accomplishment of the proposed technical and management approaches throughout the life of the contract. The Offeror’s approach should be in compliance with Executive Order 13495, Hiring of Qualified Incumbent Workforce. At a minimum, the plan shall address recruitment and hiring practices, retention measures, termination policies and procedures, employee development tools, and compensation policies to include, but not limited to: overtime (compensated and uncompensated), temporary duty, travel, per diem, leave, compensatory time, sick leave, health benefits, bonuses, severance pay, incentive pay, educational assistance and any other policies that would serve to obtain and maintain the personnel resources necessary to successfully perform this effort. Provide corporate retention rates for the past three years for the prime Offeror and each major subcontractor/team member.

2. The Offeror’s proposal shall also address its strategy for ensuring that personnel maintain DoD 8570.1 and computing environment certifications as the DoD network evolves.

C. Subfactor 2C: Processes and Procedures

1. The Offeror’s proposal shall detail its processes and procedures for the following:

a. Army Training and Certification System/Defense Manpower Data Center validation of DoD 8570.01-M required training and relevant computer environment training

b. Applying for relevant work visas for workers stationed outside of the United States

c. Applying for business licenses outside of the United States, where they are required

d. Ensuring periodic reinvestigations are conducted in a timely manner for all employees requiring security clearances

e. Ensuring adequate personnel are available to meet surge/contingency requirements contained in paragraph 5.0 of the PWS.

D. Subfactor 2D: Transition Approach

1. The Offeror shall describe its approach/strategy for Transition-In. This shall contain a reasonable, realistic approach for assuming full contractual responsibility without disruption or degradation of performance during the transition period. Also identify risks, propose appropriate risk mitigation strategies, and provide realistic and achievable staffing levels and an affordable transition schedule which will demonstrate the Offeror’s ability to enable a smooth Transition-In.

2. Additionally, the Offeror shall describe its approach/strategy for the Transition-Out. This shall contain a reasonable, realistic approach for a smooth transition of all contractual responsibility without disruption or degradation of performance during the transition period. Also identify risks, propose appropriate risk mitigation strategies, and provide realistic and achievable staffing levels and an affordable transition schedule which will demonstrate the Offeror’s ability to enable a smooth transition to any potential new contractor.

3. The Offeror shall also address how it will complete knowledge transfer and an adequate “shadowing” period between the incoming and outgoing contractors to ensure no disruptions or degradations in service; and to deter, properly identify, and address operational vulnerabilities or potential risk.

4. This submission may become part of the Transition Plan submitted under the PWS, which is required to be updated during the performance period.

L.3.4 Section 4: Factor 3 (Past Performance)

A. Each Offeror shall submit a Past Performance Section 4 with its proposal containing past performance information in accordance with the format prescribed below. Past Performance introductory overview shall state any assumptions associated with the proposed Past Performance Factor.

B. Format: The Past Performance volume shall be organized according to the following format:

1. Cover Page: RFP W52P1J-17-R-0064; Project Name: Command, Control, Communications, Computers, and Information Management Mission Services;

Offeror’s Company Name; CAGE Code and Data Universal Numbering System (DUNS) number.

2. Table – The Offeror shall provide a table listing each subcontractor’s Company Name to include its applicable CAGE Code and DUNS it intends to use in the performance of the C4IM RFP based on L.3.4.B.2.a, Proposed Subcontractor

Criteria, below.

a. Proposed Subcontractor Criteria – subcontractors or teaming partners the Offeror considers critical or a major contributor to the overall successful performance of the C4IM RFP.

b. Joint Ventures (JVs) – each member of a JV must submit its own past performance information.

3. Letters of Consent: The Offeror shall include a written Letter of Consent from each of its proposed JVs, partnerships, and major subcontractors that allows the Government to discuss the JV's, partnership’s, or major subcontractor's past performance evaluation findings during negotiations with the Offeror.

C. Contract References: The Offeror may submit with its initial proposal, no more than three (3) recent and relevant contracts and/or project references for itself. In addition to the Offeror’s references, no more than two (2) recent and relevant contracts and/or project references may be submitted for each proposed subcontractor, teaming partner, or JV partner. Offerors are required to explain what aspects of the past performance are relevant to the C4IM RFP in 500 words or less for each submitted reference.

D. Recent contract performance is defined as prime contracts, task orders, delivery orders, or first-tier subcontracts where the services or deliverables were performed, or are still being performed, anytime within three (3) years of the issuance of this C4IM RFP. The Government also reserves the right to consider any past performance after the RFP closing date and prior to award.

E. Relevant performance means work efforts that are currently being, or have been, performed that are the same or similar in scope, magnitude (dollar value), and complexity of the C4IM RFP. This includes, but is not limited to, providing service for communications and systems support, Information Assurance, Tier III help desk support, and automation support in accordance with the Army's Command, Control, and Communications, Computer, and Information Management (C4IM) standards in support of the Army. The Government will evaluate recent and relevant references that support the DoD, Federal, State, Local, or commercial contracts, task orders, delivery orders, or subcontracts.

F. Adverse Contract Performance: The Offeror shall identify every relevant contract it was awarded that experienced any performance problems related to deliverables or services; and every recent government contract that was terminated for cause or default within the past three (3) years of issuance of the C4IM RFP. The number of contracts submitted in response to Section L.3.4.F is unlimited. For any contract falling under this description, provide the following information:

1. Government Contract Number, place of performance, CAGE code, and DUNS number. If the work was performed as a first-tier subcontractor, also provide the prime contract number, the name of the prime Offeror and point of contact (POC) within the prime Offeror organization (name, email address, and telephone number);

2. Government contracting activity KO’s name, e-mail address, and telephone number;

3. Government Technical Representative/Contracting Officer Representative (COR), and current email address, and telephone number;

4. Contract number and, in the case of indefinite delivery indefinite quantity (IDIQ) type of contracts, General Services Administration (GSA) contracts, and Blanket Purchase Agreements (BPA), include Task/Delivery Order Numbers as well;

5. Period of performance of the contract and/or task/delivery order;

6. Cure notices or show cause letters received;

7. If contract was terminated, identify reason for any termination;

8. State any corrective actions taken;

9. And, describe the extent to which the corrective action has been successful, identifying POCs who can confirm the success of the corrective measures.

G. If there are no contracts meeting the descriptions in L.3.4.F above, the Offeror must so state that in Section 4 of its proposal. Failure to include this information may be cause for rejection of an Offeror’s proposal as incomplete.

H. The Offeror shall submit a Past Performance Questionnaire (PPQ) (Attachment

0004) for each of the recent and relevant past performance references included in the proposal.

1. The Offeror shall encourage the PPQ Respondent to return the completed questionnaire directly to the Government email addresses cited on the questionnaire on or before the due date for receipt of proposals. All questionnaires completed by the POC shall be sent from the POC’s email address directly to the Government email addresses; not to the Offeror for forwarding to the Government.

I. The Government reserves the right to use data provided in the Offeror's proposal and data obtained from other sources, including, but not limited to, the Past Performance Information Retrieval System (PPIRS). To ensure inclusion of all references in the evaluation process, the Offeror is encouraged to provide the Government with the most current data on each reference.

J. References provided on classified contracts or contracts to foreign entities cannot be verified; therefore, classified and foreign contracts will not be evaluated.

L.3.5 Section 5: Factor 4 (Cost/Price)

A. Offerors, and their major subcontractors, are required to provide cost/price information in accordance with FAR 15.408, Table 15-2 (Instructions for Submitting Cost/Price Proposals When Cost or Pricing Data Are Required). Offerors are responsible for ensuring that major subcontractor proposals conform to the same criteria, including support data and explanations. If work is to be performed by two or more divisions (or subsidiaries) within the Prime Offeror’s organization, separate Cost/Price proposal(s) shall be submitted for each division or subsidiary for its portion of the Cost/Price proposal(s) that meet or exceed $700,000 in an individual contract year.

B. The Price Volume shall be fully supported in accordance with the instructions below:

1. For all Contract Line Item Numbers (CLINs) and sub-CLINs (including Optional CLINs/sub-CLINs), Offerors shall enter their fully burdened hourly labor rates for all performance periods on the Pricing Sheets (Attachment 0003). All proposed fully burdened hourly labor rates shall be expressed as a dollar value and rounded to two decimal places when proposed on the Pricing Sheets and used in the computation of the Total Evaluated Price for each labor category. Offerors may add additional lines to the Pricing Sheets under each CLIN/sub-CLIN, as needed, in order to propose the labor skill mix to support the CLIN/sub-CLIN task requirements. Offerors should verify that the labor skill mix proposed is inclusive of all labor skill sets required to support the CLINs/sub-CLINs. Fully burdened hourly labor rates will then be applied by the proposed total productive hours, which will result in a total price for that labor category. Failure to include a fully burdened hourly rate for all of the proposed labor categories within the Pricing Sheets will result in the proposal being determined unacceptable, resulting in the Offeror’s proposal being rejected.

2. Offerors shall provide details of the proposed prices (including fully detailed labor rates) for all performance periods, CLINs, and shall provide supporting documentation for all costs (other than Government-developed surrogates and Not Separately Priced (NSP) CLINs). The Offeror’s proposed rates shall include a breakout of their fully burdened hourly labor rates (including subcontract labor) to include the base hourly rate, indirect rates (e.g. Fringe, Overhead, G&A), and Fee. All proposed labor rates shall be expressed as a value and rounded to two decimal places. The fully burdened hourly labor rates should match the rates proposed in Attachment 0003. All proposals shall be stated in U.S. dollars.

Where formulas exist in the Cost/Price proposal, they shall show working formulas. The Offeror's Pricing Sheets shall summarize totals for all performance periods.

3. All Cost/Price supporting documentation shall be in Microsoft Excel and Word.

All spreadsheets shall include working formulas and files should be unlocked and editable. Macros shall not be used. The Offeror shall provide Basis of Estimates (BOEs) and underlying assumptions utilized in preparation of the Cost/Price proposal. Each element of cost shall be documented completely to show the basis and rationale used in arriving at the amount proposed.

4. Failure to propose prices for all CLINs, with the exception of the not separately priced (NSP) and surrogate CLINs, may result in the Offeror being ineligible for award.

5. Offerors may provide any written explanations or documentation (in addition to the required explanations and documentation above), as deemed necessary, in order to enable the Government to…