Attch_0029_ACWS_Section_LM_4_4_2016.pdf

Sections L & M Version 2.0 22 March 2016

Attachment 0029 Sections L and M

Army Contract Writing System Solicitation Number: W52P1J-16-R-0058

Army Contracting Command – Rock

Island (ACC-RI) Information Technology Division Attn: Mr. Jonathan J. Anderson, Contracting Officer Rock Island Arsenal

3055 Rodman Avenue Rock Island, IL 61299-8000

22 March 2016

ACWS Attachment 0029 - L&M i

This page intentionally left blank ii

Revision History

Version Date Summary of Changes

Version 2.0 22 March 2016 Final Section L&M to be released with RFP iii

Table of Contents

SECTION L – INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

L.1 ADMINISTRATIVE INSTRUCTIONS

L.2 PROPOSAL STRUCTURE INSTRUCTIONS

L.3 PROPOSAL FORMAT

L.4 INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT

L.4.2 Volume I: Factor 1 - Technical/Risk

L.4.2.1 Subfactor 1 - Technical Capabilities

L.4.2.2 Subfactor 2 - Management Capabilities

L.4.3 Volume II: Factor 2 - Past Performance

L.4.5 Volume IV: Factor 4 - Small Business Participation

L.4.6 Volume V: Contract Documentation

SECTION M – EVALUATION FACTORS FOR AWARD

M.1 GENERAL

M.2 FACTORS TO BE EVALUATED

M.3 EVALUATION APPROACH

M.3.2 Factor 1 – Technical/Risk

M.3.2.1 Sub Factor 1 - Technical Capabilities

M.3.2.2 Sub Factor 2 - Management Capabilities

M.3.3 Factor 2 Past Performance

M.3.4 Factor 3 – Cost/Price

M.3.5 Factor 4 – Small Business Participation

M.4 DEFINITIONS

M.5 Volume V – Contract Documentation

*** END OF SECTION M NARRATIVE ***

Section L & M

SECTION L – INSTRUCTIONS, CONDITIONS AND NOTICES TO

OFFERORS

L.1 ADMINISTRATIVE INSTRUCTIONS

L.1.1 Proposal Submission Dates: Each Offeror shall submit one (1) electronic proposal for all Volumes I – V including attachments, plus separately, one (1) paper-version of Volume III, Cost/Price. If the Offeror wishes to be considered for the additional source selection decision, the Price Volume, paper-version and electronic proposal, must include Attachments 0020 and 0021. All such proposals shall address the Government requirements outlined in the Request for Proposal (RFP). Offerors shall submit the proposals, with a cover letter in accordance with the date and time referenced in block 9 of the SF 33. The Offeror bears responsibility for submitting its offer by the specified date/time.

All offerors must allow their proposals to be valid for at least 365 days. To be considered for the additional selection, an Offeror must record 730 calendar days in block 12 of the SF33 (365 days for Source Selection plus 365 for the period of performance of TO 0001). The Government will consider Attachment 0020 valid until the date of award of the ID/IQ. The non-price volumes and Attachment 0021 will be considered valid 365 days from the date of award of the ID/IQ.

However, only the proposal chosen in the additional source selection decision will be asked to extend its proposal validity date for the additional 365 days.

If it is determined that the contractor selected for award of the ID/IQ contract is not successfully performing, the Government intends to offer a contract to the contractor selected in this additional decision.

The Government will announce the selection of the additional proposal at the time of the ID/IQ award.

Any offeror who does not submit Attachment 0021 will not be considered in the additional source selection decision. If an offeror decides to maintain the same prices submitted on Attachment 0020, the offeror is still required to provide Attachment 0021 reflecting the same prices as in Attachment 0020.

L.1.2 Submission of Proposals. Electronic submissions of proposal files will take place via the AMRDEC Safe Access File Exchange (SAFE). Access to SAFE is available through the website at: https://safe.amrdec.army.mil/safe/Welcome.aspx

SAFE supports file sizes up to 2 gigabytes for uploading.

Upload all proposal files using the following naming convention:

https://safe.amrdec.army.mil/safe/Welcome.aspx

VendorName_Vol_#_RFP_W52P1J-16-R-0058.

Once at the AMRDEC site, manually enter the email address john.p.hemmen.civ@mail.mil to submit proposal files to Contracting Specialist, John Hemmen.

Paper submission of proposal Volume III Cost/Price, and only Volume III, shall be mailed to:

Army Contracting Command – Rock Island (ACC-RI) Information Technology Division Attn: Mr. Jonathan J. Anderson, Contracting Officer Rock Island Arsenal 3055 Rodman Avenue Rock Island, IL 61299-8000

Paper submission of Volume III, Cost/Price, must be sent via registered post or carrier and must be accepted in writing at Rock Island Arsenal prior to the established deadline.

L.1.2.1 Period for Acceptance of Offers. The Offeror agrees to hold firm the prices in its offer for 180 calendar days from the date specified for receipt of offers. The Offeror shall make a clear statement in SF 33, Section A on page one (1), block 12 of the RFP that the proposal is valid for 180 calendar days. This documentation shall be submitted in Volume V.

L.1.2.2 Late Submission. Late proposal submissions will be handled IAW 52.215- 1(c)(3).

L.1.2.3 Official Transmissions

L.1.2.3.1 Amendments will be issued via FedBizOpps.

