W15QKN16R0070-0004.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

0004 2016JUN29

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

AUSTIN ALPAUGH

EMAIL: AUSTIN.M.ALPAUGH.CIV@MAIL.MIL

W15QKN-16-R-0070

2016MAY19

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 10

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: AUSTIN ALPAUGH

Buyer Office Symbol/Telephone Number: ACC-NJ-MA/(973)724-4166

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of this amendment to:

A. Answer questions from potential offerors.

B. Correct Section L - Instructions, Conditions, and Notices to Offerors in Paragraph No. A.3.1.a. to correct reference of Standard Form

33 (SF 33) to Standard Form 1449 (SF 1449).

Questions from potential offerors and the Government's answers are as follows:

1 On page 57 of the PWS, under Proposal Instructions, paragraph A.3.1 (a), it states that one (1) signed and completed paper copy of the attached Standard Form 33 (SF 33) shall be included in the proposal. We do not have the SF 33. We only have the SF 1449.

Please advise.

ANSWER: As this is a commercial procurement, the correct form is the SF 1449. (Typically for a non-commercial procurement a SF 33 is used). This Amendment 0004 corrects the reference to Standard Form 33 and SF 33 to read Standard Form 1449 and SF 1449.

2. For the above referenced solicitation, Subfactor 3 of the proposal instructions requires the offeror to address Task Order0001, eNOVA Support Services. Should the pricing for Subfactor 3 be included in the Technical/Management volume or submitted as a separate volume?

ANSWER: As per section A.5 in Specific Proposal Instructions, Offerors are responsible for including sufficient details (without reference to cost). Whereas, in section A.4 of Format for Proposals, indicates that the Price Factor shall be included in Volume

III. The instructions for pricing Task Order 0001 is found at Section A.5.3.5.

3. The eNOVA landscape is not well defined by the Government and is only known to the current incumbent leading to a multitude of questions. Will the Government consider extending the proposal due date an additional week from the current due date in order to give time to receive answers to questions?

ANSWER: The Landscape and software has been defined in updated PWS reference Amendment 0002, Attachment 0001, dated June 22, 2016.

The proposal due date was extended to July 8, 2016, 2:00 PM Local Time by Amendment No. 0003 dated June 27, 2016.

4. Page 10 of 11, A.3.13 Solicitation Document Can the Government provide details of the support desk that serves the eNOVA user community (structure, software used, call statistics, etc.)? Is the government intending to change the deployed (Remedy) Help Desk software?

ANSWER: The Helpdesk is defined in the updated PWS reference Amendment 0002, Attachment 0001, dated June 22, 2016. No change at this time for Remedy.

5. Task Order 0001 PWS Can the Government please provide a list of software and tools being utilized within the eNOVA program

ANSWER: The Landscape and software has been defined in updated PWS reference Amendment 0002, Attachment 0001, dated June 22, 2016.

6. Task Order 0001 PWS Is the Government intending for new functionality to be added to the existing suite of capabilities for eNOVA? If so, can the Government provide an estimated timeline?

ANSWER: New functionality is not being added at this time.

7. Task Order 0001 PWS Although not listed in the Current Software Environment section of the TO 0001 PWS, we understand that the

Government is using Windchill software. Can the Government please clarify if the tool is being used as an ALM or a PLM?

ANSWER: Windchill is not managed by an eNOVA team. Helpdesk routes level II and III tickets to other GOV managed team.

8. Task Order 0001 PWS Will the Government please provide a schematic of the SAP systems landscape and the number of interfaces

2 10

W15QKN-16-R-0070 0004

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

connected to them?

ANSWER: The Government currently has four interfaces. Standard SAP protocols are used for interfaces.

9. Task Order 0001 PWS Will the Government share the version numbers of SAP, PLM-ECC, BW, BOBJ, BBP, CUA, PI, ARIS, Content Server, Portal, System Landscape Directory, Solution Manager, and any other tools are being used for eNOVA? Has the government planned, or are they considering, any immediate software version upgrades to the systems mentioned above?

ANSWER: Landscape and software is defined in the updated Task Order 0001 PWS. Upgrades and other change requests are managed through the GOV Configuration and Control Board.

10. Task Order 0001 PWS Are there any pending eNOVA system change requests/RICE objects to be built as part of the scope of this task order, or is it purely operations and maintenance?

