PWS_for_CPP_(14_Nov_2018).pdf

PERFORMANCE WORK STATEMENT (PWS)

For Cost and Performance Portal (CPP)

PART 1

GENERAL INFORMATION

1.1 Description of Services/Introduction: The contractor shall provide all personnel labor and support necessary to perform services in support of the Cost and Performance Portal (CPP) and the Programs and Strategy Directorate of the Office of the Assistant Secretary of the Army (Financial Management and Comptroller), as defined in this PWS, except as specified in Part 3 as government furnished property and services. In addition to the technical aspects of managing the portal, this will also include analytical support, building models, and providing visualized results in support of cost management and performance. These requirements will be managed within the Office of the Assistant Secretary of the Army (Financial Management & Comptroller) (ASA (FM&C)) under the direction of the Deputy Secretary of the Army – Cost and Economics

(DASA-CE).

1.2 Background: The CPP gives senior leaders the ability to quickly access important information regarding the status of programs, as well as providing cost and performance information used in Army analysis and decision making. The CPP reduces the time needed to prepare briefing materials and enables senior leaders to quickly analyze Army program performance from their computer workstations. The CPP uses government owned and operated commercial, off-the-shelf (COTS) Oracle Corporation software to digitally display and analyze performance measures, create tailored views of performance information using dashboards, automate and improve business processes, and provide senior leaders an on-line capability to interact with analysts to request/view analysis/variance data (spreadsheets, documents, presentations, reports) for a variety of Army initiatives. The COTS software utilized by CPP is the Oracle Business Intelligence Enterprise Edition (OBIEE), WebCenter Portal, WebLogic Server Enterprise Edition, Oracle Database Enterprise Edition, Oracle Partitioning, and other required supporting Oracle integration tools. Historically, the CPP has been called the Performance Metrics Warehouse.

1.3 Objectives:

1.3.1 Support Army senior leaders by providing strategic level financial and performance metrics reporting to aid in Army decision making.

1.3.2 Build and maintain centralized analytical tools accessible over the Internet for Army cost analysts to aid in accurate and consistent analysis.

1.3.3 Provide reports identifying the costs for various services, programs, and potential scenarios.

1.3.4 Provide tools to track cost, budget, and personnel reductions against targets for Army organizations.

1.3.5 Create and maintain tools to automate Army business processes.

1.3.6 Provide expert support to improve the Army’s ability to use new systems and technologies to support cost management.

1.4 Scope: The contractor shall provide technical services in support of DASA-CE’s CPP.

Services include:

- Install, Configure, Maintain Hardware and Software;

- Design, Implement, and Test WebCenter Portal Content;

- Design, Implement, Test, and Debug OBIEE Content;

- Design, Create, Populate, and Maintain CPP’s Data Warehouse;

- Maintain User Accounts and CPP Documentation;

- Work with Hosting Center and GFEBS Cost Management Support;

- Maintain Oracle Database, Oracle Access Manager, Oracle Internet Directory, Oracle

Content Server.

The contractor shall also supply expertise and guidance to create cost reporting and management tools and business processes.

1.5 Period of Performance: One (1) Base Year and Two (2) Option Years

1.6 General Information.

1.6.1 Quality Control (QC): The contractor shall develop and maintain an effective quality control program 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 quality control program is the means by which the contractor assures that the work complies with the requirement of the contract. As a minimum, the contractor shall develop quality control procedures that address the areas identified in Technical Exhibit 1, “Performance Requirements Summary”. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to its QC system. The quality control plan should be included in the contractor’s proposal submission.

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

1.6.3 Recognized Holidays: The contractor is not required to perform services on the following days:

New Year’s Day Labor Day Martin Luther King Jr. Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.4 Hours of Operation/Place of Performance: The contractor is responsible for conducting work between the hours of 0730 hours to 1700 hours Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the work force are essential.

Places of Performance: Remote working is permitted; contractor will be required to support personnel located in the Pentagon, and Fort Belvoir, VA.

1.6.5 Reserved

1.6.6 Security Requirements: All contractors must also either possess an active secret security clearance or be in process for a secret clearance prior to working with any data or systems related to GFEBS or the Cost and Performance Portal.

1.6.6.1 AT/OPSEC Requirements:

1.6.6.1.1 AT Level I Training. AT Level I Training. This provision/contract text is for contractor employees with an area of performance within an Army controlled installation, facility or area. All contracting employees, to include subcontracting employees, requiring access to government 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: https://atlevel1.dtic.mil/at.

1.6.6.1.2 Reserved

1.6.6.1.3 iWATCH Training. iWATCH Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area.

The contractor and all associated sub-contractors 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 COR. 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.

1.6.6.1.4 Access and General Protection/Security Policy and Procedures. Access and General Protection/Security Policy and Procedures. This standard language text is for contractor employees with an area of performance within an Army controlled installation, facility or area.

Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also 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 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.

1.6.6.1.5 Handling or Access to Classified Information. 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); any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

1.6.6.1.6 OPSEC Training. Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training.

1.6.6.1.7 Information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor 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 within six months of employment.

1.6.6.1.8 Contractor Employees Who Require Access to Government Information Systems.

All contractor employees with access to a government info system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter.

1.6.6.2 Physical Security. The contractor shall be responsible for safeguarding all government property provided for contractor use. At the close of each work day, government facilities, equipment, and materials shall be secured.

1.6.6.3 Key Control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

1.6.6.3.1. Lost Keys: In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

1.6.6.3.2. Contractor Access Control: The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.6.4 Lock Combinations: The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.7 Conservation of Utilities. The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount.

1.6.8 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the Contracting Officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.9 Contract Manager: The contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

1.6.10 Key Personnel: Key personnel include a Sr. Program Manager, a Sr. Database Architect, a Business Analyst, a Principle Systems Engineer, and an Application Designer. At least two Contractor personnel shall have experience in creating, customizing, and retrieving reports in SAP, specifically with the SAP cost and project systems modules, preferably with GFEBS. In addition, at least two Contractor personnel shall have knowledge and experience with financial management and the structure and management of the Army. These skills will enable them to design dashboards/workflow tools/models useful to Army Leaders, retrieve data from GFEBS to populate the model, manage the databases and display software needed. Key personnel are as follows:

Sr. Database Architect 1 FTE

Experience: Shall have a minimum of seven years of experience directly working with the design, maintenance and coding of databases, and at least five specifically with Oracle Database and OBIEE, Oracle Web Center Portal, and Oracle Application Express (APEX).

Also requires advanced knowledge of the principles, methods, and techniques used in all phases of database development, coding, and design, including business analysis, event modeling, logical and physical database design, data access analysis and design, DBMS optimization, archive and recovery strategy, load strategy design and implementation, security, and change management.

Must have excellent communication skills both written and oral.

Education: Shall have a Master of Science Degree.

Principle Systems Engineer 1FTE

Functional Responsibility: Maintain hardware reliability, system level security, system level performance monitoring and tuning, and automation of production activities including extract and load functions, repetitively produced queries/reports, etc. Ensuring that appropriate disaster recovery functions such as system level backups are performed correctly and on an accepted schedule. Establishes state-of-the-art techniques for designing, developing, modifying and troubleshooting complex computer operating/hardware systems; may work independently on projects requiring advanced, concentrated and diversified knowledge regarding engineering principles in broad assignment areas or may serve as project lead with supervisory responsibilities. Designs operating/hardware systems; formulates system concepts and architecture, specifies requirements, and develops implementation approaches;

identifies and directs resolution of complex hardware/software interface issues; subject matter expert on emerging technologies; directs the development of systems specifications and technical documentation; may serve as project lead, either working independently in a technical role in field of specialization, or in providing work leadership with management or supervisory responsibility for the group.

Experience: Shall have a minimum of ten years directly related experience in all phases of systems engineering, with Oracle products in general, and at least five in specific maintaining Oracle Database, Oracle Access Manager, Oracle Internet Directory, Oracle Content Server, Oracle WebCenter Portal, Oracle Business Intelligence Enterprise Edition. Requires knowledge of the principles, methods, and techniques used in all phases of the engineering, application, and development of multiple operating systems.

Must have excellent communication skills both written and oral.

Education: Shall have a Master of Science Degree.

Jr. Systems Engineer 1 FTE

Functional Responsibility: Support Principle Systems Engineer in maintaining hardware reliability, system level security, system level performance monitoring and tuning, and automation of production activities including extract and load functions, repetitively produced queries/reports, etc. Ensuring that appropriate disaster recovery functions such as system level backups are performed correctly and on an accepted schedule. Establishes state-of-the-art techniques for designing, developing, modifying and troubleshooting complex computer operating/hardware systems; may work independently on projects requiring advanced, concentrated and diversified knowledge regarding engineering principles in broad assignment areas or may serve as project lead with supervisory responsibilities. Designs operating/hardware systems; formulates system concepts and architecture, specifies requirements, and develops implementation approaches; identifies and directs resolution of complex hardware/software interface issues; subject matter expert on emerging technologies;

directs the development of systems specifications and technical documentation; may serve as project lead, either working independently in a technical role in field of specialization, or in providing work leadership with management or supervisory responsibility for the group.

Experience: Shall have a minimum of five years directly related experience in all phases of systems engineering, with Oracle products in general, and at least three in specific maintaining Oracle Database, Oracle Access Manager, Oracle Internet Directory, Oracle Content Server, Oracle WebCenter Portal, Oracle Business Intelligence Enterprise Edition. Requires knowledge of the principles, methods, and techniques used in all phases of the engineering, application, and development of multiple operating systems.

Must demonstrate experience writing technical documents to support Risk Management Framework (RMF) audits, Approval to Operate (ATO), DISA Security Technical Implementation Guides (STIGs), and Information Assurance Vulnerability Assessments (IAVAs) and exhibit familiarity with Army regulations; AR 25-1 Information Management Army Information Technology and AR 25-2 Information Assurance.

Education: Shall have a Bachelor of Science Degree.

Proprietary Production Application Designer, 1 FTE

Functional Responsibility: The application designer will create and administer Oracle portals using WebCenter Portal, build portal templates and page templates, and add content, services, and components to them. They shall have experience working with Oracle database, Oracle Business Intelligence Enterprise Edition, Oracle WebCenter Portal, and Oracle Application Express (APEX) software.

Expertise shall be demonstrated with at least 7 years of experience working with these products, or a combination of experience and certifications.

Must have excellent communication skills both written and oral.

Education: Shall have a Bachelor of Science Degree.

Business Analyst 1 FTE

Minimum/General Experience: Eight years of intensive and progressive experience in the individual's field of study and specialization.

Specialized experience includes: gathering and writing technical requirements, quantitative analysis, computer modeling, forecasting, management consulting, showcase strong technical and non-technical communication with non-technical and technical customers, demonstrate familiarity with DoD financial information (PPBE process), understand federal budget terminology (obligations, disbursements, and POM cycle), and the ability to effectively use applicable tools and techniques.

Functional Responsibility: Provides technical consulting support to Division Chiefs and Senior Analysts for cost models, data bases, cost factors and analyses. Designs, organizes, leads, and conducts maintenance and improvements of cost estimating models, tools and/or data development. Provides cost estimates.

Education: Bachelor's degree in Information Systems, Engineering, Business, or a Quantitative discipline such as statistics or economics or other related discipline

Non-Key Personnel

Title Description Quantity

Required

(FTE)

Minimum Education

Minimum Years Specific Experience

Data Scientist

Experience in quantitative analysis, computer modeling, and support cost analysis with metrics

1 BS/BA 4 years

Knowledge Management Specialist

Experience in collecting, organizing, displaying, sharing, and maintaining organizational knowledge

1/2 BS/BA 2 years

Database Administrator

Will support the Sr.

Database Architect

1 BS/BA 2 years

Web Graphics Designer

Experience in WebCenter Portal, and User Interface Experience

1/2 BS/BA 5 years

For experience with specific software, a combination of Oracle certifications and experience in those software may be substituted. Non-Key Personnel may provide resumes to demonstrate their collective ability to perform the technical, analytical, and financial services described in the tasks in Part 5 of the PWS.

1.6.11 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel shall obtain and display contractor badges at all times while performing the services in the PWS. The contractor shall have all personnel to fill out the necessary paperwork to obtain Common Access Cards (CAC) and Building passes for access to certain government facilities.

1.6.12 Manpower Reporting: Contractor and Manpower Reporting Requirement: The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where The Contractor shall report ALL contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor is required to completely fill in all the information in the format using the following web address:

https://contractormanpower.army.pentagon.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5) Actual direct labor hours (including sub-contractors); (6) Actual direct labor dollars paid this reporting period; (7) Total payments (including sub-contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information); (11) Locations where the contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country). As part of its submission, contractor shall provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor’s systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web site.

1.6.13 Contractor Travel: The contractor may be required to travel CONUS. Travel costs shall be paid only when authorized by the Government as prescribed by FAR 31.205-46. See Joint Travel Regulation, Appendix E3, Part 3, Government Contractors/Contractor Employee Travel for other information concerning Contractor access to certain Government transportation programs. Travel is not expected to exceed five percent (5%) of time for one or two FTEs.

1.7 Transition Period: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have Key Personnel on board during the thirty (30) day Transition Period. The contractor shall manage an overlap of operations with the replacement provider in accomplishment of tasks beginning at the end of the contract.

1.7.1 Phase-In: The Contractor shall be responsible for conducting all tasks necessary to be capable of fully performing within 30 days after contract award without disruption or degradation of the Operation Readiness mission. The contractor is responsible for coordination of all information needed to obtain appropriate access to facilities and badges required by government sites. Contractor Phase-In tasks include ensuring that sufficient resources, fully trained and qualified to perform the requirements set forth in the PWS, are on hand and available to begin work on the first day after the 30 day Start-up period.

1.7.2 Phase-Out: The Contractor shall be responsible for providing a phase-out plan with the proposal, which enables a smooth transition to replacement services for one-month when the contract ends (including technical data rights considerations). The plan shall provide phase-in support for up to 30 days to the selected contractor if the incumbent contractor is not selected for subsequent contract. The contractor is responsible for returning all badges and access obtained as a result of performance under the contract. Contractor Phase-out tasks include ensuring that sufficient resources are available to perform the requirements set forth in the PWS during the 30 day Phase-out period.

PART 2

DEFINITIONS & ACRONYMS

CLIN - Contract Line Item Number PWS - Performance Work Statement COR - Contracting Officer’s Representative: A representative from the requiring activity assigned by the Contracting Officer to perform surveillance and to act as liaison to the contractor NCRCC – National Capital Region Contracting Center QASP - Quality Assurance Surveillance Plan: An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

Defective Service - A service output that does not meet the standard of performance associated with it in the Performance Work Statement.

Quality Control - Those actions taken by a contractor to control the performance of services so that they meet the requirements of the PWS.

Quality Assurance - Those actions taken by the government to assure services meet the requirements of the Performance Work Statement.

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3.1 GENERAL: The government shall provide, the facilities, equipment, materials, and/or services listed below.

3.2 Utilities. All utilities in the facility will be available for the contractor’s use in performance of duties outlined in this PWS. The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities.

3.3 Facilities: The Government will furnish the necessary workspace for the contractor staff to provide the support outlined in this PWS to include desk space, telephones, computers and other items necessary to maintain an office environment.

3.4 Software: The Government will provide the Oracle Software used by the portal.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4.1 General: Except for those items specifically stated to be government furnished in Part 3, the contractor shall furnish everything required to perform this PWS.

PART 5

SPECIFIC TASKS

BASIC SERVICES: The contractor shall provide support services to support DASA-CE’s Cost and Performance Portal (CPP), cost models, and cost data.

The CPP approximate size, subject to change, is:

• Database size: Allocated/Used

• Production (500GB/300GB)

• Development (300GB/220GB)

• Test (300GB/35GB)

• External Interfaces: 3

• Users: 7,500, with 2,000 active in the last year

• Lies of code: estimated 21,500

5.1 Install, Configure, and Maintain government furnished Oracle COTS Software:

Contractor shall install, patch, configure, and maintain all government furnished Oracle software to support the cost and performance management program as required. The Government currently utilizes the Win 2008R2 Datacenter web server to host the CPP and its applications and the following versions of Oracle add-on products:

• Oracle Enterprise Server (Database) 11.1.0.4

• Oracle Identity Management (OIM) 11.1.1.9

• Oracle Identity and Access Management (OIAM) 11.1.2.3

• Oracle Business Intelligence Enterprise Edition (OBIEE) 11.1.1.9, 12.2.1.4

• Oracle WebCenter Portal 11.1.1.9

• Oracle WebLogic Server 10.3.6, 12.2.1.3

• Oracle HTTP Server (OHS) 12.2.1.3

The following Oracle development tools and Oracle add-on products are utilized to implement/maintain the CPP and its applications functionality:

• SQL Developer (ver 3.2)

• OBIEE RPD tool Version 11.1.1.9, 12.2.1.4

• Jdeveloper 11.1.1.9

The Government utilizes PL/SQL, Java and Javascript programming/scripting languages for the CPP application functionality.

5.1.1 Contractor shall ensure the Oracle software installed is concurrent with Oracle supported versions and complies with Army and DOD regulations (eg. AR 25-1 & AR 25-2, DoDI 8500.01 & DoDI 8510.01)

5.1.2 Contractors shall provide required account information to allow the CPP hosting center access to scan Oracle software components or perform other maintenance, tests, and upgrades as required.

5.1.3 The contractor shall manage and maintain a secure single sign on for all CPP components

5.1.4 Contract shall configure the CPP to use CAC/PKI to authenticate users. Should authentication methods need to change, the contractor shall be responsible for implementing authentication procedures that conform to DOD and Army IA standards for all CPP components.

5.1.5 Contractor shall provide Oracle Application database administration services for all components of the CPP. Services include but are not limited to: logging and working on Oracle service requests (SR), copying environments, troubleshooting issues.

5.1.6 Contractor shall provide a written report on the status of all major CPP hardware and software components at least monthly to the COTR.

5.1.7 Contractor shall immediately notify the COTR of any significant technical disruptions to any environment. The written component of this notification will include date, time, extent of issue, resolution, and estimated time to resolution.

5.1.8 Contractor will be responsible for remediating any issues that arises with CPP in a manner which minimizes any potential service disruptions. Such remediation must have the approval of the COTR

5.1.9 Contractor shall provide written plans, work breakdowns, and schedules for any upgrades or changes. The plans and schedules must be approved by the COTR. The contractor shall provide weekly updates on the progress of these changes.

5.1.10 Contractor shall notify the COTR within 48 hours if they are unable to access any component of the CPP. The written component of this notification will include date, time, extent of issue, resolution, and estimated time to resolution.

5.2 Create and maintain Oracle WebCenter Portal Reports and Tools

5.2.1 Contractor shall create and maintain Oracle WebCenter Portal reports and tools as required using industry best web development practices and procedures and will utilize COTS methods when available.

5.2.2 Contractor shall resolve portlet, display, interface, and component errors as required.

5.2.3 Contractor shall log, update, and monitor My Oracle Support service requests (SR) to resolve issues with Oracle products.

5.2.4 Contractor shall support maintenance of separate development, test, and production Oracle WebCenter Portal reports.

5.2.5 Contractor shall present designs and prototype of Oracle WebCenter Portal reports and tools to the COTR and receive approval prior to implementing.

5.2.6 Contractor shall create copies of reports and tools store them in a location specified by the COTR.

5.2.7 Contractor shall be familiar, if not certified, in topics such as Oracle WebCenter Portal Concepts, Portal Architecture, Portal Builder, Integrating Content, Mobile, Social, Skinning, Page Templates and Integration with other Oracle technology.

5.2.8 Contractor shall update, and redesign if necessary, the look and feel of the CPP, Web Center Portal.

5.3 Create and Maintain Oracle Business Intelligence Enterprise Edition (OBIEE) Reports

5.3.1 Contractor shall use government furnished OBIEE software or equivalent COTS software to create and maintain reports, generate user reports, balanced scorecard and dashboards containing: key performance indicators (KPIs), series, benchmarks, and dimensions.

5.3.2 Contractor shall resolve errors with OBIEE or equivalent COTS software as required.

5.3.3 Contractor shall log, update, and monitor My Oracle Support service requests (SR) to solve OBIEE or equivalent COTS software report errors.

5.3.4 Contractor shall present draft OBIEE or equivalent COTS software reports to the COTR and receive approval prior to implementing in a production environment.

5.3.5 Contractor shall present designs and samples of OBIEE reports and content to PROGRAMS & STRATEGY DIRECTORATE and COTR prior to deploying finalized reports.

All designs must be approved by the COTR.

5.3.6 Contractor shall create customer defined “canned” reports that all CPP users will be able access and download.

5.4 Create and maintain reports and tools using Oracle Application Express (APEX) or an Equivalent Product of DASA-CE’s choice

5.4.1 Contractor shall support the maintenance of the following reports and tools: Capabilities Knowledge Base (CKB), Cost Benefit Analysis Workflow Tool, Army Cost Framework Tool, Military Personnel Army Forecasting Tool and Reports, Cost Review Board App, and other reports and tools as required.

5.4.2 Contractor shall use Oracle Application Express COTS software or an equivalent product to generate other tools and reports.

5.5 Create, Populate, and Maintain CPP’s Data Repository

5.5.1 Contractor shall maintain the data repository in development, test, and production environments.

5.5.2 Contractor shall perform all necessary data management and manipulation in the data repository using tools such as, SQL Loader and Oracle PL/SQL or an equivalent product.

5.5.3 All data management processes, tools, formulas, and procedures used to perform them must be submitted in writing to the COTR. All tools, formulas, or procedures necessary to perform ETL processes must be appropriately documented and commented so as to be readily transparent.

5.5.4 Contractor shall use a variety of means to acquire and load data, including: data repository links, connections, and flat files.

5.5.5 Contractor shall create forms and reports to automate the collection of performance metric data and integrate and transfer data using various means.

5.5.6 Contractor shall ensure all data housed in the CPP data repository is up-to-date and accurate at all times.

5.5.7 When business rules for handling data are provided by the customer, the contractor shall apply those rules to the appropriate processes in the data repository. Contractor shall document all business rules provided by customers indicating at a minimum:

• The tables, data elements, and conditions involved in said business rule

• The organization and individual(s) identifying this business rule

• Any reporting impacts that would occur from implementing this rule

• Any potentially conflicting business rules

5.5.8 Contractor shall monitor table space sizes, monitor job loads, and ensuring jobs run to completion.

5.5.9 Contractor shall ensure that all data management and extraction from ODASA-CE data repositories is accurate and efficient.

5.5.10 Contractor shall obtain, and update Army operational, financial and performance data and store it in the CPP data repository as required.

5.5.11 Contractor shall identify and analyze new sources of data to be integrated in the CPP’s data repository as required.

5.5.12 Contractor shall define and describe all data elements and relationships contained in the CPP data warehouse. Updates shall be made monthly as required.

5.5.13 Contractor shall provide CPP’s data warehouse data for all the CPP tools, including but not limited to, OBIEE and WebCenter Portal.

5.5.14 Contractor shall provide data to Army or DOD systems as required using standard methods identified by the COTR as required.

5.5.15 Contractor shall ensure that all data CPP used in reports or tools on the C&P can be exported into Microsoft Excel (any version; comma separated value files are acceptable).

5.5.16 Contractor shall validate all data against official definition tables where available.

Contractor shall also validate data against any crosswalk tables, and keep separate tables for exceptions. Contractor shall remediate exceptions based on guidance from the COTR.

Contractor shall explicitly document the number and kinds of exceptions in any dataset and any assumptions or rules used to correct them.

5.5.17 Contractor shall run comparisons of data contained within Cost and Performance Portal tables or reports against official Army or organizational reports as directed. Contractor shall identify any areas where discrepancies exist and if possible identify any possible causes.

5.6 User Account Maintenance

5.6.1 Contractor shall enable/disable CPP user accounts based on user account requests.

5.6.2 Contractor shall update existing CPP user account creation and provisioning procedures 30 Days after contract award and update the procedures on a monthly basis as required.

5.6.3 Contractor shall make necessary modifications to the CPP user account creation processes as required by the COTR.

5.7 Documentation for COST AND PERFORMANCE PORTAL (CPP)

5.7.1 Contractor shall create, update, and maintain all documentation of the configuration and administration of the CPP. Contractor shall ensure that all relevant materials are available on either Army Knowledge Online or a SharePoint site as directed by the COTR. Documentation shall include but is not limited to: data dictionaries of all databases/data warehouses, data sources and flow diagrams, system architecture diagrams, and project schedules.

5.7.2 Contractor shall create training materials for the CPP as required including but not limited to: user manuals, power point briefings, screenshots, and multimedia downloadable/streaming training guides.

5.7.3 The contractor shall create and maintain data flow diagrams, system architecture diagrams, documentation of tools and models, and project schedules as required.

5.7.4 The contractor shall create and maintain project schedules based on milestones developed by the COTR as required.

5.7.5 The contractor shall create functional requirements and design documents for any new projects or changes to existing projects. These requirements must be approved by the COTR.

5.7.6 The contractor shall create and maintain Cost Management documents relevant to the tools and models on CPP.

5.8 Working with Hosting Center

5.8.1 Contractor shall communicate with the CPP hosting center staff as required.

5.8.2 Contractor shall adhere to all hosting center security regulations and procedures when accessing all components of the CPP.

5.8.3 Contractor shall travel to perform on-site support to the CPP hosting center as required by the customer.

5.8.4 Contractor shall provide advice and guidance on migrating hardware or Oracle COTS software, should any changes in hosting occur.

5.8.5 Contractors shall fully test hardware and Oracle COTS software during and after any major move or reconfiguration

5.9 Cost and Performance Portal (CPP) Help Desk

5.9.1 Contractor shall be responsible for monitoring and addressing help desk requests.

Currently help desk requests are not tracked apart from the email account in which they are received.

5.9.2 All help desk requests shall be visible to the entire CPP team

5.9.3 Contractor shall refer all help desk requests requiring guidance to the COTR.

5.9.4 All requests shall be closed within seven days. Every week contractor shall make a report to the COTR of all help desk tickets still open.

5.10 Business Analysis / Requirements Gathering, Analysis, and Documenting

5.10.1 The contractor shall conduct analytical activities, including but not limited to, querying data, building models, and providing visualized results, and analyzing business intelligence reports, as requested by the COTR. Sources of data may include but are not limited to: General Funds Enterprise Business System (GFEBS), Global Combat Support System Army (GCSS-A), Logistics Modernization Program (LMP).

5.10.2 The contractor shall perform requirements gathering across Army customers to DASA- CE as required by the COTR. This includes facilitating requirements workshops and producing artifacts of “as-is” business processes and “to-be” business processes and depicting requirements both graphically and in textual contexts.

5.10.3 The contractor shall support the COTR in outreach efforts to encourage the use of cost management practices or financial performance assessments in Army Commands, organizational activities, and end to end processes.

5.10.4 The contractor will support development of training materials on the processes to conduct cost management and financial performance assessments, with subjects including problem definition, development of performance measures, data sources, data visualization and analytical tools. Trainings/technical assistance can be directed at, but not limited to command and organizational G8s and resource managers.

5.11 Knowledge Management

5.11.1 The CPP manages a Cost Management Knowledge Center for the Army that includes documents, spreadsheets, and presentations, with rates, policies, memos, guidance, and examples relating to Cost Management. The contractor will deliver a Knowledge Management solution, specifically best practices in collecting, organizing, displaying, sharing, and maintaining organizational knowledge. The Knowledge Center is supported by Oracle WebCenter Portal.

5.11.2 The contractor will provide documentation describing the Knowledge Management solution, including Standard Operating Procedures for importing documents, and descriptions of the tagging or organizational features of the solution with the ability to browse via search or filter throughout the Knowledge Center.

5.12 Weekly Progress Reports Labor Tracking

5.12.1 The contractor shall provide a status update noting progress, issues and concerns weekly on a day specified by the COTR.

5.12.2 Labor Hours reports shall be sent to the COTR within first week of the month for the previous month

PART 6

APPLICABLE PUBLICATION

