W9133L-16-R-0004-0001.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

The purpose of this amendment is to:

1) extend this solicitation,

2) answ er industry questions, and

3) incorporate changes to the solicitation due to answ ers.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 71

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

16C. DATE SIGNED

BY 01-Dec-2015

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 W9133L-16-R-0004

X 9B. DATED (SEE ITEM 11)

16-Nov-2015

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

01-Dec-2015

CODE

NGB-ZC-AQ - W9133L

111 SOUTH GEORGE MASON DR

BLDG. 2, 4TH FLOOR

ARLINGTON VA 22204-1373

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W9133L-16-R-0004

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 03-Dec-2015 04:30 PM to 07-Dec-2015 04:30 PM.

The following have been modified:

ADDENDUM TO 52.212-1

Instruction to Offerors

1. PROPOSAL SUBMITTAL AND INQUIRIES

(1) Proposals shall be submitted prior to the closing date and time identified on the SF 1449 to the following address:

NGB-AQ

Attn: Major Jonathan R. Lehmann 111 South George Mason Dr Bldg. 2, 4th Floor Arlington, VA 22204-1373

(2) Electronic submissions via email or fax will not be accepted. Offers shall be mailed through a commercial/Government carrier or hand carried.

(3) Solicitation questions may be submitted to POC listed above via email, no later than 4:00 PM Eastern Time, 25 November 2015. Offerors shall submit questions in a MS Excel file following a format similar to the table below:

Table 1 – Questions Format Question

No.

Reference Question Category

Question

# RFP, SOW or Attachment, section, and page number

Contract or Technical

Question

The Offeror shall note in the email subject line the “Solicitation W9133L-16-R-0004 and Request for Clarification.” Responses to questions will be provided by the Government as soon as possible via a solicitation amendment on FedBizOpps. If the Government issues an Amendment to the solicitation, Offerors must acknowledge solicitation Amendment(s) to be considered responsive to the RFP.

Any information provided to one Offeror concerning this solicitation will be furnished promptly to all other prospective Offerors as an Amendment of the solicitation if the lack of that information would be prejudicial to any other prospective Offerors.

2. GENERAL INSTRUCTIONS

(1) The selection of a source for award will be conducted utilizing source selection (negotiated) procedures as delineated in FAR Part 15.3. Offers will be evaluated using the criteria under FAR Clause 52.212-2 Evaluation – Commercial Items and the Addendum to 52.212-2.

Noncompliance with the Request for Proposal (RFP) requirements may hamper the Government's ability to properly evaluate the proposal and may result in elimination of the proposal from further consideration for contract award.

(2) The Offer. The submission of the documentation specified below will constitute the Offeror's acceptance of the terms and conditions of the RFP, concurrence with the PWS, and the proposed contract type.

(3) It is the Government’s intention to award without discussions. Offerors are encouraged to present their best proposal and prices in their initial proposal submission. However, IAW FAR Part 15.306, should discussions become necessary, the Government reserves the right to hold discussions. If this occurs, a competitive range will be determined and Offerors notified. The competitive range may be limited for purposes of efficiency IAW FAR Part 15.306(c)(2).

(4) The Proposal Preparation Instructions (Para. 3.) as set forth below prescribe the format for the proposal and describe the approach for the development and presentation of proposal data.

These instructions are designed to ensure the submission of necessary information to provide for the understanding and comprehensive evaluation of proposals.

(5) In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

(6) If an Offeror believes that the requirements in these instructions contain an error, an ambiguity, omission, or are otherwise unsound, the Offeror shall immediately notify the Contracting Officer in writing with supporting rationale.

(7) All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

(8) Debriefings. The Contracting Officer will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505. The Contracting Officer will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

3. PROPOSAL PREPARATION INSTRUCTIONS

(1) Offeror’s proposal shall consist of five (5) separate volumes: I. Technical, II. Past Performance, III. Management, IV. Price, and V. Solicitation, Offer and Award Documents and Certification/ Representations.

(2) Proposal Format:

a) Offerors shall submit an original and the number of copies listed in paragraph 3. (2).c.

b) b. Exceptions. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors and their sub-factors. Failure to meet a requirement may result in an offer being ineligible for award. If the offeror finds it necessary to take exception to any of the requirements specified in this solicitation, the offeror shall clearly identify the applicable Volume and exceptions with a complete explanation of why the exception was taken, what benefit accrues to the Government (if any), and its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Offerors are cautioned that taking an exception may render the offer ineligible for award. This information shall be provided in the format below.

Table 2 – Solicitation Exeptions

Solicitation Document

Page/ Paragraph Requirement/ Portion

Rationale & Impact

Section B, PWS, Section L&M, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe The rationale and impact of the exception

c) The offeror’s proposal shall consist of five (5) volumes. The Volumes are I – Technical, II – Past Performance, III – Management, IV – Price, and V – Solicitation, Offer and Award Documents and Certifications/Representations. Files shall not contain classified data. The use of hyperlinks in proposals is prohibited.

Offerors are cautioned that “parroting” of the Technical requirements or the PWS with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked.

4. PROPOSAL SUBMISSION REQUIREMENTS

a) Each volume shall be submitted in a separate three-ring binder. Any pages that are changed (as a result of negotiations or proposal revisions) should be of a different color and have changed information clearly marked by a vertical line in the right margin of the page. The revised pages shall be dated. Each binder shall be clearly labeled with its Title and a copy number (e.g., copy 1 of 5).

b) Printing should be single spaced. Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial or New Times Roman fonts are required. Tables and illustrations may use a reduced font size no less than 8-point and may be landscape.

c) The proposals shall be organized into five (5) volumes. Each volume of the proposal should be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification and the Offeror's name. The same identifying data should be placed on the spine of each binder.

All text shall be single spaced and printed black on white paper (black and white requirement does not apply to graphics, photos, etc., Company stationary and logo’s are acceptable). Printing shall be easily readable (12-pitch type or 10 point proportional spacing.) Cross-references should be utilized to preclude unnecessary duplication of data between sections.

d) In addition to submitting hard copies of the proposals, digital copies shall be provided on

CD-ROM disk in Microsoft Office format and/or PDF. File names to be “Company Name – Initial” for the first submission. File name of later submissions (if necessary), shall be “Company Name – Revision X’ with X indicating the number of the revision. If files are compressed, they must be self-extracting archives (no software required to decompress). If files contain links, the links must be intact and maintained through all revisions. Additionally, spreadsheets must be easily traceable. None of the files submitted shall have any read/write/password protection. Page limitations are as follows:

PRINTED DIGITAL MAXIMUM

VOLUME TITLE COPIES COPIES PAGES

I – Technical Original + 3 1 125* II – Past Performance Original + 3 1 25 III – Management Original + 3 1 125 IV – Price Original + 3 1 N/A

V – Solicitation, Offer and Award Documents and Certification/

Representations Original + 3 1 N/A

NOTE: Pages that exceed the required page limitations will not be evaluated. Additional pages over the maximum allowed will be removed or not read and will not be evaluated by the Government.

*Manpower charts are excluded from the page count.

e) Proposal Limitation. The proposal shall not exceed the limits stated above. If the page limits are exceeded, the pages in excess of the limit shall be removed and returned, unread, to the Offeror. The Government will not accept any changes to the contractor’s proposal after the closing date of the solicitation (See FAR 15.208 for further information regarding late proposals). If discussions become necessary, page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

f) Page Limit Includes: All appendices, charts, graphs, diagrams, tables, photographs, drawings, etc.

g) Page Limit does not include the Executive Summary, covers for volumes, tables of contents, glossary of abbreviations and acronyms, indices, title pages, cross reference indices, and section dividers/tables if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. They will be counted if they contain any other information, i.e., diagrams, extraneous data, etc. Pages marked “This page intentionally left blank” will not be counted.

