W91CRB-17-T-0001.pdf

SEE ADDENDUM

(No Collect Calls)

W91CRB-17-T-0001 20-Oct-2016

b. TELEPHONE NUMBER

410-306-0082

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 21 Nov 2016

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

W91CRB9. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

KIM MCCARTHY

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

1 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.X

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESSX

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

ACC - APG - W91CRB

4310 BOOTHBY HILL AVE

ABERDEEN PROVING GROUND MD 21005-3013

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$27,500,000

NAICS:

541513

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

W91CRB-17-T-0001

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Transition and Base

FFP

60 Day Transition In along with ten months of full performance as described in the Performance Work Statement (PWS) FOB: Destination

NET AMT

0001AA Job Funding for CLIN

FFP

Funding for CLIN

0001AB Job Funding for CLIN

FFP

0002 Job Contract Manpower Reporting

FFP

Accounting for Contract Services Requirement has been added. The contractor is required to provide data on contractor manpower (including subcontractormanpower) for performance of this contract. Instructions, including the Contractor and Subcontractor User Guides, are available at https://cmra.army.mil. For further assistance, email the CMRA Help Desk at contractormanpower@hqda.army.mil

Option 1

FFP

Period of Performance is 12 months in accordance wtih PWS

0003AA Job Funding for CLIN

FFP

0003AB Job Funding for CLIN

FFP

0004 Job Contract Manpower Reporting Option 1

FFP

Accounting for Contract Services Requirement has been added. The contractor is required to provide data on contractor manpower (including subcontractormanpower) for performance of this contract. Instructions, including the Contractor and Subcontractor User Guides, are available at https://cmra.army.mil. For further assistance, email the CMRA Help Desk at

Option 2

FFP

Period of Performance is12 months in accordance wtih PWS

0005AA Job Funding for CLIN

FFP

0005AB Job Funding for CLIN

FFP

0006 Job Contract Manpower Reporting Option 2

FFP

Accounting for Contract Services Requirement has been added. The contractor is required to provide data on contractor manpower (including subcontractormanpower) for performance of this contract. Instructions, including the Contractor and Subcontractor User Guides, are available at https://cmra.army.mil. For further assistance, email the CMRA Help Desk at

Option 3

FFP

Period of Performance is12 months in accordance wtih PWS

0007AA Job Funding for CLIN

FFP

0007AB Job Funding for CLIN

FFP

0008 Job Contract Manpower Reporting Option 3

FFP

Accounting for Contract Services Requirement has been added. The contractor is required to provide data on contractor manpower (including subcontractormanpower) for performance of this contract. Instructions, including the Contractor and Subcontractor User Guides, are available at https://cmra.army.mil. For further assistance, email the CMRA Help Desk at

Option 4 and Transition Out

FFP

Period of Performance is 10 months with a 60 day transition out in accordance wtih

PWS.

0009AA Job Funding for CLIN

FFP

0009AB Job Funding for CLIN

FFP

0010 Job Contract Manpower Reporting Option 4

FFP

Accounting for Contract Services Requirement has been added. The contractor is required to provide data on contractor manpower (including subcontractormanpower) for performance of this contract. Instructions, including the Contractor and Subcontractor User Guides, are available at https://cmra.army.mil. For further assistance, email the CMRA Help Desk at

SPECIAL INSTRUCTION

Instructions to Offerors Addendum and Basis for Award Evaluation

Instructions to Offerors

The proposal shall consist of:

Technical Proposal Past Performance Price Proposal

The use of hyperlinks in proposals is prohibited. Each document shall be submitted via email in Word of Excel.

Each document shall be its own attachment in the email.

The proposal shall be submitted and named as follows:

TECHCAP.DOCX Technical Subfactor 1 (not to exceed 10 pages) TECHSTAFF.DOCX Technical Subfactor 2 (not to exceed 5 pages excluding template provided as

Attachment1 ) ATTACHMENT1.DOCX Technical Staffing Template PASTPERFSEC2.DOCX Past Performance Narratives (not to exceed 2 pages per narrative) PASTPERFSEC3.DOCX Contract Events (not to exceed 2 pages per event) PRICE.XLSX Price Spreadsheet (no page limit – use template provided as Attachment 2), PRICENARR.DOCX Price Narrative (no page limit)

***Price information shall not appear in volumes in any file other than PRICE or PRICENARR.

All information must be Microsoft Office 2007 compatible. No information may be locked; all information must be read/writable. The completed Microsoft Excel Worksheets shall NOT be "linked" to an external worksheet unless that worksheet is also provided to the Government. Zip files are not permitted. **Please note – Self extracting exe files are not acceptable. **

