W9128A-15-R-0008-FINAL.pdf

SEE ADDENDUM

(No Collect Calls)

W9128A-15-R-0008 21-Sep-2015

b. TELEPHONE NUMBER

808-835-4378

8. OFFER DUE DATE/LOCAL TIME

12:00 PM 21 Oct 2015

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

W9128A9. ISSUED BY

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

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

JENNIFER KO

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

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

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

WOMEN-OWNED SMALL

BUSINESS (WOSB)

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

CECT - CONTRACTING DIVISION

USACE, HONOLULU DISTRICT

BLDG 230 (CECT-POH)

FT. SHAFTER HI 96858-5440

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

ECONOMICALLY DISADVANTAGED

WOMEN-OWNED SMALL BUSINESS

(EDWOSB)

SIZE STANDARD:

$27,500,000

NAICS:

541512

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.

j3ct9jik Typewritten Text j3ct9jik Typewritten Text

ASIDE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF112

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.

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 FFP BASE PERIOD

The Offeror shall furnish necessary management, labor, supervision, materials, equipment, transportation, and other incidental services to perform services in accordance with the below Performance Work Statement entitled, “Project Management Automated Information System (P2) Operations & Maintenance” dated 2 September 2015.

0001AA Transition Period for 2 Months $__________________ $_______________________ O&M

0001AB P2 O&M 10 Months $__________________ $_______________________

0001AC Travel 1 Job $66,000.00 (NTE)

0001AD Production Emergency 80 Hours $__________________ $_______________________ Maintenance. The hourly rate shall include all direct and indirect costs.

0002 CMR (BASE PERIOD) 1 Job $_______________________ The Offeror shall provide professional, administrative, and technical services in accordance with below Performance Work Statement entitled, “Project Management Automated Information System (P2) Operations & Maintenance” dated 2 September 2015.

This CLIN is used for the pricing of the collection and reporting of Contractor Manpower Reporting data as described in the Performance Work Statement.

Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government Fiscal Year and must be reported by 31 October of each calendar year. If the contract does not separately price this requirement, it shall enter 0 (zero).

TOTAL BASE PERIOD (0001, 0001AA, 0001AB, 0001AC, 0001AD, AND 0002) $_______________________

W9128A-15-R-0008

0003 FFP OPTION YEAR 1

OPTION The Offeror shall furnish necessary management, labor, supervision, materials, equipment, transportation, and other incidental services to perform services in accordance with the below Performance Work Statement entitled, “Project

0003AA P2 O&M 12 Months $__________________ $_______________________

OPTION

0003AB Travel 1 Job $66,000.00 (NTE)

0003AC Production Emergency 80 Hours $_________________ $_______________________ OPTION Maintenance. The hourly rate shall include all direct and indirect costs.

0004 CMR (OPTION YEAR 1) 1 Job $_______________________ OPTION The Offeror shall provide professional, administrative, and technical services in accordance with below Performance Work Statement entitled, “Project Management Automated Information System (P2) Operations & Maintenance” dated 2 September 2015.

This CLIN is used for the pricing of the collection and reporting of Contractor Manpower Reporting data as described in the Performance Work Statement.

Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government Fiscal Year and must be reported by 31 October

TOTAL OPTION YEAR 1 (0003, 0003AA, 0003AB, 0003AC, AND 0004) $________________________

0005 FFP OPTION YEAR 2

equipment, transportation, and other incidental services to perform services in accordance with the below Performance Work Statement entitled, “Project

0005AA P2 O&M 12 Months $__________________ $_______________________

0005AB Travel 1 Job $66,000.00 (NTE)

0005AC Production Emergency 80 Hours $__________________ $_______________________

0006 CMR (OPTION YEAR 2) 1 Job $_______________________ accordance with below Performance Work Statement entitled, “Project Management Automated Information System (P2) Operations & Maintenance” dated 2 September 2015.

This CLIN is used for the pricing of the collection and reporting of Contractor Manpower Reporting data as described in the Performance Work Statement.

Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government Fiscal Year and must be reported by 31 October

TOTAL OPTION YEAR 2 (0005, 0005AA, 0005AB, 0005AC, AND 0006) $________________________

0007 FFP OPTION YEAR 3

equipment, transportation, and other incidental services to perform services in accordance with the below Performance Work Statement entitled, “Project

0007AA P2 O&M 12 Months $__________________ $_______________________

0007AB Travel 1 Job $66,000.00 (NTE)

0007AC Production Emergency 80 Hours $_________________ $_______________________

0008 CMR (OPTION YEAR 3) 1 Job $_______________________ accordance with below Performance Work Statement entitled, “Project Management Automated Information System (P2) Operations & Maintenance” dated 2 September 2015.

