closely with the CalSTRS' project management team and a third-party vendor to ensure that the third-
party vendor has done their due diligence in managing the project and producing project deliverables
and artifacts that meet CalSTRS' quality expectations in a timely manner.
The Contractor defines, analyzes and assists with the implementation of the architecture of a
computerized system (i.e., a system composed of software and hardware) in order to fulfill business and
technical requirements.
All deliverables and services will be provided in a diligent, professional, competent, and timely manner.
B. Tasks/Deliverables
1. The Contractor's tasks may include, but are not limited to, the following:
Evaluate Technical Dependencies in Project Deliverables and Documents
a. Assist in the identification and resolution of dependencies and/or discrepancies, which may
result in downstream business/technical impacts or implications, in various project deliverables
and documents.
b. Collaborate closely with the CalSTRS project management team in estimating and fine tuning
the utilization needs of technical resources.
c. Monitor and evaluate the quality of technical deliverables and timely progress of technical
activities.
d. Examples of anticipated deliverables include, but are not limited to, all the following:
• Review and recommend any potential revisions to deliverables/documents to include any
technical dependencies/provisions;
• Review and recommend any potential revisions to applicable project deliverables/documents
to incorporate all necessary technical activities and schedules; and3. 4. 5. 2. a. c. a. b. b. c. Request for Offer 5681700908
System Architect
Page 21 of 22
• Review and recommend any potential revisions to applicable project deliverables/document to
include risks, issues, and scope that may have technology/technical dependencies and
implications.
Assess Architecturally Significant Dependencies or Implications
Meet with various technical architects and technical subject matter experts (SMEs) (e.g., system
integrator's architect, CalSTRS architect, etc.) to understand and evaluate requirements and
various aspects of technical architectures of both new and existing solutions.
b. Develop technical impact analysis and/or research papers to support CalSTRS managements'
decision-making process.
Examples of anticipated deliverables include, but are not limited to, all the following:
• Impact Analysis of 'to-be' Business Architecture
• Impact Analysis of 'to-be' Technical Architecture
• Alternative Analysis of Architectural Designs & Options
• Technical and/or Implementation Dependencies
Analyze and Recommend Architecture Options
Collaborate with various technical architects and technical SMEs (e.g., system integrator's architect,
CalSTRS architect, etc.) to develop prospective bridging architecture options where the existing
solutions can continue to fulfill business needs, partially or wholly, in order to accommodate the
phased deployments of functionalities of the new solution.
Examples of anticipated deliverables include, but are not limited to, all the following:
• One or more architectural options with trade-offs
• Benefit(s), cost(s), risk(s), and schedule impact analyses for each architecture option
Guide the Technical Implementation and Delivery from a System Architecture Perspective
a. Guide and identify activities from a system architecture perspective, which have technical
impacts/dependencies, among CalSTRS' SMEs, vendors, business partners and stakeholders to
ensure on-time and with quality completion of solution development/implementation per design
specification and project requirements/objectives.
Regularly log, track, and update technical risks and issues.
Examples of anticipated activities include but not limited to, all the following:
• Client, analyze, document and communicate technical risks and architectural impacts;
• Raise and/or escalate technical issues and concerns in a timely manner;
• Enforce proper SDLC adherence;
• Timely communicate and resolve technical issues and risks; and
• Written weekly and/or monthly reports detailing various technical findings that may impact
schedules, resources, and activities, etc.