| Questions | Source | Target | Comments |
|---|---|---|---|
| Application Name | CBU Windchill | HOLSETTURBO | |
| Application ID as per APP Repository | 16026 | 34710 | |
| Application BU | CBU | CBU | |
| Application ARO | Mexico | Mexico | |
| Server Location | Cloud | Cloud | |
| Value Stream | Market & Sell | ||
| Application Vision: | April Release (Tentative) | Oracle Apex 24.1 and Oracle database 23ai | |
| Is there any existing integration? | Yes | NO | |
| Application Owner Name | Laxminarashiman Iyer | Gerardo Castillo Martin del Campo | |
| API Owner | Laxminarashiman Iyer | Gerardo Castillo Martin del Campo | |
| Application Technical Point of Contact | Lawrence (VP586) | Soumendri Das | |
| Application Support Email Group | Corporate IT – Product Lifecycle Mgmt (PLM) – Application Support – Tier 2 | EBU IT – Oracle Region Changes – Memphis Request | |
| Business Requirements / Goal: | Interface item, BOM Structure, CN (Engineering Change Notice) | Integration – Information from Windchill to APEX | |
| Name of the Business Entity: | Interface Engineering Changes From Windchill to APEX | ||
| Resource: | Interface Engineering Changes From Windchill to APEX | ||
| Protocol of API: | HTTPS | HTTPS | |
| Response Payload Type: | JSON | Others, Please Specify | Oracle Autonomous database |
| System Security: | Oauth 2.0 | Oauth 2.0 | |
| Security – Transport | SSL – Windchill Production Support Team will assist in generating | NA | |
| Integration Services – General | |||
| Description | Source | Target | |
| — | — | — | |
| Security – Transport | SSL – Windchill Production Support Team will assist in generating the Windchill Server Certificate | NA | |
| Reuse: | No | NO | |
| Operations exposed by API | Add | Add | |
| Request format required | JSON | Insert into target tables | |
| Response format required | JSON | Insert into target tables | |
| Connection Details (URL) | Middleware URL | TBD | |
| Execution Pattern | Scheduled | Scheduled | |
| Dependencies | No dependencies | NA | |
| Consumer Error Handling | Email PLM Production Support Team in case of any interface failures | Standard Error Handling | |
| Retry/Recovery Mechanism | Standard Retry | MW system will send a notification to apex. Once the issue gets fixed windchill will resend data. | |
| Caching | No | NA | |
| Hypermedia | No | No | |
| Non-Functional Requirements | |||
| Description | Value | Comments | |
| — | — | — | |
| Peak Transaction Volume | <100 (per day/hour/min/sec) | ||
| Average Transaction Volume | <100 (per day/hour/min/sec) | ||
| Maximum Payload Size | 2MB (Request) / <1MB (Response) | ||
| API Timeout Value | 5 Mins | ||
| Reliability/Availability | Weekly Once | ||
| Expected SLA percentage | 99.99 | ||
| Data Classification | “Cummins Confidential” | ||
| Scheduling | Weekly Once | The Change notice process will take 3-4 days to complete in apps database. So Business is only looking for once/week load. | |
| Maintenance Window | Monthly build | ||
| Would you like me to export this data into a structured CSV format or help you draft a summary of these requirements? |
Here is the text extracted from the image of the Excel sheet titled *“Integration Services – Requirements Questionnaire”*: Requirements Response22 Security – Transport How will the transport be secured? If SSL, explain who is generating or maintaining the certificates? Two Way SSL or One Way SSL – Windchill Production Support Team will assist in generating the Windchill Server Certificate.23 Reuse – Does this API execute any other APIs or extend an existing API? No24 Operations exposed by API – What are the various business operations provided for the business entity Add25 Request – Input format required. Agreement will be based on concurrence of both the teams. JSON26 Output format required. Agreement will be based on concurrence of both the teams. JSON27 Connection Details What is the URL, DB for the target Connection, User? Refer Sample Middleware URL TBD28 Execution Pattern How is this API triggered? Scheduled29 Dependencies No dependencies30 Use this to document system constraints and error handling NA31 Consumer Error Handling What is the error handling for the consumer as it retries failures (PLM_Infras_Support@cummins.com). This can be system errors like Service Down, Time Out, Connection Refused or Internal errors like Process Failure, Data not found. Email PLM Production Support Team in case of any interface failures (PLM_Infras_Support@cummins.com). Standard Error handling32 Retry/Recovery Mechanism – Describe the retry mechanism if there is a need to recover and/or retry the failed transaction Standard Retry33 Caching – Will this API use caching? What type of Cache? No34 Hypermedia Does this API implement Hypermedia? No35 Any other specific requirement, Please describe. No*Section heading below the table*:*Non – Functional Requirements*_Tabs visible in the Excel workbook_: *Requirements*, *Data mapping*, *Sample Only*.
Here is the text extracted from the image of the Excel sheet titled *“Integration Services – Requirements Questionnaire – Non-Functional Requirements”*:Description Value CommentsPeak Transaction Volume Provides the highest expected transactions per day <100 Provide the highest expected transactions per hour <100 Provide the highest expected transactions per msec (shortest interval) <100 Peak concurrent requests at any given time/day Average Transaction Volume 50 Provide the average expected transactions per day <100 Provide the average expected transactions per hour <100 Provide the average expected transactions per msec (shortest interval) <100 Maximum Payload Size Payload size of individual transaction – Request 2MB Payload size of individual transaction – Response <1MB API Timeout Value How long should the consumer wait before they consider it a timeout? 5 Mins How long should the provider wait before they consider it a timeout? 5 Mins Reliability / SLA commitments Expected SLA percentage 99.99 Data Calculation Describe any data restrictions assigned to the logs N/A Describe system constraints on what must be, or cannot be, logged No dependencies Scheduling Will be scheduled or on demand? If Yes, provide the schedule timing Weekly Once Is the process deployable in support fix or scheduled maintenance deployments? Monthly Build *Note at the bottom (yellow box):*“The Change notice process will take 3-4 days to complete in apex database. So business is only looking for sync/once a week load.”Do you need the data formatted differently or want specific analysis of any requirement?