L.1.2.3.2 Point of Contact. Procuring Contracting Officer (PCO) and Contract Specialist (CS) are the SOLE points of contact for this procurement. Submit, in writing, any questions or concerns you may have to the PCO and CS. All requests for clarification must be sent, in writing, to both:

PCO

Jonathan J. Anderson jonathan.j.anderson16.civ@mail.mil

AND

CS

John Hemmen john.p.hemmen.civ@mail.mil

L.1.2.3.3 Questions/Comments. Any questions and/or comments submitted regarding this solicitation shall be submitted in writing and shall refer to specific text of the solicitation in the following format:

E-mail Subject: Solicitation No. W52P1J-16-R-0058.

MS Excel (compatible with MS Excel 2013) file attachment naming convention:

VendorName_Q_RFP_W52P1J-16-R-0058.xls.

Format the file with all Questions/Comments and Rationale with Vendor Name and these column headings at the top of each page:

Vendor Company Name:

Vendor POC Name, E-mail, Phone #

RFP

Section

Vol # Attch # Page # Para # Question/Comment Rationale

L.1.2.3.4 Questions/Comments and Answers. 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 be submitted by each Offeror instead of submitting multiple sets of questions. All questions concerning the RFP should be submitted to the PCO and CS no later than 4:00 P.M.

Central Time, 14 calendar days from the initial release of the RFP (posting date to

FBO).

L.1.2.4 During the conduct of this acquisition, the Acquisition Source Selection Interactive Support Tool (ASSIST) will be used by the Government to support the proposal evaluation and source selection process. A separate tool, the ASSIST2Industry, will be used in conjunction with ASSIST to accomplish all exchanges with Offerors after receipt of proposals. ASSIST2Industry provides the ability for the Government to issue, and the Offerors to receive and respond to, all Evaluation Notices (ENs) in a secure online environment.

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

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

All Offerors are advised that ASSIST2Industry has been updated and it is now the responsibility of PRIME Contractors to establish accounts for their SUBCONTRACTORS to respond to Government ENs. A separate area within ASSIST2Industry has been created to allow authorized Subcontractor POCs to upload proposal EN response files only. Subcontractors will not be able to access any other information on the ASSIST2Industry website (e.g., Questions/Evaluation Notices, Responses, etc.). Once a Subcontractor has been added, they will receive a user ID (e.g., subcontractor0001) and password (an initial password) that will be sent via two separate system generated e-mails. A Subcontractor will have one user ID for all PRIMES and solicitation responses (i.e., if you are a Subcontractor to multiple Prime Contractors and multiple solicitation responses, you will only have one user ID). Once an account has been established for the Subcontractor, go to https://ASSIST2Industry.army.mil to access the account. Prime Contractors will only be able to see the number of files submitted by their Subcontractors; but, will be UNABLE TO VIEW the Subcontractor’s files.

NOTE: Both Prime Contractors and Subcontractors are instructed to review the ASSIST2Industry User’s Guide, located under the “Getting Started” tab on the website.

The guide has been updated and provides step by step instructions on how to perform functions and navigate the website.

Offerors can contact the ASSIST2Industry Helpdesk at usarmy.jbmdl.acc.list.vce-helpdesk@mail.mil; (609) 562-5988; or (609) 562-7050 for any technical assistance that may be needed (Monday – Friday; 9:00 AM – 5:00 PM EST).

OFFERORS ARE CAUTIONED THAT THE SYSTEM GENERATED EMAILS

REFERRED TO ABOVE ARE INTENDED FOR ADMINISTRATIVE PURPOSES ONLY.

RECEIPT OF THESE EMAILS DOES NOT CONSTITUTE THE COMMENCEMENT OF

ANY TYPE OF EXCHANGE WITH THE OFFEROR IN ACCORDANCE WITH FAR

15.306(A), (B), OR (D) (I.E., CLARIFICATIONS, COMMUNICATIONS, OR

DISCUSSIONS). ALSO, RECEIPT OF THESE EMAILS DOES NOT SIGNIFY THAT A

COMPETITIVE RANGE DETERMINATION IN ACCORDANCE WITH FAR 15.306(C)

HAS BEEN MADE OR THAT THE OFFEROR’S PROPOSAL WILL BE INCLUDED IN

THE COMPETITIVE RANGE WHEN THAT DETERMINATION IS MADE.

L.1.2.5 Notification of use of non-Government advisors https://assist2industry.army.mil/ https://assist2industry.army.mil/ mailto:usarmy.jbmdl.acc.list.vce-helpdesk@mail.mil mailto:usarmy.jbmdl.acc.list.vce-helpdesk@mail.mil

Offerors are advised that some contractors may participate as non-Government advisors in the evaluation of proposals.

Offerors must submit any required documentation IAW RFP Section H narrative paragraph 3 through 10.

L.2 PROPOSAL STRUCTURE INSTRUCTIONS

L.2.1 This section of the information to Offerors provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. To be considered for award, the Offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated.

L.2.2 The Government reserves the right to reject any proposal that does not comply with proposal preparation instructions.

L.2.3 The proposal shall be clear, concise and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government requirements, but shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will, with the exception of past performance, base its evaluation on the information presented in the Offeror's proposal.

L.3 PROPOSAL FORMAT

L.3.1 Proposal Organization

The Offeror shall prepare the proposal as set forth below.

Gate Criteria:

Attachment 0027 ACWS Offeror Self Certification

Return with Filenames:

VendorName_Attch_0027_W52P1J-16-R- 0058.xlsx Format as provided. Comment field limited to 500 characters (spaces included), No page limit.

Attachment 0028 ACWS Offeror Software Solution

Return with Filenames:

VendorName_Attch_0028_W52P1J-16-R- 0058.xlsx

Format as provided. Comment field limited to 500 characters (spaces included), 15 page limit.

Volume I, Technical/Risk:

Filename:

VendorName_Vol_1_RFP_W52P1J-16-R- 0058.pdf Page limit by section.

Overall Page Limit for Entire Technical/Risk Volume

Overall 50 pages, divided as noted by Subfactor 1 & 2

Cover, Table of Contents and Glossary/Acronym List

No page limit. Not included in 50 page count.

Subfactor 1 Technical Capabilities: Limit of 35 pages.

Subfactor 2 Management Capabilities: Limit of 15 pages.

Performance Work Statements:

VendorName_PWS_#_RFP_W52P1J-16- R-0058.pdf Overall 200 Pages.

1) ID/IQ PWS: Included in 200 pages, allocation at Offeror’s discretion.

Filename:

VendorName_PWS_IDIQ_RFP_W52P1J- 16-R-0058.pdf

2) TO 0001 PWS: Included in 200 pages, allocation at Offeror’s discretion.

Filename:

VendorName_PWS_TO- 0001_RFP_W52P1J-16-R-0058.pdf

Volume I, Attachments:

1) Integrated Master Schedule

VendorName_IMS_RFP_W52P1J-16-R- 0058.mpp

(Level 3 tasks) Compatible with MS Project 2013, No page limit.

2) Systems Evolution Description, System View (SV)-8

Filename:

VendorName_SV-8_RFP_W52P1J-16-R- 0058.pdf View graphical chart not included in Vol I page count. Limit of 1 page (1 sheet 11”x17”). Consistent with the DoD Architecture Framework (DoDAF)

3) Attachment 0015 Staff Levels and Skill Matrix Schedule

Return with Filename:

VendorName_Attch_0015_W52P1J-16-R- 0058.xlsx Format as Provided. No page limit.

Volume II, Past Performance:

VendorName_Vol_II_RFP_W52P1J-16-R- 0058.pdf

Page limit by section.

Cover and Front Matter to include Offeror’s Company Name, CAGE Code, and DUNs, Table of Contents and Glossary/Acronym List:

Not included in page limit.

Summary of the Offeror’s role and (if any) list of the Subcontractor(s) Corp Names, CAGE code(s) and DUNs.

Limit 2 pages.

Letters of Consent: Limit: 1 page for each subcontractor, teaming partner, and/or joint venture (JV) partner.

Contract Reference Description(s): Relevancy of each reference to the ACWS RFP limited to 500 words or less.

Adverse Contract Performance: No page limitation.

Attachment 18 Past Performance Questionnaire(s):

Return with Filename:

VendorName_Attch_0018_RFP_W52P1J- 16-R-0058.pdf

Format as provided. No page limit. Copies of the completed Sections IIA and IIB only.

Volume III, Cost/Price:

Filename(s):

VendorName_Vol_III_RFP_W52P1J-16- R-0058.xlsx

No page limit.

Cover, Table of Contents and Glossary/Acronym List:

No page limit. NOTE: Cost/Price must be submitted as electronically AND in hard copy.

ACWS Attachment 0020 and 0021 Pricing Matrix:

Return with Filename:

VendorName_Attch_0020_RFP_W52P1J- 16-R-0058.xlsx with supporting Excel files including working formulas.

VendorName_Attch_0021_RFP_W52P1J- 16-R-0058.xlsx with supporting Excel files including working formulas

Format as provided. No limit to supporting Excel files.

ACWS Attachment 0025 Cost and Software Data Reporting Plan:

Return with Filename:

VendorName_Attch_0025_RFP_W52P1J- 16-R-0058.pdf. No page limit.

Format as provided. No page limit.

Volume IV, Small Business Participation:

Filename(s):

VendorName_Vol_IV_RFP_W52P1J-16- R-0058.pdf

10 Page Limit.

Cover, Table of Contents and Glossary/Acronym List:

Not included in page limit.

Small Business Participation Proposal: 10 page limit

Attachment 0017 Small Business Participation Matrix:

Return with Filename:

VendorName_Attch_0017_W52P1J-16-R- 0058.xlsx

Format as provided. No page limit

Small Business Certification: Not included in page limit.

Volume V, Contract Documentation:

Filename(s):

VendorName_Vol_V_RFP_W52P1J-16- R-0058.pdf

Page limit by section.

Cover, Table of Contents and Glossary/Acronym List:

Not included in page limit.

Attachment 0024 - Software License Disclosure:

Return with Filename:

VendorName_Attch_0024_W52P1J-16-R- 0058.xlxs.

VendorName_Attch_0024_W52P1J-16-R- 0058.docx.

Format as provided. No page limit

Company information specific to the resultant contract:

No page limit.

RFP Compliance Cross Reference Matrix:

Return with Filename:

VendorName_Compliance_W52P1J-16- R-0058.xlxs Vendor format, No page limit. Not evaluated.

ACWS Attachment 0013 DISA_SRF: Return with Filename:

VendorName_Attch_0013_W52P1J-16-R- 0058.docx Format as provided. No page limit. Not evaluated.

L.3.2 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read and will not be considered in the evaluation of the proposal. Page limitations may also be established for responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

L.3.3 Page Size and Format

L.3.3.1 Page

A page is defined as each face of an 8.5 x 11 inches sheet of paper containing information.

Each volume shall be clearly identified and the text shall begin at the top of each page.

All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and RFP number in the header and/or footer. A Table of Contents shall be created using the Table of Contents feature in Microsoft Word. The cover page and table of contents are excluded from the page limitations.

Microsoft Word (.doc or .docx file extensions) files shall use the following page set-up parameters:

Margins (Top, Bottom, Left, Right) = 1.0 inch Gutter = 0 inches From Edge Header, Footer = 0.5 inches Page Size, Width = 8.5 inches Page Size, Height = 11 inches Paragraphs = Separated by at least one blank line

Microsoft Excel (.xls or .xlsx file extensions) files shall use the following page set-up parameters:

Margins (Top, Bottom, Left, Right) = 1.0 inch Gutter = 0 inches From Edge Header, Footer = 0.5 inches Page Size, Width (Maximum) = 11 inches Page Size, Height (Maximum) = 14 inches

When both sides of a sheet display printed material, it shall be counted as two pages.

Pages shall be single spaced. Except for the reproduced sections of the RFP document, the font type shall be Arial and text size shall be no less than 12 point.

Tracking, kerning and leading values shall not be changed from the default values of the word processing or page layout software. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. For electronic submissions, page limitations shall be calculated as though the document were printed as a hard copy proposal.

L.3.3.2 Tables, Charts, Graphs, and Figures. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and count as two (2) pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 point font size. For electronic submissions, page limitations shall be calculated as though the document were printed as a hard copy proposal.

L.3.3.3 Each volume shall contain a Glossary/Acronym List of all abbreviations/acronyms used and a definition for each within that volume. Glossaries of abbreviations and acronyms do not count against the page limitations for their respective volumes.

L.3.3.4 Each volume shall be written on a stand-alone basis so that its contents may be evaluated with no cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Within a proposal volume, cross-referencing is permitted where its use would conserve space without impairing clarity.

L.3.3.5 Cost or pricing information of any kind shall NOT be included in any volume except Volume III, Cost/Price Proposal.

L.3.4 Number of Copies and Format. The Proposal shall be submitted in electronic (searchable) format to the Point of Contact identified in Section L.1.2. Self-extracting .exe files, hyperlinks, and ZIP files are not acceptable. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office or searchable Adobe Acrobat (.pdf). Use separate files to permit rapid location of all portions, including factors, exhibits, annexes, and Attachments, if any.

L.4 INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT

Offerors shall submit a full proposal, all volumes and attachments, by the date and time specified.

L.4.1 Gate Criteria Submission

The Offeror will submit information in Attachments 0027 and 0028 in compliance with stated instructions within each work sheet and the Gate Criteria.

Offeror Self Certification (Attachment 0027) – The Offeror shall follow the instructions within the attachment to provide verification of an ability to meet ALL of the 1,545 requirements in the Requirements Traceability Matrix (Level 5) with one of the methodologies defined in the attachment (i.e., Out of the Box (OOTB), Configuration, Extension, Plug-In/3rd party, Customization, or Not Met) as defined in the Statement of Objectives (SOO) Terms of Reference.

Offeror Software Solution (Attachment 0028) – The Offeror shall follow the instructions within the attachment to list ALL of the proposed software application(s), or product(s), for the ACWS Solution to include the Commercial Off The Shelf Contract Writing Solution (COTS-CWS) whose core competency (OOTB) is to generate and issue Federal Acquisition Regulation-based (FAR-based) contracting actions (awards, orders, or modifications).

L.4.2 Volume I: Factor 1 - Technical/Risk

This Volume shall describe the Offeror’s proposed technical and management solution and approach for meeting the performance and capability requirements specified in the RFP. Responses will be evaluated as defined in Section M, Evaluation Factors for Award. Do not merely reiterate the objectives or reformulate the requirements specified in the RFP. This Volume shall not include price information, classified information, or "For Official Use Only" information.

For all proposal content, the ACWS program terms of reference as defined in the SOO, paragraph 2.2 shall be strictly followed.

Volume I shall contain the following information:

Factor 1 – Technical/Risk introductory overview shall state any assumptions associated with the proposed Technical/Risk Factor.

The Offeror’s Technical/Risk proposal, as well as its Offeror Self Certification (Attachment 0027), Offeror Software Solution (Attachment 0028), Integrated Master Schedule, System View – 8 (SV-8) and proposed PWSs, must address the Government-provided OV-2_SV-1-Views (Attachment 0008) and the ACWS Interface Development Strategy (Attachment 0010). In addition, it must be consistent with the Terms of Reference provided in the SOO and the Requirements Traceability Matrix (Attachment 0005). The Government will perform a cross-reference to confirm.

L.4.2.1 Subfactor 1 - Technical Capabilities

L.4.2.1.1 Technical Solution

The Offeror shall provide a description of the proposed software and associated enabling technologies as follows:

a. Describe how the proposed software and associated enabling technologies comply with the functional and technical requirements statements provided as Offeror Self Certification (Attachment 0027) and Offeror Software Solution (Attachment 0028) to the RFP.

