W15QKN18R0033-0002.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

0002 2018FEB21

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 16

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 is to:

1) Answer questions posed by potential offerors

2) Update sections of the solicitation as indicated

3) Update Attachment 0001 Pricing Schedule for Labor Categories

4) Update the Performance Work Statement for Sample Task in Functional Area 3

If contractors have already received all of the solicitation attachments they should immediately request the updated Attachment 0008 from mailto: Nicole.l.thalmann.civ@mail.mil. Updated Attachment 0001 will be attached as part of this amendment.

1) Attachment 0008 - Sample Task for Functional Area 3, page 12: There are a few inconsistencies between the CRDL and DID numbers referenced. Can the Government review our analysis and confirm our suggestions for clarification? Also, CDRLs A002 and A003 do not provide the frequency or time-frame in which they should be submitted. Can the Government provide this information?

ANSWER: Attachment 0008 has been updated in both the PWS and CDRLs for clarification.

2) For each functional area task price proposal, do we use same format as attachment 0001?

ANSWER: No. Attachment one is simply a spreadsheet that will list labor categories and rates for the life of any awarded contract. The hours associated with certain labor categories are for evaluation purposes only and are not related to sample tasks. Pricing proposals shall be submitted in accordance with Volume IV section L.4.4.

3) Do we have to take weighted average of the rates for all Subcontractors for Functional area Task price proposal? If that is the case then allocating labor hours to different subcontractors with their specific quoted rates to the prime will create subcontracting issue.

Please clarify.

ANSWER: No. Those weighted subcontractor rates cannot be exceeded. However, cost proposals for the sample tasks can be below those proposed as weighted subcontractor weights for the base contract but they cannot be above. Attachment 0001 will be used as maximum contract rates for the life of the contract.

4) With regard to resume experience Will the government allow significant experience to be substituted for education requirement?

ANSWER: The Government requires the education listed for each of the key personnel.

5) Based on review of Question and answer 16 and revised Section L in Amendment 1, it appears that Section L for FA 4 (L.4.1.4.1

Subfactor 1:, sub item 4.) still requires: Experience with Biometrics System development, implementation and software and hardware engineering. Question 16 Answer stated that: There will be no research and development of new biometric systems, only maintaining the lab access control system. Please clarify Section L requirement for FA 4 in this area.

ANSWER: No, there are no requirements for research and development, however the technical team is still requiring experience with

Biometrics System Development.

6) Per Section L.4.1.1.3, L.4.1.2.3, L4.1.3.3, L4.1.4.3, Priced proposals for the Sample Task should be included in the PRICE FACTOR

(Volume IV) of the Proposal ONLY. Since it is required to submit price proposals for the Sample Tasks included in the PRICE FACTOR

(Volume IV), what format/template should be used for the Sample Task price proposals? Is prime offeror format acceptable for Sample Task price proposals?

ANSWER: Sample Task Proposals shall be submitted in Excel with formulae intact.

7) What is the estimated start date (estimated date of award) to be used for the FFP rates and the Sample Tasks?

ANSWER: Assume Mid-May, 2018. However, should this change substantially after award of the base contracts, the offeror selected for award of each functional area task will be allowed to adjust their proposed hourly rates accordingly.

8) Attachment 0001 - PRICING SCHEDULE FOR LABOR CATEGORIES has a column for "Total Government Estimated Hours", where the Government has provided estimated hours that will be used to calculate the total contract price for evaluation. Additionally, there is a column for

2 16

W15QKN-18-R-0033 0002

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

"Total Contractor Estimated Hours". How is that column factored into the total contract price for evaluation? Additionally, the Section

L.4.4.3 states "The sum of the prime and subcontractor labor hours for each labor category shall not exceed the total estimated labor hours for the labor category". Is the total estimated labor hours the "Total Government Estimated Hours" or "Total Contractor Estimated

Hours"?

