2019-04-22 Meeting notes

Karen

This week:

Pushing out a change to the stored procs on CAP-ROCFTP01 and 02, in HQData database, which updates the ‘Target’ field for newly created servers. This process will stop working once CRM to NetSuite transition is complete. Question for Julia: Is there a plan in place to update the HQData source, to pull from Netsuite directly, with the server data, ., vs. CRM?

Reviewing the Fortified Data Tier Assessment and working on implementing recommendations.

Documenting field mappings for the API and Geckoboard projects. Checking to see whether the fields have been created in Sandbox and populated with data. Working with Stacey to get the fields populated.

Documenting AS IS, for Traffic database - jobs, services, timing.

Starting this week, have signed up for ongoing online AWS tech talks, for ongoing learning, from selecting the right database, to Elastic Beanstalk.

Abe

Looker:

• Continued development for Real Estate Sales Operations (Matt Smocovich)

  • Individual Budgets with Prior Year-To-Date, Month-To-Date, Quarter-to-Date

JIRA:

• OSM board to Kanban

Confluence:

• Started page for terms and formulas

Frank

• Core Value Developers are on vacation this week, allowing us time to catch up with data mapping (Hive Stack)

• Reviewing the Fortified Data assessment today - much work to be done to stabilize our environment

• Attending AWS Tech Talk this Tuesday on Database selection, and doing the AWS Cloud practitioner training Wednesday

Leslie

• Continuing to work on Rackspace Analysis

• Sent out questionnaire, Scott Barske is engaged

Traffic Server Upgrade Project

• Acquired Engineering resource

• Mapping out next steps with Frank and Karen

Windows 10 Phone System Upgrade Project

• Gathered Chicago-Toronto Upgrade Scope of work

• Constraint-Bandwidth upgrade requirement

• Reviewing additional cloud based phone systems

Lowell Server Room Cleanup Project

• Researching Tech owners

• Working with Kofi and Steve

• Researching e-waste vendors, disk wiping services, etc..

Rackspace Review Project

• Meeting with Steve to create a Tech owner survey

• Ticket ownership

• Patch Management

• Rackspace Assessment in progress

KPI Report

• Brainstorm Quantifiable data

  • Tickets

    • Matt

    • Julia

    • Rackspace

Julia

Systems Support

• Updated AME for US Lobby and US Elevator Networks in Pivotal

• Updated Lauren’s Q2 Dynamic Rate Card values in Pivotal for all Venues

• Need to review new OMN issues regarding Trouble Ticket deletion

• Boostr integrations

  • APIs for inbound Account and Deals up and operational

  • Begin Unit Testing of APIs

  • Provide new data dumps of Boostr related tables

  • NetSuite API integration issues, Adam couldn’t configure on his own in Sandbox

  • Security surrounding APIs and Service ID (Pivotal)

• CRM to NetSuite implementation

  • Delay causing more demand for staff to accommodate new requirements, allowing projects dependent on implementation to move forward

    • API Integrations with Programmatic

    • GeckoBoard revamp

Programmatic Support

• Updated Floor CPM and GVT for US Elevator NetWork in Vistar

• Updated Floor CPM for US Lobby Network in Vistar

• Rubicon updates for Revenue By Building requirements: reporting Exchange vs PMP separately and accurately

Reporting

• Issue with SP that supports updating PMP manual revenue amounts to override system calculated amounts

• FSBI issue with synchronized spots delivered and Affidavit reporting

• Neil Shapiro new AME by Server reporting for Vistar and Rubicon

• Code review of Revenue Share reporting

• Provide “Translation” for code that supports Utilization to Lauren

Meeting with Niel Shapiro (4/22) to decide how to go forward with changing rubicon Id’s (he has active PMP deals, can’t change them on the fly)

Wally

Annual Sales Meeting in June … plans to show off Boostr

Just did SOW to make a working prototype by the June date. Ensuring that IT will not be the bottleneck (currently on time and under budget)

CRM integration (test / dry run on the weekend).

• Julia: not enough data for a good test

• Charlie’s log can be shared

• needed more servers for an adequate test

• Functionaly good… but did not test with a realistic volume of data

• also, sandbox is not as robust