b. Describe the rationale of the methodology planned to meet the requirements (i.e., OOTB, Configuration, Extension, Plug-In/3rd party, Customization or Not Met) and the rationale for the timing associated with those efforts.

c. Describe the proposed solution’s current capability to meet the High Level Objectives and the Business Outcomes to include the threshold and objective measures.

d. Describe the proposed solution’s current capability to meet the Key Performance Parameters (KPP) defined in the SOO (Attachment 0001).

L.4.2.1.2- Technical Approach: The Offeror shall provide a description of the proposed technical approach and associated enabling technologies as follows:

a. Describe the technical approach to achieving the objectives stated in the SOO. Specifically, describe the technical capability to develop, integrate, and test the COTS-CWS solution to meet the High Level Objectives and the Business Outcomes, including Key Performance Parameters (KPPs) for Operational Availability and Net Ready along with interfaces. Describe the rationale for the proposed technical approach including associated risks and benefits.

b. Describe the technical approach to achieving the objectives stated in the SOO paragraph 6.3.3 for DoD System and Cyber Security requirements in the design, development, deployment, and operations stages to include supply chain risk protection.

c. Describe the approach to and rationale for delivering capabilities in the Offeror Self Certification (Attachment 0027) and Offeror Software Solution (Attachment 0028).

d. Describe the approach(es) to, rationale for and the composition of labor mix by CLIN, by Task Order as aligned to the Staff Levels Skill Mix Schedule (Attachment 0015).

L.4.2.1.3 Technical Schedule

The Offeror shall provide its ACWS ID/IQ Solution Integrated Master Schedule (IMS) (Offeror’s format must be compatible with MS Project 2013), and Systems Evolution Description, Systems View – 8 (SV-8) to meet the ACWS requirements to include all interfaces IAW paragraph L.4.2.4.3.

The Offeror shall provide a summary description of the approach to the IMS and rationale for the activities as follows:

a. Describe how the IMS will allow the ACWS program to meet the proposal schedule for Limited Deployment (LD), Initial Operational Capability (IOC), Full Deployment (FD) capability, and Full Deployment Decision (FDD) Program Milestones. The offeror shall include a description of the rationale for the timing of the activities, taking into consideration the RFP requirements and the RFP Notional Schedule, based on proven and mature processes.

b. Describe the rationale for the timing and sequence of the activities in Task Order 0001 based on the SOO and the RFP requirements.

c. Describe the elements of the graphical Systems Evolution Description, SV-8 that aligns with the Offeror's proposed IMS Build plan/schedule for the proposed software solution(s) that portrays all of the planned interfaces and is consistent with the DoD Architecture Framework (DoDAF).

L.4.2.1.4 – Solution Deployment, Training, Operations and Support: The Offeror shall provide an overview of its proposed methods and technical approach to Solution Deployment, Training, Operations and Support to CONUS and OCONUS locations across the Army (Attachment 0011). The Offer shall submit in Vol V, a completed Attachment 0024 Software License Disclosure. The Solution Deployment, Training, Operations and Support overview shall:

a. Describe the role of the System Integrator, the Software Provider (if different), the Army Contracting Enterprise Subject Matter Experts (SME) and/or any other entities that are expected to provide Operations and Support for the deployed solution. The summary shall identify tasks that must be performed, the timing of those tasks, and any specialized training and/or skills required by the personnel performing those tasks.

b. Describe the Configuration Management techniques or methods used to coordinate with the Army to operate and support the software solution, manage license/user access requirements and perform maintenance/upgrades.

c. Describe the approach for operations and support of the proposed solution to meet the system Operational Availability objectives (HLO-6).

d. Describe the Solution Deployment, Training, Help Desk, and Support to meet the RFP requirements to include leveraging the use of the 300 Government SMEs and the Government Knowledge Management Portal.

e. Describe a Software License Approach to meet the requirements of the Army Contracting Enterprise and the objectives of the SOO and the RFP. The approach should provide the Government the ability to operate and maintain the proposed software and software solution, and competitively procure it.

L.4.2.1.5 Technology Demonstration

The Technology Demonstration, which will include an introductory presentation, will be controlled by the PCO and will include Government support staff as determined by the

PCO.

At no point during the demonstration will discussions (IAW FAR 15.306(d)) be held.

Further details such as date, location, time and specific agenda for the Demonstration will be determined and disseminated after receipt of proposals.

All information necessary for the Technology Demonstration including required pre-staged reference/master data and general scenarios will be provided to each Offeror fourteen (14) calendar days in advance of its scheduled demonstration. All Offerors will be provided the same data and be allowed the same amount of time to prepare for demonstration.

Presenters/Demonstrators will be limited to five (5) personnel and must include at least one (1) of the Key Personnel proposed who is assigned to provide direct support to the ACWS contract.

All Offerors will be provided the same amount of time (notionally two and one half (2.5) work days) for their demonstration, which shall include an introductory presentation.

The format, content, and length of the presentation is at the discretion of the Offeror, but given the fixed time for demonstration, the length of the presentation will directly impact the length of the demonstration.

L.4.2.1.5.1 Technology Demonstration

The Offeror shall provide an introductory presentation to introduce its team and the content to be demonstrated. At least 1 of the “Key Personnel” proposed shall be the presenter during the introductory presentation. During the presentation, ALL present personnel shall be introduced.

