W15QKN18R0033-0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 ____________ copies of the amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, 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.)

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)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0003 2018FEB22

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

NICOLE THALMANN

EMAIL: NICOLE.L.THALMANN.CIV@MAIL.MIL

W15QKN-18-R-0033

2018FEB06

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 15

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: NICOLE THALMANN

Buyer Office Symbol/Telephone Number: ACC-NJ-JA/(973)724-8200

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of this Amendment (0003) is to:

a) Answer questions posed by potential offerors

b) Update sections of the solicitation as indicated

Questions:__________

1) Re: L.4.4.3: are Offerors to provide a weighted average fully burdened labor rate (FBLR) for each of the labor categories or only those where the prime anticipates them to provide support?

ANSWER: Yes. Subcontracting rates are not required if the offeror does not anticipate subcontractor support in that labor category.

2) Are the subcontractor FBLRs to be before or after any pass-through is applied?

ANSWER: Reminder, this will be the maximum amount an offeror can charge for a subcontractor in that labor category for any future task.

Including any pass-through would be at the offerors discretion. Keep in mind, cost is an evaluation factor.

3) Is it acceptable if the Prime changes Attachment 1 to edit the Attachment 1 headings to reflect the Government changes? Example:

Column H is labeled "Subcontractor 1 Hourly Rate" where this now should be "Subcontractors Weighted FBLR"; and, replace all

"Subcontractor 1" to "Subcontractor(s)".

ANSWER: Amendment 0002 updated the Attachment 0001 columns and headings and those should not be altered by any offeror.

4) The original Solicitation Section L had provisions starting on page 60 that included L-1 through L-10. It also included instructions regarding the HQ AMC-Level Protest Program. Amendment 0001 appears to have deleted these provisions. Please clarify whether or not these referenced provisions in the original Solicitation are still applicable.

ANSWER: No, these provisions are still part of the solicitation. The Amendment document only shows sections that have been updated. If a section is not updated, it is not included in the amendment document.

5) The answer to Question 14 states that "Contractors should propose hours and rates for each task separate from Attachment 0001."

Please confirm that the Government is not looking for a separate spreadsheet but that Offerors are to use Attachment 1 and provide their proposed hours and associated FBLRs in the prime and subcontract hour/rates columns. That is, the proposed hours are separate from the

Government's estimated hours.

ANSWER: No. Attachment 0001 has no correlation to contractors sample task proposals, except that it will be the maximum hourly rates per labor category that can be proposed in a task. A separate spreadsheet for a cost proposal for the sample task shall be submitted for each Functional Area that an offeror is submitting for consideration.

6) In the event that the contract reference is work as a subcontractor to a Prime, and the Prime has a corporate policy to not complete past performance questionnaires, can Offerors include a statement to that effect in the Past Performance volume and PPQ PPOC list submitted to the Gov't.

ANSWER: This can be noted. However, if offerors are listing the said contract in Section 1 of the Past Performance Volume, offerors shall submit the Past Performance Questionnaire to the Prime regardless, as it is required in L.4.2.2 (5). The policy of the Prime and whether they actually complete the questionnaire are not relevant to the requirements of the solicitation.

7) Is it the Gov't expectation that ever Sample Task responses will include hours for the 10 key personnel labor categories?

ANSWER: No. It is possible that might be how an offeror proposes in order to complete the work, but it is not the Government's expectation one way or another.

8) If an Offeror assigns non-key personnel to a specific sample task, in addition to the 10 key personnel as defined in Attachment 11, is the Offeror required to provide resumes for those non-key personnel?

2 15

W15QKN-18-R-0033 0003

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

ANSWER: No. Resumes are only required for Key Personnel, however additional information on other than key personnel is acceptable if the offeror wishes to provide it.

9) In Amendment 0001 page 22 of 25 Section L.3.6 Small Business Participation table list SDB twice and please confirm that it should only be listed once?

ANSWER: L.4.3.6 has been updated.

10) Background: Volume III Factor 3: In Amendment 0001 page 23 of 25 Section L.4.3.9 Compliance with FAR 52.219-9. Small Business

Subcontracting Plans in accordance with the requirements of 52.219-9 are usually much greater than 5 pages. The total page count for

Volume III is 5 pages. Question: Does the government require offerors to submit a complete Small Business Subcontracting Plan in

Volume 3 or just the requirement listed in sections 4.3.9.1, 4.3.9.2 and 4.3.9.3?

ANSWER: If an offeror is required to submit a subcontracting plan, it will not be part of Volume III. This is a separate document to be included in Volume V. Section L.4.3.9 only requires offerors to include information in Volume III about prior compliance with FAR 52.219-

