Engineering Change Proposal (ECP) Origination Instructions .
Work Practice InstructionsWPI0004October 29, 2004Engineering Change Proposal (ECP)Origination Instructions and Workflowfor ECPs Costing 100,000 – 1,000,000Prepared by:WSR-88D Radar Operations Center3200 Marshall Ave., Suite 100Norman, OK 73072Digitally signed by Ed BerkowitzAPPROVED FORDN: CN Ed Berkowitz, C US,EdBerkowitzO ROC, OU Program BranchUSE AS PRODUCTDate: 2004.11.29 16:07:41 -06'00'BASELINE BY: DATE:Edward L. BerkowitzProgram Branch ChiefWSR-88D Radar Operations Center1
Work Practice InstructionsWPI0004October 29, 2004Table of ContentsEngineering Change Proposal (ECP) Executive Summary . 5Acronyms . 6Launching the ECP Process. 7Creating the ECP Template. 7ECP Workflow . 11ECPs Over 100,000 (Preliminary) . 111. Pending Status. 11Populating the Preliminary ECP. 12A. Cover Page . 12B. Detail Tab. 13C. ECP Page 3. 15D. Affected Items Tab . 15E. Signoff Tab. 15F.Attachments Tab . 15G. History Tab:. 192. Routing for Project Team Review . 193. Project Team Review. 224. ECPs Rejected During Project Team Review . 265. Branch Chief Review . 296. ECPs Rejected During Branch Chief Review . 337. Submitted ECPs . 358. ECPs Rejected at Submitted Status . 369. ROC Review . 3710. TRC . 4611. CM Hold – Mediate - . 4712. Agency Review . 4813. ECPs Rejected at Agency Review Status . 512
Work Practice InstructionsWPI0004October 29, 200414. CCB . 5315. Moved to Formal. 54ECP Workflow – ECPs Over 100,000 (Formal). 551. Pending. 55Populating the Formal ECP. 56A. Cover Page . 56B. Detail Tab. 57C. ECP Page 3. 59D. Affected Items Tab . 62E. Signoff Tab. 62F.Attachments Tab . 62G. History Tab:. 652. Routing for Project Team Review . 653. Project Team Review. 694. ECPs Rejected During Project Team Review . 725. Branch Chief Review . 756. ECPs Rejected During Branch Chief Review . 797. Submitted ECPs . 818. ECPs Rejected at Submitted Status . 829. ROC Review . 8410. TRC . 9211. CM Hold – Mediate - . 9212. Agency Review . 9413. ECPs Rejected at Agency Review Status . 9714. CCB . 9915. Released . 10016. Deployed – Not Complete –. 1013
Work Practice InstructionsWPI0004October 29, 200417. Deployed. 10218. Revision or Change to an ECP . 102Appendix A - Team Member Hours in TMS. 104Appendix B – CI/CPCI/Tech Manual Tables. 107Appendix C - ECP ATTACHMENT A. 110Appendix D – ECP ATTACHMENT B . 111Appendix E - ECP ATTACHMENT C. 147Appendix F - ECP ATTACHMENT M . 153Appendix G - ECP ATTACHMENT S . 157Appendix H – ECP Revision and Change Requirements . 160Appendix I - ECP Workflow – ECPs Over 100K (Preliminary) . 161Appendix J - ECP Workflow – ECPs Over 100K (Formal). 1624
Work Practice InstructionsWPI0004October 29, 2004Engineering Change Proposal (ECP) Executive SummaryEngineering Change Proposals are the “umbrella” under which all components (ECOs, ACOs,DCRs, Modification Notes, etc.) of a system modification are organized. An approved ECP isrequired prior to incorporation of the various components into the WSR-88D baseline. Thisdocument outlines the procedures to produce, submit, review and adjudicate ECPs with a cost of 100,000 to 1,000,000.5
Work Practice InstructionsWPI0004October 29, 2004AcronymsACOArtwork Change OrderCCBConfiguration Control BoardCCRConfiguration Change RequestCMConfiguration ManagementDCRDocument Change RecordECOEngineering Change OrderECPEngineering Change ProposalROCRadar Operations CenterTMSTime Management SystemTRCTechnical Review CommitteeWPIWork Practice Instructions6
Work Practice InstructionsWPI0004October 29, 2004Launching the ECP ProcessTo activate a project, a request is made at a TRC meeting to remove a CCR(s) from theSystem Project Pool, which will then become an ECP. The TRC will assign the project leadand team members at this time.Creating the ECP TemplateThe CM Analyst will create the ECP template and populate the following fields:On the Cover Page –NumberChange TypeClassChange AdministratorDate OriginatedPriorityOriginatorTitleProduct LineStatusWorkflow7
Work Practice InstructionsWPI0004October 29, 2004On the Detail Tab –TypeEngineering AreaCognizant EngineerTeam MembersECP NumberDriving CCRsUpon completing the fields listed above, the CM Analyst will advance the CCR to CMAllocation status. At this status the CM Analyst assigns team members and the branchchief as approvers on the Signoff tab.The CM Analyst will advance the ECP to Pending status and send an email notificationto the originator (project lead) that the ECP has been produced.8
Work Practice InstructionsWPI0004October 29, 2004The ECP is now available to be worked by the project lead. The project lead can viewthe ECP clicking on the Agile document link (P7071.agm) in the email notification.This will launch Agile.The Welcome to Agile CM login screen will be displayed. Complete the Username andPassword information and click OK.9
Work Practice InstructionsWPI0004October 29, 2004The ECP (7071) will be displayed.10
Work Practice InstructionsWPI0004October 29, 2004ECP WorkflowECPs Over 100,000 (Preliminary)For projects costing 100,000 - 1,000,000, it is understood that these are large and oftencomplicated projects. Therefore, the ECP process allows for approval of these large projects totake place in a two part format – as Preliminary and Formal ECPs. Preliminary ECPs are todescribe the format of the project – a framework of the problem description, proposed solutionand implementation of the project. The Preliminary ECP should be a strong, well developed“skeleton” of the plan, with the Formal ECP filling in all the details and “fleshing out” the project.1. Pending StatusThe project lead will receive the Preliminary ECP in Pending status. All preparatorywork for the ECP will be performed while the ECP is in this status.The project lead should begin his ECP process with a team meeting. (The project teammembers will have been listed on the Detail tab of the ECP.) During Pending status, theproject lead must conduct at least one team meeting.During the team meeting, the team members should provide much of the informationrequired to populate the ECP.11
Work Practice InstructionsWPI0004October 29, 2004Populating the Preliminary ECPA. Cover PageComplete the following blocks on the Cover Page of the ECP:Description of Change:This field will contain the title of the ECP (entered by the CM Analyst).Enter a blank line after the title and then enter a description of theproposed change. The description should identify the affected portion ofthe system and the problem in question.Note: Many of the blocks on the Agile ECP form have limited characterlengths, thus limiting the amount of data that can be entered. Therefore, anattachment must be used to include all necessary information in the ECP.Attachment A is used for this purpose. The template for Attachment Acan be found on the Attachments tab of this WPI and an example of thetemplate has been included in Appendix C of this document.Reason For Change:Enter a proposed solution in sufficient detail to adequately describe whatthe project is to accomplish.12
Work Practice InstructionsWPI0004October 29, 2004B. Detail TabComplete the following blocks on the Detail Tab:Justification Code:Select one of the following from the Justification Code drop-down list:Interface – To eliminate incompatibility between CIs.Compatibility – Proposed change is necessary to make the system/item work.Deficiency – Eliminate a deficiency (use if more descriptive code doesn’t apply.)Operational or Logistics Support – Make a significant change in operationalcapability or logistic support. (Commonly known as an improvement change.)Production Stoppage – To prevent slippage in an approved production schedule.Cost Reduction – To provide net total like cycle cost savings to the Government.Safety – To correct a hazardous condition.Value Engineering – For a net life cycle cost reduction.CI/CPCI Number/Title:Select from the CI/CPCI Number/Title drop-down list all knownapplicable CIs (CPCIs for SW Build Release ECPs) affected by thisproposed change. All CIs and CPCIs are listed in Appendix B of thisdocument.Technical Manuals:Select from the Technical Manual drop-down list all known TechnicalManuals affected by the proposed change. All Technical Manuals arelisted in Appendix B of this WPI.13
Work Practice InstructionsWPI0004October 29, 2004Estimated Hard Costs:Calculate estimated hard costs (procurements, travel, printing, field labor,shipping, media, credit card purchases, etc.) for the project.Effectivity:The project lead is not expected to know the full effectivity at this point in alarge project. However, a rough indication of effectivity, such as “Willaffect all FAA sites” or “Anticipate fleet-wide installation” should beincluded on the Attachments tab as Attachment E.Soft Costs (ROC Hours):Obtain from each team member an estimated number of staff hours he orshe will spend on the project. Enter the team’s total hours in the SoftCosts block on the Detail tab of the ECP.Deployment Date:At this point, the project lead is not expected to know the deployment datefor the project. However, a brief breakdown of a proposed developmentschedule should be provided and included on the Attachments tab asAttachment S.Please Note: The Suspense Date and Type of Review blocks will becompleted by the CM Analyst when the ECP is routed for review.However, the Suspense Date and Type of Review blocks may be completedby the project lead to reflect the 7-day project team review period, if he sochooses.14
Work Practice InstructionsWPI0004October 29, 2004C. ECP Page 3At this point it is not anticipated that the project lead will have muchinformation for Page 3 of the ECP. However, if the project lead has anyinformation for the items on this page, it should be included.D. Affected Items TabNo items are to be added to the Affected Items tab!If ECOs have been produced, they should be listed on the Detail tab in theAssociated CCRs/ECOs/PCRs block of the ECP. The ECO process isexplained in Agile Work Practice Instructions WPI0010.E. Signoff TabThe Signoff tab is populated by the CM Analyst and the Agile workflow.F. Attachments TabECP attachments will vary from ECP to ECP; however, the Attachments tab of aPreliminary ECP is to contain all documentation needed to gain approval forcontinued development of the proposed change. Preliminary ECPs must contain afully developed business case, basic development schedule, and rough indicationof effectivity attachments. Attachment B is used for the business case. Instructionsfor producing a business case can be found in Appendix D of this document. For15
Work Practice InstructionsWPI0004October 29, 2004reference, an example business case attachment has also been included in AppendixD.To add attachments, select the Attachments tab, place the cursor in the whitespace on the tab and click the mouse button. A thin, blue boarder will bedisplayed ensuring the tab is activated.16
Work Practice InstructionsWPI0004October 29, 2004Click the Add Attachment buttonThe add dialog box will appear.located on the Attachment tab’s toolbar.Locate the file to be attached and click on the file name. This will highlight thename of the file and enter it in the File name block.17
Work Practice InstructionsWPI0004October 29, 2004Using the following naming convention, enter a description of the file in theDescription block on the Add dialog box:ECP Pxxxx Attachment A – Additional InformationECP Pxxxx Attachment B – Business CaseECP Pxxxx Attachment E – Rough Indication of EffectivityECP Pxxxx Attachment S – Basic Development Schedule(Where Pxxxx is the ECP number, e.g., ECP P7071 Attachment A – AdditionalInformation.)Use this naming convention on any additional attachments, e.g., ECP P7071Attachment T – Team Meeting Minutes; ECP P7071 Attachment I – WarningInstructions; ECP P7071 Attachment O – Obstruction Light Diagram; etc.18
Work Practice InstructionsWPI0004October 29, 2004Click the Add button on the Add dialog box. The file will be added and Agilewill display a prompt offering the option to delete the local copy of the file thatwas added to the Attachments tab.To retain the local file, click No. To delete the file, click Yes.G. History Tab:The History tab is automatically populated by Agile and is a permanent recordof all Agile activity performed on the ECP.2. Routing for Project Team Reviewa.Once the ECP is complete, the originator will route the ECP for project teamreview. The team members will have been assigned by the TRC and added to theECP by the CM Analyst when the ECP was created.b.Click the Next Status buttonc.Agile will display a prompt offering to perform a release audit. Click Yes.on the Agile toolbar.19
Work Practice InstructionsWPI0004October 29, 2004d.The Change Status to Project Team Review dialog box will be displayed. Agilewill automatically enter the name of the project lead in the Notify box. Theapprovers’ (team members) names will not be displayed in the Approvers boxbecause they were previously assigned on the Signoff tab by the CM Analyst whenthe ECP was in CM Allocation status.e.In the Comments box, the project lead will enter instructions for the team membersreviewing the ECP. These directions must include a suspense date by which timethe reviewer must have approved/disapproved the ECP. The suspense date will beno later than 7 days from the date and time the ECP is routed for review.It may be helpful to also provide instructions concerning how to approve/disapprove.For example:This ECP is routed for project team review and approval. Please review ECPP7071 and provide approval/disapproval no later than 10:00am Tuesday, June 8,2004. The Agile workflow requires a decision from each team member.Please Note: To approve or disapprove the ECP, select the appropriatedecision button located on the Agile toolbar. The approve and disapprove20
Work Practice InstructionsWPI0004October 29, 2004buttons are located to the left of the comment button, which is the last buttonon the Agile toolbar.f.Click the Route button located on the bottom of the Change Status to ProjectTeam Review dialog box.g.A screen will appear describing any required information that is missing from theECP. Click OK and correct all errors found during the audit.h.After correcting errors, click the Next Status buttonon the Agile toolbar. Agilewill once again display the prompt offering to perform a release audit. Click Yes.i.The Change Status to Project Team Review dialog box will be displayed onceagain. The name of the project lead will be in the Notify box and the instructionspreviously entered in the Comments box will also be displayed.j.Click the Route button located on the bottom of the Change Status to ProjectTeam Review dialog box.k.The status of the ECP will change to Project Team Review.21
Work Practice InstructionsWPI0004October 29, 2004l.Agile will send each team member an email notification of the ECP requiring hisreview and approval. Please note that Agile “canned” comments are alwayslocated in the first line of the email message and cannot be edited by the ROC.Any additional information/instructions from the sender will be located belowin the Comments section of the email.3. Project Team Reviewa.When the ECP is routed for review, the project team members will have 7 days toprovide approval or disapproval of the ECP. Agile automatically monitors thisprocess, which requires a response from all team members. Any team memberswho have not provided a decision within 5 days will receive an email reminderfrom Agile.Please Note: If a decision is not received by the end of the 7-day review cycle, Agileescalates the ECP to the team member’s team lead for action.22
Work Practice InstructionsWPI0004October 29, 2004b.To review the ECP, click on the Agile document link (P7071.agm) in the emailnotification. This will launch Agile.c.The Welcome to Agile CM login screen will be displayed. Complete theUsername and Password information and click OK.d.The ECP to be reviewed (ECP P7071) will be displayed.e.The team members are to review the ECP to ensure that it’s complete - allinformation is correct and it contains all required attachments. To approve thelocatedECP for submission, the team member will click the Approve buttonon the Agile toolbar.23
Work Practice InstructionsWPI0004October 29, 2004f.The Approve ECP Pxxxx (ECP P7071) dialog box will be displayed. Enter anyreview comments in the Signoff Comments block, then enter the password in thePassword block and click Approve.g.The project lead will receive an email notification when all team members haveapproved the ECP. The email will state, “ECP P7071 has been moved fromPROJECT TEAM REVIEW to BRANCH CHIEF REVIEW for the ECPOVER 100K (PRELIM) workflow for approval. No action is required. This isfor your information only.” This is a canned statement from Agile and cannot bealtered by the ROC.24
Work Practice InstructionsWPI0004October 29, 2004h.Once all team members have provided their approvals, the ECP will automaticallymove forward to Branch Chief Review status. The branch chief review process isdescribed in ECPs Over 100,000 (Preliminary) Section 5 of this documenti.If a team member does not agree the ECP is ready for submission, the ECP can bedisapproved. Instructions for disapproval and the process for handling rejectedECPs are described in ECPs Over 100,000 (Preliminary) Section 4 of thisdocument.25
Work Practice InstructionsWPI0004October 29, 20044. ECPs Rejected During Project Team Reviewa.If a team member does not agree that the ECP is ready for submission, he mayon the Agile toolbar.reject the ECP by clicking the Reject buttonb.The Reject ECP Pxxxx (ECP P7071) dialog box will appear. In the SignoffComments block, enter the reason for disapproval and list all items in need ofattention, e.g., attachments are missing, information is incorrect or incomplete, etc.c.When all comments have been entered, type the password in the Password blockand click the Reject button.d.If any team members disapprove the ECP, it will automatically return to Pendingstatus.e.The project lead will receive email notification from Agile stating the ECP hasbeen returned to Pending status.f.The project lead should make all necessary adjustments to the ECP. If there isdisagreement concerning the suggested changes, a team meeting should be held toreconcile the problems.g.Once the ECP has been reconciled and the changes have been made, the projectlead will return the ECP to the review cycle. To accomplish this, perform ECPsOver 100,000 (Preliminary) Routing for Project Team Review steps 2bthrough 2k of this WPI.26
Work Practice InstructionsWPI0004October 29, 2004Please Note: When the ECP was returned to Pending status, Agile automatically repopulated the Signoff tab, as shown in the graphic below. Therefore, all team membersmust once again perform the ECPs Over 100,000 (Preliminary) Project Team Reviewsteps 3a through 3h of this WPI and provide a review decision.h.When all team members provide their approvals, the ECP will automatically moveforward to Branch Chief Review status.27
Work Practice InstructionsWPI0004October 29, 2004i.Agile will send the project lead an email notification that the status of the ECP haschanged to Branch Chief Review status.28
Work Practice InstructionsWPI0004October 29, 20045. Branch Chief Reviewa.b.When the ECP enters Branch Chief Review status, Agile will send the branch chiefan email notification of the ECP requiring his review and approval.When the branch chief receives the ECP for review, he will have 7 days to provideapproval or disapproval of the ECP. Agile automatically monitors this process. Ifthe branch chief has not provided a decision within 5 days, he will receive anemail reminder from Agile.Please Note: If a decision is not received by the end of the 7-day review cycle, Agileescalates the ECP to the CM Team Lead for action.29
Work Practice InstructionsWPI0004October 29, 2004c.To review the ECP, click on the Agile document link (P7071.agm) in the emailnotification. This will launch Agile.d.The Welcome to Agile CM login screen will be displayed. Complete theUsername and Password information and click OK.e.The ECP to be reviewed (ECP P7071) will be displayed.f.The branch chief is to review the ECP to ensure that it’s complete - all informationis correct and it contains all required attachments. To approve the ECP forsubmission, the branch chief will click the Approve buttonlocated on theAgile toolbar.30
Work Practice InstructionsWPI0004October 29, 2004g.The Approve ECP Pxxxx (ECP P7071) dialog box will be displayed. Enter anyreview comments in the Signoff Comments block, then enter the password in thePassword block and click Approve.h.The project lead will receive an email notification when the branch chief approvesthe ECP. The email will state, “ECP P7071 has been moved from BRANCHCHIEF REVIEW to SUBMITTED for the ECP OVER 100K (PRELIM)workflow for approval. No action is required. This is for your informationonly.” This is a canned statement from Agile and one the ROC cannot alter.i.If the branch chief does not agree the ECP is ready for submission, the ECP can bedisapproved. Instructions for disapproval and the process for handling rejectedECPs are described in ECPs Over 100,000 (Preliminary) Section 6 of thisdocument.31
Work Practice InstructionsWPI0004October 29, 2004j.Once the branch chief has provided his approval, the ECP will automatically moveforward to Submitted status. The process for Submitted ECPs is described inECPs Over 100,000 (Preliminary) Section 7 of this WPI.32
Work Practice InstructionsWPI0004October 29, 20046. ECPs Rejected During Branch Chief Reviewa.If the branch chief does not find the ECP ready for submission, he may reject theECP by clicking the Reject buttonon the Agile toolbar.b.The Reject ECP Pxxxx (ECP P7071) dialog box will appear. Enter the reasonfor disapproval in the Signoff Comments block and list all items in need ofattention, e.g., attachments are missing, information is incorrect or incomplete, etc.c.When all comments have been entered, type the password in the Password blockand click the Reject button.33
Work Practice InstructionsWPI0004October 29, 2004d.The ECP will automatically return to Pending status.e.The project lead will receive an email notification from Agile stating the ECP hasbeen returned to Pending status.f.The project lead should make all necessary adjustments to the ECP.g.Once the ECP has been reconciled and the changes have been made, the projectlead will return the ECP to the review cycle. To accomplish this, perform ECPsOver 100,000 (Preliminary) Routing for Project Team Review steps 2bthrough 2k of this WPI.h.When the ECP was returned to Pending status, Agile once again re-populated theSignoff tab. Therefore, all team members will be required to once again performthe ECPs Over 100,000 (Preliminary) Project Team Review steps 3a through3h of this WPI and provide a review decision.i.When all team members provide their approvals, the ECP will automatically moveforward to Branch Chief Review status.j.Since Agile re-populated the Signoff tab, the branch chief will be required to onceagain perform the ECPs Over 100,000 (Preliminary) Branch Chief Reviewsteps 5a through 5h of this WPI and provide a review decision.k.When the branch chief approves the ECP, it will automatically move forward toSubmitted status.l.Agile will send the project lead an email notification that the status of the ECP hasbeen changed to Submitted.34
Work Practice InstructionsWPI0004October 29, 20047. Submitted ECPsa.Agile will send an email notification to the CM Analyst that the ECP has beensubmitted.b.The CM Analyst will review the ECP to ensure, as much as possible, thecompleteness and accuracy of the information provided.c.If the ECP is complete (contains information in all required fields and allattachments have been included), the CM Analyst will advance the ECP to ROCReview status.d.Agile will send the project lead an email notification that the status of the ECP hasbeen changed to ROC Review. The email will state, “ECP P7071 has been movedfrom SUBMITTED to ROC REVIEW for the ECP OVER 100K (PRELIM)workflow for approval. No action is required. This is for your informationonly.” This is a “canned” message from Agile and one the ROC cannot alter.e.The
To activate a project, a request is made at a TRC meeting to remove a CCR(s) from the System Project Pool, which will then become an ECP. The TRC will assign the project lead and team members at this time. Creating the ECP Template The CM Analyst will create the ECP template and populate the following fields: On the Cover Page – Number
Local ECP Hotline: 202-586-6642 Toll-free ECP Hotline: 844-799-8855
Retail Loans Origination User Guide Oracle Banking Origination Release 14.6.0.0.0 Part Number F57153-01 May 2022 . Retail Loans Origination User Guide Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon (East) Mumbai, Maharashtra 400 063
BINOCULAR LOUPE ECP Binocular Loupe 2.5X ECP Binocula Loupe 3.5X . Heine Indirect Ophthalmoscope SIGMA 250 LED . Heine Indirect Ophthalmoscope OMEGA 500 LED O u r P r o d u c t s. AUTO REFRACTOMETER ECP Ophthalmic Refraction Chair Un
the control buttons used to validate the ECP/Network Adequacy Template and create the template files to be submitted with the QHP Application. Note that additional . Facility ECPs. and . Individual ECPs. tabs cannot be added to the ECP/Network Adequacy Template. 2. Select ECPs. The . Select ECPs . tab contains the Final HHS plan year (PY) 2017 Non-
4 ECO-ECP MANUAL September 2012 revision 32 PREMESSA I generatori della serie ECO-ECP, rispondono alle direttive CEE 2006/42, 2006/95, 2004/108 e relative modifiche; pertanto non presentano pericolo per l'operatore, se installati, usati, manutenuti secondo le istruzioni fornite dalla Mecc Alte e a condizione che i dispositivi di sicurezza siano
in loan origination (Closing and Funding). Software vendors typically advise customers to start small, perhaps with a project involving exceptions which have to be processed manually. However, the company had already begun a process reengineering effort. In loan origination operations The first project needed to support that effort.
Retail Loans Origination User Guide . Oracle FLEXCUBE Onboarding . Release 14.5.0.0.0 . Part Number F41347-01 . May 2021 . Retail Loans Origination User Guide . Oracle Financial Services Software Limited . Oracle Park . Off Western Express Highway . Gurgaon (East) Mumbai, Maharashtra 400 063 .
R&D projects, but there are doubts on how many innovations have effectively gone to the market. The mid-term evaluations show outputs and results coming out of collective actions and support to regional filières and clusters. 2011 is the first year with outputs in the field of