6.0 Publications applicable to the PWS are listed below. The publications must be coded as mandatory or advisory, the dated of the publication, and what chapters or pages are applicable to the requirement. All publications listed are available via the Internet at the specific website.

6.1 https://informationassurance.us.army.mil/bbp/army_password_standards.pdf – Mandatory

6.2 https://informationassurance.us.army.mil/bbp/ia_training.pdf – Mandatory

6.3 https://informationassurance.us.army.mil/bbp/BBP DAR VER 1 0.pdf – Mandatory

6.4 https://informationassurance.us.army.mil/bbp/data_transfer.pdf – Mandatory

6.5 http://www.army.mil/usapa/epubs/pdf/r25_1.pdf – Mandatory

6.6 http://www.army.mil/usapa/epubs/pdf/r25_2.pdf – Mandatory

6.7 http://download.oracle.com/docs/cd/B25516_17/current/html/docset.html Mandatory

6.8 https://metalink.oracle.com/ Mandatory

6.9 http://www.oracle.com/technology/index.html Mandatory https://informationassurance/ https://informationassurance/ https://informationassurance/ https://informationassurance/ http://www/ http://www/ http://download/ https://metalink/ http://www/

TECHNICAL EXHIBIT 1

Performance Requirements Summary

Performance Objective Standard Performance Threshold

Method of Surveillance

PRS # 1

Contractor shall install, patch, configure, and maintain all Oracle software on DASA-CE servers to support the CPP.

(PWS 5.1.1 – 5.1.12)

Compliance with the following best practices and standards:

Army Information Assurance best practices, Risk Management Framework, Army Regulations AR 25-1 & AR 25-2, DoDI 8500.01 & DoDI 8510.01 Oracle’s best practices and online documentation including but not limited to: installation guides, maintenance guides, patching procedures, system administration guides, Critical Patch Update (CPU).

100% of government approved requirements shall be satisfied.

Outages due to incidents (unplanned unavailability) will not exceed 1% of total service time

Periodic Surveillance

PRS # 2.

Contractor shall create and maintain reports and tools using Oracle Application Express, OBIEE, WebCenter Portal, or an equivalent product

(PWS 5.2 – 5.4)

Compliance with the following best practices and standards:

Army Information Assurance best practices, Army Regulations AR 25-1 & AR 25-2, DoDI 8500.01 & DoDI 8510.01 Oracle’s best practices and online documentation including but not limited to: product and configuration references.

All applications will meet requirements approved by the government.

Testing shall be performed and bugs or issues remediated prior to final release.

100% of government approved requirements shall be satisfied.

Testing shall occur for a minimum of 2 days prior to production release.

100% of identified bugs and issues shall be remediated prior to production release

Review of work products

PRS # 3.

Contractor shall create, populate, and maintain the CPP data repository(PWS 5.5)

Compliance with the following best practices and standards:

Army Information Assurance best practices.

Army Regulations AR 25-1 & AR 25-2, DoDI 8500.01 and DoDI 8510.01 Oracle’s best practices and online Documentation.

No more than 10% deviation from the standard

PRS #4

Contractor shall enable/disable CPP user

Compliance with the following best practices and standards:

Within 2 business days of original request accounts according to policy(PWS 5.6)

Army Information Assurance best practices.

Army Regulations AR 25-1 & AR 25-2, DoDI 8500.01 and DoDI 8510.01 Oracle’s best practices and online Documentation.

PRS #5

Contractor shall provide documentation for the CPP.

(PWS 5.7)

Documentation shall conform to templates or standards used within

DASA-CE.

100% Adherence to DASA, Federal or Army standards, templates, and best practices

Review of Work Products

PRS #6

Contractor shall work with CPP hosting center to support CPP operations.

(PWS 5.8.)

Any outages are reported to the hosting center and the government within 24 hours.

Remediation strategies for any issues are identified within 24 hours.

Status updates for major ongoing disruptions are provided every 24 hours.

Deviations in hosting center behavior from the terms in the accepted Service Lifecycle agreement with the hosting center are reported when detected and a remediation strategy identified within 24 hours.

100% Reporting and remediation strategies within 24 hours of a triggering event

Periodic Surveillance

PRS #7

Contractor shall address and…