Secrets to Getting Funding for Your Cognos Projects

Secrets to Getting Funding for your IBM Cognos Upgrades and Projects
Secrets to Getting Funding for your IBM Cognos Upgrades and Projects
February 11th, 2021

Are you using software like Cognos Analytics BI and in desperate need of a Cognos upgrade?  Or maybe you are manually using Excel for your budget and forecasting process and with the rapid changes required, need a better solution like Cognos Planning Analytics?  At the end of the day, you need to know, The Secret to Getting Funding for Your Cognos Projects. 

Funding is Not Blocked.

You may have been told, there is no budget for new projects or a Cognos upgrade.  Well, I don’t believe that to be true.  In fact, I have experienced many times where clients were told there was no funding for their Cognos upgrade, but funds magically appeared when we positioned the Cognos upgrade to solve a bigger challenge, help the organization achieve a strategic goal or showed how the Cognos upgrade mitigated a huge unforeseen risk.

Cognos Funding is Not Your Problem, Positioning Is.

The Problem is not lack of funding.  The problem is you are not positioning the benefits for your Cognos or Cognos Planning Analytics upgrade or investment in a way that benefits people that can make funding appear.  You do know that almost every CFO has a discretionary funds bucket, right?

To position your project to benefit the people with the money, you also need to understand how they are wired.  How do they make decisions?  Are they risk adverse?  Once you discover how they are wired, then you want to present in a way that makes the decision to fund your Cognos project easy and comfortable, which includes addressing all their possible objections.

Bad Experience with Previous Upgrade.

You also want to explore what experiences has the decision maker had in the past with IT projects?  If the CFO, who typically is risk adverse, had a bad Cognos upgrade 10 years ago, he or she may not be willing to fund your IT project or upgrade.  The secret to getting funding then is to make sure you show them the process you will be taking and ensure mistakes of the past will not happen again. 

There are so many tips we can share about getting funding for Cognos, that we decided to create a webinar on the topic.  Here’s a link to our webinar which was the first of our monthly Client Success Webinars, How to Get Funding for Your IT Projects. 

If you would like to join our future Cognos Client success webinars see our events page

Additionally, you might want to check out our previous blog
5 Steps To Get Project Funding

Need Help Positioning Your Cognos Upgrade?

If you are an IBM Analytics customer looking to get funding for your Cognos Planning Analytics TM1 or Cognos Analytics upgrade or additional licenses, you don’t have to go it alone!  Lodestar Solutions is happy to help you strategically design your pitch for funding using are proven method and secrets to getting funding for your Cognos projects.  Just email us at so we can help show you a better way.

What Kind of Audit Trail is Available for Cognos Planning Analytics (TM1)?

Audit Trail in TM1
Audit Trail in TM1
October 29th, 2020

A budgeting and planning solution should always provide a good audit trail.  So, what kind of audit trail is available for Cognos Planning Analytics (TM1)?  IBM Planning Analytics maintains a detailed log of all changes in the system.  The log tracks changes by the users and processes as well as data changes and structural changes.  This is music to your compliance team’s ears, especially if you have to comply with the Sarbanes-Oxley Act.  (If you want to learn more about SOX and IBM Planning Analytics check out our earlier blog, Is the IBM ILMT tool SOX Compliant when used with Cognos?) 

TM1 Logging Types

The Cognos Planning Analytics administrator can turn off or on two types of logging.

  • Transaction Log - captures all changes to data caused by end users, rules or processes
  • Audit Log - captures changes to metadata, security, logon information and other system activity detail

TM1 Transaction Log

If you want to see a simple list of all changes in values, you will look at the TM1 transaction log.  It also records the cube name, time and date, username and values before and after the change.  Cube logging can be enabled and disabled for specific cubes.  The changes are recorded in the tm1s.log file. 

One thing to note is that transaction logging can be enabled and disabled during TurboIntegrator processes by using the CubeSetLogChanges() TurboIntegrator function.  Lodestar Solutions recommends you consider disabling transaction logging during a TurboIntegrator process that loads a large volume of data to a cube because the file can get quite large.  If a TurboIntegrator process can be rerun to reload the same data into a cube, transaction logging can most likely be disabled during the TurboIntegrator process.  For more information, see CubeSetLogChanges.

For more details on the TM1 Transaction Log see the IBM Knowledge Center

