PWS-PPBBOSIII.pdf

PPBBOS IIII Page 1

Performance Work Statement (PWS) For

Planning Programming Budgeting Business Operating System

(PPBBOS) - III

1.0 GENERAL INFORMATION

1.1 Task: The contractor shall provide all personnel, equipment, tools, materials, supervision, and other items and non-personal services necessary to perform services as defined in this Performance Work Statement (PWS) except as Specified in section C-Part 3 as government furnished property and services. The contractor shall perform to the standards defined in this PWS.

1.2 Background: The Program Budget Data Management Division (PBDMD) of the Deputy Chief of Staff (DCS), Army G-8, Program Analysis and Evaluation (PA&E) manages the PPBBOS II contract and will manage the PPBBOS-III contract. G-8, PA&E is responsible for providing support during the Department of Defense Planning, Programming, and Budgeting (PPB) process culminating in the annual submission of the Army’s portion of the President’s Budget.

Inherent in this responsibility is the management of the ARC/cPROBE hosted in a cloud environment and the oversight of all Information Technologies (IT) and the requirements for developing, administering, maintaining, and enhancing automated data and information systems that ensure efficient business operating processes.

ARC/cPROBE consists of multiple managed cloud environments and numerous hosted data, applications, and processes that enable Army Planning, Programming and Budgeting (PPB) processes to develop the Army Future Years Defense Program.

ARC/cPROBE integrates multiple cloud services, commercial-off-the-shelf (COTS) applications, and custom applications storing data in multiple database engines including Oracle RDS, SQL Server RDS, Postgres, Mongo DB, and RedShift, while serving more than 23,000 users. Applications exchange data with multiple other data systems and applications hosted in and out of the cloud. It performs a wide variety of automated validation routines, financial control enforcement, and produces outputs for submission to the Office of the Secretary of Defense (OSD) as outlined in the DoD Financial Management Regulation (FMR).

For reporting purposes, cPROBE maintains authoritative Army resource data within a data warehouse and accumulates all US Army resource position history used to document the Army Program Operating Memorandum and Army input to the annual President’s Budget. Data snapshots are run through declassification routines to produce an unclassified version along with the classified snapshot. The team maintains and enhances an IT service delivery model that offers consistency and predictability in client service levels, improved accountability and efficiency, better cost management, and evolving the organization.

Key activities that support ARC/cPROBE business operating processes include:

a. Management of multiple-account cloud environments

b. Administration, maintenance, and improvement of IT systems that collect Program Objective

Memorandum (POM), Budget Estimate Submission (BES) and President’s Budget resources data deemed necessary to accomplish the Department’s mission.

c. Ensuring the validity, integrity, and security of Army PPB data.

D R A F T

PPBBOS IIII Page 2

d. Enabling the availability of data for broad Army analysis using analytical tools and integrated displays, as well as, enhancing its usefulness.

e. Maintain and coordinate changes to Army programming data

f. Publication and automated submission of the Army’s POM and the submission of POM/BES and

President’s Budget positions to include the Army’s Future Years Defense Program (FYDP) to the Office of Secretary of Defense (OSD)

g. Supporting Army business transformation efforts by keeping pace with initiatives that improve the efficiency and effectiveness of PPB processes.

ARC/cPROBE consists of multiple cloud environments (IaaS, PaaS), hosted data systems and processes.

The major applications include cPROBE repository (the Army’s Authoritative Program, Budget system of record), Master Data Management, cPROBE Data Warehouse, cWork, cSustain, cMan, Army Enterprise Equipping System (AE2S), cQuiP, Army Portfolio Management System (APMS), Information Technology Approval System (ITAS), User and Role Management (URM), MRTS, and External System Interfaces. A R C / cPROBE integrates multiple cloud services, commercial-off-the-shelf (COTS) applications, and custom applications storing data in multiple databases including PaaS versions of Oracle, SQLServer, Postgres, and RedShift and an IaaS version of Mongo DB, while serving more than 50,000 users.

Application exchange data with multiple other systems and applications hosted in and out of the cloud.

Applications perform a wide variety of automated validation routines, financial control enforcement, and produces output for submission to OSD as outlined in the DoD Financial Management Regulation (FMR). ARC/cPROBE provides internal US Army Program Budget Guidance (PBG) for issuance to Army Commands (ACOM) and GFEBS.

For reporting purposes, cPROBE maintains authoritative Army resource data within a data warehouse and accumulates all US Army resource position history. Data snapshots are run through declassification routines to produce an unclassified version along with the classified snapshot. The intent of the PPBBOS-III contract as defined in this PWS is to maintain and enhance an IT service delivery model that offers consistency, predictability, improved accountability and efficiency, better cost management, and evolving the organization.

Table 1.1 documents the applications that are hosted in the Army Resource Cloud (ARC) at this time.

Additional systems/applications hosted in the ARC/ cPROBE environment over the life of the contract, coming into the environment through the documented onboarding process.

Fully-managed applications (Applications are maintained under the PPBBOS III contract):

cPROBE Repository:

cPROBE Portal Master Data Management cPROBE Data Warehouse cPROBE System Administration Tools cWork Requirements Input cSustain Sustainment Tracking cMan Manning Programming cDigital Digital Programming Army Enterprise Equipping System (AE2S) cQuiP Equipment Data Tracking Capabilities And AROC Management System (CAMS) Select and Native Process (SNAP) PB 61 Generation

D R A F

T

PPBBOS IIII Page 3

Contracted Services Reporting Command Program Issues Compo / Qty Modeling & Simulation RAND Projects Data Tagging cShare REST API data sets Commander’s Execution and Assessment Reporting TRADOC Decision Lens Sites Workforce Planning Project Management Resource Tools (PMRT) Interface Materiel Release Tracking System (MRTS) Army Portfolio Management System (APMS) Information Technology Approval System (ITAS) User and Role Management (URM) Issue Tracking System (ITS) Dynamic Reporting Tool (DRT) OSD Submission Reporting External Data Interfaces

Partially-managed applications (Applications are maintained via another contract vehicle)

JICAP

TRMIS

EKR

TRADOC DecisionLens

The list below identifies a partial list of systems that currently provide or pull data from cPROBE repositories:

Structure and Manpower Allocation System (SAMAS)

IRMIS

EAS

ASARS

The General Fund Enterprise Business System (GFEBS) Construction Appropriation Programming Control and Execution Systems (CAPCES) Resource Management system (RM-Online)

NGRMS

Resource Structure Management (RSM) DoD Information Technology Portfolio Repository (DITPR), FMSWeb Army Enterprise Systems Integration Program (AESIP)

1.3 Objectives: To obtain contractor support for the management, development, maintenance and sustainment of the environment, systems, and applications hosted in the ARC/cPROBE environment in support of Headquarters Department of the Army. This IT support contract will ensure all applications that are part of the ARC/cPROBE are operated and sustained in a cyber-secure manner.

1.4 Scope: The contractor shall provide services for the business capability definition; architectural design and evaluation; prototyping; engineering development; configuration, integration, and migration activities, along with maintenance and sustainment of all business applications, and cloud

PPBBOS IIII Page 4 infrastructure items. Each of these components will be executed throughout the life of this contract.

Component I: Cloud Infrastructure Activities Component II: Security Activities Component III: Maintenance and Sustainment Activities Component IV: New Development of Systems/Applications Component V: Enterprise Reporting Component VI: Data Services Component VII: Data Science Services

The above 7 components are mutually exclusive; separate activities that will run in parallel throughout the contract period of performance. Conceptually this encompasses more than just the acquisition of a Defense Business System (DBS); it weaves together all Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel and Facilities (DOTMLPF) to deploy a set of integrated business capabilities.

During the course of contract performance, the contractor shall introduce and maintain innovative approaches for sustaining the application suite for the architecture and capabilities within the constantly changing environment. The contractor shall develop and implement processes and provide system support for new and current initiatives that are developed within the numerous process improvements underway within Army, G-8, and PA&E including:

Standard Financial Information Structure (SFIS) Single Army Financial Enterprise (SAFE) Consolidated Identity Management (Army/DoD Enterprise Identity and Access

Management (IdAM) and other evolving enterprise processes) Army Request for Information Technology (ARFIT) Model-Based Integrated Process Improvement Methodology

FEIMA

The operating environment will dictate much of the engineering and project approach. Due to the nature and high frequency of changes within this environment, an integrated solution must be identified and deployed to meet emerging business requirements. Frequent, incremental updates will be the key to success; the analysis and engineering teams must be able to adapt their methodology to support the PPB operational requirements.

This approach shall address all areas including maintaining an evolving architecture, maintenance and sustainment of Army Resource Cloud environment, systems and applications. The objective of the overall analysis of the architecture is to evolve system architectures and capabilities that enable future business process capabilities.

The contractor shall provide a plan for consolidating services while promoting Net- Centric data sharing, and Business Modernization Management requirements. Consolidation of IT services shall strengthen accountability and leadership and is a crucial strategy in achieving the PPB performance priorities and goals while better managing costs through centralization and elimination of redundant services and equipment. Consolidation will improve risk management by coordinating technical support staff’s plans for and responses to security threats. The contractor shall provide a methodology of system implementation that removes redundant or unnecessary processes.

The contractor shall deliver an Implementation and Transformation project plan that addresses the government’s service needs, fits within the government’s financial constraints, and allows for future growth and change.

The Contractor shall deliver a Concept of Operations (CONOPS) that provides system identification, an overview of the proposed system, and a brief description of the scope of the effort required to take the

PPBBOS IIII Page 5 system from the current state to the final future state of deployment that shall be achieved at the conclusion of the proposed deployment.

See Technical Exhibit 3 for the Delivery Schedule for all required documents.

1.5 General Information:

1.5.1. Supervision of On-Site Contract Employees: The contractor shall at all times be solely responsible to manage and supervise contractor employees. The contractor shall be responsible for management and administration of contractor personnel performing this task, and the contractor bears all responsibility for contractor performance. All managerial duties for contractor personnel shall be the responsibility of the contractor, not the Government. The contractor shall assign a Contractor Director as the main point of contact between the government and the contractor. The contractor shall independently determine how best to complete the desired workload. The contractor shall independently, and not as an agent of the Government, exert its best efforts and furnish the necessary personnel to perform the work.

1.5.2. Section 508 Standards: The following Federal IT Accessibility Initiative Standards are applicable to this acquisition:

1194.21 – Software Applications and Operating Systems;

1194.22 – Web Based Intranet and internet Information and Applications;

1194.26 – Desktop and Portable Computers; and 1194.41– Information, Documentation, and Support.

1.5.3. Policy Planning, Process, Program and Project Management:

1.5.3.1 Technical Support: The contractor shall host a Technical Interchange Meeting (TIM) to ensure a common understanding between the contractor and the Government on the task order requirements. This Technical Interchange Meeting is to be conducted NLT 10 days after contract award and annually upon exercise of subsequent option years. TIM meeting minutes in written format are due NLT five (5) working days after the meeting.

1.5.3.2. Status Reporting: As part of this work, the contractor shall provide a Plan of Action and Milestone (POA&M) listing at the start of this effort for task areas one through eight (see PWS Section 6, pages 29-48). The POA&M shall describe the technical approach, organizational resources, and management controls planned by the contractor to meet the cost, performance, and schedule requirements established under this statement of work. Contractor shall submit the above POA&M 30 days following contract award with periodic updates provided for additional or schedule modifications.

The contractor shall provide a weekly status report that contains key weekly events, actions completed, Other Direct Costs (ODCs) and travel. The weekly status report shall include identification of expense using the assigned CLIN, a summary of travel, to include traveler name, destination, travel dates and total travel funding expended approved by the Contracting Officer’s Representative prior to the travel.

Review of these reports shall not constitute acceptance of charges on behalf of the Government.

The contractor shall provide an integrated master project schedule that includes key milestones with a summary of the major events and deliverables of the program, identified in a project schedule. Specific dates for deliverables shall be included in the schedule using project management software that can be exported to PDF or MS Word format.

Additionally, the contractor shall submit a monthly status report to the COR. These reports shall provide

PPBBOS IIII Page 6 a summary of activities accomplished during the past month, activities anticipated for the next reporting period, and potential issues. The monthly reports shall include a summation of topics covered in the weekly reports, an updated POA&M, and cost status including the detailed costs for the cloud environment delineated by ARC/cPROBE.

1.5.3.3 Financial Reporting: The contractor shall provide a Monthly Financial Status Report (MFSR) that includes a monthly and cumulative financial summary of labor expended, by CLIN and/or SubCLIN, related to each respective monthly effort. The MSFR shall:

Include, by labor category, hours authorized, monthly and cumulative hours expended, hours remaining, billing rate, and monthly and cumulative labor costs expended, as well as a cumulative summary of Other Direct Costs (ODCs) and travel.

Include a summary of hours and dollars expended by systems. System categories shall be identified by the Contracting Officer’s Representative and shall include those systems current hosted in the ARC or that are in the onboarding process. This summary shall record both contractor and hosting expenditures.

Include a summary of travel, to include traveler name, destination, travel dates and total travel funding expended and presented for approval by the Contracting Officer’s Representative prior to the travel. Upon completion of approved travel, the Contractor shall include a copy of a final summary to include traveler name, destination, travel dates with all related total travel costs presented to the Contracting Officer’s Representative. Review of these reports shall not constitute acceptance of charges on behalf of the Government.

The contractor shall submit all invoices in accordance with contract specifications.

1.5.4 Duplication of Effort: The contractor shall ensure that there is minimum duplication of effort in the execution of all work specified in this PWS. The contractor shall build upon work previously accomplished by the Government, the contractor, or other contractors to the fullest extent practical.

1.5.5 Cooperation/Coordination with other Contractors: There may be multiple contractors (i.e., from more than one contract vehicle and/or company) supporting the Army, tasked to work on systems that interface with applications within the ARC/cPROBE. The contractor shall work with these other contractors as required and approved by the Government to accomplish Government requirements, goals, and objectives as efficiently and effectively as possible. This may include but is not limited to sharing or coordinating information (as approved by the Government) resulting from the work required by this PWS or previous Government efforts, and/or working as a team to perform tasks in concert.

1.5.6 Data Rights and Intellectual Property: The contractor shall not use or disclose information developed or delivered under this contract for any purpose other than as required for performance of the contractor's contractual obligations without the specific authorization of the Contracting Officer.

1.5.7. Disclosure of Information: Reference DFAR 252.204-7000 DISCLOSURE OF INFORMATION (OCT 2016). The contractor shall not use or disclose information developed or delivered under this contract for any purpose other than as required for performance of the contractor's contractual obligations without the specific authorization of the Contracting Officer.

1.5.8. Capability Maturity Model Integration (CMMI) Maturity Level: The Contractor shall have successfully achieved a minimum CMMI Development Level 5 rating as verified through completed external assessments. The contractor shall apply CMMI-DEV Level 5 methodologies to all business and technical processes.

1.5.9 Quality Control: The contractor shall develop and maintain an effective Quality Control (QC)

PPBBOS IIII Page 7 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 he assures himself that his 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”. The quality control plan shall not be considered accepted until the contractor receives the contracting officer’s approval in writing. The QC Plan is due 30 days after contract award. The QCP shall identify quality assurance surveillance reporting to be delivered to the Government monthly.

1.5.9.1 Organization and resources: The contract shall provide organization chart and communication interfaces for all personnel performing QC functions and define the authority of the QCP manager to monitor and control functions, and to implement remedial and preventive actions.

1.5.9.2 Procedures for corrective action: The Contractor shall define their procedures for corrective action.

1.5.9.3 Quality Control Plan (QCP): The Contractor shall submit the QCP to the KO and COR for Government review within 30 days of contract award. After KO and COR acceptance of the QCP, the Contractor shall receive the KO’s acceptance in writing of any proposed change to his QC system.

Changes recommended by the Government shall be considered by the Contractor and incorporated into the QCP by the Contractor, if appropriate, and the QCP shall be resubmitted to the KO and COR within 10 calendar days of receipt. The Contractor shall submit updates to the plan to the KO and COR as required.

The Contractor shall maintain support documentation for all actions taken over the life of the contract (e.g., work requests and inspection correction reports). These files shall be made available to the Government when requested by the KO or COR. Upon completion of the contract, the Contractor shall turn all files over to the COR.

1.5.9.4 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. 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 shall be applied, the frequency of surveillance, and the minimum acceptable defect rate(s). The Government has the right to perform inspections and performance evaluation at any time. If any aspect of the performance is not in conformance with the requirements of the contract, the Government will have the right to issue to the Contractor a Contract Discrepancy Report (CDR). The Contractor shall explain in writing why performance was not in conformance with the requirements of the contract, how performance will be returned to conformance, and how recurrence of the problem will be prevented in the future. The Contractor shall complete and return the CDR to the COR within five working days after receipt of the

CDR.

1.5.10 Government Remedies: In addition to other remedies offered under the contract, the contracting officer shall follow 52.246-5, “Inspection of Services -- Cost-Reimbursement.” for contractor’s failure to perform satisfactory services or failure to correct non-conforming services.

1.5.11 Recognized Holidays: The contractor is not required to perform services on any Federal Holidays, or any other Presidential Proclamations. The dates for Federal holidays may be obtained from the Office of Personnel Management’s website at www.opm.gov.

1.5.12 Hours of Operation/Place of Performance: The contractor is responsible for conducting business between the hours of 7:00AM through 7:00PM EST (Eastern Standard Time) Monday through Friday except Federal holidays or when the Government facility is closed due to local or national

PPBBOS IIII Page 8 emergencies, administrative closings, or similar Government directed facility closings. The Contractor must maintain at all times an adequate work force within the NCR for the uninterrupted performance of all tasks defined within this statement of work when the Government facility is not closed. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the work force are essential. Contractor activities will be conducted primarily at contractor facilities. Some contractor activities will be performed at government facilities (located in Room 3C353, Pentagon). For these occasions, the government will provide office space and office automation equipment (hardware, software, and LAN access) for up to five contract staff personnel. The contractor shall provide support at times other than during the above stated hours in order to provide system updates and defect corrections when deemed necessary by the government in order minimize system downtimes. The COR will notify the contractor management when these off-business hours are necessary.

1.5.13 Security Requirements: The contractor is responsible for obtaining required identification cards, tags, and badges in accordance with AR 600-8-14. The contractor and subcontractor(s), if any, shall complete a background security check of all personnel (SF-85P) before new employees report for duty. Execution of SF-85P is a requirement for contractor personnel to receive a Common Access Card (CAC). All contractor personnel must be U.S. citizens. The contractor’s security office will forward security clearance and visit requests to PAE for all personnel assigned to work on this task. All personnel that support this contract will be required to execute non-disclosure statements regarding POM, budget, and other PPB data after contract award and prior to accessing production data. All products and technical data, in accordance with data rights as cited in 227.7102.4, produced and delivered under this contract will become property of the government. All contractor positions other than those listed below require SECRET clearance eligibility. For positions requiring SECRET clearance eligibility, the contractor shall be responsible for providing SECRET cleared individuals as determined necessary by the Government after contract award.

1.5.13.1 Non-Disclosure Statement: Army has a Nondisclosure Agreement (NDA) requirement for each person supporting Army. The winning contractor personnel shall complete and sign a Nondisclosure Agreement prior to commencement of the award. This requirement extends to all subcontractors and teaming arrangements. The NDA shall be provided to the COR and Administrative Contracting Office (ACO). The contractor is responsible to obtain all necessary approvals prior to obtaining access to proprietary information, in accordance with FAR 9.505- 4(b). In accomplishing their duties, the contractor may require access to proprietary information of other contractors. Therefore, pursuant to FAR 9.505-4, firms must execute an agreement with other contractors that states that they will (1) protect the contractor’s information from unauthorized use or disclosure for as long as it remains proprietary and (2) refrain from using the information for any purpose other than that for which it was furnished. This requirement shall flow down to all Subcontractors.

1.5.13.2 Physical Security: The contractor shall be responsible for safeguarding all government property provided for contractor use. At the close of each work period, government facilities, equipment, and materials for which the contractor is responsible shall be secured.

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

PPBBOS IIII Page 9

1.5.14 Post Award Meeting/Periodic Progress Meetings: The Contractor shall attend any post award meeting 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.

1.5.15 Contracting Officer Representative (COR): To be identified at time of award: The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance:

maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.5.16 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. All contractor employees shall read all applicable security regulations, to be provided by the Government. Contractor personnel shall familiarize themselves with the Government’s regulations and policies and site-specific regulations regarding access to sensitive materials, computer facility/IT network access, issue of security badges, etc., which shall be provided as required by the Government.

1.5.17 Contractor Travel and Other Direct Costs (ODCs): When travel is required, advance notification shall be provided to the appropriate Army point of contact to allow for clearances and site preparation. Reimbursement of expense shall be in accordance with the Joint Travel Regulation (JTR).

Reimbursement for contractor Travel is subject to advance approval by the COR. Travel shall not commence until written approval is received. Allowable and allocable Other Direct Costs required to support the contract may be reimbursed subject to Government review and advance approval by the

COR.

1.5.18 Organizational Conflicts of Interest: Contractor and subcontractor personnel performing work under requirement may receive or have access to proprietary information which may create a current or subsequent Organizational Conflict of Interest (OCI) as defined in FAR Subpart 9.5 and the US GAO “The Yellow Book” Government Auditing Standard (also known as the Yellow Book OCI standards).

The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including

PPBBOS IIII Page 10 prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.5.19 Contract Deliverables: The submission and review of information submitted under the Contract Deliverables Requirements List (CDRL) required by this PWS shall not limit the Government’s rights and remedies under other provisions of the contract.

1.5.20 Contractor Acceptance of Software License Agreements: The contractor shall not accept any software license for software added to a Government system without prior review and acceptance of the license terms and conditions by the Government.

1.5.21 Prohibition of Contractor Purchase of Hardware Items: Contractor will not be required to purchase hardware items for support under this contract.

1.5.22 Government Property and Services: Refer to Section 3 of this PWS for Government Property (GP) for this order. For all issued GFP for this order, Contractor shall submit a Property Management Plan to the Contracting Officer and the Property Administrator via the COR. The plan shall address the requirements as listed in the Contract Data Requirements List. The contractor shall establish and maintain and acceptable property management system. Failure to maintain an acceptable property management system, as defined in DFARS 252.245-7003, may result in disapproval of the system by the KO and/or withholding payments.

1.5.23 Cybersecurity Maturity Model Certification (CMMC) Maturity Level: The Department of Defense is in early stages of implementing the Cybersecurity Maturity Model Certification (CMMC) version 2.0. The Contract shall prepare to achieve, at a minimum, level 4 certification to protect government Controlled Unclassified Information (CUI) as this standard matures. The Department encourages contractors to continue to enhance their cybersecurity posture during the interim period while the rulemaking is underway. The Department has developed Project Spectrum to help assess Contractor cyber readiness and begin adopting sound cybersecurity practices.

1.5.24 Manpower Reporting: 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 requested by logging into SAM.gov: https://sam.gov/SAM/ The required information includes: 1) Contracting Office, KO, COR;

(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 (including sub-Contractors); (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 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, the Contractor shall also 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

PPBBOS IIII Page 11 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.

PPBBOS IIII Page 12

2.0 PERSONEL

2.1 Cleared Personnel at Contract Start: The following positions require an active SECRET clearance at time of award:

Program Manager Systems Engineers Cloud Certified (3) Application Developer (Master) Application Systems Analyst (Master) Database Specialist (Senior) Cloud Solutions Architect

Data Warehousing Specialist (Master) Applications Developer (Senior) Enterprise Security Specialist (Senior)

2.2 CyberSpace Workforce Certification: In addition to an active SECRET clearance at time of award, the following positions require a completed favorable Single Scope Background Investigation (SSBI), Security+ Certification, and 8140 Cyberspace Workforce Qualification and Management Program certification:

Systems Engineer Cloud Certified (3) Database Specialist (Senior)

2.3 Key Personnel Special Qualifications: The following are descriptions of the government minimum education, experience and certification requirements for personnel performing under the contract. The contractor shall deploy and maintain current employees for all key positions.

Key personnel positions are listed below:

Senior Program Manager Project Manager (3) Cloud Solutions Architect Systems Engineer Cloud Certified (Master) (2) Application Developer (Master) Application Systems Analyst (Master) Database Specialist (Senior) Data Engineer (Master) Software Engineer (Senior) Enterprise Security Specialist (Senior)

2.3.1 Senior Program Manager:

Serves as PPBBOS prime contract senior manager and authorized interface for the Government Program Manager and Management. The Senior Project Manager performs supervisory program management and oversight to ensure successful program performance and is responsible for overall performance on the contract. Other responsibilities may include: assigning staff, formulating and enforcing work standards, assigning contractor schedules, reviewing work discrepancies, supervising contractor and subcontractor lead personnel, and communicating policies, purposes, and goals of the organization to subordinates; The Senior Project Manager is expected to devote an appropriate amount of time to the overall management of this Contract, including coordination with Government staff, and assuring quality of work performed. This position requires on-site visits to the government facility as needed or as directed by the Government.

PPBBOS IIII Page 13

Qualifications: Undergraduate degree in Information Systems Engineering, or Computer Science, or Business or related field. Minimum 15 years of management experience with 10 years of information systems management experience. Certified Project Management Professional. Minimum 5 years of experience with Army Planning, Program, and Budget business systems. The offeror must possess a thorough understanding of planning, programming and budget formulation systems, components and capabilities used within the Army and OSD. Experience must include the supervision of business solutions, infrastructure, systems design, development, responsibility for contract administration, and personnel hiring and scheduling.

2.3.2 Project Manager:

Project managers are responsible for the day-to-day technical management of PPBBOS-II task areas.

Ensures technical solutions and schedules are implemented in a timely manner. Performs enterprise-wide horizontal integration planning and interfaces to other functional systems. Develops and manages the PPBBOS-II technical project plans to completion within time and resource constraints.

Manages project team scheduling, tracking, reporting, risk analysis, and cost management, leads the design, implementation and production life-cycle. Chairs integration meetings, stakeholder sessions, and requirement collection activities. Briefs Army leaders on current projects and the benefits to the Army.

Qualifications: Undergraduate degree in Information Systems Engineering, Computer Science, Engineering or Business or other related field. Certified Project Management Professional. Minimum 5 years program management experience with information systems. Project managers must have 5 years Minimum experience with US Army planning programming and budget formulation business (PPB) processes and a thorough understanding of requirement, design, construction and testing capabilities. Project managers will have a minimum of one of the following disciplines; At least 3 years project management experience managing complex information systems using the latest industry technologies, good understanding of DoD Cyber Security requirements, and previous project management experience with complex information systems.

2.3.3 Cloud Solutions Architect:

The Cloud Architect will design and develop cloud platform that is robust, scalable, and modeled on defense-in-depth and inherent security to translate policy, mission, and technical requirements to the enterprise. The architect will map user and application requirements in order to provide system and integration guidance to a team of cloud-certified engineers. The architect will contribute extensive knowledge of modern software development techniques and technology to design services that leverage leading technologies and architecture to produce services that meet customers’ demands. The Architect is responsible for implementing, managing, and monitoring the environment and deployments IAW DoD Business Enterprise Architecture (BEA) requirements. This shall include the design and development of an automated DevSecOps Pipeline, CI/CD support infrastructure, and Data Validation Pipeline. Testing and implementation plans shall accompany all architectural designs. The Architect shall manage the complete life cycle for all components with expert knowledge of technical design alternatives, including Open Source, and their implications by guiding the development teams in overall application technical design activities. This position will provide recommendations to both developers and engineers as necessary to ensure secure implementation of applications and assist engineers in the configuration of software and services. This position will manage system architecture, system integration, system standards, system design, and requirements specifications. This position requires extensive knowledge of cloud architectures, integration architectures, and knowledge of the Army PPB processes with complete understanding of integration into BEA. This position requires extensive knowledge of DoD Laws, Regulations and Policies, and Army IT policies and directives to assure compliance. Duty location at the Pentagon will occasionally be required.

PPBBOS IIII Page 14

Qualifications: Undergraduate degree in systems engineering, software engineering, computer science, or related engineering discipline from an accredited college or university. Minimum 10 years related technical specialized experience in the design, development, and implementation of complex, large-scale, enterprise information systems including maintenance, modification and resolution of errors;

specialized experience in cloud platform deployment models, IAAS, PAAS, and SAAS. Minimum 3-5 years’ work experience designing, executing, and supporting IT Cloud solutions, IaaS, PaaS, SaaS.

Certifications: Certified Cloud Solutions Architect. It is crucial that this position have exceptional understanding of cloud computing technologies and computing trends and familiarity with enterprise architecture and enterprise application integration. Individual should also have adept knowledge of data modeling best practices and practical knowledge of Agile Software development methodology. Cloud architects require expert knowledge of key security concepts as security is a major pillar in cloud environment. This individual should also exhibit expert knowledge of data integration technologies and have experience with business intelligence/analytics implementations. The individual should be proficient in evaluating current or emerging technologies to consider factors such as Security, Reliability, Performance, Cost Optimization, and Operations, 5 focus areas in cloud architectures;

evaluating existing systems to determine effectiveness and recommend changes to meet organizational requirements; establishing functional or technical standards to ensure operational requirements, quality assurances, and design constraints are addressed; collaborating with system engineers or software engineers/developers to select appropriate design solutions or ensure the compatibility of system components; critical thinking using logic and reasoning to identify the strengths and weaknesses of alternative solutions, conclusions or approaches to problems. The individual will be proficient with complex problem solving and be able to identify complex problems and review related information to develop and evaluate options and implement solutions, using analytical thinking and attention to details. Must have experience architecting cloud solutions and thorough knowledge of System Development Lifecycle (SDLC).

2.3.4 Systems Engineer Cloud Certified (Master):

Possess extensive experience using latest technologies with proven record of implementing a wide variety systems and applications. Proven experience using one of the major cloud service providers currently running within the DoD. Oversees all cloud environments ensuring each environment is properly configured, all necessary error and security alerts are in place, costs are being controlled appropriately, and DoD prescribed security is adhered to.

Qualifications: Undergraduate degree in computer science, engineering, or mathematics from an accredited college or university and has a combined minimum of 10 years experience in systems engineering, software engineering, and systems administration. Preferred Master of Science degree with experience performing within DoD environments. Will possess certification from at least one of the major DoD approved cloud service providers

2.3.5 Application Developer (Master):

Performs development, design, and implementation activities for custom applications. Uses latest technologies including web services development, micro services architecture, and Continuous Integration / Continuous Deployment/Delivery methods.

Qualifications: Senior-level system programmer with an undergraduate degree in computer science, engineering, or mathematics from an accredited college or university and has a minimum of 10 years of experience in computer programming. Must have technical experience with PPB process and systems.

2.3.6 Application Systems Analyst (Master):

Formulates/defines system scope and objectives. Devises or modifies procedures to solve complex

PPBBOS IIII Page 15 problems considering computer equipment capacity and limitations, operating time, and form of desired results. Prepares detailed specifications for programs. Assists in the design, development, testing, implementation, and documentation of new software and enhancements of existing applications. Works with project managers, developers, and end users to ensure application designs meet business requirements. Formulates/defines specifications for complex operating software programming applications or modifies/maintains complex existing applications using engineering releases and utilities from the manufacturer. Designs, codes, tests, debugs, and documents those programs. Provides overall operating system, such as sophisticated file maintenance routines, large telecommunications networks, computer accounting, and advanced mathematical/scientific software packages. Assists all phases of software systems programming applications. Evaluates new and existing software products.

Qualifications: Experienced senior-level system programmer or system analyst with an undergraduate degree in computer science, engineering, or mathematics from an accredited college or university. Has a minimum of 10 years of experience in computer programming, systems analysis, or systems engineering. Must have technical experience with PPB process and systems. Must have extensive experience with J2EE and web applications utilizing an Oracle database management system (DBMS).

Knowledge of XML, Web Services and DBMS data access as well as extensive knowledge of database design and implementation is required.

2.3.7 Database Specialist (Senior):

Performs overall control of database tier of the environment including interfacing between internal and external applications. Managing the Extract Transform and Load (ETL) processes, ensures data is cleansed.

Qualifications: Undergraduate degree in Information Systems Engineering, Computer Science, Engineering or Business, or other related field. Must have minimum 10 years DBA experience with 5 years of experience of Oracle database administration to include 1 year experience with Oracle 12c administration, database backup, server migration, optimization, and capacity planning and integrity routines. Must possess extensive knowledge of procedure performance tuning and troubleshooting.

Must have data modeling experience. Possess 2 or more years of experience with Army or OSD PPB data models.

2.3.8 Data Engineer (Master):

Responsible for the environment’s database layer. Coordinates administrative functions to ensure data is reliably available and access times are minimized allowing quickest access possible to data.

Responsible for all interfaces into and out of the data layer. Responsible for API hub allowing data exchanges with internal and external sources or systems. Ensures applications can access data with minimum latency. Facilitates change control, problem management, and communication among data architects, programmers, analysts, and engineers. Establishes and enforces processes to ensure a consistent, well managed, and well-integrated data infrastructure.