9.

11) Background: In Amendment 0001 page 25 of 25 L.4.5 Volume IV Solicitation, Offeror and Award Documents, its request a Small Business

Subcontracting Plan shall be submitted in accordance with 52.219-9. Question: Does the government want a full Small Business

Subcontracting Plan in accordance with 52.219-9 included with Volume V?

ANSWER: Yes, the full Small Business Subcontracting Plan should be included in Volume V if the offeror is other than a small business.

*** END OF NARRATIVE A0005 ***

3 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

\*\'02\'00.;\'01;\'03(\'01);\'02;\*

L. Proposal Submission:_______________________

L.1 Introduction: An Offeror may choose to propose against one, two, three, or all four functional areas. Each proposal shall include information for all factors and sub-factors required in this section. This section contains general proposal submissions instructions as well as specific proposal requirements for Software Engineering Services in Support of the Armament Software Engineering Center.

L.1.1 General: Offerors shall provide information by addressing each Factor/Sub-factor in the format and sequence identified in the solicitation. The Offerors must provide information in sufficient detail to allow the Government to make a best value assessment of the Offerors capability to support the proposed/required Technical, Past Performance, Small Business Participation and Price Factors. Proposals that do not contain the information requested risk being determined unacceptable by the Government.

L.1.2 The proposal must not merely repeat the solicitation requirements, but rather must provide convincing documentary evidence in support of conclusive statements of how contract requirements will be met.

L.1.3 The Government intends to award without discussions (see FAR 52.215-1). Proposals that do not contain the information requested in the solicitation risk being determined Unacceptable by the Government. The Government will not assume the Offeror possesses any capability, understanding, or commitment not specified in the proposal.

L.1.4 Alternate Proposals: Alternate proposals will not be accepted.

L.1.5 Proposals shall be valid through 30 July 2018.

L.1.6 The Government does not assume the duty to search for data to cure problems it finds in proposals. The burden of proving acceptability remains with the Offerors.

L.2 All questions concerning this procurement, either technical or contractual must be submitted in writing to the Contracting Officer.

No direct discussion between the technical representative and a prospective Offeror shall be conducted. Questions and proposals shall be submitted to the following point of contact:

Army Contracting Command New Jersey

ACC-NJ-JA, Bldg. 9

ATTN: Nicole Thalmann Telephone: (973)724-8200

Picatinny Arsenal, NJ 07806-5000

E-mail: nicole.l.thalmann.civ@mail.mil

L.2.1 Each proposal shall be submitted in the English language and SHALL SPECIFY ON THE COVER PAGE the specific

Functional Area(s) the Offeror is submitting a proposal for, i.e., Functional Area 1 - Software Development. __________________

L.2.2 Offerors may elect to submit proposal(s) for any one, combination of more than one, or all of the four Functional

Areas listed below. Each Offeror shall submit separate and distinct proposals for each Functional Area they are responding to. Each proposal shall include ALL of the following: Volume I -Technical Factor, Volume II Past

Performance Factor, Volume III - Small Business Participation Factor, and Volume IV Price Factor. Each proposal shall consist of and include all of the following:

Please note that electronic e-mail proposal submissions will not be accepted.

a. One (1) signed and completed paper copy of the attached Standard Form 33 (SF 33) and continuation sheets

(Sections A through M) signed by a person authorized to enter into the proposed contract on behalf of the

Offeror. Acknowledgment of all amendments to the solicitation and all continuation sheets are to be filled in as directed, i.e., proposed prices in the CLINs/Pricing Matrices in Section B, any fill-ins required, such as Contract Data Requirements List: DD Form 1423 with Blocks 17 and 18 completed if required, and

Certifications and Representations in Section K. Offerors are directed to thoroughly read the solicitation and fill in the required information in the appropriate solicitation clauses. For any fill-ins that are not applicable, the Offeror must acknowledge by indicating N/A. The proposal must also include computation for the use of Government Property, if applicable.

b. Original and six (6) paper copies and two (2) electronic CD copies of the proposal volume, as reflected in

L.3., shall be compiled using the Microsoft Office for Windows suite of applications, submitted on a single-write CD-ROM to prevent accidental erasure of the data therein, and formatted for an MS Windows compatible computer. The Price Factor shall be submitted in one (1) paper copy and two (2) electronic CD copies;

4 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