TM1 Audit Log

The TM1 audit log monitors changes to metadata, such as modifications to dimensions, views and subsets. It also tracks login and TurboIntegrator process execution.  By default, audit logging is disabled and must be manually enabled for each server you want to monitor.  When it is on it monitors everything, you can’t only have it monitor certain activity.  Audit logging is enabled and disabled with the AuditLogOn parameter in tm1s.cfg file.

You can query and view the audit log using the Audit Log window, available in TM1 Server Explorer. When you turn the audit log on you might want to monitor it because it can get quite large.  Some of our TM1 clients opt to turn it on only in the final stages of the budget renew process, especially if you are starting with a zero-based budget.  For more details on the TM1 Audit Log see the IBM Knowledge Center.

How to Archive TM1 Audit Logs with IBM Cognos Planning Analytics

We mentioned the TM1 log files can get quite large, especially if you did not limit the auditing to particular cubes and processes.  We all have experienced when you run out of space, weird things can happen.  So, you may want to archive your TM1 audit logs.  To do this we recommend you use the Turbo Integrator (TI) process ‘’.  This process is designed to move old transaction log files from a specified TM1 Log File Directory to a separate ‘archiving’ directory.

Turn on Audit Trail in Cognos Planning Analytics - TM1

Yes, Lodestar Solutions recommends clients to leverage the TM1 audit trail capabilities.  However, we do recommend you do so with proper planning.  Just turning it on and letting it collect data could result in a bloated log file that causes issues. 

Contact Lodestar Solutions

If you have any questions about what kind of audit trail is available for Cognos Planning Analytics (TM1) and how you should leverage the various components for auditing, don’t hesitate to reach out to us at

Visit our website;

How to Get the Best Value on Your Cognos, TM1 and SPSS Support Renewals

Support Value
Support Value
August 27th, 2020

We all know the best price is not always the best value when shopping and it is true of IBM Support Renewals as well.   If you are looking to renew your IBM Cognos, Planning Analytics (TM1) or SPSS support you want to make sure you get the best value.  You might be thinking, my support is the same if I buy it from IBM or a partner.  But that is not always true! Today we will share secrets on, “How to get the Best Value on your Cognos, TM1 and SPSS Support Renewals.”

IBM Support Renewals Process

Let’s start by reviewing the IBM support renewals process.  When you purchased your initial licensing for Cognos, Tm1 or SPSS you received one year of support with the purchase.  After that you are provided a quote for support from IBM annually. This support allows you access to patches, upgrades and the ability to contact IBM directly for support.  Here’s a link to IBM information about renewing support.

Keep Current on IBM Support

Lodestar Solutions recommends all clients keep current on their support.  It’s not worth the risk of being unsupported.  (See our blog, Consequences of Not Renewing IBM Cognos Support)  And of course we resell IBM support as do many partners.

Partners Sell Support Cheaper Then IBM

In the past, IBM partners like Lodestar Solutions were often able to sell support renewals to clients cheaper then IBM could sell it.  The way we provided aggressive quotes to clients was by giving up some of our margin, which we called the Lodestar client discount.  But what makes Lodestar unique is that in addition to very competitive quotes, Lodestar provides clients with an annual license check-up where we discuss what you own, what changes IBM has made in the licensing and the software and offer recommendations based on your unique situation.

What the Heck Do I Own - Cognos, TMI, SPSS

Our clients have found Lodestar’s IBM Support Renewal checkups and “What the Heck Do I Own” sessions for Cognos BI, Cognos Planning Analytics (TM1), and SPSS very beneficial.  Every client that renews with Lodestar receives a free customized, “What the Heck do I Own” session where we review your licenses and educate you on functionality you did not even know you had.  We talk about your challenges and how other clients have overcome similar challenges.  This is a very beneficial session. It’s not uncommon for clients to tell us the one-hour session taught them more than a week at an IBM event.   Our reviews have saved our clients huge amounts of money.  (Check out our blog: How an IBM Cognos User Reduced Support Costs by $30,000!)

IBM Changes to Renewals August 2020

Well, in August 2020 IBM changed the partner renewal program and significantly reduced the margins that partners could make. As part of the changes IBM decided they wanted to protect partners that sold the renewal last year, by giving what they call the incumbent partner more margin than other partners.  

Personally, I disagree with IBM’s changes because I believe in competition.  Not all partners offer the same value for the renewal.  I believe the recent move may hurt clients as it does not create an incentive for true value adding partners to reach out to help clients that may be confused with their licensing.  If you renewed with a partner last year that just gave a fabulous quote and did not add value, and this year you want help with licensing and clarification as to what you own, you may find that as you reach out to other IBM partners, they may not want to even provide a quote because they can’t make enough money to justify the work.

Case Study for Value Added Renewals

For a long time, Lodestar Solutions had a client that regularly reviewed their licenses with Lodestar.  Then 5 years ago the executives at the client decided to move all their support renewals to what we refer to as a license consolidator.  Consolidators are large companies that can renew almost every software brand and give discounts due to volume.  The client’s goal was to save money. 

The Cognos BI and TM1 power users were very upset as they loved all the value added services they received throughout the year from Lodestar Solutions.  But the decision came from the top.  Lodestar still worked with the client for services but did not provide licensing recommendations or the annual renewal review. 

Then late in 2018 IBM made changes to the licensing of Enterprise Planning Users and the changes put some clients that move to TM1 at risk of failing an audit.  (See Video for details)  So, Lodestar Solutions reached out to all clients we thought were at risk due to the changes, even those that moved to consolidators.  Well, it turns out, the consolidator did not educate the client on IBM license changes or do annual reviews and the client failed an audit a year earlier costing them almost $1 Million.  When we reached out educating them, they may again fail an audit they realized that the consolidator wasn’t saving them money it actually cost them a bundle!  Yes, the client returned to work with Lodestar for their renewals.  But the moral of the story is, the best price is not the best value.

IBM Changes Not in Clients Best Interest

As I stated earlier, I do not believe IBM’s recent changes to their partner renewals program benefits the clients, but it did cause me to look in the mirror and ask myself how Lodestar can add even more value!  You see, I hate telling the clients their “Lodestar client discount” is being significantly reduced.  But, due to IBM changes we cannot offer the same level of discounts, so instead we are upping our value.  Effective September 2020 all clients that renew their support with Lodestar Solutions will receive the following:

Lodestar Support Client Bonuses

  • Annual licensing review to ensure you are in the optimal licensing mix
  • A “What the Heck do I Own” session where we discuss the new functionality of your unique licensing mix
  • A forward-looking discussion to create a roadmap and recommendation of 3rd party tools that might help you realize your vision faster
  • Access to Lodestar’s private client only collection of videos to educate you on new functionality
  • Periodic no charge check-ins to address your challenges
  • Presentation coaching to help you gain the support and resources you need to success
  • Lodestar Virtual Semi-Annual User Group Meetings
  • Invites to Lodestar exclusive events and offers


Lodestar Solutions is here to help you get the best value on your Cognos, TM1 and SPSS Support Renewals.  Value is not just price.  When you evaluate who you work with, don’t you want someone that understands licensing, can navigate the IBM red tape and helps you succeed?

If you want to get the most value from your IBM Support renewal, contact us today at and set up a time to chat.

Creating the COVID Forecast with Cognos Planning Analytics, TM1

COVID Forecast
COVID Forecast
April 30th, 2020 ​

Wow, the world has changed in just a few weeks!  Our way of life as we knew it may never be the same, nor will our businesses. Lodestar Solutions has been working with our Cognos Planning Analytics TM1 clients to respond to the new risks and opportunities they are facing. For almost every business it’s time to update the plans and create a COVID forecast.  But don’t worry, creating a COVID Forecast with Cognos Planning Analytics, TM1 should be relatively easy. 

Steps for Creating a COVID Forecast in TM1 –

Define the COVID Forecast

The first thing you want to do is define what the COVID forecast in Cognos Planning Analytics should look like.  Schedule a Zoom or remote meeting with Senior Managers to discuss what they need in a COVID forecast. Before the meeting send the request and include the goal of the meeting and an agenda. You should also send examples of reports they currently receive and ask them to print them, so they have them handy.  For the meeting I recommend going on camera, as this is your time to shine and show how indispensable you are!Enter your text here...

During the meeting Lodestar Solutions recommends the following: 

  • Ask what information is important to track more granularly for a COVID forecast? Do they want a forecast or budget level details? Do they want more detail for sales and staffing?
  •  Have them write down on sticky notes everything they want in the COVID forecast and prioritize each item.   
Sticky Notes
  • Don’t commit!  Tell them you are collecting their ideas and will look at what’s easily done without massive overhaul of your TM1 models.
  • What assumptions do they want to use as “what if” scenario drivers to model the business in the new COVID forecast?
  • Refer to the current reports that you sent in advanced and have them write down what they want to see differently for the COVID forecast in TM1.  If they make a lot of changes have them screen shot or take a picture of the changes with their phone and send them to you. This will be your audit trail when they change their mind again.
  • Have follow up virtual meetings as you build your new structures to ensure you are on the right path and more importantly find out if they have changed their minds since your initial meeting on the COVID forecast models in TM1.

NOTE:  They almost always change their minds, but rarely do they communicate their new thoughts.  So, the follow-up, status check meetings are very important.

After the Meeting Planning

  1. Review the diagram of your TM1 model. If you don’t have schematic of your model now would be a good time to create one.  We like Visio for this, but PowerPoint or Word can work as well. This should have the various cubes and IT processes displayed.
  2. Update your Cognos Planning Analytics Development or Test environment with the latest version of your models, so you can make your changes in a development environment.  If you don’t have a development environment for TM1 we highly recommend it. Lodestar is happy to help you with any licensing needs for your non-production environment.  See our blog on this topic for more information. 
  3. Look to see which model or components you would need for your new COVID Forecast.  Many Cognos Planning Analytics, TM1, clients have a forecast model that is not as detailed as the budget which could be leveraged for the COVID forecast in TM1.
  4. Check for any Versions dimensions that you could add a COVID forecast too.  For example, if you have a version dimension in TM1 that has Budget, Actual, Q1 Forecast… consider adding COVID forecast to it.
  5. Identify which TM1 TI processes would need to be updated for the COVID forecast and if you need to create new TM1 model components to provide more details in specific areas.
  6. As you identify what changes need to be made, we recommend documenting items to test. The easiest way to do this is just start writing testing idea on sticky notes.  One test per note and create a pile. Later you will use this to create TM1 test scripts.
  7. Create a project plan for the your COVID forecast TM1 model changes. If you don’t have a good tool to manage your projects, Lodestar Solutions recommends and resells  Smartsheet. For more information email us at
  8. If you need assistance or just want to get another opinion, seek help from Lodestar Solutions’ team of TM1 consultants.  Email us at  or check out Lodestar’s Small Project Program.

Testing Your New TM1 COVID Models

  1. Create and execute TM1 COVID forecast test scripts based on the testing sticky notes you have been creating.
  2. Demo the updated Cognos Planning Analytics TM1 model to Sr. Managers.
  3. Assuming they love it, move the TM1 models to production.
  4. Celebrate with your kids and family!

Your Moment to Shine with TM1

See that wasn’t too bad was it. A few key points. When creating the COVID forecast with Cognos Planning Analytics, TM1, Planning is the most important point.  Since you are probably working remote, you must not assume you know what the executives want.  Heck they don’t really know what they want.  We have never been in this situation!  So, you MUST schedule virtual meetings with them.  When you meet with them, go on camera.  You want to be seen as indispensable to the organization and this is your moment to shine! 

Remember you don’t have to go it alone!  Lodestar Solutions can help you along the way.  Just email us at and schedule a time to chat about creating your COVID forecast in Cognos Planning Analytics.

Neither Cognos BI nor Microsoft Power BI can Replace Cognos Planning Analytics (TM1)!

Neither Cognos BI nor Microsoft Power BI can Replace TM1!
Neither Cognos BI nor Microsoft Power BI can Replace TM1!
February 13th, 2020

Recently I met with a client who owned and was using both IBM Cognos BI and TM1.  Their IT team was exploring if they should move from Cognos to Microsoft Power BI. Understandably, IT was trying to reduce the number of applications and tools they supported. I explained to them that neither Cognos BI nor Microsoft Power BI can replace TM1 now called IBM Planning Analytics.

What is Cognos Planning Analytics (TM1)?

BM Planning Analytics formerly known as TM1 is a powerful business performance management software designed to deliver collaborative planning, budgeting and forecasting solutions, interactive "what-if" analyses, as well as analytical and reporting applications. Over the years, IBM has added a lot of new capabilities to TM1 including hierarchies, Planning Analytics for Excel (PAX) and Planning Analytic Workspace (PAW).  Planning Analytics Workspace provides not just powerful dashboard capabilities but can be used to build new models as well.  See our earlier blog.  For more information on Planning Analytics Workspace check out our team member Atif’s Video.

Cognos Planning Analytics Workspace

Confusion Between BI and Planning Analytics (TM1)

As IBM enhanced TM1 and added Planning Analytics Workspace (PAW) they delivered amazing dashboarding capabilities.  They added balanced scorecard capabilities too.  Unfortunately, this may have led to the current confusion.  As you know dashboards are usually delivered through business intelligence tools like Cognos BI (Cognos Analytics) and Microsoft Power BI.  Additionally, some finance teams have leveraged TM1 as a lightweight version of a data mart, which IT is not always thrilled about.   So, when IT sees Planning Analytics (TM1) they can jump to the conclusion that the business intelligence tools they usually control like Power BI and/or Cognos Analytics and SQL Server Analysis Services (SSAS) cubes could replace Planning Analytics.

For more information on SSAS check out this link. 
To learn more about the new functionality in Cognos Analytics (BI) check out or earlier blog.

Cognos Planning Analytics Does what BI Does Not

Cognos Planning Analytics TM1 is very different than Cognos BI and/or Power BI!  Although it can handle dashboards and reports, it’s not designed to do bursting of reports and other functionality tools like Cognos Analytics Excel, etc… But, Cognos Planning Analytics TM1 does so much that BI does not.  Planning Analytics TM1 allows users to write back to the TM1 cubes structures to enter in budgeting and forecasting data. You would not want users to be able to change Cognos BI data that is typically historical data.  TM1 is a flexible modeling tool that allows for “What if” analysis, sandbox scenarios and powerful spread capabilities. It’s no wonder why finance departments love the power and flexibility of the new Cognos Planning Analytics version. 

If you  want  more information on the latest information on Cognos Planning Analytics check out the IBM web site or better yet, just email Lodestar Solutions and let’s chat.  Contact us at

Why Finance Needs Unique Tools Like Planning Analytics TM1

It’s important to understand that in finance we live in a constant world of change.  Finance teams need to forecast and plan the affects of changes on the financial statements of the organization. It’s not uncommon for an executive to email the finance team and ask to see data in a new way.  For example, maybe a food distributor’s CFO suddenly wants to see sales by country of origin.  When this happens the finance team previously became stressed out thinking about how they have to rebuild models to incorporate the change.  But with Cognos Planning Analytics finance can leverage virtual dimension and rapidly provide these new insights. Once provided the CFO may then ask, “What would happen to our bottom line if all our avocados from Mexico were recalled.”  With Planning Analytics TM1 the finance team could easily do a what if model entering adjustments to reduce Mexico avocados and increasing sales of avocados from the US.  This on the fly modeling is often foreign to IT and business intelligence professionals that live in a world of governance, and control.  But if IT tries to eliminate TM1, they run the risk of making finance return to the world of Excel which lacks controls and processes provided by Cognos Planning Analytics.

Finance Should Keep their Planning Analytics

In summary, neither Cognos BI nor Microsoft Power BI can replace TM1 because TM1 provides a flexible modeling tool with write back and data collection capabilities not available in most business intelligence.  If your organization is having this internal debate, you don’t have to go it alone!  At Lodestar Solutions we can help you facilitate workshops to define what your unique analytic and business intelligence roadmap should look like. We will provide our expert opinions and network you with other clients that have walked in your shoes.  So, contact us at

New Hierarchy Level Behavior in Planning Analytics (TM1) Set Editor


Leaf Element Level naming convention is really changing...

It's when I first started teaching the Performance Modeler (PM) class and showing students how to create a TI Process with the Guided Import that I noticed in PM that the leaf level was not Zero.  The highest consolidated level was Zero.  At that time I just thought it was a fluke that PM was designed differently, but as for the rest of TM1, they were going to stick with the numbering convention that Architect used.  Wrong!

You have to be a 10 to be number one.  Huh???

