Dear Partner,
Hope you are doing well.
Please find the PM based in NY. Kindly send me profile of candidates for
this role ASAP.
*Location: **Endicott, NY*
*Visa: Green card ,Citizens*
*Rate:55 to 65 if higher as well we can try.*
Program Manager with software experience with PMP
1- Schedule:
Identify the detailed schedule for each Software (SW) build, with an
associated functional content definition that is consistent with Bombardier
and BAe’s SW build definition
Confirm detailed schedule for Hardware (HW) development and delivery.
Schedules should also provide some type of PERT chart
Verify processes in place to track the current schedule against a baseline
and identify/justify changes to the schedule
Confirm that the schedule takes into consideration the CIRD delivery dates
and a realistic allowance for the CIRD reviews that are required internal
to RCI and with BA/PH
Insure a phase gate process in alignment with Gx schedules is in place and
being enforced.
Identify if an earned value system is employed
Check cycle time for defining requirements, design, coding and testing;
comparison with cycle time of other suppliers for similar equipment and
opportunities to improve schedule
Confirm adequacy in the number of test facilities for SW and FW
verification and qualification
2- Resources:
Identify the level of resources planned and evolution over time of
resources actually allocated to the project.
Identify resource skill set needs needed, and adequacy of skill set of
personnel assigned to the project based on rework, schedule deliverables
Insure processes in place to detect inadequate level of resources or skill
set and make the necessary corrections
3- Change control:
Check the configuration management plan and change control process for HW,
SW and Firmware (FW)
Identify the cycle time for making minor and more important SW changes
during integration testing and during flight test
Check for a Problem Reporting (PR) processes/system that integrates with
the PH and BA problem reporting, for PRs raised during the BAe , box level
testing, SIL integration and integration at BA on the eSIM/ ISTCR and to
provide visibility on BAE’s PRs (BAE compliance to the PH FCS PR
process). Need to confirm a closed loop problem reporting system in place.
Confirm a SW development plan that takes into consideration the need for
quick correction of problems that arise during testing; two parallel SW
development teams would likely be required such that issues that come up
during integration testing of a build can be corrected using
“patches” to allow testing to progress, without stopping or affecting the
development of the next build (with the “patches” eventually being
re-integrated into the next main build)
4- Test planning:
Confirm planning of the AFCU testing both by BAE and at PH and BA, and how
the investigating of problems will occur (ownership, roles/responsibilities)
Verify BAE plan to test the CIRD requirements .
Check for support that will be provided by BAE to PH and BA for
integration/testing of the AFCU on the PH SIL and BA CIASTA
Identify on-target SW/FW testing versus on simulator
Check risk reduction/mitigation testing for areas without a high maturity
level
Note: as a specific technical item, PH is concerned about the AFCU’s
limited capabilities for internal data retrieval during testing, which
could impact the duration of tests and problem investigation
5- Data:
Agreement on data items and delivery status versus agreed to baseline
confirmed
6- Software and SOI:
Confirm mutual understanding between BA and BAE of SOF expectations for SW
Verify checklists for the SOI audits (DO-178 and DO-254), for the
different stages (understanding of expectations) – pre-audits by BA to be
considered before involvement of the certification authorities
7- Compliance:
Confirm checklists for audit per ARP 4754, DO178 and DO254.
8- Processes:
QA process and QA audits are scheduled; infrastructure in place
Development and verification processes/plans is proceeding
Verify definition of the interfaces between the FBW and the AFCU
9- Regression
Check for methodology to prevent need for FBW function system level
re-verification when changes are made
Verify design robustness, design meets requirements, sufficient growth and
margin
Verify requirements capture of BAE CIRD, Bombardier CLAWS, other
Bombardier requirements and RC derived requirements
Best Regards
*Ravi Nigam*
978-558-4666 EXT 101
*TekNavigators*
8875 Hidden River Parkway
Suite 300
Tampa, FL 33637
DISCLAIMER: This message and any attachments are solely for the use of the
individual or entity to which it is addressed and may contain information
that is privileged or confidential. If you are not the intended recipient,
any disclosure, use or distribution of the information contained herein is
prohibited. If you have received this communication in error, please notify
the sender by reply e-mail and immediately delete this message and any
attachments. You may reply and send an email with "Remove" in the subject
line in order to discontinue communication.
--
You received this message because you are subscribed to the Google Groups
"SAP-UK" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sap-uk+unsubscr...@googlegroups.com.
To post to this group, send email to sap-uk@googlegroups.com.
Visit this group at http://groups.google.com/group/sap-uk.
For more options, visit https://groups.google.com/d/optout.
