Joint Aircraft Survivability Program by HC121104002213

VIEWS: 1 PAGES: 7

									SOW Template Information:                SOW Instructions:                             SOW Example Data:
DO NOT DELETE                            DELETE UPON COMPLETION                        UPDATE OR DELETE UNUSED
                                                UNCLASSIFIED                           UPON COMPLETION


                               Joint Aircraft Survivability Program
                                           STATEMENT OF WORK

     FY13 SOW                                         DD Month YYYY (Revision #) Leave revision #
                                                      blank if this is the original SOW for the FY.

    I. PROJECT IDENTIFICATION:

       a. Project Number:                             (For continuing projects use current project
                                                      number; if a new start project, JASPO will assign a
                                                      project number)

       b. Project Title:                              (Self-Explanatory, limit to 30 characters)

       c. Subgroup:                                   (Complete as required: Susceptibility Reduction,
                                                      Vulnerability Reduction or Survivability
                                                      Assessment)

       d. Responsible Engineer(s):                    Name (If your project is a multi-Organization effort,
                                                      enter the lead (i.e. responsible) Organization and
                                                      POC for the entire project first. Then list each
                                                      additional government organization and POC
                                                      receiving JASP funds.)
                                                      Organization/Office Code
                                                      Street Address
                                                      City, State, Zip Code
                                                      Phone: Commercial / DSN
                                                      FAX: Commercial / DSN
                                                      Email:

       e. Work Completion Date:                       DD Month YYYY (Date of last technical task
                                                      milestone, before writing report—not funding
                                                      document work completion date)

       f.   Final Report Date:                        DD Month YYYY (Generally 90 days after last
                                                      technical task milestone)

       g. Contractor(s):                              Identify Contractor(s) and Contract Number(s) for
                                                      all CAT II (direct cite) requested funding and CAT I
                                                      (reimbursable) funding that will be put on contract
                                                      by a government agency. Enter “none” if no
                                                      contract action anticipated; enter TBD if contract is
                                                      anticipated but the number is not known yet (i.e. not
                                                      signed yet, unsure which contract it will go on, etc.).



     Distribution authorized to U.S. Government agencies and their contractors only;
     Operational/Administrative Use; July 2012. Other requests shall be referred to the Joint Aircraft
                                                  th
     Survivability Program Office (JASPO), 200 12 Street South, Suite 1103, Arlington, VA 22202.

                                                UNCLASSIFIED

                                                          1
                                                    UNCLASSIFIED

II. FINANCIAL PLAN:

   Table 1. Project Funding Profile (total project costs). Replace “Other Funding” with the
   appropriate organization information. This is typically leveraged funds as outlined in the
   proposal. Update/replace the blue values with the actual project values. Total values sum
   automatically.

              PROJECT FUNDING                                              Funding ($K)
                  PROFILE                       Prior FY            FY13      FY14      FY15              Totals
                JASP Funding                                         495       350       225               1070
               Other Funding A*                                      200       150        50               400
               Other Funding B*                                      150       100                         250

                   TOTAL COST                        0              845          600          275          1720
           (Embedded Microsoft Excel Worksheet. Double click table to edit)


            *Other Funding POCs: Identify organizations and POCs, with phone
            numbers, for verifying other funding sources.

   Table 2. JASP Funding Profile (JASP portion of project). Replace government agencies
   (GOV) A, B, and C and contractors (CTR) A, B, and C in the table with the appropriate
   organization information. Each line in this table represents a separate funding action or
   Military Interdepartmental Purchase Request (MIPR) – indicate whether the funds should be
   sent CAT I Reimbursable or CAT II Direct Cite. CAT I funds are intended for Government
   salary, travel, etc., and direct cite funds will be directed to a contract. A separate MIPR will be
   sent to each organization for each type of category of funds required. In some cases, CAT I
   funds may be put on contract – show this in the table with a “CAT I” in the Funding Category
   block next to appropriate CTR. CTR “A” denotes that it will be put on contract by GOV “A”.
   Complete the Project MIPR Data Sheet per paragraph VI. A separate worksheet is required
   for each funding action.

         JASP FUNDING PROFILE                                                    Funding ($K)
                       FUNDING
       ORGANIZATION                                    Prior FY           FY13         FY14         FY15      Totals
                      CATEGORY
          GOV A          CAT I                                             175         100          100           375
           CTR A        CAT I*                                              20          20           20            60
          GOV B          CAT I                                             100          50                        150
           CTR B        CAT II                                              25          25                         50
          GOV C          CAT I                                              80          75          50            205
          CTR C         CAT II                                              95          80          55            230

         TOTAL COST                                         0              495         350          225        1070
    (Embedded Microsoft Excel Worksheet. Double click table to edit)


 *In this case, JASPO will send CAT I funds to GOV A who will turn around and put CTR A on
 contract.




                                                    UNCLASSIFIED

                                                                2
                                            UNCLASSIFIED

III. OBJECTIVES: Provide a brief text description of your overall program goals and how JASP
     funding fits into the overall project. Provide specific JASP funded objective(s) for FY13. List
     objective(s) in terms of quantifiable metrics. Each Objective shall have at least one measure
     (metric) and at least one corresponding performance target (i.e. measure of if, or how well, the
     objective is met, and/or how do you know you are done). A minimum of one objective is
     required. Performance targets should be a realistic technical or programmatic objective;
     failure to meet the target in an RDT&E project is not necessarily an indication of poor
     performance.

     Table 3. FY13 Project Objectives, Measures (metrics), and Performance Targets.
     Examples shown in Table below:

 #                  Objective(s)                       Measure(s) (metric)         Performance Target
                                                    a. Software crashes per
 1 Increase reliability of model XYZ software.                                   a. 1 crash per hour
                                                    hour
                                                    a. Number of dry bay
                                                    fires as a result of
     Demonstrate effectiveness of XYZ to                                         a. No dry bay fires
 2                                                  ballistic impacts
     protect against threat ABC.                                                 b. Less than 1 sq ft
                                                    b. Area of structural
                                                    damage
                                                    a. Detection
                                                    opportunities data
     Determine ability of AN/XYZ-123 to detect      collected                    a. 25 tests conducted
 3
     threat ABC.                                    b. False alarm               b. 100 tests conducted
                                                    opportunities data
                                                    collected



IV. METHOD OF ACCOMPLISHMENT: Provide sufficient detail so the reader will understand
    your approach, key milestones, tasks required to meet objective(s), task durations and
    interdependencies between tasks and organizations. Include resource availability if it is a key
    driver to your project (i.e. flight test aircraft, key personnel). For continuing projects, provide a
    brief description of previous accomplishments by fiscal year. For each FY13 quarter, include
    at least one Milestone, based on outcomes rather than activities (e.g. 2Q: detailed test plan
    approved vice write test plan). These will be used as a baseline to gauge project progress
    during the fiscal year. For projects continuing into FY14 and beyond, provide yearly
    goals/milestones for those year(s). Clearly identify significant risks (schedule, cost,
    performance) and a short description of how they will be mitigated. If your project includes
    Modeling and Simulation (M&S) or supports M&S V&V, discuss validation considerations and
    testing/modeling coordination required to make sure the correct data will be collected. Test
    projects collecting data for M&S validation should include an M&S subject matter expert
    participant. Below is the method of presenting tasks and milestones. Include which
    organization is performing the task if multiple organizations (including contractors) are
    involved. Fill in quarterly milestones only if there is an action to accomplish the task.




                                            UNCLASSIFIED

                                                     3
                                     UNCLASSIFIED


FY2013

Objective 1: State Objective 1 (from Table 3). Increase reliability of model XYZ software.
Task (a): Describe Task (a) that supports the accomplishment of Objective 1. Include in
parenthesis the organization(s) performing the task. Develop software reliability test plan
(GOV A, GOV B).
Quarterly Milestones: Below, use action words such as “initiate”, “begin”, “start”, “conduct”,
“meet”, “develop”, “continue”, and “complete” when describing quarterly milestones of Task
(a). Include in parenthesis the organization(s) accomplishing the milestones.
1Q:
2Q: Hold IPT meeting to develop test plan (GOV A, GOV B).
3Q: Complete test plan development (GOV A, GOV B).
4Q:

Task (b): Describe Task (b) that supports the accomplishment of Objective 1. Include in
parenthesis the organization(s) performing the task. Conduct software testing (GOV B,
CTR B).
Quarterly Milestones: Below, use action words such as “initiate”, “begin”, “start”, “conduct”,
“meet”, “develop”, “continue”, and “complete” when describing quarterly milestones of Task
(b). Include in parenthesis the organization(s) accomplishing the milestones.
1Q:
2Q:
3Q: Initiate testing (GOV B).
4Q: Complete testing (GOV B, CTR B).

Objective 2: State Objective 2 (same as Table 3). Demonstrate effectiveness of XYZ to
protect against ABC type threats.
Task (a): Describe Task (a) that supports the accomplishment of Objective 2. Include in
parenthesis the Organization(s) performing the task. Perform literature search (GOV B,
GOV C).
Quarterly Milestones: Below, use action words such as “initiate”, “begin”, “start”, “conduct”,
“meet”, “develop”, “continue”, and “complete” when describing quarterly milestones of Task
(a). Include in parenthesis the organization(s) accomplishing the milestones.
1Q: Initiate literature search (GOV B, GOV C).
2Q: Continue literature search (GOV B, GOV C).
3Q: Complete literature search (GOV C).
4Q:

Task (b): Describe Task (b) that supports the accomplishment of Objective 2. Include in
parenthesis the Organization(s) performing the task. Conduct XYZ testing (GOV C, CTR C).
Quarterly Milestones: Below, use action words such as “initiate”, “begin”, “start”, “conduct”,
“meet”, “develop”, “continue”, and “complete” when describing quarterly milestones of Task
(b). Include in parenthesis the organization(s) accomplishing the milestones.
1Q:
2Q:
3Q: Initiate XYZ testing (GOV C, CTR C).
4Q: Complete XYZ testing (GOV C, CTR C).



                                     UNCLASSIFIED

                                              4
                                     UNCLASSIFIED

Objective 3: State Objective 3 (same as Table 3). Determine ability of AN/XYZ-123 to
detect threat ABC.
Task (a): Describe Task (a) that supports the accomplishment of Objective 3. Include in
parenthesis the Organization(s) performing the task. Validate and Verify (V&V) threat ABC
surrogate (GOV A, GOV C, CTR C).
Quarterly Milestones: Below, use action words such as “initiate”, “begin”, “start”, “conduct”,
“meet”, “develop”, “continue”, and “complete” when describing quarterly milestones of Task
(a). Include in parenthesis the organization(s) accomplishing the milestones.
1Q:
2Q: Initiate V&V of surrogate (GOV A).
3Q: Continue V&V of surrogate (GOV A, GOV C, CTR C).
4Q: Complete V&V of surrogate (GOV C, CTR C).


Task (b): Describe Task (b) that supports the accomplishment of Objective 3. Include in
parenthesis the Organization(s) performing the task. Conduct flight testing (GOV A).
Quarterly Milestones: Below, use action words such as “initiate”, “begin”, “start”, “conduct”,
“meet”, “develop”, “continue”, and “complete” when describing quarterly milestones of Task
(b). Include in parenthesis the organization(s) accomplishing the milestones.
1Q:
2Q:
3Q: Begin flight testing (GOV A).
4Q: Complete flight testing (GOV A).


FY2014 (if applicable)
Yearly Goals/Milestones: Provide a brief narrative of what you plan to accomplish in FY14.

FY2015 (if applicable)
Yearly Goals/Milestones: Provide a brief narrative of what you plan to accomplish in
FY15.

Table 4. FY13 Funding Task Expenditure Profile (JASP funded portion only). Include for
each FY13 quarter the amount of funds expected to be spent on the associated task, by
organization. Each block should correlate with the task milestones in Table 3 (i.e. each
quarterly milestone should have associated funding – no quarterly milestone, no associated
funding). Your financial performance will be evaluated against this expenditure plan.

Bottom Line: What are you doing? Who’s doing it? When is it going to be done? And
how much is going to be spent doing it?




                                     UNCLASSIFIED

                                              5
                                                     UNCLASSIFIED

                  FY13 TASK EXPENDITURE PLAN                                     Funding ($K)
     OBJ                   TASKS                                  ORG    1Q   2Q    3Q     4Q   Totals
                Task (a) in support of Obj 1.                    GOV A        10    15            25
             Develop software reliability test plan.             GOV B        15    10            25
       1
                Task (b) in support of Obj 1.                    GOV B              15     20     35
                  Conduct software testing.                      CTR B                     25     25
                Task (a) in support of Obj 2.                    GOV B        20    20            40
             Develop software reliability test plan.             GOV C        20    20     10     50
       2
                Task (b) in support of Obj 2.                    CTR C              15     15     30
                  Conduct software testing.                      CTR C              25     35     60
                                                                 GOV A        20    20            40
                Task (a) in support of Obj 3.
                                                                 CTR B              10     10     20
             Develop software reliability test plan.
       3                                                         CTR C              20     15     35
                  Task (b) in support of Obj 3.
                                                                 GOV A              60    50     110
                   Conduct software testing.
                                                                 GOV A   0    30    95     50    175
                                                                 CTR A   0     0     0      0      0
                                                                 GOV B   0    35    45     20    100
                        TOTAL COST QUARTERLY                     CTR B   0     0    10     35     45
                                                                 GOV C   0    20    20     10     50
                                                                 CTR C   0     0    60     65    125
                                                                 TOTAL   0    85   230    180    495
                                                                 GOV A   0    30   125    175
                                                                 CTR A   0     0     0      0
                                                                 GOV B   0    35    80    100
                        TOTAL COST CUMULITIVE                    CTR B   0     0    10     45
                                                                 GOV C   0    20    40     50
                                                                 CTR C   0     0    60    125
                                                                 TOTAL   0    85   315    495
    (Embedded Microsoft Excel Worksheet. Double click table to edit)


V. DELIVERABLES:
   Identify the project deliverable(s) by quarter, including technology, technology readiness level
   (TRL), models or simulations, and their documentation and final reports. All JASP projects
   are required to submit an approved draft* of their final technical report within 90 days of the
   Work Completion Date (WCD) – final technical task. If the time required to generate the
   report after the WCD is not 90 days, an alternate timetable shall be negotiated with the
   appropriate DPM.

    *The Approved Draft of the Final Technical Report is a technically complete version of the
    report with project results that has been approved (signature) by the Project Engineer’s
    organizational chain-of-command. This submission is prior to any standard administrative
    review that an organization chooses for final editing/assembly (e.g. WPAFB Scientific
    Technical Information Office – STINFO or China Lake Technical Communications Office -
    TCO). The Approved Draft will be submitted to JASPO NLT 90 days after the Work
    Completion Date (WCD). The WCD is the date on which the last technical task occurs or the
    last day of the quarter in which funding was received, whichever is later.




                                                     UNCLASSIFIED

                                                                6
                                              UNCLASSIFIED

VI. REPORTING REQUIREMENTS:
    If revisions to this SOW are required (more than 1.5 months behind schedule, actual expenditures don’t
    match this SOW within 30%, change of scope, objectives, approach, or deliverables, submit a SOW
    Revision Request (SRR) form and update the SOW using track changes. Make sure you update the
    SOW date for each revision. A final SRR must be submitted to JASPO at least 30 days prior to the
    deliverable (report) due date to be considered.

    a.   PROJECT MONTHLY FINANCIAL UPDATE
         The technical POC for each government agency receiving funds (or their Business Financial
                                                                                       th
         Manager (BFM)) will submit a monthly financial update to JASPO by the 11 of each month. The
         update will include all reimbursable, direct cite (contract), and reimbursable funds put on contract.
         The report will list the funding document (e.g. MIPR) number and amount received, obligated, and
         expended against that document as of the end of the preceding month.

    b.   PROJECT QUARTERLY TECHNICAL UPDATE
         The lead project engineer submits to JASPO a technical update at the end of each fiscal year
         quarter. The report should describe accomplishments for the preceding reporting period and plans
         for the following reporting period, using the tasks and milestones from the SOW. It should highlight
         problems/issues, deviations from planned schedule/performance, unexpected setbacks or
         breakthroughs, and products delivered to customers. The reports shall be submitted to JASPO via
         email within 15 days of the end of the quarter. Reminders with templates will generally be sent out
         by JASPO DPMs. Fourth quarter technical updates will serve as annual reports, whereby
         accomplishments for the entire FY will be reported.

    c.   PROJECT MIPR DATA SHEET
         The MIPR Data Sheet identifies reimbursable and direct cite funding requirements. Reimbursable
         funds are intended to support Government agency efforts, while Direct Cite funds are directed to a
         contract. A worksheet is required for each recipient of JASP funds and should accompany the
         completed Statement of Work. Submission of a completed worksheet is the responsibility of the
         lead project engineer. Again, a separate MIPR will be sent to each organization for each type of
         category of funds required, thus requiring a separate data sheet for each.

    d.   PROJECT RE REPORT AT ANNUAL PROGRAM REVIEW
         For projects that receive $50K or more in the current fiscal year, the lead project engineer, or
         designated representative, shall prepare and present a project status briefing at the annual
         program review. The date and location of the meeting will be announced by JASPO.

    e.   PROJECT FINAL REPORT
         The results of all JASP funded efforts shall be documented in a final report. Prepare and publish
         the report in accordance with your organizations formats and processes. A “preliminary draft” of the
         final report (including contractor submitted drafts) shall be provided to the appropriate JASP
         Subgroup chairman and JASPO deputy program manager for review and comment at least 30
         days prior to the report due date and before publication by the parent organization. The lead project
         RE will obtain a JASP report number and logo from the JASPO. The JASP document number shall
         appear on the report cover and documentation page, the JASP logo shall appear on the cover. The
         report shall include a Report Documentation Page, Standard Form 298. List your project number
         (i.e. S-08-06) and “JASP” as key words on your SF-298. At a minimum, the distribution will include
         the JASP Subgroup Chairmen, Principal Members Steering Group, SURVIAC and DTIC. An
         electronic copy of all unclassified Final Reports shall be provided to the JASPO upon publication.
         For classified Final Reports, the JASPO DPM will request either a hardcopy or electronic copy at
         least 30 days before the Final Report due date.




                                              UNCLASSIFIED

                                                        7

								
To top