Fast forward and I'm now working with Planning Analytics Workspace and PAx.  Like many consultants, we learned TM1 using Architect.  In Architect, level Zero was synonymous with the leaf level element of a dimension and we all know that TM1 holds numeric data only at the leaf level.  We've gotten very accustom to using the terms "leaf", "n-level" and "Zero-level" interchangeably.  In fact, my first dynamic subset was created using the Filter by Level option and choosing "0" for the leaf elements and even naming the subset "Level_0".

Being Level Zero is tops!

Historically TM1 has labeled its hierarchy levels where level 0 is the leaf level and the highest number is the top level.

This behavior persists today in Architect and Perspectives, but with the new set editor released in the 2nd version of Planning Analytics, the behavior in the set editor now follows industry standard MDX practices where level 0 is the highest level and the highest number is the leaf level. In other words, the reverse of what it was previously.

End users should be educated in this change as to avoid confusion when working with the data.

This issue is best highlighted when editing a set. First let’s look at Architect. In this example the plan_time dimension is opened and all elements are shown.

If we filter by levels as shown below, the 0 level will be the leaf level.

And if we filter the level on 2, in this case, it will return the highest level.

Conversely in the Planning Analytics Set editor in Planning Analytics Workspace or Planning Analytics for Excel, the reverse filtering method is true and is in alignment with standard MDX queries. In this example, we are filtering on level000 which returns the top level as seen below.

And if we filter on level002, it returns the leaf level as seen below.

The set editor also provides an easy method to filter on the leaf level by providing an easy to use Leaf Level option in the filter.

Before we get into some solutions to simplify the end user experience, remember that if users are proficient in MDX syntax including TM1-specific MDX functions, they can always quickly build their expression-based subsets by editing the MDX in the Set Editor.

For example, the following standard MDX expression would return all leaf level elements in our example:


If you wanted to return the top level elements, you could use the following expression:


Again, where 0 is the highest level and 2 is the lowest level in the example.

Conversely, you could use TM1-specific MDX functions to create the old behavior in the set editor’s MDX expression by using the following syntax which returns the leaf level:

{TM1FILTERBYLEVEL( {TM1SUBSETALL( [plan_time] )}, 0)}

Or, the following to return the highest level in our example:

{TM1FILTERBYLEVEL( {TM1SUBSETALL( [plan_time] )}, 2)}

Where 0 is the leaf level and 2 is the top level.

Methods to Simplify the User Experience

Create Named Levels

One method is to give your hierarchy levels meaningful names for your end users.

To do so:

In Architect, ensure you have enabled Display Control Objects under the View menu.

Find and open the }HierarchyProperties cube and then from the Dimensions drop down list, select the dimension you would like to override the naming convention for.

In this case we will select plan_time and provide the following level names.

Save the View as Default and not Private.

Now the plan_time dimension’s hierarchy needs to be updated. To do so, we will run a TI process. Right-click Processes in the left pane and click Create New Process.

Click the Advanced tab and then the Prolog tab.

After the Generated Statements section, enter the following syntax where DimensionName is replaced with the dimension you want to update. RefreshMdxHierarchy('plan_time');

Save the Process with an appropriate name and then click on Run to execute the TI process.

Now in the Planning Analytics Set Editor, the level names will appear in a more meaningful way.

Dealing with Ragged or Unbalanced Hierarchies

In some cases, the hierarchies may present elements at the same level as your consolidated levels which you may not want to display in your results when working in the Set editor.

In our example, we can see this with the Description element being displayed when filtering on the Year level.

A simple way to make the user experience more focused is by creating appropriate subsets.

In this case you could create and save a Public subset for the dimension that only displays the Years. In this case a subset called All Years.

With this selection, users have a focused list of elements to work with which they can also expand and there is no need for the extra clicks involved in filtering.

Notice description is no longer present.

So the moral of this story is that you may as well get on board with the new naming convention and start naming your subsets according to what "Level Zero" means going forward and not keep it as it's legacy term.  This will keep the new subset editor consistent with the way Performance Modeler treats levels with the guided import process of creating TI Processes too.

Get more out of your Planning Analytics/TM1 solution faster

Need to build more analytics into your model, but don't have the time.  Lodestar Solutions offers our Small Project Service.  Chipping away at your "To Build" list with our Small Project Services will get you results faster and cheaper than making a big production creating the "Next Phase Major Build" that usually gets kicked down the line due to cost and time.  If you have additional questions about this service or require assistance immediately, please contact Lodestar at (813)-415-2910 or at