contained on a separate CD from non-price Factors. Price Factor (Volume IV) shall include Attachment 0001 and the sample task cost proposal for each of the functional areas. Price breakdown, when applicable, will include MS Excel spreadsheets with formulae intact. Process flows may be delivered in hard copy if not compatible with the above software. CD copy must mirror the submitted hard copies. If the CD copy and hard copy differ, the CD copy supplied for each Factor will be used for the evaluation. Each CD must be clearly marked with the Offerors Name and the Solicitation Number. Alternatively, files may be provided in Portable

Document Format (.pdf). REMINDER: A complete proposal package is required for each of the following functional areas that Offerors are submitting a proposal for:

Functional Area 1: Software Development

Functional Area 2: Software Sustainment

Functional Area 3: Software Process Assurance

Functional Area 4: Armament SEC Infrastructure Support

Note on Paper Submissions: The Government does not request separate binders for each Volume of each

Functional Area, as long as the Volumes are clearly separated within one binder. 7 binders may be submitted

(one original and 6 copies) for each Functional Area that include Volumes I-IV together, clearly marked and separated. The maximum number of binders the Government should receive is twenty-eight (7 for each functional area x 4 functional areas).

c. Representations through System for Award Management. The purpose of electronic Representations and ___________________________________________________

Certifications is to provide all Offerors with a portal in which to submit Reps/Certs in a publicly accessible format, nullifying the requirement to submit identical information in response to each and every

Federal contract solicitation. As a requirement under the ARDEC SEC Software Engineering Support solicitation, all Offerors must submit Reps/Certs data into the System for Award Management (S.A.M.) at https://www.sam.gov/ and provide one (1) hard copy and one (1) electronic copy (on CD) submitted as a

.PDF file. Any Offeror that has previously submitted Reps/Certs data into SAM is reminded to update the data prior to submitting with the proposal.

L.2.3 Each Large Business Offeror shall provide a Small Business Subcontracting Plan that contains all the elements required by FAR 52.219-9, alternate II. This plan shall be incorporated into any resultant contract in reference to the RFP.

L.3 FORMAT FOR PROPOSAL:________________________

L.3.1 The Offerors proposal shall be submitted in severable volumes based on the Factors as set forth below and all information specific to each Factor shall be confined to that volume. Each proposal must include all volumes and shall be submitted by the closing date and time of the solicitation. Failure to provide any volume may result in the proposal being given an Unacceptable rating. Information provided shall be specific to each Factor.

Page limitation for each Volume is as follows:

Volume I: Technical Factor: Subfactor 1 (Maximum of 25 pages per functional area)

Technical Factor: Subfactor 2 (Maximum of 2 pages per labor category for each functional area)

Technical Factor: Subfactor 3 (Maximum of 10 pages per functional area)

Volume II: Past Performance Factor (Maximum of 10 pages per functional area)

Volume III: Small Business Participation (Maximum of 5 pages per functional area)

Volume IV: Price Factor (No Maximum)

L.3.2 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 using the Table of Contents feature in MS Word. MS Word (.doc) files shall use the following page setup parameters:

Margins Top, Bottom, Left, Right - 1

Gutter - 0

5 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

From Edge - Header, Footer - 0.5

Page Size, Width - 8.5

Page Size, Height 11

L.3.3 Length:

L.3.3.1 Each volume shall be as brief as possible, and consistent with complete submission. The page count will be made by counting the pages from left to right, consecutively. Pages exceeding the page limit will not be evaluated.

Each paragraph shall be separated by at least one blank line. Annexes, documentation and attachments that are submitted by the Offeror, which are not required as part of the RFP, will count against the page limitations. If pages are printed on both sides, each side will count as a separate page. The following will not count against page limitations: volume title pages, table of contents pages, cross referencing pages, acronym lists and page dividers

(used to separate proposal parts/sections). Pages should not exceed 8-1/2 inches in width by 11 inches in length;

foldout pages depicting designs, sketches, samples, etc. may be used, with each fold counted as one page. The font used shall not be less than 12 point and font type shall be Times New Roman or Arial for the basic text. Graphs and charts can use 10 point Times New Roman, Arial or Arial Narrow.

L.3.3.2 Deviation from Requested Format: Request for deviations from the above format shall be submitted to the

Procuring Contracting Officer (PCO) in writing via email, no later than 15 days after release of the solicitation mailto:" the contract (PCO). Offerors shall provide an explanation, in a clearly relatable format, such as a matrix, _ of any differences between the manner in which the proposal was requested and the manner in which it is proposed to be submitted.

L.3.3.3 The Offeror is responsible for including sufficient details to permit a complete and accurate evaluation of the proposal. The Offeror shall provide a proposal that, at a minimum, addresses those evaluation Factors and Subfactors required in Section L and M of the RFP. Offerors must respond to all four evaluation factors.

