HS0021-15-R-0011_AMENDMENT_0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

The purpose of this amendment is to:

1) Remove the reference to "Volume V" from Section M (Factor V-Price/Cost) of the solitation as a Volume V is no longer required.

2) Clarify Sub-Factor 2.2-Key Personnel summary.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 21

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

16C. DATE SIGNED

BY 02-Jun-2015

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

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HS0021-15-R-0011

X 9B. DATED (SEE ITEM 11)

13-Feb-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

02-Jun-2015

CODE

DEFENSE SECURITY SERVICE

SHAWNA MITCHELL 571.305.6548

RUSSELL-KNOX BUILDING

27130 TELEGRAPH ROAD

QUANTICO VA 22134

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HS0021-15-R-0011

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

L.1. EXCEPTIONS OR CONDITIONS CONTAINED IN OFFEROR'S PROPOSAL.

In the event the offeror takes any exception to, or sets any conditions for its proposal under this solicitation, such exceptions or conditions shall be set forth in a cover letter to offeror's proposal. However, exceptions or conditions may make an offeror’s proposal nonresponsive and ineligible for award.

L.2 ELIGIBILITY.

To be eligible to submit an offer under this Solicitation and receive award, an offeror must meet the following requirements to be awarded the basic contract and Task Order 0001 which shall be awarded concurrently.

L.2.1.1 The National Industrial Security System (NISS) requirement is a critical program necessary for DSS to successfully meet its mission. The Government requires that the contractor's performance begin upon notice to proceed without delay. Therefore, the Contractor shall have at least an Interim facility clearance of SECRET in accordance with the DoD 5220.226M, National Industrial Security Program Operating Manual (NISPOM) at the time of contract award. This requirement applies to any entity that may require access to classified material in the performance of any contract that may result from this solicitation. An offeror in line for award will be ineligible for award if any partner, subcontractor or entity in an offeror’s proposal requiring access to classified does not have the required security clearance at the time of award, and the contract will be awarded to the next eligible offeror.

L2.1.2: In order to access additional technical data associated with this requirement please provide the following information shawna.mitchell@dss.mil and keanna.houston@dss.mil : company name, address, and cage code.

Within one business day, you will receive a user id and password with a link to access the NISS Reading Room for this requirement.

L.3. INTRODUCTION.

Proposals shall be sufficiently detailed to enable the Government to perform an accurate and complete evaluation strictly from the proposal contents. However, in the area of Past Performance the Government may use data obtained from other sources. The offeror’s proposal shall consist of four volumes, and a proof of concept (PoC) contained on a laptop computer.

Volumes I: - Solicitation, Offer and Award Documents, Section K, Representations and Certificates.

Volume II: - Technical Capability, including technical approach and Specialized Experience.

Vol III: - Past Performance, completed table and information contained in these instructions.

Vol IV: - Price/Cost. Completed table and information contained in these instructions to include pricing and deliverables for the NISS IAW SOO Increment 1.

Proposals shall not contain any classified data. The use of hyperlinks in proposals is prohibited.

Each Offeror shall indicate in their proposal the validity of proposals for at least 120 days from the closing date of solicitation, HS0021-15-R-0011.

L.4. PROPOSAL FILES.

a. Format. Microsoft (MS) Office Professional 2007 or later shall be used to create the files. All graphics shall be compatible with MS Suite 2007. All information pertaining to a particular file shall be confined to that file.

The titles for each file, along with the references are shown in table 1 below. Each file shall contain the applicable proposal information in the referenced paragraph. All proposal submissions shall be clearly indexed and logically assembled.

Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents shall be created. MS Word (.doc) files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right - 1” Gutter – 0” From Edge – Header, Footer - 0.5” Page Size, Width – 8.5” Page Size, Height – 11”

The following additional restrictions apply:

Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial or Times New Roman fonts are required. Tables and illustrations may use a reduced font size not less than 8-point and may be landscape. Single space type will be used with the exception of organization line and block charts and the Price/Cost proposal. Graphics may be submitted in black & white, half-tone or in color, in font sizes sufficient for all information to be read or reproduced without difficulty (but in no case less than 8 point Arial or Times New Roman). Foldout pages, limited to 11x17 inch page size, are permissible and will count as two pages. Page numbers, headers and footers may be within the page margins ONLY, and are not bound by the font requirements.

Company logos are prohibited with the exception of the Title Page. Pages that exceed the margin, font or total page limit will not be evaluated. Page count will NOT be based upon the numbers of pages printed but rather dictated by the number of pages in a print layout view in the application based upon the above-prescribed document setting.

Counting pages in the order they appear for viewing will make up the page count.

b. File Packaging. Proposals shall be limited to four volumes and delivered on one DVD per volume with a hard copy, bound and delivered as follows:

Table 1

PROPOSAL VOLUME VOLUME CONTENTS PAGE LIMITATION REQUIRED # OF

HARD COPIES

I Solicitation, Offer and

Award Document and Section K, Representations and Certificate

Unlimited Original +1

II Technical Capability, Technical Approach, Staffing Plan & Key Personnel, and Specialized Technical Experience

100 Original +8

III Past Performance 15 Original +3 IV Price/Cost Unlimited Original +1

Note: Cover sheets, Table of Contents, Tab Labels and Dividers are not included in the total page count.

Page Count: Those pages that exceed the page counts in Table 1 for each volume or attachment will not be evaluated. Double column pages are allowed. Proposals shall be limited in the number of pages specified in the table above. Page count will NOT be based upon the numbers of pages printed but rather dictated by the number of pages in a print layout view in the application based upon the above-prescribed document settings.

c. Content Requirements. All information shall be confined to the appropriate proposal volume. The offeror shall confine submissions to essential matters, sufficient to define the proposal and provide adequate basis for evaluation.

Offerors are responsible for including sufficient details, in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents and Summary Section.

The Summary Section shall contain a brief abstract of the file. The Government may consider any failure on the part of an offeror to comply with these instructions to be indicative of the type of conduct it can expect during contract performance. Information required for proposal evaluation that is not found in its designated volume or presentation will be assumed to have been omitted from the proposal and the proposal may be considered technically unacceptable and may not be considered for award. Therefore, offerors are encouraged to contact the Contract Specialist, Shawna Mitchell Shawna.Mitchell@dss.mil and the Contracting Officer, Keanna Houston Keanna.Houston@dss.mil, in order to request any necessary clarifications or explanations of these instructions.

Proprietary information shall be clearly marked.

d. Proposals shall include one (1) separately bound copy of Volume I, nine (9) separately bound copies of Volume II. One (1) original and three (3) copies separately bound for Volumes, III and two (2) copies of Volume IV. The proposals shall also include a Digital Versatile Discs (DVDs) submission with limited to the number it takes for you to transfer your entire proposal submission into electronic formats containing all the Volumes. The DVD(s) must be clearly labeled with the solicitation number, volume numbers, and the offeror’s name. Digital copies should be submitted as “read only” (pdf) documents or Microsoft Office Professional 2007 Suite (Excel and Word). If there are discrepancies between the electronic version (DVD) and the hard copy, the hard copy shall take precedence and shall be considered binding.

Offerors are responsible for submitting responses to the Government office designated below by the time specified in the solicitation. Offerors shall submit responses to this RFP along with the supporting documents as required by 2:00 p.m. ET, on June 4, 2015 to Keanna Houston. Any response received after the date/time specified for receipt of offers will be considered "late". It is the responsibility of the offeror to ensure that your response is received in a timely manner. The instructions for hand deliveries for PoC submissions are covered in the PoC Deliveries section.

Please ensure you allow sufficient time for delivery of your proposal. The use of a delivery service with a tracking system is strongly encouraged. Submit your response to this RFP to the following:

ATTN: Keanna Houston Defense Security Service 27130 Telegraph Road

R-K BLDG, MCBQ

Quantico, VA 22134 Email – keanna.houston@dss.mil

Technical Questions - shall be sent via email to shwan.mithcell@dss.mil and keanna.houston@dss.mil with the solicitation number reference in the subject line. All questions must be submitted no later than May 8, 2015 5:00 p.m. E.T. TELEPHONIC INQUIRIES WILL NOT BE ACCEPTED.

e. The proposal shall contain the solicitation number, narrative and other data sufficient to describe the associated element of the proposal. An offeror’s failure to furnish the necessary information may result in its proposal not being considered for award. A proposal received after the solicitation closing time and date will be considered LATE in accordance with FAR 52.215-1, Instructions to Offerors – Competitive Acquisition.

f. The Offeror’s proposal, including the Proof of Concept, will be the primary basis on which the Government will determine the capability of the offeror to perform this requirement. An Offeror’s proposal shall be specific, complete, thorough, clear, concise, and must address each element in the solicitation. The Offeror’s proposal shall be presented in separate volumes so that all information associated with each factor (Solicitation, Offer and Award document, Section K, Technical, Past Performance, and Price) is easily distinguishable. It shall not be necessary to go from volume to volume (or section to section in each volume) in order to completely evaluate each prime factor.

Information contained in a volume that belongs in another volume will not be evaluated. The Government will not evaluate information of a general nature that is not relevant to the topic being evaluated.

g. The proposal shall not merely offer to comply with the Government’s requirements by simply restating them, but shall specifically describe the means of accomplishment. The proposal in its entirety should be specific, detailed, and complete in order to demonstrate that the offeror has a thorough understanding of the solicitation requirements.

Statements such as “the offeror understands, can or will comply with the requirements”, statements that paraphrase the Statement of Objectives (SOO) or ambiguous phrases such as “standard procedures will be employed” or “well known techniques will be used” do not explain your technical solution for NISS and will be rated unacceptable.

Additionally, providing examples of past performance as a response to a task, while helpful, does not indicate an offeror’s approach to performing a task.

L.5. PROPOSAL CONTENT.

(1) VOLUME I – SOLICITATION, OFFER and AWARD DOCUMENT AND SECTION K, REPRESENTATIONS AND CERTIFICATES

Certifications and Representations - Each offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the solicitation. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. The Government will also check the contractors Representations and Certifications located in the System for Award Management (SAM) prior to award. An Acrobat PDF file shall be created to capture the signatures for submission. In order to receive an award associated with the solicitation the proposed awardee must be registered on SAM.gov in order to receive the award.

Section A – Standard Form 33 (SF 33), Solicitation, Offer and Award Section K – Representations, Certifications and Other Statements of Offerors

(2) VOLUME II – TECHNICAL CAPABILITY

Offerors shall demonstrate an understanding of the technical requirements and risk in implementing those requirements. This will include the Offeror’s plans to meet all technical requirements, and the thoroughness in which the proposal addresses each technical requirement. The Proof of Concept requirements, the proposal shall address “Technical Approach, Staffing Plan and Key Personnel, and Specialized Experience” in sufficient detail to permit evaluation in accordance with Section M. Volume II shall cover all contract years. It is imperative that you fully describe how you will meet the sub-factor requirements. Do not simply copy and paste, rephrase or restate SOO language for the technical volume. The successful offeror’s Staffing Plan will be incorporated into the contract by reference. Volume II shall discuss the following:

The overall technical requirements and proposed implementation for satisfying the technical requirements contained within the SOO and Requirements Definition Document (RDD).

Factor 1: Technical Capability:

Sub-factor 1.1: The Proof of Concept (PoC): The PoC consists of the vendor’s configured software on a laptop computer using the DSS image provided by the government as your PoC baseline. The PoC shall consist of: an oral presentation, description documents, and a slide deck with takeaways. The slide deck shall provide information highlighting your proposed solution. The PoC slide deck desired information should include screen captures of the Demo, covering the following areas: workflow screen, monitoring of case management, receipt of external user system submissions, calendar integration, search feature, notification/messaging, dashboard, and data transfer simulation specifically called out in the Use Case. The PoC description document should detail the system components of the proposed NISS solution. The description should also identify any deviations made from the image provided on the DSS image in which you should have used as your PoC baseline for our situational awareness. You will NOT be penalized for deviations but this information is required to assist us with ensuring we obtain the recommended skillsets required for sustainment of the application once it is deployed.

Please bring nine (9) copies of the PoC documents with you to your PoC demonstration. There is no page limit for your PoC documentation. The vendors shall describe the platform, software, and any additional components utilized for creating the PoC. The vendor shall highlight the reasoning behind selection of the aforementioned PoC configuration baseline. The vendors shall detail any deviations from the DSS provided baseline image. The vendors shall highlight the skillsets required for full scale development and sustainment in the event the PoC is expanded into a Production ready product. The vendor PoC must demonstrate the ability of the PoC to execute the functionality detailed within the iFCl Use Case. The PoC should clearly demonstrate abilities outlined in the Use Case including but not limited to automation of manual processes within the FCL workflow, providing ability to monitor end-to-end case management, receive, edit, and transfer documentation, Outlook calendar integration, search/content management, user friendly dashboard*, notifications, alerts, messaging, and a simulated transfer mechanism which may be used for CDS. The PoC should provide help features which guide users through functionality, including explanations for system error messages and detail the next steps, as practicable. The PoC will not be evaluated on grayed out functions for the use case provided, however these functions must be addressed in the Technical Approach Sub-factor 1.2. The PoC must: adhere to DSS technical standards, require a limited need for developer customization, provide flexibility to DSS super-users and OCIO Administration Staff for modifying items including but not limited to banners, alerts, notices, and other components subject to frequent changes. Agents should have the capability to customize items such as workflows, business processes, and system rules through drop downs or via comparable super-user administrative privileges.

The vendor shall have the opportunity to present this information in a not to exceed three (3) hour oral presentation using your company provided laptop with other proposal materials, utilizing the DSS image as the baseline. *(A user friendly dashboard is defined as having intuitive content which requires a small number of click-through for navigating within workflows, executing reporting and accessing notifications.)