ANSWER: There is no planned development in the schedule. At this time, only change requests and software upgrades to support sustainment will be required.

11. Task Order 0001 PWS What are the types of data and volumes transacted between SAP systems and non-SAP systems via the interfaces? Are there any manual data loads or conventions that do not use interfaces?

ANSWER: There is one interface that has a manual data load. Transactional volume for the interfaces is low.

12. Task Order 0001 PWS Will the Government please clarify the role and purpose of the Content Server? What is the nature of the content that this server manages?

ANSWER: The Content Server supports SAP PLM (Product Lifecycle Management). The nature of the content is irrelevant.

13. Task Order 0001 PWS Can the Government provide a list of reports that are generated and rendered using the BOBJ system?

ANSWER: There are currently no more than 10 reports generated by the BOBJ system.

14. A.5.2 Volume II Factor 2: Past Performance pg 59 In cases where performance was as a subcontractor, the Government contracting activity and/or technical representatives may not be privy to the nature and/or the quality of work that the subcontractor performed

(as the Government points out on Page 59, Section A.5.2.2.). To verify the past performance references performed as a subcontractor, is it acceptable for offerors to provide Past Performance questionnaires to the Contractual POCs (for contract / administrative verification) and Project Managers (for verification of technical performance) of the Prime Contractor, instead of the Government? Aside from the Government not always having knowledge of the work that a subcontractor performed, Prime Contractors often require their subcontractors to work through their appropriate POCs instead of interfacing directly with the Government.

ANSWER: The Offeror shall follow the guidance provided in SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS, PROPOSAL

INSTRUCTIONS, Paragraph A.5.2.

15. A.5.2 Volume II Factor 2: Past Performance pg 59 In Section A.5.2.2, it is stated that offerors are required to submit contracts in performance or awarded to them in the last 3 years. Is the Government interested in cases where the offeror has been awarded a relevant IDIQ, but performance (e.g., task orders) on that IDIQ have not begun yet?

ANSWER: As per section A.5.2.1 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.

16. We have a question about the Governments intent with the following Section L requirement in Vol I, Subfactor 1 Corporate

Knowledge and Experience. A.5.1.1.b states: The Offeror shall provide evidence of prime contractor experience in the design, development, implementation, and maintenance of robust software solutions that facilitate enterprise knowledge sharing and streamline business processes. Our initial reading and understanding of this requirement was that [the company], bidding as the prime for this acquisition, i.e., the ARDEC IT Support Services IDIQ, is required to provide evidence that our company, not a team mate or subcontractor, has prior experience in the design, development, implementation, and maintenance of robust software solutions that facilitate enterprise knowledge sharing and streamline business processes. Under this interpretation, our work as a subcontractor on various US Army projects such as GFEBS, LMP, and at LOGSA would qualify as the required experience. However, upon further reflection, we are concerned we misunderstood the intent of the requirement.

Question: Is the Governments intent, with this requirement, that bidders must demonstrate that as a prime contractor on a past contract (or contracts) they have the required experience. In other words, this required experience, gained as a subcontractor, isnt sufficient?

ANSWER: Under Specific Proposal Instructions, as per A.5.1.1 b., The Offeror shall provide evidence of prime contractor experience in the design, development, implementation, and maintenance of robust software solutions that facilitate enterprise knowledge sharing and streamline business processes.

3 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

*** END OF NARRATIVE A0005 ***

4 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

PROPOSAL INSTRUCTIONS:

A.1 General:

A.1.1 Offerors shall provide information by addressing each Factor/Subfactor 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 response to the evaluation criteria. 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.

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

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

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

A.1.5 Proposals shall be valid through 180 days after the closing of the RFP.

A.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 shall be submitted to the following point of contact:

A.2.1 The physical address for delivery is as follows:

Army Contracting Command - New Jersey (ACC-New Jersey)

Maneuver Ammunition Center

ATTN: Mr. Frank Corradi, Contract Specialist

Bldg. 10, ACC-NJ-MA Mail Stop: 10B

Picatinny Arsenal, NJ 07806-5000

For hand delivery please contact any of the points of contact below as follows:

Mr. Frank Corradi, Contract Specialist, Phone: 973-724-5421 or Mr. Austin Alpaugh, Phone: (973)724-5166, or Ms. Katherine N.

Conklin, Phone: 973-724-7674

Proposals shall be submitted to the following point of contact:

A.2.2 Army Contracting Command New Jersey

ACC-NJ-MA, Bldg. 10

Mr. Frank Corradi Telephone: (973)724-5421 or Mr. Austin Alpaugh, Telephone: (973)724-5166

Picatinny Arsenal, NJ 07806-5000

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

A.3 The proposal shall consist of the following:

A.3.1 Each proposal shall be submitted in the English language and consist of and include all of the following:

a. One (1) signed and completed paper copy of the attached Standard Form 1449 (SF 1449) and continuation sheets (all sections of the RFP) 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 Contract

Line Item Numbers (CLINs)/Pricing Matrices in Supplies or Services and Prices, 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

Representations, Certifications, and Other Statements of Offerors. 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.

b. Original and five (5) paper copies and five (5) electronic CD copies of the proposal volumes, as reflected in A.4., 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 a Microsoft (MS) Windows compatible computer. Files shall not contain classified data. The use of hyperlinks in proposals is prohibited. The Price Factor shall be contained on a separate CD from non-price

5 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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 IT Support Services for ARDEC solicitation, all Offerors must submit Reps/Certs data into the System for Award Management (SAM) at https://www.sam.gov/ and provide one (1) hard copy and one (1) electronic copy (on CD) submitted as an .XPS file. Any Offeror that has previously submitted Reps/Certs data into SAM is reminded to update the data prior to submitting with the proposal.

A.4 FORMAT FOR PROPOSALS

A.4.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/Management Factor (Maximum of 50 pages), exclusive of resumes.________

Volume II: Past Performance Factor (Maximum of 25 pages plus up to 5 pages for each major subcontractor, excluding Past_________

Performance Questionnaire Forms)

Volume III: Price Factor (No Maximum)__________

A.4.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 should be created using the Table of Contents feature in Microsoft (MS) Word. MS Word (.doc) files shall use the following page setup parameters:

Margins Top, Bottom, Left, Right - 1

Gutter 0

From Edge Header, Footer 0.5

Page Size, Width 8.5

Page Size, Height 11

A.4.3 Length:

A.4.3.1 Each volume shall be as brief as possible, consistent with complete submission. The page count will be made by counting the pages from left to right, consecutively. Pages that exceed the page limitation will be returned to the Offeror and 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, indices, acronym lists and page dividers (used to separate proposal sections). Pages should not exceed 8-1/2 inches in width by 11 inches in length; foldout pages depicting such items as sketches, factory floor layouts, etc.

may be used, with each fold counted as one additional page. The font used shall not be less than 10 point.

A.4.3.2 Deviation from Requested Format. Request for deviations from the requested format shall be submitted to the Procuring _______________________________

Contracting Officer (PCO) no later than fifteen (15) days after release of the solicitation. 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.

A.4.3.3 The Offeror is responsible for including sufficient details to permit a complete and accurate evaluation of the proposal.

Offerors shall provide a proposal that, at a minimum, addresses those evaluation Factors and Subfactors required in the Evaluation

Factors for Award section of the RFP.

A.4.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.

A.5 SPECIFIC PROPOSAL INSTRUCTIONS

Offerors are responsible for including sufficient details (without reference to cost) 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

6 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 IT Support Services for ARDEC, except for the area of Past Performance. In the response to the RFP, the Offeror shall address the following Factors and Subfactors:

A.5.1 Volume I FACTOR 1: TECHNICAL/MANAGEMENT

A.5.1.1 Subfactor 1 Corporate Knowledge and Experience______________________________________________________

The Offeror shall provide evidence of knowledge and experience of the prime contractor, major subcontractors and affiliates under common control with ARDECs Integrated Data Environment (IDE) its planning, analysis, design, implementation, and system integration.

a. The Offeror shall provide demonstrable evidence of the necessary knowledge, capability and personnel to address and support ARDECs IDE, DoD/Army Information Assurance policies, standards and procedures, Army/DoD software development programs, Armys

Enterprise Resource Planning (ERP) initiative, Enterprise Integration, multiple software development languages and development environments to include but not limited to: SAP applications including Process Integration (SAP PI), SAP Business

Warehouse/Intelligence (SAP BW/BI), SAP Business Objects (SAP BOBJ), SAP Master Data Management, (SAP MDM), SAP Governance, Risk, &

Compliance (SAP GRC), and SAP Enterprise Portal (SAP EP). Additional tools and technology include SharePoint, Oracle 10g, Oracle

WebCenter, ARIS, Windchill, Linux and Windows Servers.

b. The Offeror shall provide evidence of prime contractor experience in the design, development, implementation, and maintenance of robust software solutions that facilitate enterprise knowledge sharing and streamline business processes.

A.5.1.2 Subfactor 2 - Key Personnel and Management Knowledge and Experience_____________________________________________________________________________

The Offeror shall provide demonstrable evidence that it possesses the knowledge, capability, and key personnel to accomplish the stated requirements of this effort. Resumes of proposed key personnel/management shall be provided in regard to key personnel work experience, knowledge, expertise and qualifications as described in Attachment 0003 as they pertain to the Offerors overall technical knowledge and capability to perform the stated requirements of this effort.

A.5.1.3 Subfactor 3 Task Order 0001, eNOVA Support Services_____________________________________________________________

a. The Offeror shall provide evidence of a clear understanding of all features involved in meeting the requirements presented by Task Order 0001.

b. The Offeror shall provide its methods, approach and strategy to meeting Task Order 0001 requirements.

c. The Offerors shall provide the labor categories that would be used in the performance of Task Order 0001, rationale for the use of each labor category, and an explanation as to how each labor category would be used in the performance of Task Order

0001.

A.5.2 Volume II FACTOR 2: PAST PERFORMANCE

A.5.2.1 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.

A.5.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 Government reserves the right to use or not use past performance information submitted by the Offeror based on whether or not adequate recorded past performance information is available in its

Federal databases. Since the Government may not necessarily interview any or all of the sources provided by the Offerors, it is incumbent upon the Offeror to explain the relevance of the data provided. 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:

7 10

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, Commercial and Government Entity (CAGE) Code and Data Universal Numbering System

