Project Detail

Description

Much of this is pasted from the attached files. I have no idea on number of hours required to complete the first phase of the project.

Program Management System


1. Objective
To create a Web based system to manage different customer programs (example: Chrysler JC49, Mercedes 166.) and manage Engineering Change Request (ECR) / Engineering Change Order (ECO) and Parts / Bill of Material (BOM). The process and templates used on all programs is the same and should be driven off Parts /Bills of Material.

Security settings to access/modify information should be set up by
• System Administrator
• Program Manager
• Engineer
• Finance
• Senior Management
• Commercial
• Supplier

2. Scope of Services

a. Assist in planning and implementation of the Web based system
b. Recommend steps required to successfully install the new system
c. Establish system requirement specifications for the above said system
d. Develop and implement the application based on the above required specification
e. Phase A and B to be implemented by December 31st, 2009
f. Phase B and Phase C specifications are being created and will be available by November 6th, 2009


3. Training and Testing

a. Perform Testing at various stages of development
b. Perform Functional and Technical Testing by quality analyst
c. Work with me and my staff during installation and implementation to help gain a general understanding of the system.
d. Train in the areas of ECR – ECO management and Parts / BOM management
e. Upon completion, system test to assure that it is functioning as intended and producing accurate results.
f. Proper documentation and troubleshooting procedures.


4. My Responsibilities
This project demands significant involvement by me and my staff. Ultimate success is highly dependent on their effort. To help achieve a smooth and successful implementation, it will be my responsibility to perform the following:
1. Provide accurate and precise system requirements.
2. Provide both functional and non functional requirements
3. Assist in performing UAT (User Acceptance Test)
4. Regular review on progress and feedback


5. Your Responsibilities
(A) Bill of Material (BOM)
Required Functionalities

• Access to the system will be managed through secure ID / Password screen
• Password strength rules will be enforced
• An online form for new users to be added. Only non-System Administrator and Program Manager roles will be allowed at creation. Program Manager role must be granted by System Administrator.
• System Administrators will control roles for all users
• Create New Part function – System Administrator and Program Manager must be able to create new parts
• Core fields must be on all parts
• Manage Part Fields function - System Administrator and Program Manager must be able to add / delete / modify fields
• There is no requirement for tracking the history of changes to Parts or BOMs.
• Manage Part Fields function - Field rules must be enforced as defined
• Manage Part Fields function - System Administrator and Program Manager must be able to edit the field names for his specific BOM; this can be done through field alias. All field aliases will default to standard names and be editable by the System Administrator and Program Manager roles. Field aliases will be shown in all views.
• Manage Views function - System Administrator and Program Manager can choose order of fields
• BOMs must be multi-level as required up to a maximum of 6 levels.
• Multi – Level BOM screen - System Administrator and Program Manager can add, delete and move parts within the BOM
• System Administrator and Program Manager will be defined as part administrators with full access to their BOMs or user which has read only access to the BOM
• Part Administrators will have an Excel type web page that will allow for multiple / quick updates of all fields
• Parts Lists will have sortable column headings and link to description of field
• Parts lists and BOMs must be able to import to the system from Excel and export to Excel format
• Part Administrators and Users must be able to create their own reports / screens to choose the columns visible in the screen or export to Excel
• Master Data to be maintained by System Administrator role
• Master Data requires ability to add / edit and delete fields by System Administrator role
• Search function / report creation (Save, modify, delete) with filters – Implementation will be based on success and performance of above criteria

All above functionalities should be associated with the appropriate security group and appropriate notification process (i.e. Need Authentication and Authorization need to perform the above)


(B) ECR/ECO – Implementation will be based on success and performance of item (A)
Required Functionalities

ECR Creation
• Requests for changes can be submitted by customers, suppliers and engineers. ECR will have a standard template for all kinds of request and will be linked to Parts

ECR Review
• The Product Engineer reviews the change information and completes an ECR form which includes overlays. This information is saved in an Engineering change log

ECR Report and Search
• Different ECR reporting capability on different criteria
• Search capability on different search criteria
• Import and export capability

ECR Workflow
• Initiated  Evaluate  Review / Quote  Disposition  Plan ECO  Completed.

ECO Creation
• If change is approved and open, product engineer creates an ECO.
• This information is saved in an Engineering change log.
• Link ECO to the corresponding ECR

ECO Workflow
• Initiated  Kicked Off  Implemented  Completed

ECO Report and Search
• Different ECO reporting capability on different criteria
• Search capability on different search criteria
• Import and export capability

ECR and ECO will have the necessary security functionality associated with it. It will follow the workflow and have appropriate notification sent to the corresponding groups.

(C) Platform Financial Tracking
Required Functionalities

• Requirements to be determined at a later date based on success and performance of items (A) and (B).


6. Software Requirements

Development Environment

• This project should be developed using Microsoft .Net
• Database MS-SQL server or MySQL Server

Microsoft Development environment

• Visual Studio .Net
• IIS
• Windows XP and Windows 2003
• Internet Explorer 7.0 / Mozilla Firefox 3.5
• MS Office

System Access / Security

Access to the system will be managed through secure login screen with User ID and Password
Password strength rules will be enforced
An online form for new users to be added. Program Manager role must be granted by System Administrator.
Forgotten ID / password functionality required with password reset with automated e-mails
User able to manage their account information
System Administrators will control roles for all users
Security settings to access/modify information should be set up by
System Administrator – Full access
Program Manager – Full access to Parts / Bill of Material
Engineer – Read access to Parts / Bill of Material
Finance – Read access to Parts / Bill of Material
Senior Management – Read access to Parts / Bill of Material
Commercial – Read access to Parts / Bill of Material
Supplier – Read access to Parts / Bill of Material

Initial Screen
Once logged in the user will be taken to a screen called My Parts / Bill of Material

If user has created their own Bill of Material Part – that Part will be their start up page
System Administrator – No defined BOM for System Administrator
Program Manager – Part Type Program BOM – Where user ID is listed for the Program. If more than one than only a list of those parts. If only one than a multi-level view of that BOM.
Engineer – Part Type User BOM – Where user ID is listed as part owner. A multi-level view of that BOM.
Financial – Part Type User BOM – Where user ID is listed as part owner. A multi-level view of that BOM.
Senior Management – Part Type User BOM – Where user ID is listed as part owner. A multi-level view of that BOM.
Commercial – Part Type User BOM – Where user ID is listed as part owner. A multi-level view of that BOM.
Supplier – Part Type User BOM – Where user ID is listed as part owner. A multi-level view of that BOM.

If no BOM Part has been created specifically for the user then a Parts list will be their start up page
System Administrator – Full access
Program Manager – Full access to Parts / Bill of Material
Engineer – A list of all parts where the user ID is listed as Tool Engineer or Quality Engineer
Financial – A list of all parts where the user ID is listed for the Program
Senior Management – No defined list of parts for viewing
Commercial – A list of all parts where the user ID is listed for the Program
Supplier – A list of all parts where the tool source or fixture source is the logged in supplier

This screen will be a table showing either the BOM or the Parts list
Screen will be table format similar to Excel
An Export to Excel button will allow for exporting current view to Excel based file
A Print button to allow easy printing access of table
System Administrator and Program Manager roles will have the ability to define what fields are shown and save views/formats for use by all roles or just Program Manager role
All users will have a drop down list to pick from the list of formats / views defined by the System Administrator and Program Manager roles
User will have the ability to select how many parts / line items are visible per screen (i.e. 10, 20, 50, all)
System Administrator and Program Manager roles will have the ability to edit all information on this screen
System Administrator and Program Manager roles will have ability to Create New Part from here


Part Information
All parts listed on My Parts / BOM page will be hyperlinked to another screen showing all the part information in the database as default
Menu options / hyperlinks for the part will include
Part Information – All fields defined for specific part are shown.
Edit capabilities for System Administrator and Program Manager roles
ECRs – To be used during Phase 2
ECOs – To be used during Phase 2
Multi-Level BOM – A multi-level BOM for that specific part
System Administrator and Program Manager roles will have the ability to add and delete Parts from BOM here.
Drop down list of views will be shown for all users
Export to Excel button for all users
Print view button for all users
Where Used – A parts list showing all the parts that are parent to the specific part.
Export to Excel button for all users
Print view button for all users
Files – A place for files to be uploaded to the system for use by all users. Only Program Manager role can add / edit / delete files. All other users will have read access to these files


Additional files submitted:
Specifications.zip