h) What Counts As A Page? A page shall be an 8 ½ X 11” sheet of paper. When both sides of a sheet display printed material, it shall be counted as two pages. Letter size and spacing requirements for illustrations and tables can be at the discretion of the Offeror but must be easily readable. Fold-outs will be counted as the appropriate number of pages based on an 8 ½ X 11” sheet of paper. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins. The Contractor shall number each page in order to eliminate any confusion. In the event the contractor creates an ambiguity in their numbering of pages, the Government may exercise its own discretion in counting pages.

i) Indexing. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

j) Glossary of Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each.

5. PROPOSAL FILES

a) Content Requirement. All information shall be confined to the appropriate file. The offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file.

Proprietary information shall be clearly marked. The following shall be included in the Narrative discussion:

(i) VOLUME I – Technical.

Volume I – Technical. The Technical Proposal shall consist of a written narrative that addresses the following subfactors:

Subfactor 1: Maintenance Subfactor 2: Programming Subfactor 2: Troubleshooting

Volume I shall have NO pricing information included. The Technical Part shall not contain the name of the company, subcontractors/team members or individual/persons names and shall identify their firm by DUNS number one time only on the cover page.

Volume I shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. Legibility, clarity and coherence are very important. Your responses will be evaluated against the criteria defined in Addendum to 52.212-2, Evaluation Factors for Award. The proposal shall not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Statements that the offeror understands, can, or will comply with the Performance Work Statement; statements paraphrasing the Performance Work Statement or parts thereof (including applicable publications, technical data, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable.

Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the offeror's proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

Volume I shall, at a minimum, be prepared in a form consistent with the evaluation criteria for award set forth in the Addendum to 52.212-1 Instructions to Offerors of this solicitation. The section shall be prepared in an orderly format and in sufficient detail to enable the Government to make a thorough evaluation of the contractor’s technical competence and ability to comply with the contract task requirements specified in the Specifications. Volume I shall be organized according to the following general outline:

(1) Section 1 – Maintenance. The offeror’s proposed Maintenance. The Subfactor 1 portion of the proposal shall address the following as a minimum:

Maintain the operational readiness of FTSMCS and all its applications, modules, and servers.

Data maintenance and development of FTSMCS data architecture, data modeling, data integration, data standardization, data quality assessment and repair/refinement of data.

Software maintenance, to include definition and maintenance of an overall FTSMCS system, definition and construction of common system components and services, software technology assessments, technology insertions, software testing and integration.

Maintenance and enhancement of FTSMCS system and sub-applications, to include application software, databases, historical data repositories, forecasting models, expert systems, and web-based applications. System Maintenance, to include the creation of software development repositories and the definition and maintenance of a common software development environment.

System Compliance with DoD and NGB Information Technology and Information Assurance requirements. Must meet 98% Information Assurance (IA) requirements.

Experience using Vulnerability Management System (VMS) to manage Information Assurance Vulnerability Alert (IAVA) vulnerability compliance (DISA DECC requirement)

(2) Section 2 – Programming. This subfactor evaluates the offeror’s

Programming. The contractor will provide information that substantiates:

Technical skills include systems analysis, system design, (both structured and object oriented), modeling, requirements determination and expert system and web development. Examples of previous work will help evaluate this criteria.

FTSMCS support requires a variety of skill sets, to include Structured Query Language (SQL) Server, Internet Information Server, Analog Signal Processing (ASP), ASP.net, Oracle, and Transact-Structured Query Language (T-SQL).

(3) Section 3 – Troubleshooting. This sub-factor evaluates the offeror’s Troubleshooting. The offer will provide information to substantiate the following:

System shall be operational within 24 hours of going down

The contractor shall provide, maintain, and support the ARNG with an innovative automated tool in the management of manpower, personnel, and resources. This involves promoting decision making processes by making accurate and timely resource, personnel, and manpower information readily available to the ARNG staffs and decision makers in a variety of useable and understandable forms. National Guard experience is required.

Years of database structuring and reorganizing and repair should be documented and will be weighed. Minimum 2 years’ experience with a national database required.

(ii) VOLUME II – Past Performance. This volume shall contain past performance information regarding similar contracts. This volume shall not exceed 25 pages plus five pages for each major subcontractor, excluding Attachment 1 Past Performance Questionnaire Forms.

Offerors shall submit all Government and/or commercial contracts for the prime offeror and each major subcontractor in performance or awarded during the past three years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation. Relevant efforts are defined as services/efforts that are the same as or similar to the effort (as compared to NAICS code 541511) required by the RFP. Data concerning the offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. The Offeror shall also submit the written consent of its major subcontractors to allow the disclosure of its subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors for their past performance to be considered. This volume shall be organized into the following sections:

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

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

(c) Government’s technical representative/COR and current email 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 number.

(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, include Delivery Order Numbers.

(g) Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Material (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 or 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, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP.

(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 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 offeror’s delivered product.

(3) Section 3 – Subcontracts. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government PWS subparagraph number. This includes all subcontractors who will be providing critical hardware/services or whose subcontract is for more than 10% of the total proposed cost/price. This section will further include written consent of major subcontractors to allow the disclosure of their subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors

(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. Letters of Commitment shall be included in the proposal for these employees in order to be considered.

(5) Past Performance Questionnaire. For all contracts identified in Section 1, Contract Descriptions, a Past Performance Questionnaire must be completed and submitted.

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 Office no later than the proposal due date, to (insert email address). The offeror shall e-mail to the Contracting Officer a list of all the POC’s who were sent a questionnaire. The Government must receive this list no later than the proposal due date. 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; and Date E-Mail to POC (month/day).

(6) Submissions. Offerors are discouraged from providing points of contact with another contractors’ facility, i.e., in case an offeror (or one of his/her team members) is in a subcontract with another contractor who has submitted a proposal on the same requirement. Offerors shall provide and submit the prime contract number and all Governmental agency points of contact (POC) in lieu of subcontract numbers or prime contract POCs in situations as described above.

(7) Small Business Participation Past Performance. All Offerors shall submit information substantiating the Offerors’ past performance in complying with FAR 52.219-8, “Utilization of Small Business”, maximizing opportunities for U.S. small business subcontractors. Offerors shall also provide a statement indicating whether any negative information has been reported in the past six years concerning the Offerors’ past compliance with FAR 52.219-8. If any such negative information has been reported, the Offeror may submit explanations or comments responding to such negative information. Offerors with no prior contracts containing FAR 52.219-8 shall certify the same.

(iii) VOLUME III – Management. The volume shall be organized into the following sections:

(1) Section 1 – Key Personnel. The offeror’s proposed Key Personnel. The Subfactor 1 portion of the proposal shall address the following as a minimum:

Demonstrated experience planning, directing, and managing tasks as called for within the

PWS

Demonstrated experience in conducting subject matter research and preparing research analysis documentation relevant to core task areas within the PWS

Demonstrated experience in business process development and improvement. The Offeror shall also demonstrate that all key personnel (prime or subcontractor employees) proposed (or equal or better) are available for contract performance at the start/effective date of award.

(2) Section 2 – Quality Control. This subfactor evaluates the offeror’s Quality Control. The contractor will provide information that substantiates:

•Ability to maintain and modify database on an ongoing basis

•Ability to support administrative/reporting duties to include tracking

•Ability to manage the support personnel and interface with the government personnel in daily operations

(iv) VOLUME IV – Price – This volume shall consist of all information, required to support proposed costs and prices. Certified cost and pricing data are not currently required.

There are no page limitations for this volume.

(1) The offeror shall ensure that the information submitted in this volume is consistent with and fully supports the amounts set forth in the SF1449 and continuation sheets.

(2) The proposal shall set forth a summary of the total estimated costs by cost element and shall provide a breakdown of the proposed estimated costs of each CLIN separately, including all direct and indirect charges and fees. Cost summary spreadsheets shall be provided for the base effort and each option year. All documentation furnished to support the cost summaries are to be provided in a format chosen by the offeror that is easily traceable to the cost summary sheets. No Government template will be provided or required.

(3) Estimated phase-in costs shall be included separately in the offerors cost proposal.

(4) The specific direct labor rates utilized to price the proposal must be identified in the cost and pricing proposal only. The proposal shall set forth a complete breakdown of the direct fully burdened rates by category and the rationale thereof. Provisions for overtime and shift differential charges shall be clearly addressed on a per-hour basis. Bid codes (applicable codes used to identify a labor category in the offerors accounting system), employee names and/or other documentation (such as assigned letter of commitment for key personnel not currently employed by the offeror) to support the rates proposed shall be provided.

Letters of commitment shall clearly identify the prospective employees’ agreed-to salary/hourly rate and other pertinent conditions of employment. The same detailed support data shall be furnished for all major subcontractors.

(5) For evaluation purposes only and in determining probable cost for options in the out-years, wage determination rates shall be escalated 3 percent per year.

However, if the offeror substantiates higher wage rates and justifies different escalation factors, those wage/escalation factors will be utilized. Direct labor rates shall identify the baseline (takeoff point) plus projected escalation for each basic and option period, and the methodology for computing composite labor rates shall be shown. For example: 3 months of FY12 + 9 months of FY13 divided by 12 = the average labor rates for the contractual period of performance. The offeror and each subcontractor shall clearly state their fiscal year. Offerors are advised that projected escalation must be applied to both exempt and non-exempt labor categories.

(6) Direct labor hours and rates shall be delineated by labor category by contract year for the offeror and each subcontractor. The labor hour delineation must be directly traceable to the same information proposed in the Technical Volume.

(7) Indirect expense rates shall be proposed in the same manner as direct labor rates, i.e., by contract year with the methodology used to derive any composite rates proposed.

(8) This bullet is intentionally left blank.

(9) Offerors are reminded to identify any uncompensated or partially compensated overtime included in the proposal – per FAR Clause 52.237-10.

(10) Pursuant to the Service Contract Act of 1965, the determination by the Secretary of Labor as to the applicable minimum monetary wage and fringe benefits will be made part of any resulting contract. For evaluation purposes only, the Government has incorporated the applicable Area Wage Determinations and the Collective Bargaining Agreement as Attachment 2 of this RFP.

(11) Offerors are reminded of the requirements of Section 39 of the Office of Federal Procurement Policy (OFPP) Act (41 U.S.C. 1127, formerly 41 U.S.C. 435), as amended, which limits allowable costs for senior executive personnel compensation to $693,951 per year.

(12) For proposal preparation purposes, the expected or approximate date for initiation of contract performance is 14 January 2016.

(13) The offeror shall submit a complete breakdown of costs by major subcontractor. A major subcontractor is defined as a member of the offeror’s overall team who is expected to perform 25% or more of the proposed effort.

(14) The offeror shall ensure the proposed Unit Prices shall only include 2 (two) decimal places.

(15) As part of the proposal, the offeror shall provide the estimated total cost (if any) incurred to comply with the enterprise Contractor Manpower Reporting Application (eCMRA) requirement. Offeror shall determine, in the schedule, CLIN(s) X004, to price or not separately price the CMRA requirement. CLIN(s) X004 shall be the CLIN(s) under which the Contractor shall bill for all costs associated with the eCMRA requirement.

(v) VOLUME V – SOLICITATIONS, OFFER AND AWARD DOCUMENTS

AND CERTIFICATIONS/REPRESENTATIONS

(1) SOLICITATIONS, OFFER AND AWARD DOCUMENTS AND

CERTIFICATIONS/REPRESENTATIONS: Volume V must be clearly marked “Volume V -

SOLICITATIONS, OFFER AND AWARD DOCUMENTS AND CERTIFICATIONS/

REPRESENTATIONS, W9133L-16-R-0004.”

RFP Document. The contractor must submit the following documents as part of the RFP Document:

- PART 1, Executive Summary – Provide an executive summary that introduces the contractor team and proposal submission, to include a list of team members and subcontractors and the task areas they are designated to provide support.

Identification of the proposal point of contact (POC), e-mail address, and phone number; a list of the proposal package contents.

-PART 2, SF 1449. The SF 1449 shall be submitted fully completed. The Offeror is cautioned that the SF 1449 must contain an original signature in block 30a of the form. The contractor shall acknowledge any amendments to the RFP in accordance with the instructions on the SF 1449 and with 52.212-1 Instructions to Offerors – Commercial Items and this Addendum to 52.212-1. All final monetary extensions shall be in whole dollars only. Offerors are informed that Wage Determination and Collective Bargaining Agreement (CBA) are applicable to this requirement. The Offeror shall provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. The offeror shall provide a Unit Price and Estimated Net Amount and an Estimated Total for each period in the SF1449 CLIN Schedule. Teaming Agreements/Joint Ventures – The offeror shall provide with the proposal all required solicitation information for all parties including a copy of the teaming/partnering or joint venture agreement. The agreement shall including information which identifies the responsibilities for each entity under this contract. The agreement shall demonstrate the relationship between firms and identify contractual relationships and authorities to bind each entity of the teaming/partnering or joint venture relationship.

-PART 3, 52.212-3 (Offeror Representations and

Certifications – Commercial Items). The Offeror shall ensure that 52.212-3 Offeror Representations and Certifications – Commercial Items and 52.212-3 Alt I Offeror Representations and Certifications – Commercial Items (NOV 2015) Alternative I is submitted thoroughly completed with all blocks in each certification/ representation completed truthfully and completely.

Contractors are encouraged to submit all Representations and Certifications via SAM, but are required to submit the required Representaions and Certifications with the proposal that is not certified in SAM.

-PART 4, Exception to Terms and Conditions. The offeror shall include exceptions to terms and conditions set forth in this solicitation, the remedy sought and the impact if the Government does not concur with the exceptions.

(End of clause)

PERFORMANCE WORK STATEMENT

1.0 INTRODUCTION

1.1 The Army National Guard (ARNG) and Counterdrug Division, Domestic Operations and Force Development Directorate NG-J32 has a need for a non-personnel services contract to provide for the management and support for the Full Time Support Management Control System (FTSMCS) at the National Guard Bureau (NGB) Headquarters. The contract personnel will provide maintenance support, technical, and analytical services in the execution of their broad and diverse mission to facilitate operational requirements of the FTSMCS. ARNG also has a need for a contractor to provide for the management and daily work load activities for the Counterdrug Support Module at the National Guard Bureau (NGB) Headquarters. The contract personnel will provide administrative, technical, and analytical services in the execution of their broad and diverse mission to facilitate operational requirements of the Counterdrug Support Module.

1.1.1 Most data inputs to this system are raw data from Headquarters Department of the Army (HQDA) and Army National Guard (ARNG) systems of record such as Force Management System Website (FMSWeb), Army Marc Maintenance Data Base (AMMDB), Standard Installation/Division Personnel System (SIDPERS), Reserve Component Management System (RCMS), and Reserve Component Automated System (RCAS); as well as data from other systems, i.e. Air Force Military Personnel Data System (MilPDS), Defense Travel System (DTS), Commanders’ Resource Integration System (CRIS), etc. FTSMCS processes this data and converts it into useful information for all end users in the ARNG and ANG. The output generated will take on many forms, such as spreadsheet/tables that provides the annual voucher distribution, budget execution tables for the Active Guard and Reserve/Military Technician Active Guard and Reserve (AGR/MILTECH) program, and data collection for manpower studies. FTSMCS provides its users the ability to readily access full-time manning, budget execution, leave tracking/processing, data collection, and make it available to decision makers in a form for critical ARNG and NG-J32 wide decision.

1.1.2 The contractor shall provide all personnel, equipment, tools, materials, supervision, and quality control necessary, except as specified in Paragraph 3.0 as Government Furnished, to perform operations and maintenance for FTSMCS, as defined in this Performance Work Statement (PWS).

1.2 BACKGROUND

1.2.1 Since 1998, the FTSMCS contract has provided automated data processing and Information Technology (IT) support services to virtually all of the operational divisions within NGB Headquarters. The contract also supports individual States by facilitating and streamlining the exchange of information within the National Guard.

1.2.2 Over the past six years, the personnel and soldiers working in support of the FTSMCS have maintained responsibilities in the following key areas: Manpower; Personnel; Budget Cycles;

Accounting Management; Resource Distribution and Management; Force Structure; Force Management, and Counterdrug Operations.

1.2.3 Period of Performance (PoP): The Period of Performance shall be one Base Year of 12 months with two 12-month option years and an additional 6-month extension on option. The government anticipates awarding a contract on a Firm Fixed Price.

1.2.4 The National Guard Counterdrug Program (NG CDP) is aligned to support the goals of the White House Office of National Drug Control Policy (ONDCP) National Drug Control Strategy (NDCS) and the Department of Defense (DoD) Counterdrug support initiatives. The NG CDP accomplishes this by providing unique military capabilities in support of Federal, State, local and tribal law enforcement agencies (LEAs), community based organizations (CBOs), combatant commanders (COCOMs) and NG CDP Training Centers. Approximately 2,500 National Guard (NG) personnel are engaged daily through the Governors State Plans supporting Drug Interdiction, Drug Demand Reduction and Prevention, Treatment, and Outreach missions in the 54 States, Territories and the District of Columbia. Additionally, the National Guard Bureau Counterdrug Division (NGB-J32) supports federal missions domestically and overseas at the request of federal law enforcement agencies and COCOMs.

1.3 OBJECTIVE:

1.3.1 FTSMCS support requires a variety of skill sets, to include Structured Query Language (SQL) Server, Internet Information Server, Analog Signal Processing (ASP), ASP.net, Oracle, and Transact-Structured Query Language (T-SQL). Technical skills include systems analysis, system design, (both structured and object oriented), modeling, requirements determination and expert system and web development. Functional expertise include, but are not limited to (as they apply to Department of Defense (DoD) and the National Guard) force structure, force management, resource management, budget cycles, National Guard databases, and manpower modeling.

1.3.2 The contractor shall modify, maintain, and support the ARNG and NG-J32 with an innovative automated tool in the management of manpower, personnel, and resources. This involves promoting decision making processes by making accurate and timely resource, personnel, and manpower information readily available to the ARNG staffs and decision makers in a variety of useable and understandable forms. The cornerstone of this system is the ability to provide decision makers the capacity to easily access, integrate, refine, and enhance data from multiple sources while ultimately presenting information in a form that makes key issues apparent during the decision process.

1.3.3 Scope. The elements of work currently planned for this contract are listed below. The work areas listed will vary in amount of time and criticality during the period of performance of this PWS, but the sum of these work elements entail the elements in which the work will be performed.

1.3.3.1 Program Management, to include overall management of the program, subcontracts management, risk management, resource execution, program planning, quality assurance, systems migration, personnel acquisition, cost and progress reporting. Also included is acquisition support for acquiring and tracking hardware and software used in support of the FTSMCS program.

1.3.3.2 Maintain the operational readiness of FTSMCS and all its applications, modules, and servers.

1.3.3.3 Requirements definition and architecture, to include component identification, business process enhancements, requirements gathering and validation, requirements traceability, business process modeling, Commercial off-the-shelf/Government off-the-shelf (COTS/GOTS) identification, and business process management.

1.3.3.4 Data maintenance and modification of FTSMCS data architecture, data modeling, data integration, data standardization, data quality assessment and repair/refinement of data.

1.3.3.5 Software maintenance, to include definition and maintenance of an overall FTSMCS system, definition and construction of common system components and services, software technology assessments, technology insertions, software testing and integration.

1.3.3.6 Systems Integration, to include systems integration testing and integration of processes, hardware, software, and integration of DoD and NGB systems and applications with FTSMCS.

1.3.3.7 Documentation and definition of software systems and business processes.

1.3.3.8 Process improvement, to include the modification and maintenance of the overall integrated Program Plan, establishment of the overall metrics program and support and integration with government process organizations.

1.3.3.9 Technical and briefing support during demonstrations of FTSMCS and its capabilities to potential and current user communities within DoD and the National Guard.

1.3.3.10 Maintenance and enhancement of FTSMCS system and sub-applications, to include application software, databases, historical data repositories, forecasting models, expert systems, and web-based applications.

1.3.3.11 System Maintenance, to include the creation of software modification repositories and the definition and maintenance of a common software modified environment.

1.3.3.12 System Compliance with annual testing of IT contingency plans for the Federal Information Security Management Act (FISMA).

1.3.3.13 System Compliance with DoD and NGB Information Technology and Information Assurance requirements.

1.3.3.14 maintain Process and Business Rules; work with NGB representatives with approval of ARNG and NG-J32 CORs to define business processes and rules that ensure successful integration with existing systems.

1.3.3.15 Systems Engineering, to include the definition of interim and objective system architecture, modeling of architectural alternatives, interface documentation and engineering, system level configuration management, and overall support for system engineering concerns related to the Counterdrug Support Module.

1.3.3.16 Process Engineering, to include the modification and maintenance of the overall integrated Program Plan, establishment of the overall metrics program and support and integration with government process organizations.

1.3.3.17 Engineering Infrastructure, to include the creation of software modification repositories and the definition and maintenance of a common software modification environment.

1.3.3.18 The Contractor’s (the Prime contractor) processes and capabilities for executing the contract requirements shall meet Capability Maturity Model Integration (CMMI) Level 3 certification requirements at time of award.

1.3.4 REQUIREMENT/TASK

1.3.4.1 During the course of meeting FTSMCS’s specified requirements and performance goals, the contractor’s strategic focus will be the continued promotion of ARNG and NG-J32 staff decision making processes through the provision of accurate and timely resource, personnel, and manpower information to decision makers in a variety of useable and understandable forms.

1.3.4.2 The cornerstone of this system, and any task implemented on this contract, is the Contractors ability to provide leaders with innovative solutions and the capacity to easily access, integrate, refine, and enhance data from multiple sources while ultimately presenting information in a manner that makes key issues apparent during decision processes. The contractor’s strategic focus will be the continued promotion of ARNG and NG-J32 staff decision¬ making processes through the provision of accurate and timely resource, personnel, and manpower information to decision makers in a variety of useable and understandable forms.

1.3.4.3 The Contractor shall meet the requirements of the FTSMCS program in a manner that incorporates goal-oriented, transparent program management processes/objectives that not only support the ARNG and NG-J32 with innovative and responsive solutions but also the successful integration of any application related to the system within the overall operation of FTSMCS. It is critical to the overall effort that the Contractor meets all Information Technology and Information Assurance requirements as determined by DoD and the NGB.

1.3.4.4 Though a phased implementation is preferred, the Contractor is encouraged to present a project management plan that best suits the objectives of the FTSMCS and the overall goal of supporting the Director, ARNG and NG-J32 in the management of manpower, personnel, and resources. At any time the Government can accelerate the contract or the phased approach.

1.4 GENERAL INFORMATION

1.4.1 Quality Control (QC): The contractor shall modify and maintain an effective QC Plan (QCP) to ensure services are performed in accordance with this PWS. The contractor shall modify and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s QCP is the means by which it assures itself that its work complies with the requirements of the contract. As a minimum, the contractor shall modify QC procedures that address the areas identified in Technical Exhibit 1, Performance Requirements Summary. After acceptance of the QCP, the contractor shall obtain the Contracting Officer’s (KO) acceptance in writing of any proposed changes to its QCP.

1.4.2 Quality Assurance (QA): The Government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards.