Supplier B2B Integration Readiness and Technical Assessment Questionnaire / Version 1.0
December 1, 2014
1 Purpose
The purpose of this document is designed to capture critical information necessary to assess that CRC and its suppliers can exchange electronic business data using mutually agreed upon PIDX and RosettaNet file formats and protocols. Essentially, the Supplier B2B Integration Readiness and Technical Assessment guide demonstrates the following:
· An indication of what effort and resources will be required to ensure successful enablement
· Essential contact names and contact details within the supplier organization to ensure effective and regular communication is maintained between parties
· Connectivity requirements between CRC and its Suppliers (from/to supplier middleware server to/from CRC B2B server) via HTTPs and Client authentication
· Successful protocol/ process handling
· Successful exception and error handling
· Digital certificate signatures
2 B2B Integration Supplier Instructions
The supplier should complete this questionnaire and submit completed forms by e-mail to .
3 B2B Integration – supplier Key Contact Information
Please fill in the contact information for the following individuals:
Feature Name / Project Manager / B2B Technical Lead / B2B Support Lead / Business LeadName / / / /
Job Title / / / /
Address / / / /
Phone Number / / / /
Mobile Phone / / / /
Email Address / / / /
Corporate Information:
B2B Infrastructure LocationCorporate Mailing Address /
Web Site /
Main Phone Number /
Dun & Bradstreet Number (DUNS) /
4 B2B Integration Supplier General Business QUestions
1. What is your level of interest in becoming a CRC B2B Integrated Supplier?
High / Medium / Low2. What level of impact will becoming a CRC B2B Integrated Supplier have on your organization?
High / Medium / Low / No impact3. Does your company have a B2B initiative today?
Yes / No4. Does your company have resources to become a CRC B2B Integrated Supplier?
Yes / No5. If NO, when will the company be ready to become a CRC B2B Integrated Supplier?
2 – 4 Weeks8 – 12 Weeks
12 – 16 Weeks
In 6 months
In 9 months
In 1 yrs time
Not planning to become an CRC B2B Integrated Supplier
eeks4 ct XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
6. How is data being exchanged today with CRC or your other trading partners?
E-MailHTTPS
FTP
Excel
Fax
Phone
Electronic Trading Exchange Network (Please specify e.g. OFS Portal, Channel Link, etc.
Not Transmitting
Other (Please explain below)
7. Which of the following document types are you currently exchanging with your trading partners?
Purchase OrdersInvoices
Remittance Advices
Rate Sheets / Price Books
Field Tickets
Other (Please explain below)
8. What is the frequency in which you exchange electronic (B2B) data?
DailyBatch (Please specify
Per
Weekly
Monthly
Real Time
Not Transmitting
Other (Please explain below)
5 B2B Integration Supplier Technical Questions
9. Does your organization’s B2B implementation transmit documents from internally managed systems or through a 3rd party service provider?
If 3rd party service provider, please identify your vendor:
Vendor Name: /Vendor Phone: /
Technical Lead Name: /
Technical Lead Phone: /
Technical Lead email: /
10. What middleware/B2B software is used to support your B2B messages?
Software / Version / Latest Service PackwebMethods / /
Biztalk / /
Tibco / /
Custom Application / /
Other (Please specify below)
/ /
11. Does your middleware/B2B software or service provider have capabilities of exchanging data via the following message formats?
PIDX XMLFlat Files
EDI (Electronic Data Interchange)
Other (Please explain below)
12. Does your middleware/B2B software or your service provider support transaction tracking to ensure reliable delivery of data (handshake ACK/NACK)?
Yes / No13. Does your middleware/B2B software or your service provider support automated retries?
Yes / No14. What type of transport protocol does your middleware/B2B software or service provider support?
HTTP / HTTPSFTP / FTPS
SMTP
Web Services (SOAP/WCF – Web Services)
Other (Please explain below)
15. What ERP/business system environments do you support? (Please check all that are applicable)
Development / ProductionTest/Production Support / Disaster Recovery (DR)
16. Which of these ERP/business system environments are equipped to exchange test/production data? (Please check all that are applicable)
Development / ProductionTest/Production Support / Disaster Recovery (DR)
17. Do you have firewalls as part of your IT security?
Yes / No18. Does your company have Disaster Recovery (DR) and Business Continuity Plans?
Yes / No19. Does your company keep your ERP/business system Test/Development environments code current with your Production environment?
Yes / No20. How frequently do you refresh your ERP/business system Test/Development environments from Production?
WeeklyMonthly
Quarterly
Yearly
None
21. B2B Supply Chain communities have multiple options for security. Please indicate the type of certificates you will require for SSL connectivity (CRC requires 3 level certificate):
Test Environment
Certificate Type / Certificate Authority (CA) / Attach the certificateHTTP/HTTPS/SSL / /
Digital Signing / Validation / /
Encryption/ Decryption / /
Other (Please explain)
/ /
Production Environment
Certificate Type / Certificate Authority (CA) / Attach the certificateHTTP/HTTPS/SSL / /
Digital Signing / Validation / /
Encryption/ Decryption / /
Other (Please Explain)
/ /
Disaster Recovery (DR) Environment
Certificate Type / Certificate Authority (CA) / Attach the certificateHTTP/HTTPS/SSL / /
Digital Signing / Validation / /
Encryption/ Decryption / /
Other (Please Explain)
/ /
22. Are you currently exchanging PIDX XML data with your trading partners?
Yes / NoIf Yes, who may we contact to get sample PIDX XML invoices?
Intellectual property restrictions. CRC proprietary information. / Page 1 of 5