Attachment_0002_Section_L_UC_Soft_Client_Draft.docx

Sections L

SECTION L: INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

L.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 L.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 award 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. Offeror’s 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 them in accordance with FAR 15 as provided in Section M. 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 is provided as Attachment 0008 to this solicitation. Offerors who 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 will 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, evaluators do not access other volumes for information.

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. If an Offeror fails to include the statement that its proposal t is valid for the time period of 200 days if discussions are not opened and 380 days if discussions are opened (200 days + 180days), its proposal will not be evaluated and will not be considered for award.

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.

L.2 Proposal Instructions:

L.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. 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.

c. When requested to submit a project schedule in Microsoft Project of 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 by the USG a non-binding SLA. A final SLA shall be developed by the Offeror with input by the USG, until a final SLA is developed and signed by all authorized parties. 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, 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 in Section K. Failure to sign or acknowledge all 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 this plan will result in Offeror’s entire proposal from being evaluated and will not be considered for award.

j. If any of the instructions presented in paragraphs above are not followed, the proposal will not be further evaluated and will not be further considered for award.

L.2.2 Format for Proposal:

L.2.2.1 Phase Structure: Each proposal shall be submitted in separate parts as set forth below. Each proposal must include all parts and shall be submitted by the closing date of the solicitation. Failure to provide a part may result in the proposal being given an unacceptable rating. Information provided in each phase shall be specific to that phase 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; evaluators do not access other sub-factors for information.

Phase One - Volume I – Security and Experience

a. 1 CD Copy

b. Page Limitation:

Gate 1: Approved Products List (APL) - 10 pages Gate 2: DOD Provisional Authorization (PA) - No Page Limitation Gate 3: Experience - 02 pages

c. File Naming Structure: CompanyName-Security.XXX Volume II - Contractual Documents

a. 1 CD Copy

b. Page Limitation: No Page Limitation

c. File Naming Structure: CompanyName-Cont-Sect1.XXX

Phase Two - Volume III - Factor 1 Technical Approach

a. 1 CD Copy

b. Page Limitation:

Sub-factor I: System Architecture – 25 Pages Sub-factor II: Service Capability- 25 Pages

i. PWS –No Page Limitation

ii. SLA- No Page Limitation

iii. Milestone Schedule- No Page Limitation

c. File Naming Structure: CompanyName-Technical Volume IV - Factor 2 Past Performance

a. 1 CD Copy

b. Page Limitation: No Page Limitation

c. File Naming Structure: 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: CompanyName-Small Business

d. A completed Contract Participation Model (Attachment 0004)

Volume VI - Factor 4 Price

a. 1 CD Copy

b. Page Limitation: No Page Limitation

c. File Naming Structure: CompanyName-Price

d. Fully Populated Price Model Attachment 0005

L.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 Roman Avenue Rock Island, IL 61299-8000

c. Electronic proposals MUST be delivered no later than XXXX hours USA Central Time (CT) on XX XXX XXXX 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, they should notify Ms. Crompton Silvis immediately at katherine.e.cromptonsilvis.civ@mail.mil or Ms. Carrie Holub at 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 (L-17).

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, and shall be submitted no later than XXX. The USG is not obligated to provide responses to all questions submitted by Offerors, but will consider them 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:

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.

L.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 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:

L.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 3) will result in submitted proposal being removed from further consideration and will be determined unacceptable and ineligible for award.

Gate 1: Unified Capabilities - Approved Products List (UC APL) The Offeror shall submit UC APL documentation for the proposed UC Soft Client Solution. The solution must have completed the Joint Interoperability Test Command (JITC) UC APL Certification, Process (detailed in the “Unified Capabilities Approved Products List (UC APL) Process Guide, version 2.3, December 2014 (or current version).

Gate 2: DoD Provisional Authorization (PA) Level 5 and 6 Certifications The Offeror shall submit its SI Level 5 and 6 PA Certification(s), and associated artifacts for their specific UC soft-client Cloud Service Offering (CSO). Each Offeror responding to this RFP that does not already have a DoD PA at the required security impact level will submit a Third Party Assessment Organization (3PAO)-produced Security Assessment Report, The report shall include all required FedRAMP and DoD documentation relevant to being assessed for a DoD PA at SI levels 5 and 6. The Offeror shall include their proposed schedule to achieve the DoD PA within 90 days of contract award. The schedule submitted shall provide detailed dependencies (contractor and USG), events in order to meet the required dates for PA, and shall provide a workflow of how it will be obtained.

Gate 3: Experience The Offeror shall describe its experience in providing and deploying UC Soft Client Subscription Services to a minimum of 100,000 users within a 12 month period. The Offeror shall submit examples of contracts which demonstrates the Offeror’s corporate capability and experience in performing the 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.

L.3.2 PHASE TWO

Volume III-Factor 1 Technical Approach Offerors are required to submit a comprehensive and complete technical proposal that demonstrates their ability to perform the work described in this solicitation. Offerors are cautioned to address all elements of Section C (Statement of Objectives) and provide sufficient information to allow proposed solutions to be evaluated fully per Section M (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, 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). 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 CAP and service levels will be maintained during performance.

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).

Sub-factor 2: Service Capability - 25 Pages

a. The Offeror shall provide as part of their 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 cloud service.

iv. How proposed SLAs will resolve disputes that are discovered and how they 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 Administer 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 contractor 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, PA 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 to the overall page count for this factor and must be submitted in an approved format or it will not be evaluated.

L.3.3 Volume IV – Factor 2 Past Performance Submission requirements for the Past Performance Volume IV are listed in L 2.2. - Format for Proposal

L.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 as a prime.

Contract References represent recent and relevant performance under Department of Defense (Army, Navy, DLA, etc.), USG (Federal, State, Local) and/or commercial contracts.

A prime contractor is defined as the contractor that received or was issued the contract, task and/or delivery order for the services and/or products provided.

Recent Contracts are defined as Contracts where services or deliverables performed as a Prime Contractor - anytime within three (3) years of 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.

L.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.

The Government recommends that Offerors limit past performance references to those involving performance as a prime or first tier subcontractor unless it cannot otherwise be avoided.

L.3.4 Volume V – Factor 3 Small Business Participation Small Business Participation introductory overview shall state any assumptions associated with the proposed Small Business Participation Factor.

L.3.4.1 Small Business Participation Proposal

L.3.4.2 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

b. Commitment to Small Business

Definitions:

Participant - as used in this factor, includes the Offeror as well as any Subcontractor.

Participation - as used in this factor, includes the work (dollars) performed by the Offeror, as well as the work (dollars) performed by Subcontractors.

Recent - is defined anytime within three (3) years of the issuance of this solicitation.

Requirement - as used in the adjectival ratings for this factor, is defined as a small business participation plan.

L.3.4.3 Proposed Small Business Participation

The small business participation factor, as used in this solicitation, assesses the offerors plan to maximize opportunities for small business in the performance of the solicitation requirements.

L.3.4.3.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.

L.3.4.3.1.1 The Offeror’s proposal shall include a completed Contract Participation Matrix. The Offeror shall populate every column on the Attachment 0004 for each participant. The Contract Participation Matrix shall identify:

a. Full Company Name for each participant.

b. CAGE Code each for each participant.

c. Each Socio-Economic Category the participant qualifies for (Small Business (SB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran-Owned Small Business (SDVOSB), Small Disadvantaged Business (SDB), Women-Owned Small Business (WOSB), and Historically Underutilized Business Zone (HUBZone) Small Business).

d. Total Dollars allocated to each participant for the total period of performance.

e. The Offeror shall include proposed participation dollars for itself in the small business participation field, if a SB, or in other than small business participation field, if other than small.

f. The total dollars proposed for each category (SB, SDB, WOSB, HUBZone, VOSB, SDVOSB, and Other than Small Businesses).

g. The total contract value (total dollars proposed to Small Businesses + total dollars proposed to Other than Small Businesses). The total participation dollars shall equal the total evaluated price or Subtotal Contract Value proposed in Attachment 0005 - Price Model.

h. The percentage of participation (goal) for each socio-economic category.

i. Note: Small Business participation shall include total dollars allocated for the business in each category for which the business qualifies. For example, if the Offeror allocates $100 to a HUBZone-certified SDVOSB, the Offeror would include $100 in the SB category, $100 in the HUBZone category, $100 in the SDVOSB category, and $100 in the VOSB category.

L.3.4. 3.1.2 The Offeror shall provide the written certification of size (either small or other than small) and socio-economic status for each small business subcontractor proposed for this procurement. The Offeror may, but is not required to, provide a copy of the System for Award Management (SAM) certifications for clause 52.219-1, Small Business Program Representations in lieu of written certifications. However, for HUBZone certified subcontractors, the Offeror shall provide evidence of HUBZone certification using one of the methods in FAR clause 52.219- 8(d) (2). The written certifications shall match the size and socio-economic status identified in the Contract Participation Model (Attachment 0004) for each subcontractor.

L.3.4.4. Commitment to Small Business

The Offeror’s proposal shall also provide evidence supporting the Offeror’s commitment to small business. This information shall address:

a. The Offeror shall provide information on its historical small business participation.

b. Compliance with all terms and conditions of FAR 52.219-8, Utilization of Small Business Concerns (when required on recent contracts). This shall include procedures established to ensure timely payments to small business subcontractors. This clause is normally in most Federal contracts, and is also applicable to small businesses. If not required in any recent and relevant contracts, the Offeror shall so state.

c. Compliance with terms and conditions of FAR 52.219-9, Small Business Subcontracting plan (when required on recent contracts). If not required in any recent contracts, the Offeror shall so state.

d. Actual small business utilization compared to small business participation goals identified in the approved subcontracting plan for a minimum of 3, but no more than 5 recent contracts that included a subcontracting plan. Offerors shall identify the date of the last Individual Subcontracting Report (ISR). Offerors shall address achievement on each individual goal stated within the subcontracting plan including good faith effort if the goal was not achieved. 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.

e. The Offeror shall submit documentation that demonstrates a commitment to small business. The documentation may include bilateral teaming arrangement, an explanation of internal controls/documentation /systems, or any other documentation that demonstrates a commitment to small business. The Offeror’s submission must explain how the documentation demonstrates a commitment to small business. Lack of documentation may be viewed as the Offeror not having a strong commitment to the USG’s small business program.

Note for other than small businesses ONLY. Separate from Small Business Participation, other than small business offerors shall also submit a Small Business Subcontracting Plan as required by FAR 19.7 (FAR Clause 52.219-9, Small Business Subcontracting Plan). The Small Business Subcontracting Plan shall be consistent with proposed small business participation. The subcontracting plan shall be submitted in Volume II, not this Volume.

L3.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 on 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 on this model or makes changes to the model in any manner which is not allowed, will result in the Offeror’s proposal being removed from further consideration and will no longer be eligible for award.

Offerors shall understand that all CLINs are either Firm-Fixed-Unit-Prices (FFUPs), or 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 for the following CLINs:

CLIN 0005 - NIPRNet Outlook Client Integration Price (One Time for Entire User Base) CLIN 0006 – SIPRNet Outlook Client Integration Price (One Time for Entire User Base) CLIN 0007 – NIPRNet Directory Integration Price (One Time for Entire User Base) CLIN 0008 – SIPRNet Directory Integration Price (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-Unit Price (FFUP) for CLINs 0001 through 0004 and CLIN 0010 within each of the yellow highlighted cells, for each of the corresponding quantity ranges: 500-75,000, 75,001-150,000, 150,001-500,000, and 500,001-1,000,000. This FFUP 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-Unit Price (FFUP), by quantity range, that an Offeror charges the USG to implement a new user onto the NIPRNet service. The FFUP 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 FFUP 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 FFUP, by quantity range, that an Offeror charges the USG to provide the recurring NIPRNet service. The FFUP shall include the vendor’s costs of maintaining the service, to include software assurance, hardware maintenance, data center labor, tier II help desk and application administration. The FFUP 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 FFUP, by quantity range, that an Offeror charges the USG to implement a new user onto the SIPRNet Service. The FFUP shall include the costs to purchase all hardware and software (server only) required, and all labor necessary to install and set-up the service in the hosting facility. The FFUP 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 FFUP, by quantity range, that an Offeror charges the USG to provide the recurring SIPRNet service. The FFUP shall include the costs of maintaining the service, to include (server) software assurance, hardware maintenance, data center labor, tier III help desk and application administration. The FFUP shall also include any ongoing information assurance costs.

CLIN 0009- Tactical Interoperability: the Offeror shall input a FFP (extended price) within each yellow highlighted cell for the Base and Option Years One (1) through Four (4) Tabs.

CLIN 0010 – PSTN Integration Option: the Offerors shall input a FFP (extended price) within each yellow highlighted cell for the Base and Option Years One (1) through Four (4) Tabs. 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.

CLIN 0011 – Contract Data Requirements List (CDRL), DD Form 1423 CLIN 0011 is not separately priced and is for all data deliverables required under this requirement.