(a) Under the following authorities, the Administrator has delegated to the Associate Administrator for Procurement authority to prepare, issue, and maintain the NFS:

(i) The National Aeronautics and Space Act of 1958 (Public Law 85-568; 42 U.S.C. 2451 et seq.).

(ii) 10 U.S.C. chapter 137.

(iii) Other statutory authority.

(iv) FAR subpart 1.3.

The NFS applies to all acquisitions as defined in FAR Part 2 except those expressly excluded by the FAR or this chapter.

(a) The single official NASA-maintained version of the NFS is on the Internet (http://www.hq.nasa.gov/office/procurement/regs/nfstoc.htm).

(b) The NFS is issued as chapter 18 of title 48, Code of Federal Regulations (CFR).

(b)(1)(A) Numbering of NFS text implementing the FAR shall be the same as that of the related FAR text, except when the NFS coverage exceeds one paragraph. In such case the NFS text is numbered by skipping a unit in the FAR 1.105-2(b)(2) prescribed numbering sequence. For example, two paragraphs implementing FAR 1.105-2(b)(1) are numbered 1801.105-2(b)(1) (A) and (B), rather than (1) (i) and (ii). Further subdivision of the NFS implementing paragraphs would follow the prescribed sequence in FAR 1.105(b)(2).

(B) NFS text that supplements the FAR is numbered the same as its FAR counterpart with the addition of a number 70 and up. For example, NFS supplement of FAR subsection 1.105-3 is numbered 1801.105-370. Supplemental text exceeding one paragraph is numbered using the FAR 1.105-2(b)(2) prescribed numbering sequence without skipping a unit.

(2) Subdivision numbering below the fourth level repeats the numbering sequence using italicized letters and numbers.

(1) NFS requirements. The following OMB control numbers apply:

(2) Solicitations and contracts. Various requirements in a solicitation or contract, generally in the statement of work, are not tied to specific paragraphs cleared in paragraph (1) of this section, yet require information collection or recordkeeping. The following OMB control numbers apply to these requirements: 2700-0086 (acquisitions up to $25,000), 2700-0087 (solicitations that may result in bids or proposals not exceeding $500,000), 2700-0085 (solicitations that may result in bids or proposals exceeding $500,000), 2700-0088 (contracts not exceeding $500,000), and 2700-0089 (contracts exceeding $500,000).

(a) The NFS is amended by publishing changes in the Federal Register. These changes are then incorporated into the NASA-maintained Internet version of the NFS through Procurement Notices (PNs). PNs are numbered consecutively, prefixed by the last two digits of the calendar year of issuance of the current edition of the NFS.

(b) Compliance with a revision to the NFS shall be in accordance with the PN containing the revision. Unless otherwise stated, solicitations that have been issued, and bilateral agreements for which negotiations have been completed, before the receipt of new or revised contract clauses need not be amended to include the new or revised clauses if including them would unduly delay the acquisition.

(a) Informal suggestions for improving the NFS, including correction of errors, should be directed to the Headquarters Office of Procurement (Code HK).

(b) (1) Formal requests for changes to the FAR or the NFS should be written and contain

(i) A description of the problem the suggested revision is designed to cure,

(ii) The revision in the form of a marked-up copy of the current FAR or NFS language or the text of any additional language,

(iii) The consequences of making no change and the benefits to be expected from a change, and

(iv) Any other information necessary for understanding the situation, such as relationship between FAR and NFS coverage, legal opinions, coordination with other offices, and existing agreements.

(2) Formal requests for FAR and NFS changes should be sent to Code HK. Requests from Headquarters offices should originate at the division level or higher, while installation requests should be signed at the procurement officer or higher level.

(a) The Procurement Information Circular (PIC) is used for internal dissemination of procurement-related information and directives not suitable for inclusion in the NFS. Code HK is responsible for issuing PICs.

(b) PICs are numbered on a calendar year basis, beginning with number 1, prefixed by the last two digits of the year.

(a) (2) Heads of NASA field installations may prescribe policies and procedures that do not have a significant effect beyond the internal operating procedures of their installations. All other policies, procedures, and solicitation and contract provisions and clauses must be forwarded to the Headquarters Office of Procurement (Code HK) for approval in accordance with 1801.271(b).

(b) (i) 41 U.S.C. 418b requires publication of NFS changes for public comment where there will be a significant effect beyond the internal operating procedures of the agency or a significant cost or administrative impact on contractors or offerors. However, it does not define “significant effect beyond the internal operating procedures” or “significant cost or administrative impact.” Examples of policies or procedures that fall in either of these categories are:

(A) A contract clause requiring contractors to take precautions to avoid injury to Florida manatees, which have been designated as an endangered species, has a significant cost impact for contractors who must obtain protective devices for boat propellers and take other safety actions.

(B) A contract clause requiring contractors to follow the Government's holiday schedule, thereby disallowing premium pay for work on contractor-designated holidays, will have an effect outside the internal operating procedures of the agency.

(C) A contract clause requiring contractors to segregate costs by appropriations will affect the contractor's internal accounting system and have a significant impact.

(D) Requiring contractor compliance with NASA's Space Transportation System Personnel Reliability Program will have an effect outside the internal operating procedures of the agency.

(ii) In contrast, the following would not have to be publicized for public comment:

(A) Security procedures for identifying and badging contractor personnel to obtain access at a NASA installation.

(B) A one-time requirement in a construction contract for the contractor to develop a placement plan and for inspection prior to any concrete being placed. (This is a part of the specification or statement of work.)

(C) A policy that requires the NASA installation to maintain copies of unsuccessful offers.

(a) Part, subpart, and section numbers 70 through 89 are reserved for NFS supplementary material for which there is no FAR counterpart.

This subpart prescribes the policies and procedures for authorizing deviations from the FAR and the NFS.

(a) Requests for authority to deviate from the FAR or the NFS shall be submitted by the Procurement Officer to the Headquarters Office of Procurement (Code HS).

(b) Each request for a deviation shall contain, as a minimum—

(1) Identification of the FAR or the NFS requirement from which a deviation is sought;

(2) A full description of the deviation, the circumstances in which it will be used, and the specific contract action(s) to which it applies;

(3) A description of its intended effect;

(4) A statement as to whether the deviation has been requested previously and, if so, the circumstances of the previous request;

(5) Identification of the contractor(s) and the contract(s) affected, including dollar value(s);

(6) Detailed reasons supporting the request, including any pertinent background information; and

(7) A copy of counsel's concurrence or comments.

(c) In addition to the information required by 1801.471(b), requests for individual deviations from FAR cost principles under FAR 31.101 should include a copy of the contractor's request for cost allowance.

The authority to contract for authorized supplies and services is delegated to the Associate Administrator for Procurement and installation officials by NPD 5101.32.

(b) Policy. Individuals making unauthorized commitments may be subject to disciplinary action, and the issue may be referred to the Office of Inspector General.

(c)(7) The authority in FAR 1.602-3 may be exercised only when—

(A) The Government employee who made the unauthorized commitment, or his/her supervisor, if appropriate, initiates a procurement request in accordance with 1804.7301.

(B) The procurement request and/or accompanying documentation identifies the individual who made the unauthorized commitment, and includes a statement signed by the individual that explains why normal acquisition procedures were not followed, explains why the firm was selected, lists other sources considered, describes the work, and estimates or states the agreed price. If the Government representative who made the unauthorized commitment is no longer available, appropriate program personnel shall provide the information described in this paragraph.

(C) The procurement request is submitted through the director of the cognizant program office at the contracting activity, or comparable official. In the procurement request, the director shall describe measures taken to prevent the recurrence of the unauthorized commitment.

Normally, only GS-1102 and -1105 personnel with the proper training and experience may be appointed contracting officers and only when a valid organizational need can be demonstrated.

A COTR delegation may be made only by the contracting officer cognizant of that contract at the time the delegation is made. If the cognizant contracting officer is absent, the delegation letter may be signed by a warranted contracting officer at any level above the cognizant contracting officer. An individual COTR may have only the duties specifically identified in a written delegation to him or her by name (i.e., COTR duties may not be delegated to a position) and has no authority to exceed them. COTRs should be informed that they may be personally liable for unauthorized commitments. Contracting officer authority to sign or authorize contractual instruments shall not be delegated through a COTR designation or by any means other than a contracting officer warrant.

Signatory authority for determinations and findings (D&Fs) is specified in the FAR or the NFS text for the associated subject matter. The Administrator may make any of the D&Fs that may be made by the Associate Administrator for Procurement or by a contracting officer.

Each D&F, including class D&Fs, shall be reviewed by counsel for form and legality before signature by the approving authority.

Any suspected violations of the clause at FAR 52.203-3, Gratuities, shall be reported to the installation's Office of Inspector General.

(b)(i) When offers are received that, in the opinion of the contracting officer, indicate possible antitrust violations, the contracting officer shall report the circumstances to the General Counsel, NASA Headquarters, through the Office of Procurement (Code HS). Reports should not be submitted automatically but only when there is reason to believe the offers may not have been arrived at independently. These reports shall be submitted with conformed copies of bids or proposals, contract documents, and other supporting data, and shall set forth—

(A) The noncompetitive pattern or situation under consideration;

(B) Purchase experience in the same product or service for a reasonable period (one or more years) preceding receipt of the offers under consideration, including unit and total contract prices and abstracts of bids;

(C) Community of financial interest among offerors, insofar as it is known;

(D) The extent, if any, to which specification requirements or patents restrict competition;

(E) Any information available about the pricing system employed in offers believed to reflect noncompetitive practices; and

(F) Any other pertinent information.

(ii) Evidence of practices that, in the opinion of he General Counsel, NASA Headquarters, may violate the antitrust laws shall be forwarded to the Attorney General of the United States (see FAR 3.303).

(d) The contracting officer shall submit the identical bid report required by FAR 3.303(d) to NASA Headquarters, Office of Procurement (Code HS). The report shall include the reasons for suspecting collusion. Code HS shall forward a copy to the NASA Office of the Inspector General.

Contracting officers shall report suspected violations of the Anti-Kickback Act in accordance with 1809.470.

The Associate Administrator for Procurement has been delegated the authority to authorize an exception to the policy in FAR 3.601. The Associate Administrator for Procurement has redelegated this authority to the heads of contracting activities (HCAs) for individual actions in the aggregate of $100,000 and below, inclusive of follow-on acquisitions, with concurrence by the HCA's Office of Chief Counsel. All requests above the HCA's authority shall be forwarded to the Associate Administrator for Procurement (Code HS) for approval.

(a) The Associate Administrator for Procurement has been delegated authority to void or rescind contracts when there is a final conviction for violation of 18 U.S.C. 201-224 (Bribery, Graft and Conflicts of Interest) relating to them.

Procurement officers shall make reports to the Associate Administrator for Procurement (Code HS). The Associate Administrator for Procurement is responsible for the actions, notices, and decisions required by FAR 3.705(c), (d), and (e).

Procurement officers shall forward one copy of each Disclosure of Lobbying Activities (SF-LLL) furnished pursuant to FAR 3.803 to the Office of Procurement (Code HS). The original shall be retained in the contract file. Forms shall be submitted semi-annually by April 15th for the six-month period ending March 31st, and by October 15th for the period ending September 30th.

The Associate Administrator for Procurement (Code HS) is the designated official to whom suspected violations of the Act shall be referred.

The contracting officer shall include the clause at FAR 52.204-1, Approval of Contract, in solicitations, contracts, and supplemental agreements that require higher level approval. For actions requiring Headquarters approval, insert “NASA Associate Administrator for Procurement” in the clause's blank space.

(a) Contract effective date means the date agreed upon by the parties for beginning the period of performance under the contract. In no case shall the effective date precede the date on which the contracting officer or designated higher approval authority signs the document.

(b) Costs incurred before the contract effective date are unallowable unless they qualify as precontract costs (see FAR 31.205-32) and the clause prescribed at 1831.205-70 is used.

In addition to the requirements in FAR 4.201, the contracting officer shall distribute one copy of each R&D contract, including the Statement of Work, to the NASA Center for AeroSpace Information (CASI), Attention: Document Processing Section, 7121 Standard Drive, Hanover, MD 21076-1320.

Instead of using the last page of the contract to provide the information listed in FAR 4.203, NASA installations may allow contracting officers to use a different distribution method, such as annotating the cover page of the payment office copy of the contract.

(b) NASA industrial security policies and procedures are prescribed in NMI 1600.2, NASA Security Program. (See also 1842.202-72).

The contracting officer shall insert the clause at 1852.204-75, Security Classification Requirements, in solicitations and contracts if work is to be performed will require security clearances. This clause may be modified to add instructions for obtaining security clearances and access to security areas that are applicable to the particular acquisition and installation.

This section implements the acquisition-related aspects of Federal policies for assuring the security of unclassified automated information resources.

NASA policies and procedures on automated information security are prescribed in NMI 2410.7, Assuring the Security and Integrity of NASA Automated Information Resources, and in NHB 2410.9, NASA Automated Information Security Handbook, Chapters 3 and 4. Security requirements for safeguarding sensitive information in unclassified Federal computer systems are required in:

(a) Contracts for automatic data processing equipment, software, the management or operation of Data Processing Installations (DPIs) or related services; and

(b) Contracts under which contractor personnel must have physical or electronic access to sensitive automated information, or automated information that supports mission-critical functions.

When considered appropriate for contract performance, the contracting officer, with the concurrence of the requiring activity and the center automated information security (AIS) manager, may require the contractor to submit for post-award Government approval a detailed Security Plan for Unclassified Federal Information Technology Systems. The plan shall be required as a contract data deliverable that will be subsequently incorporated into the contract as a compliance document after Government approval. The plan shall demonstrate thorough understanding of NMI 2410.7 and NHB 2410.9, and shall include, as a minimum, the security measures and program safeguards to ensure that the information technology resources acquired and used by contractor and subcontractor personnel:

(a) Operate effectively and accurately;

(b) Are protected from unauthorized alteration, disclosure, or misuse of information processed, stored, or transmitted;

(c) Can maintain the continuity of automated information support for Government missions, programs, and functions;

(d) Incorporate management, general, and application controls sufficient to provide cost-effective assurance of the system's integrity and accuracy; and

(e) Have appropriate technical, personnel, administrative, environmental, and access safeguards.

The contracting officer shall insert the clause substantially as stated at 1852.204-76, Security Requirements for Unclassified Automated Information Resources, in solicitations and contracts involving unclassified automated information resources. Paragraph (a) of the clause shall be completed with information supplied by the cognizant requiring activity.

The NASA Acquisition Internet Service (NAIS) provides an electronic means for posting procurement synopses, solicitations, procurement regulations, and associated information on the Internet.

(a) The NAIS Electronic Posting System (EPS) enables the NASA procurement staff to:

(1) Electronically create and post synopses on the Internet and in the Commerce Business Daily (CBD); and

(2) Post solicitation documents, including solicitation amendments or cancellations, and other procurement information on the Internet.

(b) The EPS maintains an on-line index linking the posted synopses and solicitations for viewing and downloading.

(c) The EPS shall be used to:

(1) Create and post all synopses in accordance with FAR part 5 and NFS 1805; and

(2) Post all competitive solicitation files, excluding large construction and other drawings, for acquisitions exceeding $25,000.

(d) The NAIS is the official site for solicitation postings. In the event supporting materials, such as program libraries, cannot be reasonably accommodated by the NAIS, Internet sites external to NAIS may be established after coordination with the Contracting Officer. Such sites must be linked from the NAIS business opportunities index where the solicitations reside. External sites should not duplicate any of the files residing on the NAIS.

The Headquarters Office of Procurement (Code HS) is responsible for meeting the requirements of FAR 4.601, based on installation submission of Individual Procurement Action Reports (NASA Form 507 series) data.

(d) Code HS is responsible for requesting, obtaining, and reporting Contractor Establishment Codes to the FPDS.

The Individual Procurement Action Report and Supplements (NASA Form 507 series) provide essential procurement records and statistics through a single uniform reporting program as a basis for required recurring and special reports to Congress, Federal Procurement Data Center, and other Federal agencies. The preparation and utilization of the NASA Form 507 series are integral parts of the agencywide Financial and Contractual Status (FACS) system.

The following procurement actions are individually reportable and require the completion of one or more of the forms in the 507 series.

(a) Initial basic procurements. (1) All contracts, regardless of dollar obligation amount.

(2) All grants, cooperative agreements, and funded Space Act agreements.

(3) Intragovernmental procurements and purchase orders when the initial value is more than $25,000.

(4) All purchase orders for advisory and assistance services.

(5) Purchase orders of $25,000 or less for services within the four designated industry groups identified at FAR 19.1005(a) under the Small Business Competitiveness Demonstration Program. (These actions are not FACS reportable, but are required for FPDS reports.)

(b) Modifications. Modifications that

(1) Obligate or deobligate funds, regardless of dollar amount,

(2) Change the estimated cost and/or fee,

(3) Extend the completion date, or

(4) Add or change procurement statistics previously reported.

The FACS report shall have information as of the last day of the month and shall arrive in NASA Headquarters not later than the close of business on the fifth work day following each month being reported. The installation procurement officer should establish an agreement with the installation financial officer on a cut-off date for processing contractual documents to ensure that the FACS procurement submission and the FACS financial submission for the month include the same contracts.

(a) The information required by the following forms shall be provided when submitting individual Procurement Action Reports:

(1) New contract awards—NASA Forms 507, 507A, and 507B.

(2) New grants, cooperative agreements, funded Space Act agreements, intragovernmental agreements, and orders against federal supply schedules—NASA Forms 507G and 507B.

(3) Modifications to any procurement action—NASA Forms 507M and, if necessary, 507B.

(b) The NASA Forms 507 series shall be prepared in accordance with instructions issued by Code HS. These instructions will be issued and updated through Procurement Information Circulars (PICs).

NASA Form 1356, C.A.S.E. Report on College and University Projects, shall be prepared for awards to nonprofit institutions of higher education or to nonprofit institutions that are operationally affiliated or integrated with an educational institution. Information on this form is used to produce reports required by the National Science Foundation and to respond to inquiries. Submission is required regardless of instrument type (contract, grant, cooperative agreement, or funded Space Act agreement) and type of proposal (solicited or unsolicited). Instructions appear on the form itself and constitute the detailed guidance for preparation and submission. The form, which is either included with the acquisition package or initiated by the contracting office, shall be completed, reviewed, and promptly forwarded upon award to the Headquarters Office of Human Resources and Education (Code FE).

When a contract is unclassified, classified material relating to that contract shall be maintained in a separate file folder and container, and the unclassified folder shall be marked to indicate the location of the classified material. The front and back of each folder containing classified material shall be marked with the highest classification assigned to any document in the folder.

NASA Form 1098, Checklist for Contract Award File Content, shall be used as the “top page” in contract files.

(b) Upon receiving the NASA Form 1611 or DD Form 1594, Contract Completion Statement, from the contract administration office and complying with FAR 4.804-2(b), the contracting officer shall complete the form.

(a) When the contracting office retains contract administration (excluding acquisitions under the simplified acquisition threshold), the contracting officer shall comply with FAR 4.804-5(a) by completing NASA Form 1612, Contract Closeout Checklist, and DD Form 1593, Contract Administration Completion Record.

(b) To comply with FAR 4.804-5(b), the contracting officer shall complete NASA Form 1611 or DD Form 1594, Contract Completion Statement, except for acquisitions under the simplified acquisition threshold.

(a) See NPG 1441.1C, Records Retention Schedules.

(a) Upon determination of contract completion under the procedures outlined in 1804.804, each office shall remove the official contract files from the active file series, mark each file folder with “Completed (Date)”, and place the folder in a completed (inactive) contract file series. Separate series should be established for contracts of $25,000 or less and for contracts of more than $25,000, to facilitate later disposal. Any original or official file copies of documents contained in duplicate or “working” contract files shall be removed and placed in the appropriate official file; any remaining material in the duplicate or “working” file shall be destroyed immediately or segregated and marked for early disposal.

(b) Each office shall review contractor “general” files (i.e., a file containing documents relating generally to a contractor rather than a specific contract) at least once annually and remove documents that—

(1) Are obsolete or superseded documents relating generally to the contractor (e.g., documents no longer pertinent to any aspect of a contractor's current or future capability, performance, or programs, and documents relating to a contractor that is no longer a possible source of supplies, services, or technical assistance) and dispose of the documents as authorized in 1804.805; or

(2) Pertain only to completed contracts. Place those files that are not routine in nature in inactive files for later disposal, and immediately dispose of routine documents as authorized in NPG 1441.1C, Records Retention Schedules.

Each NASA installation, that has its own employer identification number, may elect to report to the IRS payments under purchase orders and contracts for merchandise and other exempt bills.

This subpart contains policies and procedures applicable to the transfer of contracts between NASA installations.

Transfer of a contract, as used in this subpart, means that process whereby a contract and all future responsibility for a contract held by one installation are transferred or reassigned in writing to another installation.

(a) The approval authority for requests to transfer a contract is the official in charge of the cognizant Headquarters program office or designee. Requests for approval shall be submitted by the director of the transferring installation after receiving the concurrence of the director of the receiving installation. Concurrence of the Associate Deputy Administrator (Code AI) is also required for a transfer where an installation's roles and missions may be affected.

(b) Approval of a program transfer by the cognizant Headquarters official constitutes approval to transfer program-related contracts.

The contracting officer of the transferring installation shall take the following steps before transferring the contract:

(a) Agree on a plan and schedule with the contracting officer of the receiving installation for transferring contract responsibility and contract files.

(b) Coordinate with the following offices:

(1) Financial Management Office, to determine the contract financial records to be transferred and the method, timing, and dollar amount of such transfers.

(2) Technical (Engineering and Project) Office, to determine the status of any outstanding engineering changes.

(3) Reliability and Quality Assurance Office, to determine status and method of transferring the reliability and quality assurance functions.

(4) Industrial Property and Facilities Office, to determine the method of transferring the Government property records.

(5) Transportation Office, to determine the status of bills of lading furnished the contractor.

(6) Security Office, to determine whether any classified material is outstanding and whether special precautions are necessary during the transfer process.

(7) Other organizational elements, to determine the status of any other actions such as new technology, materials reports, PERT, and safety.

The contracting officer of the transferring installation shall prepare an inventory of the contract file. This inventory shall also include a separate listing of all outstanding requests for contract administration assistance issued to other Government agencies, indicating the name and address of the agency office, functions requested to be performed, estimated cost of the services, and estimated reimbursement due the administration agency for the services yet to be performed for each requested function. Copies of this inventory shall be provided to the contracting officer of the receiving installation.

The contracting officer of the transferring installation shall provide written notification of the planned transfer to the contractor and all agencies performing or requested to perform administration services.

(a) Upon completion of the actions described in 1804.7003-1 through 1804.7003-3, the contracting officer of the transferring installation shall issue a letter to the contractor, agencies performing contract administration functions, contracting officer representatives, and the contracting officer of the receiving installation. This letter shall provide notification of the transfer date, termination of appointment of the contracting officer's representatives, and the name, mailing address, and telephone number of the contracting officer of the receiving installation.

(b) After issuing the letters described in 1804.7003-4(a), the contracting officer of the transferring installation shall send the contract file to the contracting officer of the receiving installation with a letter transferring contract responsibility. This letter shall contain a provision for acceptance of the responsibility for the contract and its related files by the contracting officer of the receiving installation.

The contracting officer of the transferring installation shall retain for permanent file a copy of the approvals and concurrences required by 1804.7002, the transfer acceptance letter of the contracting officer of the receiving installation, and any additional documents necessary for a complete summary of the transfer action.

The contracting officer of the receiving installation shall review the contract, letters of request, actions in process, and other related files and to request corrective action, if necessary, before the official transfer of the contract. This review may be waived by written notification to the contracting officer of the transferring installation.

The contracting officer of the receiving installation shall—

(a) Provide the contracting officer of the transferring installation written acceptance of contract responsibility and receipt of the contract files;

(b) Inform all offices affected within the installation of the receipt of the contract;

(c) Appoint new contracting officer's technical representatives, as necessary;

(d) Issue a contract modification to provide for the administrative changes resulting from the transfer action (e.g., identifying offices responsible for performing contract administration and making payment and the office to which vouchers, reports, and data are to be submitted);

(e) Provide copies of the contract documents to affected installation offices; and

(f) If appropriate, supplement the letter of request to the Government agency providing contract administration services to reflect the changes resulting from the transfer action. The supplement may terminate or amend an existing contract administration support arrangement or may request support in additional areas.

This subpart contains the procedures for uniform numbering of NASA solicitations, contracts (including letter contracts), purchase orders (including requests to other Government agencies), basic ordering agreements, other agreements between the parties involving the payment of appropriated funds or collection of funds for credit to the Treasury of the United States, and modifications or supplements to these instruments.

(a) Contractual documents shall be numbered with approved prefixes and serial numbers as prescribed in this subpart. If other identification is required for center purposes, it shall be placed on the document in such a location as to clearly separate it from the identification number.

(b) The identification number shall consist of not more than 11 alpha-numeric characters positioned as prescribed in this subpart and shall be retained unchanged for the life of the particular instrument.

(a) Approved prefixes are as follows:

(b) The contract prefix shall be used for the following documents:

(1) Contracts, including letter contracts, indefinite-delivery contracts, utilities, leases of real property and renewals.

(2) Easements.

(3) Basic ordering agreements.

(4) Other written agreements involving payment or receipt of funds not covered by 1804.7102(e).

(c) Contracts totally funded under reimbursable arrangements with the department of Energy shall use a DEN prefix instead of the NAS prefix (e.g., DEN 8 for Marshall).

(d) Space Act agreements awarded under the authority of Section 203(c)(5) or 203(c)(6) of the Space Act shall use an NCA prefix instead of the NAS prefix (e.g., NCA 8 for Marshall).

(e) The purchase order prefix shall be used for purchase orders (including blanket purchase agreements) and requests to other Government agencies to furnish supplies or services.

(f) Solicitations shall be numbered in accordance with installation procedures, except that in all cases the identifying number shall begin with the portion of the installation's contract prefix following “NAS.”

(g) If a prefix is required for an installation or office not listed in this section, a request for a prefix assignment shall be submitted to the Headquarters Office of Procurement (Code HS).

(a) Installations shall number contracts and agreements identified in 1804.7102(b) serially by fiscal year. The serial number shall be five digits beginning with a two-digit fiscal year identifier followed by a three digits commencing with “001” and continuing in succession. For example, the first contracts awarded by Ames Research Center in fiscal year 1997 shall be numbered NAS 2 97001 and NAS 2 97002. Fiscal year identification is optional for Space Act agreements.

(b) Serial number for purchase orders shall be assigned serially without fiscal year identification. When the series of numbers exceeds five digits (over 99,999), a new series shall be used, beginning the series with number “1” and followed by the capital letter “A.” Should additional series become necessary, they will be distinguished by the capital letters “B,” “C,” and so forth, as may be required, except that the letters “I” and “O” shall not be used.

(a) Modifications of definitive or letter contracts or agreements shall (1) bear the same identification as the contract or agreement being modified and (2) be numbered consecutively for each contract or agreement, beginning with Modification Number 1, regardless of whether the modification is accomplished by unilateral or bilateral action. Except for termination notices, modifications shall be effected by the use of Standard Form 30, Amendment of Solicitation/Modification of Contract.

(b) Definitive contracts superseding letter contracts shall retain the same contract number as that originally assigned to the letter contract. Actions definitizing letter contracts are considered modifications and shall be assigned modification numbers in accordance with paragraph (a) of this section.

(a) Requests for approval of contracts and supplemental agreements by the Associate Administrator for Procurement shall be submitted to the Headquarters Office of Procurement (Code HS) in sufficient time to allow a minimum of 15 days for review.

(b) Each request for approval shall be accompanied by (1) five copies of the contractual document, one of which has been executed by the contractor and contracting officer, and (2) the official contract file containing the appropriate documentation as set forth in FAR 4.803(a). However, for the items specified in FAR 4.803(a) (10), (11), and (12), the contracting officer shall provide documentation pertaining only to the successful offeror; and, in lieu of the items specified in FAR 4.803(a)(26) (ii) and (iii), the contracting officer shall provide an index briefly describing the content of all previous modifications.

(c) The approval required under this section shall be made by signature of the Associate Administrator for Procurement on the contract/supplemental agreement.