This CLIN is used for the pricing of the collection and reporting of Contractor Manpower Reporting data as described in the Performance Work Statement.

Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government Fiscal Year and must be reported by 31 October

TOTAL PRICE OPTION YEAR 3 (0007, 0007AA, 0007AB, 0007AC, AND 0008) $________________________

0009 FFP OPTION YEAR 4

equipment, transportation, and other incidental services to perform services in accordance with the below Performance Work Statement entitled, “Project

0009AA P2 O&M 12 Months $_________________ $_______________________

0009AB Travel 1 Job $66,000.00 (NTE)

0009AC Production Emergency 80 Hours $_________________ $_______________________

0010 CMR (OPTION YEAR 4) 1 Job $_______________________ accordance with below Performance Work Statement entitled, “Project Management Automated Information System (P2) Operations & Maintenance” dated 2 September 2015.

This CLIN is used for the pricing of the collection and reporting of Contractor Manpower Reporting data as described in the Performance Work Statement.

Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government Fiscal Year and must be reported by 31 October

TOTAL OPTION YEAR 4 (0009, 0009AA, 0009AB, 0009AC, AND 0010) $_______________________

Performance Work Statement (PWS) For

Project Management Automated Information System (P2)

Operations & Maintenance

S15-0254 2 September 2015

Performance Work Statement 02 Sep 2015 P2 O&M

© 2015 Project Management Business Process U.S. Army Corps of Engineers Page 2

1. Introduction: Operations and Maintenance (O&M) of the P2 System. The Project Management

Information System (P2) provides standard tools for Program and Project Managers and their Project Delivery Teams within the U.S. Army Corps of Engineers (USACE) to facilitate project planning, execution, and management in accordance with the Project Management Business Process (PMBP).

P2 is composed of a commercially available application. The successful offeror, herein referred to as the Service Provider (SP) or Contractor, shall perform all Operations and Maintenance necessary to keep P2 available to the users 24 hours per day/7 days per week/365 days per year.

2. Background: The U.S. Army Corps of Engineers developed P2 (currently in version 3.1.4) and is currently responsible for its technical operation and maintenance. Other Functional PMBP groups provide requirements that are used by the SP to modify and/or extend the existing P2 system hardware/software suite. The other PMBP groups also provide the functional testing, users guide modifications, training for new software updates, and the integration of new industry product solutions that compliment P2.

3. General Requirements: The scope of this O&M Plan for P2 is only for the operation and maintenance of the existing application(s), P2 EDW reporting, and corporate reporting. The service provider is responsible for the operation and support required to maintain the existing functionality of P2 and all system interfaces necessary for proper operation. P2 includes the Java software used to initiate and maintain projects, the commercial-off-the-shelf (COTS) package, Primavera, that is supported by Oracle and all customized software required to interface P2 with other USACE and Department of Defense (DoD) Automated Information Systems (AIS). Software maintenance of P2 includes modification to the software or components after delivery to correct faults, improve performance, adapt to a changed environment or most importantly in order to integrate new hardware such as Oracle’s T5 servers and iOS & Android based thin client applications.

a. Period of Performance. Performance will be for a base period of twelve (12) months from date of award which includes a 60 day transition period and 10 months of O&M, followed by four (4) option periods of twelve (12) months each, of O&M.

b. Transition. A transition period of 60 calendar days will be commence upon contract award to allow the contractor to reach full staffing and complete all personnel and facility security requirements described in the following paragraphs of this PWS. The Government will also take advantage of the transition period to configure and issue all required equipment to the Service Provider personnel and provide all the requisite system documents necessary to conduct O&M. The SP is not required to conduct system O&M until the conclusion of the transition period; these duties will be carried out by the incumbent under a separate contract.

c. Security Requirements: All personnel working on this project will be required to follow all security and access rules and regulations (i.e., physical access and/or network access requirements) as set forth by the US Government in order to gain access to the USACE offices and/or systems to perform work assignments and/or for the delivery of equipment to include DoD 8570 IT security requirements. This project has been determined to be “Sensitive Unclassified.” All documentation required for security certification (i.e. OPM SF85P) will be the responsibility of the SP.

d. The SP positions required for this contract are in the following two classifications (IT-II or IT-III). Individuals employed on this contract shall have a minimum IT-III current

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 3 background investigation or have one initiated at the start of employment. The P2 Project Manager along with the Contracting Officer Representative (COR) will determine the required level of investigation based on responsibilities:

IT-II – Example: Personnel in positions (operating system administration of common applications or enclaves, back-up operators) with limited privileged level access to control, manage, or configure ISs, AISs, and devices. Background Investigation is labeled NACLC, National Agency Check with Law and Credit. The NACLC will be used as the initial investigation for contractors at the Confidential, Secret, and L access levels. It will also be used as the reinvestigation product for both contractors and Federal employees at the same access levels. Secret clearance will be issued.

IT-III: General user. Background Investigation is labeled a NAC (national agency check without clearance).

e. Additional Security Requirements:

i. Antiterrorism (AT) Level I Training: All SP employees, including subcontractor employees, requiring access to Army installation, facilities, or 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 applies. The SP shall submit certificates of completion for each affected SP employee and subcontractor employee to the COR within 10 calendar days after completion of training by all employees and subcontractor personnel. AT Level I training is available at https://atlevel1.dtic.mil/at.

ii. Access and General Protection/Security Policy and Procedures: The SP and all associated subcontractors’ employees shall comply with applicable installation, access and local security policies and procedures. Policies and procedures will be provided by the local Security Office. The SP workforce must comply with all personal identity verification requirements as directed by DoD, Headquarters Department of Army, HQDA, and local policies. 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 SP security matters or processes.

iii. iWATCH Training: The SP and all associated subcontractors shall brief all employees on the USACE iWATCH program. This locally developed training will be used to inform employees of the type of behavior to watch for and instruct employees to report suspicious activity to the COR. The training shall be completed within 30 calendar days of contract award and within 30 days of new employees commencing performance on the contract. The SP shall provide certification of completion to the COR within 10 days of training completion. Training documents will be provided by the Security Office.

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 4

iv. Access to Government Information Systems: All SP employees with access to a Government information system must successfully complete the DoD Information Assurance Awareness training prior to access to the system and then annually thereafter.

v. Operations Security (OPSEC) Standing Operating Procedure/Plan: The SP and all associated subcontractor employees shall comply with applicable installation OPSEC plan and requirements to include initial OPSEC briefing within the period of performance of reporting to duty and annual training.

vi. Operations Security (OPSEC) Training: All new SP employees will complete Level I OPSEC training within the period of performance of their reporting duty. Additionally, all SP employees must complete annual OPSEC awareness training.