ANSWER: The Government assumes that the Hours in Prime and Subcontractor will add up to be the same as the Government's Estimated Hours.

For example, FA1, Year 1, the Government estimates Configuration Analyst II at 1400 hours. Should the contractor propose both hours for

Prime and Sub, they should total 1400 (i.e. 1000 Prime Hours, 400 Sub hours). The only reason there are separate columns for Prime and

Sub hours is if offeror assumes the hours will be split between prime and sub.

9) Are all proposed Contract Labor Rates submitted in Attachment 0001 considered onsite labor rates?

ANSWER: The labor rates proposed will be maximum labor rates per labor category whether on or off site. Reminder, when proposing for sample tasks (as well as future tasks if a contract is awarded), the labor rates can be less than those in Attachment 0001 but not more.

10) Per the response to Question 11 in Amendment 1, We do not require each individual subcontractor's loaded labor rates. Instead, we require one weighted average fully burdened labor rate for subcontractors. However, in Attachment 0001 PRICING

SCHEDULE FOR LABOR CATEGORIES there is a column for Subcontractor 1

Contractor Name. Should we disregard that column, since the rates will be the weighted average fully burdened labor rate for all our proposed subcontractors?

ANSWER: Yes. The Attachment 0001 has been updated and included as part of this Amendment.

11) Per the response to Question 12 in Amendment 1, As part of the Sample Task Proposal (Subfactor 3)\'85offerors clearly reference which personnel in Subfactor 2 would be utilized in which labor category that task. Since we are only providing 1 resume for each of the

10 LCATs highlighted for Subfactor 2, how should we reference other personnel that would be utilized in support of each corresponding

Sample Task? Must all personnel referenced in the Sample Tasks also be included in Subfactor 2?

ANSWER: All other labor categories, aside from the Key Personnel, that a contractor is proposing for a sample task (Technical Subfactor

3) shall be included in the proposal for Subfactor 3 and will not count toward the maximum 10 pages per functional area.

12) Per Section L.2.2.b, Original and six (6) paper copies and two (2) electronic CD copies of the proposal volumes, 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 contained on a separate CD from non-price Factors. Since the Price Factor shall be contained on a separate CD from non-price Factors, is there a requirement to include a printed hard copy of the Price Factor, Attachment 0001 - PRICING SCHEDULE FOR LABOR CATEGORIES?

ANSWER: The Government will require ONE printed hard copy of the Price Factor, Attachment 0001 as well as TWO CD Copies. Also, ONE printed copy for the cost proposal for each functional area sample task. Section L.2.2 (b) has been updated to reflect this.

13) When printing each Functional Area, shall all Volumes within that Functional Area be included in one binder, with tabs, or does each

Volume require a separate binder for submission?

ANSWER: Separate binders will be accepted, but they are not required. If contractors submit all volumes for each functional area in one binder, the Government just requires them to be clearly separated (by tabs, separators, etc.) by volume and subfactor. However, each

Functional Area shall be in separate binders.

14) Section A states: ""The services to be performed under this effort will be at various levels up to and including Secret. The services to be performed shall also require the contractor to gain access to locations and offices within Picatinny Arsenal, NJ and other sites. Security provisions will be specified on a form DD254. Security requirements will be specified based on individual task order.""

Question: Do key personnel whose resumes are submitted need to have Secret clearance? "

ANSWER: All key personnel must have Secret Clearance.

15) The RFP (L.4.3.9.1 ) requires the inclusion of documentation of goals and accomplishments under subcontracting plans of prior contracts performed over the past twelve (12) months (from the date of solicitation issuance), to include Individual Subcontracting

Reports (ISRs/DD Form 294s) which list both goals and accomplishments against individual or master plans. In order to be compliant with this requirement as written, we would have to submit a large number of ISRs. Is it the Governments intent that offerors provide ISRs for only the contracts referenced in the Past Performance Volume vice ISRs for all company activity performed over the past twelve (12) months?

