Description
System Integrator Architect - Major Blue Chip - Amsterdam
Architecture scope: Application
The software vendor will together with business representatives configure the system. Hardly the input of the SI architect will be needed for that.
Insofar it is needed to deviate from standard Vanilla Manhattan software, eg adding attributes, adding functionality that need extensions. That decision must be prepared by the architect as so-called 'Key Design Decision'.
A number of KDD's are still pending (about 10 to 20). The preparation of KDD's takes time for investigation of alternative solutions, and aligning Business and IT.
Architecture scope: Integration
For a number of satellite system integrations have to be solutioned, designed, built, tested and deployed. The role of the architect is to coordinate and guard the integrations that are defined in the solution blueprint. For each system, one or more parties have to be involved in making the solution. That takes coordination time.
The main integrations are:
- Peoplesoft Financials
- Accounts Payable,
- Accounts Receivable interfaces Manhattan2PS_financials.
- And suppliers/customers interface PS_Financials2Manhattan.
- Financial Accounting Hub
- General Ledger transaction data Manhattan2FAH
- Conversion from Orion2Manhattan
- All data that is needed for support of property management and financial control processes
- Identity Management,Authentication management systems ITIM and TAM
- user provisioning ITIM2Manhattan
- user authentication: TAM2Manhattan (webseal, in fact).
- Xtendis
- safeguard the continued usage of Xtendis as doc. management system to support Manhattan processes that need documents, interface of reference data (supplier-id's, contract-id's) will be manual.
- Oracle BI
- ETL from Manhattan2OracleBI apps environment
- Reports to be required, designed, built in OracleBI
Architecture scope: Security
- safeguard the proper usage of scrambling tools in test-environments
- safeguard the proper design & build of TIM/TAM adapters.
- safeguard the ability and follow-up
- safeguard the penetration testing of remediated findings
Architecture scope: Infra
- safeguard the proper implementation of DTAP environments.
- infra is already approved and partly implemented.
- coordinate infra-related findings, if they occur in test phase. eg performance issues.
Documents to be finished
- Solution Blueprint. Some last security related aspects to be finished before it can be approved.
- Integration Solution Blueprint
Documents to be reviewed/aproved, during coming delivery phase of the project. Review often also means having meetings, bringing parties together.
- Design documents for interface adapters
- Testplans
- Rollout plan