|
|
MOSIS Automated E-mail System
MOSIS makes this e-mail system available for customers who cannot
access the Word Wide Web to use the MOSIS
Web
Forms, or do not have an FTP client to transmit design files.
|
|
1. Introduction
-
MOSIS customers with access to the World Wide Web can request
information, submit projects, check the status of a wafer run, or ask
questions of the MOSIS staff by using MOSIS
Web
Forms. If you have access to the Word Wide Web, you will find the
web forms easy to use.
Customers without access to the World Wide Web can use the MOSIS
electronic mail (e-mail) system, sending their requests to
mosis@mosis.com. Software developed by MOSIS, using a format called
the MOSIS Command Language, interprets these e-mail requests
automatically. This enables MOSIS to serve thousands of users with a
very small staff.
-
2. Request Message Format
-
All MOSIS Request Messages have three parts:
-
1. Request
-
For example,
REQUEST: STATUS.
A list of all
available requests is presented in
Section 4.
2. Parameter
-
Each request has various parameters that
can go with it. The
REQUEST: STATUS
example above will be followed by the parameters DESIGN-NUMBER and
DESIGN-PASSWORD.
3. End
-
Entering the line REQUEST: END marks the end of requests in a message.
Any text written after this line will be ignored. To append two or
more requests, remove the REQUEST: END line between them otherwise
only the first request will be parsed.
For example, a message to MOSIS requesting the status of a project
before fabrication begins would look like this:
-
REQUEST: STATUS
DESIGN-NUMBER:
99999
DESIGN-PASSWORD:
pqrst465
REQUEST: END
Parameter names are case independent. No control codes other than
<CR>, <LF>, <TAB>, or <FF> should be used.
Net-Address Parameter:
Normally MOSIS addresses its replies to your requests according to the
Reply-To field in your message header. The only time this is not true
is when you are submitting a
NEW-PROJECT
or
FABRICATE
request. Because these
templates
contain a NET-ADDRESS
parameter that overrides the Reply-To field, it's important to fill
this in properly. If there is a problem with the NET-ADDRESS
parameter, or if the specified design number is not valid,
i.e.,
does not exist or is not accompanied by the proper
DESIGN-PASSWORD
then MOSIS will direct its response to the Reply-To
field. Input to the NET-ADDRESS parameter can contain multiple
addresses, separated by commas, all on one line of up to 255
characters.
-
3. Project Submission Sequence
-
There are four stages within the submission sequence that define
whether MOSIS has a valid layout file for your project and where the
project is in the sequence. The following sections describe the major
MOSIS requests in the context of these four stages:
-
Requesting a Design Number
-
Requesting Fabrication
-
Notice of Layout Queued for Fabrication
-
Notice of Project Being Fabricated
-
4.1 Requesting a MOSIS Design Number
-
The first step is to obtain a MOSIS design number by sending a
NEW-PROJECT request to
mosis@mosis.com. MOSIS will reply to this request by sending you
a five-digit number which is the unique identifier for your project.
You must refer to this design number in all subsequent communications
to MOSIS concerning this project.
-
4.2 Requesting Fabrication
-
After you have received a MOSIS design number, you can send your
design file to MOSIS using a
FABRICATE
request. If your layout file is extremely large, we recommend sending
it in fragments or using the LAYOUT-FRAGMENT parameter. MOSIS will
check the syntax of your layout file before queueing it for
fabrication. This syntax and bondability review is called
PROJECT-CHECK. If there are problems with
your layout file, MOSIS will notify you so you may correct the file
and resubmit it.
Making Changes:
You can change the parameters you submitted for your project by
e-mailing an
UPDATE request to
mosis@mosis.com. The UPDATE request does not affect your layout
file. See Section 3.3 for layout modification
instructions.
-
3.3 Notice of Layout Queued for Fabrication
-
Once your layout file passes PROJECT-CHECK, you will receive an
acknowledgment from MOSIS that your project is queued for fabrication.
This means your project will be fabricated on the next scheduled run
that includes your TECHNOLOGY-CODE.
Cancelling Fabrication and Updating the Layout:
- A.
CANCEL-FABRICATION
-
To modify a layout currently queued for fabrication, first submit a
CANCEL-FABRICATION request. That will remove the file from queue and
still preserves all of the information previously submitted, including
the five-digit design number. After requesting CANCEL-FABRICATION,
you are able to submit a new layout file for fabrication, using the
same five-digit design number.
If you do not plan to submit a new layout file, or wish to submit it
under a different account number, use CANCEL-PROJECT instead of
CANCEL-FABRICATION.
-
B.
CANCEL-PROJECT
-
Use this request to cancel your project in its entirety.
-
4.4 Notice of Project Being Fabricated
-
After your project is place on a fabrication run, MOSIS will send you
a "being fabricated" message. This message will include a new ID
called a Fab-ID, which is a unique identifier for this particular
fabrication of your project. A Fab-ID (like T17XAB) consists of two
parts: a 4-character Run ID (like T17X) and a 2-letter ID (like AB)
for your project on the run. If you later ask MOSIS to refabricate
your design, your design number will remain the same, but a new
Fab-ID will be assigned for each new fabrication of the project.
-
4. MOSIS Requests
-
See
Section 5 for a complete list of parameters that can be used with
the following requests.
-
REQUEST: ATTENTION
-
Directs your message to the attention of the MOSIS staff.
-
REQUEST: CANCEL-FABRICATION
-
Cancels previously requested fabrication of a project, but retains
design number for future use. Use when you want to submit a new
layout file under existing design number.
-
REQUEST: CANCEL-PROJECT
-
Withdraws project completely, cancels design number.
-
REQUEST: END
-
Terminates all requests in a message. Anything in your message
following this line will be ignored.
-
REQUEST: FABRICATE
-
Puts project in queue to be fabricated on next run of appropriate
technology.
-
REQUEST: NEW-PROJECT
-
Requests the creation of a new project and the assignment of a new
design number.
-
REQUEST: REPORT
-
Use for sending follow-up report on the performance of fabricated
projects.
-
REQUEST: STATUS
-
Requests project status.
-
REQUEST: UPDATE
-
Use for modifications of project parameters.
Standard Submissions:
The standard submission style includes two templates in this order:
NEW-PROJECT, then
FABRICATE. It is possible to expedite submission by combining a
few steps
(One-Step
Submission). Sometimes it is necessary to fragment large layout
files and send each
fragment individually.
Avoiding Delays:
Accurate syntax is very important in avoiding error and delay in
project submission and in all communication with MOSIS. Remember also
that common network problems can cause your project to be received too
late for inclusion on the desired run. Please don't wait until the
last minute to submit your project, since this will increase the
probability that you won't make the run. Use the MOSIS mail system to
make sure that you have the most up-to-date copy of important
documents, like the
fabrication
schedule.
Response Time:
Response time varies according to network load, number of messages
being processed by MOSIS, etc. Under normal circumstances, the MOSIS
software can automatically respond to a request within 10 minutes. If
a response is not received within one hour, please contact us via
phone or fax to determine the cause of the delay. This applies only
to messages that can be interpreted automatically using the MOSIS
Command Language. Messages directed to MOSIS staff are generally
answered within two business days.
-
5. Parameters for MOSIS Requests
-
See
Section 4 for a complete list of MOSIS requests.
-
ATTENTION
<1 line>
-
Special handling for a project.
-
BONDING-DIAGRAM-SUPPLIER
<1 line>
-
The source of the bonding diagram used to package your project. Select
"MOSIS" if you want MOSIS to attempt to generate a bonding diagram
automatically. Select "Customer" if you will supply a bonding
diagram. Customer-supplied bonding diagrams should be faxed to MOSIS
Packaging Manager at 310.823.5624. Leave this field as blank if you
did not provide a PACKAGE-NAME or
QUANTITY-PACKAGED. Please note that MOSIS can
only attempt automatic bonding diagram generation for
Ceramic
Packages Available From MOSIS; for plastic packages, you must
select
"Customer" and supply a bonding diagram.
-
COMMENTS
<n lines>
-
Any additional comments you want to make about your design or the
quality of the parts you received from MOSIS.
-
CRC-CHECKSUM
<number> <number>
-
Pair of numbers (separated by white space) computed for a layout
design file or fragment to help determine the integrity of the
received file or fragment. The CRC-CHECKSUM parameter should be used
when you computed the checksum of your design file using the MOSIS CRC
checksum program.
CRC-CHECKSUM checks the accuracy of GDS or CIF layout files sent from
your computer to MOSIS, either via magnetic tape or over a computer
network. To compute the CRC checksum, you must run the MOSIS CRC
checksum program on your CIF or GDS design file (before any
compression or encoding) and send the values (described below) to
MOSIS. If you send your layout in fragments, the CRC checksum program
must be run on each fragment. MOSIS will then compute the
CRC-CHECKSUM of the received file or fragment to verify that it was
transmitted correctly.
The program that computes the MOSIS CRC checksum for a file is
provided in two formats:
When you run the program, you must
specify either the "-b" switch (for a binary file, such as GDS) or
the "-t" switch (for a text file, such as CIF).
The program displays two numbers: a checksum and a count.
Submit the CRC-CHECKSUM parameter as "CRC-CHECKSUM: <checksum>
<count>"
with white space or a comma between the checksum and the computed byte
count. Checksum is computed on the entire original design file, before
any compression or encoding. If the file is
transmitted in smaller fragments, the checksum should be computed
on each fragment.
Text design files (CIF format) may undergo several trivial
modifications during
file transmission, such as replacing EOLs or <CR>s by
<CR><LF>s, addition/deletion of nulls and of trailing
spaces, conversion of TABs into SPACEs, and addition of
spaces/<CR>s at either end of the file. CRC-CHECKSUM is
insensitive to these minor changes.
CRC-CHECKSUM can be used with the FABRICATE request. When MOSIS
receives the file or fragment, if there is a mismatch between MOSIS'
computed checksum and the supplied checksum, the file is rejected and
MOSIS notifies the designer. If only one fragment is rejected, MOSIS
will retain the rest of the fragments and only that fragment should be
resubmitted.
-
CUSTOMER-ACCOUNT-NUMBER
<1 line>
-
Identifies the MOSIS Customer Account to be charged for a project.
-
CUSTOMER-ACCOUNT-PASSWORD
<1 line>
-
Contains the account password from the MOSIS database
assigned to this account.
-
DESCRIPTION
<n lines>
-
A description of the project.
-
DESIGN-KIT-VERSION
<1 line>
-
IBM design technologies only. Version of design kit you used to
design your project. Required for IBM design technologies. Leave blank
for other technologies.
-
DESIGN-NAME
<1 line>
-
Short name for the project, e.g., ADDER.
-
DESIGN-NUMBER
<number>
-
Provides the unique five-digit identification
number assigned to the project by MOSIS.
-
DESIGN-PASSWORD
<1 line>
-
Arbitrary password assigned to the project by the user
in the
NEW-PROJECT
request.
-
DESIGN-SIZE
<x dimension> x <y dimension>
-
Specifies the size of the project in microns.
-
DESIGN-TYPE
<1 line>
-
The design type of your project (Digital, Analog, Mixed-Signal, etc).
-
EMAIL-ADDRESS
<1 line>
-
For REQUEST: REPORT only. The e-mail address of the person submitting
the report. If you are submitting the report on behalf of someone else
(e.g., an administrative assistant submitting a report for a
university professor), you should use the e-mail address of the person
for whom you are submitting the report.
-
FAB-ID
<1 line>
-
When a design is placed on a fabrication run, it is assigned a
Fab-ID, which identifies a particular fabrication of a design. If
you ask MOSIS to refabricate your design on additional fabrication
runs,
you will receive a new Fab-ID for each refabrication.
The Fab-ID (like T17XAB) consists of two parts:
-
a four-character Run ID which identifies the wafer fabrication run
("T17X")
-
a two-letter ID which identifies for your design on the run ("AA").
-
FAB-OPTIONS
<1 line>
-
Currently applicable only for TSMC 0.18 and TSMC 0.25 fabrications to
specify an option not determined by the layout.
These are the only combinations available. The EPI and
thick-top-metal combination is not a standard offering.
Separate multiple options with white space or a comma.
|
Subtrait
|
Top Metal
|
|
None
|
|
EPI¹ or NON-EPI (don't care)
|
Standard metal
|
|
EPI¹
|
Standard metal
|
|
Non-EPI
|
Standard metal
|
|
Non-EPI
|
Thick top metal
|
¹ Epitaxial-type wafers, when available, are so at an
additional cost
Any update will not add to but will replace previous requests; "none"
will remove all requested options.
-
FAILURE-CAUSES
<n lines>
-
For REQUEST: REPORT only. The reason(s) your parts failed or did not
work as expected. If you're not sure of the reasons, give your best
guess. Leave blank if your parts worked as expected.
-
FILE
<1 line>
-
To request status of a run.
-
FILL-AUTHORIZED
<1 line>
-
Some processes impose minimum density requirements on certain layers
to facilitate Chemical Mechanical Polishing (CMP). The designer
should design the project so that these density requirements are met.
Normally, MOSIS does not add any fill to projects to bring layer
densities up to the required minimums. If you choose "Yes", you
authorize MOSIS to add fill to your project. Note that there may not
be enough open area in your project to add the required amount of
fill, so authorizing MOSIS to add fill does not guarantee that density
requirements will be met. Also note that adding fill may change the
characteristics of your circuit. For more information, see the
the
Filling Layout for Chemical Mechanical Polishing section of the
Design Issues FAQ.
-
FOUNDRY
<1 line>
-
Specifies the name of foundry or foundries that are
acceptable to the designer for fabrication. It is not necessary to
use this parameter when specifying a foundry-specific technology,
e.g., AMI_C5N, since a foundry is already implied; however,
you should use this with vendor-independent design technologies.
To remove any previously specified foundry restrictions and allow
fabrication at any foundry, use a value of "ANY".
-
INTENDED-DISPOSITION
<1 line>
-
Required by export control regulations
What you ultimately plan to do with this design.
There are three options. Chose only one.
-
Choose Production for
all production stages, such as product engineering, manufacture,
integration, etc.
-
Choose Development for all stages prior to serial
production.
-
Choose Research if this design is a research project for
which you intend to publish results of the design/software in publicly
available resources.
-
IP-INCLUDED
<1 line>
-
Some designs include intellectual property (IP) licensed from another
party (for example, Artisan). If your design includes licensed IP,
you must choose "Artisan" if the IP is licensed from Artisan or
"Other" if the IP is licensed from some other vendor. This will allow
MOSIS to help you meet your contractual obligations with respect to
that property. For Artisan, please fill out the
Artisan tapeout form and fax to 310-823-5624, attention MOSIS
Customer Support. NOTE: you can use the UPDATE request and specify
"None" if you previously chose "Artisan" or "Other" by mistake.
-
LAMBDA
<number>
-
Specifies the value of lambda (in microns) that
applies to this project. Lambda must be provided for all scalable
technologies. Projects using a non-scalable TECHNOLOGY-CODE do not
need to
provide this parameter; it will be ignored if supplied.
-
LAYOUT
<n lines to end of message or to next line starting with
REQUEST>
-
The project design file. Note: The keyword LAYOUT has no
arguments but is followed on the next and subsequent lines by the
project design itself.
Note also that the LAYOUT design must be the last item in the request.
Lines that follow the LAYOUT, but which do not begin with REQUEST:,
will be considered part of the LAYOUT. For example, if the line
"ATTENTION:<text>" is placed following the LAYOUT text in a
FABRICATION request, it will be considered part of the design file and
will not be processed.
To help insure design file integrity, it is strongly recommended that
the LAYOUT be explicitly terminated with another REQUEST, e.g.,
REQUEST: END, rather than simply allowing it to be terminated by the
end of the message.
-
LAYOUT-CHECKSUM
<number> <number>
-
Note: The CRC-CHECKSUM parameter specifies
a CRC checksum computed via a a more reliable algorithm. You should
use it if possible. We still accept the LAYOUT-CHECKSUM parameter,
but may discontinue support for it in the future.
Pair of numbers (separated by white space)
computed for a layout design file or fragment to help determine the
integrity of the received file or fragment.
LAYOUT-CHECKSUM checks the accuracy of message files sent from your
computer to MOSIS, either via magnetic tape or over a computer
network. To use LAYOUT-CHECKSUM you must run the program on your CIF
or uu-encoded GDS design file and send the values (described below) to
MOSIS. MOSIS will then compute the LAYOUT-CHECKSUM of the received
file to verify that the file, as transmitted, is complete.
The program that computes traditional checksum values is no longer
provided. If you do not yet have a MOSIS checksum program, you
should use the CRC-CHECKSUM parameter instead and obtain the
program that computes the CRC checksum. See the
CRC-CHECKSUM parameter for more
information.
Submit LAYOUT-CHECKSUM as "LAYOUT-CHECKSUM: <checksum>
<count>"
with white space or a comma between the checksum and the computed byte
count. Checksum is computed on the entire file or, if the file is
transmitted in smaller fragments, LAYOUT-CHECKSUM should be computed
on each fragment.
Layout design files may undergo several trivial modifications during
file transmission, such as replacing EOLs or <CR>s by
<CR><LF>s, addition/deletion of nulls and of trailing
spaces, conversion of TABs into SPACEs, and addition of
spaces/<CR>s at either end of the file. LAYOUT-CHECKSUM is
insensitive to these minor changes.
LAYOUT-CHECKSUM refers to the actual file in that submission, whether
it is an entire file, a single LAYOUT-FRAGMENT, or a file obtained via
LAYOUT-FTP-PATH.
LAYOUT-CHECKSUM can be used with the FABRICATE request. When MOSIS
receives the file or fragment, if there is a mismatch between MOSIS'
computed CHECKSUM and the supplied CHECKSUM, the file is rejected and
MOSIS notifies the designer. If only one fragment is rejected, MOSIS
will retain the rest of the fragments and only that fragment should be
resubmitted.
-
LAYOUT-FORMAT
<1 line>
-
Use this to specify the format for the design file (CIF or GDS) and
any transformations you made to the layout before sending it. The
first word must be CIF or GDS to indicate the basic format of your
design file. You can follow this with a sequence of words that
indicates transformations you made to the layout. Order of words is
important and indicates the order in which the transformations were
made. Allowed transformation words are:
-
compressed
-
File was compressed with gzip, pkzip, compress or pack
-
base64
-
File was encoded in base64 (also known as Radix 64 or
ASCII armor)
-
uuencoded
-
File was uuencoded
-
quoted
-
File was encoded in quoted-printable
-
fragmented
-
File was broken into fragments
For example, a layout format of "GDS compressed" indicates a GDS file
which has been compressed. A format of "CIF compressed base64"
indicates a CIF file which has been compressed and then base64-encoded
so that it can be sent via e-mail. We will continue to accept a
layout format of UUGDS (equivalent to "GDS uuencoded") for
backward compatability.
Note: If format is GDS, the TOP-STRUCTURE parameter must be included.
-
LAYOUT-FRAGMENT
<n lines>
-
Use to send your layout file in fragments. First line must contain
K
/
N,
where
N
is the total number of fragments and
K
is the chronological number of the fragment. The layout fragment
itself should begin on the line following the LAYOUT-FRAGMENT
parameter.
-
LAYOUT-FTP-PATH
<1 line>
-
Your file can be retrieved by MOSIS using LAYOUT-FTP-PATH if your host
implements the Internet's TCP/IP FTP protocol and if it runs an "FTP
server." Your file protection must also allow this FTP access.
MOSIS will make an initial attempt and two retries to retrieve your
file
and will notify you at the completion of successful transfer or if the
transfer attempts fail. If successful, the message you receive from
MOSIS will include the LAYOUT-CHECKSUM for your file. If you provide a
LAYOUT-CHECKSUM with the LAYOUT-FTP-PATH, MOSIS stores this
information for comparison after the file is retrieved.
Send an ATTENTION request to MOSIS to obtain instructions on the FTP
of layout design file fragments:
Specify the LAYOUT-FTP-PATH with a one-line parameter of the following
form:
LAYOUT-FTP-PATH: !hostname!username!password!filename
WHERE:
-
hostname
-
The name of the Internet host or IP address
-
username
-
The name of a user on that host who can log in via FTP
(if no user name is needed, the field may be left empty)
-
password
-
The literal password needed for the FTP login (may be
optional).
If the user is 'anonymous' and the password is not provided,
then 'mosis@mosis.com' will used.
-
filename
-
The name of the layout design file or file path
NOTE: The example below uses "!" as the field delimiter.
-
REQUEST: FABRICATE
DESIGN-NUMBER: 67890
DESIGN-PASSWORD: HELLO THERE
LAYOUT-FTP-PATH: !HOST.ISI.EDU!USERNAME!PASSWORD!FILE.CIF
LAYOUT-FORMAT: CIF
TOP-STRUCTURE: CHIP
CRC-CHECKSUM: 1234567,23456
REQUEST: END
-
LAYOUT-FTP-SEND-AUTH
<1 line>
-
The design file FTP server allows customers to transfer their design
files to MOSIS using any FTP client program.
To use the design file FTP server to transfer your file to MOSIS, you
must first request fabrication for your design and specify that you
will send the file to us. The fabrication request must include the
following information:
-
Host name or IP address from which you will login to the design file
FTP server
-
Password you will supply to the server when you login. Passwords are
case-sensitive. (You must supply the project's design number as the
user name)
-
Name of file you will store on the server
-
(Optional) Number of hours until transfer authorization expires.
Transfer must be initiated before authorization expires. Default is 8
hours if not specified and the maximum allowed is 24 hours.
If the fabrication request is accepted, you can then login to the
design file FTP server at "ftp.design.mosis.com" and send your file.
You are automatically connected to the right directory when you login
so there is no need to change to the proper directory.
The server displays a session number when you first connect to it and
a communication number when you successfully login. These numbers can
help MOSIS Customer Support quickly locate the transcript of your FTP
session if you need assistance. The server will close the connection
if there is no activity for a period of time or if you fail to make
progress towards logging in and sending your file.
For security reasons, the server allows logins only when all of the
following conditions are met:
-
An unexpired "send" transfer request for your design number exists;
-
You supply the design number as user name and the Send FTP Password
specified in the Fabricate request as password;
-
The connection to the server is from the host or IP address specified
in the Fabricate request.
In addition, the server will not accept a file unless:
-
The transfer mode is the correct one for the file's type (e.g., ASCII
for a CIF file, binary for a GDS COMPRESSED file, etc),
-
The file is stored under the name specified in the Fabricate request,
-
The file can be decompressed if it was compressed,
-
The checksum computed on the received file matches the one specified
in the Fabricate request.
A "send" transfer request remains pending until either the design file
is successfully transferred, transfer authorization expires, or a
Cancel-Fabrication request is processed. If you need to change the
checksum or layout format after you have requested a "send" file
transfer, you must cancel fabrication and submit another Fabricate
request with the new values.
To ensure that design files cannot be retrieved from the design
file FTP server, the server does not implement the RETR command,
which is used to retrieve files from an FTP server.
Customers who use the e-mail interface must use the new
LAYOUT-FTP-SEND-AUTH parameter to authorize a "send" ftp. The syntax
of this parameter is:
-
LAYOUT-FTP-SEND-AUTH: !host!password!file!hours!
WHERE:
-
host
-
The name of the Internet host or IP address from which you
will connect to the MOSIS design file FTP server. If you use
an Internet Service Provider to connect to the Internet, you
may be assigned a different IP address each time you connect.
If this is the case or if you have a fixed IP address but
don't know what it is, just ftp to the MOSIS design file ftp
server. The server will display your IP address in the
initial greeting it sends when you connect to it. This
greeting is sent before you login, but you can use the invalid
user name "anonymous" if your ftp client software won't
connect to the server without a user name.
-
password
-
The password you will supply to the server when you login.
Passwords are case-sensitive. (You must supply the
project's design number as the user name.)
-
filename
-
Name of file you will store on the server.
-
hours
-
The number of hours until authorization expires (optional). It can be
a real number (e.g., values like 0.5 are allowed). Default is 8 hours
if not specified and the maximum allowed is 24 hours.
NOTE: The example below uses "!" as the field delimiter.
-
REQUEST: FABRICATE
DESIGN-NUMBER: 67890
LAYOUT-FTP-SEND-AUTH: !myhost.mycompany.com!si932!adder.gds!
LAYOUT-FORMAT: GDS
TOP-STRUCTURE: CHIP
CRC-CHECKSUM: 1234567,23456
REQUEST: END
In the example above, execution of a Fabricate request with these
parameters authorizes transfer of the design file via the design file
FTP server. Authorization expires after 8 hours. In this case, the
sender must login to the server as user "67890" with password "si932"
from host "myhost.mycompany.com". The file must be stored under the
name "adder.gds."
-
NET-ADDRESS
username@sitename {,username@sitename, ...} <1 line>
-
Note: MOSIS will send all replies to requests only to above net
address(es). It is very important that net address(es) be kept
current throughout the lifetime of the project. Use the
REQUEST:
UPDATE template to modify net-address(es) if necessary. Only one
line up to 255 characters of net-addresses can be read by our
software.
-
NUMBER-PARTS-FUNCTIONAL
<number>
-
Number of parts which were tested and worked as expected.
-
NUMBER-PARTS-RECEIVED
<number>
-
Number of parts parts you received for this project. You should count
all parts received, both packaged and unpackaged, regardless of
whether they were received in one shipment or in multiple shipments.
-
NUMBER-PARTS-TESTED
<number>
-
Number of parts tested to determine whether they worked as expected
-
PACKAGE-NAME
<1 line>
-
Use to specify the name of a
package
available through MOSIS in which your design is to be packaged.
If you want MOSIS to select a package for you based on your design
size and pad count, enter the word "DEFAULT." If you don't want any of
your parts packaged or constrained in size by a package, leave this
field blank. If you want to receive unpackaged parts, but intend to
package the parts yourself in a package known to MOSIS, enter the
package name in this field and a zero in the
QUANTITY-PACKAGED field. If you want your
parts packaged in two or more different packages, you must request it
in SPECIAL-HANDLING. Please note that
there are additional charges for multiple packages.
-
PAD-COUNT
<number>
-
Number of bonding pads for the project.
-
PART-SPEED
<number>
-
The measured speed of the parts. Leave blank if not applicable to your
project.
-
PHONE-NUMBER
<1 line>
-
Telephone AND fax numbers where customer can be reached.
-
PO-NUMBER
<number>
-
For commercial customers only; specifies purchase order number
authorizing the fabrication of your project. The number must be
exactly as it appears on the physical P.O. (this includes any
non-alphanumeric characters such as hyphens).
-
PROJECT-URL
<1 line>
-
The URL for the web site for your project. Leave blank if none.
-
QUANTITY-ORDERED
<number>
-
Allows you to order more than the minimum number of parts (sum of
packaged and unpackaged parts). Arbitrary quantities are not
acceptable. Please refer to the
Prototype Lot Quantities
page for available quantities. Also see the
QUANTITY-PACKAGED and
QUANTITY-UNPACKAGED parameters.
-
QUANTITY-PACKAGED
<number>
-
The number of parts to be delivered packaged in the package named in
PACKAGE-NAME. If you want all parts
packaged, enter the word "ALL." If you leave this field blank but
enter a number in the
QUANTITY-UNPACKAGED field, any remaining
parts from your explicit or implicit
QUANTITY-ORDERED will be packaged. If you want
to constrain the size of your die to fit in a package, but don't want
MOSIS to package any of the parts, enter a zero and make sure you
provide the name of a
package available through MOSIS.
-
QUANTITY-UNPACKAGED
<number>
-
The number of parts to be delivered unpackaged (as loose die). If you
want all parts unpackaged, enter the word "ALL." If you leave this
field blank, but enter a number for the
QUANTITY-PACKAGED, any remaining parts from
your explicit or implicit QUANTITY-ORDERED
will be delivered unpackaged.
-
QUOTE-ID
<number>
-
If MOSIS has given you a quote id, please enter it here. Otherwise,
leave this field blank.
-
REPORT
<n lines to end of message or to next line starting with
REQUEST>
-
Sends user report to MOSIS on the performance of a fabricated project.
-
ROUTING-LABEL
<n lines>
-
Upon completion of the fabrication process, parts are placed in
static-dissipative carriers and sealed in individual envelopes, which
are then placed in boxes and shipped to our customers. Parts that
were submitted for fabrication under a commercial account are shipped
to the address specified on the purchase order. Parts that were
submitted under a research or education account are sent to the
shipping address associated in our database with the account. Input
to the optional ROUTING-LABEL parameter is used to generate a label
that will be placed on the envelope inside the shipping box. The
label is not used for shipping, but for internal routing from the
destination point.
Note: As with input to all MOSIS parameters, colons should be avoided
because they are used to terminate parameters.
-
RUN-TYPE
<1 line>
-
The type of run for which project is being submitted. There are three
options. Chose only one.
SCHEDULED:
Most users
should choose the default, which is a scheduled
multi-project run shared with other customers.
DEDICATED:
A dedicated single
customer run is an "on demand" run which is only for customers who
want an entire run to themselves, to be closed on the date they
choose. Dedicated run pricing must be negotiated with MOSIS Customer
Support.
TRUSTED-FOUNDRY:
A Trusted Foundry run is sponsored by DARPA and is only
available to projects authorized by DARPA.
-
SPECIAL-HANDLING
<n lines>
-
Specifies special size, bonding and shipping requests not already
requested. Use only to provide instructions not covered by other
parameters.
-
SUBMITTER
<1 line>
-
The name of the person submitting the report. If you are submitting
the report on behalf of someone else (e.g., an administrative
assistant submitting a report for a university professor), you should
use the name of the person for whom you are submitting the report.
-
TECHNOLOGY-CODE
<1 line>
-
Project technology (See
MOSIS Technology Codes).
-
TOP-STRUCTURE
<1 line>
-
Specifies the case-sensitive top structure in your layout design file.
Required only if your format is GDS.
|
Related Links
Fabrication Schedule
Customer Support
MOSIS Products
|
|
|
