HTC711-13-R-D003-0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

Amendment 0004 is issued to update Attachment 7 to include labor category descriptions for Systems Architect Level 4-Master, Systems Architect Level 3-Senior and Security Engineer Level 4-Master. In addition, the closing date of the remaining Technical, Staffing and Pricing volumes is extended to 24 July 2013 at 2:00p.m. CDT.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 8

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

16C. DATE SIGNED

BY 18-Jul-2013

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

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HTC711-13-R-D003

X 9B. DATED (SEE ITEM 11)

12-Jun-2013

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

18-Jul-2013

CODE

USTRANSCOM-AQ - HTC711

508 SCOTT DR

SCOTT AFB IL 62225-5357

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HTC711-13-R-D003

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 22-Jul-2013 02:00 PM to 24-Jul-2013 02:00 PM.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

L-1. Requests for clarification and/or information concerning this solicitation shall be submitted in writing referencing the PWS/RFP or attachment by Section, Page, and Paragraph to the address below:

USTRANSCOM/TCAQ-DPO

508 Scott Drive Bldg. 1900W, Ste 1123 Scott AFB, IL 62225 Attn: Ms. Jen Knobeloch and Ms. Lisa Gross Solicitation HTC711-13-R-D003 E-mail: jennifer.knobeloch@ustranscom.mil and lisa.gross@ustranscom.mil Fax No.: 618-220-6248

a. No requests for clarification will be provided in response to Offeror-initiated telephone calls. All such requests must be made in writing via e-mail and submitted to the above address. Written inquiries will be answered in writing and provided to all Offerors. However, time may not permit requests to be answered if received by the above addressee within 10 calendar days of the due date for offers as specified in this solicitation.

b. Use of Non-Government Advisors

(1) The Government has contracted with The MITRE Corporation, St Louis Operations, 505 Corporate Center Drive, Shiloh, IL 62221 to provide advisory assistance to the evaluation team. Contractor personnel will have access to Contractors’ proposals. Submission of your proposal is considered to be your written consent to release of proprietary, confidential or privileged commercial or financial data included in your proposal to MITRE personnel.

All Contractor personnel participating on the evaluation team will sign a non-disclosure certificate prohibiting them from releasing proprietary information.

(2) The contract(s) under which non-Government technical advisors will provide support to this source selection include an Organizational Conflict of Interest (OCI) clause. The OCI clause requires the companies and their individual non-Government advisors to protect Offeror proprietary data and Government evaluation information and prohibit the companies from otherwise participating as an Offeror, a subContractor, or as a consultant to an Offeror/subContractor in relation to this acquisition.

c. Offerors’ proposals must be valid for a period of time not less than 180 days from the original submission date.

Offerors shall enter ‘180’ in Block 12 of the SF33.

L-2. PROPOSAL SUBMISSION REQUIREMENTS

(a) RFP Submissions – Proposals shall be submitted according to the following schedule. Electronic copies of the proposal shall be submitted to Ms. Jennifer Knobeloch and Ms. Lisa Gross, via the e-mail addresses listed in L-1, in a format that can be read and edited by Microsoft (MS) Word 2000, MS Excel 2000, MS Project 2000, MS Power

Point 2000 (or newer versions, thru MS Office 2007), and Adobe Acrobat (PDF). In the event hard copy and soft copy content conflict, soft copies will take precedence over hard copies. For submission purposes, electronic copies will be considered the official copy.

(1) Proposal Volume 3 shall be received by 2:00 pm (Central Standard Time) on 15 July 2013 in SOFT COPY ONLY. Proposal Volumes 1, 2, and 4 shall be received by 2:00 pm (Central Standard Time) on 24 July 2013 in BOTH soft and hard copy.

(2) The Past Performance Questionnaire shall be submitted via fax or e-mail to the Contract Specialist, Jennifer Knobeloch and Contracting Officer, Lisa Gross at the e-mail addresses or fax number listed in Section L-1 above.

(b) Hand Carried Proposals - ACCESS TO SCOTT AFB FOR DELIVERY OF HAND CARRIED PROPOSAL.

Offerors are cautioned that when hand carrying proposals to the depository (508 Scott Drive, Building 1900W, Ste 1123, Scott AFB, IL 62225) those individuals not affiliated with this installation must obtain visitors’ passes prior to entrance. The Shiloh gate has been designated as the “Visitors Center.” Some delays can be anticipated for visitors to process through the “Visitors Center” and Offerors should allow sufficient time to obtain visitors’ passes in order that they may arrive at the depository to submit their proposal within the time-frame specified by the Contracting Officer. Late proposals will be processed in accordance with the provision entitled “Submission, Modification, Revision and Withdrawals of Proposals”, FAR 52.215-1(c)(3).

L-3. PROPOSAL PREPARATION INSTRUCTIONS

1. Guidelines

(a) The Offeror’s response to this solicitation shall include a proposal. The proposal (offer) as the term is defined and used in Federal Acquisition Regulation (FAR) 2.101 shall consist of RFP sections A through K (excluding Section B), including all documents, and attachments that are incorporated herein and made a part of the contract. In addition to its offer, each Offeror must provide “Past Performance Information”. Past Performance Information consists of contracts of similar scope and size to this acquisition, a Past Performance Log, and Past Performance Questionnaires completed on each contract.

(b) This section provides general guidance for preparing proposals and Past Performance Information, as well as specific instructions on the format and content of proposals and Past Performance Information. Offerors’ proposals and Past Performance Information must include all data and information requested by this solicitation and submitted in accordance with these instructions. Non-conformance with the specific organization, content, and page limitations may result in mis-evaluation of proposals; or depending on the magnitude of the non-conformance, the proposals may be eliminated from further consideration. Telegraphic offers will not be considered.

(c) The proposal and Past Performance Information shall be clear, concise, and include sufficient detail to enable the Government to fully evaluate and determine the Offeror’s capability to comply with (i.e., meet or exceed) all requirements identified in this solicitation. The proposal information should not simply rephrase or restate the PWS, but should provide convincing rationale to address how the Offeror intends to meet the requirements of the solicitation. In responding to the specific tasks set forth in the solicitation, Offerors are encouraged to highlight the unique features (strengths) of their approach to meeting/exceeding PWS requirements; especially those which will enhance system capability and cost effective evolution beyond minimum requirements.

2. Organization/Number of Copies/Markings

(a) Organization - The proposal shall be structured into four (4) volumes with maximum page limits as indicated below. Each volume shall be written to the greatest extent possible on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other parts of the proposal. Each volume shall contain a glossary of all abbreviations and acronyms used within that volume, with an explanation for each. The Offeror shall ensure that no pricing data is included in the Technical Capability, Volume 1. The maximum page limit for each volume includes all text pages, table of contents, title page, appendices, tables, foldouts, graphs, and other types of illustrative material. Glossaries do not count against the page limits for the respective volumes. The page limitations listed below are absolute maximums and not planning goals. Excess pages exceeding the maximum limits will not be read or considered in the evaluation. It is entirely acceptable to submit volumes with fewer pages than the maximum limits.

(b) Number of Copies/Markings

VOLUMES 1 - 4 PROPOSAL PAGE LIMIT COPIES

Volume 1 – Technical Capability 100 Pages** 6 hard + 1 soft copy

Volume 2 – Staffing Approach 100 Pages** 6 hard + 1 soft copy

Volume 3 - Past Performance (e-mail/fax submission only)

1 soft copy Section 1 – Past Performance Log Section 2 – Past Performance Questionnaire ** **e-mail/fax submission only

Volume 4 –Price Proposal 6 hard + 1 soft copy

Section 1 – Sections A-K (excluding Section B), OCI Mitigation Plan, Administrative Information, and Backup Documentation

Section 2 – Attachment 6, Pricing Matrix Template

**NOTE: The total page limit for the Technical Capability and Staffing Approach is 100 pages COMBINED.

A complete response to this solicitation shall consist of the required number of copies of the volumes as specified above.

(c) Pages, Typing, and Page Numbering - The contents of the above volumes shall be typed on 8-1/2 by 11 inch white paper, single side, with one inch margins on all sides. Times New Roman 12 point font shall be used except for figures and diagrams, where small is acceptable as long as it is readable. Foldouts are acceptable and will be counted as multiples of 8.5x11 depending on size. Anything between 8.5x11 and 11x17 counts as two pages, anything between 11x17 and 11x25.5 counts as three, 17x22 counts as four, etc.. All page numbers shall be sequential throughout the volumes and at the bottom of each page. Each page shall identify the Offeror in the upper right hand corner. Charts, attachments, etc., should be page numbered and may have additional identification such as a chart or attachment number.

(d) Volume Markings. Volumes should be bound in a three-ring loose leaf binder with allowances made for space to facilitate potential page changes. Staples shall not be used. A cover sheet shall be applied to each binder, clearly marked as to volume/part, title, RFP identification, and Offeror's name. Volumes 1 and 2 may be combined into one binder. Volume 4 shall be in its own binder. Offerors will submit a total of 12 binders (6 containing Technical and Staffing and 6 containing Price).

3. Requests for Information

The Government will make the final determination as to whether a proposal is acceptable or unacceptable, and may accept a proposal as initially submitted without requesting further information from any Offeror. However, should the Government request additional information (via clarification requests/evaluation notices), the Offeror shall include the question(s) with their written response. The Government may request additional information from any Offeror at any stage of the acquisition for the purpose of clarification and for determining whether discussions should be conducted with the Offeror. The determination to request such additional information from any Offeror, or to conduct further negotiations with any Offeror, shall be at the sole discretion of the Government.

4. Proposal Changes

Offerors shall update proposals (offers) throughout the negotiation (FAR 15.306(d)) process based on such things as Government clarification and evaluation notices issued to Offerors. Regardless of the number of proposal updates submitted, integrity and clarity of each proposal must be maintained. All proposal updates must meet the following criteria:

(a) Changes to proposal data shall be submitted as complete page changes for each page on which a change occurs. A solid black line in the right hand margin of the changed page shall be used to identify the lines of text, data, or graphics changed.

(b) Each change page will contain a revision number and date of each affected page. Changes shall be numbered sequentially, beginning with Change 1.

(c) Change pages must be submitted which maintain the separation of cost and pricing data as specified for the original proposal submission.

5. Proposal Content:

The Offeror's proposal shall respond to all requirements of this solicitation clearly and completely. It is the Offeror's responsibility to ensure information supplied by its subcontractors is accurate and unambiguous. Offerors who fail to respond adequately, or fail to clarify or correct their proposals after having been notified by the Government, may be eliminated from the source selection process without further discussions. Promotional or marketing brochures submitted by the Offeror will not be evaluated.

L-4 FACTORS and SUBFACTORS

The Government intends to award a single-award ID/IQ from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The following factors shall be used to evaluate offers:

(1) TECHNICAL CAPABILITY

(2) STAFFING APPROACH

(3) PAST PERFORMANCE

(4) PRICE

This is a competitive best value source selection in which competing offerors’ technical capability is considered significantly more important than staffing and past performance (which are equal in importance). When combined, the non-price factors are approximately equal to price.

Award will be made to the offeror who is deemed responsible in accordance with the Federal Acquisition Regulation, as supplemented, whose proposal conforms to the solicitation requirements (to include all terms, conditions, representations, certifications, and all other information required by this solicitation), and is judged, based on the evaluation factors, to represent the best value to the Government. This may result in an award to a higher rated, higher priced offeror, where the decision is consistent with the evaluation factors. However, the Government will not pay a price premium that it considers to be disproportionate to the benefits associated with the proposed margin of service superiority. Therefore, the Government will award a single contract to the offeror considered to be the best value, all factors considered, given their relative order of importance.

The Government reserves the right to award no contract at all depending on the quality of the proposals submitted and availability of funds. The Government may conduct discussions with offerors. However, the Government reserves the right to not conduct discussions, written and/or oral, with offerors if determined to be in the Government’s best interest. The Contracting Officer may limit the competitive range for purposes of efficiency.

Factor 1: Technical Capability:

Sub-factors are listed in descending order of importance:

Subfactor 1: Technical Approach - The Offeror shall submit a sound plan for accomplishing the requirements of the PWS. The plan should provide a logical approach that ensures timely support for all tasks as described in the PWS.

Subfactor 2: Enterprise Architecture Development (Task 2) – Offerors shall submit an integrated model subset addressing the following:

(a) The Offeror shall develop and submit Department of Defense Architecture Framework (DODAF) v2.02 models based on the attached use case (Attachment 3) and applicable reference listed in sub-paragraph (b), below. Models required for submission:

1. OV-5a, Operational Decomposition Tree

2. OV-6c, Event-Trace Description (Developed using BPMN)

3. AV-2, Integrated Dictionary

(b) Reference Materials. The following reference materials will be used by the evaluation team to review submissions under this subfactor:

1. DODAF, Version 2.02

2. Enterprise Architecture Planning, Developing a Blueprint for Data, Applications, and Technology, Steven H. Spewak, and Steven C. Hill A Wiley –QED publication

3. The Practical Guide to Business Process Reengineering Using IDEF0, Clarence Feldmand, Dorset House Publishing, 1998

4. BPMN Method & Style, Bruce Silver

Subfactor 3: Enterprise Engineering Support (Task 5) - The Offeror shall provide a straw man (notional) representation of the deliverables showing their ability to produce engineering tasks under PWS paragraph 1.3.5.1 through 1.3.5.5.2. The Offeror shall provide one (1) example for each of the five (5) areas listed in the PWS paragraphs. The five examples shall collectively demonstrate an:

(a) understanding of design and implementation information services using SOA in a virtualized environment. This includes design and allocation of services to IaaS, PaaS, and SaaS layers, infrastructure versus application support services, use of software frameworks, and modern software and system architectures based on J2EE and related designs.

(b) understanding of designing and constructing SOAP-based information services using XML, and related documentation for consumers of the services.

(c) understanding of security related to information services in a SOA environment by describing a sample of security risks they have encountered in designing and building information services in a SOA environment and how those risk were mitigated.

(d) understanding of service designs in XML (WSDLs) and any associated documentation designed to support consumption of the services by a client system or application.

(e) understanding of design, development and deployment of mobile applications, including the risks and design factors (e.g., UX design, SOA consumption, local data storage factors, master device management & provisioning) associated with leading mobile device platforms (iOS, Android, Windows), and their experience with related development languages and tooling.

(f) understanding of use of mash-up and virtual database technologies to fuse disparate data sources within a complex enterprise environment to support SOA. Risks and mitigations of their approach(es) shall be discussed.

(g) understanding of design and development of data analytics and dashboard applications within a SOA environment, including risk factors and mitigations related to performance and data quality when dealing with large data potentially distributed source sets.

(h) effective use of design and development of reference implementation and micro-architecture frameworks and libraries to guide, secure and improve efficiency of enterprise development activities through reuse.

(i) understanding of integration of portal frameworks and visualization technologies in a distributed, virtualized environment.

(j) proven performance in development of disciplined project management and engineering artifacts:

1. Configuration Management

2. Requirements Management

3. Capability Development Documents

4. System Requirements Documents

5. Security Certification IAW DIACAP standards and processes

6. System Administration Guides

7. UML-based Artifacts (showing detailed software architecture)

8. Security Vulnerability Testing Management

(k) understanding of software assurance by describing processes, procedures, and tooling used to conduct development in a secure facility and protect critical IP from infiltration or exfiltration, design and develop secure software comprising information services and applications, test and identify software security flaws, and securely deliver software and other developmental artifacts to the Government. The offeror shall demonstrate as part of the response their explicit understanding of security factors related to constructing and operating information services in a SOA environment by describing a sample of security risks they have encountered in designing and building information services in a SOA environment and how those risk were mitigated. Understanding of continuous integration and automated regression testing procedures and tooling shall also be demonstrated.

Subfactor 4: Test Management (Task 5) - The Offeror shall provide a straw man (notional) representation of the deliverables showing their ability to produce items a-d below.

a. schemas

b. a data management plan

c. a test management plan

d. a performance/load plan

Reference Material (Test Management): The evaluation team will use Definitive XML Schema, Priscilla Walmsley, publication 2002 to evaluate proposal submissions provided under this subfactor.

Factor 2: Staffing Approach:

Offerors are required to submit their staffing approach as reflected in a personnel matrix which identifies the personnel resources given the Offeror's approach to performing the PWS tasks. The matrix shall correlate each labor category to each PWS task and sub-task (if applicable). Offerors shall include an organizational structure which shows how the team will be organized and identifies the labor category of personnel resources assigned to meet the requirements by function (Enterprise Architecture, Enterprise Engineering, Enterprise Data and Tools) as described in the PWS.

Factor 3: Past Performance:

Offerors shall submit four references of past performance. The purpose of the past performance evaluation is to allow the Government to assess the offerors’ ability to perform enterprise engineering, enterprise architecture, enterprise data, and tools. Past performance questionnaires submitted by the offerors’ Points of Contact (POCs), Past Performance Information Retrieval System (PPIRS) and other information independently obtained from Government or commercial sources, will be used by the Government to assign a confidence assessment on each offeror.

Subcontractor consents (if applicable). Past performance information pertaining to a subcontractor cannot be disclosed to the prime offeror without the subcontractor's consent. With your proposal response, provide a letter from your principal subcontractor(s) that will perform major or critical aspects of the requirement consenting to the release of their past performance information to the prime contractor.

Using the past performance log, Attachment 4, the offeror should provide the Company or Agency name, Point of Contact, Phone Number, and Email for each reference listed. The Government may contact those agencies and individuals to verify information and/or obtain additional information.

The offeror shall complete all applicable information in page one of the Past Performance Questionnaire, Attachment 5. The Government will evaluate the quality and extent of the offerors past performance deemed relevant to the requirements of this RFP. The Government reserves the right to use information submitted by the offeror and obtained from other sources, such as Government offices and commercial sources to assess performance.

Maximum of four individual contract Past Performance Questionnaires will be accepted by the Government from each offeror. The offeror shall send out the Past Performance Questionnaires to each reference identified. The responsibility to send out the Past Performance Questionnaires rests solely with the offeror; whereas, it shall not be delegated to any other entity. Once the questionnaires are completed, the information therein shall be considered sensitive and shall not be released to the offeror. The Past Performance Questionnaires shall be sent directly to the Government from the respondent. If more than one questionnaire is received on any of the four contract examples, only the first one received will be accepted. The evaluation of past performance information will take into account the past performance information regarding key subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the instant acquisition.

Factor 4: Price

Offerors shall price the base period and all option periods using the template pricing matrix, which will be Attachment 6 to the solicitation. Offerors shall provide a proposed labor rate for personnel proposed. Offerors are not required to complete Section B of this solicitation.

(End of Summary of Changes)