RFI Draft 01 EDM PWS FY26.docx

EDM Support PWS EDM Support PWS EDM Support PWS

Performance Work Statement (PWS) Enterprise Data Management (EDM) Support Services

November 2025, DRAFT

Table of Contents

1 Introduction The Office of the Comptroller of the Currency (OCC) is an independent bureau of the U.S. Department of the Treasury. Its primary mission is to charter, regulate, and supervise all national banks and Federal savings associations. The OCC’s goal in supervising banks and Federal savings associations is to ensure that these entities operate in a safe and sound manner and in compliance with laws requiring fair treatment and access to credit and financial products.

Headquartered in Washington, D.C. with a staff of approximately 4,000 employees, the OCC has four district offices and an Office of the Ombudsman to supervise the activities of national banks. To carry out its mission, national bank examiners conduct on-site reviews of national banks and Federal savings associations (or Federal thrifts) and provide sustained supervision of these institutions’ operations. Examiners also analyze loan and investment portfolios, funds management, capital, earnings, liquidity, sensitivity to market risk, and compliance with consumer banking laws. In addition, these examiners conduct audits to review internal and external controls, as well as to evaluate management’s ability to identify and control risks

1.1 Background

OCC’s Information Technology Services (ITS) office delivers and maintains IT solutions across the OCC which helps to connect internal and external OCC stakeholders with information they need to achieve OCC’s mission.

Within ITS, the Enterprise Data Management (EDM) group is responsible for designing, developing, maintaining, and supporting the Data Warehouse Platform, Analytical Platforms and other data related products. The team is also responsible for technical implementation of data and analytical solutions in alignment with the OCC Data Strategy and in support of the agency’s mission.

The EDM teams is responsible for the following platforms.

Data Warehouse Platform:

· On-Prem Data Warehouse Platform: The On-Prem Data warehouse is built on the Microsoft SQL Server platform and uses SQL Server Integration Services (SSIS) for extract, transform and load (ETL) operations, data movement, and integration activities. This environment is being phased out as the team transitions to a modern cloud-based platform.

· Cloud Data Warehouse Platform: The Cloud Data Warehouse Platform operates on Amazon Web Services (AWS) and Snowflake data platform. We are currently migrating data and workloads from the On-prem Data Warehouse Platform to this modern platform.

Business Objects Platform:

The Business Objects platform consists of the SAP Business Objects WebIntelligence application, the various Universes configured within it, and all reports developed in the application. The platform is currently in a sunset phase and is planned for retirement during the current contract period, with its reporting functions transitioning to other solutions. Transitioning content from Business Objects to other platforms is not in the scope of this contract.

Data Blending Platform (Alteryx):

Alteryx provides data blending capabilities to OCC data analysts through repeatable workflow processes that deliver data for self‐service data analytics. The platform is used internally within the team for Data blending.

1.2 Scope of Required Services

The OCC seeks a responsible Contractor to support the EDM team to provide support for the following types of work for in-scope platforms, applications, tools, information, and data assets:

· Program and Project Management

· Operations and Production Support activities, which includes tasks associated with data loads, data monitoring, incident and service request management, system auditing, and compliance (i.e., requirements associated with ensuring that existing systems adhere to all cyber security and regulatory mandates)

· Maintenance activities, which include tasks associated with business enablement (i.e., new system requirements)

· Migration of On-Prem data warehouse datasets to a Cloud data warehouse platform

· Design, develop, deploy new technical solutions supporting the data analytics requirements which support OCC’s Strategic goals

· Support EDM-related data governance activities such as Data Standardization, Data Maturity and Assessments, Risk Mitigation, and the maturation of policies governing Data Management and Analytics The Contractor shall assist the OCC with maintaining the functionality, reliability, availability, performance, stability, sustainability, and security of the Data Warehouse Platform (On-Prem Data Warehouse and the Cloud Data Warehouse), the Business Objects Platform, the Data Blending Platform and other data delivery/management products (e.g., Data Marts), tools, and information resources of the OCC.

On-Prem Data Warehouse Platform:

The contractor shall support the existing Legacy Data Warehouse Platform, which is built on Microsoft SQL Server. This environment utilizes SQL Server Integration Services (SSIS) to perform extract, transform and load (ETL) operations, data movement, and integration activities. The contractor shall maintain operations and ensure continuity of service until full transition to the cloud platform is complete.

Cloud Data Warehouse: The contractor shall provide operational support and ensure compliance for the Cloud Data Warehouse Platform, which operates on Amazon Web Services (AWS) and Snowflake. The platform is currently operational, and the agency has begun the migration of on-prem data sets to the cloud environment. The contractor shall:

· Maintain the cloud platforms availability, performance and security

· Assist with migration of data and workloads from the legacy environment

· Implement platform features in alignment with architectural standards and compliance requirements

· Retire the existing on-prem Data Warehouse Platform Until all data and ETLs have been successfully migrated to the cloud and the On-Prem Data Warehouse is retired, both the On-Prem and Cloud Data Warehouses must be maintained in parallel. As such, all references in this PWS to the Data Warehouse are referring to both the On-Prem, and Cloud Data Warehouses simultaneously.

The individual products associated with the Data Warehouse and the Business Objects platform are listed in Appendix A. Each of the products listed in Appendix A are associated with one of the platform functional areas. Each month, development activities associated with one or more platforms or products contribute to the monthly release.

Project Management functions include:

· Status reports and meetings

· Risk and issue management

· Risk assessments

· Schedule and scope management

· Contract management including cost management

· Audit, security, and software compliance management

· Transition planning, execution, and compliance

· Quality management

Operations (i.e. Operations, Production Support and Compliance) functions include:

· Refreshing, testing, maintaining, and supporting the Data Warehouse Platform (On-Prem and the Cloud Data Warehouse), the Business Objects Platform (i.e., the infrastructure and Business Objects universes), the Data Blending Platform (i.e., the Alteryx infrastructure and Derived Data Products)

· Responding to and remediating Incidents reported against any EDM-managed platform in alignment with established policies, procedures and SLAs

· Fulfilling Service Catalog requests in alignment with established policies, procedures and SLAs

· Maintenance of service account passwords (annual password changes) associated with all platforms and products listed in Appendix A

· Maintenance of comprehensive and up-to-date inventories of all service accounts, Active Directory groups, and other relevant technical assets

· Development and maintenance of documentation as needed for the administration, maintenance and use of EDM-managed platforms (i.e. Standard Operating Procedures, User Guides, etc.)

· Supporting the OCC’s ITS security and compliance objectives and mission, including administering internal and external audits, responding to data calls, remediating Plans of Action and Milestones (POAMs) and creating/maintaining security documentation and artifacts as required

· Monitoring the Data Warehouse environment to confirm that the load processes are executed to provide accurate, consistent, reliable, efficiently structured, and timely data. Performing on-going production data monitoring of the Data Warehouse environment by reviewing data exceptions and warnings during the load processes to identify data discrepancies. Please note, post-production monitoring needs to take place every time a refresh occurs

· Performing on-going monitoring of the Business Objects Platform, the Data Blending Platform and other data/analytical products to maintain system availability

Maintenance (i.e. Business Enablement) functions include:

· Performing adaptive, perfective, and corrective maintenance

· Adaptive maintenance includes modifying a system to address changes in the software or database environment

· Perfective maintenance includes implementing new or updated user requirements that involve functional enhancements to the software or database

· Corrective maintenance includes identifying, diagnosing and fixing errors, including errors identified by users

· Gathering and documenting functional and technical requirements

· Designing and developing data and analytical products for Data Warehouse, Business Objects and Alteryx.

· Sharing and documenting system knowledge

· Providing technical expertise to the application developers, end-users, and other data and service providers of OCC applications who consume Data Warehouse and Business Objects, Alteryx and related data management products

· Maintaining business systems, tools, databases, data warehouse environments, and other data delivery/management products

· Providing regular status updates to key stakeholders for all in-flight work

· Implementing OCC-approved knowledge management methods

· Maintaining the functionality, reliability, availability, performance, stability, sustainability, and security of the Data Warehouse and Business Objects environments, Alteryx and related data management products

· Analyzing and reporting the impact of infrastructure, connectivity, capacity, and other changes to the computing environment

· Validating and testing deliverables to ensure that they meet applicable standards, policies, business requirements, and quality measures

· Ensuring all required approvals are in place prior to the deployment of any work product, for each environment as applicable

· Preparing and managing Change Requests (CRs) in accordance with the OCC Software Development Lifecycle (SDLC) and other standards, in order to deploy code changes to the OCC production environment

The Contractor should be aware that at any point during the period of performance, the OCC may add new applications or platforms to its information technology (IT) portfolio for which the EDM team must provide support. For these new applications and platforms, the EDM team will require the same types of services and deliverables outlined in Section 3 of this PWS. The Contracting Officer will review any changes to the requirements by performing a scope determination and may issue modifications, if required.

1.3 Clarification of Terms

The following sections provide clarification of some terms and the way they should be interpreted within the context of this PWS.

1.3.1 The Term “Support”

Providing support for Data Management Systems encompasses a wide range of activities. Similarly, there are a wide range of documents and other artifacts that need to be developed and maintained to provide proper support.

Given such a wide range, it is not possible to know or precisely specify all activities that will need to be performed or all documents and other artifacts that will need to be produced in order to support the OCC’s Enterprise Data Management platforms and systems.

That said, the word “support” should be interpreted broadly and assumed to include performance of activities and development and maintenance of documents and artifacts that are reasonable and customary for professional information technology services in a government environment. Furthermore, just because an activity, document, or artifact is not specifically mentioned in a task description, the Contractor should not assume that it will not be required for a given task.

1.3.2 The Terms “Develop”, “Maintain,” and “Deploy”

Unless otherwise stated, the terms “develop,” “maintain,” and “deploy” and their grammatical variants should be interpreted broadly and assumed to include any of the following:

· Appropriate management of development, maintenance, and deployment activities

· Appropriate planning for development, maintenance, and deployment activities

· Appropriate technical review of development, maintenance, and deployment activities, including architecture reviews, design reviews, and code reviews

· Business Systems and Data Analysis

· Requirements elicitation and documentation

· Design, Solutions Architecture and alignment with Data Environment

· Set up, configuration, and implementation of infrastructure and environments, including the installation and configuration of software

· Writing, constructing, configuring, testing, troubleshooting, upgrading, patching, documenting, implementing, and deploying the object being developed, maintained, or deployed, as applicable Assume that the term “develop” includes maintenance and deployment activities even if not explicitly stated.

1.3.3 The Term “Test”

The term “test” and its grammatical variants should be interpreted broadly and assumed to include:

· Management of test activates

· Planning for test activities

· Development and maintenance of test strategies, plans, suites, cases, procedures, and scripts

· In the case of automated testing, development and maintenance of automated test scripts and other software

· Development and maintenance of test data

· Multiple stages of testing, including unit, integration, system, performance, application verification, user acceptance testing, disaster recovery testing and security testing (e.g. Penetration testing)

· Testing in multiple environments, including the Enterprise Test Laboratory

· Configuration of test environments

· Test execution

· Issue remediation and resolution

· Documentation of test results, including defects found during testing, issue resolution, and remediation or improvements resulting from analysis of test results

1.3.4 The Term “Data Warehouse Platform”

The term “Data Warehouse Platform” refers to both the On-Prem Data Warehouse Platform and the Cloud Data Warehouse Platform.

2 Tasks and Deliverables This section defines the tasks to be performed and the work products and deliverables to be created/maintained by the Contractor. All deliverables are due to the COR unless explicitly stated otherwise.

2.1 Project Management (Firm Fixed-Price)

The performance of the Contractor’s project management activities shall be accomplished consistent with the requirements set forth in this PWS.

2.1.1 Project and Contract Management

The tasks described in Table 2.1.1 shall be performed for all the EDM Platforms and Products identified in Appendix A.

Table 2.1.1 Project and Contract Management Tasks

· Executive summary of key reporting dimensions (for cost, schedule, quality, and risk)

· Key milestones

· A copy of the risk register for the EDM Platforms and Products within the supported portfolio

· The status of compliance activities

· Contractor concerns or recommendations

· Status of active or recently completed projects or tasks performed under this PWS

· Status of any quality-assurance activities for the month (including QA reviews of formal deliverables)

· Key Operational level metrics for all EDM Platforms and products

· Resource: Place of Performance Metrics report for the month to demonstrate place of performance expectations

· Contract financial summary, including actual and projected budgets along with projections for the execution

· Monthly and cumulative labor hours by labor category (for labor-hour tasks only

Hold a monthly program status review meeting with the OCC Contracting Officer’s Representative (COR), project managers, and key project team members.

After task order award, the OCC will confirm with the Contractor the template to be used for producing this report.

· Activities by technical/functional area

· Updates to the Integrated Master Schedule (IMS) or sprint plans

· Status of deliverables (submitted, late, or planned)

· Key risks and mitigation plans

· Key issues and action items

· Staff changes

· Performance metrics

Attend a Weekly meeting to review the status of ongoing work with the OCC Contracting Officer’s Representative (COR), project managers, and key project team members or Team Leads.

After task order award, the OCC will provide the template to be used for producing this report.

Weekly Status Report and Weekly Status Review Meeting

The Contractor is required to submit a COR Review Package by noon on the third Wednesday of each month. The version submitted by this time must be signed by the Contractor’s program manager. The COR will complete the review within a reasonable amount of time to complete their review and acceptance of the COR Review Package.

· Maintain the release plans in the OCC approved application life cycle management (ALM) software (currently AzureDevOps but referred to as ALM through the remainder of the document).

· The Release plan should include sprint, UAT and production release timelines.

The contractor must do the following:

· Configure and update ALM dashboards as software development is performed.

· Present these required reports in monthly KPI meetings that occur on the third Wednesday of every month. If the Contractor demonstrates full adoption of SPS’s Agile methodology as reflected on the SPS Agile Heat Map, for a specific product, then it will have the opportunity to reduce the frequency of presentations to a quarterly basis for that product. The Contractor must request approval of the change of frequency to quarterly from the COR.

The contractor is also responsible for maintaining Standard Operating Procedures governing the administration of each EDM-managed platform. Quarterly reviews of proposed edits to System Administration SOPs will be conducted.

All documentation developed by the contractor must be submitted for review and approval by the COR or their representative prior to publishing via existing, standardized processes.

The cost data should be for both FFP and LH tasks.

Report, which contains the Invoice ID, Invoice Date, Invoice Through Date, Contract/Task Order number, Approver Category, Solution (i.e., product), Business Unit, Project code, Hours Charged, Cost, Resource Name and Labor Category. The report shall be submitted at the same time as the invoice submission. The report and the invoices shall be submitted to the COR and the Accounts Payable mailbox.

After task order award, the OCC will provide the template to be used for producing this report.

2.1.2 Contract and Transition Planning and Management

After award, the Contractor must collaborate with ITS and the incumbent Contractor to refine and expand the initial plan into a complete transition plan that will successfully transition all applicable products, business systems, and tools from the existing project team (which will include incumbent contractors and/or OCC employees).

At the end of the task order period of performance, the Contractor shall create and execute the Transition-Out Plan and assist in the transition of its scope of work to the replacement Contractor.

For the platforms and products assigned to the Contractor in Appendix A, the Contractor shall perform the types of work described in Table 2.1.2

Table 2.1.2 Contract and Application Transition – End of Period Transition

· Transition scope and approach

· OCC resources required to support the transition

· Requirements for support from resources other than the Contractor’s team or OCC’s employees (e.g., support from third-party vendors)

· Risks and issues (e.g., schedule, cost)

· Milestone schedule must reflect completion of transition activities within 60 days.

· A list of key information items that must be communicated to other teams or business units to support the transition effectively

· Knowledge-transfer requirements

· Transfer of OCC-specific project information in the incumbent’s knowledge bases/repositories to an OCC-approved repository on OCC’s network

· Government-required training (e.g., annual ITS Security & Privacy training)

· Transfer of hardware warranties and software licenses (if applicable)

· Transfer of all existing business and/or technical documentation

· Transfer of compiled and uncompiled source code, to include all versions, baselines, maintenance updates, and patches (if applicable)

· List of desired OCC-led briefings that will serve to orient the Contractor’s new project

· The approach that the Contractor will use to document informally communicated in-formation by the incumbent that the Contractor will need to effectively maintain and operate the OCC systems

· The approach that the Contractor will use to ensure that ownership of and access to the existing project SharePoint sites are effectively transferred to the Contractor’s team

· Source-code control procedures.

The Contractor must adequately staff its transition plan to perform the full scope of work throughout the transition.

Final Transition Plan (This final version will be created from the draft Transition Plan that the Contractor shall include in its proposal for evaluation. And must include all products and platforms to be transitioned)

· Review platform and product documentation to ensure accuracy prior to offboarding including:

· Data flow diagrams (for both On-prem and the Cloud Platforms)

· Environment architecture diagrams

· Standard Operating Procedures

· System Administrator Guides

· EDM Process documentation

· Information System Contingency Plan (ISCP)

· Review open Change Requests and all work items in the ALM backlog to ensure all are current and accurate

· Review and understand EDM policies, SOPs, standards, and other relevant documents to ensure all are current and accurate

· Review last three months of helpdesk incidents and ServiceNow requests for all OCC products on the EDM platform

· Enter Privilege Access Requests (PARs) for all personnel to obtain access to EDM systems and resources across all environments

· Complete Information System Contingency Planning (ISCP) training for key personnel. This training is provided by OCC staff.

The contractor shall complete the following:

· Disseminate the Weekly Transition Status Report no later than the close of the business day (COB) prior to the Weekly Transition Status Meeting

· When possible, communicate issues, risks, and delays in advance of the Weekly Transition Status Meeting to the COR.

· Provide a list of individuals to be included in the Weekly Transition Status Meeting to the COR

· Add or remove individuals from the invite list for the Weekly Transition Status Meeting only with the approval of the COR

The Contractor must provide a draft of the Transition Completion Briefing to the COR no less than two (2) business days prior to the scheduled briefing.

Transition Completion Briefing Presentation (must include all products and platforms within the agreed level of effort.

· All business and technical documentation, whether draft or finalized, including all maintenance and operational process and procedure materials

· Transfer all compiled and uncompiled source code, to include all versions, baselines, maintenance updates, and patches (if applicable)

· Source control procedures

· Code/configurations baselines

· System logs and system notification methods

· Change-management processes and procedures

· Risk and issue logs, as well as risk-management process descriptions

· Configuration management processes and procedures

· System backup processes and procedures

· Descriptions of all environments for each platform and an explanation of the procedures for migrating code across environments Descriptions of the roles and responsibilities of the existing Contractor team members as they relate to required operations and maintenance activities.

2.1.3 Risk Management

The Contractor shall develop a Risk Management Plan for risks associated with the EDM Platforms and Products in Appendix A. Representative risk types include change management, project resources, business, technology, security, schedule, cost, technical obsolescence, feasibility, capability, strategic, and reliability. Within the risk register, the Contractor shall document the following information for each risk: the description of the risk, risk severity, the probability of occurrence, the risk owner, the associated mitigation(s), and risk resolution schedule dates.

At times, the Contractor may identify a risk that requires prompt attention by the OCC. The Contractor shall proactively notify the COR of such a risk with a level of urgency consistent with the severity of the risk.

For the platforms assigned to the Contractor in Appendix A, the Contractor shall perform the types of work described in Table 2.1.3

Table 2.1.3 Risk Management Tasks

Platforms and Products in Appendix A

the effective date of award

· Description of the risk

· Name(s) of the EDM Platforms and Products for which the risk is relevant • Risk severity

· Probability of the risk’s occurrence

· Risk owner

· Mitigation action(s) and the timeframe for implementing the mitigation(s).

Platforms and Products in Appendix A

2.1.4 Quality Control Management

The Contractor shall perform all work under this task order in accordance with the Quality Control Plan (QCP) procedures under this task order approved by the Contracting Officer and in accordance with best industry practices. The COR will monitor the Contractor’s performance to ensure that the Contractor is following accepted quality control measures.

2.1.4.1 Quality Assurance Surveillance

The OCC will use Quality Assurance Surveillance to monitor compliance with task order terms and conditions and identify nonconforming services. All work and deliverables will require 100% inspection by the COR or assigned Project Manager or their designee.

The Contractor shall comply with applicable OCC policies, standards, procedures and Federal rules, laws and regulations for the duration of this requirement. The requirements identified as most important to task order performance are set forth in Appendix B: Performance Requirements Summary (PRS). The PRS contains the OCC’s intended quality assurance standards (objectives), procedures for monitoring compliance with established standards (measures) and defines satisfactory performance ratings (expectations) for these requirements. The Contractor shall measure actual performance against the performance standards and report the results to the COR monthly (or more often if a performance problem is identified).

2.1.4.2 Quality Control Plan (QCP)

The Contractor shall develop and manage a QCP to meet the quality standards established in the Performance Work Statement. The Final QCP will be negotiated after task order award and shall be fully operational within 60 calendar days of contract award. When reviewed by the OCC COR, and accepted by the CO, the Contractor shall operate under the QCP. The QCP shall promote excellence in all functional areas of the task order. The specifics of the plan may change periodically to ensure successful performance of this task order.

The Contractor shall create a QCP to include, but not be limited to:

· A description of how the quality of all services and deliverables will be gauged and controlled to ensure conformance to contract requirements. The description shall include specifics as to the areas, items, and deliverables to be inspected, on both a scheduled and unscheduled basis, and the frequency of inspections.

· A description of the methods to be used for identifying and preventing defects in the quality of service performed.

· A description of the records to be kept to document inspections and corrective or preventive actions taken.

All inspection records shall be kept and made available to the CO and COR, when requested, throughout the contract performance period and for the period after task order completion until final settlement of any claims under this task order.

Table 2.1.4 Quality Control Tasks

Platforms and Products in Appendix A

2.1.4.3 Performance Requirements Summary

All services under this contract shall always be subject to inspection by the government. The Performance Requirements Summary (see Appendix B) identifies those task order requirements considered most important to acceptable contract performance and the government’s intended quality assurance procedures. However, the contractor is required to meet all contract requirements. The Performance Requirements Summary references apply to all required deliverables/services throughout this task order, the qualitative performance standards (objectives), the government’s intended quality assurance procedures and frequency of inspection (measures), and what the government identifies as the minimum satisfactory rating (expectations).

2.1.5 Continuous Process Improvement

The Contractor shall create and develop quality initiatives related to development and operational activities. These initiatives include collaborative activities designed to develop and enhance standards, conventions, processes, and design approaches for error handling; and approaches to reduce risk and complexity, improve performance, and support increased component uniformity and reuse. (Component may include any aspect of the EDM environment or its supporting infrastructure).

For all the EDM Platforms and Products assigned to the Contractor in Appendix A, the Contractor shall perform the types of work described in Table 2.1.5 Table 2.1.5 Continuous Improvement Tasks

2.2 EDM Operations (Firm Fixed-Price)

2.2.1 EDM Operations and Compliance

For the EDM Platforms and Products in Appendix A, the Contractor shall perform the following operations and compliance tasks.

Table 2.2.1 EDM Operations Tasks

Platform, and other data and analytical products (listed in Appendix A) to confirm that the load processes are executed as per the plan to provide accurate, consistent, reliable, efficiently structured, and timely data.

Perform on-going production data monitoring of the Data Warehouse Platform by reviewing data exceptions and warnings during the load processes to identify data discrepancies. Please note that every time a refresh occurs, this post-production monitoring must be performed, and the exceptions must be documented in the Data Exception Report. Any data exceptions and warnings should be reviewed with the business data stewards, communicated with downstream data consumers as appropriate and remediated with a sense of urgency.

The contractor is responsible for all Snowflake configurations, operations and maintenance activities including but not limited to:

· Snowflake User and Role administration: Manage roles, privileges and RBAC policies. Implement fine-grained access controls, data masking, and data security rules

· Snowflake Warehouse and Resource Management

· Performance Optimization

· Monitoring and auditing: Tracking user activity, query usage, system performance, audit logs for compliance

· Implement encryption, row and column level security, cataloging, lineage and governance artifacts

· Validate and manage Time Travel and Fail-safe policies and conduct annual recovery testing

· Provide operational support for ML pipelines, feature stores, AI integrations

· Cost Governance: Monitor usage costs, recommend strategies for cost efficiency and workload optimization

On AWS, the AWS Platform Engineering team manages the foundational services (e.g. VPCs, networking, guardrails), the contractor’s AWS responsibilities are limited to consumption and integration of the AWS services within the VPCs provisioned by the AWS Platform Engineering team. The AWS Platform Engineering team is also responsible for the integration of Snowflake and AWS VPCs.

The contractor is responsible for configurations of all AWS services within the EDM VPCs, including but not limited to:

· Work with the AWS Platform Engineering team on Identity and access management, Networking configurations, storage and compute resource administration

· Data Services Integration support for the configuration and operation of AWS data services such as AWS Glue, Athena, Lake formation and other services to enable data movement and analytics integration with Snowflake and other OCC platforms

· Maintain and enhance automation scripts and cloud formation templates to support repeatable, secure and compliance deployments

· Configure and maintain AWS CloudWatch, Cloud Trail and other monitoring and logging services for system performance, operational monitoring and audit compliance

· Apply OCC Cloud governance controls, encryption policies and data protection requirements for all workloads within the EDM VPCs

· Support the configuration and operation of other AWS Services to meet the requirements

· Administration of the Business Objects Platform in Development, Test and Production environments

· Maintain schedules and distribution of all active reports

· Administer and maintain the 360 Application Suite used to streamline the administration of the Business Objects Platform

· User account management, assist customers with reports as needed, maintain application certificates and service account passwords

· Perform routine maintenance and conduct monthly patch testing

· Upgrade the Business Objects platform with new releases

· Develop and maintain all documentation relevant to the administration of the platform

· Resolve all production incidents reported against the Business Objects platform by modifying configuration settings or other required actions to fix reported issues, testing the fixes, and implementing these fixes in all environments

· Administration of the Data Blending (Alteryx) tool in both Development and Production environment

· Refining and implementing governance models and best practices for the Data Blending

· Maintenance and patching of the Alteryx Platform, maintain application certificates and service account passwords

· Support for production deployments of workflows

· Defining and monitoring the environment controls consistent with EDM Data Provisioning CONOPS

· Monitor scheduled jobs/workflows to ensure they run successfully and promptly remediate any issues encountered – total number of current jobs below: