Attach005-FMS-ACES RFI - Schedule Template.xlsx

Cover Page Attachment 005 – FMS-ACES RFI Schedule Template

Reference the "Instructions" TAB to complete.

Instructions

You may add, change, and delete any major area (Program Management, Hosting, Infrastructure…) to convey the schedule to deliver your solution.

You may add additional months.

Maintain the overall format of the "Schedule" Tab. The objective is to illustrate the significant activities, products, events, and decision points anticipated for the program. This template provides a framework for building a schedule and communicating the major components of the schedule for your solution. While several major areas are identified, the goal is to provide what you see as the work to be performed to achive an operational solution. One month increment level of detail is deemed sufficient for conveying the duration of the work to be performed to deliver your solution.

Activities: Tasks such as requirements analysis, architecture development, design development, capability development, integration testing, end-to-end testing, CI/CD pipeline creation, …

Events: Tasks such as management reviews, technical reviews, Government acceptance test, ATO, …

Products: Tasks such as program plans, metrics, design documents, architecture artifacts, test plans, test reports, training materials, deployment plan, …

Decision Points: Tasks such as Go Live, Government approvals, ...

Review the major areas (Program Management, Hosting, Infrastructure, …) Add any major areas deemed missing Change / Delete task areas that do not pertain to your plan to deliver an operational solution

Step 2:

Add Tasks (Activites, Products, Events, Decision Points) for each major area; add as many as you need to communicate your plan Delete any extra tasks that do not pertain to your plan.

Change the generic names (Activity 1, Activity n, Product 1, Product n, ...) to provide a descriptive name for each task to assist in explaining your solution roadmap and schedule.

Step 3:

Add additional months (if necessary) to provide suffiicent space in the schedule include the estimated duration and show how you would deliver your solution. There is neither significance nor implied menaing in the number of months provided in the template.

Step 4:

Color the cells (as shown in the example Program Management Task Area) to show the estimated duration of each task. Use any colors (or a single color) that communicates your plan best. There is neither significance nor implied meaning in the duration or number of colored cells or the color of the cells in the example.

Delete/remove/uncolor the example bars before preparing your schedule.

Step 5:

At the end of your schedule, reelative to your schedule:

- Note any Assumptions

- Note any Dependencies Use as many rows as you need.

END OF INSTRUCTIONS

Schedule

image1.png