TAT STI Assessment Report Working Aid 22 December 2011

balecomputerSecurity

Nov 3, 2013 (3 years and 10 months ago)

82 views

TAT STI Ass
essment Report


Working Aid


22

December 2011




1

TAT STI Assessment Report



IAC: _________________

Contract Number: _____________ Date: _____________


Reporting Period: __________________


IAC Director

IAC Technical Point of Contact

Name:

__________________________________

Name:

_____________________________

Phone/FAX:______________________________

Phone/FAX:_________________________

Email:

__________________________________

Email:

_____________________________


COR:

Name:_____________________________


Phone:______________________
_______

FAX:_____________________________


Delivery
Order #

Status*
(open/closed/

inactive)

Ceiling Value

% Ceiling
Expended

Date
Closed

Final TR
Complete
(yes/no)

Total STI
Required By
TAT

Total STI
Produced Under
TAT to date

STI
Uploaded
to
DTIC

STI Not Suited for
Upload to
DTIC
**



























































































* Inactive DOs require a detailed explanation of the reason for their inactive status, as well as an
assessment of the
prospect for the future of the DO (i.e., will it become active; if so, when?)

** Due to classification above SECRET

and inability to produce sanitized deliverable or SF298 at
SECRET or below

(other reasons for not uploading to
DTIC

must be approved by the
DTIC IAC PM)

***
Note
: report all TATs, both open and closed; DO shall be reported as “archived” (gray background
and move to bottom of list), once
all

of the following conditions are met:



Status = closed



Final TR Complete = yes



Total STI

Produced

=

STI Up
loaded to
DTIC

+ STI Not Suited for Upload to
D
TIC

TAT STI Ass
essment Report


Working Aid


22

December 2011




2

1.

Format

a.

Please u
se the above format for reporting

2.

Content

a.

Content of the STI assessment report should cover all
TAT
Delivery Orders under
the same report, with each DO listed on a separate line within t
he
report, per the
above format

b.

Please report all currently open TATs, as well as any TATs that were open as of
the effective date of the revised SOP

that first implemented the TAT STI
Assessment Report requirement

(1 July 2009)

i.

For TATs closed prior to 1 Jul
y 2009, no reporting is required

ii.

For TATs closed subsequent to 1 July 2009, reporting is required

iii.

For all open TATs, reporting is required

c.

Specific definitions of each column are as follows:

i.

Delivery Order

1.

Please use Deliver Order number (from the
DD

Form
1155
),
not

TAT number (from PREMIS
/RMS
)

ii.

Status

1.

O
pen TAT
s may be classified as either active or inactive

a.

If open and active, please report as “open”

b.

If open and inactive, please report as “inactive”

i.

Inactive refers to those TATs on which
PoP
remains, but al
l funding received has been expended

ii.

For inactive TATs, please indicate whether we are
expecting additional funding

and, if so, when; if no
additional funding is expected
,
inactive TATs

are
candidates for close
-
out

2.

For closed TATs, please only report those

TATs that closed after 1
July 2009

iii.

Ceiling Value

1.

Ceiling value (total potential value) of
TAT
, as indicated in TAT
Task Order award

iv.

%
Ceiling Expended

1.

Funds expended divided by ceiling value of each TAT

v.

Date Closed

1.

If TAT is closed, identify date
DD250
was signed by COR

2.

If DD250 has not yet been signed, then TAT is still considered
open, even if all deliverables have been submitted and PoP has
ended

vi.

Final TR Complete

1.

Has final Technical Report been for
mally accepted by the COR

a.

A
cceptanc
e occurs via signa
ture on SF298

or in the TEMS
Web Services interface

b.

Indicate “Yes” or “No”

vii.

Total STI Required by TAT

1.

Total number of contract deliverables that are considered/expected
to be of STI nature

(this number will not change)

TAT STI Ass
essment Report


Working Aid


22

December 2011




3

2.

Report all STI deliverables listed on
the contract, even if the TAT
is not fully funded

viii.

Total STI Produced Under TAT to date

1.

Report all STI deliverables formally
a
ccepted by the COR

a.

A
cceptanc
e occurs via signature on SF298

or in the TEMS
Web Services interface

2.

For STI deliverables with classi
fication or distribution restrictions
that preclude upload to
DTIC
, a sanitized deliverable or sanitized
SF298 may be substituted

3.

Include
STI
deliverables that are listed on the TAT, as well as ad
hoc STI deliverables requested by the RA and already
accept
ed by
the COR


a.

Accepta
nce

occurs via signature on SF298

or in the TEMS
Web Services interface

4.

Upon COR acceptance of an STI deliverable, the IAC should make
every effort to upload the deliverable into
DTIC

(via entry into the
TEMS Web Services interfac
e
)

in an expeditious manner, making
current STI available to a broad audience

5.

IACs should coordinate a mutually agreeable schedule with their
COR to ensure review of all deliverables on a quarterly basis, at a
minimum; review may occur more frequently, if mu
tually agreed
by the IAC and COR

ix.

STI Uploaded to
DTIC

1.

Report all STI

deliverables that have been uploaded to
the TEMS
Web Services interface

as of the date of the report

a.

Include only STI deliverables produced and delivered by
the IAC under performance of t
he subject TAT

b.

Include STI deliverable uploaded during the reporting
period, as well as STI deliverables uploaded previously

2.

Note:
when entering data into the TEMS Web Services interface
,
for deliverables produced under a TAT, please be sure to
include
the

Delivery Order number in

the
designated

field
; the TEMS Web
Services interface ensures entry in the proper format

x.

STI Not Suited for Upload to
DTIC

1.

If an STI deliverable is not suited for
DTIC
(due to classification
or distribution restrictions) and a sanitized copy or abstract cannot
be produced suitable for
DTIC
, report the deliverable as “not
suited for
DTIC


2.

DTIC
can only accept STI classified SECRET or below

(SECRET
records are loaded into
DTIC Online Classified; unclassified
records are loaded into DTIC Online Access Controlled
-

DOAC)

3.

Every effort should be made to produce a sanitized copy of
deliverables
originally
classified above SECRET, or to produce
and upload an SF298 classified SECR
ET or below

4.

For IACs that do not have the ability to upload classified

STI
, if
you have deliverables or abstracts of deliverables classified
TAT STI Ass
essment Report


Working Aid


22

December 2011




4

SECRET that are suited for upload to
DTI
C
, please coordinate
with your PMA for potential submission to DTIC for upl
oad, on a
case
-
by
-
case basis

5.

Not
e: for all classified
IAC
STI included in DTIC Online
Classified, any record entered after July 2009 should have a
sanitized
metadata record

produced and included in DOAC

(via
creation of the record in the TEMS Web Services
interface)
; be
sure to follow
all applicable
IAC, DTIC, and DoD policies and
procedures

3.

General Clarification

a.

Report distribution is to the PMA and COR
, per the TAT SOP

b.

T
he IAC PMO requests the report by the 23
rd

calendar day of the month after the
end of each quarter (i.e., Jan 23, Apr 23, Jul 23, and Oct 23)

c.

The IAC PMO recognizes that the term “deliverable” is subject to interpretation
.


The STI Assessment Report

is focused on deliverables considered of suffici
ent
STI value for upload to
DTIC

i.

A good rule of thumb is to ask if the potential “deliverable” would be
valuable to share with the broader techn
ical community; if the answer is

“yes,” then consider it an STI deliverable for the purpose of this report; if
t
he answer is “no,” then do not consider it for this report.

ii.

Also, reference the TEMS Data Providers Guide for clarification on what
constitutes STI and is appropriate for upload to
DTIC

d.

The purpose for tracking
the # of
actual STI deliverables against
the
# of
STI
deliverables identified in the contract is to ensure we are providing at least as
much STI to the broader community as originally contracted. However, rather
than simply tracking the
specific
deliverables listed on the contract, the IAC PMO
recog
nizes that the RA may substitute ad hoc deliverables for those listed.

In
short, this report measures STI delivered and made publicly available against STI
procured via IAC contracts.

i.

The IAC PMO recognizes that upon completion of a TAT, especially if
the

TAT is not fully funded, total STI produced may be less than total STI
required.

ii.

For the above reason, we have
included

a column to document how much
of the ceiling value of the TAT has been expended to date

1.

The IAC PMO recognizes that, even if 50% of cei
ling has been
expended, it is likely that less than 50% of STI deliverables have
been produced, since many deliverables may be scheduled for later
phases of TAT completion; however, funding expended is
one
factor

in setting expectations for STI production,

especially for
TATs that close without being fully funded