Bringing our values to life SWG Vendor Operations
Bringing our values to life SWG Vendor Operations – Guidelines for Vendors During an engagement – Non ERS October 2009 © 2005 IBM Corporation
Agenda • During an engagement Vendor Responsibilities Consultant Activity Reports (Timecards) Expense Reports Status Reports Invoicing IBM e. Mail Access/Badges §Contact Information/Where to go for help 2 © 2005 IBM Corporation
DURING ENGAGEMENT Vendor Responsibilities While deployed on an engagement • Vendor Management • Respond to requests for Non ERS/SOW review and signature within same business day. • Do not allow consultant to start work or work beyond contract limits without work authorization (ERSA, SOWA and Amendments must be processed prior to). • Monitor hours, expense and dates against contracted parameters. If extensions are needed, contact engagement owner in advance for contract alterations and copy BRAND ID. • Inform engagement owner of any issues that arise on the account and copy BRAND ID. • Inform engagement owner of any scheduled consultant absence and arrange for backup if required. Copy BRAND ID • Gather and review timesheets and status reports and ensure subm ission are on time and on a weekly basis. • Ensure billing is current (within two weeks of work performed). • Do not solicit for hire or consider for hire another vendor’s consultan t you learned about on an IBM engagement. 3 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT While deployed on an engagement • Vendor Consultants • Keep IBM engagement owner informed regarding engagement. • Submit accurate timesheets and status reports by noon EDT each Monday following the week worked. • Submit expenses on a timely basis to ensure billing is current and to secure reimbursement (within two weeks of exp incurred). • Do not discuss the specifics of IBM’s contract with the IBM customer. • Do not discuss rates with the IBM customer. • Protect IBM’s intellectual property and confidential information. • Submit all deliverables to the engagement owner and to your vend or management for inclusion with billing. • Any modifications to your engagement must be made by IBM and not 4 the end Customer. © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT Details • Consultant Activity Record (CAR) – • A CAR is the form used to submit a record of a consultant’s hours work ed on an IBM engagement. • A CAR must be submitted every week for every consultant under contr act whether they have worked or not. CAR forms are due into timecard@us. ibm. com by NOON EDT on Monday following the week worked. • CARs should be submitted to a central focal point within your vend or company. The focal point will either enter labor directly into the IBM labor claiming syste m (ILC), or will provide softcopy to timecard@us. ibm. com. • Please ensure that labor is submitted accurately the first time. • If you do not have a CAR form (a copy is included in the Master SOW or regular SOW), please download one from: ftp: //public. dhe. ibm. com/software/service soperations/. • Approved CARs generate invoices to IBM customers. For this reaso n, IBM tracks weekly submission of CARs and will contact your company if a CAR is subm itted incorrectly or is missing. • In order to pay a vendor invoice containing hours, approved hours matching the invoice must be in IBMs labor claiming system. 5 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT Details • Consultant Activity Records (CARs) – • How to complete a CAR - Shown on the next slide • Submit in Excel format (no zip files for multiple consultants) • Include w/e time period • Include Consultant Name • Include Customer Name • Include work # • Include Bill Code • Include z. Serial# • Include BRAND • A CAR is required for each project. If a consultant is engaged on one or more projects then a CAR form must be submitted each week for each project. • A Zero Hour CAR must be submitted if a Consultant is scheduled but has not worked during a specific week • Please utilize the following naming convention for each CAR: CAR_Your Company Name_Consultant Name_Work#_Week Endin g Date (mm/dd). xls ex: CAR Perficient John Jenkins C 45672 03/31. xls • Submit CARs to: timecard@us. ibm. com 6 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT Details • ZSerial # • What is it? • A unique identifier for each subcontractor consultant, used when enter ing labor into IBM’s labor claiming system • Why do you need one? • These are required by your company to enter consultant labor into IBMs labor claiming system or for submission of a CAR and Expense Reports. They allow IBM to track expense and labor by consultant. . • Where can I find z. Serial #’s for my consultants? • On the VRS generated when an IBM PO is requested by a subcontra ctor analyst. If you are unsure of which # to use, please contact your subcontractor analy st 7 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT Details • Work Number • What is it? • A unique identifier for each IBM customer contract. The number is used by IBM to charge expense to the project and to generate invoices to IBM custo mers. • Why do you need one? • These are required by your company to enter consultant labor into IBMs labor claiming system or for submission of CAR and Expense Reports. • How do you know which Work Number to use? • On the VRS generated when an IBM PO is requested by a subcontra ctor analyst. If you are unsure of which # to use, please contact your subcontractor analy st 8 © 2005 IBM Corporation
DURING ENGAGEMENT 9 © 2005 IBM Corporation
DURING ENGAGEMENT Vendor Responsibilities Details • Status Reports (requirements varies per project and BRAND) • Status reports are required on a case by case/project by project basis • Please check with the engagement owner to see if they require a statu s report • A status report template is contained in a Master SOW or an SOW . • For a softcopy form, please work with the engagement owner. • If a status report is required, please check with the Engagement owne r on who should receive them 10 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT Invoicing IBM • Receipts are required for any single expense $25 or more. • One expense report is required per consultant for each week of trave l. • Bundling of Consultant meals is not allowed • Invoice should be submitted electronically against the PO via the WOI system. • Utilizing the following format for invoice line items will ensure we have enough information to validate your invoice and eliminate the need to follo w up (which can cause delays in payment). Please note that any deliverables as outli ned in the SOW/ERS are included with the billing back up • Labor line item format: Consultant Name, ZSerial#, Work #, # of hours per w/e date ex: John Smith Z 45389 C 46932 w/e 3/30 40 hours w/e 4/7 45 hours w/e 4/13 40 hours • Expense line item format: Consultant Name, z. Serial#, Work#, expe nse amount per w/e date ex: John Smith Z 45389 C 46932 $370. 25 w/e 4/7 $1, 567. 00 w/e 4/13 • Fixed price line item format: Milestone Name as outlined in agreement with IBM, customer name, deliverable if applicable ex: Architecture Review, Bell. South, Architecture Document 11 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT Invoicing IBM – Cont’d. • Vendor billing focal should efax or email expense forms and receipts to subcontractor analyst prior to or at the time of invoice submission. • Expenses should be billed within two weeks of incurring the expense. • Expense backup should be submitted to the BRAND ID as separate files and emails, not in the same email as CAR and Status Reports. • Standard Format – shown on next page should be used • If you have problems with WOI, please contact the WOI Helpdesk at 800 -856 -1626 or email woical@in. ibm. com 12 © 2005 IBM Corporation
Vendor Responsibilities 13 DURING ENGAGEMENT © 2005 IBM Corporation
Vendor Responsibilities 14 DURING ENGAGEMENT © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT IBM email and access behind the IBM firewall • If an engagement requires that a vendor consultant have an IBM ID and access behind the IBM firewall, the IBM engagement owner must submit a request form to outssubk@us. ibm. com. • Consultants must have a valid schedule entry in the scheduling data base prior to an ID being issued. • If access is required for a vendor RDM or admin requests must be Andrea Ward, AEWARD@CA. IBM. COM. approved by • Issuance of an IBM ID takes approximately 10 business days. • IDs will be sent to the requesting IBM Manager/Project Owner for distr ibution to the vendor PM. 15 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT IBM email and access behind the IBM firewall – Cont’d. . • Parameters for keeping systems access: • Core vendor consultants can keep their IDs in place as long as six weeks after the engagement ends. If not re-deployed at that time, system acce ss will be suspended. • Other vendors system access will be suspended within 24 hours of engagement end. • Vendor companies must notify outssubk@us. ibm. com immediately if any resource having an IBM ID leaves their employ for any reason. • ID owners must comply with the IBM IT Security Guidelines outlined in the information sent with the ID. • ID owners can only use IBM IDs for IBM approved purposes. 16 © 2005 IBM Corporation
Vendor Responsibilities DURING ENGAGEMENT IBM Badge. §IBM badges should only be required if an subcontractor is working on IBM premises. §If a badge is required for a subcontractor, a request must be sent to outssubk@us. ibm. com. The request must include the location of the nearest IBM facility – the location the subcontractor would go to for the badge. §To be eligible for a badge, a subcontractor must be actively deployed on an IBM engagement. §For core vendors, badges can be kept active as long as six weeks with no deployment. At that time, the badge will be deactivated. If a core vendor leave s the employment of the vendor for any reason, the badge must be collected and retur ned. OUTSSUBK@US. IBM. COM must be notified within 24 hours of the last date of employment so that the badge can be deactivated. §For other vendors, badges must be deactivated within 24 hours after engagement or employment end and then sent to Outsourcing for destruction. Mail to Lita Mann, 7003 Buccaneer Trail, Austin TX 78729. 17 © 2005 IBM Corporation
Contact Information Where to go for Help: Subcontractor Analysts (note: brand ids are monitored by a primary SA, with backup coverage as needed) Collaboration (Lotus) isscsubk@us. ibm. com (efax 845 -491 -3180) 18 Tivoli isstsubk@us. ibm. com (efax 845 -491 -5767) Rational issrsubk@us. ibm. com (efax 845 -264 -6263) Business Analytics (Cognos) issbasub@us. ibm. com (efax 845 -491 -7076) Web. Sphere aimsubk@us. ibm. com Information Management issimsub@us. ibm. com (efax 845 -463 -8741) Security ibmss@us. ibm. com (efax 845 -491 -7076) Industry Solutions ississub@us. ibm. com © 2005 IBM Corporation
Contact Information Where to go for Help: General Topics CAR/Timesheet Submission timecard@us. ibm. com CBC/Resource Verification ibmswgdocs@infinite. com Forms, Resumes, Subcontractor Set-Up, Am. Ex Travel 19 Procurement Contacts by Brand Check with your Brand Subcontractor Analyst Vendor Systems Access/Badge outssubk@us. ibm. com Escalation Tom Kuhar, tom_kuhar@us. ibm. com, 208395 -0355 © 2005 IBM Corporation
Contact Information Where to go for Help: Partner Relationship Management Team Roles: §Proactive partner relationship management §Identifying new vendor companies that can address skill gaps §Negotiation and set up of MSOWs (ERS enables a partner) §Point of contact for the delivery team to address issues with existing partners *For a complete list of Partner Relationship managers please see Contact List for Partner Relationships 20 © 2005 IBM Corporation
Contact Information Where to go for Help: Partner Relationship Manager Gina Benedick. Davidson 21 Rational, Tivoli, Security, Information Management 208 -395 -0347 ginabene@us. ibm. com Brian Hawthorne Web. Sphere 401 -477 -6489 brianhaw@us. ibm. com Ted Smith Business Analytics, Collaboration 720 -396 -9210 ted_smith@us. ibm. com Andrea Ward Industry Solutions 905 -686 -5566 aeward@ca. ibm. com © 2005 IBM Corporation
Contact Information for ICS Where to go for Help: Initial Set up John Laskey jlaskey@bellsouth. net Sales Recruiter/problem solver 919 -678 -1228 Kathy Rowell Issue Resolution: POs, Unique email ID ERS/ERSA 813 -641 -0730 Krowell@infinite. com Ibm-ers@infinite. com Billing inquiries: Unique email ID ibmpayables@infinite. com Consultant Documents CBC/RVF, Resumes, AMEX Travel, etc Unique email ID ibmswgdocs@infinite. com Contracts Subba Badeti 609 -269 -8633 sbadeti@infinite. com 22 © 2005 IBM Corporation
- Slides: 22