ANSWER: No, that is not the Government's intent. ISRs are required to be submitted semiannually on all contracts requiring a subcontracting plan. The contractors shall submit a list of all contracts that have been reported (April 30th and October 30th of 2017) and the firm's accomplishments toward the goals of those contracts. If a contract did not require a subcontracting plan, then the

3 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

contractor would not have submitted an ISR. We do not intend for contractors to enter ISRs for contracts in which they are not required, but instead to provide the results of the reporting that was already required via FAR 52.219-9 and DFARS 252.219-7003. If any offeror is delinquent in their ISRs reporting from October, they should complete that prior to the closing of this solicitation in order to report it in accordance with L4.3.9.1. If an offeror has not been required to submit an ISR within the last 12 months, L.4.3.10 explains what can be submitted instead of the requirement at L.4.3.9.1.

16) This Section (L.4.2 Section 3) requires 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. As the volume relates to Past Performance, is it the

Governments intention that Offerors outline how proposed subcontractors have been utilized on those contracts cited for Past

Performance or is the intention to identify subcontractor use going forward under this volume?

ANSWER: The Government does not require information on how subcontractors have been utilized in the past under L.4.2 Section 3. Rather we only require information on subcontractors that will perform more than 25% of the total evaluated price and what work they will be responsible for under this effort.

17) In the Performance Work Statement (3.4) it says "Travel: The contractor shall perform travel as necessary for the individual task orders. Travel may include CONUS." Will travel, with applicable burdens, in the sample tasks be cost reimbursable or part of the FFP

Price?

ANSWER: Travel will be clearly identified in each Performance Work Statement for each Task, therefore, it will be included in the Firm

Fixed Price proposals for each task.

18) Section L2.2 b says "Price breakdown, when applicable, will include MS Excel spreadsheets with formulae intact. Please explain the details of Price breakdown. Would this entail rate build backup information to include direct rates, indirect rates and profit?

ANSWER: No. This is a competitive procurement and the only formulae we expect for the base award will be in Attachment 0001 (multiplying hourly rates time number of hours proposed. In the sample tasks, the price proposals should include all line items proposed (labor, travel, Other Direct Costs, etc.) if any of those apply).

19) CLIN 0023 is for Minimum Guarantee. Kickoff Meeting Minutes. Are the Sample Task Orders going to be awarded as part of the main IDIQ award?

ANSWER: No. Some sample tasks will be awarded shortly after the base contracts are in place and will be based off of the evaluations done under Subfactor 3. All contractors will participate in a kickoff meeting, but only those who are not selected for one of the sample tasks will be required to submit meeting minutes for the kickoff meeting.

20) Ref. L.4.1.1.4. Is there a specific format required for the Sample Task Order Pricings? If not, would the only pricing details be:

fully burdened labor rates times hours plus any fully burdened ODCs?

ANSWER: There is no specific format. However, the price proposals should include all line items proposed (labor, travel, Other Direct

Costs, etc.) if any of those apply).

21) Ref. L.2.2 b: Is it the Governments intention that a complete set of 7 instances (1 original + 6 copies) be created for each

Functional Area proposal being submitted, each of which contains 4 separate volumes/binders? Further, is it the Governments intent, for any contractor submitting responses for all 4 Functional Areas, to receive 112 total binders (7 sets for each of the 4 Functional Areas, each containing 4 binders per set)?

ANSWER: Yes, the Government requires 7 separate copies for each functional area. However, there is no requirement for separate binders, as long as the Volumes are clearly separated within one binder. For example: If a company submits a proposal for each of the four functional areas, the Government could receive as little as 28 binders. 7 for each functional area (with Volumes 1-4 clearly separated and marked in each binder).

*** END OF NARRATIVE A0004 ***

4 16

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;

5 16

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

6 16

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

7 16

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.

8 16

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

9 16

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.

10 16

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:

11 16

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…