(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/Contracting Officer 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 e-mail address, telephone and fax numbers.

(f) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, also include Delivery Order Numbers.

(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 the 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.

(b) For all contracts, the Offeror shall provide data on all manufacturing warranty returns. Data shall delineate total number of warranty returns, number of Could Not Duplicate (CND), number of failures attributable to GFE component failures, and number and nature of failures attributable to the Offerors delivered product.

(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 major 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 (Attachment 0002). 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 POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the

Contracting Officer within thirty (30) calendar days of the release of the RFP, to Katherine N. Conklin, Katherine.N.Conklin.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 thirty (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).

A.5.3 Volume III FACTOR 3: PRICE

A.5.3.1 The Offeror shall complete and submit RFP Attachment 0003 titled Labor Category and Rate Table. Offerors shall complete this table which shall contain the Offeror's Firm Fixed Price (FFP) fully loaded labor rates (inclusive of direct labor, indirect expenses and profit, etc.) for each labor category and ordering period. Offerors may not deviate from labor categories listed.

8 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Note: The Government provided estimated labor hours included in the solicitation are for evaluation purposes only and do not obligate the Government to award such labor hours amounts.

A.5.3.2 Other Direct: Travel will be funded on appropriate CLINs and will be evaluated prior to award of individual Task Orders.

A.5.3.3 As a result of market research, it is expected that, after the solicitation is issued, there will be more than adequate competition that will result in more than one basic contract. Assuming multiple awards, task orders shall be competed among

Offerors awarded a contract. Offerors shall propose labor categories in accordance with the resultant contract. The Offeror shall propose FFP rates for task orders at or below the rates contained in their contract.

A.5.3.4 CLIN 0001 IT Services for ARDEC: The Offeror shall provide a completed Attachment 0003 of the RFP, Labor Categories & Rate

Table, which shall contain the Offeror's FFP fully loaded labor rates (inclusive of direct labor, indirect rates and profit) for each labor category. Offerors may not deviate from the labor categories listed in the Labor Categories & Rate Table attachment and defined in the Labor Category Descriptions attachment. Offerors will have the opportunity to propose lower fully loaded FFP labor rates for task orders but may not exceed what is set forth in the basic contract award. Note: The Government provided estimated labor hours per ordering period contained in Attachment 0003, Labor Categories & Rate Table, are for evaluation purposes only and do not obligate the Government to award such labor hours.

CLIN 0002- Travel: Travel, including applicable indirect rates, will be funded on appropriate task orders and will be evaluated prior to award of individual task orders.

CLIN 0003 - Contract Data Requirements List (CDRLs): CDRLs will be negotiated separately prior to award of individual task orders.

The CDRLs (DD1423) shall be not separately priced (NSP), but the Offeror shall be required to complete blocks 17 & 18 on each DD

1423 Form.

CLIN 0004 Contractors may include the cost for Contractor Manpower Reporting in CLIN 0004 as appropriate for each Ordering Period.

CLIN 0004 Contractor Manpower Reporting (CMR) will be determined on an order by order basis and will be included on the individual task orders.

Labor Hours, Travel, CDRLs and CMR shall be evaluated/negotiated on a task order by task order basis.

A.5.3.5 TASK ORDER 0001

A.5.3.5.1 The Offeror shall provide a proposal for Task Order 0001 which includes the labor categories, FFP fully loaded labor rates, hours, extended amounts for each labor category and a total price for the task order in order for the Government to verify the fully loaded labor rates proposed. Travel is not anticipated for the Task Order 0001. An offer may be rejected if the Offerors proposed labor rates are higher than the rates proposed under CLIN 0001 for Ordering Period 1 (Labor Categories and Rate Table, Attachment 0003). Labor categories cannot deviate from the labor categories provided by the Government in Attachments 0003 (Labor

Categories and Rate Table) and 0004 (Labor Category Descriptions) of the RFP. Offerors may propose fully loaded labor rates lower than the rates proposed under CLIN 0001.

A.5.3.5.2 Task Order 0001: The Government will perform a price analysis in accordance with FAR 15.404-1(b) utilizing the Offeror's proposed price for Task 0001 Base Year and Option Year. The Offeror shall provide a total proposed price for Task Order 0001 Base

Year and Task Order 0001 Option Year. The proposed prices will be evaluated separately from CLIN 0001.

A.5.3.6 Price Inconsistencies: A proposal is presumed to represent an Offeror's best effort to respond to the solicitation. Any inconsistencies, whether real or apparent between promised performance and price should be explained in the proposal. Any significant inconsistencies, if unexplained, raise a fundamental issue of the Offeror's understanding of the nature and scope of work required and his/her financial ability to perform the contract, and may be grounds for rejection of the proposal.

A.5.3.7 Unbalanced Pricing: Offerors are cautioned against submitting an offer that contains unbalanced pricing. Unbalanced pricing exist when, despite an acceptable total evaluated price, one or more of the proposed FFP fully loaded labor rates are significantly over or understated as indicated by the application of cost or price analysis techniques. In accordance with FAR 15.404-1(g), a proposal may be rejected if the PCO determines that the lack of balance poses an unacceptable risk to the Government. If the

Offeror's proposed FFP fully loaded labor rates appear unbalanced when comparing them from ordering period to ordering period, the

Offeror shall provide documentation, including calculations and supporting rationale, explaining the apparent unbalanced pricing.

LABOR CATEGORY AND RATE TABLE (is found at Attachment 0003 to the RFP)

TASK ORDER 0001

Offerors shall submit a price proposal for Task Order 0001. It is the intent of the Government to award this task immediately following the basic award, however the price of Task Order 0001 will be evaluated separately after the basic awardees are determined.

9 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The proposed pricing for Task Order 0001 shall use the same or lower labor rates submitted by the contractor in the Labor

Category and Rates Table for Ordering Period 1 only. Offerors may not deviate from categories listed in the Labor Category and

Rates Table. The proposal for Task Order 0001 shall include travel and any other costs deemed appropriate by the offeror in addition to the proposed hours. The labor hours and rates need to be broken out separately in order for the Government to verify the labor rates used.

A.6. VOLUME IV SOLICITATION, OFFER AND AWARD DOCUMENTS AND CERTIFICATIONS/REPRESENTATIONS

A.6.1 Each Offeror shall complete (fill-ins, signatures and any attachments or amendments to the RFP) the solicitation sections as indicated in the Standard Form 1449 (SF 1449) Solicitation/Contract/Order for Commercial Items. An authorized official of the firm shall sign the SF 1449 and all certifications requiring original signature. An Acrobat .PDF file shall be created to capture the signatures for submission.

*** END OF NARRATIVE L0001 ***

10 10