The demonstration must be of a preconfigured, FAR-compliant COTS-CWS product and/or components from an existing Federal user’s active implementation(s) in the native, web-based architecture. This demonstration shall include verification of the proposed software solution, OOTB capability and a response to a Script/Scenario (provided upon arrival to demonstration site). Proposed usability features and built-in training/help functions shall be available at all stages of the demonstration. The Offeror’s response to the Script/Scenario will include at a minimum the following:

1. Requirements Development: Ability to receive a requirement in multiple formats (e.g., MS Word, MS Excel and Adobe).

2. Build Solicitation: Basic Contract Writing with the Uniform Contract Format;

Provide Training Aides / Help Tools; Select Clauses; Build Contract Data Requirements Lists; Assign CLIN Types (e.g., FFP, CPFF); Publish/Post an RFP;

Publish/Post an amendment.

3. Source Selection: Capability to receive proposals in Offeror’s proposed solution and provide confirmation to Vendors; Enable user to assemble an Evaluation Package for review, create and execute a workflow and evaluate proposals and record ratings.

4. Award: Produce a Conformed Contract in Offeror’s proposed solution; Post notifications for award and notifications for unsuccessful offerors via Offeror’s proposed solution.

5. Contract Administration: Personalization by End User; Rapid adaptability (new data field in a report); Reorganization (DoDAAC Org & Workload changes);

Business Intelligence; Receive accepted invoices (manually or automated).

6. Contract Closeout: Record and process an Administrative closeout.

7. ACWS Solution Training: Demonstrate built in training aids/features within the context of the Script/Scenarios 1 – 6 above.

8. Government Personnel/Usability: Provide Government personnel the opportunity to use the Offeror’s proposed solution without assistance from the Offeror’s Demonstration Team.

L.4.2.2 Subfactor 2 - Management Capabilities

L.4.2.2.1 Systems Engineering Management and Planning

The Offeror shall provide a summary of its approach for Management of Systems Engineering, Design, Development, Test and Evaluation. This summary shall:

a. Describe the details of the Offerors processes and methodology for the Management of Systems Engineering, Design, Development, Test, Evaluation, and Support Functions as related to the RFP requirements.

b. Describe the Offeror’s experience and demonstrated ability to perform tasks that support the planning, organizing, directing, coordinating, controlling, and approval of Systems Engineering actions to accomplish overall ACWS program objectives for cost, schedule, and performance as related to the RFP requirements.

L.4.2.2.2 Program Management

The Offeror shall provide a summary of its approach for Program Management. This summary shall describe the Program Management approach to control Cost, Schedule, Personnel, Communications, Risk, Quality, Configuration, Documentation, Audit Readiness, Training, Deployment, Organizational Change as well as Operations and Support. This includes details of the experience with any proposed team members and the proposed ACWS Software solution operating in the Federal Government.

L.4.2.2.3 Personnel Qualifications and Personnel Management

The Offeror shall provide a summary of its approach for Personnel Qualifications and Personnel Management. This summary shall:

a. Describe the approaches for recruiting, managing, and retaining a qualified and capable workforce that possesses the necessary experience, education, certifications, clearances and skills to support the entire scope described in the SOO are proven, mature, complete and feasible as related to the RFP requirements.

b. Describe the approach to replace departed personnel with equally qualified personnel that meets the process and timeframes specified in the SOO.

c. Describe the governance procedures to include roles, responsibilities, accountability and clear lines of communication between the Contractor team and the Government for timely problem identification, mitigation and resolution.

d. Provide a completed Offeror’s ACWS Staff Levels and Skill Mix Schedule (Attachment 0015) that includes an estimate of the personnel hours, by labor category and level, proposed for each task (by CLIN and by Task Order) within the proposed PWS.

L.4.2.3 - Performance Work Statement (PWS)

L.4.2.3.1 ID/IQ Performance Work Statement (PWS)

The Offeror shall propose a written PWS for the entire scope of the ACWS requirement based on Attachment 0001, ACWS Statement of Objectives. The Offeror’s proposed PWS shall be concise, but detailed enough for the Government to determine the Offerors understanding of the nature of the work and plan for providing the services and products required to achieve the ACWS Full Deployment Decision (FDD).

L.4.2.3.2 Task Order 0001 Performance Work Statement (PWS) The Offeror shall propose a written PWS for the entire scope of the ACWS TO 0001 requirement based on Attachment 0002, ACWS Task Order 0001 Statement of Objectives. The Offeror’s proposed TO 0001 PWS shall be concise, but detailed enough for the Government to determine the Offerors understanding of the nature of the work and plan for providing the services and products required to complete the Risk Reduction Phase.

L.4.2.4 - Compliance Matrix, Offeror Self Certification, IMS, and SV-8

L.4.2.4.1 Compliance and Cross Reference Matrix (Offeror format) The Offeror shall submit a complete Compliance and Cross Reference Matrix that provides the Government with the visibility to the relationships between Section L, Section M, SOO, Deliverables, CLIN, and Offerors Proposal Volume to include page number. If the offeror’s entry into this matrix conflicts with any portion of the proposal, that portion of the proposal shall take precedence over this matrix.

L.4.2.4.2 Offeror Self Certification (Attachment 0027) and Offeror Software Solution (Attachment 0028)

The Offeror shall submit a complete Technical Capability Self Certification and Offeror Software Solution IAW the instructions in Attachments 0027 and 0028. To be compliant, the offeror shall complete all tabs IAW the instructions. If the offeror’s entry into this matrix conflicts with any portion of the proposal, that portion of the matrix shall take precedence over the proposal narrative.

L.4.2.4.3 ACWS ID/IQ Solution Integrated Master Schedule (IMS) (Offeror format .mpp file)

The Offeror shall submit an IMS (compatible with MS Project 2013). All other formatting is up to Offeror’s discretion. The IMS shall clearly state activities at Level 3 planned over the entire ID/IQ Ordering Period. The Task Order 0001 IMS activities (which shall be included in the ID/IQ IMS) shall include all activities at all anticipated levels for the period of performance for Task Order 0001 IMS. This IMS shall include projected Government activities, decisions and milestones associated with the proposed solution.

In addition, this IMS shall include work streams, deliverables, and offeror’s milestones associated with the proposed solution/approach for the performance of the ACWS contract based on the SOO and the requirements of the RFP.

L.4.2.4.4 ACWS Systems Evolution Description, System View (SV)-8 (Offeror format .pdf file)

The Offeror shall submit a graphical Systems Evolution Description, SV-8 that aligns with the Offeror's proposed IMS Build plan/schedule for the proposed software solution(s) that portrays all of the planned interfaces and is consistent with the DoD Architecture Framework (DoDAF).

L.4.3 Volume II: Factor 2 - Past Performance

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

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

L.4.3.1.1 Cover Page: Offeror’s Company Name, CAGE Code, and DUNs

L.4.3.1.2 Table - The Offeror shall provide a table listing each proposed subcontractor’s Company Name to include its applicable CAGE Code and DUNs it intends to use in the performance of the ACWS RFP based on L.4.3.1.2.1. Proposed Subcontractor Criteria below.

L.4.3.1.2.1 Proposed Subcontractor Criteria – subcontractors or teaming partners that are proposed to perform at least twenty percent (20%) or more of the work effort based on the total proposed contract value, or any subcontractor or teaming partner the Offeror considers critical to overall successful performance of the ACWS Request for Proposal (RFP).

L.4.3.1.2.2 Joint Ventures – each member of a joint venture (JV) must submit its own past performance information.

L.4.3.1.3 Letters of Consent: Copies of signed and dated Letters of Consent from an authorized agent for each subcontractor, teaming partner or JV that authorizes the

Government to discuss the subcontractor’s, teaming partner’s or each member of the JV’s past performance evaluation results with the Offeror during negotiations.

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

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

L.4.3.1.4.2 Relevant performance means work efforts that are currently or have been performed that are the same or similar in scope, magnitude (dollar value), and complexity of the ACWS RFP. This includes providing COTS based platforms and/or performing systems development and configuration, interface development, testing, delivery, deployment, training, and help desk support activities. Of particular interest is performance of other Federal or DoD contract writing system contracts.

L.4.3.1.5 Adverse Contract Performance

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

a. Government Contract Number, place of performance, CAGE Code and DUNS Number. If the work was performed as a 1st tier subcontractor, also provide the name of the prime contractor and point of contact (POC) within the prime contractor organization (name, and current address, email address, and telephone numbers).

b. Government contracting activity Contracting Officer's name, e-mail address, telephone numbers.

c. Government technical representative/COR, and current e-mail address, telephone numbers.

d. Contract number and, in the case of indefinite delivery type contracts, GSA contracts, and Blanket Purchase Agreements, include Task/Delivery Order Numbers as well.

e. Period of performance of the contract or task/delivery order.

f. Provide a copy of any cure notices or show cause letters received,

g. Identify reason for any termination,

h. State any corrective actions taken,

i. Describe the extent to which the corrective action has been successful, identifying points of contact who can confirm the success of the corrective measures.

L.4.3.1.5.1 If there are no contracts meeting the descriptions above, the Offeror must so state that in Volume II Part D of its proposal. Failure to include this information may be cause for rejection of an Offeror’s proposal as incomplete.

L.4.3.1.6 Past Performance Questionnaire (PPQ)

The Offeror shall submit a PPQ (Past Performance Questionnaire Attachment 0018) for each of the past performance references included in the proposal. Offerors are also required to complete Section IIA. General Information and Section IIB. Contract Identification of the PPQ and include the only the completed Sections IIA and IIB in Volume II of the ACWS RFP.

L.4.3.1.6.1 Offerors supplying such information shall send the questionnaire to the point of contact (POC) requesting the remaining portions of the PPQ to be completed by the

POC.

L.4.3.1.6.2 The Offeror shall request the PPQ Respondent return the completed questionnaire directly to the Government email address cited on the questionnaire on or before the due date of the solicitation closure date. All questionnaires completed by the POC shall be sent from the POCs email address directly to the Government email address; not to the Offeror for forwarding to the Government. The POC Respondent shall submit the completed PPQ to:

Jonathan J. Anderson Procuring Contracting Officer Mail to: jonathan.j.anderson16.civ@mail.mil

AND

John Hemmen Contract Specialist Mail to: john.p.hemmen.civ@mail.mil

Past Performance Questionnaires submitted for an Offerors significant teaming partners and/or subcontractors shall clearly indicate the name of the Prime Offeror on the questionnaire.

Submission of Past Performance Questionnaires should be made no later than the proposal due date specified in the RFP.

L.4.4 Volume III: Factor 3 - Cost/Price

***NOTE***

Only one Price Matrix submission (Attachment 0020) is necessary to be considered for the ID/IQ award. However, if the Offeror wants to be considered in the additional source selection decision, it must fill out two price matrices (Attachments 0020 and 0021).

No contract award will be made to the additional offeror selected at the time of the ID/IQ award. The Government intends to offer that offeror with a contract should the ID/IQ awardee fail to successfully perform.

ACWS Price Matrix (Attachment 0020) will cover the initial 12-month base ordering period, the 48-month option ordering period 1, and the 60-month option ordering period 2.

ACWS Additional Price Matrix (Attachment 0021) will contain the same base and option ordering period structure as the ID/IQ; however, the Offerors shall price Attachment 0021 to begin 12 months after the ID/IQ Period of Performance has begun.

Any offeror who does not submit Attachment 0021 will not be considered in the additional source selection decision. If an offeror decides to maintain the same prices submitted on Attachment 0020, the offeror is still required to provide Attachment 0021 reflecting the same prices as in Attachment 0020.

Cost Realism will be performed on the cost CLINs in both Attachment 0020 and Attachment 0021.

The Government will not accept a second technical, past performance or small business volume. The initial submission for these three factors will be considered along with Attachment 0021 for the selection of the additional proposal.

L.4.4.1 Cost/Price introductory overview shall state any assumptions associated with the proposed Cost/Price Factor.

L.4.4.2 The Offeror shall complete the ACWS Price Matrix (Attachment 0020). Each area that requires the Offeror’s input has been highlighted in Blue. Please note the price for each Build will be entered on the Tab “Individual Builds” and will automatically be brought forward to the Price Evaluation Summary. The “Individual Builds” Tab allows for up to six (6) Builds. However, if additional Builds are required adjust the Individual Builds Tab as needed. Also, note the price for Support will be entered on the Tab Support and will automatically be brought forward to the Price Evaluation Summary.

The Support Tab allows for ten (10) years of Support, if necessary. In response to the solicitation, the Offeror shall provide a detailed cost proposal for each of the cost CLINs (0003, 0004, and 0006) with the exception of CLINs 0012 and 0013 which will have surrogate (Government provided number) amounts. Each proposed Build identified on tab “Individual Builds” in Attachment 0020, Price Matrix, under CLINs 0003, 0004, and

0006 requires a separate cost proposal. Each proposed Support identified on Tab Support under CLINs 0003, 0004, and 0006 requires a separate cost proposal. To be considered for the additional selection, the Offeror must also complete Attachment 0021 following these same instructions.

The anticipated CLIN structure for the base award and/or task orders is as follows:

CLIN 0001 (FFP) - Program Management CLIN 0002 (FFP) - Systems Engineering Management and Planning CLIN 0003 (CPFF) - Solution Design and Development CLIN 0004 (CPFF) - Test and Evaluation CLIN 0005 (FFP) - Training CLIN 0006 (CPFF) - Solution Deployment CLIN 0007 (FFP) - Organizational Change Management CLIN 0008 (FFP) - Operations and Support CLIN 0009 (FFP) - Licenses (for Commercial Software) CLIN 0010 (FFP) – Transition Out CLIN 0011 (FFP) - Studies, Analysis, Assessments and Improvements CLIN 0012 (Cost Reimbursable) - Travel (Non-Fee Bearing) CLIN 0013 (Cost Reimbursable) - Other Direct Cost (ODC) (Non-Fee Bearing) CLIN 0014 (Not Separately Priced) - Contractor Manpower Reporting CLIN 0015 (Not Separately Priced) - Contract Data Requirements List (CDRL)

L.4.4.3 The detailed cost proposal shall include ALL proposed costs to include the Prime, Subcontractors, and any other cost the Offeror would utilize to accomplish the CLIN broken out by phase and/or build. This information shall be submitted electronically in Excel format with working formulas and a paper copy - prepared in accordance with Federal Acquisition Regulation (FAR) 15.403-5(b). An Offeror may use its own format for the cost proposal as long as it contains all the elements and detail as delineated in FAR Table 15-2, Instructions for Submitting Cost/Price Proposals When Cost or Pricing Data are required.

Supporting documentation shall be included within both the electronic and paper copy of the cost proposal. The supporting documentation is required for the Government to perform the mandatory cost realism analysis. The support documentation shall be labeled, legible, and identifiable. The submitted Cost Proposal MUST contain all information required by FAR Table 15-2. The following are examples of supporting documentation that shall be included with the submission of the cost proposal and is NOT all inclusive.

L.4.4.4 Pricing Narrative

Pricing introductory overview shall state any assumptions associated with the proposed Pricing Factor and application of indirect rates and associated rationale.

L.4.4.5 Direct Labor Rates

The documentation used as the Basis of Estimate, i.e., Payroll data documenting the labor rates, letters of intent, wage surveys, Defense Contract Audit Agency/Defense Contract Management Agency (DCAA/DCMA) audited/reviewed labor rate, etc.

L.4.4.6 Proposed Indirect Rates, Fringes, and Factors

An Offeror having a Forward Pricing Rate Proposal (FPRP), Forward Pricing Rate Recommendation (FPRR) or Forward Pricing Rate Agreement (FPRA) shall include this documentation when submitting the proposal. An Offeror not having this documentation shall provide all of the necessary data to review the indirect rates; the following data is required.

L.4.4.6.1 Indirect Cost Pool

A descriptive summary of the costs proposed in each pool is required to be submitted in the Offeror's proposal.