vii. Information Assurance (IA)/Information Technology (IT) Training: All SP employees and associated subcontractors’ employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All SP employees working IA/IT functions must comply with DoD and Army training requirements in DoD 8570.01, DoD 8570.01-M and AR 25-2 within 6 months of employment (http://www.dtic.mil/whs/directives/corres/pdf/857001m.pdf and http://armypubs.army.mil/epubs/pdf/r25_2.pdf)

viii. Information Assurance (IA)/Information Technology (IT) Training Certification:

All SP employees supporting IA/IT functions shall be appropriately certified upon contract in accordance with (IAW) DoD 8570.01-M, DFARS 252.239-7001 and AR 25-

2. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

ix. Handling/Access to Classified Information: The SP shall comply with AR 380-67 (Personnel Security Program) and Homeland Security Presidential Directive 12 (Policy for a Common Identification Standard for Federal Employees and Contractors) as well as FAR 52.204-2, Security Requirements.

x. Access to classified and/or sensitive materials and/or sensitive or restricted areas:

All SP employees, including subcontractor employees who are not in possession of the appropriate security clearance, will be escorted in areas where they may be exposed to classified and/or sensitive or restricted areas. The SP will coordinate with the COR and/or facility security office for access when required.

xi. Facility Clearance requirements: The SP Company must obtain a Facility Clearance at the appropriate level (IAW the NISPOM DoD 5220.22-M). The Facility clearance shall be completed during the 60 day transition period and prior to commencing the work.

f. Location of Work Performance. The work will be performed on the USACE CorpsNet network on location and/or via CorpsNet Virtual Private Network (VPN :

CONUS/OCONUS) at the USACE Central Process Center (CPC) Data Center 1165 Porters Chapel, Rd. Vicksburg Mississippi where the P2 production, development, test, and training environments are hosted. Work on the P2 Continuance of Operations, COOP, located at the Western Processing Center (WPC) Data Center will be performed in Portland Oregon likewise on location on CorpsNet and/or VPN. For functions not performed on location at

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 5

CPC or WPC, work will be performed via the SP’s facility via the use of CorpsNet VPN connectivity. SP facility must be available for Government inspection within 24 hours notice.

The Government will initiate and require specific attendance by the Contractor, at meetings, conferences and workshops, in support of the PWS requirements. The events will be held in Vicksburg, MS, and the SP will be notified at least one week prior to the event. Prior to attending these events, the Contractor shall provide the names and travel dates to the COR, so that any travel associated, may be tracked against this requirement.

The contractor's time associated with attending Government arranged meetings, conferences and workshops, shall be included in the CLIN prices for Travel. Costs associated with travel shall as described below. Entitlements and amounts related to travel shall be in accordance with the publication "Joint Travel Regulations" (JTR). For example, perdiem limitations are subject to rate limitation described in Ch 4: Temporary Duty Travel Part B: Per Diem.

Costs associated with travel, lodging and perdiem for attendance at meetings, conferences and workshops shall be included in the separately priced subclin entitled “Travel” as follows (yearly occurrences):

4 trips, 5 day duration for 3 individuals at the following location may be at either

Washington, DC, Vicksburg, MS, Nashville, TN, or Fort Worth, TX.

1 trip, 3 day duration for 15 individuals, where meeting location will be at Fort

Worth, TX.

Contract Line Items for travel, shall be priced following the practices and limitations of the Joint Travel Regulation https://www.defensetravel.dod.mil/Docs/perdiem/JTR.pdf. Invoices that include travel costs shall be accompanied by a breakdown of travel costs including transportation, lodging and perdiem, all of which shall be within the limitations of the JTR.

Travel that exceeds the quantities stated above, shall not be included as part of the contract price and shall not be reimbursed by the Government. If additional travel is required, the Government may negotiate additional scope for travel for the Contractors attendance at meetings, conferences or workshops, and add by issuing a modification to the contract. The Government reserves the right to negotiate a deductive modification if the quantity of actual travel is less than the quantities stated above. All terms, conditions and pricing shall be in accordance with the Joint Travel Regulation https://www.defensetravel.dod.mil/Docs/perdiem/JTR.pdf

g. POCs shall inspect all Services performed by the SP under this PWS through the final reports and provide feedback and acknowledgement of acceptance by the customer of the deliverables:

ACE-IT P2 Project Manager:

Peyton Lassiter, 601-634-4597, Peyton.E.Lassiter@usace.army.mil

ACE-IT P2 COR:

Ron Fletcher, 251-690-3405, Ronald.E.Fletcher@usace.army.mil

Contracting Officer:

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 6

Joan Kaimikaua, 808-835-4376, Joan.F.Kaimikaua@usace.army.mil

4. Performance Requirements: The ACE-IT Data Center is responsible for the P2 hardware, network, and database/application server hosting infrastructure. The SP will be responsible for operating and maintaining the application and software infrastructure components of the P2 system. This includes but is not limited to: Install, upgrade, and configure database and application software including:

IBM Data Stage, Oracle Portal, Oracle Reports, Oracle Internet Directory, Oracle Single Sign-on, Oracle Access Manager, Oracle Identity Manager, Oracle Databases, Primavera Web Logic Application Server, Primavera Web and Client Software patches, Application Upgrade of Primavera Databases, Primavera Job Services, and Java/Primavera Integration APIs. The P2 production environment (1TB) hosts 500 concurrent users (7,600 registers users).

The system reached its development maturity with the deployment of the latest version of P2 (P2v3.1). It has now transitioned from a “development” phase to a stable “sustainment & integration” phase. The SP will therefore be required to focus on the integration of existing & new COTS products with the Government provided hardware in order to exploit P2 data. In a recent study, Gartner Inc., stated that 90% of device adoption within the next four years will be in smart phones and tablets. In light of these facts and due to DoD-wide initiatives urging subordinate commands to leverage COTS solutions in lieu of Government off-the-shelf solutions (GOTS), the P2 strategic direction was modified to accommodate these new realities. Consequently, COTS software & hardware integration expertise will be a key SP requirement throughout the P2 O&M lifecycle.

Oracle’s P6 Analytics, BI Publisher and Primavera Team Member are example of such solutions in the P2 architecture roadmap. These products will require integration with Common Access Card (CAC) enabled thin clients such as Apple ipads, iphones and/or Android based devices. The SP shall be responsible for obtaining any security clearances required, and obtain P2 Program Management Office (PMO)/functional approval before any changes are migrated to production approval.

NOTE in reference to OFA: Operation and Maintenance of the Oracle Financial Application (OFA) COTS is NOT included in the scope of this PWS and will be performed by others (Subject Matter Experts). However, the successful offerer, or Service Provider, will be responsible for the operations and maintenance of scripts and interfaces that are dedicated to stage “OFA data” for the replacement systems (Oracle Hyperion Planning Plus, HPP, and Oracle Application Express, APEX).

5. P2 O&M Tasks (Refer to figures 1 & 3 for P2 system diagram and Appendix A for a list of acronyms):

a. Project Management: Provide software and project management services to accomplish the activities listed in this PWS and comply with the Quality Assurance Surveillance Plan (QASP). The ACE-IT Project Manager (Technical PM) is the primary point of contact with the customer and is responsible for all activities listed in section 5 and 7 of this PWS, to include the Project Management Plan (PMP) and all deliverables.

b. Program Management: Provide the necessary services to support the Program Management Office (PMO) in order to implement the P2 roadmap/strategic guidance document, manage the system release plan, develop strategy white papers, develop a strategy to consolidate reporting, and work with user groups to develop Functional Requirements Documents (FRDs) for future enhancements.

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 7

c. Maintain Information Assurance Posture and Functionality: Ensures the security of the P2 application by monitoring application audit logs and identifying and mitigating unauthorized application and database access:

1. Ensures all application roles and permissions are properly assigned.

2. Ensures all database accounts have appropriate access levels IAW least privilege best practices.

3. Ensures all system application and database passwords are changed IAW ACE-

IT/UPASS policy.

4. Coordinates with ACE-IT Data Center and performs all actions to maintain

DIACAP/Federal Information Security Management (FISMA) accreditation of P2.

d. Maintain System Documentation: The SP shall prepare and manage the availability of the System Database Architectural Documentation. The SP shall prepare, manage and maintain the DoD Information Assurance Certification and Accreditation Process (DIACAP) documentation required for System Certification and Accreditation (C&A).

1. Maintain currency of the P2 architecture documentation to support compliance with DIACAP and Business Enterprise Architecture (BEA).

2. Maintain currency of custom code documentation.

3. Maintain standard operation procedures (SOPs) and scripts for development, training, production and testing environments.

4. Maintain Functional Requirements Documents, Design & Specifications for all system components including the Fact Sheet Generator, ePMP and all interfaces.

e. Maintain Custom Built Software (PM+ and Staging Area): The SP shall maintain the following P2 system custom code:

1. Project Initiation and Maintenance (PM+) and staging area: 30,635 lines of database server code including functions, procedures, and packages, 580 database tables and objects including views, indexes, sequences, triggers, and synonyms. A detailed description of this application is shown in Appendices B, C and D of this PWS.

2. Corporate Management Information (CMI) (real-time data): 5,266 lines of database server code including functions, procedures, and packages, 148 database objects including views and indexes, and 17 database tables and objects including views, indexes, sequences, triggers, and synonyms.

3. WebCMI (real-time data): 988 lines of database server code including functions, procedures, and packages; 7979 lines of custom application code (visual basic)

4. Corps of Engineers Financial Management System (CEFMS), Oracle Financial Analyzer, OFA (or its replacement HPP and APEX), Common Integration Layer (CIL) Interface data staging: 12,302 of database server code including Functions, Procedures, and Packages, 6,230 database objects including views and indexes, 169 database tables and objects including views, indexes, sequences, triggers, and synonyms.

5. Admin App (Java Code): 60,998 lines of code (15% of total makes up Reorg process code = 9,149)

6. Implement code changes that are a direct result of a bug that stops the software from performing in the method defined by the functional requirement and/or the mode of performance accepted during deployment.

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 8

7. Implement code changes that are a direct result of a formalized functional requirement change in which requires a creation, modification or removal of a function in the software.

8. Implement code changes necessary to maintain P2 performance after software updates, to included COTS associated with P2, Server/Workstation O/S and security patches, Java upgrades and any other software updates/changes that impact P2 operation.

9. Maintain the custom IBM/Ascential DataStage configuration to include the 182 DataStage jobs used for data sharing by the CIL.

10. Maintain custom Procedural Language/Structured Query Language (PL/SQL) custom code: 47,990 lines of code to include stored procedures, functions and packages; 6,822 database tables and objects to include views, indexes, sequences, triggers, and synonyms (See appendices E-I for reference).

11. Maintain the webCMI custom code.

Figure 1: P2 application diagram

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 9

f. Maintain System Interfaces (Detailed descriptions of the interfaces are shown in Appendices E thru I of this PWS):

1. Maintain the interfaces between P2 and CEFMS, RMS, ACES, CAPCES, FUDSMIS and UPASS (see table below for brief description).

2. Develop & maintain scripts and procedures to stage data for Enterprise Data Warehouse (EDW), OFA or its replacement systems: Hyperion Planning Plus and Oracle Application Express and other enterprise AISs as needed.

3. Modify the P2 interfaces and modules as required to ensure compatibility with new data visualization software and thin client hardware solutions such as CAC enabled smart phones and tablets.

4. Support the integration of P2 application/COTS with CAC enabled devices (both iOS and Android). Support applications that enable mapping P2 projects/data with commercial applications such as Google Earth, Google Maps or Live Maps.

ACES

One way interface. DataStage process invokes PL/SQL package to extract data from ACES database to staging tables. Quartz scheduler executes Java procedure to create/update projects in PM+/Primavera (See Appendix E for a detailed description).

CAPCES

Two way interface. CAPCES sends a flat file to Unix directory twice per day. Datastage processes the file and populates staging tables evoking a PL/SQL package. Quartz scheduled Java procedure reads data to create/update projects in PM+/Primavera. The Outbound process creates two flat file for the Unix directory for CAPCES access (See Appendix F for a detailed description).

CEFMS

Financial, organizational, rates, actual costs, and employee information are extracted nightly from 60+ CEFMS databases. P2 project data including project and activity codes, WBS structure, activities, key members, and budget lines are sent to CEFMS (See Appendix G for a detailed description).

FUDSMIS

Two way interface. FUDSMIS connects P2 database to populate a staging table. Schedule Quartz process creates/updates projects in PM+/Primavera. FUDSMIS Outbound extracts Primavera data to a staging table for FUDSMIS to extract (See Appendix H for a detailed description).

OFA

DataStage processes populate PM+, Primavera, and CEFMS data into staging tables on a dedicated instance for OFA (or its replacement systems HPP & APEX) to extract nightly.

RMS

Two way interface. RMS invokes P2 PL/SQL Package to extract data from RMS to populate staging tables. Quartz scheduled Java process creates/updates projects in PM+/Primavera. The Outbound is a DataStage process loading Primavera data to a staging table for RMS to extract on demand. Interface uses PL/SQL, Java, Quartz, and DataStage (See Appendix I for a detailed description).

UPASS

One way interface. User account information is extracted from Oracle Internet Directory (OID) into staging tables. Quartz scheduled processes extract user information from staging tables to add or delete user accounts in Primavera. Interfaces use PL/SQL, Quartz, Java, and Primavera Java APIs.

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 10

g. Maintain the PMBP portal: The portal is the common entry point for P2 containing links to Primavera, PM+, custom P2 reporting, training, other P2 and USACE applications and the EDW as well as a P2 document repository. The portal consists of an Oracle Portal/Reports

11.1.1.6 Server installation with stored HTML and Document Library hosting both static and dynamic content.

h. Maintain P2 EDW Data structures & Corporate reports:

1. Provide support and maintenance for P2 repositories and all P2 EDW universes

(total of 36). A complete listing of universes can be seen in Appendix J.

2. Develop and Maintain all system reports to include configuration management:

Corporate reports 140 Oracle reports 20 OFA General reports 13 (Converted to Business Objects)

3. Provide support to the PMBP Project Tools such as the ePMP and the Fact Sheet Generators (FSG). These tools were developed in the Microsoft .NET development framework (Microsoft SQL and Internet Information Services IIS application server and database). PMBP Project Tools architecture consists of MS SQL Server 2008 R2, Figure 2: P2 EDW diagram

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 11

IIS 7.5, MS Application Server Pages (ASP) 4.0, MS Silver Light 5.1, and Adobe Flash 11.8

4. Monitor and maintain the nightly Extract/Transfer/Load (ETL) processes to load P2 data into the EDW.

5. Triage all P2 EDW ETL jobs upon failure and develop modified code migration documents to facilitate resolution for implementation by the ACE-IT EDW O&M team.

6. Provide routine updates to the EDW Universes modifying or adding fields to accommodate the yearly changes in the mission area's requirements and metrics.

i. Maintain and Administer Primavera: This is an Oracle enterprise Project Management software implementation configured to support 8,000 users in the U.S. Army Corps of Engineers. Evaluate Primavera software patches to ensure all components function as expected. The components include Primavera Web, Primavera Citrix client, Primavera reporting tools, P6 Analytics, Team member, BI publisher, Application Databases, Job Services, and Integration API.

j. Administer Oracle Database: The SP shall support the Oracle Database Administration, Design, and System Engineering Services required for the operations of P2. Coordinate with the ACE-IT Data Center to restore P2 Application services in the event of a disaster within the capabilities of the USACE COOP infrastructure and perform annual P2 Application COOP tests. Installation, configuration, upgrading, administration, monitoring, maintenance, and security of databases in an organization for the following environments:

1. Maintain P2 Development Environment: SP will maintain the P2 Development environment to support ongoing P2 software/code enhancements and bug fixes.

2. Maintain the P2 Testing Environment: The Service Provide will develop and execute test plans to validate releases, code updates, and upgrades for field functional testing.

3. Maintain P2 Training Environment: SP will maintain the P2 Training environment to ensure it is readily available to support the P2 training mission at all times. SP will ensure all training users are provisioned correctly in the P2 Training system and will coordinate with the ACE-IT UPASS team as necessary to ensure access is granted provided training students have executed all necessary enrollment steps. The P2 training environment supports approx 6,300 registered students and 250 students monthly in course delivery.

k. Helpdesk Support (Tiers 2 and 3): The trouble ticket reporting system, Tier 1, support (3,000 tickets/year) is NOT included in this PWS. The SP will be assigned trouble tickets for tiers 2 and 3 by the P2 HelpDesk. Estimate a total of 4,000 (tiers 2 and 3) tickets per year (includes system and P2 EDW tickets). The SP will acknowledge those tickets by next business day. Prior coordination for the transfer of existing and newly assigned tickets to other contract team-members will be performed in cases where the SP is on authorized TDY or vacation/leave. SP will accept, document and resolve incidents and approved change requests in accordance with the contract QASP. Tier 3 support consists of the management of change requests and/or bug fixes.

l. Off-Duty hour support: There are several occasions when the SP will be required to provide support beyond normal duty hours:

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 12

1. P2 Production Emergency Maintenance: For each period of Operation and Maintenance (base and each option period), the Contractor shall include in their CLIN prices for “Production Emergency Maintenance”, 80 hours of emergency maintenance, that is expected to be performed outside of normal duty hours. In the event of an unanticipated problems or an unplanned outage, the Government P2 Project Manager may declare an emergency maintenance situation. The SP will be required to assist the ACE-IT data center to restore the system back into production.

Emergency Maintenance labor will be requested in writing through a work order issued by the COR, stating the number of hours being requested, and the scope of the effort required. Historical records show that the emergencies occur approximately 4 times/year. The ACE-IT Data Center is responsible for maintaining P2 Infrastructure to include server hardware, network, and storage. In addition the ACE-IT Data Center maintains P2 Production Oracle software configuration and database configuration (including software/database patch levels). During an Emergency Maintenance activity, the SP as the P2 Application SME will be required to coordinate and validate the “point in time” of restoration from a time/data perspective with ACE-IT Data Center personnel. The Government reserves the right to negotiate a deductive modification at the end of a performance period, to reduce the price of the contract based on the number of unused Emergency Maintenance hours for that period.

2. P2 system releases: System releases are normally done outside the normal USACE

Continental United States (CONUS) duty schedule. The SP will be required to provide weekend support for 10 such releases in order to ensure system stability prior to the resumption of normal USACE operations.

3. Quarterly Reorganization Process: The SP will coordinate all aspects of the P2

Quarterly Reorganization (Reorg.) process as approved by the designated Government PM. The P2 Reorg Process is defined as the quarterly procedure in which steps are performed in P2 Primavera to synchronize the project management organizational structure with the financial organizational structure in CEFMS. P2 interface jobs are run to transfer the entire organizational structure and burden rate data from CEFMS to P2 for participating districts in the Reorg. The SP P2 Technical personnel will execute the processes in P2 to synchronize P2 project data structures with CEFMS financial data structures in according to the Government provided P2 Reorganization Process documentation. The reorg normally occurs 4 times a year during weekends. Coordination for reorgs is usually done during duty hours (see custom code section 5.d.4 in this PWS):

i. Coordinate with Headquarters (HQ) to determine reorganization dates.

ii. Coordinate with Users to gather and validate requirements for planned reorganizations.

iii. Coordinate with Users, CEFMS, Finance Center, and HQ to implement reorganization requests.

iv. Coordinate with the ACE-IT Enterprise Data Center to ensure systems are disabled and enabled appropriately pre/post Reorg execution.

v. Execute the P2 processes to synchronize P2 project data structures with

CEFMS financial data structures.

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 13

m. Maintain Oracle Financial Analyzer (OFA) replacement systems Oracle Hyperion Planning Plus (HPP) and Application Express (APEX): OFA is a complete application for financial reporting, data analysis, budgeting, and planning built upon an Oracle Express multidimensional database, which stores data in the way that managers think about their business. OFA will be phased out by the end of FY16; it is used primarily by Resource Management (HPP) and Civil Works. Additional information on OFA is shown in Appendix K:

1. OFA integrates a central source of management data with powerful analytical tools, allowing businesses to make, manage, and measure decisions across the enterprise.

The system provides businesses with everything they need to control costs, analyze performance, evaluate opportunities, and formulate future direction. Extensive customizations have been implemented within the underlying Oracle Express database (via programs that utilize the Oracle Express Stored Procedure Language) as well as UNIX shell scripts to provide an automated mechanism for nightly updates from the P2 source systems.

2. Additional customizations have been implemented within the data entry forms to enable OFA to meet various USACE business process objectives. The approximate size of the deployed OFA databases (OFA Manpower, Workload/Workforce Planning, Civil Works, and General) is 160GB.

3. OFA is administered using tiered client-server architecture. The OFA Client and Oracle Express Administrator applications represent the client component. Oracle Express Server represents the server component. The Oracle Express SNAPI (Structured N-Dimensional Application Programming Interface) supports the client-server processing model.

4. OFA is also accessed by end users using tiered client-server architecture. The OFA Web application (in conjunction with utilizing a web browser) represents the client component. Oracle Express Server; including the Oracle Express Web Agent component, represents the server component. An Apache web listener supports the client-server processing model.

n. Maintain Corporate Management Information (CMI/WebCMI): CMI is a custom web-based application for real-time consolidated project viewing without the need for an Oracle Primavera license or responsibility assignment. CMI consolidates project, schedule, budget, expenditures, comments, and ePMP documentation into a web interface via the P2 PMBP Portal. WebCMI is an offsite reporting tool that uses a data extract from the production P2 databases. WebCMI provides specific reports and summary metrics for Headquarters USACE. WebCMI is accessible to USACE and military installation customers only:

1. CMI is access by end users using the P2 Oracle 11g Portal, Reports, and Database client-server framework providing web-based access to P2 data via web-browser.

2. WebCMI is also accessed by end users via web browser using tiered client-server architecture. The WebCMI application consists of a Microsoft Server 2008 application server framework that includes an Oracle database and custom batch jobs written in Visual basic that facilitate and monitors the data transfer from the P2 production environment.

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 14 uction. WebCMI provides reports via Microsoft Automation Server and Access components.

Figure 3: P2 detailed system diagram

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 15

6. Quality Assurance Surveillance Plan (QASP): The purpose of the QASP is to provide an overarching strategy and methodology to evaluate Contractor performance. More specifically, the QASP outlines the methods and procedures the Government intends to use to evaluate Contractor compliance with all requirements outlined in the PWS. This QASP is based on the premise that the Government desires to maintain a high quality standard in operating and maintaining the USACE P2 System and Application Code and that a service contract to provide the service is the best means of achieving that objective. The SP, and NOT the Government, is responsible for management and quality control actions to meet the terms of the contract. The role of the Government is conduct quality assurance in order to ensure that contract standards are met. In this contract the quality control program is the driver for service quality. The SP is required to develop a comprehensive program of inspections and monitoring actions. This QASP provides for the following:

a. Metrics (Identification of the metrics and parameters that will be monitored and assessed): The ACE-IT PM will be responsible with assembling all Contractor performance data. The Contractor will provide performance data, commentary regarding monthly analysis, Root Cause Analysis and Performance Improvement Plan, not later than the 10th of the month for previous month’s performance evaluation. The Government will use the Contract data to validate monthly invoices. The ACE-IT PM or designated government personnel will audit the Contractor’s submittal for accuracy, completeness, consistency and compliance. The initial rating period will begin 30 days after contract startup. There will be monthly PRB meetings to review performance and identify under-performing or downward trending areas that are in need of improvement. Performance improvement initiatives will be identified and tracked to completion. New and existing metric and service level modifications will be identified and jointly approved.

b. Monitoring (Definition of the monitoring strategy and approach): The QASP will incorporate

100% inspection of performance reports. In addition, the PRB will supplement performance report reviews with random, detailed audits of raw data from the Contractor reporting system to ensure that reported performance is consistent with the raw data. All Contractor reporting systems will be validated and verified at least annually to ensure alignment of system to task order requirements. Acceptable Performance. The Government defines acceptable performance as meeting the performance threshold in accordance with the criteria defined in this PWS. The Government will document its surveillance assessment of Contractor performance on a monthly basis. Unacceptable Performance. When the performance for any service does not meet the threshold requirements, the Contractor’s performance is unsatisfactory. The PCO will notify the contractor of unacceptable performance in writing by filling a Performance Assessment Report (PAR) – sample enclosed. The PCO and the ACE- IT PM will meet with the Contractor to discuss discrepancies, trends, and intended corrective measures. The following surveillance methods will be employed to verify and validate performance information:

I. Performance Objectives: The Government COR will inspect all work tasks required by the contract provided in the monthly utilization report to ensure SP compliance. If inspection of the monthly utilization report indicates unacceptable performance, the COR will notify the contract manager or QCI of the deficiencies for correction. The SP shall be given adequate time after notification to correct the unacceptable performance.

Performance Work Statement 02 Sep 2015

U.S. Army Corps of Engineers Page 16

II. Performance Demonstration and Observation. The Government will employ a system that provides for direct observation of performance, operation, and data collection, analysis and reporting. The ACE-IT PM will provide the contractor with the monthly Performance Assessment Report on a monthly basis (Form enclosed at the end of the PWS).

III. Performance Auditing/Analysis. This method will be executed by examining and assessing the application of tools and approved techniques in order to determine if the reports delivered are consistent and accurate. Performance auditing will be executed using multiple statistical sampling methodologies (Random).

IV. Independent measurements using Government Information Systems. This method employs the use of Independent tools to replicate the approved measurement process and procedures. Input from other internal and external interfaces (CAPCES, ACES, EDW, OFA, Training/Test environment support, etc.).

V. Customer Satisfaction Survey. All service requests and incidents (REMEDY) will generate customer satisfaction surveys at the completion of service. Periodic random surveys will be conducted to solicit stakeholder feedback.

VI. User complaints: The ACE-IT Project Manager, or any member of the PMBP National Team, may receive complaints from Government personnel and pass them to the Contractor’s Project Manager or quality control inspector (QCI) for correction.

Complaints can be initiated by any random…