The proposal shall remain valid for a minimum of one hundred and twenty (120) days and shall not contain classified data/information. Proposals not marked with a validity period shall automatically be considered valid for 120 days.

Proposals shall be limited to the number of pages as shown above for each factor. Any pages exceeding stated page limits will NOT be evaluated. Electronic Word pages shall be on a standard 8-1/2 X 11 inch format. Each page shall be single spaced with a minimum of twelve (12) point Times New Roman font and one (1) inch borders.

Submissions shall be emailed to Kimberly.a.mccarthy14.civ@mail.mil. The number after the “mccarthy” is the NUMBER fourteen (14). The contractor must verify that the submission was received by the Government in its entirety.

PROPOSAL CONTENT REQUIREMENTS

Technical

Subfactor a: Technical Capability - The proposal should not merely offer to perform the work in accordance with the solicitation requirements, but shall outline the offeror’s actual approach. The offeror's proposal shall:

1. Demonstrate its knowledge of an Oracle data warehouse and the ability to design processes that integrate Logistics Modernization Program and Candidate Item File (Paragraph 1.2.1 of PWS).

2. Demonstrate its knowledge of integrating new systems into existing systems on Oracle based applications.

(Paragraph 1.2.2 of PWS)

3. Demonstrate understanding the roles of the various agencies that comprise the Army analytical community (e.g., the TRADOC Analysis Center (TRAC), Center for Army Analysis (CAA), National Ground Intelligence Center (NGIC) and AMSAA), and the JTCG/ME community (e.g., JTCG/ME Program Office, Army Research Laboratory, etc.) and how those agencies contribute to the overall AMSAA and JTCG/ME product development processes. (Paragraph 1.2.3 of the PWS)

4. Demonstrate its knowledge of Oracle technical support of: Oracle-related software patches, Oracle software updates, the tuning of Oracle based software systems/databases/data warehouses, miscellaneous security fixes, user administration and general problem solving. Integration of technologies (e.g., Army Knowledge Online (AKO)-S, Single-Sign-On (SSO)) into existing applications is another critical component. Provide expertise in applying the Defense Information Systems Agency’s (DISA) Security Technical Implementation Guides (STIGS) to the Oracle databases as required for system accreditation under Risk Management Framework. (Paragraph 1.2.4 of PWS)

5. Demonstrate its knowledge of an enterprise cloud environment and the ability to migrate from a database application to the cloud. (Paragraph 1.2.5 of PWS)

6. Provide proof of a SECRET facility clearance and the ability to provide staff that possesses a minimum of a SECRET security clearance at time proposal submission. (Paragraphs 2.1 and 2.2 of PWS)

Subfactor b: Staffing – The offeror shall provide a resume for the Senior Logistics Data Analyst (SLDA), Principal Application Engineer (PAE) and Senior Database Administrator (SDBA). In addition, the offeror must complete Attachment1 (Technical Staffing Template).

In a separate document, not exceeding 2 pages, the offeror shall demonstrate how it will meet the requirements of paragraph 4.4 of the PWS.

As part of the 2 pages, offerors shall identify any teaming arrangement or proposed subcontractor who will perform a significant portion of the effort. A significant portion is defined as fifteen percent (15%) of the total effort. The contractor must explain how it will be in compliance with FAR 52.219.14 – Limitations on Subcontracting or indicate that no subcontractors are to be utilized.

**Note Subfactor b: Staffing is three or four parts. Part 1) Three resumes, Part 2) Attachment1, Part 3) one staffing document, and if subcontracting or teaming Part 4)a separate document of explanation.

Past Performance

The offeror shall provide a contract list for at least one but no more than five recent and relevant contracts to this effort. In addition to the recent and relevant contracts, list ALL contracts (whether on the recent and relevant list or not) in the past five years that have had one of the following: option not exercised, termination for default, cure notice, suspension or debarment, security violation and/or incidents, or notifications received for violations of FAR 32.006.

Offerors shall provide a specific narrative explanation of each contract listed describing the objectives achieved and detailing how the effort is similar to the requirements of this solicitation.

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. Narratives are limited to two (2) pages for each contract.

For any contracts that did not/do not meet original cost, schedule or technical performance requirements provide a brief explanation of the reason(s) for the shortcomings and any corrective actions taken to avoid recurrence.

Additionally, a written explanation is required for ANY contact that had one of the following: option not exercised, termination for default, cure notice, suspension or debarment, security violation and/or incidents, or notifications received for violations of FAR 32.006. The explanation shall include the corrective action taken. The written account for each of the events shall not exceed two (2) pages for each explanation. Note: One contract may have more than one event that needs to be explained.

Offerors are cautioned that in conducting the past performance assessment, the Government may use data provided in the offeror's proposal and data obtained from other sources. Since the Government may not necessarily interview all of the sources provided by the offerors, it is incumbent upon the offerors to explain the relevance of the data provided. Offerors are reminded that while the Government may elect to consider data obtained from other sources, the burden of proving acceptable past performance rests with the offerors.

Price Proposal

Offeror and subcontractor proposals will be evaluated based on the evaluation criteria Factor 3 – Price. A proposal is presumed to represent the offeror's best effort to respond to the solicitation. Any inconsistency, whether real or apparent, between promised performance and price shall be explained in the proposal.

a. Each offeror's price proposal shall contain supporting quantitative and narrative documentation necessary to adequately support the FAR 15.404-1 fairness & reasonableness of proposed prices for all CLINs. Offeror price proposals shall conform to the criteria in FAR 15.408, Table 15-2. Therefore, a Microsoft Excel workbook titled "PRICE.xls" has been provided as an attachment to this solicitation (PRICE.XLSX). Instructions for completing PRICE.XLSX are contained in the file. Each offeror is to complete and include the spreadsheets in PRICE.XLSX as part of their price proposal. These spreadsheets will help facilitate a more efficient, consistent, and fair evaluation of each offeror's proposal, and aid in post-award contract administration. Offerors are permitted to alter the format of the spreadsheet (i.e. add and subtract rows, columns, and formulas as necessary, etc). However the labor categories and hours shall remain the same based on the categories and hours provided in the PRICE.xlsx model. Offerors can split/divide/allocate the hours in any given labor category between the offeror and any subcontractors based on planned performance, however the hours by labor category and total shall remain the same as contained in the PRICE.xlsx model.

b. Offerors are encouraged to provide whatever supplemental information (i.e. schedules, spreadsheets, documents, etc) as necessary to help the Government understand why the proposed costs are FAR 15.404-1 fair/reasonable.

Supporting narrative shall be submitted in Microsoft Word or Excel compatible format. Any supporting schedules shall be submitted in a Microsoft Excel readable format.

c. In accordance with FAR 15.404-3(b)(1) each offeror shall conduct the appropriate price and/or cost analysis to establish the reasonableness and realism of proposed subcontract cost/prices. Evidence of this review shall be submitted as part of the offeror's cost/price proposal. Any subcontractor proprietary data can be submitted under separate cover to the contracting officer.

d. As part of its proposal, the offeror will provide the estimated total cost (if any) incurred to comply with the Contractor Manpower Reporting Application (CMRA) requirement. Offerors will determine, in Section B, CMRA CLINs to price or not separately price the CMRA requirement.

f. FAR 52.222-46 requires that each offeror submit a total compensation plan setting forth and describing total compensation (i.e. salaries/direct labor rates and fringe benefits) proposed for professional employees who will work on the contract. This plan shall be included as an attachment to the price proposal and shall address recruiting and retention, and its consistency with the total plan for compensation as contained in FAR 52.222-46. Supporting information in the plan shall include data such as recognized national and regional compensation surveys and studies as described in FAR 52.222-46 used in establishing the compensation structure.

BASIS FOR AWARD - EVALUATION

One award will be made to the lowest priced proposal that is Acceptable for both the Technical and Past Performance factors.

Factors and Sub-Factors to be evaluated:

Factor 1 – Technical

Subfactor a - Technical Capability Subfactor b - Staffing

The evaluation of the ofBasferor’s proposal shall address each subfactor as it applies to the Performance Work Statement (PWS). A detailed explanation of the criteria for the evaluation is set forth in the “Evaluation Approach,” Paragraph B of this section.

Factor 2 – Past Performance: Each offeror’s past performance will be reviewed to determine whether the Government has a reasonable expectation that the offeror will successfully perform the required effort.

Factor 3 – Price: Price will be evaluated competitively. Price analysis will be used to evaluate FFP effort to determine that the offered price is reasonable. If an offer is considered technically unacceptable, price will not be evaluated.

EVALUATION APPROACH

The proposals will be evaluated for the extent to which each requirement of the solicitation has been addressed in the proposal. The proposals will be evaluated to determine whether the offeror's methods and approach in meeting the proposed requirements provide the Government with an acceptable level of confidence of successful completion in a timely manner. If an offeror is not determined technically acceptable or acceptable in past performance, their price will not be considered.

The overarching evaluation approach for all factors and subfactors is as follows:

Factor 1 - Technical The Technical factor will be rated as Acceptable or Unacceptable. An offeror must be deemed Acceptable for both subfactors to receive an Acceptable rating for the Technical factor.

The following definitions apply to the Technical Factor and Subfactors:

Acceptable: Proposal clearly meets the minimum requirements of the solicitation and the proposed approach is workable with achievable end results.

Unacceptable: Proposal does not clearly meet the minimum requirements of the solicitation and the proposed approach is not workable with achievable end results.

Factor 2 - Past Performance The Past Performance evaluation will assess the relative likelihood of success in performing the solicitation’s requirements as indicated by that offeror’s record of past performance. In this context, “offeror” refers to the proposed prime contractor and all proposed subcontractors. The prime and proposed subcontractors will be assessed individually and the results will then be assessed in their totality to derive the offeror’s overall past performance rating.

The Government reserves the right to contact any other sources of information that may have knowledge or information on an offeror’s relevant past performance history. The Government will use data provided in the offeror’s proposal as well as data obtained from other sources including, but not limited to, Past Performance Information Retrieval System (PPIRS) and interviews with other Government officials.

Past Performance must be recent and relevant for consideration and will receive one of the ratings shown below. For the purposes of this solicitation, “recent” is defined as present/past performance within the past five years.

“Relevant” is defined as present/past performance effort that involved a similar scope and magnitude of effort and complexities to this solicitation.

Acceptable: Based on the offeror’s performance record, the Government has a reasonable expectation that the offeror will successfully perform the required effort, or the offeror’s performance record is unknown. (See note below.)

Unacceptable: Based on the offeror’s performance record, the Government has no reasonable expectation that the offeror will be able to successfully perform the required effort.

Note: In the case of an offeror without a record of relevant past performance or for whom information on past performance is not available or so sparse that no meaningful past performance rating can be reasonably assigned, the offeror may not be evaluated favorably or unfavorably on past performance (see FAR 15.305 (a)(2)(iv)). Therefore, the offeror shall be determined to have unknown past performance. In the context of acceptability/unacceptability, "unknown" shall be considered "acceptable."

Factor 3 – Price: Proposed price will not be adjectively rated. A completed and totaled Section B shall be submitted with the offeror’s price proposal. The total evaluated price will be the sum of all CLINs. All CLINs will be evaluated for fairness and reasonableness in accordance with FAR 15.404-1. In accordance with FAR 15.404- 1(a)(1) the analytical techniques and procedures described in FAR 15.404-1 will be used singly or in combination with others as determined necessary by the Contracting Officer based on competition and other factors.

Competition is anticipated. Therefore, certified cost and pricing data is not currently required in accordance with FAR 15.403-1(b)(1), however the Government reserves the right to request certified cost or pricing data prior to award if adequate competition is not received.

ATTACHMENTS

Attachment List:

Attachment 1 TECHSTAFF.DOCX Technical Subfactor 2 (not to exceed 5 pages excluding template provided as Attachment1 )

Attachment 2 PRICE.XLSX Price Spreadsheet (no page limit – use template provided as Attachment 2)

Attachment 3 DD254

PERFORMANCE WORK STATEMENT PERFORMANCE WORK STATEMENT (PWS); TECHNICAL SUPPORT TO

US ARMY MATERIEL SYSTEMS ANALYSIS ACTIVITY (AMSAA)

MATERIEL/LOGISTICS ANALYSES AND DATA BASE ENABLED PROCESSES

PART 1: GENERAL INFORMATION

1.1 DESCRIPTION OF SERVICES/INTRODUCTION: The US Army Materiel Systems Analysis Activity (AMSAA) provides decision support to Department of Army (DA) and Department of Defense (DoD) Leadership as relates to materiel/weapon systems; and logistics systems, policies, concepts, readiness, and sustainability requirements. AMSAA requires specialized technical support to assist in the analysis of Army materiel and logistics data/processes that also relies on an underlying expertise in Oracle databases, application programming and database security. AMSAA requires analytical support services, expertise with existing Army logistics databases as well as support in designing, developing and maintaining the necessary in-house database infrastructure to operate them.

1.2 OBJECTIVES: AMSAA has the following objectives as pertains to the required contract support as spelled out in Part 3 of this PWS:

1.2.1 Support the performance of AMSAA’s broad spectrum logistics/resource analyses, and modeling and simulation (M&S) technical efforts through review and update of key logistics, supply and maintenance data that drive support analyses. This includes the transition from Army legacy data systems/databases to new Logistics

Modernization Program (LMP) data feeds/sources and Candidate Item File (CIF) updates. Knowledge of the underlying business processes that support the LMP data and CIF is critical to success. Since these processes are facilitated by an underlying Oracle database warehouse, the ability to define and design processes that integrate LMP and CIF data into logistics analysis processes within that environment is also critical.

1.2.2 Support the development and maintenance of AMSAA’s broad spectrum business and technical mission Oracle-based applications (current and future systems). Successfully meeting this objective requires integrating new systems into existing ones so they seamlessly interoperate.

1.2.3 Support AMSAA’s Joint Data Center (JDC) materiel data collection and analysis processes that connect internal systems to external systems deployed by Army analytical and DoD intelligence agencies. These tools impact database applications such as the Characteristics and Performance Data Portal, the AMSAA Performance Estimate Data System and the Joint Technical Coordinating Group for Munitions Effectiveness (JTCG/ME) Product and Information Access System on both the Defense Research and Engineering Network (DREN) and Secure Internet Protocol Router (SIPR) networks. Success with this task requires understanding the roles of the various agencies that comprise the Army analytical community (e.g., the TRADOC Analysis Center (TRAC), Center for Army Analysis (CAA), National Ground Intelligence Center (NGIC) and AMSAA), and the JTCG/ME community (e.g., JTCG/ME Program Office, Army Research Laboratory, etc.) and how those agencies contribute to the overall AMSAA and JTCG/ME product development processes.

1.2.4 Provide other miscellaneous Oracle technical support to the AMSAA G-6 Information Management business area and the AMSAA technical divisions on both the DREN and SIPR networks. This support includes, but is not limited to: Oracle-related software patches, Oracle software updates, the tuning of Oracle based software systems/databases/data warehouses, miscellaneous security fixes, user administration and general problem solving.

Integration of technologies (e.g., Army Knowledge Online (AKO)-S, Single-Sign-On (SSO)) into existing applications is another critical component. Provide expertise in applying the Defense Information Systems Agency’s (DISA) Security Technical Implementation Guides (STIGS) to the Oracle databases as required for system accreditation under Risk Management Framework.

1.2.5 Provide expertise in database application migration. As part of the Army Data Center Consolidation Program (ADCCP), the applications listed above may be required to be migrated to an enterprise cloud environment.

Expertise in application migration will be required to support this effort.

1.3 SCOPE: The contractor shall provide highly specialized systems professional expertise and technical performance to support the goals of the AMSAA’s overall mission success. The contractor shall provide all personnel and supervision necessary to perform the services defined in this PWS. All objectives will be performed to the standards set forth in this document. AMSAA requires specialized and certified technical support in order to provide reliable, responsive weapon/materiel and logistical analyses to the Army and DoD communities.

1.4 TYPE OF CONTRACT: The government anticipates awarding a Firm Fixed Price contract.

1.5 PERIOD OF PERFORMANCE: The period of performance for this support effort is 60 months after date of award.

1.6 PLACE OF PERFORMANCE: The contractor will perform the support services in accordance with the PWS objectives, predominantly at the AMSAA government facility at (Aberdeen Proving Ground (APG), MD).

Contractor personnel will be required to attend meetings and workshops at offices in Aberdeen Proving Ground, Maryland.

1.6.1 AMSAA headquarters is located on APG, MD. Personnel at AMSAA work either: 1) a Flexible Work Schedule (FWS) (i.e., a schedule which allows for a 10 workday biweekly work schedule (a basic 8-hour workday, Monday through Friday) with fixed or flexible hours); or 2) a Compressed Work Schedule (CWS) (i.e., a schedule which allows for a fixed 8, 9 or 10 workday biweekly work schedule that completes the 80-hour pay period obligation). Supervisors stagger the day off for their staff working the CWS so that there will be adequate coverage for every team every day of the work week. The time bands for AMSAA have been established as follows: flexible

– 0630-0900, core – 0900–1100, flexible – 1100–1230, core – 1230–1500, flexible – 1500–1800, Monday through Friday.

The following Federal Holidays are observed:

(a) January 1st (f) 1st Monday in September

(b) 3rd Monday in January (g) 2nd Monday in October

(c) 3rd Monday in February (h) November 11th

(d) Last Monday in May (i) 4th Thursday in November

(e) July 4th (j) December 25th

1.6.2 When any of the above holidays fall on a Sunday, the following Monday will be observed as the holiday;

when a holiday falls on a Saturday the preceding Friday is observed as the holiday.

1.7 GOVERNMENT FURNISHED ITEMS AND SERVICES: When the contractor is providing on-site support on APG, MD, the government will configure and provide the computer hardware, software and supplies necessary for the completion of the contract tasks. The government will also provide a fully equipped work area at APG, MD with furniture and office equipment required to perform the contract tasks. The following services will also be provided at the APG site: utilities, mail distribution, desktop computing support, network access/support, telephone service, and facilities support.

1.8 CONTRACTOR FURNISHED FACILITIES & SERVICES: When the contractor is providing support from an off-site location, the contractor will be solely responsible for providing all property, equipment, software, facilities and services.

1.9 QUALITY CONTROL The contractor shall develop and maintain an effective quality control program (QCP) to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s QCP is the means by which contractor assures work complies with the requirement of the contract. As a minimum, the contractor shall develop QCP procedures that address the areas identified in the Performance Requirements Summary. The awarded contractor shall receive the contracting officer’s acceptance in writing, of any proposed change to his QC system, after award.

1.10 QUALITY ASSURANCE: The government will evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP) and QCP. The QASP is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.11 MEETINGS: The contractor shall keep AMSAA personnel informed of tasks that have been completed on a weekly basis. This correspondence shall take place in person or, if necessary, by way of e-mail. However, if weekly meetings are primarily done via e-mail, the contractor shall meet with AMSAA personnel, in person, once a month.

PART 2: SECURITY REQUIREMENTS:

2.1 Facility Clearance: The contractor shall possess a SECRET facility clearance as prescribed by DD Form 254 (Contract Security Classification Specification). The contractor shall not be required to access or safeguard classified information at their facility. Contractor personnel shall only access classified information at AMSAA or other government and cleared contractor facilities as specified by the COR.

2.2 Personnel Security Clearances: The contractor personnel shall be required to possess a minimum of a SECRET security clearance. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified "Confidential," "Secret," or "Top Secret" and requires contractors to comply with: (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M) and, (2) any revisions to DoD 5220.22-M.

2.3 Information Technology (IT) Access: The contractor shall designate IT positions for all personnel requiring access to government IT systems IAW paragraph 4-14, AR 25-2. The contractor shall request the appropriate personnel security investigation based upon the IT position designation. Access to IT systems will not be granted until the basic requirements of paragraph 4-14a, AR 25-2 are validated by AMSAA G2 personnel. All contractor employees with access to government IT systems must be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services. In addition, the contractor shall ensure that all personnel designated to IT positions meet the training and certification requirements outlined in Department of Defense Directive (DoDD) 8570.01 and must successfully complete the DoD Information Assurance Awareness and the DoD Cyber Awareness Challenge training prior to IT access and then annually thereafter. Specifically, those with administrative privileges must possess a current baseline and computing environment certification. All contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 which must be completed upon contract awards.

2.4 Reports of Adverse Information: The contractor shall immediately report to the AMSAA G2 all adverse information on contractor personnel such as security violations, arrests, bankruptcy, and denial, suspension, or revocation of security clearances. Contractor personnel may be denied access into APG restricted areas by the AMSAA G2 based upon the adverse information.

2.5 Installation Access: Aberdeen Proving Ground (APG) is a closed post. All vehicles and personnel are subject to search and seizure of contraband and/or unauthorized Government property IAW AR 190-13. All contractor personnel shall comply with the requirements of APGR 190-4, Movement Control within the Installation, for entry, exit, and internal control of personnel, material, and vehicles on APG. Contractor and all associated subcontractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office.

Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

2.6 Unescorted Access into Restricted Areas: Unescorted access into the APG restricted areas shall be granted to contractor personnel who possess a security clearance or were the subject of a favorably adjudicated National Agency Check (NAC) or FBI Fingerprint Check. Unescorted access shall be authorized provided no more than 24 months have lapsed since the date of the termination of the security clearance or break of service and there is no known adverse information. The AMSAA G2 will serve as the approval authority for contractors nominated by the Contracting Officer’s Representative (COR) or Alternate COR to have unescorted access into the restricted areas of Aberdeen Proving Ground, MD. Contractors granted unescorted access into the restricted areas shall ensure they access only those government facilities approved by the COR or Alternate COR. Contractor personnel violating AMSAA and APG policies regarding access into the restricted area may have their unescorted access approval withdrawn on a temporary or permanent basis upon request of the AMSAA G2, COR, or Alternate COR.

2.7 Photographic Security Badges: Photographic security badges will only be issued to contractor personnel that require access to AMSAA. Photographic security badges shall be approved and issued by AMSAA G2 to contractor personnel upon request from the COR and after the investigation or security clearance has been verified. Contractor personnel shall wear the photographic security badge at all times when in the restricted areas of APG. Contractors shall only escort visitors into the restricted area that have been approved by the COR or the Alternate COR.

Contractor personnel violating AMSAA and APG policies regarding escorting requirements may have their photographic security badge confiscated on a temporary or permanent basis upon request of the AMSAA G2, COR, or Alternate COR.

2.8 Common Access Cards: Common Access Cards (CAC) will be issued to contractor personnel nominated by the COR or Alternate COR for secure access to government computer systems and networks. The contractor shall coordinate with the COR or Alternate COR to request and obtain a CAC via the automated Trusted Associate Sponsorship System (TASS). Contractors must comply with Homeland Security Presidential Directive-12 (HSPD-

12) as required by paragraph 2b of enclosure 1 of Army Directive 2011-08. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated national Agency Check with Inquiries (NACI) or an equipment or higher investigation in accordance with Army Directive 2014-05.

2.10 Foreign Nationals/Immigrant Aliens: Foreign nationals/immigrant aliens cannot be granted access to classified or unclassified sensitive information as identified by the COR and will not be scheduled to perform work on contract tasks. When foreign nationals/immigrant aliens are visiting AMSAA, the contractor shall comply with

AR 380-10.

2.11 Safeguarding Government Information and Property: The contractor shall be responsible for safeguarding all Government information and property provided for contractor use. Contractor personnel shall safeguard information and material designated as classified, unclassified sensitive, For Official Use Only (FOUO), Operations Security (OPSEC) sensitive, and Privacy Act Information IAW applicable directives.

2.12 Loss or Possible Compromise of Classified Information: The contractor shall immediately report the loss of possible compromise of classified information or material to the AMSAA G2.

2.13 Security Training: The Contractor shall develop and implement a security education program to ensure contractor personnel understand and are familiar with the safeguarding of classified information. The Contractor shall conduct security indoctrination training for all new employees within 30 days after their arrival and ensure refresher briefings and debriefings are provided as required. Contractor personnel performing tasks at AMSAA shall complete security training as directed by the AMSAA G2. Examples of this training include but are not limited to Information Security, Information Assurance (IA), Communications Security (COMSEC), Operations Security (OPSEC), Threat Awareness and Reporting Program (TARP), and Antiterrorism (AT). Contractor personnel shall comply with TARP requirements IAW paragraph 1-14, AR 381-12 and must receive annual TARP training by a Counterintelligence Agency or other trainer as specified in paragraph 2-4b, AR 381-12.

• Antiterrorism Level 1 training: All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR or to the contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website:

http://jko.jten.mil.

• iWATCH training: The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the CO. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 30 calendar days after contract award.

• OPSEC training: Per AR 530-1, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained with 30 calendar days of their reporting for duty and annually thereafter.

2.14 Operations Security (OPSEC) Plan/Reviews. All contractor personnel must read and comply with AMSAA’s OPSEC Plan. The COR will ensure a copy of the current AMSAA OPSEC Plan is provided to contractor personnel. All material produced and/or develop by contractor personnel which discuss the support provided to AMSAA and is to be disseminated into the public domain shall be submitted to the AMSAA G2/OPSEC Officer prior to its release. This includes all written (hardcopy) and electronic materials produced such as organizational press releases and marketing material. Contractor personnel shall submit to the AMSAA G2 any http://jko.jten.mil/ material proposed for public dissemination at least 10 days prior to its release. Only that material which has undergone an OPSEC and security review and has been approved by the AMSAA G2/OPSEC Officer shall be released in to the public domain.

2.15 Departing Employees: The Contractor shall ensure all contractor personnel process through the AMSAA G2 to return issued security identification badges, DoD identification cards (i.e. CAC), keys, etc. to the Government at the completion of their employment. Contractor personnel may also be required to execute specific debriefing statements. Contractor personnel shall also process through the AMSAA G6 to ensure information system accounts/permissions are terminated.

PART 3: BASIC SERVICES: The contractor shall provide technical services related to the analysis of Army materiel system performance and Army logistics systems/operations; and support the related Oracle database and application environment at AMSAA for these areas and for general business operations. This effort is organized into the basic service areas that are spelled out in this section of the PWS. These basic service areas are expected to be worked concurrently and have duration as approved by and monitored by the AMSAA COR. The contractor shall provide support to AMSAA to include – but not limited to – the following requirements/objectives:

a) Logistics Analysis Support/Data Tasks:

1) Support logistics analysis by deciphering problems and formulating solutions that derive the necessary data needed to inform/drive decisions about Army logistics processes (from logistics data sets shown in b) through g) below, as well as other data sets mentioned separately).

2) Update documentation/data dictionary in the data warehouse to reflect changes.

3) Incorporate Logistics Modernization Program (LMP) data feeds into the data warehouse for transitioned data sets.

4) Candidate Item File (CIF) updates.

5) Address data integrity issues and perform general trouble shooting by editing/scrubbing and manipulating data sets in support of various AMSAA analyses/studies.

6) Address any anomalies that occur during standard data loads.

7) Incorporate new logistics data feeds to supplement or replace LOGSA data feeds (e.g. G-CSS-Army), to support AMSAA’s web-based analytical tools.

