ML20128H209
| ML20128H209 | |
| Person / Time | |
|---|---|
| Issue date: | 06/10/1985 |
| From: | Matt Thomas, Wiggins E, Zentner M NRC OFFICE OF ADMINISTRATION (ADM), SMALL BUSINESS ADMINISTRATION, TECHNASSOCIATES, INC. |
| To: | |
| Shared Package | |
| ML20128H207 | List: |
| References | |
| CON-FIN-D-1363, CON-NRC-33-85-322 NUDOCS 8507090449 | |
| Download: ML20128H209 (7) | |
Text
AMLNbt.'.LN1 Ul- SU1UGUT MISW)/ MODIFICATION OF CONT RACT
. Aquviv.mooie ic Ai oN No 1 l7 a t. e t o.vt oui t u tc.s50.eh..v tHA5 u o No r mt c i N e n< eh m.
.e. 'Onnf1) ORM-85-322, 4/3/85
' ' " ' ' " '^""'""""""""'" __
coat _IM :p 9___ c d_ _ _ _ _ .
U.S. Nuclear Regulatory Commission Division of Contracts, AR 2223
'cla shi ngton, D.C. 20555 s N Au t AN D ADDset 5 O* C oN1 R AC T o R sso , .t.,,t, cot.n r>. sao e, and zu code) g 94. A u t N Dut Ni or Sot ic al e.T iv. vo-PRIME:' U.S. Small Business Administration' Washington District Office 1111 18th Street, N.W., 6th Floor 9B DAT ED <str iTsu s s)
Washington, D.C. 20417 SUB: Technassociates, Inc. son. uooiriC ATiON OF CO~T RaCza DEA 1700 Rockville Pike, Suite 200 *
~ NRC-33-85-322/
Rockville, Maryland 20852 x SB3-85-1-6374 lob DAT E D tSLE ATEM 13I CODE lF ACluTY CODt 3/18/85
- 11. THIS ITE M ONLY APPLIES TO AME NDMENTS OF SOLICIT ATIONS Tne at.o.t numbe ed solicitation is emended as set forth in item 14 The nou and cate see:Jed for rem;pt of OHe i is entenoec. e not es te n 2.c Ottrs must eca no.iecy rece;;t et this amenoment p<ior to the hou anc cate spepfie: ir the sootitation or as a ended. by one of the 1ohemns f*et ocs L) By completm; stems B and 15.anc returnin; copies o' tne amenomer t. (b) Bv octroaw; n; rete pt of this amensment on ea:t copy c' re oNe-submittec. or (c) By separate lette* or teieram which includes a reference to the soi.citabon anc amendment numters F AILURE OF YOUR ACKN?ALEDG MENT TO BE RECElvED AT THE PLACE DEstGNATED FOR THE RECEIPT OF OF FERs PRIOR TO THE HOUR AND DATE sPECIFIED MAY REsul~
IN F, EJECTION OF YOUR OFFER 11 by virtue of this annoment you ces.re to changt ae o*fe* aveah satmittec. such chany may be rnade b, te eya :-
lettr. prow.sec ea:b teie; am or 6ette rnames reference to the schcitation and this amen: ment.a,= is reaived p ior to tne opening hou' ano date spe:'ec
- 12. ACCOUNT ANG AND APPR OPhi AT ION DAT A (1/ reguued; N/A
- 13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS / ORDERS.
IT MODIFIES THE CONTR ACT/ ORDER NO AS DESCRIBED IN ITEM 14 g A, THIS CH ANGE ORDER is ISSUE D PVR5UANT TO: (Specif> outhority) THE CH ANGES SE T F OR TH iN IT E M 3 a A RE M ADE iN T HE Coa s-TR ACT ORDE R NO. lN ITEM 10A.
B. THE ABOVE NUMBE RE D CONT R ACT/ ORDER 15 MODIFIED TO R EF LECT THE ADUiN!5TR ATIVE CHANGES (such as chantes m pas.es ofUta apr'opriation date. etc.) SET F O RTH 14 ITEM 14, PU RSU ANT TO THE AUT HO RITY OF F A R 43.3 03(c).
C. T His SUPPLEMENT AL AGREEMENT 15 ENTE RED iNTO PUR$vANT TO AUTHORITY OF :
x Mutual agreement of the parties D. OT HL R (Specify type of modshea tnan and au thority)
E. IMPORT ANT: Contractor is not. is required to sign this docurnent and return Copies to the issuing office
- 1. DESC RiPT son oF AMENDMENT MoDIF 4 CAT ON (Organued by UCT section headmas. inesudmg sohettarion/ contract subiect motser uherr tens;s.e A The purpose of this task order is to incorporate minimum documentation standards for task orders issued hereunder. Therefore, the following change is hereby incorporated:
Section C.1.3, Statement of Work, Paragraph D is deleted in its entirety and the following is substituted in lieu thereof:
Encept as p 'ctCe ano sMett. 'ovided hettin, all tetrns anc conditior's of the docurnent referentec in item 9 A or IC A. as be'etof ort changed. remains unchangec and in f u IS A. N AME AND TITLE OF SIGNER (T>pe or print) 16A. N AME AND TITLE OF CONT R ACTING OF FiCER IT>pe or p :ets See Signature Page See Signature Page 2 5C DAT E 5,GNE D lth UNJ ED ST ATES OF Avi MC A 2 t.; L A T t 5 5'. E; 2th C O' i s.AL1 0 s/OFF E3 0E=
64 45.cneture rf person author. sed to s4n) (S.s na t.nve of Contractant Offuer)
N5N 75a041152 8070 30-105 ST AND ARD FORM 30 (RE 10-8 3 8507090449 850610 E'"R l%'CPRN^ m PDR CONTR NRC-33-85-322 PDR
"
- Centract No. NRC-33-85-322 SB3-85-1-6374 Modification No. One Page 2 of 7 "D. Users and Systems documentation shall be required as necessary for all system upgrades or modifications. Documentation format shall be determined by the Project Officer or his designee.
Following is a minimum standard documentation guide. It is not implied that all categories of documentation shall be needed for each task; rather, those categories that are needed (e.g., Program / Macro Documentation) shall be done in compliance with the following:
- 1. Reouirements Document-User Request Definition This document is used as a preliminary response to a users
' formal request for ADP system services and will usually be addressed by the Project Officer or task manager. It will assist RM/D in determining the overall feasibility, complexity, and severity / priority of the request. The document must include:
Date received Requested completion date System identifier /name User contact / phone / organization Reason for request -
Description of what is needed Reference Task Order Form Page 1A in the Appendix.
- 2. Feasibility Study Definition The feasibility study is the preliminary step necessary to ascertain if the user's request warrants a more in-depth study.
The document provides generalized requirements, methodologies for satisfying these requirements, and alternatives. As a minimum, this document will contain:
)
Devise feasibility study work plan Description of present environment or system Identify preliminary user requirements <
v
- _ _ _ -- .mA
Contract No. NRC-33-85-322 5B3-85-1-6374 <
Modification No. One Page 3 of 7 Identify technical constraints and rescuices needed
. Identify solutions and alternatives Develop initial project plans to estimate levels of effort and timing needed to complete requirements Prepare economic estimates evaluation:
Cost vs. lease Hardware / software cost considerations NRC purchases needed -
Estimated contractor costs Estimated total project cost User and task manager acceptance and project "go-ahead" statement and dates of signatures
- 3. Detail Functional Requirements Document for Task Completion Definition The functional requirements document serves as the basis and guide for technical support approach, conceptual design, and implementation -
and turnover plans. This document will contain as a minimum:
Detailed work plan delineating all tasks and subtasks to be performed, key personnel, and information sources All functional requirements to be satisfied System Data:
Define file structures and attributes Define directory structures Define all hardcopy/ screen inputs and outputs Determine environmental requirements s Define work flows Design testing plans and procedures Define training plans Define via Gant or CPM implementation plans and schedules and turncver procedures 6
8
r-- .
~
Contract No. NRC-33-85-322 SB3-85-1-6374 e Modification No. One Page 4 of 7 Detailed cost estimates (NRC items to be purchased and task costs)
User acceptance statement and signature /date 4 Systems Design Documentation Definition This document serves to illustrate the finalized system in detailed form. Items to be contained in this document include:
Systems overview and diagrams File data m
Hardcopy/ screen inputs / outputs
. Directory structures l
4 Special constraints:
Communications Run times -;
' ACLs and searchlists 4 Other considerations as necessary Special procedures and controls Vendor and user contacts
- i. 5. Program / Macro Documentation Definition Program / Macro documentation provides the information necessary to explain all aspects of a specific piece of software, sufficient enough to allow other technical personnel to understand and when necessary, modify the software. As a minimum, the documentation should include: "
E W
D
Contract N). NRC-33-85-322 SB3-85-1-6374 c Modification No. One Page 5 of 7 Module name Programmer name .
Date implemented.
Associated system (s) name Modification-list (name,date)
Description, purpose and overview of module I/O file, screen, and hardcopy data as applicable Program internals:
Arguments Switches Calling sequences Include files Entry points Stack areas Program flow narrative -
Pertinent comments:
Special edits ;
User responses Directory structures ACLs and searchlists Etc.
- 6. User Documentation Definition User _ documertation, sometimes referred to as user's guides, consists h of step-by ' tep instructions that will enable a user to successfully logon, invfie, and use a system and its related modules. As a -
- minimum, such documentation should include: 4 System operational overview and description User controls Technical operational procedures
P
- - J '. ,~ # .
Contract No. NRC-33-85-322 SB3-85-1-6374 i Modification fio. One -
Page 6 of 7 Problem identification and resolutions (e.g., erroi codes)
Contracts -
Special considerations:
When to execute-Input sources Output distributions Technical The contractor shall identify system changes necessary to serve the needs of the users and assess the impact of any such change on the system and related systems and provide this assessment to the Project Officer before any action is taken."
There' is no change to the total amount obligated to this contract.
All other terms and conditions remain the same.
f 9
-.,~j
Contract No. NRC-33-85-322 SB3-85-1-6374 _
Modification No. One Page 7 of 7 TRIPARTITE AGREEMENT Signature Page .
PRIME CONTRACTOR:
U.S. Small Business Admin' tion j By:
b,,
G OFFICER
- hOh /
Name., [
Ti tle:
SUBCONTRACTOR:
Technassociptes Inc. Oe By: ! d&
-c [,z Date: May 31, 1985 Name: V[
MARVIN A. ZENTNER
Title:
Executive Vice President PROCURING OFFICE:
l U.S. Nuclear Regulatory Commission By: (L 4 s& gate: $ ,h 3lpS-
~
l Name: Elois Wiggins uu - -
l l
Title:
Contracting Officer -
t i
I
^
i l
I l
L. *