Sub-factor 1.2: Technical Approach: The vendor must provide a Project Management Plan in sufficient detail to demonstrate technical competency in execution of their proposed NISS Program solution. The Project Management Plan must include the following sections:

Schedule Management Plan—Vendors shall provide a proposed Integrated Master Schedule (IMS) that expands upon the provided DSS WBS, detailing the activities and durations expected for development, implementation and deployment of the six phases referenced within the SOO (above) and the RDD. The schedule shall include NISS Increment development according to the phases in the SOO, milestones including incremental and final software delivery dates with time allocated for Requirements Validation, Integration with the on-site Government test environment, Operational Test and Evaluation (OT&E) activities, Production Readiness Reviews (PRR) and Deployment to Production.

Risk Management Plan—Vendors shall provide a proposed approach for identifying and managing Project Risk. This includes describing the firm’s approach to performing risk identification, qualitative analysis, quantitative analysis, as well as the development and implementation of risk strategies. The vendors should focus upon the optimal use of resources to meet all performance requirements.

Change Management Plan—Vendors shall detail the process for managing proposed changes to project work and scope. The vendors should include specifics regarding changes to Requirements, Functionality, Documentation and Software Code. The vendors shall detail the Requirements Management and Configuration Management tools intended for use during contract execution.

Factor 2: Staffing Plan and Key Personnel:

Sub-factor 2.1 Staffing Plan: The contractor shall provide a Corporate Structure and staffing plan that explains how the key and non-key personnel will be staffed. The plan should contain the following information: position and location; tie-back to tasks in SOO. An explanation on how this position will be filled is required; and how the prime contractor will verify the experience and education of the contractor employee for verification that the employee meets the minimum requirements specified below. The offeror should also address which labor categories shall be filled by subcontractor or its own employees. The offeror should also address plans in the event of prime and/or subcontractor candidates withdraw or additional resources are required and staffing updates, throughout the period of performance. The Staffing Plan must address:

The labor mix assigned to the functional program areas that includes position name, level (i.e.

Junior, Mid-level, or senior employee), Secret and Top Secret Sensitive Compartmented Information (TS/SCI) clearance eligible level. A table may be best to summarize this information.

Staffing Strategy: The vendors shall detail how open vacancies will be filled to meet the date in which the proposed Integrated Master Schedule (IMS) requires that skillset. The Staffing Strategy shall address the manner and the average anticipated time for fill each position including those that may require a TS and TS/SCI eligibility in the future.

Sub-Factor 2.2 Key Personnel Summary: The vendor shall provide a two page (maximum) summary or Résumé per person for key personnel including full time availability, security clearance, and SCI eligibility for each person, being proposed for the following labor categories:

Technical Project Manager (TPM): The proposed TPM shall have 10 or more years of experience managing highly complex software development projects with incremental deliveries spanning multiple years. A PMI-PMP certification and at least five (5) years of DoD experience is required.

Deputy Project Manager: The proposed Deputy Project Manager shall have five (5) or more years of experience managing highly complex software development projects with incremental deliveries spanning multiple years. A PMI-PMP certification and at least two (2) years of DoD experience is required.

Oracle Database Administrator: The proposed Oracle Database Administrator shall have at least five (5) or more years of experience with implementing data analytics initiatives that leverage a data warehouse infrastructure capability. Three (3) or more years of NoSQL administration is also required.

WebLogic/LDAP: The proposed WebLogic/LDAP shall have at least five (5) or more years of experience in enabling software applications with Common Access Card (CAC) or Public Key Infrastructure (PKI) identity management (IdM) capabilities.

Software Developer: The proposed Software Developer shall have five (5) or more years of experience in automating complex organizational Business Processes through commercial off the shelf (COTS) or customized web development initiatives.

NOTE: KEY PERSONNEL SUMMARY OR RÉSUMÉ PAGES ARE NOT INCLUDED IN THE PAGE

COUNT.

Factor 3: Specialized Technical Experience: The government anticipates requiring the following capabilities to be accomplished in future task orders issued under this contract.

Sub-factor 3.1 Cross Domain Solution (CDS) Experience: The vendor shall provide unclassified level details of successful CDS implementations. Experience within the past two (2) years should consist of near real-time, bi-directional automated transfers between NIPR, SIPR, and JWICS. Successful CDS transfers with dynamic web-based streaming or data feeds and experience with Defense Information Systems Agency (DISA) managed CDS is highly preferred.

Sub-factor 3.2 Cloud Development Experience: The vendors shall provide details of successful cloud development utilization for software development projects. The vendors shall include details of customer testing or validation cycles prior to official code delivery. Experience with development using MilCloud services is highly preferred.

Sub-factor 3.3 Integration: The vendors shall provide details of experience integrating software applications with interfaces to customer internal and external Agency systems. Experience with enabling real time data exchanges between DoD systems is highly preferred.