L.3.3.4 File Packaging - All of the proposal files shall be compressed (zipped) into one file using WinZip version 6.2 or later, or as separate uploads in their native format, i.e. doc,.xls, ppt., etc. Please note Self extracting .exe files will not be accepted.

L.4 SPECIFIC PROPOSAL INSTRUCTIONS:

Offerors are responsible for including sufficient details (i.e. drawings, test data) to permit a complete and accurate evaluation strictly from a technical standpoint. The Technical Volume(s) shall have a separate index, which contains narrative titles that are cross-referenced to both the applicable Performance Work Statement (PWS) paragraph and page number. This index shall not count against the Page limitation for the Technical Volume. The narrative discussions shall also be related to the applicable PWS paragraph by placing the appropriate PWS number at the beginning of the discussion text. The proposal shall be detailed and clearly stated to allow an assessment by the Government without the need for additional clarifications. The

Offeror shall provide detailed narrative discussions that address both the PWS and the Contract Data Requirements List (CDRLs) of the solicitation. All information and data provided shall be specific to the ARDEC SEC Software Engineering Support effort, except for the area of Past Performance. In the response to the Request for Proposal, the Offeror must address the Factors and

Subfactors listed below. Offeror may elect to submit separate proposals for any one, combination of more than one, or all four functional areas identified below:

L.4.1 VOLUME I TECHNICAL Each Offeror shall submit a separate and distinct technical proposal for each functional area___________________________ proposed.

L.4.1.1

Technical Factor for Functional Area 1 - Software Development

L.4.1.1.2 SUBFACTOR 1: Adequacy of Response to Satisfy the Requirements ____________

Each offeror and major subcontractor and affiliate under shall describe and demonstrate with detailed examples, how its software development capability was applied successfully to systems/projects similar to this functional area. Major subcontractor and affiliate is defined as: any subcontract/affiliate that would perform more than 20% of the work proposed. This will determine the adequacy of the offerors knowledge, experience, and capabilities in the area of software development in accordance with the Performance Work Statement (PWS) paragraphs 3.8.4.1, 3.8.1, and 3.8.2. The

Offeror shall identify the relevancy of the prior contracts/projects to the work identified in this

RFP. Specific emphasis shall be placed on, but is not limited to, on the following:

1. Experience with IEEE 12207 Standard for

6 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Information Technology Software Life Cycle Processes and Life Cycle Data or equivalent.

2. Familiarity with software development process maturity and implementation of Capability Maturity

Model Integration (CMMI) or equivalent.

Offerors may receive a higher rating based on the quality of proposal submissions including items 1 and or 2 above.

L.4.1.1.3 SUBFACTOR 2: Availability/Expertise of Proper Personnel to Perform the Work ____________

Offerors shall submit resumes for proposed personnel to be assigned to work on the resulting contract in accordance with the labor categories and descriptions included in Section J. Resumes shall include qualifications, education and work experience to demonstrate that the proposed personnel are qualified per Attachment J requirements and can meet the technical requirement of the RFP. Section

J, Attachment includes the list of key labor categories for this functional area. For the purposes of this solicitation, the government considers ONLY THE LABOR CATEGORIES DENOTED WITH ASTERICKS, YELLOW HIGHLIGHTS AND UNDERLINES in Attachment 0011 key for the Technical Factor.

L.4.1.1.4 SUBFACTOR 3: Sample Task Proposal ____________

Offerors are responsible for including sufficient details in the technical volume (WITHOUT REFERENCE TO

COST/PRICE) to permit a complete and accurate evaluation strictly from a technical standpoint. This part shall have an index which contains narrative titles which are cross-referenced to both the applicable sample task paragraph and page number. The narrative discussions shall also be related to the applicable sample task paragraph by placing the appropriate sample task number at the beginning of the discussion text. The offeror shall provide detailed narrative discussions that address the sample task requirements.

Priced proposals for the Sample Task should be included in the PRICE FACTOR (Volume IV) of the Proposal ONLY.

At a minimum the offeror should include:

A plan of how the offeror intends to perform the requirements of the sample task, including his/her technical approach, specific expertise of personnel, and any other factors which would indicate that the contractor can meet the requirements. In addition, a detailed work breakdown structure should be included, showing how the contractor intends to organize and perform the work effort. Capabilities to be used in the execution of the scope of work shall be detailed. Any subcontracting planned shall be detailed. The offeror shall provide evidence that shows the appropriate resources to complete each task will be available when required (any subcontracted work must be described in the same level of detail as in-house activities). The offeror shall describe their quality management system as related to the work effort involved in this scope of work. In addition, the offeror shall discuss specifically how the proposed quality system will be applied to perform the requirements of this solicitation. The offeror shall describe the training background, duties, experience and qualifications for all key personnel, including work and educational experience, certificates, degrees, licenses and other measures of recognition attained. Particularly, they shall address availability of said personnel as related to this task, including subcontractors, if applicable.

L.4.1.2

Technical Factor for Functional Area 2 Software Sustainment

L.4.1.2.1 SUBFACTOR 1: Adequacy of Response to Satisfy the Requirements ____________

Each offeror and major subcontractor and affiliate shall describe and demonstrate with detailed examples, how its software sustainment capability was applied successfully to systems/projects similar to this functional area Major subcontractor and affiliate is defined as: any subcontract/affiliate that would perform more than 20% of the work proposed. This will determine the adequacy of the offerors knowledge, experience, and capabilities in software sustainment in accordance with the Performance Work Statement (PWS) paragraphs 3.8.4.2, 3.8.1, and 3.8.2. The offeror shall identify the relevancy of the prior contracts/projects to the work identified in this

RFP. Specific emphasis shall be placed on, but is not limited to, the following:

1. Experience with IEEE 12207 Standard for Information Technology Software Life Cycle Processes and

Life Cycle Data or equivalent.

2. Familiarity with software sustainment process maturity and implementation of Capability Maturity

Model Integration (CMMI) or equivalent.

7 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Offerors may receive a higher rating based on the quality of proposal submissions including items 1 and or 2 above.

L.4.1.2.2 SUBFACTOR 2: Availability/Expertise of Proper Personnel to Perform the Work ____________

Offerors shall submit resumes for proposed personnel to be assigned to work on the resulting contract in accordance with the labor categories and descriptions included in Section J, Attachment. Resumes shall include qualifications, education and work experience to demonstrate that the proposed personnel are qualified per the Attachment J requirements and can meet the technical requirement of the RFP. Section J, Attachment includes the list of key labor categories for this functional area.

For the purposes of this solicitation, the government considers ONLY THE LABOR CATEGORIES DENOTED

WITH ASTERICKS, YELLOW HIGHLIGHTS AND UNDERLINES in Attachment 0011 key for the Technical Factor.

L.4.1.2.3 SUBFACTOR 3: Sample Task Proposal ____________

Offerors are responsible for including sufficient details in the technical volume (WITHOUT REFERENCE TO

COST/PRICE) to permit a complete and accurate evaluation strictly from a technical standpoint. This part shall have an index which contains narrative titles which are cross-referenced to both the applicable sample task paragraph and page number. The narrative discussions shall also be related to the applicable sample task paragraph by placing the appropriate sample task number at the beginning of the discussion text. The offeror shall provide detailed narrative discussions that address the sample task requirements.

Priced proposals for the Sample Task should be included in the PRICE FACTOR (Volume IV) of the Proposal ONLY.

At a minimum the offeror should include:

A plan of how the offeror intends to perform the requirements of the sample task, including his/her technical approach, specific expertise of personnel, and any other factors which would indicate that the contractor can meet the requirements. In addition, a detailed work breakdown structure should be included, showing how the contractor intends to organize and perform the work effort. Capabilities to be used in the execution of the scope of work shall be detailed. Any subcontracting planned shall be detailed. The offeror shall provide evidence that shows the appropriate resources to complete each task will be available when required (any subcontracted work must be described in the same level of detail as in-house activities). The offeror shall describe their quality management system as related to the work effort involved in this scope of work. In addition, the offeror shall discuss specifically how the proposed quality system will be applied to perform the requirements of this solicitation. The offeror shall describe the training background, duties, experience and qualifications for all key personnel, including work and educational experience, certificates, degrees, licenses and other measures of recognition attained. Particularly, they shall address availability of said personnel as related to this task, including subcontractors, if applicable.

L.4.1.3

Technical Factor for Functional Area 3 Software Process Assurance

L.4.1.3.1 SUBFACTOR 1: Adequacy of Response to Satisfy the Requirements

Each offeror and major subcontractor and affiliate under shall describe and demonstrate with examples on how software process assurance was applied to similar systems/projects/organizations to this functional area. Major subcontractor and affiliate is defined as: any subcontract/affiliate that would perform more than 20% of the work proposed. This will determine the adequacy of the offerors knowledge, experience, and capabilities in software process assurance in accordance with the

Performance Work Statement (PWS) paragraphs 3.8.4.3. The offeror shall identify the relevancy of the prior contracts/projects to the work identified in this RFP. Specific emphasis shall be placed on, but is not limited to, the following:

1. Proven experience with implementing principles of Capability Maturity Model Integration (CMMI), as per CMMI-SE/SW/SS V 1.3 or later.

2. Experience in the development and maintenance of Intranet sites.

3. Experience with statistical models and analysis.

Offerors may receive a higher rating based on the quality of proposal submissions including items 1 and or 2

8 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

and or 3 above.

L.4.1.3.2 SUBFACTOR 2: Availability/Expertise of Proper Personnel to Perform the Work______________________

Offerors shall submit resumes for proposed personnel to be assigned to work on the resulting contract in accordance with the labor categories and descriptions included in Section J, Attachment. Resumes shall include education and work experience to demonstrate that the proposed personnel are qualified per the Attachment J requirements and can meet the technical requirement of the RFP. Section J, Attachment includes the list of key labor categories for this functional area. For the purposes of this solicitation, the government considers ONLY THE LABOR CATEGORIES DENOTED WITH ASTERICKS, YELLOW

HIGHLIGHTS AND UNDERLINES in Attachment 0011 key for the Technical Factor.

L.4.1.3.3 SUBFACTOR 3: Sample Task Proposal ____________

Offerors are responsible for including sufficient details in the technical volume (WITHOUT REFERENCE TO

COST/PRICE) to permit a complete and accurate evaluation strictly from a technical standpoint. This part shall have an index which contains narrative titles which are cross-referenced to both the applicable sample task paragraph and page number. The narrative discussions shall also be related to the applicable sample task paragraph by placing the appropriate sample task number at the beginning of the discussion text. The offeror shall provide detailed narrative discussions that address the sample task requirements.

Priced proposals for the Sample Task should be included in the PRICE FACTOR (Volume IV) of the Proposal ONLY.

At a minimum the offeror should include:

A plan of how the offeror intends to perform the requirements of the sample task, including his/her technical approach, specific expertise of personnel, and any other factors which would indicate that the contractor can meet the requirements. In addition, a detailed work breakdown structure should be included, showing how the contractor intends to organize and perform the work effort. Capabilities to be used in the execution of the scope of work shall be detailed. Any subcontracting planned shall be detailed. The offeror shall provide evidence that shows the appropriate resources to complete each task will be available when required (any subcontracted work must be described in the same level of detail as in-house activities). The offeror shall describe their quality management system as related to the work effort involved in this scope of work. In addition, the offeror shall discuss specifically how the proposed quality system will be applied to perform the requirements of this solicitation. The offeror shall describe the training background, duties, experience and qualifications for all key personnel, including work and educational experience, certificates, degrees, licenses and other measures of recognition attained. Particularly, they shall address availability of said personnel as related to this task, including subcontractors, if applicable.

L. 4.1.4

Technical Factor - Functional Area 4 Armament SEC Infrastructure Support

L.4.1.4.1 SUBFACTOR 1: Adequacy of Response to Satisfy the Requirements______________________

Each offeror and major subcontractor and affiliate under shall describe and demonstrate with examples on how infrastructure support was applied tosimilar systems/projects/organizations to this functional area. Major subcontractor and affiliate is defined as: any subcontract/affiliate that would perform more than 20% of the work proposed.. This will determine the adequacy of the offerors knowledge, experience, and capabilities in infrastructure support in accordance with the Performance Work

Statement (PWS) paragraphs 3.8.4.4. The offeror shall identify the relevancy of the prior contracts/projects to the work identified in this RFP. Specific emphasis shall be placed on, but is not limited to, the following:

1. Experience with DoD and Army Regulations, Policies and Best Business Practices (BBPs) for Cyber

Security.

2. Experience with Cisco routers, Windows workstations and servers, and Linux/Unix based systems.

3. Familiarity with software development process maturity and implementation of a mature process model such as Capability Maturity Model Integration (CMMI)/ISO 9000 Armaments SEC OSP or equivalent from past or current Information Systems and Infrastructure Support projects.

4. Experience with Biometrics Systems development, implementation, and software and hardware engineering.

9 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Offerors may receive a higher rating based on the quality of proposal submissions including items 1 and or 2 and or 3 and or 4 above.

L.4.1.4.2 SUBFACTOR 2: Availability/Expertise of Proper Personnel to Perform the Work______________________

Offerors shall submit resumes for proposed personnel to be assigned to work on the resulting contract in accordance with the labor categories and descriptions included in Section J, Attachment. Resumes shall include education and work experience to demonstrate that the proposed personnel are qualified per the

Section J, Attachment requirements and can meet the technical requirement of the RFP. Section J, Attachment includes the list of key labor categories for this functional area. For the purposes of this solicitation, the government considers ONLY THE LABOR CATEGORIES DENOTED WITH ASTERICKS, YELLOW HIGHLIGHTS AND UNDERLINES in Attachment 0011 key for the Technical Factor.

L.4.1.4.3 SUBFACTOR 3: Sample Task Proposal ____________

Offerors are responsible for including sufficient details in the technical volume (WITHOUT REFERENCE TO

COST/PRICE) to permit a complete and accurate evaluation strictly from a technical standpoint. This part shall have an index which contains narrative titles which are cross-referenced to both the applicable sample task paragraph and page number. The narrative discussions shall also be related to the applicable sample task paragraph by placing the appropriate sample task number at the beginning of the discussion text. The offeror shall provide detailed narrative discussions that address the sample task requirements.

Priced proposals for the Sample Task should be included in the PRICE FACTOR (Volume IV) of the Proposal ONLY.

At a minimum the offeror should include:

A plan of how the offeror intends to perform the requirements of the sample task, including his/her technical approach, specific expertise of personnel, and any other factors which would indicate that the contractor can meet the requirements. In addition, a detailed work breakdown structure should be included, showing how the contractor intends to organize and perform the work effort. Capabilities to be used in the execution of the scope of work shall be detailed. Any subcontracting planned shall be detailed. The offeror shall provide evidence that shows the appropriate resources to complete each task will be available when required (any subcontracted work must be described in the same level of detail as in-house activities). The offeror shall describe their quality management system as related to the work effort involved in this scope of work. In addition, the offeror shall discuss specifically how the proposed quality system will be applied to perform the requirements of this solicitation. The offeror shall describe the training background, duties, experience and qualifications for all key personnel, including work and educational experience, certificates, degrees, licenses and other measures of recognition attained. Particularly, they shall address availability of said personnel as related to this task, including subcontractors, if applicable.

L.4.2 Volume II FACTOR 2 - PAST PERFORMANCE:_____________________________________________

L.4.2.1 Each Offeror shall submit a separate and distinct Past Performance proposal for each functional area proposed. Offerors shall identify pertinent past history, which indicates that similar efforts of equal or greater complexity have been performed using the Offerors existing plant capability and demonstrate satisfaction of customer requirements.

L.4.2.2 Offerors shall submit a list of all recent Government contracts (prime and major subcontracts) in performance or awarded to the Offeror and any of its major subcontractors within the past three (3) years, or awarded earlier than three

(3) years ago, but for which deliveries/performance occurred or were scheduled to occur within the past three (3) years, which are relevant to the effort required by the solicitation. Data concerning the prime Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. Offerors are reminded that both independent data and data provided by the Offerors in their proposals may be used to evaluate the Offerors past performance. The

Government plans to rely on existing documentation from Federal databases to the maximum extent practicable. Sources of existing information available to the Government include, but are not limited to, Past Performance Information and

Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), and Electronic

Subcontract Reporting System (eSRS). The Government may use past performance information obtained from sources other than those identified by the Offeror. The burden of providing thorough and complete past performance information remains with the Offerors. Proposals that do not contain the information requested by this paragraph may result in rejection or receipt of a high performance risk evaluation by the Government. This volume shall be organized into the following sections:

10 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(1) Section 1 Contract Descriptions. 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). PLEASE NOTE: While an

Offeror may submit past performance information on relevant efforts where they performed as a major subcontractor, the

Government does not have privity with subcontracts and therefore, may not be able to obtain qualitative information.

(b) Government contracting activity, and current address, Procuring Contracting Officer's name, e-mail address, telephone and fax numbers.

(c) Governments technical representative/COR, and current e-mail address, telephone and fax numbers.

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

(e) Government contract administration activity's Pre-Award Monitor's name and current email address, telephone and fax numbers.

(f) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket

Purchase Agreements, include Delivery Order Numbers also.

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

(h) Awarded price/cost.

(i) Final or projected final price/cost.

(j) Original delivery schedule, including dates of start and completion of work.

(k) Final or projected final, delivery schedule, including dates of start and completion of work.

(2) Section 2 - Performance. Offerors shall provide a specific narrative explanation of each contract listed in _______________________

Section 1 describing the objectives achieved and detailing how the effort is relevant to the requirements of this solicitation.

(a) For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The Offerors shall also provide a copy of any

Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror or proposed subcontractor. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

(3) Section 3 Subcontracts. Offerors shall provide an outline of how the effort required by the solicitation will _______________________ be assigned for performance within the Offerors 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

PWS subparagraph number. This includes all subcontractors who will be providing critical hardware/services or whose subcontract is for more than 25% of the total proposed price.

(4) Section 4 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.

(5) Past Performance Questionnaire. For all contracts identified in Section 1, Past Performance ______________________________

Questionnaires must be completed and submitted (APPENDIX D). The Offeror shall complete Part I of the Past

Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POC's shall be instructed to electronically complete

Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Officer within 30 calendar days of the release of the RFP, to nicole.l.thalmann.civ@mail.mil. The Offeror shall also e-mail to the Contracting

Officer a list of all the POCs who were sent a questionnaire. The Government must receive this list within 30 calendar days after release of the RFP. The POC List shall be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-Mail Address; Date E-Mailed to POC (month/day).

(6) Offerors are cautioned that the Government may use data obtained from other sources. Since the Government may not necessarily interview all of the sources provided by the Offerors, it is incumbent upon the Offerors to explain the relevance of the data provided.

L.4.3 Volume III - FACTOR 3: SMALL BUSINESS PARTICIPATION FACTOR__________________________________________________________________

11 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.3.1 Each Offeror shall submit a separate and distinct Small Business Participation proposal for each functional area proposed. The Small Business Participation Factor Volume is comprised of a single chapter. Offerors are responsible for including sufficient detail to permit a complete evaluation. Any information provided as part of the

Small Business Participation Factor Volume may be used to correlate the evaluation of the other proposal volumes.

L.4.3.2 This provision applies to every Offeror (U.S. and non-U.S.), regardless of size status or locations of working facilities or headquarters. For proposal preparation purposes, the Offerors Small Business Participation proposals shall be consistent with any subcontracting references/identification contained elsewhere in any other Factor Volume.

Percentages are calculated using proposed total contract price as the denominator and include first-tier subcontractors only. For the purpose of evaluating Small Business Participation, the total contract price is determined to be the ceiling price on the contract. Offerors shall also explain their rationale as to why the percentage of SB participation being utilized for this effort is appropriate for their company. Offerors shall describe their approach and efforts undertaken to utilize Small Businesses (SB). SB targets will be incorporated into any resulting prime contract and contractors will be required to report SB participation.

L.4.3.3 All Offerors, including Offerors who are themselves U.S. Small Business concerns based on the NAICS code assigned to this requirement, are to identify the extent to which U.S. Small Business concerns will be utilized as first-tier subcontractors in the performance of this proposed contract. U.S. small business concerns are defined (1) in

FAR 19.001 and (2) by the criteria and size standards in FAR 19.102 for the applicable NAICS code. U.S. Small Business concerns include Small Businesses (SBs), Small Disadvantaged Businesses (SDBs), Woman-Owned Small Businesses (WOSBs), HUBZone Small Businesses (HUBZone SBs), Veteran-Owned Small Businesses (VOSBs), and Service Disabled Veteran-Owned

Small Businesses (SDVOSBs).

L.4.3.4 If the Offeror (to include any U.S. Small Business concerns who are proposing as part of a joint venture or teaming arrangement) is itself a U.S. Small Business concern, the Offeror's own participation as a SB, SDB, WOSB, HUBZone SB, VOSB, or SDVOSB will also be considered Small Business Participation for the purpose of this evaluation. In this event, the extent of the Offeror participation as a U.S. Small Business concern shall be detailed in the same manner as subcontracts to first-tier U.S. Small Business concerns.

L.4.3.5 Small Business Amounts: All Offerors shall address anticipated U.S. Small Business concern participation and subcontracting based on the total contract dollars proposed by the Offeror.

L.4.3.6 The Offeror shall provide information for Small Business Participation and subcontracting in a table format in accordance with the following example:

Small Business Participation Table (in Millions)

Business $ Cost All % of SB Cost Total ________ __________ _____________ __________

Category Contracts Participation SubK ________ __________ _____________ ____

Contract $43.00

Total Price

SB $10.34 24.00% $10.34 of $43.00

SDB $5.22 12.15% $5.22 of $43.00

WOSB $2.05 4.75% $2.05 of $43.00

HUBZone SB $1.08 2.50% $1.08 of $43.00

VOSB $1.55 3.60% $1.55 of $43.00

SDVOSB $1.46 3.40% $1.46 of $43.00

L.4.3.6.1 Guidance for filling in the above "Small Business Participation" Table:

(a) Include first-tier subcontractors only.