Note: An additional Database Application Summary is provided at the end of this PWS/Quality Assurance Surveillance Plan (QASP) document to provide technical characteristics and information associated with AMSAA’s classified and unclassified database instances and applications.

b) AMDF (Army Master Data File):

1) Monthly download AMDF and Interchangeability and Substitutability (I&S) elements from FEDLOG discs

(minimum of 1 data set per month).

2) Update AMDF and I&S tables.

3) Backup updated tables.

c) Integrated Logistics Automation Program (ILAP):

1) Load monthly ILAP data files (minimum of 1 data set per month).

2) Update Fact and Current ILAP tables.

4) Load EDA and other LOGSA tables daily to monthly to support web-based analysis tools.

d) Pipeline:

1) Load monthly Pipeline data files (minimum of 1 data set per month).

2) Update Fact and Current Pipeline tables.

e) Quantity by Owner (QBO):

1) Load monthly QBO files (minimum of 1 data set per month).

2) Update Fact table.

f) Federal Logistics Information System (FLIS):

1) Load monthly FLIS files (minimum of 1 data set per month).

g) Maintenance Data:

1) Load monthly Maintenance files (minimum of 1 data set per month).

h) Support database tuning tasks for AMSAA G-Staff/Enclave (e.g. patches, updates, tuning and security fixes).

Manage application servers and Oracle instances on the Defense Research and Engineering Network (DREN).

i) Maintain and enhance the Quick Data Analyzer (QDA).

j) Joint Technical Coordinating Group for Munitions Effectiveness (JTCG/ME) and Joint Data Center (JDC)

Application Server Configuration Support (both the Unclassified Defense Research and Engineering Network (DREN), and the Secret Internet Protocol Router Network (SIPRNET) databases, applications and websites):

1) Develop, manage, maintain back-up and recovery scheme for all databases.

2) Manage application servers and Oracle instances.

3) Assist developers with connection issues and application server deployments.

4) Provide developer support; provide information on database schemas, applications and how they integrate into the existing application, network and system architecture; assist with connection issues; help implement/integrate new technologies.

k) Resource Tracking System (RTS), Campaign Plan Line of Effort (LOE) Metrics and other web-based applications/databases:

1) Provide RTS Oracle database, application programming, data query and report writing support to the

Budget Office at fiscal year (FY) end, during new FY start-up and as required throughout the execution year. This support will encompass RTS maintenance, updates, security and future development.

2) Provide future custom database/web application development as pertains to the automating the data collection, derivation and reporting associated with AMSAAs Campaign Plan LOE metrics. These LOE metrics cut across the organization’s broad weapon systems performance analysis and logistics engineering analysis mission/functional areas as well as the core human resources/workforce and resource management/financial business areas.

3) Implement and maintain Single Sign-On (SSO) across all web applications.

4) Maintain and enhance the Quick Data Analyzer (QDA).

l) Support database and application migration to an Enterprise Data Center cloud environment, as required.

m) Exhibit detailed knowledge/expertise in the broad spectrum of Army logistics data to include sources, composition, structure and uses in support of logistics analyses. Coordinate the workflow associated with processing of logistics data to/from the data warehouse, while supporting analyses by developing appropriate metrics from maintenance, repair and usage data. Plan and oversee the technical transitions between the data warehouse and other Army logistics data suppliers. Facilitate change control, problem management, and communication among data architects, programmers, analysts, and engineers. Establish processes to ensure a consistent, well managed, and well-integrated process flow. Expand and improve processes to include data flow, analysis, transformation and cleansing.

n) Formulate and define system scope and objectives through research and fact-finding to develop or modify moderately complex information systems. Prepare detailed specifications and then write and modify programs based on these specifications. Analyze and revise existing system logic difficulties and documentation as necessary.

o) Perform database administration to include securing the databases to DISA STIG requirements, upgrades, user management, backup and recovery, data modeling, and supports data/system documentation.

PART 4: PERSONNEL FUNCTIONS & SPECIAL QUALIFICATIONS:

4.1 The following are considered key personnel functions needed by the government.

• Senior Logistics Data Analyst (SLDA) – Coordinates the workflow associated with processing of logistics data to/from the data warehouse, supports analyses by developing appropriate metrics from maintenance, repair and usage data. Plans and oversees the technical transitions between the data warehouse and other Army logistics data suppliers. Facilitates change control, problem management, and communication among data architects, programmers, analysts, and engineers. Establishes processes to ensure a consistent, well managed, and well-integrated process flow. Expands and improves processes to include data flow, analysis, transformation and cleansing.

• Principal Application Engineer (PAE) – Formulates and defines system scope and objectives through research and fact-finding to develop or modify moderately complex information systems.