The Technical volume shall be organized as follows:

TAB 1: Technical Approach including:

Project Management Plan with appropriate sections (Schedule, Risk and Change Management Plans)

TAB 2: Staffing Plan and Key Personnel

TAB 3: Specialized Technical Experience

PROOF OF CONCEPT DOCUMENTS ARE NOT PART OF THE TECHNICAL VOLUME SUBMISSION,

HOWEVER, YOU ARE REQUIRED TO PROVIDE A COPY OF YOUR SLIDES AT THE PROOF OF

CONCEPT DEMONSTRATION. THE POC DOCUMENTATION IS NOT INCLUDED IN PAGE COUNT OF

THE TECHNICAL VOLUME. PLEASE SEE PROOF OF CONCEPT INSTRUCTIONS.

(3) VOLUME III – PAST PERFORMANCE.

Offerors shall provide a relevant project list for past work in Government and non-Government contracts for work similar to that required for the NISS solution in accordance with the below instructions. Data concerning the prime offeror shall be provided first, followed by each major subcontractor, in alphabetical order.

Example:

RELEVANT PROJECT SUMMARIES

OFFEROR: HS0021-15-R-0011

Contract #

Project Name

Company

Name

Performing

As Customer

Contract

Type

Completion Date

$ Value

Offeror as the Prime/Subcontractor

1 OFFEROR

2 OFFEROR

3 OFFEROR

Significant Subcontractors/Teaming Partners “Performing As” – insert “Prime”, “Sub” ( for subcontractor), “Team”, or “Partner” “Contract Type” – insert FFP, CPFF, CPAF, etc.

“Completion Date” – The date that performance was completed “$ Value”: Annual Dollar Value

Relevant Project Summaries This volume shall be organized into the following sections:

1. Section-1 – Relevant Project Summaries: Offerors shall provide a Relevant Project Summary List for past or on-going work for Government or Non-Government contracts for work similar to that required for the NISS solution. The list shall contain no more than three projects. Data concerning the prime offeror shall be provided first, followed by each major subcontractor, in alphabetical order. This information may be contained in a chart, similar to the example above: (This is the "Relevant Project Summary List table)

Offerors shall submit information on projects deemed relevant in demonstrating the ability to perform the proposed effort and explain how/why the referenced projects are relevant to the proposed effort. “Relevant” projects are defined as those contracts ongoing or completed (within the last three years) that are of comparable magnitude and complexity to those described in the SOO. For each contract referenced, the offeror shall provide a separate Relevant Project Summary, not to exceed five (5) pages per example with a maximum of three (3) examples total.

This section shall include the following information in the following format:

a. Contractor/Subcontractor place of performance, CAGE Code, and DUNS Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers.

b. Government contracting activity and current address Procuring Contracting Officer’s name, email address, and telephone and fax numbers.

c. Government’s technical capability representative (COR) and current e-mail address, telephone, and fax numbers.

d. Government contract administration activity and the Administrative Contracting Officer’s name, current e-mail address, telephone, and fax numbers.

e. Contract number and in the case of Indefinite Delivery Indefinite Quantity (IDIQ) type contracts, GSA contracts, and Blanket Purchase Agreements, include Delivery Order numbers.

f. Contract Type (specific type such as Fixed Price, Cost Reimbursement, Time & Material, etc. In the case of IDIQ contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and the secondary contract type (FP, CR, T&M, etc.).

g. Awarded price/cost

h. Final or projected final price/cost

i. Original delivery schedule, including dates of start and completion of work.

j. Final or projected final, delivery schedule, including dates of start and completion work.

Note PPQs do not count in the total page count for Volume III.

2. Section-2 – Past Performance: Offerors shall provide a specific narrative explanation of each contract/experience listed in Section-1 describing the objectives achieved and detailing how the effort is relevant to the requirements of this solicitation.

For any contracts that did not/do not meet original schedule or technical capability performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offeror shall list each time the delivery schedule was revised and provide an explanation as to why the revision was necessary. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The Offeror shall also provide a copy of any Cure Notices or Show Cause Letters received on each contract listed and a description of any correction action implemented by the Offeror or proposed subcontractor. The Offeror shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

3. Section-3 – New Corporate Entities: New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

4. Section-4 –Past Performance Assessment Questionnaire: The Past Performance Questionnaire (PPQ) included in Section J of the solicitation is provided for the offeror or its team members to submit to their client(s) for each project the offeror includes in its proposal for Past Performance/Experience. Ensure correct phone numbers and email addresses are provided for the client point of contact. Completed Past Performance Questionnaires should be E-Mailed directly from the client (POC/COR) to Ms. Shawna Mitchell, shawna.mitchell@dss.mil and Ms.

Keanna Houston, keanna.houston@dss.mil on or prior to 15 May 2015. PPQs are exempt from the Past Performance Volume page count limitation. The Government is not precluded from utilizing previously submitted PPQ information in the past performance evaluation. Also include in this section the following information:

performance recognition documents received within the last three (3) years such as awards, award fee determinations, customer letters of commendation, and any other forms of performance recognition.

In addition to the above, the Government may review any other sources of information for evaluating past performance. Other sources may include, but are not limited to, past performance information retrieved through the Past Performance Information Retrieval System (PPIRS), including Contractor Performance Assessment Reporting System (CPARS), using all CAGE/DUNS numbers of team members (partnership, joint venture, teaming arrangement, or parent company/subsidiary/affiliate) identified in the offeror’s proposal, inquiries of owner representative(s), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), and any other known sources not provided by the offeror.

While the Government may elect to consider data from other sources, the burden of providing detailed, current, accurate and complete past performance information rests with the Offeror.

(4). VOLUME IV – COST/PRICE.

The offeror shall provide estimated cost and proposed fixed fee information for each item listed in the Schedule (Section B), both for the basic contract and Task Order 0001. The breakdown of costs shall provide sufficient detail for the Government to identify the work effort and resources proposed to accomplish the work for each CLIN and evaluate the proposed for realism and reasonableness. The cost proposal shall include: Name, telephone number, and e-mail address of the point of contact at the offeror’s facility, and name, title and signature of authorized representative. Failure to provide detailed pricing may be grounds for finding a proposal nonresponsive and not eligible for award. A cost breakdown to include percentages for the indirect rates (G&A, Overhead (OH), Material/Subcontract OH, Fringe, etc.) and profit must be provided in the narrative portion of volume IV. While Cost/Price will not be given an adjectival rating, it will be evaluated for cost realism and price reasonableness.

Additionally, a determination will be made if there is any significant performance risk to the Government because of unrealistically low or high costs/prices. Cost/Price information included in any volume other than the Price Volume will not be evaluated.

Cost Proposal Volume, Proposal shall be in Microsoft EXCEL format and include all arithmetic formulas and shall provide detail for each of the five ordering periods.

a. ALL proposed labor categories (include a full definition of each category) intended for program level support

b. Unburdened direct labor and overhead rates for each labor category by each ordering period (include escalation factor for any and all ordering periods, if proposed)

c. Other Direct Costs. List all other direct costs other than direct labor dollars such as but not limited to subcontractor’s costs, material, travel equipment, consultant, etc.

d. ALL proposed indirect rates and the base to which they are applied

e. Basis of Estimate (BOE) for software to include license structure (i.e. perpetual, subscription, enterprise)

f. Profit/fee

Labor Cat 1 Unburdened Labor Rate Escalation Factor OH Labor % Base Labor Cat 2 Unburdened Labor Rate Escalation Factor OH Labor % Base Labor Cat 3 Unburdened Labor Rate Escalation Factor OH Labor % Base Profit/Fee % (Will be applied to total labor dollars only)

The successful offeror’s proposed direct and indirect rates shall be used for all subsequent Task Orders throughout the five-year ordering period that are issued against the Basic IDIQ.

Subcontracts: Offerors shall provide an outline of how the effort required by the solicitation will be assigned for performance within the Offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime Offeror and each proposed major subcontractor must include the entire company name, company address, CAGE code, DUNS Number and type of work to be performed by citing the applicable Government SOW subparagraph number. This includes all subcontractors who will be providing critical services or whose subcontract is for more than 15% of the total proposed price.

For the Initial Task Order 0001, the Offeror shall include in its Cost/Price Volume the following:

The labor categories, the labor rates, and skill mix proposed that will reflect the work to be and any other costs (by cost element) proposed at the same level of detail as shown in the Table below.

Cost Element Summary: Disclose all elements of cost and/or price applicable to the proposed effort for Initial Task Order 0001. All elements of cost and/or price shall include supporting rationale as allocable and allowable to the task order.

i. Direct Labor Costs:

Information including the name, title, and the raw hourly direct labor rate shall be provided by the offeror for each labor category proposed. If the offeror proposes direct labor rates based on a composite rate structure, then the offeror shall clearly identify the individuals comprising the composite, their respective fixed hourly rates, and method used to derive the composite rate.

Offeror’s proposed labor categories should be clearly identified along with a brief position description

Offerors are reminded that the staff proposed in the technical proposal must be the same staff proposed in the cost proposal.

ii. Indirect Rates: Offerors shall list the cost elements that comprise the fringe, overhead, general and administrative expenses, and the other indirect cost pools as applicable. All indirect rates shall be summarized. If proposed rates reflect negotiated forward pricing rates, a copy of the current forward pricing rate agreement (FPRA) shall be provided. If the rates are not negotiated forward pricing rates, then the basis of proposed indirect rates shall be explained.

iii. Travel: As task orders are issued for services, the travel requirements shall be identified by the

Government and the offeror shall propose travel costs along with the methodology utilized in determining how travel costs were proposed in order to demonstrate cost and price reasonableness.

iv. Other Direct Costs: The offeror shall propose ODCs that are reasonable and consistent with the technical approach and are necessary to meet the requirement. Offeror shall include the basis of estimate and documentation with the other than cost or pricing data to support the proposed costs. Offerors shall identify any indirect rates that will be applied to the ODCs and include the indirect expenses in the total ODC amount as outlined in the table below.

v. Subcontracting: If the offeror proposes to use subcontractors, such as (but not limited to) subcontractors, vendors, consultants, each of them shall be addressed separately, and detailed information shall be provided in the same format as required for the prime contractor, including cost information. Proprietary cost information may be provided separately to the Government if the subcontractors, vendors, consultants, etc.

will not provide this data to the prime offeror. Each shall submit such cost information directly to the Government by mailing it directly to Ms. Shawna Mitchell, shawn.mitchell@dss.mil and Ms. Keanna Houston, keanna.houston@dss.mil. Regardless, Offerors must ensure that subcontractors adhere to the guidance set forth herein. FAR 15.404-3, Subcontract pricing considerations, requires that an offeror provide an analysis of subcontractors’ cost proposals. To that end, the offeror’s proposal must:

Identify principal items/services to be subcontracted

Identify prospective subcontractors and the basis on which they were selected. In non-competitive, provide selected source justification.

Identify the type of contractual arrangement contemplated for the subcontract and provide a rationale for same

Identify the basis for the subcontract costs as included in the offeror’s proposal (e.g., firm quote or estimate, etc.)

vi. Fee and/or Profit: Identify the fee or profit rate and the total amount proposed, to include technical, management and performance risk factors utilized in deriving the fixed fee or profit proposed.

**Note: Only total labor dollars are fee and/or profit bearing. All offerors shall provide their rationale for the fixed fee and/or profit proposed.

vii. Provide the assigned DCAA Branch office for the offeror and all subcontractors, to include the following information: name, phone number and e-mail address of the DCAA point of contact. The contractor is required to provide an explanation if any known discrepancies exist between the offeror’s proposed costs and DCAA or DCMA recommendations.

Table – EXAMPLE

Labor Category 2 $ 15.00 50 750$ Total Direct Labor (DL) Dollars 100 1,250$

Indirect Labor Factors BASE %

Include all indirect labor factors to be proposed and identify the base to which it is applied along with the factor value expressed in a percentage carried out to the second significant factor Fringe (applied to total Direct Labor Dollars) See Note 1 below 30% 375$ Overhead (applied to Direct Labor plus Fringe) See Note 2 below 40% 650$ Total Fringe and Overhead (OH) 1,025$ Total DL Dollars plus Fringe and OH 2,275$

Other Direct Costs:

Material/Subcontractor 500$ Equipment 100$ Other miscellaneous direct costs 50$ Travel 75$ Total ODC's 725$

Indirect Factors Base %

Include all indirect factors for ODC's to be proposed and identify the base to which it is applied along with the factor value expressed in a percentage carried out to the second significant factor

Material and Subcontractor Handling Rate See Note 3 3% 15$ Total Mat/Subk Handling 15$ Subtotal Costs 3,015$

Other indirect factors Base %

Include any other indirect factors to be proposed and identify the base to which it is applied along with the factor value expressed in a percentage carried out to the second significant factor

G&A (Value-Added Base) See Note 4 25% 628.75$ Subtotal Cost 3,644$

Facilities Capital Cost of Money Estimated Cost 0.0001 0.36$ Total Estimated Costs 3,644$ Fixed Fee Base % Include the proposed fixed fee and the base to which it is applied along with the factor value expressed in a percentage carried out to the second significant factor

Total Labor Dollars;

See Note 5 4% 50$

TOTAL 3,694$

Notes:

1. Total labor dollars (direct and indirect labor dollars).

2. Total direct labor dollars, Bid & Proposal (B&P) direct labor dollars, plus fringe applied to direct labor dollars and B&P direct labor dollars.

3. Total direct material and subcontract costs.

4. Value-added cost input base is total cost input less material and subcontract costs.

5. Only total labor dollars are fee and/or profit bearing. All offerors shall provide their rationale for the fixed fee and/or profit proposed.

If a Forward Pricing Rate Agreement (FPRA) or a recent (within the last 12 months from the date this solicitation is issued) audit report exists (for the prime or proposed subcontractor(s), copies should be submitted by the offeror.

This information may be used by the Government for purposes of a cost realism analysis.

The offeror shall provide cognizant DCMA (if applicable) and DCAA point of contact information, (name, telephone number and email address).

All proposed third party entities are required to provide supporting cost information at the same detail as the offeror.

Each third party cost submittal shall be clearly label “COST INFORMATION –COMPANY NAME” to facilitate easy identification and transmittal to DCAA personnel.

Complete Section B of the RFP. CPFF elements must be separately and clearly priced.

To assist the Government in determining cost reasonableness/realism for this effort, the offeror shall provide sufficient detailed cost information and supporting documentation with the proposal to make this determination.

Additional supporting information must be provided as required by the complexity of the offer. Offerors and their subcontractors are required to submit a cost and/or price proposal as instructed in Section L above, FAR clause 52.215-20(b), Requirements for Cost or Pricing or Information Other Than Cost or Pricing Data (OCT 2010).

Financial Statements: Offerors shall provide copies of both the offeror’s balance sheet and income statement.

These sheets shall be from the offeror’s most recent complete business.

L.6 Offerors are cautioned that it is the Government’s intent to make award selection without discussions.

Thus, it is incumbent upon each offeror to submit its best proposal upon initial submission. In the event discussions are conducted; a competitive range will be established in accordance with FAR 15.306(c) (1), and discussions will be held in accordance with FAR 15.306(d).

L.7 The offeror will be required to submit two separate boxes for proposal submission. One box shall contain nine

(9) copies of your hard copy technical proposal, two (2) copies of your cost proposal, and four (4) copies of your past performance. The second box shall contain a laptop loaded with your proof of concept submission along with the USB drive supplied by the Defense Security Service if you are not submitting your PoC in person. Please ensure the box containing your laptop is properly secured with sufficient tape. Your laptop will be stored in a secured location designated by the DSS Office of Acquisition until the day of your PoC demonstration. You will receive your unopened box back on the day of your PoC presentation in order for you to present your proposed solution.

After you present your proposed solution your laptop will be returned to the Office of Acquisition representative who will submit your laptop for testing to ensure compliance with the baseline requirements.

SECTION M - EVALUATION FACTORS FOR AWARD

The following have been modified:

EVALUATION FACTORS

M.1 INTRODUCTION

This section states the government’s basis for evaluation of the offerors’ proposals submitted in response to the solicitation. A formal source selection process will be conducted in accordance with FAR 15.3, Source Selection, and FAR 15.101, Best Value Continuum, for the National Industrial Security System (NISS). The Government reserves the right to make an award to other than the lowest priced offeror or other than the highest technically rated offeror by employing the Tradeoff Process in accordance with FAR Part 15.101-1.

M.2 BASIS FOR AWARD

The Government may award a single award contract resulting from this solicitation to the responsible offeror whose proposal best meets the needs of the government and whose proposed solution represents the best value after evaluation in accordance with FAR 52.215-1 and the following factors and subfactors.. The five (5) evaluation factors are: 1) Technical Capability, 2) Staffing Plan/ Key Personnel, 3) Specialized Technical Experience, 4) Past Performance, and 5) Price/Cost. Factors one through three consist of the Technical Approach for this requirement.

The Technical Capability factor consists of two sub-factors: (1.1) Proof of Concept (PoC) and (1.2) Technical Approach. The Specialized Technical Experience factor consists of three sub-factors: (3.1) Cross Domain Solution, (3.2) Cloud Development, and (3.3) Integration. To receive consideration for the award, the offeror must achieve an “Acceptable” rating (in accordance with the DOD Source Selection Manual Technical ratings as identified in Table 1) or better for the elements which comprise the Technical Solution. Within the best value continuum, the Government will employ a tradeoff analysis of cost / price and non-cost/price factors in evaluating the proposals submitted. The offeror’s initial proposal shall contain the offeror’s best terms from a cost/price and technical standpoint. The Government may award a contract resulting from this solicitation to the offeror whose offer, conforms to the solicitation requirements, such as terms and conditions is determined to provide the “best value” to the Government for the overall combined NISS solution (the Basic IDIQ) and the NISS development Increment One (Task Order 0001).

Proposals will be assessed for how well the offeror’s proposal meets the solicitation requirements. Risks associated with the offeror’s proposed solution may also be considered in accordance with the DOD Source Selection Manual Technical Risk ratings as identified in Table one (1). Proposals will also be assessed for the strengths, weaknesses, and deficiencies contained in each offer.

Proposals will be evaluated based solely on the factors contained in this solicitation. While the Government reserves the right to make an award without discussions,…