Attachment_0002_Instructions_Conditions_and_Notices_to_Offerors_05_Jan_2017.pdf

Attachment 0002 05 Jan 2017

INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

1 GENERAL INSTRUCTIONS:

These instructions are a guide for preparing a proposal. These instructions describe the type and extent of information required, and emphasize the significant areas to be addressed in the proposal. Offerors shall examine this solicitation in its entirety and ensure that its proposal is complete and contains all necessary information and documentation required as instructed by this solicitation.

1.1. Introduction: This Section contains general proposal submission instructions as well as specific proposal requirements for the Unified Capabilities Soft Client Subscription

Services solicitation.

a. The United States Government (USG) plans to award a single contract to the

Offeror who is determined to be the best value to the USG based on the evaluation criteria outlined in this solicitation. The USG will be utilizing a two-phased approach to determine which Offeror’s proposal represents the best value to the USG. Phase one will utilize a rating criteria of acceptable/unacceptable. Those Offerors receiving an acceptable rating in

Phase One will continue to have its proposal evaluated in Phase Two. An Offeror receiving an unacceptable rating in Phase one will not have its proposal evaluated in Phase two and will be ineligible for award.

b. Each Offeror will provide the information as required by this solicitation (including attachments and exhibits) in the proper format. The proposal must contain all information as required for each Phase, volume, and shall be put into the format described herein. Each Phase shall be addressed in the prescribed format and sequence as identified in this solicitation. Proposals that do not contain the information requested in the solicitation risk being determined unacceptable.

c. The USG intends to award without discussions (See FAR 52.212-1). Therefore, proposals shall contain each Offeror’s best terms and conditions. The USG will not assume the Offeror possesses any capability, understanding, or commitment not specified in the Offeror’s proposal. In the event discussions must be conducted, the USG will conduct discussions in accordance with FAR 15 as provided in Attachment 0003. The USG intends to utilize the Acquisition Source

Selection Interactive Support Tool (ASSIST). However, the USG reserves the right to obtain clarifications; have communications; and/or hold discussions with

Offerors outside the ASSIST tool, if determined to be in the USG’s best interest to do so. Information and general instructions on the use of the ASSIST tool are provided as Attachment 0008 to this solicitation. Any Offeror that will have its proposal evaluated in Phase Two, will have accounts established in ASSIST in accordance with the information in Attachment 0008.

d. During the evaluation process, the USG may, at its discretion, enter into clarifications or communications as needed. The USG need not enter into communications or clarifications with all Offerors. In evaluating proposals, the

Government may establish a competitive range to reduce Offerors participating in the competition to the most highly rated proposals. Any Offeror eliminated from further consideration will be notified in writing. If the USG enters into discussions, it will be with those Offerors considered to be within the Competitive Range.

e. The proposal must not merely repeat the solicitation requirements, but rather provide documentary evidence explaining how requirements will be met.

Narratives must establish demonstrable evidence in support of any statements relating to promised capabilities or performance. Proposals should be written in a concise, straightforward, and forthright manner. Superficial marketing statements and materials should not be included.

Offerors are cautioned to examine this solicitation in its entirety and to ensure that its proposal contains all necessary information, provides all required documentation, and is complete and sufficiently detailed in all respects. Offerors are cautioned that merely re-stating the requirements with a statement of intent to perform DOES NOT reflect an understanding of the requirements or capability to perform. The USG will consider an Offeror’s noncompliance with the proposal instructions, to include incomplete proposals, to be indicative of the type of conduct that it may expect from the Offeror during contract performance and may result in the Offeror’s proposal being ineligible for award and therefore its proposal rejected.

f. Offerors are directed to thoroughly read the solicitation and fill in information on appropriate clauses as stated in the solicitation. For any fill-ins that are not applicable the Offeror must acknowledge by indicating “N/A”.

g. A separate proposal shall be submitted for each Factor/Volume provided below.

Each Factor/Volume will be evaluated independently of each other. All information pertaining to a particular volume shall be confined to that volume. All information pertaining to a particular gate or sub-factor shall be confined to that gate or sub-factor. Offerors should confine its submissions to essential matters sufficient to address the requirements of the proposal and to provide an adequate basis for evaluation. Each proposal volume is evaluated separately.

h. Failure to completely fill out the price model may result in the Offeror’s proposal being determined unacceptable and un-awardable. All prices will be binding. The USG reserves the right to require the submission of any data (i.e.

other than cost or pricing data) necessary to validate the reasonableness of an offer.

i. All prices and conditions proposed shall remain in effect from date of solicitation closing for a period of 200 days. If discussions are opened, the prices and conditions proposed shall remain in effect for a period of 180 days from date of discussion closing and submission of final proposal revision. Offerors must confirm the validity period of its proposal in its submission.

j. Alternate proposals will not be accepted. Proposals shall not contain classified data. The use of hyperlinks in proposals is prohibited.

k. The solicitation, amendments, notices, and other information will be made available on FEDBIZOPPS at http://fbo.gov. Therefore, Offerors are advised to continuously monitor FBO for new information. The Offerors are deemed to have knowledge of all documents which are posted to FBO for this requirement.

2 Proposal Instructions:

2.1 Structure:

a. The proposal shall be submitted in the English language. Offerors shall ensure its proposal, when printed, prints on 8 ½ x 11 plain white paper (except as specifically noted), with a one-inch margin all around, text shall be a minimum

12-point font size. Arial font is required. Tables and illustrations may use a reduced font size not less than 8-point and may be landscaped, tables and illustrations shall be used only to clarify or enhance information in proposal, not augment font size restrictions. A page printed on both sides shall be counted as two pages. Annexes, documentation, and attachments will count against the page limitations. Self-extracting .exe files, hyperlinks, and ZIP files are not acceptable. Paragraphs shall be separated by at least one blank line. All blank lines shall be no less than 10-point (this restriction is not applicable to lists, including bullets, content within tables, illustrations, and graphs). Proposals submitted in other fonts, including but not limited to Arial Black, Arial

Narrow, and Arial Unicode MS are not allowed and will result in an Offeror’s proposal not being evaluated or considered for award.

b. Foldouts (pages larger than 8 ½ x11, but not greater than 11 x17), if needed for clarification, may be included within the volumes and will count as one page per foldout. Foldouts cannot exceed five per volume. Any foldouts exceeding this limit will not be considered. Foldouts (i.e., diagrams, charts, graphs) shall not be used as a substitute for narrative text. For foldouts printed on both sides, each fold and side counts as 1 page each i.e. 4 pages per 1 11x17 foldout printed on both sides has one fold.

http://fbo.gov/

c. When requested to submit a project schedule in Microsoft Project or Adobe (pdf), the page limitation stated below for each volume are not applicable. Schedules submitted and requested in these formats as part of the proposal do not have page limitations, unless otherwise stated.

d. The Performance Work Statement (PWS) which is required to be submitted in

Volume III proposal, does not have a page limitation. However, an Offeror shall not include any details or proposal information within this PWS that is not relevant to the content of a PWS, or the Offeror risks having its PWS excluded during the evaluation process, rendering it ineligible for award.

e. The Service Level Agreement (SLA) provided as part of this solicitation is considered a draft SLA. A final SLA shall be developed by the Offeror, with input by the USG after award. Until a final SLA is developed and signed by all authorized parties the SLA submitted as part of the proposal is binding. The SLA does not have any page limitations.

f. Title pages, table of contents, table of figures, list of tables and glossary of abbreviations & acronyms do not count against page count limitations. The table of contents shall list sections, subsections and page numbers. Each volume shall contain a glossary of all abbreviations and acronyms used. Each acronym used shall be spelled out in the text the first time it appears in each proposal volume.

g. Each Volume shall be as brief as possible, while still including all required information and shall not exceed the maximum number of pages listed below.

The page count will be made by counting left to right consecutively. Proposal contents that exceed the stated page limitations will be removed from the proposal by the Contracting Officer (PCO), and will not be evaluated.

h. The Offeror’s proposal shall consist of six (6) Volumes each submitted electronically on separate compact discs (CD’s). A total of six (6) CDs shall be submitted in regards to this solicitation. Each CD must be clearly marked with the

Offeror’s Name, Phase Number, and Volume Number. CDs submitted must be compiled using Microsoft (MS) Office for Windows 2013 or a format which can be read by MS Office 2013 (except volume II see below), submitted on a CD-ROM to prevent accidental erasure of the data. Each volume shall be separate and complete so that evaluation of each volume can be accomplished independently.

The Volumes are as follows:

PHASE ONE:

Volume I – Security and Experience

Volume II – Contractual Documents

PHASE TWO:

Volume III – Technical

Volume IV – Past Performance

Volume V – Small Business Participation

Volume VI –Price Proposal

i. Volume II consists of:

i. One completed copy (including signatures) of the attached Standard Form

1449 and continuation sheets signed by a person authorized to enter into the proposed contract on behalf of the Offeror.

ii. Acknowledgements of all amendments to the solicitation and all continuation sheets are to be filled in as directed and Certifications and Representations.

Failure to sign or acknowledge all material amendments will result in your proposal not be evaluated and will not be considered for award.

iii. In order to initiate the use of ASSIST2Industry, the USG requires the names, company titles, telephone numbers, and email addresses of two individuals that the Offeror has designated as responsible for receiving and responding to the USG in the event discussions are opened and ASSIST is utilized.

iv. Contract Administration Data

v. Title Page

vi. Subcontracting Plan as required by FAR Clause 52.219-9, Alt II, Small

Business Subcontracting Plan. Please reference DFARS clause 252.219-

7003, Small Business Subcontracting Plan (DOD Contracts). If required, this plan will be negotiated concurrently with the rest of the proposal; however, it will not be evaluated as part of the proposal. This does not apply to any small business submitting an offeror. Failure to submit a plan will result in the

Offeror’s proposal not being evaluated and its proposal will not be considered for award.

2.2 Format for Proposal:

2.2.1 Phase Structure: Each proposal shall be submitted in separate Volumes as set forth below. Each proposal must include all Volumes and shall be submitted by the closing date of the solicitation. Failure to provide a Volume or any part of will result in the proposal being given an unacceptable rating.

Information provided in each phase shall be specific to that phase, volume, factor and that sub-factor. Each sub-factor proposal submitted shall not have information for another sub-factor contained within its page limitations. Each sub-factor is evaluated separately.

Phase One -

Volume I – Security and Experience

a. 1 CD Copy

b. Page Limitation:

Gate 1: DOD Provisional Authorization (PA) - No Page Limitation

Gate 2: Experience - 05 pages

c. File Naming Structure for Volume I: CompanyName-Security.XXX

d. Gate File Naming Structure for Volume I: CompanyName-Security-Gate#.XXX

Volume II - Contractual Documents

a. 1 CD Copy

b. Page Limitation: No Page Limitation

c. File Naming Structure for Volume II: CompanyName-Cont-Sect1.XXX

d. Two files shall be submitted in this volume. One file with a .pdf extension to submit Government documents (as required) that are in .pdf format and one file of the other volume content which shall be readable with MS Office 2013.

Phase Two -

Volume III - Factor 1 Technical Approach

a. 1 CD Copy

b. Page Limitation:

Sub-factor I: System Architecture – 35 Pages

Sub-factor II: Service Capability- 30 Pages

i. PWS –No Page Limitation

ii. SLA- No Page Limitation

iii. Milestone Schedule- No Page Limitation

c. File Naming Structure for Volume III: CompanyName-Technical

d. Sub-factor File Naming Structure: CompanyName-Technical-Subfactor#.XXX

Volume IV - Factor 2 Past Performance

a. 1 CD Copy

b. Page Limitation: No Page Limitation

c. File Naming Structure for Volume IV: CompanyName-Past Performance

d. Completion of Form PPI-002-M(1 per reference)(Attachment 0006)

Volume V - Factor 3 Small Business Participation

a. 1 CD Copy

b. Page Limitation: No Page Limitation

c. File Naming Structure for Volume V: CompanyName-Small Business

d. A completed Small Business Participation Plan (Attachment 0004)

Volume VI - Factor 4 Price

a. 1 CD Copy

b. Page Limitation: No Page Limitation

c. File Naming Structure for Volume VI: CompanyName-Price

d. Fully Populated Price Model Attachment 0005

2.3 Proposal Submission and Questions:

a. By submission of a proposal on electronic media, the Offeror must ensure that the submission is readable, in the format specified in the solicitation, and has been verified as free of computer viruses. Prior to any evaluation, the USG will check all files for viruses and ensure that all information is readable. In the event that any files are defective (unreadable), the USG will only evaluate the readable electronic files. Further, if defective (unreadable) media renders a significant deficiency in the Offeror's proposal, the USG will consider the proposal incomplete and not consider such proposals for further evaluation.

b. All proposals and related information shall be submitted to the Army at the address shown below no later than the date and time specified in the solicitation/amendment documents(s).

Army Contracting Command- Rock Island (ACC-RI)

Attn: CCRC-TC, Katherine Crompton Silvis

3055 Rodman Avenue

Rock Island, IL 61299-8000

c. Proposals MUST be delivered no later than 1400 hours USA Central Time (CT) on 13 Jan 2017 to Ms. Crompton Silvis at the address above.

d. All proposals received after the time and date listed above will be considered late and will not be handled in accordance with FAR 52.212-1.

e. Should an Offeror have difficulties with delivery dates for proposals, it should notify Ms. Crompton Silvis immediately at katherine.e.cromptonsilvis.civ@mail.mil or Ms. Carrie Holub at carrie.l.holub.civ@mail.mil .

mailto:katherine.e.cromptonsilvis.civ@mail.mil mailto:carrie.l.holub.civ@mail.mil

f. No email submissions will be accepted. If proposals will be hand carried to ACC-

RI, refer to clause 52.214-4584, Hand Delivered Bids, Quotes, or Proposals.

g. Any and all questions or comments pertaining to this solicitation shall be submitted in writing and addressed to the Contracting Officer, Katherine

Crompton Silvis at katherine.e.cromptonsilvis.civ@mail.mil and to the Contract

Specialist (CS) Carrie Holub at carrie.l.holub.civ@mail.mil. The USG is not obligated to provide responses to all questions submitted by Offerors, but will consider questions submitted and incorporate changes in the solicitation as deemed necessary. USG response to questions will be posted at www.fbo.gov for review by all Offerors. Therefore, questions/comments shall not be marked with a restrictive legend and shall not include proprietary information.

h. When submitting questions and comments, Offerors shall refer to specific text of the solicitation in a MS Excel (compatible with MS Excel 2013) file attachment.

Format is provided below:

Offeror

Name:

RFP Section Volume Attachment Page Paragraph Question/Comment

The PCO and CS will field written questions to ensure that all Offeror inquiries have been addressed in advance of the proposal suspense date/time. It is preferred that only one set of questions is submitted by each Offeror instead of multiple sets of questions.

3 Specific Proposal Instructions:

The Offeror shall submit documentation illustrating its approach to satisfying the requirements of this solicitation. Proposals must be clear, coherent, and prepared in sufficient detail for effective evaluation of the Offeror’s proposal against the evaluation criteria. Documentation shall cover all aspects of this solicitation and include the

Offeror’s approach to meeting the Army’s requirements to providing the Army UC Soft

Client. Proposals must clearly demonstrate how the Offeror intends to accomplish the project and must include convincing rationale and substantiation of all claims.

Unnecessarily elaborate brochures or other presentations beyond those sufficient to present a complete effective response to the solicitation are not desired.

Offerors are responsible for including sufficient details to permit a complete and accurate evaluation. The proposal shall be detailed and clearly stated to allow an mailto:katherine.e.cromptonsilvis.civ@mail.mil mailto:carrie.l.holub.civ@mail.mil http://www.fbo.gov/ assessment by the USG without the need for additional clarifications or discussions.

The Offeror shall provide detailed information in accordance with the solicitation. All information provided shall be specific to the UC Soft Client requirement.

The Offeror shall be held responsible for the validity of all information supplied in its proposal, including information provided by potential subcontractors. The USG does not assume the duty to search for data to cure problems it finds in the proposal. The burden of providing thorough and complete information remains with the Offeror.

In the response to the solicitation, the Offeror must address the following Phases:

3.1 Phase ONE – Security and Experience

Any errors or omissions in this phase, where the USG is unable to ascertain the intent of the information without discussions, will result in the proposal being determined unacceptable. Failure to include the minimum number of references (Gate 2) will result in submitted proposal being removed from further consideration and will be determined unacceptable and ineligible for award.

3.1.1 Gate 1: DoD Provisional Authorization (PA) Impact Level 5 and 6 Certifications

For Offerors proposing a Cloud based solution on or off premise: If an Offeror has a current DoD PA for its proposed Cloud Service Offering (CSO) at the required impact level (Impact Level 5 and 6) it shall submit the DoD PA memo signed by the DISA

Authorizing Official.

Each Offeror responding to this RFP that does not already have a DoD PA at the required security impact level (IL) 5 for its CSO shall submit a Third Party Assessment

Organization (3PAO)-produced Readiness Assessment Report (RAR), The RAR shall include all required FedRAMP and DoD information relevant to being assessed for a

DoD PA at IL 5. The Offeror shall also include its proposed schedule to achieve the

DoD PA IL 5 within 180 days of contract award. The schedule submitted shall provide detailed dependencies (contractor and USG), events in order to meet the required dates for PA IL 5, and shall provide a workflow of how it will be obtained. The RAR shall encompass each layer of the Cloud Service Offering and should be based upon DoD

Cloud Computing regulations and guidance.

The Offeror shall also include its proposed schedule and plan to achieve IL 6, with classified overlay. The schedule submitted shall provide detailed dependencies

(contractor and USG), events in order to meet the required dates for PA IL 6 and shall provide a workflow of how it will be obtained by IOC (C+440).

For Offerors proposing a Non-Cloud based solution: If a proposed solution has the

DoDI 8500.01 and 8510.01 Risk Management Framework (RMF) authorizations/accreditation, the Offeror shall provide the RMF authorizations/accreditations for its solution. The solution shall support a Security

Categorization and Control Selection for National Security Systems (CNSSI) 1253 categorization of Moderate Confidentiality, Moderate Integrity, and High Availability (M, M, and H). The RMF authorizations and accreditations shall be submitted for NIPR.

(SIPR RMF authorization/accreditations may be submitted to show how an Offeror will meet the SIPR requirement and will not have to submit a schedule as provided below.)

If the proposed solution does not have an RMF authorization/accreditations for NIPR or SIPR, the Offeror shall provide a milestone schedule which reflects the processes/milestones to account for how it will accomplish all 6 steps of the RMF process to include authorization. The schedule submitted shall provide detailed dependencies (contractor and USG), events in order to meet the required dates for NIPR and SIPR, and shall provide a workflow of how it will be obtained.

For Offerors proposing a Hybrid solution (Cloud and Non-Cloud): For the Cloud portion of an Offeror’s solution: it shall submit the requirements, as outlined for Cloud based solutions (see above). For the non-cloud portion of an Offeror’s solution it shall submit the requirements, as outline for non-cloud based solutions (see above).

*For purposes of proposal only, Offerors shall use January 1, 2017 as a fictional award date; in order to demonstrate its ability to obtain PA at the required levels.

The schedules submitted under Gate 1 shall only include information on and be related to, obtaining the above security requirements and authorizations/accreditations. The schedule should not include information requested under the technical factor below. The technical factor is where a complete milestone/IMS schedule shall be submitted. Failure to follow this instruction may result in submitted proposal being removed from further consideration and will be determined unacceptable and ineligible for award

3.1.2 Gate 2: Experience

The Offeror shall describe its experience in providing and deploying UC Soft Client

Subscription Services to a minimum of 100,000 users in a 36 month period, in blocks of

10,000 to 40,000 users. The Offeror shall submit documentation of contracts which demonstrates the Offeror’s corporate capability and its partners which may include;

management and oversight of, engineering of, furnishing of, installation of, securing of, testing of, and experience in performing or providing services required under this effort.

The Offeror shall submit and clearly identify a minimum of 1 reference where services were performed or still being performed anytime within 3 years of the issuance of this solicitation. The Offeror shall provide descriptions of the following information in each reference:

a. Provide contract number for which the work was performed, identify the agency or commercial entity the work was performed for.

b. Identify the start and stop dates for this contract on which the work was performed.

c. Identify the number of users services were deployed to, timeframe deployed, and geographic locations deployed.

d. Identify specific UC capabilities that were performed on the referenced contract.

Provide how these capabilities directly relates to the type of service required under this effort.

3.2 PHASE TWO

Volume III-Factor 1 Technical Approach

Offerors are required to submit a comprehensive and complete technical proposal that demonstrates its ability to perform the work described in this solicitation. Offerors are cautioned to address all elements of Attachment 0001 (Statement of Objectives) and provide sufficient information to allow proposed solutions to be evaluated fully per

Attachment 0003 (Evaluation Factors for Award). The technical proposal shall contain a proposed Performance Work Statement (PWS). The technical proposals submitted shall not include statements of; at no additional price, not separately priced, or other similar statements as it relates to price.

Sub-factor 1: System Architecture – 25 Pages

a. The Offeror shall provide as part of its proposal its solution which demonstrates the Offeror’s ability to implement UC Soft Client requirements for a seamless UC deployment worldwide, including risk mitigation procedures that the Offeror must adhere to for DoD PA/Cybersecurity authentication challenges and infrastructure changes to NIPRNet/ SIPRNet to ensure minimal disruption during deployment of

UC.

b. The Offeror shall provide a proposal which identifies its hosting requirements for its proposed solution. Provide details and documentation, including system architecture and diagram, on how the Offeror will plan for hosting its technical solution in unclassified and classified environments and by geographical region.

Offerors shall propose hosting solutions for Continental United States (CONUS) to include Hawaii, Alaska and US territories and Outside Continental United

States (OCONUS) requirements in accordance with the Cloud Computing SRG version 1R2 (section 5.2.1.1) for cloud based solutions, in accordance with DoDI

8500.01 and 8510.01 Risk Management Framework (RMF) for non-cloud based solutions, and in accordance with SRG and DoDI requirements for hybrid solutions. Proposals shall provide information on efficient use of on premise hosting space and environmental resources. All assumptions and constraints shall be stated clearly. The Offerors response must clearly and completely describe its approach for hosting UC Services on both the NIRPNet and SIPRNet and within CONUS and OCONUS.

c. Offerors shall provide for its on premise hosting and shall provide the contractor’s

NIPRNet and/or SIPRNet requirements for floor space, rack space, physical security/separation, high-density compute/cooling environments, per rack power requirements (single phase, 3-phase, amperage, voltage, etc.), bandwidth requirements, physical access requirements, remote management, and networking environment (IP addressing, sub netting, Computer Network Defense

(CND). For either proposed hosting environment for CONUS the Offeror shall provide how the hosting environment will operate with the Cloud Access Point and service levels will be maintained during performance (for Cloud and hybrid based solutions).

d. The Offeror must clearly and completely describe its approach to integration with the Public Switched Telephone Network (PSTN), including integration with the

Defense Switched Network (DSN).

e. Offeror’s that propose to use Army Local Session Controllers in the delivery of the service globally , must include a plan in its proposal that addresses client licensing; which provides a standardized enterprise service and includes portability of licenses. The plan shall provide the approach the Offeror will use for technical refresh which will alleviate the Army’s investment in new equipment.

f. For cloud based software subscription solutions and for any portion of a solution which is off premise, the Offeror’s system design documents and proposed architecture must clearly and completely describe how it meets the peering point gateway/interfaces (SBC/firewall) requirements in order to separate its commercial managed network from the DoD network; in compliance with UCR

2013, change 1 and how it is XMPP compliant.

g. For any portion of a solution which is on premise, the Offeror’s system design documents and proposed architecture must clearly document how it’s proposed on premise hardware and software has gone through JTIC certification processes and is approved to for use on a DoD network; in compliance with the

DoD UC Approved Products List.

Sub-factor 2: Service Capability - 30 Pages

a. The Offeror shall provide as part of its proposal a baseline Service Level

Agreement (SLA). The Offeror SLA shall at a minimum provide the following information:

i. How SLAs proposed directly aligns and comprehensively captures requirements identified within the Statement of Objectives (SOO), PWS, and Quality Control Plan.

ii. How proposed SLAs identify how the Contractor will monitor performance and report results.

iii. How proposed SLAs logically and clearly defines key terms (e.g.

dates/performance); levels of service and performance that NETCOM would expect the Contractor to meet; capacity and capability of service.

iv. How proposed SLAs will resolve disputes that are discovered and how issues are handled; enforceable consequences and remedies for performance failures; and how the Contractor will mitigate the risk of future failures.

v. Proposed SLAs must describe any applicable exception criteria when the Contractor performance measures do not apply.

vi. Provide how the Offeror will support the client to include Reporting, Help Desk Integration, System Interface Management and Identity

Management/Authentication. (e.g. support hours, response time to issues and problems, target time to resolve).

vii. Maintainability to audit performance data.

b. The Offeror shall provide as part of its proposal a detailed plan on how it will achieve and maintain 99.9% availability of all services provided under this contract.

c. The Offeror shall develop a PWS including a performance requirements summary in response to the SOO and the solicitation terms and conditions. The

Offeror shall propose a written PWS for the entire scope of the UC Soft Client requirement based on Attachment 0001, Statement of Objectives and other information contained within the solicitation. The Offeror’s proposed PWS shall be concise, but detailed enough for the USG to determine the Offerors understanding of the nature of the work and plan for providing the services and products required to achieve Initial Operating Capability (IOC), Full Operating

Capability (FOC) and terms and conditions as provided in the solicitation.

Offerors are cautioned that “parroting” of the Technical requirements or the

Statement of Objectives (SOO) with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform.

The PWS shall include and provide how the Offeror will provide end user training to meet performance requirements. In addition, the PWS shall provide the

Offeror’s approach to transition the Army on and off the UC Solution provided, to include security and removal of information from equipment. The PWS shall address hardware and software requirements for end user devices as provided in the SOO and address how the Offeror will maintain any GFE/GFP as required by the solicitation. If the Offeror is providing any capabilities in addition to those required in the SOO, the Offeror shall include these capabilities in the PWS and describe the approach to providing, the performance metrics for these capabilities and other information as required in a PWS. The PWS shall include a performance requirements summary.

d. The Offeror shall provide a milestone schedule which demonstrates the Offerors proposed approach to implementation of its solution, and shall include all dependencies and major events to provide a fully operational solution to the

USG. The schedule shall include all dates and events, deliverables, and dependencies provided in the SOO/PWS. The Offeror shall provide a project schedule that includes at a minimum: kickoff date, site survey, PA and/or RMF requirements, CDRLs, Key Meetings (significant performance events on the

Work Breakdown Structure (WBS) and all other critical events as appropriate.

Each activity must have a start and finish date, be logical, and demonstrate project life cycle. The schedule will show dependencies and have the predecessor/successor properly aligned. The schedule submitted will not count against the overall page count for this sub-factor and must be submitted in an approved format or it will not be evaluated. *For purposes of proposal only, Offerors shall use January 1, 2017 as a fictional award date.

e. The Offeror shall provide and describe how it will staff and manage personnel to support its solution, in order to maintain its SLA and to provide the best value to the Government. The proposal shall include how it will meet the SLA for on premise locations in OCONUS, and how it will manage its staff in OCONUS locations.

f. The Offeror shall provide how it will conduct a site survey (to include required personnel, USG and contractor) and at which locations if it intends to conduct it.

The proposal shall address how the survey will be conducted to ensure the need for repeat surveys are avoided and that the approach does not create an undue burden on the Government to support. The proposal shall include how the

Offeror will address and provide risk mitigation, if its proposed solution is not conducive for the proposed locations, in order to not impact schedule or level of service.

3.3 Volume IV – Factor 2 Past Performance

Submission requirements for the Past Performance Volume IV are listed in paragraph

2.2. - Format for Proposal

3.3.1The Offeror may submit with its initial proposal up to three contract or project references for itself. All project or contract reference(s) shall represent recent and relevant performance.

Contract References shall represent demonstrated performance on recent and relevant contracts as a prime or first tier subcontractor under Department of Defense (Army, Navy, DLA, etc.), USG (Federal, State, Local) and/or commercial contracts. References shall match the solution being proposed. Example: if proposing a cloud based service, references shall be for recent and relevant cloud based services.

Recent performance means contracts and task orders where the services or deliverables were performed anytime within three (3) years of the issuance of this solicitation. The

USG reserves the right to consider any significant recent or past performance after the solicitation closing date and prior to a contract award decision.

Relevant performance means contracted work efforts that are currently or have been performed that provides CONUS and/or OCONUS accessible Unified Capabilities (UC) software client services in support of voice, video, instant messaging and/or chat, presence and desktop sharing capabilities as a cloud-based software service, hybrid service or non-cloud based service.

3.3.2 The contract information to be provided with each contract shall be provided on

Form PPI-002-M (Attachment 0006). The Offeror shall complete Form PPI-002-M in its entirety for each referenced contract in Volume IV Past Performance.

3.4 Volume V – Factor 3 Small Business Participation

3.4.1 Small Business Participation Proposal

The Offeror shall demonstrate small business participation by detailing its proposed approach to meet the requirements under this factor by addressing the following two areas in its Small Business Participation proposal:

a. Proposed Small Business Participation in performance of the potential contract (applies to Other than Small Businesses and Small Businesses).

b. Commitment to Small Business

i. Payment Procedures (applies to Other Than Small Businesses and Small Businesses)

ii. Compliance with Small Business Subcontracting Plans (applies to Other Than Small Businesses only)

3.4.2 Proposed Small Business Participation Plan

3.4.2.1 The Offeror shall submit the following documentation or its proposal will be removed from further consideration and will no longer be eligible for award.

3.4.2.1.1 The Offeror shall complete the Small Business Participation Plan Attachment

0004 to show maximum practicable opportunities to small businesses to compete on this requirement in accordance with FAR 52.219-8, Utilization of Small Business

Concerns.

3.4.3. Commitment to Small Business

3.4.3.1 The Offeror shall include a written statement of its established procedures to ensure timely payments to small business subcontractors in accordance with FAR

52.219-8, Utilization of Small Business Concerns (for those contracts under which it was required within the past three years from the closing date of this solicitation). If not required in any recent contracts, the Offeror shall so state.

3.4.3.2 Note for other than small businesses ONLY. Compliance with terms and conditions of FAR 52.219-9, Small Business Subcontracting Plan (if required on recent contracts) The Other than Small Business Offeror shall provide three Individual

Subcontracting Reports (ISRs) for recent contracts (within the past three years from the closing date of this solicitation) that included a subcontracting plan. If not required in any recent contracts the Offeror shall so state. If the Offeror has less than three recent contracts, the Offeror shall provide the most recent ISR for each contract it has, and state that the Offeror does not have three recent contracts.

3.5 Volume VI – Factor 4 Price

Pricing Model Instructions:

All prices submitted for this acquisition shall be stated in current U.S. dollars, and shall include the appropriate escalation. The prices must be submitted within the Attachment

0005, Price model. The price model should not be changed in any manner by the

Offeror, outside what is allowed by the below instructions. Any Offeror who fails to submit prices within this model or changes the model will be removed from further consideration for award. If a price is $0 for any field, a price of $0 shall be entered, spaces and fill-ins shall not be left blank.

Further consideration for award.

Offerors shall understand that all CLINs are Firm-Fixed-Priced (FFP), and as such are fixed throughout the life of the contract. The Offeror will not be allowed to exceed the prices proposed or adjust its pricing or propose new prices after contract award.

a. Summary Tab: Offerors shall enter the Offeror Name, Proposal Number/Version, and Proposal Date in the corresponding cells. Offerors shall input a FFP per year for the following CLINs:

CLIN 0005 – TASK ONE - NIPRNet Outlook Client Integration Price (ONE TIME FOR

ENTIRE USER BASE)

CLIN 0006 – TASK ONE - SIPRNet Outlook Client Integration Price (ONE TIME FOR

ENTIRE USER BASE)

CLIN 0007 – TASK ONE - NIPRNet Directory Integration Price (ONE TIME FOR

ENTIRE USER BASE)

CLIN 0008 – TASK ONE - SIPRNet Directory Integration Price (ONE TIME FOR

ENTIRE USER BASE)

CLIN 0009 – TASK ONE – XMPP Interface Price (ONE TIME PER INTERFACE FOR

ENTIRE USER BASE)

CLIN 0011 – TASK ONE – DRSN and ECVoIP Connections (or VoSIP) Integration

(ONE TIME FOR ENTIRE USER BASE)

b. Base Year, Option Year One (OY 1), Option Year Two (OY 2), Option Year Three

(OY 3), and Option Year Four (OY 4) Tabs:

Offerors shall enter a Firm-Fixed-Price per user for CLINs 0001 through 0004, and CLIN

0009, and CLIN 0010 within each of the yellow highlighted cells, for each of the corresponding quantity ranges. These FFPs shall represent the following:

CLIN 0001 - Non-Secure Internet Protocol Router Network (NIPRNet), One-Time

Implementation Price per User – Base and Option Years One (1) through Four (4)

CLIN 0001 shall represent the Firm-Fixed- Price per user, by quantity range and weighting factor, that an Offeror charges the USG to implement a new user onto the

NIPRNet service. The FFP shall include the vendor’s costs to purchase all hardware and software (user and server) needed, and all labor required to install and set-up the service in the hosting facility. The FFP shall also include information assurance costs, training provided by the vendor to Network Enterprise Center (NEC) personnel, and

Computer Based Training (CBT) provided to new users, as well as the cost of setting up the test environment.

CLIN 0002 – NIPRNet Recurring Price, Recurring Price per User – Base and

Options One (1) through Four (4)

CLIN 0002 shall represent the FFP per user, by quantity range and weighting factor, that an Offeror charges the USG to provide the recurring NIPRNet service. The FFP shall include the vendor’s costs of maintaining the service, to include software assurance, hardware maintenance, data center labor, tier III help desk and application administration. The FFP shall also include any ongoing information assurance costs and maintaining the test environment.

CLIN 0003 – Secret Internet Protocol Router Network (SIPRNet), One-Time

Implementation Price per User – Base and Options One (1) through Four (4)

CLIN 0003 shall represent the FFP per user, by quantity range and weighting factor, that an

Offeror charges the USG to implement a new user onto the SIPRNet Service. The FFP shall include the costs to purchase all hardware and software required, and all labor necessary to install and set-up the service in the hosting facility. The FFP shall also include information assurance costs, and training provided by the Offeror to NEC personnel.

CLIN 0004 – SIPRNet, Recurring Price, Price per User – Base and Options One (1) through Four (4)

CLIN 0004 shall represent the FFP per user, by quantity range and weighting factor, that an Offeror charges the USG to provide the recurring SIPRNet service. The FFP shall include the costs of maintaining the service, to include software assurance, hardware maintenance, data center labor, tier III help desk and application administration. The FFP shall also include any ongoing information assurance costs.

CLIN 0009 - TASK ONE – XMPP Interface and CLIN 0009 – TASK TWO – XMPP

Interface Sustainment Price

CLIN 0009 – TASK ONE shall represent the FFP per XMPP interface point, that an

Offeror charges the USG to provide the Interoperability with an existing system.

CLIN 0009 TASK TWO – XMPP Interface Sustainment Price shall represent the FFP per year per interface point, that an Offeror charges the USG to provide the

Interoperability Sustainment of CLIN 0009 Task One.

CLIN 0010 - TASK ONE PSTN and DSN Integration – Base and Option Years One

(1) through Four (4), and TASK TWO – PSTN and DSN Sustainment Option –

Base and Option Years One (1) through Four (4), CLIN 0010 - TASK ONE AND TWO shall represent the FFP per user, by quantity range and weighting, that an Offeror charges the USG to provide the PSTN and DSN

Integration Points Sustainment. Offerors shall note that this is an optional CLIN within the Base and Option Years One (1) through Four (4) and shall be contractually exercised as such.

TASK TWO CLINs 0005, 0006, 0007, 0008, 0009, (TASK TWO CLIN 0010 is listed above) and 0011 within each of the yellow highlighted cells. These FFPs per year shall represent the following:

CLIN 0005 - TASK TWO - NIPRNet Outlook Client Integration Point Sustainment Price

CLIN 0006 - TASK TWO - SIPRNET Outlook Client Integration Point Sustainment Price

CLIN 0007 - TASK TWO - NIPRNet Directory Integration Point Sustainment Price

CLIN 0008 - TASK TWO - SIPRNet Directory Integration Point Sustainment Price

CLIN 0009 - TASK TWO – XMPP Interface Sustainment Price

CLIN 0011 – TASK TWO – DRSN and ECVoIP Connections (or VoSIP) Sustainment

Price

CLIN 0012 – Contract Data Requirements List (CDRL), DD Form 1423

CLIN 0012 is not separately priced and is for all data deliverables required under this requirement.

CLIN 0013 – Contract Data Requirements List (CDRL), DD Form 1423